Integration / Shopify
In short
There is no Bitrix24-built Shopify connector. You either install a third-party Bitrix24 Market app (Albato or Flamix), route data through Zapier or Make, or build a custom sync on Shopify webhooks and the Bitrix24 REST API. Apps cover new orders and customers well; a custom sync is needed for two-way status, stock, multiple stores, or B2B logic.
Shopify is excellent at taking orders. It is not built to run what happens around them: sales follow-up on abandoned or high-value carts, B2B quotes, repeat-purchase campaigns, after-sales service, and WhatsApp conversations with the buyer. That work lives in a CRM — which is why Shopify merchants connect to Bitrix24.
The goal is simple to state: every Shopify order lands in Bitrix24 as a deal with its line items, every buyer exists once as a contact, and your team works the relationship without retyping anything. How you get there depends on volume, how many stores you run, and whether data must flow back to Shopify.
Checked against the Bitrix24 Market and vendor documentation on 6 October 2026. Sources are listed at the end.
Third-party connector in the Bitrix24 Market, built by Albato (an integration platform).
Best for: Single store, standard order flow, quick start.
Paid third-party Bitrix24 Market app (30-day trial, monthly or annual subscription).
Best for: Stores that want orders as deals with line items and sensible duplicate handling.
General automation platforms with both Shopify and Bitrix24 modules.
Best for: Low order volume or simple one-way flows.
Shopify webhooks + Admin API on one side, Bitrix24 REST API on the other, with a queue in between.
Best for: Higher volume, multiple stores, B2B, or when the CRM must drive Shopify (status, stock, tags).
New order
Shopify → Bitrix24
Deal (or lead) with line items as product rows, totals, discounts, currency, order number, and source.
Customer
Shopify → Bitrix24
Contact matched by email/phone; companies for B2B buyers. One person, one record.
Payment & fulfilment status
Shopify → Bitrix24
Moves the deal through stages: paid, fulfilled, delivered, refunded.
Products & prices
Shopify → Bitrix24
Bitrix24 catalogue kept aligned so deals use real SKUs and prices.
Stock levels
Either way
Pick one system as the source of truth; syncing both ways without rules causes oversells.
Order tags / notes
Bitrix24 → Shopify
Optional: CRM decisions (VIP, B2B approved, hold) written back to the order.
Abandoned checkouts
Shopify → Bitrix24
Optional: become leads with a WhatsApp or call follow-up task.
| Data | Direction | What good looks like |
|---|---|---|
| New order | Shopify → Bitrix24 | Deal (or lead) with line items as product rows, totals, discounts, currency, order number, and source. |
| Customer | Shopify → Bitrix24 | Contact matched by email/phone; companies for B2B buyers. One person, one record. |
| Payment & fulfilment status | Shopify → Bitrix24 | Moves the deal through stages: paid, fulfilled, delivered, refunded. |
| Products & prices | Shopify → Bitrix24 | Bitrix24 catalogue kept aligned so deals use real SKUs and prices. |
| Stock levels | Either way | Pick one system as the source of truth; syncing both ways without rules causes oversells. |
| Order tags / notes | Bitrix24 → Shopify | Optional: CRM decisions (VIP, B2B approved, hold) written back to the order. |
| Abandoned checkouts | Shopify → Bitrix24 | Optional: become leads with a WhatsApp or call follow-up task. |
Two or more of these? Get a written recommendation before you buy an app.
Get a free Shopify integration planCustom development
We build Shopify ↔ Bitrix24 integrations directly on both platforms' APIs — no marketplace app or per-task fees in between — so the sync follows your business rules instead of a connector's settings.
Order, customer, refund, and inventory webhooks (orders/create, orders/updated, refunds/create, customers/create, inventory_levels/update) for real-time events; the Admin GraphQL API for backfills, tags, fulfilment, and stock writes.
crm.deal.add / crm.item.add for orders, product rows on the deal (crm.item.productrow.set), duplicate lookup by phone or email (crm.duplicate.findbycomm), and batch calls to stay inside API limits.
event.bind on deal updates (ONCRMDEALUPDATE) so CRM decisions — B2B approval, hold, VIP — flow back to the Shopify order.
Stores, order types (retail, B2B, COD), stages, who follows up, and which system owns stock and prices.
Field-by-field mapping, duplicate rules, and how edits, cancellations, and refunds are handled.
Shopify webhooks feed a queue; a worker writes to Bitrix24 with batch calls, retries, and back-off within API limits.
Optional import of past orders and customers so lifetime value and repeat buyers are visible from day one.
Bitrix24 automation rules: thank-you and review requests on WhatsApp, high-value order alerts, re-order reminders.
Logs, failure alerts, and documentation — so you can see what happened to any order.
Typical effort: A one-way order and customer feed is typically a few days of work; a two-way sync with stock, multiple stores, or B2B rules usually takes one to three weeks. The integration cost guide explains what moves the number; you get a fixed price after the free review.
Tell us how many stores and orders you run. We'll recommend app, automation platform, or custom sync — and show you the data map before you spend anything.
Not one built by Bitrix24 itself. Shopify connectors in the Bitrix24 Market are made by third parties such as Albato and Flamix. For anything beyond their settings, Shopify's webhooks and Admin API plus the Bitrix24 REST API allow a custom sync.
Yes. Good integrations create the deal with each line item as a product row (SKU, quantity, price, discount), link it to the buyer's contact, and move it through stages as payment and fulfilment change.
Yes, with a custom integration: order tags, notes, fulfilment status, and stock levels can be written back through the Shopify Admin API. Most marketplace apps focus on Shopify → Bitrix24.
Apps usually start from the install date. A custom build can backfill historical orders and customers, which makes repeat-buyer and lifetime-value reporting accurate from day one.
Marketplace apps and REST integrations need a paid (commercial) Bitrix24 plan. Higher plans also raise API limits — Enterprise allows 5 requests/second versus 2 on standard plans.
Marketplace apps change often; verified 6 October 2026.
Tell us how many stores and orders you run. We'll recommend app, automation platform, or custom sync — and show you the data map before you spend anything.