Create one durable order record
Whether an order begins in checkout, a form, email, or a staff-created draft, convert it into one durable record with the customer, items, payment state, fulfillment method, source identifiers, and current owner together.
Do not treat a confirmation page or a single notification as proof that downstream work happened. Payment and commerce systems use asynchronous events, retries, and status transitions, so fulfillment must be safe when the same signal arrives more than once or arrives out of order.
Automate the standard lane and expose exceptions
A standard order can be acknowledged, routed, and advanced through defined statuses automatically. Missing inventory, conflicting delivery instructions, payment uncertainty, unusual discounts, substitutions, and policy exceptions belong in a visible queue.
- Validate required customer and fulfillment information
- Use source IDs and idempotency controls to prevent duplicate work
- Record each status transition and the event that caused it
- Notify staff only when an action or exception needs attention
- Give customers updates that match the internal state
Test failure paths before increasing volume
Test duplicated events, delayed events, partial fulfillment, cancellations, refunds, unavailable products, and orders that mix pickup with shipping or delivery. Confirm who can recover each state and what the customer sees.
Automation is ready to expand when a repeated signal cannot create a second fulfillment and every unresolved order has an owner, a current state, and a safe next step.