White Label Software Glossary

Access controls define who can access data, settings, and functionality within a software platform.

Explanation: Access controls determine what different users and roles can view, create, edit, delete, configure, or administer. In white-label software, robust access controls help isolate client accounts, separate tenant data, and give resellers fine-grained control over how customers, client administrators, staff members, and support teams use the platform.

Example:
A white-label analytics platform allows a reseller to assign administrator, manager, and viewer roles so each client's team members see only the data and functionality relevant to their responsibilities.

An admin console is the central management interface where administrators configure, monitor, and control a software platform.

Explanation: The admin console commonly provides tools for managing users, settings, integrations, billing, permissions, and system behaviour. In white-label software, resellers use it to configure branding, create client accounts, assign subscriptions, enable or disable features, and manage customer access.

Example:
A reseller uses an admin console to add a new client, assign user licences, upload the client's logo, configure billing, and activate the modules included in that customer's plan.

An agency is a business that uses a white-label platform to deliver services to multiple clients under its own brand.

Explanation: Agencies commonly need multi-client, sub-account, or tenant-management capabilities so they can manage many client accounts from one operating environment. They also benefit from client management, per-client configuration, branded reporting, custom domains, and the ability to tailor services for different customers.

Example:
A digital marketing agency manages 40 client accounts through one branded reporting platform, with each client seeing only its own campaigns, dashboards, and reports.

An analytics dashboard is a visual interface that displays key metrics, performance data, and insights in a consolidated, easy-to-read format.

Explanation: Dashboards bring together information from one or more sources through charts, graphs, tables, and summary indicators. In a white-label context, analytics dashboards can be branded and customised so resellers provide customers with reporting that looks and feels like their own proprietary solution.

Example:
A marketing agency gives clients access to a branded analytics dashboard showing website traffic, lead generation, advertising results, and campaign performance.

Analytics platforms are software systems that collect, process, analyse, and present data to generate insights and support decision-making.

Explanation: These platforms can combine information from websites, applications, CRMs, advertising channels, and other sources. White-label analytics platforms allow resellers to offer branded data, reporting, dashboards, and performance insights without building complex data infrastructure themselves.

Example:
A consultancy offers a performance-insights platform under its own brand, while the underlying reporting technology is supplied by a white-label analytics provider.

API access is the ability to access platform data or functionality programmatically through an application programming interface.

Explanation: APIs allow developers to connect a white-label platform with their own applications, systems, workflows, and data sources rather than relying solely on the platform's user interface. API access is particularly important for SaaS builders and solution integrators that need to automate account creation, retrieve data, trigger actions, or embed platform capabilities.

Example:
A solution integrator uses an API to create customer accounts automatically from its own application.

API integration is the process of connecting different software systems through application programming interfaces so they can exchange data and functionality.

Explanation: API integrations reduce manual work, eliminate duplicate data entry, and enable more seamless workflows. In white-label software, API integration allows resellers to connect a platform with client CRMs, ERPs, payment systems, marketing tools, and other applications so the solution fits naturally into the customer's technology stack.

Example:
A white-label reporting platform pulls data from a customer's CRM and email-marketing system through APIs to produce unified campaign reports.

The application layer is the part of a software system where user-facing features, business logic, workflows, and application services operate.

Explanation: In practical terms, the application layer is where users interact with a platform through its interface, functions, and processes. In white-label software, much of the visible branding, configuration, and customer experience occurs at the application layer without requiring changes to the provider's underlying infrastructure.

Example:
A reseller customises the navigation labels, terminology, and feature layout of a white-label client portal so the application feels native to its target industry.

Automated billing is the process of generating invoices and processing payments automatically according to predefined pricing rules and subscription terms.

Explanation: Automated billing systems can track usage, apply pricing plans, generate invoices, process recurring charges, and send payment notifications with minimal manual intervention. In white-label SaaS, this can allow resellers to offer branded subscriptions while the underlying platform manages recurring charges and invoicing.

