Distinguish the item from its description.
A product name can change without the underlying item changing. A stable identifier helps a store tool, online channel, or stock record refer to the same item. Decide which identifier is used and how variants are distinguished.
A blue shirt in two sizes needs more than a shared display name. The system should make it possible to select, count, or fulfill the correct version without relying on someone to remember the difference.
Make units and field meanings explicit.
A quantity can refer to individual items, packs, or cases. A price may apply to a particular unit or channel. Define those meanings before information is moved between tools.
Keep an account of which fields are required and who can change them. When a field is unavailable, show that condition instead of filling it with a value that appears authoritative but has no reliable source.
Know where changes begin.
Identify the source responsible for a product’s core details and how corrections reach other systems. Independent edits in several tools can create inconsistent records.
Useful project material includes a small, permitted sample of product records and a list of known inconsistencies. A redacted example is preferable to a full commercial catalog in an initial inquiry. Specific data access and handling should be agreed separately.