Promised for over 2 Years - Can someone please Raise the Collective Variant Limit

Technical Q&A
, ,
1

I have researched and found that this issue has existed for some time, over two years of promises to fix this, with no results… hoping this can be looked at. Stop tweaking and fixing things that aren’t broken or need fixing, and give us the features we need. Stop changing the menus and layouts of our products, for example… And work through requests actually important to us
I have run into an issue with the Shopify Collective program. The collective limits products that have over 100 variants. I know this might seem crazy and that there are workarounds, but we don’t want these. I just want the limit on variations taken off.
I deal with travel products, specifically those that are personalized for different Countries and Cities, which is a vast number. The items work fine on the host store but can’t be shared through the collective.

Thank You

2

The 100-variant cap on Collective traces back to how Shopify’s variant graph is shaped. Every variant has its own InventoryLevel per location, and Collective replicates that on the supplier side at sync time. A 200-variant product through Collective means ~200 inventory propagation paths plus pricing rule attachments per retailer connection. Doable, just not trivial, which is probably why it keeps slipping in roadmap priority.

Realistic workarounds people are running:

  1. Split SKUs into 2-3 master products by primary axis (size, color) and link them with metafields. Less elegant but Collective handles each cleanly.
  2. Sync a single representative product on Collective + handle the long-tail variants direct B2B (custom app + draft order flow).
  3. For high-variant suppliers, skip Collective entirely and run a wholesale storefront on a separate myshopify domain with B2B pricing.

If you are already at 100+ variants with no clean split, your products are probably doing the work of 3-4 SKUs at once (size × color × style × edition). Worth examining whether variants are the actual constraint or if it is a catalog architecture issue showing up at the variant boundary.

How many variants per product on average, and is the 100+ axis size, color, or something else?

3

Hey TravelingBags, totally hear the frustration on this one. The 100-variant cap hits hardest when your variation isn’t really about SKUs but about content, which sounds like your case with country and city personalization.

Building on what @lumine said about the inventory graph reasoning, one angle worth thinking through: if your variations are mostly textual differences for the same physical product, it’s worth questioning whether they should live in the variant model at all.

A pattern that works for travel and personalized products:

  1. Keep one core product per design, with size or color as native variants if needed (stays under 100).
  2. Move country and city personalization out of variants entirely. Treat it as customer-entered or selectable text that flows through to the order as a line-item property.
  3. Same physical SKU on the supplier side, but the customer still sees their specific city or country on the product page and on the order.

That keeps Collective happy because the variant count stays small, while customers still get the per-region experience. Trade-off is you lose per-variant inventory tracking, but for personalization-style differences you usually don’t need it.

FWIW we work on TailorKit which handles this kind of customer-driven personalization layer, but the underlying pattern (line-item properties for content, native variants for SKU-level differences) holds regardless of which app you go with.

Eli

4

I am not the collective supplier; I am the seller, and the collective supplier doesn’t want to split the items.
I don’t know all the reasons why; it’s basically just a NO !
I would be willing to do it for them… It wouldn’t be hard. The company is the Wanderclub. They sell these tiny little collectible tokens for travelers. I get why it’s easy to keep it as is, and I have tried to explain to them why I need this, and he says he understands, just doesn’t want to do it.
I have also explained how much easier it would be for Customers to search by region: North America, South America, Europe, … But he is happy with where they are and doesn’t want to change. UGH! I also can’t afford to buy 1000s of the little tags wholesale to build my own inventory and do what I want… UGH UGH &$^&%#^%*&% UGH

Thanks for the info.