Skip to main content
An earning rule defines when a member earns points or receives another configured result for something they did. Each earning rule combines a trigger, optional conditions, and one or more earnings.

Triggers

An earning rule reacts to one of three triggers:
  • Order paid: Triggered after an order is successfully paid and can calculate points proportionally to the order or item amounts.
  • Custom event: Triggered when a selected custom event is sent to Voucherify.
  • Segment entered: Triggered when a member enters a selected customer segment.

Conditions and earnings

Beyond the trigger itself, each earning can require that the member belongs to a specific loyalty tier, or that the triggering event meets additional criteria (for example, a minimum order amount). Each earning defines one or more effects. An effect adds a fixed or proportional number of points to a point wallet, or grants a benefit. One earning can include more than one effect, so the earning that runs can award points and grant a benefit together. A rule can hold several earnings. They are alternatives, not a stack. Voucherify checks them in the order they appear on the rule and applies the first one that passes. Every later earning is skipped, including earnings that would also have passed. Adding ten earnings does not grant ten rewards. An earning passes when its tier requirement is met and its conditions are met. An earning with no tier requirement and no conditions passes immediately. Placed first, that earning wins on every trigger, and the earnings below it never run. The earning that wins runs all of its effects. Processing does not stop after the first effect. If no earning passes, the rule applies nothing. This selection happens inside one earning rule. Other earning rules assigned to the program are evaluated separately, and each can apply its own winning earning. A points effect can override the card definition’s point expiration. The override type must be NO_EXPIRATION or the same type as that card definition.

Trigger limits

Trigger limits control how often a rule can fire for the same member: a cooldown between triggers, a frequency cap over a time window, or both. When omitted, a rule has no cooldown and no frequency limit, so it can fire every time its trigger occurs.

Earning limits

Earning limits cap how many points the rule can award. When omitted, the rule has no earning limit.

Lifecycle

An earning rule is created as DRAFT unless status is set to ACTIVE. INACTIVE cannot be set at creation. From there: Once a rule leaves DRAFT, its trigger cannot change. Name, earnings, the default error, validity hours, start and end dates, trigger limits, earning limits, and metadata can still change. Replacing the earnings also replaces their conditions and tier requirements. A rule that is still DRAFT can change its trigger. Deleting a rule sets status to DELETED and returns that rule. List and activity calls do not return a deleted rule. A rule can be deleted only when no program references it.

Assigning earning rules to a program

Earning rules are created independently of any program and connected through the Programs batch assignment endpoint. Unlike card definitions, earning rules can be assigned or unassigned while the program is ACTIVE, as long as the program keeps at least one active earning rule.
Last modified on November 18, 2026