Confirmations across channels must stay consistent
Aliases: receipt email mismatch · confirmation consistency · omnichannel receipt
What it is
The same success shows on the success page, in mail, SMS, push, and order detail. Content consistent means order id, amount, goods summary, and key times match across those channels—not mail still on the promo price, the app on captured amount, SMS “success” with no id. It is not collapsing channel orders into one list, and not whether the original can be edited. It is whether the confirmation said in several places at one moment is one sentence.
Why it happens
People reconcile against whichever message arrives first. Late mail or an old template fights the success page; they think they were charged twice or charged wrong. Channels often render from different systems: pay-success event, mail service, marketing template. Split field sources break consistency. Marketing rewriting a mail template to insert recs that push amount below the first screen makes that channel not a confirmation. Push is short and may carry fewer fields, but it must not contradict the main confirmation’s numbers.
Studying it
Place an order; open success page, mail, SMS, and order detail together; check id and amount line by line. Change the mail template and retest.
Independent variables: channels reading one snapshot, templates allowed to override amount, push includes id. Dependent variables: mismatched fields across channels, tickets for “two charges,” which channel people trust.
Labs often look only at the success page. Actually send the mail. Log late arrival: a late old template is a common incident.
Where it stops holding
Localized channels may differ in language; digits and ids must not. A compliance channel (invoice mail) may have more fields than marketing mail, but must not contradict the purchase confirmation. If the user disabled mail, consistency cannot rest on mail; success page and order detail still have to agree. Push failure is not inconsistency; a missing channel is not a wrong channel.
Applying it
- All confirmation channels take id and amount from the same issued snapshot; templates do not assemble their own.
- Mail and SMS show order id and captured amount in the first screen; marketing blocks come after those fields.
- Template changes get a field-contract test: sample a live order and diff channels.
- Verify on a test order by tabulating id and amount from success page, mail, SMS, detail. Any cell differs, or a channel lacks the id, consistency fails.
Related
- Within the group: H7.12.1 E-invoices and purchase receipts serve different legal uses · H7.12.2 Multi-channel orders need one order history · H7.12.3 Receipt content must not be rewritten after issue
- Adjacent: H7.05 Order confirmation · H5.06 Actionable notifications · H7.11 Payment security interaction
- Search terms:
confirmation consistency·receipt email·order snapshot