quindart
← All articles

How to Choose an ERP for a Small Make-to-Order Factory With QuickBooks and Excel

Give ERP vendors the same changed drawing and split shipment before comparing licenses, integrations or feature lists.

Two colleagues compare an existing computer and tablet linked by a cable.

Map the work before comparing systems

A vendor demo ships the whole order on time. Give the vendor a different job. In this hypothetical make-to-order shop, the customer wants 12 housings on Tuesday and 8 on Friday, then sends a new drawing after the first batch starts. Ask the vendor to show what changes in the production order, what remains on hold and what QuickBooks will invoice.

Pick three recent jobs: one routine order, one with a drawing or specification change, and one with a partial shipment, material substitute, or rework. Use the records your team already works from, such as the quote, approved drawing, purchase order, schedule, production notes, shipping record, and invoice.

Ask the people who handle each step to show where they find the current quantity, revision, due date, and job status. This helps you see whether the problem is missing software, repeated data entry, unclear ownership, or a handoff that is not being managed.

Ask every vendor to demonstrate the same order

Give each vendor the same example and ask them to show the work in order. A screen full of features is less useful than seeing how one job moves through the system. Production orders, for example, connect planned work with the material and operations needed to make it. [2]

Record which exception each product handles with its standard workflow and which needs configuration or custom work. Quindart’s comparison guide spells out what to ask about ownership and maintenance after the demo. [3]

What to ask every vendor to demonstrate
Change during the demoRecord the vendor must showWhat counts as a pass
Drawing changes after work startsApproved drawing, job revision and disposition for earlier unitsThe operator can see which revision applies and who authorized it.
The customer accepts a partial shipmentShipment lines and remaining demandFinance can tell what is invoiceable without closing the rest of the order.
The accounting connection dropsFailed transaction and retry or recovery screenSomeone can recover it without posting a duplicate invoice.

Decide what belongs in QuickBooks and Excel

QuickBooks may remain the accounting record while the ERP manages production orders and materials. Decide which system owns each record. For example, agree where customer and item IDs are created, which system prepares invoices, and how corrections to a shipment reach finance.

Excel may contain temporary analysis, or it may hold the only current schedule or quoting assumptions. Review the sheets with the people who maintain them before moving data. Ask how updates will flow between systems and how the team will see a failed transfer.

Check the work after the demonstration

Review the demo with planning, purchasing, production, finance, and the people who will enter the data. Check whether each person can find the information needed for their next step. Also ask about training, backups, user access, exports, support, and what happens when the system or connection is unavailable.

Mark each requirement as demonstrated, needing setup, handled by another product, or outside the proposed scope. That makes gaps easier to discuss before a contract is signed.

Choose a system the team can maintain

The right choice may be a manufacturing ERP, a smaller MRP system connected to QuickBooks, or a limited improvement to the current tools. It depends on the products, order variation, planning needs, and the team available to maintain the system.

A NIST Manufacturing Extension Partnership case describes ERP analysis and implementation work with a manufacturer. The practical lesson is to understand the factory’s requirements before choosing a product. If a system cannot show how a real order, its exceptions, and its accounting records fit together, a longer feature list will not resolve that gap. [1]

Sources

  1. Purdue MEP ERP analysis and implementation case, NIST
  2. Production orders, Microsoft Learn
  3. Compare custom and standard manufacturing software