Zudo WorksWork orders (jobs)
Route: /jobs [jobs.read; create/update/lifecycle jobs.write; issue/return jobs.issue]
| Status | Meaning | Next |
|---|---|---|
| draft | Planned, editable | released, cancelled |
| released | Material plan frozen from the BOM; issuable | in_progress, cancelled |
| in_progress | Started; material issuable | completed |
| completed | Completed quantity recorded | closed |
| closed | Final | — |
| cancelled | Final | — |
Job page cards
- Header:
JOB-000045, item, quantity, due date, customer reference, status badge, actions (Release, Start, Complete, Close, Cancel), Job card PDF (in-app viewer, QR code), Barcode. - Materials: planned (from BOM incl. scrap) vs issued vs returned per component; Issue form (warehouse, quantities, reason for over-issue or unplanned components) and Return form (up to issued).
- Routing: ordered steps with work centre and planned hours; Start / Complete in sequence (pending → running → done).
- Labour: hours × rate.
- Cost: material (issued − returned at moving-average cost), labour, total, per unit (total ÷ completed quantity).
- Movements: the
JIS/JRTdocuments of the job. Photos & signatures attachments.
Views on the list: table, Kanban by status (drag between columns), calendar by due date, KPI strip. Each lifecycle move notifies the job's creator, writes the audit log and fires the job.* webhooks.
Last updated