...
Forward Order Workflows
| Drawio | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Using this feature, the Seller can generate AWB and Shipping Label Document for the shipments of Brand.com or Webshops like Shopify and Magento.
In this workflow there are theree three APIs available which are listed below:
Create Order API:
This will create the order in the logistic aggregator system.
The AWB will not be yet assigned to the order/shipment by Loigistic Aggregator System.
This is only applicable for Shiprocket and Shipway.
Generate Shipping Label API: This API will generats the AWB and Shipping Label PDF (Public URL) in Logistic Aggregator System after the Courier partner is assigned to the shipment.
Get Shipping Label API: This API fetches the AWB number details and Shipping Label Document which was generated in previous step from the Logistic Aggregator System.
...
Return Order Workflows
| Drawio | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Workflow Step | API Touchpoint | Summary |
|---|---|---|
1 | Generate Return AWB API | Sending notification to Logsitic Aggregator system to generate AWB for Return Shipment |
2 | Get Return AWB API | Retrieve details of Return Shipments like Courier Partner name, AWB number, Return Shipment Number etc. |
3 | Return Orders Notifications API | Receiving Shipment notifications like RETURN CREATED, RETURN PICKED UP, IN TRANSIT for Return orders from Logistic Aggregator to RMS System |
...
Notifications for Return Shipments will be sent by Logistic Aggregators to RMS system case the Notifications are enabled and Webhook details are configured on Logistic Aggregator System UI.
These notifications once received can be forwarded to any External systems by Increff Standard APIs based on the Webhook Endpoint URL configured in RMS User Interface.
Notifications for Return Orders can be of Statuses: RTO, RETURN_PICKED_UP etc.
Return/Exchange Workflow
Using Clickpost Integration
For any Return order which has created for which an Exchange order is asked by the end customer , Clickpost will create a Forward order as Replacement type using Shopify custom tags say
Custom tag 1and keep it on hold using ShopifyCustom tag 2.As soon as the Return order QC has completed in Increff WMS, Increff system will pass the QC information to Clickpost system using Increff RMS Standard APIs and based on QC status Clickpost will update the order data on Shopify webshop.
For
QC Status=Pass, Clickpost will update the order withCustom tag 2to unhold the order.For
QC Status=Fail, Clickpost will update the order to cancel those order line items or the whole order.
Increff Shopify integration layer will receive the updated order details in
Update OrderWebhook and will update the same in Increff OMS.
Using Shiprocket<>Returns Prime App Integration
The end customer places a return order on http://brand.com website built on top of Shopify.
The Returns Prime app captures this return order, generates the Return AWB via Shiprocket and makes the Create Return Order API call to Increff RMS system.
Increff RMS system will push the Return Order to Shopify Integration (same api and payload as for tracking updates from Clickpost/Shiprocket) and Shopify Integration will push the return expectation to Increff OMS system. The return expectation is now created in OMS.
Once the physical return shipment reaches the warehouse, QC checks happen in the return processing screen in Increff WMS.
Increff RMS sends the return processing updates to Returns Prime system through Returns Processing Update API.
Since the QC Status and QC Reason details have been passed to Returns Prime, refund processes can be initiated on Returns Prime.