Glossary

What is a product data workflow?

A product data workflow defines how information moves through tasks, responsibilities and decision points, from collection or editing to an agreed outcome. It specifies who acts, what they need to complete and how a record proceeds or returns for correction. A workflow can support initial onboarding or ongoing changes and may combine automated checks with human decisions.

Define states, triggers and responsibility

A workflow needs more than a sequence of screen names. Define what starts it, which products it covers, the responsible roles and the conditions for moving between steps. Explain how failures, unanswered questions and changes to already reviewed values are handled.

Some tasks can run independently, while others depend on an earlier decision. The design should reflect those dependencies rather than requiring every product to pass through identical work regardless of its needs.

Example: preparing a new product range

A workflow for a new range begins with source collection and field mapping. Applicable quality checks identify missing or invalid information. A data steward resolves routine issues, a technical reviewer checks specialist claims and an authorised role confirms the agreed release criteria.

If a supplier changes a critical specification later, a separate update trigger can return the affected information for review. Unrelated approved fields need not be rewritten simply because the record re-enters the process.

Workflow and automation

A workflow describes the process whether its steps are manual or automated. Automation can execute defined tasks, but it does not establish the business rules or resolve every ambiguous claim. Keep task completion, content approval and successful delivery to a destination distinguishable, with enough history to understand the outcome.

Related terms

Sources and further reading

Product Data Services

Explore practical support for organising, improving and maintaining product information.