Rubik Combined Listings on Shrine is an interesting pairing because Shrine’s entire brand identity is built around not needing apps. “Built-in features so you don’t need apps” is literally their pitch. And for most things, they deliver on that promise. Shrine packs in mega menus, advanced filters, countdown timers, back-in-stock alerts, and a dozen other features that would normally require separate app installs. But there’s one thing Shrine can’t do, no matter which tier you buy: group separate products together and show swatches on collection cards.
That’s not a knock on Shrine. No Shopify theme does this natively. Grouping separate products requires metaobject references, cross-product data linking, and a swatch rendering engine that reads that data on collection pages. It’s an app-level feature, not a theme-level one. Shopify itself only added native combined listings as a platform feature in late 2023, and they locked it behind Shopify Plus.
Rubik Combined Listings is the one app that a Shrine store genuinely needs. Everything else Shrine handles internally. Product grouping is the exception.
Table of Contents
- What makes Shrine different
- Shrine’s 3 tiers and what each includes
- The one feature Shrine can’t build into a theme
- How RCL works on Shrine
- Collection page swatches on Shrine
- Setup (3 steps)
- Working with Shrine’s no-app philosophy
- Pairing with Rubik Variant Images
- FAQ
- Related reading
What makes Shrine different
Shrine is sold outside the Shopify Theme Store. You buy it directly from the developer, and it comes in three tiers (unlike most themes that have a single price). The entire marketing message centers on reducing your app stack: why pay $10-50/month per feature when Shrine builds those features into the theme code?
Honestly? It’s a good argument. Every app adds JavaScript, every script adds load time, and most stores run 8-15 apps that collectively slow the site down. Shrine’s approach of bundling common features into theme code is smart engineering. We respect it.
But product grouping isn’t a theme feature. It’s a data layer feature. Linking Product A to Product B to Product C and storing that relationship requires metaobjects, metafield references, and an admin UI to manage groups. No theme can ship that because themes don’t have admin pages. Only apps do.
Shrine’s 3 tiers and what each includes
Shrine offers three pricing tiers, each building on the last:
| Tier | Key built-in features | Includes product grouping? |
|---|---|---|
| Starter | Basic theme, clean layout, fast performance | No |
| Pro | Mega menus, countdown timers, advanced search, back-in-stock | No |
| Ultra | Everything in Pro plus advanced filters, animations, custom sections | No |
Notice the third column. None of the tiers include cross-product grouping or collection card swatches for linked products. This isn’t a feature Shrine forgot to build. It’s a feature that structurally cannot live inside a theme file. Shrine can build swatches for variants on a single product (and it does, beautifully). But connecting separate products? That’s app territory.
The one feature Shrine can’t build into a theme
Why can’t a theme handle product grouping? Let’s get technical for a second.
Product grouping requires: (1) a database layer to store which products belong together, (2) an admin interface to create and manage those groups, (3) a Liquid or JavaScript rendering layer that reads group data and injects swatches onto collection pages, and (4) real-time sync when products go out of stock, get archived, or change price.
Themes can do item 3. They can render things. But items 1, 2, and 4 require Shopify app infrastructure: app proxy endpoints, webhook subscriptions, metaobject management, and an embedded admin panel. Themes don’t have access to any of that.
This is why even Shopify’s own solution (native Combined Listings) is a platform feature, not a theme feature. It lives in the Shopify admin, not in Dawn’s codebase. And it costs $2,300/month because it’s only available on Plus.
RCL does exactly what native Combined Listings does, minus the Plus requirement. It stores group data as metafield references, renders swatches via an app embed, and syncs in real time. Starting at $0 for 5 groups. That’s not bad for the one app a Shrine store actually needs.
How RCL works on Shrine
RCL renders swatches inside Shadow DOM. That’s worth repeating because it matters for Shrine specifically. Shrine bundles a lot of CSS. Complex themes with many built-in features tend to have large stylesheets with aggressive selectors. Shadow DOM means RCL’s swatch styles live in a completely isolated scope. Shrine’s CSS can’t accidentally override swatch colors, borders, or spacing. And RCL’s CSS can’t leak into Shrine’s layout.
This is the architectural difference between apps that inject inline styles or append to the theme stylesheet (fragile, breaks on theme updates) and apps that use Shadow DOM (isolated, theme-update-proof). We went with Shadow DOM specifically because themes like Shrine have complex, opinionated CSS that doesn’t play nicely with injected styles.
RCL loads its data from Shopify metafields. No external API calls, no third-party CDN, no server roundtrips. The swatch data is part of the page payload that Shopify already serves. This aligns with Shrine’s performance-first philosophy: you’re not adding a slow, heavy app. You’re adding a lightweight metafield reader with an isolated rendering layer.
Collection page swatches on Shrine
Shrine’s collection pages are clean and structured. Product cards follow a standard layout: image at top, title below, price below that. RCL injects swatches between the title and price, matching the card’s padding and alignment.
Because Shrine stores tend to value minimalism (the whole no-app philosophy attracts design-conscious merchants), here are the swatch settings that work best:
- Shape: Circle
- Size: 18-20px
- Border: 1px, light grey (#ddd)
- Active state: 2px solid, brand color
- Gap: 5px
- Overflow: “+N” pill (keeps the card compact)
Shrine Pro and Ultra both support advanced collection filtering. When a shopper applies a color filter, RCL swatches still appear on each card within the filtered results. The swatches show all colors in the group, not just the filtered one. This way, shoppers can see what other options exist without clearing their filter.
Does that create a UX conflict? Some merchants worry about it. Our take: if someone filters to “Blue” and sees a product card with swatches showing Blue (active), Red, Green, and Black, that’s useful information. It tells the shopper “this product also comes in other colors.” Hiding that information would make the collection feel artificially limited.
Setup (3 steps)
Shrine follows OS 2.0 conventions (even though it’s sold outside the Theme Store), so RCL’s standard setup process works without modifications.
1. Install RCL
Install Rubik Combined Listings from the Shopify App Store. The free plan covers 5 groups for testing.
2. Enable the app embed
Open your Shopify admin, go to Online Store, click Customize on Shrine. In the left sidebar, find App embeds and toggle Rubik Combined Listings on. Save. Takes 10 seconds.
3. Create groups
In the RCL app, create your first group. Select 2 or more products, set the option name (“Color”, “Material”, “Size”, whatever fits), and assign each product its value. RCL writes metafield references to each product. The storefront reads those metafields and renders swatches.
For larger catalogs, use bulk grouping. Three detection methods: title pattern (splits on ” – ” or ” | “), product tags (RUBIK:: format), and shared metafield values. Most Shrine stores we’ve seen use title pattern detection because their product naming is already consistent.
After creating groups, browse your collection page. Swatches appear on each grouped card. Click a swatch, and the card image updates to preview the other product. No page reload. The shopper decides which color they want before clicking through to the product page.
Working with Shrine’s no-app philosophy
If you chose Shrine specifically to minimize your app stack, adding an app might feel counterintuitive. We get that. Here’s our perspective.
The apps Shrine replaces are typically: review apps, wishlist apps, search apps, timer apps, back-in-stock apps, and filter apps. These are features that CAN live in theme code because they operate on data that’s already available in the Liquid context (product data, collection data, cart data). A theme can read that data and render UI around it.
Product grouping is different. It requires creating NEW data (group relationships) that doesn’t exist anywhere in Shopify’s default data model. You need metaobjects to store groups, metafield references to link products to groups, and an admin interface to manage those relationships. That’s app infrastructure.
Think of it this way: Shrine replaces apps that display existing data in better ways. RCL creates new data relationships that didn’t exist before. Different category entirely.
And because RCL uses Shadow DOM and metafields (not injected scripts or external APIs), it doesn’t undermine Shrine’s performance story. Your PageSpeed score stays the same. Your time-to-interactive stays the same. The only thing that changes is that your collection cards now have swatches.
Product page grouping on Shrine
RCL doesn’t just add swatches to collection cards. It also renders group swatches on the product page. When a shopper lands on “Wool Blanket – Charcoal” and that product belongs to a group, RCL shows swatches for all colors in the group (Charcoal, Ivory, Moss, Blush). Clicking a swatch navigates to that product’s page.
On Shrine, the product page group swatches appear near the variant picker. RCL detects the theme’s variant picker location and positions the group swatches accordingly. You can configure separate visual settings for desktop product page, mobile product page, desktop product card, and mobile product card. Four configurations per group.
Shrine’s built-in variant picker handles single-product variants (sizes on a blanket). RCL’s group swatches handle cross-product links (colors across separate blanket products). They sit next to each other on the product page without overlapping. Shrine users sometimes ask if these two will conflict visually. They won’t. Different elements, different data sources, different DOM scopes.
Pairing with Rubik Variant Images
If your Shrine store has products with multiple variants (color AND size, for example), you might want variant-level image filtering on the product page. RCL handles the cross-product grouping. Rubik Variant Images handles the within-product gallery filtering.
Example: your “Wool Blanket – Charcoal” product has variants for Queen and King size, each with different photos. When the shopper picks “King,” RVI filters the gallery to show only King-size photos. Meanwhile, the RCL group swatches at the top still show all blanket colors. Two layers, zero overlap.
We have a dedicated Shrine Pro variant images guide on the RVI blog if you want the full setup for that side of the equation. Both apps have verified Shrine support, both use Shadow DOM, and both are metafield-based. Adding both to a Shrine store brings the total app count to… two. Still pretty minimal.
“I was struggling with separate product pages for different colors/flavors (e.g., aftershave red, green, blue as individual products for better SEO and unique URLs), but I wanted customers to see swatches and switch between them easily, like real variants — on BOTH the product page and collection pages (under each card). This app does it perfectly.”
Ostwint, Romania, March 2026 , Rubik Combined Listings on the Shopify App Store
The SEO case for separate products on Shrine
Why split products in the first place? Because each separate product gets its own URL, its own title tag, its own meta description, its own product images, and its own schema markup. Google indexes each one independently. For a blanket brand with 4 colors, that’s 4 indexable pages instead of 1. Four chances to rank for color-specific searches like “charcoal wool blanket” or “ivory throw blanket.”
The trade-off is collection page clutter: 4 cards instead of 1. RCL eliminates that trade-off. You keep the SEO surface area AND the clean collection experience. One card shows the blanket, swatches show the colors, each swatch leads to its own optimized product page.
For more on this strategy, read the full separate products vs. variants SEO comparison. And for URL structure optimization that complements this approach, see the URL structure SEO guide.
See the live demo store, watch the tutorial video, or read the getting started docs.
Frequently asked questions
Does RCL work with all Shrine tiers (Starter, Pro, Ultra)?
Yes. All three Shrine tiers follow OS 2.0 conventions and support app embeds. RCL’s setup process is identical across Starter, Pro, and Ultra.
Will adding RCL slow down my Shrine store?
No. RCL is metafield-based with no external API calls. It reads data that’s already in the page payload. Shadow DOM rendering adds minimal DOM weight. If you chose Shrine for performance, RCL won’t undo that.
Does Shrine’s built-in filter system work with RCL swatches?
Yes. Shrine Pro and Ultra include advanced collection filters. RCL swatches render on cards within filtered results. The two systems are independent: filters control which cards show up, RCL controls which swatches appear on each card.
Do I need Shopify Plus?
No. RCL works on Basic, Shopify, Advanced, and Plus plans. Shopify’s native combined listings feature requires Plus, but RCL does not.
How many groups can I create?
Free plan: 5 groups. Starter ($10/month): 100. Advanced ($30/month): 500. Premium ($50/month): 5,000. Annual billing saves 17%. Every feature is available on every plan.
Can I use RCL alongside Shrine’s built-in variant swatches?
Yes. Shrine’s variant swatches handle single-product variants (like sizes). RCL handles cross-product grouping (like colors across separate products). They serve different purposes and don’t conflict. Shadow DOM keeps RCL’s styles isolated from Shrine’s CSS.
Shrine is not on the Shopify Theme Store. Does RCL still support it?
Yes. RCL supports 350+ themes including those sold outside the Theme Store. Shrine follows standard OS 2.0 patterns, so RCL’s app embed works normally. We’ve tested and verified Shrine support across all three tiers.
