Customer Loyalty and Rewards Program

Most loyalty programs running alongside SAP Business One are not really connected to it. Points are calculated in a separate app or a spreadsheet, vouchers are honoured as ad-hoc manual discounts on the invoice, tiers exist as a colour-coded column somewhere in marketing, and nobody in finance can state what the outstanding points balance is worth. The program influences real revenue and creates a real obligation to customers, yet none of it is visible on the Business Partner master or in the general ledger.

That gap produces a familiar set of problems. A customer claims a balance the ERP cannot confirm, so the counter staff guess. A voucher gets redeemed twice because there is no single place that marks it consumed. A credit memo reverses the sale but not the points earned on it, so the balance drifts upward every month. Discounts given for tier status are keyed by hand, so the same customer is treated differently at two branches. And when the auditor asks how the loyalty liability was calculated, the answer is a spreadsheet that only one person maintains.

What ECOSIRE builds

We build the loyalty engine inside SAP Business One, anchored to the objects you already trust. Members are Business Partners. Earning events are posted A/R Invoices. Reversals are A/R Credit Memos. Redemptions are lines on real sales documents. The points ledger is a user-defined table where every row references the source document object type and entry, so any balance can be traced back to a document you can open in the SAP Business One client.

Program and earn rules

A loyalty program user-defined object holds the rule set: which item groups earn, which are excluded, whether freight and tax participate, the points-per-currency-unit rate, campaign date windows, and multipliers for specific item groups, Business Partner groups or price lists. Multiple programs can run in parallel — for example a retail scheme and a trade scheme — with precedence rules so a document only earns under one of them.

Members anchored to Business Partners

Each member record links to a Business Partner or, where you sell to organisations with many buyers, to a contact person. Card number, enrolment date, marketing consent flag, preferred channel and status are held as user-defined fields on the master data, so anyone with the customer record open can see the loyalty position without leaving the screen. Enrolment can happen in the SAP Business One client or through an API call from your storefront or point of sale.

The points ledger

Accrual happens when an A/R Invoice posts, calculated on net line amounts after discounts by default and adjustable by rule. The service polls or subscribes through the Service Layer, computes the points, and appends an immutable ledger row keyed to the invoice. Credit memos claw back exactly what the referenced invoice lines earned rather than a flat reversal, which is the difference between a balance that reconciles and one that does not. Adjustments are possible, but they are a distinct transaction type carrying a reason code, the user, a timestamp and the before and after balance — and they can be routed through a standard SAP Business One approval procedure.

Tiers

The tier engine evaluates spend or points over a rolling window you define, applies thresholds, and writes the resulting tier to a user-defined field on the Business Partner. That field can then drive Special Prices or discount groups so tier benefits are applied by SAP Business One pricing rather than by staff remembering. Upgrades and downgrades run as a scheduled job with a full movement history, so a customer can be told exactly when and why their tier changed.

Vouchers and redemption

Vouchers are issued with a unique code, a value or percentage, an expiry date, and a single-use or multi-use rule. Redemption applies the voucher to a Sales Order or A/R Invoice as a document line or discount, and marks the voucher consumed in the same transaction, which closes the double-redemption hole. Points redemption works the same way, converting points to value at a configured rate against the document.

Finance integration

Optionally, accrual posts a Journal Entry to a loyalty liability account and redemption reverses it, through the Service Layer journal entry endpoint and respecting posting periods. Expiry runs release breakage back to the profit and loss account. This is the part that turns a marketing scheme into something finance can sign off, and it is built to the account structure and posting policy your accountant specifies during scoping.

Channels and reporting

Authenticated, tenant-scoped REST endpoints let a point of sale, e-commerce storefront or mobile app look up a member, quote a balance, validate a voucher and redeem it. Crystal Reports layouts cover outstanding liability, redemption by outlet and period, tier movement, member statements and breakage.

Who this is for

Retailers and multi-branch traders running SAP Business One who want one balance rather than one per channel. B2B distributors running trade rebate or reward schemes against Business Partner groups. Franchise and dealer networks that need redemption controlled centrally while selling locally. Businesses whose finance team has been asked to quantify a loyalty liability and cannot.

How delivery works

This app is built to order. There is no instant download and no free trial.

1. Scoping call. We go through your earn rules, exclusions, tier thresholds, voucher policy, expiry policy, redemption channels and the accounting treatment you want. We look at how invoices and credit memos are actually posted today, because that determines where accrual hooks in. 2. Fixed quotation. You receive a written scope and a fixed price. Optional pieces — general-ledger posting, external channel APIs, member portal — are priced separately so you can choose what to include. 3. Build. Typical lead time is two to four weeks from acceptance, depending on how many earn rules and channels are in scope and whether the general-ledger integration is included. 4. Install in test. We install into your test company database with all user-defined field, table and object scripts, then replay a sample of your real invoices and credit memos so you can verify the balances the engine produces before anything is live. 5. Install in production. Production install and cutover are scheduled with your team, including any opening-balance load from your existing scheme. We verify the first live accruals and redemptions with you. 6. Support. A defect-fix window follows go-live, with an optional annual support and upgrade agreement afterwards.

After go-live

The add-on is delivered per tenant with source code and documentation handed over, and runs against SAP Business One 10.0 on Microsoft SQL Server or SAP HANA, on premise or cloud-hosted. Rules are configuration, not code, so changing a multiplier or a tier threshold does not require us. Because everything is anchored to standard documents, the loyalty history remains readable in SAP Business One regardless of what you do with the program later.