Decathlon Marketplace Mirakl and Carma Tree Planting
Integration Agency & Consultants
Intelligent Consulting
Detailed Solution Design
Smooth Integration
Visibility
Training
BigCommerce
Common failures
Tree planting costs on refunded or cancelled orders.
Operational impact: Triggering tree planting on initial order placement means the business pays Carma for trees linked to orders that are later cancelled or fully refunded. This inflates the cost of the sustainability programme and requires the finance team to perform manual reconciliations between Mirakl payout reports and Carma invoices. At scale, this can lead to a material overstatement of both cost and environmental impact.
Prevention / Action: The integration's trigger for planting trees should be linked to an operational event that confirms the sale is final, such as 'order shipped' or after the returns window. This aligns the cost directly with settled revenue. A scheduled process should periodically compare Mirakl's list of shipped sales orders against the records in Carma to ensure alignment and flag exceptions for review.
Unrecorded planting actions from transient API errors.
Operational impact: If the integration calls the Carma API directly upon a Mirakl order event, any temporary network issue or platform unavailability can cause the planting action to fail silently. This creates a critical reporting gap between actual qualifying sales and the number of trees recorded, undermining the integrity of sustainability commitments. The operations team is left with no visibility of these failures until an audit reveals a large discrepancy.
Prevention / Action: Design the integration to be fault-tolerant using a message queue for all outbound requests to Carma. When a Mirakl order needs a tree planted, the integration posts a message to an internal queue. A separate worker process handles sending those messages to the Carma API, implementing a retry strategy with exponential backoff for failed attempts. Any message that fails permanently should be routed to an exception handling workflow for manual investigation.
Inaccurate impact reporting on partially fulfilled orders.
Operational impact: When a customer order is partially cancelled or split into multiple shipments, a simple 'one tree per order' logic breaks down. This can result in planting a tree for an order that was mostly cancelled, or creating confusion for customers and the CX team. It complicates reporting for the finance and sustainability teams, who cannot accurately attribute impact to fulfilled sales value.
Prevention / Action: The source-of-truth for the planting trigger must be the shipment event, not the initial sales order. The integration logic must inspect the shipment data from Mirakl and determine the planting logic based on business rules, such as planting only on the first shipment of an order. This ensures the link between a fulfilled, revenue-generating transaction and the corresponding sustainability action is always clear and auditable.
Incorrect planting due to poor product eligibility data.
Operational impact: If tree planting is tied to specific products, relying on inconsistent SKU data or tags in Mirakl can cause errors. Trees may be planted for excluded items, incurring unnecessary costs, or missed for eligible items, failing to meet marketing commitments. This places a constant manual audit burden on merchandising and finance teams to validate that Carma invoices align with sales of eligible SKUs.
Prevention / Action: Establish a clear source of truth for product eligibility using a specific Mirakl custom field or a predefined list of SKUs managed outside the marketplace. The integration logic must check this eligibility flag for each line item in a sales order before triggering a tree planting action. Regularly scheduled audits should compare the master list of eligible SKUs against the products for which trees were actually planted to catch any data drift.
Frequently asked questions
At what point in the Decathlon Marketplace order process is a tree planted in Carma?
Planting a tree prematurely can create reporting errors. The integration avoids using initial Decathlon Marketplace Mirakl statuses like 'STAGING', because these orders may not be confirmed. Instead, the trigger to create a Carma Tree Planting record is tied to a definite commercial event like 'order shipped', ensuring trees are only recorded for finalised sales orders.
What happens to the planted tree record if a customer's order is refunded?
When Decathlon Marketplace Mirakl processes a customer refund, this action does not automatically reverse the corresponding record in Carma Tree Planting. This creates a data gap, leading to over-reporting your environmental impact. The integration corrects this by ensuring a confirmed refund on a Mirakl sales order explicitly triggers a corresponding cancellation or adjustment in Carma.
We are scaling quickly on Decathlon Marketplace. Can this integration provide the verifiable proof needed for our sustainability reports?
Yes, this is a primary function for scaling brands. By linking every fulfilled sales order from Decathlon Marketplace Mirakl to a unique record in Carma Tree Planting, you move beyond high-level estimates. This provides the transaction-level data required for auditable sustainability reporting and demonstrates a direct, verifiable link between marketplace growth and environmental action.
How does the integration handle orders with multiple items or partial shipments?
This is defined by the operating model, as Decathlon Marketplace orders can be complex. The integration logic can be configured to create one Carma Tree Planting record for the parent sales order, or one record per item or SKU sold. This flexibility prevents inaccurate tree counts when an order is fulfilled in multiple parts, ensuring reports align precisely with your commitment.
We are concerned this will create another complex dataset to manage. How do we get a unified view of sales and impact?
The integration is designed to reduce complexity, not add to it. A shared identifier links the Decathlon Marketplace Mirakl sales order to its corresponding Carma Tree Planting record. This enables a consolidated view for reporting and auditing, allowing your team to trace a specific customer order straight through to its verified environmental impact without manual reconciliation.