Straight into the service manual page
WrenchQuarry
More

3 limits to set on a recurring maintenance plan discount

WrenchQuarry Editorial Team · Published · 12 min read · How these guides are written

Why a discount code needs limits

A recurring maintenance plan discount needs three limits: a cap on total redemptions, a fixed duration, and a limit on how many discounts can stack. Without them, a promotion meant for one season can keep costing you money long after everyone has forgotten it.

The stakes are bigger than one bad code. OpenStax describes the scale of the service business this way: "The service industry is a vital sector of the U.S. economy, providing 65% of the U.S. private-sector gross domestic product and more than 79% of U.S. private-sector jobs." Maintenance work is part of that sector, and a plan is a service sold on repeat. A small pricing error on a plan gets multiplied at every renewal.

A maintenance plan is a promise that repeats. A customer pays a set amount on a regular schedule, and in return your crew comes out for tune-ups, inspections, filter changes, or whatever the plan covers. Discounts are a natural way to bring people in. A first-season deal or a referral code can help a plan fill up during a slow stretch.

The trouble starts when a discount has no edges. A code meant for one spring promotion gets passed around in a neighborhood group chat. A customer keeps using it long after the promotion ended. A second code is created for another campaign, and a third gets added because a dispatcher wanted to close a sale that afternoon. Nobody made a bad decision on purpose. Each code was created on its own, with no shared rule about what it could cost over time.

Recurring billing makes this worse than a one-time job discount. A discount on a single invoice costs you once. A discount on a subscription repeats on every renewal until something stops it. A small percentage left running for a long time can quietly erode the margin on a plan.

Before you create the next code, answer three questions. How many times can it be used in total? How long does it last for each customer? Can it combine with other discounts? Those answers cover most of the leaks owners and dispatchers run into. They don't require special software, only someone to write the answers down and check them.

The examples here draw on Stripe's billing documentation because it describes these settings in plain language. The same thinking applies whether your plans run through billing software, a payment processor's dashboard, or a spreadsheet and a calendar. Check what your own tool supports, because not every system offers every setting. If your tool cannot enforce a limit, write it into your policy anyway and have someone check it by hand. For more on setup controls, see maintenance subscription setup controls.

Limit one: cap the total number of redemptions

Set a maximum on how many times a code can be used in total, rather than leaving it open-ended. The Stripe coupon documentation explains that setting max_redemptions=50 means the coupon can only be applied 50 times total: once each to 50 different customers, 50 times to the same customer, or any combination until the limit is reached.

That last part matters more than it first appears. A cap on redemptions is not a cap on customers. If one customer can use the code again and again, the whole allowance can go to a single account. Pair the cap with a rule about who can use the code and how often.

For a plan promotion, a clear rule might be that the code is for new customers only, and that each household can use it once. The check takes seconds once it becomes a habit, and it keeps a promotion meant for new business from quietly reaching existing customers.

Choose the cap based on what you can afford to give away. If you run another promotion later, create a new code with its own cap rather than reviving an old one.

Write the cap down before you launch, along with the start date and who approved it. A cap that lives only in someone's head tends to drift. A written note settles the question before it becomes an argument with a customer. Review the redemption count while the promotion is running. If the code is being used faster than expected, you can let it run out, narrow the audience, or make a short announcement.

Limit two: set how long the discount lasts

The second limit controls time, and it is where most long-running mistakes begin. An open-ended discount on a recurring plan is easy to create and easy to forget. Months later the customer still pays the lower price, and nobody remembers it was meant to be temporary.

The Stripe documentation gives a concrete case: "a coupon for 50% off with duration_in_months=4 applies to all invoices in the 4-month period starting when the coupon is first applied." That sentence contains two things worth checking every time you set a duration.

The first is the length. If your offer says three months off, the duration setting needs to match that promise exactly. A mismatch between what the customer was told and what the billing system does leads to disputes, and it is far easier to prevent at setup than to fix on a bill.

The second is the starting point. The clock begins when the coupon is first applied, not when the code was announced. A customer who hears about the offer in March but signs up in April gets a window that starts in April. Put the start rule in the promotion description so the customer understands it before they sign up.

Billing frequency changes the math too. The same duration can cover a different number of charges depending on how often the plan bills. The Stripe documentation notes that "in a monthly subscription, the coupon applies to the first 4 invoices," while "in a weekly subscription, it applies to every invoice in the first 4 months."

Billing scheduleWhat the 4-month duration coversWhat the customer sees
MonthlyThe first 4 invoicesFour discounted bills
WeeklyEvery invoice in the first 4 monthsMany more discounted bills

Describe the offer in the same units the customer sees on their bill. Decide which unit you are promising, write it in the offer, and confirm the schedule before the code goes live. For how plan billing dates are set, see maintenance plan billing settings.

The end of the discount needs its own plan. Decide whether the price returns to the regular rate on the next invoice, and whether the customer gets advance notice. A sudden jump after a long stretch of lower payments can feel misleading even when the terms were technically correct. Telling customers ahead of time, in plain words, turns a surprise into a planned step. Use the same notice rule for every customer.

Be careful with open-ended discounts. Some owners keep a lower rate for a loyal customer on purpose, and that can be a sound choice. Make it a deliberate loyalty decision with a stated reason and an approver, rather than a code created without an end date that nobody chose.

Limit three: cap how many discounts can stack

The third limit is about combinations, and it is the one owners tend to think about last. Offers pile up. A referral credit, a seasonal promotion, a loyalty rate, and a bundle deal might each be reasonable alone. Together on the same plan, they can push the monthly price well below what it costs to deliver the service, and the total is easy to miss until it shows up on a report.

