Use the two-size example on the Samples page, or find the fields that distinguish your own products, such as Size, Colour or supplier.
1. Look at the repeated rows
A repeated SKU may be a mistake, but it may also represent different sizes or colours. Check the original records before removing anything.
2. Choose a combination that is unique
In Map & match, choose SKU and Size if the sizes tell the products apart. Both files need those columns. Use details that stay the same between updates; a changing price is not a good way to identify a product.
3. Calculate the review again
In the sample, TEE appears twice, so the code alone cannot tell you which shirt to update. Matching TEE with size S and TEE with size M gives two separate results. Check the old and new prices for both.
4. Resolve anything still unclear
If a row is a mistake, correct the original file and add it again. You can also use Ignore this source record to leave out a duplicate row from the current calculation. Check the filename and row number first. Two products with the same code should not have their stock combined unless they really are the same product.
Try the duplicate-SKU exampleCheck that each proposed update belongs to the intended product and variant. Resolve uncertain matches before approving them, then test a few records in your shop.