Recurring Billing: Automate Payments on Every Delivery Route

If the same twenty stops appear on your Tuesday route every week, you already have a subscription business. You’re just invoicing it by hand.

That’s the gap this article is about. Recurring billing is an automated charge on a set schedule, authorized once by the customer. The textbook version of it was built for software subscriptions, where the amount is identical every month and nothing physical happens. Recurring billing for businesses with delivery routes has to survive a total that moves every week, a delivery that sometimes doesn’t happen, and a customer who is a business rather than a consumer.

The good news is that it’s a solved problem, and the tooling exists. The trap is assuming a SaaS-shaped billing tool will fit a route-shaped business. If you’re still choosing the underlying payment provider, start with the three factors that decide a payment gateway for delivery orders, because ACH support and stored payment methods are the two properties that make everything below possible.

The Bottom Line

• A standing order is not a subscription. Your amount changes weekly, so you need variable-amount billing, not a fixed plan.
• Failed payments are the real leak. Recurly’s benchmarks put average involuntary churn at 1.25% against total churn of 3.60%, so roughly a third of all lost customers leave because a payment failed rather than because they wanted to (Recurly, retrieved September 2026).
• For wholesale amounts, ACH is not a preference, it’s arithmetic: roughly $0.50 to $1.50 on a $10,000 invoice against about $250 on a card (Resolve, retrieved September 2026).
• Bill after the drop, not before. Charging Monday for a Thursday delivery guarantees refunds every time a stop is skipped or short.
• The route benefit is separate from the cash benefit. Standing orders tell you what tomorrow’s van needs to carry, which is worth having even before the billing is automated.

Standing Orders Versus Subscriptions: Why the Difference Matters

Most recurring billing software is built around a plan: a fixed price, a fixed interval, the same charge forever. That model fits a gym membership and breaks on a delivery route.

Here’s what breaks. A cafe on your Tuesday route takes six loaves most weeks, nine before a holiday, and none the week they close for renovation. A produce account orders by weight, and weight is only known after the pick. A florist’s standing corporate arrangement changes price with the stems available.

So the billing has to be variable-amount and event-driven: the charge is generated from what was actually delivered, on a schedule, against a payment method the customer authorized once. That’s a different setup from a subscription plan, even though both are sold under the words “recurring billing”.

Three consequences worth planning around:

• You need a stored payment method rather than a fixed plan. The token is permanent, the amount isn’t.
• You need the delivery record to be the source of the amount, which is an integration question more than a billing one. The mechanics of that link are in the guide to payment APIs for order fulfillment.
• You need a way to skip a cycle without cancelling the arrangement, because “closed for two weeks in August” is normal and shouldn’t require re-signing anybody.

How to Set Up Recurring Billing on a Delivery Route

The sequence that works looks like this.

• Get one authorization, in writing. The customer agrees that you may charge a stored card or debit their bank account for goods delivered on an agreed schedule. Keep the record. It’s your defense in a dispute, and for ACH it’s a requirement rather than a nicety.
• Store the payment method, not the card number. Your provider returns a token. You keep the token. Nobody on your team should be able to read a card number, and storing one turns your order system into a PCI problem.
• Generate the charge from the delivery, not from the calendar. The run completes, the quantities are confirmed, the amount is known, the charge goes out. A billing job that fires on a fixed date regardless of what happened on the route will bill for deliveries you didn’t make.
• Send the statement before the money moves. For wholesale accounts especially, a notification a day or two ahead of the debit prevents most disputes, because the customer can query a line before it becomes a chargeback.
• Reconcile by payout. One deposit covering a whole route minus fees is what your accounting software has to match. Trying to reconcile stop by stop makes month-end worse, not better.

Card or ACH for Standing Delivery Accounts?

This is the decision with actual money attached, and it turns almost entirely on your average order value.

The crossover is easy to compute for your own business. A card at roughly 2.9% on a $180 weekly bakery drop costs about $5.50 a week. The same rate on a $2,400 weekly wholesale order costs about $70. Multiply by fifty weeks and the second number is a part-time salary.

Resolve’s comparison puts the extreme case plainly: on a $10,000 invoice, ACH costs roughly $0.50 to $1.50 while a card at 2.5% costs about $250 (Resolve, retrieved September 2026).

Most route businesses end up running both: cards for smaller retail-style standing orders where the fee is tolerable and setup is instant, ACH for the wholesale accounts where the percentage becomes indefensible.

Recovering Failed Payments Before They Become Lost Customers

This is the part everyone skips, and it’s where the money is.

A failed recurring payment doesn’t feel like churn. The customer still wants the bread. But if nobody notices for three weeks, you’ve delivered three weeks of goods for free, and the conversation that follows is the kind that ends accounts. Recurly’s benchmark data puts average involuntary churn at 1.25% against total churn of 3.60%, which means roughly a third of lost customers across their dataset left because of a payment failure rather than a decision (Recurly, retrieved September 2026). In ecommerce specifically the figures are 1.38% and 4.25%.

What to put in place, in order of effort:

• An alert on failure that reaches a person, not a log file. For a route business the deadline is the next delivery, which may be six days away.
• Automatic retries on a sensible schedule. Many declines are temporary, and a retry two days later clears a good share of them without anyone being contacted.
• A card updater service, offered by most major providers, which refreshes expired and reissued card details automatically. Expiries are one of the largest single causes of failure and this removes them quietly.
• A short, unembarrassing message to the customer with a link to update their details. For a standing account this is a normal piece of admin, not a collections letter.
• A rule about what happens to the next delivery. Decide in advance whether a failed payment pauses the stop, and tell customers what the rule is when they sign up.

What Standing Orders Do for the Route Itself

The billing case is the obvious one. The operational case is arguably bigger and tends to get ignored.

When a meaningful share of your stops are standing orders, tomorrow’s van load is known today. You can buy to a forecast instead of a guess, you can sequence a route that barely changes week to week, and your drivers learn the buildings, the loading docks and the back gates that cost fifteen minutes the first time and two minutes the tenth.

Routing software vendors make this point about recurring orders generally: predictable repeat stops reduce admin and make planning inventory, staffing and routes easier (WorkWave, retrieved September 2026).

Worth saying plainly: you can capture that benefit before you automate any billing. A written standing order with a manual invoice still tells you what Thursday looks like. Automating the charge is what stops the standing order from costing you an hour of admin a week.

Pricing a Standing Order Without Undercutting Yourself

Two questions come up every time.

Should a standing customer get a discount? Usually a small one is justified, because the order is predictable, the route is efficient, and the acquisition cost is already paid. Price it against the operational saving rather than as a general loyalty gesture, and set it as a percentage off the line items rather than a free delivery, so it doesn’t vanish the moment fuel costs move.

Should the delivery fee be part of the recurring charge? Generally yes, folded into a per-drop rate rather than itemized weekly. A stable, visible per-drop fee is easier to defend in a price conversation than a fee that moves with the order size, and it means a light week doesn’t produce a bill where the delivery costs more than the goods.

Getting Started This Month

If you’re running standing orders on manual invoices right now, the useful first step isn’t software.

Write down which of your customers are actually on a repeat pattern, what they take, and what they pay. That list is the requirements document. If most of them are small and retail-shaped, a card-on-file setup through your existing gateway will cover it. If most of the revenue sits in a handful of wholesale accounts, ACH is the priority and the billing tool matters less than the bank rails underneath it.

Then automate one segment, not all of them. Pick the group where a failure is cheapest to catch, run it for a month, and check the two numbers that matter: how many charges went out without anyone touching them, and how many failed without anyone noticing.