Some billing platforms impose their own ceilings. The Stripe documentation states that "you can apply up to 20 discounts to a subscription, subscription item, or invoice." That is a platform limit, not a business rule. A smaller limit you choose is usually easier to explain to a customer, easier to apply correctly, and easier to audit at the end of the season.

A practical version is a simple stacking rule. For example, a plan may take at most one promotion code and one loyalty rate at a time, and no other offers. Decide whether a referral credit counts toward that total or is handled as an account credit instead. The exact rule is your choice. What matters is that it is written down, that everyone who creates or approves a discount knows it, and that the billing setup reflects it as closely as the tool allows.

Codes and coupons are different things, and the difference affects stacking. The Stripe documentation gives an example: "For example, FALLPROMO and SPRINGPROMO can both map to a single 25% off coupon." Two code names can point to the same discount. The code is a label a customer types in, and the terms come from the coupon behind it. The name on the code is the least useful part of the record.

Stacking mistakes often start with good intentions. A dispatcher wants to keep a customer who is thinking of cancelling, so they add a second discount. A written limit gives a clear answer: the plan has reached its allowed discounts, and here is what the team can offer instead, such as a free add-on inspection or scheduling priority. A non-price benefit can keep a customer without changing the discount math.

Decide who can override the rule. A warranty issue or a service complaint may justify an exception. If overrides are allowed, record who approved them and why. Unrecorded exceptions become the new normal, and then the limit stops meaning anything.

Putting the three limits together

The three limits work best as a set. Here they are side by side:

LimitQuestion it answersExample from the source docsWhat to write down
Redemption capHow many total uses are allowed?max_redemptions=50 allows 50 applications in totalThe cap, the start date, and the approver
DurationHow long does each customer keep the price?duration_in_months=4 covers the 4-month period from first applicationThe length in billing units, the start rule, and the price after it ends
StackingHow many discounts can combine?The platform allows up to 20 discounts; your rule can be smallerThe maximum count, what counts toward it, and who can override it

The duration limit controls how long each person benefits. The stacking limit controls how many discounts apply at once. If you set only two of them, the third is usually the gap that causes trouble.

Consider a sample spring offer: a percentage off for a fixed number of months, available only to new customers, capped at a set total of uses, and not combinable with other discounts. The cap keeps total cost within a planned range. The duration limit ensures the discount ends on a known date for each customer. The stacking rule keeps a new customer from receiving the spring offer plus a referral credit plus a loyalty rate on the same plan.

Now picture the same offer with no limits. The code is open-ended, usable by anyone who has seen it, and combinable with whatever a dispatcher thinks is reasonable. Plan count may rise in the first month and look like a success. Later, the team may find customers paying well below the regular rate, some of them existing customers who found the code, and no end date anywhere. Nobody made one large mistake. Several small, reasonable choices added up.

The limits do not have to be harsh. A generous offer can still be well controlled. The goal is that the discount does what you intended, for the people you intended, for as long as you intended.

For a quick test of any new code, read its terms twice: once as the customer and once as the owner. The customer should be able to tell when the discount starts, how long it lasts, and what the price will be afterward. The owner should be able to tell the most the promotion can cost and whether it combines with anything else.

A short checklist before you launch

Use this list each time a new discount code is created for a recurring plan. It is short on purpose, so that it actually gets used.

  • Write down the total redemption cap before the code goes live, and decide whether one customer can use it more than once.
  • Decide who the code is for, and state the rule in the promotion record. If your tool cannot enforce it, name the person who will check it.
  • Set the duration in the same units the customer sees on their bill, and confirm when the clock starts.
  • Write down what the price returns to when the discount ends, and how and when the customer will be told.
  • Set a limit on how many discounts can combine on one plan, and check that the billing setup matches it.
  • Look up the coupon behind each code so you know the real terms, not just the name.
  • Set a review date while the promotion is running, so that an offer meant to end does not quietly continue.

Who owns these settings

Often the dispatcher creates codes and the owner approves them, or the owner does both. Either arrangement works, as long as the limits are written where both people can see them. A short policy page, kept with the plan documents or in the billing tool's notes, is enough. It should list the standard cap rules, the default duration, the stacking rule, and the exception process.

Owners should review active codes on a regular schedule. Check each code's cap, duration, and stacking terms against the written policy, confirm that any open-ended pricing still has a reason behind it, and remove finished codes. A short review at the start of each season can catch drift before it costs real money.

Dispatchers often hear about a discount question or problem first. A dispatcher who knows the three limits can answer a customer clearly, decline a stacking request politely, and flag a code that is being used more often than expected. Make sure your dispatchers have the policy, not just the codes.

When a customer asks for an exception, have a standard response ready. Explain the current offer, mention a non-price benefit if the business can afford one, or state when the offer ended and what the regular rate is. Say it the same way to every customer in a similar situation.

Final thoughts

Discount codes on recurring plans are easy to create and hard to undo. That is the reason to set limits before the code goes out, not after it has been shared. Three questions cover most of the risk: how many total uses are allowed, how long each customer keeps the discount, and how many discounts can stack on one plan. Answer those in writing, check them against your billing tool, and review the active list on a regular schedule.

None of this requires a large system or an accounting background. It requires a short, clear policy and the habit of using it. Start with the next code you were planning to create. Put a cap on it, set its duration in the units your customers see, and decide what the price will be when it ends.

Sources

More field guides