In digital advertising a product is a data record, not an object. It is the structured description of a single sellable item that a merchant submits to a platform catalogue, and from which the platform assembles listings, advertisements and, increasingly, conversational answers. The record carries an identifier, a title, a description, a landing page, an image, a price and an availability state. Everything a shopper sees in a Shopping result is drawn from those fields rather than written by an advertiser.

Google's product data specification makes the distinction explicit, and the vocabulary is easy to trip over. A product, in that document, is the thing customers search for. An item is that product once it has been added to product data, which in a text feed means one line. A variant is a specific version of a product, such as one size of a shirt. Three words, three different objects, and most feed problems begin where they are confused.

What the record contains

Seven attributes are required of every entry: id, title, description, link, image link, availability and price. Beyond those, requirements turn conditional. Brand plus either a Global Trade Item Number or a manufacturer part number is expected for manufactured goods, and Google's identifier exists attribute is the declaration a merchant makes when none of those codes applies, a policy documented for Shopping ads and free listings with the warning that setting it to false can limit visibility. Apparel adds colour, size, gender, age group and condition. Categories layer on further obligations, and regulated goods layer on more again.

Records reach a platform in four ways: a delimited text file, an XML document using RSS 2.0 with a dedicated namespace, a linked spreadsheet, or an application programming interface. A fifth route, an automated scan of the merchant's own website, removes the file entirely.

Identity is where the abstraction becomes concrete. Under Google's Merchant API, a product resource is named accounts/{account}/products/{product}, and the second segment is a composite key in the form contentLanguage~feedLabel~offerId. The documented example is en~US~sku123. Legacy local products carry a fourth element at the front. Where an offer identifier contains a slash, a percent sign or a tilde, the segment has to be submitted as an unpadded base64url string instead, and Google recommends that encoding for every identifier rather than only the awkward ones. The predecessor system, the Content API for Shopping, expressed the same idea with colons as channel:contentLanguage:feedLabel:offerId. That interface reached the end of its life on 18 August 2026, a date fixed when the Merchant API reached general availability in August 2025.

Values inside the record are equally specific. Price is submitted in micros alongside an ISO currency code, so 15,990,000 micros represents 15.99 dollars. Availability uses a controlled enumeration. Variants are bound to a parent through an item group identifier, and each variant remains a separate record with its own identifier, its own price and its own approval status. Store-level and region-level inventories attach as child resources keyed by store code or region, which is how a single product can hold different prices in different places without being duplicated.

From record to placement

Every submitted record passes through validation before it can serve. Failures produce warnings or disapprovals, and a disapproval is not campaign-scoped: it removes the product from Shopping advertisements, free listings, conversational surfaces and image experiences simultaneously. Availability is policed against the landing page in both directions. Google's rules tightened in March 2026 around non-functional buy buttons, with feed declarations required to match what the page shows.

Approved records then serve two further roles. They are the unit of bidding, subdivided through listing groups and custom labels rather than through keywords. They are also the unit of reporting. Google expanded product reporting across all campaign types from 15 June 2026, extending cost and conversion metrics beyond Shopping and Performance Max to Video, Demand Gen and App campaigns, and standardising the shopping performance view across campaign types. Merchant Center caught up on 24 August 2026, separating YouTube affiliate traffic from the organic bucket and widening the paid figures, with Google warning of a one-time increase in impressions and clicks.

Above the account sits the Shopping Graph, which Google described at Google Marketing Live in May 2026 as holding more than 60 billion listings with over 2 billion updated hourly. Free listings, Shopping advertisements, AI Mode, Gemini and Lens all draw on the same store.

Origin and evolution

Google launched Froogle in December 2002 as a comparison engine built by Craig Nevill-Manning, indexing vendor pages with a crawler rather than charging for inclusion. The service was renamed Google Product Search on 18 April 2007, and renamed again to Google Shopping on 31 May 2012, when submission became paid. Unpaid distribution returned on 21 April 2020, when Google opened the Shopping tab primarily to free listings through the Surfaces across Google programme, with global expansion following that October. According to Google's announcement, the change let merchants appear regardless of whether they advertised.

The specification itself changes annually. The April 2024 revision introduced structured title and structured description attributes so merchants could disclose text generated by artificial intelligence. The 2025 update landed on 8 April, altering installment pricing, energy efficiency labelling and shipping, including a carrier shipping attribute with sub-attributes for origin postal code, handling time and transit time. The 2026 revision, published on 14 April, raised the minimum image resolution to 500 by 500 pixels and added handling cutoff time, minimum order value, video link and loyalty shipping sub-attributes. Warnings began that day; enforcement starts on 31 January 2027. Two of those attributes, pickup cost and minimum order value, become mandatory for in-store products in the United Kingdom, Switzerland and the European Economic Area on 30 September 2026.

Identity rules moved in parallel. Google required separate product identifiers for online and in-store versions of the same item where price, availability or condition differ, enforced from March 2026, then clarified on 8 April 2026 that reusing identifiers across separate accounts triggers no duplicate disapproval.

Why the record now carries more weight

Attribute depth used to affect one campaign type. It now determines eligibility across surfaces that did not exist three years ago. Google announced dozens of conversational attributes in January 2026, and feed practitioners subsequently identified eight tied explicitly to AI-driven experiences, among them product highlight, product detail, variant option and related product. According to FeedArmy founder Emmanuel Flossie, one client recorded an 80% improvement in Google advertising performance from product data changes alone, without altering bids or creative. That figure is a single practitioner case rather than a platform benchmark.

