Rubik Combined Listings Swatch is a Shopify app that links separate product listings together so they display as a single variant listing, with image or colour swatches on the collection card and on the product page. Every underlying product keeps its own URL, its own search-engine equity, and its own independent inventory. Craftshift launched it on the Shopify App Store on February 3, 2026, in the Product Variants category.
The catalogue problem native variants don't solve
Native Shopify variants live inside one product record, on one shared inventory context. Plenty of catalogues can't work that way: stock counted per colourway, a different vendor behind each variation, or years of growth one listing at a time. The result is separate products for what a shopper reads as one. Rubik Combined Listings Swatch links them without merging anything.
This is rarely a mistake. It's an operations decision made years before anyone looked at the storefront consequences, and unwinding it is expensive. Three patterns produce it more than any others.
- Independent inventory tracking. Each variation is counted, reordered and reconciled on its own, usually inside a warehouse or ERP system that treats every SKU as a first-class item with its own reorder point rather than a child row under a parent product.
- Different vendors per variation. The core colourway comes from one supplier and the seasonal drop from another, with different lead times and different costs. Collapsing them into one product record flattens data the buying team relies on every week.
- Catalogue drift. The store launched with three products, added a fourth colour in year two and a fifth in year three, each as a fresh listing. By the time it looks messy, restructuring means rewriting URLs, redirects, and inventory history.
The cost lands on the shopper. A collection page shows six near-identical cards. The product page offers no way to switch colour, so choosing means going back, re-scanning thumbnails, and clicking in again. Every extra step is another chance to leave.
The cost also lands on merchandising. Six separate cards eat six slots in a collection grid that should be showing six different products. And the shopper who wanted "that jacket, but in green" has to work out that green even exists.
What Rubik Combined Listings Swatch does
Rubik Combined Listings Swatch groups sibling products and renders them as swatches on the product card and the product page. Click a colour, land on that product's own page. Product information syncs across the group in real time, and every product keeps independent inventory, its own pricing, and its own indexed URL.
The feature set breaks into four jobs.
- Grouping. Combine sibling products so they display as variants on product cards, and build subcategories or product groups where a catalogue varies on more than one axis.
- Display. Variant image swatches and colour swatch grouping styles, with brand and style controls deep enough that the row matches your theme instead of fighting it.
- Sync. Real-time automatic sync of product information across the group, so an edit to one sibling doesn't leave the rest of the group displaying stale data.
- Scale. Bulk grouping by title, tag or metafield, AI credits to automate the grouping setup, multi-language and multi-currency support, and a lightweight front-end implementation with zero page-load impact.
Real-time sync is the quiet one. Grouped products drift — someone edits one sibling's description or media and the rest of the group carries on showing the old information. Automatic sync across the group is what stops a grouping you set up in March from quietly decaying by June.
Underline the zero-page-load-impact part. A swatch row renders on every collection card, in the critical path of the first page a shopper judges, so weight there is the most expensive weight in the store. Rubik stays light, and it carries Built for Shopify certification — Shopify's own bar for performance, embedding and app quality.
Grouping at scale: title, tag, or metafield
Bulk grouping is what separates a demo from a deployable app. Rubik Combined Listings Swatch groups products automatically by title, by tag, or by metafield, so a 400-SKU catalogue never needs 400 manual pairings. AI credits are included on every plan, including the free one, to automate the setup.
By title
Title-based grouping is the fastest route when your naming is consistent: "Merino Crew Neck — Charcoal", "Merino Crew Neck — Oat", "Merino Crew Neck — Navy". The shared stem becomes the group, the suffix becomes the swatch label. Costs nothing to try, and it fails loudly rather than silently.
By tag
Tag-based grouping is explicit control. You decide exactly which products belong together, whatever they're called, by applying a shared tag. It's the pragmatic option for catalogues that have been through a rebrand, a migration, or three different naming conventions.
By metafield
Metafield-based grouping is the right answer when a style code, parent SKU, or product family already lives in your PIM or ERP and syncs into Shopify. The grouping then maintains itself: new products arriving with the same style code join the correct group without anyone opening the app.
Inconsistent titles, no tags, no metafield? That's what the AI credits are for — they work out the groupings for you. Every plan includes a monthly allowance, so the free plan is enough to test the approach on a slice of the catalogue before committing.
Subcategories and product groups
Not every catalogue varies on one axis. A cushion sold in four fabrics and three sizes, or a guide sold in two formats across three editions, needs more structure than a flat swatch row. Rubik Combined Listings Swatch supports subcategory and product-group creation, so a group can nest instead of sprawling into twelve undifferentiated swatches.
What shoppers see, including the sold-out case
The visible output is a swatch row: either variant image swatches showing the actual product photo, or colour swatches in one of several grouping styles. Both appear on collection cards and product pages, so a shopper can see the full range from the grid and switch between siblings without backtracking.
Out-of-stock behaviour is configurable, and it's the setting worth thinking hardest about. A sold-out sibling can be shown crossed out, moved to the end of the swatch row, or hidden from the group entirely.
Crossing out advertises the depth of your range and implies a restock is coming, which suits a brand whose colourways return every season. Moving sold-out siblings to the end keeps buyable options in front without pretending the rest never existed. Hiding is the cleanest look and the right call for catalogues carrying a long tail of permanently sold-out variations.
Multi-language and multi-currency support carries the swatch layer onto Shopify Markets storefronts in the shopper's own language and currency, and the brand-level styling controls make the row read as part of your theme rather than a bolt-on.
For a catalogue that needs independent stock per variation
| What you need | Native variants | Combined listings |
|---|---|---|
| Inventory per variation | One product record | Fully independent |
| Indexed URL per variation | One shared URL | One URL each |
| Different vendor per variation | Single vendor field | Per product |
| Swatch row on collection cards | Theme dependent | Built in |
| Catalogue restructuring required | Merge products first | None |
Combined Listings vs Variant Images: which Rubik app
Craftshift ships two apps that sound adjacent and solve opposite halves of the same experience. Rubik Combined Listings Swatch links entirely separate products together as if they were variants of one listing. Rubik Variant Images works inside a single product that already has variants, assigning the right photos to each variant combination.
One question decides it: is each variation its own product record? If green and navy are two products with two URLs and two inventory counts, you need Combined Listings. If green and navy are two options inside one product and the problem is that the wrong photo shows when a shopper picks navy, you need Rubik Variant Images.
Plenty of catalogues need both, because plenty of catalogues are half one and half the other: a legacy range split into separate products, plus newer products built with variants from day one. The two apps work at different levels and stack cleanly, so running both is the normal outcome for any catalogue with some history behind it.
Pricing, plans, and what a "product group" is
Rubik Combined Listings Swatch has a permanently free tier and three paid plans, all metered on product groups and AI credits rather than on catalogue size or traffic. Annual billing on every paid plan works out at ten months for twelve.
- Free5 product groups · 100 AI credits/mo
- Starter — $10/mo or $100/yr100 groups · 1,000 AI credits
- Advanced — $30/mo or $300/yr500 groups · 5,000 AI credits
- Premium — $50/mo or $500/yr5,000 groups · 50,000 AI credits
The unit that matters is the product group, not the product. A jacket sold in eight colourways is one group, not eight, so the 100-group Starter plan covers a catalogue with several hundred individual listings. Count your families, not your SKUs, before picking a tier.
The free tier is usable as a pilot rather than a demo. Five groups is enough to cover your five best-selling families, ship them to the live storefront, and read the difference in collection-page click-through before deciding whether a paid tier earns its place.
As of writing, the app is rated 5.0 out of 5 stars from 63 reviews on the Shopify App Store, with 98% of reviewers leaving five stars and the remaining 2% leaving four. It also carries Built for Shopify certification and ships an MCP server for merchants wiring their storefront tooling into AI agents.
Where this fits if you sell digital products
Digital catalogues split into separate products for their own reasons: one listing per file format, one per licence tier, one per bundle size. Each needs its own file mapping and its own delivery rules, which makes a single multi-variant product awkward. So the listings stay separate, and the storefront pays for it.
A sheet-music seller shipping PDF, MusicXML and printed editions as three products has exactly this problem. So does a font foundry selling desktop, web and app licences separately, or a template studio selling single-seat and team versions of the same file set.
The same logic covers bundle laddering: single track, five-track EP, full stem pack, each its own product with its own file set. A swatch row turns three isolated listings into one visible ladder — the cheapest upsell surface most digital catalogues never build.
Combined listings put a format or licence switcher on the page without collapsing those products into one, which keeps every listing individually mappable in Alva Digital Downloads. The delivery side stays exactly as it was; only the shopper's path through the catalogue changes. If you are still deciding between apps, the side-by-side comparison of every serious combined-listing app is the faster read.
How to tell a combined listing is the right fix
Combined listings solve a presentation problem, which makes the fit easy to check before you install anything. Three questions settle it.
- Does each variation need its own stock count? If size S and size M draw down the same pool and always will, native Shopify variants already have you covered. If every colourway is counted, reordered and reconciled on its own, that is precisely the catalogue Rubik was built to group.
- Is a catalogue rebuild already on the calendar? A scheduled migration is its own moment to decide which products should have been variants. Everyone else — which is most stores — gets the storefront fixed this week without rewriting a single product record.
- Are you happy with one cart line per colourway? Grouped products stay separate products, so two colourways means two lines. That is the design working as intended: independent inventory is the entire reason those listings are separate, and it survives the grouping untouched.
The trade is a good one. Keep the operational structure your warehouse and buying team depend on, and stop making shoppers reverse-engineer it from a collection grid.
Frequently asked questions
No. Rubik Combined Listings Swatch is a storefront presentation layer. It links sibling products so they display as one variant listing with swatches, but every product keeps its own page, its own SEO, and its own independent inventory. Nothing is merged, no records are rewritten, and you can group and ungroup products without touching stock data.
There is a free plan with 5 product groups and 100 monthly AI credits. Starter is $10/month or $100/year for 100 product groups and 1,000 AI credits. Advanced is $30/month or $300/year for 500 groups and 5,000 credits. Premium is $50/month or $500/year for 5,000 groups and 50,000 credits. Current pricing is on the Shopify App Store listing.
Rubik Combined Listings Swatch supports bulk grouping by product title, by tag, or by metafield, so a large catalogue is grouped by rule rather than product by product. AI credits, included on every plan, automate the setup where naming is inconsistent. You can also build subcategories and product groups for catalogues that vary on more than one axis.
Out-of-stock display is configurable. A sold-out sibling can be shown crossed out, moved to the end of the swatch row, or hidden from the group entirely. Crossing out signals range depth and an expected restock; moving it to the end keeps in-stock options first; hiding keeps the row clean on catalogues with a long tail of sold-out colourways.
Rubik Combined Listings Swatch links entirely separate products together so they behave like one variant listing. Rubik Variant Images works inside a single product that already has variants, assigning the right photos to each variant combination. The deciding question is whether each variation is its own product record. If it is, you need Combined Listings; if not, you need Variant Images.