Developer guide · Application
A complete Laravel loyalty application, not a package.
You receive the maintained application source, its user interfaces, database model, modules, and deployment responsibilities.
- Delivery
- Complete application source
- Interfaces
- Member, staff, partner, admin
- Current stack
- Maintained in technical docs
Short answer
Start with the complete application.
Reward Loyalty is a complete Laravel application, not a Composer package. The license holder receives the application source, database migrations, modules, interfaces, APIs, and configuration needed to run the product. Standard Laravel knowledge helps with deployment and extension, while product changes still require domain analysis and regression testing.
Decision criteria
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.
Application scope
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.
Development workflow
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.
Product and operating limits
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.
Implementation guides
Use current documentation for changing details.
Requirements, interfaces, settings, limits, and release behavior belong in the maintained product documentation.