FareHarbor Review for Fishing Guides

I could not find out what FareHarbor costs. Not because I did not look: its pricing URL resolves to a not-found page, its own page sitemap contains no pricing entry at all, and the help-centre article that would explain the fee requires a login I do not have. What I did find is the mechanism, written clearly in the terms it publishes for the people who actually pay it. Your customers do. And the rate, in the platform's own words, is displayed in the booking funnel, which means at checkout on the day rather than anywhere you can read before deciding.

What do the customer terms actually say?

That the person booking pays a fee for using the service, that it applies online and in person, and that its amount appears in the booking funnel.

Section 3.1 of the customer terms is unusually explicit for a document nobody reads. It defines the booking fee as something the customer agrees to pay for obtaining a reservation.

It then names two cases. Bookings made online through the system, which it calls Online Direct, and bookings made in person through the provider, which it calls Offline Direct.

That second case is the one worth pausing on. A client who rings you, agrees a date on the phone and is then entered into the system is described as an Offline Direct booking, and the fee is defined to reach it.

Section 3.6 adds that booking fees are non-refundable except as otherwise provided, and section 1.6 authorises the card to be charged for the activity price and the booking fee together.

Blue Water, AL

Why does none of this appear on a pricing page?

Because there is no pricing page. The URL redirects to a not-found page and the site's own page inventory lists nothing of the kind.

That is a deliberate architecture rather than an oversight. A company hiding a price by accident does not also omit it from its sitemap.

And the logic is coherent once you see who pays. When the charge falls on the angler paying for the trip, no operator ever has to be persuaded of it, so there is no audience for a pricing page.

The comparison that makes this vivid is with the vendors that charge the operator. Those publish a number on a page you can read in ten seconds, because they have to sell it to you.

That correlation, between who pays and whether the rate is published, holds across the whole category and is examined in the free-tools piece.

Delta SportFishing, CA

Does the customer-paid model actually cost you anything?

Yes, indirectly, and that is the argument most operators skip. A fee added at checkout raises the total your angler sees, and conversion is decided at that screen.

A guide publishing $600 whose customer is charged $636 at checkout has advertised one number and collected another, whatever the paperwork says about who owes it.

Whether that matters depends entirely on the alternative in front of the client. If a competitor's page shows $600 flat, the comparison happens and you lose it silently.

It also complicates any published rate card, because the number on your website is no longer the number a booking produces.

The wider question of what a published price is for, and how few operators publish one at all, is measured in the pricing-page piece.

What is the API fee?

Two percent, paid by the operator on API-generated bookings, and it is the one rate I could establish at all.

Even that came from a public search-results snippet rather than a published page. The help-centre article explaining it sits behind a sign-in wall.

The public API fee terms define the mechanism carefully. The operator agrees to pay API fees for the facilitation of API bookings, calculated against the prices in the OTA price sheets.

I read that document end to end and no percentage appears anywhere in it. It establishes that a fee exists and how it is computed, and never says how much.

A separate public snippet indicates that bookings flowing through Booking.com are exempt from the API fee, which suggests the arrangement varies by channel in ways an operator would need to ask about.

What does the demo actually decide?

Everything, on this platform, which makes it a very different meeting from a demo of software whose price you already know.

With a published vendor the demo answers whether the tool fits how you work. The commercial question was settled before you booked the call.

Here both happen at once, and the second is being answered by a salesperson rather than by a page, which is a structurally weaker position for the buyer.

The practical response is to separate them. Ask for the commercial terms in writing before the product walkthrough, and treat a refusal as its own answer.

A guide who has already worked out what a competitor would cost across a season walks into that conversation with a figure to test against, which is the only real leverage available.

Does the booking fee show on your own website?

Yes, wherever the booking flow is embedded, and that is the detail with the most operational consequence.

The terms describe bookings made online through the system as Online Direct, which covers the widget or page a client reaches from your own site.

So a visitor who read your rate card, decided on a $600 trip and clicked through to book encounters a different total at the final step.

That gap between advertised and charged is the thing to think hardest about, because it arrives at the exact moment a booking is most likely to be abandoned.

How much of a guide's business actually converts at that screen, and how few sites are built to hold somebody there, is covered in the anatomy piece.

Is any of this unusual?

Less than it sounds. Five of fourteen booking vendors publish no price, and two of those have no pricing page at all.

What makes this one notable is scale rather than secrecy. It is among the largest platforms in the category, so the number of operators affected is correspondingly large.

It is also worth being fair about what the absence does not prove. An unpublished rate is not automatically a high one, and plenty of enterprise software is priced by conversation.

The published competitors are the useful contrast. One leads its pricing page with a claim about transparency and then states $99 a month plus 3 percent on online bookings only.

Another publishes three tiers with the online percentage and a fixed per-booking figure for offline and agent bookings, which is about as legible as this category gets.

What is the Booking.com exemption telling you?

That the fee structure is negotiated per channel, which means whatever you are quoted is unlikely to be a single universal number.

A public snippet indicates that bookings routed through Booking.com carry no API fee, since they flow through a different arrangement.

Read that as a signal rather than a detail. A platform with channel-specific exemptions has a commercial team making channel-specific deals, and the terms you get are the terms you asked for.

That cuts both ways for a small operator. A guide with no leverage takes the standard arrangement; a guide who asks specific questions may find there is room in them.

Either way it argues for treating the quoted figure as an opening position rather than a published rate, which is a very different negotiation from buying a $99 subscription.

What happens to the fee if a trip is cancelled?

The published position is that booking fees are non-refundable, except as otherwise provided in the terms.

