A SKU, short for stock keeping unit, is the code a business assigns to each distinct thing it sells. One SKU covers one item at one specification: a product in a particular colour, size, flavour or pack format, counted separately from everything else in the catalogue. The code belongs to whoever created it. No standards body issues SKUs, no register validates them, and two companies stocking the identical carton of shampoo will almost certainly label it differently.

That looseness is the point. A SKU answers an operational question: how many units of exactly this thing are in stock, and how fast they move. Because the code is private, it can encode whatever the operator finds useful; because it is granular, it separates variants a shopper would treat as one product. Advertising inherited both properties when catalogues moved online, and the SKU became the object that campaigns target, bid on and report against.

How a SKU is built

There is no format specification. SKUs are typically alphanumeric strings of roughly eight to twelve characters, assembled from segments a warehouse worker can read at a glance. A common pattern places category first, then style, then the distinguishing attribute: TSHIRT-BLU-M and TSHIRT-BLU-L differ only in the final segment, and each is counted separately.

Granularity is set by the operator. A grocer might hold one SKU per pack size of the same cereal, while an apparel retailer holds one per colour and size combination, turning a single style into dozens of codes. The unit of measure is whatever the business needs to count, not what a shopper perceives as a product.

Two rules follow from private ownership. SKUs are not portable: a supplier's code means nothing to a distributor, so trading partners match on external identifiers instead. And SKUs are not barcodes. A barcode encodes a Global Trade Item Number, or GTIN, issued through GS1 in 8, 12, 13 or 14 digit forms. The GTIN travels. The SKU stays home.

Where the SKU enters advertising

The bridge is the product feed. Google Merchant Center requires an ID attribute for every item and recommends using the product SKU as that value. The field takes 1 to 50 characters, Unicode with ASCII recommended, restricted to alphanumerics, underscores and dashes, and maps to the schema.org property Product.sku.

The constraints on that field are stricter than the SKU's own. IDs must be stable, because Google combines the ID with target country and language to retrieve product data and hold performance history; changing it overwrites the product and its record. IDs must not be recycled after a product is discontinued, and casing cannot be used to make two distinct, since abc123 and ABC123 may be read as one product in Google Ads filtering. A single value is expected across countries and languages.

Variants use a second field. A parent SKU shared by a family of items goes in item group ID, and each child takes an ID derived from it. Google's own example lists item group ID 12345 with children 12345-R, 12345-G, 12345-Y and 12345-B for four colours of the same sunglasses, the structure that lets a Shopping campaign bid on one colourway while reporting rolls up to the style.

Other platforms carry the code as a separate attribute rather than as the key. Microsoft Advertising's Product explorer, covered in June 2026, filters a catalogue by fields including product ID, feed label, brand, GTIN, MPN, SKU, product type, condition and custom label. On Amazon the seller SKU sits beneath the catalogue key: one ASIN can carry thousands of seller SKUs, while one SKU maps to exactly one ASIN, and a third code, the FNSKU, ties physical units in a fulfilment centre to a seller account.

Origin and evolution

The concept comes from retail inventory management, not advertising. It hardened into standard practice through the 1960s and 1970s, as self-service formats and widening assortments made recordkeeping by product name unworkable. Automation followed the barcode: the first commercial scan of a Universal Product Code took place on 26 June 1974 at a supermarket in Troy, Ohio. Retailers gained an external number to scan and kept an internal one to plan with, a division of labour that has held since.

Digital feeds moved the code outward. Comparison shopping and later Shopping ads required structured catalogues, and the identifier field in those files became the SKU by default. Google's December 2024 glossary for Merchant Center documented the surrounding vocabulary, including unique product identifiers, manufacturer part numbers and GTINs. Programmatic access shifted again when Merchant API reached general availability in August 2025, with the Content API for Shopping scheduled to shut down on 18 August 2026.

Retail media then made the SKU a measurement object rather than a catalogue key. The IAB and Media Rating Council's Retail Media Measurement Guidelines, published in January 2024, state that SKU-level reporting should be provided at minimum, on the reasoning that most investment goes to promoting specific SKUs. IAB Europe's Commerce Media Measurement Standards, issued for public comment in October 2025, add a rule for sponsored product formats: same SKU attribution should cover the parent SKU, so a click on a shirt credits every size and colour variation. The same document fixes halo attribution as same brand, same category.

Why SKU-level data matters commercially

Closed-loop retail media promises that an exposure can be tied to a purchase of the advertised item. That claim means something only at SKU resolution, since brand-level or category-level sales cannot separate the promoted pack from the rest of a range.

The infrastructure built during 2026 reflects that. Google's Commerce Media Suite, unveiled at Think Week in September 2025 for SKU-level measurement, took on Kroger Precision Marketing on 24 March 2026, attributing sales at SKU level to exposures bought through Display and Video 360. The plumbing splits in two: LiveRamp's RampID resolves identity, while MetaRouter routes conversion events from Kroger systems into the reporting layer. Walmart Connect followed on 11 June 2026, and Walmart Data Ventures had already opened roughly 500 retail data elements including item attributes and omni sales figures through the Scintilla Media Data Feed on 28 April 2026. On the seller side, Amazon's Profit Analytics dashboard, released on 18 September 2025, calculates profitability at SKU, ASIN and parent ASIN level for up to 500,000 listings.

Reporting granularity widened in parallel. The Google Ads API expanded product-level reporting to video, Demand Gen and app campaigns from 15 June 2026, adding cost and conversion metrics where only impressions and clicks had been available, with no historical backfill.

Limitations and disputes

