Almost every e-shop is set up the same way: an order arrives, the system mails a copy to the owner and maybe to the warehouse address. It has worked for years, nobody questions it, and it is the weakest link in the whole fulfilment chain.
E-mail is not an alerting channel. It is an archive that looks like one.
What does not work about e-mail
It mixes with everything else. The same inbox that receives a two-thousand-euro order also receives invoices, newsletters and complaint threads. Important and unimportant look identical, so everything gets read with the same attention — which is to say, very little.
It has one recipient. Forwarding rules and distribution groups only pretend to solve that. Nobody can see who already opened the message, so either two people work the same order, or nobody does, each assuming the other has it.
It is muted on the phone. Most people turn mail notifications off precisely because they would ring all day. An alert that is deliberately silenced is not an alert.
It says nothing when nothing happens. And silence is often the most expensive information there is. If no order arrives for three hours, e-mail naturally sends nothing — yet that is exactly when it is worth checking the payment gateway or a broken template.
What you actually need from a channel
Three things, and e-mail does none of them properly.
- Speed with a way to respond. The message should land where the team already is, and be something you can comment on or assign to a person.
- Shared context. When an order drops into a team channel, the warehouse, support and the owner see it at once and settle in one thread who takes it.
- A quiet mode. Not every event deserves a ring. A new order does; twenty status changes an hour do not — those belong in one digest.
That is why sending orders to Slack, Discord, Teams or Telegram makes sense. Not because it is more modern, but because chat is the one place the team genuinely spends the day.
Where e-mail does belong
We are not saying to turn e-mail off. It has two jobs nothing else does better:
- Archive and accounting. A copy of the order in the inbox is searchable years back and does not depend on some service keeping your account alive.
- The daily summary. One message in the morning with yesterday’s revenue reads better in an inbox than in chat, where it would sink out of sight.
The difference is the job. E-mail is the record, chat is the alert. The trouble starts when one is used for both.
Practical setup
If you go ahead, three recommendations save the most arguing:
- A dedicated channel, say
#orders. In the main team channel the notifications annoy everyone within a week and get muted, just like the mail. - Only events that need action. New order, cancellation, an order still unpaid after two hours. A status change made by your own colleague is not something anyone needs to see.
- One digest a day instead of running numbers. Revenue, order count and a comparison with last week in a single message.
That is exactly how our Notify addon is built: orders go to the channel you pick, noisy events are merged into a digest, and customer personal data is not in the message at all by default.