Skip to content
Industries · Manufacturing · Food processing

ERP for food manufacturing and meat processing, built on ERPNext

With our ERP for food manufacturing, you know when every batch was made, when it expires and where it went. The system follows each batch from the farm to the chiller, then the production hall and the shop.

We have implemented ERPNext for a food and meat processor in Saudi Arabia.
The process

From farm to shop: one ERP for the whole food chain

1

Farms and suppliers

Animals, carcasses, ingredients and packaging arrive from farms and suppliers.

2

Receiving by batch

Each carcass or lot becomes a batch with its slaughter date and expiry date.

3

Chillers and stores

While batches wait in the chillers, a report shows how many days each has left.

4

Processing and production

Work orders then turn raw meat into cuts and processed products.

5

Packing

Finished batches are packed on a packing slip that names the batch.

6

Sales and delivery

Sales invoices go to ZATCA, and each delivery leaves on a delivery note.

7

Accounts

Every movement carries its value into stock and the ledger.

Problems we solve

What a food factory struggles with, and how the ERP answers

Fresh stock ages by the hour

Chilled meat loses value every day it waits, but the oldest batch is often found too late.

Every carcass is different

Animals differ in type, weight, age and source. Unless that data sits on the stock, a quality question cannot be traced back to one animal.

Weight disappears between the scale and the shelf

Meat loses weight while it chills and when it is cut. If nobody records that loss, system stock drifts away from the chiller.

The factory floor does not work in ERP menus

Butchers and packers stand at a station with gloves on, so they will not open several forms to report one job.

One product, many units

The same product is counted in kilos, packs and cartons, so a work order that ends on half a carton confuses the store.

Farms, factory and shops keep separate books

When each site keeps its own files, nobody sees total stock, and sales reach the accountant late.

What we set up

What we set up in an ERP for food manufacturing

Eight things we have built or configured for a food and meat processor. Each one says what standard ERPNext does and what we added for that project.

Carcass receiving, one batch at a time

Each carcass or lot is received as its own batch, with its slaughter date as the batch’s production date. ERPNext then works out the expiry date from the item’s shelf life. For a food and meat processor in Saudi Arabia, we added a carcass view to the purchase receipt. Its ‘Create Batches’ action splits a received line into batches, each with a series number, a permit or tag number and a quantity. The animal type and source are also chosen once per line.

ERPNext purchase receipt form with supplier, accepted warehouse and received items, demo data
A purchase receipt into the stores (general ERPNext demo, office supplies)

Batch tracing, QR scanning and a batch scanner

In standard ERPNext, a batch report shows each batch per warehouse with what came in, what went out and the balance. For a food and meat processor in Saudi Arabia, we added QR scanning. There, scanning a batch QR code on a stock entry, a delivery note, a sales invoice or a stock count adds the item, the batch, its quantity and its warehouse. A batch scanner page also shows the batch with its quantity, receiving warehouse and expiry date, and lists the documents that moved it.

ERPNext batch list, the batch record a food ERP keeps, with batch ID, active or expired status, item name and batch quantity, demo data
The batch list with status and quantity per batch (general ERPNext demo, office supplies)

Weight loss, calculated and posted

Meat loses weight while it chills and when it is cut. For a food and meat processor in Saudi Arabia, we built weight-loss handling on the stock transfer. There, one allowed loss rate applies to chosen item groups. The transfer then shows the batch quantity beside the quantity moved and works out the loss. A repack entry writes the batch down by the allowed rate, and any loss beyond it is posted to a chosen expense account and cost centre.

ERPNext stock entry of type Material Transfer with source warehouse, target warehouse, items and quantities, demo data
A material transfer between two warehouses (general ERPNext demo, office supplies)

Batch expiry and stock age by warehouse

A standard report lists every batch with its expiry date and the days it has left. ERPNext also refuses the sale of a batch whose expiry date has passed. For a food and meat processor in Saudi Arabia, we built a stock-age report on top. It lists stock by warehouse with the batch, its quantity and its slaughter, production and expiry dates. The report can also be e-mailed every day to chosen roles.

ERPNext Stock Ageing report with a bar chart and age bands per item, the stock-age view of a food ERP, demo data
The standard Stock Ageing report: stock value by age band per item (general ERPNext demo, office supplies)

Work orders with material availability

A standard work order shows the quantity required, transferred and consumed for each material. Its finished batch also gets its own expiry date. For a food and meat processor in Saudi Arabia, we built a work-orders board on top. Planners see open work orders there, with the materials required, transferred and in store. From the same board, they then create the material transfer. Two rules also keep plans clean: one routing per production plan, and work orders in whole multiples of the largest unit.

ERPNext work order form, the production order of a food manufacturing ERP, with its warehouses and the required items with their required, transferred and consumed quantity, demo data
A work order: required items against the quantity to manufacture (general manufacturing demo, office supplies)

Arabic screens for each factory hall

