WASMS · BigCommerce
Install. Connect. Make it yours.
Your BigCommerce installation and use guide.
A guided look inside.
Six short steps through the actual WASMS interface. English on-screen captions, a full transcript and demonstration data. No narration.
1 minute · English captionsShared plugin screens vary by platform. Native installation steps remain in the written guide. No messages were sent while creating this walkthrough.
English transcript & chapters
This is a hosted BigCommerce integration kit. Deploy its private configuration and worker first, then complete the app installation for your test store.
Enter your own WASMS API key and WhatsApp device ID in Configurations. Keep test mode enabled during setup. Normal WASMS plan limits and usage charges apply.
Open Management, select one supported event and edit its English or Arabic template. Confirm the supported merge fields before enabling notifications.
Open the composer and inspect the recipient and message preview. Screens use fictional demonstration data; no real messages are sent in this walkthrough.
Use Logs to inspect pending, accepted and failed requests. Accepted is not proof of phone delivery. Investigate an unknown outcome before retrying.
Follow the written guide for license activation and your platform worker. Native CMS installation and a controlled delivery test are still required before live use.
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.
Your shared control center

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.
Choose an event template

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.
Connection and test mode

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.
Preview a message before sending

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.
Read delivery states correctly
