A Practical Guide to Product Information Management
Systems and processes, known as PIM, that store and manage product data centrally, then distribute it to websites, marketplaces and feeds.
Marcus Adeyemi
Why does it matter?
As catalogs and channels grow, keeping product data consistent by hand becomes impossible, and errors multiply across every channel.
What are the numbers?
- Central source one place for product attributes, descriptions and media
- Channels websites, marketplaces, feeds and print
- Data quality completeness and consistency rules
- Identifiers GTINs and SKUs connect data across systems
What should I do?
- Define required attributes per category
- Use one source of truth for product data
- Set data quality checks
- Map attributes to each channel's requirements
- Assign ownership of product data
What should I avoid?
Avoid:
- Editing product data in several places
- Missing attributes that break filters
- Inconsistent units and formats
- No ownership of data quality
When should I get help?
Short answer Bring in help when product data is inconsistent across channels, or when catalogs grow rapidly.
Where this comes from
- GS1 US — Product data standards
- Google Merchant Center Help — Product data specification
The figures and practices above come from the sources listed.
Working on something like this?
We take on E-commerce Development work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
