Production workflow software for small manufacturers

Connect customer orders to production output.

BatchTrace digitises order intake, planning and shop-floor records into one shared operational workflow—without forcing your factory into a full ERP.

Built around existing forms Start with one process Browser-based access
Pilot workspace · Order backlog

Order Backlog

3 open orders
Needs planning96,000
Scheduled108,000
In production78,600
Produced1,400
Customer orderCO-100 · Pilot companyTapa Prater · Violeta
Customer due: 30 Sep
Production allocation
1,400 produced · 78,600 active · 60,000 scheduled · 60,000 to plan
Still to plan60,000Create production run
Live operational signalRun PR-100-01 is activeMachine IMM-001 · planned finish before customer due date.
The operational problem

Production information should not disappear between paper, Excel and the factory floor.

BatchTrace connects the handoffs that are usually fragmented, while leaving the factory’s familiar operating process intact.

01

Customer demand arrives

Orders, delivery dates, products and special instructions are captured once.

Registered once
02

Planning splits the work

Demand becomes linked production runs with machines, operators and dates.

Every run stays connected
03

Production records output

Completed boxes and actual quantities update the shared operational view.

Progress becomes visible
The product

One operational record, viewed differently by every role.

The office, planner and production team use different screens, but they work from the same connected order and production data.

BatchTrace · Operational overview

Operational Overview

Immediate visibility across the current production workflow.

31 Jul 2026
Needs planning96,000
Scheduled108,000
In production78,600
Produced1,400
Needs planning3
CO-101 · Client AClosure cap 38 mm · due 31 Aug16,000
CO-102 · Client BHandle red · due 24 Sep20,000
CO-100 · Pilot companyPrater violet · due 30 Sep60,000
Scheduled3
PR-102-04IMM-005 · starts 14 Aug14,000
PR-100-03IMM-003 · starts 1 Sep60,000
In production1
PR-100-011,400 of 80,000 produced78,600 left
Produced1
PR-100-01Current accepted output1,400
BatchTrace · Order backlog

Order Backlog

Customer demand separated into planned, active and produced quantities.

3 open orders
Needs planning110,000
Scheduled94,000
In production78,600
Produced1,400
CO-102 · Client B
Handle red · ordered 34,000
Customer due 24 Sep
Production allocation
34,000 needs planning
Still to plan34,000
Create production run
CO-101 · Client A
Closure cap 38 mm · ordered 50,000
Customer due 31 Aug
Production allocation
34,000 scheduled16,000 needs planning
Still to plan16,000
Create production run
CO-100 · Pilot company
Prater violet · ordered 200,000
Customer due 30 Sep
Production allocation
1,400 produced78,600 active60,000 scheduled60,000 to plan
Still to plan60,000
Create production run
BatchTrace · Production schedule

Production

Active work first, then paused, scheduled and completed runs.

4 production runs
Status
Run / product
Machine
Planned start
Planned finish
Customer due
Action
Running
PR-100-01
Prater violet
IMM-001
03 Aug
08 Aug
30 Sep
Open run
Scheduled
PR-101-02
Closure cap 38 mm
IMM-006
12 Aug
15 Aug
31 Aug
Open run
Scheduled
PR-102-04
Handle red
IMM-005
14 Aug
16 Aug
24 Sep
Open run
Scheduled
PR-100-03
Prater violet
IMM-003
01 Sep
07 Sep
30 Sep
Open run
One workflow, different roles

Each team sees the action it owns—without losing the full order connection.

OF

Office

Registers customer demand, products, dates and instructions once.

PL

Planner

Splits demand into runs and assigns machines, operators and dates.

PR

Production

Records completed boxes and actual output against the correct run.

QC

Quality

Completes inspections linked automatically to the production run.

Private pilot program

Start with the workflow you already use.

A pilot is configured around one real operational process—not a generic ERP implementation.

1

Share the existing workflow

Forms, spreadsheets, labels and a recorded walkthrough of how work moves today.

2

Map the operational handoffs

Define what the office, planner, operator and quality team need to see and record.

3

Receive a configured workspace

Your customers, products, machines and familiar terminology are loaded into the pilot.

4

Test one end-to-end process

Validate intake, planning and production visibility before expanding the scope.

Honest product scope

A focused operational core, designed to expand carefully.

The current pilot concentrates on the workflow that already delivers immediate visibility. Additional modules are connected only after the foundation is proven.

Available in the current pilot

Customer and product Master DataOrder IntakeOrder BacklogProduction planningProduction executionOperational Overview

Connected next

Quality inspectionsBox labels and QR traceabilityDispatch recordsRole-specific reporting
Built for practical deployment

A private company workspace, not another disconnected spreadsheet.

Production deployments use authenticated access, a central application layer and a structured PostgreSQL database. Pilot previews use sample or non-sensitive data for workflow validation.

01

Private company workspace

Customers, products, machines and workflows are separated by company.

02

Browser-based access

Office, planners and production teams access role-specific screens through the web.

03

Connected operational data

Orders, runs, output and later quality records share one traceable relationship chain.

See how BatchTrace would fit your production workflow.

Start with one existing process, one configured company workspace and one clear pilot objective.