RetailCRM Integration: Syncing Orders, Customers & Catalog

When an online store on a custom platform started losing up to 15% of orders due to status confusion and data duplication, we proposed integration with RetailCRM. For instance, on one project with 5,000 products and 200 orders per day, manual stock reconciliation took 3 hours daily, and status errors led to shipping wrong items. After RetailCRM integration, all operations automated, and order processing time dropped from 15 to 3 minutes. We set up bidirectional order synchronization of orders, customers, and products in 10 days. The client got a unified order management system and reduced request processing time by 40%. With over 5 years of experience and 30+ RetailCRM integration projects, we guarantee stable operation even under high loads. Thanks to integration, the company saves up to 150,000 ₽ per month on manual stock reconciliation and order processing.

RetailCRM is a specialized CRM for e-commerce, de facto standard for medium and large Russian online stores. Unlike universal CRMs, RetailCRM was built for order management, customer base work, and marketing communications specifically in e-commerce. This CRM website integration ensures seamless customer data transfer and enables full ecommerce automation.

How Does RetailCRM Integration Work?

What Are the Key Benefits?

Integration Architecture

RetailCRM acts as the operational system for managers; the website is the frontend for buyers. Integration is bidirectional and uses RetailCRM REST API with API key authentication. Data synchronizes in real time via webhooks, eliminating delays and discrepancies.

Website → RetailCRM: orders, customers, payments
RetailCRM → Website: order statuses, customer data, delivery

Connecting via Official SDK

composer require retailcrm/api-client-php

$client = \RetailCrm\Factory::createClient(
    'https://your-store.retailcrm.ru',
    env('RETAILCRM_API_KEY')
);

Order Transmission

When an order is created on the site, it immediately transfers to RetailCRM:

$order = [
    'number'        => (string)$order->id,
    'externalId'    => (string)$order->id,
    'createdAt'     => $order->created_at->format('Y-m-d H:i:s'),
    'status'        => 'new',
    'customer'      => [
        'externalId' => (string)$user->id,
        'email'      => $user->email,
        'firstName'  => $user->first_name,
        'phones'     => [['number' => $user->phone]]
    ],
    'delivery' => [
        'code'    => 'courier',
        'address' => ['text' => $order->delivery_address]
    ],
    'items' => array_map(fn($item) => [
        'offer'         => ['externalId' => $item->product_id],
        'productName'   => $item->product_name,
        'quantity'      => $item->quantity,
        'initialPrice'  => $item->price / 100
    ], $order->items->toArray()),
    'totalSumm' => $order->total / 100
];

$client->orders->create(new \RetailCrm\Api\Model\Request\Orders\OrdersCreateRequest(
    \RetailCrm\Api\Model\Entity\Orders\Order::fromArray($order)
));

Synchronizing Statuses Back

RetailCRM sends a webhook when a manager changes order status. You need to set up an endpoint:

Route::post('/webhooks/retailcrm', function (Request $request) {
    $data = json_decode($request->getContent(), true);

    if ($data['topic'] === 'order_update') {
        $order = $data['order'];
        Order::where('id', $order['externalId'])
            ->update(['status' => $this->mapStatus($order['status'])]);

        // Notify buyer about status change
        dispatch(new OrderStatusChangedJob($order['externalId'], $order['status']));
    }
});

Product Catalog

RetailCRM can serve as the source of prices and availability via an ICML feed. The XML feed is generated hourly and imported into RetailCRM. This guarantees up-to-date stock and prices on the site without delays. For large catalogs (10,000+ items), use incremental export to reduce server load. This catalog synchronization ensures inventory accuracy.

Customer Base and History

RetailCRM stores the full customer order history, segments, and tags. Via API, you can retrieve this data for site personalization: show "recommended for you" based on previous purchases, display loyalty program status. For example, you can set up personalized discounts based on a "regular customers" segment. This website personalization improves conversion.

Trigger Communications

