Superdrug Marketplace Mirakl and SAP ECC
Integration Agency & Consultants
Superdrug Marketplace orders and settlement reports often reach a volume where manual processing in SAP ECC is no longer viable. The primary challenge for finance teams is reconciling Mirakl settlement data against SAP sales documents to ensure VAT accuracy and ledger balance. We focus on mapping these structured marketplace transactions into SAP ECC to automate the clearing of seller accounts and reduce manual reconciliation work at period-end.
Mapping architectural gaps and system audits
Cogent2 connects Superdrug Marketplace Mirakl and SAP ECC, ensuring your Marketplaces and ERP systems function efficiently. Our consulting services, including system audits, identify integration gaps and inefficiencies, enabling your team to take decisive action. By addressing these issues, we help your tech ecosystems operate smoothly, enhancing the customer experience. Our expertise with Superdrug Marketplace Mirakl and SAP ECC ensures your Marketplaces and ERP systems are optimised for performance, allowing you to deliver exceptional service to your customers.
Solution Design
For the Superdrug Marketplace Mirakl and SAP ECC integration, SAP ECC typically remains the financial source of truth for sales and tax liabilities. We design order flows to post into ECC, ensuring VAT and commission calculations are mapped to your chart of accounts. A primary design trade-off involves inventory sync frequency. While rapid updates protect seller performance on the marketplace, they can increase the processing load on legacy SAP ECC systems. We often balance this by choosing a sync cadence that maintains ERP stability while protecting against overselling. This design ensures the finance team can perform month-end reconciliations using validated ECC data, while the operations team manages marketplace transactions via Mirakl.
Automating the Mirakl order to cash cycle
This integration automates the order-to-cash cycle between Superdrug Marketplace Mirakl and SAP ECC. Orders are captured from Mirakl and transformed into SAP sales documents, applying logic to separate item prices from marketplace commission and fees. Inventory availability pushes from SAP ECC to Mirakl on a defined schedule, often incorporating safety buffers to protect your seller performance rating. Once fulfilment is confirmed in SAP, the status is pushed back to Mirakl to trigger customer notifications. The integration layer monitors these flows for sequence errors or mapping failures, ensuring that tax discrepancies or commission mismatches are identified before they reach the general ledger.
Orchestrating logic via compliant IPaaS layers
Cogent2 leverages IPaaS to integrate Superdrug Marketplace Mirakl with SAP ECC efficiently and securely. IPaaS connects Marketplaces and ERP systems, ensuring data flow and operational efficiency. It supports Superdrug Marketplace Mirakl and SAP ECC integration by providing a centralised framework. IPaaS platforms with ISO 27001 and SOC 2 compliance and above ensure data security. This approach enhances security, reduces complexity, and supports scalable, reliable operations across Marketplaces and ERP systems.
Surfacing discrepancies before they reach finance
Visibility requires detecting discrepancies where marketplace order totals or tax amounts do not match the SAP ECC record. We monitor these flows to surface failed syncs, out-of-sequence updates, and inventory gaps. Standard monitoring often misses these granular failures, which can create significant reconciliation work for finance teams. By surfacing these issues early, you can resolve master data mismatches or status errors before they lead to incorrect reporting or financial imbalances.
Adopting the shared marketplace operating model
Finance and operations teams adopt a shared operating model to manage the Superdrug Marketplace Mirakl and SAP ECC sync. The handover focuses on how marketplace data is mapped into SAP ECC, allowing finance to own the reconciliation of settlement reports. Operations teams learn to monitor inventory levels and shipping attributes that impact marketplace seller ratings. We provide operational documentation that explains how to read alerts and identifies which system owns specific data exceptions. This ensures teams know which system to check for order discrepancies, providing a practical guide for daily business ownership.
Managing API timeouts and reconciliation gaps
Support focuses on maintaining the data flow between Mirakl and SAP ECC. We monitor for technical failures, such as API timeouts, as well as operational exceptions like tax mismatches that cause reconciliation gaps. When issues arise, we provide clear context so the relevant team can resolve the problem quickly. This ongoing monitoring ensures that as your marketplace volume scales or ERP configurations change, the integration remains stable and your financial reporting stays accurate.
Common failures
Incorrect financial posting of marketplace transactions
Operational impact: When third-party seller transactions from Mirakl are created in SAP ECC as standard Sales Orders, it results in overstated revenue and incorrect VAT liability in the general ledger. This forces the finance team to perform time-consuming manual reconciliations to separate marketplace activity from direct sales during the month-end close and accurately calculate partner payouts.
Prevention / Action: Design the integration to use a distinct SAP Sales Document type (AUART) specifically for Mirakl orders, triggering separate accounting determination rules. The process must map Mirakl's commission and other fees to specific G/L accounts in SAP ECC, often via separate journal entries. This ensures Mirakl settlement reports can be programmatically matched against ledger postings.
Mismatched VAT and commission settlement data
Operational impact: The finance team finds that VAT and commission figures calculated natively within SAP ECC do not match the settlement reports provided by Mirakl. This creates journal imbalances and requires significant manual effort to investigate discrepancies for every payout period, delaying financial closing and risking inaccurate VAT reporting.
Prevention / Action: Establish Mirakl as the definitive source of truth for transaction-level commissions, fees, and tax. The integration should be designed to post these values from the Mirakl settlement file directly into the corresponding financial documents in SAP ECC, overriding standard SAP pricing and tax procedures for marketplace transactions. This often involves customising IDoc processing logic to accept these external values.
Delayed shipment and carrier confirmations
Operational impact: Dispatch confirmations and carrier tracking details from SAP ECC are not sent back to Mirakl quickly enough, or are rejected due to incorrect carrier codes. Because Superdrug monitors seller performance metrics closely, these delays can result in penalties and poor seller ratings. This is often caused by relying on slow, batch-based IDoc processing for outbound shipments.
Prevention / Action: The integration's fulfilment process should be event-driven, triggering an immediate update to Mirakl when a Post Goods Issue (PGI) is completed in SAP ECC for a delivery. This avoids delays associated with batch schedules. The integration logic must also include a mapping table to translate SAP carrier codes into the exact format required by the Mirakl carrier list to prevent data rejection.
SKU and offer data formatting errors
Operational impact: SAP ECC sends product master data containing internal formatting, such as SKUs with leading zeros, that Mirakl does not recognise. This mismatch causes inventory and price updates to fail for specific SKUs, leading to overselling or the deactivation of valid offers. The ecommerce or operations team is then left to investigate and manually correct the resulting stock and listing errors.
Prevention / Action: Implement a transformation step within the integration layer to normalise data before it is sent. This should include logic to strip or pad SKU identifiers to ensure they match across both systems. All key data points, such as units of measure or EANs, must have their formatting rules defined and enforced to prevent rejections by the Mirakl API. The source of truth for different product attributes should be clearly defined and respected by the integration workflow.
Frequently asked questions
How are Superdrug Marketplace fees and commissions handled in our SAP ECC system?
The integration maps the detailed Mirakl Payout and settlement reports to financial postings in SAP ECC, automatically creating documents that account for gross sales, commissions, and VAT. This avoids having the finance team manually reconcile and create separate journal entries for each payout. This is essential for maintaining an accurate general ledger and simplifying the month-end close process.
Which system becomes the source of truth for stock levels?
Typically, SAP ECC remains the master record for all inventory levels to ensure data consistency across your entire business, not just the marketplace. The integration pushes stock availability from SAP ECC to Superdrug Marketplace Mirakl on a regular, defined schedule. This direct sync is critical for preventing overselling on the marketplace and protecting your seller performance metrics.
Our SAP SKUs use a different format than our marketplace listings. How is this handled?
This is a common operational issue where SAP ECC may use padded or internal-only SKU formats. The integration provides a necessary transformation layer, mapping the Superdrug Marketplace Mirakl SKU from an incoming Sales Order to the correct Item record in SAP ECC. Without this mapping, orders would fail to post, requiring manual lookup and correction for every affected transaction.
How do we ensure shipment updates meet Superdrug's specific carrier requirements?
When an outbound delivery is processed in SAP ECC, the integration relays this status and the tracking data back to Superdrug Marketplace Mirakl. A key part of this process is mapping your internal SAP carrier codes to the exact 'Carrier' list specified by Superdrug's platform. Failing to map these codes correctly will cause the Item Fulfilment update to be rejected, impacting seller metrics and delaying customer communication.
What is the trigger for creating a Sales Order in SAP ECC?
The integration is typically configured to create a new Sales Order in SAP ECC as soon as an order is confirmed within the Superdrug Marketplace Mirakl platform. This automated process replaces the need to manually key in orders from marketplace reports, reducing both data entry errors and delays in the order-to-cash cycle. The mapping must correctly translate Mirakl order data into the required SAP IDoc format to prevent posting failures.
How does the integration handle returns and refunds initiated on the marketplace?
When a return is authorised in Superdrug Marketplace Mirakl, the integration can trigger the creation of a corresponding Return Delivery document in SAP ECC, instructing the warehouse. For refunds, the financial data from Mirakl's settlement reports is used to generate the necessary credit postings in SAP. This ensures the entire returns handling process, from logistics to financial reconciliation, remains synchronised between the two systems.