Skip to content
✦

Small plugins. A more connected business. One-time $15 licenses for your favorite platforms.

Explore the collection ↗
← All integrationsDOITEASY WASMS · BIGCOMMERCE

Keep every
customer connected.

WhatsApp notifications, editable templates and phone verification for BigCommerce. One-time activation for one site, with installation and usage guides.

Thoughtfully connected.
BUILT FOR YOUR WORKFLOW

Everything in one place.

WhatsApp notifications

Account, order, payment and shipping events supported by your platform, with separate switches and editable message templates.

One familiar control center

Connection settings, client preferences, message history, templates and administrator tools stay together. Native event coverage varies by platform.

Arabic & English

One language at a time, Arabic RTL or English LTR, with IBM Plex fonts and a compact responsive layout.

Templates & formatting

Reusable presets, safe merge fields, bold, italic, strike, code, lists, quotes and a searchable emoji picker.

Phone ownership & preferences

Opt-in and opt-out controls, expiring verification codes, attempt limits and separate WhatsApp-registration checks where supported.

Reliable dispatch & records

Durable queues, duplicate protection, delivery-request states, encrypted history and test mode. Acceptance is separate from phone delivery.

Your own WASMS connection

Use your account API key and connected WhatsApp device. Normal plan limits and usage charges apply separately.

One purchase, one site

A one-time license for this plugin on one canonical site. Move it by reissuing the activation code from My licenses.

KNOWLEDGE BASE

From install to everyday use.

Installation, activation, templates, sending, troubleshooting and moving your license.

01Before you install+
Hosted PHP 8.1+ app deployment kit, requiring HTTPS, PDO MySQL and an isolated database. This is not a marketplace-published app. Native OAuth/webhook installation testing is pending.
02Install & open your product+
Create a draft app in the BigCommerce Developer Portal. Configure the supplied /bigcommerce/auth, /bigcommerce/load and /bigcommerce/uninstall callbacks on your HTTPS host. Match the bundled read-only order/customer OAuth scopes exactly. Install on a sandbox store and open WASMS from the store control panel. Use https://store-STOREHASH.mybigcommerce.com as the canonical license identity, replacing STOREHASH with your store hash.
03Scheduled sending & reminders+
Keep only public/ as the web root. Store the completed config.example.php outside it; define DOITEASY_HOSTED_CONFIG for both PHP-FPM and CLI. Preserve app_key on updates. Initialize with php bin/worker.php install, then schedule php bin/worker.php every minute using the same private configuration. The nginx.example.conf and platform app profile are supplied templates, not ready-to-use credentials.
04What to configure & test+
OAuth owner validation, signed load/uninstall callbacks and queued order/customer/shipment webhook handling. Webhook setup and the supplied storefront customer-verification integration must be checked in the sandbox. Marketplace publication is a separate step.
05Activation & connection+
Open WASMS → My licenses, select this product and download the matching archive. Enter its activation code in the plugin License section; the configured site URL is its one-site identity. In Connection save your own WASMS API key and connected WhatsApp device ID. Keep messaging disabled and test mode enabled until configuration is checked. Sending requires wa_send; number registration checks require validate_wa_phone. Normal WASMS plan limits and usage charges apply.
06Cloud API & Copy code (optional)+
For supported OTP flows, open WASMS account → Cloud API and enter your own Meta access token, WhatsApp Business Account ID, phone number ID and approved AUTHENTICATION / COPY_CODE template for the intended language. Verify that profile, then select Cloud API for OTP delivery in plugin Connection settings. A linked device alone cannot create the native Copy code card. Keep the existing sender until the Cloud profile is verified; this does not enable a native login factor on platforms that do not include one.
07First test & everyday use+
Start on a CMS test installation or a WASMS test workspace. Choose Arabic (RTL) or English (LTR), save one template and confirm its supported merge fields. Check permissions, license/entitlement and the worker heartbeat. Test mode should create no real delivery. When ready, use one recipient you control who has agreed to receive the test. Enable only the needed event and confirm receipt on the phone. Check duplicate events, opt-out and failed credentials before expanding automation.
08Troubleshooting & safe updates+
Queued: check the worker, PHP executable, permissions and connection. Accepted: the request was accepted, not proof of phone delivery. Unknown: inspect the original request before retrying. For license errors check the product and canonical site URL. Before updates back up files/database and preserve private configuration and encryption secrets. Disable messaging and pause the worker before rollback; restore the matching files and database together. Do not erase customer data during a routine update. Send support the platform/PHP version and a redacted error, never API keys or OTPs.
09Installation & activation+
This is a hosted-app deployment kit, not a marketplace listing. Deploy the PHP app behind HTTPS, keep private configuration outside the web root, configure your BigCommerce app credentials and exact callback URLs, then authorize the target store.

