Cabdata integration.
Modern booking channels in front of a long-standing Cabdata installation — API where you have one, scheduled exchange where you don't.
- Booking sync via API or scheduled CSV / database exchange
- Customer and account-client record mapping
- Rate-card and vehicle-class alignment
- Completed-job feed for invoicing and reporting
- Full historical import — customers, accounts, addresses, trips
- No change required to your on-premise dispatch setup
- Staged migration path if you later replace Cabdata
What the connector covers
Bookings taken through Limozoft channels are written into Cabdata with the correct account reference, rate and vehicle class. Completed-job data comes back for invoicing, account statements and reporting. Where your installation supports live status, passenger tracking and WhatsApp driver-confirmation messages run in real time; where it does not, passengers still get booking confirmation, price and reminder messaging.
Discovery is the first step on every Cabdata project because no two installations are configured identically. We document exactly which fields sync in which direction before any work starts.
Pricing and contract notes
Limozoft: flat per-vehicle monthly with the connector included; standard UK figures on the pricing page. Bespoke database work, if your install needs it, is scoped and quoted once during onboarding — never billed as an ongoing surprise.
Cabdata: quote-only, per fleet, and often bundled with on-premise server, telephony and support lines. If replacement is on your roadmap, get a written data export commitment and check your notice period first — that is where on-premise agreements usually bite.
Setup timeline
Day 1–2: discovery on your specific installation and access route. Day 3: field mapping for customers, accounts and rate cards. Day 4: test bookings and completed-job feed. Day 5–7: parallel run with live work. API-enabled sites are usually quicker; file-exchange sites take the full week.
Frequently asked questions
Does Limozoft integrate with Cabdata?+
Yes. Cabdata deployments vary by site, so we integrate through whichever route your installation exposes — booking API where available, database-level or scheduled file exchange where it is not. A short discovery call establishes which applies to your setup.
What if my Cabdata install has no API?+
Older on-premise installs often do not. In that case we use scheduled CSV or database exchange for bookings, customers, accounts and completed-job data, typically on a short polling interval. It is not real time to the second, but it is reliable and requires no change to your existing setup.
Can Limozoft import historical Cabdata records?+
Yes. Customers, account clients, saved addresses, rate cards, drivers, vehicles and booking history all import from standard exports. Request the export before serving notice on any agreement.
Does Cabdata publish pricing?+
No. Cabdata is quoted per fleet and commonly involves on-premise server and support costs alongside the licence. Limozoft publishes a flat per-vehicle monthly price with no per-trip fee.
Is the Cabdata connector included in my Limozoft plan?+
Standard API and scheduled-exchange connectors are included. If your installation needs bespoke database work, we scope that once during onboarding and tell you the cost up front.