PIM System Integration with Website

Note: when your catalog has 10,000+ SKUs and products are sold via website, marketplaces, and mobile apps, storing attributes and descriptions in each system separately leads to chaos. Attribute errors cost an average of 200 person-hours of manual reconciliation per month, and inconsistent content across channels drops conversion by 15%. A typical scenario: a manager updates weight in ERP, but the description on the site remains old, and the customer receives outdated information.

We solve this by integrating a PIM system (Akeneo, Pimcore, Plytix) with the website. PIM becomes the central repository for product data: texts, images, documents, translations. The website consumes this data via REST API or webhook, rather than storing it in its own database. This achieves a single source of truth — all changes are made once and automatically distributed to all channels. According to Wikipedia, PIM systems reduce time-to-market by an average of 30-50%.

What Problem Does PIM Solve?

The main pain is data desynchronization across channels. For example, a product's weight changes in ERP, but the description on the site remains old. Or a manager manually edits a card on a marketplace, and a week later the changes are lost. PIM eliminates manual work: all changes are made once and automatically propagated to all systems. In our experience, PIM implementation reduces time-to-market by 40%.

What Is Included in the Work?

1. Analysis of current data architecture: studying product structure, sources (ERP, CRM), consumption channels.
2. Designing synchronization scheme: selecting strategy (pull/push/hybrid), determining frequency.
3. Integration with PIM via REST API: configuring client (PHP, Node.js), optimizing requests (pagination, filters).
4. Synchronizing categories and attributes: building category tree, field mapping.
5. Media files: uploading images from PIM to the site's CDN with hash verification.
6. Multilingual support: configuring locales, automatic content switching.
7. Testing and monitoring: data integrity checks, alerts on failures.

{
  "events": ["product.created", "product.updated", "product.deleted"],
  "url": "https://your-site.com/webhook/akeneo",
  "method": "POST",
  "secret": "your-secret"
}

Popular PIM Systems

Which Synchronization Strategy to Choose: Pull or Push?

Pull approach — the site periodically requests changes from PIM. Usually every 15-30 minutes. Suitable for most tasks, but introduces latency. Example request for changed products:

GET /products?search={"updated":[{"operator":">","value":"2025-01-01T10:00:00"}]}

Push approach (webhook) — PIM notifies the site upon publication. Akeneo supports events product.updated, product.created. Latency — seconds. Requires processing on the site side (queue, rate limiting).

We often use a hybrid: base updates via pull every 30 minutes, critical updates (e.g., product disable) via webhook. Below is a comparison of key parameters:

Push synchronization is 60x faster than pull in terms of data freshness, but requires more complex infrastructure.

Example Integration with Akeneo

<?php
// composer require akeneo/api-php-client

$client = \Akeneo\Pim\ApiClient\AkeneoPimClientBuilder::create(
    'https://your-pim.akeneo.com'
)->buildAuthenticatedByPassword('client_id', 'secret', 'user', 'pass');

// Get products with specified attributes
$products = $client->product()->listPerPage(100, true, [
    'channel'    => 'ecommerce',
    'locales'    => ['ru_RU', 'en_US'],
    'attributes' => ['name', 'description', 'weight', 'color'],
    'filters'    => [['field' => 'enabled', 'operator' => '=', 'value' => true]]
]);

foreach ($products->getItems() as $product) {
    $name = $product['values']['name'][0]['data'];
    $description = $product['values']['description'][0]['data'];
    // Sync to local site DB
}

Integration Specifics: Media, Multilingual, and Categories

Media files — images are stored in PIM linked to products. The site can cache them on S3 with hash verification, serve directly from PIM (only for secure environments), or use PIM's CDN. Typical volume: 500+ images for a catalog of 10,000 SKUs.

Multilingual support — PIM natively manages translations. Russian and English versions of a product are stored with locale binding. When requesting data, the site passes the required locale:

GET /products/tshirt-blue?scope=ecommerce&locales=ru_RU

Category synchronization — the hierarchy comes from PIM as a flat array with parent_code. We rebuild the tree on the site side, ensuring the structure is up-to-date.

Why Choose Us?

Over 10 years of integration experience. Akeneo certified specialists. Each project has a manager and an engineer. We provide a warranty on all work. Get a consultation for your project — contact us to discuss details.

Timeline and Cost

Integration timeline: from 4 to 8 weeks depending on catalog complexity and number of channels. Cost is calculated individually. Request a project evaluation — we'll prepare a proposal.

Typical Integration Mistakes

• Synchronizing all data at once — overloads the API and slows the site. Use incremental updates.
• Ignoring media — images from PIM are heavy. Set up CDN and compression.
• Lack of monitoring — without alerts, a sync failure can go unnoticed. Set up notifications.

Our experience helps avoid these mistakes. Request a project evaluation — we'll prepare a proposal.

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)