Skip to content
$349
Get it · $349 Try demo
Download

Multi-tenant loyalty software for separate client businesses.

Give each client its own programs, staff and business dashboard on one Reward Loyalty installation. Set its plan and fees. Customers use one member account, while each business keeps its own balances and activity.

Try the product demo License and pricing

Separate businesses, shared infrastructure.

Reward Loyalty is multi-tenant loyalty software for agencies and operators serving several businesses. Each partner manages its programs, staff, members and reports. The operator sets plans, permissions and billing on one installation. Members use one account across participating businesses, with separate program balances and business activity.

A franchisor can apply that boundary through the franchise rollout and governance model.

One install for your client businesses.

Add a café, a salon and a shop as separate partner accounts. Each business runs its programs and sees its own members and activity. The member can use one account across all three, with separate balances and rewards.

Business permissions and plans

Assign a plan to each partner and set its feature access and allowances. Partner overrides let the administrator grant or revoke supported features for a specific business.

Inspect the permission model

A shared member account

My cards holds programs from several businesses. The wallet keeps each program balance separate; it does not pool points across merchants.

See the account and data boundaries

Built-in partner billing

Use manual billing or connect Stripe or PayPal subscriptions. Configure monthly and annual plan prices, let eligible clients manage their subscriptions and review subscription health in Plans & billing.

Inspect the billing dashboard

An operator you appoint

Administrators run the installation. Managers work within their assigned scope. Partners and staff use business-scoped dashboards. Your team owns server capacity and shared service incidents.

Review the five roles
My cards brings programs into one member wallet while each card keeps its own balance.
My cards brings programs into one member wallet while each card keeps its own balance.

One license, unlimited client businesses

$349 once for one installation, including full source and 12 months of updates and product support. Keep running your last version if you skip the optional $99 yearly renewal. You pay for hosting and email delivery and maintain the installation.

Try the product demo Read the license terms

Price one installation and ten client relationships.

Multi-tenancy can spread fixed software and infrastructure costs. Client onboarding and support still grow with the service.

Use the ten-client agency cost scenario as a worked example, then replace every hosting, mail, monitoring, onboarding, maintenance, and labor input.

Read the agency operating model for shared client infrastructure before deciding who owns production, first-line support, client data, and service incidents.

Return to the deployment model behind a shared installation when vendor operation or a required integration matters more than multi-business control.

Before you start.

Tenant definition

Treat a partner as a business boundary, not as a casual label for each branch or department.

Operator responsibility

The installation owner controls shared configuration, plans, infrastructure, managers, and service health.

Member experience

One account reduces signup friction, while each business still presents and operates its own programs.

Separate shared services from partner ownership.

Platform operator

Owns the domain, platform identity, infrastructure, release process, plans, and cross-installation administration.

Partner

Owns its business settings, staff, programs, customers, activity, and reports within granted permissions.

Member

Uses one account and wallet, with program balances, passes, vouchers, and achievements shown per business.

Design the support and access model.

  1. Define onboarding

    Decide who creates a partner, which plan or permissions apply, and who verifies business settings.

  2. Set manager scope

    Grant only the administration needed for the portfolio or network the manager operates.

  3. Test partner isolation

    Use separate accounts to verify lists, exports, staff, programs, member relationships, and dashboard access.

  4. Plan shared incidents

    Mail, queues, scheduler, storage, or deployment problems can affect several businesses at once. Name the response owner.

Test the shared failure domain before adding clients.

Capacity

Measure queue load, mail volume, storage, database growth, backups, and restore time against the client mix the operator plans to sell.

Isolation

Test every role, export, API credential, manager scope, and support workflow with accounts from separate partner businesses.

Service ownership

Set maintenance windows, incident communication, escalation, and client exit steps before the shared platform becomes business-critical.

Limits.

  • Stripe and PayPal subscription billing require provider configuration. The operator still owns tax handling, client contracts, onboarding and first-line support.
  • The shared wallet does not merge partner balances or let one partner inspect another partner’s customers and activity.
  • One license covers one installation under the current license terms. Separate installations need separate licenses.

Documentation.

Review the shared-wallet architecture

Understand platform branding, partner isolation, member identity, and network use cases.

Review user roles

Map administrators, managers, partners, staff, and members to operating responsibilities.

Configure partner permissions

Control feature access and partner-level overrides.

Group related businesses

Use networks for administration without inventing cross-partner data access.