Create Offer¶

This section details the different offers configurations supported in the Lobyco Platform.

Details¶

Name is used to identify and locate activities in the Lobyco Portal. Unique names aren't required, but a naming convention is recommended (e.g., 2024_week_42_CocaCola_20off).

Type defines the behavior of the coupon: in general, where to be shown, how it's gained (allocated or won).

Most of the settings are the same for all types. The main difference is in the way that they are allocated.
Direct - offer is allocated to the users at the time of the offer creation. The coupon's validity matches the offer date.
Direct - two steps has the member allocation of the offer done in a second step, and the coupons can be valid for less than the offer date.
Reward is used by another product to allocate coupons as rewards inside this offer. The coupons can be valid for less than the offer date.
You are able to see only the offer types enabled in your system. Additional custom types can be added to support different scenarios, like showing offers with a different design.

Note that not all types might be available in your environment, depending on the activated features and flows. Additionally, some custom offer types could be created based on bespoke needs, and not documented in this table.

WL supported Offer types:¶

Offer type	Description	Allocation	Activation
App Coupon	General offer available to all users	Direct - offer	pre-activated flag applies
Challenge	Offer used as reward for challenge activity	Reward	pre-activated flag applies
Game	Offer used as a reward for game activity	Reward	always pre-activated flag applies
Member Offer	Offer allocated to a list of members with a specific design in the App	Direct - offer	pre-activated flag applies
Personal Offer	Offer allocated dynamically to users based on their purchase history. The offer is created, and afterward, coupons are allocated to members in an additional step.	Direct - two steps	needs activation
Segmented App Offer	Offer segmented to a specific list of users	Direct - offer	needs activation

Custom Offer types:¶

Offer type	Description	Allocation	Activation
External	An external type of an offer used to be redeemed on the partner side. This could either be shown in the app or not (depends on your particular case) but the end integration should be happening on the partner's POS. E.g., an offer for a fuel discount as a reward after shopping in a store.	Direct - offer	pre-activated flag applies
External Segmented	A segmented version of the External offer.	Reward	pre-activated flag applies
Base Bonus	Base Bonus offer is used as a base % bonus on top of every purchase. This allows more customisation than the regular Base earn bonus feature, like defining a list of included/excluded products or categories and stacking rules configuration. Such an offer should always be pre-activated, and we recommend not showing it in the app as an offer card.	Direct - offer	pre-activated flag applies
Gift	A default choice for Orchestration. Offer is allocated through custom business logic on the Orchestration canvas.	Reward	pre-activated flag applies
Liquor	Offer used for liquor products, shown in the same way as App Coupons but with some extra legal notice	Direct - offer	pre-activated flag applies
Preferred Store	Offer available to members based on their preferred store selection. These are specific to the store and their audience	Direct - offer	pre-activated flag applies
Stickers Offer	Offer used as a reward for sticker campaign activity. Users collect stickers to exchange for rewards	Reward	always pre-activated
Stamp Card	Deprecated - use Challenge	Reward	-
Voucher - Standard	Deprecated - use other Offer types with Bonus benefit	Direct - offer	pre-activated flag applies
Voucher - Triggered	Deprecated - use other Offer types with Bonus benefit	Reward	pre-activated flag applies
Fuel - Standard	An offer for a fuel discount. Available to all users and is ready to use.	Direct - offer	pre-activated flag applies
Fuel - Triggered	Triggered fuel discount offer. Used as a Game/Challenge reward or as a custom orchestration flow reward.	Reward	pre-activated flag applies

Start date and End date determine the visibility of the Offer in the App, or when it's available to have allocated coupons in the offer for the reward offer types, like Games, Challenges, and Sticker Cards.

The dates are pre-populated from the parent campaign, but can be changed as needed.

