Product Identity: Getting Item Coding Right Before Passports Arrive

Before any question of carriers or platforms, there is a more basic one: what identifier actually refers to the thing being described? Passport requirements will attach information to a product, and if a factory’s internal codes cannot be mapped unambiguously to what a buyer calls the same item, everything downstream is built on guesswork.

The common failure is not that codes are missing but that they are inconsistent in meaning. A style code may persist across seasons with changed materials. A colour code may differ between the merchandising team and the ERP. A size may be recorded differently in production and in quality records. Each is individually harmless and collectively fatal to a per-style query.

The remedy is to designate one identifier as the reference for external purposes and maintain a mapping to everything else. This does not require re-coding the factory. It requires deciding which code travels outward, ensuring it is unique per sellable item, and keeping a simple cross-reference that someone owns.

It is also worth being realistic about granularity. Buyer requests may arrive at style level, at order level, or at item level depending on who is asking and why. A factory that can answer at style level today and knows precisely what it would take to answer at item level is in a far better position than one that assumed a single level and guessed wrong.

This is unglamorous work with an unusually high return. Product identity is the join every other passport field depends on: composition, suppliers, processing, tests and certificates all attach to something. Get the join wrong and accurate data still produces a wrong answer.