- Use case 1. Buyer requests a refund before the order is delivered
- Use case 2. Buyer requests a refund for a delivered order and Temu refunds without item return
- Use case 3. Buyer returns the item from the delivered order and receives a refund
- Partial refunds
- Inventory handling for returned/refunded items
- How Temu return and refund data reaches external systems
- Need help?
M2E Multichannel Connect synchronizes refunds and returns from Temu to your store. Refunds are issued on Temu, and M2E records them against the corresponding order in your store.
The use cases below cover the refund and return scenarios supported by M2E.
ℹ️ Temu refund and return synchronization is available for Shopify, BigCommerce, and WooCommerce stores.
Use case 1. Buyer requests a refund before the order is delivered #
Temu cancels the order rather than issuing a refund, because the buyer has not yet received the item. M2E detects the cancellation and updates the order status and relevant order details in your store.
On Temu: the order status changes to Canceled.
In your store: the order is marked as Canceled.
Use case 2. Buyer requests a refund for a delivered order and Temu refunds without item return #
Buyer requests a refund after receiving the order. Temu determines that the item does not need to be returned, which often applies to low-value items and items that arrived damaged. Temu issues the refund automatically, and M2E synchronizes the completed refund details with your store.
On Temu: the refund is completed without seller involvement.
In your store: the order information is updated to reflect the completed refund, including the order status and the refund amount.
Use case 3. Buyer returns the item from the delivered order and receives a refund #
Buyer requests a refund, and Temu requires the item to be returned. Once you have received the returned item, the refund is issued on Temu, and M2E synchronizes the completed refund details to your store.
On Temu: the refund is completed.
In your store: the order information is updated to reflect the completed refund, including the order status and the refund amount.
Partial refunds #
Temu partial refunds are reflected in your store with the amount refunded, not the full order value. For example, an order contains a jacket ($120) and a scarf ($30). The buyer requests a return for the jacket only, and Temu issues a $120 refund. M2E marks the order in your store as Partially Refunded, and the scarf line item remains unaffected.
Inventory handling for returned/refunded items #
M2E does not adjust inventory when a Temu return or refund is synchronized to your store. This is because neither a refund nor a return processed on the marketplace confirms that the item has been received or that it is fit for resale.
You need to adjust your store's stock manually after you receive and inspect the returned item.
How Temu return and refund data reaches external systems #
M2E does not connect to ERP, 3PL, or warehouse systems directly. It records order-related Temu events in your store, and your external system reads them from there through your store's standard API, the same way it reads order and shipment updates.
For events that originate on Temu, the data flow is:
Temu → M2E Multichannel Connect → Store → ERP / 3PL / warehouse system
Need help? #
If you have questions about how M2E synchronizes returns and refunds, or if an order in your store does not reflect what happened on Temu, please contact our support team.