How Are Duplicate Transactions Prevented?

Duplicate transactions are dangerous because they can cause double-crediting and overpayment of sales incentives. We provide different ways to protect against duplicate transactions.

For transactions having been imported with a "Unique ID" field:

We will use this field to prevent other transactions with the same "Unique ID" from being imported
If transactions are modified at the source, and re-imported (manually or automatically) with the same "Unique ID" data, the current transaction will be updated to reflect the latest changes (instead of creating a duplicate)

For transactions having been imported without an "Unique ID" field:

We calculate a checksum using all mapped fields (note: we also offer the option to choose which fields should be used to generate this checksum)
If transactions are re-imported (manually or automatically), transactions will be ignored if they match others with the same checksum (i.e. no duplicates will be created)

Unique IDs Must Be Unique

You should not map fields to the "Unique ID" category if not truly unique. For example, if a purchase and its corresponding refund transaction share the same ID, then you should NOT map this ID to the "Unique ID" category. Indeed, once the refund transaction is added, it would replace the purchase transaction in Sales Cookie.