Fynd Shipment Accept/ Reject Flow

Open

Open

Step 1: Eshopbox Shipment Service will listen to the WMS Update Shipment Event from PubSub.

Step 2: From this WMS Event extract the “integrationType" and “resource”. Before moving on, make sure that the integrationType is “Fynd“ and the resource is “shipment”. If these conditions are met, and the eventSubType is either “accepted” or “rejected”, push the update shipment request into the TaskQueue.

Step 3: After that tasks are listened one by one from the taskQueue and requestBody is formed then.

Step 4: RequestBody Formation: 

Check the eventSubType in the WMS event request body

3.1 If the eventSubType is “rejected”, Mark the status as “bag_not_confirmed”.

3.2 If the eventSubType is “accepted”, Mark the status as “Confirmed”.

Step 5: In Case of order eventSubType : “rejected”. Post Order Cancelation API by following Request Body.

Request Body:

Parameters:

note:

• Must provide cancellation reason_code on bag level.

• Partial shipment cancellation is allowed before confirming and never after confirming.

• Complete shipment cancellation is allowed until the bag is not picked by the delivery partner.

Response :

HTTP status: 200

Step 6: If the eventSubType is “accepted”:

6.1  It try to fetch the access token and inputFields(to get sellerCode) from the cache. 

6.2.  If it is not found in the cache, then it retrieves it from the Database (ie_appinstall_connection

         table), using the connectionId fetched from WMS event body.

It is then stored in the cache memory in the following format:

6.3 Now we have accessToken.

1. will call a new method to check the customer cancellation status by passing parameters accesstoken, shipmentevent.

2. In the method at first i will retrive customer order number from shipment event. Prepare a request body to call fynd get Shipment API

3. Now add a header in the request as : ApiKey <{{accessToken}}>

4. call the get shipment API :

Request Body:

Response Body :

1. call a method and check for the particular customer Number if for any Item Shipment ID is 0 or not

2. check if for any item shipment ID = 0

6.4 Now make order Status Update In API by replacing the ApiKey with the accessToken we retrieved.

6.5 Now add a header in the request as : ApiKey <{{accessToken}}>

Step 7: Call the Post Order Confirmation status Update In API to update the shipment status with requestBody:

Request Body:

Note:

• In the shipment accept case also we can partially Reject “if for some item Shipment_id=0” (ignore those items in the request body) and Post Shipment Confirmation.

• In case of order confirmation is raised for shipment was part item is cancelled by the customer, confirm non-cancelled item and consider the request as a success.

• Limit 100 orders per transaction

• Mark status as “confirmed”

• In case of order confirmation is raised for shipment where the entire shipment is cancelled by the customer, fail the shipment update.

Response:

Situation 1: Request successful
http status: 200

Situation 2: Request partially successful
http status: 200

Situation 3: Request failed
http status: 200

1.Invalid Token Error Handling Flow : In case of any error due to invalid token - call refresh token API

1. get connection Detail using the below API

2. fetch existing connection detail from database using connectionId.

3. call the fynd refresh token api using the ConnctionId details

API Method: POST

Request:

Response:

4. update the new details in database against the connectionId.

5. get the existing cache detail (save in a variable existingCacheDetailMap)

6. Clear old cache and create new cache from new detail of db