Title: ERP Implementation Checklist for Small Shops URL: https://zudoworks.com/answers/erp-implementation-checklist-small-manufacturer/ Description: ERP implementation checklist for a small manufacturer: owner and dates, clean master data, configuration, testing with real orders, training and go-live. Updated: 2026-11-03 # ERP implementation checklist for a small manufacturer An ERP implementation checklist for a small manufacturer has five parts: name one owner and a go-live date; clean the master data (items, BOMs, customers, vendors, opening stock); configure numbering, units, tax rates and roles; test three real orders end to end; then train each role and go live with stock and work orders before accounting. Tick every item in a part before starting the next. By Arunkumar V, CTO · 03 November 2026 · 2 min read [Try ZMOS free](https://app.zudoworks.com/signup) [Book a 20-minute demo](https://zudoworks.com/contact/) - ERP go-live checklist - ERP implementation steps - ERP project plan small business - manufacturing ERP rollout ## Before you sign The checklist starts before the contract. Decide what problem the ERP must fix in the first three months and write it in one sentence; everything else is phase two. Confirm export terms, the renewal price, and who answers questions after go-live. - One named owner inside the shop with hours set aside each week - A go-live date at the start of a month, outside peak season - The three processes that go live first, in writing - Export and cancellation terms checked - A budget line for your own time, not only the licence ## Master data Data cleaning is most of the project. Work through items first, because BOMs, stock and purchasing all hang off them. One item code per physical part, one unit of measure, one description format. Mark obsolete items so they are not imported. For BOMs, choose the current revision for each product and record scrap allowances where you know them. For customers and vendors, dedupe names and capture tax numbers. Opening stock comes last, from a physical count on the weekend before go-live, not from the spreadsheet's running balance. ## Configuration and testing Set document numbering, warehouses and locations, units, tax rates, work centres and their hourly rates, and roles with the fields each role may see or edit. Then test with real orders, not sample data: pick one simple job, one job with a multi-level BOM, and one job that goes out for subcontracting. Follow each from quotation or order through purchase, receipt, issue, production, labour, inspection, despatch and invoice. Every gap you find here is cheap; the same gap after go-live is not. ## Training, go-live and the month after Train by role, on that role's screens only, with a printed one-page guide. Go live with stock and work orders, then purchasing, then accounting at a month end. In the first month, hold a short daily stand-up to collect problems, fix the data causes rather than working around them, and stop the old spreadsheets after the first reconciliation. - Each role has done one real transaction under supervision - Opening stock and open orders loaded and signed off - Backups or exports scheduled and tested once - A list of who to call for each kind of problem ## How to run an ERP implementation checklist 1. **Step 1** Write the first-quarter goal in one sentence and name the owner. 2. **Step 2** Clean items, then BOMs, then customers and vendors, in that order. 3. **Step 3** Configure numbering, warehouses, units, tax rates, work centres and roles. 4. **Step 4** Import the data, run three real orders end to end and fix every gap found. 5. **Step 5** Train each role, count stock, load opening balances and go live at the start of a month. 6. **Step 6** Review daily for the first month and retire the old spreadsheets after the first reconciliation. ## Where ZMOS fits For a 10 to 50 person sheet-metal, machining or fabrication shop, ZMOS covers the checklist above in one workspace: CSV import for items, customers and vendors, BOMs with revisions and scrap, work orders with routing steps and work centres, roles and permissions down to fields, and an audit log of every change. The user guide has 54 step-by-step tasks with real screenshots, which replaces much of a partner's training. It is not the fit for a shop that needs an on-premise install or a partner to own the whole programme. [What ZMOS does](https://zudoworks.com/zmos/) - [manufacturing workflows](https://zudoworks.com/manufacturing/workflows/) - [roles and audit log](https://zudoworks.com/zmos/roles-audit-api/) - [start the free period](https://zudoworks.com/zmos/free-trial/) - [how we run a build](https://zudoworks.com/how-we-work/) ## People also ask Short answers, each one complete on its own. ### Related answers - [How long does ERP implementation take?](https://zudoworks.com/answers/how-long-does-erp-implementation-take/) - [How does ERP data migration work for a small shop?](https://zudoworks.com/answers/erp-data-migration-for-small-shops/) - [Why do ERP implementations fail?](https://zudoworks.com/answers/why-erp-implementations-fail/) - [How do I move from spreadsheets to an ERP?](https://zudoworks.com/answers/how-to-move-from-spreadsheets-to-an-erp/) - [What questions should I ask an ERP vendor?](https://zudoworks.com/answers/questions-to-ask-an-erp-vendor/) - [What should I look for in an ERP demo?](https://zudoworks.com/answers/what-to-look-for-in-an-erp-demo/) - [All 54 answers](https://zudoworks.com/answers/) ### Inside ZMOS [Zudo AI](https://zudoworks.com/zudo-ai/)[Stock ledger](https://zudoworks.com/zmos/stock-ledger/)[Low-code forms and rules](https://zudoworks.com/zmos/low-code/)[Barcode job cards](https://zudoworks.com/zmos/barcode-job-cards/)[Roles, audit log, API](https://zudoworks.com/zmos/roles-audit-api/)[Security](https://zudoworks.com/zmos/security/)[Free trial](https://zudoworks.com/zmos/free-trial/)[Why Zudo Works](https://zudoworks.com/why-zudo-works/) Who should own an ERP implementation in a small shop? The person who already knows the parts and the process, usually the owner, plant manager or planner, with real hours set aside each week. Handing it to an outside consultant alone fails because the decisions about items and processes belong to the shop. Do we need to clean every item before go-live? Clean the items that are active in the last twelve months and mark the rest obsolete. Importing thousands of dead codes slows searches and hides mistakes. You can add an old item later on the rare day it is needed. How many test orders are enough? Three well-chosen orders find most gaps: one simple job, one with a multi-level BOM, and one that goes out for subcontracting. Follow each from order to invoice. A dozen half-finished tests teach less than three complete ones. What should the first month after go-live look like? A short daily stand-up to log problems, one person fixing data causes rather than symptoms, a reconciliation of stock and open orders at the end of week two, and the old spreadsheets switched off once it agrees.