🧾 DW Orders — From Quote to Completion.

A universal service-order management platform for FiveM.

Quote → customer approval → active order → live status tracking → additional-work approval → completion → payment → receipt/history — all built in, all synced in real time, for any job that quotes and bills work.

It's not just another mechanic script. Run a repair shop, a tow company, a law firm, a clinic, a real-estate agency — or a police department that issues citations directly, with jail-time and MDT integration. Every business is just a config file; the engine underneath is identical.

✨ Features

Core order lifecycle

• Quote → customer approves (fully or partially) → active order → live progress tracking → payment → receipt/history.
• Additional work mid-order always needs a fresh customer approval before the total changes — no surprise charges.
• Full audit log: every price change, stage jump, and payment is recorded with who/what/when.

Two business types

• Private businesses (mechanic shop, tow company, clinic, anything customer-facing) — the classic quote → approve → work → pay flow.
• Public businesses (police, or anything issued unilaterally) — citations issue instantly, no approval step, with optional jail-time and MDT record integration.

Built for staff

• Categorized, color-coded service/charge picker — searchable, no more scrolling a giant dropdown.
• Live order queue with priority levels and one-click custom status jumps.
• In-game Business Settings — edit workflow stages, service templates, and employee permissions without touching a config file or restarting.

Built for customers

• A live-updating portal: progress tracker, itemized pricing, order history.
• Built-in two-way chat on every order — no Discord ticket, no phone number.
• Flexible payment: cash, bank, company/society account, or your own custom handler.

Runs on what you already have

• Framework: QBCore (primary target), with ESX and Qbox bridges included.
• Inventory: qb-inventory, ox_inventory, or qs-inventory.
• Every core system talks through one internal bridge layer — no hardcoded framework calls anywhere in the logic.