Fulfillment and payments

A replenishment request starts work, but physical movement has its own evidence. Fulfillment Events records a dated event type, quantity, product and external event identifier against the customer order. The team can follow allocation, picking, shipment, delivery or return events while keeping the original order and its lines in view. This history helps explain differences between ordered and shipped units.

Payment Evidence records provider events against the same parent order. Its type distinguishes authorization, capture, refund and void. The verified state tells staff whether the provider event has been confirmed. A local payment record should retain the provider event identifier and reference so a repeated message can be investigated against the same source.

• Physical event. The quantity, product and date identify a fulfillment occurrence.
• Provider event. The payment type, amount and verification state identify financial evidence.
• Shared parent. Both trails link back to the customer order for reconciliation.

A delivery event and a captured payment answer different questions. The first says what the physical event source recorded. The second says what the payment provider reported and whether it has been verified. The Order Coordinator can compare both with the order’s commercial amount, but should not infer one from the other.

Choose the source of fulfillment events and the source of payment confirmations. Map their external identifiers before importing history. Agree who reconciles duplicate or late events, particularly when a physical return or refund is involved. Product identities must use the same SKU convention as the order lines for useful comparison.

For a pilot, define how line quantities will be updated from event history and who resolves a discrepancy. A shipment event with the wrong product or parent order can make the order appear further along than it is. Keep an attachment under the relevant order when a delivery or return needs supporting material.

Pick one order with a partial shipment. Compare its line’s shipped units with the dated shipment events. Check the product and external event identifier on each occurrence. Then read the payment evidence: a captured amount marked verified should be distinguishable from an authorization or unverified refund.

Try a repeated external event identifier in the rehearsal data. The team should identify it as the same source occurrence before changing any totals. Ask the Auditor to reconstruct the order’s physical and financial trail from the linked records. This case exposes mapping errors while the scope is still small.

• Fulfillment Events — Dated physical events show their parent order and product.
• Payment Evidence — Provider events retain their verified state and parent order.

Review order progress and inspect exceptions.