asos Marketplace Mirakl and SAP ECC
Integration Agency & Consultants
High-volume trading on ASOS Marketplace Mirakl eventually outpaces the manual capacity of legacy SAP ECC environments. When order volumes spike, the gap between marketplace sales and ERP processing creates financial reconciliation debt and inventory lag. We align the high-frequency agility of Mirakl with the strict governance of SAP ECC to ensure every transaction is captured and fulfilled without manual data entry.
Auditing data gaps between Mirakl and SAP
We connect your asos Marketplace Mirakl and SAP ECC integrations with expertise across Marketplaces and ERP systems. Our consulting services are invaluable, offering in-depth system audit services that uncover inefficiencies and integration gaps between asos Marketplace Mirakl, SAP ECC, and other platforms. These audits empower both our consultants and your team to take decisive action, ensuring your ERP and Marketplaces tech ecosystems operate efficiently. This enables you to deliver a reliable, high-quality experience to your customers and maintain smooth business operations.
Solution Design
In this design, SAP ECC typically remains the master for inventory and financial reconciliation, while ASOS Mirakl serves as the source for sales events. We prioritise the mapping of marketplace data into SAP structures to prevent financial reconciliation errors. A common design trade-off involves inventory sync frequency: we often suggest balancing update speed with SAP ECC system load to ensure stability during high volume. Orders are typically sequenced to import on a defined schedule, while fee and settlement data are often reconciled in batches. This approach allows finance to close the books using the ERP as the single source of truth, while operations teams rely on consistent fulfilment statuses across both systems.
Mapping IDocs and marketplace order data flows
This integration maintains SAP ECC as the master for inventory truth while Mirakl drives the sales engine. Orders are imported into SAP via IDocs, where we map ASOS commission fees and VAT logic directly from the Mirakl order data to prevent out-of-balance financial postings. To protect system integrity, we use cross-reference tables to map ASOS identifiers to internal SAP Material Numbers. Stock updates are synchronised from ECC to Mirakl on a defined trigger, ensuring only validated SKUs are updated to prevent import errors. Once fulfilment is confirmed in SAP, tracking details and carrier codes flow back to Mirakl to satisfy marketplace requirements.
Orchestrating secure data exchange with compliant IPaaS
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between asos Marketplace Mirakl and SAP ECC, connecting Marketplaces and ERP systems. This approach simplifies data exchange between asos Marketplace Mirakl and SAP ECC, supporting Marketplaces and ERP requirements while ensuring compliance. IPaaS platforms offer centralised management, robust security, and scalability, making integrations more reliable and future-proof.
Surfacing financial exceptions and inventory mismatches
Common dashboards often fail to catch the silent errors that occur when marketplace data structures clash with rigid ERP validation rules. True visibility requires identifying when a financial posting is out of balance or when an inventory update has stalled. Our approach surfaces these operational exceptions early, allowing your team to address failed order imports or shipping data mismatches before they impact customer experience. We monitor for records that go out of sync, ensuring that what the marketplace shows to the customer aligns with the data held in your SAP ECC system.
Operating models for finance and ecommerce teams
Finance, operations, and ecommerce teams must own the daily reality of the ASOS Marketplace and SAP ECC flow. We hand over an operating model that defines where inventory truth sits and how marketplace fees are typically reconciled against ERP ledger entries. Training focuses on practical exception handling, such as identifying data mapping errors or tax discrepancies before they hit the general ledger. Your team learns to monitor the integration layer for alert triggers and understands which department owns specific failure types, from warehouse sync delays to price mismatches. We provide operational documentation written for the staff running the business, ensuring they can verify order ingestion and stock accuracy without needing a technical background.
Governance for marketplace performance and data stability
Post-launch, we monitor the integration’s performance, looking for the specific failure modes that can disrupt marketplace sales. Our support model is designed to catch data mapping errors or sync delays before they escalate into financial discrepancies or marketplace performance warnings. We provide a clear path for resolving issues while ensuring your internal teams have the visibility to manage daily exceptions. This continuous oversight helps ensure that as marketplace requirements change or your ERP configuration evolves, the integration remains stable and your data remains accurate.
Common failures
Incorrect commission and fee reconciliation
Operational impact: ASOS Mirakl's fee structures, particularly for commissions and VAT, often lack a direct equivalent in standard SAP ECC financial documents. This results in mismatched journal entries and payout records, compelling the finance team to perform manual, error-prone reconciliations. At scale, this can obscure the true profitability of the channel and introduces significant audit and compliance risks during month-end closing.
Prevention / Action: Design an intermediate processing layer or use specific integration logic to parse the ASOS settlement reports before creating SAP postings. This logic should segregate sales revenue, commissions, and VAT into distinct components that can be mapped correctly to SAP G/L accounts. The integration should validate that all components balance against the gross payout value before generating the final IDoc for financial posting, ensuring journal entries are consistently accurate.
Mismatched product identifiers and offer data
Operational impact: SAP ECC often uses internal material numbers or padded SKUs which do not align with the consumer-facing Offer SKUs required by Mirakl. This discrepancy causes offer import jobs to fail or, more seriously, associates incorrect inventory and pricing data with live ASOS listings. This forces merchandising and operations teams into reactive, manual investigations to diagnose why products are not appearing or why stock levels are inaccurate.
Prevention / Action: The integration should maintain a dedicated mapping table to correlate SAP material masters with ASOS Offer SKUs. This reference data must be used to translate all outbound product-related information, including inventory levels from an ATP check and pricing updates. Implement robust exception handling and monitoring to flag any data sent from SAP for a material that lacks a corresponding, valid Offer SKU in the mapping table.
Delayed order acknowledgement and dispatch confirmations
Operational impact: ASOS Marketplace enforces strict SLAs for sellers to acknowledge new orders. An integration that waits for a Sales Order to be successfully created in SAP ECC before acknowledging the order in Mirakl risks breaching this window, damaging seller performance metrics. This can lead to account warnings or suspension, directly impacting revenue and requiring intervention from the operations team.
Prevention / Action: Decouple the Mirakl order acknowledgement from the SAP Sales Order creation workflow. The integration platform should immediately acknowledge the order on the Mirakl API upon receipt, placing the order message into a reliable queue for processing into SAP. This ensures the SLA is met, while the separate workflow handles the internal creation of the Sales Order via IDoc, including retry logic for any transient SAP processing delays.
Inventory latency causing overselling
Operational impact: If inventory updates from SAP ECC are sent to ASOS Mirakl on a slow, infrequent batch schedule, a significant latency window is created. During this period, stock that has been allocated or sold via other channels may still appear available on ASOS, leading to overselling. Each oversold order requires manual intervention from customer service and fulfilment teams, damages the customer experience, and negatively impacts seller performance ratings.
Prevention / Action: Supplement periodic full-catalogue inventory syncs with event-driven updates from SAP ECC. Configure the integration to listen for specific inventory movement events (like goods issues or stock adjustments) within SAP. These events should trigger immediate, targeted API calls to update the stock levels for only the affected SKUs on Mirakl. This approach dramatically reduces the risk of overselling compared to relying solely on batch updates.
Frequently asked questions
How do we prevent 'Material Not Found' errors during the IDoc import if SKUs don't match?
We implement a mapping layer that connects the ASOS 'Offer ID' to your internal SAP Material Numbers. Without this translation, SAP ECC will reject the IDoc because the marketplace SKU does not exist in your master material list.
Why shouldn't we use the standard SAP VAT engine for ASOS global orders?
Using the standard SAP tax logic often leads to rounding discrepancies in the Finance module. We extract the marketplace-calculated tax amounts directly from the order data and map them to SAP to ensure the ledger stays in balance with the payout report.
How do we handle inventory sync for SKUs that aren't yet live on ASOS?
If SAP transmits stock for SKUs not yet validated by the ASOS category team, it can trigger errors that stall the sync. We apply a filter to ensure only active offers receive inventory updates, protecting the integrity of the Mirakl offer import process.
Our SAP system processes in batches. Will this cause us to miss ASOS's order acknowledgement window?
To protect your seller rating, orders are acknowledged via the API immediately upon extraction. This ensures you meet the ASOS service level while the data follows your standard SAP processing schedule.
How are partial fulfilments in SAP ECC handled back in Mirakl?
Mirakl requires a valid tracking number and a specific carrier code to mark an order as shipped. If your SAP ECC generates multiple outbound deliveries for a single order, we ensure each shipment is posted to the marketplace as it occurs.