• Enhancements · OpenCart 3.x and 4.x

Loyalty program: bonuses that return the buyer

A loyalty program in an online store is a set of rules according to which the buyer receives a return benefit: points, accumulative discount, levels or cashback. We make it on OpenCart as a separate log of transactions, and not as a "balance" field in the client's card: the first thing the buyer asks is where the number came from, and the story should answer, not the manager in the chat. The term is 12–35 working days. We call the amount after a free analysis of the model, because it is not the code that is expensive here, but the percentage of the margin that you give for a long time.
See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Implementation period
12-35 working days from the approval of the rules
after a free audit
Price
30
Guarantee

days after project sign-off

12-35
Implementation period

working days from the approval of the rules

after free model analysis, it takes 2-4 working days
Cost
accrual percentage, write-off ceiling, burn-in period, exclusion
What we fix before development
54,302
Measured store with ready-made infrastructure

products and 635 categories, first response 413.8 ms

the share of accrued points that are actually written off
The main indicator after launch
payment by stages, warranty period of 30 calendar days
Conditions
Who it's for

Situations where this service delivers results

Scenario 1 of 4

The goods are bought cyclically

Cosmetics, feed, consumables, coffee. The buyer will return in a month anyway - the only question is, to you or to the neighbor. Points give you a reason not to look for an alternative: the accumulated points are visible in the cabinet and are linked to your store. In a short buying cycle, this mechanic pays for itself faster than others.

We'll review your situation in a free audit
What's included

Complete list of work and what you get as a result

  • Charges for the amount of the order, for the category, for the first order or for the action - the rules are changed by the manager in the admin, without a programmer
  • Debiting in the basket with a ceiling for a part of the check: you can see how many bonuses have been applied and how much is left on the balance
  • Exclusion from calculation - promotional items and categories with a minimum markup, so that the discount does not fall on the discount
  • Burning of points with a warning letter for the agreed deadline, not a silent reset
  • Levels or accumulative discount showing how much is left until the next threshold
  • Balance and history of transactions in the office: each line with date, order number and reason
  • Charges after order execution and withdrawal upon return — the program does not pay for canceled and unredeemed items
  • Identification of the buyer by phone or account, compilation of duplicates in the existing database
  • Notification by mail or in the messenger: it has been calculated, it will burn soon, a discount is available
  • Report in the admin: accrued, written off, average check in orders with bonuses versus normal
  • Page of the rules of the program in human language, with an example of calculation on a specific amount
  • Terms of work: payment by stages, warranty period of 30 calendar days after acceptance
When this service isn't right

What's not included — so there are no surprises at delivery

  • The decision of how much margin to give — we calculate the options, you choose
  • Integration with offline cash register and fiscal equipment — evaluated separately
  • The content of newsletters and the promotional offers themselves
  • Legal texts of program rules
  • Hosting, domain, acquiring

Free analysis of the loyalty model

Economic questions are answered before development, not technical ones. We help you deliver them and count them in your order statistics - before the first line of code appears.

What we measure

  • Buyer behavior nowHow many are returned, with what frequency, what is the average check in repeat orders. Without these figures, it is not known whether there is anything to increase.
  • Mechanics for your nichePoints, cumulative discount, levels or cashback. Different models work for cyclical demand and for rare expensive purchases.
  • The cost of the programHow much margin do you give with each mechanic. This counts before development: changing the percentage after launch is more difficult than it seems.
  • Communication with other channelsAre there newsletters, messengers, an offline point. It is wise to build the program on top of the existing infrastructure, not parallel to it.
  • Buyer identificationHow can you recognize it: registration, phone, login through an account. Without reliable identification, there is no one to count points.
  • What will measure successWhat indicators will you be looking at in three months? A program without pre-defined metrics turns into a permanent discount.

What you get

  • Calculation of the cost of the program according to various mechanics on your numbers.
  • A recommendation for a model with a justification as to why it fits your niche.
  • A list of indicators that will show in three months whether the program is paying off or not.
  • Conversation for 30–40 minutes on the document.

Timeline: 2-4 working days

Why is it free

Because the main risk here is not technical, but economic: the program is easy to launch and difficult to close. A few days of calculations save from handing out margin without a return.

What's next

