Service

V2 Add On

Ali Shaown

1. Overview

Service Add-Ons let agencies offer optional, billable add-ons linked to main services.

Order Form Builder enables custom drag-and-drop forms for collecting client info, add-on selections, upsells, and e-signatures.

2. Service Add-Ons

Key Features

Add-ons are created separately and linked to one or more main services.

Each add-on has(update):

Independent pricing: subscription (hourly/daily/monthly/yearly) or one-time

Rules

Add-ons must be purchased with their parent service.

Add-ons now support independent billing cycles.

Mixed pricing allowed:

One-time services can have subscription add-ons

Subscription services can have one-time add-ons

Order Behavior

Add-ons show with pricing in the same order as the parent service.

All add-ons appear on the initial invoice, regardless of billing type.

⁠

3. Order Form Builder (Link:
`Order Form`⁠
)

Components (details in order form)

Add-ons (linked to selected service)

for one time service

one time add on with same currency can be added

for subscription add on once a subscription add on is selected only add ons with the same billing cycle can be added

For subscription services

one time add on with same currency can be added

add ons with subscriptions will need to be with same billing cycle

Upsells (optional extra services)

upsells can now be either one time or subscription (similar to add ons)

Purchase Flow

One main order + separate backend orders for upsells.

upsell invoice will be separate.

Later invoices for recurring services

Client sees total combined cost clearly (e.g., $15 + $5 + $30 = $50)

client purchases a service with one time and a subscription/subscriptions add on

order will be created and a subscription will be created

from the next billing cycle only add on price will be changed

subscription purchase with multiple/single subscription add on

only one subscription will be created

based on the number of billing cycle subscription will continue

if add on/service billing cycle ends before subscription ends adjust pricing accordingly

Acceptance Criteria: Service Add-Ons

Add-On Creation

Users can create an add-on with name, description, pricing type (subscription/one-time), and currency.

Add-ons can be linked to one or more existing services.

Add-ons can be published/unpublished via a toggle.

Pricing & Billing Logic

Add-ons support both one-time and subscription pricing models.

Each subscription add-on has its own independent billing cycle.

The system allows one-time services to include subscription add-ons.

The system allows subscription services to include one-time add-ons.

Order Integration

Add-ons can only be selected when the parent service is added to the order.

Add-ons and their pricing are clearly shown in the order summary alongside the parent service.

All add-ons appear in the initial invoice, regardless of pricing model.

For subscription add-ons, only the add-on amount is charged in future billing cycles (not the main service).

Acceptance Criteria: Order Form Builder

Form Creation & Targeting

Agencies can create order forms using a drag-and-drop interface.

Forms can be assigned to a single service or multiple selected services.

Form Components

Agencies can add client info fields: Name, Email, Phone, Address, Company.

Forms support linking add-ons tied to the selected service.

Agencies can configure upsells (additional service offers) in the form.

Purchase Flow Logic

When a client submits an order form, a main order is created for the primary service.

If upsells are selected, separate backend orders are generated.

The client’s initial invoice shows the full combined amount (main + add-ons).

Upsells appear in a separate invoice.

Recurring invoices (e.g., for subscription add-ons) are created correctly from the next billing cycle onward.

If the main service is one-time and the add-on is subscription-based, only the add-on recurs in future cycles.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.