Overview
A return order cannot be processed in the Assure system, if the forward order has not been dispatched via the Assure System. For all such return orders, please receive them in your ERP and then Stock Transfer to Assure.
Marketplaces Return Integration Issues
Marketplace | Returns Integrated ? | Issues |
Flipkart | Yes | Their AWB on packet vs. what we get in the return order no. changes. All return orders also don’t come in because Flipkart APIs to fetch return orders are not evolved. |
Myntra | Yes | All return orders also don’t come in, because Myntra does not push around 5% orders. |
Snapdeal | Yes | All return orders also don’t come in because Snapdeal APIs to fetch return orders are not evolved. |
Amazon EDI | Ongoing | Amazon sends Return data via API for already existing Sellers. However for new Sellers API does not share the Return data.
CRET portal has been deprecated and new sites are not provided CRET portal. Seller need to process the return as they receive. 1) Sellable - Seller should inbound the inventory as they do in case of normal inventory inbound. 2) Damaged - Seller Flex (and WI) has the flat damage reimbursement policy, at category level, hence seller need not to do anything for damaged product. 3) Swithroo - Seller needs to fill a form to raise the swithroo claim (Link - https://survey-az.tfaforms.net/1780) 4) LIT (Lost in Transit) - LIT reimbursements are pro-active basis the trans scans of the customer returns. For cases of disputes, trans scans shows "delivered", seller claims "undelivered", seller needs to raise reimbursement claim via Seller Central Return-recon report shared at seller level, is to be used by seller for return-reconciliation. Return data is created, once customer returns have been picked up by Trans. |
PayTM | Yes | The return APIs run well, but still there are few orders which don’t come via their APIs |
Amazon MWS | No | The returns APIs are not integrated as no client is using this integration because Amazon MWS is not suitable for large scale operations |
Limeroad | No | Limeroad does not have APIs to fetch returns as per our last API review |
Nykaa | No | Nykaa has APIs to fetch returns but we are not integrated because of low volumes of orders. |
TataCliq | No | TataCliq does not have return APIs. Some other players like Unicommerce have asked TataCliq to use Unicommerce APIs for full integration. Increff may take that approach only if return order volumes per warehouse is large (say 200 / day). Also TataCliq has mentioned that they will be developing returns APIs in 2020. So it is a wait and watch for us |
CloudTail | No | CloudTail is B2B2C. All returns directly go back to CloudTail warehouse |
FirstCry | No | They don’t have APIs |
Olabi | No | This channel is used to fulfill store replenishment orders. So this is a B2B channel. |
Ajio Dropship | Yes | This works 100% correctly. Occasionally we have seen these APIs break from AJIOs side. |
Brand Portal (Shopify) | No | There is no return flow available on Shopify platform itself. |
Brand Portal (Assure Magic) | Yes | Brand portals can push return orders via Assure Magic APIs. But we’ve seen issues happening from brand’s portals. |
B2C Returns Process
Following table gives you a guidance on how to process B2C Return Orders. Please follow these steps wherever it is mentioned Manual Return Order Upload.
Marketplace | Process |
Flipkart | Manual Return Order Upload |
Myntra | For the return orders which don’t come from Myntra, a request has to be raised to Myntra to push those orders. |
Snapdeal | Manual Return Order Upload |
Amazon EDI | If Item ID is present on Returned Item:
Ops team has to scan both the item_id & AWB from the returned shipment in Excel sheet.
Use the item id in the report Outwards : Shipped Order Items Detail Report - WMS to get the forward order details.
Upload this data in CIMS and process the returns.
If Item ID is not present on Returned Item:
If the item_id is not there,
Please follow the below process
Take the list of AWBs and share it with the Amazon team to get the forward order details.
Upload this data in CIMS and process the returns
First process returned inventory in CRET portal given by Amazon Download the CRET returns report Follow Manual Return Order Upload process |
PayTM | For orders not received via PayTM returns, use the Manual Return Order Upload process. Use this manual process for only those orders which have not been received automatically via APIs. |
| Amazon MWS | Not applicable for now. |
Limeroad | Manual Return Order Upload |
Nykaa | Manual Return Order Upload |
TataCliq | Manual Return Order Upload |
CloudTail | Not applicable as all returns directly go back to CloudTail warehouse |
FirstCry | Manual Return Order Upload |
Olabi | Not applicable |
Ajio Dropship | For orders not received automatically in the system, raise issues to Ajio with AWBs. They should re-push the return orders to Assure.
|
Brand Portal (Shopify) | Manual Return Order Upload |
Brand Portal (Assure Magic) | For orders not received automatically in the system re-push the return orders to Assure. You should get in touch with your portal administrator or support services to do the same |
Note: You will come to know about orders not received automatically in the system , only after trying to process the return inventory on the Return Processing Screen. The system will show you an error for such inventory - "No Return Orders Found”.
Please connect with our customer support to get Marketplace contacts.
