How to roll out price changes across locations
To roll out price changes across several locations, the change needs an effective date, an approval and a confirmation from each store. In Jestor, a price change is a record connected to the products and locations it affects, with completion tracked per store.
Why price changes arrive unevenly
A new price is decided centrally and communicated by message. Some stores apply it immediately, others the following week, and one never sees the message.
Customers then encounter different prices for the same item, and reconciliation at head office becomes impossible.
What a structured rollout fixes:
- Prices applied on different dates per location
- No confirmation that a change was actually made
- Promotional prices left active after the campaign
- No record of what a price was on a given date
- Changes made without approval
What a price change record should hold
| Field | Why |
|---|---|
| Products affected | Connected records, not a list in text |
| Old and new price | Historical record |
| Effective date | When it applies |
| End date | Essential for promotions |
| Locations affected | Not every change is universal |
| Confirmation per location | Proof it was applied |
Step by step to implement it
- Create the change as a record, with products and locations connected.
- Route it through approval, since pricing is a commercial decision.
- Set the effective date, and an end date for anything promotional.
- Notify each location with the date, not with an instruction to act now.
- Require confirmation from each store once applied.
- Track outstanding confirmations on one board.
- Reverse promotions automatically at the end date.
Why the end date matters more than the start date
Promotional prices left running after a campaign are a recurring and quiet margin loss. Requiring an end date at creation, and reverting automatically, removes a failure that otherwise depends entirely on someone remembering.
Why choose Jestor
In Jestor, price changes connect to products and locations as related records, approval routes through the same logic used for other decisions, confirmations per location are tracked on one board, automations handle the reversal at the end date, and the history shows what a price was at any point.
Frequently Asked Questions
How do I know every store applied the change?
Require a confirmation per location and track outstanding ones on a board. See jestor.com.
Why require an end date on promotions?
Because promotional prices left active are a quiet and recurring margin loss.
Can I see what a price was on a past date?
Yes, through the change history connected to the product.
Video Tutorial: Step by Step
With Jestor, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.