Automated Record Store Day Preorder Tracking
Every morning in the run up to Record Store Day, WebRun reads your customer reservations, tallies how many are held for each RSD title, compares that to the allocation you logged in a Google Sheet, and posts your team a Slack list of which titles are oversubscribed, fully spoken for, or still have copies free to sell on the day.
How do I track Record Store Day preorders against my allocation?
WebRun tracks your Record Store Day demand every morning. It tallies customer reservations in Common Ground, compares them against the allocation you logged in a Google Sheet, and posts your team a Slack list of which titles are oversubscribed, fully reserved, or still free to sell, so you can manage waitlists and floor stock before the day.
- Oversubscribed RSD titles are flagged before the day, not on it
- Staff know exactly how many copies of each title are still sellable
- Reservations and allocations reconcile every single morning
Built for record store owners · shop managers · counter staff · RSD participating stores
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
admin.common-ground.ioin a real browser with your saved login - no setup, no API keys. -
1
Common Ground - tally customer reservations
common-ground.io
WebRun tallies customer RSD reservations from Common Ground. - Open Common Ground and read the customer reservations tagged for Record Store Day
- Group them by RSD title and count how many copies are reserved for each
- Note the customer name against each reservation so holds can be honored in order
Done when Every RSD title has a live count of how many copies are reserved.
-
2
Google Sheets - compare against your allocation
google.com
WebRun compares reservations against your allocation sheet. - Open the RSD allocation sheet listing how many of each title you were allocated
- Match each title to its reservation count
- Calculate copies still free to sell, and flag any title where reservations exceed the allocation
Done when Every allocated title shows reserved, free, and oversubscribed counts.
-
3
Slack - report oversubscribed and free titles
slack.com
WebRun posts which RSD titles are oversubscribed or still free. - Post an RSD status list to your shop Slack channel
- Group it into oversubscribed, fully reserved, and copies still free to sell
- Put oversubscribed titles first so staff can manage the waitlist before the day
- Keep it internal. WebRun does not message reserving customers on its own.
Done when Your team has today's RSD reservation status list in Slack.
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
Will it contact customers about their reservations?
No. WebRun posts an internal Slack list for your team only. Any message to a reserving customer is left for a person to send, so nobody is contacted automatically.
How does it know my allocation for each title?
It reads the allocation counts you keep in a Google Sheet and matches them to the reservation tally, so oversubscribed and free-to-sell numbers are always based on your real numbers.
What happens when a title is oversubscribed?
It flags that title at the top of the list with the count over allocation, so your team can start a waitlist and decide how to handle it well before Record Store Day arrives.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.