Microsoft has pushed the same argument. Its Copilot playbook, published in January 2026, told retailers that most of the signals influencing ranking already exist inside their businesses but remain absent from feeds. The company later shipped Product explorer, a catalogue view limited to advertisers with fewer than 100,000 stock-keeping units, a threshold that excludes larger retailers from the tool.

Limitations and disputes

Freshness is the oldest complaint. Merchant Center automatic import claims a 24-hour refresh, yet testing on 13 January 2026 found product data nine days out of date. The artificial intelligence import beta added in May 2026 went further, performing a one-time website scan with no refresh promise and assigning identifiers algorithmically, which breaks the link between feed identifiers and remarketing tags on the merchant's own site.

Visibility on conversational surfaces is contested. Productrise research reported in late July 2026 found AI Mode returning roughly 95% fewer Shopping listings than standard search for identical queries, with only 0.8% of products overlapping between the two surfaces on the same day. A later dataset covering more than 2 million listings found the same products priced 21.6% higher in AI Mode. Google has not published counter-measurement.

Control is the third dispute. Google now optimises images below the new resolution threshold by substituting near-duplicates or upscaling with artificial intelligence, preventing disapproval without merchant action but also editing merchant data. Whether that is a service or an intervention depends on the merchant.

Disambiguation

Product is not a SKU. A stock keeping unit is an internal retailer code and commonly supplies the offer identifier, but the product record is the platform-side entity built around it. Product is not an ASIN either: Amazon's catalogue key identifies a listing within one marketplace and can differ by country for the same item. Product is not product tagging, which is the act of linking a catalogue entry to a piece of creator content.

A separate meaning survives in publisher sales. In IAB Tech Lab's OpenDirect specification, which underpins programmatic guaranteed transactions, Products are entries in a seller's inventory catalogue and Lines reference them. There, a product is packaged advertising space, not merchandise.

Recent developments

Agentic commerce has made the record transactable rather than merely visible. The Universal Commerce Protocol announced in January 2026 converts feed quality into the ability to complete a purchase inside a conversational interface, with Microsoft adding protocol feeds to its own Merchant Center in April 2026. Measurement followed the surfaces: Google introduced AI performance insights on 27 May 2026, reporting share of voice and an attribute completeness score across AI Mode, AI Overviews and the Gemini app in five markets. The record, once a line in a file uploaded for one campaign type, is now the merchant's primary interface to Google.

Timeline

  • December 2002: Google launches Froogle, a comparison engine indexing vendor pages
  • 18 April 2007: Froogle is renamed Google Product Search and integrated with web search results
  • 31 May 2012: The service becomes Google Shopping and moves to paid submission
  • 21 April 2020: Google opens the Shopping tab primarily to free listings through Surfaces across Google
  • October 2020: Free listings expand beyond the United States
  • April 2024: Structured title and structured description attributes are added for AI-generated text disclosure
  • August 2024: The Merchant Center Next rollout completes globally
  • 8 April 2025: The annual specification update revises installment pricing, energy efficiency and shipping attributes
  • 20 August 2025: Merchant API reaches general availability, with the Content API for Shopping scheduled to close
  • January 2026: Dozens of conversational commerce attributes are announced
  • 13 January 2026: Automatic import is documented returning data nine days stale
  • March 2026: Separate product identifiers become mandatory where online and in-store attributes differ
  • 8 April 2026: Google clarifies that identical identifiers across accounts cause no duplicate disapproval
  • 14 April 2026: The 2026 specification update sets a 500 by 500 pixel image minimum and adds four attributes
  • 27 May 2026: AI performance insights arrive in Merchant Center with an attribute completeness score
  • 15 June 2026: Product reporting expands across all Google Ads campaign types
  • 18 August 2026: The Content API for Shopping shuts down
  • 24 August 2026: Merchant Center reporting definitions change for organic and paid product metrics
  • 30 September 2026: Pickup cost and minimum order value become mandatory for in-store products in the UK, Switzerland and the EEA
  • 31 January 2027: Enforcement of the 500 by 500 pixel image requirement begins

Summary

Who. Retailers, brands and marketplace sellers create product records; feed management vendors and agencies maintain them; Google, Microsoft, Amazon and Meta ingest and validate them. Google's product data specification is the de facto standard, and the IAB Tech Lab governs the unrelated publisher-side meaning through OpenDirect.

What. A structured record describing one sellable item, carrying at minimum an identifier, title, description, landing page, image, price and availability, from which platforms build listings, advertisements and conversational answers.

When. The form dates from Froogle in December 2002, hardened into a specification through Merchant Center, and has been revised annually since, most recently on 14 April 2026, with programmatic access moving to the Merchant API after the Content API closed on 18 August 2026.

Where. Inside merchant catalogues such as Google Merchant Center and Microsoft Merchant Center, in the Shopping Graph that Google says holds more than 60 billion listings, and on every surface those catalogues feed: Shopping results, free listings, Performance Max, Demand Gen, AI Mode, Gemini and Lens.

Why. Product advertising cannot be written in advance, because price, availability and assortment change faster than creative can be produced. The record exists so machines can assemble the listing at query time, which makes data completeness a performance variable in its own right and hands platforms substantial influence over how merchandise is described, priced in display and, on conversational surfaces, whether it appears at all.