Configuring Order Status Notifications in WhatsApp for 1С-Битрикс
Imagine a customer places an order at 23:00, expects confirmation, but the notification never arrives. The next morning they call and find out the order was canceled due to lack of confirmation. Or worse — the order is already packed and shipped, but the customer canceled because they didn't receive a status update. Such situations erode trust and repeat sales. Automatic notifications solve this, but setting them up in 1С-Битрикс requires understanding internal mechanics: event model, agents, caching, and external API integration.
We often encounter situations where a customer makes an order but doesn't receive confirmation. The result: lost leads, support calls. Configuring push notifications in WhatsApp for an online store on 1С-Битрикс is a task with pitfalls. There is no official WhatsApp bot, and unofficial gateways can get your number blocked. Here's how we solve this problem reliably and cost-effectively.
How to Choose the 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, possible blocks |
| Launch speed | 3–5 business days (verification, templates) | 4–8 hours (minimum integration) |
| Cost | Per outgoing message | Fixed subscription + message count |
| Legal compliance | Fully legal | Risk of TOS violation |
| Message customization | Only approved templates | Any text, dynamic formatting |
For small businesses (<500 messages/day), Green API is a working option. For large stores with delivery guarantees — only WhatsApp Business API. The official API delivers in 99.8% of cases versus 95% for unofficial gateways — critical for returns and cancellations.
Why Not Use Unofficial Gateways for High Volumes?
Meta strictly enforces WhatsApp Web usage policies. Exceeding limits or receiving user complaints leads to immediate number blocking without warning. We've seen projects lose access to a 5000+ audience in one day. Meta recommends using the official Business API for automated messaging.
How We Set Up Notifications for an Auto Parts Store (Case Study)
From our practice: an integration for an auto parts online store with a catalog of 50,000 items. We chose the official WhatsApp Business API via Twilio because of the order volume — 200–300 per day. The setup included:
- Business verification with Meta (provided TIN and contracts).
- Creation of 5 message templates: received, confirmed, shipped, delivered, canceled.
- Integration with 1С-Битрикс via the OnSaleOrderStatusChange event handler.
- Phone number formatting (conversion to format 79XXXXXXXXX).
- Logging sends in a high-load table.
Result: time from order to notification under 1 second, delivery failure rate 0.2%. Thanks to tagged caching and agent optimization, server load did not increase.
What's Included in the Notification Setup Work?
- Audit of current 1С exchange and order structure.
- Selection and connection of the appropriate gateway (WhatsApp Business API / Green API).
- Development of an event handler with filtering by statuses.
- Creation of message templates (for official API — with Meta moderation).
- Configuration of logging and send monitoring.
- Testing: sending test orders for 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 — review your 1С exchange, order properties, current statuses.
- Design — select the gateway, design templates, define triggers.
- Implementation — write handler code, integrate API, configure logs.
- Testing — run scenarios: new order, payment, cancellation, return.
- Deployment — roll out to production, test 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, depends on complexity and chosen gateway. We provide an estimate after audit.
Why Choose Us
- 5+ years of experience in 1С-Битрикс development.
- Over 100 successful integrations with external APIs.
- Certified Bitrix specialists (1С-Битрикс certifications).
- Transparent reporting: weekly calls, demonstration of results.
Common Mistakes When Setting Up Independently
- Incorrect phone number formatting (missing country code or @c.us suffix).
- No handler for the 'return' status — customer receives outdated data.
- Using one template for all statuses — violation of Meta policy.
- No Redis/Memcached — agents hang when sending 100+ notifications simultaneously.
Contact us for an audit of your store. Get a consultation based on your catalog and order volume.