Stop guessing your wedding travel fee — price it by real distance

You quote a couple in Riverside. You quote another couple in Big Bear. Both venues are "about an hour away," so you charge the same travel fee. Then Big Bear turns out to be a two-and-a-half-hour drive each way with mountain roads, an overnight stay, and gas that costs more than the fee covers.

This is the quiet tax that comes with a zone-map travel fee — the kind where you draw a rough circle around your home base and charge a flat rate inside it, a bigger flat rate in the next ring out, and "contact for pricing" beyond that. It's simple to explain to clients. It's also almost never accurate, and the inaccuracy runs one direction more often than you'd like: against you.

The zone map is costing you more than you think

Most wedding photographers set travel fees the same way: pick a few concentric rings on a map, assign a flat number to each, and hope the average works out. It's not a bad system for a first pass. It just breaks down the moment a venue sits near the edge of a ring, or on a road that isn't a straight line, or across a mountain pass, a bridge toll, or a stretch of highway that turns a 40-mile trip into a 90-minute drive.

Here's what that actually costs over a season:

Undercharging on the far bookings. A venue that's technically "just inside" your outer ring but is genuinely 90 minutes of driving away gets the same fee as a venue that's a straight 45-minute shot down the interstate. You eat the difference every single time you shoot there — in gas, in the extra hour you're not editing or booking another client, in the wear on your car.

Overcharging on the close ones — and losing the booking. The flip side is just as real. A couple finds a venue that looks far on a map because it's across a lake or on the "wrong side" of a ring boundary, but the actual drive is short. You quote the higher zone fee, they balk, and you never even find out you scared off a booking you could have won at the accurate price.

The awkward conversation. Every wedding season, someone asks "why is the travel fee for our venue higher than what our friend paid for theirs, when they're basically the same distance?" You don't have a clean answer, because the zone map doesn't have one either. It's a flat rate standing in for something that's actually variable.

The mid-season scramble. New venue, no idea what ring it falls in, couple waiting on a quote, you're pulling up a map app and eyeballing it between client emails. It's a few minutes each time, but multiply that by every inquiry across a season and it adds up to hours you're not shooting or editing.

None of this is a huge dramatic loss on any single wedding. It's a slow leak — a few dollars short here, a booking missed there, a slightly-too-high quote that never gets a reply. Over a full wedding season, that leak is real money.

Price by the actual mile, not the ring you happened to fall in

The fix isn't a better map app or a more detailed spreadsheet of zones. It's knowing the real distance — or drive time — from your home base to every venue you're quoting, without spending time on it manually.

That's what CSV2GEO's subscription is built for. You keep a simple list — one column with your studio address, one column for each venue you're asked to shoot at — and you send that list in as a spreadsheet. What comes back is the same spreadsheet with exact coordinates and distance added for every row. No zones, no eyeballing, no "about an hour." Just the real number, for every venue, every time.

You set your travel fee as a rate per mile (or a rate per band of actual miles, if you prefer tiers) instead of a hand-drawn ring on a map. The fee becomes something you can quote confidently and explain in one sentence: "our travel fee is calculated by actual distance from our studio, and here's what that comes to for your venue."

How it works

You don't need any technical skill for this — if you can open a spreadsheet and attach a file to an email, you're set.

Step 1: Build your venue list

Keep a simple spreadsheet with the venues you're quoting or have booked — one venue per row, with the full address in one column. Add a column for your studio's home address too (it can just be the same address repeated on every row, or a separate reference point).

Step 2: Upload the file

Log in to your CSV2GEO account and upload that spreadsheet. There's nothing to install and nothing to configure — you're just handing over a file, the same way you'd attach it to an email.

Step 3: Let it process

The system reads every address in your list and works out the precise location for each one. For a wedding season's worth of venues — even a big one — this takes minutes, not hours.

Step 4: Download your results

You get back the same spreadsheet, now with exact coordinates and distance information added as new columns. Every venue, matched, with nothing left to guess at.

Step 5: Turn distance into your travel fee

Apply your per-mile rate (or your distance bands) to the new column, and you've got an accurate, defensible travel fee for every booking — one you can quote on the spot instead of estimating.

Step 6: Repeat it every month without starting over

Venue inquiries don't stop after the first upload. Each new wedding season, each new inquiry, you add the new venues to your list and run it again. Because it's a subscription, this isn't a one-off tool you paid for and forgot — it's there every month, ready for the next batch.

What it actually costs

CSV2GEO's Lite plan is $19 a month and covers 21,000 US rows. For context, most wedding photographers are quoting or shooting somewhere between a handful and a few dozen venues a month, even in a busy season — so this plan isn't sized for you, it's oversized for you, with room to spare for every inquiry, every booked wedding, and every "just checking the travel fee before we decide" email a couple sends. You can cancel any month you don't need it, but for the price of about one hour of shooting time, you get accurate travel pricing on every single booking for the whole month.

Compare that to the cost of even one underpriced far-venue wedding, or one lost booking because a close venue got quoted like it was across the county — and the $19 pays for itself the first time it prevents either.

FAQ

Is this hard to set up if I'm not techy at all? No. If you can attach a file to an email, you can use this. There's no software to install and nothing to learn beyond uploading a spreadsheet and downloading the one that comes back.

What if a venue address is messy — like a ranch with no street number, or "the barn behind the main house"? Most real-world venue addresses, even loosely written ones, are matched successfully. For the rare address that's too vague to place — a ranch with no formal street address, for instance — you'll see it flagged in your results so you know to double-check it yourself rather than guess.

Do I need to know anything about coordinates or mapping to use this? No. You don't need to understand what a coordinate is or how distance is calculated. You send addresses, you get back distances. That's the whole interaction.

Can I cancel if I only need this during wedding season? Yes. The subscription is month to month with no lock-in, so you can subscribe for your busy months and pause the rest of the year if that fits your business better.

Will this replace the client-facing quote I send, or is it just for my own use? It's for your own pricing work — you use the distance data to calculate the fee, then present that fee to your client however you normally do. Nothing about your quote template needs to change, just the number behind it.

Is my venue and client address data safe? Yes. You're uploading a spreadsheet to process it and get results back — it isn't shared, sold, or used for anything beyond producing your file.

What if I book more weddings than expected and need more than the Lite plan covers? You can move up a plan at any time. The next tier up, Plus, is $29 a month and covers 32,000 US rows, so there's room to grow without switching to a different kind of tool.

Related articles

• The real cost of running your own geocoder
• From free tier to your first paid plan: a startup's guide
• The one-week geocoding pilot playbook
• Handling addresses that won't geocode
• Geocoding without engineers: an ops guide

---

*I.A. / CSV2GEO Creator*