How duplicate order matching works

A sale can appear in both a storefront or marketplace and an ERP. Counting both records as separate sales would overstate the combined view. Balta Labs can link records from two connected accounts into one order. It keeps the original records so you can still compare what each system reported. See what each connection imports to understand which sources may hold records of the same sale.

A match needs evidence

A deduplication rule compares two specific connections. It first limits each side by connection and any optional filters. It then compares order identifiers, such as an order number or source order ID. You can add supporting checks for references, products, dates, or amounts. Every comparison in the rule must pass (AND).

Choose identifiers that genuinely refer to the same sale in both systems. A similar amount or date alone is not enough. For identifiers with a known prefix or suffix, the editor can remove that affix before comparing. Preview the exact rule and inspect example pairs before activation.

One primary record, both originals

The rule chooses Source A or Source B as primary. That record supplies the authoritative order amount in the current combined order and OSS views. The other source record stays stored and linked; matching does not delete or rewrite either original. Open an order’s Source records to see the primary badge and compare the values. A missing source field is not a zero amount.

Active rules match orders in the background. New successful order fetches queue matching for the dates they cover. Activating a rule also starts a full-history evaluation. Results may take time to appear, especially for a large history.

Why exports can have different totals

The OSS report and the Tax summary and Individual orders export bases use the selected authoritative record for a matched order. All source events deliberately retains the original sale and refund events, including duplicates. Compare sources places matched records side by side to investigate differences. Do not sum All source events as a deduplicated sales total.

If a pair is wrong, correct or pause the rule and recheck the order and report after background processing. If a sale remains split, verify that both connections imported the relevant dates and that its identifiers meet every condition. See how to manage a rule for the steps.