# Small Manufacturer ERP Requirements Document Template > Source: https://netray.co/tools/small-manufacturer-erp-requirements-document-template > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A fill-in requirements document you can send to MRPeasy, Katana, Odoo, ERPNext or Fishbowl resellers so every vendor quotes the same scope. ## Category erp-migration ## Industry Small Manufacturing ## Audience - Owner - Operations manager - Plant manager - ERP selection lead ## Tool **Kind:** template **Output:** document **Fields:** #### Company name **Key:** company **Type:** text **Default:** Northfield Fabrication LLC #### Project lead **Key:** contact **Type:** text **Default:** Dana Whitfield, Operations Manager #### Date **Key:** date **Type:** date **Default:** 2026-10-20 #### Manufacturing mode **Key:** mfg_type **Type:** select **Options:** - Make to stock - Make to order - Engineer to order - Mixed **Default:** Make to order #### Named users **Key:** users **Type:** number **Default:** 14 #### Active part numbers **Key:** skus **Type:** number **Default:** 1800 #### Sites and warehouses **Key:** sites **Type:** text **Default:** 1 plant, 1 warehouse, 1 consignment bin at a customer #### Current system **Key:** current **Type:** textarea **Default:** Excel workbooks for BOMs and planning, QuickBooks Online for accounting, paper travelers on the floor. #### Top pain points **Key:** pain **Type:** textarea **Default:** Stockouts of purchased parts, no live view of open jobs, quotes take two days, no lot traceability for one aerospace customer. #### Required integrations **Key:** integrations **Type:** textarea **Default:** QuickBooks Online, Shopify, UPS and FedEx labels, barcode scanners. #### Budget range and timeline **Key:** budget **Type:** text **Default:** 20,000 to 40,000 USD first year, go live within 5 months **Blocks:** #### Requirements Document **Body:** Company: {{company}} Project lead: {{contact}} Date: {{date}} This document describes what {{company}} needs from a cloud MRP or small business ERP. Please answer each section in your proposal using the same numbering. #### 1. Company profile **Body:** Manufacturing mode: {{mfg_type}} Named users: {{users}} Active part numbers: {{skus}} Sites and warehouses: {{sites}} #### 2. Current state and pain points **Body:** Current systems: {{current}} Top pain points: {{pain}} #### 3. Functional requirements **Table:** **Columns:** - Area - Requirement - Priority (Must/Should/Nice) - Vendor response **Rows:** **0:** Items and BOMs **1:** Multi-level BOMs, revisions, alternates, phantom assemblies **2:** Must **0:** Planning **1:** MRP netting with lead times, safety stock and reorder points **2:** Must **0:** Purchasing **1:** POs from MRP suggestions, receiving against PO, vendor lead times **2:** Must **0:** Production **1:** Job or manufacturing orders, routings, work centers, shop floor status **2:** Must **0:** Inventory **1:** Lot or serial tracking, bin locations, cycle counts, barcode scanning **2:** Should **0:** Sales **1:** Quotes, sales orders, customer price lists, shipping and labels **2:** Should **0:** Quality **1:** Inspection records, nonconformance, certificates **2:** Nice **0:** Reporting **1:** Job costing, on-time delivery, inventory valuation **2:** Must #### 4. Integrations and data migration **Body:** Required integrations: {{integrations}} Data to migrate: items, BOMs, routings, vendors, customers, open sales orders, open purchase orders, opening inventory balances. Please state which items you load for us and which we must load ourselves. #### 5. Commercial terms requested **Body:** Budget range and timeline: {{budget}} Please itemize subscription fees per user, implementation, training, data migration, support, and any cost per additional integration or API call. #### 6. Vendor evaluation **Signatures:** - Project lead - Finance approver - Vendor representative **Notes:** Starting point only. Add your own compliance needs (for example lot traceability for AS9100 customers) and mark each requirement Must, Should or Nice so quotes can be compared fairly. ## Content **Intro:** Most small manufacturers pick software from a demo and then discover the gaps after paying the first invoice. A written requirements document makes every vendor answer the same questions. This template produces one you can send to any cloud MRP vendor or reseller. **Sections:** #### How to use the template **Body:** Fill the fields on the left with your real numbers. Be honest about user count and part count, because per-user pricing and data migration effort both scale with them. Then edit the functional requirements table: delete rows you do not need and mark each remaining row Must, Should or Nice. Export to PDF or Word and send it with the vendor demo invitation, asking for answers in the Vendor response column. **Bullets:** - Fix the Must list before you see any demo - Send the identical document to every vendor - Ask for written answers, not demo promises - Share the budget range so vendors do not quote enterprise tiers #### What to ask for in each section **Body:** Items and BOMs decide most outcomes in small plants. Ask whether the tool supports multi-level BOMs with revisions, alternates and phantom assemblies, and how routing steps attach to work centers. For planning, ask how MRP treats lead times, lot sizes and safety stock, and whether it creates purchase suggestions you can convert to POs in bulk. Cloud MRPs differ here: some are built for simple make-to-order flows, others for deeper multi-level planning. #### Reading vendor responses **Body:** Score each answer as standard, configured, custom or not available. Standard means it works out of the box. Configured means settings only. Custom means paid development or a third-party app, which affects both cost and upgrade risk. A product with many Must items marked custom is a poor fit even if the subscription price is low. Compare the five-year cost, not the monthly fee. #### Common mistakes **Body:** Listing every wish as a Must makes all vendors look bad and hides the real differences. Forgetting integrations is the other classic error: accounting, e-commerce and shipping connectors are often paid add-ons. Also write down who will own data cleanup, because BOM accuracy, not software, usually sets the go-live date. **Bullets:** - Too many Must items - No integration list - No owner for data cleanup - Comparing monthly fees instead of total cost **Cta:** If you want the requirements checked against your existing ERP or spreadsheet data before you send them out, Netray can review the draft and flag gaps. **Faq:** #### How long should an ERP requirements document be for a small plant? **Answer:** Three to six pages is enough. Focus on your must-have workflows, your data volumes, integrations and budget. A short document that every vendor answers in writing beats a long one that nobody reads. #### Can I use this for MRPeasy, Katana, Odoo, ERPNext and Fishbowl at once? **Answer:** Yes. The template is vendor neutral. Send the same document to each reseller or vendor and compare answers side by side, including which items are standard, configured or custom. #### Should I include price in the requirements? **Answer:** Include a budget range and timeline, and ask for itemized pricing. Without a range, vendors may quote higher tiers. Without itemization, add-ons and implementation costs surface only after signing. #### Who should sign the document? **Answer:** The project lead and a finance approver on your side, and the vendor representative who confirms the answers. The signature lines make it clear which statements form part of the proposal. ## Search terms erp requirements template, small manufacturer erp requirements, mrp software requirements document, erp selection requirements word, cloud mrp requirements checklist, erp rfp template small business, manufacturing software requirements template --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json