Example:
A reseller offers a monthly subscription to its branded analytics platform, and the white-label system automatically bills clients each month and sends branded invoices.

Automated onboarding is the use of guided flows and automated steps to help new users set up and begin using a product without extensive manual support.

Explanation: Automated onboarding can include welcome tours, setup wizards, checklists, tooltips, default configurations, and instructional messages. In white-label software, onboarding can be configured to reflect the reseller's brand, messaging, service model, and intended customer journey.

Example:
When a new client signs up for a reseller's branded CRM, an automated flow guides them through importing contacts, connecting email accounts, and configuring sales pipelines.

Backend customization is the process of modifying server-side logic, data structures, integrations, automation rules, and other components that determine how a software platform processes and stores information.

Explanation: While frontend customization changes visible interface elements, backend customization affects how data is handled, workflows run, and external systems connect. In white-label platforms, it can help resellers support specialised industries, customer requirements, or operating processes while retaining the provider's shared core product.

Example:
A white-label platform allows a reseller to customise backend rules so leads from specific campaigns are automatically routed to the correct sales team and tagged with the appropriate metadata.

Backend dashboard branding is the ability to apply the buyer's branding to the administrative or management dashboard used by the buyer and its team.

Explanation: The backend dashboard differs from the customer-facing frontend. In a white-label operation, the buyer may want employees, account managers, and support staff to work within a branded environment rather than a provider-branded administration interface.

Example:
An agency's staff manage all client accounts through an administration dashboard carrying the agency's logo, colours, and visual identity.

Beta features are new or experimental functionalities released to a limited group of users for testing and feedback before a full public launch.

Explanation: Beta releases allow product teams to validate ideas, identify issues, and refine the user experience before broad deployment. In white-label software, resellers may receive early access so they can assess the feature, provide feedback, and plan how to position it under their own brand before making it available to clients.

Example:
A white-label SaaS provider invites selected resellers to test a new AI recommendations feature before making it available to all customers.

A brand is the distinctive identity, perception, and emotional connection associated with a company, product, or service.

Explanation: A brand includes more than logos and colours. It also includes reputation, voice, positioning, customer experience, and the values a business communicates. In white-label software, resellers apply their own brand to a provider's technology so customers perceive the platform as part of the reseller's own offering.

Example:
A marketing agency applies its logo, colour palette, language, and service identity to a white-labeled analytics dashboard so clients see it as part of the agency's core product.

Brand assets are the visual and verbal elements that represent a brand, such as logos, colours, typography, imagery, templates, and taglines.

Explanation: Brand assets are used consistently across customer touchpoints to build recognition and trust. In white-label software, they can be applied to the interface, login screens, email templates, PDFs, portals, reports, invoices, and other materials so the software appears to have been developed by the reseller.

Example:
A white-label customer portal uses the reseller's logo, primary colours, typography, and imagery to match the reseller's website and marketing materials.

Brand guidelines are documented rules that explain how a brand should be represented across channels, materials, and customer experiences.

Explanation: Brand guidelines commonly cover logo use, colour palettes, typography, tone of voice, imagery, layout, and accessibility requirements. In white-label implementations, they help ensure that interfaces, emails, documents, and customer communications remain consistent with the reseller's identity.

Example:
A reseller's brand guidelines specify how its logo should appear in the header of a white-labeled dashboard and which colours should be used for buttons, alerts, and navigation.

Brand identity is the collection of visual, verbal, and experiential elements that communicate how a brand looks, sounds, and feels.

Explanation: It includes logos, colours, typography, tone of voice, messaging, and the overall style of customer interactions. In a white-label context, the reseller's brand identity is applied to the provider's underlying technology so end users associate the experience with the reseller rather than the original platform provider.

Example:
A consulting firm applies its logo, colour scheme, messaging, and professional tone to a white-label reporting platform so the tool feels like an integral part of its service.

