Clarus WMS and Merret Retail Assist
Integration Agency & Consultants
Inventory counts often begin to diverge the moment order volumes outpace manual updates. When Merret Retail Assist acts as the hub for orders but lacks an automated link to Clarus WMS, the resulting delay in data creates gaps that become visible during peak trade. Integrating Clarus and Merret ensures that fulfilment execution in the warehouse updates stock levels in your ERP on a defined trigger. This helps prevent overselling by aligning available-to-sell figures and ensures that financial reporting reflects the actual state of your inventory.
Audit your warehouse and ERP processes
Cogent connects your Clarus WMS and Merret Retail Assist with precision, ensuring your WMS/3PL and ERP systems work harmoniously. Our consulting services, including comprehensive system audits, are invaluable for identifying inefficiencies and integration gaps. By leveraging these insights, our consultants collaborate with your team to optimise your tech ecosystem, ensuring smooth operations. This enables your Clarus WMS and Merret Retail Assist to function efficiently, allowing your WMS/3PL and ERP systems to deliver an exceptional customer experience.
Solution Design
Integrating Clarus WMS and Merret Retail Assist requires a strict split between financial record-keeping and floor execution. In most setups, Merret is the master for orders and the financial ledger, while Clarus owns inventory accuracy and fulfilment. A primary design decision is the timing of fulfilment status updates. Pushing these in defined intervals reduces system overhead and simplifies reconciliation, but it creates a trade-off: customer service teams in Merret may see brief lags in shipment status compared to the live warehouse floor. We prioritise stock-level sync frequency from Clarus to Merret to protect against overselling during peak periods, while deferring financial postings to a daily cadence. This structure means ops can move at pace in Clarus while finance maintains a clean close in Merret without intraday noise.
How orders and inventory stay synchronised
The integration establishes Merret Retail Assist as the hub for order management and Clarus WMS as the engine for fulfilment. Orders approved in Merret are typically pushed to Clarus to initiate picking. As the warehouse team completes shipments, fulfilments and tracking details flow back from Clarus to Merret to update the order status and trigger financial postings. Inventory levels are synchronised to ensure that stock adjustments made in the warehouse are recognised by the ERP, maintaining a consistent view of available inventory. Constant monitoring within the integration layer detects failed transmissions before they compound into backlogs.
Middle layer for secure data orchestration
Cogent2 uses iPaaS to integrate Clarus WMS and Merret Retail Assist with ERP systems, ensuring secure, efficient data exchange. This approach supports WMS/3PL operations and enhances Clarus WMS and Merret Retail Assist functionality. iPaaS platforms with ISO 27001 and SOC 2 compliance and above ensure data security, offering a centralised framework for connecting systems, automating workflows, and maintaining strong security standards, making them ideal for businesses seeking reliable, scalable integration solutions.
Monitoring for inventory and order drift
Standard dashboards often fail to show why a record in Merret Retail Assist does not match the physical stock in Clarus WMS. We provide visibility that moves beyond simple success or failure metrics to surface the root causes of data drift. Our monitoring platform identifies orphan orders that fail to post to the WMS or stock updates that do not reach the ERP due to SKU mismatches. By catching these exceptions early, teams can resolve inventory discrepancies before they lead to overselling or fulfilment delays. This level of oversight ensures that the integration remains a trusted source for both operations and finance.
Operational handover for non technical users
Training ensures your finance and operations teams can confidently run the combined Clarus WMS and Merret Retail Assist environment. We document the operating model in plain English, outlining how data moves between systems and what tasks are required daily, weekly, and monthly. Teams learn how to interpret alerts from the integration layer and who owns specific exceptions, such as fulfilment delays or stock mismatches. We provide operational documentation designed for the people using the systems every day, rather than technical references for IT. This focus on clear ownership allows your staff to maintain data integrity across the warehouse and the head office.
Post launch governance and workflow stability
After launch, we provide ongoing operational support that goes beyond technical bug fixes. We monitor the data flow between Merret Retail Assist and Clarus WMS to ensure that inventory adjustments and order updates continue to align. When discrepancies arise, our team provides the insight needed to resolve the root cause rather than just treating the symptom. This proactive oversight ensures that your warehouse operations and finance reporting remain accurate as your order volumes grow and your processes evolve.
Common failures
Inventory latency and overselling.
Operational impact: Merret's view of stock becomes stale because stock updates from Clarus are delayed, often due to batch processing. This causes sales channels to sell SKUs that the warehouse cannot fulfil, leading to cancelled orders, poor customer experience, and a high volume of exceptions for customer service and fulfilment teams to manage. It directly impacts revenue and erodes customer trust.
Prevention / Action: The integration's highest priority should be the near-real-time synchronisation of inventory levels from Clarus back to Merret. An event-driven approach, where a stock change in Clarus triggers an immediate update, is preferable to scheduled batches. The logic must account for different stock dispositions in Clarus (e.g., available, quarantine, damaged) to ensure the available-to-sell quantity in Merret is consistently accurate.
Mismatched fulfilment and financial records.
Operational impact: Dispatch confirmations from Clarus fail to create corresponding Item Fulfilment records in Merret correctly. This means the finance team cannot recognise revenue or close Sales Orders, creating significant manual work during month-end reconciliation. Without timely fulfilment data in Merret, the customer service team cannot access shipping details, leading to longer response times and an inability to answer tracking queries.
Prevention / Action: Establish a clear source of truth: Clarus owns the dispatch event, and Merret owns the financial posting. The integration must ensure a shipment confirmation from the WMS is the sole trigger for creating an Item Fulfilment in the ERP. Implement robust exception handling and a daily reconciliation report to identify and alert teams to Clarus shipments that do not have a matching record in Merret within an agreed period.
Inconsistent product master data.
Operational impact: New SKUs created in Merret are not synchronised to Clarus before an order is placed, or critical attributes like barcodes or weight are missing. This causes order-to-WMS sync failures for any Sales Order containing that SKU, halting fulfilment entirely until it is manually corrected. These errors create a significant data administration burden and directly delay customer orders.
Prevention / Action: Define Merret as the single source of truth for all item master data. The integration process for new product introductions must ensure an item record is successfully created and validated in Clarus before that SKU can be made available for sale. Implement monitoring to flag any failures in the SKU synchronisation process so they can be fixed before blocking orders.
Incorrect returns processing and stranded stock.
Operational impact: Returned goods are processed and put away in the Clarus WMS, but the corresponding credit and stock adjustment is not correctly triggered in Merret. This results in physical inventory being unavailable for resale because Merret does not know it has been returned, leading to inaccurate stock levels for replenishment planning. It also delays customer refunds, increasing workload for CX teams and damaging satisfaction.
Prevention / Action: Design a two-step returns process in the integration. Clarus confirming receipt of a return should trigger a notification to Merret to begin the refund process. However, the stock should only be formally returned to sellable inventory once Merret confirms the credit note has been raised, ensuring the financial and physical inventory movements are kept in sequence.
Frequently asked questions
What happens if our product SKUs in Merret have a different format or length to those in Clarus WMS?
This is a common failure point that causes orders to fail when syncing from Merret to Clarus WMS. For example, if a Merret SKU exceeds the character limit in Clarus, the corresponding Sales Order will be rejected and will not be passed to the warehouse for fulfilment. This requires manual data intervention to correct the failed order and a permanent mapping adjustment to prevent future errors.
How do we prevent overselling if Merret's inventory updates are not real-time?
Merret's reliance on batch processing for inventory updates can create a dangerous lag between stock levels in the ERP and the warehouse, leading to overselling fast-moving products. A robust integration makes Clarus WMS the source of truth for physical stock, syncing frequent inventory updates back to Merret. This ensures the master inventory record in Merret is as accurate as possible, reducing the risk of selling unavailable stock.
Our products are sold as single items but stored in cases. How does the integration handle different Units of Measure (UOM)?
Mismatched UOMs are a frequent cause of stock and order errors between Merret and Clarus WMS. For instance, if Merret sends an order for 12 'eaches' but Clarus only recognises the SKU in a 'case of 12', the stock allocation will fail. A properly designed integration must include logic to translate UOMs for all order and inventory messages, ensuring accurate stock decrements.
How are customer returns processed between Clarus WMS and Merret to ensure stock and financial records match?
When Clarus WMS accepts a returned item into stock, this action on its own does not typically create the corresponding financial transaction in Merret. This can result in accurate inventory in the warehouse but an incorrect financial state, as no Credit Note is raised for the customer. The integration must ensure that a goods receipt event in Clarus triggers the creation of the correct credit transaction in Merret to complete the returns handling process.