The first retail UPC scan was a packet of chewing gum.

The barcode on a package normally identifies the product; it does not need to print the current selling price in its bars. A checkout system reads the identifier and looks up the corresponding item record and price. That separation lets a store change a price in its database without replacing every package’s printed barcode.

The bars and spaces form a machine-readable representation of digits. A scanner detects the pattern and decodes it; checkout software then decides what to do with the result. The scanner is therefore only one part of the system. Product registration, accurate database records, compatible labels, and operational procedures are equally necessary for a useful transaction.

A common product identifier does not usually distinguish every physical package from every other identical package. Two packs of the same product can carry the same UPC. Serialization, batch tracking, and expiration information require additional arrangements when needed. This distinction prevents the misleading assumption that a basic supermarket scan automatically reveals the full history of one individual object.

The grocery industry had to agree on identification and scanning conventions before manufacturers and retailers could invest confidently. A store could not benefit much from a scanner if most suppliers printed incompatible symbols. Conversely, suppliers had little reason to label packages for a system that stores would not use. Shared standards helped resolve that coordination problem.

The 1974 Marsh transaction is widely remembered because the item was ordinary and inexpensive. Its importance came from its place in an operational retail system, not from the gum having special technical properties. GS1’s historical timeline identifies the Wrigley’s pack and the Ohio supermarket as the first scan in this retail barcode history.

Barcode ideas and experiments predated the event. Describing the gum purchase as the first retail UPC scan is more precise than calling it the first barcode ever read. The former is a documented deployment milestone; the latter would incorrectly erase earlier invention, development, and testing. Standards adoption often produces several legitimate “firsts” with different boundaries.

Once a sale is linked to a product identifier, the same event can support inventory updates, sales analysis, and replenishment. Those benefits arise from the surrounding information system, not from the bars alone. If a database associates the identifier with the wrong item, a perfectly successful optical scan can still produce a wrong description or price.

The basic architecture also explains why a barcode is not proof of authenticity. Copying a valid symbol can copy the identifier without copying the genuine product or its authorized origin. Other controls are required where counterfeiting, traceability, or regulated supply chains matter. A scan provides a reliable way to input an encoded number, but verification depends on what the system checks afterward.

The gum scan was a checkout milestone because identification, standardized numbering, and store equipment worked together. The printed barcode was only one part of that arrangement. QR codes later illustrate another setting for optical identification, but neither format should be mistaken for a complete database or an independent source of product information.