Reference
Glossary
Short definitions of common TreadOS terms.
- Job
- A single workshop visit or work package, holding measurements, narrative, and links to quotes or invoices.
- Wheel map
- Diagram of the vehicle’s tyre positions with colour-coded condition bands.
- Re-Torque
- Legally required nut check after wheels were removed and refitted; tracked as its own event.
- Torque Check
- Routine nut tension verification at any time — not interchangeable with Re-Torque.
- Quote
- Priced proposal before work is committed; may be shared to the portal or by secure email for approval. Some workshops label these as estimates instead — controlled under Settings → Finance → Quote or estimate language.
- Estimate
- Alternative label for a priced pre-work proposal when the workshop enables estimates instead of quotes under Settings → Finance → Quote or estimate language. Same workflow, different customer-facing wording.
- Invoice
- Bill for completed work; may sync to your accounting integration.
- Credit status
- Whether a trade customer can open more account work: open, overdue, or stop credit.
- Stop credit
- Blocks new jobs for a customer until the account owner approves the next job (one approval, 24 hours) or clears the stop.
- Customer reminder
- Automatic email or text to a customer about an unpaid invoice, tyre rotation, or wheel alignment — configured under Settings → Reminders.
- Twilio / text messaging
- The external messaging service your workshop connects under Settings → Text messages so TreadOS can send customer texts. The workshop pays Twilio; staff never paste API keys into TreadOS.
- Work request
- Customer-submitted note or ticket that workshop staff triage from their notifications queue.
- Document origin
- The “Created … by …” line on some jobs, invoices, and proposals showing whether the record was created manually or automatically and what it came from.
- Bug report
- In-app feedback sent to the TreadOS team when software behaviour is unexpected, including optional automatic error capture.
- Accounting sync state
- Status of an invoice or proposal push to Xero or QuickBooks — for example pending, synced, or needing manual correction after a mapping or connection issue.
- Site
- A branch, depot, yard, or workshop location under a broader customer or tenant structure.
- Portal user
- A customer-side login that can view the portal according to the permissions the workshop granted.
- Stock movement
- A recorded change in inventory quantity, usually with a reason or source behind the adjustment.
- Audit trail
- Recorded history showing who changed something, what changed, and when it happened.
- Purchase order
- A supplier order for stock — build, email, receive, and reconcile against inventory.
- Counter sales
- Front-desk point-of-sale flow for walk-in retail and quick billing, separate from the full job pipeline.
- Tread forecast
- Projection of when a tyre position will reach minimum legal tread based on recorded wear and distance — used for alerts and fleet planning.
- Passkey
- Optional device-based sign-in (face, fingerprint, or PIN) registered after a normal email-and-password login.
- Service job
- A booked appointment on the workshop schedule — may link to an inspection job when the vehicle arrives.
- Casing class
- A retread grouping (for example size and application) within which casing credits can be swapped. Credits do not cross classes.
- Casing credit / charge
- Optional retread accounting for the value of a returned casing or the charge when no credit applies — configured under Settings → Retread & casing.
- Alignment machine
- A connected wheel alignment system registered to a workshop site so results can flow into TreadOS.
- Price band
- A customer pricing tier with optional quantity breaks, set under Inventory settings and assigned on the customer record.
- Callout charge
- Default inventory lines added automatically when a job is marked as a callout / after-hours visit — configured under Job settings.
- Tenant / workshop
- Your organisation’s isolated data space inside TreadOS. One workshop does not see another workshop’s data.