Merret Retail Assist and John Lewis Marketplace
Integration Agency & Consultants
When sales volume on John Lewis Marketplace scales, the gap between Merret Retail Assist inventory feeds and marketplace storefronts becomes a source of operational drag. At high volume, manual updates cannot keep pace, leading to stock discrepancies and the risk of overselling. This integration connects Merret Retail Assist with John Lewis Marketplace to ensure product listings remain accurate and orders flow directly into your fulfilment process without manual intervention. Success depends on reconciling Merret's ERP data with the marketplace's strict fulfilment windows to protect your vendor status and customer trust.
Auditing ERP and marketplace system logic
Cogent connects your Merret Retail Assist and John Lewis Marketplace integrations efficiently. Our consulting services are invaluable, offering system audit services that empower both our consultants and your team to optimise your tech ecosystems. This ensures smooth and efficient operations, allowing you to deliver an exceptional customer experience. By auditing your ERP and Marketplace systems, we identify and address inefficiencies, ensuring Merret Retail Assist and John Lewis Marketplace work harmoniously. This approach guarantees your ERP and Marketplaces operate effectively, enhancing your business's overall performance.
Solution Design
The design establishes Merret Retail Assist as the master for inventory and product data, pushing updates to John Lewis Marketplace on a defined schedule. Order ingestion is the priority, flowing immediately into Merret to trigger warehouse processes. A key design decision involves the trade-off between inventory sync frequency and system load; we typically use safety buffers in the feed to mitigate oversell risk during the batch intervals required by Merret's architecture. While despatch confirmations are automated, financial reconciliation of marketplace fees often remains a periodic batch process to ensure the finance team can verify payouts against ERP order totals. This approach ensures the warehouse works from a single queue in Merret while finance maintains a clear trust boundary for marketplace settlements. The design reduces operational latency and ensures fulfilments meet the John Lewis vendor lead time requirements.
Mapping inventory feeds and order flows
The integration maintains a controlled flow where Merret Retail Assist is the authoritative system of record for inventory and orders. Marketplace orders are ingested into Merret to trigger warehouse fulfilment, ensuring marketplace sales are treated with the same priority as direct-to-consumer orders. Stock feeds are synchronised on a defined schedule to prevent the sync illusion that often results from high-volume trading gaps. The integration maps carrier and tracking data from Merret fulfilment records back to John Lewis Marketplace at the line-item level, which is a critical requirement for prompt payment. Continuous monitoring surfaces data mismatches before they prevent an order from posting, keeping your storefront range accurate and your fulfilments on track.
Orchestrating data through secure middleware platforms
Cogent2 leverages IPaaS to deliver Merret Retail Assist and John Lewis Marketplace integration securely and efficiently. IPaaS connects ERP systems with marketplaces, ensuring smooth data flow. It benefits Merret Retail Assist and John Lewis Marketplace by automating processes and maintaining high security standards. With ISO 27001 and SOC 2 compliance and above, IPaaS platforms ensure data protection, making them ideal for integrating ERP systems and marketplaces securely.
Surfacing data mismatches and settlement drift
Effective visibility identifies hidden issues like settlement drift before they impact the bottom line. The integration monitors for specific John Lewis requirements, such as whether despatch confirmations include the necessary line-item tracking or if an EAN exists in the Merret master record. By surfacing these failures via the platform, teams can resolve mismatched carrier codes or stock sync errors before orders are cancelled or payouts delayed. Rather than static dashboards, visibility theatre is avoided by providing contextual alerts that trigger clear accountability for the ecommerce and fulfilment teams. This allows you to track the exact state of an order across both systems, ensuring data integrity is maintained through peak trading periods.
Defining team ownership and operational boundaries
Handover ensures finance, operations, and ecommerce teams own the daily flow between Merret Retail Assist and John Lewis Marketplace. We provide operational documentation defining the ownership boundary for each data object, such as who validates product attributes before a range goes live. Finance teams are trained to reconcile John Lewis payment reports against the Merret ledger, while ops teams learn to manage inventory sync exceptions. Documentation is a practical operating reference focused on day-to-day management rather than a technical archive. This ensures your team can identify where an order is stalled or why a SKU is suppressed without external support. Training is anchored in the specific design decisions made for your business setup.
Monitoring sync health and vendor ratings
Ongoing support manages the operational issues that occurs as your product range and order volume scale on John Lewis Marketplace. We monitor the connection to detect sync failures, such as tracking mismatches or suppressed SKUs, before they impact your vendor rating. When exceptions occur, they are surfaced with the necessary context for your ops or finance teams to resolve them according to your established ownership boundaries. We perform regular checks to ensure Merret remains the trusted source of truth and that marketplace fulfilment standards are consistently met. This move from reactive chasing to proactive oversight ensures inventory accuracy is maintained through peak trading periods.
Common failures
Vendor Lead Time and SKU Suppression
Operational impact: John Lewis requires specific Vendor Lead Time values in the product feed. If Merret's lead time logic is not perfectly aligned with the John Lewis calendar, the marketplace automatically suppresses the SKU from the storefront. This leads to immediate revenue loss as products disappear from sale without a direct stock-out event in Merret.
Prevention / Action: The integration must map Merret's availability lead times specifically to the John Lewis required formats. Monitoring should alert when a product is suppressed for a lead-time mismatch, allowing teams to adjust the Merret logic before the storefront listing is impacted.
Return and Refund Reconciliation Gaps
Operational impact: Returns processed in Merret do not always trigger an automatic refund via the marketplace API. Typically, an operator must manually reconcile the 'Return Pending' state in the John Lewis portal to release funds. If this second step is missed, customers experience refund delays, leading to CX complaints and negative marketplace feedback despite the physical return being completed.
Prevention / Action: The integration should surface the discrepancy between a processed Merret return and the John Lewis payment state. We design workflows that prompt the finance or customer service team to release portal funds once the Merret credit is authorised.
Line-Item Tracking Failures
Operational impact: John Lewis requires tracking numbers at the line-item level. If the Merret despatch data doesn't repeat the carrier code for every row in a multi-item shipment, the sync fails. To the customer, the order remains 'Unfulfilled' even though it has left the warehouse, triggering avoidable queries and delaying marketplace payouts.
Prevention / Action: Data mapping rules must ensure carrier and tracking codes are explicitly repeated for every item in the despatch flat-file. Automated validation checks for these requirements before the API call is sent to John Lewis.
Frequently asked questions
How do we handle the mismatch between Merret batch stock updates and John Lewis Marketplace?
Because Merret typically relies on batch processing, we use syncing logic tailored to these cycles. We often implement safety buffers in the inventory feed to John Lewis. This creates a stock 'cushion' that protects against the overselling that occurs when high-volume marketplace sales outpace the next available batch update from Merret.
What happens if our Merret carrier names don't match the John Lewis list?
John Lewis Marketplace requires tracking information to be mapped at the line-item level using specific approved carrier codes. If the carrier data in Merret does not align exactly with the JLP portal requirements, the despatch confirmation will fail. This leaves orders looking unfulfilled and delays your payment settlement. Our integration includes a mapping layer to ensure these values are translated correctly before submission.
Why are some of our Merret SKUs being suppressed on the marketplace storefront?
A common cause is a mismatch in 'Vendor Lead Time' values. John Lewis requires lead time logic that aligns with their specific operational calendar. If the data from Merret doesn't match these expected values, the marketplace may automatically suppress the SKU to avoid delivery promises that cannot be met. We ensure Merret's lead time logic is synchronised with John Lewis requirements.
Do returns in Merret automatically trigger refunds on John Lewis?
In most setups, physical returns processed in Merret do not automatically trigger the final refund through the marketplace API. An operator typically has to manually reconcile the 'Return Pending' state in the John Lewis portal to release the customer's funds. The integration highlights these pending states to ensure your team can complete the final financial step promptly and avoid customer service complaints.