Claimable benefits in an eCommerce context follow the same Definition/Issue/Redeem pattern as in-store benefits, but the checkout integration requires additional steps to surface the benefit to the customer and capture the redemption at the point of purchase.Documentation Index
Fetch the complete documentation index at: https://docs.omneo.io/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The typical flow is:- Customer authenticates on your eCommerce platform (resolved to Omneo profile via identity)
- At checkout, your storefront queries available benefits for the profile
- Customer selects which benefit to apply
- Your checkout creates a redemption via the API
- Your checkout applies the discount to the cart (handled by your platform, not Omneo)
- On order completion, a transaction is created in Omneo with the
redemption_id
Step 1: Resolve the Omneo profile
Use the identity search endpoint to find the Omneo profile ID from your eCommerce platform’s customer ID:Step 2: Fetch available benefits
status: "active" benefits to show only currently redeemable benefits.
Step 3: Create a redemption
When the customer confirms benefit application at checkout:id in the checkout session.
Step 4: Apply the discount
Omneo records the redemption but does not apply discounts to your eCommerce cart directly. Your platform is responsible for applying the discount value. Retrieve the benefit definition’s discount type and value from the definition, and apply it via your platform’s discount mechanism (e.g., Shopify discount codes or draft orders, Salesforce Commerce Cloud price adjustments).Step 5: Record the transaction
When the order is fulfilled and payment confirmed, create the transaction with theredemption_id to complete the loop:
Shopify-specific: Checkout Rewards component
For Shopify specifically, Omneo provides a pre-built checkout component (shapes-shopify-checkout.js) that handles benefit and reward display at checkout. See Shopify Checkout Rewards for the full integration guide.
Content needed: benefit status enum values, handling redemption cancellation if customer abandons checkout, and multi-benefit checkout flow.