One Platform for Every Team.
KozyOps gives dispatch, AR, service, customers, and leadership the same data, the same audit trail, and the same source of truth.
Open the Tab for Your Team.
Mid-market buyers evaluate by who signs off, not who logs in. The panel swaps to the workspace that team actually opens.
Run the Desk From One Queue.
- Multi-seat dispatch desk with shift hand-off and one shared queue
- Route planning across depots, fuels, delivery types, and schedules
- Degree-day delivery windows plus Otodata and Tank Utility monitor sync
Dispatch sees routes, will-calls, depots, delivery windows, and field updates from one board, with Kozy Service feeding the office in real time.
Close Books From the Ledger.
- Kozy Payments is built in, not a profit center, and posts through the ledger
- Sage Intacct deep push, plus QuickBooks export for QuickBooks shops
- Eight-level RBAC keeps AR, AP, payroll, and dispatch duties separate
Invoices, payments, deposits, refunds, chargebacks, and GL mapping stay tied to the customer ledger, with Sage Intacct deep push and QuickBooks export.
Let Customers Handle Routine Work.
- Online bill pay, will-call payment, and card-on-file support
- Tune-up booking tied to real service availability
- Twilio SMS and portal messages tied to the customer record
The portal gives customers a branded place to pay, request delivery, book tune-ups, upload photos, and message the office.
See Every Brand and Depot.
- Per-tenant database, S3 storage, and feature flags
- Eight server-side roles with segregation of duties
- Audit logs and record-level change history across resources
Owners and GMs get one operating view across teams, brands, depots, roles, records, and audit trails.
KozyOps is built for fuel dealers who also run service. The dispatch desk sees routes and will-calls. AR sees the ledger. Technicians and drivers work from Kozy Service. Customers pay, book, and message through the portal.
Same customer. Same data. Same audit trail.
Different Screens. Same Record.
KozyOps gives each team the screen they need without splitting the data behind it.
Web Back Office
Dispatch, AR, AP, payroll, parts, service, and leadership work from the web back office. It runs on a per-tenant deployment with its own database, S3 storage, and feature flags.
Kozy Service iOS
Everyone in the field uses one app and one login for deliveries, service, and timecards. The field record updates the same customer record the office sees. Inside the field crew workflow
Customer Portal
Customers pay bills, request deliveries, book tune-ups, upload photos, and message the office under your brand. The portal uses the same data model as the back office. Inside the customer experience
Kozy Payments
Kozy Payments is the in-house processor, run to cover cost rather than as a profit center and wired through the ledger. Charges, partial refunds, chargebacks, and deposits stay tied to the customer record. How Kozy Payments works
Built Inside the Work.
Built inside a working fuel-and-service operation, shaped by winter work, and matched to how dealers run.
Run each seat from one record and its own surface: dispatch, AR, AP, payroll, service, parts, customer experience, leadership, IT.
Deploy each tenant with its own database, S3 storage, and feature flags. Run a one-truck shop or thousand-truck fleet across twelve depots.
Enforce eight built-in roles server-side. A driver cannot see the ledger because the API refuses the request, not because the menu is hidden.
Pass controller scrutiny: Kozy Payments run to cover cost (not a profit center), Sage Intacct deep push, QuickBooks export, audit trails, record-level change logs showing who touched what, when.
Handle cold weather: degree-day forecasting, K-factor, monitored tanks, fuel assistance, HOD compliance, and service on delivery trucks.

