--- title: "AI Shopping Wrong Price Fixes | GigaCommerce" url: https://gigacommerce.co/insights/agentic-commerce/ai-shopping-wrong-price description: "AI shopping quotes the wrong price when schema, Shopify discounts, and Amazon coupons disagree. Align the offer before peak, then run a free readiness score." lang: en --- Black Friday is Nov 27. Shoppers will ask AI what to buy — is your catalog readable? Check yours free (https://gigacommerce.co/tools/agentic-readiness-score) # When AI Shopping Quotes the Wrong Price AI shopping quotes the wrong price when schema, Shopify discounts, and Amazon coupons disagree. Align the offer before peak, then run a free readiness score. Image: Sujan Bhuiyan (https://gigacommerce.co/_next/image?url=%2Fteam%2Fsujan-bhuiyan.webp&w=96&q=75) Sujan Bhuiyan Founder, GigaCommerce SEP 23, 2026 · UPDATED OCT 22, 2026 · 12 MIN · GUIDE Share on LinkedIn: https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fgigacommerce.co%2Finsights%2Fagentic-commerce%2Fai-shopping-wrong-price Share on X: https://x.com/intent/post?url=https%3A%2F%2Fgigacommerce.co%2Finsights%2Fagentic-commerce%2Fai-shopping-wrong-price&text=When%20AI%20Shopping%20Quotes%20the%20Wrong%20Price Ask Match catalog Recommend Pay in chat Order A stroller that fits a small trunk? Agentic commerce Discovery to paid, inside one chat Short answer AI shopping quotes one price. The number it should cite is the amount a shopper pays right now, in the currency on the page, with any public sale already applied. - Shopify compare-at, automatic checkout discounts, Amazon coupons, and Offer schema often describe four different amounts. Assistants and Google Merchant Center treat a mismatch as a bad fact. - Google uses Offer.price when both Offer.price and priceSpecification claim the active price. Put the live selling price in Offer.price, and the crossed-out reference in a strikethrough price specification. - A same-week drill on your top 25 revenue SKUs — PDP, schema, checkout, and the Amazon offer — catches the quotes that create refunds and disapprovals before peak traffic. AI shopping quotes the wrong price when the amount on the product page, the amount in structured data, the amount at checkout, and the amount on Amazon are four different numbers. The quote an assistant should give is the price a shopper pays right now: the live selling price, in the currency shown on the page, with any public sale already applied. A compare-at figure, a coupon that still needs a clip, or a “was” line in a bullet is context. It is a second fact, and it has to be labeled as one. This briefing is for Shopify and Amazon operators in the $100K–$10M range heading into peak. It names the four prices that drift apart, walks a worked offer, and gives a same-week drill so assistants stop citing a number your checkout will not charge. ## Why assistants cite a single number A shopper can see $64 crossed out, $48 in bold, and a 15% banner, and still do the math. An assistant recommending the product has to say one number. If your data offers four candidates, it picks the first figure in the description, the schema `price`, or a cached sale from last month. The shopper arrives expecting that figure. Checkout shows another. The gap shows up where you already spend money. A Brand Agent that states compare-at as the current price creates a ticket the moment the cart loads. The first 30 days after launch (https://gigacommerce.co/insights/agentic-commerce/first-30-days-after-brand-agent-launch) are the cheapest window to catch that. On Amazon, a detail page can show a current price, a list price, a coupon, and a Subscribe & Save price together, and a bullet that says “was $64” hands any reader a second number with no label. On Google, Merchant Center’s “Mismatched product price” article says a disagreement between the `price` in your product data and the price on the landing page can disapprove the item. Structured data has to match the price the user sees, and a sale the user would actually pay belongs in that markup. A check that only asks whether `Product` schema exists will miss this. The agentic commerce readiness checklist (https://gigacommerce.co/insights/agentic-commerce/agentic-commerce-readiness-checklist) already flags live price and availability. This post is the price half of that check, written so a team can run it. ## The four prices that usually disagree Pick one hero SKU and write down every price a machine could read. Mid-market brands usually find four. ### Shopify selling price versus compare-at Shopify stores a variant’s selling price in cents. Themes that follow the Dawn pattern emit `Offer.price` as that value divided by 100, along with `priceCurrency` from the shop currency and an availability URL such as `https://schema.org/InStock`. That selling price is the number the assistant should quote for a one-time purchase at the price currently on the variant. Compare-at (`compare_at_price`) is the crossed-out reference. It belongs beside the selling price, labeled as a reference, when you have a real prior price to show. It does not belong in `Offer.price`. Google’s product-snippet documentation states a tie-break you can test: if you put an active price in both `offers.price` and `offers.priceSpecification`, Google uses `offers.price` and ignores the specification. So the safe pattern is: - `Offer.price` and `Offer.priceCurrency` = the live selling price. - A `UnitPriceSpecification` with `priceType` set to `https://schema.org/StrikethroughPrice` = the compare-at amount, and only when that amount is a real reference price you are allowed to show. `highPrice` and `lowPrice` describe an `AggregateOffer` range across variants. They do not encode “was $64, now $48” on one variant. `priceValidUntil` belongs only on a price that actually ends. A fake expiry makes assistants drop a live price, or keep a promotional price after the promotion ended. ### Checkout discounts the schema never sees Automatic discounts and some discount codes apply in the cart, after the product JSON-LD has already been rendered. The PDP can say $48 in HTML and in schema while checkout charges $40.80 because a 15% automatic discount fired. Google’s `price` rules require the submitted amount and currency to match the landing page and checkout. For an advertised sale, show both the non-sale price and the sale price on the landing page, charge the sale price at checkout, and keep it consistent through checkout. An advertised coupon has to be available to users generally, with both prices visible once it is applied. Two practical rules keep the Brand Agent and the feed honest: 1. 01 If every shopper gets the discount with no code, the price on the PDP, in `Offer.price`, and in the feed should already be the discounted amount — or the PDP must show both numbers with the sale as the current price. 2. 02 If the discount is a code for a segment (welcome, SMS, VIP), the public price stays the variant price. The agent may mention the code only when your policy says that code is public. A code buried in a popup is a poor fact for an assistant to promise to a stranger. Copilot Checkout and any other agent-mediated purchase will charge whatever Shopify calculates. If you have not tested the discounted path, read the edge-case section of the Copilot Checkout configuration guide (https://gigacommerce.co/insights/agentic-commerce/copilot-checkout-configuration-guide) before you let an assistant promise a price. ### Amazon price, coupon, and Subscribe & Save Amazon’s detail page is allowed to show more than one figure. The current price is what a one-time buyer pays before a coupon. A list price, when Amazon displays it, is a reference and has to meet Amazon’s list-price rules — a recent price you charged or another substantiated reference, not a number invented for a strikethrough. A coupon changes the price only after the shopper clips it. Subscribe & Save shows a lower recurring price that a one-time buyer does not pay. Quote the current price for “what does it cost?”, the clipped amount only when the shopper asks about the coupon, and Subscribe & Save only for a subscription. A bullet that says “was $64” with no date gets repeated as the offer. Coupon depth also changes weekly in peak. The person who owns the Amazon offer for a SKU should be able to see the Shopify price the same day, so a marketplace promo does not become the number your site agent cites for the DTC SKU. Amazon marketplace operations (https://gigacommerce.co/amazon) is where listing price, coupons, and list-price compliance get fixed. The Shopify agent still needs an explicit line when the channels differ: “DTC price is $48. The Amazon offer is priced separately and may include a coupon.” ### Feed price versus the page a crawler actually receives Merchant Center can update price from your landing-page markup when automatic item updates are on, and it can disapprove the item when the feed and the page disagree. For the match to work, Google’s structured-data setup for Merchant Center requires the markup in the HTML returned by the server. Markup injected only after JavaScript runs is invisible to that crawl. The price in that HTML must use a period as the decimal separator (`48.00`, not `48,00`). Merchant Center’s setup notes also say landing-page price must not change based on user information such as IP address if you want markup to match product data. A theme that swaps currency in the browser after load, while the first HTML response contains a different amount, breaks that match. Several currencies means several `Offer` objects, each with its own `priceCurrency`. On a URL with multiple variants, each offer needs a SKU or GTIN that matches the feed, or neither Google nor an assistant can tell which price belongs to which unit. $40.80 Checkout price in the worked example after a public 15% discount on a $48 Shopify variant. Compare-at still reads $64. Schema that only emits the variant price still reads $48. Amazon at $49.99 with a 20% clip lands at $39.99. Illustrative offer for an audit drill. Arithmetic you can reproduce. Not a client result. ## What a mismatched quote does to the sale Take that hero SKU and put the four numbers in one row. Say the product is a mid-weight hoodie, one colorway, sold on Shopify and on Amazon — a hypothetical offer for the drill, not a client's. | Surface | Amount | What it actually is | | --- | --- | --- | | Shopify compare-at | $64.00 | Reference price, crossed out on the PDP | | Shopify variant price | $48.00 | Live one-time price before the automatic discount | | Checkout after 15% automatic | $40.80 | Amount charged if the discount applies to everyone | | `Offer.price` in the theme JSON-LD | $48.00 | What many themes emit from `variant.price` | | Amazon current price | $49.99 | One-time marketplace price | | Amazon after a 20% coupon clip | $39.99 | Conditional price, only after clip | Six prices a machine can read for one hypothetical hoodie. Asked “how much is this hoodie?”, an assistant can answer any of those six figures. For a shopper who lands on the DTC page and gets the public 15% discount, the citable price is $40.80. Label $48 as the pre-discount variant price and $64 as the older reference, or leave them out of the quote. A cart that disagrees with the cited price bounces or refunds, and Merchant Center can drop the Shopping row for the same mismatch. Track it beside agent-referred revenue. The agentic commerce ROI (https://gigacommerce.co/insights/agentic-commerce/measuring-agentic-commerce-roi) piece already separates those sessions. Add PDPs whose schema price differs from the cart by more than a rounding cent. That backlog does not show up inside ACoS. A “was” price with no history Compare-at on Shopify and list price on Amazon both claim a real higher price. If you cannot point at that prior price, remove the strikethrough. ## A same-week price-truth drill Run this on the 25 SKUs with the most revenue in the last 90 days, plus any SKU in a live promotion. The same Liquid runs on every product, so this sample exposes a theme-level schema bug. 1. 01 Export the live selling price From Shopify, export variant price, compare-at price, and SKU for the 25. Note which discounts are automatic and which need a code. Calculate the checkout amount for the automatic case (a 15% discount on $48.00 is $40.80, not “about $41”). 2. 02 Read the HTML, not the app preview View source on the PDP, or use Google’s Rich Results Test, and find `Offer.price`, `priceCurrency`, and any `priceSpecification`. Confirm the markup is in the server HTML. Confirm `Offer.price` equals the amount you want quoted, using a period as the decimal separator. 3. 03 Add the reference price only as strikethrough If compare-at is real, encode it as a strikethrough price specification. Leave `Offer.price` on the live amount. Delete `priceValidUntil` unless the sale has a calendar end. 4. 04 Place the same order the assistant would Add the variant to cart in a clean browser. Confirm the charged price matches the number you decided is public. If a code is required, confirm the PDP does not promise that code in schema or in the first paragraph. 5. 05 Reconcile Amazon on the same row For each SKU with an ASIN, record current price, list price, coupon, and Subscribe & Save. Write one sentence your Brand Agent is allowed to say about the Amazon price. If the channels differ on purpose, that sentence should say they differ. 6. 06 Fix the feed the same day Update Merchant Center `price` and, when you are in a real sale, `sale_price` plus the effective dates, so the feed matches the landing page and checkout. Recheck the variant identifier (SKU or GTIN) on multi-variant URLs. The output is a sheet with one public price per SKU, the schema snippet that states it, and a yes/no on whether checkout matches. Keep conflicting SKUs out of peak creative. If every row shows the theme emitting variant price and never a strikethrough specification, fix that once in Liquid. Check compare-at values per SKU, because a vanity anchor is a content error, not a theme error. ## Publish one price an assistant may cite Put the decided price in the five places that get quoted. - **Product page.** The current price is the primary figure. Compare-at is secondary and crossed out. A public automatic discount is already inside the current price, or both numbers are on the page with the lower one marked as the price now. - **JSON-LD.** `Offer.price` is that current amount. `priceCurrency` is the ISO code (`USD`). Strikethrough lives in `priceSpecification`. One offer per variant when prices differ, each with a SKU or GTIN. - **Agent source.** Paste a short rule: “Quote `Offer.price` for the selected variant. Mention compare-at only as a reference price. Mention a code only if it is in the public offers metafield. Say that Amazon is priced separately when the SKU has an ASIN.” That rule is part of Agentic Commerce Setup (https://gigacommerce.co/agentic-commerce-setup): the agent stays as current as the offer data you maintain. - **Amazon.** Update the current price, the coupon, and any list price together with the bullets. Remove “was” claims that do not match the list price on the detail page. - **Feed.** For a timed sale, `price` is the non-sale amount, `sale_price` is the current amount, and the landing page shows both. With no separate sale, `price` matches the page and the checkout. Recheck a SKU the day its price, discount, coupon, or end date changes, and pass the full 25 weekly through peak. A `priceValidUntil` of 30 November that nobody extends makes a careful agent drop a price that is still correct. A missing end date leaves November’s deal quotable in January. Attribute work answers “what is it?” This drill answers “what do I pay?” Grade the markup an assistant reads The free Product Schema Grader: paste a product URL and see which fields agents read — like `Offer.price`, currency and availability — are missing. It is the fastest way to start the schema half of this drill. Grade a product page (https://gigacommerce.co/tools/product-schema-grader) ## FAQ ### Should Offer.price be the amount before or after an automatic discount? Use the amount the shopper pays when the discount applies to everyone and needs no private code. A 15% automatic discount that takes $48.00 to $40.80 means $40.80 is the price the landing page, schema, and feed should share, with $48.00 labeled as the pre-discount figure if you show both. When the lower price needs a code that is not offered to all users, keep `Offer.price` at $48.00 and keep $40.80 out of the agent’s promise. ### Can I put compare-at price in Offer.price to show a bigger discount? Keep compare-at out of `Offer.price`. That field is the current offer. Google’s product-snippet docs use `offers.price` as the active price when both `offers.price` and `priceSpecification` are present. Put the live amount in `Offer.price` and a genuine compare-at in a strikethrough price specification. Inflated compare-at values also conflict with platform rules on reference prices. ### What if my Shopify price and my Amazon price are supposed to be different? Keep them different, and label them. The DTC agent quotes the Shopify public price. It describes Amazon as a separate offer — current price, coupon, Subscribe & Save — only from source content your team updates with the listing. One unlabeled number in a bullet gets quoted for both channels. ### How often should we recheck price truth during peak? Recheck a SKU the day its price, compare-at, automatic discount, coupon, or sale end date changes, and pass the top 25 weekly through peak. A Sunday end date still sits in schema on Monday if nobody owns `priceValidUntil` and the feed’s sale window. A weekly pass is a few hours. A week of expired quotes costs more in refunds and disapprovals. ### Will correct schema stop an assistant from quoting an old price? Current schema fixes what a fresh fetch can see. Assistants and search systems also cache, so an updated page, a real `priceValidUntil`, an updated feed, and copy that has dropped the old amount give the next fetch one consistent story. Align the page, the markup, the checkout, and the Amazon offer so that next citation has a single defensible number. ## Sources 1. 1. Product snippet (Product, Review, Offer) structured data (https://developers.google.com/search/docs/appearance/structured-data/product-snippet) · Google Search Central Required and recommended Offer price properties 2. 2. StrikethroughPrice (https://schema.org/StrikethroughPrice) · schema.org Marking a former price so it isn't read as the current one Free tool ## Grade your product schema Paste a product URL. See which of the fields AI agents read are missing, wrong or unreadable. Grade a product page (https://gigacommerce.co/tools/product-schema-grader) Free template Agentic Commerce Readiness Checklist 27 checks with a verification method for each, so you can audit your own store without taking anyone's word for it. Get the CSV (https://gigacommerce.co/templates/agentic-readiness-checklist) Image: Sujan Bhuiyan (https://gigacommerce.co/_next/image?url=%2Fteam%2Fsujan-bhuiyan.webp&w=256&q=75) Sujan Bhuiyan Founder, GigaCommerce Founder of GigaCommerce, part of Gigaverse. Works with mid-market Shopify and Amazon merchants on agentic commerce installs, AI-ready catalogs, and Commerce GEO. LinkedIn (https://www.linkedin.com/in/sujanbhuiyan) Cite this article Bhuiyan, S. (2026, Sep 23). When AI Shopping Quotes the Wrong Price. GigaCommerce Insights. gigacommerce.co/insights/agentic-commerce/ai-shopping-wrong-price ## Keep reading in Agentic Commerce All Agentic Commerce (https://gigacommerce.co/insights/agentic-commerce) PLAYBOOK · 12 min The First 30 Days After Your Agent Goes Live GigaCommerce Team · Jun 29, 2026: https://gigacommerce.co/insights/agentic-commerce/first-30-days-after-brand-agent-launch PLAYBOOK · 10 min The Agentic Commerce Readiness Checklist GigaCommerce Team · Jun 18, 2026: https://gigacommerce.co/insights/agentic-commerce/agentic-commerce-readiness-checklist PLAYBOOK · 12 min How to Measure Agentic Commerce ROI Sujan Bhuiyan · Jun 21, 2026: https://gigacommerce.co/insights/agentic-commerce/measuring-agentic-commerce-roi The operator's brief · weekly ## One email a week. What shipped, and what to do about it. No spam. Unsubscribe in one click. ## Structured data ```json [ [ { "@context": "https://schema.org", "@type": [ "Article", "BlogPosting" ], "headline": "When AI Shopping Quotes the Wrong Price", "description": "AI shopping quotes the wrong price when schema, Shopify discounts, and Amazon coupons disagree. Align the offer before peak, then run a free readiness score.", "url": "https://gigacommerce.co/insights/agentic-commerce/ai-shopping-wrong-price", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://gigacommerce.co/insights/agentic-commerce/ai-shopping-wrong-price" }, "image": "https://gigacommerce.co/insights/agentic-commerce/ai-shopping-wrong-price/opengraph-image", "datePublished": "2026-09-23", "dateModified": "2026-10-22", "wordCount": 2785, "timeRequired": "PT12M", "articleSection": "Agentic Commerce on Shopify", "keywords": "AI shopping, pricing, offer schema, Shopify, Amazon", "author": { "@type": "Person", "@id": "https://gigacommerce.co/about#sujan-bhuiyan", "name": "Sujan Bhuiyan", "jobTitle": "Founder, GigaCommerce", "url": "https://gigacommerce.co/about", "sameAs": [ "https://www.linkedin.com/in/sujanbhuiyan" ], "worksFor": { "@id": "https://gigacommerce.co/#organization" } }, "publisher": { "@id": "https://gigacommerce.co/#organization" }, "articleBody": "AI shopping quotes the wrong price when the amount on the product page, the amount in structured data, the amount at checkout, and the amount on Amazon are four different numbers. The quote an assistant should give is the price a shopper pays right now: the live selling price, in the currency shown on the page, with any public sale already applied. A compare-at figure, a coupon that still needs a clip, or a “was” line in a bullet is context. It is a second fact, and it has to be labeled as one.\n\nThis briefing is for Shopify and Amazon operators in the $100K–$10M range heading into peak. It names the four prices that drift apart, walks a worked offer, and gives a same-week drill so assistants stop citing a number your checkout will not charge.\n\nThe citable price is what the shopper pays today, in the currency on the page, after any public sale. Compare-at, clipped coupons, Subscribe & Save, and checkout-only discounts are separate facts. Label them. Do not let them overwrite Offer.price. Google Merchant Center can disapprove an item when the feed price and the landing-page price disagree. Schema has to match the price the user sees. Audit the top 25 revenue SKUs on PDP, JSON-LD, checkout, and the Amazon offer before you scale peak promotions.\n\nWhy assistants cite a single number\n\nA shopper can see $64 crossed out, $48 in bold, and a 15% banner, and still do the math. An assistant recommending the product has to say one number. If your data offers four candidates, it picks the first figure in the description, the schema price, or a cached sale from last month. The shopper arrives expecting that figure. Checkout shows another.\n\nThe gap shows up where you already spend money. A Brand Agent that states compare-at as the current price creates a ticket the moment the cart loads. The first 30 days after launch are the cheapest window to catch that. On Amazon, a detail page can show a current price, a list price, a coupon, and a Subscribe & Save price together, and a bullet that says “was $64” hands any reader a second number with no label. On Google, Merchant Center’s “Mismatched product price” article says a disagreement between the price in your product data and the price on the landing page can disapprove the item. Structured data has to match the price the user sees, and a sale the user would actually pay belongs in that markup.\n\nA check that only asks whether Product schema exists will miss this. The agentic commerce readiness checklist already flags live price and availability. This post is the price half of that check, written so a team can run it.\n\nThe four prices that usually disagree\n\nPick one hero SKU and write down every price a machine could read. Mid-market brands usually find four.\n\nShopify selling price versus compare-at\n\nShopify stores a variant’s selling price in cents. Themes that follow the Dawn pattern emit Offer.price as that value divided by 100, along with priceCurrency from the shop currency and an availability URL such as https://schema.org/InStock. That selling price is the number the assistant should quote for a one-time purchase at the price currently on the variant.\n\nCompare-at (compare_at_price) is the crossed-out reference. It belongs beside the selling price, labeled as a reference, when you have a real prior price to show. It does not belong in Offer.price.\n\nGoogle’s product-snippet documentation states a tie-break you can test: if you put an active price in both offers.price and offers.priceSpecification, Google uses offers.price and ignores the specification. So the safe pattern is:\n\nOffer.price and Offer.priceCurrency = the live selling price. A UnitPriceSpecification with priceType set to https://schema.org/StrikethroughPrice = the compare-at amount, and only when that amount is a real reference price you are allowed to show.\n\nhighPrice and lowPrice describe an AggregateOffer range across variants. They do not encode “was $64, now $48” on one variant. priceValidUntil belongs only on a price that actually ends. A fake expiry makes assistants drop a live price, or keep a promotional price after the promotion ended.\n\nCheckout discounts the schema never sees\n\nAutomatic discounts and some discount codes apply in the cart, after the product JSON-LD has already been rendered. The PDP can say $48 in HTML and in schema while checkout charges $40.80 because a 15% automatic discount fired.\n\nGoogle’s price rules require the submitted amount and currency to match the landing page and checkout. For an advertised sale, show both the non-sale price and the sale price on the landing page, charge the sale price at checkout, and keep it consistent through checkout. An advertised coupon has to be available to users generally, with both prices visible once it is applied.\n\nTwo practical rules keep the Brand Agent and the feed honest:\n\nIf every shopper gets the discount with no code, the price on the PDP, in Offer.price, and in the feed should already be the discounted amount — or the PDP must show b", "citation": [ { "@type": "CreativeWork", "name": "Product snippet (Product, Review, Offer) structured data", "url": "https://developers.google.com/search/docs/appearance/structured-data/product-snippet", "publisher": { "@type": "Organization", "name": "Google Search Central" } }, { "@type": "CreativeWork", "name": "StrikethroughPrice", "url": "https://schema.org/StrikethroughPrice", "publisher": { "@type": "Organization", "name": "schema.org" } } ] }, { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://gigacommerce.co" }, { "@type": "ListItem", "position": 2, "name": "Insights", "item": "https://gigacommerce.co/insights" }, { "@type": "ListItem", "position": 3, "name": "Agentic Commerce", "item": "https://gigacommerce.co/insights/agentic-commerce" }, { "@type": "ListItem", "position": 4, "name": "When AI Shopping Quotes the Wrong Price", "item": "https://gigacommerce.co/insights/agentic-commerce/ai-shopping-wrong-price" } ] }, { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Should Offer.price be the amount before or after an automatic discount?", "acceptedAnswer": { "@type": "Answer", "text": "Use the amount the shopper pays when the discount applies to everyone and needs no private code. A 15% automatic discount that takes $48.00 to $40.80 means $40.80 is the price the landing page, schema, and feed should share, with $48.00 labeled as the pre-discount figure if you show both. When the lower price needs a code that is not offered to all users, keep Offer.price at $48.00 and keep $40.80 out of the agent’s promise." } }, { "@type": "Question", "name": "Can I put compare-at price in Offer.price to show a bigger discount?", "acceptedAnswer": { "@type": "Answer", "text": "Keep compare-at out of Offer.price. That field is the current offer. Google’s product-snippet docs use offers.price as the active price when both offers.price and priceSpecification are present. Put the live amount in Offer.price and a genuine compare-at in a strikethrough price specification. Inflated compare-at values also conflict with platform rules on reference prices." } }, { "@type": "Question", "name": "What if my Shopify price and my Amazon price are supposed to be different?", "acceptedAnswer": { "@type": "Answer", "text": "Keep them different, and label them. The DTC agent quotes the Shopify public price. It describes Amazon as a separate offer — current price, coupon, Subscribe & Save — only from source content your team updates with the listing. One unlabeled number in a bullet gets quoted for both channels." } }, { "@type": "Question", "name": "How often should we recheck price truth during peak?", "acceptedAnswer": { "@type": "Answer", "text": "Recheck a SKU the day its price, compare-at, automatic discount, coupon, or sale end date changes, and pass the top 25 weekly through peak. A Sunday end date still sits in schema on Monday if nobody owns priceValidUntil and the feed’s sale window. A weekly pass is a few hours. A week of expired quotes costs more in refunds and disapprovals." } }, { "@type": "Question", "name": "Will correct schema stop an assistant from quoting an old price?", "acceptedAnswer": { "@type": "Answer", "text": "Current schema fixes what a fresh fetch can see. Assistants and search systems also cache, so an updated page, a real priceValidUntil, an updated feed, and copy that has dropped the old amount give the next fetch one consistent story. Align the page, the markup, the checkout, and the Amazon offer so that next citation has a single defensible number." } } ] } ], [ { "@context": "https://schema.org", "@type": "Organization", "@id": "https://gigacommerce.co/#organization", "name": "GigaCommerce", "legalName": "Gigaverse Global LLC", "url": "https://gigacommerce.co", "logo": { "@type": "ImageObject", "url": "https://gigacommerce.co/brand/gigacommerce-dark-logo-mark.svg" }, "address": { "@type": "PostalAddress", "addressLocality": "Sheridan", "addressRegion": "WY", "addressCountry": "US" }, "description": "We set up agentic storefronts, Microsoft Brand Agents, Copilot Checkout and AI-ready catalogs for mid-market merchants. Fixed scope, live in two weeks. Free Agentic Commerce Readiness Score.", "email": "hello@gigacommerce.co", "foundingDate": "2024", "founder": { "@type": "Person", "@id": "https://gigacommerce.co/about#sujan-bhuiyan", "name": "Sujan Bhuiyan", "jobTitle": "Founder, GigaCommerce", "url": "https://gigacommerce.co/about", "sameAs": [ "https://www.linkedin.com/in/sujanbhuiyan" ], "worksFor": { "@id": "https://gigacommerce.co/#organization" } }, "areaServed": [ "US", "GB", "CA", "AU", "EU" ], "parentOrganization": { "@type": "Organization", "name": "Gigaverse" }, "sameAs": [ "https://www.linkedin.com/company/gigacommerce" ] }, { "@context": "https://schema.org", "@type": "WebSite", "@id": "https://gigacommerce.co/#website", "name": "GigaCommerce", "url": "https://gigacommerce.co", "publisher": { "@id": "https://gigacommerce.co/#organization" } } ] ] ```