What food manufacturing software actually needs to do
Generic business software (Xero, MYOB, even the base version of Microsoft Dynamics 365 Business Central without food extensions) handles finance, purchasing, and sales. That is necessary but not sufficient for food manufacturing. The features that separate food-specific software from general business software are the ones that match how your factory actually operates.
Recipe and formula management
Food manufacturers work with recipes, sometimes called bills of materials or formulas. A recipe defines the ingredients, quantities, and process steps to produce a finished product. This sounds simple until you deal with the realities of food production:
Variable yields. A recipe that nominally produces 1,000 units might produce 980 or 1,020, depending on ingredient moisture, ambient temperature, and equipment condition. Your software must record actual vs expected yield per batch and adjust costing accordingly. If it only tracks expected yield, your cost of goods is wrong on every batch and the error compounds across thousands of batches per year.
Scalable recipes. If the standard recipe is for 500kg and you need to produce 2,000kg, the system should automatically scale ingredient quantities. But not all ingredients scale linearly. A seasoning that works at 0.5% concentration in a 500kg batch might need 0.48% in a 2,000kg batch because flavour intensity does not scale proportionally. Your recipe management needs to handle these non-linear scaling rules.
Substitutions. When your primary supplier cannot deliver, can you substitute an equivalent ingredient? The system should manage approved substitutions with their quality, cost, and allergen implications. Using a substitute flour with a different allergen profile without updating the label constitutes a compliance failure. The system needs to flag this, not leave it to someone remembering.
Multi-level recipes. Many food products involve intermediate products. A sauce that goes into three different ready meals. A dough that becomes four different product lines. A base mix that is flavoured differently for different SKUs. The system must handle nested recipes where one recipe feeds into another, and traceability must flow through every level. If someone asks which finished products contained a specific lot of an ingredient used in an intermediate, the system needs to trace through all levels to answer that question.
In Business Central with Yaveon, this is handled through "manufacturing specifications", which combine the BOM, the routing, and the batch-specific parameters into a single production document. This is fundamentally different from standard BC where BOMs and routings are separate objects. The combined specification means that when an operator opens a production order, they see everything in one place: ingredients, quantities, process steps, quality checkpoints, expected yield, and any batch-specific notes. They do not need to flip between three different screens to understand what they are making.
Batch traceability
Full forward and backward traceability by batch or lot number. This is non-negotiable for NZ food manufacturers operating under the Food Act 2014. The system must automatically link supplier lots to production batches to customer shipments without requiring manual data entry at each step.
We covered what MPI requires and how ERP delivers it in our detailed article on food traceability and MPI requirements.
Quality management
Quality assurance in food manufacturing goes beyond checking that a finished product looks right. The system needs to manage quality as an integrated part of the production workflow, not as a separate process that operators do on the side.
Incoming inspection. Testing raw materials against specifications before they enter production. Certificate of analysis verification. Automatic quarantine of materials that fail inspection. In Yaveon, inspection orders are created automatically when you post a goods receipt for items that require testing. The lot cannot be consumed until the inspection is complete and the lot is released.
In-process checks. Temperature monitoring, pH testing, and visual inspection at defined process steps. The system should prompt operators to perform quality checks at the right time and record the results against the production batch. If a check fails, the system should change the lot status and notify the quality manager before the product moves to the next step. Not after the entire batch is finished and packaged.
Finished product testing. Microbiological testing, shelf life validation, and sensory evaluation. With configurable hold periods, the product cannot be shipped until test results are confirmed. A batch of chilled ready meals should not be pickable for a customer order until the micro results come back clear. The system enforces this through lot status rules, not by having someone remember to check.
Non-conformance management. When something fails a quality check, the system should trigger a workflow: quarantine the affected batch, notify the quality manager, record the investigation findings, document the corrective action, and update the batch status. This creates a complete quality history per lot that you can present to auditors, customers, or MPI.
Regulatory compliance
NZ food manufacturers need software that supports their compliance obligations as part of daily operations:
MPI Food Control Plans and RMPs. Documentation and record-keeping that aligns with your registered food safety programme. Every quality check, every lot movement, every temperature record should be captured within the system so your compliance documentation builds itself from normal operations.
HACCP workflows. Critical control points monitored and recorded within the production process. If your CCP is a temperature check at the cooking stage, the system should prompt for that reading at that step, record it against the batch, and flag deviations immediately. Not on a separate paper form that gets filed in a folder and reviewed once a month.
Allergen management. Tracking allergens through the entire supply chain. Flagging when a production run follows an allergen-containing product and requires a clean-down. Ensuring that the allergen profile of finished goods accurately reflects the ingredients consumed. Yaveon carries allergen attributes at the lot level, so when you substitute an ingredient, the system knows whether the allergen profile has changed and flags it before the product is labelled and shipped.
Export documentation. Health certificates, phytosanitary certificates, and market-specific documentation for export shipments. The data to populate these documents should come from the system, not from someone manually assembling information from multiple sources.
FEFO and shelf life management
Perishable inventory must be managed by expiry date, not arrival date. The system should support FEFO (First Expired, First Out) picking, minimum-remaining-shelf-life rules per customer, and automatic alerts when stock approaches expiry. This is where many generic ERPs fall short because they treat expiry dates as informational rather than operational. In a food environment, the expiry date drives which lot gets picked, which customers it can be shipped to, and when it needs to be moved to alternative channels.
We covered the details of FEFO vs FIFO in a separate article.
Production planning with food-specific constraints
Planning production in a food manufacturing environment involves constraints that general manufacturing software does not account for:
- Shelf life constraints on raw materials. You cannot plan to use an ingredient next week if it expires in three days. The planning system needs to consider ingredient shelf life when scheduling production orders and alert you when planned consumption falls after expiry.
- Equipment scheduling with clean-down time. Switching from a product containing peanuts to a peanut-free product requires a full clean-down. Switching between products with different colour profiles may require equipment flushing. The planning system needs to account for these changeover times and ideally sequence production to minimise them. Running all peanut-containing products consecutively before a single clean-down is more efficient than alternating between peanut- and non-peanut-containing products, with a clean-down each time.
- Seasonal demand patterns. Many NZ food businesses have significant seasonal variation. Christmas, Easter, barbecue season, export windows. The planning system needs to support demand forecasting and production smoothing so you build stock ahead of peak demand rather than scrambling during it.
What is available in New Zealand
Dynamics 365 Business Central with Yaveon
Business Central is Microsoft's mid-market ERP. On its own, it handles finance, purchasing, sales, and basic manufacturing. The Yaveon food and beverage extension adds recipe management via manufacturing specifications, full-lot lifecycle management with custom attributes, quality assurance with automatic inspection orders, FEFO warehouse picking, catch-weight handling, allergen tracking, and compliance features, including electronic signatures and audit trails. This is what Equerra implements for NZ food manufacturers.
Strengths: Full food manufacturing functionality integrated into a mainstream ERP platform. Microsoft ecosystem (Office 365, Power BI, Azure, Copilot). Scales from 10 to 500+ users. Strong NZ and AU partner network. Regular updates from both Microsoft and Yaveon.
Considerations: Requires a certified implementation partner. Not a self-service product. Implementation typically takes 3 to 6 months, depending on complexity.
NetSuite
Oracle's cloud ERP platform. Has food and beverage functionality through add-on modules or partner solutions.
Strengths: Cloud native. Strong financials and multi-entity support. Good for businesses with complex corporate structures.
Considerations: Food-specific features are typically less deep than dedicated solutions like Yaveon. NZ support is primarily through Australian partners. Higher ongoing cost at the mid-market level. Customisation can be expensive.
SAP Business One
SAP's small to mid-market offering. Food manufacturing features are available through partner add-ons such as Boyum.
Strengths: SAP brand recognition. Good for businesses that may grow into SAP S/4HANA later. Solid inventory management.
Considerations: The base product needs significant extension work for food manufacturing. Smaller NZ partner network than Business Central. The path to full SAP is expensive and not always necessary.
Foodware 365
A food-specific extension for Business Central, similar in concept to Yaveon.
Strengths: Built for food manufacturing on the Business Central platform. Strong in recipe management.
Considerations: Smaller market presence in New Zealand and Australia compared to Yaveon. Fewer local implementation partners with food industry experience.
Standalone food manufacturing systems
Products like Infor CloudSuite Food and Beverage, CSB-System, and Aptean Food and Beverage are dedicated food manufacturing platforms.
Strengths: Deep food manufacturing functionality built from the ground up.
Considerations: Limited NZ partner presence. Often designed for large enterprise rather than mid-market. Integration with your existing finance and sales systems may be complex and expensive. You may end up running two systems instead of one.
What to avoid
Generic accounting software with manufacturing add-ons. If the vendor describes their food manufacturing capability as an add-on or module rather than a core part of the system, expect gaps. Traceability and quality management need to be woven into every transaction. If they are bolted on top, your team ends up maintaining parallel processes: one in the system and one on paper or in spreadsheets. That defeats the purpose.
Systems that require parallel paper records. If your new software still needs you to maintain spreadsheets or paper logs for quality checks, allergen tracking, or traceability, it is not solving the problem. Ask the vendor directly: after implementation, will we still need any paper-based quality or traceability records? If the answer is yes, dig into why.
Vendors without NZ food manufacturing references. Ask for references from NZ food businesses of similar size and complexity to yours. A vendor that has implemented for European or American food manufacturers may not understand MPI requirements, NZ-specific export documentation, the way Foodstuffs and Woolworths manage supplier compliance, or the practical realities of food manufacturing in New Zealand. The regulations, the supply chain, and the customer expectations are different enough to matter.
How to evaluate
Run a structured evaluation process, not a series of vendor demos where each vendor shows their product at its best with pre-built demo data. Define your requirements based on your actual operations: your real recipes, your real quality processes, your real compliance obligations, your real pain points. Weigh the requirements by importance to your business.
Then have vendors demonstrate how they meet each requirement using your scenarios. Ask them to show a trace on your example data. Ask them to show how they handle your most complex recipe. Ask them to show what happens when a quality check fails mid-production. The gaps will become obvious quickly.
If you do not have the internal expertise to run this evaluation, consider engaging an independent advisor rather than relying on the vendors themselves to guide the process.
See our ERP buying guide for a detailed framework.
Equerra implements Dynamics 365 Business Central with Yaveon for NZ food manufacturers. Fixed price implementations from $80,000.
See our food manufacturing ERP page for capabilities, or check our pricing page for transparent cost information.
Book a discovery call to discuss your requirements.