That clause sits in the same section of the customer document and it is short enough to read twice, because on a weather-cancelled trip it matters.

Compare the marketplace convention. One competitor states plainly that on a weather cancellation the customer is refunded in full and the platform keeps nothing at all.

On a fishery where weather cancels more days than anything else, the difference between those two positions is a real annual number and a real source of client irritation.

Whose problem that becomes is worth establishing before you sign, because the person asking you about it will be the angler rather than the vendor. The wider weather question is in the deposit piece.

What should a fishing guide take from this?

That the product may well be excellent and the purchase is still a leap, because you cannot model the cost before committing.

FareHarbor is widely used and by most accounts capable software. Nothing here is evidence about the quality of the tool, only about the legibility of the deal.

What a guide should do is treat the demo as a pricing interview rather than a product tour. Ask the booking fee percentage, ask whether it applies to phone bookings, and ask what the API fee attaches to.

Get those answers in writing before signing, because the published record will not confirm them afterwards.

If the answers are good, the absence of a pricing page becomes a formality. If they are evasive, you have learned something more useful than a number.

How does it compare on the offline question?

Badly for a phone-heavy operation, at least on the published terms, because the fee is defined to reach in-person bookings.

Most guide bookings still arrive by phone. A platform whose fee attaches to a trip you sold yourself, on a call, is charging for something it did not source.

One competitor takes the opposite position explicitly, charging its percentage on online bookings and stating that offline sales carry no fee at all.

Another charges a fixed sum per offline booking of $1, dropping to 85 and then 70 cents on higher tiers, which is close to nothing on a $600 trip.

If most of your calendar is filled by returning clients ringing you directly, that single distinction is worth more than any feature comparison. How much of a guide's business actually arrives that way is measured in the website survey.

What are the common mistakes?

Four: assuming customer-paid means free, comparing against published competitors as though the totals were commensurable, skipping the offline question, and not asking about the API fee.

The first is the big one. A fee your customer pays still sits between your advertised price and their card, and it competes with every operator on your water who does not have one.

The second produces a false comfort. Setting a $99 subscription against an unknown percentage and concluding the unknown is cheaper is not a comparison, it is a hope.

The third catches exactly the operators this article is written for, because guiding is a phone business in a category built for online ticketing.

The fourth matters if you list anywhere else. The 2 percent applies to API-generated bookings, which is how a marketplace listing would route into your calendar.

What surprises people about this?

That the terms are clearer than the marketing. The legal documents describe the arrangement precisely and the website describes it not at all.

The customer terms name the fee, name the two cases it covers, state where the amount is displayed, and state that it is non-refundable. That is four useful facts in one section.

The second surprise is the phrase Offline Direct, which is a term of art for a booking the platform did not generate and does charge for.

The third is that a competitor's pricing page opens by claiming the simplest and most transparent pricing in the industry, which reads as a direct response to exactly this.

The fourth is how little of this is hidden. Everything in this article came from documents the company publishes; it is simply not where an operator would look.

What you must disclose to a customer before taking payment is set separately in every state and revised from time to time. Check the current rules with whichever authority licenses your operation before assuming a vendor's terms cover you.

What would change this assessment?

A pricing page. One number, publicly stated, would move this from an unknowable purchase to an ordinary one.

That is worth saying because nothing else here is a complaint about the company. The software may be excellent, the support may be first rate, and neither is in question.

What is in question is whether a guide can make an informed decision from outside, and today the answer is no, by design rather than by neglect.

Several competitors demonstrate that publishing is possible in this category without giving anything away, and one of them makes transparency its headline claim.

If that page appears, most of this article becomes obsolete, which is the outcome any operator reading it should prefer.

How would you decide?

By getting the three numbers in writing and then running the same arithmetic you would run on any published competitor.

Ask for the booking fee percentage, confirm in writing whether it applies to bookings you take by phone, and confirm what triggers the API fee.

Then put your own annual booking value through it and set it beside a vendor charging $99 monthly with 3 percent of online sales, which is the clearest benchmark this category offers.

Then decide how much the customer-facing total matters on your water. If your competitors publish flat prices, an added fee at checkout is a real competitive cost.

Then look at the alternatives with published numbers before committing. The rest of the category sits in the booking software hub, and the direct comparisons are in the alternatives piece.

Is the platform the wrong shape for guiding?

Possibly, and it is worth saying plainly rather than treating price as the only question.

This category was built for ticketed tours: fixed departures, per-seat inventory, high volume, online sale. That is a genuinely different business from a guide selling whole days to parties of two.

The vocabulary gives it away. Terms like online booking system, booking funnel and OTA price sheets describe a ticketing operation rather than a diary with a boat attached.

None of that makes the software bad. It makes it built for somebody else, and a guide adopting it is fitting their business to a model rather than the reverse.

Which is why the cheapest subscription vendors often suit guides better than the largest platforms, a point the whole category tends to obscure and which the free-tools piece works through.

What is not established here?

The rate, obviously, and anything about whether the software is good.

This is a review of a published record rather than of a product. I have not used the platform and nothing here is a judgement about its scheduling, its reporting or its support.

The 2 percent API figure comes from a public search snippet rather than a readable page, which is weaker evidence than a quoted document and I have flagged it as such throughout.

It is also possible that pricing is disclosed clearly and consistently during a demo. That would be a reasonable way to run a business and it is simply not verifiable from outside.

All of the above came off the company's own domain on a single day in July 2026. Documents like these get rewritten without announcement, so confirm the wording yourself before leaning on it.