PPS Order Notifier for WhatsApp: settings reference
Updated November 10, 2026
Configure order notifications under WooCommerce > Settings > WhatsApp Notifier with manage_woocommerce. Save changes after configuring a provider, credentials and templates. Verify provider acceptance and customer consent separately before sending messages.
Release in preparation. This reference is not confirmation of download or Pro purchase availability.
Where to configure it
Free supplies the WhatsApp Notifier settings tab, consent/account controls, chat link and WooCommerce > WhatsApp Logs. Pro appends Twilio and optional COD confirmation to the same settings form. There is no global notification enable switch, test-send button, template-ID selector, product editor or custom post type.
Gateway, chat and credentials
All fields below are on the WhatsApp Notifier settings tab. Password inputs always render blank, including after a token is saved. Leave blank to preserve a token; enter a fresh token to replace it. Do not paste stored ciphertext into them. Tokens use the site's existing AUTH_KEY-based helper, not an external vault or security certification; key changes can require re-entry.
| Field | Default / accepted value | Save and runtime effect | Access |
|---|---|---|---|
| Active Gateway (pps_whatsapp_active_gateway) | meta; meta or ultramsg, plus twilio under approved Pro | Chooses the sender at execution time. Missing/unconfigured/unsupported gateways refuse sending. Changing configuration invalidates queued payload stamps. | Free; Twilio Pro |
| Enable Chat Widget (pps_whatsapp_enable_chat_widget) | no/off | Checkbox yes/no. Requires a nonempty phone. This opens a link, not an API send. | Free |
| Chat Widget Phone (pps_whatsapp_chat_widget_phone) | Blank; international phone | Used for the wa.me link. Blank removes useful chat output. | Free |
| Chat Widget Pre-filled Message (pps_whatsapp_chat_widget_message) | Hello, I have a question. | Plain text encoded into the chat URL. | Free |
| Phone Number ID (pps_whatsapp_meta_phone_id) | Blank | Meta sender identifier, not the displayed phone number. Required with a token for Meta sending. | Free |
| Access Token (pps_whatsapp_meta_token) | Blank input; blank preserves stored token | Nonempty replacement goes through the credential save hook and unified settings copy. Never sent to the storefront. | Free |
| Instance ID (pps_whatsapp_ultramsg_instance) | Blank | Required UltraMsg instance identifier. | Free |
| Token (pps_whatsapp_ultramsg_token) | Blank input; blank preserves stored token | Provider credential, replaced only by nonempty input. | Free |
| Twilio Account SID (pps_whatsapp_twilio_sid) | Blank | Required with token and WhatsApp sender for Twilio. | Pro |
| Twilio Auth Token (pps_whatsapp_twilio_token) | Blank input; blank preserves stored token | Uses the same credential-only replacement boundary, not ordinary populated password saving. | Pro |
| Twilio WhatsApp Sender (pps_whatsapp_twilio_sender) | Blank; whatsapp:+1234567890 | Provider sender value. Configuration is not proof that the provider accepts it. | Pro |
Status messages
Only the three listed status templates send ordinary notifications. Blank disables that status. Unknown statuses do not receive a generic fallback message. Edit the completed template's shipping wording to match your own process; a completed order is not carrier dispatch evidence.
| Field | Default | Accepted input and effect | Access |
|---|---|---|---|
| Processing Order (pps_whatsapp_template_processing) | Hello {first_name}, your order #{order_id} at {store_name} is now processing. Total: {order_total} | Plain multiline message; blank disables. | Free |
| Completed Order (pps_whatsapp_template_completed) | Great news {first_name}! Your order #{order_id} has been completed and shipped. | Plain multiline message; blank disables. | Free |
| Cancelled Order (pps_whatsapp_template_cancelled) | Hi {first_name}, unfortunately your order #{order_id} has been cancelled. | Plain multiline message; blank disables. | Free |
Supported substitutions include {order_id}, {first_name}, {order_status}, {order_total}, {payment_method}, {billing_email} and {store_name}; unknown placeholders stay literal. These are text-message fields, not provider-approved template-message IDs.
Checkout, account and shortcodes
Classic checkout displays Receive order updates via WhatsApp, initially unchecked, storing the order's yes/no opt-in. My Account > WhatsApp Preferences has a separate initially unchecked preference and Save changes with a login/nonce check. An explicit account no overrides an order yes; otherwise an order or account yes permits the ordinary message. Historical order metadata is not rewritten by account changes. Send time rechecks current consent, order/customer/phone/status, gateway configuration and payload authority; a later opt-out can drop queued work.
| Example | Attributes and effect |
|---|---|
| [pps_waon_optin] | No supported attributes. Prints the checkout opt-in only on checkout. Avoid duplicating the existing hook's checkbox. |
| [pps_waon_chat_widget] | No supported attributes. Uses global enabled/phone/message settings. Avoid duplicate placement beside automatic footer output. |
| [pps_whatsapp_cod_otp_form] | Pro, no attributes. On a page with an order_id query parameter, shows only for the signed-in owner of an eligible pending COD order with a current challenge. It is not a login or ownership bypass. |
The fixed bottom-right Chat with us link has no color, position, label or schedule editor. It opens WhatsApp with the configured phone/message and does not use gateway credentials.
COD confirmation (Pro)
These fields are on the same settings tab, under COD OTP Verification. Abandoned-cart automation and its former settings are removed/unsupported. There is no tokenized abandoned-cart recovery, guest COD confirmation, new resend service or automatic verification-page redirect.
| Field | Default / accepted input | Runtime effect | Access |
|---|---|---|---|
| Enable COD OTP Verification (pps_whatsapp_enable_cod_otp) | no/off; checkbox | Current permission, enabled setting, pending positive-total COD order, signed-in ownership, consent, valid phone/provider and configured message are all required. | Pro |
| Verify Message (pps_whatsapp_cod_otp_message) | Thank you for your order! Your Cash-on-Delivery verification OTP is: {otp}. Please enter this on the website to confirm your order. | Plain multiline text; {otp} must be present or the flow refuses. Blank does not create a challenge. | Pro |
The issued code is six digits, valid for five minutes, with five failed attempts and a 60-second issuance cooldown. These are fixed source limits, not editable settings. The verification input starts blank, requires six digits and Confirm order submits it with the form nonce. The server rechecks current order ownership/status/phone/template/expiry/attempts and compares a bound hash. A valid code consumes challenge state, changes the order to processing and redirects to its received-order URL. Merely opening the form or retrying native payment does not verify anything.
Expired/locked/malformed challenges retain the existing COD order status on native payment retry while the feature and permission remain active. Pending stays pending and a merchant's failed/status decision is not silently overwritten. Missing challenge state is not proof that an eligible pending owner verified. Guest orders never challenged retain native behavior. Turning OTP off or losing permission restores native Woo payment behavior rather than imposing an independent permanent hold. Merchant handling or the existing authorized issuance flow is needed when a code is unusable; no complete anti-fraud, concurrent-request or provider-delivery guarantee is made.
Sending and logs
One queue/sender accepts structured versioned payloads. Legacy positional jobs, zero/missing orders, stale configuration or revoked consent are refused. Pro non-status messages require explicit current authorization. Action Scheduler queues when available; otherwise the sender path is immediate. A short duplicate guard is not exactly-once delivery. Retry behavior belongs to the actual queue and error path; there is no editable exponential-backoff/retry policy.
WooCommerce > WhatsApp Logs shows 20 rows per page, newest first, with ID, order, phone, status, gateway and date; supported sorting is allowlisted. There is no test-send, details, retry, delete, export, search or retention control. Error bodies and credentials are not copied into log details. A provider message ID/accepted response is not proof of receipt or reading.
The configured Meta endpoint targets Graph API v27.0; that version target alone does not confirm message acceptance. The complete current WhatsApp message contract, merchant eligibility, template/window policies, credentials and actual request acceptance/delivery remain unverified. UltraMsg/Twilio likewise need separate provider acceptance. Selecting a gateway or entering credentials cannot establish it.
Troubleshooting
Save the selected gateway and credentials, ensure the specific status template is nonblank, check the formatted international billing phone and current order/account consent, then inspect the existing Scheduled Actions and logs. A dropped stale/opted-out job is not a successful send.
Disable or roll back safely
Turn off chat to stop future chat links and turn off COD OTP before changing that workflow. Blank the relevant status templates to disable ordinary statuses, or deactivate the listener/worker. Deactivation cannot recall sent messages, undo order changes or erase stored jobs. Review queued work and logs separately. Uninstall is not a reversible privacy reset and does not establish deletion of all order/user consent or external copies.
Services and data
Meta receives recipient phone and rendered message at graph.facebook.com; UltraMsg uses api.ultramsg.com; approved Pro can use api.twilio.com with its configured sender. Jobs contain message/order/customer/phone authority and can include a live code. Logs contain operational phone/order/provider data. Chat-link clicks send phone/message to WhatsApp. Keep tokens, codes, verification URLs and personal order content out of public screenshots. Freemius account/license/update traffic is separate. No provider, delivery, privacy, security, legal or commercial acceptance is claimed.
Related documentation
Setup: https://propluginstack.com/docs/whatsapp-order-notifier-setup-reference/
Changelog: https://propluginstack.com/changelog/whatsapp-order-notifier-source-changelog/