Factory MBOM
Factory MBOM FAQ
Common questions about the Factory MBOM product, its API, and how it differs from the Online Store Widget.
Is Factory MBOM part of the Online Store Widget?
No. They are two separate products that share the same layout engine. The Online Store Widget plans a shopper's room on a storefront and hands resolved SKUs to the cart. Factory MBOM is a planner feature — an Enterprise user plans in the studio and exports the machine-readable manufacturing document. See the overview for the side-by-side comparison.
Does the widget emit an MBOM?
No. The storefront widget never produces scalarcut.factory_bom.v1.1; its output is SKUs and quantities — see the widget cart integration. The Factory MBOM export lives in the planner, not the embed.
How do I export the MBOM?
Plan the room in the planner as usual, then click the Factory MBOM button in the planner header. The planner downloads the JSON and CSV. See the Quickstart.
How do I authenticate the HTTP API?
For machine-to-machine pulls, send your Factory MBOM Enterprise Key as X-Enterprise-Key (or X-Widget-Key), or an embed widget HMAC token with typ=widget in Authorization: Bearer. You do not need the API to use the planner export. Full details in the API Reference.
Can I pull a live scene yet?
Not in this release. The endpoint currently serves the garage fixture (scene_id/project_id = 121). Any other id returns 404. Live scene/project pull is on the roadmap without breaking the existing contract.
Why millimetres?
The planner's internal lattice is metres, but production cuts are physical. The document exports canonical integer millimetres (w_mm / h_mm) and never emits inch columns, so a cutting table can consume it directly.
Are consumables included?
Yes. Adhesive, grout, and primer are always emitted as frozen rates and computed per surface and in totals. Unlike the widget cart, where consumables are an opt-in line, Factory MBOM always carries them so production never has to recalculate.
What does fragile mean?
A cut below the 50 mm floor that is likely to break during fitting. Route fragile: true pieces for manual handling.
Do group IDs stay the same across re-exports?
Yes. group_id is derived from the location and size, and legend letters follow group order. The same layout re-exports with identical ids and letters.
What about the boxes field?
boxes is a deprecated alias for boxes_to_order (the cartons to buy). Prefer boxes_to_order.
How do I map this into my ERP?
Start with ERP & MES Integration for the field-by-field mapping, JSON vs CSV guidance, and idempotent-pull advice.