Skip to main content
A benefit is a value granted automatically to a member when an earning rule’s conditions are met. It can serve as an alternative to earning points on a loyalty card or it can be used alongside points. Members don’t redeem benefits themselves; they simply receive one once they fulfill the conditions of the earning rule that references it. Benefits are optional and are only useful once connected to at least one earning rule.

​
Benefit types

A benefit must define exactly one type-specific configuration object that matches its type:
  • points: A fixed number of points added to a card.
  • points_proportional: Points calculated proportionally to a triggering value, such as order amount.
  • material: A physical product or SKU.
  • digital: A discount coupon or gift card.

​
Stock

Like rewards, benefits can be limited in quantity through a stock configuration. When omitted, a benefit defaults to UNLIMITED stock, meaning it can be granted as many times as its earning rule is triggered.

​
Referenced resources

Depending on its type, a benefit references other resources: A card definition for points-based benefits, or a product/SKU/campaign for material and digital benefits. These references are validated on create and update; for example, a points-based benefit can only be activated if its connected card definition is itself ACTIVE.

​
Lifecycle

A benefit is created in DRAFT status by default, and only moves between DRAFT and ACTIVE through the activate and draft endpoints. There is no INACTIVE state. While in DRAFT, every property can be updated; once ACTIVE, only name and stock can still be changed. Two safeguards protect benefits that are already wired into your program:
  • A benefit that’s referenced by any earning rule can’t be deleted until that reference is removed.
  • A benefit connected to an active earning rule can’t be moved back to DRAFT.
Last modified on August 4, 2026