Why it is a separate MicroERP
A rewards/value service has its own users, decisions and reconciled output; it can serve many checkout systems through event/API adapters.
CRM & CustomersReviewed functional scope
Loyalty & Gift Cards MicroERP
Auditable reward or gift-value balance and redemption history
Who it helpsRetail loyalty / stored-value administrator
FROM A REAL REQUEST TO A USEFUL RESULT
The working flow.
Program enrolment, earn/issue event or redemption request
- 01
Configure approved programme
- 02
earn/issue balance
- 03
authorize redemption
- 04
reverse/expire/reconcile
- 05
resolve disputed balance
The useful outcome
Auditable reward or gift-value balance and redemption history
ALL FEATURES IN THEIR OWNING PRODUCT2 feature modules.
2 feature modules.
One product scope.
Open each module to review its purpose and actions. These features belong inside Loyalty & Gift Cards MicroERP.
01Gift Cards & Voucher Value3 scoped actions
Maintain stored gift value through sale and permitted redemption.
- Issue and activate cards
- Partial redemption balances
- Refund and lost-card controls
02Loyalty Points3 scoped actions
Maintain earned and redeemed retail benefit balances.
- Earn and redemption rules
- Expiry and reversals
- Duplicate-redemption protection
CLEAR OWNERSHIP. CONNECTED FUNCTIONS.
How the scope fits together.
Dependencies to plan
- Customer reference
- POS/order events
- Finance liability/reconciliation interface
Outside this scope
- Loyalty points and paid stored value must remain different ledgers/rules; no payment-provider operation is implied.
REUSE THE SAME PRODUCT
Mapped to your industry.
Industry compositions select relevant products and modules. Some options apply only under particular operating conditions; review the industry page before choosing.
Start with this scope.
Confirm your workflows, required integrations, team access, migration and acceptance checks in one implementation brief.