Skip to main content

#Discounts0 discussing

We are looking to apply a % discount year over year without applying it one product line item at a time per year. For example, apply 10% discount in year 1, 5% in year 2 and none in year 3. So far we are only seeing product discount by the line level or whole contract discount on the shopping cart level. Anyone come across this before and have a possible workaround where the discount can be applied by segment year?

 

#CPQ #MDQ #MDQ Pricing #Discounts #Sales Cloud #Trailhead 

1 answer
0/9000

Hi all,

 

I'm currently building a system to allocate discount vouchers in Marketing Cloud using a CloudPages form.

 

The discount vouchers are generated externally by our ecommerce system, then uploaded into a Data Extension containing three values (CouponCode, isClaimed and EmailAddress). 

 

When users enter their details in the CloudPages form, they're entered into a Data Extension, and every hour I have a Journey running which checks for new entries and sends them a code from the codes Data Extension, using AmpScript to select a code, set "isClaimed" to "True" and to put the user's email into "EmailAddress". All so far, so functional.

 

My issue is that we only want codes to be valid for 12 months after a user has requested them, but also to remain in the Data Extension to ensure that a user cannot request multiple codes.

 

We plan to upload new codes every three months, valid for a total of 15 months (at the start, to ensure that whenever they're requested, there's always at least 12 months of usage left).

 

What is the easiest way to deal with this via email? There's a couple of ideas I've considered but don't seem viable:

 

  • Have each batch of codes stored in a new data extension with each one set to purge all data after 12 months via Data Retention settings
    • Not viable because it needs to retain the record of the original code to prevent a user from requesting another one
    • Also would lead to four data extensions each year which seems excessive
  • Include the expiry and upload date fields with the codes and use some sort of logic to purge the database of their records after 1 year, allowing the customer to request a new code
    • To my knowledge, you can't set data retention on a row-by-row basis
    • It may be possible to use some logic in the AmpScript for this but I'm unsure.

I can't be the only one who's faced a similar issue in the past, but to summarise we need a system where:

 

  1. Users can self-serve to request codes
    1. We use Journey filtering to ensure that only users with approved email format are able to receive the emails, as these coupons are ostensibly a closed system.
  2. Codes are uploaded in their own data extension after being externally generated
  3. Codes can only be requested by a user once per year

Thanks!

 

#Coupon Codes  #Discounts  #AMPscript  #Marketing Cloud

7 answers
  1. Sep 17, 2021, 2:45 PM

    Nice, yeah please do! Journey re-entry criteria is a good idea, as long as that journey is the only place a contact can claim a coupon code from. 

     

    You should absolutely be able to write some AMPscript to look up/claim rows based on the date column in your coupon DE, using some combination of LookupRows (or LookupOrderedRows) and UpdateDE.

     

    Have a good weekend!

0/9000

New video posted on Youtube Channel - Applying Default Pricing Rule to Price Book, Product, Price Book Entry Made Easy in Salesforce

Applying Default Pricing Rule to Price Book, Product, Price Book Entry Made Easy in Salesforce

0/9000

New blog posted on LinkedIn - Applying Default Pricing Rule to Price Book, Product, Price Book Entry Made Easy in Salesforce

Applying Default Pricing Rule to Price Book, Product, Price Book Entry Made Easy in Salesforce

0/9000

Hello! I have the following questions:

 

1) If I want to ensure that sales reps apply a discount for all opportunities from the same account, how would I achieve that? I'm thinking if I add a custom field to the standard price book with a formula that takes a % off, that would do the trick, but is this the right approach?

 

2) Why would two different values from picklists each throw a different error message? 

 

3) What is "default text" in the context of a standard object? I'm looking at the "Account" object. I've heard this term a few times but have not been able to find it. I see there's a "help settings" for the object itself and "help text" for the actual field. 

 

4) For IP access settings, if a user is within the org-wide trusted range but NOT within the range defined for their profile, are they not able to login or do they get the email with the verification code? 

 

5) If there's a restructure in a sales team and the sales manger isn't able to see the typical opportunity data they are used to seeing, what could be the reason?

 

Thank you for the help!

0/9000

Hi All,

We are seeing price discrepancies when we amend a discounted product and have a term that is not 12 months. I need a way to keep the net price consistent on amendments too. After a lot of research, looks like the root cause is the prorate multiplier.

One of the fixes was to create a price rule to update the default subscription term to be equal to the subscription term on the amendment .

I created a formula field Amendment Term = 

ROUND((SBQQ__Quote__r.SBQQ__EndDate__c - SBQQ__Quote__r.SBQQ__StartDate__c)/30,0)

Then using a price rule to insert the Amendment Term in the Default Subscription Term field and the price rule is working but the prorate multiplier is still not 1.

 

Attached screenshot

Thanks!

4 comments
  1. Aug 14, 2019, 8:51 PM

    Yes I have a few Custom Fields for this. I have some time tomorrow afternoon if you wish to connect.

    OH and before I forget...I could not have done this without some guidance from

    @Christopher Hickman!
0/9000