Support from the Bridgo Team

Search here to get answers to your questions

Connecting WooCommerce with Bridgo

Table Of Contents

The WooCommerce Integration connects your WooCommerce store with Bridgo, so store events can trigger WhatsApp transactional messages automatically.

Use this integration to send WhatsApp updates for new orders, cash on delivery orders, order status changes, refunds, failed orders, and abandoned carts.

📍 Where to Enable WooCommerce Integration #

Go to:

Settings → WhatsApp Settings → Integration → WooCommerce Integration

From this section, you can:

  • Enable or disable WooCommerce integration
  • Generate a WooCommerce API key
  • Rotate an existing key
  • Revoke WooCommerce access
  • Download the Bridgo WooCommerce plugin
  • Open the WooCommerce report
  • Copy Company ID and API URL
  • Configure WooCommerce Event Rules

🔐 Before You Start #

Before connecting WooCommerce, make sure:

  • WooCommerce Integration is enabled in Bridgo.
  • Your subscription plan supports WooCommerce.
  • Your WhatsApp account is configured and active.
  • You have created the transactional templates you want to send.
  • You have generated a WooCommerce API key.
  • You downloaded the Bridgo WooCommerce plugin.

The plugin uses the API key as:

Authorization: Bearer <key>

The key is shown only once. If you lose it, rotate or generate a new one.

🔑 Step 1: Generate a WooCommerce API Key #

  1. Open WhatsApp Settings.
  2. Go to the Integration tab.
  3. Find WooCommerce Integration.
  4. Turn the integration on.
  5. Click Generate API Key.
  6. Copy the key immediately.
  7. Store it securely.

Important:

  • The key is shown only once.
  • Rotating the key revokes the old key immediately.
  • Revoking the key disables WooCommerce plugin access.
  • The key is stored securely and cannot be viewed again later.

⬇️ Step 2: Download the WooCommerce Plugin #

In the WooCommerce Integration section, click:

Download Plugin

Install the plugin in your WordPress/WooCommerce store.

The plugin is used to send WooCommerce events to Bridgo through the WooCommerce API endpoint.

⚙️ Step 3: Configure the Plugin #

In Bridgo, copy these values from the WooCommerce Integration section:

  • Company ID
  • API URL
  • WooCommerce API Key

Then open your WooCommerce plugin settings and paste the required values.

The plugin uses these values to:

  • Authenticate with Bridgo
  • Register the store
  • Test the connection
  • Fetch transactional templates
  • Send WooCommerce events

🧪 Step 4: Test the Connection #

The plugin can test the connection with Bridgo.

When the connection is successful, Bridgo returns details such as:

  • Company ID
  • Store URL
  • Store name
  • Server UTC time
  • Event endpoint
  • Register store endpoint
  • Transactionals endpoint

If the test fails, check the API key, Company ID, and API URL.

🏪 Step 5: Register the Store #

The plugin can register your WooCommerce store with Bridgo.

Store registration sends details such as:

  • Company ID
  • Store URL
  • Store name
  • Admin email
  • WooCommerce/WordPress version
  • Plugin version
  • Webhook secret hint

Bridgo verifies that the Company ID matches the authenticated WooCommerce API key before saving the store connection.

🧾 Step 6: Configure WooCommerce Event Rules #

In Bridgo, go to:

WhatsApp Settings → Integration → WooCommerce Event Rules

Each event can be enabled or disabled and linked to a transactional message.

For each rule, configure:

  • Enable/disable event
  • WooCommerce event
  • Transactional template/message

Click Save WooCommerce Rules after updating the rules.

📣 Supported WooCommerce Events #

WooCommerce can send the following events to Bridgo:

  • order.created
  • order.created.cod
  • order.status.pending
  • order.status.on-hold
  • order.status.processing
  • order.status.completed
  • order.status.cancelled
  • order.status.failed
  • order.status.refunded
  • cart.abandoned

🛍️ New Order #

Event:

order.created

Use this event to send a WhatsApp message when a new order is placed.

Example use cases:

  • Thank the customer for the order
  • Confirm that the order was received
  • Share the order number and total
  • Tell the customer what happens next

