Build a Shopify Combined Listings Media Map Before Merging Products

01

1. Confirm that Combined Listings fits the catalog and storefront

Check eligibility and theme behavior before committing creative-production time.

Shopify describes Combined Listings as a way to connect separate products through a shared option while retaining product-specific information. Each child remains a separate product, so it can retain its own title, description, images, and URL. The parent organizes the relationship but is not the purchasable inventory-bearing item (Shopify developer documentation). That distinction is why the workflow must be organized around children rather than around a generic parent gallery.

Shopify’s current documentation says the Combined Listings app requires Shopify Plus or an enterprise commerce plan, the Online Store sales channel, and a compatible theme. Shopify also warns that apps adding content to product pages might not work correctly on combined-listing pages and recommends previewing the listing before publishing it (Shopify Help Center). Confirm those dependencies with the storefront owner before booking photography or restructuring the catalog.

1. Confirm store-plan and Online Store eligibility.
2. Confirm that the production theme supports Combined Listings.
3. List product-page apps or custom blocks that must survive a child-product switch.
4. Choose an owner for theme compatibility and storefront QA.

02

2. Freeze the proposed child-product roster

Create the catalog roster before creating media tasks.

Start with the planned parent name, followed by one row for every proposed child. Record the exact Shopify product name, product ID or primary SKU, URL handle, shared option value, current publication status, and responsible product owner. Use identifiers rather than visual descriptions such as “blue bottle” or “large kit”; similar-looking products are precisely where incorrect media assignments occur.

Shopify says children must already exist as products, one product can belong to only one combined listing at a time, and a combined listing can contain up to 60 child products (Shopify Help Center). Check those constraints while freezing the roster, not after asset production begins.

Add a separate row for the parent or default landing experience. The parent can have product details and media, but Shopify’s developer documentation identifies it as a non-purchasable product without inventory or sales data (Shopify developer documentation). Decide what a visitor should see when reaching that URL before selecting a child.

1. Name the proposed parent listing.
2. Record every child’s product ID or SKU and URL handle.
3. Define the exact shared-option label and unique value for each child.
4. Flag any child already assigned to another combined listing.
5. Add a parent/default-experience row.

03

3. Build one media-map row per child

The media map should describe the intended storefront state, ownership, and implementation status.

Use columns for: parent listing; child product; product ID or SKU; shared option value; child URL; hero or featured media; ordered gallery; front and rear angles; detail shots; scale, fit, or dimensions; lifestyle image; packaging or included-items image; video file and cover image; 3D model; alt text; disclosures; missing assets; rights notes; creative owner; merchandising approver; due date; approval status; Shopify upload status; and storefront QA result.

Do not reduce the map to a folder of filenames. “IMG_2048-final.jpg” does not explain which child it represents, why it belongs in position three, whether the depicted packaging is current, or who approved it. For gallery sequence, number every position explicitly: 01 hero, 02 front, 03 rear, 04 detail, and so forth. If an asset is shared, list the same approved asset against each applicable child and mark the reuse as deliberate.

Ordinary Shopify variants support one assigned image rather than a complete variant-level set of images, videos, and 3D media. Additional visual coverage belongs to the product’s media gallery (Shopify Help Center). Therefore, map the complete gallery at the child-product level. Add within-child variant-image fields only when variants inside that child have a genuine visual difference.

1. Create one row for each child and one for the parent experience.
2. Identify the intended first media item.
3. Write the complete gallery order rather than listing an unsequenced folder.
4. Mark shared assets explicitly.
5. Name both the delivery owner and the accuracy approver.

04

4. Audit existing media before commissioning production

Classify what already exists, then turn only genuine coverage gaps into work.

Shopify product media can include images, videos, and 3D models. The store-wide Files area can be reviewed and filtered by attributes including file type, usage reference, and alt text (Shopify Help Center). Compare those files with your source library, photographer deliveries, packaging renders, and previously approved campaign assets.

Give each candidate asset one controlled status: Approved, Needs edit, Needs verification, Missing, Shared, or Do not use. “Needs verification” is important when the visual identity is uncertain—for example, when two finishes look similar, old and new packaging coexist, or included components changed. Do not let uncertainty become implicit approval.

Treat “Shared” as a merchandising decision, not a shortcut. A neutral sizing diagram or brand-level lifestyle image may apply to several children. A hero depicting a specific color, finish, dimension, formula, package count, or included accessory usually should not be inherited by another child unless it is factually accurate there too.

1. Search Shopify Files and the team’s master asset library.
2. Match every candidate file to an exact child identifier.
3. Apply an audit status and record why edits or verification are required.
4. Quarantine obsolete, inaccurate, rights-restricted, or unidentified files.
5. Calculate missing coverage separately for every child.

05

5. Define minimum media coverage and production tasks

Use a repeatable coverage standard, but adapt it to what shoppers need to distinguish each child.

A practical baseline is a child-specific hero, primary and secondary angles, material or feature details, scale or fit context, a lifestyle or in-use image, packaging or included-items coverage where relevant, and disclosures required for accurate merchandising. Add a demonstration video when movement, assembly, texture, or setup is difficult to communicate in stills. Add a 3D model when spatial inspection materially helps the product explanation.

The first item in the product media list is featured media and can be used on other Shopify surfaces, including collection, cart, checkout, and home-page contexts (Shopify Help Center). Hero assignment and ordering are therefore launch controls, not final cosmetic adjustments.