A brand kit is a curated collection of core brand assets and guidance packaged for easy implementation.

Explanation: A brand kit typically includes logo files, colour codes, font recommendations, imagery, templates, and usage rules. In white-label software, it is often used during initial setup to configure the platform interface, email templates, login experience, reports, and documents.

Example:
When onboarding a reseller, a white-label provider requests its brand kit and uses it to configure the dashboard theme, email templates, and branded login page.

A brand name is the distinctive name used to identify a company, product, or service in the market.

Explanation: A brand name plays a central role in recognition, recall, positioning, and customer trust. In white-label software, the reseller's brand name appears on the product, marketing materials, login screens, documents, and customer communications so customers associate the solution with the reseller instead of the provider.

Example:
A reseller markets a white-label CRM as “GrowthFlow CRM” rather than using the original platform provider's name.

Branded emails are transactional, notification, and system-generated emails that use the buyer's branding.

Explanation: White-label branding should extend beyond the application interface. Provider-branded emails can reveal the underlying vendor even when the platform itself is fully branded. Branded emails may use the buyer's logo, sender name, sender domain, colours, templates, and support details.

Example:
A customer receives a password-reset email containing the reseller's logo, sender address, domain, and visual identity rather than the provider's branding.

A branded frontend is the ability to present the customer-facing interface of software under the buyer's brand.

Explanation: It covers the primary experience customers use, rather than only an isolated login screen or dashboard. A branded frontend may include navigation, customer portals, interface styling, labels, workflows, help content, and visible product identity.

Example:
A company provides a customer portal where the complete frontend is presented as its own service, with no visible provider identity.

A branded login is the ability to apply the buyer's branding to login, registration, password-reset, and authentication screens.

Explanation: The login experience is commonly the first point at which a customer interacts with a platform. Provider branding at this stage can weaken the white-label experience and expose the underlying technology provider.

Example:
Customers access a branded login page displaying the reseller's logo, domain, colours, and visual identity.

A branded mobile application is the ability to provide software as a mobile app carrying the buyer's own branding.

Explanation: For platforms with mobile applications, the white-label experience may need to extend beyond the web platform. Brand control can include the app name, icon, splash screen, store listing, interface styling, notifications, and support identity.

Example:
A fitness business offers customers iOS and Android applications published under its own brand rather than the platform provider's name.

Branded reports and documents are reports, PDFs, exports, invoices, and other generated materials that display the buyer's branding.

Explanation: Generated documents are often shared externally and therefore shape customer perception of the product. Applying consistent branding allows a buyer to present platform outputs as part of its own service offering.

Example:
A consultancy generates client reports containing its own logo, colours, contact details, and visual style rather than the software provider's identity.

Bulk user import is the process of adding multiple users to a system at once, usually by uploading a file such as a CSV or Excel spreadsheet.

Explanation: This capability streamlines onboarding by allowing organisations to create and configure many user accounts in a single operation. In white-label platforms, it helps resellers set up client teams quickly, reduce administrative work, and accelerate deployment.

Example:
A reseller uploads a CSV file containing 250 employees and creates all user accounts in a white-labeled learning platform within minutes.

Client billing and invoicing is the ability to generate, manage, or automate invoices and charges for customers.

Explanation: This supports the operational side of running a white-label commercial offering. It can include invoice generation, recurring charges, payment tracking, branded invoices, tax handling, payment reminders, account records, and collections processes.

Example:
An agency automatically generates branded monthly invoices for each customer based on its selected platform plan and additional services.

Client management encompasses the processes and tools used to manage customer relationships, communications, services, projects, and performance.

Explanation: Effective client management helps organisations track interactions, deliver services, monitor account activity, provide support, and identify growth opportunities. White-label platforms often include client-management capabilities so resellers can manage multiple client accounts through a branded interface.

Example:
A white-label agency platform allows a reseller to manage client accounts, assign team members, track activity, monitor results, and provide support from one branded environment.