💵 Cash on Delivery Order #

Event:

order.created.cod

Use this event when an order is created with cash on delivery payment.

Example use cases:

  • Confirm COD order placement
  • Remind the customer to prepare payment
  • Send delivery instructions
  • Confirm the customer’s phone number

⏳ Pending Order #

Event:

order.status.pending

Use this event when an order status becomes pending.

Example use cases:

  • Notify the customer that payment is pending
  • Ask the customer to complete checkout
  • Send support instructions if the payment failed

🟡 On-Hold Order #

Event:

order.status.on-hold

Use this event when an order is placed on hold.

Example use cases:

  • Notify the customer that the order is waiting for confirmation
  • Explain that a payment/manual review is needed
  • Share support contact details

🔄 Processing Order #

Event:

order.status.processing

Use this event when an order moves to processing.

Example use cases:

  • Tell the customer the order is being prepared
  • Share expected fulfillment timing
  • Confirm that the order is moving forward

✅ Completed Order #

Event:

order.status.completed

Use this event when an order is completed.

Example use cases:

  • Thank the customer
  • Send completion confirmation
  • Ask for feedback
  • Share after-sales support information

❌ Cancelled Order #

Event:

order.status.cancelled

Use this event when an order is cancelled.

Example use cases:

  • Notify the customer about cancellation
  • Explain the next steps
  • Invite the customer to reorder or contact support

⚠️ Failed Order #

Event:

order.status.failed

Use this event when an order fails.

Example use cases:

  • Notify the customer that payment/order processing failed
  • Ask the customer to try again
  • Send support instructions

↩️ Refunded Order #

Event:

order.status.refunded

Use this event when an order is refunded.

Example use cases:

  • Confirm that the refund was processed
  • Share refund timing
  • Provide support contact details

🛒 Abandoned Cart #

Event:

cart.abandoned

Use this event when a customer leaves products in the cart without completing checkout.

Important:

  • Abandoned cart messages require consent.
  • If consent is missing or denied, Bridgo skips the message.
  • The event must include a valid phone number or business-scoped user ID.

Example use cases:

  • Remind the customer to complete checkout
  • Send cart recovery message
  • Offer support if they had checkout issues

📩 Transactional Template Lookup #

The WooCommerce plugin can fetch available transactional messages from Bridgo.

This helps the plugin or setup flow display valid transactional options.

The lookup returns:

  • Transactional ID
  • Transactional name

Use these IDs when linking WooCommerce events to transactional messages.

🧩 WooCommerce Placeholder Values #

When Bridgo sends a WooCommerce transactional message, it can pass WooCommerce data as custom placeholders.

Available WooCommerce placeholders include:

  • {{WooCommerce.OrderId}}
  • {{WooCommerce.OrderNumber}}
  • {{WooCommerce.OrderStatus}}
  • {{WooCommerce.PaymentMethod}}
  • {{WooCommerce.PaymentMethodTitle}}
  • {{WooCommerce.Currency}}
  • {{WooCommerce.OrderTotal}}
  • {{WooCommerce.RefundAmount}}
  • {{WooCommerce.CustomerFirstName}}
  • {{WooCommerce.CustomerLastName}}
  • {{WooCommerce.CustomerEmail}}
  • {{WooCommerce.CustomerCountry}}
  • {{WooCommerce.BusinessScopedUserID}}
  • {{WooCommerce.WhatsAppUsername}}
  • {{WooCommerce.CartToken}}
  • {{WooCommerce.StoreName}}
  • {{WooCommerce.StoreUrl}}

Use these placeholders inside transactional messages to personalize WooCommerce notifications.

📦 What Happens When WooCommerce Sends an Event #

When WooCommerce sends an event to Bridgo:

  1. Bridgo authenticates the request using the WooCommerce API key.
  2. Bridgo verifies that the Company ID matches the authenticated tenant.
  3. Bridgo checks whether the event type is supported.
  4. Bridgo logs the incoming event.
  5. Duplicate events are detected using the source event ID.
  6. Bridgo normalizes customer, order, cart, payment, and consent data.
  7. Bridgo checks whether the customer can receive the message.
  8. Bridgo finds the matching WooCommerce Event Rule.
  9. Bridgo sends the linked transactional WhatsApp template.
  10. The event log is updated as sent, skipped, failed, or queued for retry.