For a food and meat processor in Saudi Arabia, we built one screen for the processing hall and one for the production hall. Each screen lists job cards with the work order, item, operation, workstation, quantities, time spent and status. A worker starts, pauses or finishes a job, then names the employees and enters the quantity done. When the last operation ends, the system drafts the production entry, and the supervisor then reviews and submits it. In standard ERPNext, the automatic batch pick for production already skips an expired batch.

ERPNext work order list with item to manufacture, status and order number, demo data
Work orders by status (general manufacturing demo, office supplies)

Packing, loading and delivery

A standard packing slip lists the items of a delivery with their batch and the gross weight of the packages. For a food and meat processor in Saudi Arabia, we built a packing screen with start, pause and finish actions. A loading tab on the delivery note there records the driver, the vehicle and the entry, exit and loading times. Ticking ‘delivered to customer’ on the note then updates the sales order.

ERPNext delivery note form with customer, source warehouse, items and quantities, demo data
A delivery note to a customer (general ERPNext demo, office supplies)

HR and payroll across farms, factory and shops

Staff on farms, in the factory and in shops sit in one HR system. A shift attendance report shows each employee’s shift, in and out time, late entry and early exit. The salary register also lists each payslip with one column per earning and deduction. For a food and meat processor in Saudi Arabia, we also built a check-in report with the first punch in, last punch out, device and shift, which flags a missing punch.

Frappe HR salary register report with salary slips, employees, departments and designations, demo data
The standard salary register for one month (general HR and payroll demo)

Screens show demo data.

Modules

ERPNext modules and integrations for food manufacturing

ERPNext modules

Bills of materials, routings, work orders and job cards.

Warehouses for farms, the factory and shops, with batches and expiry dates.

Carcasses, ingredients and packaging, from order until receipt.

Orders, deliveries and invoices for branches and customers.

Stock value, receivables and payables in one ledger.

Employees, attendance and leave across all sites.

Salaries with allowances, deductions and advances.

Integrations

Tax invoices cleared and simplified invoices reported from the sales invoice, with the QR code on the print.

Stories

Where we have delivered ERP for food manufacturing

Client name withheld

A food and meat processor in Saudi Arabia

Meat production and food manufacturing, from farm to retail · Saudi Arabia

One system from the farm to the shop counter.

What we set up

Screens behind the food manufacturing steps

The standard ERPNext screens behind those steps: batch expiry, the ZATCA tax invoice and the bill of materials.

ERP for food manufacturing: batch stock in the ERPNext Batch-Wise Balance History report, by item and warehouse, demo data
Stock per batch and warehouse: quantity in, quantity out and balance (general ERPNext demo, office supplies)
ERPNext Batch Item Expiry Status report, the expiry check of a food ERP, with item, batch, quantity, expiry date and days to expiry, demo data
Batch Item Expiry Status: each batch with its expiry date and the days left (general ERPNext demo, office supplies)
Printed Arabic and English tax invoice with a QR code, VAT lines and a ZATCA Cleared badge, demo data
A bilingual tax invoice with the ZATCA QR code and the 'Cleared' status (ZATCA integration demo, fictional company)
ERPNext bill of materials form with its operations and component items, quantities, rates and amounts, demo data
A bill of materials: the raw materials, quantities and cost of one finished item (general manufacturing demo, office supplies)

Screens show demo data.

FAQ

Frequently asked questions about ERP for food manufacturing

Have you implemented ERPNext for a food manufacturer before?

Yes. We implemented ERPNext for a food and meat processor in Saudi Arabia with farms, a processing plant and retail branches. The project covered accounting, purchasing, sales, stock and manufacturing, as well as ZATCA e-invoicing and HR.

Yes, back to its batch. Each carcass or lot is received as a batch with its slaughter date. A batch report then shows every warehouse it passed through, from the farm store to the shop. For a food and meat processor in Saudi Arabia, we also added the tag number and the animal details to the batch.

Each batch holds a production date and an expiry date. ERPNext can also work out the expiry from the item’s shelf life. When you sell, it refuses a batch whose expiry date has passed. Before it gets that far, a standard report lists every batch with the days it has left.

For a food and meat processor in Saudi Arabia, we built it into the stock transfer. An allowed loss rate is set for chosen item groups. The system then compares the batch quantity with the quantity moved, writes the batch down by that rate and posts any extra loss to an expense account. Standard ERPNext does not do this by itself.

Yes. In Saudi Arabia, our ZATCA Phase 2 integration sends tax and simplified invoices from the sales invoice. If your factory is in Egypt, we have a separate ETA e-invoicing integration.

Both. Purchasing, stock, batches, bills of materials, work orders, sales and accounts are standard ERPNext. Carcass receiving, weight-loss handling, the stock-age report and the hall screens are additions we built for a food and meat processor in Saudi Arabia. On a new project, we adapt them to that factory.

Mostly, yes. The project we delivered is in meat, but batches, expiry dates, bills of materials, work orders and packing work the same for any food product. The animal details are meat-specific, so we adapt those fields to your product.

Frappe Certified Gold Partner

Running a food factory? Ask about a similar project

Tell us how you receive, process, pack and sell. We will then show you how the same steps run in an ERP for food manufacturing on ERPNext.