WASMS · WooCommerce
Install. Connect. Make it yours.
Your WooCommerce 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
Activate WooCommerce, then install the WASMS ZIP through WordPress Plugins. Open Settings, Doiteasy WASMS. Do not install a second WordPress WASMS copy.
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+
Package header requires WordPress 6.8+ and PHP 8.1+. Use a staging site and the PHP/database versions supported by that WordPress release. Native installation testing is pending.
Your shared control center

02Install & open your product+
Activate WooCommerce first. Install the downloaded ZIP through WordPress Plugins → Add New → Upload Plugin. Use Settings → Doiteasy WASMS. Do not install a second WordPress WASMS copy. With WooCommerce active, activate a WooCommerce license for the site. Test both your actual checkout type and order storage mode.
03Scheduled sending & reminders+
Activation schedules doiteasy_wasms_tick every minute using WP-Cron. Traffic-driven WP-Cron may be delayed on quiet sites. For reliable timing, have your host run WordPress due cron events every minute using the normal site user, then verify the WASMS heartbeat. Do not disable WP-Cron until its replacement is working.
04What to configure & test+
Order created/status, payment, refund and supported shipment tracking updates; classic and block checkout consent, HPOS-aware order access and account verification. Tracking requires saved carrier/tracking data or doiteasy_wasms_shipping_update. It does not fetch carrier status by itself.
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
