Table of Contents Introduction References Cashback Process Earning Redemption Return Feature Flag and Preferences Charging and Voiding Order Fulfillment Status Import Manual Execution Notification Handling Implementation Promotions Cashback Earning Promotion Cashback Redemption Promotion Storefront

Description Actual Behavior The cashback promotion code search is case sensitive. This means searching for e.g. 'Patricia' leads to results whereas searching for 'patricia' does not. This might be a problem for back office users who have to look up something and don't pay attention to capitalization

Description Description: A java.lang.IllegalAccessError occurs in In a patched class from <IS_LOCAL>/lib when calling a protected/default method from a class of the same package. Example: I want to patch the class com/intershop/sellside/pmc/internal/rendering/PipelineDictionaryProvider.java. In this

Description Problem: The ORM persistence manager locks the whole cache manager implementation in: com.intershop.beehive.orm.internal.common.PersistenceManagerImpl.createObject(ORMObjectKey, ClassDescription) com.intershop.beehive.orm.internal.common.PersistenceManagerImpl.getObjectByQueryResult(QueryResult)

Description Description: The Localization domain of a partner application is not deleted when the partner is deleted. Steps to repeat: login as admin to inSPIRED select "Reseller Channel" create a new partner PartnerSupport login as admin to PartnerSupport create a new sales channel PartnerSupportChannel

Description Description: The GetUserGroupsByCustomerSegments pipelet does throw an exception in case of an invalid live system USERGROUPASSIGNMENT table entry Steps to repeat: In case of special replication scenario steps: create promotion in editing system replicate to live assign promotion to users

Description REST call: post baskets/<basketId>/merges The baskets could not be merged. Authentication token contains syntactic errors. code: basket.merges.authentication_token_syntax_failure.error Further Investigations it seems the problem occur if the authentication token comtains the prefix 'encryption'

Description REST request: post basket/<basketId>/items Current behavior if you add a product to basket with a quantity that exceeds the maximum quantity per line item limit there are 2 info messages: "This product has limited inventory. We have adjusted the quantity to reflect the number of products

Description In basket REST request answers the client needs information of the lineItemId in the info section. Only the paths section is not convinient at all. Example: Maximum Quantity per Product in Cart will be exceeded by the following operations post: /basket/<basketId/items (Add a product with

Description Description: The GetUserGroupsByCustomerSegments pipelet does throw an exception in case of an invalid live system USERGROUPASSIGNMENT table entry Steps to repeat: In case of special replication scenario steps: create promotion in editing system replicate to live assign promotion to users