Hi @Chloe_M 
Yes, this is possible, but there are a couple of important distinctions to consider.
Pipeline, like most Shopify themes, normally renders products in the collection grid rather than individual variants. So if you have:
Hoodie
→ Black
→ White
→ Navy
Shopify will normally render one product card for the Hoodie rather than three separate cards.
To display each variant as its own card while keeping them under the same product, you would need to customize the collection/product-card logic so that it loops through the relevant variants and renders a card for each one. The card would also need to pass the variant ID in the product URL, for example: /products/hoodie?variant=123456
That way, clicking “Black” can still open the same Hoodie product page with the Black variant selected.
The tricky part is that this isn’t just a visual change. Once you start rendering variants as collection items, you also need to consider pagination, collection sorting, filters, product counts, inventory, and how the card gets its image, price, and availability from the selected variant. That’s why a simple Liquid modification sometimes works for a basic collection but causes issues with other collection functionality.
If you only need a visual way for customers to move between colors, I’d actually consider a different approach: keep the variants within the same product and use color/image swatches on the product card or product page.
If each color really needs to behave like an independent item throughout the collection, another approach is to use separate products and connect them as related products. This gives you much more control over collection cards, images, inventory and URLs.
I’ve seen merchants use Easify Custom Product Options for the latter type of setup when they want visual color/image choices that can link customers to specific Shopify products. For example, Black, White and Navy can each be represented visually and connected to their corresponding products, without requiring customers to understand how the products are structured behind the scenes.
So I’d choose based on the goal:
Same product + variants displayed separately → custom Pipeline collection-card development.
Separate products that behave like one product family → linked products + visual swatches can be much easier to maintain.
If you specifically need every native variant to appear as an independent collection card without creating duplicate products, I’d lean toward custom development rather than trying to force an app to change Pipeline’s underlying collection loop.