Your store comms aren't broken by volume. They're broken by the roster.

Here is a week at a fashion group, told as a clock.

Monday, one hour: the meeting that sets this week's tacticals. Monday, 5pm: the instructions go out. Tuesday: stores implement.

And a detail the operator mentioned almost in passing, the way you mention something you've stopped noticing: a lot of their store managers don't work Mondays.

A retailer in a different category, unprompted, described the same failure from the other side:

"Someone is going to read the email and then their shifts are going to end. They're not going to work for another three days and they're going to miss this email."

Two businesses with nothing in common, arriving at the same diagnosis without being asked. That's usually the sign you're looking at structure rather than sloppiness.

Your comms plan is built on a calendar. Your stores run on a roster. Nobody ever reconciled the two.

The message sent. The reader wasn't rostered.

Everyone reading this already knows their store comms get missed. What most people don't have is a diagnosis they can put in front of a GM, because "stores don't read their emails" isn't one, it's a complaint.

Here's the actual mechanism. A directive with a 48-hour life, sent to a workforce that has a 72-hour gap between shifts, has a structural miss rate. It doesn't matter how well the email was written. It doesn't matter how many times you resend it. Part-timers, 2ICs, RDOs, casuals, weekend-only managers; the person who needed to see it wasn't at work when it existed.

Now add the process on top. One retailer described the formal route for a business-wide message:

"The formal business-wide one is you have to submit a memo or comms paper-based form, essentially a Word document, on the Wednesday prior to the Monday it's going to be released. So for real-time comms and changing behaviour, it's pretty slow."

Five days' lead time, on a Word document, in a business that trades every hour. Nobody designed that. It accumulated.

An update sent as a reply to the original email splits your stores in two

This is the sharpest thing anyone said in any of these conversations, and it's worth reading twice:

"If there's any changes which, you know, it's retail, they always are, I go off on the back of that original email to say there's a tactical update. So the store might see the original email and be working off that promotion and not then see the update… And that's what we do every single week."

Follow what that does.

The original email goes to 300 stores. The update goes on the back of it. Some stores open the thread and see both. Some open the first message, act, and never come back. You now have two versions of the promotion running simultaneously across your network, and no way to tell which store is on which.

Send a second update and there are three versions. Every week. By design.

This is also the answer to a question a lot of retailers find themselves unable to answer: why can't I confirm the campaign is live? Because it isn't one campaign. Every reply-all forks it.

There's a second-order version too. In the same business, stores check email for the instruction and a separate intranet for the signage. Two systems, two chances to be looking at the wrong version of the same week.

Distribution lists are made of people, and people leave

A regional manager transitions out of the business. The Christmas trade notes go to their inbox, the way they have every year. The promotion never runs in that group of stores. The new regional manager finds it in the new year.

Nobody did anything wrong. The instruction went to the address it always went to.

If your comms route through a named individual, you have a single point of failure with a notice period.

The restructure version is worse because it's slower and nobody owns it. From a large apparel group in the middle of one:

"Our stores currently aren't receiving reports and those sorts of things because systems have changed, people have left the business. We're basically starting from scratch."

Sending is not the job. Confirming comprehension is the job.

Ask an experienced operator how they used to do it and you get an unusually honest answer:

"You'd post something on workplace or via email or via whatever store comms channel they had, and you would just hope that directive was being read, actioned, or completed."

Hope. His word.

Another put the trust chain plainly:

"It's one thing to have communicated it, but then you've got to trust all of the retail brand managers and the store managers to have read that and actually make sure everyone understood that change. That can be quite difficult."

Comprehension failure has a tell, and once you know it you'll see it every week: questions coming back that the email already answered. One operator's version: "the most frustrating part is when they ask questions and it's actually in the email we just sent." Its cousin is partial reading. You ask two questions, you get one answer, so now you're sending two emails where one should have done.

Three things get confused here, and they aren't the same:

Read receipt, a mail client opened a message. Tells you nothing about who, or whether they act on anything.

Acknowledgement, a named person, on shift, confirmed they've seen it.

Response, they understood it well enough to answer something back.

For a change of standard, only the third is worth anything.

Adding a chat channel doesn't fix it. It adds a place to look.

The instinct at this point is to put it in chat. Resist it for a moment.

"We've got a million different platforms. It's just trying to think of which platform is going to have what information… Did I see that on chat? Did I see that on email? Where did I see that?"

And channels get flanked anyway. A convenience retailer described how the support office routes around its own process without meaning to: colleagues "innocently just go, I'll email that field manager — but what they don't know is maybe another 10 people emailed them and asked in the same week."

Then there's the blocker almost nobody designs for. In a lot of retailers, frontline staff have no corporate login and no work email at all. That's why so much store communication lives on a consumer messaging app, not preference, not laziness. It's an identity gap, and it brings an audit-trail and HR exposure along with it.

Adding a channel to that situation doesn't close the loop. It adds a surface.

What a comms loop that actually closes looks like

Four structural requirements. Each one is the direct inverse of a failure above.

1. One version, updated in place. Not a reply-all. The store opens the thing and sees its current state, not its state at the time it was sent. This single change kills the forking problem.

2. Acknowledgement tied to the shift, not the inbox. The person who's on when it matters is the person who confirms it. A message read by someone who then disappears for three days hasn't landed.

3. Routing to a role, not to a person's address. Regional manager, not that regional manager. Roles don't resign.

4. A gatekeeper on inbound. One operator's own word for what's missing is exactly that: a gatekeeping system for what the support office is allowed to push at stores in a given week. Another, from a hard-discount background, described a single national gatekeeper of comms and no store-manager email at all, and his verdict was "it was super efficient for our teams in store."

One operator's summary of what changed when they fixed it is the cleanest statement of the goal: "if the wrong person's not CC'd into the email, everyone can just log into the platform and see it for themselves."

Worth saying: rituals can work. One retailer reports better than 99% completion on their weekly trade feedback rhythm, a fixed cadence, a known format, an expected response. Well-drilled routine beats good intentions. The question is what happens to everything that falls outside the ritual, which in most businesses is most of it.

Frequently asked questions

Why do store emails get missed even when they're read? Because retail runs on shifts. The person who reads Monday's email may not work again until Thursday, and by then it's been superseded. It's a roster problem wearing an inbox costume.

Should tactical updates go out by email at all? They can go out anywhere. The failure isn't the channel, it's sending an update as a new message rather than changing the original. If a store can be looking at last week's version without knowing it, the channel is irrelevant.

Is a read receipt enough? No. A read receipt tells you a message was opened. It doesn't tell you who opened it, whether they're the person who has to act, or whether they understood it. Acknowledgement by a named person on shift is the minimum useful signal.

How do you stop comms breaking when a regional manager leaves? Route to the role rather than the individual, and keep the record with the store rather than in someone's inbox. Retailers who route to a named address inherit a single point of failure with a notice period.

Our frontline staff don't have work emails. What then? Common, and structural rather than a preference, it's why so much store communication runs on consumer messaging apps. The answer is an identity that belongs to the role and the shift, rather than a corporate mailbox per person, which most retailers can't justify at frontline scale.

Every quote in this piece comes from a recorded conversation with a retail operator. Names, brands and identifying details have been removed.