Effortless Real-Time Data Sync for Your 1C-Bitrix Store
Imagine your online store runs on 1C-Bitrix while inventory and accounting are in 1C. During a promotion, you update prices, but CommerceML transfers them every 30 minutes. Customers see outdated prices and incorrect stock levels—orders ship with negative inventory. Sound familiar? We specialize in integrating 1C and Bitrix via a REST-based interface. With over 10 years in production, we've deployed seamless exchange for 100+ projects. Our solution synchronizes data in real time, eliminating delays and errors.
CommerceML is a synchronous batch file exchange. REST API is event-driven, triggering updates the moment data changes. The difference is critical: REST updates data in seconds and supports entities CommerceML cannot handle—custom directories, documents, tasks. That's why this approach is becoming the de facto standard for modern commerce.
Why REST API Is Faster Than CommerceML
| Parameter | CommerceML | REST API |
|---|---|---|
| Exchange speed | Every 15–30 minutes | Instant (seconds) |
| Transfer type | Batch file | Event-driven request |
| Support for custom entities | Only catalog, orders | Any data (tasks, directories) |
| Server load | High (processes all data) | Low (point updates) |
| Sync errors | Frequent due to locks | Minimal with correct setup |
When to Choose REST API Over CommerceML
REST integration is justified when: data must update faster than every 15 minutes (promotional prices, critical stock); exchanging non-standard data; integrating with a custom 1C configuration that lacks the standard exchange handler; connecting multiple sites or services to the same 1C database. Moving to this method reduces manual sync overhead and lowers error probability.
How We Configure Inventory Sync via REST
Bitrix provides REST API through the rest module. For external systems, create an inbound webhook: Settings → Product Settings → REST API → Inbound Webhooks → Add. Assign only required permissions: catalog for catalog, sale for orders. Never grant administrator rights.
From 1C (via HTTP connection in the configurator), send a request to the Bitrix API:
POST https://myshop.ru/rest/1/WEBHOOK_KEY/catalog.storeproduct.update Content-Type: application/json { "productId": 12345, "storeId": 3, "amount": 47 } This is a point update—only the specific product at the specific warehouse is changed. Unlike batch processing that handles all 50,000 items, a REST call takes milliseconds.
Case study: For one client with a catalog of 20,000 items, we replaced a CommerceML sync that took 8 seconds per operation with REST API calls averaging 1.2 seconds. Manual error corrections dropped by 90%.
How We Deliver Orders to 1C Without Delays
Instead of file exchange, 1C polls the REST API on a schedule:
GET https://myshop.ru/rest/1/WEBHOOK_KEY/sale.order.list ?filter[STATUS_ID]=N &filter[>=DATE_INSERT]=DATE_LAST_SYNC &select[]=ID &select[]=ACCOUNT_NUMBER &select[]=PRICE &select[]=CURRENCY The response is a JSON list of new orders. 1C processes each, creates documents, then updates the status via sale.order.update.
For immediate event delivery (new order, status change), set up Bitrix outbound webhooks that send data to an HTTP service in 1C: Settings → REST API → Outbound Webhooks → Add. Enter the HTTP service URL and event type ONSALEORDERNEW. When a new order appears, Bitrix immediately POSTs to 1C—no waiting for the next exchange session.
How to Avoid Common Integration Errors
Frequent issues: incorrect webhook URL (no response), order duplication (improper status handling), authentication error (wrong key). Solutions: check HTTP service accessibility, use idempotent keys, verify permissions in REST API settings. Details in the official documentation.
Additional configuration parameters
- Set up separate access rights for each webhook.
- Use the REST API for custom entities.
- Log requests for debugging.
What's Included in Our Turnkey Configuration
- Audit of your current integration to identify bottlenecks.
- Design of exchange schema: selecting REST methods, setting up webhooks.
- Implementation of HTTP service in 1C to receive requests.
- Writing exchange scripts for inventory, prices, and orders.
- Testing synchronization accuracy on test data.
- Operation documentation and training for your staff.
- One month of warranty support after deployment.
Our Process
- Analysis: We study your 1C configuration and site setup.
- Design: We develop integration architecture.
- Implementation: We configure REST API and write the HTTP service.
- Testing: We verify sync across all scenarios.
- Deployment: We go live in production.
Timeline and Pricing
Basic inventory and order sync: 1–2 days. With bidirectional webhooks: 3–5 days. Full replacement of CommerceML for a large catalog: 1–3 weeks. Price is determined after audit. Our basic integration starts at €500 and typically pays for itself within 2-3 months through reduced manual labor. Contact us for a free consultation—we'll evaluate your project and propose the best solution. The investment typically pays for itself in 2–3 months.
We guarantee quality: all work is done by engineers with 10+ years of experience in Bitrix and 1C. We provide certificates and references. Order your integration today—get a free consultation.