HomeFeaturesIntegrationsSolutionsPricingBlogContact Book a demo
Solutions · Retail & E-commerce

WhatsApp for retail and e-commerce

The deepest non-vertical fit on the platform. Shopify and WooCommerce sync natively — catalogue, orders and carts — with recovery flows, pay-by-link, back-in-stock alerts and ad attribution closing the loop.

Commerce module Official WhatsApp Business API
The problem

Why retail & e-commerce ends up on WhatsApp

Online retail has a well-documented leak: most carts are abandoned, and most recovery attempts go to email, where they compete with everything else in an inbox and are largely ignored.

WhatsApp changes the arithmetic because the message actually gets read. But a recovery message is only useful if it carries a working checkout link, knows what was in the cart, and stops sending the moment the order completes — which means the store and the messaging platform have to share state, not just exchange notifications.

That is what the Commerce module does. Shopify and WooCommerce catalogue, order and cart data sync in real time. Recovery flows fire on timed rules with a one-tap checkout link. Payment happens in the thread through Stripe, PayTabs, Razorpay or Telr, and the payment event returns to the conversation. Click-to-WhatsApp ad attribution then ties the order back to the campaign that produced it.

Workflow

An abandoned cart, recovered

The single highest-return flow in retail, and the one worth building first.

  1. 1

    Cart abandoned in the store

    Shopify or WooCommerce fires the cart event to Zapelite. The contact is matched by phone number, and the cart contents are attached to their record — so the message can name the product rather than say "you left something behind".

  2. 2

    Timed reminder with a real checkout link

    A recovery flow waits a configured interval, then sends a marketing template carrying a one-tap checkout link. If the order completes at any point, the sequence stops — nobody gets chased for a purchase they already made.

  3. 3

    Payment in the thread

    For customers who would rather not return to the store, a pay-by-link through Stripe, PayTabs, Razorpay or Telr closes the sale inside WhatsApp. The payment event comes back to the conversation that produced it.

  4. 4

    Order updates as utility templates

    Confirmation, dispatch and delivery updates go out as utility templates — correctly categorised, which is materially cheaper than sending them as marketing, and they land inside the thread the customer already knows.

  5. 5

    Review request, then attribution

    A post-purchase review or NPS flow runs after delivery. Meanwhile CTWA attribution reports which ad campaign produced the order, so ad spend is judged on revenue rather than on clicks.

Use cases

What teams actually run

Everything below ships in the product. See every feature or the integrations catalogue.

Commerce

Storefront in chat

Shopify or WooCommerce catalogues synced in real time — browse to checkout in chat.

Recovery

Abandoned cart recovery

Timed reminders with one-tap checkout links, stopping automatically on purchase.

Payments

Pay-by-link & invoices

Stripe, PayTabs, Razorpay or Telr links and WhatsApp invoices, sent by flows.

Restock

Back-in-stock alerts

Wishlisted customers notified the moment inventory returns.

Ads

CTWA attribution

Click-to-WhatsApp ads tracked to orders — see which campaign sold what.

Feedback

Review requests

Post-purchase review and NPS flows, piped into your dashboards.

Outcomes

What changes

  • Cart recovery moves to a channel that gets opened, with a link that works and a sequence that knows when to stop.
  • Order updates cost less, because they are categorised as utility rather than marketing.
  • Ad spend is judged against orders rather than clicks, through Click-to-WhatsApp attribution.
  • Support and sales share one thread — the question about sizing and the order it produced are the same conversation.
Where to start

Build this first

Build abandoned-cart recovery first. It is the clearest return in retail, it needs only the store integration, and its impact is directly measurable against your current recovery rate — which makes it the easiest case to build the rest of the programme on.

Order notifications come next, because they reduce support volume and cost little when categorised correctly. Leave broadcast campaigns until segmentation is real; a marketing blast to an unsegmented list is the fastest way to damage the number your storefront depends on.

Questions

Retail & E-commerce, answered.

Both, natively. Catalogue, orders and cart events sync in real time, which is what makes abandoned-cart recovery, back-in-stock alerts and order updates work without manual exports.

The store fires a cart event, the contact is matched by phone number and a timed flow sends a marketing template with a one-tap checkout link. The sequence stops automatically if the order completes, so customers are never chased for a purchase they already made.

Yes. Pay-by-link through Stripe, PayTabs, Razorpay or Telr is sent inside the thread, and the payment event returns to the same conversation. For UAE stores, PayTabs and Telr are gateways local customers already recognise.

Order confirmations, dispatch and delivery updates are utility templates, priced lower than marketing and free inside an open 24-hour customer service window. The costly mistake is letting them be categorised as marketing.

Yes. Click-to-WhatsApp attribution tracks the ad click through the conversation to the order, so campaigns are measured on revenue rather than on click volume.

Yes. A return request opens a ticket with its own number and SLA, and the conversation stays attached to the original order, so the agent handling it can see what was bought and when without asking the customer to repeat it.

Your industry, automated

See it running on your workflow

Book a demo and bring one real scenario from your operation. We will build it in the product rather than describe it on a slide.

Chat with us — replies in seconds