Follow an order all the way through

Follow the same order, not just the success screen

A checkout is working only when the storefront, store Admin, and relevant payment records agree. In this local sample, payment is manual and simulated. No card is charged and nothing ships.

1. Place one sample order

1. Open the local shop and choose Everyday pouch.
2. Select a color, add one pouch to the bag, and open Review test checkout.
3. Confirm the synthetic buyer details and test totals: $24 for one pouch, $5 test delivery, $0 test tax, $29 total.
4. Choose Place test order once. Save the order number on the confirmation.
5. Open Store Admin → Orders and find the same order. Check the product, variant, quantity, delivery, and total.

These expected amounts apply to the unchanged sample. If you have changed the catalog or shipping rules, calculate the new expected total first. A sample’s zero tax is not a tax policy for your real business.

2. Understand what the statuses mean

What you see	What it establishes
Product appears in the bag	The cart contains a selected item.
Order confirmation and matching Admin order	The sample stored that order.
Manual test payment marked authorized	A simulated payment step was recorded.
A payment-provider receipt in a future live store	A provider operation occurred; settlement still has its own status.

Do not tell a real customer that a payment settled just because your website shows a thank-you page.

3. Reopen the shop

Reload the page and reopen the order in Admin. Orders and catalog changes live in the database, so a page refresh does not erase them. The browser remembers a cart ID and the latest test order ID.

If checkout times out, keep the same bag and recover its result. Do not create a fresh bag or new payment attempt until you know what happened to the first one.

4. Ask AI to reconcile the result

Help me check this local sample order. Compare the same order in the
storefront and authenticated Admin. Report only product, variant,
quantity, subtotal, shipping, tax, total, and test-payment status.
Use synthetic data. Do not reveal passwords or customer details, edit
order states, create a replacement order, or capture/refund a payment.
If the result is uncertain, explain how to read the existing result.

The kit also has npm run verify for a repeatable engineering check. It creates another synthetic order and restarts this sample’s services, so use it only when you are not editing the shop. It is not the daily live-store health check.

Ready when

The same order exists in both places and every amount matches. You know that this proves the local test flow, not real payment acceptance. If the amounts differ, save the expected and actual figures and ask for help before proceeding.