Connect Commercetools with Yotpo Loyalty to run points, rewards, referrals, and VIP tiers based on real order and customer account data, with clean redemption rules and tracking.
• Customer identities from commercetools (customer ID, email, and optional external IDs) are mapped to Yotpo Loyalty member records to keep accounts consistent across channels.
• Order and payment events are sent to Yotpo to drive points earning, VIP tier evaluation, and referral attribution, with event payloads carrying order totals, currency, discounts, and line items when available.
• Order status and return/refund updates are propagated so awarded points can be adjusted based on fulfillment, cancellations, and partial refunds, according to the program rules configured in Yotpo.
• Reward redemptions are exchanged as validation calls, where Yotpo returns eligibility and redemption outcomes, and commercetools applies the discount or benefit to the cart or order.
• Idempotency keys and delta-based processing are used to prevent duplicate point grants when the same commercetools event is replayed or retried.
• Sync jobs and webhooks are logged with correlation IDs, error responses, and retry states to support troubleshooting in production and during go-live.
.png)
We map Commercetools order events to Yotpo triggers, including paid, fulfilled, canceled, and refunded states. That keeps point awards and tier upgrades aligned with the order lifecycle.
Typically we sync customer identity, order totals, line items, discounts, and returns signals. This lets Yotpo calculate points, referrals, and reward eligibility on clean commerce data.
Yes, redemption can be validated server-side and applied as discounts or promotions in Commercetools. We make sure the same rules apply across web, mobile, and any custom checkout UI.
We listen for return and refund updates and adjust points and reward balances accordingly. This prevents over-rewarding and reduces “missing points” support cases.
Yes, we can scope rules by project, store, currency, or locale, and keep customer accounts consistent. It’s a common requirement in composable, multi-market setups.