CNAME mapping is the process of using a DNS CNAME record to point a custom domain or subdomain to another domain.

Explanation: In white-label software, CNAME mapping is commonly used to connect a reseller's branded domain to the provider's platform infrastructure. It supports the buyer-facing capability of offering a custom domain without requiring the reseller to host the core application independently.

Example:
A reseller configures portal.agencyname.com as a CNAME pointing to the white-label provider's application domain.

Conditional logic is the ability to configure workflows or platform functionality to behave differently based on defined conditions.

Explanation: Conditional logic allows different customers, users, subscription plans, account types, data values, or events to follow different processes. It helps an operator deliver tailored experiences without creating separate software products.

Example:
Customers on a premium subscription are automatically routed to a different onboarding workflow from customers on a basic plan.

Configurable billing is the ability to define how customers are charged for a white-label offering.

Explanation: Configurable billing may include recurring subscriptions, plan-based pricing, per-user charges, usage-based charges, one-time fees, trials, discounts, taxes, and other commercial models. It gives the buyer more control over how the white-label platform is packaged and monetised.

Example:
A reseller charges customers a monthly platform fee based on their subscription plan and the number of active users.

Configurable notifications are the ability to control when and how customer notifications are triggered and delivered.

Explanation: Notification configuration allows a white-label operator to adapt communications to its own customer experience, branding, workflows, support model, and commercial processes. It can include email, in-app, SMS, push, or webhook notifications.

Example:
A reseller changes the notification triggered when a customer's subscription is upgraded and sends the message using its own branded email template.

Currency support is the ability to support or configure different currencies within a software platform.

Explanation: Currency support becomes important when a buyer serves customers across multiple markets. It can affect pricing, billing, invoices, payments, reporting, taxation, and how commercial information is presented to customers.

Example:
Customers in the Netherlands are billed in euros while customers in the United Kingdom are billed in pounds.

Custom components and pages are the ability to create or modify pages, interface components, dashboards, or other parts of the platform experience.

Explanation: This capability provides greater control over how customers interact with a white-label product. It can allow an operator to create client-specific dashboards, industry-specific pages, tailored navigation, custom self-service areas, or branded workflow screens.

Example:
An agency creates a custom client dashboard containing only the functions, metrics, and actions relevant to its service.

A custom domain is the ability to make a white-label platform accessible through the buyer's own domain or subdomain.

Explanation: A custom domain removes one of the clearest signs that the software is operated by another provider. It allows a buyer to present the platform through an address such as portal.company.com instead of a provider-owned address such as app.vendor.com.

Example:
Instead of accessing app.vendor.com, customers access the platform through portal.company.com.

Custom fields are additional data fields created beyond those provided by the platform by default.

Explanation: Custom fields allow a white-label operator to adapt the platform's data model to a particular market, service, workflow, or client requirement. They are particularly valuable when a general-purpose platform is being positioned as a specialised solution.

Example:
A property-management business adds fields for property ID, lease type, inspection date, and maintenance status.

Custom forms are forms that a buyer can create or modify to collect information from customers or users.

Explanation: Custom forms allow the operator to adapt data collection to its own service requirements, workflows, branding, onboarding process, and customer journey.

Example:
A consultant creates a branded onboarding form containing the specific information required from every new client.

Customer provisioning is the ability to create, configure, and onboard customer accounts efficiently.

Explanation: Provisioning becomes important when a white-label operator needs to create many customer environments rather than manually configuring each account. It can include account creation, default settings, branding, user invitations, plan assignment, domain setup, integrations, and onboarding communications.

Example:
A reseller creates a new customer account, applies a predefined configuration, assigns a subscription plan, and sends the customer branded login details.

Customer support is the assistance provided to users before, during, and after they use a product or service.

