Setting Up Order Status Notifications in WhatsApp for 1C-Bitrix
Imagine: a customer places an order at 23:00, expects confirmation, but no notification arrives. In the morning, they call and find out the order was canceled due to lack of confirmation.
Or worse — the order has already been assembled and shipped, and the customer canceled it because they didn't receive the status. Such situations lead to loss of trust and 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 a situation: a customer places an order but does not receive confirmation. The result is lost leads and support calls. Setting up push notifications in WhatsApp for an online store on 1C-Bitrix is a task with pitfalls.
WhatsApp has no official bot, and unofficial gateways can get a number blocked. We'll 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, Meta guarantee | Medium, blocks possible |
| Launch speed | 3–5 business days (verification, templates) | 4–8 hours (minimal integration) |
| Cost | Per each outgoing message | Fixed subscription + number of messages |
| Legal cleanliness | 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 that need guaranteed delivery, 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 You Use Unofficial Gateways 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 a single 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 the order volume was 200–300 per day. The setup included:
- Business verification in Meta (provided TIN and contracts).
- Creation of 5 message templates: accepted, confirmed, handed to delivery, completed, canceled.
- Integration with 1C-Bitrix via the OnSaleOrderStatusChange event handler.
- Phone number formatting (conversion to the 79XXXXXXXXX format).
- Logging sends to a high-load table.
Result: time from order to notification — less than a second, delivery failures — 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).
- Setup of logging and monitoring for sends.
- Testing: sending test orders across all statuses.
- Documentation: integration diagram, access rights, instructions for adding new statuses.
- Post-release support: 2 weeks of maintenance (bug fixes, optimization).
Work Process
- Analytics — we study your exchange with 1C, order properties, current statuses.
- Design — we select a gateway, design templates, define triggers.
- Implementation — we write the handler code, integrate the API, configure logs.
- Testing — we run scenarios: new order, payment, cancellation, return.
- Deployment — we roll out to production and check under load.
Estimated Timelines
| Scenario | Timeline |
|---|---|
| Green API (unofficial) | from 4 hours |
| WhatsApp Business API (verification + templates) | from 3 to 5 business days |
Cost is calculated individually and depends on complexity and the chosen gateway. We provide an estimate after the audit.
Why Clients 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.
Typical Mistakes During Self-Setup
- Incorrect phone number formatting (missing country code or the @c.us symbol).
- No handler for the "return" status — the customer receives outdated data.
- Using one template for all statuses — a violation of Meta policy.
- No Redis/Memcached — when sending 100+ notifications at once, agents hang.
Contact us for an audit of your store. Get a consultation based on your catalog and order volume.
