Customize Default SaaS Sub-Account Naming in Sparkforge
Agencies on the SaaS Configurator can pick whether new sub-accounts use Company Name or Customer Name + 's Account at creation. The setting applies to future signups only.
The SaaS Configurator includes a setting that controls how new SaaS sub-accounts are named when they are created during checkout. Pick Company Name to reflect the operating business, or keep the traditional Customer Name + 's Account format. Choice applies to future signups, not existing accounts.
What this setting does
It defines the default naming convention used when Sparkforge spins up a new SaaS sub-account at checkout. Agencies pick once, and every new signup follows the rule. Existing accounts are not renamed.
Where it lives: SaaS Configurator at the agency level. Available to agencies running SaaS Mode.
How to set it
- Open SaaS Configurator → Advanced Settings → Sub-Account Onboarding.
- Pick one option:
- Company Name (recommended for business-forward clarity)
- Customer Name + 's Account (useful if your team searches by buyer name)
- Click Save.
New SaaS sub-accounts created via Sparkforge funnels and supported external checkouts will follow the selection.
The two options
Company Name
Uses the business name provided at checkout. Example: Acme Dental.
Customer Name + 's Account
Uses the buyer's personal name with 's Account appended. Example: Jane Smith's Account.
Note: if Company Name is selected but the field is empty or missing during checkout, Sparkforge falls back to Customer Name + 's Account.
External checkouts
To extend the same behavior to checkouts outside Sparkforge funnels, pass the business name as companyName in the subscription metadata.
- Send a non-empty
companyNamevalue in subscription metadata. - Keep the SaaS Configurator on Use Company Name.
- If
companyNameis missing or empty, Sparkforge falls back to Customer Name + 's Account.
Example metadata payload:
{
"subscription": {
"metadata": {
"companyName": "Acme Dental"
}
}
}How company name is captured
Sparkforge captures the Company Name a customer enters at checkout and stores it in the subscription metadata as companyName. This applies to V2 funnels using the Payments ecosystem and SaaS V1 setups using Stripe.
Examples
- Company Name selected, business name provided → sub-account is
Acme Dental. - Company Name selected, no business name provided → falls back to
Jane Smith's Account. - Customer Name + 's Account selected →
Jane Smith's Account.
Admins can update the Location's Friendly Business Name later. Changing it after creation does not retroactively change confirmations or emails already sent.
Frequently Asked Questions
Does this affect existing SaaS accounts?
What if no Company Name is provided at checkout?
Can I change the default later?
How do I enable this for external checkouts?
Does the choice affect merge fields like {{location.name}}?
Was this article helpful?
Thanks for the feedback.