Guides

Your store says in stock. Google says sold out. Which system owns the answer?

Emre Benian
Emre Benian · August 26, 2026 · 5 min read

Drafted and quality-gated by Benian’s own editorial system; every number is verified against the client record it cites. How this site runs: /how-this-site-runs

A buyer finds the right product on Google. The listing says it is in stock. Your store says it is backordered. Which one should they believe?

You can rewrite the product description and still leave that problem untouched. Start by following the value through the systems that publish it: inventory, the store, the feed connector and Merchant Center.

What this has to do with AI shopping

Google describes its shopping experiences as using product data, and its AI Max for Shopping announcement explicitly names the Merchant Center feed as an input. That makes catalog accuracy worth checking. It does not establish that the feed is the only source Google uses, that ad copy never matters, or that a particular missing field guarantees exclusion from an AI answer.

Treat a feed audit as an information-quality job with a measurable result. A repaired stock mismatch is a result. “Optimized for AI” without evidence of what changed is not much to work with.

Trace one product before changing the whole catalog

Here is a hypothetical example. A parts distributor has a six-pack of filters in the warehouse. Its store shows the right quantity, but the feed connector is reading an older export. Merchant Center receives a valid file containing yesterday’s availability.

The file can be processed successfully while the business fact is wrong. The repair depends on the failing step: an export schedule, a field mapping, a connector error or the stock record itself. Updating the title would leave all four possibilities unresolved.

A sample trace for one product; illustrative checks, not observed client results
CheckWhat to compareWho can resolve it
IdentityThe same product and variant ID in every systemCatalog owner
AvailabilityInventory record, product page and received Google dataInventory and connector owners
PriceCurrent offer, currency and product-page priceCommerce owner
Update timeWhen the source changed and when Google received the changeIntegration owner
Failure handlingWhere an unsuccessful or delayed update is reportedNamed operations owner

Fix the facts a buyer needs

Use Google’s product data specification for the required fields and formatting that apply to your products. Check identity, title, price, availability, images and the relevant variant information. Compare the received item with its live landing page, not just the spreadsheet you intended to upload.

Identifiers deserve a separate check. A missing GTIN in an export does not mean none exists. Google’s identifier_exists guidance considers GTIN, MPN and brand. Check the manufacturer’s information and the applicable requirements before changing that field. Never fill a gap with a made-up number.

For titles, ask whether someone can distinguish the item from its adjacent variants. In the filter example, size, rating and pack quantity help a buyer identify the product. That is a practical clarity test, not a claim about Google’s ranking weights.

Make the next update dependable

Choose an update frequency around how quickly your stock and prices change, then measure whether the connector meets it. A weekly update might be inadequate for fast-moving inventory; a daily file can still be wrong immediately after a sale. There is no useful universal schedule without looking at the operation.

For API connections, check the current implementation. Google states that the Content API for Shopping sunset on August 18, 2026. A new proposal should address Merchant API and verify connector compatibility, rather than recommending the retired API from an old tutorial.

Assign one owner to investigate failed updates. The alert should identify the product or batch, the last successful update and the failed step. Preserve the original source value so a troubleshooting attempt does not overwrite good inventory data with an outdated export.

Measure the repair separately from the sales effect

Choose a manageable product group and record the baseline: observed mismatches, update delay and unresolved item issues. Repair the failing steps, then check the same group after subsequent updates. Keep a dated change log so another catalog edit does not get mistaken for your result.

Track exposure, visits, orders and margin separately using the reports available in your account. Google has announced Merchant Center tools for AI search performance; check their actual availability and definitions in your account. When a report cannot isolate a surface, label that limitation rather than assigning all movement to AI Mode.

A before-and-after improvement alone does not establish causation. Price, promotions, seasonality and stock changes can affect sales at the same time. Keep those changes visible when deciding whether a larger integration is worth buying.

The next step

Pick ten important products and trace them through the table above. If the facts already agree and updates arrive reliably, the next investigation may be the offer, demand or product positioning. If they disagree, you have a concrete repair to scope before commissioning more content.

For a broader starting point, the free Opportunity Map gives you three ranked AI and automation opportunities with practical next steps, delivered within two business days. Describe the mismatch, the tools involved and where your team is spending time. It is a starting assessment, not a promise of placement in Google or a full live-account audit.

Emre Benian, Founder of Benian Technologies

Emre Benian

Founder and CEO, Benian

LinkedIn

Emre started Benian in a dorm room at the University of Illinois Urbana-Champaign in May 2025. It took him 300 cold calls to land the first client. He’s an unusual kind of AI builder: he scopes the project, signs the contract, and writes the code that runs after. Based in Chicago. Trained in Industrial Engineering, which he treats as the lens of his practice: getting complex technology to work inside a running business, not in theory.

Want this answered for your business?

Thirty minutes with the engineer who builds these systems. You leave with a first fix and an honest read on whether AI is even the answer.

Read how we do this work: AI Visibility. Not ready for a call? Start with the free Opportunity Map.