Scales from a guy and a truck to a thousand-vehicle fleet across a dozen depots. KozyOps runs the back office, the field app, the customer portal, and the card processor. Any fuel you sell, any trade you also run, on the same trucks.
KozyOps is deployed per tenant, with its own database, S3 storage, and feature flags. You learn one platform. Every capability listed below is shipping today.
KozyOps pulls OpenMeteo weather every 30 minutes, applies per-customer K-factors, and tells your dispatcher who is due next. Baseload, propane, and oil each have their own window calculators. Calendar schedules support seasonal cadence.
Otodata and Tank Utility supported natively. Sync every 15 minutes. Token refresh runs every four hours.
HVAC heating and cooling. Photos, notes, equipment readings, parts. Multi-visit jobs roll up into one billable project.
The Sage Intacct integration runs deep: invoices, payments, deposits, AR, GL mapping. QuickBooks export is supported for shops on QuickBooks.
Bill pay, will-call payment, delivery request, tune-up self-booking, photo upload, contact, service messaging. Same data model as the office app.
Built into the ledger, not bolted on. Partial-refund allocation and chargeback flow post directly. The result, not the headline: rates lower than third-party gateways usually charge.
Authorizations, contracts, dashboards, third-party vendor pricing. Daily expirations and stale-price alerts run on cron. A real advantage in cold-weather states.
KozyServiceman is the same app for drivers and technicians. Three sections: Delivery, Servicemen, My Time. QR scanning, photos, Bluetooth meters, offline-tolerant.
Mid-market buyers navigate by function — which department signs off — not by role. Choose a tab; the panel swaps to the corresponding workspace.
Three or four seats coordinating year-round. Multi-depot route boards. Will-call queues that survive shift hand-off. KozyServiceman on the iPad in every truck. Calendar schedules and degree-day windows running across thousands of accounts.
Ledger cards per customer, deposit batches with gateway settlement timestamps, payroll PDFs, GL mapping to Sage Intacct (deep) or QuickBooks. Promotions, surcharges, late fees — real line-item types. Eight-level RBAC with segregation of duties enforced server-side.
The customer portal is the third surface of the platform — branded for your operation, served by the same back end that runs the office. Bill pay, will-call payment, tune-up self-booking, contact, photo upload, service messaging. Twilio SMS and SES email tied back to the customer record.
Per-tenant database, S3 bucket, feature flags. Eight realm-based roles. Platform settings refresh every minute. Multi-brand account numbering. Department-level KPI rollups. Audit logs and record-level data-change history that survive a controller's scrutiny.
KozyOps shows up differently for different people, because a dispatcher and a delivery driver and a controller don’t need the same screen. They do need the same data, the same audit trail, and the same source of truth.
A dispatch desk with multi-seat coordination and shift-change hand-off. An AR team posting against a single ledger with segregation of duties enforced server-side. A controller closing the books at month-end with a deep two-way Sage Intacct push (or QuickBooks, your choice). A parts manager working real parts requests against multi-visit projects. A GM watching department-level KPIs from a configurable dashboard. Tour the back office
One app for every driver and every technician on your fleet. Three sections: Delivery, Servicemen, My Time. Capture deliveries on an oil or propane route, work a service job with photos and parts, clock in and out. The same app whether the driver is W-2 or 1099. No more juggling separate apps for separate roles. See the iOS app
Your customers log in, see their balance, pay a bill, request a delivery, or book a tune-up. They never call the office unless they want to, which keeps your dispatch lines open for the calls that actually need a human. See the portal
We were built inside a working fuel-and-service operation, not in a vacuum. The product reflects that. We don’t ship features we haven’t lived with for a season. The same product runs a one-truck operator and a thousand-vehicle fleet across a dozen depots, because the data model and the API were built that way from day one.