Revel Systems Multi-Location Price Change Rollout
When you upload a price change file, WebRun reads each item and new price, opens Revel Systems and applies the update across every designated location, logs each change in a Google Sheet as it goes, and posts a completion checklist to Slack so you can confirm no location or item was missed.
How do I roll out a price change across multiple Revel Systems locations automatically?
WebRun reads your price change file in Google Sheets, opens Revel Systems, and applies every updated price across each designated location in sequence, confirming each change before moving on. It then posts a completion checklist to Slack showing every item, its old and new price, and the status per location.
- Price changes applied across all Revel locations without manual item-by-item editing
- Every update confirmed and logged before moving to the next item
- Completion checklist in Slack so management can verify the rollout was complete
Built for multi-location restaurant operators · QSR franchise managers · retail chain managers · operations managers using Revel
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
manage.revelsystems.comin a real browser with your saved login - no setup, no API keys. -
1
Google Sheets - read the price change list
google.com
WebRun opens Google Sheets to read the price change list. - Open the price change Google Sheet uploaded by the manager
- Read each row: item name, current price, new price, and the locations to apply it to
- Validate that every item name matches a product in Revel before proceeding
Done when Every item in the price change file is confirmed present in Revel and ready for update.
-
2
Revel Systems - apply updates across each location
revelsystems.com
WebRun opens Revel Systems to apply updates across each location. - Open Revel Systems Management Console and navigate to Product Management
- For each item in the list, open its record and update the price for each designated location
- Confirm the saved value matches the new price before moving to the next item
Done when Every price change from the list has been saved and confirmed in Revel for each location.
-
3
Slack - post the completion checklist
slack.com
WebRun opens Slack to post the completion checklist. - Post a completion checklist to Slack showing each item, old price, new price, and location status
- Flag any item that could not be updated due to a mismatch or lock
- Provide the count of successful updates versus total items in the file
Done when A completion checklist with per-item and per-location status is posted in Slack for review.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Can WebRun roll back a price change if something went wrong?
WebRun logs the old price for every item before applying the update, so your team has a complete record to revert from. The actual rollback is done by your team using that log as a reference.
How does it handle items that only apply to some locations?
The price change file includes a location column. WebRun applies each price only to the locations specified in that row and confirms the update per location in the checklist.
What if an item name in the sheet does not match Revel exactly?
WebRun validates every item against Revel before starting updates and flags any mismatches in the completion checklist. It skips rather than guessing, so no wrong item is updated.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.