Explanation: Support can include documentation, live chat, email, phone assistance, training, troubleshooting, and success management. In white-label software, resellers commonly provide frontline support under their own brand, while the underlying provider handles deeper technical issues or product-level escalation.

Example:
When a user encounters an issue in a white-labeled CRM, they contact the reseller's support team rather than the original software provider.

To customise means to modify a product or service to better match specific requirements, preferences, branding, workflows, or customer needs.

Explanation: Customisation can involve changing appearance, adjusting settings, configuring features, creating workflows, adding fields, changing terminology, or modifying parts of the user experience. In white-label software, it helps resellers adapt a shared platform so it feels purpose-built for their audience or market.

Example:
A reseller customises navigation labels and dashboard widgets in a white-label platform to use industry-specific terminology that resonates with its clients.

Data encryption is the process of converting readable data into a coded form that can only be accessed or decrypted by authorised parties.

Explanation: Encryption protects data both at rest, when it is stored, and in transit, when it moves across networks. In white-label software, providers use encryption to protect data across reseller and customer environments, allowing resellers to offer a more secure platform under their own brand.

Example:
A white-label SaaS product encrypts database records and uses HTTPS for all connections to protect sensitive client information.

Data export is the process of extracting data from a system into a file or format that can be used elsewhere, such as CSV, Excel, PDF, or JSON.

Explanation: Export capabilities give organisations flexibility to analyse, archive, migrate, or share their data using other tools. In white-label software, data export allows resellers and their clients to download reports, backups, or raw data while remaining within the reseller's branded platform.

Example:
A white-label analytics platform allows users to export campaign performance data as CSV files for further analysis in business-intelligence tools.

Data import is the process of bringing external data into a system, often by uploading files or connecting data sources to populate records.

Explanation: Importing data helps organisations onboard new systems by migrating information from legacy tools, spreadsheets, databases, or other platforms. In white-label software, import tools allow resellers to help clients move contacts, products, transactions, and historical records into the branded solution.

Example:
A reseller helps a new client import thousands of customer records from a CSV file into a white-labeled CRM during onboarding.

Data mapping is the process of defining how fields and data elements from one system correspond to fields in another system.

Explanation: Proper data mapping ensures that information is transferred accurately and consistently during integrations, migrations, and imports. In white-label software, resellers can use data mapping to align the platform with each client's existing systems and data structures.

Example:
When integrating a white-labeled platform with a client's CRM, a reseller maps “Customer Email” in one system to “Primary Contact Email” in the other.

Data residency refers to the physical or geographic location where data is stored and processed.

Explanation: Countries and regions can have different legal, regulatory, performance, and customer-preference requirements for data location. White-label providers may offer regional hosting options so resellers can meet the needs of customers in specific jurisdictions or markets.

Example:
A reseller serving European clients selects EU-based data centres for its white-labeled SaaS offering to meet regional data-protection requirements.

A developer console is a dedicated interface or toolset that gives developers access to APIs, keys, documentation, configuration options, and technical resources for building integrations or extensions.

Explanation: A developer console can include API-key management, sandbox environments, webhook configuration, usage logs, error monitoring, and technical documentation. In white-label software, it allows resellers, SaaS builders, and solution integrators to extend the platform or connect it with other systems.

Example:
A reseller uses a platform's developer console to generate API keys and configure webhooks for a custom integration with its internal reporting system.

A favicon is the small browser icon associated with a website or web application.

Explanation: In white-label software, favicon customisation allows the buyer to replace the provider's browser icon with its own. Although small, the favicon is visible in browser tabs, bookmarks, browser history, and shortcuts, making it part of a consistent branded experience.

Example:
A white-label CRM displays the agency's favicon in the browser tab rather than the CRM provider's icon.

Feature entitlements are the ability to determine which functionality a customer receives based on its subscription, account type, contract, or configuration.

Explanation: Feature entitlements connect product functionality with customer plans and access rights. They allow operators to enforce commercial packages, limit access to premium capabilities, and provide specific functionality to individual clients without maintaining separate product versions.

