POS Coupon API
- 10 Mar 2025
- 2 Minutes to read
- Contributors
- Print
- DarkLight
- PDF
POS Coupon API
- Updated on 10 Mar 2025
- 2 Minutes to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Released 10th of March 2025
Support for mix match type 105 in PosCouponService (RTP-35414)
PosCouponService with the EG CouponService provider supports coupons with mix match type 105. Coupon offers created in Promotion Management and Coupon Management can be retrieved by POS through PosCouponService, allowing for weight-based coupon campaigns for members.
Released 26th of February 2025
Improved Coupon Handling for Multiple Memberships ((RTP-35878)
When multiple membership numbers are linked to a registered identity, POSCouponService sends all of them to CouponService. This ensures that POS retrieves all available coupons, providing more reliable coupon handling.
Released 16th of December 2024
New provider for POS Coupon Service, EG Coupon Service
When using EG Coupon Service as provider everything is handled by POSCouponService, CouponService and PromotionService.
Discounts are fetched by POS from POS CouponService (not POS Master).
More information about dataflow and setup / parameters in Confluence
POS Coupon Service in general:
Integration - POS Coupon Service - EG Retail Platform - Confluence EG A/S
Specific for EG Coupon Service provider:
Provider EGCouponService - EG Retail Platform - Confluence EG A/S
Commit coupons
If POS is not able to commit coupons. It will save transaction locally and retry the commit according to schedule in new parameter.
POS Configuration
New POS parameter:
OfflineCouponRedemptionJobSchedule - 0 0/20 * * * ?
If blank it is not active. Set to Cron schedule.
This only works if existing parameter IgnoreCouponCommitErrors is set to True.
Fetching Voyado Member Coupons and Bonus Checks in POS
POS can retrieve member coupons and bonus checks (reward vouchers) through the POSCouponService when using the Voyado member integration. This method supports multi-country setups, ensuring coupons and bonus checks are fetched from the correct Voyado endpoint for each country. Retailers can manage loyalty programs more flexibly across different countries or store groups.
POS Configuration
Important existing parameters:
PosCouponServiceUrl (default empty) - should be set to https://poscouponservice.egretail-test.cloud/ for TEST and https://poscouponservice.egretail.cloud/ for PROD.
CouponProvider (default value 'None') - should be set to 'PosCouponService'.
LoyalytProgramId (default value '0') - should be set to the corresponding value (0, 1 or 2) pointing for the correct config in TenantAdmin PosCouponService and PosCustomerService. In a multi country setup this number will be different for each country and should be carefully configured in TenantAdmin for the different services and routings.
CustomerMasterLocation (default value 'Internal') - should be set to 'Internal' if bonus checks / reward vouchers from Voyado will be used. This has no effect if only coupons are used.
Fetching coupons for H&ME members using SapCRMID ((RTP-32332)
POSCouponService fetch coupons for both H&ME members and T&ME member using SapCRMID. This ensures consistent behavior across multiple loyalty programs for both H&ME and T&ME members with the Hybris integration.
Redeeming Coupons for Members with SAPCrmId ((RTP-35517)
PosCouponService reformats coupon IDs and member IDs into a simplified format for communication between POS and PosCouponService. This ensures consistent handling of coupon redemption requests for both T&Me and H&Me members.
Was this article helpful?
