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.