Origo Help
Basic setup
Agree the catalogue model before loading a large number of products.
Last reviewed:
Key concepts and when to use them
A durable setup separates product structure, product facts, navigation, languages, and destinations. Product families define expected facts. Attributes hold those facts. Categories organise discovery. Channels describe use in a destination.
Permissions and preparation
Assign a catalogue owner and include the people who create products, enrich data, translate content, and publish it. Administrators control shared settings; editors maintain catalogue content; viewers inspect it.
Steps
- List the product types and the information customers need to compare them.
- Create product families and the attributes that belong to each family.
- Set controlled lists, measures, and content languages before entering many records.
- Design a small category tree based on how people browse.
- Create a representative product, then review it with editors and destination owners before importing at scale.
Verification
Use a small group of typical and unusual products. Check that each can be classified, enriched, translated, found, and prepared for its intended destination without workaround fields.
Common mistakes and rules
- Do not start with every possible attribute.
- Do not let category names decide which fields a product must have.
- Do not load a full catalogue until a sample workflow has been reviewed.
Work through a representative example
Model one chair before importing a furniture catalogue. Give it the Chair product family, add dimensions and materials attributes, place it in a browsing category, and enter a translated name if needed. Ask an editor and a destination owner to review the same record. Their questions reveal missing fields, unclear names, or a category being used as a product rule.
Use the reviewed chair as the import sample. Its identifiers, attributes, category links, languages, and media should demonstrate the agreed pattern before the first Import Job is started.