WMS Inward Module Development
Budget: ₹1,500 – ₹12,500 INR
I am extending our in-house Warehouse Management System so that the entire “inward” process runs without spreadsheets or manual data entry. Your task is to deliver a production-ready Inward Module that plugs directly into our existing ERP and CRM stack.
Scope of work
• Automatically pull every confirmed Purchase Order from the ERP and open it in the WMS as a draft inward record.
• Let the warehouse team finish the record by capturing the three essential data groups exactly as they sit in the PO—Product details, Vendor information and Quantity received—plus any batch or serial identifiers the ERP already stores.
• Generate the standard receiving documents (GRN, inspection sheet, discrepancy note) on the fly and email them to the internal mailing list the moment an entry is saved.
• Surface real-time status inside the WMS dashboard and fire an alert if the quantities logged differ from the PO so that finance and procurement see the variance immediately.
• Push the final, verified inward data back to the ERP through the same API endpoint we currently use for sales dispatches, keeping master stock figures in one source of truth.
Tech context
The core WMS is written in Nodejs with Reactjs front-end components. We expose and consume JSON REST APIs for all external links, so stay within that pattern. Source code will live in our private GitHub repo and the build is containerised with Docker; you will branch off develop and raise PRs when milestones are met.
Acceptance criteria
1. A PO imported from the ERP can be located in search within two seconds.
2. An inward entry cannot be closed unless product, vendor and quantity fields are populated.
3. On save, the correct GRN PDF lands in the test mailbox and the record appears in the ERP stock table within one minute.
4. Any mismatch between PO quantity and received quantity produces a red banner in the UI and an email alert marked “discrepancy”.
Hand-over items
• Clean, documented source code and migration scripts
• Postman collection for every new API route
• A short README explaining environment variables and deployment steps
That is the full shape of the module I need; everything else in the WMS is already operational and will be demonstrated in a brief onboarding call.
Scope of work
• Automatically pull every confirmed Purchase Order from the ERP and open it in the WMS as a draft inward record.
• Let the warehouse team finish the record by capturing the three essential data groups exactly as they sit in the PO—Product details, Vendor information and Quantity received—plus any batch or serial identifiers the ERP already stores.
• Generate the standard receiving documents (GRN, inspection sheet, discrepancy note) on the fly and email them to the internal mailing list the moment an entry is saved.
• Surface real-time status inside the WMS dashboard and fire an alert if the quantities logged differ from the PO so that finance and procurement see the variance immediately.
• Push the final, verified inward data back to the ERP through the same API endpoint we currently use for sales dispatches, keeping master stock figures in one source of truth.
Tech context
The core WMS is written in Nodejs with Reactjs front-end components. We expose and consume JSON REST APIs for all external links, so stay within that pattern. Source code will live in our private GitHub repo and the build is containerised with Docker; you will branch off develop and raise PRs when milestones are met.
Acceptance criteria
1. A PO imported from the ERP can be located in search within two seconds.
2. An inward entry cannot be closed unless product, vendor and quantity fields are populated.
3. On save, the correct GRN PDF lands in the test mailbox and the record appears in the ERP stock table within one minute.
4. Any mismatch between PO quantity and received quantity produces a red banner in the UI and an email alert marked “discrepancy”.
Hand-over items
• Clean, documented source code and migration scripts
• Postman collection for every new API route
• A short README explaining environment variables and deployment steps
That is the full shape of the module I need; everything else in the WMS is already operational and will be demonstrated in a brief onboarding call.