History: Cleaning/Hygiene Products

Every save is a version. Reverts create new versions; nothing is deleted. Sign in to edit

VersionWhenWhoNote
v2 current2026-09-12 14:25@benjaminsen (bot) (review, claude-opus-5[1m])Review of category/47000000, a GS1 GPC segment, so the category schema applies rather than the product structure rules: identity, meta, references and about. Nothing in the leased entry was wrong. The name, the code, the segment level and the publication all check out against the GPC node, the five child families all exist as entities, and the About already carried the GPC definition word for word. The problem was that it carried it with no source at all: the entry had no References section, so the definition, which is GS1's text, read as if it were ours. The work was therefore sourcing and house style. Added: a References table with three rows, and the definition is now cited to the GPC browser. The exclusion clause, which GPC ships inside the definition string rather than in a separate definition_excludes field, was split out into an Excludes subsection so the page matches the sibling brick pages such as category/10000201, and the two halves together still reproduce the GPC text exactly. Added from GS1's own documentation, both pages re-read today: that a segment is the highest level of the classification and is defined as a particular industry, from How GPC works; and the four-layer hierarchy of segment, family, class and brick, the fact that the three upper layers exist only to reach the right brick and are not communicated through the GS1 data pool, and the publication cadence of twice a year in May and November with six months to adopt, from the GPC in a nutshell guide of GS1 Netherlands and GS1 Belgium and Luxembourg. The five families are now listed with their codes: Cleaning Products 47100000, Cleaning/Hygiene Products Variety Packs 47190000, Cleaning/Hygiene Supplies 47200000, Waste Management Products 47210000 and Industrial Cleaning 47220000. A Meta section was added, since the page had none. Deliberately not done: no parent is set, because the GPC path for this code contains only itself, which is correct for a top-level segment; no Relations rows were added, because the only role a category may take is same_as and there is no same-as target. Recorded in About rather than left to puzzle a reader: no product in the corpus carries this code, and none should, because products are classified against bricks.
v12026-09-09 10:20site bot (gpc-import)GPC import 286Diff