WooCommerce + WhatsApp Integration for India

Connect with REST API keys, and let WatEase subscribe to the webhooks

Setup is a paste, not a plugin install: enter the store address and a WooCommerce REST API consumer key and secret (WooCommerce → Settings → Advanced → REST API), and WatEase validates the connection before it goes live. It then registers exactly six webhook subscriptions on the store — order created, updated and deleted; product created, updated and deleted — pointed at a tenant-specific endpoint. Deliveries are signed by WooCommerce and verified before a byte of the payload is decoded, so a forged post never touches an order.

WatEase does not subscribe to customer webhooks, on purpose. WooCommerce sends a full billing address for every account holder on that topic, and no feature needs one it did not already receive with an order — so the integration does not hold personal data it has no use for. If a store's webhook subscriptions are removed or break, a repair action re-creates them from the dashboard, and disconnecting removes the ones WatEase created.

Products and orders mirror in, whether or not the webhook arrives

Webhooks are not a delivery guarantee, and on WooCommerce the server sending them is the merchant's own: shared hosting drops them under load, a security plugin blocks the request, or the store gives up after a few retries. So WatEase also runs a catch-up pull on a schedule — every store is swept for anything modified since its last clean pass, with a ten-minute overlap so an order written during clock skew is never missed. Orders are pulled in every status, including cancelled and refunded, because those are exactly the transitions that must stop a fulfilment or a customer message.

Products come across with their variations, prices and stock status, and a product a merchant trashes in WooCommerce stops being sellable in WatEase. Which side owns the catalog is a setting: with WooCommerce as the system of record WatEase mirrors it and refuses local catalog edits; with WatEase as the record the flow reverses and products, variations, sale prices and stock are pushed out to the store instead.

Orders taken on WhatsApp are written back into the store

An order the AI agent takes in a WhatsApp conversation, or that a customer places on the WatEase storefront, is created in WooCommerce as a real order — line items, totals, the customer's contact details and any note — so the team that picks and packs out of WooCommerce sees it in the same queue as the storefront orders. Every publish leaves a ledger row before and after, and a publish that fails because the store was down is retried automatically by the next sweep; a sale can never silently go missing from the merchant's book of record.

Order state flows the other way too. When WatEase marks an order shipped, the WooCommerce order moves to completed with the carrier and tracking number attached as a customer note, which is what WooCommerce emails the buyer. When a WatEase order is cancelled, the store order is cancelled with a private note for the fulfilment team, so nobody ships a parcel the customer already cancelled.

Every delivery is logged, and every failure can be replayed

The dashboard keeps a per-delivery log of every webhook the store sent — topic, outcome and timing — with a retry for any that failed, plus the sync history and the last error for the catch-up pull. When orders stop arriving (the failure mode on a merchant-hosted platform is silence, not an error) the log says whether the store stopped sending, the signature stopped verifying, or a payload could not be applied, and the repair and retry actions fix each without a support ticket.