MoraselSync and enforce WhatsApp marketing consent for every Shopify customer
Every promotional send is checked against a consent state that stays in sync with Shopify — captured at checkout or by a WhatsApp reply, honoured the moment it's revoked, without touching a single transactional message.
Discover
Convert
Order
Fulfil
Support
Retain
Feedback
What breaks without synced WhatsApp consent
Marketing consent that lives only in Shopify, or only in a chat inbox, drifts. A merchant ends up guessing who opted in, messaging someone who already said stop, or blocking an order update that should never have been touched.
- A checkout opt-in is recorded in Shopify but never reaches the system that sends WhatsApp campaigns
- A customer replies "STOP" on WhatsApp, and the next scheduled campaign goes out anyway because the reply was never synced back
- An order confirmation or shipping update gets held back by a rule meant only for marketing
- Two systems report two different consent states for the same customer, and no one knows which one is current
The consent record Morasel keeps
A consent record stored per customer, kept current with Shopify — not a snapshot taken once at signup.
- Consent source
- The checkout WhatsApp marketing opt-in, or an explicit WhatsApp reply such as opting in or replying "STOP" — whichever happened most recently.
- Consent state
- Synced with Shopify's CustomerWhatsAppMarketingConsent value, so both systems report the same marketing state for the same customer.
- Sync trigger
- The customer WhatsApp marketing consent update webhook, applied the moment Shopify's record changes.
- Enforcement point
- Checked immediately before every marketing send is queued — not only when the customer was first added to a list.
- Revocation handling
- A revoked consent state is honoured immediately: no promotional message goes out afterward.
- Scope
- Applies to marketing sends only. Order, shipping, payment, and other transactional messages run on their own basis and stay unaffected.
How a consent state stays trustworthy
The same check runs before every marketing message, whichever direction consent last changed.
Customer opts in
At Shopify checkout, or by replying to a WhatsApp message with an opt-in confirmation.
Morasel records the state
The consent state is stored per customer, synced with Shopify's CustomerWhatsAppMarketingConsent value.
Shopify and Morasel stay in sync
A consent-update webhook applies any change from either side, so the two records never drift apart.
Every marketing send checks first
Before a promotional message queues, the customer's current consent state is checked — never assumed from an earlier snapshot.
A revocation is honoured immediately
A "STOP" reply or an opt-out in Shopify blocks every future marketing send at once. Transactional messages keep going.
What a consent change looks like on WhatsApp
One thread: a checkout opt-in honoured, a revocation applied, and a transactional update sent regardless.
What the team sees
Consent state next to every customer, not buried in a spreadsheet or a separate app.
- Each customer's current WhatsApp marketing consent state, synced from Shopify's CustomerWhatsAppMarketingConsent field
- A visible history of when consent was granted — at checkout or by WhatsApp reply — and when it last changed
- Every marketing send checked against current consent before it queues, never against a cached list
- Transactional messages tracked separately, so an opt-out never blocks an order or shipping update
Who can change what
Consent state changes only from a verified signal — never from a manual override that isn't logged.
- Consent state updates only from a Shopify checkout opt-in, a Shopify consent-update webhook, or an explicit WhatsApp reply — never inferred from silence
- Every consent change is logged with its source and timestamp
- Only staff with campaign access can build a send list, and every list is filtered by current consent before it sends
- A support conversation with an opted-out customer keeps flowing on WhatsApp — the boundary is on marketing, not on the channel
What this does not do
Morasel never treats a phone number, an order, a checkout, or a generic SMS or email consent as WhatsApp marketing consent — only an explicit checkout opt-in or a WhatsApp-specific opt-in counts. It also never sends a marketing message just because a webhook fired; every send still checks the current consent state first.
Keep every WhatsApp send consent-checked
Connect your Shopify store so every marketing message checks a consent state that's always in sync — and every revocation is honoured immediately.
Consent questions
How is WhatsApp marketing consent captured?
Either at Shopify checkout through the WhatsApp marketing opt-in, or by an explicit WhatsApp reply. Whichever happened most recently is the current state.
What happens when a customer replies "STOP"?
Their consent state is revoked immediately, and no further marketing message is sent. Order, shipping, and other transactional messages are unaffected.
Does placing an order count as WhatsApp marketing consent?
No. An order, a checkout, a phone number on file, or a generic SMS or email consent is never treated as WhatsApp marketing consent.
Is consent checked once or before every message?
Before every marketing send. A customer who opted in last month but revoked yesterday will not receive today's campaign.
Will an opt-out stop my order confirmations?
No. A marketing opt-out only blocks promotional sends. Order, payment, fulfillment, and shipping messages run on their own basis.
Does consent sync cost anything on its own?
No — it comes with the Shopify connection, not as a separate line. Consent sync runs 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.