Families and variants
Define variants along axes such as colour and size; only the combinations you actually sell are created.
Your product information in one place, right in every channel.
The physical product lives in the warehouse, its commercial content in the catalog, and both point to the same product. Descriptions, images, categories and customs data are entered once and prepared for each channel by its own rules.
What gets easier
What gets easier for your product and content team
Multilingual content and media
Titles, descriptions, images, videos and documents are kept per language; every product has a clear main image.
Category tree and channel mapping
A product can sit in several categories; categories are mapped to each channel's own taxonomy.
Content per channel and market
Set different content, images or price references for a channel or a country without touching the master record.
Publication readiness check
A channel's required fields are checked before publishing; gaps are visible, and each publication's status and history stay on record.
Customs and tax data
HS codes by destination country, origin and tax code live on the product; trade and billing use them.
With the rest of Zagru One
The same record moves on to the next step by itself.
This solution shares its data with the others on the same platform. No files passed between teams, nothing typed in twice.
E-commerce and marketplaces
Channel orders, channel price lists, fast picking and packing, same-day return intake.
Quoting and pricing · CPQ
Quote requests, configuration, contract-based pricing, approval, versions, acceptance and conversion to orders.
Order management · OMS
Orders from every channel in one model: promise, warehouse choice, splitting, backorders and returns.
Industries
Where is it used most?
At e-commerce and retail businesses selling many products across several channels, and at food and pharmaceutical businesses where accurate product and label data matters.
FAQ
Questions you may have
What is the difference between the product record and the catalog?
The product record describes the physical item in the warehouse: barcode, units, dimensions. The catalog holds its commercial side: content, images, categories and channel data. Both point to the same product, so nothing is entered twice.
Can content go through approval before it is published?
Yes. A catalog entry moves through draft, review, approval and publication; who changed what and when stays on record.
How do we bring in our existing product data?
You load products through the CSV import wizard or the API; we map the fields together during onboarding.
Let's look at it with your own operation.
Tell us which solution you want to start with; we'll run the demo around your own use case.
- 30-minute intro with the team that builds the product
- Demo on your own products and flows
- No commitment, no sales pressure
Get a demo with your own data
Leave your details and we'll get back to you shortly.