Inventory the actual records
Check order history rather than relying only on a browser notification. Record every relevant order ID, exact target, service and submission time, including requests that appear identical at first glance.
Avoid assuming cancellation
An accidental duplicate may already be processing. Contact support with the specific records and ask what the service allows; do not promise a client that one request will certainly be canceled or refunded.
Prevent the next duplicate
Assign one ordering operator and wait for the account history to update before retrying. Where a submission remains uncertain, check its record first instead of using another browser session as a workaround.
Decision checklist
| Decision | What to check |
|---|---|
| Existence | Separate order IDs in history |
| Charges | Ledger entry for each request |
| Resolution | Allowed action for current statuses |
Worked example
In a hypothetical incident, a buyer sees two 250-unit requests for the same Reel within one minute. Both references are sent to support. The buyer does not submit a third order or assume the visible counter can identify which request is responsible.
Example figures explain the decision; they are not current prices or promised results.