Fleet Fueling Website vs Fuel Dispatch Software: What Should Own What?

Overview

A mobile fueling company has two very different workflows.

The public front office needs to know:

The delivery operation needs to know:

Trying to make one ordinary CRM own both creates a brittle system.

• who wants fuel;
• where;
• how many units;
• which fuels;
• rough volume;
• delivery cadence;
• who should quote the account.
• which customer site;
• which order;
• which truck;
• which driver;
• which route;
• how many gallons;
• which vehicle or asset received fuel;
• what proof confirms delivery.

What the public website should own

Usually:

Current OneStudio features fit this layer.

• service pages;
• industry pages;
• service territory;
• public quote request;
• ordinary client/contact history;
• marketing analytics.

What fuel dispatch software should own

Current petroleum-delivery systems manage combinations of:

That is operational delivery logic.

• orders;
• dispatch;
• routes;
• trucks;
• drivers;
• site/tank records;
• inventory/forecasting;
• quantities;
• proof of delivery;
• signatures/photos;
• delivery exceptions;
• invoicing.

Keep the quote separate from the delivery account

Prospect:

60 trucks at two yards, diesel and DEF, overnight fueling three times a week.

Accepted account may later contain:

Keep both.

The quote explains the commercial opportunity.

The delivery account controls operations.

• exact site coordinates;
• security instructions;
• vehicle roster;
• tank details;
• delivery windows;
• pricing;
• routes;
• reporting rules.

Keep customer and delivery sites separate

One company can have:

The CRM records the relationship.

The fuel system records the operational sites.

• headquarters;
• several yards;
• construction sites;
• generators;
• temporary projects.

Keep recurring orders specialist

Recurring fuel delivery can depend on:

A general reminder is not the authoritative recurring delivery schedule.

• day;
• time window;
• volume;
• tank level;
• fleet shift;
• route density;
• seasonality.

Keep route optimization specialist

Current delivery platforms calculate or manage:

OneStudio should not be positioned as a route engine.

• delivery sequence;
• route;
• ETA;
• driver/truck assignment;
• changes;
• missed stops.

Keep driver workflow specialist

The driver may need:

This belongs in the driver/dispatch app.

• route sheet;
• stop instructions;
• customer access notes;
• fuel product;
• gallons;
• meter;
• signature;
• photos;
• exception reason.

Keep metered quantities specialist

Mobile fueling can track the exact gallons delivered to:

That data can support billing and cost allocation.

Keep it in the fuel-management system.

• vehicle;
• equipment;
• asset;
• tank;
• job.

Keep proof of delivery specialist

Modern fuel-delivery software can capture:

That is delivery evidence, not a marketing activity.

• signature;
• photo;
• quantity;
• time;
• geolocation.

Keep tank telemetry specialist

Bulk-fuel operations may add:

Use the fuel platform that owns that data.

• tank-level monitoring;
• reorder thresholds;
• inventory forecasting.

Keep tax/reporting specialist

Some commercial accounts may need:

Do not claim the website produces these reports.

• fuel-tax data;
• IFTA support;
• cost codes;
• equipment/job reporting.

Use one explicit handoff

Choose:

Fleet fueling quote accepted into delivery operations

Before handoff:

After handoff:

• website;
• quote request;
• ordinary client/contact;
• marketing source.
• delivery account;
• sites/tanks;
• orders;
• dispatch;
• routes;
• drivers;
• metering;
• POD;
• operational billing.

Source-of-truth matrix

A 28-point buyer test

1. Website and dispatch systems have explicit roles.
2. Quote and delivery order are separate.
3. Client and operational account are separate concepts.
4. Client and site are separate.
5. Submitted fleet/volume remains historical.
6. Handoff has one explicit trigger.
7. Site has one owner.
8. Tank has one owner.
9. Pricing agreement has one owner.
10. Recurring schedule has one owner.
11. Delivery order has one owner.
12. Route has one owner.
13. Truck has one owner.
14. Driver has one owner.
15. ETA has one owner.
16. Gallons delivered has one owner.
17. Vehicle/asset fueling record has one owner.
18. POD has one owner.
19. Delivery exception has one owner.
20. Tank telemetry has one owner.
21. Invoice has one owner.
22. Fuel-tax/reporting data has one owner.
23. Public CRM excludes live route data.
24. Public CRM excludes driver tracking.
25. Public CRM excludes meter/POD truth.
26. Website URLs can survive dispatch-software changes.
27. Public analytics exclude sensitive operational data.
28. Staff can explain the boundary in one sentence.

Give the website the account opportunity and dispatch the delivery truth

The public layer should make it easy to qualify a fleet.

The fuel operations layer should make every stop, gallon and delivery traceable.

Explore OneStudio features, compare plans, or review the turnkey website service.

Questions businesses ask