Orders and payment

Bookings brings the customer’s order together with its line items, address, shipping method and payment state. Separate financial, fraud, fulfillment and overall statuses let staff answer different questions without collapsing them into one label. Payment evidence records an authorization, capture, sale or void with amount, result and provider reference.

• Keep the placed order intact. Booking resources retain item quantities and prices even if the catalog changes later.
• Read each result separately. Payment evidence, fraud status and fulfillment status answer different questions for Customer Service Rep.
• Escalate exceptions. Merchant Owner reviews risk and payment policy while Warehouse Operator works the physical shipment.

A service rep opening an order can see whether payment evidence succeeded, whether the risk status is under review, and whether any items have been fulfilled. Suppose a customer asks about a paid order that has not shipped. The financial status can be Paid while fulfillment remains Unfulfilled; the rep can give an accurate answer and send the shipping question to Warehouse Operator. Operation receipts preserves the sequence of events attached to that booking.

Agree when staff may cancel a booking, how provider results are reconciled, and who clears a risk exception. Merchant Owner should review payment method settings and any manual review policy before accepting orders. Keep captured money and shipment progress separate. An event row is useful evidence, while actual provider collection requires the chosen payment connection.

A pilot should use a real product range, one supported market, a shipping method and a representative order. Confirm which person owns each state change. Review the information that will arrive from payment, carrier and messaging services, and decide how the team will reconcile a delayed or failed response. Keep the customer’s original transaction visible when correcting a later event.

Start with a customer selecting a shippable variant. Compare the item quantity and price in the cart with the resulting booking line. Confirm the delivery address and shipping method. Then follow payment evidence, shipment status and any service request in sequence. If an exception arises, the next person should be able to see the affected booking and the reason for the handoff without guessing from a single overall status.

This exercise also tests access. Customer Service Rep should be able to work the records in this module. A colleague with read-only responsibility should be able to inspect the relevant result without gaining permission to change payment or fulfillment evidence. Rehearse an incorrect address and a failed payment result so the team knows how to stop and correct the case.

• Open bookings — Orders with their financial and fulfillment states side by side.
• Bookings under risk review — Orders marked for a risk decision before release.

Follow the operating process and review the record model.