Use Cases

Give points for every order

Under Reward Points → Rules → New rule, set Rule Type to Order Behavior and Apply to For each Y€ spent, give X Points. Value (Y) is the spend amount, Value (X) the points awarded per that amount — e.g. Y = 10, X = 1 gives 1 point per 10 currency units spent. Points are credited once the order reaches one of the statuses configured in Approve earned points when (see Settings), and clawed back automatically if the order later moves to one of the Refund earned points when statuses.

Give a flat bonus for completing an order

Same rule type, but set Apply to Give X Points for Completing Order and only fill in Value (X) — every qualifying order earns a fixed amount regardless of its total.

Reward newsletter sign-ups, registrations, and other customer behaviors

Set Rule Type to Customer Behavior. Available actions are: newsletter subscription, birthday gift, account registration, X days of inactivity, and product review. Each still uses Value (X) for the points awarded; Value (Y) is unused for these actions. Customer-behavior rules fire from their respective events (e.g. sign-up) rather than from an order status change.

Customize point rules per product

On an order-behavior rule, enable Customized by Product. This exposes a Product Reward Points field that can be added to product entries — when a product with its own steps/points override is in the order, its per-product values are used instead of the rule's defaults for that line item.

Apply for shipping / Apply for payments (not yet functional)

An order-behavior rule's sidebar also has Apply for shipping and Apply for payments toggles, labeled in the CP as converting the shipping or payment method's price into points. In the current release these flags are saved but not read by the point calculation — enabling them has no effect on earned points. See Rules.

Restrict a rule to specific customers or a time window

On the rule's Restrictions tab, set From/To Date to limit a rule to a campaign period, and Customer Groups to restrict it to specific groups. Leaving customer groups empty makes the rule available to everyone.

Let customers redeem points at checkout

With Show on cart/checkout page enabled (see Settings), customers with a positive balance see a slider on the checkout sidebar showing their current balance and how many points they're about to spend, plus a Maximize my discount with points checkbox to redeem the maximum the order allows (bounded by Maximum spending points per order). The chosen amount is converted to a discount using Point value and applied when the order is placed; the spent points are deducted from the customer's balance at that point.

Build a loyalty tier program

Enable Loyalty Program in settings and configure the tier thresholds (defaults: Beginner 0, Bronze 500, Silver 2000, Gold 4000, VIP 8000 points). Customers move up tiers automatically as their balance crosses a threshold; turn on Automatically lower tier if a tier should also be lost when the balance drops back below it (e.g. after a large redemption).

Let customers review their points and history

Customers see their current balance and a link to Reward Points in their account navigation, and a full history page (rewardpoints/account/status) listing every earn/redeem entry with the date, the rule that triggered it, and the resulting balance. In the CP, the same balance is visible under a dedicated Reward Points tab on the customer's edit page, and the full history is under Reward Points → History.

Bulk-import existing point balances

When migrating from another loyalty system, use the rewardpoints/import/points console command to import balances by customer email — see Developer / API for the exact command and expected CSV/JSON columns.

See Rules for the full reference on rule types, actions, rounding, and restrictions, Settings for the fields referenced above, and Developer / API for the Twig variable, events, MCP tools, and console commands.