Standing Add-On vs Separate Line Item Decision Tree

Why this matters

Every catalog eventually accumulates services that don't obviously belong in one bucket or the other: things techs sometimes attach to a bigger job and sometimes sell on their own. Filed the wrong way, these items either get buried as an afterthought nobody remembers to offer, or they clutter the main catalog with something that's really just an accessory to other work. Getting this classification right affects whether the item actually gets sold consistently, because a tech only offers what's easy to find and easy to explain in the moment.

Start here: how is the item actually used in practice

Pull your job history for this specific item and answer one question: in the jobs where it was sold, was it almost always attached to another service, or did it stand on its own as the entire reason for the visit?

• Almost always attached to something else - go to "Signs it should be a standing add-on."
• Regularly sold as the entire job on its own - go to "Signs it should be a separate line item."
• Genuinely mixed, no clear majority - go to "When it's genuinely both."

Signs it should be a standing add-on

Check these in order:

1. It rarely if ever justifies its own service call. If a customer would almost never call specifically to book this item alone, it's not carrying enough weight to stand as its own catalog entry.
2. It's naturally offered at the point of a bigger job. The best moment to sell it is while a tech is already on-site doing something else, "while I'm here" is the natural pitch, not a separate marketing push.
3. It's cheap and fast relative to the jobs it attaches to. Add-ons work best when they're a small increment of time and cost layered onto an existing visit, not a substantial job in their own right.
4. Multiple different core services could reasonably attach it. If it makes sense as an add-on to three or four different job types rather than one specific service, it belongs in a standing add-on catalog that any tech can pull from regardless of the base job.

If most of these are true, build it as a standing add-on: a short, always-visible list any tech can attach to any applicable job, with its own quick description and price, surfaced at the quoting or invoicing step rather than buried in a specific service's detail page.

Signs it should be a separate line item

Check these in order:

1. Customers call specifically asking for it. If it generates its own inbound demand, independent of any other job, it needs to be findable as its own catalog entry, not tucked inside another service's add-on list.
2. It has enough scope and time to justify solo pricing. If the job takes real, dedicated time and the four-input pricing method (labor, material, overhead, margin) produces a substantial number on its own, it's a real service, not an accessory. See related: Flat-Rate Menu Pricing: The Structural Mechanics.
3. It has its own seasonal or trigger pattern. If demand for it spikes independently of your other services, on its own calendar, it needs its own visibility in the catalog to be found when that demand hits.
4. It could anchor its own tiered structure. If Good-Better-Best tiering makes sense for this item on its own, it's substantial enough to be a standalone service, add-ons are rarely tiered because they're already the smaller half of a transaction. See related: Structuring a Good, Better, Best Catalog.

If most of these are true, give it a full catalog entry: its own category placement, its own description built around what it does and why a customer needs it, and if volume supports it, its own tiering.

When it's genuinely both

Some items legitimately earn a place in both structures at once: a standalone entry for the customer who calls specifically wanting it, and a standing add-on listing for the tech to attach it opportunistically to other jobs. This isn't a contradiction, it's the same underlying service reaching two different demand paths. Price it consistently across both listings so a customer never sees the same thing at two different prices depending on how they found it.

Quick recap

1. Check the job-history pattern first, don't guess from memory.
2. Mostly attached to other jobs, cheap, fast, cross-applicable: standing add-on.
3. Regularly stands alone, substantial scope, own demand pattern: separate line item.
4. Genuine mix: list it both places, one consistent price.

References

• See related: Flat-Rate Menu Pricing: The Structural Mechanics
• See related: Bundling Services Into Packages That Make Sense
• See related: Structuring a Good, Better, Best Catalog