Summary of enhancements:

  1. Addressing Issues in Create Shipment and Bulk Shipment Flow.
  2. Return and Replacement for Bundle Products.
  3. Order Allocation - Run order allocation rule excluding the rejected store.
  4. Ability to Capture Order Sub-status Change Comments.



Addressing Issues in Create Shipment and Bulk Shipment Flow

Context:

  • In the Orders & Leads -> Book Shipment -> Bulk Shipment page when a location is selected and searched the result is not accurate i.e. in the result also some orders which are not to be shipped from the selected location get populated

  • In the Orders & Leads -> Authorized page when multiple orders having multiple locations are selected to be bulk shipped, the location filter does not work

Solution:

  • In the ‘Bulk Book Shipment’ page, the results upon searching based on a location now lists correct orders only

  • When the ‘Bulk Book Shipment’ page is reached through Orders & Leade -> Authorized, then select more than one order, click Book shipment the ‘Bulk Book Shipment’ page opens. In this page now the following two cases are possible:

    • All orders are of the same location: The location filter will be disabled and only that location will be displayed.

    • The orders have more than one location: By default, the selected location will be ‘Multiple’ and the user will have the choice to choose any one of the locations and book the shipment



Return and Replacement for Bundle Products

Context:

  • When a bundle order needs to be replaced and when the parent product ID is added, only the parent product gets displayed. The ideal case is that all the child products also need to be included as a part of the replacement.

Solution:

Return of Bundle Child:

  • A new merchant level configuration ‘Allow Return of Individual Bundle Child Items’ has been created which will be enabled by default.

  • When this configuration is enabled, a return can be initiated for a single bundle child item if it's a physical product. When the configuration is disabled, bundle child items won’t be eligible for return initiation. 

  • Child items can only be exchanged with the same item or replaced with a different item. A refund for the child item alone is not allowed.

  • Return initiation through both the CP and the API will be validated based on the configuration. 

Return of Bundle Parent:

  • When a return is created for a parent bundle, the return will get created for all the child items of the bundle along with the parent by default.

  • This will be taken into account for returns created through the CP and the API.

Note: If the configuration ‘Allow Return of Individual Bundle Child Items’ is enabled, the parent item won’t be eligible for return if a return of a child item has been initiated already.

Replacement Order of Bundle Parent:

  • When a replacement order is created for a bundle parent product, all the child products will automatically get added to the new order.

CP Screenshot:



Order Allocation - Run order allocation rule excluding the rejected store

Context:

  • Currently, when a location (say Location A) rejects the item, it gets allocated to a different location (say Location B). If location B also rejects the order, then in the list of available locations, location A will also be available which causes the order to get allocated to location A again. This scenario causes a loop where the order gets allocated only to these two locations repeatedly on rejection.

Solution:

  • The allocation rule has been modified such that once a location rejects an order, the order won’t get allocated to the same location automatically. When all the possible locations reject an order it gets allocated to the default location and the default location, in turn, will allocate the order manually to a suitable location.


Ability to Capture Order Sub-status Change Comments

Context: 

  • If an order is allocated to a store and for some reason, if the store is rejecting the fulfillment order we update the sub status as "RJ" and it gets allocated to a different store. The client also wants to capture the reason in MJ if the store is rejecting the order

Problem Statement:

  • Currently, the platform doesn’t capture any comment for order sub-status change

Solution:

  • A new parameter ‘comment’ is added in the change sub status API. Now, comments for order sub-status change can be captured via Sub-Status Change API

  • The sub-status change comments are captured in Order Activity History

Sample API:

Order/ChangeSubStatus/{{merchant_id}}/{{order_id}}

MerchantId={{merchant_id}}&InputFormat=application/json&InputData={

   "ChangeSubStatus":{

      "SubStatus":"RJ",

      "Comment":"Testcomment",

      "OperatorId":"",

      "ItemLevelSubStatus":[

         {

            "OrderLineId":"abccdef",

            "SubStatus":"RJ"

         }

      ]

   }

}

Response:

{

    "messageCode": "1004",

    "Message": "Successful",

    "ErrorCode": 0

}