Rewards And Claims

Stores create claim tiers that customers redeem from the mobile app.

Reward Tiers

A tier defines how many points are required and what the customer receives. Tiers can be scoped for in-store use, online use, or global use.

Recommended tier fields:

• store
• title
• description
• points required
• claim channel
• active status

Use clear customer-facing names, such as “Free coffee” or “10% off next order”.

Claim Codes

When a customer claims a reward, Tapidu creates a short-lived claim code. Store staff can apply in-store claims from Checkout. WooCommerce can accept online Tapidu claim codes through the plugin.

Claim codes should use the TAPIDU- prefix so integrations can identify them without intercepting unrelated coupons.

Channel rules:

• In-store: apply from admin Checkout.
• Online: apply in WooCommerce checkout.
• Global: valid wherever the store allows.

Expiry And Refunds

Pending claims expire automatically. When a claim expires or is cancelled before it is applied, points are returned to the customer's account automatically. Expiring or cancelling a pending claim should never burn the customer's points.

The mobile app should show how long the claim remains active and allow cancellation while the claim is still pending.

Activity

Applied claims, cancelled claims, expired claims, refunds, and WooCommerce claim usage are visible in customer and admin activity.

Best Practices

• Keep the first reward easy to understand.
• Avoid creating too many overlapping tiers at launch.
• Use online-only rewards only when WooCommerce is connected and tested.
• Train staff to apply only in-store or global claim codes from Checkout.
• Review pending claims regularly during early store onboarding.