Setting Up WhatsApp Order Status Notifications in 1C-Bitrix
Imagine: a customer places an order at 11:00 PM, expects confirmation, but no notification arrives. In the morning, they call and find out the order was canceled because there was no confirmation.
Or even worse — the order has already been assembled and shipped, but the customer canceled it because they didn't wait for the status. Such situations lead to lost trust and lost repeat sales.
Automatic notifications solve this problem, but setting them up in 1C-Bitrix requires understanding internal mechanisms: the event model, agents, caching, and integration with external APIs.
We often encounter this situation: a customer places an order but does not receive confirmation. The result is lost leads and support calls. Setting up WhatsApp push notifications for an online store on 1C-Bitrix is a task with hidden pitfalls.
WhatsApp has no official bot, and unofficial gateways can get a number blocked. We will explain how we solve this problem reliably and with minimal costs.
How to Choose an Integration Method for Notifications?
There are two paths: the official WhatsApp Business API (via Meta or a BSP) and unofficial gateways based on WhatsApp Web (Green API, Chat-api, etc.). The choice depends on volume, delivery criticality, and budget. Below is a comparison of key parameters.
| Parameter | WhatsApp Business API (Meta) | Green API (unofficial) |
|---|---|---|
| Delivery reliability | High, guaranteed by Meta | Medium, possible blocks |
| Launch speed | 3–5 business days (verification, templates) | 4–8 hours (minimum integration) |
| Cost | Per outgoing message | Fixed subscription + number of messages |
| Legal compliance | Fully legal | Risk of violating WhatsApp TOS |
| Message customization | Only approved templates | Any text, dynamic formatting |
For small businesses (< 500 messages/day), Green API is a workable option. For large stores with delivery guarantees, only WhatsApp Business API will do.
The official API ensures delivery in 99.8% of cases versus 95% for unofficial gateways — this is especially critical when processing returns and cancellations.
Why Shouldn't Unofficial Gateways Be Used for Large Volumes?
Meta strictly monitors misuse of WhatsApp Web. If limits are exceeded or users complain, the number is blocked without warning. We have seen projects where a business lost access to its audience of 5,000+ people in one day. Meta recommends using official Business API for automated messaging.
How Did We Set Up Notifications for an Auto Parts Store? (Case Study)
From our practice: implementation for an online auto parts store with a catalog of 50,000 products. We chose the official WhatsApp Business API via Twilio because order volume is 200–300 per day. The setup included:
- Business verification in Meta (we provided a tax identification number and contracts).
- Creating 5 message templates: accepted, confirmed, handed to delivery, completed, canceled.
- Integration with 1C-Bitrix via the OnSaleOrderStatusChange event handler.
- Formatting phone numbers (conversion to the 79XXXXXXXXX format).
- Logging sends to a high-load table.
Result: time from order to notification is less than a second, delivery failures are 0.2%. Thanks to tagged caching and agent optimization, server load did not increase.
What Is Included in Notification Setup Work?
- Audit of the current 1C exchange and order structure.
- Selection and connection of a suitable gateway (WhatsApp Business API / Green API).
- Development of an event handler with filtering by statuses.
- Creation of message templates (for the official API — with Meta moderation).
- Setting up logging and monitoring of sends.
- Testing: sending test orders through all statuses.
- Documentation: integration diagram, access rights, instructions for adding new statuses.
- Post-release support: 2 weeks of maintenance (bug fixing, optimization).
Work Process
- Analytics — we study your 1C exchange, order properties, and current statuses.
- Design — we select the gateway, design templates, and define triggers.
- Implementation — we write the handler code, integrate the API, and configure logs.
- Testing — we run scenarios: new order, payment, cancellation, return.
- Deployment — we roll out to production and check under load.
Approximate Timeframes
| Scenario | Timeframe |
|---|---|
| Green API (unofficial) | from 4 hours |
| WhatsApp Business API (verification + templates) | from 3 to 5 business days |
Cost is calculated individually; it depends on complexity and the chosen gateway. We provide an estimate after an audit.
Why Choose Us
- 5+ years of experience in 1C-Bitrix development.
- More than 100 successful integrations with external APIs.
- Certified Bitrix specialists (1C-Bitrix certificates).
- Transparent reports: weekly calls, demonstration of results.
Common Mistakes During Self-Setup
- Incorrect phone number formatting (missing country code or the @c.us symbol).
- No handler for the 'return' status — the client receives outdated data.
- Using one template for all statuses — a violation of Meta policy.
- No Redis/Memcached — when sending 100+ notifications simultaneously, agents hang.
Contact us for an audit of your store. Get a consultation based on your catalog and order volume.