How to Sync Turo and Wheelbase to Prevent Double Bookings: A Step-by-Step Guide

Running a vehicle across more than one booking channel — Turo and a direct booking website, most commonly — creates real double-booking risk the moment those two channels stop talking to each other in real time. A renter books the vehicle on Turo, your website doesn't know about it yet, and a second renter books the exact same dates directly. This is largely preventable with the right setup, and it comes down to establishing one system as the single source of truth for every vehicle's availability, rather than trying to keep two or three separate calendars manually in sync. It's the practical, platform-specific version of the broader principles in our guide to preventing overbooking and double-booking.

The Core Architecture: Wheelbase as Your Central Reservation System

If you're running Wheelbase Pro as your booking engine, the setup you want is straightforward in concept, even though it takes a few deliberate steps to configure correctly. The goal is a single source of truth: Wheelbase holds the real availability for every vehicle, and every channel checks against it.

• A booking made on Turo automatically blocks that vehicle's dates in Wheelbase — and therefore on your direct booking website, which runs through Wheelbase.
• A booking made on your direct booking website is recorded in Wheelbase as the source of truth, and Turo's calendar is kept in step (see “What Syncs Automatically” below for exactly how).
• The same vehicle should never be bookable for the same dates through more than one channel.

The important architectural principle is that your website should communicate with Wheelbase, and Wheelbase should be the hub — your website should not be trying to talk to Turo directly. Wheelbase sits in the middle as the single source of truth. Wheelbase also offers a Turo-specific calendar option, which is a meaningfully more reliable way to pull Turo's bookings in than relying purely on a generic calendar file (ICS) feed — more on why that distinction matters below.

What Syncs Automatically — and What You Handle Manually

This is the part worth being precise about, because getting it wrong is exactly how double-bookings slip through. Wheelbase's Turo integration is designed to pull Turo's reservations INTO Wheelbase — the Turo calendar option plus email forwarding (both covered below) reliably capture Turo bookings so they block your website automatically. That direction is solid.

The reverse direction — a website booking automatically blocking those dates on Turo — is not something Wheelbase's own documentation currently describes, and Turo generally does not accept inbound calendar blocks from outside systems. In practice that means you should treat blocking Turo as a manual step: when a direct booking comes in, block those dates on the Turo listing yourself (or confirm the current behavior in your own account before relying on it). The same underlying reason is why the vehicle-reassignment limitation further down exists. Building that one manual block into your routine is what fully closes the double-booking gap.

Step 1: Connect the Turo Calendar Inside Wheelbase

For each individual vehicle in your fleet, you'll need to connect that vehicle's specific Turo listing to its corresponding vehicle profile in Wheelbase. In the Wheelbase dashboard, this generally involves navigating to your vehicle list, selecting the specific vehicle, opening its calendar settings, and choosing the option to manage connected calendars — specifically selecting the Turo calendar option rather than a generic external ICS feed.

You'll need that vehicle's Turo Vehicle ID to complete this connection. This ID is the number found at the end of that specific vehicle's Turo listing URL — for example, in a listing URL ending in “/tesla/model-3/2456789”, the Vehicle ID is the final number, 2456789. Enter that ID into the corresponding field in Wheelbase and save the connection.

This step needs to be repeated individually for every vehicle in your fleet that's listed on both Turo and your direct booking site — there's no bulk shortcut, since each vehicle's Turo listing needs to be mapped to its own specific Wheelbase vehicle profile.

Step 2: Set Up Turo Email Forwarding

Beyond the calendar connection itself, Wheelbase also benefits from receiving the actual reservation emails Turo sends — confirmations, cancellations, and modification notices — since this gives Wheelbase more reliable, immediate information about changes than calendar syncing alone might catch.

Inside the same calendar connection settings in Wheelbase, you'll find a unique forwarding email address generated specifically for your account — copy it. The setup on the email side means creating a forwarding rule in whatever account receives your Turo notifications (commonly Gmail) so messages from Turo's notification address get forwarded to that Wheelbase address automatically. A common snag: the Wheelbase forwarding address ends in .co, not .com, so double-check that when you enter it.