After verified purchase, open My licenses on WASMS. Download the matching package, copy your activation code and enter it in the plugin’s License section. Activation binds to its configured site URL.

In Connection settings, save your WASMS API key and WhatsApp device unique ID. Keep test mode enabled while reviewing. wa_send is needed for sending; validate_wa_phone is needed for number checks.

Configure your platform’s scheduled worker. For WHMCS use Configurations → Queue cron → Install cron, while keeping the native WHMCS billing cron. Check the heartbeat before enabling automatic notifications.
10Send your first message+
Use an opted-in test recipient and an international number such as +9665xxxxxxxx. Confirm the connected device is online, enable messaging, and turn test mode off only when ready. In WHMCS, Send to number → Send immediately dispatches that message directly; bulk messages use the queue. Check Logs and confirm receipt on the phone.
11Templates, language & emoji+
Choose a section and event, enable it, select an Arabic or English preset and edit the text. Keep the supported merge fields unchanged. The toolbar inserts WhatsApp formatting; preview can vary on the recipient’s device. Select emoji by name or paste Unicode emoji. Save and test one event before enabling the next.
12Queued, accepted or unknown?+
Queued means waiting for a worker. Check its cron command, PHP executable, heartbeat and connectivity. Accepted means WASMS accepted the request, not proof of delivery. Unknown means transport confirmation was unavailable; check the original request before manually resending to avoid duplicates. Test mode performs no real delivery.
13Move a license to another site+
Back up and disable the old installation. Open WASMS → My licenses → Reissue activation, confirm the site move, then copy the new code into the new installation. The old code and installation token are revoked. Existing validated installations refresh every five minutes and stop no later than the one-hour cached lease. Customer reissue is limited to once per hour; administrators can assist.
14Verification & optional WHMCS 2FA+
Phone ownership, WhatsApp registration and notification consent are separate states. WHMCS optionally provides WASMS WhatsApp 2FA for clients/admins: code validity 1–15 minutes (default 6), attempts 1–10 (default 5), and rate window 1–60 minutes (default 60). Complete native enrollment and retain the native recovery code. Existing factors are not migrated automatically.
15Shipping, guest checkout & contacts+
Shipping updates require tracking data from the platform or a carrier extension. WHMCS shipping uses doiteasy_wasms_shipping_notify. WHMCS guest-order verification enforcement and secondary-contact fan-out are not included in this release. Platform-specific commerce events do not exist on a plain WordPress site without the relevant commerce plugin.
16Updates, compatibility & support+
This is an unencoded review release. Native installation has been tested on WHMCS 8.11.2 / PHP 8.2.34; WHMCS 7/9 and the other platform installations still need native testing. Select the matching archive and test on staging before replacing files. Keep your host encryption secret and private configuration. ionCube-encoded packages are not yet available. Contact support@doiteasy.net with version and a redacted error; never include API keys or OTPs.
Purchases are awaiting completion of the seller’s e-invoicing setup. You can review checkout, but no payment or license is issued until verified live payment succeeds.
CUSTOMER RATINGS

Your experience matters.

Reviews from verified purchasers. New and edited reviews are moderated before publication.

—☆☆☆☆☆0 reviews

Be the first to review this plugin after your purchase.

Sign in with a purchased license to review

Published versions

Matching licensed packages are available from My licenses.

VersionProfileCompatibilityUpdated
0.3.0-rc1defaultHosted integration kit · PHP 8.1+ · deployment test required2026-10-24