Service Orders

What the Home says, checked against the app — 12 backed · 10 partly · 2 not verified

• Backed by the appThe app generates flat-rate labour manuals with AI, estimating hours per operation and pricing them at the shop's rate.
• Backed by the appOp codes make sure the same job is quoted the same way every time.
• Partly liveLabour is priced from op codes at the rate tier that applies to the customer, work type or division, so there is not one flat rate for everything.Why: Rate tiers exist and can be assigned per customer or work order, but the files shown neither tie tiers to work type or division nor apply a tier's rate to labour lines.
• Backed by the appShop supplies are calculated automatically as a configurable percentage of labour.
• Backed by the appTax is decided per work order rather than by a blanket assumption.
• Backed by the appAI usage on a job is metered to that job and held in WIP until the order posts.
• Partly liveSublet work sent outside is tracked on the order with its cost and markup.Why: Sublet vendors and markup % are stored and sublet techs can be put on labour lines, but nothing shown applies sublet cost or markup on the order.
• Partly liveAn AI parts lookup suggests the parts an operation needs.Why: AI suggests parts for the recommended work on a diagnosis write-up, not for an individual operation or op code.
• Partly liveWork orders go through a dispatch, assignment and completion workflow, with dispatch to technicians whose day appears on Scheduling.Why: Service hands dispatch off and tracks assignment and completion; the technician's day view lives in another module.
• Partly liveWork orders can be printed for the customer and for the technician.Why: A printable customer work order exists; no technician version is shown.
• Backed by the appA work order posts to the division that owns the work, so revenue and cost land in that division's Books.
• Partly liveTime tickets and parts are recorded on the work order as they happen.Why: Parts and labour hours are entered on the order, but no time-ticket capture UI is in the files shown.
• Partly liveThe customer's history is one tap away from the work order.Why: A CRM-beside link is wired in, but the code that shows the customer's history is not in these files.
• Backed by the appA work order is invoiced from the job and billed from the same record.
• Backed by the appCustomers see their side of the work order in the portal.
• Backed by the appA quote is produced from op code, hours and rate in seconds.
• Backed by the appThe module uses the same tenant identity, permissions and shared records as the rest of AppSite.
• Not checked yetWork orders, the labour manual, dispatch, sublet and posting to Books are included in every AppSite plan.Why: Plan inclusion is a pricing statement — content, not code.
• Backed by the appThe CRM module keeps one customer record shared across the platform.
• Partly liveInvoices are built from the work, numbered in sequence and posted to the ledger.Why: Building invoices from the work and numbering them in sequence are both implemented, but none of the files shown posts an invoice to the general ledger; they only hold the account mapping and the work-order billing record.
• Backed by the appPayments are matched to the invoice and to the bank account they landed in.
• Partly liveBooks keeps one master chart of accounts across many divisions, consolidated into one company.Why: Service respects a shared chart across divisions; consolidation is done by Books.
• Partly livePurchase orders flow into stock and into the ledger.Why: Service raises purchase orders, but receiving into stock and posting to the ledger are done by Purchasing.
• Not checked yetCourses and the three-level AppSite OPS certificate are included free and open in Training.Why: Free courses and a certificate in Training are content and pricing — content, not code.