{
    "id": 1081612,
    "title": "Barcodes, GTINs and SKUs",
    "slug": "product-identifiers",
    "type": "page",
    "url": "https://teas.co.uk/ai/product-identifiers/",
    "modified": "2026-11-20T13:08:54+00:00",
    "excerpt": "A product identifier is a code used to tell one item from another. That matters when two boxes have similar names but different pack sizes, prices or\u2026",
    "content_text": "A product identifier is a code used to tell one item from another. That matters when two boxes have similar names but different pack sizes, prices or ingredients.\nA barcode tells an assistant that the 80-bag box and the 240-bag box are different products, with different prices per cup.\nWhy do the 80-bag and 240-bag boxes of one tea need different barcodes? Because the right picture and the right facts have to stay with the right pack.\nFor a shopper, the important question is simple: does the record describe the exact box I am choosing?\nThe names you may see\nA GTIN is a Global Trade Item Number, used to identify a trade item. The number associated with a familiar retail barcode is often a GTIN. The barcode is the machine-readable symbol carrying information; the identifier is the value it represents.\nAn SKU is a stock-keeping unit, a code a shop uses internally. Different shops can use different SKUs for the same physical product. A GTIN is intended to be the same across retailers.\nWhy pack size matters\nYorkshire Tea Original comes in several sizes. The 80-bag box and the 240-bag box never share one barcode. A wrong quantity means a wrong price per cup. The barcode is what stops the mix-up.\nDo not assume that similar names mean identical ingredients either. A decaf version needs its own accurate record. Pack changes and reformulations need review rather than an automatic copy of older facts.\nDecaf shows the same thing from another side. Tetley Decaf English Breakfast, 40 bags and its 120-bag box are two more products, separate from the caffeinated packs, each with its own barcode and record. In each record caffeine is held as three separate facts: whether the tea has caffeine, whether it is decaffeinated and whether it is naturally caffeine free. They are three different things, so they are never folded into one.\nHow teas.co.uk uses the idea\nThe shop\u2019s public Product Truth API guidance supports exact lookups using several identifiers. That lets software request a particular item and receive its linked facts instead of guessing from a broad search term.\nIn practice, any product on teas.co.uk can be looked up by its barcode, its product code, its name or its address. Software holding nothing but a barcode gets the full record back. That is the same record that sits behind the product page. When I finished my book in November 2026, each record held 81 labelled fields, with the barcode among them so there is no doubt which pack is meant.\nTake Tetley Earl Grey, 50 tea bags, 125g. Its record carries the barcode, the price, the pack weight, the number of bags and the price per cup. It also says whether the tea contains caffeine and how to brew it. The identifier and those facts are also published as labelled data behind the page, so software can read them without guessing.\nA clean product link should open the same item the answer describes. Connecting the right identifier to the right record also supports the wider entity model: facts about one thing should stay attached to that thing.\nAn identifier establishes which item is being discussed. Sources, current stock and the pack itself still determine what can honestly be said about it.\nWhen the question is a photograph\nMore shoppers now search with a phone camera instead of typing. When the photograph shows a box of tea, the most useful thing in it for telling one pack from another is the barcode. Until the exact product is confirmed, the honest answer is \u201cthis looks like X; can you confirm the size?\u201d",
    "contentSignals": "ai-train=yes, search=yes, ai-input=yes",
    "links": {
        "apiCatalog": "https://teas.co.uk/.well-known/api-catalog",
        "llmsTxt": "https://teas.co.uk/llms.txt",
        "mcp": "https://teas.co.uk/mcp",
        "mcpSetupGuides": "https://teas.co.uk/ai/",
        "mcpCard": "https://teas.co.uk/.well-known/mcp/server-card.json",
        "primaryAgenticRouteAuthority": "https://teas.co.uk/.well-known/teas-primary-agentic-route-authority.json"
    }
}