Origo Help

Best practices

Make catalogue changes small, named, reviewable, and easy to repeat.

Last reviewed:

Key concepts and when to use them

A reliable catalogue uses one agreed meaning for each field, one owner for each source, and a clear review point before information reaches customers. Consistency matters more than filling every possible field.

Permissions and preparation

Agree who owns each product area and who approves changes. Admins manage shared rules, editors enrich and review records, and viewers provide read-only feedback.

Steps

  1. Write down the source and owner for each important field.
  2. Use controlled lists and measures instead of repeatedly typed variations.
  3. Create one complete example for each product family.
  4. Review a small change with the people who publish or use the data.
  5. Use imports, exports, and delivery runs in small batches with a named reviewer.

Verification

Check that another editor can understand a product without asking the original author. Compare similar products for missing values, inconsistent units, duplicate assets, and unclear category placement.

Common mistakes and rules

  • Do not use free text for a value that needs filtering or reporting.
  • Do not overwrite a shared asset or translation without checking its other uses.
  • Do not mix a new model decision with a large content import.

Work through a representative example

When a supplier introduces a new finish, first decide whether it belongs in an existing controlled list. Add the option once, update a small set of representative products, and ask the destination owner to review an export. Record the decision and owner. This prevents several spellings of the same finish from spreading through later product updates.

Use the same small review set after any model change. It should include an ordinary product, a variant, and an exception, so approvals are based on visible catalogue behaviour rather than a spreadsheet column alone. Keep the review outcome with the change record.