Standard integrations, and what's available by arrangement.
These integrations are active in HaulageOps today. No additional scoping required.
The integrations below are built, tested, and running as part of the standard HaulageOps platform. When you set up HaulageOps, these are available to configure as part of your onboarding — not feature requests, not roadmap items, not optional add-ons at extra cost.
Xero
OAuth2 connection to your Xero account. Invoices created in HaulageOps sync to Xero on a 6-hourly cron schedule. Real-time payment webhooks flow back when Xero records a payment — updating invoice status in HaulageOps and the Client Portal without manual action.
Full Xero integration detailGoogle Maps
Address autocomplete powered by the Google Maps API — used during job creation for pickup and delivery addresses, reducing entry errors and ensuring addresses are geocoded correctly. Distance calculation for rate and routing reference.
Mapbox
Interactive mapping used in the Subcontractor Portal. Subcontractors view their assigned job locations on an interactive map — pickup point, delivery site, and current routing — without needing a separate navigation app to understand the assignment.
Firebase FCM
Push notifications for the driver mobile app on iOS and Android, delivered via Firebase Cloud Messaging. Job assignments, status alerts, and dispatch notifications are pushed to the driver's device without requiring the app to be open. Notification delivery is not dependent on the driver checking the app.
Microsoft Azure
All document and file storage in HaulageOps uses Microsoft Azure Blob Storage — POD photographs, customer signatures, delivery dockets, driver licences, vehicle registrations, insurance certificates, and contract documents. Files are stored in Azure regardless of where they were uploaded from (driver app, Admin Panel, or direct upload).
Socket.io (real-time)
Live job tracking and real-time dispatch board updates use Socket.io. When a driver updates a job status or their GPS position changes, the dispatch board and the Client Portal reflect that update in real time — without requiring a manual refresh from the person watching the board.
MYOB is not a standard live integration — but it may be achievable for your setup.
MYOB is not a standard built-in integration in HaulageOps the way Xero is. MYOB exists across a range of product versions — MYOB Business, MYOB AccountRight, MYOB Essentials, and others — each with different API capabilities, configuration requirements, and limitations. A connection that works cleanly for one MYOB setup may not be practical for another.
If you use MYOB, we can explore what is technically achievable for your specific situation. The starting point is understanding:
- Which MYOB product and version you are running
- Whether your MYOB is cloud-hosted or on-premises
- What you need the connection to do — invoice sync, payment status, or both
- Your timeline and whether a phased approach is acceptable
From that starting point, we can give you an honest answer about whether a connection is practical for your situation, what it would involve to build, and whether the scope is something we can commit to. We will not tell you MYOB is supported and then scope it to something different after you sign.
If MYOB is a firm requirement during your evaluation, raise it at the demo stage. That conversation is the right place to get a direct answer.
These are planned. They are not available in the current product.
The items below are on the HaulageOps development roadmap. They are not live features, not in beta, and not available to configure. We list them here because operators ask about them — and being clear that they are future items, not current capabilities, is more useful than a vague “coming soon” buried in a features list.
Hardware telematics APIs
Connection to hardware GPS and telematics devices (Teletrac Navman, Samsara, Lytx, and similar). HaulageOps currently uses phone-based GPS through the driver app. Hardware telematics integration is on the roadmap. Until then: keep your GPS hardware — HaulageOps is the operations layer above it, and the two can coexist without a live data connection.
ELD / Electronic Work Diary
Electronic Work Diary integration for fatigue management compliance is on the roadmap. HaulageOps currently records break and rest periods through the driver app manually. A direct ELD connection — syncing work diary records automatically — is not live today. If this is a requirement, let us know your timeline.
Sage accounting
Sage is not a current integration. If you use Sage and are evaluating HaulageOps, the Xero integration is the accounting connection that is live today. A Sage connection is on the roadmap but has no committed timeline. Tell us if Sage is your accounting system and we will be direct about what is realistic.
OCR scale ticket capture
Automated extraction of tonnage and load data from scale tickets via optical character recognition. Not live today — scale ticket data is currently entered manually into the job record. OCR capture is on the roadmap to reduce that entry burden, particularly for high-volume quarry and earthworks operations.
Weighbridge integration
Direct data feed from weighbridge systems into job records — automatic capture of gross, tare, and net weights at the point of measurement. Not live today. If weighbridge data is a key part of your invoicing workflow and manual entry is a current pain point, raise it at the demo stage.
Route optimisation
Automated route optimisation for multi-stop scheduling. Not live today — routing decisions are currently made by dispatch using the available mapping and job visibility tools. Route optimisation is on the roadmap. We will not describe the current product as having this capability.
If a roadmap item is a hard requirement for your evaluation: tell us at the demo. We will give you a direct answer about realistic timelines rather than letting it become a surprise after you have committed. Some roadmap items have clearer paths and shorter horizons than others — the conversation is the right place to find out which applies to what you need.
Some integrations are outside scope — not a gap, a deliberate boundary.
HaulageOps is purpose-built for bulk haulage, earthworks, and construction logistics. The platform is not a horizontal TMS trying to serve every transport model. That focus is why the features that do exist are well-suited to operators in those sectors — and it means some integration requests are genuinely outside scope, not just not yet built.
Parcel TMS models
Parcel delivery operations run on fundamentally different data structures — multi-stop routes, consumer-facing delivery windows, barcode scanning at every touchpoint, returns processing. HaulageOps is not built for that model and does not integrate with parcel-oriented TMS platforms. If your operation is parcel delivery, HaulageOps is the wrong product.
3PL warehousing systems
Warehouse Management Systems (WMS) for third-party logistics operations have a data model centred on inventory, SKUs, pick-pack-ship workflows, and storage locations. HaulageOps does not have a WMS component and does not integrate with 3PL WMS platforms. We are transport management for bulk haulage — not warehousing.
Freight forwarding platforms
Freight forwarding involves customs, multi-modal transport, bill of lading, and freight broker workflows that are structurally different from domestic bulk haulage dispatch. HaulageOps does not integrate with freight forwarding platforms and is not designed to support that operational model.
The narrowness of HaulageOps is intentional. Operators managing 15 to 80 vehicles across bulk haulage, earthworks, quarries, and civil construction logistics get a platform that is built for their exact operation — not a generic TMS with features that do not apply to them and gaps in the ones that do. If your operation is in that bracket, book a demo and see how the features map to your actual workflow.
The integration picture connects to the core platform.
Xero Integration
The full detail on how the Xero connection works — OAuth2, 6-hourly sync, real-time payment webhooks, and how the two systems divide responsibility.
Xero integration detailPlatform Overview
The full picture of what HaulageOps does across all five portals — job management, dispatch, driver app, subcontractor portal, client portal, billing, and compliance.
Platform overviewBilling & Invoicing
How invoices are created from completed job data, managed through the draft-to-paid lifecycle, and synced to Xero — before any external integration is involved.
Billing & invoicingAdd-ons and integrations — common questions.
Can you build a custom integration for a system we use that isn't listed here?
It depends on what the system is and what the connection needs to do. Some custom integrations are practical — if the external system has a well-documented API and the data exchange is well-defined, a scoped connection is often achievable. Others are not practical within a standard engagement. The starting point is telling us what system you use, what you need it to do with HaulageOps, and your timeline. We will give you a direct assessment — including whether it is a standard build, a scoped project, or outside what we can support.
What does “available subject to scope” mean in practice?
“Subject to scope” means the integration is not a standard off-the-shelf connection that can be switched on during setup. It means that whether a connection is possible — and what it would look like — depends on your specific system configuration, version, and required workflow. For MYOB specifically: we need to understand your MYOB product, hosting arrangement, and what data needs to flow, before we can tell you whether a connection is achievable and what it would involve. “Subject to scope” is honest — it is not a soft yes or a delayed no.
Is there a fee for add-ons or integrations?
The standard live integrations — Xero, Google Maps, Mapbox, Firebase FCM, Microsoft Azure — are included in your HaulageOps subscription. There is no separate per-integration licence fee for these. For integrations that require custom scoping and build work — such as MYOB or other non-standard connections — the cost is determined by the scope of the connection required. This is discussed and agreed before any work starts.
We use Xero in the UK / NZ — does the integration work for us?
Yes. The Xero API is consistent across Xero's AU, NZ, and UK products. The HaulageOps Xero integration works with active Xero accounts in all three markets. The connection uses Xero's standard OAuth2 API regardless of which regional Xero product you are on. See the Xero integration page for full detail.
We need weighbridge data in our jobs — what are our options today?
A live weighbridge integration is on the roadmap but not currently built. Today, weighbridge data — gross, tare, net weights — is entered manually into the job record at the point of capture or immediately after. For operations with high weighbridge volumes, this is an acknowledged data entry burden. If you need a timeline on the weighbridge integration, raise it at the demo and we will tell you where it sits in the development sequence.
We have hardware GPS trackers on our trucks. Can HaulageOps use that data?
Not directly today. Live telematics integration with hardware GPS devices is on the roadmap. The current approach is: keep your hardware GPS — it serves its own purpose for vehicle tracking. HaulageOps uses phone-based GPS through the driver app for job tracking, status updates, and dispatch visibility. The two systems coexist without a live data feed between them. When hardware telematics integration becomes available, it will add a second source of position data into the HaulageOps tracking layer.