Why row order fails
Sorting, deduplication and partial results can change row order. If the team pastes a status column beside an independently sorted source, the labels may attach to the wrong records while the totals still look plausible. Treat row position as presentation, not proof of identity.
Choose a documented mapping
Use the fields actually supported by the vendor export. Preserve an untouched input snapshot and document how returned records map back. Do not assume every vendor echoes custom identifiers. If the output lacks the field you need, resolve the mapping before a production upload.
Three-record rehearsal
Create fictional records A, B and C with no real addresses. Reorder the output C, A, B and verify that your local mapping still assigns results correctly. Then omit B and add a duplicate A. The process should flag both exceptions rather than silently attach the next available result.
Put it into practice
A useful exception report names the mapping rule and reports its failures without silently repairing them. Suppose three synthetic source records have keys Cedar-A, Cedar-B and Cedar-C. The result file is sorted by category and returns Cedar-C first. A position-based paste would attach C's observation to A. A key-based process should still associate each result correctly, but only if the chosen key is actually present and unique under the documented rule. Next remove Cedar-B from the result and duplicate Cedar-A. The report must now show one missing key and one repeated key. A matching overall row count does not make the mapping valid. Review how intentional deduplication changes the expectations, and preserve any one-to-many mapping separately. Do not invent vendor support for custom IDs; confirm the exact export shape before depending on it.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Bouncer API introduction — Merchant documentation · docs.usebouncer.com · Merchant-controlled · checked 2026-09-27