# Shopify Multiple Barcodes: A Practical Setup and Testing Checklist > Shopify now supports multiple barcodes per variant. Learn what changed in September 2026 and how to test your POS, product data and integrations before rollout. Canonical page: https://www.thesjdevelopment.com/blog/shopify-multiple-barcodes-guide Author: EssDeeJay Engineering Team Published: 2026-09-18 Updated: 2026-09-18 Photo: Matthew Henry / Burst (https://www.shopify.com/stock-photos/photos/store-scanner-for-checkout) ## What changed in September 2026? Shopify's September 8 announcement introduced support for up to 20 barcodes on a product variant. Merchants can manage them on the variant, through bulk editing or through the product CSV's Variant Barcodes column. Existing codes remain in place. Where a channel or tool expects one barcode, the first code remains significant. [Shopify's multiple-barcode announcement](https://changelog.shopify.com/posts/multiple-barcodes-in-variants). The practical opportunity is to identify the same sellable variant using different valid codes. The implementation task is to confirm that your receiving, checkout and external systems agree about which variant each code represents. The checklist below is our recommended rollout process. It does not assume that every third-party app supports the new list in the same way. ## 1. Choose a small pilot group Select a few variants with a real operational reason for additional codes. Include one simple product and one product with several sizes or colours. Keep a record of the current values before changing anything. For each pilot, write down: - The Shopify variant and internal stock identifier. - Each physical label that staff may scan. - The supplier or system responsible for the label. - The expected result when that label is scanned. - The channels and integrations that consume the record. This small inventory turns a configuration change into a testable requirement. If two teams disagree about what a label identifies, resolve that question before adding more data. ## 2. Confirm that the codes describe the same unit Use the variant as the starting point. Compare the actual item, size, colour and unit of sale against the source record. For example, a single bottle and a carton of six bottles may look closely related in a spreadsheet but represent different quantities for receiving and fulfillment. Do not attach a code simply because it shares a product name. Ask the inventory owner to confirm the exact item it identifies. Keep this decision documented. Future imports are easier to review when the team can distinguish deliberate alternate codes from accidental duplicates. ## 3. Make the first-code decision explicit The first barcode continues to be used by systems that consume a single value, according to Shopify's announcement. Before reordering codes, list the feeds, labels and apps that may rely on that value. [Single-barcode compatibility details](https://changelog.shopify.com/posts/multiple-barcodes-in-variants). Our recommendation is to assign an owner for this decision. Record why a particular code comes first, where it is used and which tests need repeating if it changes. Avoid treating the order as an incidental result of a spreadsheet sort. ## 4. Test the whole workflow A successful scan in one interface is one test result, not a complete integration check. Use your actual devices and the same software staff use during a normal shift. Run a short test matrix: 1. Scan each approved code and confirm the exact variant. 2. Verify the quantity and unit of sale. 3. Check the order or receiving record created downstream. 4. Inspect the payload or exported record used by your connected system. 5. Try an unknown code and confirm that the error is understandable. 6. Repeat the process with a similar-looking variant to catch ambiguous mappings. Record both the expected result and the observed result. A failed test is useful: it shows where the data contract or staff procedure needs attention before a broader change. ## 5. Expand in controlled batches Keep an export of the original data and agree a rollback procedure with the team responsible for inventory. Review the first batch with the people doing receiving and checkout, then expand only after the pilot behaves as expected. Useful measures include unmatched scans, manual product lookups and incorrect variant selections. Compare equivalent operating periods and investigate exceptions instead of assuming that the feature alone has solved the workflow. ## Frequently Asked Questions ### How many barcodes can a Shopify variant have? Shopify's September 2026 announcement specifies up to 20 barcodes per variant. Review the linked release note for the current supported behavior. ### Should we remove our existing barcode first? The release note says existing barcodes remain in place. Preserve your working data while testing any additions and confirm downstream requirements before changing code order. ### Does this mean every connected application supports multiple barcodes? Do not assume that it does. Test the app's actual input and output and confirm its supported behavior with the provider before relying on it operationally. ## Need help connecting inventory systems? Our [Shopify integration service](https://www.thesjdevelopment.com/services/integrations) covers data ownership, mappings and failure handling between commerce and business systems. If your workflow needs a dedicated interface, explore [custom development](https://www.thesjdevelopment.com/services/custom-development).