Stock, Terms and Trust: Making UK Product Feeds Legible to AI Shopping Agents

The product feed has long been treated as merchant-centre plumbing: a file that exists to populate shopping surfaces and, when time allows, to be tidied. In 2026 that assumption is increasingly unsafe. AI shopping agents are being asked to compare products, check stock and summarise delivery and returns terms. They do not read a feed as a retailer reads a catalogue; they read it as evidence. A stale availability flag or an ambiguous delivery charge can become a repeated misstatement in an agent's answer, and the commercial cost is not a lost impression but a damaged transaction.

For UK retailers, the practical response is a feed readiness audit. The aim is not to chase every enrichment field. It is to make the commercial facts that an agent needs to repeat — price, stock, delivery, returns and merchant legitimacy — unambiguous, consistent and machine-readable.

Why the feed is now a search surface

Agents compare structured data across merchants. They rely on identifiers, brand, price, availability, shipping terms and returns policy to decide which products to surface and how to describe them. When those fields are missing, agents may infer from page text, exclude the item or, worse, blend contradictory signals. UK-specific ambiguity matters: prices should be clearly inclusive of VAT where that is the customer-facing convention, delivery options should distinguish UK mainland from Highlands and Northern Ireland where costs differ, and returns terms should state who pays return postage. The feed is no longer only an advertising input. It is part of the evidence layer that determines whether a product can be recommended with confidence.

Audit layer one: structured attributes

Begin with identity and variant clarity. Check that GTIN, MPN, brand and condition are present where applicable. Confirm that variant relationships are coherent through item group identifiers, colour, size and material. Titles should be factual rather than keyword-stuffed; descriptions should describe the product, not repeat campaign copy. Category taxonomy should be consistent across the feed and the landing page. Attribute completeness is not cosmetic: it is the difference between an agent treating a product as a known item and treating it as an unknown one.

Audit layer two: availability accuracy

Availability is the highest-risk field because it changes fastest. Compare feed status, product page status and checkout status for a sample of high-demand SKUs. A product marked in stock in the feed but unavailable at checkout is a trust failure. Set a tolerance: zero mismatches for the top quintile of revenue-generating SKUs, near-real-time synchronisation for fast movers, and explicit labels for backorder and preorder. If store collection is offered, keep local availability aligned with the same discipline. UK bank holidays and carrier disruptions should be reflected in the language used, not left to the customer to discover.

Audit layer three: delivery-cost clarity

Delivery is where agents are most likely to summarise and most likely to be wrong. The feed and product page should state delivery cost, estimated minimum and maximum days, geographic restrictions, order cut-off times and carrier where relevant. Free-delivery thresholds should be explicit. Phrases such as 'fast delivery' should be replaced with defined time windows. Where structured shipping details are supported, use them; where they are not, ensure the feed fields and page copy agree. An agent that quotes a delivery promise the checkout cannot honour creates a service problem that search measurement will not explain.

Audit layer four: returns-policy markup

Returns terms are increasingly part of the product answer. Record the return window, who pays return postage, exclusions, condition requirements and refund timing. Where supported, use structured return policy markup with return days, policy category and return shipping fees. Test that the marked-up terms match the written policy and the feed. Agents will repeat what they can parse. Inconsistent returns information generates pre-purchase friction and post-purchase complaints, both of which distort product-level performance data.

Audit layer five: trust signals

Agents and the surfaces that feed them need to know who the merchant is. Keep business identity, contact routes, warranty information and review data current. Review signals should be accurate and attributable; stale or selective ratings are a liability. Trust signals are not a substitute for product data, but they affect whether an agent presents a merchant as a safe recommendation rather than a price-only option.

A prioritised checklist for UK retailers

Treat the audit as a staged remediation programme. Priority zero: price and tax consistency, availability synchronisation and checkout parity for the top 20% of SKUs by revenue. Priority one: identifiers and variant structure, shipping cost and delivery windows, and returns-policy markup. Priority two: images, review data, warranty and business details. Priority three: enrichment copy and campaign-specific fields. Assign an owner and a review cadence. Sample weekly, fix root causes rather than individual rows, and keep a log of recurring feed errors.

Measuring qualified product discovery

Cleaner feeds should improve the quality of product discovery, not simply the volume of clicks. Define qualified discovery in commercial terms: product detail views that lead to add-to-cart, delivery or returns information use, or a completed purchase, with returns-related customer contacts tracked as a counter-metric. Because agent referrals are often opaque, combine sources: landing-page reports, merchant-centre diagnostics, server logs, customer-service tags and consented on-site behaviour. Use matched cohorts where possible: remediate one product group, hold another back, and compare over four to six weeks. Track feed error rates, attribute completeness, availability mismatch rates and policy parseability alongside sessions, conversion and cancellation rates. Expect a lag. The objective is not to flatter a dashboard but to reduce the gap between what an agent says about a product and what the UK retailer can actually deliver.

Conclusion

AI shopping agents raise the cost of ambiguity. A feed that is approximately right is no longer sufficient when an agent is prepared to summarise it to a customer. UK retailers should treat feed readiness as a search strategy issue: prioritise the commercial facts, make them consistent across feed and page, and measure qualified discovery rather than raw traffic. The retailers that do this will be easier to recommend, easier to trust and harder to misrepresent.