asos Marketplace Mirakl and Deposco
Integration Agency & Consultants
As ASOS Marketplace sales scale, manual order transfer into Deposco creates significant operational risk. ASOS enforces strict lead-time compliance. Delayed data transfer leads directly to marketplace penalty fees and damaged seller ratings. This integration automates the flow between Mirakl and Deposco, ensuring orders move quickly into the fulfilment cycle. By connecting these systems, teams can maintain delivery promises during volume spikes and prevent orders from remaining stuck in a pending status after they have been despatched.
Auditing the Mirakl and Deposco stack
We connect your asos Marketplace Mirakl and Deposco integrations with expert consulting, ensuring your Marketplaces and WMS/3PL systems work together efficiently. Our system audit services uncover integration gaps and inefficiencies between asos Marketplace Mirakl, Deposco, and your wider tech stack. This enables our consultants and your team to take decisive action, helping your Marketplaces, WMS/3PL, and fulfilment operations run smoothly. With our guidance, you can deliver a reliable, high-quality experience to your customers and support your business’s ongoing growth.
Solution Design
We typically treat Deposco as the master for inventory and shipping status, while ASOS Mirakl acts as the capture point for marketplace orders. A key design decision is the cadence of inventory pushes to ASOS to protect seller performance. We prioritising a consistent sync for order ingestion to Deposco to meet marketplace fulfilment windows, while financial settlement data is often handled on a schedule to simplify reconciliation. This involves a trade-off: higher-frequency inventory updates protect against overselling during peak periods but require more robust monitoring of API limits. Our design ensures that ASOS business rules are mapped correctly to Deposco logic, preventing status drift where orders remain 'pending' in the marketplace after they have been despatched. This architecture allows Ops to work from Deposco while Finance reconciles against settlement reports.
Mapping order flows and inventory logic
The integration manages the flow of orders from ASOS Mirakl into Deposco for fulfilment. Deposco typically acts as the source of truth for inventory, pushing available levels back to the marketplace to prevent overselling. When an order is shipped, the fulfilment status and tracking ID flow back to ASOS to close the order loop. We map relevant marketplace attributes to the Deposco item master to ensure data integrity during ingest. Monitoring is used to detect when status updates fail, which avoids orders remaining in a pending state incorrectly.
Orchestrating workflows via secure IPaaS middleware
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between asos Marketplace Mirakl, Deposco, Marketplaces, and WMS/3PL systems. This approach simplifies connecting asos Marketplace Mirakl with Deposco and other Marketplaces or WMS/3PL platforms, ensuring data integrity and compliance. IPaaS platforms offer centralised management, robust security, and scalability, making integrations more reliable and future-proof for businesses handling sensitive data.
Surfacing data drift and status exceptions
Standard dashboards often miss the logic gaps between ASOS and Deposco. We focus on surfacing exceptions where data drifts: orders that were accepted by the marketplace but rejected by the WMS due to SKU mismatches, or shipments that haven't triggered a status update in ASOS. Hidden issues like these compound during peak periods, leading to marketplace penalties. Monitoring identifies these failures early, allowing the team to fix the individual record before it triggers a broader performance warning.
Operational handovers for functional teams
We hand over a defined operating model to the teams running the business. For ASOS Marketplace and Deposco, this typically involves Ecommerce teams managing listing compliance and Operations owning the flow into the warehouse. We train finance on settlement reconciliation and CX on tracking order status across systems. Handover covers what to check on an agreed cadence, how to interpret integration alerts, and who owns specific exception types. Documentation is written as an operational manual for these roles, not a technical reference for IT. This ensures the team knows where each data object lives and how to resolve issues before they affect marketplace lead-time compliance.
Managing post-launch drift and order failures
Post-launch, we maintain ongoing operational ownership of the integration. We monitor for failed order imports, inventory sync errors, and shipping status gaps between Deposco and ASOS. Escalations are handled with an understanding of marketplace lead-time risks, ensuring that issues are resolved quickly. We provide active monitoring to catch technical drift, so your operations stay connected as your ASOS volumes grow.
Common failures
Delayed despatch notifications
Operational impact: If Deposco despatches an order but the integration fails to update Mirakl, the order remains 'pending' in ASOS. This breaches ASOS's strict lead-time SLAs, leading to financial penalties and negative seller ratings. The customer experience team is then forced to manage a high volume of queries for orders that have already been shipped.
Prevention / Action: The integration logic must guarantee the delivery of despatch confirmations from Deposco to Mirakl. Use a persistent queue for outgoing status updates and implement a retry mechanism with exponential backoff for API calls. Configure critical alerts to notify the operations team if a despatch notification fails repeatedly, allowing for manual intervention before SLAs are breached.
Inventory latency causing overselling
Operational impact: During peak periods, a lag in syncing inventory from Deposco to Mirakl can result in selling stock that is no longer available. This forces order cancellations, which severely damages seller metrics on ASOS. It also creates downstream work for fulfilment teams investigating stock-outs and for finance teams processing refunds.
Prevention / Action: Deposco must be the single source of truth for 'available to sell' stock. The integration should sync a calculated figure, not just total stock, based on physical inventory minus allocated stock in Deposco. Schedule frequent delta updates, especially during known sales events, and consider using the integration layer to maintain a small safety stock buffer as a final guard against overselling.
Failure to acknowledge new orders
Operational impact: ASOS Marketplace requires that every new order is programmatically 'acknowledged' via Mirakl within a strict timeframe. Failure to send this acknowledgement before the order is processed in Deposco can lead to ASOS automatically cancelling the order. This results in lost revenue and a confusing experience for the customer.
Prevention / Action: Sequence the integration logic to ensure order acknowledgement is the first step. Upon receiving an order webhook from Mirakl, the integration's first action should be to call the order acceptance endpoint. Only after a successful acknowledgement should the integration proceed to create the Sales Order in Deposco for fulfilment. This decouples compliance from internal processing.
Mismatched marketplace payout reconciliation
Operational impact: Mirakl payout reports contain sales, commissions, and fees which must be reconciled against despatched orders in Deposco. Integration failures, such as dropped refund statuses, create discrepancies that require manual investigation by the finance team. This delays the month-end close and makes it difficult to produce accurate performance and profitability reporting.
Prevention / Action: The integration must create and maintain a shared, unique identifier between the Mirakl order and the corresponding Sales Order in Deposco. Use this identifier to automatically match lines in the Mirakl settlement report against despatch and return records from Deposco. Any line items that cannot be matched should be automatically added to an exception report for the finance team to review.
Frequently asked questions
How does the integration stop orders getting stuck as 'pending' on ASOS Marketplace after they have been despatched from Deposco?
When a shipping confirmation and tracking number are created in Deposco, the integration automatically triggers a corresponding item fulfilment update in ASOS Mirakl. This action pushes the Sales Order status from 'pending' to 'shipped' on the marketplace, protecting your seller rating and preventing late despatch penalties.
ASOS has strict order acknowledgement rules. How does the integration meet these before the order even reaches the warehouse?
Immediately upon receiving a new marketplace order, the integration sends an 'Order Acknowledgment' confirmation back to ASOS via the Mirakl API, before the order is processed by Deposco. This secures the Sales Order within ASOS's required timeframe, preventing automatic cancellation and protecting your seller metrics before fulfilment begins.
We are worried about overselling on ASOS during flash sales. How does the integration keep inventory synchronised?
The operating model treats Deposco as the master for inventory, ensuring a single source of truth for stock levels. The integration sends available inventory data from Deposco to ASOS Mirakl at a frequent, defined interval. This ensures the quantity on the marketplace accurately reflects warehouse stock, which is critical for preventing overselling during high-velocity sales periods.
How do we move away from manually uploading ASOS order CSVs into Deposco?
This integration replaces the manual process by creating a direct API connection between ASOS Mirakl and Deposco for the full order-to-cash cycle. New Sales Orders from the marketplace are automatically created in Deposco as they are received, which removes the delays and human error associated with managing CSV files.
We have seen Mirakl report an inventory update as 'successful' when the file actually failed. How does the integration handle this?
We build our integrations to account for Mirakl's asynchronous processing, where an initial API response does not guarantee the file has been successfully validated. The integration monitors for the final processing status of any offer or inventory update sent from Deposco. This prevents discrepancies where a file fails post-submission, ensuring your stock levels on ASOS Marketplace are genuinely accurate.