Merret Retail Assist and DotDigital
Integration Agency & Consultants
Cogent2 combines AI-powered integration delivery with operators who understand retail data must flow properly. Connecting Merret Retail Assist to DotDigital ensures rich customer and order history is no longer trapped in operations. This gives marketing teams reliable data for better segmentation, leading to more effective campaigns and improved customer engagement.
Auditing data gaps between ERP and ESP
Cogent will efficiently connect your Merret Retail Assist and DotDigital systems, ensuring your ERP and ESP platforms operate smoothly. Our consulting services, including system audits, are invaluable for identifying inefficiencies and enabling your team to take decisive action. By addressing integration gaps and optimising workflows, we help your tech ecosystems function efficiently, ensuring your Merret Retail Assist and DotDigital solutions deliver an exceptional customer experience. With a focus on ERP and ESP integration, our audits provide the insights needed to maintain seamless operations and customer satisfaction.
Solution Design
Design for this pair prioritises Merret Retail Assist as the master for transactional data and validated customer records. A core decision involves the sequencing of data into DotDigital: we typically favour prioritising profile updates for marketing triggers while managing historical order data on an appropriate schedule to maintain system stability. A common trade-off occurs with real-time data syncs. While real-time updates support immediate customer engagement, they can increase the load on core retail systems. We typically implement a design that balances responsiveness with operational reliability. This approach ensures marketing segments are built on operationally grounded data. Marketing executes campaigns based on enriched profiles while core operations continue to run from the ERP, reducing the risk of targeting customers with incorrect information.
Synchronising Merret identities with DotDigital profiles
This integration establishes Merret Retail Assist as the authoritative source of truth for customer identities and order history. DotDigital consumes this data to drive marketing segmentation based on real transactional behaviour. Records sync on a defined schedule, ensuring that retail-specific attributes from Merret are reflected accurately in marketing profiles.
We prioritise data mapping rules that prevent profile fragmentation, particularly when managing the relationship between Merret's internal customer IDs and DotDigital's email-based identifiers. For transactional triggers like abandoned baskets, the integration ensures the connection between front-end session data and Merret's inventory records. Monitoring surfaces data mismatches or interrupted flows early, ensuring marketing teams do not build campaigns on top of a compromised or inaccurate data set.
Orchestrating workflows via secure middleware layers
Cogent2 leverages iPaaS to integrate Merret Retail Assist and DotDigital with ERP and ESP systems securely. iPaaS platforms ensure Merret Retail Assist and DotDigital integrations are efficient, maintaining ISO 27001 and SOC 2 compliance and above. This approach benefits businesses by providing a centralised integration framework, enhancing data flow between ERP and ESP systems, and ensuring robust security standards.
Surfacing record drift and data exceptions
Standard connection dashboards often confirm that a sync triggered, but they rarely flag if the underlying data is actually correct. Incomplete customer records or missed order history from Merret Retail Assist can degrade marketing segments without throwing a hard error. We focus on surfacing these data-level exceptions. By categorising failures where the DotDigital profile drifts from the source of truth in Merret, teams can fix specific record issues before a campaign is sent. This provides visibility into data health rather than just sync status.
Handing over the day-to-day operating model
Ecommerce, marketing, and CRM teams must own the daily reality of their data. Handover focuses on the operating model, explaining where each data object lives and how to maintain accuracy across Merret Retail Assist and DotDigital. We provide operational documentation written for those running the business, not for IT. This covers what to check on a defined schedule and how to respond to alerts from the integration layer. Training is anchored in the design decisions made for your business, ensuring teams know who owns each exception type. These references are designed for people running the business, ensuring they can maintain high-quality data without needing technical intervention.
Maintaining data integrity after go-live
Post-launch support is about maintaining the integrity of the data flow between retail operations and marketing. We monitor the synchronisation of customer records and order data from Merret Retail Assist, identifying exceptions before they impact campaign performance. We provide a framework for escalation and operational oversight. This ensures that as your customer base scales, the connection between your ERP and DotDigital remains stable and your segments stay accurate.
Common failures
Incomplete customer profile synchronisation
Operational impact: When customer data from Merret is not fully or accurately mapped to DotDigital, marketing segmentation becomes unreliable. The marketing team may build campaigns based on incomplete purchase histories or incorrect customer attributes, leading to wasted budget and poor targeting. This erodes the value of having an integrated stack, as the single customer view remains fragmented and untrustworthy.
Prevention / Action: The integration's design must specify Merret as the source of truth for the master customer record. A unique, immutable identifier for each customer must be established and mapped to a corresponding key in DotDigital to prevent duplicates. Implement pre-sync data validation and an exception handling queue for records that fail validation, ensuring an operator can review and correct issues before they pollute the marketing database.
Delayed order data transfer for marketing automation
Operational impact: If sales order and dispatch data from Merret faces significant latency before appearing in DotDigital, time-sensitive campaigns fail. Post-purchase automations, such as review requests or first-time buyer welcome sequences, are triggered too late to be effective. This missed opportunity damages the customer experience and prevents the marketing team from capitalising on recent buying signals.
Prevention / Action: Analyse the required timing for critical marketing automations and design the integration schedule accordingly. Where possible, use event-based triggers upon order confirmation or dispatch in Merret, rather than relying solely on infrequent batch file transfers. If batch processing is the only option, ensure its frequency is sufficient and that processing jobs are monitored for backlogs or failures.
Misaligned marketing consent status
Operational impact: Failure to synchronise marketing consent between the two systems creates compliance risk and customer frustration. If a customer opts out via a DotDigital email but this is not reflected in Merret, they may continue to receive messages, leading to complaints and potential GDPR breaches. Conversely, if a new customer provides consent during checkout and this is not passed to DotDigital, a valuable opportunity to engage them is lost.
Prevention / Action: Establish a single source of truth for marketing consent, which is typically DotDigital. The integration must support bidirectional syncing of consent fields. Any opt-in or opt-out event in DotDigital must be reflected on the customer record in Merret, and vice versa. Schedule a regular reconciliation process to audit consent flags across both systems to identify and correct any discrepancies.
Frequently asked questions
If a customer updates their details, which system should we update: Merret or DotDigital?
Merret Retail Assist should be the source of truth for all core customer records. Any updates should be made in Merret, which then syncs to DotDigital to enrich the contact record. Updating details directly in DotDigital risks the data being overwritten during the next sync from Merret, which can lead to targeting errors.
Why might our 'post-purchase' automations not trigger in DotDigital after an order is placed?
This often happens if the order status mapping is misconfigured. For the sync to work, an order's 'Web Status' in Merret Retail Assist must be mapped correctly to a triggering event in DotDigital. If this link is broken, transactional order data for those sales will not sync, and your marketing automations will fail to run.
We want to use 'back in stock' alerts from DotDigital. How does Merret’s inventory syncing affect this?
This needs careful planning as Merret typically updates inventory levels in scheduled batches. If a 'back in stock' campaign in DotDigital triggers between these batches, you could notify customers about a SKU that isn't purchasable yet, causing frustration. The integration must be designed around Merret's batch processing to ensure stock alerts are accurate.
Can we segment customers in DotDigital based on their lifetime value from Merret?
Yes, this is a core purpose of connecting the two systems. The integration syncs sales order history from Merret Retail Assist into DotDigital's data fields, allowing you to calculate lifetime value. This enables you to build specific campaigns targeting your most valuable customer segments or to re-engage those who have not purchased recently.
How do you handle historical order data when first connecting Merret to DotDigital?
The initial sync populates DotDigital with historical sales orders and customer records from Merret, creating the baseline for segmentation. We typically work with you to define the scope, such as whether to import one or five years of order history. This ensures that your initial DotDigital campaigns are built on a rich, relevant dataset from day one.