Overview

• RMS is integrated with Logistic Aggregators like Clickpost, Shiprocket and Shipway for Shipping Label Generation, Return Order creation, Notification updates etc. through API integration.

• These Logistic Aggregators are integrated with various Courier Partners like Delhivery,Bluedart etc. using their API endpoints.

• For the Clickpost and Shipwat Integration, RMS is integrated with their International APIs as well.
  These APIs facilitate Shipping Label Generation in MENA, EU, US and SEA regions.

• RMS also provides its RMS Magic APIs, using which any Logistic Aggregator System can integrate with RMS endpoints to use Standard Workflows of RMS.

Forward Order Workflows

Shipping Label Generation

• 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 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.

Multiple Shipping Label Configurations

• Just like how multiple invoice configurations are possible, multiple shipping label configurations are also possible.

• They will be identified with the help of logistic account aliases which are configured on RMS UI.

• This logistic account alias will then be passed in the request payload of the API call which will be used to identify the logistic configuration to be used.

Forward Notification Push

• Delivery Notifications for Forward Orders can be sent by Logistic Aggregator System in 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 can be of statuses mentioned below

  • DELIVERED

  • OUT_FOR_DELIVERY

  • CANCELLED

• The URL where notifications are to be pushed and the credentials to be used in the notification API call can be configured on the RMS UI.

Return Order Workflows

Return Order Creation

• Using this feature, Seller can generate Return AWB for a return order which is created on Brand.com or Standard Webhops like Magento or Shopify after the Return Order expectation is first pushed to Increff Standard APIs (Omni Magic APIs)

• There are 2 APIs available here:

  • Generate Return AWB API: This creates the return order and generates return AWB on the logistic aggregator portal.

  • Get Return AWB API: This fetches the return AWB from the logistic aggregator

• The same multiple configurations for Logistic Aggregator Credentials can be used here as well as mentioned it for Forward Order Creation Workflow.

Return Notification Push

• 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

1. 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 1 and keep it on hold using Shopify Custom tag 2.

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.

   1. For QC Status=Pass, Clickpost will update the order with Custom tag 2 to unhold the order.

   2. For QC Status=Fail, Clickpost will update the order to cancel those order line items or the whole order.

3. Increff Shopify integration layer will receive the updated order details in Update Order Webhook and will update the same in Increff OMS.

Using Shiprocket<>Returns Prime App Integration

1. The end customer places a return order on http://brand.com website built on top of Shopify.

2. 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.

3. 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.

4. Once the physical return shipment reaches the warehouse, QC checks happen in the return processing screen in Increff WMS.

5. Increff RMS sends the return processing updates to Returns Prime system through Returns Processing Update API.

6. Since the QC Status and QC Reason details have been passed to Returns Prime, refund processes can be initiated on Returns Prime.