Auperator Flow for Unfulfillable Orders

Open

1. Marketplace: When the order arrives from the marketplace such as Flipkart, Amazon etc then it is created using Create Order API as mentioned below:

POST API:

Sample Request Body:

Once the Order is created and API returns 200 OK response, an event is published to Middleware using PubSub topic: “create-order-middleware“

2. Middleware: At middleware, once the event arrives from Create Order API Service, the inventory allocation rule process the items present in the event. It checks the available inventory for the items and there can be multiple scenarios as explained below:

• If all the items are fulfillable then the Shipment is created

• If any item is Unfulfillable and the warehouse is configured to Auperator then in that case shipment will not be created. Instead, ESB-WMS-Order Service API will be called which will create an entry in the orders_unfulfillable table

2. ESB-WMS-Order Service: This Service is basically an API that will create an entry in the table known as orders_unfulfillable. The path of the API is as mentioned below:

Working:
1. If the order_id is already present in “orders_unfulfillable” table then check its shipmentStatus

2. If the order_id is not present then save the model the “orders_unfulfillable“ table.

POST API:

Request Body:

Mapping:

Success Case Response Body:

Failure Case Response Body:

3. Cron-Order Service: A cron will be implemented which will fetch all the entries/records from orders_unfulfillable table having shipmentStatus='PENDING', along with which we need to prepare a Shipment Event which will be pushed on a PubSub topic. After retrieving records from orders_unfulfillable the orders data will be pushed into TaskQueue in batches of 10

• PubSub Topic: 'order_unfulfillable'

• API Path:

GET API:

Order Event to be Prepared:

SQL Query to get details as shown in the above sample Order Event:

Note: We need to add constant key-value pair in the Shipment Event which will be pushed as given below:

Success Response Body:

Now this shipment event will be pushed on a PubSub topic as mentioned above. The listener for this PubSub topic is Middleware service only which will consume this event and will check whether the inventory is now available or not for the items present in the shipment event. Following scenarios can take place:

• If the Inventory is available now for all the items present in the Shipment Event then simply create the shipment and mark the shipmentStatus as “CREATED" in the orders_unfulfillable table

• If any of the item is Unfulfillable and the warehouse belongs/configured to Auperator then check for "orderUnfulfillable" if this exists in the Shipment event with value '1' then ignore and return otherwise call the ESB-WMS-Order Service

1. Cancelled event in: if any "inventoryStatus" = unfulfillable, then prepare wms cancel order request body and make a request

   1. Remarks = "fulfillment_cancel".

   2. For integrationType = "8",

      1. shipmentStatusLog.status must be "rejected" but only the item which is unfulfillable, set it's order_items.lineItemOrderStatus = "failure" and order_items.status="cancelled" (eventSubType="rejected" must be published).

      2.  no further shipment creation will be done for the remaining items.

1. For integrationType(4,11) run the inventory location and shipment creation for all items.

2. For other integrationType run the shipment creation for remaining items.

   1. shipment must be cancelled but only the item which is unfulfillable, set it's lineItemOrderStatus = "failure" and status="cancelled".

   2. New shipment will be created for the remaining items.