Home › Blog › Shopify Product Bundle Schema

Shopify Product Bundle Schema: Why AI Shopping Agents Can't Price Your Bundles (and the hasPart Fix)

2026-06-12 — ~16 min read — hasPartBundle schemaPriceSpecificationShopify LiquidAI shopping

A customer asks ChatGPT: "What's the best skincare starter kit under $150?" Your $129 bundle — cleanser, toner, and moisturizer, a $210 retail value — does not appear in the answer. ChatGPT sees a $129 product with a vague title and no structured component data. It has no idea you're selling three products for the price of two.

Bundles are one of the highest-margin SKUs in DTC e-commerce. They also produce some of the worst AI shopping agent results — not because AI agents can't handle bundles conceptually, but because the schema markup needed to describe a bundle is almost never present. This guide explains exactly what's missing and how to fix it.

Why Bundles Break AI Shopping Agents

When ChatGPT Shopping, Perplexity Shopping, or Google AI Mode indexes a product page, it reads structured JSON-LD data. A standard Shopify product page generates a minimal Offer block that looks like this:

{
  "@type": "Product",
  "name": "Skincare Starter Kit",
  "offers": {
    "@type": "Offer",
    "price": "129.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}

This tells the AI agent: there is a product named "Skincare Starter Kit" that costs $129. That is all. It conveys nothing about:

• What products are inside the bundle
• What the individual retail prices of those products are
• How much the customer saves compared to buying separately
• Which specific variants (sizes, shades) are included

From a pure structured-data perspective, your $129 bundle looks identical to a $129 face cream. An AI agent answering "best skincare value under $150" will rank products on price, reviews, brand signals, and description quality — but without component data, it cannot compute that your bundle delivers $210 in value. It will rank you the same as a single-item $129 product.

This gap also affects how AI agents answer specific queries. Consider these common purchase-intent queries that bundle schema would directly answer:

• "skincare kit that includes a cleanser AND moisturizer under $150"
• "coffee bundle with grinder and beans together"
• "camera kit that comes with lenses included"
• "starter pack for [specific hobby] with everything I need"

Every one of these queries is asking about component composition. Without hasPart, your bundle is invisible to them — even if your title says "Starter Kit" or "Complete Bundle." AI agents do not parse prose titles for component claims. They parse structured data.

This is the same fundamental issue discussed in our product descriptions guide — but for bundles the gap is even larger because the composition claim is completely unverifiable from unstructured text.

Schema.org Vocabulary for Bundles

Schema.org provides several properties for describing product composition and relationships. Here is the full vocabulary with notes on when each applies to Shopify bundles:

The critical distinction is hasPart vs. isRelatedTo. hasPart is a compositional claim — the customer receives all declared parts when they purchase the bundle. isRelatedTo is an associative claim — the products are connected but not necessarily included. Using isRelatedTo for bundle components is the most common mistake, and it causes AI agents to represent the bundle as a product that "goes well with" other products rather than one that contains them.

For add-on kits — products sold separately that expand a base purchase — isAccessoryOrSparePartFor on the add-on pointing to the base product is the correct signal. This tells AI agents that the expansion pack only makes sense if the customer has (or is buying) the base product.

Bundle JSON-LD Patterns

Pattern 1: Simple multi-product bundle

The most common DTC bundle: two or three products packaged together and sold as one SKU at a discount.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "@id": "https://yourstore.com/products/skincare-starter-kit",
  "name": "Skincare Starter Kit",
  "description": "Complete beginner skincare routine: gentle cleanser, hydrating toner, and daily moisturizer.",
  "sku": "SKU-SKIN-KIT-001",
  "image": "https://yourstore.com/products/starter-kit.jpg",
  "hasPart": [
    {
      "@type": "Product",
      "name": "Gentle Daily Cleanser (100ml)",
      "sku": "SKU-CLEAN-001",
      "url": "https://yourstore.com/products/gentle-daily-cleanser",
      "offers": {
        "@type": "Offer",
        "price": "28.00",
        "priceCurrency": "USD",
        "priceSpecification": {
          "@type": "PriceSpecification",
          "price": "28.00",
          "priceCurrency": "USD",
          "priceType": "https://schema.org/ListPrice"
        }
      }
    },
    {
      "@type": "Product",
      "name": "Hydrating Facial Toner (150ml)",
      "sku": "SKU-TONE-001",
      "url": "https://yourstore.com/products/hydrating-facial-toner",
      "offers": {
        "@type": "Offer",
        "price": "32.00",
        "priceCurrency": "USD",
        "priceSpecification": {
          "@type": "PriceSpecification",
          "price": "32.00",
          "priceCurrency": "USD",
          "priceType": "https://schema.org/ListPrice"
        }
      }
    },
    {
      "@type": "Product",
      "name": "Daily Moisturizer SPF 30 (50ml)",
      "sku": "SKU-MOIST-001",
      "url": "https://yourstore.com/products/daily-moisturizer-spf30",
      "offers": {
        "@type": "Offer",
        "price": "48.00",
        "priceCurrency": "USD",
        "priceSpecification": {
          "@type": "PriceSpecification",
          "price": "48.00",
          "priceCurrency": "USD",
          "priceType": "https://schema.org/ListPrice"
        }
      }
    }
  ],
  "offers": {
    "@type": "Offer",
    "price": "89.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "priceSpecification": {
      "@type": "PriceSpecification",
      "price": "108.00",
      "priceCurrency": "USD",
      "priceType": "https://schema.org/ListPrice"
    }
  },
  "additionalProperty": [
    {
      "@type": "PropertyValue",
      "propertyID": "bundleComponents",
      "value": "3"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "bundleSavings",
      "value": "19.00"
    },
    {
      "@type": "PropertyValue",
      "propertyID": "bundleSavingsPercent",
      "value": "17.6"
    }
  ]
}

