01 / Start with the journey
Pick a representative style, order or product group.
Product-data work becomes easier to discuss when it starts with a specific journey: a garment style, an order or another clearly bounded product scope. Identify the buyer question or business goal first, then list the suppliers, facilities, processes and handoffs relevant to that example.
This is not a claim that every factory must use the same data model. It is a way to discover where the chosen product's information is created, maintained and shared today.
02 / Find existing records
Look across the records the teams already use.
Useful information may be distributed across systems, spreadsheets, documents, portals and supplier communications. For the selected scope, ask where the current record is kept and who is responsible for it.
- Product development: specifications, variants, material definitions and BOM information may be recorded in PLM tools or approved files.
- Purchasing and inventory: material masters, purchase orders, receipts and lot references may appear in ERP or inventory workflows.
- Factory operations: production events, consumption and batch connections may be recorded in MES or operational records.
- Suppliers and movement: supplier, logistics and recycling information may sit in SCM tools, partner portals or documents.
- Quality and evidence: compliance records, certificates and test reports may be held in QMS tools or controlled files.
These are discovery examples, not a guarantee that a particular system has a field, captures data at a specific granularity or provides an export.
03 / Map meaning and ownership
Record more than the value.
A value is more reusable when people can understand its meaning and context. For each useful data point, record the source, identifier, owner, review status, last-updated date and any evidence link or known limitation. Note whether information is supplier-declared, checked against a document or independently assured; those statuses are not interchangeable.
Where identifiers do not connect cleanly—for example, style, order, supplier, facility or batch—record the gap rather than silently guessing a match.
04 / Make supplier participation workable
Explain the request before asking for data.
Supplier requests are more useful when they explain which product or order they concern, why the information is needed, who will use it, what format is acceptable and how corrections can be made. Consider existing records before asking suppliers to repeat the same information in a new form.
Agree who owns and may share each item. Keep personal or confidential records out of informal channels, and set data-handling expectations before exchanging detailed files.
05 / Decide the next step
Use the map to scope a modest pilot.
Review the map with product, sourcing, factory, quality/compliance and IT/data owners. Agree which gaps matter for the selected question, what can be tested with available data and what remains outside scope. A readiness score can help frame a discussion, but it is self-reported planning input—not an audit or compliance result.
Explore the PLM, ERP, MES, SCM and QMS examples to see possible sources, or use the DPP readiness check.