What is the currently implemented logic?

According to the current logic, the status is getting updated as follows:

• ACTUAL OUTCOME FROM CURRENT IMPLEMENTATION:

  PSEUDO CODE: FOR reference order_items is a table in our Database Various conditions according to which the current status is updated: 1. if (order_items.status == "ONHOLD") the condition is true then update the current status to ONHOLD 2. if (order_items.status=="CANCELLED") the condition is true then update the current status to CANCELLED 3. if (check if return flag is true means return is created){ and latestStatus is not null means it has a value then we update the current status to a status from RETURN } 4. else case { if latestStatus is not null we update the current status again to "NEW" in our case according to the logic }

  • Firstly it checks if the current status is “ON HOLD” and if it is true then we update the status to “ON HOLD”.

  • Secondly, if the current status is “CANCELLED” and if it is true then we again update the status so the final status after two movements is “CANCELLED”.

  • After the first two steps, we check if the return is created for the same order or not and if the return is created we check if “latestStatus” is not null means it has a value in it we update the current status again so, final status moves again to “RETURN ON THE WAY”

  • If the return is not created, we are again updating the status here which is in our case “NEW”

• EXPECTED:

Value required for the below logic to execute

1. order_items.onhold

2. order_items.status

3. order_items.returnFlag

4. order_items.reversePickupReason

5. order_items.warehouseInboundStatus

6. shipment_status_logs.latestReturnStatus

7. shipment_status_logs.latestOrderStatus

8. shipment_status_logs.latestOrderStatusBeforeDispatched

9. return_shipment_status_logs.latestReturnStatus

10. orders.thirdPartyShipping

• First, we will check whether order_item.status == “CANCELLED” AND returnFlag == 0, then show the current status as “CANCELLED” on export (break out of the function) cases should be made

• Check if shipment_id == 0 AND returnFlag == 0 then set the current status as “UNFULFILLABLE” (break)

• Now based order_item.status, check if order_item.onhold == 1 AND returnFlag == 0 set the current status to “ONHOLD” (break)

• When order_item.returnFlag == 1 AND order_item.warehouseInboundStatus == “received” set the current status as “RETURN IN PROCESSING” and then (break)

• When order_item.returnFlag == 1 AND order_item.warehouseInboundStatus == “complete”

  • Now check if order_item.reversePickupReason == “good_inventory” then set the current status as “RESTOCKED” and then (break)

  • Now check if order_item.reversePickupReason == “bad_inventory” then set the current status as “QUARANTINED” and then (break)

  • Now check if order_item.reversePickupReason == “lost” OR “partial_lost” then set the current status as “LOSTINPROCESSING” then (break)

• Fetch latestStatus of return shipment status log if order_item.returnFlag == 1 AND order_item.return_shipment_id != 0, set current order status on the basis of latestStatus and then (break).

• Fetch latest return status of shipment status log if order_item.returnFlag == 1 AND order_item.return_shipment_id == 0, set current order status on the basis latestReturnStatus and then (break)

• Fetch latest order status of shipment status log if order_item.returnFlag == 0, set current order status on the basis of latestOrderStatus (break)