Order Twin

A real-time digital replica of every order, from placement through final delivery.

Talk to an Outcome Advisor

Know exactly where every order stands, from PO to final delivery, without switching systems.

The Order Twin connects the commercial side to the physical side, modeling the order, its line items, its deliveries, and its shipments as one live structure instead of scattered records. A 50 line purchase order split across 12 deliveries and 4 carriers stays a single order you can actually follow, not something you have to reassemble by hand across three systems.

Supply Chain Objects Modeled

​

Purchase Order (PO)

An inbound order placed with a supplier. Carries supplier details, ship-to facility (GLN), required delivery date, commodity info. Lifecycle: Created, Open, In Transit, Partially Delivered, Fully Delivered, Cancelled, Closed.
​

Sales Order (SO)

An outbound order committed to a customer. Carries customer details, ship-from facility, ship date, delivery terms. Lifecycle: Created, Open, Ready to Ship, Dispatched, In Transit, Delivered, Cancelled, Closed.
​

Stock Transfer Order (STO)

An internal movement between your own facilities: DC to DC, plant to warehouse, warehouse to store.
​

Production Order

An order tied to a manufacturing schedule. Links raw material inbound shipments to production line requirements for line-down risk prediction.
​

Line Item

An individual SKU within an order: product code, ordered quantity, shipped quantity, received quantity, unit price. Supports batch and lot-level tracking.
​

Delivery

A fulfillment unit grouping one or more line items shipped together. A single order may have multiple deliveries. Each links to physical shipments in the Shipment Twin.
​

Risk Score

AI-generated assessment of each order's likelihood of arriving on time and in full, continuously updated as shipments move and conditions change.

Execution Systems Ingested

ERP
SAP (S/4HANA, ECC), Oracle (Cloud, E-Business Suite). POs, SOs, STOs, production orders, line items, delivery schedules, goods receipt. Integration via REST API, SOAP, or iDoc/BAPI.
OMS
Manhattan OMS, IBM Sterling, custom platforms. Sales orders, fulfillment status, allocation decisions.
WMS
Manhattan WMS, Blue Yonder WMS. Picking confirmation, loading confirmation, shipment-to-delivery linkage, goods receipt.
TMS
Shipment-to-order mapping. When a shipment is created against a PO, the Order Twin automatically links physical movement to the commercial order.
Supplier Systems (via Sam)
Commercial invoices, packing lists, BOLs, and ASNs submitted by suppliers. Sam extracts structured data and links to the corresponding order.

When you need this Twin

Procurement creates POs in SAP but has no visibility into whether those orders are physically moving, at risk, or stuck.

Customer service spends significant time answering WISMO inquiries by toggling between ERP, TMS, and carrier portals.

You have OTIF penalty exposure but discover at-risk orders too late for corrective action.

Split shipments, partial fills, and multi-mode orders create complexity your current systems cannot model in a unified way.

Planning teams lack forward-looking order risk signals. The ERP shows what was supposed to happen; nobody shows what will actually happen.

Stock transfer orders between your own facilities are invisible. Inventory is "in transit" in SAP but nobody knows when it will actually arrive.

Core Capabilities

Capability
Description
End-to-End Order Lifecycle
Visibility from order creation through every stage. Each transition timestamped and attributed to the responsible party (supplier, carrier, facility).
Full Order Hierarchy
Models Order to Line Items to Deliveries to Shipments. A PO with 50 lines, 12 deliveries, 8 shipments across 4 carriers is one connected graph.
Order Risk Scoring
AI-driven risk assessment against carrier reliability, lane performance, weather, and facility patterns. High-risk orders surfaced days before impact.
OTIF Performance Analytics
Real-time On-Time In-Full at order, line item, supplier, carrier, and lane level. Automated root-cause attribution for every miss.
Bidirectional ERP Sync
Status updates, delivery confirmations, and risk alerts flow back to your ERP via API or callback events.
Agent Integration
Cassie resolves WISMO inquiries. Sam detects document mismatches. Tracy prioritizes carrier follow-ups by order value and customer criticality.

Frequently Asked Questions

Your ERP knows what was ordered. Your TMS knows what shipped. Neither holds the real-time connection between the two, enriched with predictive ETAs, risk scoring, and agent-powered resolution. The Order Twin bridges commercial systems and logistics execution into one continuous model.

Purchase Orders (PO), Sales Orders (SO), Stock Transfer Orders (STO), and Production Orders (via linkage to inbound material POs). Each type has its own lifecycle stages. The data model is the same for all: Order to Line to Delivery to Shipment.

The Order Twin and Shipment Twin are tightly coupled: every delivery links to shipments, and shipment events automatically update order status. The Inventory Twin consumes order data as demand/supply signals. The Facility Twin uses order data for appointment scheduling and labor planning.

One billion hours 
of operational work completed by AI agents over the next decade

Talk to an Outcome Advisor