It's good practice to start activities at 00:01 and end at 23:59 to avoid confusion for end users and plan more efficiently.
Even though the offer's end date supports past dates, we recommend not creating them with start times in the past.
If the offer is created inside a campaign, the start date and end date need to be inside the campaign dates. The campaign start date and end date are shown under the dates input fields.

Pre-activated allows users to get the offer applied without having to interact (activate it) in the app. In the Lobyco Mobile App the Activate (or similar) button does not appear, and the offer is automatically redeemable at the POS.

⚠️The toggle is shown and can be toggled for all types, but is currently only applicable for these types: App Offer, Liquor, and Preferred Store.

Display priority defines the order of the offer in the App, compared with other offers of the same type.

If you have an offer section in your Loyalty App where multiple offer types can be shown (e.g. App Offer, Store Offer) then the sorting order will be decided by you during the implementation of the Lobyco Promotion Platform.

Sponsor is a field that can be selected to support reporting the source of the offer sponsorship. It can be a Store, Supplier, Chain, or Group.

Visibility before offer start date – can be optionally selected to show the offer in the app some time in advance before it can be activated. The user will see the offer locked and the date when it can be activated. If this field is left blank, the offer will just be visible at Campaign start date. This option is only available for offers with segmentation capabilities.

Validity period of voucher – defines offer validity period. This option is only available for offers with triggered capabilities.

Location¶

Chain IDs or Store IDs

Select where the offer is valid, either in chains or stores.
Chains and stores cannot be selected simultaneously. If you choose one or more chains, the store selector will automatically be disabled, and vice versa.
Press the up arrow from the store field to upload a store list. The file needs to be in CSV format, with one store ID per line.
Once one or more stores are selected, press the down arrow to download the list of selected stores in CSV format.

Stacking and limits¶

Here you define how the offer applies and stacks in relation to other Lobyco Offers. The store discounts are normally treated as starting prices and are always stacked - see Offers Overview for details.

Allow other offers on top

True - other Lobyco offers CAN be applied over the current one.
False - other Lobyco offers CANNOT be applied over the current one.

This is by default enabled, as you will normally make sure that a product is not part of multiple offers and want offers to be cumulative (e.g., you have a basket coupon for 10% off that should be applied on all products, even if they are discounted).

Stacking Priority

Sets the order in which offers are applied.
If there are two discounts with the same priority, the one that expires first is applied, with the oldest start date and earliest end date.

This allows values from 1 to 10, and by default is 5. This default value is set so that all offers are medium priority, and you can always create some higher or lower priority offers that are applied first or afterward.

📝Example: You want to create a "best price" offer, with 50% off on a product. To ensure that this is the final price for that product and no other offers are applied, you should set Allow other offers on top to false, and set the Priority to 1 (highest). This ensures that this offer is always applied first for this product, and no other offers reduce the price afterward.

Apply on items

Apply on all items - discount applies to all items, regardless of whether a discount is already applied or not
Apply only on discounted items - applies only on already discounted items
Apply only on non-discounted items - applies only on already NOT discounted items

Most of the time you can leave the three stacking configurations (Allow other offers on top, Priority, Apply on items) to their default values. This means that this is just a regular offer that could potentially stack with other offers in any way.

Discount type¶

A Discount is the monetary reduction or a bonus value applied to a basket or item, calculated by the Lobyco Discount Service according to Offer/Coupon rules.

These settings define available discount triggers and the effects.

Product Discount¶

Applies the discount at the product level.

Buy: the products or categories included in Product IDs and/or Category IDs, in the quantity or amount specified on Purchase Value.
Get: discount amount off, percentage off, or fixed price from Offer Value
Limit: Maximum quantity per receipt in one transaction.

Basket Discount¶

Applies the discount on the basket total value, optionally excluding some items or categories.

Buy: anything excluding products or categories included in Product IDs and/or Category IDs, at least of the amount specified on Purchase Value.
Get: discount amount off or percentage off.
Limit: Discount amount limit is the maximum value of the discount on a transaction.