The absence of a standard is the structural weakness. Because SKUs are private, no two retailers describe the same physical item identically, and cross-retailer measurement has to be reconstructed through GTINs, clean rooms or modelling. Research published on 15 June 2026 covering 150,000 campaigns and 350 million dollars of spend across four networks estimated that siloed attribution misses 36% to 53% of campaign impact, rising to 67% to 80% for off-site video. The study is vendor-supplied and the retailers unnamed, a limitation its publisher acknowledges.

Whether SKU-level closed-loop data should displace older methods is contested. A white paper published by the IAB on 7 April 2026, co-authored with Instacart, argued that marketing mix modelling is structurally misaligned with retail media and causes brands to undervalue the channel. Defenders of modelling counter that closed loops see only the retailer's own transactions, the same blind spot the halo research measures.

Feed mechanics create friction of their own. Google's requirement, announced on 6 January 2026 and enforced from March, that merchants use separate product IDs when online and in-store versions differ in price, availability or conditionsplits one physical SKU into two advertising records. Freshness is unreliable too: automatic import, which claims a 24-hour refresh, returned data nine days stale when tested on 13 January 2026.

Distinguishing SKU from adjacent terms

A GTIN is issued through GS1, is globally unique and identifies the manufacturer's item; a SKU is self-assigned and locally meaningful. A UPC is one encoding of a GTIN, not a separate scheme.

An ASIN is Amazon's catalogue key for a detail page shared by all sellers of an item, whereas a seller SKU is private to one account.

A product ID or item ID is the feed field, not the code itself. Google recommends populating it with the SKU, but the two diverge whenever platform rules on stability, recycling or channel splits force another value.

A software SKU is a licence or configuration tier, as used by Google Cloud and Microsoft, sharing only the word.

Recent developments

Feed identifiers kept moving through 2026. Google clarified on 8 April that using the same product IDs across multiple Merchant Center accounts will not trigger duplicate disapprovals, an ambiguity that had troubled merchants running one account per country. In March, the out-of-stock rule tightened, requiring buy buttons to be greyed out rather than hidden.

Generative surfaces now pull on the same fields. Google has flagged eight Merchant Center attributes as primarily intended for conversational experiences, including product relationships declared by GTIN or by the product's own identifier. Microsoft's guidance for Copilot visibility, published in January 2026, directs retailers to keep price, availability, colour, size, SKU, GTIN and modification date synchronised. A beta option added in May 2026 lets Google generate product listings from a website scan without a structured feed, handing identifier assignment to detection algorithms rather than the merchant.

The SKU began as a private counting device and has become the smallest unit against which media is bought, attributed and audited, without ever acquiring the standardisation that role would ordinarily require.

Timeline

  • 26 June 1974: The first commercial Universal Product Code scan takes place at a supermarket in Troy, Ohio, establishing the external product number alongside internal stock codes
  • January 2024: The IAB and Media Rating Council publish Retail Media Measurement Guidelines recommending SKU-level reporting as a minimum
  • 23 December 2024: Google releases a Merchant Center glossary documenting unique product identifiers, MPN and GTIN
  • August 2025: Merchant API reaches general availability, with the Content API for Shopping set to shut down on 18 August 2026
  • 10 September 2025: Google unveils a Commerce Media suite built around SKU-level measurement
  • 18 September 2025: Amazon releases Profit Analytics, calculating profitability at SKU, ASIN and parent ASIN level
  • October 2025: IAB Europe issues Commerce Media Measurement Standards for public comment, defining parent SKU attribution and halo as same brand, same category
  • 6 January 2026: Google announces that separate product IDs will be required from March where online and in-store attributes differ
  • 13 January 2026: Merchant Center automatic import is found returning data nine days out of date
  • 24 March 2026: Kroger Precision Marketing joins Google's Commerce Media Suite with SKU-level sales attribution on YouTube
  • 7 April 2026: The IAB and Instacart publish a white paper arguing marketing mix modelling is misaligned with retail media
  • 8 April 2026: Google confirms that reusing product IDs across Merchant Center accounts is acceptable
  • 28 April 2026: Walmart Data Ventures launches the Scintilla Media Data Feed with roughly 500 retail data elements
  • 11 June 2026: Walmart Connect purchase data reaches Display and Video 360 for YouTube buying
  • 15 June 2026: Google Ads API product reporting expands to video, Demand Gen and app campaigns
  • 18 August 2026: Scheduled shutdown date for the Content API for Shopping

Summary

Who. Retailers, brands and marketplace sellers create SKUs; ad platforms consume them. Google Merchant Center recommends the SKU as the feed ID, Microsoft exposes it as a filterable attribute, and Amazon layers seller SKUs beneath ASINs. The IAB, the Media Rating Council and IAB Europe set the reporting expectations built on them.

What. A stock keeping unit is a self-assigned alphanumeric code identifying one distinct sellable item at one specification. It carries no external authority, no fixed format and no cross-company meaning, which is what separates it from a GTIN.

When. The practice hardened in retail inventory management during the 1960s and 1970s, gained an external counterpart when barcode scanning began in 1974, and became a media measurement unit as retail media matured, formalised by the IAB and MRC guidelines in January 2024 and built into platform integrations through 2026.

Where. SKUs sit in warehouse and point-of-sale systems, in product feeds submitted to Merchant Center and its equivalents, in seller accounts on marketplaces, and in the attribution reports retail media networks return to brands.

Why. Advertising a product range means bidding on and measuring individual items, and only the SKU resolves to that level. The cost of using a private identifier for a public purpose is that it does not travel between retailers, which is why cross-retailer measurement remains modelled rather than observed.