Counters are typed
Good parts build the production count, scrap builds the defect count, and inspections are counted on their own. Rework runs as its own mode.
Production tracking software that records as you work.
Approved orders become jobs, and every start, count, pause and stop at the station is written to the job as it happens. Order to invoice on the same record.
From approved order to issued invoice.
Production tracking starts before the floor does. The order, its jobs, the work at each station and the invoice are one record in Bulk, so nothing is retyped between the office and the machines.
Approved order
Approve the customer’s document and Bulk opens the production order with its customer, dates and lines.
Jobs, created for you
The jobs are created in the background, each carrying a frozen copy of the routing it will run.
Worked at a station
Operators load the jobs at their workstation, run the timer and tap counts as the parts come off.
Recorded as it happens
Time, good parts, scrap and material land on the job the moment they are entered. Nobody types them up later.
On the invoice
Completed jobs are ticked onto a draft invoice and issued. Credit notes live on the same record.
Run a job. Watch it record.
This is the operate screen on a shop floor tablet. Start the timer, tap the counters for good parts, inspections and scrap, and watch the record and the OEE readout move. It is a working demo, not a screenshot.
Pick a station. Pass the check. Load the work.
Shop floor control starts at the workstation. The operator chooses where they are working, clears any check the station demands, then loads the jobs that will carry the time and the counts.
Select the station
The asset screen shows every station as running, available, in maintenance or offline, so nobody walks to a machine that is down.
Pass the pre-use check
A compulsory safety, quality or maintenance check blocks the station until it passes. A supervisor override needs a reason, a duration of 1, 2, 4, 8 or 24 hours and a signature.
Load the work
Scan the traveller or search, filter to overdue or due today, and load up to the station’s capacity. Each step shows how long it usually takes, worked out from past runs.
Every station, as it runs.
Production monitoring without walking the floor. The asset board shows every station’s state, the jobs on it and how long it has been that way, with a 24-hour OEE line under each one, on a desk or a TV on the wall.
Time that adds up to the job.
Manufacturing time tracking without timesheets. One session runs per station, a pause opens downtime with a reason, and stopping shares the productive time across the jobs that were loaded.
Four ways to run the clock
Start and stop, adjustable with backdating when someone forgot to press start, manual minutes, or a timer that the counters start.
Downtime with a reason
Every pause asks why. Reasons are grouped as availability, performance and quality loss, which is exactly what OEE is built from.
Sources you can tell apart
Each entry is marked timer, manual or adjustment. The job’s Timers tab shows them by phase and by day, with downtime by reason beside them.
Every tap is a line on the record.
Shop floor data collection that happens in the work, not after it. Each counter tap writes its own record against the job, so the totals are always the sum of what was entered.
Scrap becomes a quality issue
A reject raises a linked quality issue with its category, root cause, disposition and quantity. Nobody has to remember to report it.
Corrections stay visible
Take a count back and Bulk posts an offsetting line. The original and the fix both stay on the job, so the total is always the sum of its lines.
Material comes off stock
Log a consumable at the station and it is drawn down in inventory against the job that used it, as it happens.
Routings that branch, loop and hold for review.
Real jobs do not run in a straight line. Each job runs its own copy of the routing, and completing a step decides what comes next: a branch, another pass or a stop for someone to look.
A snapshot per job
A job keeps the routing version it was created with. Jobs that have not started can move to a new revision, and a job edited on its own shows as custom.
Branches decided on the job
A conditional split picks the branch for each job, with an Else path and a review outlet for anything that cannot be decided. The decision is saved on the job.
Loops with a limit
A repeat group runs until it passes or reaches its maximum passes. At the limit the job waits for a supervisor instead of looping forever.
Sign-off before work
A routing can require approval from any one approver, in order, or everyone. Its jobs wait in Awaiting approval until then.
The office sees what the floor did.
Planners and supervisors work the desktop side of the same record. Every order, job and routed step is in a list, steps can be completed or undone in bulk, and every status change stays on the order’s timeline.
Orders, jobs and transactions
Every order, job and routed step sits in a list you can search, filter and save as a view. Jobs can be bulk edited, and selected steps completed or undone together.
A tab for every question
An order opens on General, Jobs, Transactions, Datasheets, Output, Timers, Quality and Logs, with its progress and status timeline beside them. The floor’s records, already added up.
Travellers, labels and corrections
Print travellers with the routing, a barcode or QR code and a signature block, and item labels from your own templates. Undo a completed step and choose to keep or reverse what was recorded.
What production tracking software should answer.
Production tracking software records what happens to each job on the shop floor: where it is, how long it took, how many parts were good, why it stopped and what it used. In Bulk every answer comes from records operators create at the station.
| The question | How Bulk records it | Where you read it |
|---|---|---|
| Where is this job? | Each step on the job is pending, loaded, in progress, completed or skipped, and the station it is loaded on is named. | Jobs list and the job’s Routing tab |
| How long did it take? | Timer segments, manual minutes and adjustments become time entries on the job. | Timers tab, by phase and by day |
| How many were good? | Typed counters record good parts, scrap and inspections as the operator taps. | Output tab: produced, good, scrap and yield |
| Why did it stop? | Every pause carries a reason, grouped as availability, performance or quality loss. | Downtime by reason, and OEE |
| What did it use? | Material logged at the station is split across the loaded jobs with its unit cost. | The job, and stock in Inventory |
| Who did it, and when? | Every status change on an order or job is written to its history with the person and the time. | Logs tab and the audit trail |
| Can we bill it yet? | Completed jobs wait at the invoicing station until they are ticked onto an invoice. | Invoicing, draft to issued |
One record, read everywhere.
Production writes it once. Quality, stock, OEE, planning and invoicing all read the same records the floor creates, which is how Bulk runs order to invoice on one record.
- Inbound & OCRAn approved customer document becomes the order and its jobs.
- RoutingThe step graph each job runs, copied onto the job.
- SchedulingPlans use step durations learned from past runs.
- QualityScrap raises a linked issue, and a hold stops an order being loaded.
- InventoryMaterial logged at the station draws stock down.
- OEE & AnalyticsPauses and counts feed availability, performance and quality.
- InvoicingCompleted jobs go onto invoices, and credit notes follow them.
Questions, answered.
01
What is production tracking software?
Production tracking software records what happens to each production job as it is worked: which station it is on, how long each step took, how many parts were good or scrapped, why work stopped and what material was used. Bulk records all of it at the workstation as operators work, so the record is complete without anyone typing it up afterwards.
02
How does Bulk track production in real time?
Operators start the timer, tap counters and complete steps at the workstation, and each action is written to the job straight away. The station, the job and its order update together, and planners read the same record in the jobs list and on the order’s Output and Timers tabs.
03
How do approved orders become jobs?
Approving the inbound document creates the production order and its jobs in the background, each with a snapshot of its routing. If a run fails part-way it can be resumed with Retry job creation. Jobs can also be created, imported or bulk updated directly.
04
What does an operator see at the workstation?
A layout of widgets set per station type: the Timer, Loaded Jobs, the Job Card counters, Cycles, Materials Used, Forms and Attachments. Fulfilment and invoicing stations load whole orders instead of jobs. Layouts are arranged in settings, with no code.
05
Can a station be blocked until pre-use checks are done?
Yes. A compulsory safety, quality or maintenance check shows the station as Production blocked until it passes. A supervisor can override it with a reason, a duration of 1, 2, 4, 8 or 24 hours and a signature.
06
How is downtime recorded?
Pausing the timer closes the running segment and opens downtime with a reason, grouped as availability, performance or quality loss. Downtime can be recorded even when no job is loaded, and it feeds OEE directly.
07
How is time shared when several jobs are loaded?
One timer session runs per station. When it stops, the productive time is split equally across the loaded jobs as time entries, and each entry is marked as timer, manual or adjustment.
08
What happens when a part is scrapped?
Tapping a scrap counter creates a linked quality issue with its category, root cause, disposition and quantity. Dispositions include scrap, rework, concession, use as is and return to supplier.
09
Can a recorded count or step be corrected?
Yes. Taking a count back posts an offsetting record, so the original and the correction both stay on the job. A completed step can be undone, with the option to reverse the values recorded against it, and every status change stays in the history.
10
Does Bulk work with barcode scanners?
Yes. Operators can scan with the tablet camera when loading jobs and confirming completion, and keyboard-style scanners work in the scan fields. Printed travellers carry a barcode or QR code.
11
Can Bulk replace my ERP?
It can. Orders, jobs, stock, invoices and credit notes live on the same record as the floor work, installed one app at a time. Where you keep an ERP or accounts package, approved orders flow in as jobs and the live record flows back out.
12
Can I start with a production log before using software?
Yes. Our daily production log records output, downtime and scrap, and the shift handover report carries unresolved work into the next shift. Use the time study sheet to measure a repeated task. For the same work in Bulk, follow the guide to recording production output.
Run your messiest routing in Bulk.
Start a free trial, set up the workstations the way your floor works and run a real job through them: timers, counters, the lot. No card needed.
