Brightpearl and DotDigital
Integration Agency & Consultants
At scale, marketing teams cannot fly blind. Operational friction starts when automated flows send communications based on stale data, such as targeting customers with items they have even though the order failed in Brightpearl. We connect Brightpearl to Dotdigital to ensure marketing segments are driven by transactional history and accurate lifetime value. This integration gives teams visibility into the order history and warehouse statuses locked inside the ERP, replacing manual exports with commerce-aware automation. It is designed for merchants where segmentation accuracy and personalisation timing have direct commercial consequences.
Auditing system gaps and data inefficiencies
Cogent2 connects your Brightpearl and DotDigital integration swiftly, ensuring your ERP and ESP platforms work together efficiently. Our consulting services are invaluable, with our system audit uncovering inefficiencies and integration gaps between Brightpearl, DotDigital, ERP, and ESP systems. This enables our consultants and your team to take decisive action, optimising your technology ecosystem for smooth operations. As a result, you can deliver an outstanding customer experience, confident that your systems are aligned and performing at their best.
Solution Design
Our design for the Brightpearl and Dotdigital integration treats the ERP as the master for customer records, order history, and product catalogues. A primary decision involves mapping Brightpearl order status movements to trigger or suppress marketing programmes in Dotdigital. We typically prioritise order and contact updates as frequent flows while scheduling larger catalogue updates on a set cadence. A key trade-off is the depth of custom contact field mapping. Increasing the data points per contact supports granular personalisation but can introduce sync latency under load; we manage this by sequencing critical transactional updates first. This design ensures marketing segments reflect the actual transactional history held in the ERP. It preserves the trust boundary where finance relies on Brightpearl data while marketing automations stay in step with customer behaviour.
Managing customer data and order synchronisation
The integration typically treats Brightpearl as the master for transactional data and customer records. When an order status changes within the ERP, these updates flow to Dotdigital to update relevant contact data fields. Data integrity is maintained by mapping retail-specific logic, ensuring personalisation is based on actual order history and returns. We incorporate monitoring to detect sync lags between systems. By synchronising the product catalogue alongside customer history, marketing can trigger automated programmes based on what was actually despatched from the warehouse.
Orchestrating workflows via secure middleware
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations, Brightpearl and DotDigital integrations are delivered efficiently and securely. IPaaS connects ERP and ESP platforms, automates data between Brightpearl and DotDigital, and supports ERP and ESP workflows. This approach ensures robust data protection, reduces manual effort, and simplifies complex integrations, all while meeting strict compliance standards.
Monitoring sync health and status discrepancies
Standard dashboards can hide granular errors, such as a contact field that fails to update despite the order sync appearing successful in Brightpearl. This can lead to customers receiving automated emails that do not match their actual order status. Our approach surfaces these discrepancies by monitoring the relationship between Brightpearl order statuses and Dotdigital contact flags. We provide visibility into the health of your segments, identifying where a sync lag might affect automated flows. This allows teams to manage exceptions before data issues compromise the customer experience.
Documenting ownership and operational handovers
The marketing, ecommerce, and operations teams must adopt the new operating model to maintain campaign accuracy. We hand over an architecture that defines Brightpearl as the master for transactional history, customer records, and return statuses. Training focuses on how to perform routine checks to ensure data is reaching the marketing engine and how to interpret alerts from the integration layer. Marketing learns to identify why a segment might be stalling, while ops teams ensure the status movements in the ERP are triggering the correct flows. We provide operational documentation written for the people running the business, focusing on who owns each exception type.
Protecting data integrity and flow updates
Support centres on defending the integrity of the transactional data flow. We watch for gaps where contact fields in Dotdigital fail to update after a Brightpearl status change, causing marketing flows to stall. Our team manages the escalation path to identify whether an exception originates in the ERP, the marketing platform, or the data sync. We prioritise resolving errors that block lifecycle programmes or high-value segments. By monitoring for failed contact updates and data drift, we ensure that warehouse movements like returns are reflected in your marketing segments. This prevents automation from running on stale data and protects the customer experience.
Common failures
Delayed status sync leading to marketing friction
Operational impact: When a Brightpearl order is cancelled, a delay in updating Dotdigital leaves the customer in the standard post-purchase flow. Sending 'thank you' or cross-sell emails to a customer whose order was just voided creates immediate friction and increases support tickets.
Prevention: Map cancellation statuses in Brightpearl as high-priority triggers to suppress marketing flows. The integration should prioritise these status changes over routine data updates to ensure automation is interrupted before the next send.
Profitability drift in custom contact fields
Operational impact: Marketing segments based on Lifetime Value (LTV) often become inaccurate because Dotdigital data is not updated for returns or refunds processed in the ERP. This gap between the marketing engine and Brightpearl leads to targeting customers with incorrect offers, wasting spend and undermining segment trust.
Prevention: Brightpearl must be the master for all transactional history. The integration should trigger a data update in Dotdigital as soon as a return or refund is processed in the ERP, ensuring contact records reflect the most recent commercial reality.
Guest record fragmentation
Operational impact: Guest checkouts can create duplicate contacts in Dotdigital if the integration logic does not check for existing records. This fragments the view of the customer, making it impossible to calculate accurate repeat purchase rates or loyalty tiers. It also increases platform costs due to a bloated database.
Prevention: Use a matching rule that identifies existing contacts by email address before creating new records. By centralising the customer record, the integration ensures all order history is attributed to a single contact for reliable segmentation.
Frequently asked questions
How does the integration stop us from marketing to customers whose orders haven't shipped or have been returned?
The integration synchronises key status changes from Brightpearl to Dotdigital to enable precise timing. For instance, a 'Goods Out Note' marked as 'Shipped' in Brightpearl updates a contact record in Dotdigital to trigger a post-fulfilment sequence. Similarly, issuing a 'Sales Credit' for a return can change a customer's status, ensuring they are excluded from campaigns that would be inappropriate.
Can we segment customers in Dotdigital based on their lifetime value calculated in Brightpearl?
Yes, by establishing Brightpearl as the system of record for all order and customer data. The integration pushes the entire sales order history for each customer record into Dotdigital's Insight data fields. This allows the marketing team to build valuable segments based on metrics held in Brightpearl, like total spend or order frequency.
Which system should be the master for customer information, Brightpearl or Dotdigital?
In a robust operating model, Brightpearl must be the single source of truth for customer records and their complete transactional history. Dotdigital receives contact updates and order data from Brightpearl, but does not write this information back. This one-way flow for core data prevents inconsistencies and ensures your Dotdigital segments are always based on the verified master data in your ERP.
Does the integration handle B2B customers who order via a company account?
Yes, but it requires careful mapping to avoid common failures. For corporate accounts, the 'Company' field must be mapped correctly to the Brightpearl 'Organisation' on the customer record. If this is not done, new sales orders from B2B customers often fail to post into Brightpearl, leaving contacts in Dotdigital without their associated order history.