Commerce & Digital · Illustrated edition
Payment received. Order missing. Who finds it?
A buyer has a receipt. The workshop has no job. Here is how to commission a checkout that finds the missing order without making the customer pay twice.

The short answer
Give operations a list of paid orders without a confirmed fulfillment job. Each row should lead back to the original purchase and show who owns the next step. Release the job only after checking whether it already exists; never ask the customer to pay again just to recreate an internal record.
A receipt proves payment. It is not a packing instruction.
In this article
01 / 04
Two teams can both be telling the truth.
Imagine a shop selling made-to-order lamps. A buyer pays for a brass lamp with a short stem. On Monday she writes to ask when it will ship. Finance finds the payment. The workshop searches by her name and finds nothing. Creating a new order sounds helpful. But what if the first instruction is already sitting in the printer queue?
Support needs two different answers: what the customer bought and whether the workshop accepted the job. An empty tray answers neither question.
02 / 04
Ask for the list of orders that disagree.
Most checkout demonstrations end on a thank-you page. Ask the supplier to close the buyer’s browser before that page opens. Can the shop still identify what was bought, tell whether it was paid for, and find out whether anyone has started making it?
Axiom Forge’s recommendation is to keep three references that staff can follow without searching by name: the shop’s order number, the provider’s payment reference and the workshop’s job number. Preserve the purchased configuration with the order. Looking up today’s catalogue later will not recover a finish that has since been discontinued.

The useful screen is the one where that chain stops. For the brass lamp it might say: Payment confirmed. Order found. No workshop acknowledgement. Assigned to operations. That gives support an honest answer and gives operations a task. “Something went wrong” does neither.
One implementation detail matters to the buyer: the browser must not be the only messenger. For example, Stripe’s Checkout guidance explains why the buyer might never reach the return page. It also distinguishes completing checkout from receiving payment when the payment method settles later. A pending payment belongs in a different queue from money received for an order nobody has fulfilled.
03 / 04
A person can close the gap. Sometimes that is the right design.

A staffed exception list
For a small workshop where every lamp is reviewed before assembly, ask for a daily list of paid purchases without an acknowledged job. Give one named role responsibility for clearing it before the production cut-off. The trade-off is delay: a Friday evening payment may wait until Monday. Is that consistent with the promise on the checkout page?
Automatic reconciliation
If the shop promises immediate access or ships in frequent batches, have the system compare payments, orders and downstream acknowledgements on an agreed schedule. Automatically repair only the unambiguous cases. A matching amount and surname are not enough: two people can order the same lamp.
Neither route makes an uncertain dispatch safe to repeat. If the workshop created a job but its confirmation was lost, look up the job using the original order reference. If the workshop cannot do that, stop and ask a person to verify it. A second lamp is an expensive way to discover the first one was already in production.
04 / 04
Give the supplier one awkward order.
Use a sandbox purchase, not a real charge. Specify a distinctive configuration so the team must recover the actual order rather than substitute a generic product. Then ask for three demonstrations:
- Paid, browser closed. Show how support finds the purchase without the customer’s screenshot. The buyer should not need to return to the shop to finish the internal handoff.
- Paid, workshop silent. Hide the acknowledgement. Show who sees the exception, what evidence they check and how long it can remain unassigned. “Someone gets an email” is not an owner.
- Recovered, notification arrives late. Deliver the original notification after the operator has resolved the case. Show one workshop job, not two, and a record of why no further action was taken.
The decision to make before signing is not simply “manual or automatic?” It is how long can a paid order go unnoticed, and who can safely release it? Put that answer in the brief. The team can then price the actual work: preserving the order, matching the payment, checking the workshop and handling the cases the software cannot decide.
For the delivery mechanics, read the webhook integration guide. For a different problem—money arriving after reserved inventory is released—see reservation holds and late payments.
Sources and editorial scope
This is Axiom Forge’s procurement and product-delivery guidance, not a guaranteed project plan. The example is illustrative. Sources checked on 12 Nov 2026.
- Stripe: Fulfill orders — Checkout-specific guidance on return pages, delayed payment methods and handling fulfillment more than once.