Order Routing Single Location Implementation

What is the purpose of this article?

This is a sub document of order routing main document.Order Routing Implementation Document

The purpose of this article is to discuss the implementation when a single location existing with only one routing rule i.e., default rule for a workspace.

Approach discussed earlier

Earlier we had discussed an approach to add a new column “isOrderSplittingEnabled“ in order_additional_config table in DB. Thereafter it was decided to update the values of isOrderSplittingEnabled in that particular column in case of single location.

Challenge faced in the above approach

1. Handling needs to be done in GET and PUT API of account details of Inventory Engine Client Portal Project. This will increase the dependency of order routing fEature in multiple projects

2. While handling in inventory allocation, we will not know whether the workspace is having a single location or the location was pre decided while importing the order. The handling will be difficult.

Alternative approach

1. As the single location page will be shown in UI only if there is a default rule, we can directly update the default rule of that [particular workspace. In this approach neither there will a no need to add any new column nor there will be a need to do handling in inventory Engine Client portal project. Also there will be no need to do any additional handling in inventory allocation project. And it is easily achiveable.

What are the steps to achieving this task?

Handling in shipping service

1. Frontend will send a request body in the PUT API of order routing

   curl --location --request PUT 'https://test_test_ajeet.auperator.co/shipping/api/v1/routingrules/4696' \ --header 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6IlJVVXdSREZCUVRSRFFqQkdORFUxTVVZeE16ZEdPRFJHTnpORk5EaEJSVEU0TVVORk5qVTJOdyJ9.eyJodHRwczovL2FwcERhdGEiOnt9LCJodHRwczovL3VzZXJEZXRhaWxzIjp7ImlkIjoxNzIwLCJ1c2VyVHlwZSI6ImRlZmF1bHQiLCJlbWFpbCI6InNhdXJhdi5rdW1hckBlc2hvcGJveC5jb20ifSwiaHR0cHM6Ly9hY2NvdW50cyI6WyJibGFja2JlcnJ5cyIsIm1vbnRlY2FybG8iLCJ0ZXN0X3Rlc3RfYWplZXQiLCJzYXVyYXYiLCJ0ZXN0c3RhZ2luZyIsInRlc3RfdGVzdF9hamVldG9yZGVydGVhbSIsInRhYm9yZGVydGVhbWZjbmV3IiwicWFzdGFnaW5nIiwicWFzdGFnaW5nMjAyMyIsInFhc3RhZ2luZ2JscjAwMSIsInFhc3RhZ2luZ2NoZTAwMSIsInRhYmRlbHN5bXAwMSIsInRhYmRlbGhpc3ltcGhvbnkxMDIiLCJjb2RpdGFzLWxscHNhdXJhdiIsInFhc3RhZ2luZ2t0MDEiLCJxYXN0YWdpbmdrdDAyIl0sImh0dHBzOi8vd2FyZWhvdXNlV29ya3NwYWNlcyI6WyJ0ZXN0c3RhZ2luZyIsInRlc3RfdGVzdF9hamVldG9yZGVydGVhbSIsInRhYm9yZGVydGVhbWZjbmV3IiwicWFzdGFnaW5nMjAyMyIsInFhc3RhZ2luZ2JscjAwMSIsInFhc3RhZ2luZ2NoZTAwMSIsInRhYmRlbHN5bXAwMSIsInRhYmRlbGhpc3ltcGhvbnkxMDIiLCJjb2RpdGFzLWxscHNhdXJhdiIsInFhc3RhZ2luZ2t0MDEiLCJxYXN0YWdpbmdrdDAyIl0sImh0dHBzOi8vd2FyZWhvdXNlcyI6W10sImh0dHBzOi8vcGFydG5lcnMiOltdLCJpc3MiOiJodHRwczovL2VzaG9wYm94LXBheW1lbnQtcmVjby5hdXRoMC5jb20vIiwic3ViIjoiZW1haWx8NjEyZTE0NWVkNjQ5NmZjZjY2OTVmMTcxIiwiYXVkIjpbImh0dHBzOi8vZXNob3Bib3gtcG9ydGFsLWRldi5hcHBzcG90LmNvbSIsImh0dHBzOi8vZXNob3Bib3gtcGF5bWVudC1yZWNvLmF1dGgwLmNvbS91c2VyaW5mbyJdLCJpYXQiOjE3MDgwNzAzMzAsImV4cCI6MTcwODE1NjcyOCwiYXpwIjoiVFNIMlRYeDdXdmZ4NmhwcElGZnpsNWNiMU1HcXY5VnAiLCJzY29wZSI6Im9wZW5pZCBwcm9maWxlIGVtYWlsIn0.rxkfSrjCh-Oh8ZdT6EPvzizFEe00r06A6wPxAfVQ7vInEes669uEo5KFTQbv12SVul1qkNS3dlRtgsEK-SNjlzRELnF6tA84iNO1A0RkKEaaqA51T9PPRTXZb_4VSIM8sm2W9iS1dshlrYgJwK_RwIjyxlZEKj6Wdu63NnRFqQrLYDQ59h3_UcIsxuJaAmKPbRZqoBaD1mMMXVlDyMN0w0j1c8yHCE4lLfCXQeNY3xwVf6mpgqUE4V64NkeVONCU19eNEN_I_Wboy4XXdeYCRSuJv5PEbPSIIyRc3p73vNH7oqTRu1x7AJGY_KFMVbnKsK9o9bu1lZVmH0aygkf1Mw' \ --header 'Content-Type: application/json' \ --data '{ "isOrderSplittingEnabled" : "1", "actionType" : "update split button" }'

2. In the backend, an update query will run which will update the default rule with the new value of isOrderSplittingEnabled

   UPDATE order_routing_rules SET isOrderSplittingEnabled = '1' where id = 4696;

3. Once the update query has been run, we will fetch all the rules of that particular accountId and update them in memcache and then return all the rules as response.

4. Response of the PUT API

   { "orderRoutingRules": [ { "id": "4696", "accountId": "733", "ruleName": "Order routing & splitting rule", "priority": 4, "isDefault": "1", "status": "1", "isOrderSplittingEnabled": "1", "createdBy": "Eshopbox", "createdAt": "2024-02-08 22:53:32", "updatedAt": "2024-02-16 13:47:40", "routingRules": [ { "high": "Minimize order splitting", "mid": "Ship from the closest location" } ], "rules": { "AND": [ { "AND": [ { "property": "Payment method", "operator": "is", "value": [ "Cash on delivery", "Prepaid" ] } ] } ] } } ] }

Handling in inventory allocation service

1. Remove the check for externalWarehouseId = 0 ie., At current we are calling order routing API only when externalWarehouseId > 1. This check needs to be removed and order routing API needs to be called for all the orders.