What Add-On Fees Should I Be Charging That I'm Not?

What separates a fee customers accept from one they resent

There is a clean dividing line, and it holds across trades, retail, hospitality, and professional services: a fee is accepted when the customer can point to the thing it pays for. "Trip & dispatch" pays for the truck rolling. "Materials handling" pays for someone sourcing, staging, and hauling the parts. "After-hours service" pays for the tech who gave up a Saturday. "Rush turnaround" pays for reshuffling the schedule. Each of these names a tangible action, so the customer's brain files it under *cost of the thing I asked for* rather than *padding*.

The fees that generate complaints, chargebacks, and one-star reviews are the ones with no referent: "service surcharge," "administrative fee," "convenience charge" that isn't attached to any convenience. The dollar amount is rarely what triggers pushback — a $39 named fee lands more softly than a $12 mystery line. What triggers pushback is the customer's inability to reconcile the line item with anything they experienced. That reconciliation gap is the whole game.

This is why the sequencing matters more than the pricing. A fee introduced at quote time, as a visible line the customer sees before agreeing to work, converts at a dramatically different rate than the same fee appearing on an invoice after the job. Same amount, same name, opposite emotional reaction. The first reads as pricing; the second reads as a bait-and-switch. If you take one operational change away from this page, make it moving every candidate fee upstream into the estimate, proposal, or booking confirmation.

There is also a disclosure dimension that is no longer optional. Card-processing recovery fees are regulated differently state by state — surcharging is restricted or conditioned in several jurisdictions, and card network rules require clear disclosure at the point of sale plus a cap tied to your actual cost of acceptance. Before you switch on a processing recovery fee, check your state's rules and your processor's surcharge program. A cash-discount structure is the common alternative where surcharging is constrained. This is the one fee category where "just add it" can create real legal exposure, so treat it as a compliance step rather than a pricing step.

This vs. the common alternatives

Owners who feel underpriced usually have four levers available, and add-on fees are only one of them. Understanding why fees often win — and when they lose — keeps you from picking the wrong instrument.

Alternative one: raise the base rate. The cleanest move philosophically. No new line items, no explaining, no compliance questions. The problem is visibility. Your hourly rate, your service-call price, and your headline SKU prices are the numbers competitors shop and customers remember. A 10% base-rate increase is legible to the entire market instantly; a $29 dispatch fee is nearly invisible in comparison shopping because most buyers compare the headline number. Base-rate increases also apply uniformly, including to the low-cost jobs where you were already fine, while a fee applies precisely to the cost driver you are trying to recover.

Alternative two: raise volume. Sell more jobs. This is where most owners instinctively go and it is the most expensive path. New volume costs marketing spend, capacity, scheduling, sometimes headcount — and it arrives at your blended gross margin of roughly 25%–45%, not the 80%–95% of a fee. Adding $10,000 of new monthly job revenue at 35% margin contributes about $3,500. Adding $10,000 of fee revenue at 90% margin contributes about $9,000, with zero incremental jobs sold and no new capacity required. On a pure return-on-effort basis, the fee wins by a wide margin.

Alternative three: cut cost. Renegotiate suppliers, tighten routing, reduce truck rolls, trim software. Real and worth doing, but cost cutting is finite and often runs into service quality. You can only remove a cost once. A fee, once installed, compounds every month across every transaction.

Alternative four: bundle into tiers. Instead of a standalone dispatch fee, build "good-better-best" service levels where the premium tiers include priority dispatch, after-hours availability, and rush handling. This is the highest-sophistication play and the one that scales best — it converts a fee conversation into a value conversation. It also takes the longest to build, requires trained presentation in the field, and needs a pricebook structure most small shops do not yet have.

The honest comparison: fees are the fastest-to-cash, highest-margin, lowest-visibility lever, which is exactly why they are the most commonly left on the table. Tiering is the strongest long-term structure. Volume is the most expensive. Cost cutting is the most finite. Most shops should install two or three named fees now, then migrate them into tiers over the following year as the pricebook matures.

A useful sizing formula before you pick anything: Missed Add-On Revenue per Month = Monthly Transactions × Realistic Attach Rate % × Fee Amount, and the portion that reaches the bottom line is that figure × Add-On Contribution Margin %. A shop running 600 jobs a month, adding a $39 trip-and-dispatch fee at a 70% attach rate, is looking at 600 × 0.70 × $39 ≈ $16,380 in new monthly revenue, and at a 90% contribution margin roughly $14,700 of that lands as margin. Note the two variables that actually move the answer: attach rate and margin, not fee size.

