Documentation

Requirements

• PHP 8.1 or newer
• WooCommerce 7.0 or newer
• HTTPS and outbound access to your provider
• A configured WhatsApp provider account

Install and license

1. Download the latest ZIP from your Emargy account.
2. Upload it through Plugins → Add New Plugin → Upload Plugin.
3. Activate the plugin.
4. Open WooCommerce → WhatsApp Notify → License and activate the key for this domain.

1. Choose a provider and enter only the credentials required by that provider.
2. Enable owner notifications first and use a phone number you control.
3. Select only the new-order event and review the template.
4. Save settings and use the built-in provider test where available.
5. Place a test WooCommerce order and inspect the notification log.
6. Only then enable customer events that match your consent process and approved WhatsApp templates.

Provider success does not guarantee final handset delivery. Confirm the result in your provider dashboard.

Supported provider paths

• WhatsApp Cloud API — Meta phone-number ID, access token, business account ID, and Graph API version.
• WazaTool — base URL, API token, approved template names, language, optional header and footer.
• OpenWA — server URL, session ID, and API key.
• Custom webhook — endpoint and API key receiving the plugin JSON payload.

Messages and phone numbers travel directly from your store to the selected service. Review that service’s terms, privacy policy, data location, pricing, and WhatsApp compliance requirements before enabling customer sends.

Owner and customer notifications are configured independently. Events can cover new orders and WooCommerce status transitions such as processing, completed, cancelled, failed, and refunded.

Message placeholders include order ID, customer details, total, payment method, status, store name, and the admin order URL where appropriate. WazaTool customer sends can map events to approved business template names and parameters.

Do not place credentials or sensitive payment data in a message template.

Order hooks enqueue delivery through WooCommerce Action Scheduler. If it is unavailable, a single WordPress cron event processes the notification. Successful event-recipient pairs are marked on the order so repeated hooks do not resend them.

Operational logs mask destination phone numbers, redact common secret fields, omit payload previews, and limit response text. Daily cleanup removes logs older than 30 days.

For dependable timing, configure a real server cron for WordPress and review WooCommerce Scheduled Actions for failed work.

No notification arrives

1. Confirm the plugin and intended recipient type are enabled.
2. Verify that the order event is selected.
3. Check WooCommerce Scheduled Actions and the plugin log.
4. Test credentials and destination formatting with the provider.
5. Confirm the business template is approved for business-initiated customer messages.

An update is not offered

Confirm the license is active on the exact domain, then ask WordPress to check for updates again. Contact [email protected] with the plugin version, provider name, event, and redacted log result.