Skip to content

Shopify Dude Fix

Shopify Markets Price Looks Wrong? Trace Contextual Pricing Adjustments With the 2026-10 Audit Trail

Shopify Admin API 2026-10 exposes a pricing audit trail for contextual variant prices. Trace adjustments without confusing the calculation with market or catalog selection.

Quick answer: On Shopify Admin API 2026-10, query ProductVariant.contextualPricing.auditTrail.priceAdjustments to see the ordered operations behind a variant’s contextual price. It is a much better starting point than guessing whether currency conversion, a price-list adjustment, or rounding changed the number. But the audit trail does not tell you which market, catalog, or price list Shopify selected. You still have to verify the buyer context and its catalog assignments.
On this page

The price can be right for Shopify and wrong for your expectation

A merchant sees one price in the base product record and another when shopping in a different country. An ERP export sees a third. The reflex is to change a fixed price, disable a currency adjustment, or edit the theme. That is premature. Shopify resolves a contextual price from the buyer context and then applies adjustments. A theme can display the resulting number without being responsible for calculating it.

Older troubleshooting threads often send you straight to Settings → Markets → Products and pricing to reset a fixed price. That may have been a useful path for an older Markets setup, but it does not identify the current calculation or distinguish market selection from arithmetic. Modern Markets uses catalogs, inherited customizations, and context-specific pricing. Inspect the resolved result first, then change the source that actually controls it.

What the 2026-10 audit trail gives you

Shopify added auditTrail to ProductVariantContextualPricing on September 17, 2026, for Admin API 2026-10. An app with read_products can retrieve the adjustments in calculation order. Each adjustment has a type, numeric value, the resulting price, and a localized display label. Supported types are ADDITION, MULTIPLICATION, and REPLACEMENT.

The price after each operation is useful evidence. If the sequence contains a replacement, a multiplication, and a later addition, you can see where the number changed without reverse-engineering the final total from storefront HTML. The labels are for people: Shopify explicitly warns that they can be localized or changed. Do not write business rules that match label text.

Query one variant in a specific country

Run this against the 2026-10 GraphQL Admin endpoint. Pass a real ProductVariant GID and a two-letter country code such as FR or CA in the variables. This is read-only.

query VariantPriceAudit($id: ID!, $country: CountryCode!) {
  productVariant(id: $id) {
    id
    sku
    price
    contextualPricing(context: { country: $country }) {
      price { amount currencyCode }
      compareAtPrice { amount currencyCode }
      auditTrail {
        priceAdjustments {
          type
          value
          label
          price { amount currencyCode }
        }
      }
    }
  }
}
{
  "id": "gid://shopify/ProductVariant/123456789",
  "country": "FR"
}

The GID above is a placeholder. For B2B investigations, ContextualPricingContext also accepts companyLocationId. Use the actual purchasing company location when diagnosing catalog prices for a wholesale buyer; a country-only query is not equivalent to a B2B company-location context.

Separate source selection from calculation

This distinction matters more than the new field itself. The audit trail explains the adjustments used to calculate the contextual variant price. Shopify says it does not identify the market, catalog, or price list selected. If your France storefront has the wrong price because the wrong catalog is assigned or a submarket inherits an unexpected setting, a mathematically correct audit trail cannot solve that configuration problem.

  1. Confirm the exact variant and its base shop-currency price. Do not compare two different SKUs or variants.
  2. Confirm the buyer context: country, and where relevant B2B company location. A preview in one country is not proof of another context.
  3. Read contextualPricing.price, compareAtPrice, and the audit trail in one query.
  4. Review the market’s catalog and inherited pricing customizations in Shopify admin. Check whether a fixed price or adjustment is intended for that audience.
  5. Compare the resolved price to a real storefront session in the same market. Check currency, tax display, and whether the page is showing a cached or manually formatted number.

An empty adjustment list is not a clean bill of health

If Shopify cannot return a complete and correct sequence, priceAdjustments is an empty array. That is not proof that no adjustments occurred. Treat an empty list as no complete public audit trail available, and continue with the contextual price, catalog configuration, and storefront checks.

The feature currently applies to product variant contextual pricing, not order line items or draft order line items. It also does not change the values of the existing price and compareAtPrice fields. Do not present the audit trail as an order-level accounting ledger.

How to use it in a pricing integration

A practical diagnostic report should show the variant GID and SKU, the requested context, base price, resolved contextual price, ordered adjustments, and whether the trail is complete. Keep the raw type and value for logic and the label for display only. Record the API version with the report so an older integration that lacks the field is not mistaken for a store with no adjustments.

If the contextual price is correct but the storefront is wrong, investigate theme formatting, market selection, and frontend state. If both the API and storefront are wrong, inspect catalogs and market inheritance. If the order total is different, inspect checkout-specific discounts, taxes, and shipping separately rather than expecting this variant audit to explain them.

Common misunderstanding: “The audit trail tells me exactly which market or price list won.” It does not. It explains how the selected contextual price was adjusted, not why that source was selected. An empty list also does not mean the price was never adjusted.

How to test this

  1. Choose a variant with known country-specific pricing and note its base shop-currency price.
  2. Run the query for the home country and a second active market, using the same variant ID.
  3. Confirm the contextual price and currency for both contexts, and inspect each ordered adjustment.
  4. Repeat using a B2B companyLocationId if the store uses company catalogs; compare the result to the buyer’s company-location session.
  5. Check a variant with no visible audit entries and verify that the UI reports “audit trail unavailable or empty,” not “no price adjustments.”
  6. Compare the result with the actual product page in the same market and then with checkout. Investigate any differences at the correct layer.
  7. Test any app logic in two locales to ensure it never branches on the localized label text.