How to set different SKUs per variant on Shopify (combined listings)
Native Shopify variants each carry their own SKU field. So at the variant level, per-SKU tracking works fine: each fabric variant of the Linnea Sofa can have its own SKU like LIN-SOFA-BC, LIN-SOFA-LS, LIN-SOFA-WL. Where the architecture starts to feel constrained is at the product-lineage level. If your operations team treats each fabric as a separate SKU lineage with its own vendor, its own warehouse location, its own freight class, the variant-as-row model creates friction. Combined listings flips the model: each fabric is its own product with its own complete SKU lineage, while the storefront still presents them as a connected listing.
This post covers when to use native variant SKUs versus combined listings for SKU management. We build Rubik Combined Listings, and operations-driven merchants are some of the heaviest users.
In this guide
- Native variant SKUs: what works
- Combined listings SKU architecture
- When to split SKUs into separate products
- Setup walkthrough
- Barcode and vendor code per product
- FAQ
- Related reading
Native variant SKUs: what works
Each native Shopify variant has its own SKU field. The product-level SKU is the variant-level SKU of the first variant; subsequent variants have their own SKUs. So per-SKU tracking is supported out of the box.
What native variants don’t isolate cleanly:
- Vendor field is product-level (one vendor per product, not per variant)
- Product type is product-level
- Custom metafields can be variant-level but require setup; many ERPs don’t read variant metafields cleanly
- Reporting and analytics often roll up to product, making per-SKU revenue analysis indirect
Combined listings SKU architecture
With combined listings, each fabric variant is its own product. Each one carries its own SKU, vendor, product type, metafield definitions, and reporting category. ERP and warehouse integrations treat each grouped product as a distinct SKU lineage, which maps more cleanly to operations.
When to split SKUs into separate products
| Condition | Native variants | Combined listings |
|---|---|---|
| Variants share same vendor | Fine | Optional |
| Variants have different vendors | Awkward | Cleaner |
| ERP needs distinct product records | Limited | Yes |
| Each variant has different freight class | Hard | Native |
| Per-SKU revenue analytics needed | Indirect | Direct |
| Different country of origin per variant | Hard (variant metafield) | Native field |
Setup walkthrough
- Create a separate Shopify product per variant. Set the SKU on each one.
- Set vendor, product type, barcode (UPC/EAN), and any custom metafields per product.
- Install Rubik Combined Listings and group the products.
- Verify your ERP/3PL integration sees each grouped product as a distinct SKU.
“I think it’s an extremely useful application. It’s easy to install and use, and it doesn’t require any learning curve because it’s so intuitive. The helpdesk is also very supportive, the issue I reported was fixed within minutes.”
Paco, Ireland, 2026-02-18, Rubik Combined Listings on the Shopify App Store
Barcode and vendor code per product
Each grouped product has its own barcode field (UPC, EAN, ISBN). For retailers who require unique barcodes per SKU lineage (like submitting to Google Shopping or selling on marketplaces), combined listings keep the data clean. Barcodes don’t get tangled up in one product’s variant array.
Vendor codes can also be per-product. If you source camel boucle from Vendor A and walnut leather from Vendor B, each grouped product can carry its own vendor field. Useful for purchase order generation and reorder workflows.
See the live demo store, watch the tutorial video, or read the getting started guide.
FAQ
Can native Shopify variants have different SKUs?
Yes. Each variant has its own SKU field. Combined listings adds product-level SKU lineage on top, useful when each variant has its own vendor, freight class, or ERP record.
Will my ERP integration work with combined listings?
Yes. Each grouped product is a real Shopify product, so ERP integrations (NetSuite, Brightpearl, Acumatica, Cin7, Stocky) treat them as distinct SKU lineages. The combined listings group is metadata that ERPs typically ignore.
Does combined listings change how I generate SKUs?
No. Generate SKUs the same way you do today (master-product-prefix + variant-suffix). The naming convention can include the fabric or finish identifier so each grouped product’s SKU is recognizable.
Can I import SKUs via CSV?
Yes. Shopify’s product import accepts SKU per row. The bulk grouping flow in Rubik Combined Listings supports tag-based and metafield-based detection, so you can group post-import via the same CSV that brought in the products.
Does this require Shopify Plus?
No. Rubik Combined Listings runs on every Shopify plan.
Where do I see per-product SKU revenue?
Shopify Reports → Sales by Product. Each grouped product shows separately, so per-fabric revenue rolls up cleanly.
Related reading
Umid
Co-Founder at Craftshift