Manual batch tracking eats hours, and it quietly creates risk. A typo in a batch number, a missing expiry date, a duplicate entry, and your traceability is no longer reliable. Generic software often isn’t much better: it makes you fit your production around its assumptions, enforces a batch numbering scheme that doesn’t match your suppliers, and still leaves your ERP disconnected.
Most UK manufacturers come to us at a recognisable point. Spreadsheets stop coping somewhere past 100 SKUs or a handful of batch movements a day. A second site makes a single shared view impossible. An audit flags a gap in HACCP or FSMA documentation. Or a recall takes hours to trace when it should have taken minutes. At ByteGears, we build batch tracking systems around how you actually produce and move stock, not around a vendor’s template.
We’re a London-based business automation team, and most of our work is helping UK SMEs replace error-prone manual processes with software that fits.
Why off-the-shelf batch tracking systems fall short
For single-site operations with under 100 SKUs, simple FIFO and basic expiry tracking, an off-the-shelf tool is often the sensible choice, and we’ll tell you so. The trouble starts when your operation has any real complexity. The usual problems:
- Rigid batch numbering. Many tools enforce their own code format, so supplier lots, production batches and sales records never line up without manual reconciliation.
- One-size-fits-all approval flows. SaaS products often assume every batch follows the same QA-approve-then-release path. Real operations have exceptions, so staff build workarounds, and the system data stops being trustworthy.
- Compliance gaps discovered late. Lightweight tools like Zoho Inventory or MRPeasy handle basic lot tracking but aren’t built for GMP or FSMA 204. The shortfall often surfaces during an audit, and then it’s rework.
- Multi-site blind spots. Single-site tools can’t give you a consolidated batch view across facilities, so you end up juggling separate instances.
- Per-user pricing that punishes growth. Add ten warehouse staff or a new site and the bill climbs. Specialist platforms can run well over £15,000 a year before integration and customisation.
- Disconnected systems. Batch logs that don’t sync with accounting or e-commerce create silos and manual reconciliation, which is usually the reason you wanted software in the first place.
You end up with workarounds and process improvements you never get round to. Plenty of businesses walk away from expensive SaaS once it’s clear the “flexibility” in the sales deck doesn’t reach their operations.
What’s different about a ByteGears custom batch tracking system
Our UK-built systems skip the compromises that come with generic software.
Designed around your process. We map how you actually handle batches, including your numbering scheme and your real approval exceptions, before anyone writes code. The software supports your operation instead of fighting it.
Compliance built into the data model. Audit trails, immutable records, change history and digital signatures go in from day one for regulated industries, not after an inspection flags them.
Recall you can run in minutes. Forward and backward trace are core, so you can identify affected batches by supplier lot, date, site or customer fast.
Pay once, own it. No perpetual licensing and no per-user creep. You own the code and the data, and records export cleanly to CSV and JSON.
Connects to what you already run. We link to your ERP, warehouse management, accounting and LIMS through secure APIs or custom interfaces, with mapping rules to handle mismatched batch codes.
Room to grow. Add sites, tracking dimensions, reporting or integration points as the business changes, without a forced platform migration.
Local support. Our London team handles implementation and ongoing help, no timezone gaps, and UK or EU hosting is easy to specify.
Core features we build into batch tracking systems
Every build is scoped to your operation, but the common ground looks like this:
Batch lifecycle and status tracking - batches move through active, quarantine, hold, released, consumed, expired and scrapped, with the transitions your QA process needs.
Forward and backward traceability - link finished goods to the raw material lots they consumed, and supplier lots to the batches and shipments they ended up in. Two-step trace for outbreak and quality investigations.
Expiry and FEFO automation - shelf life calculated from manufacture or receive date, with predictive alerts and first-expired-first-out picking to cut waste.
Hold, release and quarantine - configurable approval rules with authorised release, exception handling, and a full record of who held and released what, and why.
Quality test linkage - record test results against a batch, link to critical control points, and quarantine automatically on a failed test.
Recall management - query affected stock by supplier lot, date range or site, see which customers and shipments are affected, and trigger your recall workflow from a supplier notification.
Batch splitting, merging and nesting - parent and child relationships for batches that don’t stay in one neat unit.
Mobile warehouse scanning - floor staff scan and update batches from handheld devices, with offline capability so a dropped connection doesn’t stop work.
Audit log and access control - immutable movement history and role-based permissions by site, department or job function, meeting UK data protection standards.
Reporting that fits - traceability reports, recall impact analysis, expiry forecasting, batch aging and defect trends, without bolting on third-party tools.
API and integration - real-time batch queries, webhooks for batch events, and connections to ERP, accounting, e-commerce and lab systems.
How we deliver your system
Four phases, and we phase delivery so you get a working system early.
1. Discovery and planning (2-3 weeks). Workshops and time on your floor to document current processes, your batch numbering reality, integration requirements and the compliance regime you work under. This is also where we audit your legacy batch data, because numbering standardisation is usually a multi-week job and worth getting right early.
2. MVP development (8-12 weeks). Our UK-based developers build the core: batch master data, receipts and shipments, expiry alerts, FIFO/FEFO rules, traceability reports, audit log and access control. You get regular progress updates and a system you can actually use.
3. Phase two (typically 3-4 months after MVP). Multi-site visibility, electronic batch records and digital signatures, ERP and accounting integration, LIMS quality imports, recall automation, deviation and CAPA workflows, and the warehouse mobile app, scoped to what you need.
4. Testing, deployment and support. We run the new system in parallel with the old one for a couple of weeks to catch data discrepancies, then roll out in stages. Training is tailored by role, and UK-based support continues afterwards.
The most common ways these projects go wrong are inadequate data cleanup before migration, batch numbering that wasn’t standardised before go-live, and integrations that aren’t ready in time. We plan around all three deliberately.
What it costs
Custom development costs more upfront than a SaaS subscription. Over time, owning the system usually wins.
- Per-user SaaS scales with headcount and sites; specialist flat-rate platforms can run £15,000 or more a year, and the meter never stops.
- A focused custom MVP typically runs £15,000-£25,000. MVP plus phase-two integrations is roughly £35,000-£65,000. A full build with compliance features and a mobile app sits higher.
- Hidden SaaS costs add up too: data migration, premium support tiers, API access charges, and custom development to close compliance gaps.
- You own the code and data outright, with no vendor lock-in and no migration penalty later.
For multi-site or compliance-heavy operations, total cost of ownership tends to reach parity with SaaS around year three to four, and the fit is better the whole way. The free consultation gives you an accurate figure for your specific requirements rather than a range.
Industries we build batch tracking for
Each build adapts to the regulations and workflows of the sector it’s for.
Food and beverage - ingredient lot tracking with FIFO sequencing, finished-goods traceability for HACCP and FSMA 204, automated FEFO picking for perishables, and supplier lot mapping for outbreak tracing. Recall capability within 24 hours.
Pharmaceuticals and supplements - electronic batch records with digital signatures, raw material qualification before production use, batch-to-API mapping, and GMP/MHRA audit trails. FDA 21 CFR Part 11 alignment where you export to the US.
Cosmetics and personal care - formulation and stability batch records, allergen traceability for labelling compliance, and supplier audit trails for product liability.
Chemicals - batches linked to the correct safety data sheet version, storage condition tracking, supplier purity certification, and blending records with material variance.
Medical devices - batch traceability for ISO 13485 and 21 CFR Part 820, sterilisation validation by batch, and post-market surveillance support.
Discrete manufacturing - component lot tracking through assembly, supplier defect rates by lot, and work-in-progress visibility with hold and release at quality gates.
Automotive - parts linked to vehicle VINs for recall management.
Electronics and aerospace - component lot traceability through assembly, with the full records these supply chains require.
If batch management is a genuine differentiator for your business, or you have proprietary traceability and recall logic that no standard product fits, that’s exactly where a custom build pays off.
Common Questions About Custom Batch Tracking Systems
How does a custom batch tracking system compare to SaaS on cost?
A SaaS subscription costs less in year one. The picture changes over time. Per-user tools like MRPeasy or Zoho Inventory scale up as you add warehouse staff or sites, and specialist platforms can run £15,000 or more a year on a flat plan. A custom build is a one-time development cost, typically £15,000-£50,000, with ongoing support if you want it. For multi-site or compliance-heavy operations, total cost usually reaches parity with SaaS around year three to four. We give you a clear figure for your scope at the consultation rather than a vague promise.
What's a realistic development timeline?
A focused batch tracking MVP, covering batch master data, receipts and shipments, expiry alerts, FIFO/FEFO rules, traceability reports and basic access control, usually takes 8-12 weeks. Adding ERP integration, electronic batch records, recall automation and a warehouse mobile app extends that to roughly 16-20 weeks. Full enterprise rollout across multiple sites can run longer. We phase delivery so you get a working system early rather than waiting for everything at once.
Can you build the audit trail and compliance features regulated industries need?
Yes. For food and beverage we build to HACCP critical control point linkage and FSMA 204 traceability, with lot codes and critical tracking events logged. For pharma, supplements and medical devices we build immutable batch records, change history and digital signatures aligned to GMP/MHRA expectations and FDA 21 CFR Part 11 where you export to the US. Compliance goes into the data model from the start, not bolted on after an audit flags a gap.
Can it integrate with our ERP and accounting systems?
Yes. We regularly connect batch data to ERP platforms (Sage, NetSuite, Odoo), accounting systems (Xero, QuickBooks), warehouse and e-commerce tools, and LIMS for importing quality test results. The common headaches are batch numbering schemes that differ between supplier, production and sales systems, and inconsistent expiry date logic. We handle those with mapping rules and validation, and test integrations early so they aren't a surprise at go-live.
How do you handle a product recall?
The system stores forward and backward trace, so you can query affected batches by supplier lot, production date, site or customer in seconds rather than digging through spreadsheets. We build recall workflows around how you actually escalate and notify, and they can be triggered automatically from a supplier notification or a failed quality test. The aim is to identify and isolate affected stock fast enough to satisfy a 24-hour traceability expectation.
What happens to our data and code afterwards?
You own the code and the data outright. Records export cleanly to CSV and JSON, so there's no vendor lock-in and no migration penalty if you ever want to move or extend the system. We can host it, or hand it to your IT team. UK or EU hosting is straightforward to specify, which matters for NHS and government supply contracts and for audit efficiency.