Shop-floor tablet mode is on the Stokka roadmap. This page describes what we are building.
Feature · Shop-floor tablet mode · Coming soon
The record is the work, not the write-up.
A tablet-first view designed for gloved hands and 6am starts. Big tap targets. Scan the component batch. Confirm quantity. Capture variance at the station. Everything you'd have re-typed at 6pm is already on the finished batch record.
BASE-VLV
VLV-20260408-A
130 g
PIG-IOR
PIG-20260402-B → PIG-20260411-A
36 g + 28 g
WAX-CRN
WAX-20260301-C
54 g
OIL-JOJ
OIL-20260410-A
76 g · planned 72 g
TUB-BLK
awaiting scan
—
The discipline
Capture at the moment of use. Nothing else survives a busy day.
End-of-day paperwork is where batch records go to die. Even with disciplined operators, reconstruction introduces gaps, and gaps are the thing a real recall cannot survive.
Stokka's shop-floor view is not a miniaturised desktop app. It is a flow built around the physical actions of a production run: prep, issue, consume, record, close. Everything the operator does is captured as it happens, with a timestamp, and lands on the finished batch record without any end-of-day reconciliation.
Multi-batch capture
Mid-run batch switching is the rule, not the exception.
Drums empty. Fresh ones open. A single production run often consumes two batches of the same component. Stokka's tablet flow records each as it happens, with quantity and timestamp, so the finished batch knows exactly what went in.
Both contributions land on the finished batch record with their unit ranges. The ingredient-first recall lookup can find this batch from either pigment batch independently.
Designed for the floor
The details that make it work.
Targets
44px minimum, gloves-friendly
Buttons and inputs sized so nitrile gloves, wet hands, and 6am focus all work. No hover states.
Scan
Barcode-first component lookup
Every component batch has a scannable code. Point, scan, quantity, done. Typing is the fallback.
FEFO
Expiry-aware batch suggestions
The tablet suggests the correct batch to issue by expiry or receipt date. Override requires a reason; the reason lands in the audit trail.
Variance
Captured at the station
Actual vs planned consumption is logged per component as you work. Reports surface which runs and which materials drift.
Offline
Resumes cleanly if the network drops
The run card keeps working without connectivity. Changes sync when the tablet is back on the floor's Wi-Fi.
Roles
QA release gate
Runs close to a QA-only state before they become shippable. Release requires the named QA role, captured with timestamp.
Variance, continuously
Small overages add up to big margin leaks.
A 4% overage on jojoba oil on one run is nothing. The same overage on 40 runs a quarter is a conversation with the supplier, or a BOM that needs updating.
+6.1%
OIL-JOJ
3 runs this month · trending
+2.8%
PIG-IOR
Within tolerance · no flag
−1.4%
WAX-CRN
Improved after new hopper
Related reading
Go deeper.
- Batch traceability
Batch tracking for small manufacturers: the complete playbook
Batch tracking is the discipline of knowing which component batch went into which finished batch and which customer shipment. Here is how to set it up so it holds up in an audit and under pressure.
- Batch traceability
Multi-batch recall in under 60 seconds: how it actually works
An ingredient-first recall lookup finds every finished batch, every shipment, and every customer touched by a single bad component batch. Here is the logic that makes it work, and why spreadsheets choke on it.
- Bills of materials
How to build a bill of materials (step by step)
A bill of materials is the spine of any production operation. Here is how to build one that captures real-world yield, sub-assemblies, and the operator-friendly detail that keeps the floor running.
Stokka · shipping soon
The operating system you've been waiting for.
Inventory, BOMs and orders on one screen, with unlimited users. Xero, QuickBooks and Shopify sync at launch, with batch traceability and production planning in the box; shop-floor tablet mode follows on the roadmap.