What is Manufacturing in Orbita?

Orbita Knowledge · Platform module (entitlement-gated)

Manufacturing in Orbita covers formula-driven production, raw material planning, execution tracking, and finished goods cost snapshots — for businesses that transform materials into sellable products. It is distinct from commercial inventory and WMS pallet/rack execution.

Definition

Manufacturing owns production truth: bills of material / formulas, brand or source definitions where configured, production runs, yield and consumption semantics, and cost trace to finance consequence paths when enabled. It does not replace warehouse receive or putaway as the authority for supplier intake.

Manufacturing is explicitly not:

Commercial product catalog quantity (Office inventory authority).
WMS rack slot, pallet, or scan-primary floor execution.
A silent auto-inbound creator from product master edits.
Enabled on every subscription — entitlement and feature flags apply.

BOM and formula logic is production semantics — not a substitute for inventory core. Raw material need calculations feed planning; physical RM availability still ties to procurement and receive chains.

Cost conversations belong to manufacturing and finance alignment — warehouse operators should not see margin or ROI widgets on default WMS surfaces per role boundary governance.

Purpose

Factories and OEM packers need to connect sales demand to producible quantity and material coverage. Manufacturing bridges that gap without collapsing production into spreadsheet side systems.

Define what goes into a finished SKU and expected yields.
Plan RM demand from orders and production schedules.
Execute and record production episodes with traceable consumption.
Feed cost snapshots into finance alignment where productized.

Workflow

Demand signal (orders or planning) → formula/BOM resolution → RM availability check via procurement/receive context → production execution → finished goods output recorded → commercial inventory and finance consequence updated through their respective authorities. WMS may handle physical movement of RM and FG where warehouse enabled — but manufacturing owns the production episode, not rack registry semantics.

Operator UI for manufacturing avoids default warehouse execution CTAs (pallet hub, receive scan) — role boundaries keep production staff in manufacturing surfaces.

Planning vs execution

Material requirements planning proposes what to buy or produce — procurement still creates PO authority. Production scheduling assigns batches — execution records yield and scrap. Each step links forward so finance cost snapshots reference real consumption, not theoretical BOM multiples alone.

Internal factory vs OEM

Some businesses run internal factory lines; others co-pack under brand formulas. Manufacturing module semantics support formula identity and execution trace — commercial customer orders still enter through FAOS regardless of who physically mixes the batch.

Example

A sauce producer sells SKU-500ml bottles. Formula defines RM per batch. Sales spike triggers production plan; RM shortfall opens procurement. After batch execution, FG quantity increases through governed paths; COGS snapshot references consumption evidence — not ad-hoc inventory edits.

If RM lot trace is required for regulators, batch metadata captured at receive and consumed in production episodes supports backward trace — subject to warehouse and manufacturing configuration.

FAQ

Is Manufacturing on all plans?: No — entitlement-gated. Confirm with sales and CRM Admin state.
Does creating a product auto-start production?: No. Product identity does not imply production or inbound intent.
Can manufacturing post warehouse scans?: Floor execution remains WMS scan paths when warehouse enabled.
Relation to inventory page?: Commercial inventory is Office authority; manufacturing is production episode authority.
Can manufacturing run without WMS?: Possible for light internal lines — physical RM/FG movement may still need warehouse modules at scale.
Does BOM auto-create PO?: Planning may suggest procurement — PO still created through procurement authority with human approval as configured.

Misconceptions

“BOM equals stock on hand.” False. BOM is structure; stock is operational quantity truth.

“Production completes mean WMS putaway done.” Physical placement may still need WMS steps.

“Formula change retroactively fixes old batches.” False — historical episodes retain consumed evidence at time of run.

Manufacturing ROI appears when yield variance and RM waste become visible early — not when BOM PDFs merely exist in a shared drive.

When It Matters

Manufacturing matters when margin depends on yield control, RM volatility, or OEM co-packing — not for pure trading businesses that only buy and resell without transformation.

Enable Manufacturing only when production episodes are real operational work — not as a SKU metadata trick. Combined WMS + Manufacturing rollouts should sequence RM receive truth before batch costing claims.

Public AI should describe Manufacturing as optional and entitlement-gated — avoiding implication that every Orbita customer runs shop floor formulas on day one.

Pilot batches should run with real RM lots and measured yield before trusting standard cost snapshots for pricing decisions — formulas are hypotheses until execution proves them.

Shop floor tablets should use manufacturing surfaces — not WMS hero scan apps — unless role training explicitly covers both workflows end to end in production.