Mix & Match¶

Applies the discount when 2 or more different products are purchased. Any number of rules can be added, and all must be met to trigger the discount.

Buy: the products or categories included in Product IDs and/or Category IDs, in the quantity or amount specified on Purchase Value. At least two rules need to be defined.
Get: discount amount off or percentage off. It can be different from rule to rule, as there could be an offer to give 10% off on items from the first rule, and 20% off on items from the second rule.
Limit: Maximum quantity per receipt is the total number of groups of items from the rule that get the discount.

Mix & Match Total Value¶

Applies the discount when 2 or more different products are purchased. Any number of rules can be added, and all must be met to trigger the discount. It's different than Mix & Match because it applies only one discount to all involved products, and it allows a fixed value for all items.

This is most commonly used for Meal Deal-type offers.

Buy: the products or categories included in Product IDs and/or Category IDs, in the quantity or amount specified on Threshold Value. At least two rules need to be defined.
Get: discount amount off, percentage off, or all items for a fixed total price.

Threshold Discount¶

Applies a discount to every n-th item once the configured quantity threshold is reached.

⚠️ The threshold value cannot be set to 1.

Buy: the products or categories included in Product IDs and/or Category IDs, in a quantity equal to or greater than the specified Threshold value.
Get: discount defined in Offer Value (amount off, percentage off, or fixed price) applied to every n-th item.
Limit: Maximum quantity per receipt within one transaction.

📝Example: If the limit is set to 2 and the Threshold value is 3, the discount will apply to the 3rd and 6th items, but not to the 9th.

Quantity Tier¶

Applied after each defined quantity is reached, multiple steps available each with its own discount. The greatest reached tier's discount applies.

⚠️ Minimum amount of rules cannot be less than 2.

Buy: the products or categories included in Product IDs and/or Category IDs are the same for all rules. The quantity of those products is defined per rule, cannot be less than 2 and should always increase with each rule.
Get: discount defined in Offer Value (amount off, percentage off, or fixed price). Defined per each rule, no limitations for the discount to be greater as the rule increments.
Limit: Maximum quantity per receipt within one transaction.

Product IDs / Category IDs

Configures the items or categories that are included in the offer. Click the pen or plus to edit the list of item IDs, one per line.
You can also upload a CSV file with IDs, one ID per line. The content of the file is just populated in the form and can be later reviewed and edited. The initially uploaded file name is not stored.
We advise that the list of IDs should not exceed 40,000 affiliations and 20 challenges running simultaneously, as going beyond these limits may lead to performance issues.
The IDs can be downloaded for further review.
For Basket Discount, the product and categories are used for exclusion from the offer.

Offer type

Amount off - gives a fixed amount off from the price of the product or basket.
Fixed Price - sets a fixed price for the product. Not available for Basket offer level.
Percentage off - gives a percentage off from the price of the product or basket.
Bonus Percent - gives a bonus percentage from the price of the product or basket.
Bonus Amount - gives a bonus fixed amount.

Purchase type - configures when the offer is triggered, related to the amount or quantity to be purchased.

Amount - when the value of the products or total basket has been reached. Example: buy a minimum of $5 of Coca-Cola to get 10% off.
Quantity - a number of products from the offer have been purchased. Example: buy at least 2 bottles of Coca-Cola to get 10% off.

Purchase value

The minimum UoM (unit of measure) or amount that must be met before the offer is applied.
When the Purchase type is Amount, use 0.01 to trigger the offer for any purchase.
For weighted items, if the offer needs to be triggered for any purchase, then use a low value, e.g. 0.001 - 1 gram.

Maximum uses per receipt

This is the maximum quantity in UoM (unit of measure) that can get the offer on a single transaction. Overall, the offer will discount a maximum of Redemption Limit x Maximum uses per receipt.
This can be overwritten by Discount amount limit in case the maximum amount is reached before.
Not available for Basket offer level.

