Solution · Resellers
Resell a loyalty service without reselling the source.
The reseller buys and operates the licensed installation, then sells a service to client businesses. The client offer, support route, and data terms belong to the reseller.
- Buyer
- Specialist reseller
- Client purchase
- Managed service access
- Installation owner
- The reseller
Short answer
Sell the service around an installation you operate.
This model fits a specialist loyalty consultant or reseller that buys a commercial license, owns one installation, hosts and maintains it, and sells a managed service to client businesses. The reseller configures partner businesses or gives clients scoped control, trains their staff, provides first-line support, and defines the customer data relationship. The license permits operation and source modification for the licensed installation. It does not permit source redistribution or a sublicense of the application.
Decision criteria
Define the commercial and support boundary.
A reseller needs more than a branded screen. The offer needs a license-safe structure, a client contract, an operating team, and a clear customer-data model.
Offer design
Choose the client, outcome, onboarding scope, support hours, included configuration, change policy, and exit process before setting a service price.
Control split
State which settings the reseller controls, which settings each client controls, and who can see, export, correct, or delete customer records.
License fit
Sell access and operating work around the licensed installation. Keep application source, redistribution, separate production installs, and sublicensing inside the maintained terms.
Buyer fit
Choose this model when the reseller will operate the service.
The buyer needs delivery and support capacity, rather than a referral link and commission.
Fits a specialist loyalty operator
The reseller understands program economics, business onboarding, staff workflow, customer support, and the technical operation behind a branded service.
Fits a repeatable client offer
The target clients share a clear onboarding path, configuration range, support boundary, and commercial promise that the reseller can document and price.
Choose the agency path for broad project work
An agency that delivers loyalty as one part of wider client services should start with the agency Solution. This page owns the narrower resale and license decision.
Choose a vendor reseller program when operation is unwanted
A vendor-run referral or reseller scheme fits better when the buyer does not want to host software, maintain releases, support client staff, or handle service incidents.
Commercial model
Sell managed access and expertise, not application rights.
The reseller’s value comes from the service it operates around the product.
What the reseller buys
The reseller buys the current commercial license for its production installation and accepts the related hosting, maintenance, security, update, and license duties.
What the client buys
The client buys a managed service: onboarding, configured loyalty workflows, access for approved roles, training, first-line support, reporting, and agreed change work.
What remains restricted
The client does not receive a sublicense to the application source. The reseller must not publish, share, sell, or redistribute the source outside the maintained license terms.
How revenue works
The reseller sets service fees and scope in its own client contract. Complete cost includes the maintained software price, infrastructure, email, backups, monitoring, onboarding, support, account management, integration, and source-change maintenance.
Responsibility
Write the operator, client, and product roles into the service.
Brand ownership should never hide support ownership.
Reseller operator
Owns the installation, domain, platform brand, hosting, mail delivery, backups, security, updates, monitoring, incidents, client onboarding, and escalation to product support.
Client business
Owns its customer promise, reward economics, legal basis, business content, staff conduct, reward fulfilment, and the accuracy of information supplied for configuration.
Configuration and training
The contract states whether the reseller or client creates programs, imports customers, assigns staff, runs campaigns, reviews reports, and trains each new staff member.
Customer and staff support
The reseller provides first-line support to participating businesses and their staff under the service agreement. The client handles customer-facing reward and service questions unless the contract assigns that work elsewhere.
Implementation
Build one repeatable client launch before selling at scale.
The first launch should create the checklist, evidence, and support records for the next one.
-
1
Confirm license and data roles
Read the maintained terms, define the reseller-client service contract, map controller and processor roles, and set retention, export, deletion, security, and breach procedures.
-
2
Prepare the operator layer
Configure the installation identity, domain, email sender, legal and support routes, plans or permissions, backup and restore, monitoring, updates, and incident contacts.
-
3
Create the client blueprint
Collect business identity, locations, languages, currencies, program economics, staff roles, imports, integrations, training needs, reports, and approval owners in one brief.
-
4
Pilot onboarding and exit
Launch one client, test every role, record support demand, run an export, rehearse a client exit, and revise the offer before adding another client segment.
Day-to-day operation
Run a support chain clients can explain.
Each problem needs one first contact and one escalation path.
Client staff
Uses the assigned club and program workflow, records supported actions, fulfils rewards, and sends access or transaction exceptions to the client lead or reseller.
Client lead
Approves program changes, reviews staff use and reports, answers customer-policy questions, and requests configuration or data work through the reseller service route.
Reseller service team
Maintains client configuration, handles first-line support, monitors shared services, reviews incidents, trains new client teams, and communicates release or policy changes.
Product escalation
The reseller reproduces a maintained-application issue, checks current documentation, and contacts Reward Loyalty product support. Custom integrations, server work, and client operations stay with the reseller unless separately scoped.
Buying checklist
Inspect the parts the brand cannot answer.
A client should understand the service owner, data owner, and exit route before signing.
Branding scope
White-label relevance: Central to the buying decision. Map installation branding, each business profile and program, wallet presentation, public URLs, domain, email identity, and any source work needed for uncovered surfaces.
Customer data and client exit
State where customer data sits, who controls it, which subprocessors handle it, who answers access or deletion requests, what clients can export, and what happens at contract end.
Service and security
Inspect support hours, severity levels, backups, restore evidence, monitoring, updates, access review, staff turnover, incident notice, mail reputation, integration ownership, and business continuity.
License and growth
Confirm the permitted installation and modification model in the maintained terms. Price separate production installations, source changes, new markets, integrations, and support growth before promising them.
Product and operating limits
Keep service resale separate from source distribution.
- Reward Loyalty supplies software and product support within its maintained terms. It does not acquire reseller clients, write client contracts, host the reseller service, onboard businesses, train client staff, or answer the reseller’s end-customer questions.
- Branding controls do not remove every product identity or create a custom native app. Some surfaces can require source work, with testing and update costs owned by the reseller.
- The commercial license does not grant unrestricted resale, redistribution, publication, or sublicensing of the application source. Use the maintained terms for the exact rights.
- Partner isolation and permissions support a multi-client service, but the reseller must design billing, tax, plans, service levels, data roles, abuse handling, offboarding, and operational capacity.
Implementation guides
Use current documentation for changing details.
Requirements, interfaces, settings, limits, and release behavior belong in the maintained product documentation.