Skip to main content
Xoxoday Plum supports rules-based reward issuance by integrating with loyalty engines, POS systems, and CRM platforms to automatically trigger vouchers when business criteria—such as spend thresholds, fuel volumes, or visit frequency—are met.
Xoxoday Plum’s redemption marketplace is designed to work alongside your existing systems rather than replace them. When your loyalty engine, mobile app backend, POS system, or CRM detects that a qualifying business rule has been satisfied, it triggers reward issuance automatically through Xoxoday Plum’s secure APIs and workflows. The qualifying logic stays in your source system; Xoxoday Plum handles the fulfilment layer.

Event-Driven Triggers

The trigger model is entirely event-driven. Your source system—whether a fuel retail POS, a CRM such as Salesforce, or an HR platform such as SAP SuccessFactors—applies the qualifying logic and fires an event the moment the criteria is met. When a customer crosses a defined fuel volume threshold or completes three store visits within 30 days, the source system calls Xoxoday Plum’s issuance API and the reward or voucher is dispatched immediately. No manual intervention is required at the point of fulfilment.

Workflow Automation and Integrations

Xoxoday Plum supports pre-built automation patterns that connect common integration layers to the issuance workflow. You can configure “send reward” actions through workflow rules without building custom code from scratch. This makes it straightforward to wire Xoxoday Plum into an existing automation stack—for example, a Salesforce flow that monitors cumulative spend and routes the trigger through a configured workflow to issue a digital voucher the moment a threshold is crossed.

Governance and Campaign Controls

Every issuance configuration includes governance controls built for enterprise campaigns. Rewards can be set to issue automatically or held for admin approval before dispatch. Campaign managers can enforce start and end dates, set maximum reward counts per campaign, and define per-user caps—ensuring programme budgets remain in bounds even as trigger volumes scale. This is especially useful for fuel retail or FMCG loyalty programmes where thousands of qualifying events may occur simultaneously.

A Practical Example

Consider a petrol retail chain running a frequency-based loyalty programme. Their POS system tracks visit data and, upon the third visit in a 30-day window, pushes an event to Xoxoday Plum via API. Xoxoday Plum validates the request against the configured campaign rules, checks that the maximum reward count has not been reached, and issues a digital gift voucher directly to the customer’s registered mobile number—all without manual steps. The entire flow is auditable and governed by the campaign’s defined parameters. Learn more: Xoxoday Plum Help Centre — General

API-Based Reward Issuance

Learn how Xoxoday Plum’s issuance APIs accept event-driven triggers from external systems and deliver rewards programmatically at scale.

Campaign Governance and Reward Limits

Explore the controls available in Xoxoday Plum for setting campaign budgets, approval workflows, start/end dates, and per-user reward caps.