Enterprise · Factory MBOM

Turn room layouts into manufacturing data

Connect product-specific room planning with your factory, ERP or MES workflow. Scalarcut converts the calculated layout into structured Factory MBOM JSON, including piece dimensions, cuts, quantities, packing information and supported cut-recycling data. Your systems can use this data without someone manually rebuilding the project from a PDF or spreadsheet.

Download sample Factory MBOM JSON

From layout to production data

A room layout contains more than a total quantity. It can describe individual pieces, cut dimensions, openings, fragile strips and the way products are packed. Factory MBOM makes that information available in a structured format that your integration layer can map into downstream business or manufacturing systems.

  1. CREATE

    You plan the room in the Scalarcut planner the same way as any job — dimensions, tile, pattern, openings.

  2. EXPORT

    Click Factory MBOM in the planner header to download the JSON and CSV, or pull the same document over the API.

  3. CONNECT

    Your ERP, MES or middleware maps the fields to your internal product, job, inventory or cutting workflow.

Two worlds, one millimetre schema

Legacy ERPs and offline CAD/CAM both need geometry. Factory MBOM is the bridge — not another desktop tool and not another square-metre guess.

ERP / MES ingest geometry

SAP (discrete manufacturing), Oracle, Frontier ERP (Friedman), OptiProERP, 1C, and industry MES stacks.

They turn raw data into a Manufacturing BOM (MBOM) for inventory, routing, and work centers. They do not compute millimetre tile layouts natively — someone retypes a static sheet or a calc export. Scalarcut JSON lets the ERP speak geometry.

CAD/CAM & nesting desks

Architectural fabrication software and CNC nesting engines on the cutting floor.

Factory MBOM carries the same millimetre cut geometry in the planner and in the outbound JSON. Cut-recycling recipes[] pack leftover strips for the cutting desk — nesting for this export, not a separate API.

What operations and IT actually get

Trace every run

Stable project_id, scene_id, and surface_id on every export so the same job maps in ERP, 1C, SAP, or Oracle.

Order pieces or boxes

order_pieces, then full_boxes plus loose_tiles (pack_mode: full_boxes_plus_loose). Ops orders without rebuilding the count.

A cut list the saw can follow

Size in millimetres, cut type, quantity, FRAGILE, CRE parent or recycled, and L-cuts — the same millimetre truth the saw and the ERP share.

Waste that becomes stock

recipes[] leftover strips for the cutting desk. This is cut-recycling on the millimetre lattice — not a generic nesting optimization API.

Consumables in the same rollup

Adhesive, grout, primer, and net area in one totals object with the pieces.

Planner in, factory out

Plan the room in the studio, click Factory MBOM, and feed the JSON into the other end of the web-to-factory pipeline.

Preview the machine-readable manufacturing BOM

Download the sample JSON, open a project in the planner and click Factory MBOM, or call the MBOM API with your Enterprise Key. Schema scalarcut.factory_bom.v1.1 — prices stripped. Use Try MBOM API below to load the JSON into this panel.

What the data include

  • Individual piece dimensions and quantities
  • Cut types, including supported complex cuts
  • Flags for fragile or narrow pieces
  • Product and project identifiers
  • Full-box and loose-piece packing information
  • Supported cut-recycling recipes
  • Calculated project totals and supported consumables
Download sample Factory MBOM JSON

Example request

curl -sS -H "X-Enterprise-Key: sc_bom_playground_local_not_for_production" "https://embed.scalarcut.com/v1/tiling/factory-bom"
{}

FAQs

Factory MBOM is the planner's structured manufacturing-data export. You plan a room in Scalarcut, click Factory MBOM in the header, and download the same cut list and bill of materials as the Blueprint PDF — as JSON or CSV your systems can read.

Factory MBOM provides structured JSON that can be mapped into those systems. The required integration depends on the target system and its available interfaces.

A Blueprint PDF is a human-readable project document for reviewing, sharing and carrying out the work. Factory MBOM is structured data intended for software systems and downstream manufacturing workflows.

Yes. The schema can include individual piece dimensions, quantities and supported cut details. The precise fields depend on the schema version and available project data.

The schema supports cut-recycling recipe data for supported layouts. This is structured information about reusable offcuts.

They're two different products. The Online Store widget plans a shopper's room on a storefront and hands the SKUs and quantities to a cart. Factory MBOM exports from the Scalarcut planner, where you plan in 2D/3D. They share the same layout engine, but the export lives in the planner.

Yes. Your middleware calls the Factory MBOM API with your Enterprise Key to pull the scalarcut.factory_bom.v1.1 JSON for a project by scene or project id. The API is a GET pull — the layout is created in the planner, not sent to the API.

The public sample is intended to demonstrate the data structure and does not include retail prices. Production catalog and pricing fields depend on the agreed integration.

Download the sample JSON to see the structure, then . We'll map your target system, required fields and intended workflow, and issue production access.