Example:
Only Enterprise customers receive advanced analytics, automated reporting, API access, and priority support.

Feature packaging is the ability to group platform functionality into different customer packages or plans.

Explanation: Feature packaging allows an operator to create differentiated offerings rather than giving every customer access to the same functionality. It supports tiered products such as Basic, Professional, and Enterprise plans.

Example:
A reseller creates Basic, Professional, and Enterprise packages with different user limits, integrations, dashboards, and feature sets.

Language localisation is the ability to provide a white-label platform in different languages.

Explanation: Language support allows a buyer to operate the platform across different markets, regions, or customer groups. Strong localisation can cover interface text, system messages, emails, notifications, forms, help content, and generated documents.

Example:
A European reseller provides its platform in English, Dutch, French, and German.

Measurement-unit configuration is the ability to configure measurement units according to a customer's market or preference.

Explanation: This capability is relevant where measurements form part of the product experience, including logistics, property, health, manufacturing, engineering, energy, agriculture, or fleet-management software.

Example:
A fleet-management platform allows customers to use kilometres and litres rather than miles and gallons.

Multi-client and sub-account capability is the ability to manage multiple customer accounts, organisations, or sub-accounts from one white-label platform.

Explanation: This allows one operator to use a single platform to serve multiple customers without creating entirely separate software environments. Each client should access only its own users, data, configurations, workflows, and relevant functionality.

Example:
An agency manages 40 client accounts from one administration environment, with each client accessing only its own data, dashboards, and reports.

Multi-tenant management is the ability to operate multiple logically separated customer environments within the same platform.

Explanation: Multi-tenancy provides the operational structure for serving multiple organisations while keeping their users, data, settings, permissions, and configurations distinct. Multi-tenant management gives the operator tools to create, configure, monitor, and administer those separate customer environments.

Example:
An agency operates one white-label platform containing separate, secure environments for hundreds of clients.

Native integrations are pre-built connections between a white-label platform and other software, services, or data sources.

Explanation: Native integrations reduce the technical work needed to connect the platform to a customer's existing technology stack. They can make a white-label solution quicker to deploy and more useful within established business processes.

Example:
An agency connects a white-label platform directly to a customer's CRM, email-marketing system, accounting platform, and analytics tools.

A no-code and low-code builder is a visual tool that allows users to create or substantially modify parts of software without traditional software development.

Explanation: A builder provides greater flexibility than standard configuration settings because the buyer can construct or modify pages, interfaces, workflows, applications, or components. Low-code tools may also allow developers to add custom logic when visual configuration is insufficient.

Example:
An agency uses a visual builder to create a customised client portal for each customer without developing every portal from scratch.

No-code configuration is the ability to configure significant aspects of a white-label platform without writing code.

Explanation: No-code configuration allows non-technical users to adapt functionality, customer experiences, workflows, fields, notifications, and settings directly through the platform. It is particularly valuable for no-code entrepreneurs, agencies, and operational teams that need to launch or modify an offering quickly.

Example:
A solo entrepreneur changes customer fields, notifications, and workflows through a platform's configuration interface without using a developer.

A no-code entrepreneur is a non-technical founder or operator who uses a platform to launch a branded product quickly without writing code.

Explanation: No-code entrepreneurs generally have limited technical resources and prioritise speed, simplicity, and an out-of-the-box experience over deep technical control. They benefit from platforms that support branding, customer onboarding, configuration, and basic commercial setup through visual settings.

Example:
A solo founder launches a branded membership portal by configuring an existing white-label platform, adding a logo and custom domain, and selling subscriptions without hiring developers.

Payment gateway integration is the ability to connect a platform to payment providers so customers can make or process payments.

Explanation: Payment integration can allow the white-label operator to manage customer transactions as part of its own offering. It may support subscription payments, one-time purchases, invoices, saved payment methods, refunds, payment-status updates, and recurring billing.