How to choose between them

Choosing a fee is a filtering exercise, not a brainstorm. Run every candidate through the same four gates and most ideas die early — which is the point, because a bad fee costs you reviews and repeat business that no amount of fee revenue repays.

Gate one: does it recover a real cost or deliver a named benefit? If you cannot finish the sentence "this fee covers ___" in five words a customer would recognize, kill it. Fuel and vehicle wear, parts sourcing labor, weekend overtime, schedule displacement, interchange cost — all pass. "Administration" does not.

Gate two: is the math meaningful? Multiply transactions by a realistic attach rate by the amount. Be pessimistic on attach rate; owners routinely assume 90% and get 45%. If the result is not worth the operational friction of training staff, updating your pricebook, and handling objections, drop it and pick a different fee. Below roughly $1,000–$2,000 a month for most small shops, the friction outweighs the gain.

Gate three: can your existing system capture it automatically? A fee that depends on a human remembering to add it has an attach rate of whatever your least-disciplined employee does on their worst day. Fees must be default-on in the system: an automatic service charge, a pricebook item that appears on every relevant job type, a surcharge rule at the order level. If capturing it requires manual entry every time, expect leakage of 30% or more.

Gate four: is it compliant and disclosable? Processing recovery fees, auto-gratuity, and mandatory service charges all carry jurisdiction-specific rules and, in hospitality, tip-credit and wage implications. Confirm before you ship.

Rank surviving candidates by attach rate first, amount second. This is counterintuitive and it is where most owners get it wrong: a $15 materials handling fee at a 70% attach rate produces more monthly margin than a $50 expedite fee at 15%, and it generates a fraction of the objections. High-attach small fees also normalize faster — after two months nobody argues about them, and they become part of how your pricing simply works.

One more selection heuristic: prefer fees tied to events that already trigger a system record. A truck being dispatched, a card being run, an order marked rush, a job scheduled outside business hours — each of these is already a field in your software, which means the fee can be automated and audited. Fees tied to judgment calls ("difficult access," "extra cleanup") are hard to apply consistently and invite disputes.

Costs, timelines, and expected impact

The direct cost of installing add-on fees is usually near zero, which is what makes this the highest-ROI pricing work available to a small operator. If you already run a POS, field-service platform, or accounting system, fee capability is almost certainly included and unused.

Software you likely already have. Square's POS and invoicing are free to use, with in-person card processing around 2.6% + 10¢ and online around 2.9% + 30¢, and it supports custom service charges, surcharges, and auto-gratuity at item or order level at no additional software cost — its restaurant and appointment plans run roughly $0–$69 per location per month for richer tooling. Stripe Billing adds roughly 0.5% on recurring charges on top of standard card pricing and is the right choice when a fee must be computed per transaction or per seat programmatically. QuickBooks Online, where most small businesses already invoice, supports custom service items and a built-in surcharge feature. Toast, purpose-built for restaurants, runs roughly $0–$165+ per terminal per month and breaks out fee contribution by type. In field service, Housecall Pro runs roughly $59–$149+ per month with seat add-ons, Jobber roughly $29–$199+ per month by plan and seat, and ServiceTitan is quote-based, typically landing in the several-hundred-per-technician-per-month range for established shops with mature pricebooks. Proposal tools like PandaDoc, roughly $19–$49+ per user per month, matter less for capture and more for presentation — a pre-checked optional line inside a polished quote converts far better than a post-hoc invoice line.

The point of that list is not to buy anything. It is to establish that in nearly every case the fee feature is already paid for. Do not purchase a billing platform to charge a fee.

Real costs are operational, not financial. Budget four to eight hours to audit current pricing and pick candidates, two to four hours to configure the fee in your system and update templates, one hour of team training including objection handling, and roughly two weeks of active monitoring on attach rate and complaint volume. If you are touching card-processing recovery, add time for a state-law and processor-program check.

A realistic timeline. Week one: audit and select two candidate fees, build the objection script. Week two: configure in-system, update quote and invoice templates, train the team, soft-launch on a subset of jobs or one crew. Weeks three and four: full rollout, daily attach-rate check, weekly complaint review. Month two: measure average ticket change against a pre-launch baseline, adjust amount or presentation. Month three: install the second fee, and begin drafting the tier structure the fees will eventually fold into.

