Pimberly | In this video
The demo starts where most product data problems begin: information scattered across suppliers, ERP and PLM systems, DAM and CMS platforms, and pricing and translation services. It shows how Pimberly brings all of it into one governed record, using a fashion product split into style, color, and size, with values inheriting up and down the hierarchy.
From there, you’ll see business users configure attributes without code, and photography, video, and 3D files held on the product record with full version history. Suppliers submit data through the Vendor Portal, where validation catches errors before anything reaches Pimberly, and Pimberly AI writes descriptions for different audiences, with every change logged alongside your team’s.
Finally, it shows how lifecycle stages decide when a product is ready to move on, and how each record is checked against a channel’s requirements before it’s published, so problems surface in Pimberly, not on the marketplace.
Keep Watching
How does Pimberly handle product hierarchies?
Your business defines the hierarchy. For example, a fashion product can be split into style, color, and size, with marketing content held at the style level and size held at the sellable SKU. Values inherit up and down the hierarchy, so data is entered once at the right level rather than repeated on every variant.
Do we need developers to set up attributes?
No. Attributes are configured through the Pimberly interface rather than in code. With the right permissions, a business user can set an attribute’s data type, permitted values, and languages, and decide which system is allowed to overwrite each value.
Where are digital assets stored in Pimberly?
Digital assets sit on the same record as the product data they describe. Photography, video, design files, 3D assets, and other file types are held against the product itself, rather than in a separate library with its own naming conventions.
Can we see what changed and roll back to an earlier version?
Yes. Assets carry full version history, so previous versions remain available and can be restored. Every change to a product or an asset records what changed, who changed it, and when.
How do suppliers send us their product data?
Suppliers submit data through the Pimberly Vendor Portal, using templates your business defines. You can also request missing information from suppliers, with notes and due dates, and see what is still outstanding.
How does Pimberly catch errors in supplier data?
Validation rules run as soon as data is entered. Errors surface for the supplier to correct before the data reaches Pimberly, so your team isn’t left fixing problems after the fact.
How do automated feeds work?
Automated feeds map incoming fields to Pimberly attributes. Values can be looked up, cleaned, and normalized on the way in, and a copy of every source file is kept for traceability.
How do we know when a product is ready to publish?
