Provide an operations owner, representatives of each working role, building and slotting information, item and order extracts, carrier account access and suitable devices. Confirm authority limits, quality decisions, stock ownership and acceptance criteria. Missing dimensions, identity data or connection access become explicit rollout work.
Implementation
Plan your warehouse rollout around the building, stock, connections and people who will use it.
Application configuration, connected equipment and operating acceptance are still required. Agree the rollout scope and readiness checks with your implementation team; timing depends on the building, source data and connections.
Implementation phases
Phase 1 · Team and ERP.ai
Map the operation
Walk receiving, storage, pick faces, pack benches and shipping. Confirm location codes, capacities, equipment constraints and which system owns each stock or financial effect.
Phase 2 · Team and ERP.ai
Prepare items and rules
Verify units, conversions, dimensions, weights, lot and serial controls. Configure put-away priorities, replenishment, count cadence, adjustment thresholds, pack tolerances and timezones with their owners.
Phase 3 · Team and ERP.ai
Set access and decisions
Assign people to roles and warehouses. Rehearse wave release, receipt close, count correction, label void and manifest close. Confirm delegation periods and the evidence needed for an exception.
Phase 4 · Team and ERP.ai
Connect and test
Exercise item and order feeds, purchasing, carrier accounts, devices and the financial destination. Include duplicate scans, lost carrier responses, repeated messages and rejected updates in the checks.
Phase 5 · Team and ERP.ai
Reconcile opening stock
Count and identify the stock by location and plate, with base units, lots, serials, expiry and holds. Load a reviewed opening baseline without sending historical receipt or shipment events. Agree the continuing physical-inventory and cycle-count policy with the customer's control owners.
Phase 6 · Team and ERP.ai
Rehearse a shift
Work a delivery, put-away, wave, pick, carton and carrier handover with the people who will run them. Include a short pick, damaged goods, an unknown label outcome and a count during other warehouse activity.
Phase 7 · Team and ERP.ai
Switch between waves
Complete or resolve released work in the old system. Reconcile open demand and expected receipts, activate the baseline once and release the next wave in the new application. A migration of in-flight work requires separate dependency and carrier reconciliation.
Phase 8 · Team and ERP.ai
Review early operation
Investigate recurring holds, placement overrides, replenishment shortages and count differences. Change rules through reviewed releases and verify the effect on the floor.
Use Proto to prepare configuration and application changes on a branch for review and release. Adding a zone or supported carrier service may be configuration; a new device protocol, carrier connector or materially different operating process needs its own implementation and verification scope.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.