Inventory digitisation is often bought as a stock module and discovered to be an operating-model project. The software has to cope with the item master, units of measure, bills of materials, batch or lot traceability, work-in-progress, scrap and the gap between the warehouse and the shop floor. A buying decision that starts with a feature list usually ends with a system that finance tolerates and production works around.
This guide is for a manufacturer in Bangladesh that has decided to replace spreadsheets, a legacy inventory tool or a set of disconnected departmental systems. It sets out the requirements, the provider models, a scorecard, a pilot and the exit terms that protect the business after signing.
Start with the plant reality
Document the product families, routings, BOM depth, unit conversions, batch and expiry rules, locations, production order flow, costing method and the reports management actually uses. Include the exceptions: substitutes, rework, scrap, by-products and job work. If the process cannot be described on one page per product family, the requirements are not ready for a vendor.
Requirements by area
- Item master: one owner, a naming rule, duplicate prevention and a status for obsolete items.
- Units of measure: a base unit for every item and explicit conversion rules for purchase, stock and production.
- Locations: warehouses, bins, production lines and the movement rules between them.
- Purchasing: suppliers, purchase orders, goods received, inspection and landed cost.
- Production: orders, BOM versions, material issue, completion, scrap and rework.
- Traceability: batch or lot genealogy from receipt through production to dispatch.
- Costing: a method that finance agrees, with a sample calculation and reconciliation.
- Barcode and devices: label printing, scanners and shop-floor input that works with gloves and dust.
- Integrations: accounting, sales, payroll and any existing ERP, with a documented contract.
- Reporting: stock ageing, yield, variance, production status and the numbers used in the monthly review.
Provider categories
Full ERP suite. Broad and integrated, with one ledger for finance, stock and production. The implementation is heavier and the fit to a specific plant may be shallow without configuration work.
Manufacturing-focused ERP. Deeper production and costing features, often narrower commercial coverage. It fits a plant whose complexity sits in BOMs, routings and traceability rather than in retail or distribution.
Inventory or warehouse add-on. Strong stock control and barcode workflows, weaker production planning. It works when the core problem is accuracy in the warehouse rather than the shop floor.
Custom build on an existing system. Fits a genuinely unusual process and can preserve investments in an ERP. It creates a product to maintain, so the business needs an owner and a support plan.
Spreadsheet plus barcode pilot. A low-cost way to prove data quality and label design before buying a platform. It is a pilot, not a destination for a growing plant.
A scorecard
| Criterion | Evidence to request |
|---|---|
| Item master | A sample import, duplicate rules and an obsolete-item process |
| Units of measure | A conversion test using your actual purchase and issue units |
| BOM control | Versioning, effective dates and substitute handling |
| Traceability | A batch genealogy demonstration, not a report mock-up |
| Production flow | Release, issue, completion, scrap and rework in one sequence |
| Costing | A sample calculation reconciled to the current method |
| Integration | A documented API or file contract with your accounting system |
| Support | Local presence, a named engineer and an escalation path |
Pricing questions
Ask whether pricing is per user, per site, per module or per transaction, and whether shop-floor users are included. Confirm what data migration costs, whether integrations are in scope and whether devices and licences are separate. Ask for the annual support percentage, the cost of an additional site and the data export terms at exit. A quote based on one plant, one warehouse and a defined product family is more useful than a package price.
Pilot design
Choose one product family and one warehouse. Run the pilot for six to eight weeks. Acceptance criteria should cover a clean item master, correct unit conversions, BOM issues that reconcile, working batch traceability for a sample lot, and month-end stock and production reports that agree with the current method. Measure whether supervisors use the system without a translator, because adoption is part of acceptance.
Data migration and cutover
Cleanse the item master before import and freeze new item creation during the cutover window. Reconcile opening stock by location. Run parallel for one stock cycle if the risk is high. Define the cutover decision, the rollback path and the person who signs. A big-bang cutover without a reconciliation plan is a gamble with the month-end accounts.
Red flags
A demonstration on clean sample data, no unit conversion, no BOM versioning, traceability described as a report rather than a data model, no named implementation lead, no plan for shop-floor training, a contract that prevents data export and support available only from another country. These gaps surface after go-live, when the plant is already dependent on the system.
Decision framework
Choose a full ERP when finance and production must share one ledger. Choose a manufacturing ERP when production depth matters more than breadth. Choose a warehouse add-on when stock accuracy is the only problem. Choose a custom build when the process is genuinely different and you can maintain it. Pilot before committing to a multi-site rollout.
We build inventory and production systems under Custom Software & Integrations. The pricing page explains how discovery, delivery and support are separated. For the failure patterns this purchase should correct, read manufacturing inventory digitisation problems and fixes.
Sources
- International Society of Automation, ISA-95 enterprise-control system integration standard, accessed 17 November 2026.
- GS1, GTIN: Global Trade Item Number, accessed 17 November 2026.
- International Organization for Standardization, ISO 9001:2015, Quality management systems, accessed 17 November 2026.
- Microsoft, Inventory management in Dynamics 365 Supply Chain Management, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.