An order can appear once in the shop and twice in a measurement report. For an online shop in Kartal or any business testing a new checkout, compare the signals sent by the site with the order record. A receipt screen can be opened several times during a single purchase.
Choose the order record you will compare against
Create a sandbox order with a known total, currency and order reference. Record the moment your order system marks the purchase complete. In the measurement system, use a test property or diagnostic view where you can see each event and its order reference without mixing the exercise with customer reports.
Agree which stage counts as a purchase for the business. Keep tests for a completed payment, a pending payment and a failed attempt separate so each result can be interpreted against that rule.
Reopen the receipt in three ways
Complete one order. Reload the receipt, reopen it from the browser history and return again from the payment page if the provider supports that flow. Compare each action with the event log. One successful order should be counted once. In a separate test, leave the payment flow before confirmation and check the outcome against the order’s actual state.
Check reports as well as the browser
If the browser and server can both send a purchase event, note the order reference used by each. Compare the raw events with the final count. Ask the developer to show where retries or repeated receipt views are stopped or reconciled. Repeat with a second new order so the fix still counts distinct purchases.
Record the result before enabling live traffic
For each run record the interface language, test reference, order status, number of raw events, number counted and currency. Repeat in English and French, using a new order reference for each independent test.
Checklist before publishing
- Order status verified at the source
- Receipt reload and payment return tested
- One order counted once in the report
- A second successful order still counted