Deals won in Pipedrive become sales orders in your ERP. Quotes from your ERP create Deals in Pipedrive automatically. Fulfilment events advance pipeline stages and update custom fields. Multiple pipelines supported — one for sales, one for order and fulfilment tracking — so your CRM reflects your actual commercial workflow.
Pipedrive pipelines are flexible enough to model different commercial workflows — not just linear sales. Supply Lens supports multiple pipelines simultaneously, with each pipeline connected to a different set of triggers and ERP events. Your sales team works in the pipeline they know, and operational data flows into the right one automatically.
A standard sales pipeline where a Deal moving to Won triggers ERP sales order creation. Alternatively, a quote raised in your ERP creates a new Deal at the Quotation stage, giving the sales team visibility of the quote in Pipedrive without manually entering it. The pipeline reflects commercial intent — the ERP handles operational execution.
A separate pipeline dedicated to post-sale order and fulfilment management. When a sales order is created in the ERP — whether from a Pipedrive Deal or any other source — a corresponding Deal is created in this pipeline. ERP events advance the pipeline stage automatically: order confirmed, despatched, delivered. Your operations or account management team can see exactly where every order is without leaving Pipedrive.
The integration is genuinely bidirectional — data flows from Pipedrive to your ERP and from your ERP back to Pipedrive. Custom fields on Deals give your team visibility of operational data without switching systems.
The same flows work across every ERP and IMS pairing. Deals become orders, quotes become Deals, pipelines advance on fulfilment, custom fields stay in sync — regardless of which system sits behind Pipedrive.
Pipedrive's API is stable and the data model is clean. The complexity is in matching Organisations to ERP accounts reliably, keeping product catalogues aligned, and deciding how multiple pipelines map to ERP events.
Matching a Pipedrive Organisation to an ERP customer account by name alone is unreliable — company names diverge over time, abbreviations creep in, and subsidiaries create ambiguity. Supply Lens stores the ERP customer account code as a custom field on the Pipedrive Organisation, creating a permanent machine-readable link between the two records. This account code is set once during the initial sync and updated if the ERP account changes. Every subsequent Deal conversion uses the account code to resolve the customer reliably, regardless of how the Organisation name reads in Pipedrive.
Not every quote raised in an ERP is externally facing or relevant to the sales team. Supply Lens applies a configurable filter before creating a Pipedrive Deal from an ERP quote — by quote status, customer type, value threshold, or any combination of ERP fields you define. Only quotes that meet your criteria appear in Pipedrive. Quotes below a threshold, internal transfers or draft-only quotes stay in the ERP without creating noise in the sales pipeline.
Pipedrive's multi-pipeline model means different teams often work in different pipelines with different stage structures and different information needs. Supply Lens configures each pipeline independently — the sales pipeline responds to Deal Won and drives ERP order creation, the account management or fulfilment pipeline is driven by ERP events and advances stages on order confirmation, despatch and delivery. The two pipelines can share the same underlying ERP records or operate on separate Deal objects, depending on how you want to structure the data.
Custom fields in Pipedrive are there for a reason — they capture data the sales team collects during the Deal process that the ERP needs to process the order correctly. Delivery preferences, project references, preferred despatch dates, territory codes — these fields exist because the default data model does not cover everything. Supply Lens reads every custom field on the Deal that is included in the field mapping configuration and writes the values to the corresponding ERP fields at the point of order creation. The mapping is specified during setup, covers as many fields as needed, and is updated when new custom fields are added.
The scope call covers pipeline structure, stage triggers, custom field mapping and customer matching strategy. Once those decisions are made the configuration is straightforward.
Ongoing support includes pipeline structure changes, new custom field mappings and stage trigger updates as your workflows evolve.
Deals become orders. Quotes become Deals. Pipelines advance on fulfilment. Custom fields stay in sync. 30-day trial available.