asos Marketplace Mirakl and SAP B1
Integration Agency & Consultants
Manual reconciliation between ASOS Marketplace and SAP Business One creates immediate friction when month-end reporting falls behind. As boutique sales volume grows, the gap between Mirakl sales data and your ERP truth typically leads to inventory mismatches and delayed financial close. This integration connects ASOS sales directly to SAP B1, establishing the ERP as the definitive record for inventory and finance. This transition removes the operational drag of unlinked marketplace data and ensures your reporting stays on schedule even as channel complexity increases.
Auditing system architecture and process gaps
We connect your asos Marketplace Mirakl and SAP B1 integrations with expertise across Marketplaces and ERP systems. Our consulting services are invaluable, offering a thorough systems audit to uncover inefficiencies and integration gaps between asos Marketplace Mirakl, SAP B1, and other platforms. This enables both our consultants and your team to take decisive action, ensuring your ERP and Marketplaces tech ecosystems run efficiently. The result: smoother operations and a consistently excellent experience for your customers.
Solution Design
For the asos Marketplace Mirakl and SAP B1 integration, we typically treat SAP B1 as the system of record for inventory truth and financial reporting, while Mirakl serves as the frontline for order ingestion. One primary design choice involves the sequencing of order imports: we commonly prioritise rapid order ingestion into SAP B1 to secure stock against commitments, whereas financial settlement data is processed on a defined cadence to permit easier reconciliation against marketplace fees. A key trade-off is the synchronisation frequency of available-to-sell stock. Pushing inventory updates more frequently provides higher protection against overselling during peak traffic but increases load on the ERP. This design ensures finance can close the month accurately based on SAP B1 postings while operations rely on Mirakl for seller performance metrics.
Managing stock levels and shipment updates
The integration manages the flow of orders, inventory, and shipment data between ASOS Mirakl and SAP Business One to maintain financial trust. Orders are typically imported into SAP B1 only once they reach a status ready for shipping to prevent premature inventory allocation. To protect boutique seller performance, inventory levels are pushed from the ERP to ASOS on a defined schedule. Once fulfilment is processed in SAP B1, valid carrier codes and tracking details must flow back to the marketplace to trigger shipment confirmation. We monitor these flows to ensure every SKU is correctly mapped and orders do not become orphaned during transmission.
Orchestrating workflows via secure middleware platforms
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between asos Marketplace Mirakl and SAP B1, connecting Marketplaces and ERP systems. This approach simplifies data flow between asos Marketplace Mirakl and SAP B1, ensuring Marketplaces and ERP data remain accurate and protected. IPaaS platforms offer centralised management, robust compliance, and scalability, making integrations more reliable and secure.
Monitoring data drift and operational exceptions
Standard dashboards often show a running sync while missing the underlying data drift that breaks reconciliation. For ASOS and SAP B1, visibility targets specific operational failures like orders that fail to post due to ERP configuration or tracking numbers that do not meet marketplace requirements. We monitor for these exceptions early, alerting your team to orphaned orders or SKU mapping errors before they impact seller performance or cause a month-end backlog. This approach identifies the root cause of a sync failure rather than just reporting the symptom.
Handing over the marketplace operating model
Handover focuses on how your finance and ecommerce teams own the ASOS Marketplace and SAP Business One operating model. Finance teams learn to reconcile marketplace settlements within the ERP, while ecommerce operations monitor order ingestion and seller performance scores. Your team receives an operational playbook detailing daily checks and responses to common exceptions like SKU mapping errors or tax code mismatches. Training is anchored in the specific design choices made for the ASOS environment, ensuring teams know where each transaction lives and who owns the resolution. Documentation is provided as a practical guide for running the business, not a technical archive.
Preventing reconciliation debt after go live
Support is designed to prevent reconciliation debt from accumulating as marketplace volumes scale. We monitor the ASOS and SAP B1 link for issues that impact data integrity, such as when shipping data in the ERP does not match marketplace requirements. Rather than just responding to tickets, we evaluate integration behaviour to identify why orders fail to post or why inventory levels are drifting. This ensures the order-to-cash process remains stable, protecting your seller rating and allowing finance to trust the marketplace data during the month-end close.
Common failures
Inventory latency and overselling
Operational impact: ASOS penalises sellers for cancelling orders due to lack of stock, directly impacting seller metrics and platform visibility. When stock levels in SAP B1 are not synchronised accurately with Mirakl, the fulfilment and CX teams must manage oversold SKUs, leading to poor customer experience. At scale, this results in significant manual effort and reputational damage on a key sales channel.
Prevention / Action: The integration must treat SAP B1 as the single source of truth for inventory. Implement a scheduled, batched synchronisation of stock levels to Mirakl, balancing the need for accuracy against the risk of SAP B1 record locking. A safety stock buffer, configured either in SAP B1 or the integration layer, should be used to create a margin of safety that accounts for sync delays.
Missed order acknowledgements
Operational impact: ASOS Marketplace requires orders to be acknowledged via the Mirakl API within a strict timeframe, otherwise the order is automatically cancelled. This causes immediate revenue loss and damages seller performance scores. The first the operations or fulfilment team might know of a new sale is when it disappears from their queue, creating confusion and undermining trust in the automation.
Prevention / Action: Design the integration logic to send the 'Order Acknowledgment' immediately after the Sales Order is successfully created in SAP B1, not before. This confirmation step must be a robust, queued process with automated retries. An exception process must generate immediate alerts for any acknowledgement failures, allowing for rapid manual intervention to prevent cancellation.
Financial reconciliation gaps
Operational impact: The finance team cannot complete the month-end close because the payout reports from Mirakl do not match the sales and invoice data in SAP B1. This is typically caused by unmapped marketplace commissions, payment fees, or incorrectly processed refunds. This forces the finance team into time-consuming manual reconciliations, introduces errors into financial reporting, and obscures the true profitability of the ASOS channel.
Prevention / Action: The integration must post consolidated journal entries to SAP B1 that account for the gross sale value, Mirakl commissions, and any other fees detailed in the settlement reports. Use the Mirakl Order ID as the unique key to tie the payout data back to the original SAP B1 Sales Order or AR Invoice. An exception report should automatically flag any payout transactions that cannot be matched to a corresponding SAP B1 document.
Inaccurate dispatch notifications
Operational impact: Failure to send timely or accurate dispatch notifications to Mirakl breaches seller SLAs and negatively affects performance metrics. When the SAP B1 'Delivery' document is created but the integration fails to update Mirakl, the customer receives no shipping confirmation. This increases 'where is my order?' queries for the customer service team and makes it impossible for ASOS to track fulfilment performance.
Prevention / Action: The creation of a 'Delivery' document in SAP B1 should automatically trigger the shipping notification process to Mirakl. This process must include logic to map the carrier used in SAP B1 to the exact 'Carrier Code' required by ASOS Marketplace. All dispatch updates must include a valid tracking number. The integration should monitor for successful processing by Mirakl and flag any failures for operational review.
Frequently asked questions
How do you prevent the integration from slowing down our SAP B1 system during high-frequency stock updates?
Our integration architecture is designed to avoid using SAP B1's standard DI API for high-volume inventory updates, a common cause of record locking and performance issues. Instead, we use methods that allow for resilient stock synchronisation between SAP B1 and ASOS Marketplace without disrupting core ERP operations for your team.
ASOS has strict rules for sellers. How does the integration ensure order updates are sent on time?
The integration automates the critical 'Order Acknowledgment' in ASOS Mirakl immediately after a Sales Order is created in SAP Business One. When you later create a Shipment document in SAP B1 for that order, the integration automatically sends the required shipping notification back to the marketplace, protecting your seller performance metrics.
Our finance team struggles to reconcile ASOS payouts. How does this integration address that?
The integration can be configured to automatically post financial data from ASOS Marketplace settlement reports into SAP Business One. This creates corresponding journal entries for sales, refunds, and fees, which simplifies the bank reconciliation process and removes hours of manual data entry during the month-end close.
How do you map ASOS 'Offer IDs' to our existing SAP B1 item records?
We establish a definitive link between the ASOS Marketplace 'Offer ID' and the correct Item Master Data record in SAP Business One, typically using a cross-reference table. This prevents 'Material Not Found' errors when orders are posted from Mirakl into your ERP, ensuring the order-to-cash process runs without manual intervention.
We have several warehouses in SAP B1. How do you sync a consolidated stock level to ASOS?
The integration logic is configured to aggregate inventory levels from multiple specified warehouses (OWHS) in SAP Business One before sending a single availability figure to ASOS Marketplace. This ensures your marketplace listing accurately reflects the total stock available to promise, preventing both underselling and overselling.