Deduplication

When the same physical product is carried by multiple suppliers, deduplication ensures only one record is sent to the destination store.

The problem

Supplier A and Supplier B both carry “Widget Pro” with EAN 5901234123457. Without deduplication:

• Two product records are created in the destination store
• The store shows the same product twice
• Stock and price are reported separately per supplier instead of combined

Deduplication keys

A deduplication key identifies which products are “the same”:

Key	Behavior
gtin	Products with the same EAN/GTIN are considered duplicates
sku	Products with the same SKU (across suppliers) are considered duplicates
none	No deduplication — all products are exported separately

GTIN-based deduplication is the most reliable when suppliers provide EAN codes. SKU-based deduplication is useful when suppliers agree on a common part number.

Deduplication strategies

When duplicates are found, one record is selected as the winner based on the strategy:

Strategy	Winner
cheapest	The variant with the lowest price (after pricing rules are applied)
highest_priority	The variant from the supplier with the highest priority score
first_seen	The variant that was first imported into the catalogue

The winning variant’s price and stock are used. The losing variants contribute to a combined stock count if you enable stock aggregation (add stock across all duplicate suppliers).

Example

Supplier A: Widget Pro, price €80, stock 10, priority 1 Supplier B: Widget Pro, price €75, stock 5, priority 2

With cheapest strategy: Supplier B wins (€75 price, 5 stock) With highest_priority strategy: Supplier B wins (priority 2 > 1) With stock aggregation enabled: winner’s stock + loser’s stock = 15

Configuring deduplication

In the export profile settings:

1. Set Deduplication key: gtin, sku, or none
2. Set Deduplication strategy: cheapest, highest_priority, or first_seen
3. Toggle Aggregate stock if you want to combine stock from all duplicate suppliers

Deduplication is evaluated at export time, not at import time. The catalogue stores all variants from all suppliers; deduplication only affects what gets exported.

Attribute enrichment vs. price/stock

Deduplication applies only to which price and stock value to export. Attribute enrichment (which name, description, images to use) is controlled by supplier priority — higher-priority supplier data overwrites lower-priority data when the same attribute is set by multiple suppliers.

This means you can use Supplier B’s cheaper price while using Supplier A’s better product description.