asos Marketplace Mirakl and Reveni
Integration Agency & Consultants
Intelligent Consulting
Detailed Solution Design
Smooth Integration
Visibility
Training
BigCommerce
Common failures
Incorrect refund value processing
Operational impact: Reveni may calculate refund amounts that do not account for Mirakl's commission structures or seller-specific promotions. This creates discrepancies in financial reconciliation, forcing the finance team to manually adjust payout records and journal entries. At scale, this erodes profit margins and consumes significant accounting resources.
Prevention / Action: The integration's logic must use the Mirakl order data as the definitive source for all refund calculations, including item price, shipping, and discounts. When Reveni initiates a return, it should query the original Mirakl sales order to fetch the correct values before processing the refund. Logging the source calculation data for each refund transaction simplifies auditing and exception handling.
Return reason code mismatches
Operational impact: If customer-facing return reasons in Reveni are not mapped correctly to Mirakl's required disposition codes, returns fail to process within the marketplace. This delays customer refunds, negatively affects seller performance metrics, and requires manual intervention from customer service teams to investigate and resolve each case.
Prevention / Action: A strict mapping table for return reason codes between Reveni and Mirakl must be established and maintained as a core part of the integration. The process logic should treat any unmapped reason as a critical exception, halting the return and flagging it for immediate review. This prevents invalid data from causing downstream processing failures.
Inventory latency on returned stock
Operational impact: A delay between Reveni confirming a returned item is sellable and the stock level being updated in Mirakl means the asset is not available for purchase. This results in lost sales opportunities and can lead to discrepancies between the warehouse management system and the marketplace's view of available inventory. The fulfilment team sees stock, but the sales channel cannot sell it.
Prevention / Action: Structure the integration to trigger an inventory level update to Mirakl immediately following a 'restock' event in Reveni, rather than relying on a scheduled batch process. This returns workflow should be prioritised over less time-sensitive data syncs. Implement monitoring specifically for this job queue to ensure updates are processed promptly and to alert on any failures.
Missed order acknowledgement SLAs
Operational impact: ASOS Marketplace enforces strict time limits for acknowledging new orders within Mirakl. Failure to send the 'order accepted' status update via the API can result in automatic order cancellation and damage to the seller's performance rating. This causes lost revenue and complicates financial forecasting when expected orders fail to materialise in payout reports.
Prevention / Action: The integration design must prioritise the order acknowledgement process. On receipt of a new sales order from Mirakl, the immediate first step should be to send the acknowledgement status back to the API. This action should be handled as a high-priority, transactional job with a dedicated queue, robust retry logic for transient errors, and strict monitoring.
Frequently asked questions
How does a customer return from ASOS Marketplace get processed between Mirakl and Reveni?
The return is initiated on ASOS Marketplace, which creates a return record in the Mirakl platform. The integration then transmits this data, including original Sales Order details and SKUs, to Reveni to start the returns handling process. Reveni manages the physical return and refund logic, ensuring all actions are correctly linked back to the originating marketplace order.
My finance team struggles to reconcile ASOS payouts against refunds. How does this integration help?
The integration ensures that when a return is completed in Reveni, the correct refund value is mapped against the original Mirakl Sales Order. This provides a clear data trail for the finance team, preventing discrepancies between payout reports and actual refund costs. This avoids the common problem of manually matching individual refund transactions to ASOS payout statements during the month-end close.
What happens to our stock levels on ASOS Marketplace when an item is returned via Reveni?
Once Reveni confirms an item is returned and restocked, the integration automatically updates the inventory level for that SKU on ASOS Marketplace through the Mirakl API. This is critical for preventing overselling and ensuring returned products become available for repurchase without manual work. The process relies on accurate SKU mapping to avoid sync failures, for example when Mirakl rejects updates for products in a 'staging' status.
How does the integration handle different return reasons from ASOS Marketplace?
The integration maps the return reason codes provided by the customer on ASOS Marketplace to corresponding dispositions within Reveni. This ensures that when a return, such as 'damaged' or 'wrong item sent', is processed, it triggers the correct workflow in your operations. For example, a 'damaged' item can be routed to an inspection location and excluded from stock updates, while a 'wrong item' return can correctly update inventory for the returned SKU.