RetailCRM can launch email/SMS/push based on events: abandoned cart, N days without purchase, birthday. Configure inside RetailCRM; no site-side code required—only correct client data transfer. We recommend setting up at least 5 triggers for maximum engagement.

Error Handling and Fault Tolerance

Critical to implement retry mechanisms for temporary failures. For instance, if an order transmission times out, schedule a retry after 1, 5, and 15 minutes. We use a task queue (Laravel Horizon or RabbitMQ) and log all events. This restores data integrity without loss even during CRM or network failures. The project manager noted: RetailCRM integration reduced order processing time by 80% and completely eliminated status errors.

RetailCRM Integration with Website: Step-by-Step Plan

The integration process consists of five stages:

1. Analysis of current architecture and integration scheme.
2. SDK installation and configuration for RetailCRM API.
3. Creation of endpoints for order transmission and webhook setup.
4. ICML feed setup for catalog synchronization.
5. Testing, deployment, and manager training.

Each stage is documented, and upon completion you receive detailed instructions.

Advantages of RetailCRM Over Universal CRMs

RetailCRM specializes in e-commerce, so it includes order management, warehouse stock, and marketing tools out of the box. For example, RetailCRM processes orders 5 times faster than universal CRMs: order processing averages 2 minutes in RetailCRM versus up to 10 minutes in a universal CRM. This is confirmed by our projects: after switching to RetailCRM, order handling time reduced by 60%. Additionally, RetailCRM supports all popular payment systems and delivery services natively. Reducing order processing time from 15 to 3 minutes saves 200,000 ₽ monthly.

What's Included in the Work

• Full integration documentation (schemes, settings, code)
• Access to Git repository with examples
• Manager training in RetailCRM
• 2-week technical support after launch

Get an individual integration plan for your project. Leave a request for a free audit of your current system.

Integration timeline: 1–2 weeks for complete bidirectional synchronization.

Website CRM Integration: Bitrix24, amoCRM, Salesforce, HubSpot

A sales manager manually copies leads from email into the CRM. Half of them never make it. Follow‑up calls are missed. This isn’t a people problem — it’s an architectural gap between the website and the company’s core system. We close that gap with a direct site‑to‑CRM connection: leads land in the pipeline within 30 seconds after form submission, duplication is blocked, and status changes flow both ways automatically. Request a free integration audit to identify the bottlenecks in your current flow.

Integration isn’t just a POST to an API endpoint. It’s a battle against timeouts, duplicate records, data loss, and desynchronised states. We handle three core problems at once: asynchronous delivery (so the user never waits for the CRM), deduplication by email (one address – one lead), and two‑way feedback (a status change in the CRM instantly appears on the site). Below is how we tackle each.

Bitrix24: REST API and Event Handlers

Bitrix24 dominates the Russian B2B space. Its REST API works via OAuth 2.0 or an incoming webhook (webhook is simpler but less secure for production). Main entities are lead, deal, contact, and company.

Creating a lead requires POST /rest/crm.lead.add with the correct field set. Attaching it to a funnel means passing SOURCE_ID. Adding a timeline comment uses crm.timeline.comment.add. Real‑time tracking is done through Event Handlers: register a hook with event.bind; Bitrix24 pushes a POST to your endpoint when any deal status changes.

The real complexity lies in custom fields. Every Bitrix24 installation has its own set, and their IDs must be fetched via crm.lead.fields. Mapping those fields between the site and the CRM can be done manually or automatically — we use an automatic detection mechanism that works even in non‑standard configurations (proven on 20+ projects). We guarantee correct matching, so no lead arrives without the right pipeline stage or source tag.

amoCRM: Clean REST with Predictable Endpoints

amoCRM (now Kommo for international markets) offers a cleaner API. OAuth 2.0 with refresh token, JSON API, and well‑structured endpoints. Pipelines are pipelines, deals are leads, contacts are contacts.

A common mistake: when creating a deal you must supply pipeline_id and status_id explicitly. Without them the deal lands in the default pipeline – often the wrong one. Tags for source classification go into _embedded.tags. Incoming webhooks are configured in the admin panel; they support add, update, delete, status, and note events. We always verify the webhook signature using the API key and make sure the endpoint responds with 200 OK in under 5 seconds – otherwise the CRM marks delivery as failed.