🧪 Example WooCommerce Workflows #

Example 1: New Order Confirmation #

  1. WooCommerce event: order.created
  2. Bridgo rule: enabled
  3. Transactional: Order Confirmation
  4. Customer receives a WhatsApp message with the order number and total

Example 2: COD Order Reminder #

  1. WooCommerce event: order.created.cod
  2. Bridgo rule: enabled
  3. Transactional: Cash on Delivery Confirmation
  4. Customer receives WhatsApp instructions for COD payment

Example 3: Order Completed Message #

  1. WooCommerce event: order.status.completed
  2. Bridgo rule: enabled
  3. Transactional: Order Completed
  4. Customer receives confirmation and thank-you message

Example 4: Abandoned Cart Recovery #

  1. WooCommerce event: cart.abandoned
  2. Customer consent is granted
  3. Bridgo rule: enabled
  4. Transactional: Abandoned Cart Reminder
  5. Customer receives a WhatsApp cart recovery message

📊 WooCommerce Report #

The WooCommerce Integration section includes an Open Report button.

Use this report to review WooCommerce integration activity, such as received events and dispatched outcomes.

The event processor can mark events as:

  • Mapped
  • Skipped because consent was not granted
  • Failed validation
  • Skipped because no matching rule exists
  • Dispatching
  • Sent
  • Failed dispatch

⚠️ Common Issues #

Plugin Connection Fails #

Check that:

  • WooCommerce Integration is enabled in Bridgo.
  • The API key is correct.
  • The key has not been revoked.
  • The Company ID is correct.
  • The API URL is copied correctly.
  • Your subscription plan supports WooCommerce.

Store Registration Fails #

Check that:

  • The Company ID in the plugin matches the Bridgo Company ID.
  • The API key belongs to the same company.
  • The store URL and store name are valid.
  • The plugin can reach the Bridgo API URL.

Event Is Rejected #

Possible reasons:

  • Unsupported event name
  • Missing source_event_id
  • Company ID mismatch
  • Invalid or missing API key
  • Integration disabled

WhatsApp Message Is Not Sent #

Check that:

  • The WooCommerce event rule is enabled.
  • A transactional message is selected for that event.
  • The customer has a valid phone number or business-scoped user ID.
  • The WhatsApp template is approved and active.
  • For abandoned cart events, consent is granted.
  • The WhatsApp account credentials are valid.

Abandoned Cart Message Is Skipped #

Abandoned cart events require opt-in consent.

The event may be skipped if consent is:

  • Missing
  • Denied
  • Not granted

No Rule Matched #

This means Bridgo received the event, but no active WooCommerce Event Rule matched it.

Go to:

WhatsApp Settings → Integration → WooCommerce Event Rules

Then enable the event and select a transactional message.

🧠 Best Practices #

  • 🔐 Store WooCommerce API keys securely.
  • 🔁 Rotate keys if they may have been exposed.
  • ❌ Revoke unused keys.
  • 🧪 Test the plugin connection after setup.
  • 📩 Create transactional templates before configuring event rules.
  • ✅ Enable only the WooCommerce events you actually want to send.
  • 🛒 Use abandoned cart messages only when customer consent is granted.
  • 📱 Use valid international phone numbers where possible.
  • 📊 Review the WooCommerce report after launch.
  • 🧾 Include order number, status, and total in customer messages.
  • 🚦 Avoid enabling too many event messages at once without testing.

✅ Summary #

The WooCommerce Integration connects your store to Bridgo so WooCommerce events can automatically send WhatsApp transactional messages.

You can generate a secure API key, install the Bridgo WooCommerce plugin, register the store, configure event rules, and send messages for orders, status changes, refunds, failed orders, and abandoned carts.

What are your feelings

Updated on May 31, 2026