Example:
A SaaS operator connects its branded platform to a payment gateway so customers can subscribe and pay directly through the platform.

Per-client branding is the ability to apply different branding configurations to individual customers, accounts, or sub-accounts.

Explanation: This capability is particularly important when one operator serves multiple organisations that each require their own branded environment. Per-client branding can include separate logos, colours, email templates, domains, dashboards, reports, and documents.

Example:
An agency operates one platform but gives Client A a blue-branded portal and Client B a separate logo, colour scheme, email identity, and custom domain.

Per-client configuration is the ability to configure platform functionality differently for individual customers or accounts.

Explanation: Different customers can require different settings, workflows, integrations, fields, notifications, data structures, or available functionality. Per-client configuration lets an operator tailor a shared platform without maintaining separate product versions.

Example:
A managed service provider gives one customer a basic platform configuration while enabling additional modules and integrations for another customer.

Per-client feature visibility is the ability to control which features or functionality are visible to individual customers.

Explanation: This allows an operator to tailor customer experiences without necessarily creating separate software versions. It can support commercial plans, customer-specific requirements, staged feature rollouts, and simplified user experiences.

Example:
A reseller enables reporting features for premium customers while hiding those features from customers on a basic plan.

Provider branding removal is the ability to remove visible references to the underlying software provider from the customer experience.

Explanation: Adding a buyer's logo does not necessarily make software fully white label if the provider's name, links, logos, “Powered by” notices, help-centre branding, or other identifiers remain visible. Provider branding removal is a key test of whether an offering is fully white-label or partly co-branded.

Example:
A reseller removes vendor logos, provider links, “Powered by” text, and other provider references from the customer-facing application.

Regional date and number formats are the ability to adapt date, time, decimal, and number formatting to different markets.

Explanation: Regional formatting makes a platform more understandable and appropriate for customers operating in different countries. It can affect dates, times, currencies, decimals, separators, addresses, reports, and other customer-facing information.

Example:
The platform displays dates and decimal formats according to each customer's selected region.

Regional payment methods are the ability to support payment methods that are relevant to specific geographic markets.

Explanation: Local payment options can be important when a white-label operator serves customers internationally. Relevant methods vary by country and can include bank transfers, direct debit, local wallets, regional card schemes, and other locally preferred payment options.

Example:
A European platform supports SEPA payments alongside debit and credit card payments.

A reseller is a business that sells a software platform to customers under its own business or brand.

Explanation: Resellers need the ability to package, price, market, and sell software as their own offering. They commonly require branding controls, customer-account management, subscription configuration, billing support, customer provisioning, and separate client environments where needed.

Example:
A managed service provider sells a branded customer-support portal as part of its monthly IT service package while the underlying platform is operated by a third-party provider.

Roles and permissions are the ability to define different access rights for administrators, staff, customers, and other users.

Explanation: White-label platforms serving multiple customers must control who can view, edit, manage, export, configure, or administer information and functionality. Roles and permissions help protect client data while allowing resellers to retain platform-wide administrative and support access.

Example:
A customer administrator can manage users within its own account while the reseller retains access to platform-wide administration and support tools.

A SaaS builder is a business or product team that uses a platform as the foundation for its own software product.

Explanation: SaaS builders usually need deeper customisation, integration, commercial, and product-development capabilities than a standard reseller. They may rely on APIs, SDKs, embedded components, custom workflows, feature packaging, billing controls, and per-client configuration to create an experience that is substantially their own.

Example:
A startup builds an industry-specific compliance platform on top of a white-label workflow system, adds custom fields and integrations, and sells it as a specialised SaaS product.

A software development kit, or SDK, is a provider-supplied collection of tools, libraries, components, and documentation that helps developers build integrations or applications around a platform.

Explanation: An SDK can provide a more structured development experience than API access alone. It may include reusable components, authentication tools, client libraries, code samples, testing utilities, integration documentation, and development environments.

