Factory MBOM

Factory MBOM Overview

The planner's Factory MBOM export: the same cut list and BOM as your Blueprint PDF, downloaded as machine-readable JSON and CSV for ERP, MES, and cutting tables.

Updated 27 October 2026

Factory MBOM is a capability of the Scalarcut tiling planner, not a separate app. It is a distinct product from the Online Store Widget: the widget plans a shopper's room on a storefront and hands SKUs to the cart, while Factory MBOM turns a planned layout into a machine-readable manufacturing bill of materials.

What it is

Factory MBOM turns a room planned in Scalarcut into structured manufacturing data: the same millimetre cut list and bill of materials as the Blueprint PDF, in a machine-readable form your ERP, MES, or cutting table can read.

The planner already does everything you need to plan a room: 2D/3D layout, catalog products, cut list, estimate, and blueprints. Factory MBOM adds one thing — a Factory MBOM button in the planner header that downloads the layout as structured data.

How it works

  1. Plan. A designer prepares a tile layout in Scalarcut — dimensions, tile, pattern, openings, cut list, and estimate. Sliver Guard re-anchors thin cuts and the Cut Recycling Engine reuses offcuts.
  2. Export. The designer clicks Factory MBOM to download the JSON and CSV, or an integration pulls the same document over the authenticated HTTP API.
  3. Map. An integration maps the exported fields to the receiving system (ERP, MES, or cutting table).
  4. Consume. The receiving system uses the data in its own production workflow.

Exporting structured data does not, by itself, mean Scalarcut drives a cutting table, creates production orders, or integrates automatically with a particular ERP — the mapping and downstream workflow are yours.

JSON vs CSV

Capability JSON CSV
Individual pieces and cut dimensions Yes Yes
Full document structure and metadata Yes No
Packing, recipes and totals Yes No
Optional geometry data If present in the export No

The JSON document is versioned (scalarcut.factory_bom.v1.1). The CSV is a flat piece list — the same columns as the JSON pieces, without packing, ids, rates, totals, or the optional geometry.

A piece may include an optional geometry object. This is not richer hidden geometry the Blueprint PDF omitted — it is the same leftover shape the PDF already shows, expressed as structured millimetre vertices for integrators that consume leftover polygons. It is not a CNC toolpath. See the Schema Reference.

What the document contains

  • Header — schema version, scene/project identity, unit policy (metric, mm).
  • Pieces — one entry per cut group: width and height in millimetres, cut type, quantity, fragility flags, L-cut and recycling metadata.
  • Recipes — the Cut Recycling Engine plan, so each cut is traceable to the blank it came from.
  • Consumables — frozen adhesive, grout, and primer rates, computed from the actual layout geometry.
  • Totals — a rollup across all surfaces for audit against the blueprint.

Factory MBOM vs. the Online Store Widget

Online Store Widget Factory MBOM
Audience Shoppers on a product page ERP / MES integrators, production
Where it lives /v1/tiling iframe + SDK on your storefront The planner's header export button
Output SKUs + quantities into the store cart scalarcut.factory_bom.v1.1 JSON / CSV download
Geometry Screen layout Integer mm cut geometry
Consumables Opt-in cart lines Frozen rates, always emitted
AI rendering Disabled by default Not applicable

The two products share the same layout math and cut engine, but their surfaces and integrations are deliberately separate.

Who it is for

  • Manufacturers and importers who want their dealers' plans to drop straight into production.
  • Factories and cutting services that receive plans and need a deterministic cut list.
  • System integrators building the bridge between Scalarcut and an ERP or MES.

Where to go from here