Custom software
Systems built for how your business actually runs, replacing the spreadsheets and workarounds holding it together.
How it worksAll industries
Regulated production
Shelf life is an operational constraint, not a label.
Batch coding, shelf-life driven dispatch, recipe yield, cold chain records, and distributor claim settlement in one system.
Where the standard system leaves the cost in place.
Food operations run against a clock that most software ignores. Stock has a remaining life, dispatch order changes what reaches the customer and what gets written off, and the cost of getting it wrong is paid twice: once in the write-off and once in the trade claim that follows. Add contract packers, farm-level incoming quality, and a licensing regime that expects traceability in both directions, and the spreadsheet stops being adequate well before the business feels large. The pattern is consistent: the operation knows the answer, but not in time to act on it.
- Dispatch is picked by convenience rather than by remaining shelf life, so near-expiry stock is discovered when it is already unsellable.
- Recipe yield and wastage are estimated, so the difference between costed and actual conversion is never quite known.
- Batch coding is applied at packing but not carried into stock, so a recall means tracing through dispatch registers by hand.
- Cold chain and storage condition records are on paper, filed separately from the stock they refer to.
- Distributor schemes, damaged-goods returns, and claim settlement are reconciled in spreadsheets months after the sales they relate to.
Built for food and beverage.
Built on the same core our products run on, extended with the records and rules this sector is actually judged against. These are scopes we build and integrate, not shelf modules with a licence key.
Recipe, yield and wastage
Recipes with actual against standard consumption per production run, wastage recorded where it happens, and conversion cost that reflects what the line actually did.
Batch coding and shelf-life stock
Every unit carries its batch and expiry into stock, so remaining life is a property of the inventory rather than a number printed on a pack and forgotten.
FEFO dispatch control
Picking and allocation driven by first expiry first out, with near-expiry stock surfaced early enough to be sold rather than written off.
Incoming and supplier quality
Goods-in checks against specification, supplier and farm-level performance history, and rejection recorded against the vendor it belongs to.
Cold chain and condition records
Storage and transport condition logging held against the batch, so a temperature excursion is linked to the stock it affected instead of sitting in a separate register.
Contract packing and trade claims
Material issued to and received from co-packers with yield reconciliation, and distributor schemes, returns, and claims settled against the invoices that generated them.
What it has to be able to prove.
Compliance fails when it is a parallel activity. These obligations are carried by the system that runs the operation, so the evidence exists because of how work was recorded rather than because someone assembled it afterwards.
Licence and label obligations
Licence details, permitted claims, and mandatory label declarations held against the product, so what is printed matches what is approved.
Two-way recall traceability
Forward trace from a batch to every distributor and outlet it reached, and backward to every ingredient lot and supplier it came from, retrievable in one pass.
Hygiene and audit records
Cleaning, sanitation, pest control, and critical control point checks recorded on schedule, so third-party and buyer audits are supplied from the system rather than prepared for.
What it runs on.
The sector layer is built. The operational core underneath it is not a proposal: it is running in production with clients today.
ERPMachERPLiveProduction, procurement, sales, and finance, extended with recipe, batch coding, and shelf-life logic through to dispatch and claim settlement.See what it does
SIMSMach SIMSLive with clientsBatch and expiry-aware stock across plants, cold stores, and distributor locations, with FEFO allocation and movement history.See what it does
What it returns.
Write-offs move from discovery to decision
Near-expiry stock is visible while it can still be sold, promoted, or redirected.
Recall response measured in minutes
Batch genealogy runs both directions, so the affected quantity and its destinations are known before the phone calls start.
Trade spend stops leaking
Schemes and claims are settled against the invoices they relate to, so what was promised and what was paid finally agree.
Where this normally starts.
Which of these applies depends on how well the constraint is already understood. A review that finds the real one usually turns into a build.
Data and reporting
Turning scattered records into dependable, current reporting that leaders can act on rather than argue about.
How it worksQuestions we actually get asked.
Our production is partly manual, with no terminals on the line. Does this still work?
Yes. Capture points are designed around how the line actually runs: a supervisor entry at a single station, a tablet at packing, or printed batch documents reconciled at a controlled point. What matters is that the record is created once, close to the event. Instrumenting the whole line is an option, not a prerequisite.
We use contract packers for part of the range. Can the system track that?
It has to, because that is where material and yield most often go unaccounted for. Issues to the packer, receipts back, yield against agreed norms, and the packer's own batch references are all held in the same structure as in-house production.
Distributor claims are our biggest reconciliation headache. Does this touch that?
Directly. Schemes, discounts, returns, and damage claims are recorded against the invoices and batches they arise from, so settlement is a calculation instead of a negotiation carried out with two different spreadsheets.