You've done the hard thinking: the route is split into sensible days, the resupply stops are sorted, the overnights are booked. Now all of that has to live on the device you'll actually be looking at — your Wahoo or Garmin — so that on day three, somewhere you've never been, you can see that the last water for 40 km is coming up and tonight's bed is 12 km after the climb.
This is the step where a lot of bikepacking plans quietly fall apart. The route line transfers fine. The stops — the part that makes it a tour and not just a track — often don't. Here's why, and how to get them across properly.
Why a tour makes this harder than a day ride
On a single day out you might have two or three waypoints and you half-remember them anyway. A multi-day route is different: each day has its own set of stops, and you genuinely need them on screen because you're navigating unfamiliar terrain for hours, tired, with no phone signal. The plan only pays off if every day's water, food, campsite and accommodation are right there on the map and in the cue sheet.
So the goal is one file per day, each carrying that day's stops, each landing on your head unit with icons you can read at a glance and notes you can act on.
The reason planned stops arrive as blank pins
Every GPS brand uses its own internal vocabulary for waypoint types. What one planning app calls "water" or "food" or "shelter" doesn't line up with what a Wahoo or Garmin expects — so when the file lands on the device, it often can't tell what each stop is. The result is the classic disappointment: a screen of identical generic pins, or worse, stops that don't show at all. Your carefully marked "last shop before the pass" looks exactly like "nice view."
The fix is to translate each stop into the icon vocabulary your specific device understands before it goes on the head unit. That's the whole job, and it's what VeloPin does — it maps each stop to the right symbol for your chosen device, so water shows as water and a shop shows as a shop.
The core problem in one sentence: planning apps and head units label waypoints differently, so a stop that's perfectly clear on your screen at home can arrive on the device as a meaningless pin — or vanish.
On a Wahoo
Wahoo ELEMNT devices show waypoints as points of interest along the route, and the newer units render proper icons and let a note pop up as you approach. The catch is that the waypoint has to be recognised as the right type first — if the category doesn't translate, you get the default pin and the note usually doesn't appear either. Get the mapping right and each day's stops show as fork-and-knife, water drop, warning triangle and so on, exactly where you'll meet them. (More detail in our Wahoo waypoints guide.)
On a Garmin
Garmin Edge units treat your stops as course points and give you an approach alert — a little heads-up as you near each one, which is exactly what you want on a long day. Two things worth knowing: Garmin shows waypoint names truncated to a short length, so put the important word first ("Water — fountain", not "Fountain by the church — water"), and the note tends to appear as you approach rather than in a browsable list. Plan the names with that in mind and the device becomes genuinely useful. (See our Garmin Edge waypoints guide for the specifics.)
Notes earn their keep on a tour
On a day ride a note is a nice-to-have. On a tour it's the difference between a smooth resupply and a mistake you pay for. "Last water for 40 km." "Shop closes 18:00." "Campsite reception shuts at 20:00 — call ahead." These are the things you can't hold in your head on day four. Because different devices surface notes differently — some on approach, some only via the name — it's worth front-loading the critical word so it survives however your unit displays it.
Export each stage, not one giant file
It's tempting to put the whole tour on the device as a single route. Don't — a four-day file is unwieldy to navigate and your daily progress gets lost in it. One file per stage is far better: each day starts and ends cleanly, the cue sheet matches the day you're riding, and the stops shown are the ones that matter today. VeloPin builds your tour as one continuous route, then lets you export each day separately, with that stage's waypoints already translated for your device.
Getting the files onto the unit
Once each stage is exported for your device, it needs to reach the head unit. The quickest path is VeloPin's Send to Phone: scan the on-screen QR, the file downloads to your phone, and you open it straight into the Wahoo or Garmin app, which syncs it to the unit over Bluetooth or Wi-Fi. You can also transfer by USB or AirDrop if you prefer. Do this for each day's file before you leave home, or the night before each stage if you'd rather keep the unit tidy.
Pricing: Planning the tour and previewing every day's stops is free in VeloPin. Exporting each stage to your device with its waypoints, and Send to Phone, are part of VeloPin Pro (€4/month or €36/year), with a 3-day free trial.
Putting it together
The waypoints are what turn a line on a map into a tour you can actually ride: water where you'll need it, the shop you have to catch, the bed at the end of the day — each one on the device, recognisable, timed to where you'll be. Plan the route and resupply first (our guide on planning a bikepacking tour with resupply stops covers that), then export each day to your Wahoo or Garmin with its stops intact. Out on the trail, you stop reconstructing the plan from memory and just ride it.
Get your stops on your device
Free to plan · Per-stage export with VeloPin Pro
Open the bikepacking planner →