Example:
A developer uses a provider's SDK to integrate platform functionality into a proprietary application.

A solution integrator is a technical operator that integrates or embeds software functionality directly into its own product, application, or infrastructure.

Explanation: Solution integrators need a high degree of technical control and strong integration capabilities. They may require APIs, SDKs, webhooks, embedded components, developer tools, or access to underlying code so the provider's functionality can feel native to the integrator's own environment.

Example:
A software company uses a provider's API and SDK to embed document-signing functionality directly into its own customer portal.

Subscription configuration is the ability to create and configure different subscription plans for customers.

Explanation: Subscription controls allow a buyer to structure recurring commercial offerings around a platform. They can include billing cycles, plan levels, trials, upgrades, downgrades, user limits, included functionality, and subscription-based access rights.

Example:
A SaaS business offers monthly and annual subscriptions with different features, user limits, pricing, and support levels.

Time-zone support is the ability to configure or recognise different customer, account, or user time zones.

Explanation: Time zones affect scheduling, notifications, reporting, activity logs, automations, appointments, deadlines, and other time-sensitive functionality. Proper time-zone handling is important for white-label operators serving international customers.

Example:
An international platform displays appointment times and automated notifications according to each customer's local time zone.

UI brand configuration is the ability to apply a consistent brand identity across a platform interface, including colours, typography, buttons, icons, navigation, and other visual styling.

Explanation: A genuinely branded experience goes beyond inserting a logo. UI brand configuration allows a buyer to apply elements from its brand guidelines throughout the customer-facing interface so the software aligns with its website, marketing materials, and service identity.

Example:
A reseller applies its brand kit to a platform so customers see its colours, typography, buttons, and interface styling rather than the vendor's default design.

Usage-based monetisation is the ability to charge customers according to their consumption or usage of a platform.

Explanation: Usage-based pricing provides an alternative to fixed subscription charges. Usage can be measured through transactions, messages, API calls, storage, active users, documents processed, reports generated, or another product-specific unit.

Example:
A white-label communications platform charges customers according to the number of messages they send each month.

Webhooks are user-defined HTTP callbacks that send real-time data from one system to another when specific events occur.

Explanation: When an event is triggered, such as a new user signup, completed payment, status change, or created customer account, the platform sends structured information to a designated URL. In white-label platforms, webhooks help resellers and solution integrators connect the product to their own systems or their clients' tools.

Example:
A white-label SaaS platform sends a webhook to a reseller's system when a new client account is created, triggering welcome emails and account-setup workflows.

White label refers to a product or service created by one company and rebranded for resale by another as if it were their own.

Explanation: White-label offerings are built to be generic and rebrandable so multiple resellers can customise and market them under distinct identities. This arrangement lets resellers expand their portfolios quickly without investing heavily in product development. In software, the provider operates the core technology while resellers focus on branding, packaging, pricing, support, and customer relationships.

Example:
A social media agency resells a white-labeled analytics dashboard under its own name, presenting it to clients as an in-house reporting tool.

White-label software is a software solution developed by one company that can be rebranded, customised, and sold by other companies under their own brand.

Explanation: Instead of building software from scratch, resellers license a ready-made platform that they can brand and configure for their customers. This shortens time to market, reduces development costs, and allows businesses to focus on sales, marketing, client success, and commercial growth. White-label software commonly includes branding tools, configuration options, multi-client capabilities, and integration options.

Example:
A digital agency offers its own marketing automation suite by reselling a white-label software platform that it has fully branded and configured for its client base.

Workflow configuration is the ability to create or modify automated processes within a platform.

Explanation: Workflow configuration allows the buyer to adapt how a platform behaves around different customer processes, including onboarding, task creation, routing, approvals, notifications, follow-up activities, data updates, and service delivery.

Example:
When a customer submits a form, the platform automatically creates a task, sends an email, assigns an owner, and updates the customer's account.