Overhead audio has a production problem, not a playback problem
Playing music in a store is solved. Every vendor in the category can put a licensed playlist on a speaker. What none of them solved is the part retailers actually complain about: getting a message onto the floor while it is still true.
The standard process is a form, a voice-design portal, a producer, an approval and a delivery window. It works, and it takes days. So the sign in the window says one thing, the app says another, and the overhead audio is still promoting the sale that ended on Sunday — because changing it means starting the production process again.
AirWaves Retail removes the studio from the loop. A manager writes the line, picks a voice, hears it, and schedules it. The whole path is minutes, and it is the same scheduling and playout engine that runs radio stations, which is a rather higher bar than an in-store playlist app has to clear.
Three ways to make an announcement
An announcement is one of three things, and the difference is only how the audio gets made.
- AUDIO — use a piece of audio you already have. A jingle, a produced spot, a corporate-supplied message. It plays as it is.
- SCRIPT — write the words and choose a voice. AirWaves renders it, you preview it, and it goes into rotation. No booking, no turnaround, no per-message production fee.
- DYNAMIC — write a template rather than a sentence. It is re-resolved for each day and each hour it plays, so one announcement can name the day, the location or the current offer and stay correct all week without anyone re-recording it.
Scheduled the way a manager actually thinks
There is no traffic system here, and that is deliberate. Retail creates no orders, no avails, no invoices and no commercial breaks. A store manager is scheduling an announcement, not selling an ad buy, and every field exists because somebody running a floor would ask for it.
- A date range — the promotion starts and stops on its own. Nobody has to remember to pull it.
- A time-of-day window — the lunch message plays at lunch. The closing announcement plays near close.
- The weekdays it runs — weekend-only, weekdays-only, or the three days of a sale.
- A rotation weight from 1 to 100 — the message that matters most is heard most, without banning the others.
- A cap on plays per day — the ceiling that stops staff hearing the same twelve words two hundred times a shift.
- A target length from 4 to 180 seconds — the script is written to the length, so a twenty-second slot gets a twenty-second read rather than a rushed one.
Rotation you can explain to a district manager
Most in-store systems will not tell you why a message played as often as it did. AirWaves will, because the rule is arithmetic rather than a black box.
The next announcement is the one with the fewest plays for its weight. If two are level, the one that has waited longest goes first. That is the whole rule. It means a weight-5 message runs roughly five times as often as a weight-1 message, it means nothing starves, and it means the answer to “why did that run four times this morning?” is a number you can point at.
The safety properties matter more than the features
Three things in this module exist purely so a store is never left with a problem nobody is standing next to.
- A failed render cannot create silence. The scheduled announcement becomes an ordinary talk element between two songs. There is no special case anywhere in the playout path and no placeholder that can air as dead air.
- An edited announcement cannot air in its old words. Change the script, the voice or the mode and the cached audio is discarded. There is no route by which the corrected message and the wrong message both exist.
- Nothing airs unheard. Every announcement can be previewed before it is scheduled, in the voice it will actually use.
Where it came from, and why that matters
AirWaves Retail is not a retail product that grew a scheduler. It is a broadcast platform with the traffic system deliberately taken out.
The engine underneath is the same real-time C++ engine that runs radio stations: it holds the log, cues the audio, handles the segues and does not fall over at two in the morning. Scheduling music by category, rotating messages against rules, dayparting, and never leaving air silent are not features that had to be built for retail — they are what the platform already does for a living.
What was built for retail is the part that removes everything a store does not need: the orders, the avails, the invoices, the breaks and the studio.
Retail audio and in-store messaging, answered
Retail audio — also called in-store audio or overhead music and messaging — is the music and the spoken announcements playing through the speakers in a shop, restaurant or venue. The music sets the room; the announcements do the work: promotions, loyalty sign-ups, safety and directional messages, and whatever is true this week. AirWaves Retail schedules both, and voices the announcements with AI so a message can be written and airing the same hour.
The music is comparable. The difference is the message. In the standard model you fill in a request, a producer records it and it is delivered on their schedule, so a change costs days and a fee. In AirWaves a manager types the line, picks a voice, previews it and schedules it — and a dynamic template re-reads itself every day and hour, so a message that names the day or the current offer never has to be re-recorded at all.
No, and there is not one to configure. Retail creates no orders, no avails, no invoices and no commercial breaks by design. You schedule announcements, not ad buys. Everything is a date range, a time window, the weekdays it runs, a weight and a daily cap.
Yes — that is what a dynamic announcement is. Instead of a fixed sentence you write a template, and it is resolved fresh for each day and each hour it plays, so a single announcement can carry the day, the location or the current promotion and stay correct across a whole campaign without being re-recorded.
Two controls, and they work together. A rotation weight from 1 to 100 sets how often a message is heard relative to the others, and a maximum-plays-per-day cap sets a hard ceiling. The scheduler then always picks whichever announcement has the fewest plays for its weight, so nothing starves and nothing dominates.
Nothing airs that should not. The chosen announcement only becomes a scheduled element once its audio exists, so a failed render simply means that announcement is not scheduled that time round — it can never leave a silent placeholder on the floor. This is a design rule in the module rather than an error handler bolted on afterwards.
Yes. An announcement in AUDIO mode plays a file you supply, so professionally produced messages, corporate-supplied audio and your own voice talent all work exactly as they do today. Most sites end up mixing the two — produced audio for brand messages, AI-voiced scripts for the things that change weekly.
Explore the rest of the platform
Every AirWaves module shares one engine, one database and one login — and every one of them also runs standalone against the automation system you already own.
Hear what your stores could sound like
Book a walkthrough with an engineer who has actually run a radio station, or call 1-877-224-1656. No bots, no phone tree.