Expected impact. Operators who formalize a trip or dispatch fee commonly report average-ticket lifts in the mid-to-high single digits into low double digits without measurable churn, precisely because the fee is bound to a visible action. The mechanism is boring and reliable: revenue rises on transactions you were already performing, and because incremental cost is near zero, almost all of it drops to contribution margin.

Watch three numbers and only three: attach rate by fee, average ticket versus your pre-launch baseline, and complaint or waiver rate. If attach rate is low, the problem is capture or presentation, not price. If complaints are high, the problem is naming or timing. If average ticket did not move despite a healthy attach rate, someone is discounting elsewhere to offset it — a classic leak where field staff quietly reduce labor hours to keep the total flat.

Where the margin should go. Fee margin is the natural funding source for the back-office capacity that most growing shops under-resource: dispatchers, schedulers, a service coordinator, the person answering the phone on the first ring. This is the RevOps loop that makes fees compound rather than sit as a one-time bump — better dispatch improves on-time arrival, on-time arrival justifies the dispatch fee, the fee funds the dispatcher. Fees that fund nothing eventually get discounted away by the same team that resented explaining them.

Implementation and handoff details

Installation fails in predictable places, and every one of them is a handoff.

Handoff one: owner to system. The fee must exist as a real object in your software — a pricebook item, a service charge rule, an automatic surcharge — not as a note telling staff to remember it. Configure it to apply by default on the matching job type, order type, or time window, and require a reason code plus manager approval to waive it. Waiver-with-reason-code is the single most valuable control here, because it turns leakage into data: if 40% of dispatch fees are being waived under "customer complained," you have a presentation problem you can now see.

Handoff two: system to quote. Update every customer-facing template — estimates, proposals, booking confirmations, service agreements — so the fee appears as a named line before work is authorized. Include a one-sentence explanation inline. This is where PandaDoc-style proposal tools and quote templates earn their keep: the fee arrives framed as part of the offer.

Handoff three: quote to field. Your technicians, servers, and CSRs need one sentence they can say without hesitating. Write it for them: "The dispatch fee covers getting a fully stocked truck to you in the window we promised." Ten minutes of practice beats a memo. Untrained staff apologize for fees, and an apologized-for fee gets waived.

Handoff four: field to invoice. The fee must appear on the invoice with the same name it had on the quote. Renaming it between documents — "trip fee" on the estimate, "service charge" on the invoice — is a reliable way to manufacture a dispute.

Handoff five: invoice to collection. A fee you bill but never collect is worse than no fee: it inflates your reported revenue and hides a receivables problem. Card-on-file, automatic payments, and dunning on failed transactions matter here — subscription platforms like Recurly exist largely because failed-payment recovery is where fee margin quietly disappears.

Handoff six: collection to reporting. Break fee revenue out as its own income line so you can see contribution by fee type. If it is buried in "other income," you will never know which fee is working, and you will end up defending all of them or none of them.

A note on adjacent categories worth auditing while you are in here, because the same mechanics apply outside field service. Retail and food: to-go packaging, delivery, large-party service charge, allergen or custom-prep handling. Professional services: rush turnaround, expedited document processing, additional-revision fees, onboarding or setup fees, consultation fees that convert to credit against the engagement. Subscription and SaaS: implementation and onboarding, overage above a usage threshold, priority support, sandbox or additional-environment fees, data-migration charges. Equipment-heavy businesses: rental or loaner during repair, disposal and recycling, restocking on returns. Any business with a schedule: cancellation and no-show fees, which are less about revenue than about protecting capacity — a no-show fee that recovers only a fraction of the slot's value still changes behavior enough to pay for itself.

The upstream effect people underestimate: once fees are itemized, your job costing gets more honest. You stop absorbing dispatch and materials handling into a blended labor rate, which means you finally see which job types are actually profitable. Several shops discover that their cheapest service call was losing money for years, and the fee did not just add revenue — it exposed a pricing error in the base offer.

Related questions

How do I know whether my attach rate is good?

Compare it to the share of transactions the fee logically applies to. A dispatch fee should attach on nearly every dispatched job; if it attaches on 45%, that gap is leakage, not customer resistance. Waiver reason codes will tell you which it is within two weeks.