• In Gmail, open Settings (the gear icon) → See all settings → the Forwarding and POP/IMAP tab, then click Add a forwarding address and paste the Wheelbase address (confirm it ends in .co).
• Click through Next → Proceed → OK. Gmail runs a verification/authentication step to confirm the connection — follow any on-screen prompts to authorize it.
• Create a filter: open the search options (the sliders icon in the search bar), enter noreply@mail.turo.com in the From field, and click Create filter.
• On the next screen, check “Forward it to:” and select the Wheelbase address, then click Update filter. Optionally apply a label to keep these emails organized in your inbox.

To confirm it's working, go back to Gmail Settings → Filters and Blocked Addresses and check that the forwarding entry is listed. If Turo messages aren't reaching Wheelbase within about 24 hours, revisit the Forwarding and POP/IMAP tab and make sure the forwarding address shows as “Verified.” This is what lets Wheelbase process reservation changes, cancellations, and other updates more reliably than calendar data alone.

Step 3: Confirm Your Website Books Through Wheelbase

If your direct booking website uses the Wheelbase booking widget or connects through the Wheelbase API, the website side of the sync works automatically once the steps above are complete. When a customer books through your website, that reservation is created in Wheelbase, which immediately marks the vehicle unavailable for those dates everywhere Wheelbase controls — including your live site. When a customer books the vehicle on Turo instead, Wheelbase receives that reservation through the Turo integration and email forwarding, and your website's availability calendar reflects the vehicle as unavailable for those same dates.

The one direction to handle deliberately, as covered above, is pushing a website booking onto Turo — that's the manual block worth building into your process. With that habit in place, every channel stays genuinely in step. If you want deeper background on how Wheelbase handles the booking flow this setup protects, our plain-English explainer walks through it.

If You're Relying on ICS Calendar Feeds Instead

For operators not using the Turo calendar option, a more basic approach exists using iCalendar (.ics) feeds — exporting a calendar from Wheelbase and importing it where the other platform supports it, and importing a calendar feed in return. This can work as a fallback, but it comes with an important limitation worth understanding clearly: ICS syncing is generally not real-time. Depending on the specific platforms involved, updates can be delayed by anywhere from several minutes to several hours, which leaves a real window where a double-booking could still occur before the sync catches up. That's exactly why the dedicated Turo option, where available, is the more reliable choice for a business where a double-booking carries real reputational and financial cost.

Best Practice for Multi-Vehicle Fleets

For a fleet with more than one vehicle, the mapping between platforms needs to stay strictly one-to-one. Each specific Turo listing should be connected to exactly one specific Wheelbase vehicle profile, which in turn corresponds to exactly one listing on your website. A Tesla Model 3's Turo listing connects to its own dedicated Wheelbase vehicle entry, which feeds its own website listing — and the same pattern repeats independently for every other vehicle, whether that's a Toyota Camry or anything else you're running.

Never point multiple Turo listings at the same Wheelbase vehicle profile, or vice versa. That kind of many-to-one or one-to-many mapping breaks the entire premise of the sync system and reintroduces exactly the double-booking risk this setup is designed to eliminate. As your fleet and channel mix grow, the deeper configuration in our advanced Wheelbase guide is worth reading.

An Important Limitation Worth Knowing

One specific edge case worth understanding: if you manually change which vehicle is assigned to a reservation inside Wheelbase — for instance, swapping a renter from one vehicle to a similar one due to a maintenance issue — that change does not automatically propagate back to Turo. You'll need to manually update the corresponding reservation on Turo's side as well, or the two calendars will fall out of sync for that specific booking. Build this into your standard process for any vehicle reassignment rather than assuming the sync handles it automatically.

Common Mistakes When Setting Up This Sync

• Relying on ICS feeds when the dedicated Turo calendar option is available — the delay risk with ICS syncing is real and largely avoidable.
• Mapping more than one Turo listing to a single Wheelbase vehicle, which breaks the one-to-one relationship the entire system depends on.
• Assuming website bookings block Turo automatically — they don't reliably, so build in the manual Turo block for every direct booking.
• Forgetting to manually update Turo after reassigning a vehicle inside Wheelbase, since that action doesn't sync automatically.
• Not setting up email forwarding alongside the calendar connection — the calendar sync alone helps, but pairing it with forwarding gives Wheelbase more complete, timely information.
• Skipping this setup for even one or two vehicles because it feels like extra work — the double-booking risk applies to every vehicle listed on more than one channel.

If you're still weighing how Turo, Wheelbase, and a custom website fit together as a broader strategy rather than just a technical sync, that comparison is worth reading on its own.