Decide where the work belongs
Classify the duplicate
Elevate two durable orders or payments above two rows with one identifier. Treat a confirmation that encourages another submit as high risk even before a second record exists. Record whether the shopper can tell which row is authoritative.
Describe observed scope
List the page, sort, pagination, refresh, retry, device, and timing conditions reproduced. Compare sampled order identifiers only when authorized and redacted. Do not infer a broad duplicate rate from one repeated visual row.
Choose containment
Decide whether to deduplicate the read view, disable repeated submission, show one canonical order, or hold recovery until records are reconciled. Never hide a second order by deleting a row. Assign an owner for customer-impact review.
What to carry forward
Prioritize duplicate payment or fulfillment evidence highest, then any confirmation path that can create another order. Queue a visual-only duplicate with exact trigger, canonical identifier, safe containment, and evidence needed to prove persistence scope before closing.
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