How should an inventory and production system for a factory be customized?
Do not begin with a menu of features. First align material, unit, bin, batch, quality state, ownership, and inventory-balance definitions. Then use one real production order to complete purchase receipt, inspection, issue and return, production consumption, finished-goods receipt, sales dispatch, and traceability. Configure a standard ERP when it covers the main chain; customize only where shop-floor use, traceability, or integration creates a material difference.
Factory inventory differs from trading inventory because movements must connect to production, quality, and cost objects. One material may use purchase, stock, and issue units. One batch can be pending inspection, accepted, held, or scrapped. Work-in-progress moves between operations. If those meanings are disputed, software only spreads spreadsheet discrepancies faster.
| Route | Suitable condition | Advantage | Warning sign |
|---|---|---|---|
| Configure standard ERP/WMS | Conventional flow, few integrations, acceptable product definitions | Faster launch, mature upgrades and finance | Extensive workarounds or changes to core inventory logic |
| Standard system plus shop-floor extension | Purchasing/finance are standard; scanning, reporting, traceability differ | Keeps mature accounting while improving front-line work | Two systems both believe they own stock |
| Independent custom system | Distinctive production, deep legacy integration, strong data control | Tailored states and authorization | Unstable requirements paired with an attempt to rebuild all ERP |
| Organize the process first | Conflicting material codes, unknown stock variance, no owner | Exposes management gaps cheaply | Expectation that software resolves undecided rules |
Wavesteam does not default to full custom development. We test whether a product covers the main chain and critical controls, whether remaining differences affect throughput, quality, traceability, or compliance, and whether lifecycle and exit cost are justified. Historical habits may need process change; proprietary production or customer traceability may warrant custom work.
When separating device, connectivity, and platform responsibilities, also compare How can factory operations data be monitored and investigated online? and How should a small or midsize manufacturer begin digital transformation?; the linked guidance adds context that should be considered in the same decision.
Make balances the result of business events
Ordinary users should not edit a balance directly. Receipts, inspections, transfers, issues, returns, production reporting, finished receipt, dispatch, and count variances create immutable events. A reversal adds a linked opposite record with a reason rather than deleting history. Unit conversion retains precision and rounding.
A production order links planned BOM quantities with actual issue and return, accepted output, work-in-progress, rework, scrap, and pending disposition. The business owner confirms over-issue, negative stock, batch substitution, and backflush rules. Traceability must work backward from finished batch through material, supplier, inspection, and order, and forward from a suspect input to affected products and customers.
The ISA-95 integration framework helps separate enterprise planning, manufacturing operations, and field control and clarify exchanges among ERP, MES/WMS, PLCs, and devices. It does not prescribe one product, but discourages several systems from becoming simultaneous sources of truth.
Shop-floor acceptance uses real operators, gloves and lighting, production networks, scanners, damaged barcodes, repeated scans, batch split/merge, pallet and loose units, weak connectivity, and concurrent work. Offline operation needs reservation, conflict ownership, deduplication, and lost-device revocation—not only local form storage.
Wavesteam pilots a controlled scope covering representative materials, quality states, issue/return exceptions, and traceability for at least one full production and stock-count cycle. Baselines include inventory accuracy, handling time, shortages, count variance, excess issue, delayed entry, and trace time. We sample two-way traceability and reconcile purchasing, production, sales, and finance. Advanced costing, automatic equipment collection, and scheduling follow only after the base data remains trustworthy.