The SKU key code defines the unique internal identifier for any distinct, separately stockable and separately sellable unit within an hri07e‑compliant project. It provides a stable, deterministic tag used across Data Sheets, CDIDs, BOMs, routings, and logistics automation.
SKUs behave in Data Dictionaries and Data Sheets much as variable names behave in software code. They ensure that “stockable item” means the same thing to all users and systems.
The SKU key code is used wherever a project must reference a specific physical or sellable unit. Examples include:
Inventory control
Warehouse management
Replenishment and forecasting
BOM and routing linkage
CDID mapping
MakeAltQ SKU opportunity generation
SKUs are intended to support automated calculation and cross‑system consistency.
A SKU must be used whenever a unit is distinct for stocking, selling, picking, receiving, reporting, or forecasting.
The SKU definition belongs to ddILS, the Integrated Logistics & Systems Data Dictionary. Organizations should adopt ddILS rather than invent their own SKU definitions.
Projects may extend SKU usage for specialized items, but should avoid redefining the core SKU meaning.
SKU is not derived from external standards (GTIN, UPC, EAN, MPN). It is an internal HRI construct.
ddILS hri07e.doc
dd04 Data Sheet hri07e.doc
dd02 Contract Deliverable Item Description hri07e.doc
<dd:km kc:policy>
<dd:km kc:cdidrefs>
The SIG:ILS DD Authority controls the SKU definition and ensures consistency across all hri07e‑compliant projects.
The SKU definition is owned by Hammond River Institute (HRI) under ddILS.
SKU governance requires continuous maintenance and cross‑SIG coordination.
Improper SKU definition may cause inventory errors, routing failures, or financial misstatements. As with all DD items, misuse can expose authors to liability.
ils
Integrated Logistics & Systems Data Dictionary
ddILS hri07e
Hammond River Institute (HRI) Filename structure: ddILS SKU hri07e.doc
sku
SKU
s = Stock k = Keeping u = Unit
stkunit
Stock Keeping Unit
A SKU is the unique internal identifier for a distinct stockable unit. It is the anchor for inventory, logistics, routing, costing, and CDID cross‑references.
A Stock Keeping Unit (SKU) is a company‑defined identifier used to uniquely represent a stockable item. It is the primary key for:
inventory control
warehouse management
replenishment
forecasting
routing
BOM linkage
CDID mapping
A SKU applies to one and only one distinct unit. If two units can be counted separately, they must have different SKUs.
A SKU is not a GTIN, UPC, EAN, or manufacturer part number.
Governance:
Primary Owner: SIG:ILS
Technical Review: SIG:IE
Portfolio Review: SIG:Biz
Financial Review: SIG:Acc (they may argue, but ownership remains with SIG:ILS)
SKU has no algebraic function. It is a unique identifier, not a calculable quantity.
Constraints:
Must be unique
Must be stable
Must not encode volatile attributes
Must be machine‑readable
SKU derivation is organizational, not mathematical:
SIG:ILS defines naming rules
SIG:Biz defines assortment boundaries
SIG:IE defines manufacturability constraints
MakeAltQ may propose new SKUs
CDID mapping finalizes lifecycle linkage
cdid
mpn
gtin
uom
hs
bomref
routref
binloc
reorder
xml
<ddILS>
<kc id="sku">
<symbol>SKU</symbol>
<label>Stock Keeping Unit</label>
<mnemonic>stkunit</mnemonic>
<title>Stock Keeping Unit</title>
<description>Internal unique identifier for stockable units.</description>
<lifecycle>
<state>proposed</state>
<state>approved</state>
<state>active</state>
<state>suspended</state>
<state>retired</state>
</lifecycle>
</kc>
</ddILS>
SIG:ILS
HRI DD Authority (Section 6.0)
From your attached DD document:
“Key Codes are used within hri07e Data Dictionaries and Data Sheets much as variable names are used in computer software code.” “There will be a designated DD Authority for each Data Dictionary domain…”
Steps to create a new SKU:
Confirm the item is distinct
Assign a stable identifier
Link to CDID
Link to BOM and routing
Validate with SIG:ILS
Approve lifecycle state
r0 — Initial creation
r1 — Lifecycle added
r2 — XML block added
r3 — Reformatted to dd01 structure