Glossary
An approval workflow is a defined process for reviewing proposed information or changes and recording an authorised decision before they proceed. In product data, it can assign reviewers to technical attributes, descriptions or assets, with routes for acceptance, rejection and correction. The approval applies to a stated scope and evidence; a recorded decision does not make every associated claim automatically correct.
Specify the fields, documents or changes under review, the criteria and the person authorised to decide. A reviewer checking product imagery may not have the expertise to approve an electrical rating. Separate those responsibilities where the evidence and expertise differ.
The workflow should retain the reviewed version, decision, reviewer and any reason for rejection. Decide which later changes require another review so an approval cannot silently cover information that was never examined.
An AI tool drafts a description from a manufacturer document and approved attributes. The reviewer checks whether the wording preserves those facts, uses the correct product variant and introduces any unsupported performance claims. Uncertain statements return for correction or clarification.
The same process can review manually written copy or supplier submissions. Human review is an assigned activity with defined evidence and authority, rather than a label added to content after publication.
Automated validation can check formats and required fields before review, while approval addresses the decision within the assigned scope. Neither replaces the other. Keep exceptional acceptance explicit and distinguish approval from successful publication or delivery. A product may be approved yet still wait for a separate operational step.
Explore practical support for organising, improving and maintaining product information.