How do I ensure my price changes with electronic shelf label platforms are compliant and fully auditable?

To make electronic shelf label (ESL) price changes compliant and fully auditable, you want controls across the whole lifecycle: who requested the change, who approved it, when it was published, what exactly changed, and whether the shelf, POS, and online price all matched afterward.

Key practices

1) Use role-based approvals

• Separate requester, approver, and publisher duties.
• Require approval for sensitive changes:
  • promotional prices
  • markdowns
  • dynamic pricing
  • regulated items
• Use thresholds for extra approval, e.g.:
  • % discount over a limit
  • margin below minimum
  • changes outside business hours

2) Maintain a complete audit trail

Log every event with:

• user ID / system ID
• timestamp in UTC
• SKU / location / store / zone
• old price and new price
• reason code
• approval ID
• device or API source
• publication status
• failure/retry details
• checksum/hash of the change payload if possible

Make logs immutable or append-only, with retention according to your policy.

3) Version every price file and rule

• Store each price as a versioned record.
• Preserve:
  • effective date/time
  • expiry date/time
  • promotion ID
  • rule engine output
  • rollback version
• Never overwrite the original request; create a new version instead.

4) Reconcile ESL, POS, and ecommerce prices

Compliance is not just “the label changed.”

• Run automated reconciliations:
  • ESL vs POS
  • ESL vs promotions engine
  • ESL vs online catalog
• Alert on mismatches beyond a defined tolerance window.
• Keep evidence of reconciliation results.

5) Time-stamp and schedule changes carefully

• Use a single authoritative clock source.
• Schedule price changes with:
  • effective start/end times
  • store timezone handling
  • daylight saving time rules
• Record the exact activation time on the label system.

6) Enforce validation rules before publishing

Block or flag changes that:

• violate legal pricing rules
• break price endings or rounding policies
• create negative margins
• conflict with regulated price constraints
• exceed allowed frequency of changes

7) Use tamper-evident records

• Write logs to a system with WORM-like controls or equivalent immutability.
• Restrict admin access.
• Hash or sign transaction records.
• Keep audit logs separate from operational logs.

8) Confirm successful publication

For each change, capture:

• request accepted
• approved
• distributed to ESL gateway
• label acknowledged
• label rendered successfully
• any retries or fallbacks

If a label fails, the audit record should show the exception and remediation.

9) Keep change reasons and evidence

Require a mandatory reason code such as:

• promotion
• competitor match
• seasonal markdown
• correction
• regulatory update

Attach supporting evidence where relevant:

• campaign ID
• pricing policy reference
• approval ticket
• market data snapshot

10) Periodically test and review

• Run audit spot checks.
• Test rollback procedures.
• Review access rights regularly.
• Validate that logs are complete and exportable for regulators or internal audit.

A good compliance workflow

1. Price change is requested in the pricing system.
2. System validates business rules.
3. Manager/compliance approves if required.
4. Change is published to ESL platform.
5. Platform confirms label update.
6. System reconciles against POS/ecommerce.
7. All steps are written to immutable audit logs.
8. Exception cases are escalated and retained.

What auditors typically want

Be ready to show:

• change history by SKU/store/date
• approval records
• who had access
• system-generated timestamps
• mismatch reports
• exception handling records
• proof that shelf price matched checkout price within required timeframes

If you want, I can also give you:

1. a sample audit log schema,
2. a control checklist for ESL compliance, or
3. a reference workflow diagram.