The loyalty program in Hummerce credits customers with points for placed orders and lets them pay with accumulated points on future purchases - with the customer's own loyalty card. Instead of (or alongside) its own program, a store can also connect to the nationwide Payback program, where the customer collects and redeems points outside the store as well.
Last updated: 2026-09-29.
¶ Benefits and use cases
- An incentive to come back - the customer sees points on their account and can use them on the next purchase, instead of looking for a one-off coupon.
- No manual work to credit points - points are calculated automatically from the order value (items, optionally delivery and payment).
- A loyalty card with a unique number - points can be collected even before the card is assigned to a specific customer.
- Paying with points as a separate payment method in the cart - the customer covers part or all of an order with points.
- Points only for paid orders (a configuration option) - no crediting for orders that were never completed.
- An alternative to building your own program from scratch - integration with Payback, a nationwide loyalty program.
- A rewards catalog as a separate store view - a separate assortment bought only with points.
- Points are credited when an order is placed: the sum of the cart items, optionally increased by delivery and payment cost.
- Points can be calculated from the gross or the net price.
- A points crediting operation has a status: queued (credited, not yet on the account), confirmed, approved (only now do the points land on the customer's balance), or canceled (the crediting is reversed).
- By default, points are approved only once the order is paid - the store can turn this off and approve points right when the order is placed.
- For an order split into several shipments, the store can recalculate points separately for each part.
- The card has a unique, automatically generated number (16 digits, using the Luhn algorithm used on payment cards).
- A customer can have more than one card. A card doesn't have to be assigned to a specific customer right away - points can be credited to a card and assigned to a customer later.
- A logged-in customer without a card gets one automatically the first time points are credited.
- Paying with points requires a logged-in customer with a loyalty card and a sufficient points balance.
- The store can restrict paying with points to a chosen store view - e.g. a separate "rewards catalog" view.
- After choosing to pay with points, the store checks the balance, deducts the points from the customer's account and marks the order as paid.
- A customer's profile in the panel has a Loyalty Program tab (can be disabled in configuration) with the points balance and the customer's card.
- Order details show the points credited for that order.
- Historical orders from before the program started can be topped up with points using a transfer tool in the panel (see Configuration details).
- Instead of (or alongside) its own points program, a store can connect to Payback - a nationwide, multi-store loyalty program, where the customer also collects and redeems points at other, independent stores and chains.
- The integration works as a payment method in the cart: the customer identifies themselves with a card or a Payback number, and the store passes the transaction to the Payback system to credit or redeem the customer's points.
- Payback requires a separate agreement with the program operator - it's an external program, not part of the Hummerce platform.
The loyalty program (own points) has been part of the Hummerce platform for a long time - the exact version it was introduced in isn't clear from the available sources. The Payback integration works as a separate, long-available payment module.
- Paying with points requires the loyalty program payment method configured on the store's list of payments.
- A rewards catalog as a separate view requires the Views module.
- Payback requires a separate agreement with the program operator and access credentials for its system.
- The loyalty card and points have no additional template requirements beyond a standard customer account.
- Requires implementation - neither variant is enabled by default. The scope of a store's own points program:
- enabling the module, setting the points formula (items, delivery, payment; gross or net) and the moment points are approved,
- configuring payment with points, including any restriction to a separate view (a rewards catalog),
- the customer tab in the panel and the place for the points balance and paying with points in the store template,
- a points transfer for orders from before the program started (optional),
- testing: crediting points, approval after payment, paying with points, canceling an order.
- Minimum estimated time:
- a store's own points program, without a rewards catalog - from 8 h,
- with a separate rewards catalog view - an additional 4 h,
- Payback integration - quoted once the scope is agreed with the program operator.
- The time for a specific implementation depends on its scope - we quote it individually.
- What the time depends on: the points formula, fitting the balance and points payment into the template, a rewards catalog as a separate view, transferring points for old orders, the store's version.
- The loyalty program has no operations of its own in the REST API or MCP - points and cards are managed only in the panel.
- By default, points and the card are visible in the admin panel - showing them to the customer on the storefront requires adapting the template.
- Payback is an external program - the store doesn't set its rules for crediting or redeeming points, it only passes the transaction to its system.
- We do not verify the configuration for legal compliance - the loyalty program's terms and the points crediting rules are set by the store.
- Loyalty program operations in the REST API and MCP (reading the balance, points history).
- A ready-made view of the points balance and operation history on the storefront customer account, with no template adaptation needed.
- Loyalty tiers (e.g. a higher points multiplier above a spending threshold).
- A separate, dedicated rewards catalog redeemable for points, independent of buying regular products with points in a view.
Can a customer pay for a whole order with points?
Yes, if the points balance covers the order - paying with points is a separate payment method in the cart.
Are points credited right after placing an order?
It depends on configuration. By default, points reach the customer's balance only after the order is paid - the store can change this and approve points right away.
Can Payback be connected instead of a store's own points program?
Yes. Payback is an external, nationwide loyalty program, available as a separate integration - it requires its own agreement with the operator.
How long does implementing a loyalty program take?
A store's own points program, without a rewards catalog - from 8 h. A rewards catalog as a separate view adds another 4 h.
Does the loyalty program have REST API or MCP operations?
No. Points, cards and the program are managed only in the panel.
Want to see how a loyalty program could work in your store? Contact the Hummerce team (in Polish).
- Program configuration: the Loyalty Program settings group - Tab in the customer's panel profile (turns the customer's tab on/off, on by default), Recalculate points (for split order results) (off by default).
- Customer profile: the Loyalty Program tab - the customer's card and points balance.
- Order details: a tab with the points credited for that order.
- Payments: the points payment method on the store's list of payments.
- Transfers: "Transfer points from past orders" - adds points for orders from before the program started, with an optional date range.
¶ REST API and MCP
The loyalty program has no operations of its own in the REST API or MCP.
The message shown when the loyalty module is disabled (e.g. when trying to pay with points) is changed in the message editor.
| Symbol |
Object |
Purpose |
_loyaltyProgramPoints |
order |
number of points credited for the order |
_loyaltyProgramOperation |
order |
link to the points crediting operation |
_loyaltyCard |
order |
the loyalty card used for the order |