Trigger
During new-product setup, channel listing, barcode change, bundle split or supplier substitution, the same product carries different identifiers in PLM, ERP, marketplaces and warehouses.
SCENARIO-DETAIL / LOCALIZED DECISION BRIEF
Product Identity and Cross-system Data Lineage
Business trigger: During new-product setup, channel listing, barcode change, bundle split or supplier substitution, the same product carries different identifiers in PLM, ERP, marketplaces and warehouses.
REFERENCE_ARCHITECTURE · READBACK_VERIFY
DECISION RECORD / C.07
What this route helps you decide
Source-traceable reference · pp.18–19
Goal
Create governed mappings among style or model, SPU, SKU, ASIN or marketplace item, barcode, supplier part number and warehouse code.
Risk / exception
Keep highly similar products without a unique match in human review and never merge them automatically. Do not delete identities with transaction history; retire and map them through versions.
Close condition
Each product has a stable business identity; mappings have versions and effective dates; downstream impact is reviewed; synchronization results and sampling evidence are complete.
Next safe action
Bring a real set of product codes into the comparison and establish the golden identity, field Owners and non-deletion rules.
KNOWLEDGE → COMPARISON → DIRECTION → OPTIMIZATION
Evidence stays attached to the decision.
The full-detail canonical evidence record remains available in Chinese. IDs, Truth classes, boundaries, and source references stay unchanged across languages.
Knowledge
Source-traceable reference
Comparison
Compare the same operating fields before choosing a direction.
Direction
Confirm the owner, authority, human gate, and readback rule.
Optimization
Define a baseline, target, owner, and observation window before claiming impact.