Managing Multiple Barcodes on Shopify Product Variants
On 8 September 2026, Shopify released a feature that solves a real problem for Indian D2C brands selling across multiple marketplaces. You can now store up to 20 different barcodes on a single product variant. If you sell the same sweater on Shopify, Flipkart, and Amazon, each marketplace assigns its own barcode. You had to manually track which belonged to which channel. Now you can store all of them in one place, labeled by channel, and inventory sync tools can pull the right one.
Why the old single-barcode system broke multi-channel selling?
A product variant on Shopify used to have one barcode field. That field could hold one value. Your product with SKU "SWTR-GR-M" had barcode "123456789012". But on Flipkart, that same SKU got assigned barcode "987654321098" automatically. On Amazon, it became "456789012345". You owned three barcodes for one product. Shopify only stored one of them.
The workaround was painful. Some merchants stored all three barcodes in the single field, separated by slashes: "123456789012 / 987654321098 / 456789012345". But then inventory sync apps could not parse which barcode belonged to which channel. Others created custom metafields for the extra barcodes. But metafields are not part of the standard product schema, so third-party apps did not read them reliably.
The result was manual work. You had to keep a spreadsheet mapping SKU to barcode by marketplace. When you were building a multi-channel strategy across Amazon and Flipkart, barcode management became a bottleneck. If you got the mapping wrong, the item listed on Flipkart did not sync, or worse, it synced to the wrong product and you doubled inventory counts without knowing it.
This cost time and created errors. For a brand with a hundred SKUs across three channels, that is three hundred barcode mappings to maintain.
What changed on 8 September 2026?
Shopify expanded the product variant barcode field from a single value to a list. A variant can now hold up to 20 barcodes. Each barcode can be tagged with a type: GTIN, UPC, EAN, or a custom label like "flipkart" or "amazon-in".
Instead of guessing which field held the Flipkart barcode, you now store it with the label "flipkart" right there in the variant. When an inventory sync tool needs to push stock to Flipkart, it queries for the barcode tagged "flipkart" and uses that one. No spreadsheet. No manual lookup. No risk of using the wrong barcode.
This is a structural change to how Shopify stores barcode data. It touched the GraphQL Admin API and the REST API. If you use the default Shopify product editor in the admin, you will see a new interface for adding multiple barcodes. If you build custom apps or integrations, you will query a barcodes list instead of a single barcode string.
The feature is live for all Shopify plans. It applies to all regions. But it matters most in markets where multi-channel selling is the default, and that includes India.
Why does India-specific multi-channel selling need this?
In India, a D2C brand does not choose between Shopify and Flipkart. It operates on both, plus Amazon, because each marketplace controls a different audience segment and a different inventory. A fashion brand may sell through its own Shopify store, through Flipkart for discoverability, and through Amazon as well, with the split between them changing month to month. Each channel has its own product listing, its own SKU numbering sometimes, and its own barcode generated automatically by the marketplace platform.
The inventory sits in a shared warehouse. When you pick an order, it does not matter which channel the customer bought through. But it matters for stock tracking. Flipkart deducts from Flipkart inventory. Amazon deducts from Amazon inventory. Your warehouse deducts from total warehouse stock. All three have to stay in sync.
Before that change, that sync required external tools and manual supervision. The inventory app had to translate between "Shopify barcode 123" and "Flipkart barcode 456" using a mapping file you built outside Shopify. If the mapping was wrong, inventory went out of sync and you either oversold or listed things as out of stock when you had stock.
Now Shopify knows all three barcodes for the same SKU. Inventory sync becomes precise. The mapping lives in Shopify itself, not in a separate spreadsheet or app. This is the single biggest operational improvement for Indian D2C brands that the barcode change brings. It is not about barcodes. It is about inventory accuracy across channels.
What barcode types can you actually use?
Shopify lists six barcode types: UPC, EAN, ISBN, GTIN, ASIN and Custom. Each one means something different. Understanding which to use prevents confusion when you set this up.
GTIN stands for Global Trade Item Number. It is the standard identifier for products in global commerce. Most consumer goods have a GTIN assigned by their brand. If you make a product, you can register a GTIN with GS1 India. Retailers and platforms recognize GTINs. Amazon, Flipkart, and other marketplaces accept GTINs as product identifiers. If your product has a GTIN, use that as your barcode type on Shopify. It is the most portable barcode type across channels.
UPC stands for Universal Product Code. It is the 12-digit barcode used in North America. If your brand sources packaging from US suppliers or distributes to US retailers, your packaging might have a UPC printed on it. In India, UPC is less common than GTIN or EAN, but some brands use it. Use the UPC type if your barcode is a standard 12-digit UPC.
EAN is the European Article Number, also known as the International Article Number. It is a 13-digit barcode standard used globally outside North America. EAN is more common in India than UPC. If your product has a 13-digit barcode and you obtained it from an Indian supplier or manufacturer, it is likely an EAN. Use the EAN type for these barcodes.
Custom is the catch-all. If your barcode does not fit GTIN, UPC, or EAN standards, or if you want to label a barcode by marketplace instead of standard type, use custom. You can call it "flipkart-barcode", "amazon-in-asin", "nykaa-sku", or anything else that makes sense to you and your team. Custom labels make it easy to see at a glance which barcode belongs to which channel.
The Custom type is there for codes that belong to your own system rather than to a standard. You will have one field labeled "shopify" with your Shopify-assigned barcode, one labeled "flipkart" with the Flipkart barcode, and one labeled "amazon-in" with the Amazon barcode. If your product is brand new and has not been assigned GTINs or EANs yet, the Custom type is the one to use.
How do you add multiple barcodes to a variant?
In the Shopify admin, go to Products, then select the product you want to edit. Click on a variant to expand the variant details. Look for the Barcodes section. Before that change, this was a single text field. Now it is a list. Click "Add barcode" to add a new one.
For each barcode, you enter the barcode value and select or type the barcode type. If you choose GTIN, UPC, or EAN, Shopify validates the format. If the barcode you enter does not match the standard format for that type, Shopify flags it. Custom types have no validation. You can enter anything.
You can add up to 20 barcodes per variant. For most brands, you will use 2 to 5: your primary internal SKU barcode, your Shopify barcode, your Flipkart barcode, your Amazon barcode, and maybe one for a B2B marketplace or a distribution partner. If you are exporting to a large number of channels, 20 is enough to cover them all.
Each barcode you add is stored in Shopify's database and exposed through the GraphQL Admin API and REST API. When an inventory sync app makes an API call to Shopify and asks for the barcodes on a variant, it gets back the complete list with types. That app can then select the barcode labeled "flipkart" and use it to sync inventory to Flipkart.
There is no performance penalty for storing multiple barcodes. Shopify's API queries return barcode lists just as quickly as they returned single barcode strings before. The change is transparent to most merchants using the default Shopify admin interface.
How do inventory sync tools use multiple barcodes?
The real value of multiple barcodes emerges when you integrate with an inventory management app. Apps like StockLogic, Trakinvapp, or even simple Zapier workflows can now pull the right barcode for each channel automatically. Here is how it works.
An inventory app queries the Shopify API asking for all products and their variants. For each variant, it gets back a list of barcodes, each with a type label. The app parses that list. It looks for a barcode labeled "flipkart" and stores that. It looks for a barcode labeled "amazon-in" and stores that. When it needs to push inventory updates to Flipkart, it uses the "flipkart" barcode. When it needs to push to Amazon, it uses the "amazon-in" barcode. The mapping happens automatically, with zero manual work.
This works for any third-party app that has been updated to read barcode lists. Older apps built before that change that only read a single barcode field will still work, but they will only see the first barcode in the list. To take full advantage, your apps need to be updated by their developers.
If you build custom integrations or use Make or Zapier workflows, you can write logic to parse the barcode list. A Zapier filter can look for a barcode with type "flipkart" and extract it. This requires a tiny bit of technical work, but it is straightforward JSON parsing. If you need help writing these workflows, most Shopify Plus partners and app developers can set them up in an hour or two.
The key point: before that change, inventory sync required external mapping files. Since then, the mapping lives in Shopify. This is not just a feature upgrade. It is a shift in how Shopify stores channel-specific product data.
What about brands that do not use inventory sync apps?
If you manage inventory manually, the multiple barcode feature is still useful but less transformative. You benefit from having all barcodes in one place so you do not have to reference a separate spreadsheet. When you receive a shipment from your warehouse, your picking system can scan a barcode. Instead of looking up which barcode belongs to Flipkart, you see it right there in the variant. When a customer calls asking about an order they placed on Amazon, you can look at the order in Shopify and see that it used the barcode labeled "amazon-in".
The real efficiency gain comes if you use apps that automate inventory flow. A manual process can work around the single-barcode limitation. An automated process cannot. If you are considering moving to automated inventory management for quick commerce or high-velocity channels in the future, the multiple barcode feature makes that transition easier and cheaper.
If you only sell on Shopify and do not use other marketplaces, multiple barcodes are not critical. You have one barcode per variant and one destination channel. The feature does not hurt, but it solves a problem you do not have.
Should you add all barcodes now or wait until you expand?
The best time to add marketplace barcodes is when you list the product on that marketplace. If you have been selling on Shopify only and now want to expand to Flipkart, add the Flipkart barcode to your variants at that moment. Do not retroactively go back and add barcodes for channels you might sell on someday.
However, if you already sell on multiple channels and have been tracking barcodes in a spreadsheet, now is the right time to add them all to Shopify. How long the work takes depends on how many variants and channels you have. The payoff comes immediately when you set up an inventory sync app and stop maintaining a barcode mapping file by hand.
Plan this as a project. Export your current barcode mappings from your spreadsheet or marketplace listings. Create a CSV with columns for variant ID, barcode value, and barcode type. Use Shopify's bulk editor or a Zapier workflow to upload the barcodes. Test with one product first. Then run it across your entire catalog.
What happens to your existing single barcode?
If you already have a barcode in the single-barcode field that existed before that change, Shopify moves it into the new barcodes list automatically. It gets tagged as type "unknown" because Shopify does not know if it was a GTIN, UPC, or EAN. You can edit it to assign it the correct type. You can then add new barcodes alongside it.
There is no data loss. Your existing barcode remains in place and continues to work. The change is additive. You are gaining the ability to store more barcodes, not losing the one you have.
If you have been using workarounds like storing multiple barcodes in the single field separated by slashes, this is a good time to clean that up. Separate each barcode into its own entry in the new barcodes list and label it clearly. This makes your data cleaner and makes it easier for apps to parse.
Where does this leave multi-channel brands in India?
The multiple barcode feature is an infrastructure upgrade. It does not change how many channels you can sell on or how many barcodes exist. It changes where the truth lives. Instead of a spreadsheet outside Shopify mapping SKU to barcode by channel, the mapping now lives in Shopify itself.
For brands managing inventory across Shopify, Flipkart, Amazon, and other marketplaces, this reduces operational friction. Inventory sync becomes automated instead of manual. Barcode lookups disappear from your process. Your data is clean and centralized.
If you are currently managing barcodes across multiple places, consolidating them into Shopify is the most important step. After that, setting up an inventory sync app makes the whole operation run by itself. For more on implementing this infrastructure, check the Shopify GraphQL Admin API documentation for product queries.
If you need help planning a multi-channel barcode migration or setting up inventory sync across Shopify and Flipkart, send us your store URL and list the channels you sell on. We will audit your current barcode setup and show you what needs to be consolidated into Shopify, and what inventory sync approach makes sense for your volume and product mix. The conversation is free, and the setup usually takes a week.