Data flow โ stock hub to interco
How pricing data flows from the stock hub's master database into an interco entity's quotation, and the three rules a vendor implementation has to honour.
Step-by-step data flow
1
JIL maintains all master data
Product maintenance, HW cost, margin codes, aluminium finishes, freight rates โ all maintained centrally at JIL. These feed the list price engine.
2
JIL list price engine computes selling prices
Formula branches on product type (aluminium vs HW/accessories). Output = USD price per piece, per finish ร destination ร shipping mode.
Aluminium: (sqm/pc ร finish_sqm + kg/pc ร finish_kg) / (1 - product_margin) + (kg/pc ร freight) / (1 - freight_margin) Hardware: HW_list_price + (kg/pc ร freight) / (1 - freight_margin)
3
JIL list price pushed to interco as cost
The JIL list price for the relevant destination + shipping mode is pushed to each interco entity's database. This becomes their cost for the supply-only section of their BOQ. Currency conversion may apply (USD โ local currency).
4
Interco maintains local price table
Each interco office (JSZ, JBK, JSG, JKL, JHK, JBJ) maintains its own local price maintenance table in local currency. Covers 9 categories: local hardware, labour (partition / door frame / swing door / sliding door), clear glass, colourback glass, switchable glass, door glass. Bilingual descriptions (Chinese + English).
5
Interco BOQ = Supply (JIL) + Local (interco)
Section A โ Supply only: quantities ร JIL list price (pushed as cost); JIL also uses this section alone. Section B โ Local materials & installation: labour, local hardware, glass, powdercoat, cleaning, contingency + GP markup on installation, with unit rates looked up from local price maintenance. JIL does NOT have this section.
6
Profit sheet = Supply total + Local total + GP
The quotation engine computes Supply total (USD converted) + Local cost total + GP on installation = quote price to client. The profit sheet compares this against the actual JIL cost to derive the project margin.
Key implementation notes for the vendor
!
JIL = supply only, no local section
The BOQ builder must be entity-aware. When the entity is JIL, Section B must be completely hidden โ not just empty, but structurally absent. JIL quotations only contain supply prices.
!
Local price table is per-entity, per-currency
The local price maintenance table is NOT shared across interco entities. Each entity has its own copy with its own rates in local currency. The schema must support multi-entity isolation (entity_code as part of the composite key, or a tenant id).
!
Two-currency BOQ for interco
Interco BOQs display pricing in two currencies: the unit rate at cost (what the interco pays) and the unit rate for client quotation (with markup). Both columns are tracked per line item. GP on installation is a percentage markup on total local costs, configurable per entity.