Picktask Handler For Wholesale Order Service

Overview

The current process(old world) has the POST /stock endpoint in the osp-event-handler-service. The OSP platform webhook is configured to call the stock endpoint. The stock end point often receives duplicate pick task with different events. The curent design simply ignores the duplicates, thus reporting comes up with wrong stocks of items from stores in RMS and SMS2.The demand forecasting from SMS2 hence cannot be accurate due to the above flaw. The obvious solution to this can be reversal of the duplicate items from the previous order.The WOS service(external) however has no facility / end-point for item / order reversal. The only option available now is to update the WOS only after the final event of the picktask is received. The picktask handler for the Wholesale Order Service(WOS) in new world is designed to overcome the mentioned limitations and challenges.

References

Document	Ref
Architecture Document	Solution Architecture.
Jira Epic	Duplicate pickTaskId processing:.
Bitbucket Repository	storepick-osp-wholesale-order-handler.

Components

Components

• Picktask-Wholesale Order Handler Runbook
• Picktask- Wholesale Order Infrastructure
• Code: Picktask Handler for Wholesale Order Service

Diagrams

Overview of the Picktask Handler for Wholesale Order Service

The below is the component & flow diagram for the picktask handler.

The section titled “WOS” is the scope of this handler. The right hand part in lite blue is the common kafka design.

Picktask handler for Wholesale Order Service contains following components i.e.

1. Order Aggregator

2. Post Cutoff Aggregator

3. Wholesale Order Transfer

4. Orders SQS & associated DLQ

5. Ready SQS & associated DLQ

6. Orders DB

7. S3 bucket for paylaod json