Shopify Now Schedules Sale Prices. Will Google and ChatGPT Keep Up?

Shopify can now switch your prices on a timer. The Shopify changelog entry for catalog changes in Rollouts says merchants can schedule product availability and pricing per market, activate or switch between catalogs at a set date and time, run experiments between catalogs on the online store, and launch all of it together with a theme and checkout change. The entry went up in late October, in time for Black Friday planning.

What the entry leaves out matters for a lean catalog team. Your store is not the only place a shopper sees your price. Google Shopping, ChatGPT and Google AI Mode each hold a copy of your catalog, and each copy updates on its own schedule. A price change that lands on your storefront at midnight and in your feeds at 6 a.m. is a six hour price mismatch, on the busiest day of the year.

What Shopify says reaches the channels, and what does not

Shopify's requirements and considerations page for Rollouts is specific. A rollout that publishes catalog changes to 100 percent of visitors updates prices and availability in the online store, and depending on the catalog's markets and sales channels, also in checkout and cart, headless storefronts, Shopify POS and your Google and YouTube product feeds.

The same page sets two limits. First, experiments and rollouts that reach fewer than 100 percent of visitors apply only to the online store. In Shopify's words, "your online store can display different prices or products than Google or other sales channels," and "product ads, listings, feeds, and third-party apps might not display the same offer." Second, when an Event ends or a rollout is paused, "Shopify POS and your product feeds return on their next sync. Until that happens, they can still display the published prices."

So the sync problem exists at both ends of a promotion. On the way in, a partial rollout never reaches the feeds. On the way out, the feeds keep the sale price until their next sync, after the storefront has returned to full price.

One more detail from the catalogs help page: a rollout changes only whether a catalog is active or draft. Any edits you make to the catalog's prices or products while the rollout runs are saved right away and shown to customers. There is no frozen copy to fall back on, so the catalog you schedule is the catalog you must stop editing once the clock is running.

Why a mismatch costs more than a confused shopper

Google treats a gap between the feed and the landing page as a policy issue. Its help page on inaccurate price status from feed and landing page inconsistency lists the first common cause as a sale that "has started or ended but the price in the feed hasn't been updated." The guidance: update the site and the product data at the same time, put the lower price in the sale price attribute, and align the sale price effective date with the website. Mismatches lead to warnings and preemptive disapprovals.

Shopify's own catalogs documentation makes the same point from the other direction: traffic generating channels that send customers to your online store require the catalog's products to match the online store price.

AI answers add a third copy. For Shopify merchants, product data reaches ChatGPT through Shopify Catalog, the route explained in why Shopify products fail to show in ChatGPT. Google AI Mode and Universal Cart read Merchant Center. Neither assistant publishes a refresh interval you can set. If your catalog flips at midnight, assume the answer a shopper gets at 12:05 a.m. still carries the old price. The related checks are in what to check before Universal Cart quotes your price and stock.

The buyer decision: schedule it, but decide what each channel shows

The decision for a Head of Ecommerce is not whether to use Rollouts. Scheduling beats a team member changing prices at midnight. The decision is which channels may disagree with the storefront, for how long, and who checks. Three choices cover most catalogs.

1. Full rollouts for anything a feed carries

Use a 100 percent Launch or Event for every price change on products that are live in Google Shopping, ChatGPT or any other feed. Keep experiments, and anything under 100 percent, for products you are willing to pull from feeds for the test window, or for theme and discount changes that leave the catalog price alone. Experiments need the Grow plan or higher, and the page says scheduling itself is available from Basic.

2. Line up the feed clock with the catalog clock

Open Merchant Center the day before the first change and note the last sync time for the Shopify source. If it syncs on a cadence rather than on change, start the storefront schedule shortly before a sync, or accept a short gap. Put the sale price in the sale price attribute with an effective date that matches the rollout window, so Google can tell a planned sale from a mismatch. Plan the end of the Event the same way, since the feed keeps the sale price until its next sync.

3. Keep the reference price intact

If the catalog switch moves the selling price, make sure compare-at prices move with it, or the sale shows as a plain price change with no markdown context. The settings that decide what agents see are in which Shopify settings let AI agents read your compare-at price. A scheduled catalog that drops compare-at on the way in, or forgets to restore it on the way out, is a common place for this to break.

The check on the day

Pick ten products with the biggest price moves. One hour after the scheduled minute, open each on the storefront and in Google Shopping, then ask ChatGPT and Google AI Mode what it costs. Record the four prices in a sheet. Any row with two different numbers goes to whoever owns the feed. Repeat the same ten at the end of the Event. Twenty minutes of checking, twice, is cheaper than a batch of disapprovals before Cyber Monday.

Keep the rollout analytics in their lane. Shopify measures rollout results on the online store, cart and checkout only, so a lift in that report says nothing about Google Shopping or AI answers during the same window. Compare channel revenue separately.

What to leave for later

Leave per market catalogs alone unless you already sell in more than one country with distinct pricing. Leave experiments between catalogs for January, when a wrong price on a feed costs less. Do not rebuild your feed setup to chase a perfect sync. A short, known gap that someone checks is better than a new integration shipped in November.

How Paz handles this

A Paz expert maps which of your products are live in Google Merchant Center and ChatGPT, reads the catalog and feed timing against your promotion calendar, and flags the products where a scheduled price change will not reach a channel in time. The expert ships the feed and attribute fixes within the guidelines you approve, brings exceptions to you first, and the platform publishes the changes and tracks price and availability issues against your baseline through the holiday window. Talk to us.