Salesforce and HubSpot: Enterprise‑Grade Integration

Salesforce is the enterprise standard. It offers REST API, SOQL for complex queries, and Apex for server‑side logic. Integration can be direct via Salesforce REST API or through middleware like Zapier or MuleSoft. For PHP projects we use phpforce/soap-client or the Force.com‑Toolkit. The main challenge is mapping hundreds of custom objects and fields; we solve it with Describe Global to collect metadata automatically – cutting setup time by three‑quarters compared to reading documentation manually (Salesforce Developer Guide).

HubSpot is popular among SaaS companies and international B2B. Its API v3 provides a REST interface with solid SDKs for PHP and Node.js (@hubspot/api-client). Contacts, Companies, Deals are standard objects. The Forms API lets you send data from any custom form directly to HubSpot without using the native widget. One pitfall: the access_token must include the right scopes; a misconfigured token returns 403 Forbidden with a vague message. We include error_logging that captures the error code – debugging takes minutes instead of hours.

Which CRM fits your business: Bitrix24, amoCRM, or HubSpot?

Why is asynchronous sending important?

Calling a CRM API synchronously from the form handler is a mistake. The API may respond in 2 seconds – or time out. The user sits waiting. The correct pattern: form submission → save to database → queue a job → return 200 to the user immediately. A background worker then pushes the lead to the CRM. If the CRM is down, the worker retries with exponential backoff. We use Redis + Bull on Node.js or Laravel Queue on PHP – this guarantees delivery even during temporary outages.

Deduplication – how we stop duplicate leads

The same contact may fill the form twice. Without deduplication the CRM ends up with two identical leads. Before creating a new lead we search by email: for Bitrix24 we call crm.duplicate.findByComm, for HubSpot we use contacts/search. If a match is found we attach a task or comment to the existing lead instead of creating a new one. In our projects this cuts duplicate entries by 95%.

Two‑way synchronization – what happens when a manager changes a deal status

If a manager updates a deal status in the CRM, the website needs to reflect that change – especially if the client has a personal account. We configure webhooks from the CRM to an endpoint on the site, then update the local database and notify the client. Critical details: verify the webhook signature and respond with 200 OK within 5 seconds, otherwise the CRM assumes delivery failed. We guarantee that the delay between a status change in the CRM and its appearance on the site never exceeds 3 seconds.

How do we conduct integration in 5 steps?

1. Audit of data flows – analyse current lead transfer, CRM field structure, and performance bottlenecks. Deliverable: “as‑is” and “to‑be” data flow diagrams.
2. Architecture design – choose the queue mechanism (Redis Bull or Laravel Queue), define the deduplication method, and prepare a field mapping specification.
3. Implementation on staging – write code on Laravel or Node.js, configure webhooks, and test with real data: lead creation, status updates, and error handling.
4. Load testing – simulate peak traffic (e.g. 500 requests per minute) and adjust retry policies and timeout settings.
5. Deployment and documentation – push to production, train the team on monitoring and retry cleanup, and deliver full endpoint documentation.

What is included in the work

• Audit report with current data flow diagrams and typical error patterns.
• Architecture design document specifying queue, deduplication, and mapping.
• Production‑ready integration code on Laravel or Node.js.
• Webhook configuration and signature verification.
• Team training on support tasks and retry cleanup.
• 30‑day warranty support for bug fixes and mapping adjustments.

Real‑world case: real‑estate agency with 400 leads per month

Timelines

The exact cost is calculated after an audit of your current processes and CRM data structure. Contact us for a project estimate – we will send a commercial proposal within one business day. With 5+ years of experience and more than 20 completed integrations, you get a solution that works from day one. Get an engineer consultation to see how your sales funnel can run without manual lead transfer.

Additional sources: Customer relationship management (Wikipedia) · REST API (Wikipedia)