Enterprise · Factory MBOM

Automate the tile cutting layout into a manufacturing BOM JSON.

Storefront layout in, factory data out. Factory MBOM (Manufacturing Bill of Materials): the same millimetre engine that builds the blueprint PDF exports machine-readable manufacturing JSON — a web-to-factory ERP data pipeline for flooring. Schema scalarcut.factory_bom.v1.1. Pieces in millimetres, FRAGILE flags, cut-recycling recipes, box packing. SAP, Oracle, 1C, or MES ingest it. Nobody retypes the sheet.

Download sample Factory MBOM (JSON)

Web layout to factory desk — one schema

Unified pipeline: storefront to cutting desk. No screenshot of a calc, no offline CAM in the middle. Waste recovery (recipes[]) and logistical packing (pack_mode) ride in the same payload.

  1. LAYOUT

    Customer or consultant runs millimetre layout on the product page or in Tile Layout Studio.

  2. JSON

    Schema scalarcut.factory_bom.v1.1 — pieces, FRAGILE, CRE recipes, full boxes plus loose tiles.

  3. FACTORY

    SAP, Oracle, 1C, or MES ingest Manufacturing BOM (MBOM) fields without retyping a sheet.

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 on the product page 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.

Storefront in, factory out

Pairs with the enterprise iFrame: millimetre layout on the product page, Factory MBOM JSON on the other side of the web-to-factory pipeline.

What IT needs before go-live

SSO and access control, a versioned JSON schema, and an enterprise-first deprecation policy. SLA and MSA numbers are scoped in sales.

  • SSO / directory access

    SSO / directory access for the data pipeline.

  • Stable Factory MBOM JSON

    Stable Factory MBOM JSON for cutting-desk ingest.

  • Versioned schema

    Versioned schema (scalarcut.factory_bom.v1.1) so ERP parsers are not surprised by breaking changes.

Preview the machine-readable manufacturing BOM

Download the sample, open the storefront iFrame, or call the MBOM API with an Enterprise Key. Schema scalarcut.factory_bom.v1.1 — prices stripped. Use Try MBOM API below to load the JSON into this panel.

Download sample Factory MBOM (JSON) Storefront iFrame

Example request

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

Frequently asked questions

The same millimetre CAD that draws the installer blueprint also exports Factory MBOM JSON (schema scalarcut.factory_bom.v1.1): piece sizes, cut types, packing, recycling recipes, and room totals. Enterprise Key required for production export.

A versioned document your plant and ERP can ingest without retyping a sheet. Scalarcut Factory MBOM lists pieces in millimetres, FRAGILE flags, CRE parent or recycled rows, L-cuts, box packing, and consumable rates.

Layout runs on the storefront (enterprise iFrame) or in Tile Layout Studio. Factory MBOM is the outbound JSON: stable IDs, order pieces or full boxes plus loose tiles, recipes for leftover strips. SAP, Oracle, 1C, or MES map those fields into the job.

Yes as an ingestible JSON contract, not as a native SAP module. You map scalarcut.factory_bom.v1.1 into your ERP item, cut, and packing tables. Preview the sample, then .

No separate nesting API. Cut-recycling recipes (recipes[]) pack leftover strips from the millimetre lattice — CRE parent, recycled pieces, leftover sizes — ready for the cutting desk. Cut-recycling recipes (recipes[]) pack leftover strips for the cutting desk — nesting for this export, not a separate API.

No. The public fixture is prices stripped so you can see fields without retail data. Production runs can carry catalog SKU; price is your ERP’s job.

Normally a company buys a web visualizer, staff manually turn those designs into an Engineering BOM (EBOM), then a factory engineer translates that into a machine-ready Manufacturing BOM (MBOM). Factory MBOM is the millimetre layout as manufacturing JSON so SAP, Oracle, or MES can skip that double translation.

Yes as an ingestible contract those systems can map — not as a certified native SAP, Frontier, or OptiPro module. Preview the sample, then .

CAD/CAM nesting usually runs offline on a factory desktop, isolated from the customer website and needing a trained technician. Scalarcut unifies the pipeline: enterprise iFrame on the product page, real-time scalarcut.factory_bom.v1.1 JSON out to the cutting desk or ERP.

Yes. GET /v1/tiling/factory-bom on the embed host with X-Widget-Key (or a Bearer widget token) returns the fixture as ingestible scalarcut.factory_bom.v1.1 JSON. Use the try button or curl on this page, then .

Yes. The MBOM API supports two-way integration with an Enterprise Key: GET to pull Factory MBOM JSON, and POST so your ERP or middleware sends room, opening, and tile parameters into our millimetre engine and receives scalarcut.factory_bom.v1.1 for the cutting desk or MES. Use Try MBOM API on this page to inspect the outbound document, then .

Scalarcut © 2026, All rights reserved.

ИП Аль-Хатиб А. Ф. UNP 692111656 Ул. Сологуба, 20. Столбцы, РБ. State registration certificate No. 0883388

bePaid

All rights reserved.