Integrations
Connect production evidence and commercial work with controlled imports and handoffs.
Connections are scoped and configured during implementation. Agree the system that owns each fact, the supported action and how uncertain or rejected work will be resolved. An imported result or acknowledged message is evidence of receipt by a connection; its operational meaning still follows the reviewed contract.
- Products, suppliers and orders
- Product and recipe importsin and out
- Supplier documentsin
- Customer ordersin and out
- Production and quality evidence
- Production reportingin and out
- Laboratory and inspection resultsInspectionResults · in and out
- Storage and process observationsin and out
- Labels and packingin and out
- Delivery and financial work
- Warehouse and carrier eventsin and out
- Finance and bankingin and out
- Withdrawal coordinationin and out
- Agents
- Your agentWorks within the permissions you assign
Products, suppliers and orders
- Product and recipe imports. Map identifiers, recipe revisions, units, fixed conversions and approved specifications. Preserve the version actually used by existing batches and validate incompatible measurements before accepting new work.
- Supplier documents. Link purchase terms, lot identifiers and specification evidence to the correct supplier and receipt. Imported documents cannot establish accepted stock or quality release without the required review.
- Customer orders. Preserve external order identity, product, pack and delivery requirements. Repeated imports update eligible work through the controlled action rather than creating another commitment or shipment.
Production and quality evidence
- Production reporting. Map actual batch, operation, input population, output and measurement basis. Resolve duplicate or uncertain events before releasing their claimed quantity for another action.
- Laboratory and inspection results. Retain the specification, method, unit, sample, source and result revision. A result does not independently approve release or clear an unrelated hold.
- Storage and process observations. Identify the device or recorded source, time and affected scope. Connections to sensors or monitoring systems require their own configuration and failure handling; manual evidence remains distinguishable.
- Labels and packing. Verify product, lot, packaging revision and authorized print or packing scope. A successful print message does not prove correct application to goods or change their date history.
Delivery and financial work
- Warehouse and carrier events. Keep actual handover, delivery acceptance and exception evidence separate. A transport acknowledgment cannot invent title transfer, recover lost goods or reopen previously performed delivery.
- Finance and banking. Map company, account, document and currency identities with exact reconciliation. Preserve actual settlement, current carrying and the difference between bank confirmation and a request awaiting an outcome.
- Withdrawal coordination. Prepare recipient work from the reviewed affected scope. Sending notices requires explicit authorization and a configured channel; the system records responses without claiming statutory notification is complete.
How connections are governed
service accounts, audit, pausingUse restricted service identities, durable external keys and source-bound actions. Replays with the same content preserve the original result; conflicting content and unknown outcomes remain visible for resolution. Reconcile quantities, value and event history before expanding access. Machine work and retained data follow the published pricing rules.
The API is one more client of the same interface. AI assistants and API →