Everything Wenbru TMS does.

1. 01

   Job tracking and Job Control

   One place to move a job, one correct next step at a time.

   • 01Validated unique job numbers, priority P1 / P2 / P3 (P1 requires a reason), expected, received and required-by dates, and an ordered production route.
   • 02Lifecycle EXPECTED → RECEIVED → PLANNING → IN PRODUCTION → COMPLETED, with ON HOLD and CANCELLED; a job can be captured while it is still on the way.
   • 03Job Control computes the single next step and refuses a stale page — there are no other movement endpoints.
   • 04Audited exceptions on the same panel: priority change, hold and resume, cancel, and closing a job with unfinished operations only with a recorded override reason.
   • 05Every job page shows the route, live tooling usage from the ledger and an activity feed derived from the audit trail.
2. 02

   Planning, allocation and authorisation

   Only authorised, available people on available machines — enforced by the database, not the dropdown.

   • 01Planning board with per-machine queues; drag-and-drop posts to the same endpoint as the buttons and never moves a job between statuses.
   • 02Machine authorisation as a checkbox tree over workshop › area › machine, with AUTHORISED / TRAINING / SUSPENDED status and validity dates; grants are withdrawn, never deleted.
   • 03Person-only eligibility for fitting, inspection and fabrication stages — “no machine” never means “no person”.
   • 04Planned-time double-booking check (warn or refuse) and live single occupancy — one running operation per person and per machine — backed by database constraints.
   • 05“Who is doing what”: people at work right now, paused work and what it still holds, machines not running.
3. 03

   Shop-floor time capture

   Who worked on what, when, and why it stopped — reproducible from the events.

   • 01Start, pause with reason, resume and complete from the station or from Job Control; every action is an append-only operation event.
   • 02Configurable pause reasons with a category, a time class (productive, operator waiting, machine downtime, non-productive) and what the pause frees.
   • 03Productive, waiting, machine-down and elapsed durations derived from the timeline; after-hours time against a configurable shift window.
   • 04Corrections always carry a note; the original row is never edited and the corrected sequence must still validate.
   • 05Machine status follows the work — AVAILABLE, RUNNING, OCCUPIED — while SETUP, MAINTENANCE, BREAKDOWN and OFFLINE are set by people.
4. 04

   Tool Cupboard station

   Take, borrow and return tooling in a few taps, booked to a job — with no web login on the tablet.

   • 01A shared tablet is paired once with a one-time code; workers sign in from name tiles with a short cupboard password that opens nothing but the cupboard.
   • 02TAKE consumables through Category → Family → Variant picture tiles with “recently used” and “often used by you” strips, a basket, BOOK TO, REVIEW and CONFIRM.
   • 03BORROW a special tool and RETURN it later from MY TOOLS; custody starts and ends on the ledger and is capped at what the worker actually holds.
   • 04RETURN UNUSED puts usable consumables back against the original issue; RETURN DAMAGED records a broken consumable with no stock change.
   • 05Unknown booking references are refused or recorded exactly as typed for the foreman to reconcile, by policy.
5. 05

   Stock ledger, locations and custody

   One append-only ledger; stock never silently negative; mistakes corrected, never rewritten.

   • 01Receive, issue, return, damaged, scrap, adjustment, reversal, transfer and stocktake movements — every one written through a single path that locks the item, checks the balance and writes the audit event in one transaction.
   • 02Per-location balances over a Shop › Storage area › Section tree; “held at” on every list and export.
   • 03Source-first bulk transfers with an all-or-nothing confirm; reverse or correct a wrong book-out in one audited, cross-referenced step.
   • 04Item behaviour — consumable, reusable tool, general — snapshotted onto every ledger row, so reclassifying later never changes what already happened.
   • 05Low-stock signalling on the dashboard, Stock Overview and a Low Stock page.
6. 06

   Stocktake

   A count is evidence; only an approved adjustment moves stock.

   • 01Numbered sessions with a scope (whole location, one category or selected items), blind or guided, DRAFT → COUNTING → REVIEW → CLOSED.
   • 02Starting a count snapshots expected quantities and locks those items at that location against every other movement, whichever screen tries it.
   • 03Count sheets save many lines in one request with per-row version checks; each count is an append-only evidence row.
   • 04Review flags surplus, shortage, custody and not-counted lines; recounts, custody reconciliation and findings are separate actions.
   • 05Count, review and approve are three separate capabilities; summary and variance reports export to Excel or CSV.
7. 07

   Tooling administration

   Shape the tooling catalogue without a developer — and never move stock by accident.

   • 01Category tree of any depth with per-category behaviour, pack size, minimum and target.
   • 02Tool types with attribute templates; product families whose variants inherit defaults until overridden.
   • 03Derived stock codes with a live duplicate check; merge two products through the ledger; delete only what nothing has ever used.
   • 04Manufacturers (with aliases) kept distinct from suppliers (SKU, pack quantity, lead time, latest cost); replacement mapping and compatibility held as data.
   • 05Quick Add at the shelf: WHERE → SEARCH → EXISTING or NEW → COUNT / RECEIVE, with supported manufacturers’ catalogues searched from what is printed on the box.
8. 08

   Dashboards, TV board and exports

   The shop’s state on a wall or a desk — the same numbers everywhere.

   • 01Foreman dashboard with a P1 attention area, overdue and due-today, machines running / available / occupied / down, and low stock; every card links to the rows it counted.
   • 02TV production board that auto-refreshes, shown by a display account carrying no restricted data; priority always shown as text, never colour alone.
   • 03Every data table exports to Excel or CSV with the same filters and sort, so the figure on screen equals the figure in the workbook.
   • 04Performance screens per employee and per machine: planned versus actual, productive / waiting / down split, delay reasons and tooling counts.
   • 05More than 160 permanent error codes, a unique incident reference on every refusal, and a one-tap report-a-problem with screenshot from every screen.

Show us one job.

Send one job the way you run it today. We will show you how it runs in Wenbru.