Dynamic pricing is no longer only a merchandising decision. For retailers operating automated pricing across stores, websites and apps, it is becoming a systems-governance issue: a pricing rule can be commercially sound yet impermissible in a particular location, channel or context.

New Jersey’s action banning certain dynamic-pricing practices and pausing the use of electronic shelf labels illustrates the operational challenge. Compliance cannot sit in a policy document while pricing engines continue publishing changes without jurisdiction-aware controls. Retailers need to translate legal requirements into configuration, approval, testing, evidence and rollback procedures.

The practical goal is not to stop every automated price update. It is to ensure that the business can distinguish permitted changes from prohibited practices, apply the right rule to every transaction and prove what happened afterward.

Map regulation to systems, locations and channels

Start with a control matrix rather than a broad instruction to “disable dynamic pricing.” Record each affected jurisdiction, effective period, covered product or transaction, prohibited pricing behavior and any restriction affecting electronic shelf labels. Legal counsel should validate the interpretation; engineering and operations should convert it into enforceable rules.

Then map those rules to every place a price can be created or displayed: the pricing engine, promotion platform, store server, electronic shelf label system, point of sale, self-checkout, website, mobile app, marketplace feed and customer-service tools. Include fulfillment scenarios such as buy online, pick up in store, where the customer’s location, selected store and transaction channel may produce conflicting rule assignments.

Do not assume a “New Jersey” flag in one database covers the entire journey. Location can be represented by store address, device location, delivery destination, billing address or pickup point. Assign one authoritative method for determining which pricing policy applies, document exceptions and test ambiguous cases.

Separate routine updates from prohibited dynamic practices

Automated pricing encompasses very different actions. Scheduled markdowns, centrally approved promotions, clearance changes and corrections may present different compliance risks from rapid, demand-responsive adjustments. The system therefore needs a taxonomy of price-change reasons, not merely old and new values.

Require every proposed change to carry a reason code, source, affected products, channel, geography, start and end time, and approving policy version. Rules should block or quarantine changes that use prohibited inputs or methods in covered locations. They should also prevent teams from recreating a restricted practice through another tool, such as a promotion engine or store-level override.

Electronic shelf labels deserve separate treatment. They are a display and execution layer, not synonymous with dynamic pricing, but a regulatory pause affecting their use creates its own control requirement. A retailer may need to freeze label automation in covered stores while preserving lawful updates through an approved alternative process. The source article should be treated as a prompt for legal review, not as a substitute for the underlying rule or tailored advice.

Put approval, logging and consistency tests in the release path

High-risk price changes should require human approval before publication. Use role-based access and separation of duties: the person designing a pricing rule should not be its sole approver. Approval thresholds can reflect jurisdiction, speed, scale, input type and customer impact, with stricter review for rules capable of changing prices quickly or differently across customers.

Maintain an immutable audit trail that connects the business decision to the customer-visible outcome. At minimum, capture the rule and model version, inputs, old and proposed prices, reason code, covered SKUs and locations, timestamps, requester, approver, deployment result, overrides and rollback events. Retention should align with legal and dispute-resolution needs.

Publication is not completion. Run automated tests comparing the authoritative price with shelf signage, electronic labels where permitted, point of sale, self-checkout, web, app and order confirmation. Use representative baskets that include promotions, loyalty pricing, taxes, substitutions and pickup orders. Fail closed when a protected location receives an unapproved rule, and alert operators when shelf and checkout prices diverge.

What most people miss

The hardest failures occur at boundaries. A national campaign may be lawful generally but incorrectly propagate into an excluded store. A cached app price may outlive a rollback. A manual shelf label may lag behind the register. A marketplace may continue displaying a feed after the retailer has disabled its own page.

Ownership must therefore extend beyond the pricing team. Assign named owners for policy interpretation, rule configuration, store execution, channel synchronization, incident response and customer remediation. Track third-party dependencies and require vendors to provide change records, access controls and an emergency stop mechanism.

Prepare rollback and incident procedures before deployment

Every automated pricing release should have a tested rollback plan. Preserve the last approved price set, support rollback by jurisdiction and channel, and define a safe fallback when synchronization fails. A global shutdown may create unnecessary disruption; a narrowly scoped kill switch is usually more useful.

The incident runbook should define who can halt publication, how stores receive instructions, how stale labels are identified, how digital caches and external feeds are cleared, and how affected transactions are reviewed. It should also specify escalation to legal, compliance, finance and customer service. Rehearse the procedure with a scenario in which one channel rolls back successfully while another remains stale.

Post-incident review should examine both technical and governance failures. Ask why the rule passed validation, whether jurisdiction data was correct, whether an override bypassed approval and whether monitoring detected customer-visible inconsistency quickly enough. Feed the findings into tests and access policies.

Govern customer-facing AI as a connected risk

Kohl’s AI shopping-assistant initiative is contextual rather than evidence about New Jersey’s law. It nevertheless highlights a related governance problem: customer-facing automation can influence product discovery, recommendations and perceptions of value even when it does not directly set prices.

Retailers should disclose when customers are interacting with an automated assistant, define what customer and transaction data it may access, and prevent it from inventing prices, promotions or availability. The assistant should retrieve current values from authoritative services, preserve applicable location and channel rules, and hand off disputed or ambiguous cases to a person.

Log the information shown and the system sources used without collecting unnecessary personal data. Test whether recommendations or explanations change improperly across customer segments, and prohibit the assistant from implying that a price is personalized unless that practice has been reviewed and authorized. Pricing governance and AI governance can share controls for versioning, approvals, monitoring, incident handling and vendor oversight.

Practical compliance checklist

• Have legal counsel document the covered New Jersey practices, locations, dates and electronic-shelf-label requirements.
• Inventory every system and vendor that creates, transmits, displays or charges a price.
• Define an authoritative jurisdiction signal for stores, delivery orders and pickup transactions.
• Classify price changes with mandatory reason codes and distinguish routine updates from restricted dynamic practices.
• Configure location- and channel-specific blocks instead of relying on written instructions.
• Require independent human approval for high-risk rules and overrides.
• Log inputs, versions, prices, scope, approvals, publication outcomes and rollback events.
• Continuously test shelf, label, register, self-checkout, website, app and order-confirmation consistency.
• Maintain a last-known-approved price set and scoped kill switches.
• Rehearse store communications, cache clearing, external-feed withdrawal and customer remediation.
• Require AI assistants to disclose automation, respect data boundaries and use authoritative price sources.
• Review controls after regulatory changes, system releases and pricing incidents.