A Laravel loyalty script with the application included.

Name: Reward Loyalty
Brand: Reward Loyalty
Price: 349 USD
Availability: InStock
Author: NowSquare

Start with working member, staff, partner and administrator screens. Reward Loyalty includes the full Laravel source, loyalty modules, database migrations and APIs for a product you can host and extend.

Try the product demo License and pricing

Delivery: Complete application source
Interfaces: Member, staff, partner, admin
Current stack: Maintained in technical docs

Start with the complete application.

Reward Loyalty is a complete Laravel loyalty application with full source, database migrations and member, staff, partner and administrator interfaces. Its modules cover points, stamps, vouchers, prepaid passes, tiers, referrals and campaigns. Install it as its own application; use APIs or webhooks to connect other systems.

What the Laravel source includes.

Start with the working Reward Loyalty application: member accounts and wallet, staff transactions, partner program management and administrator controls. The source includes database migrations, modules and the interfaces behind those workflows.

Working loyalty modules

Points cards, stamps, vouchers and prepaid passes include configuration, member screens, staff actions and history. Tiers, referrals, predefined achievements and email campaigns support the program.

Browse the module guides

Business accounts and subscriptions

A partner represents a business. Plans set features and allowances; manual, Stripe and PayPal billing modes support a service for clients. The shared member identity keeps business activity separate.

Inspect the multi-tenant product

APIs and signed webhooks

REST and scoped Agent API credentials expose the documented operations. Outbound webhooks notify external systems. A POS integration still needs a supported connector or development against those interfaces.

Review the integration surfaces

A maintained application fork

Keep custom changes in version control and test updates on staging. Check the current framework, runtime and database requirements in the technical docs before choosing infrastructure.

Check the current technology stack

The included administrator interface manages partner plans and billing. Figures shown are demo data.

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

Decide where source-level work belongs.

Deployment, product configuration, integration, and code changes carry different costs and different update obligations.

Application or library

Choose Reward Loyalty when the shipped product is a useful base. Choose a package or custom domain layer when another application already owns every interface.

Extension boundary

Separate configuration, presentation changes, integrations, and deep domain changes before estimating work.

Update strategy

Keep custom work reviewable so framework, dependency, migration, and product releases remain deployable.

The source spans more than loyalty calculations.

The purchase includes working roles and workflows that a package would leave to the buyer.

Member experience

Accounts, wallet, cards, rewards, passes, vouchers, achievements, referrals, privacy, and communication preferences.

Counter experience

Staff search, scanning, points, stamps, rewards, vouchers, passes, corrections, and history.

Business operation

Programs, staff, customers, analytics, campaigns, pages, QR assets, permissions, and support.

Installation operation

Administration, plans, managers, health checks, integrations, APIs, webhooks, configuration, and updates.

Treat source access as a maintained fork.

A clean extension process keeps product updates usable.

1

Read current requirements and stack

Use the technical documentation for live versions and supported infrastructure.
2

Reproduce the workflow before changing it

Trace the role, route, data model, validation, ledger effect, permissions, and tests behind the requirement.
3

Prefer supported extension points

Use configuration, branding, APIs, webhooks, and modular boundaries before replacing core behavior.
4

Test release merges on staging

Run product and custom tests, review migrations, and verify built assets and role-based workflows.

Do not confuse source access with a small code sample.

Reward Loyalty is not a drop-in Laravel package for an existing application.
Source access does not make large feature changes small. Loyalty ledgers, permissions, multi-business scoping, communication, and UI states interact.
The current framework, runtime, database, and build versions can change. Use the maintained requirements and technology-stack pages.

Use current documentation for changing details.

Requirements, interfaces, settings, limits, and release behavior belong in the maintained product documentation.

Review the current technology stackUse the maintained source for framework, runtime, frontend, and dependency information. Review current server requirementsCheck supported runtimes, extensions, databases, SSL, and web-server needs. Plan updates around custom workUnderstand backups, source changes, release checks, and deployment. Review machine-to-machine integrationUse scoped APIs where an integration is a better fit than a core source change.