Answered Questions

Same working day batch processing (v1). Real-time/immediate is the v2 goal once the system is proven.

Process each item independently based on available info and produce a partial quote. Items with enough info get proposed products. Items without enough info are flagged as "insufficient spec — team to complete." Do not hold the whole quote because one item is ambiguous.

No. Team searches competitor datasheets, product websites, and Google manually for each request. No spreadsheet or formal table exists.

• Lumen: equal or higher. Lower is rarely approved — "difícil de ser aprovado"
• IP: equal or higher minimum. Higher is always fine — "Se for mais alto, nosso stress... se for mais baixo é que é pior"
• Dimensions: critical for recessed. Never propose smaller than the existing ceiling cutout.
• Voltage: flexible — lens variations between manufacturers mean exact match is not required.
• CRI: important but no specific threshold given.
• Wattage: not a hard filter, but significant overspec is also problematic (30W req, 60W proposed = "quase certeza" rejected).

Propose the closest alternative and send the technical datasheet. Client validates on their end. If the product is very different, no proposal is sent at all.

No. Higher IP is always accepted. Lower IP is the problem.

Partial quote: provide what you can, flag the missing items. Client can look elsewhere for the rest.

Yes. Always goes to human analysis. "Sempre analisado por nós para confirmar" — either an existing Aronlight product is found or the factory is contacted for a custom product.

Propose the closest available product. No back-and-forth asking for more details.

Dimensions win for recessed products. The proposed product can never be smaller than the existing ceiling cutout. "Não pode ser algo mais pequeno."

Philips, Katoa, Kleamer, Carismaluce, Aura Light, iGuzzini, LDV. Team confirmed these and noted they can provide a fuller list.

Propose the non-DALI version. Never offer DALI as an upgrade unless explicitly requested.

Both. Quick PVPs (price lists) are sent by email first, especially to Spain. All proposals must eventually go through Odoo as a formal requirement.

Always under the distributor/intermediary. "Sempre distribuidor." End project clients often do not exist in Odoo at all.

consultas@ handles Portugal. pedidos@ handles Spain. Italy and France go via agents and land in the Portugal Odoo instance (company_id=3).

PVP is general for all clients. Discounts are stored in the client record in Odoo and applied per distributor/installer tier. No separate price list entity.

Three sources:

• PSU for LED strips: 20% buffer rule (100W load requires 120–150W supply minimum).
• Connection pieces for linear multi-unit installations.
• Accessories as separate lines — clients rarely ask for them; team adds from product knowledge.

No formal documentation exists — team learns from colleagues.

Always separate lines. No kits or bundles exist in Odoo (mrp.bom phantom = 0). Clients usually do not ask for accessories; the team adds them.

Yes. ILDV- prefix SKUs are always separate lines. Not stocked due to unpredictable demand. Either manufactured new or drivers swapped in-house.

Often require DIALux/Relux lighting study post-proposal for equivalence validation. Sometimes client asks for the study only after the initial proposal is sent. Not fully automated.

No. ~30 structured fields exist (IP, DALI, power, CCT, dimensions, CRI) but 0–2% populated across 4,416 products. All specs live in the product name as free text. Matching engine must parse the name field.

Only 57%. 1,882 of 4,416 products have categ_id = "All" and are active, sellable products. Cannot filter by fixture type via category.

No — sequential by creation order. The prefix encodes the product line: ILAR = general catalog, ILDV = drivers, ILEM = emergency, PRJP/E/M/I = project projectors.

No. 136 of 852 partners with real sale orders have customer_rank = 0. Filter by rank misses ~16% of real customers.

Yes. 4,026 of 4,064 partners have no company_id set. A client can have orders in both companies. Must filter/disambiguate by company_id when searching orders.

~1.3× product lines per RFQ position after filtering out section headers. Of 63,958 sale.order.line records, 11,156 are notes/sections (display_type set). Filter those before counting.