System for Checking Shelf Label Content Before Publication

The problem

Label drafts, product records and promotion terms arrive from different systems and event logs, preventing the team from viewing each case on a single timeline.

As a result, source links may be lost while warnings for missing fields and inconsistencies are prepared, the case may be referred to the wrong team and the basis for a technical decision may remain unclear.

An incomplete workflow may overlook unclear required wording or unit pricing, while an unsuitable workflow could lead to a misleading label being printed.

What we set out to improve

• Time taken for draft missing-field and inconsistency warnings to be ready for specialist review
• Correct referral of records with unclear required wording or unit pricing to the appropriate specialist queue
• Record of suggestions corrected or rejected by the pricing officer

How the system works

1. 01 Retrieve label draft, product record and promotion term data from authorised sources
2. 02 Verify the source, timestamp and record identifier
3. 03 Add the context of the relevant asset, user, store, vehicle or content
4. 04 Prepare draft warnings for missing fields and inconsistencies
5. 05 Compare the draft with technical rules and authority limits
6. 06 Check for exceptions: unclear required wording or unit pricing
7. 07 Obtain the pricing officer's approval, correction or rejection
8. 08 Write the input, suggestion, change and final decision to the audit log

Methods we used

• Source- and time-traceable data extraction for label drafts, product records and promotion terms
• Structured output that constrains missing-field and inconsistency warning fields according to technical rules
• An exception gate that separates unclear required wording or unit pricing from workflow processing
• An authorised queue that presents evidence and suggestions together for the pricing officer
• Duplicate transaction checks and a rollback record to address the risk of printing a misleading label

Where people stay involved

Data and security

Only fields required for the task are processed from label drafts, product records and promotion terms. Source-system permissions are preserved, and personal, technical and security-sensitive data is minimised before being provided to the model. Every read, suggestion, human change and target-system action is written to the audit log.

Who this suits

Frequently asked questions