Aglet

How to triage a duplicate order after checkout

Two order rows do not prove two orders, and one row does not prove one fulfillment. Triage should compare visible order identifiers, saved records, payment attempts, and the actions that preceded the display. Keep duplicate rendering, duplicate persistence, and duplicate charge as separate findings.

Establish what is happening

  1. Capture what is visible

    Record the order labels, identifiers, timestamps, item count, total, status, and page or confirmation state using synthetic data. Note whether the rows are identical or differ in status. Avoid copying real customer order details into evidence.

  2. Repeat display triggers

    Refresh, paginate, return from confirmation, submit twice rapidly, and revisit the order list after a delayed response. Compare visible rows with the order query and saved record count. Keep each trigger isolated to identify the first duplicate surface.

  3. Reconcile durable state

    Match displayed identifiers to order, payment, and fulfillment records. Check whether one order appears through two read paths or two records share a key. Record duplicate payment or fulfillment evidence separately from a list rendering defect.

What to carry forward

Triage is complete when the visible duplicate has a reproducible trigger, identifier comparison, and durable record outcome. If the source record cannot be queried safely, mark order identity unknown and do not recommend a retry or cancellation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow