Order-Level Content → Menu → Legacy Offers → Offer
Overview
What are Legacy Offers?
These are offers that are not managed through the loyalty engine. A market will use them when they do not have loyalty available or want offers that are not only for loyalty members.
Offers are what we use for coupons and discounts. They typically have their own PLUs in their respective POS map.
Setting them up
Document Validations
Name
This is the name of the offer that will show in the platform, so must be edited according to your marketing guidelines.
Internal Name
The name that will be displayed in Sanity - it will help you quickly identify and organize your offers.
Localized Image
This is the image that is shown for the offer.
Best Practices Tip
The image of the offer plays a critical role in conveying the guest with the needed information in a fast and efficient way. Offers will likely perform better when some features are present:
Price - undoubtedly the most important, having the price within the image, always placed in the same part of the image, is highly recommended, as it will provide guests with the fast indication of the coupon price.
Short code - specially important if not all your restaurants are equipped with a reader, placing the coupon short code in the image will allow for a faster interaction between guests and restaurant operators.
Product - image of the product(s) redeemable with the offer.
Choosing a picture without a background will likely look better, remove noise, and turn the guests' focus to the actual purchase 🍔 🍟
Note that you can edit the background in the field Background Image.
Image Description
This will be the text for the alt attribute on the image.
Description
This is the description for the offer in the offers page and once clicked on.
Add Tags
This section is to add tags to your offer created in the tags section to be able to send these attributes to mParticle (and consequently Amplitude, Braze, or other connected tools, to create your cohorts more efficiently).
Tags Example:
1$ off coupon
Beef Coupon
More Info
In some cases we want the offer to have its own disclaimer as it might be a particular one. Offers by default tend to display the disclaimer set in Feature Disclaimers (Feature-> Feature Disclaimers → Offer disclaimer).
However, if this field “More Info” within the offer document is filled out it will overwrite the default disclaimer by the one set up in More Info.
How To Redeem
The explanation to guests of how to redeem the offer.
Option
This is the benefit of the offer, eg the combo or item you will receive for redeeming the offer. This piece is key for the offer to work. Please follow the following guidelines.
Always create a combo for the offer benefit, no matter if it is just a discounted item like Whopper for 1€ or a special promo like 3,99€ Whopper Meal.
Why not create just an item?
Because creating a new item would require you to update MDS, which would make the process unnecessarily longer and more complicated.
Creating combos allows you and your team to move fast 🚀
To understand in detail how to create a combo, please refer to the Combo documentation. Followingly, we provide some notes about creating a Combo offer.
Name
Unlike the rest of the combos, this combo will not be displayed to the guest as a combo, since it is being created only to link a PLU to an offer. What does this mean? Guests will never find the offers in the combo format below, and this name is thus not relevant but must be filled.
Main Item
Important distinction below!
If your offer is composed of 1 Item
Example: 1€ WHOPPER®
The main Item will correspond to your item only.
If your offer is composed of anything else than just 1 Item
Example: 6€ for 2 WHOPPER® or Big King Meals
The main Item will always be the same and correspond to a dummy item created for the purpose of tricking the system into injecting the correct values.
Best practice tip
Create an item called Combo Item or Offer Combo Item, and set all its Vendor Configs to Ignore.
Always use this item as your Main Item for Offers that are anything but 1 item only.
Options
If your offer is composed of 1 Item, there are no Options.
For any other case, you must create a combo slot for your guest’s different options. Let’s see some examples below:
For the offer “3.99€ WHOPPER® Meal”, we will have 3 additional combo slots:
“Offer – Whopper”, a combo slot with a Whopper (item), as the only pre-selected option
Medium Combo Drinks, a combo slot with the drinks you wish to include as an option for this offer
Regular Fries, a combo slot with Fries (item), as the only pre-selected option
For the offer “6€ for 2 WHOPPER® or Big King Meals” – we will have 6 additional combo slots:
“Offer – Whopper or Big King”, a combo slot with a Whopper (item) or Big King (item) as options
“Offer – Whopper or Big King”, a combo slot with a Whopper (item) or Big King (item) as options
Regular Fries, a combo slot with Fries (item), as the only pre-selected option
Regular fries, a combo slot with Fries (item), as the only pre-selected option
Medium Combo Drinks, a combo slot with the drinks you wish to include as an option for this offer
Medium Combo Drinks, a combo slot with the drinks you wish to include as an option for this offer
Alternatively, you could have created just one combo slot “Regular Fries x2”, and include two Regular Fries, as pre-selected options. This is applicable because the guest does not have to make any choice, as is the case with the Whopper or Big King, or the drinks.
Using the same combo slot among offers or within the same offer will not work.
In the above example, you must duplicate the combo slot Medium Combo Drinks and add both to the Combo.
In order to show modifier options, make sure to go to each “Offer – Whopper” combo slots and change UI Pattern to “show”.
Reminder: Combo Slots never have a PLU, i.e. are set to ignore for each POS Vendor Config.
Except for Tablet / Simply Delivery, which must have the combo item id as a constant PLU (retrieve it from the path or by clicking on the 3 vertical dots at the top right → inspect → id).
Vendor Configs
Complex offers are particularly difficult to configure due to POS complexity, but do not get confused, these are the Vendor Configs of the Combo you just associated your offer with.
Your POS will likely require a Constant PLU but visit the guide Vendor Config Plu Types to check your POS configurations.
The Offer and the Combo will always have the same PLU.
Upsell Options
This allows you to propose to guests to upsell to a similar, bigger coupon. Usually, you will want to create a coupon with the exact same products, only bigger sizes, and try to upsell that option instead.
You need to have previously created the offer that you want to upsell, as it needs to be linked to this offer.
Any offer added here will be prompted as an upsell when the user clicks to redeem. With this feature, the brands will have the ability to offer the customer multiple up-sell coupons when they select a coupon.
Example:
Main Coupon
2€ Whopper
Upsell Coupons
3€ Whopper + Small Fries 🍔 🍟
4€ Whopper + Nuggets 🍔 🐥
4€ Whopper Meal 🍔 🍟 🍹
Short Code
Configure the code used for in-restaurant redemption.
Daypart
Configure the time of day the offer is available. More information on dayparts can be found here Dayparts
UI Pattern
Please select Standard Offer - this is the only pattern supported for your market
Locked offers Pannel
Promo Code Pannel
RuleSet
Rulesets allow you to dynamically attribute rules to your offers.
For example, you can limit the amount of times a user can redeem a coupon, the restaurants where this offer can be redeemed, the payment method that must be utilized with this offer, etc.
Below you can find the list of Rulesets, and the corresponding explanation. When set up, these conditions must be satisfied in order to use the offer:
Date-Band - Set the start and end date of when the coupon is redeemable. Outside of these dates, the coupon will be filtered from the UI.
Day-of-week-Band - Boolean flag per day of the week. Those days that are set to true will be the only days on which the coupon shows on the UI / can be redeemed.
Time-Band - Set the start and end time of when the coupon is redeemable. Outside of these times, the coupon will be filtered from the UI – working to make it so that the coupon isn’t actually filtered, but rather shows a modal that says not redeemable until ____. Also outstanding work: must be able to read the local time of the restaurant/user to properly assess this prop
Cool-Down - Seconds until the user can redeem this offer again. Default is 0, so if not included, the user can reorder right away.
Limit - User can redeem this coupon ___ times per day/week/month/year. Must always specify the time interval here. If the limit is not included, the number of redemptions is unlimited.
Restaurant Group Restrictions: This will display the offer only in the store group that has been assigned to the offer.
Cart Property - The cart must satisfy the following restrictions in order for the offer to be redeemable (we check rulesets at price call and commit call). If you set the
negate
flag on this rule, it makes it so that these properties must not be true in order for the offer to be redeemablesubtotal rule - cart subtotal must be [< , >, =, etc.] ___ cents
service mode - service mode must be set to one of the following
DELIVERY DRIVE_THRU EAT_IN TAKEOUT CURBSIDE CATERING_PICKUP CATERING_DELIVERY
platform - specify that user’s platform must be one of the following:
app kiosk web
loyalty - (this will prob be deprecated.. turned out to have no use case for it.. or at least we do not yet)
Payment-Card-Type - specify that user’s payment must be one of the following:
APPLE_PAY GOOGLE_PAY MASTERCARD VISA AMEX DINERSCLUB DISCOVER JCB
First-Order - Boolean flag, if true offer is only redeemable to users that have never purchased before
Requires Assignment - this is a string field.. write anything in this field to make it apply (“ “ works). If true, the coupon has to be assigned via Braze webhook in order to appear for a guest to redeem. All Tim Hortons offers must have this rule.
Allow redemption without Login - this is a string field.. write anything in this field to make it apply (“ “ works). If true, users can redeem without having to sign in
AND - All of the sub-requirements of an AND rule must be true in order for the offer to be redeemable
OR - one of the sub-requirements of an OR rule must be true in order for the offer to be redeemable
Order-History - this is equivalent to a quest or locked offer - we are basing eligibility based on PAST purchase behavior.
All order-history offers must either have a date band (did the user satisfy the criteria between these dates?) or a past seconds requirement (did the user satisfy the criteria in the last week?)
Between dates are inclusive of the dates listed
Past n seconds is calculated in SECONDS so you must convert if you want to calculate days, weeks
If the order of events matters, set the
sequence matters
flag to trueAll top level rules will have an accompanying checkbox on the UI
Incentives
For Support?
You can create offers specifically to compensate users for any business reason via the Support Tool. For example, let’s say you delivered an order that arrived cold and the guest complained. Instead of automatically refunding the client, you might want to propose offering a very nice offer so that you retain the guest.
If toggled, this offer will not appear in the Platform (web and app). Instead, it will show in the Support Tool, ready to be assigned to users.
Redemption Methods
By default, an offer can be redeemed in restaurant, or in a mobile order. That will result in two buttons being displayed for each offer: Add to Mobile Ordering and Use at Restaurant. However, you can limit it to only one of the two scenarios.
Note that limiting redemption to Mobile Ordering will allow offers to be redeemed in any service mode. To limit per service mode (delivery, eat-in, takeout, drive-thru, curbside), use the Ruleset field.
Offer Price:
Define the price of the offer.
Prices are set in cents, so 1.99€ would be 199
Market Price
Vendor Configs
This is where the PLU and PLU configurations are done.
In your brand and country Sanity environment, you will see the Service Mode Groups (Pickup and Delivery) and POS used, as well as the Tablet system in place, in case some restaurants use a POS without order injection integration.
In the example above, please note that rPOS will include the PLU of items for all Pickup service modes (Takeaway, Dine-in, Drive-thru, Curbside), whereas rPOS Delivery refers to the PLU of items for delivery only.
For each Service Mode Group (Pickup and Delivery), you will need to configure the correct PLU.
The Vendor Configs play a key role at our systems, as they are the bridge between the digital and the physical world. For that reason, we have created a comprehensive guide just for this topic.
Background Image
A background image can be inserted here. Managers tend to use this field to upload a 1 or 2 color background image to keep the offer’s attention on the products.
How to display the offers in the Front end?
Creating the offer only will not guarantee it gets displayed in the Front End, i.e. in the application. For that reason, this guide contains the necessary steps to make that happen and conclude the operation of offer creation.
Firstly, access the following document:
Marketing Content → Features → Feature Offers
Add the offers you want in the list, then depending on the rulesets and configurations you have defined previously, they will appear in the application for guests - offers are located in the page /rewards/offers. For example, www.burgerking.co.uk/rewards/offers.
Sorted Offers
Access the Sorted Offers field and associate each of the offers to be displayed. Note that offers will be shown to guests in the same order as defined here.
Best Practices Tips
Be mindful of the internal name of your offers. Adding identifiable internal names to offers will make this association a lot easier and faster.
For further information about configuring the offers page, access the guide Feature Offers.