Should I grandfather existing customers?

For recurring or contract customers, yes — announce the fee with 30 to 60 days' notice and apply it at renewal. For transactional customers, no grandfathering needed. Silent mid-contract additions are the fastest way to lose an account you already earned.

Can I add a fee without new software?

Almost always. Square, QuickBooks, Jobber, Housecall Pro, Toast, and Stripe all support service charges or surcharges natively. Configure what you already pay for. Buying a billing platform solely to charge a fee inverts the ROI you were chasing.

What if a competitor doesn't charge this fee?

That is usually an advantage, not a risk, because your headline rate can stay competitive while your effective ticket rises. Verify by checking whether the competitor's base rate is higher — often it is, and they have simply bundled what you are itemizing.

Do fees hurt online reviews?

Named, quote-time-disclosed fees rarely appear in reviews. Surprise fees on invoices do, consistently. The review risk is entirely a function of timing and naming, which is why the presentation handoff matters more than the amount.

FAQ

What is the most common add-on fee I'm likely missing?

A trip or dispatch charge. Most service businesses absorb the cost of rolling a truck into their labor rate, where it is invisible and uncompensated on short jobs. Customers accept a named fee tied to the tangible act of sending a stocked vehicle to their address, and because it applies to nearly every job, its attach rate is naturally high.

How do I decide the amount for a new fee?

Start from the cost you are recovering, not from what you wish you could charge. Estimate fuel, vehicle wear, drive time, and dispatch labor per trip, set the fee at or modestly above that number, and test it. Small and defensible beats large and arguable — you can raise a normalized fee later far more easily than you can rescue one that generated complaints in month one.

Will Charging new fees drive customers away?

Not when the fee names a real cost or benefit and appears before the work is authorized. Vague surcharges on surprise invoices cause churn; named, quote-time fees generally do not, and operators formalizing trip fees typically see average ticket rise without measurable customer loss. The variables that predict pushback are naming and timing, not the dollar amount.

Which fee is easiest to implement first?

A materials handling fee, if you stock and haul parts, because it is uncontroversial and already tied to a visible activity. Card-processing recovery is mechanically the simplest but carries state-law and card-network disclosure requirements, so it is easy to switch on and easy to get wrong — check your jurisdiction and processor program first.

How should I handle a customer who refuses the fee?

Give the team one sentence explaining what the fee covers, then a bounded fallback: waive it with manager approval and a logged reason code, or offer it waived as part of a bundle or membership. The logging matters more than the waiver — reason codes convert individual objections into a pattern you can fix upstream in your presentation.

Where should the new margin go?

Into the back-office capacity that makes the fee true. Dispatchers, schedulers, and coordinators are what turn a dispatch fee into a promise you actually keep, and that RevOps feedback loop is what keeps the fee defensible over years rather than months. Fees that fund nothing tend to get discounted away by the same staff who dislike explaining them.

Sources

• Square Support Center — Service charges and automatic gratuity: https://squareup.com/help/us/en/article/5068-service-charges
• Stripe Docs — Billing pricing and invoicing: https://stripe.com/pricing
• Intuit QuickBooks Support — Add a surcharge or service fee to invoices: https://quickbooks.intuit.com/learn-support/
• Toast — Restaurant POS pricing and plans: https://pos.toasttab.com/pricing
• Jobber — Pricing and plans: https://www.getjobber.com/pricing/
• Housecall Pro — Pricing: https://www.housecallpro.com/pricing/
• National Conference of State Legislatures — Credit or debit card surcharge statutes: https://www.ncsl.org/financial-services/credit-or-debit-card-surcharges-statutes
• Visa — Rules and surcharging merchant guidance: https://usa.visa.com/support/merchant.html
• U.S. Small Business Administration — Pricing your product or service: https://www.sba.gov/business-guide/manage-your-business/pricing

Related on PULSE

• [How Many Attendants Should I Schedule Each Day at My Car Wash?](/knowledge/tl0067)
• [How Many Sales Reps Do I Need to Hire for My Logistics Company?](/knowledge/tl0058)
• [How Many Salespeople Do I Need to Hire for My Car Dealership?](/knowledge/tl0052)
• [How Many Producers Do I Need to Hire for My Insurance Agency to Grow My Book?](/knowledge/tl0015)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)