Handling add-ons and custom options without endless email chains

Quoting and configurators

The short answer

Handle add-ons by giving each option a clear definition, eligibility rule, quantity rule, and place in the saved quote specification. Separate standard extras from custom requests that need review. Show customers how an earlier choice affects later options, and update the summary when they change a selection. A structured form or existing product-options tool may be enough; a configurator is useful when dependencies and exceptions are difficult to represent clearly.

An email saying 'include the extra shelf too' is easy to miss when the base product, finish, and quantity have already changed in three other messages.

Create an option register your team can maintain

Put the options for one product or service range into a shared register. Give each one a stable identifier, customer-facing name, plain explanation, allowed quantities, and active or discontinued status. Names alone are fragile: two extras called 'premium finish' may mean different things.

Separate an included feature, an optional upgrade, a required dependent component, and a custom request. Customers should know whether they are choosing something extra or something essential for their earlier selection to work.

Name who owns the register and how changes are approved. If staff update a sales brochure but not the quote form, customers can request an option the team no longer supplies. Use a clear effective date and preserve enough history to interpret saved specifications created before the change.

Write down dependencies and quantity behavior

Rules to define for each optional selection
RuleQuestion to answerIllustrative example
PrerequisiteWhat must already be selected?Lighting requires the electrical preparation package.
IncompatibilityWhat cannot be selected together?A wall rail occupies the same position as a storage panel.
QuantityPer item, per order, or independently entered?One installation visit for the order, not for every unit.
ReviewWhen should staff decide?A requested finish outside the standard range.

These rules should describe the actual offer, not an arbitrary form sequence. SYSPRO's configurator documentation illustrates the role of dependencies in defining available selections. A small business can document the same relationships without adopting a large manufacturing system.

Make changed choices visible instead of silently repairing them

When an earlier answer changes, revisit dependent selections. If a chosen upgrade no longer applies, explain which choice caused the conflict and offer a clear way forward. Do not quietly substitute something the customer did not select.

For example, switching from a powered model to an unpowered model may invalidate an electrical add-on. The summary should identify the removed selection, update any estimate, and ask the customer to review the result. Saving the old hidden value would send staff a contradictory brief.

Preserve unrelated answers, uploaded references, and notes. Changing a product width should not erase the customer's delivery instructions. Where a free-text request remains relevant, retain its original wording and flag it for the reviewer rather than attempting to rewrite it into a standard option.

Illustrative example: one readable request for three units

Suppose a business offers configurable display units. A customer requests three standard units, two extra shelves per unit, one delivery, and a nonstandard paint color for review. The request should distinguish six shelves from two shelves total and one delivery from three deliveries.

A useful saved summary could read: 'Quantity: 3 units. Extra shelves: 2 per unit, 6 total. Delivery: one destination, pending address review. Paint: custom color requested, reference attached, not yet approved.' The customer can review that summary before sending.

If they reduce the order to two units, the shelf total changes to four while the delivery remains one. The custom color still needs review. This is exactly the kind of small dependency a test should catch before staff use the specification to price, purchase, or schedule work.

Give custom requests a useful boundary

Provide a route for 'Something else' where your business is willing to consider exceptions. Ask for the desired result, relevant measurements, and a reference if useful. Explain that staff will assess it rather than treating the request as an available option.

Keep custom work out of automatic totals until its pricing rules are defined. A zero-price placeholder can look like a free extra. Instead, show that the item is awaiting review and state whether the rest of the displayed amount is only a partial estimate.

A reviewer should be able to approve an allowed option, request clarification, or propose an alternative while preserving what the customer originally asked. Once a substitution is agreed, record the new selection and the approval, not just an internal note saying 'sorted by phone.'

Connect the choices to quoting without duplicating the catalog

First check whether your existing product-options or estimating tool can store the required selections. WooCommerce's Product Add-Ons documentation describes option features and notes that conditional logic needs another approach. Test the exact dependency you need instead of assuming every add-ons extension supports it.

The quoting reviewer needs the base selection, quantities, options, custom requests, unresolved checks, and configuration version in one readable record. If accepted details later move to a job or invoice system, pass identifiers as well as labels so similarly named options do not get confused.

We can scope quoting tools and configurators around that handoff. A better form may be enough. For more involved selections, agree the rules and review actions first, then decide whether pricing, a visual preview, or additional connections would help.

A few follow-up questions

Should optional extras be selected by default?

Make included items and paid additions unmistakable. For an optional addition, use a deliberate customer choice and a visible summary rather than relying on someone to notice and remove it.

What happens to a saved request when an option is discontinued?

Preserve what was originally selected. Flag the unavailable option for review and propose an alternative. Do not silently change the saved request to a different product or finish.

Can customers choose different options for each item?

Yes, if the flow distinguishes individual items or groups with identical specifications. A single order-level checkbox is insufficient when only one of several units should receive an extra.

Sources and further reading

Bring the options that keep creating follow-up

Show us your base products, common extras, and the combinations staff have to clarify. We can plan a clearer selection and quote handoff using your existing tools where they fit.

Discuss options and add-ons See what our quoting and configurators service includes
Website by TelosOps