Autocoding
Open-knowledge reference entry
Autocoding refers to software solutions that help manufacturers, particularly those in the food industry, ensure that products have the correct packaging and correct 'sell by' date codes, thereby reducing the number of Emergency Product Withdrawals (EPW). The term was first used during an initiative between Geest PLC (acquired by Bakkavör in 2005 ) and Tesco in 2001.
The key objective of the software was to reduce the number of EPW's associated with date and price coding errors, and pot and lid marriage errors. This still remains the main objective of autocoding software, but functionality has been expanded to encompass quality assurance and OEE performance data.
History
The concept of autocoding originally came from an initiative between Geest PLC and Tesco in 2001, with both parties seeking to reduce the number of emergency product withdrawals associated with packaging and date coding errors. From here, several software engineering companies expanded on this preliminary work to create more reliable and robust systems. In 2004, 2D barcoding was introduced for the first time, a major step forward for the securing of all parts of food packaging.
Prior to this, 1D retail barcodes were used that only offered limited protection as they did not cover all packaging on products. 2D barcodes meant that lids, sleeves, pack could all be identified by a barcode scanner to check that the product is packaged and dated correctly. In 2009, Marks & Spencer introduced a code of practice for the labelling of products that stipulated an autocoding system must be used on every production line.
This brief starts where responsible research should: with the source description of “Autocoding” as open-knowledge reference entry. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as open-knowledge reference entry. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Feb 21, 2026. The linked authority identifier is Q16148068. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2005, 2001, 2004 and 2009.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Autocoding”, its source revision and the description used here.
- Expand the search: follow Autocoding primary sources, Autocoding archive and Autocoding research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Autocoding”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Autocoding” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.