A long feature list can look reassuring while leaving important questions unanswered. A product business needs reliable connections between materials, formulas, production, quality decisions, costs, and finished stock.
That is the real test for **small batch manufacturing software**: can it follow the physical work without forcing the owner to rebuild the truth in a spreadsheet afterward?
Before committing, use one real product, one recent run, and one common exception. These 12 **manufacturing software requirements** test the decisions your business actually makes.
Build one realistic test case first
Choose a regular product—not the easiest item. Gather its formula or bill of materials, packaging requirements, a supplier receipt, one batch record, a quality check, and current costs. Add a real exception: two supplier lots, failed containers, low yield, or finished units on hold. A trial must handle both the normal path and the messy moment.
Test materials and packaging before testing dashboards
1. Can it distinguish physical stock from usable stock?
A shelf count and an available quantity are not always the same. Material may be allocated, held, damaged, expired, or inaccessible. The **raw material inventory** record should show what is on hand, usable, committed, and unavailable without changing the physical total.
2. Can it use the units your team actually buys and consumes?
You may buy fragrance by kilogram and use grams, or buy jars by case and issue eaches. Test conversions, a partial container, a short shipment, and damaged units. Poor unit handling weakens purchasing, production, and costing at once.
3. Can it preserve supplier lots and material movements?
Receive two lots of the same material, issue both to one batch, and trace each lot forward. The system should retain supplier identity, quantity, location, status, usage, and remainder. Do not accept “lot tracking” until you complete the trace.
Test the product definition, not just the item list
4. Can it separate the approved formula from what happened in one run?
The formula describes the intended product; the production record describes the event. Test an adjustment without editing the standard to make the run look planned. The system should preserve versions, effective dates, expected yield, packaging, and work instructions. See how [production records support batch consistency](https://resources.buildwithkerno.com/achieving-batch-consistency-with-production-records/).
5. Can it make a product change without rewriting history?
Create a new formula or package version. Confirm that new work uses it while earlier **batch records** retain the version that applied. This matters when a supplier, fill weight, or label changes.
Make production tracking follow the work
6. Can a plan become a production record without duplicate entry?
Create an order with the product version, quantity, due date, and materials. Check whether those facts carry into the run. Good **production tracking** captures actual quantities, lots, yield, waste, timing, observations, and exceptions without retyping identifiers into disconnected forms.
7. Can the system show what is ready, active, blocked, and complete?
Ask for current status. Distinguish ready, active, waiting for materials, on hold, ready for packaging, and complete. The [production workflow guide for small studios](https://resources.buildwithkerno.com/streamlining-production-workflow-for-small-studios/) explains how status and completion signals should match physical work.
8. Can it record an exception without erasing the original event?
Enter a mistaken quantity, substitution, rework instruction, or yield shortfall. Can the team see what changed, why, when, and by whom? Corrections should be practical without silently replacing the history.
Test quality, finished goods, and costing together
9. Can quality status control what is available to sell?
Complete the batch but hold six units. Confirm only released units become available, then approve or reject the hold and verify the inventory change. Quality disposition is an inventory fact.
10. Can actual results improve the cost answer?
Enter current prices, actual usage, packaging, acceptable yield, and waste. Compare expected and actual cost. The system need not replace accounting, but it should show how price changes, extra use, rejects, and low yield affect operational cost. Review [end-to-end product management](https://resources.buildwithkerno.com/end-to-end-product-management-for-growing-brands/) for the full connection.
Test the system around the people who will use it
11. Can each role do its work without gaining unnecessary control?
An operator may record usage but not approve formulas; a packer may complete checks but not release holds. Test real roles, multifactor authentication, account removal, backups, exports, and recovery. CISA’s [Secure Our World guidance](https://www.cisa.gov/secure-our-world) offers a practical security baseline.
12. Can you retrieve your records without vendor help?
Export products, materials, formulas, transactions, batches, and quality results. Confirm that identifiers and relationships remain understandable. Then ask: “Which lots, formula version, quality decision, and finished units belong to this batch?” An answer that requires support or several manual joins is not operationally useful.
Score the workflow, not the sales presentation
Mark each question:
- **Green:** the test works with your real data and exception.
- **Yellow:** it works only with a manual step, workaround, or unclear responsibility.
- **Red:** the system cannot preserve the needed information or connection.
A red result is not automatically a reason to reject a tool. First decide how important that workflow is to cost, availability, quality, traceability, or customer trust. But do not let a polished dashboard hide a critical red connection.
If your current workbook already shows warning signs, run this [production spreadsheet risk check](https://resources.buildwithkerno.com/production-spreadsheet-risk-seven-warning-signs/) before migrating. Moving unclear item names, conflicting units, and incomplete records into new software only makes old confusion faster.
Kerno is being built for product businesses that need better control over inventory, production, costing, and quality. This same test should apply to Kerno or any other system: prove the workflow with a real product before asking the whole team to depend on it.
Frequently asked questions
Is inventory software enough for a business that makes products?
It may be enough when you only need purchase and sales quantities. Once formulas, production consumption, yields, batch history, quality status, or actual costs matter, test whether the inventory tool connects those events rather than storing totals alone.
Does a very small product business need lot tracking?
Not every item needs the same detail. Use lot tracking where safety, shelf life, supplier variation, customer requirements, or investigation value makes the connection useful.
Should manufacturing software replace accounting software?
Usually no. Manufacturing records support operational costing, inventory movement, and production decisions. Your accounting system and professional guidance still govern financial reporting, tax, and formal valuation methods.
How much historical data should move into a new system?
Start with active products, usable materials, current formulas, open work, and recent records needed for traceability or decisions. Archive older data clearly instead of importing every duplicate and obsolete row.
What is the best first product to use in a software trial?
Choose a frequent or high-risk product with real materials, packaging, production steps, checks, and exceptions. Avoid an unusually simple product that cannot expose workflow gaps.
Practical takeaway
Do not choose manufacturing software by counting features. Run one product from receipt through production, quality, finished stock, and cost. Test an exception, export the records, and score the 12 connections. The best fit is the system your team can use to reach a trustworthy answer while the physical work is happening.
Research references
- [NIST Manufacturing Extension Partnership](https://www.nist.gov/mep)
- [NIST Smart Manufacturing](https://www.nist.gov/smart-manufacturing)
- [CISA Secure Our World](https://www.cisa.gov/secure-our-world)
