Glossary
Exception management is the process of identifying, routing and resolving cases that cannot follow the normal processing rules. In product-data operations, exceptions may include conflicting specifications, unrecognised values, failed validations or uncertain matches. Each case needs an owner and an explicit outcome, such as correction, clarification or documented acceptance, rather than being silently skipped or forced through the workflow.
An exception record should show the affected product, the failed condition, the source evidence and what decision is needed. Assign the case to someone able to act, with a route for specialist questions. Group repeated failures where they share a cause without losing visibility of the affected products.
Prioritisation should reflect the intended use and consequences of the issue. A missing optional image and a contradictory technical specification may require different treatment, even when both appear in the same import.
A supplier provides a value for "Diameter" without identifying whether it is internal, external or nominal. The record cannot be mapped confidently. The team asks for clarification and keeps the original value with the question instead of guessing the target field.
Once the supplier confirms the meaning, the mapping and affected records can be corrected. If other rows use the same unclear column, the resolution should address the shared cause rather than only the first reported item.
An authorised decision to accept a departure should record its scope, reason and any review condition. That is different from disabling a rule for every product. Exception handling also differs from ordinary approval: it deals with a specific obstacle or deviation that needs resolution before normal processing can continue.
Explore practical support for organising, improving and maintaining product information.