Note the two-level pricing structure: each component's hasPart Product has a ListPrice Offer (the individual retail price), and the bundle's top-level Offer has the discounted bundle price plus a ListPrice PriceSpecification equal to the sum of components. This lets AI agents compute and communicate the bundle savings.

Pattern 2: Add-on expansion kit

An expansion pack that requires a base product. This pattern uses isAccessoryOrSparePartFor on the add-on, pointing to the base product URL.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Advanced Filter Replacement Kit (3-pack)",
  "description": "Replacement filters for the AquaPure Pro water filtration system. Compatible with all AquaPure Pro models.",
  "sku": "SKU-FILTER-3PK",
  "isAccessoryOrSparePartFor": {
    "@type": "Product",
    "name": "AquaPure Pro Water Filter System",
    "url": "https://yourstore.com/products/aquapure-pro",
    "@id": "https://yourstore.com/products/aquapure-pro"
  },
  "offers": {
    "@type": "Offer",
    "price": "39.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}

Pattern 3: Variant-specific bundle components

Some bundles let customers choose a variant for one or more components — for example, a coffee bundle where the customer picks their roast. In this case, use a ProductGroup inside hasPart for variable components, referencing the individual variants via hasVariant. See our ProductGroup JSON-LD guide for the full variant schema pattern.

Shopify Liquid Implementation

The following Liquid snippet inserts bundle-aware JSON-LD when a product has the bundle tag and a bundle.components metafield. Add this to your theme's product.liquid or product-form.liquid, replacing the default Shopify JSON-LD section.

First, set up the required metafields in Shopify Admin under Settings → Custom data → Products:

• bundle.components — type: JSON, stores component array
• bundle.individual_total — type: Decimal (optional, computed from components)

The bundle.components metafield stores a JSON array structured as:

[
  {
    "name": "Gentle Daily Cleanser (100ml)",
    "sku": "SKU-CLEAN-001",
    "url": "/products/gentle-daily-cleanser",
    "price": 28.00
  },
  {
    "name": "Hydrating Facial Toner (150ml)",
    "sku": "SKU-TONE-001",
    "url": "/products/hydrating-facial-toner",
    "price": 32.00
  }
]

Then in your product Liquid template, use this snippet to emit bundle-aware JSON-LD:

{% assign is_bundle = false %}
{% for tag in product.tags %}
  {% if tag == 'bundle' %}
    {% assign is_bundle = true %}
  {% endif %}
{% endfor %}

{% assign bundle_components_raw = product.metafields.bundle.components %}
{% assign bundle_individual_total = product.metafields.bundle.individual_total %}


{% endunless %}

Signaling Bundle Savings Correctly

There are two common but incorrect ways Shopify merchants try to signal bundle value, and one correct way.

The semantic distinction matters because AI agents treat compare_at_price (or the schema equivalent, a ListPrice higher than the current Offer price without hasPart) as a sale signal. With hasPart present, the same ListPrice signal is interpreted as a bundle savings signal — the higher ListPrice is the sum of parts, the lower Offer price is the bundle discount. For more on pricing schema signals, see our priceValidUntil and sale pricing guide.

Common Mistakes

Testing Your Bundle Schema

After implementing the Liquid snippet, verify your bundle JSON-LD using the following steps:

1. View page source on a bundle product page. Search for "hasPart" — it should appear in the application/ld+json block. If it is absent, check that the product has the bundle tag and the bundle.components metafield is set.
2. Google Rich Results Test (search.google.com/test/rich-results) — paste the product URL. Look for the Product result with the Offer price. Google does not show hasPart in rich results but validates the JSON-LD syntax.
3. Schema.org Validator (validator.schema.org) — paste your JSON-LD block directly. This will surface any property or type errors in your hasPart structure.
4. CatalogScan scan — run a free scan to check whether CatalogScan detects the bundle tag + hasPart pair and marks the bundle schema gap as resolved.

For a more complete guide to structured data testing tools for Shopify, see our structured data audit tools roundup.

Frequently Asked Questions