Convert every gap into a production task containing the child product or SKU, deliverable, shot purpose, orientation or crop, owner, reviewer, due date, usage or rights notes, final file location, and Shopify upload status. Use the broader Creative Workflow For Ecommerce to structure briefing and review, and connect dependencies to Help/Roadmaps/What Is The Creative Roadmap.

1. Define required coverage by product category.
2. Compare each child row with that standard.
3. Create one owned task for each missing or deficient deliverable.
4. Specify how the output will prove the identity or feature of that child.
5. Require merchandising approval before marking an asset ready to upload.

06

6. Upload, label, and sequence child media first

Implement the approved child galleries before building the parent relationship.

On each child product, upload the approved media, put the designated hero first, arrange the rest in the mapped order, add alt text, and check video cover images. Shopify’s product-media tools support adding and rearranging media from the product page (Shopify Help Center). A second person should compare the live admin sequence with the approved row rather than relying on the uploader’s memory.

Shopify notes that removing media from a product does not necessarily remove the underlying file from the store. It also warns that editing a file from the Files area can affect every place where that file is used (Shopify Help Center). Before replacing a shared file, identify all children and other storefront placements that reference it.

Shopify recommends concise, descriptive alt text and gives a recommended length of 125 characters or fewer, with a technical maximum of 512 characters (Shopify Help Center). Describe the displayed child and relevant visual information rather than repeating the product-family name across every image. Keep approved master files and handoff context together; ATIYO users can follow Help/Integrations/Uploading And Storing Assets In The Vault for the product’s asset-storage workflow.

1. Upload only approved files to the correct child.
2. Place the approved hero first.
3. Match the remaining sequence to the media map.
4. Add child-accurate alt text and inspect video cover images.
5. Have a second person confirm the implementation.
6. Update upload and approval statuses in the map.

07

7. Create the combined listing as a draft

Connect already-prepared children instead of using the parent build to discover media problems.

Shopify creates a new combined listing in Draft status by default. In the Combined Listings app, add the existing child products, define the shared option, and assign each child a unique option value (Shopify Help Center). Keep the listing in draft until every row has passed storefront QA.

The shared-option wording must agree with the media map and product content. If the selector says “Walnut,” the selected child’s hero, details, description, and included-item images must all represent the walnut product. Avoid vague labels that force the customer to infer which visual or specification changed.

If the parent URL will be linked from navigation, campaigns, or editorial pages, implement and review its default media as a separate experience. Do not assume the first child’s gallery is automatically the best parent landing state.

1. Confirm all child rows are approved and uploaded.
2. Create the combined listing in Draft.
3. Add children using exact product identifiers.
4. Check shared-option labels and values against the map.
5. Implement the approved parent/default media.
6. Keep the listing unpublished until full QA is complete.

08

8. Verify every child on the storefront

Test the rendered customer experience, not only the product relationship shown in Shopify admin.

A compatible theme should update the displayed product information when a shopper changes the shared option, including the sibling product’s images, description, price, and URL (Shopify theme documentation). Test every child because an accurate first selection does not prove the remaining mappings.

For each shared-option value, confirm the label, hero, complete gallery, title, description, price, availability, and URL. Open the child URL directly and confirm it restores the intended selection. Test refresh, back, and forward navigation; add the item to cart and verify that the purchasable child was added rather than the non-purchasable parent.

Review mobile and desktop galleries separately. Check thumbnail identity, swipe behavior, video covers, video playback, 3D rendering, alt text, and app-provided PDP blocks. Shopify says all Shopify-built Online Store 2.0 themes support video and 3D media, while merchants using third-party themes should check theme documentation or contact the developer (Shopify Help Center). Record failures against the exact child row, owner, and retest date.

Also decide whether storefront search and recommendations should expose the parent, children, or both. Shopify documents settings for controlling combined-listing visibility in Search & Discovery (Shopify Help Center). That decision affects which hero images customers encounter before reaching the PDP.

1. Switch through every shared-option value on desktop.
2. Repeat the complete test on mobile.
3. Open every child URL directly and refresh it.
4. Verify gallery order, video, 3D media, alt text, price, availability, and cart behavior.
5. Test product-page app blocks and custom theme content.
6. Confirm search and recommendation visibility.
7. Resolve failures and rerun the affected child’s complete test.

09

9. Preserve ownership and learning after launch

Keep the map as the record for later packaging changes, reshoots, and gallery revisions.

After launch, record the publication date, approved parent and child URLs, final asset locations, exceptions, and unresolved follow-up work. When packaging, included components, specifications, or visual identity change, reopen the affected child row rather than replacing a shared file without impact review.

ATIYO can organize this media map alongside roadmaps, briefs, brand context, assets, iterations, approvals, and reusable team learnings. It does not connect to ad accounts, buy media, calculate ROAS, or automatically know performance. Media performance remains in the ad platform, and ATIYO preserves creative context and learnings that users record.

If the team needs one operational home for the roadmap, asset decisions, owners, and revisions, start a card-confirmed seven-day ATIYO trial before billing begins.

1. Archive the approved launch-state map.
2. Record exceptions and temporary substitutions.
3. Reopen affected child rows when product details or packaging change.
4. Bring externally observed performance lessons back as recorded context, without treating ATIYO as an ad-reporting system.