WhatsApp Business Integration

主な機能

Automated WhatsApp order, invoice, and shipment notifications triggered by Magento sales events (observers on order/shipment save) with tracking links injected into approved templates

Abandoned-cart recovery sequence: a cron job scans quotes idle past a configurable threshold and sends WhatsApp nudges with a one-click resume-cart link

OTP and order-confirmation flows for checkout verification and COD confirmation, with rate limiting and retry handling

Storefront click-to-chat widget rendered via a layout XML block + UI component, with configurable position, greeting text, and per-store-view phone routing

WhatsApp Business Cloud API (Meta Graph API) client built as a di.xml virtual type, with token/phone-number-ID stored encrypted in Magento config

Template message management in the admin: map Magento events to your approved Meta templates, set language locale, and preview variable placeholders

Asynchronous dispatch through Magento's message queue / bin/magento cron so storefront and admin saves never block on the API

Per-store-view and per-website configuration so multi-brand and multi-country stores route to different WABA numbers

Admin ACL-gated configuration section (system.xml) plus a delivery/status log grid for sent, queued, and failed messages

Webhook endpoint (REST controller) to ingest WhatsApp delivery receipts and inbound replies, updating message status

GraphQL & REST coverage: a service-contract API to trigger or query notifications for headless/PWA storefronts and external systems

Opt-in and consent handling on customer accounts and at checkout to keep messaging compliant with WhatsApp policy

Full i18n / translation support for message variables and widget copy across your store-view locales

Configurable fallback to email when a WhatsApp send fails or the customer has no opted-in number

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Magento 2 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

WhatsApp Business Integration is a build-to-order Magento 2 module that turns WhatsApp into a first-class transactional and conversational channel for your store. For merchants across MENA, South & Southeast Asia, and LATAM — where WhatsApp is often the primary way customers expect to hear from a brand — email open rates simply don't cut it. This extension closes that gap.

ECOSIRE engineers the module under app/code/Ecosire/WhatsApp, wiring it into Magento with the patterns you'd expect from production code: observers and plugins (interceptors) on sales_order_save_after and shipment events, di.xml virtual types for the API client, service contracts (interfaces under Api/) so logic stays decoupled, and a system.xml-driven admin configuration section guarded by proper ACL resources. Messages are dispatched asynchronously through Magento's message queue / cron so checkout and admin save operations never block on an outbound HTTP call.

The module talks to the official WhatsApp Business Cloud API (Meta Graph API) using approved message templates, with your WABA phone-number ID and permanent access token stored encrypted in Magento config. It works on both Magento Open Source and Adobe Commerce.

Because every store's order statuses, template wording, languages, and number-routing differ, this is not a one-click Marketplace download. ECOSIRE scopes your flows, builds the module to fit your Magento version and theme, installs it on your environment, and supports it after launch. You get clean, upgrade-safe code — no core hacks — plus the Meta template submissions and configuration done for you.

得られるもの

A custom Magento 2 module (Ecosire_WhatsApp) under app/code, compatible with your exact Magento Open Source or Adobe Commerce version and PHP version

Installation and configuration on your staging and production environments, including setup:upgrade, di:compile, and cache/index validation

WhatsApp Business Cloud API connection set up against your verified WABA — phone-number ID, permanent token, and webhook callback wired and tested

Meta message-template drafting and submission guidance for your order, shipping, OTP, and cart-recovery flows

Admin configuration walkthrough plus a written runbook covering template mapping, cron, and the message log grid

Source code with composer.json, an upgrade-safe structure (no core overrides), and a short developer README for your team

A post-launch support and bug-fix window, with optional ongoing maintenance retainer

これは誰のためのものですか

MENA & Gulf retail merchant

Runs a Magento store in the UAE, Saudi Arabia, or Egypt where customers expect order updates and support over WhatsApp, not email. Needs Arabic-language templates, COD confirmation, and a click-to-chat widget that routes to the right number per store view.

South & Southeast Asia D2C brand

An India, Pakistan, Indonesia, or Philippines direct-to-consumer seller with high cart abandonment and low email engagement. Wants automated WhatsApp cart-recovery nudges and OTP-based checkout confirmation to cut fake orders.

LATAM multi-store operator

Operates several Magento websites across Brazil, Mexico, or Colombia and needs per-website WABA routing, Spanish/Portuguese templates, and delivery-status logging to prove messages reached customers.

WhatsApp Business Integration の比較方法

基準	エコシエール	カスタムビルド	競合他社	Magento 2 標準機能
Native WhatsApp order/shipping notifications	付属	付属	部分的なサポート	含まれていない
Abandoned-cart recovery over WhatsApp via cron	付属	部分的なサポート	部分的なサポート	含まれていない
OTP & COD confirmation flows	付属	部分的なサポート	部分的なサポート	含まれていない
Built, installed & supported for you (build-to-order)	付属	部分的なサポート	含まれていない	含まれていない
Upgrade-safe code (no core hacks, service contracts/plugins)	付属	部分的なサポート	部分的なサポート	含まれていない
Per-website/store-view WABA number routing	付属	部分的なサポート	部分的なサポート	含まれていない
You own the source code, no per-message vendor fee	付属	付属	含まれていない	付属
GraphQL/REST API for headless/PWA storefronts	付属	部分的なサポート	部分的なサポート	含まれていない

WhatsApp Business Integration に関するよくある質問

How long until the extension is ready and live on my store?

Because this is built to order, typical delivery is about 2 to 3 weeks from kickoff. That covers scoping your order statuses and flows, building the module against your exact Magento version, your Meta template submissions (Meta's own template approval can add a few days outside our control), and installation plus testing on staging before we go live on production. Tighter timelines are sometimes possible — tell us your target date and we'll be honest about it.

What support and updates do I get after launch?

Every build includes a post-launch support window for bug fixes and configuration adjustments. After that, you can keep an optional maintenance retainer that covers compatibility with new Magento / Adobe Commerce patch releases, WhatsApp Cloud API version changes, new message templates, and added flows. You own the source code either way — there is no license lock-in or per-message fee from us; you pay Meta directly for conversation charges.

Do I need an approved WhatsApp Business account first?

Yes. You need a verified WhatsApp Business Account (WABA) with a registered phone number on the WhatsApp Business Cloud API, plus Meta business verification. If you don't have one yet, we guide you through the setup and the message-template submissions as part of the engagement — but the WABA and Meta verification belong to you, not to ECOSIRE.

Will this work with my Adobe Commerce setup and custom theme?

Yes. The module is built to run on both Magento Open Source and Adobe Commerce, including multi-store, multi-website, and multi-language configurations. The click-to-chat widget is added through layout XML so it respects your theme, and all logic uses service contracts and plugins rather than core overrides, so it stays compatible through upgrades.

Is this a one-click download from the Adobe Commerce Marketplace?

No, and we won't pretend otherwise. This is a custom engineering engagement: ECOSIRE builds the module to fit your store, installs it, wires it to your WhatsApp Business account, and supports it. You receive real source code under app/code — not a generic Marketplace package — which is why it fits your flows exactly instead of forcing you into someone else's assumptions.