After analysis - amount and term by stages, contract, account, act. If your numbers show that repeat purchases are almost non-existent and loyalty won't change anything, we'll say so.

Short form: your contact and site URL

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • European clients

    Among our work — projects for Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

What affects the price

Why two seemingly identical tasks are priced differently

  • MechanicsCumulative discount per customer group is setup and one checkout in the cart. Points with accrual, write-off ceiling, burn and levels - transaction log, task queue and a dozen rules, each of which is checked on return.
  • Combustion and notificationThese are background tasks: go through the balances every day, find those that burn, send an email, then write it off. Along with letters in the mailing service, there is a separate step, not a check mark in the settings.
  • The state of the customer baseIf orders are made without registration, and one phone number is recorded in three variants, duplicates are first made. Otherwise, the points are distributed among the clones of one buyer.
  • Offline and external systemsDebiting at the cash register, in the CRM or in the accounting system is already a two-way exchange with its synchronization schedule, and it is counted outside of site work.
Process steps

Transparent stages with approval at every step

Total duration:12–35 days

  1. Rules of the program and TK

    2-4 working days

    We fix the accrual percentage, write-off ceiling, burn-in period, exclusion and method of identification of the buyer. This is the document by which the work is accepted, and the only stage where it is still cheap to change the numbers.

  2. Data and charges

    3-6 working days

    Log of operations, linking to the order and the buyer, accrual after the order has been completed, withdrawal upon return. Each transaction has an idempotent key, so a repeated change of status will not count a second time.

  3. Checkout in the cart

    2-5 working days

    The field of application of points, the ceiling on the share of the check, recalculation when the composition of the basket is changed, behavior in the case of a partial return. We check on orders with a discount and paid delivery - that's where double accounting comes out.

  4. Levels, burning, notifications

    2-7 working days

    Thresholds of levels or accumulative discount, background task of burning, letters about accruals and warnings before writing off through the mailing service.

  5. Cabinet and reports

    2-7 working days

    Balance sheet, transaction history with a reason for each line, page of rules with an example of calculation. In the admin section, there is a report on accrued, debited and average checks in orders with bonuses.

  6. Scripting and transmission

    1-6 working days

    End-to-end scenarios: order with points, partial refund, cancellation, burn, re-invoke payment. Next, the admin session with the manager and written rules for support.

Did not find your case?

Describe how it works on your side — we will tell you whether “Loyalty program in the online store” fits and what it means in your situation. No brief and no call: one question, one answer.

Technologies & integrations

What we build on and what it connects to

Stack

  • OpenCart 3.x and 4.x — loyalty rules live as a separate module, the core cannot be patched
  • a separate table of transactions instead of the "balance" field - otherwise there is no history of where the figure comes from
  • idempotence key for operation: repeated change of order status will not count a second time
  • PHP and MySQL - points in the same database as the order: a transaction rollback takes both records
  • the queue of tasks for burning and letters — depends on cron hosting, accuracy to minutes, not to seconds
  • API of the mailing service - without consent to the mailing, the trigger will not work, this is a requirement of the law, not a precaution
  • GA4 events to order with bonuses — GA4 gives a trend, we sum up with the admin
  • WooCommerce is the same logic on hooks; out-of-the-box plugins usually don't hold partial returns

Integrations

  • eSputnik
  • SMTP
  • SMS gateway
  • Telegram
  • Viber
  • sign in with a Google account
  • KeyCRM
  • 1C / BAS
  • Google Tag Manager
  • GA4
Own program in the store versus an external loyalty service

How this option differs from the alternative

Where balances livein your database, next to orders
Calculation rulesany: per category, per first order, per action
Checkout in the cartrecalculation in the basket itself, the ceiling for a share of the check
Moneyone-time development and support upon the fact of changes
Offline pointa separate integration with the checkout is required
Reportingreport in the admin on accrued and debited
Cases

Tasks and results in numbers — all metrics measured by us

online store of tactical equipment with a catalog of more than 50,000 items

