Supplement UPCs and Seller SKUs: Match the Package Variant before Comparing Listings
Use a manufacturer’s UPC as one package reference while keeping retailer-specific stock codes and bottle counts separate.
We have not performed hands-on testing of the products discussed. Manufacturer references and official guidance support the documented information below; comparison exercises are our editorial guidance.
Two sellers can give the same manufacturer product different internal stock codes. Conversely, two bottle sizes within a product range can have different manufacturer identifiers. These facts make a code comparison useful only when the code type is known. This guide uses an actual supplement size table to explain a buying-record method without claiming that a matching barcode authenticates physical contents.
Distinguish the identifier types first
GS1 US explains that a GTIN identifies a product across trading partners, while a SKU is an internal inventory identifier. Multiple companies may use different SKUs for the same product. NOW’s consulted glutathione size table provides separate manufacturer SKU and UPC entries for its 30-, 60- and 120-capsule bottles. Preserve the column headings when copying the codes; a bare number without its type is easy to compare incorrectly.
Match the complete variant rather than only the name
A listing titled glutathione 500 mg still needs its bottle count and current panel checked. Compare its stated package with the manufacturer’s matching size-table row. A retailer’s own stock code need not resemble NOW’s SKU. Likewise, a code shown for the smaller bottle does not identify the larger bottle merely because the ingredient headline is the same. Keep product name, quantity and identifier together.
Worked example: resolve a false mismatch
Suppose an illustrative shopping sheet marks two offers different because their seller SKUs differ. Both offers show the same named manufacturer variant and its matching UPC. Move the seller codes to separate retailer-reference fields, then compare the full panels and package counts. If those also match, the internal stock codes are not the reason to separate the products. If one offer is a seller-made bundle, record its bottle quantity separately rather than assuming a single-bottle UPC describes the entire bundle.
Treat a matching code as a reference, not a seal
This method helps ask a clear identity question, but it does not inspect ingredients or prove a physical bottle’s authenticity. A copied number on a listing cannot provide that assurance. Ask the seller to resolve inconsistent package images and counts, retaining the actual offer and the current manufacturer row. GS1’s naming framework explains the code types; the maker’s size table supplies the concrete package references. Do not derive expiry, lot identity or an ingredient-source country from a SKU or UPC. Those are separate fields requiring their own evidence. The useful endpoint is a correctly matched catalogue variant, with bundle quantities and unresolved package discrepancies still visible before comparing delivered costs.
Compare the trade-offs
| Option | Useful when | Purchase limitation |
|---|---|---|
| Manufacturer UPC | Match the exact size-table row | Useful product reference, not content verification |
| Seller SKU | Save under that retailer’s name | Different internal codes may refer to the same product |
| Seller bundle | Record the number of original bottles | A single-bottle code does not describe bundle quantity |
Your purchase checklist
- Keep each code’s type and issuing party visible.
- Match bottle count to the correct manufacturer row.
- Do not treat a copied identifier as authentication.
Sources and further reading
Reference links concern the stated topic or example. They do not indicate endorsement of this publication. Product versions, local labels, availability and seller terms can change; verify the exact listing before ordering.