Ignore offer on POS - This is an option mostly relevant in those cases where an external system is used to set up offers. - Making this true (on) will mark this offer to not be sent to the POS for discount calculation. - It means such an offer will only be visible in the mobile app but not sent to the POS to avoid double allocation of similar offer from both systems.

Limits¶

Redemption limit¶

Configures the total number of transactions on which the offer can be used.

Changing the redemption limit to an activated offer does not apply to already activated or redeemed coupons.

Discount amount limit¶

Sets the maximum amount given as a discount with the current Coupon per redemption.

In case of Product and Basket Discount with percentage off selected and if the redemption limit is more than 1, you will have a choice to set up Discount amount limit per redemption or across all redemptions. Use 0 or leave empty for unlimited.

Per redemption limit cannot be exceeded within a single transaction while Across all redemptions limit is shared across all redemptions and once reached, the discount will not be granted with the next redemptions.

⚠️ Across all redemptions applies per Coupon and not Offer. So, if a user will receive multiple Coupons of the same Offer, the limit will be set per each Coupon separately.

Prices¶

Available only for Product Discount and might not be used by some retailers, or could be used when a backup Price needs to be shown in the Application for a product. This is not the actual calculation price, it's just a price to be shown in the App if there is no Pricing Catalog integration done. When the coupon is redeemed, the discount will be applied to the price received from the checkout system.

Product price before discount - the price per product to be shown in the App for the product before discount
Unit price before discount - the price per unit to be shown in the App for the product before discount

Content¶

In this section, you configure the look and feel of the offer in the App. Some fields might not appear in the Admin Portal, as this section supports some level of customizations.

Offer title is the name of the offer as shown in the App.

Description textbox allows you to input the relevant information about the offer. Could be product details, terms and conditions, and others.

Product brand is optional and can be used to show the brand of the product. The App offer design needs to be aligned to show this value.

Image of the product can be uploaded to be shown in the App. The file format needs to be jpg or png, and there is no file size limit. However, we recommend that the images should be optimized and rather small in size < 300kb, so they can be loaded fast in the App.

Image URL is an alternative to point to an image that is already hosted on a public server and can be reached by the App.

Discount label is optional and can be used to show a discount tag in the App. The App offer design needs to be aligned to show this value.

Normal price label is optional and defines the text shown in front of the price before discount in the App (e.g. Normally, Was, Non-member price). This field is the label only — the price itself is taken from Product price before discount in the Prices section. Note that in some App implementations the price before discount is only displayed when this label is filled in, so leave it empty only if you don't want the price before discount shown.

Condition label is optional and can be used to show the purchase condition of the offer in the App (e.g. When you buy 3 or more). It overrides the default condition text that the App would otherwise show. The field allows up to 64 characters, so keep it short.

Enable price per unit label is optional and controls whether the price per unit is shown in the App. Both this option and Unit of measure need to be set for the label to appear, together with Unit price before discount in the Prices section.

Unit of measure is optional and can be used to show the unit of measure in the app (e.g. kg, L). The App offer design needs to be aligned to show this value.

Receipt display text is optional and can be used to send this field to the POS so that it's printed as the discount label on the receipt. Integration needs to be aligned so that the POS uses this value.

💡Additional content fields¶

Additional metadata fields can be added in the Offer content section to allow further customization of the look and feel of the coupons. This can be done during the implementation phase or afterward, based on a custom request.

Save as template¶

An activity can be flagged as a template and used as a starting point later on to create new activities. This is just a flag and does not impact the offer in any way.

The template flag can be toggled on and off at any point, even after the activity has expired.

When a template is created, it preserves all of the original activity's properties except for the Start date and End date.

Edit active Offer¶

It's possible to edit an already active Offer with some limitations. - Offer type cannot be changed once an Offer is active. - Redemption limit, Start date and End date shouldn't be changed as the change will not take effect on already activated or redeemed coupons.