Task
Maintain an extremely large assortment in one store with detailed filtering and build an infrastructure for working with the customer base: mailings, customer recognition, checkout events.
Solution
Store on OpenCart 3, two language versions. Checkout includes LiqPay, online card, cash on delivery, cash on delivery, cashless settlement and online installments with a separate dataLayer event. Telephony, email service, login through Google account, tag manager and analytics are connected.
Result
54,302 products and 635 categories — confirmed by two independent methods: sitemap-index of 32 product files gives 110,096 addresses in two languages, cross-checking with standard search — 54,501–54,600 positions, discrepancy 0.4%. TTFB 413.8ms and full load 511.1ms with 421.5KB HTML. Nine types of structured data on the main. For the loyalty program, this means one thing: the notification channel and customer recognition are already in place, it is necessary to build accruals, not infrastructure. Defect found: hreflang declared as uk-UA and uk-RU with lang="ru" on the root version. Measured on 07/31/2026.
What we need from you

We can't start without this — best to prepare in advance

  1. Discharge of orders for the last year: repeat purchases, average check, frequency.
  2. The decision on the accrual percentage and the write-off ceiling — you name the numbers, we calculate the options.
  3. The point burn rule, if applicable, and the notice period before it.
  4. The text of the rules of the program from your side is legally your zone.
  5. Access to the site, database and mailing service.
  6. One person with the right to make decisions on the economy of the program.

If something is missing — let us know, we'll help you gather it or do it as a separate task.

FAQ

Most frequently asked questions — with concrete answers

Points or accumulative discount?

Depends on the purchase cycle. Points work where there is frequent shopping: the shopper sees the accumulation and comes back to spend it. The cumulative discount is simpler and better suited to rare large purchases — it does not require you to remember the balance. Volume pricing levels rather than bonuses are usually more logical for the band and dealers.

How not to give away the margin?

Calculate the cost of the program before launch and limit write-offs. Working fuses: points cover no more than the agreed share of the check, are not credited to promotional items and items with a minimum margin, burn out after a specified period. You need to lay them down immediately - it is easy to remove restrictions later, but adding them after launch is painful for buyers.

When to calculate points?

After the order is fulfilled, not after registration. Otherwise, points fly for orders that are canceled or not redeemed, and the program turns into a hole. It is also important to remove the accrued amount when returning the goods - this part of the logic is mentioned already after the first abuse, when you have to adjust the balances by hand.

How does the buyer know about the balance?

From the office and from notifications. In the office there is a balance and a history of operations, where each line has a date, order number and reason. Notifications include billing after ordering and warning before burning. Silent combustion spoils the attitude towards the store more than the absence of the program at all.

Do you need integration with newsletters?

Very desirable: it is letters that turn points into repeat sales. In the equipment store we measured, 54,000 items already have an email service, telephony and login through a Google account — it is smart to build the program on top of that. The limit of the mechanics is fair: without consent to mailing, the trigger has no right to work, and going through the frequency of letters gives unsubscribes.

How to understand that the program is working?

According to indicators determined before the launch: share of repeat orders, average check in orders with bonuses vs. regular, share of accrued points that are actually spent. The last indicator is the most interesting — if points are accrued, but not deducted, the program costs you obligations and does not bring returns. At the same time, numbers from GA4 are reduced to administration: analytics gives a trend, not accounting.

And won't it slow down the site on a large directory?

It doesn't have to, unless the balance is counted as the sum of the entire journal on each page. The same measured store for 54,302 products gives the first response in 413.8 ms - the load creates a catalog, not bonuses. Our recommendation: keep the current balance in a separate section and list it during the transaction, and show the full log only in the office, where one buyer enters, and not a search robot.

We have an offline point - will the points be shared?

Technically yes, the only question is how to write off in the hall. The cheapest option: the seller finds the buyer over the phone in the administration and writes off with his hands - works from the first day and does not require anything from the cash register. Direct communication with cash register software and fiscal equipment is counted separately, because there is a synchronization schedule, access rights, and a foreign exchange format.

How long does implementation take?

12-35 working days, these are six stages. Cumulative discount by customer group is the lower limit. Points with accrual, redemption cap, burn, tiers, notifications, and link to newsletters is top because there are many rules and each is tested against real scenarios, including returns and partial payments.

Send the export of orders for a year - we will calculate whether there is anyone to return.

In response: the share of repeat purchases on your data, the cost of the program by three mechanics and a recommendation by model. If there are almost no repeat orders, we will say so in the first email.

From measured cases54,302 products and 635 categories

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.