One barcode identifies two active catalog items

Prove the collision from the mappings, not from memory

Pull the catalog records and list every active product or variant whose record carries the disputed barcode value, with each item's distinct identity: its own identifier, title, variant details and location. Two rows sharing a value is the finding. Do not decide by seniority, sales volume or familiarity which item is the real owner of the barcode; the collision exists because both records claim it, and both claims are data until someone authorized changes one.

Shopify recommends unique SKUs for inventory tracking, and the same uniqueness discipline applies to barcodes used for picking. That recommendation is guidance about merchant data, not a promise that the platform blocks every cross-product duplicate — do not assume the system would have prevented this, and do not assume another platform behaves the same way. The collision is a condition in your records that your records must resolve.

Read what the scan records actually resolved

Check the scan history for the disputed value: which item record each scan selected, when, and on which orders. Depending on how the scanning tool is configured, a lookup may return the first match, the most recently edited match, or prompt for a choice — the behavior of your actual tool, from its own documentation, decides how to read these events. Those records tell you which catalog record the system pointed staff toward.

What they cannot tell you is which physical item left the shelf. A scan that resolved to item A does not prove the picker took item A, and a scan resolved correctly does not clear a parcel that was packed wrong. Distinguish routing ambiguity — the scanner cannot uniquely select an item — from a confirmed wrong pick, which needs physical evidence such as packing checks or the buyer's report. Confirmed mispicks follow the wrong-item investigation; unresolved ones stay open rather than being decided by the scan log.

Hold the route and assign the correction

Pause picking on the disputed barcode wherever scans cannot uniquely resolve an item. A bare barcode matching two active records is not enough to identify an item on its own; whether any given scan routed by accident or by a configured choice depends on the tool's actual behavior and the context of each event, which the scan records you gathered will show. Hold the routes your evidence cannot resolve rather than treating every past scan as accidental, because each order picked in an unresolved state adds to the set of parcels someone may later have to untangle. The hold is an operational control, not an admission about any order already shipped.

The authorized catalog owner records the correction: a new unique identifier for one of the items, the relabeling steps for physical stock, and the effective date. Where one of the two items is genuinely retired, archiving may resolve one side — on Shopify, archiving removes a product from active sale visibility — but archiving is a visibility state, not a remedy for two items the business still sells, and it does not rewrite what earlier scans meant. Record who will verify, after the change, that a scan now resolves to one item only.

Prevent the next collision

Add a uniqueness check to the moments collisions are born: activating a new product or variant, changing a barcode on an existing record, and importing catalog data in bulk. A periodic duplicate-value audit across active records catches what the moment checks miss. Keep the check procedural and recorded — who ran it, when, and what it found — so the next collision is discovered in a report rather than at the packing bench.

If the collision surfaces in how the storefront or catalog displays identifiers, a Prism consultation can discuss that website concern within an agreed scope. Confirm responsibilities, fees and terms before work; the consultation does not manage your warehouse or certify your catalog data.

Barcode-collision hold sheet

Use one sheet per disputed barcode value. Fill every row from actual catalog records, scan logs and physical checks; where evidence does not exist, write unknown rather than a plausible answer. The sheet holds a route; it does not correct the catalog by itself.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.