Questions, answered

Click Get started, then use Proto to configure OMS for Food and Beverage D2C for your business. Pilot one fulfillment organization, a small product list and an order with a normal shipment and an exception.

A customer order identifies its owner, customer, ship-to customer, promised date, status, revision and net USD amount. Order lines hold products, quantities, prices and lot and best-by detail.

The coordinator confirms line amounts and moves the Draft order to Review. A reviewer examines the current revision and linked exceptions before recording an independent decision.

Each product carries a storage regime. Fulfillment events can record temperature and cold-chain state at handoff, while exceptions keep the investigation tied to the order.

An order line can hold its lot number and best-by date. A fulfillment event can also retain the lot used in the recorded action.

A handoff links to the order and can hold a channel, handoff time and carrier reference. The operations team reviews submitted handoffs before approval.

A cold-chain exception records the type, owner, detail and resolution. The investigator works the case against the order and related fulfillment events.

Payment evidence holds a status, method, USD amount and provider reference against the order. The payment analyst uses those records during completion review.

Completion reconciliation compares lines, fulfillment events, payment evidence and operation receipts. A discrepancy is recorded for investigation with a failed receipt and open exception.

Keep its executed evidence. Record an escalation decision and compensating operation receipt so the later resolution remains traceable.