MoraselWhatsApp order notifications for every Shopify event
Turn on the order events you want — created, paid, edited, cancelled, partially fulfilled, fulfilled — and map each to an approved WhatsApp template. Draft orders and risk checks stay internal.
Discover
Convert
Order
Fulfil
Support
Retain
Feedback
What breaks with manual order updates
Typing order updates by hand means some go out late, some go out twice, and a cancelled order can still get a fulfilled message if nobody catches it in time.
- A staff member copies order numbers into chat, so updates arrive hours after the event or not at all
- The same event fires twice from Shopify and the customer gets two identical messages
- An order is cancelled after being marked fulfilled, and both messages reach the customer
- Draft orders or internal risk flags get treated like real customer-facing events
What the notification record holds
One record per order event, covering the toggle, the template, and why a send did or didn't happen.
- Event toggle
- Per-event on/off switch for created, paid, edited, cancelled, partially fulfilled and fulfilled.
- Template map
- The Meta-approved template each enabled event sends.
- Dedupe window
- The minimum time between messages for the same order and event, so a repeated webhook doesn't send twice.
- Suppression reason
- Recorded when a later state supersedes an earlier one — a cancelled order never gets a fulfilled message.
- Internal-only flag
- Draft orders and risk-assessment events are logged but never reach the customer.
- Send log
- Every attempted send, with its outcome: sent, suppressed, or held by the dedupe window.
What happens between the event and the message
The same six checks run for every order event, before anything reaches the customer.
Shopify sends the event
Created, paid, edited, cancelled, partially fulfilled or fulfilled — the raw webhook lands first.
Check the event toggle
An event with its toggle off stops here; nothing is sent.
Check for a duplicate
If an identical event landed within the dedupe window, the repeat is skipped.
Check for suppression
If a later state already supersedes this one — cancelled after fulfilled, for instance — the send is suppressed.
Send the mapped template
The enabled, non-suppressed event goes out on the Meta-approved template mapped to it.
Log the outcome
Sent, suppressed or held — every event is logged, whether or not it reached the customer.
What the customer sees, event by event
Two events, two messages, each on its own approved template.
What the team sees
Every toggle, template and suppressed send, visible in one place.
- A toggle panel for created, paid, edited, cancelled, partially fulfilled and fulfilled, each mapped to its template
- A suppression log showing which sends were blocked and why
- The dedupe window, configurable per workspace
- Draft orders and risk-assessment events marked internal-only, never shown as sent
Who decides what sends
Enabling an event and approving a template are separate, deliberate steps.
- A workspace admin turns each event on or off; nothing sends by default until it is enabled
- Only a Meta-approved template can be mapped to an event
- The dedupe window and suppression rules apply the same way to every store
- Risk-assessment and Shopify Protect events stay internal; they never generate a customer message
What this does not do
Morasel does not message a customer for every Shopify event — only the ones you enable. Draft orders and risk-assessment events never reach a customer, and a superseded state, a cancelled order for one, is suppressed rather than sent.
Map your Shopify order events to WhatsApp
Turn on the events you want, map each to an approved template, and let dedupe and suppression handle the rest.
Order notification questions
Does every order event send a message?
No. Only the events you turn on — created, paid, edited, cancelled, partially fulfilled or fulfilled — send a message, each on its own approved template.
What stops a duplicate message?
A dedupe window: if the same event fires twice for the same order within that window, only the first send goes out.
Can a cancelled order still get a fulfilled message?
No. Suppression checks the order's current state before sending, so a superseded event — fulfilled after cancelled — is blocked.
Do draft orders message the customer?
No. Draft orders and risk-assessment events are logged for internal use only and never generate a customer-facing send.
Can I choose which events are enabled?
Yes. Each of the six events has its own toggle and its own template mapping.
Is sending order notifications charged per message?
Not by Morasel — the per-message cost is WhatsApp's, and you see it in the wallet. Order notifications run on your Morasel subscription — Core $49, Pro $99, Max $199, Enterprise on request. WhatsApp usage is billed separately from a prepaid wallet at Meta's official rates.