Custom reports, third-party integrations, billing logic, new modules, state tax filings, and full API access — all built by the same in-house team that wrote BookWorks. Every project is scoped in a detailed Statement of Work before a line of code is written. No sharp elbows on any opportunity.
When a prospect or customer needs something BookWorks doesn't do yet — a specific integration, a unique billing structure, a state tax report, a connection to a third-party system — our answer is never "sorry, we don't do that." It's "let's scope it."
We embrace every custom software opportunity. If your operation needs it, we want to build it. The work is scoped in a detailed Statement of Work with agreed hours and dollars before a single line of code is written — so there are no surprises for you or for us. Custom work strengthens BookWorks. Every integration built for one client makes the platform more capable for everyone.
Custom work is done in-house by the same developers who built and maintain BookWorks — not outsourced to a third party who needs to learn the codebase. They know every data structure, every API endpoint, and every integration pattern in the platform.
Every custom project is scoped in meticulous detail before work begins. The Statement of Work identifies every deliverable, every hour, and the total cost. No scope creep surprises, no open-ended billing. You approve the SOW; we build exactly what it says.
Custom features built for any client are candidates for inclusion in a future BookWorks release — available to all clients, maintained with the platform, and supported under the standard monthly fee. Custom work makes the platform better for everyone.
Key owns the code built on custom projects, and you have perpetual use of it. You're not renting a feature that disappears if you leave. The work is yours to use as long as you run BookWorks.
Every petroleum operation has unique combinations of systems, supplier relationships, regulatory requirements, and billing structures. When a standard feature doesn't quite fit, custom development is how BookWorks molds to your operation rather than the other way around.
Your ATG system, your C-store back office, your fleet software, your bank's specific NACHA format, your loyalty platform — if it needs to talk to BookWorks, we can build the bridge.
A state adds a new fuel tax report format. A regulator requires a specific electronic filing. Your state's environmental fee calculation changes. We build the new report or import/export to spec.
Your contract structure doesn't fit a standard price matrix. Your fleet billing has a custom surcharge calculation. Your consignment commission formula is unlike anything in the standard platform. We build it to your spec.
Your controller needs a specific Crystal Reports layout. Your executive team wants a dashboard that doesn't exist in standard BookWorks. We build the report.
These are integrations Key has built — connecting BookWorks to the third-party systems petroleum operators actually use. Each was built to a detailed SOW, tested against live data, and is now in active use by BookWorks customers.
Comprehensive DTN integration covering every automated data feed relevant to petroleum wholesale operations — the most widely used integration in the BookWorks platform.
Bidirectional integration between BookWorks petroleum accounting and Ignite Retail Technology's Profit Central C-store back-office platform — for operators running both petroleum wholesale and convenience retail.
Full Corpay / Fleetcor card transaction import — covering both Pacific Pride and CFN networks — enabling unified fleet billing across Corpay-managed cardlock accounts directly within BookWorks CardLock.
Native support for BizSpeed, FleetPanda, and RowLogic delivery and field mobility platforms — full API configuration and bidirectional order exchange between BookWorks and each platform.
Integration between BookWorks and MobiWork — the award-winning field services management platform (4.9 on G2 and Capterra). MobiWork field service notifications and work order updates surface in BookWorks, giving back-office teams real-time visibility into field activity without manual bridging between the two systems.
Running a system that needs to connect to BookWorks? ATG platforms, cardlock networks, fleet management software, banking systems, state regulatory portals, ERP or accounting systems, or anything else — bring the requirement and we'll scope it.
BookWorks exposes a comprehensive API covering every data entity the platform manages — customers, orders, inventory, pricing, GL transactions, deliveries, tank readings, and more. Every standard endpoint is available for integration. And when a custom API endpoint is needed for a specific workflow, we build it.
Every custom software project at Key follows the same process — a detailed discovery, a meticulous Statement of Work, and then execution by the team that built the platform. You know exactly what you're getting and what it costs before work begins.
You describe the requirement — a new integration, a missing report, a billing rule that doesn't exist in standard BookWorks. Key asks clarifying questions to fully understand the scope, the data involved, the systems that need to connect, and the desired outcome. This conversation is free.
Key's development team breaks the project into tasks, estimates each one in hours, and assembles a detailed Statement of Work that describes every deliverable, every integration point, every test case, and the total fixed fee. This is a real engineering document — not a vague proposal.
You review the SOW, ask questions, and approve it. If the scope needs adjustment — you want to add something or remove something — the SOW is revised before sign-off. Nothing starts until you've agreed to exactly what's being built and what it costs.
Development is done in-house by the BookWorks development team — not outsourced. They have full access to the BookWorks codebase, full knowledge of the data model, and deep understanding of petroleum operations. Work is done against the SOW scope.
Custom work is tested against your actual BookWorks environment before deployment. You review the output — the integration working, the report rendering, the billing logic calculating — and sign off before it goes live. Deployment is managed by Key, not handed off to you as a self-service update.
Once deployed, custom features are supported under your standard BookWorks monthly support. If something breaks, you call support. If a platform update affects your custom integration, Key addresses it. You're not left maintaining a feature you paid to build.
Custom BookWorks development falls into five broad categories — each with its own scope considerations, typical timelines, and integration points. If what you need spans multiple categories, that's fine. The SOW covers everything.
Connect BookWorks to any external system that has an API or file-based interface. We've built integrations across C-store POS, fleet management, card networks, delivery platforms, and banking — and we'll build yours.
Crystal Reports layouts, Excel exports, management dashboards, state tax filings, and any structured output your operation or regulators require that isn't in standard BookWorks.
Billing structures and pricing logic that don't fit the standard BookWorks model — unique surcharge calculations, custom contract pricing, unusual commission structures, or non-standard invoice formats.
Entirely new functionality added to BookWorks — workflows, screens, automation, or data management capabilities that don't exist anywhere in the platform today. The most complex category, and the one most likely to become a standard BookWorks feature.
Purpose-built import and export formats for specific suppliers, state regulators, banking systems, or partner platforms that require BookWorks data in a format it doesn't currently produce.
If you have a requirement that doesn't fit neatly into one of these categories — or if you're not sure whether it's even feasible — describe it to us. The discovery conversation is free, and "no, that's not possible" is rarely the answer.
When Key builds a custom feature for any client, it becomes a candidate for inclusion in a future BookWorks release. What started as one client's specific requirement often turns out to be something the broader BookWorks customer community needs — it just hadn't been asked for yet.
The discovery conversation costs nothing. Describe the requirement — the integration, the report, the billing logic, the new feature — and Key's development team will assess feasibility and scope a Statement of Work. No obligation until you approve the SOW.
📧 sales@keyinfotech.com · 1000 S. Old Woodward Ave, Suite 102, Birmingham, MI 48009
Other BookWorks services