EARLY-ACCESS GUIDE · UPDATED 29 September 2026
Orders, revisions and system ownership
Understand the records and connections needed for controlled order release.
This guide describes the service scope. Access and the workflow supported for your site are confirmed during onboarding.
Keep source and normalised values
Identify the source order, its revision and each line or unit. Retain the original customer codes alongside reviewed mappings. An unknown value needs resolution before it can be treated as an approved option.
Choose one authority for each record
An initial evaluation can leave commercial orders and inventory in existing software. Agree who owns customer details, accepted prices, product specifications, stock and despatch records. OrderFlow must not create a competing balance or silently overwrite an authoritative record.
Define the receiving contract
Agree the accepted payload, external identifiers, acknowledgement and retry behaviour. Repeated messages need duplicate protection. An uncertain handoff needs reconciliation before an operator sends it again.
Use the suite where it fits
ConfigSheets provides reviewed reference data and FactorySpec defines product requirements. LabelLogic, WorkSteps and KitProof address printing, instructions and kit verification. These are proposed integration boundaries; availability and supported contracts are confirmed separately.