Bring the product and location masters, stock extracts, original cost evidence, active claims and open receipt, issue, transfer and return documents. Include the people responsible for warehouse operations, purchasing and accounting, plus the approval and access policies they will use. Reserve time for actual operators to rehearse the work and verify that protected costs remain protected.
Implementation
Plan the first release around trusted quantities, costs and warehouse responsibilities.
Start with a defined group of products and locations, the physical work they perform and the outside systems that own demand, purchasing and accounting.
Implementation phases
- Agree the operating boundaryTeam and ERP.ai
- Configure identities and controlsTeam and ERP.ai
- Prepare the opening positionTeam and ERP.ai
- Rehearse ordinary work and exceptionsTeam and ERP.ai
- Rehearse counts and accountingTeam and ERP.ai
- Accept and releaseInventory Manager
Phase 1 · Team and ERP.ai
Agree the operating boundary
Choose the warehouses, shallow bins and stocked product/site combinations in scope. Identify external purchasing, sales, service and accounting owners. Define when receipt, ownership, issue, transfer arrival and return disposition are established by actual evidence.
Phase 2 · Team and ERP.ai
Configure identities and controls
Set product units, product-specific conversions, lot and serial requirements, ownership and expiry policies. Choose the installation valuation currency and effective cost methods. Configure site access, protected costs, independent approval limits, count tolerances and reorder settings, then activate reviewed policies.
Phase 3 · Team and ERP.ai
Prepare the opening position
Retain source namespaces, cutoff dates, identities and digests. Reconcile current positions with remaining cost layers, holds, picked stock, claims and transit. Preserve partial-document history and pending provider requests. Current opening stock and its historical movements must not both add the same quantity again.
Phase 4 · Team and ERP.ai
Rehearse ordinary work and exceptions
Receive and put away a partial delivery, reserve and issue stock, transfer it between locations and resolve a return. Check product-unit conversions, original expiry and serial uniqueness. Test repeated scans, cancelled picks, unknown costs and an unresolved transit shortage.
Phase 5 · Team and ERP.ai
Rehearse counts and accounting
Begin a blind floor-stock count with its full scope controlled, then test a recount, discovered stock and a stale or expired lock. Reconcile goods physically away in transit separately through transfer evidence. Confirm eligible automatic differences and independent exceptions. Reconcile the opening value plus accepted incremental exports to closing stock, including cost-method changes and corrections.
Phase 6 · Inventory Manager
Accept and release
Have the operating owners review complete quantity, value, ownership, serial, claim and transit totals. A different eligible Inventory Manager approves migration activation. Enable new actions from the agreed cutoff, support the first receipt/issue/count cycle and retire earlier records after their outstanding work is accounted for.
Use Proto to propose changes on a branch and review them before release. Changes to units, cost methods, identity or tolerances need an effective policy and reconciliation plan. Preserve posted source evidence and earlier count results; a new master setting should not rewrite historical quantities or values.
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.