Identifying reorders & duplicate UPCs
When you upload a purchase order, Tangerine Star looks at every line item and asks a simple question: have you bought this before? If you have, it's a reorder — the quantity should flow into the product you already have. If you haven't, it's a new product that needs to be created. Getting this right is what keeps your counts accurate and your catalog free of duplicates.
The important part: when the answer isn't certain, we show you the candidate and let you decide. The system never silently merges two products.
What "a match" means
Tangerine Star checks for a match in tiers, strongest signal first. The first tier that fires wins.
Line-item history
Have we seen this exact line — from this vendor — on a previous PO? This is the strongest signal. If your last order from this vendor had the same item and you received it, the new line is treated as a confident reorder of that same product.
Identifying IDs and exact names
If there's no prior line to lean on, we look for a hard identifier: a vendor-specific mapping you've set up, a UPC, a vendor item number, or an exact (case-insensitive) name match. Any of these is also a confident reorder — they point at one specific product.
Similar names
If the only thing in common is a similar name, we stop and ask. A normalized or fuzzy name match is not treated as an automatic reorder — it's surfaced as a candidate for you to confirm.
No match
If nothing lines up, the item is a new product, ready to be created on receive.
Why similar names don't auto-merge
This is the rule that protects your catalog:
A common nursery example makes it concrete:
- Your catalog already has "Hosta Patriot 1 gallon."
- A new PO lists "Hosta Patriot 2 gallon."
The name normalizer strips the size, so a naive match would collapse these into one product — quietly merging two genuinely different sellable items and corrupting both their counts. Instead, Tangerine Star surfaces the existing 1-gallon item as a candidate parent and offers to promote it into a variant family — only if you confirm it. You stay in control of whether that's one product or two.
When we get it wrong
Detection is a starting point, not a verdict. If a line is flagged as a reorder but it's actually something new, you can mark it "not a reorder" right in the receive review. That clears the match so the item is treated as new — and your correction is remembered for that line.
Duplicate UPCs
The flip side of recognizing a product is recognizing its barcode. The same item can carry more than one UPC across vendors and orders, and occasionally two different items collide on one. Tangerine Star records every identity it sees, ranks them by how much it trusts each, and settles on a single canonical barcode — the one true scan target — without throwing the others away. When a barcode is ambiguous, that surfaces at receive so you can confirm rather than guess.
Where you'll see this
Reorder verdicts show up in the receive review for every PO: each line is labeled as a reorder (pointing at the product it matches) or as new. Review them, override anything that looks off, and receive — your counts update against the right products automatically.