Shopify Multi-Currency Price Schema: PriceSpecification for AI Agents

Why Multi-Currency Schema Matters for AI Agents

AI shopping agents like ChatGPT Shopping, Perplexity, and Google's AI Overviews answer queries such as "find me a leather wallet under £50." To answer correctly, the agent needs to know: (a) your wallet's GBP price, and (b) whether you ship to the UK. Both signals come from your structured data — not from your storefront UI, which the AI crawler may never see in its localized form.

The problem with single-currency JSON-LD on a multi-currency store:

• Your JSON-LD outputs price: 59.00, priceCurrency: USD on your primary storefront
• Your UK Market charges £48.00 — but that page lives at yourstore.com/en-gb/products/wallet
• AI crawlers indexing your primary storefront see only the USD price
• When a UK shopper asks ChatGPT "leather wallets under £50," your product shows up as $59 USD — or not at all, because the agent can't determine GBP equivalence

Adding multi-currency PriceSpecification blocks to your primary product page structured data solves this: one page, all currencies, region-constrained via eligibleRegion.

Schema.org Types for Multi-Currency Pricing

PriceSpecification properties

DefinedRegion properties

Multi-Currency Offer Block: Complete JSON-LD Example

This example shows a product sold in three Shopify Markets: US (USD), UK (GBP), and EU (EUR). Each market gets its own Offer with the correct priceCurrency and eligibleRegion. All three are nested inside a single Product block using the offers array.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Premium Leather Bifold Wallet",
  "sku": "WALLET-LTH-BRN-001",
  "offers": [
    {
      "@type": "Offer",
      "priceCurrency": "USD",
      "price": "59.00",
      "availability": "https://schema.org/InStock",
      "url": "https://acme-store.com/products/premium-leather-wallet",
      "eligibleRegion": {
        "@type": "DefinedRegion",
        "name": "North America",
        "containsPlace": [
          {"@type": "Country", "identifier": "US"},
          {"@type": "Country", "identifier": "CA"}
        ]
      }
    },
    {
      "@type": "Offer",
      "priceCurrency": "GBP",
      "price": "48.00",
      "availability": "https://schema.org/InStock",
      "url": "https://acme-store.com/en-gb/products/premium-leather-wallet",
      "valueAddedTaxIncluded": true,
      "eligibleRegion": {
        "@type": "DefinedRegion",
        "name": "United Kingdom",
        "containsPlace": [
          {"@type": "Country", "identifier": "GB"}
        ]
      }
    },
    {
      "@type": "Offer",
      "priceCurrency": "EUR",
      "price": "55.00",
      "availability": "https://schema.org/InStock",
      "url": "https://acme-store.com/en-eu/products/premium-leather-wallet",
      "valueAddedTaxIncluded": true,
      "eligibleRegion": {
        "@type": "DefinedRegion",
        "name": "European Union",
        "containsPlace": [
          {"@type": "Country", "identifier": "DE"},
          {"@type": "Country", "identifier": "FR"},
          {"@type": "Country", "identifier": "NL"},
          {"@type": "Country", "identifier": "IT"},
          {"@type": "Country", "identifier": "ES"}
        ]
      }
    }
  ]
}

Shopify Liquid Template Implementation

Shopify Markets uses subfolders (/en-gb/, /en-eu/) or subdomains for localized storefronts. The cleanest approach is to output the primary market currency on your main storefront, and let each localized storefront output its own market currency. For stores that want all currencies on one page (for crawlers indexing only the primary URL), use a Liquid object or metafield approach.

Single-storefront approach: primary currency + market hints

{% comment %} product.liquid — primary storefront with market currency hints {% endcomment %}

Shopify Markets subfolder approach: per-locale storefront

When your Shopify Markets setup creates /en-gb/products/handle URLs, Google and AI crawlers index those URLs separately. Each subfolder page's Liquid context has the correct localized currency. Use localization.country and cart.currency to output the region-appropriate price in JSON-LD:

{% comment %} product.liquid — Markets-aware multi-currency JSON-LD {% endcomment %}

ISO 4217 Currency Codes for Common Shopify Markets

VAT-Inclusive Pricing for EU and UK Markets

EU and UK law requires consumer-facing prices to include VAT. Your GBP and EUR prices on-site are already VAT-inclusive — but if your JSON-LD outputs a raw price without valueAddedTaxIncluded: true, AI agents and comparison engines may show the price without the VAT signal, making cross-border comparison inaccurate.

The valueAddedTaxIncluded property on Offer (or PriceSpecification) is a boolean:

• Set true for all EU, UK, AUS, JP, NO, SE, CH market prices
• Set false (or omit) for US, CA prices where tax is calculated at checkout
• Google's Merchant Center validates this field — incorrect values cause product disapprovals in Shopping campaigns

For a EUR price of €55.00 inclusive of 19% German VAT, the pre-tax equivalent is €46.22. AI agents comparing "net prices" across stores will use valueAddedTaxIncluded to normalize correctly — essential for B2B queries where buyers are VAT-registered and care about net pricing.

Common Multi-Currency Schema Mistakes

CatalogScan Multi-Currency Schema Checks

CatalogScan's AI Readiness scan checks your product JSON-LD for multi-currency completeness. The scan flags: missing priceCurrency on any Offer block, numeric price values containing currency symbols, EU/UK Offers missing valueAddedTaxIncluded, and Offers without eligibleRegion on multi-market stores. Stores enabled for Shopify Markets but outputting only a single Offer receive a Markets currency gap warning in the scan report.

Related guides: Shopify schema markup overview · Product availability structured data · International SEO hreflang for Shopify · Payment method schema