Menu Banner Settings allows users to upload menu banners and assign them to individual stores or groups of stores, instead of applying a single banner across the entire channel. This lets brands tailor promotions to a more local and relevant market. The channel-level default banner is still set in the Content Manager tool; see Content Manager Tool User Guide for the channel-level default.
Store-level banners apply everywhere a store's menu appears in Serve: on Serve web and in the Serve iOS and Android apps. A banner assigned to a store displays consistently across all three.
NOTE: The store-level upload experience (Menu Banner Settings) and the channel-level default upload experience (Content Manager tool) are separate today. Olo intends to migrate them together in the future.
Requirements
Prerequisite
The brand must be using Serve, Olo's white-label ordering solution.
Permissions Needed
An Olo Dashboard account with one of the following permission levels is required:
\n
\nBrand Manager: Can upload, assign, remove, and delete store-level menu banners.
\n
\nBrand Administrator: Can manage store-level menu banners and grant access to other Dashboard users via User Management permissions.
\n
How store-level banners work
Each store displays one menu banner above the menu in Serve, on both Serve web and the Serve iOS and Android apps. Which banner a store shows is controlled in Olo Dashboard under Menu Banner Settings. On the Stores tab, the Banner Source column shows where a store's banner comes from:
\n
\nBrand Default: The store inherits the channel-level default banner set in the Content Manager tool.
\n
\nOverride: A store-level banner has been assigned to the store in Menu Banner Settings and replaces the brand default.
\n
How to open Menu Banner Settings
Open the page one of two ways:
\n
Navigate to Settings > Brand Settings > Menu Banner Settings.
\n
From anywhere in Dashboard, type Menu Banner Settings in the search field and select it from the results.
\n
The page opens with two tabs: Stores and Banner Assets.
How to upload a banner
Upload a banner to your library before assigning it to stores.
\n
Select the Banner Assets tab.
\n
Click Upload Banner.
\n
In the Upload New Banner window, click Upload Image and select your image. A preview appears once the image is accepted.
\n
Complete the required fields, then click Upload. The banner appears in the Banner Assets list.
\n
Banner Fields
\n
\nBanner Image: Required. 2560 x 512px minimum. JPG, PNG, or GIF. Maximum size 5MB. Images that do not meet the quality or dimension requirements are rejected with an error.
\n
\nBanner Name: Required. Up to 100 characters. An internal name used to identify the banner in your library.
\n
\nRedirect Link: Optional. The page a guest opens when they tap the banner. Must be a full, valid URL (for example, https://www.olo.com/); an invalid format is rejected.
\n
\nOpen link in a new browser window: Optional. When checked, the redirect link opens in a new tab.
\n
\nAlt Text: Required. Up to 125 characters. Describes the image for accessibility.
\n
\nInternal Description: Optional. An internal note about the banner.
\n
How to assign a banner to stores
A banner image must first be uploaded on the Banner Assets tab before it can be assigned to a store. Once the banner is uploaded:
\n
Select the Stores tab.
\n
Check the box next to each store you want to update. Checking a group of stores selects all stores beneath it.
\n
Click Select Banner in the action bar at the bottom of the page.
\n
In the Apply Banner window, choose a banner, then click Next.
\n
Review the Confirm Selection screen, which shows the current banner and the banner each store is changing to, then click Apply Banner.
\n
The selected stores now show the assigned banner with a Banner Source of Override.
The Confirm Selection step shows each store's current banner and what it is changing to.
How to remove a banner from stores
Removing a banner reverts the selected stores to the brand default.
\n
On the Stores tab, check the box next to each store you want to revert.
\n
Click Remove Banner in the action bar.
\n
In the confirmation window, review the affected stores, then click Remove Banner.
\n
The Banner Source for those stores returns to Brand Default.
How to delete a banner
Deleting a banner cannot be undone. Any store using the banner reverts to the brand default.
\n
Select the Banner Assets tab.
\n
Click the three-dot menu on the banner's row and select Delete Banner.
\n
In the confirmation window, review the affected stores, then click Delete Banner. A confirmation message will be shown.
\n
How to preview a banner on Serve
On the Stores tab, click any store name to launch that store's Serve site in a new tab, where the assigned banner appears above the menu categories. The same banner also appears above the menu in the Serve iOS and Android apps.
Setting the channel-level default banner
The brand default banner that stores inherit is set in the Content Manager tool, not in Menu Banner Settings. For instructions on uploading the channel-level default banner, see Content Manager Tool User Guide.
FAQ
What is the difference between Brand Default and Override?
Brand Default means the store inherits the channel-level banner set in the Content Manager tool. Override means a store-level banner has been assigned in Menu Banner Settings and replaces the brand default for that store.
Where does the banner appear for guests?
The assigned banner appears above the menu categories anywhere the store's menu is shown in Serve, including Serve web and the Serve iOS and Android apps. No separate setup is needed for the apps.
Can I assign one banner to many stores at once?
Yes. On the Stores tab, check multiple stores, or check a brand or group to select every store beneath it, then use Select Banner to apply one banner to all of them.
What happens to a store's banner if I delete the banner it is using?
The store reverts to the brand default. Deleting a banner cannot be undone.
Why is my image rejected on upload?
The image must meet the minimum dimensions and be a supported format (JPG, PNG, or GIF) under 5MB. A redirect link must also be a full, valid URL, such as https://www.olo.com/.
Are the store-level and channel-level banner tools the same?
Not today. Store-level banners are managed in Menu Banner Settings, and the channel-level default is set in the Content Manager tool. Olo intends to migrate these experiences together in the future.
","user_segment_ids":[]},{"id":48064695598875,"url":"https://olosupport.zendesk.com/api/v2/help_center/en-us/articles/48064695598875.json","html_url":"https://olosupport.zendesk.com/hc/en-us/articles/48064695598875-Periodic-Text-Messages","author_id":392524727751,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":46237264270363,"created_at":"2026-03-20T17:08:13Z","updated_at":"2026-07-14T17:02:15Z","name":"Periodic Text Messages","title":"Periodic Text Messages","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-06-16T20:50:17Z","user_segment_id":null,"permission_group_id":1679032,"content_tag_ids":[],"label_names":[],"body":"
Periodic messages sent for marketing purposes require customers to actively express consent in writing (e.g. double opt-in) to receive your text messages.
\n
\n\n
\n
When crafting your message content, it’s important to understand compliance before you send a message. Prior express written consent from your customers is mandatory.
\n
It is always a good idea to contact an attorney to seek additional advice pertaining to TCPA (Telephone Consumer Protection Act) and SMS —text marketing best practices in general.
\n
\n\n
\n
The below is a step-by-step guide on how to setup a marketing message via campaign and campaign notifications:
\n
\n
Via Campaign
\n
A campaign text message is strictly marketing message sent to a defined audience.
\n
\n
Navigate to Campaigns > Create
\n
Select the automation type Date & Time or Recurring and click Next Step\n
\n
Note: The Recurring campaign requires additional interval details to be defined before clicking Next Step
\n
Select to Send Text Message\n
\n
Enter your text message content and click Next Step.
\n
Note: The Date & Time campaign requires additional scheduling to be defined before clicking Next Step
\n
Define your Audience segment and click Next Step. For more info, see Audience Filters\n
\n
Enter a unique and easy to understand campaign name for your internal reference
\n
Define the start and end dates
\n
Review and confirm by clicking to Schedule your campaign
\n
\n
\n
Via Campaign Text Notification
\n
A campaign text notification is a text message send that occurs at the time of a specified event.
\n
\n
Navigate to Campaigns > Notifications
\n
Add a new notification
\n
Select the event that will trigger the notification and click Next.
\n
Enter a unique and easy to understand event name Note: fields may vary based on event type, enter all required information\n
\n
Select the to medium of the notification — in this use case, you will select Text message Note: Medium options will only be displayed if the integration is enabled.\n
\n
Enter your text message content.
\n
Enter the start and end dates
\n
Review and Create your new notification.
\n
\n
\n
","user_segment_ids":[]},{"id":48063963383707,"url":"https://olosupport.zendesk.com/api/v2/help_center/en-us/articles/48063963383707.json","html_url":"https://olosupport.zendesk.com/hc/en-us/articles/48063963383707-One-Time-Text-Messages","author_id":392524727751,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":46237264270363,"created_at":"2026-03-20T16:56:49Z","updated_at":"2026-07-14T17:01:54Z","name":"One-Time Text Messages","title":"One-Time Text Messages","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-06-16T20:51:05Z","user_segment_id":null,"permission_group_id":1679032,"content_tag_ids":[],"label_names":[],"body":"
The below is a step-by-step guide on how to setup a one-time message via settings notifications:
\n
\n
\n
A one-time text message is not marketing, you can only send the requested information by the customer once. These are commonly used for account notifications.
\n
\n\n
\n
\n
Settings Notifications
\n
\n
Navigate to Settings > Notifications
\n
Add a new notification
\n
Select the event that will trigger the notification and click Next.
\n
Enter a unique and easy to understand event name Note: the fields may vary based on event type, enter all required information\n
\n
Select whether to require customer opt-in. By requiring opt-in, a person must have consented to marketing messages and be double opted-in to receive the text message upon event.\n
\n
Select the to medium (email or text message) of the notification — in this use case, you will select Text message\n
\n
Note: Medium options will only be displayed in the dropdown if the integration is enabled.
\n
Enter your one-time text message content.
\n
Review and Create your new notification Notifications may take up to 10 minutes to start sending.\n
\n
\n
\n
","user_segment_ids":[]},{"id":48063203084699,"url":"https://olosupport.zendesk.com/api/v2/help_center/en-us/articles/48063203084699.json","html_url":"https://olosupport.zendesk.com/hc/en-us/articles/48063203084699-Loyalty-Store-Settings","author_id":392524727751,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":46237360852123,"created_at":"2026-03-20T16:43:43Z","updated_at":"2026-07-14T17:01:29Z","name":"Loyalty Store Settings","title":"Loyalty Store Settings","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-05-27T21:06:02Z","user_segment_id":null,"permission_group_id":1679032,"content_tag_ids":[],"label_names":[],"body":"
\n
\n
\n
\n
Your Loyalty Store Settings are a central place to view and manage all your store details in your account.
\n
Stores are defined as the places where a member visits, makes purchases, earns points, or redeems offers. These activity types are associated with the store at which the event occurs. Members have the option to select a favorite store, allowing for targeted marketing tailored to their preferred shopping location. Many of your program insights can be filtered by your member’s favorite store details.
\n
\n
Things To Know
\n
\n
Stores cannot be deleted; this preserves any transaction or member’s favorite store data associated with the store.
\n
Updates to a store’s number may break your POS, e-commerce, or marketing integrations. Whenever making updates to the store details, also update all your integrated platform providers to ensure the mapping of the store numbers match and the connected integrations are not broken.
\n
Existing store details can be edited and repurposed by an Admin or Marketing Manager user; however, this will impact past data associated with the store. For example, if “Store A” details are updated to the new labeling of “Store B”, going forward all of “Store A” past data will be associated with the new label of “Store B”. If you have any 3rd-party marketing integrations, any prior synced member store preferences will not be updated when a store label changes in the Olo Loyalty system. A member’s store preference will only update to 3rd-party providers when a member makes an update to their account.
\n
\n
\n\n
\n
Create A New Store
\n
You must be an Admin or Marketing Manager user to create a store.
\n\n
Navigate to your Dashboard Settings / Stores.
\n
Click + Create New Store button.
\n
Enter the store details. See Store Details below for more information.
\n
Click Save.
\n\n
\n\n
\n
Manage Your Store Settings
\n
You must be an Admin or Marketing Manager user to create a store.
\n\n
Navigate to your Dashboard Settings / Stores.
\n
In the store row, click Manage / Edit to edit your store details.
\n
Enter the store details. See Store Details below for more information.
\n
Click Save.
\n\n
\n\n
\n
\n
Store Details
\n
\n
\n
\n
Field
\n
Description
\n
\n\n
\n
Store Name
\n
The store name is visible to your members. Most often they will see the store name on digital transactions, in their activity feed, and their favorite store preference.
\n
\n
\n
Store Number
\n
The store number is a unique alphanumeric code for the store. It's important that your store numbers are in sync across your Olo Loyalty integrations for orders and/or loyalty to work properly.
\n
\n
\n
Street Address
\n
Street address of the store location.
\n
\n
\n
City
\n
City of the store location.
\n
\n
\n
State/Province
\n
State/Province of the store location.
\n
\n
\n
Zip/Postal Code
\n
Zip/Postal Code of the store location.
\n
\n
\n
Store Phone Number
\n
Store phone number at the store location.
\n
\n
\n
Status
\n
\n
Store status values are:
\n
• Open for when the store is live and open. • Closed for when the store is permanently closed. • Active Hidden for when the store is visible in your Dashboard (most often for testing purposes), but not visible to your members. • Inactive for when the store is temporarily closed and has a planned reopening. Inactive store data is hidden from the Insights data and from participating in new campaign offers.
\n
\n
\n
\n
Discount Code Override
\n
The Discount Code Override allows Admin and Marketing Manager users to override the campaign discount codes on a store-level. For example, if Store A's Discount Code Override is set to \"DISCOUNT A\", and an offer was created with the discount code of \"DISCOUNT ALL\", at Store A, the discount code of \"DISCOUNT ALL\" will be overridden and uses the \"DISCOUNT A\". This is most commonly used when a store has a unique POS system where there is discount code variation between stores. Note: only one (1) Discount Code Override value can be set per store.\n
Disclaimer: This feature is currently in the pilot phase. It is only available to a select number of brands with early access. If you are interested in this feature, please connect with your CXM.
Overview
The Custom Boxes feature set unlocks two variations of a single user experience for your guests. Designed for both Serve and Switchboard, this UX accommodates menu item bundles where guests require maximum customization capabilities. It is well suited for large catering orders as well as standard mealtime scenarios.
Benefits
\n
Reduced Guest Friction: Allows guests to order large quantities of customized items (e.g., 50 burgers across 5 variations of 10 each) without repeatedly entering and exiting the product flow.
Advanced Bundle Management: Supports flexible ratios of choices within bundles (e.g., 1 bundle = 20 burgers, 2 salads, and 1 gallon beverage).
\n
Experience in action
Serve and Switchboard automatically select one of two layouts for a bundled product based on your menu structure. Both layouts are driven entirely by menu configuration—there is no separate backend setting to toggle between them.
\n
\n
\n
\n
\n
\n\n
\n
\n
Fixed Capacity Layout
\n
Minimum Threshold Layout
\n
\n
\n
Trigger condition
\n
Menu defines a strict, fixed item count per bundle
\n
Menu defines a minimum item count with no fixed ceiling
\n
\n
\n
Pricing model
\n
Flat price per bundle*
\n
Per-unit pricing once minimum is met*
\n
\n
\n
Ideal use case
\n
Pre-packaged, all-in-one value meals
\n
Large group or catering orders with variable sizes
\n
\n
\n
Customization
\n
Entrees and sides selectable on a single screen; quantities scale automatically with bundle count
\n
Entrees and sides selectable on a single screen; fully open-ended flexibility
\n
\n\n
*Modifiers can still carry their own add-on pricing on top of the bundle or per-unit price.
1. Fixed Capacity Layout
Designed for pre-packaged, all-in-one value meals with a strictly defined item count. Quantities scale automatically based on the number of bundles ordered, making this layout best suited for high-volume efficiency—such as standardized combo meals rather than custom group orders.
A typical Fixed Capacity bundle combines multiple required components. For example, a 20-person Burger Bundle might include burger variants, a salad selection, a cookie selection, and a beverage choice, each enforced through required/optional tags on the product page. As guests build out their burger variants, the page tracks progress against the bundle total directly in the call-to-action button (e.g., \"Add 10 more Burgers (Min. 20)\"), ensuring clarity on remaining requirements. Guests can also add side quantities beyond the bundle at a per-unit upcharge.
\n
\n
\n
\n
\n
\n
\n
Serve Product Page:
\n
\n
\n
\n
Serve Customization Page:
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Switchboard Product Page:
\n\n
\n
\n
Switchboard Customization Page:
\n
\n
\n
\n
\n
2. Minimum Threshold Layout
An open-ended format for large groups where guests pay per individual unit once a minimum requirement is met. This layout trades the strict structure of Fixed Capacity for maximum flexibility, making it ideal for catering orders where the final count is not known upfront.
As guests add variants, each item is listed as an editable line item with its own quantity stepper, edit link, and remove option. This provides full visibility into configured items and allows quick adjustments without restarting the flow.
Note: The Customization Drilldown experience uses identical fields and interaction patterns in both layouts (variant-level protein, bun, and cheese selection, with identical Save/Cancel controls). The layouts diverge at the product page level, where Fixed Capacity enforces a strict total and Minimum Threshold allows open-ended item addition.
\n
\n
\n
\n
\n
\n
\n
Serve Product Page:
\n\n
\n
\n
Serve Customization Page:
\n\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Switchboard Product Page:
\n
\n
\n
\n
\n
\n
\n
\n
Switchboard Customization Page:
\n
\n
\n
\n
Menu
The Menu functions as the structural backend and configuration tool for validating product and modifier quantities. The menu structure and the Consolidate Modifiers on Quantity setting are essential for Serve and Switchboard to process bundled products correctly.
See the \"how to set it up\" section, below, for details and screenshots of the Menu configuration.
Vendor Exports
A new product property, \"hasconsolidatedquantities,\" has been added to the Vendor Exports file structure. With that property and the menu structure information already available in the Vendor Export files, you will have everything that you need to see the full picture of your custom box products.
Ordering API
A new product property, \"hasconsolidatedquantities,\" has been added to the product object on all Ordering API endpoints that return the object. With that property and the menu structure information already available, you will have everything that you need to see the full picture of your custom box products.
To configure your menu to use the new Serve UX, there are a few essential requirements.
Consolidate Modifiers on Quantity
The \"Consolidate Modifiers on Quantity\" property, on the product must be enabled.
This feature will multiply the nested modifier groups' modifier quantity settings by the quantity of products (bundles) that the guest as selected, for the first nested level only.
In this example, a single bundle requires exactly 20 burgers, as per the Modifier Aggregate Quantity settings. Also, you are able to increment your unique customizable burgers by 1 to a maximum of 20, as per the Min/Max Modifier Quantity settings.
Menu Structure Requirements
In addition to the consolidate modifiers on quantity setting, Serve also reacts with one of the two UX experiences shown above based on the structure of the menu.
As shown below,
Your first level nested modifier group can be either a multi-nested group such as the Burgers and Salads, or a single nested group such as the Cookies. These will show up differently on Serve for ease of use by the guest.
For the multi-nested groups, you control the maximum number of customizations possible by duplicating variants of your nested choices to the max number of customizations that you want to support. In this example, the guest will be able to make between 1 and 3 customizations but not 4. The total quantities of all customizations must fit within the parameters described in the Consolidate Modifiers on Quantity section, above.
FAQs
Do I need to be on Catering+ for this feature?
No! This feature is available to all channels, including mealtime channels.
How do I enable the feature for a product?
Check the Consolidate Modifiers on Quantity setting in the product's settings.
What controls whether or not there is a root quantity field displayed for the guest?
The quantity of root level modifier groups governs the user experience regarding the bundle quantity field.
\n
Single modifier group below the product results in the experience without the quantity selector
\n
Two or more modifier groups below the product results in the experience with the quantity selector
Disclaimer: This feature is currently in the pilot phase. It is only available to a select number of brands with early access. If you are interested in this feature, please connect with your CXM.
Overview
The Custom Boxes feature set unlocks two variations of a single user experience for your guests. Designed for both Serve and Switchboard, this UX accommodates menu item bundles where guests require maximum customization capabilities. It is well suited for large catering orders as well as standard mealtime scenarios.
Benefits
\n
Reduced Guest Friction: Allows guests to order large quantities of customized items (e.g., 50 burgers across 5 variations of 10 each) without repeatedly entering and exiting the product flow.
Advanced Bundle Management: Supports flexible ratios of choices within bundles (e.g., 1 bundle = 20 burgers, 2 salads, and 1 gallon beverage).
\n
Experience in action
Serve and Switchboard automatically select one of two layouts for a bundled product based on your menu structure. Both layouts are driven entirely by menu configuration—there is no separate backend setting to toggle between them.
\n
\n
\n
\n
\n
\n\n
\n
\n
Fixed Capacity Layout
\n
Minimum Threshold Layout
\n
\n
\n
Trigger condition
\n
Menu defines a strict, fixed item count per bundle
\n
Menu defines a minimum item count with no fixed ceiling
\n
\n
\n
Pricing model
\n
Flat price per bundle*
\n
Per-unit pricing once minimum is met*
\n
\n
\n
Ideal use case
\n
Pre-packaged, all-in-one value meals
\n
Large group or catering orders with variable sizes
\n
\n
\n
Customization
\n
Entrees and sides selectable on a single screen; quantities scale automatically with bundle count
\n
Entrees and sides selectable on a single screen; fully open-ended flexibility
\n
\n\n
*Modifiers can still carry their own add-on pricing on top of the bundle or per-unit price.
1. Fixed Capacity Layout
Designed for pre-packaged, all-in-one value meals with a strictly defined item count. Quantities scale automatically based on the number of bundles ordered, making this layout best suited for high-volume efficiency—such as standardized combo meals rather than custom group orders.
A typical Fixed Capacity bundle combines multiple required components. For example, a 20-person Burger Bundle might include burger variants, a salad selection, a cookie selection, and a beverage choice, each enforced through required/optional tags on the product page. As guests build out their burger variants, the page tracks progress against the bundle total directly in the call-to-action button (e.g., \"Add 10 more Burgers (Min. 20)\"), ensuring clarity on remaining requirements. Guests can also add side quantities beyond the bundle at a per-unit upcharge.
\n
\n
\n
\n
\n
\n
\n
Serve Product Page:
\n
\n
\n
\n
Serve Customization Page:
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Switchboard Product Page:
\n\n
\n
\n
Switchboard Customization Page:
\n
\n
\n
\n
\n
2. Minimum Threshold Layout
An open-ended format for large groups where guests pay per individual unit once a minimum requirement is met. This layout trades the strict structure of Fixed Capacity for maximum flexibility, making it ideal for catering orders where the final count is not known upfront.
As guests add variants, each item is listed as an editable line item with its own quantity stepper, edit link, and remove option. This provides full visibility into configured items and allows quick adjustments without restarting the flow.
Note: The Customization Drilldown experience uses identical fields and interaction patterns in both layouts (variant-level protein, bun, and cheese selection, with identical Save/Cancel controls). The layouts diverge at the product page level, where Fixed Capacity enforces a strict total and Minimum Threshold allows open-ended item addition.
\n
\n
\n
\n
\n
\n
\n
Serve Product Page:
\n\n
\n
\n
Serve Customization Page:
\n\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Switchboard Product Page:
\n
\n
\n
\n
\n
\n
\n
\n
Switchboard Customization Page:
\n
\n
\n
\n
Menu
The Menu functions as the structural backend and configuration tool for validating product and modifier quantities. The menu structure and the Consolidate Modifiers on Quantity setting are essential for Serve and Switchboard to process bundled products correctly.
See the \"how to set it up\" section, below, for details and screenshots of the Menu configuration.
Vendor Exports
A new product property, \"hasconsolidatedquantities,\" has been added to the Vendor Exports file structure. With that property and the menu structure information already available in the Vendor Export files, you will have everything that you need to see the full picture of your custom box products.
Ordering API
A new product property, \"hasconsolidatedquantities,\" has been added to the product object on all Ordering API endpoints that return the object. With that property and the menu structure information already available, you will have everything that you need to see the full picture of your custom box products.
To configure your menu to use the new Serve UX, there are a few essential requirements.
Consolidate Modifiers on Quantity
The \"Consolidate Modifiers on Quantity\" property, on the product must be enabled.
This feature will multiply the nested modifier groups' modifier quantity settings by the quantity of products (bundles) that the guest as selected, for the first nested level only.
In this example, a single bundle requires exactly 20 burgers, as per the Modifier Aggregate Quantity settings. Also, you are able to increment your unique customizable burgers by 1 to a maximum of 20, as per the Min/Max Modifier Quantity settings.
Menu Structure Requirements
In addition to the consolidate modifiers on quantity setting, Serve also reacts with one of the two UX experiences shown above based on the structure of the menu.
As shown below,
Your first level nested modifier group can be either a multi-nested group such as the Burgers and Salads, or a single nested group such as the Cookies. These will show up differently on Serve for ease of use by the guest.
For the multi-nested groups, you control the maximum number of customizations possible by duplicating variants of your nested choices to the max number of customizations that you want to support. In this example, the guest will be able to make between 1 and 3 customizations but not 4. The total quantities of all customizations must fit within the parameters described in the Consolidate Modifiers on Quantity section, above.
FAQs
Do I need to be on Catering+ for this feature?
No! This feature is available to all channels, including mealtime channels.
How do I enable the feature for a product?
Check the Consolidate Modifiers on Quantity setting in the product's settings.
What controls whether or not there is a root quantity field displayed for the guest?
The quantity of root level modifier groups governs the user experience regarding the bundle quantity field.
\n
Single modifier group below the product results in the experience without the quantity selector
\n
Two or more modifier groups below the product results in the experience with the quantity selector
\n
","user_segment_ids":[]},{"id":47160939729947,"url":"https://olosupport.zendesk.com/api/v2/help_center/en-us/articles/47160939729947.json","html_url":"https://olosupport.zendesk.com/hc/en-us/articles/47160939729947-Infobip-Add-Points-Offers-to-a-Facebook-Form","author_id":410246746312,"comments_disabled":true,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":46237264270363,"created_at":"2026-02-26T23:52:15Z","updated_at":"2026-04-24T20:36:00Z","name":"Infobip | Add Points/Offers to a Facebook Form","title":"Infobip | Add Points/Offers to a Facebook Form","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-04-24T20:36:00Z","user_segment_id":null,"permission_group_id":1679032,"content_tag_ids":["01KGMP5A7NRMH84AC4N55D24FK"],"label_names":["olo loyalty","spendgo"],"body":"
Facebook Forms are a great way to acquire and build your audience. Now, you can In this article you will learn how to connect your Facebook Account to Infobip, Create a Form, and give an offer to members who complete a Facebook Form.
\n
\nExample implementations
\n
\n
Give an offer for joining text offers.
\n
Give a free online offer for joining
\n
\n
\nBefore You Start
\n
\nDefine Your Strategy
\n
Whether you’re trying to increase sign ups, build your test
\n
\nCreate Your Facebook Form
\n
When creating your Facebook Form, take into consideration the following Olo Loyalty member requirements when defining your fields to be collected
\n
A mobile phone number is the mininum requirement to create a Starter member.
show Lead Ads Facebook forms listed in the Infobip Form template builder.
\n
allow you to define your processing rules and field mappings so new Leads will be created in Infobip as soon as the Facebook form is submitted. You must establish a successful connection before setting your processing rules and field mappings.
\n
\n
\n
\n
\nThings to Know
\n
\n
Both active or archived forms may be visible depending on the forms you have configured in Facebook. Archived forms cannot be selected for edits in Infobip. Ensure your forms are active before setting up integrations and mappings.
\n
Regularly check for any updates in both Infobip and Facebook integration settings to maintain a seamless connection.
\n
Continuously monitor the new leads created in Infobip to ensure that the data mapping and processing rules are functioning as expected.
\n
\n\n
\nStep 1: Connect Your Facebook Account
\n
To integrate your Facebook business account with your Infobip environment and define your processing rules, follow these steps:
\n\n
\n
Log in your Infobip account and navigate to Exchange / All Apps.
\n
Opens image in full screen\n
\n
\n
\n
Search for Facebook Leads for People and click on the module.
\n
Opens image in full screen\n
\n
When you have not connected your app, the bottom status reads, “FREE”.
\n
\n
\n
Click Add.
\n
Opens image in full screen\n
\n
\n
\n
Confirm you want to add the app by clicking Add App.
\n
Opens image in full screen\n
\n
\n
\n
Click Connect Account.
\n
Opens image in full screen\n
\n
\n
\n
Click Connect With Facebook.
\n
Opens image in full screen\n
\n
\n
\n
A Facebook window will open. Follow the onscreen instruction to login and configure the account connection.
\n
Opens image in full screen\n
\n
\n
\n
Once the connnection is established you will see a success message that your Facebook account has been connected to Infobip Forms.
\n
Opens image in full screen\n
If you go to Exchange / My Apps you will also see the Facebook Leads for People module status is now Added.
\n
Opens image in full screen\n
\n
\n\n\n
\nStep 2: Create New Facebook Form
\n\n
\n
In Infobip, go to Content / Forms.
\n
Opens image in full screen\n
\n
\n
\n
Click CreateNew / Facebookform.
\n
Opens image in full screen\n
\n
\n
Select the three dot menu on the existing form template and click Use Form.
\n
Map the fields from the Facebook form to the corresponding fields in Infobip. This ensures that the data from the form submissions are correctly transferred. If your field does not exist in Infobip, create the Custom Person Attribute and then return to form for mapping.
Set the Lead and Customer Update to be one of the following options:\n
Add only new information
\n
Override existing information
\n
Do not update existing persons
\n\n
\n
Click Activate tolaunch your new form.
\n
Conduct a test submission to ensure that the data flows correctly from Facebook to Infobip.
\n\n\n
\nStep 3: Create a Flow to Add Points/Offer on Form Submit
\n
Use the following flow as an example on how to add points/offer to a member’s account on their Facebook Form submission. You may want to add additional steps based on your Form objectives.
\n\n
\n
In you Infobip portal, navigate to Moments / Communications.
\n
Opens image in full screen\n
\n
\n
\n
Click Create Flow button
\n
Opens image in full screen\n
\n
\n
\n
Choose +Start from Scratch.
\n
Opens image in full screen\n
\n
\n
\n
Choose Trigger as the way your audience will enter your flow.
\n
Opens image in full screen\n
\n
\n
\n
Choose your Trigger to be a People Real-Time Event.
\n
Opens image in full screen\n
\n
\n
\n
Define your People Real-Time Event Condition 1 to filter for when Form Submitted | happened | more or equal to | 1 times | any time This looks for each time a member a form at any time.
\n
Opens image in full screen\n
\n
\n
\n
Add a + Property
\n
Opens image in full screen\n
\n
\n
\n
Select your specific Facebook Form. Form | is | Select your Form Name.
\n
Opens image in full screen\n
\n
\n
Click Close to close the trigger settings.
\n
\n
Click the → right arrow to add an element.
\n
Opens image in full screen\n
\n
\n
\n
Select the Call API element.
\n
Opens image in full screen\n
\n
\n
\n
Enter in the Request URL input your url provided by Olo Loyalty. The URL will be formatted like (your exact URL is provided by Olo Loyalty and must be kept secure and not be shared). https://webservice.<env_name>.com/v2/loyalty/accounts/rewards?auth=<API_auth_key>
\n
Opens image in full screen\n
\n
\n
\n
Enable escaping of URL parameters (by default this is checked).
\n
Opens image in full screen\n
\n
\n
\n
Choose the Method as Post.
\n
Opens image in full screen\n
\n
\n
\n
Choose the Body / Data Format as JSON.
\n
Opens image in full screen\n
\n
\n
Enter the JSON code in the input field…\n
\n
To add points, copy paste the following code: IMPORTANT: please replace the50value in the below sample,\"balance_quantity\" : 50with the point value you want to add to member’s accounts for entering the Flow.
To add offers, copy paste the following code: IMPORTANT: please replace the16774value in the below sample,\"campaign_id\" : \"16774\"with the Campaign Id you retrieved from the Olo Loyalty Dashboard.
In the JSON code, highlight {msisdn} and click {} in the right corner to personalize with placeholders. Please note, the “+” prefix is required, do not remove.
\n
Opens image in full screen\n
\n
\n
\n
Search msisdn and select the attribute.
\n
Opens image in full screen\n
\n
\n
The {msisdn} will change from a regular to bold font style. Click Close.
\n
\n
Name your Flow at the bottom of your screen.
\n
Opens image in full screen\n
\n
\n
\n
Click Flow Settings at bottom right of screen.
\n
Opens image in full screen\n
\n
\n
\n
Add Condition to the Entry Limitations.
\n
Opens image in full screen\n
\n
\n
\n
Enter your Entry Limitation Condition. This limits how many times a person can submit a form and earn the offer/points.
A summary of the Olo Loyalty integration with Bite, including supported features and steps for setup.
\n
Bite
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Bite is the leading provider of intelligent kiosk solutions for fast-casual and quick-service restaurants as well as convenience stores.
\n
Launched May 2025
\n
Article Last Updated May 2025
\n
Category status:KISOK
\n
\n
\n
\n
\n
\nIntegration Summary
\n
\nWhat’s supported?
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Feature
\n
Supported
\n
Not Supported
\n
\n\n
\n
Ordering Interfaces
\n
\n
Kiosk
\n
\n
\n
Linebuster
\n
\n
\n
Olo Loyalty Features
\n
\n
Accrue points for loyalty claimed orders
\n
Redeem Olo Loyalty offers/rewards
\n
Combine Olo Loyalty rewards with non-Olo Loyalty rewards
\n
Loyalty reversal when order is refunded.
\n
\n
\n
\n
Claim receipt to accrue points for orders not claimed at the store
\n
Combine Olo Loyalty rewards with non-Olo Loyalty rewards
\n
\n
\n
\n
\n
\n
Base Program Types
\n
Points Banking
\n
Shop with Points
\n
\n
\n
Basket Level Rewards/Offers Types
\n
\n
$ Discount (Rebate)
\n
% Discount (Discount)
\n
Bonus Points
\n
\n
\n
\n
\n
Item Based Rewards/Offers Types
\n
\n
BOGO
\n
Free Item
\n
$ Discount
\n
Price Adjustment
\n
Bonus Points (Only at Basket level)
\n
\n
\n
\n
\n
Viewing/Selecting the available Rewards
\n
Listing of Available Rewards is at the order checkout.
\n
Only rewards applicable to the order is shown.
\n
Guest will not be able to view all available rewards on the kiosk and will have to look up the rewards
\n
On the Mobile App if the Merchant has an App available that is integrated with Olo Loyalty.
\n
On the Member Portal.
\n
\n
\n
\n
\n
\n
\n
Discount code requirement
\n
\n
There is no need to set up a discount in Bite.
\n
However, Bite needs to map Olo Loyalty reward applied in the order to be mapped with an Open $ discount configured in the POS system.
\n
\n
\n
\n
QR Code
\n
Supports scanning QR code containing 10 digit phone number for
\n
\n
\n
Online and In-Store Ordering Platforms supported by Bite
\n
\n
Bite supports Kiosk ordering with multiple different ordering platforms. Following are the ordering platforms that both Bite and Olo Loyalty support.
\n
\n
NCR Aloha
\n
Olo
\n
Par Brink
\n
Qu
\n
Revel
\n
Simphony
\n
Toast
\n
\n
\n
\n\n
\n
\n\n
\nThings to Know
\n
\n
\nNo support for guest orders:An order can be completed in the Kiosk without making a loyalty claim by entering the phone number before placing the order. However, such “guest' orders are not sent to Olo Loyalty. Guest orders will not show on Olo Loyalty dashboard and will not be available for accruing points by claiming the order receipt from Loyalty Member Portal.
\n
\nOrder ID Format: The Bite Kiosk member orders show up with a 12-14 digit numerical ID such as 6818e01f6fa5176220063a8f0 in the Olo Loyalty Dashboard. This is a unique Order ID created by Bite and varies from Merchant to Merchant. This is different from the order ID printed on the POS receipt. It is not possible to know the Order ID printed on the printed receipt from Olo Loyalty Dashboard. The Bite order Id should be looked up in Bite to get the corresponding POS receipt ID.
\n
\nThe Member order shows both as a Bite order and a POS order in Dashboard:When the Member places the order from Bite Kiosk Olo Loyalty order processes the loyalty on the order with Kiosk order ID. However it is possible that when the order is received at the POS terminal, it is possible that the POS also sends the order with the POS order ID as a guest order to Olo Loyalty. Some POS systems do not send Kiosk orders to Olo Loyalty but some systems do not. The integration has not been fully tested end-to-end with all Bite+POS combinations so at this time we do not have accurate information on which POS systems send and which POS systems do not. We will update this documentation with POS specific behavior as and when the information becomes available. It is not possible to prevent this duplication from happening either from Bite or Olo Loyalty. The only way to prevent the duplication from happening is if the POS system stops sending the Kiosk order to Olo Loyalty. When this happens
\n
The order placed from Bite shows up in Olo Loyalty as two orders with a different ID. The Bite order shows as a loyalty order but the POS order shows as a guest order.
\n
Since the orders are counted twice - this causes over-reporting of sales and orders counts and may impact the offers configured based on the sales or orders count.
\n
\n
\n
\nAdditional notes about how the order IDs are handled if the Member changes the order after applying the reward:Bite generates an order ID and sends it to Olo Loyalty for loyalty processing when the reward is applied. If the member changes the order after applying the reward or changes the applied reward, Bite voids the order and assigns a different order ID to the cart. So, in the dashboard this will show up as two orders. One with 0 points and the other for the updated order. Please note that even though this does not cause over-reporting of sales it will cause over reporting of orders count in Olo Loyalty Dashboard reports and may impact the offers configured based on the orders count.
\n
\n
\nProcessing Refunds to a closed order: The refunds on the closed order can be processed from Bite admin portal.
\n
\n
\n
\n\n
\n
Action
\n
Loyalty Processing
\n
\n
\n
Order is fully refunded
\n
\n
Loyalty on the order is revered.
\n
\n
Points accrued on the order is reversed
\n
Any loyalty reward applied to the order is added back to the Member’s balance
\n
\n
\n
\n\n
\n
Order is partially refunded
\n
\n
Partial loyalty reversal is not supported in Olo Loyalty. Partial refund is also treated the same way as the full refund.
\n
In order to keep the loyalty on the partial refund to be processed correctly, it is recommended to fully refund the order and create a new order with the updated order details.
\n
\n
\n
\n
\n
Notes about the order receipt on Olo Loyalty Dashboard
\n\n
\nReceipt Subtotal:\n
TheSubtotal shown on the Dashboard receipt matches with the Subtotal in Bite order.
\n
Subtotal reflects the sum of line items and tax and not the applied rewards/discounts/coupons and tips.
\n
Also note that the points accrued on the order does not always match with the subtotal. This is because Olo Loyalty does not compute points based on the receipt subtotal, but based on the sum of prices of items marked as qualifying for points.
\n\n
\n
\nReceipt Total:\n
\n\n
The Total shown on the Dashboard receipt matches with the Total on the Brink order. Receipt total reflects the sum of line item prices including modifiers + Tax + Tip minus the applied rewards/discounts.
\n
\n
\nIntegration Setup
\n
\nRequirements
\n
\n
The POS system is configured in Production
\n
Bite account is configured in Production
\n
Olo Loyalty account is configured in Production
\n
\n
\nSteps to Enable the Integration\n
\n
\nStep 1.Confirm the location(s) is ready for setting up the integration.\n
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Identify the locations to enable the Olo Loyalty Integration.
\n
\n
\n
Procedure
\n
After the POS, Bite and Olo Loyalty accounts are set up in Production, inform Olo Customer Success Manager (CSM) the list of locations that needs to be enabled and the name of the open $ discount in the POS that needs to be mapped in Kiosk.
Authorization from the Merchant to enable the integration
\n
\n
\n
Procedure
\n
\n
Co-ordinate with the Merchant the date and time for setting up the integration.
\n
Evaluate if there is any testing required after the integration.
If any testing is required, setup the testing time.
\n
\n
Instruct the Integrations team to set up and share Olo Loyalty API credentials with the Bite Technical consultant working with the Merchant.
\n
\n
\n
\n
Data to share
\n
\n
Locations List.
\n
Open $ discount configured in the POS system to be mapped in Bite.
\n
\n
\n
\n
Outcome
\n
\n
The time slot for enabling the integration is set up with the Merchant.
\n
A working session is set up with the Merchant for testing, if required.
\n
Instructions sent to the integration team along with the location list and the open $ discount name.
\n
\n
\n\n
\n
\n
\nStep 3: Olo Loyalty Integration team shares API credentials with Bite\n
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Olo Loyalty Integration Team
\n
\n
\n
Required Input
\n
Authorization from CSM and the Merchant contact to send the credentials to.
\n
\n
\n
Procedure
\n
\n
If the credentials are already not shared with Bite,
\n\n
Setup the Loyalty POS API keys in the Olo Loyalty Admin portal.
\n
Share the API credentials securely in a 1Password link with Bite.
\n
Include the Olo Loyalty Location Name and Numbers for each location
\n\n
Refer to internal documentation for detailed instructions.
\n
\n
\n
\n
Data to share
\n
Refer to internal documentation.
\n
\n
\n
Outcome
\n
API credentials mentioned above are shared with the open $discount name and the Olo Loyalty Store Numbers for each location.
\n
\n\n
\n
\n
\nStep 4: Bite enables the integration\n
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Bite
\n
\n
\n
Required Input
\n
API credentials shared by Olo Loyalty Integration team
\n
\n
\n
Outcome
\n
Integration Configured
\n
\n\n
\n
\n
\nStep 5: Verify the Integration\n
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Procedure
\n
\n
After the integration is set up, the quickest way to check if the integration is working is to do the Loyalty Member look up. Please refer to the “Loyalty Member Lookup” in the “Loyalty Flow” section below.
\n
\n
On the lookup screen enter a 10 digit US/Canada phone number. If it results in an error then there is an issue with the integration. Please report to Olo Customer Success Manager and Olo Loyalty Integration team.
\n
If the basic validation is successful and if this is the first location (preferably the lab store) inform the Olo Customer Success Manager. Olo Customer Success Manager follows up with the Merchant to complete the testing.
\n
\n
\n
\n\n
\n
\n\n
\nDisabling the integration\n
\n
\nStep 1.Confirm the location(s) is ready for disabling the integration.\n
\n
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Identify the locations to disable the Olo Loyalty Integration.
\n
\n
\n
Procedure
\n
Inform Olo Customer Success Manager (CSM) the list of locations that needs to be disabled.
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Olo Loyalty CSM
\n
\n
\n
Required Input
\n
Authorization from the Merchant to disable the integration
\n
\n
\n
Procedure
\n
Send the instructions to Bite
\n
\n
\n
Data to share
\n
Locations list
\n
\n
\n
Outcome
\n
Integration disabled at the identified locations.
\n
\n\n
\n
\n
\n\n
\nLoyalty Flow
\n
\nLoyalty Member Lookup
\n
Create the order on the Kiosk and click on “Buy Now”
\n
Select “Get Rewards”
\n
Enter the 10 digit Phone number to look up the available rewards
\n
If this an existing Olo Loyalty Member for the Merchant, the Points Balance and the rewards that can be applied to the order is displayed for selection.
\n
\n
\n
\n
If the Member exists in Olo Loyalty and this is the first time the number is looked up for the Brand, then the Member account is linked first and then the balance/rewards are fetched.
\n
If no Member exists in Olo Loyalty, a new “starter” account is created in Olo Loyalty.
\n
\n
\n
\n
\n
Only the rewards that the order qualifies are shown. It is possible the Member has other rewards available at the store. List of all available rewards can be viewed on the Member Portal.
\n
\n
\n
If no applicable rewards is available for the order then “No rewards” message is shown.
\n
\nApplying a reward\n
\n\n
After the Member lookup, review the available rewards. If no reward is to be applied click on “Pay with Credit card” and complete the order.
\n
For applying a reward, click on the “Apply” button next to a listed reward.
\n\n
Reward gets applied and the cart shows with the update after applying the reward. The “Apply” button changes to “Remove” for the applied reward.
\n
Click on “Play with Credit Card” to pay and complete the order.
\n
\nChanging the order after applying the reward
\n\n
To remove the reward click on the “Remove” button.
\n
To change the reward, remove the applied reward and select the other reward.
\n
If you want to change the order by adding or removing items for the cart, or change the quantity, the applied reward is automatically removed. The updated rewards list based on the updated cart shows for selection.
\n\n
Refunding the order
\n
Navigate to your orders in Bite admin and then choose “refund order”
A summary of the Olo Loyalty integration with the Techtris App, including supported features and steps for setup.
\n
\n
\n
\n
\n
\n
\n
\n
\n
Techtris builds Ordering and Marketing interfaces for Restaurant brands. Techtris integrates with Olo Loyalty for Loyalty integration for App with Toast POS.
\n
Launched January2025
\n
Article Last Updated March 2025
\n
Category APP
\n
\n
\n
\n
\nIntegration Summary
\nWhat’s supported?
\n
\n
\n
\n
\n
\n
\n
\n
\n
Feature
\n
Supported
\n
Not Supported
\n
\n\n
\n
Ordering Interfaces
\n
\n
iOS & Android App
\n
With Toast POS
\n
\n
\n
Web Ordering
\n
\n
\n
Olo Loyalty Features
\n
\n
Olo Loyalty Member Sign In/Sign up through Olo Loyalty oAuth interface*
\n
Accrue points for loyalty claimed orders
\n
Redeem Olo Loyalty offers/rewards
\n
\n
\n
\n
Accrue points for prior guest checkout orders by claiming the receipt
\n
Loyalty reversal
\n
\n
\n
\n
\n
\n
Base Program Types
\n
Points Banking
\n
Shop with Points
\n
\n
\n
Basket Level Rewards/Offers Types
\n
\n
$ Discount (Rebate)
\n
% Discount (Discount)
\n
Bonus Points
\n
\n
\n
\n
\n
Item Based Rewards/Offers Types
\n
\n
BOGO
\n
Free Item
\n
$ Discount
\n
Price Adjustment
\n
Bonus Points (Only at Basket level)
\n
\n
\n
\n
\n
Viewing/Selecting the available Rewards
\n
Listing of Available Rewards after logging in
\n
\nAt Rewards tab in the App - All rewards available to the Member at the Brand including the Points Banking awards available up to the Member’s current points Balance.
\n
\nAt order checkout: Rewards applicable to the order in the Cart.
\n
\n
\n
\n
\n
QR Code
\n
To be used for scanning for loyalty lookup in store
\n
\n
\n
Push Notification
\n
Supported when Olo Loyalty at the Merchant is configured with Infobip.
\n
\n\n
\n
\nThings to Know
No support for guest orders: An order can be placed from the App without logging in. However the order placed as guest is not sent to Olo Loyalty. Guest orders will not show on Olo Loyalty dashboard and will not be available for accruing points by claiming the order receipt from Loyalty Member Portal.
Order Format: The order placed from Techtris App matches with the toast Order ID.
\n
The Subtotal in the receipt view in Olo Loyalty Dashboard reflects the Order Subtotal before applying the reward.
\n
Dashboard receipt view contains tax on the order. But the tip and delivery is not shown.
\n
Total in the dashboard receipt view = Subtotal + Tax + Tip - Applied Reward.
\n
\nIntegration Setup
\n
\nRequirements:
\n
The Toast POS is configured in Production
\n
Olo Loyalty account is configured in Production
\n
\n
\n
Steps to Enable the Integration
\n
\nStep 1.Confirm the location(s) is ready for setting up the integration.\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Identify the locations to enable the Olo Loyalty Integration.
\n
\n
\n
Procedure
\n
After the Toast and Olo Loyalty account is setup in Production inform Olo Customer Success Manager (CSM) the list of locations that needs to be enabled.
Authorization from the Merchant to enable the integration
\n
\n
\n
Procedure
\n
\n
Co-ordinate with the Merchant the date and time for setting up the integration.
\n
Evaluate if there is any testing required after the integration.
If any testing is required, setup the testing time.
\n
\n
Instruct the Integrations team to setup and share Olo Loyalty API credentials with the Merchant.
\n
\n
\n
\n
Data to share
\n
\n
\n
\n
Outcome
\n
\n
The time slot for enabling the integration is setup with the Merchant.
\n
Working session is setup with the Merchant for testing, if required.
\n
Instructions sent to the integration team.
\n
\n
\n\n
\n
\nStep 3: Olo Loyalty Integration team shares API credentials with Techtris\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Olo Loyalty Integration Team
\n
\n
\n
Required Input
\n
Authorization from CSM and the Merchant contact to send the credentials to.
\n
\n
\n
Procedure
\n
\n
If the credentials are already not shared with Techtris,
\n\n
Setup the Loyalty and OAuth API keys in Olo Loyalty Admin portal.
\n
Share the API credentials securely in a 1Password link with Techtris.
\n\n
Refer to internal documentation for detailed instructions.
\n
\n
\n
\n
Data to share
\n
Refer to internal documentation.
\n
\n
\n
Outcome
\n
API credentials mentioned above are shared with the Merchant
\n
\n\n
\n
\nStep 4: Techtris enables the integration\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Techtris
\n
\n
\n
Required Input
\n
API credentials shared by Olo Loyalty Integration team
\n
\n
\n
Outcome
\n
Integration Configured
\n
\n\n
\n
\nUser Experience Screenshots:
\nApp Launches after the install (Landing)\n
Sign In/Sign Up - Loads Olo Loyalty oAuth login Page. Sign In/Sign up handled by Olo Loyalty Password less Login flow.
a. If the login fails or if the user does not want to proceed user can close the Window by clicking on “Done”
b. If the user logs in
b1. If this the first time login to the Brand, Olo Loyalty oAuth brings up the consent page.
b1a: On the consent screen if the user clicks cancel, then the oAuth window closes and the user returns to the landing page as not logged in.
b1b. User makesBrand specific selections (Favorite Store, Zip, Email, SMS Preferences).
c. User is returned to the landing page as a logged in user.
\n
\n
\n
\n\n
\n
UI Element
\n
Description
\n
Notes
\n
\n
\n
<Hello Place holder> First Name
\n
\n
\n
\n\n\n
\n
Points Balance
\n
Current Points Balance
\n
\n
Refreshed at next App launch or app login or if the Member clicks on the “Rewards” tab.
\n
Clicking the “Points”Balance opens the rewards tab
\n
\n
\n
\n
Rewards tab
\n
Shows Available Rewards (from /balance)
\n
\n
\n
\n
Account
\n
\n
Shows Profile
\n
+ some additional details such as Order History
\n
\n
Refreshes at next app launch or app login or if the Member clicks on the “Account” tab.
\n
\n
\n
QR code icon
\n
Open QR code to scan
\n
Contains Obfuscated Olo Loyalty ID
\n
\n\n
\n
\n3. Rewards tab
\n
\n
\n
\n
\n\n
\n
UI Element
\n
Description
\n
Notes
\n
\n
\n
You have <X> Points
\n
Current Points Balance
\n
\n
\n\n\n
\n
Scan for Loyalty
\n
Brings up QR Code to scan
\n
\n
\n
\n
Rewards Name
\n
\n
Shows all applicable rewards available to the Member.
\n
\n
\n
Expires
\n
Shows expiry date if available else blank.
\n
\n
\n
\n
<Brand> Loyalty tab
\n
Brand Specific rewards description
\n
\n
\n\n
\n
\n
\n3.1 Scan for Loyalty
\n
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
UI Element
\n
Description
\n
Notes
\n
\n
\n
Go to Loyalty
\n
Takes to the Rewards → <Band> Loyalty tab.
\n
\n
\n\n
\n
\n4. Account tab
\n
\n
\n
\n\n
\n
UI Element
\n
Description
\n
Notes
\n
\n
\n
My Account
\n
First Name, Last Name
\n
\n
\n\n\n
\n
Profile
\n
Open the “Read Only” Profile page
\n
\n
\n
\n
Logout
\n
Logs the user out
\n
Returns to Landing page as user not logged in
\n
\n
\n
\n
Payment
\n
Feedback
\n
Orders Tab
\n
\n
Not Loyalty related
\n
\n
\n\n
\n
\n4.1 Profile
\n4.1.1 Manage Profile
After going through the Passwordless login again for Member portal - Loyalty Member Portal is shown.
\n
\n
\n
\n
\n
\n
UI Element
\n
Description
\n
Notes
\n
\n
\n
Done
\n
Close the Member Portal and return to App
\n
\n
\n
\n
\n
\n5 Order Flow
\n
\n
The guest can create an order without login but for placing the order user needs to have a payment details. The payment detail can be added only if the Member is logged in so effectively there is no way to place a “Guest” order as of now. The guest is asked to login and will have to go through the oAuth login flow.
\n
\n5.1 Review and apply rewards on order checkout screen
Menu → Select the location → Add items to Cart → Checkout the cart
\n
\n
\n
\n\n
\n
UI Elements
\n
Description
\n
Notes
\n
\n
\n
Rewards
\n
Displays rewards applicable to the order
\n
\n
\n\n\n
\n
My Rewards
\n
Takes to 'Rewards” tab if the Member wants to view all available rewards
\n
\n
\n
\n
Apply
\n
Applies the reward
\n
\n
\n\n
\n
\n5.2 Applying a reward
Click on “Apply” link. The Reward is marked as “Applied” and the Cart updates
\n5.3 Removing the applied reward
Click on the x to remove the reward. Cart updates to show the order without the reward.
\n5.4 Switching reward
When a reward is applied, a reward can be change by clicking on “Apply” next to the reward to switch to. No need to remove the applied reward before switching.
\n5.5 Changing the cart after applying a reward
If the cart is changed after applying the reward
a. Reward Removed” message flashes and the updated cart shown with a reward removed
b. Rewards list is updated as per the updated cart.
\n5.6 Place the order
\na. If there is any error in placing the order, the error flashes and the user remains on the checkout screen.
b. If the billing completed and order is placed successfully, user is shown the order complete screen
Claim receipt from the Member Portal to accrue points for orders not claimed at the store
\n
Redeem Olo Loyalty offers/rewards
\n
Combine Olo Loyalty rewards with non-Olo Loyalty rewards
\n
Loyalty Reversal on order void/refund (Full void/refund only, Olo Loyalty does not support partial refunds)
\n
\n
\n
\n
\n
Base Program Types
\n
Points Banking & Auto-Earn
\n
\n
\n
\n
Basket Level Rewards/Offers Types
\n
\n
$ Discount (Rebate)
\n
% Discount (Discount)
\n
Bonus Points
\n
\n
\n
\n
\n
Item Based Rewards/Offers Types
\n
\n
BOGO
\n
Free Item
\n
$ Discount
\n
% Discount
\n
Bonus Points
\n
Price Adjustment
\n
\n
\n
\n
\n
Rewards shown for selection
\n
\n
Upon looking up the Member after creating the order, only the rewards applicable to the order are shown.
\n
All available rewards can be looked up by looking up the Member without creating the order. The rewards listed at this stage are not redeemable.
\n
If the order changes, the rewards are not validated automatically. Rewards re-lookup is needed if the order changes.
\n
\n
\n
\n
Discount code setup
\n
\n
A discount code is only needed if using an online ordering or third party in-store or payment platform integration which requires discount codes (such as Olo)
Please Name/Label the Discount Olo Loyalty Discount \n
\n
This Discount Code will be used to process all loyalty discounts and is passed in the API between Toast /Olo Loyalty when a reward is applied to an order.
\n
Settings should be as follows:
\n
Open $-off
\n
Apply to Entire Check
\n
No selection on the “Limit to Dining Options” drop down
\n
Availability - leave blank (should be all days/ times)
\n
Do not add any “Promo Code”
\n
Open “Advanced Settings”
\n
Set Permission Level → Any User
\n
Leave “Allow with other discounts” setting off(Olo Loyalty does not support discount stacking)
\n
\n
\n
\n
\n
Save and Publish to all locations
\n
\n
Once you have created/saved/published the Discount for all stores, within your Toast Admin it displays the discount name and number.
\n
Please then click on Discount code to edit - to locate the Discount Code GUID found in the URL.
After activating the Olo Loyalty integration in Toast there are several loyalty settings that are not visible to to the merchant. Changing these settings requires reaching out to your Toast RSM or to Toast Support. Below is the screenshot of the prompt settings options you can request (for the best loyalty program results, we suggest the “Always prompt to add rewards account to checks in POS” setting)
Impact of \"Use Toast Order GUID as Olo Loyalty Order Id\" Setting on Olo Loyalty Order Handling with Toast Order Updates:
Upon merchant request, the Olo Loyalty Integration team can enable the 'Use Toast Order GUID as Olo Loyalty Order Id' integration setting. When enabled, this setting prevents orders from being voided in Olo Loyalty if a closed order is updated in Toast (e.g., when an order is reopened to add a tip). The table below illustrates the difference between the default behavior and enabling this setting.
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
Feature
\n
Default Setting
\n
When \"Use Toast Order GUID as Olo Loyalty Order ID\" is Enabled
\n
\n\n
\n
Olo Loyalty Order ID
\n
All orders show in Olo Loyalty Dashboard with the guest-facing Toast order number.
\n
All orders show in Olo Loyalty Dashboard with the Toast internal ID (Toast order GUID).
\n
\n
\n
When a closed order in Toast is reopened and updated
\n
\n
Order gets voided in Olo Loyalty and shows with amount and points as 0 in the Dashboard.
\n
It looks as if the order got refunded from Toast. There is no way to distinguish between the real refund v/s the order showing as voided because if the update.
\n
\n
\n
The original order shows as voided (amount and points as 0).
\n
A new, updated order with a different Toast GUID shows with the updated amount and points. Please note that this also has few other implications
\n
Reporting: The orders will get counted twice.
\n
\nCampaigns that are targeted to audiences based on conditions such as visit count or average order amount may not work accurately.
\n
\n
\n
\n
\n
\n
Receipt Claims from Member Portal
\n
“voided” (refunded or updated) orders are not available for receipt claim. However all other guest orders can be claimed.
\n
Orders cannot be claimed from the member portal. Members will need to contact Olo Loyalty support with their receipt to claim an order.
\n
\n\n
\n
\n
Offline Mode: Olo Loyalty functionality is unavailable when the POS is in Offline Mode. Notably, if an order with an applied reward transitions to Offline Mode before completion, the reward will remain in the member’s balance despite being applied to the transaction. This creates a risk of duplicate redemptions.
Processing of the order Refunds
\n
Refunds are supported only for the same day orders.
\n
Please refer to the below table what happens when the order is refunded.
\n
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
Action
\n
Loyalty Processing
\n
\n\n
\n
Order is fully refunded
\n
\n
Loyalty on the order is revered.
\n
\n
Points accrued on the order is reversed
\n
Any loyalty reward applied to the order is added back to the Member’s balance
\n
\n
\n
\n
\n
Order is partially refunded
\n
\n
Partial loyalty reversal is not supported in Olo Loyalty. Partial refund is also treated same way as the full refund.
\n
In order to keep the loyalty on the partial refund to be processed correctly, it is recommended to fully refund the order and create a new order with the updated order details.
\n
\n
\n\n
\n
\n
\nStacking of multiple Olo Loyalty rewards are not supported
Please note that the Toast UI allows applying multiple Olo Loyalty rewards to an order but if you try to place the order with multiple rewards applied, an error message is displayed and the applied rewards are removed. A reward will have to be re-applied before placing the order.
\n
\n
\nHandling of Combo Menu items: When a combo menu item comprising of other items in the menu is created,
\n
The combo item price is attached with the main combo item and all sub items prices are all rolled up into the combo.
\n
The item based reward can be created based on the Combo item name.
\n
Individual items within the combo and their prices do not come into Olo Loyalty from Toast separately and hence do not show up in the Dashboard receipt.
\n
If an item based reward is defined on a menu item, the reward is applicable only when the item is on the order individually, not when it is part of the Combo.
\n
\n
\n
\nHandling of priced modifiers
\n
The price of any priced modifier is not rolled up into the price of the main item. The main item and the modifier prices come into Olo Loyalty from Toast separately.
\n
Toast does not allow any priced modifier to be added to the item free of cost.
\n
\n
\n
\nDouble counting of transactions when Olo Loyalty integration is enabled both in StoreFront and Toast POS at the location.
\n
The order sent by Storefront and Toast have different orders IDs and hence gets created as separate orders in Olo Loyalty. This is the default behavior.
\n
As of now, only Member orders are supported in the Storefront integration. When the same orders come through from Toast, it comes in as a Guest orders. So, even thought order is counted and shows in the Olo Loyalty Dashboard twice, this does not result in double awarding of points to the Member (Unless the Member actually also goes into the Member portal and make a loyalty claim on the Toast receipt).
\n
However, since the orders are counted twice - this causes over-reporting of sales and orders counts.
\n
\n
\n
\nDiscount Code:
\n
\n
\n
\n
When the location specific discount code set up in Toast, If the discount code is not correctly mapped in Olo, it will result in the below error showing up when the Order is placed from Olo.
\n
This error needs to be reported to Olo.
\n
\n
\n
\nSteps for Exporting the Item Ids from Toast: If Olo Loyalty is configured to use Item Ids instead of Item names, the Item Ids can be exported from Toast using the steps below.
\n
\nOrder ID Format:
\n
By default, Toast orders show up with a short (1-4 digits) ID. The short IDs are not unique to Toast. However, you can identify it as a Toast order by opening the Receipt View and looking up the “ReferenceID” in the GUID format, as shown below.
\n
If the “Use Toast Order GUID as Olo Loyalty Order Id” is set then all orders show with the Toast GUID.
\n
\n
\n
\n4. Integration Setup
\n4.1 Requirements
\n
Ensure Toast and Olo Loyalty accounts are fully set up. A Olo Customer Success Manager will inform you when your Olo Loyalty account is ready to enable loyalty with Toast.
\n
If migrating from Toast Loyalty or any other third party loyalty vendors to Olo Loyalty, ensure all locations in the Toast Loyalty group are ready to migrate.
Toast does not allow different locations within the Loyalty group to have different loyalty vendors.
\n
\n
Ensure that there are no unpublished changes in the Toast Admin Portal.
\n
\n
If using Olo or Bbot for online ordering:
\n
Ensure that the Toast integration is enabled on Olo or Bbot.
\n
Ensure that the discount code is setup in Toast and shared with Olo and Olo Loyalty.
If you have a requirement such as reopening closed order in Toast to make an update to the order (such as adding a tip to the order) review if enabling the “Use Toast Order GUID as Olo Loyalty Order Id” is required. Please refer to Section 2 above for more details on this setting.
\n
\n4.2 How to Enable the Integration\n
\n
As part of the Account setup or when ready to enable the integration, Olo Loyalty Integration team sets up the Loyalty POS API credentials in Olo Loyalty.
Olo integration team enables the “Use Toast Order GUID as Olo Loyalty Order Id” from the Olo Loyalty admin portal, if required.
\n
\n
Once Olo Loyalty confirms the account is setup, Merchant sends an email request to Toast and Olo Loyalty to enable the integration using the email template below.
Please note that this authorization applies to enabling Olo Loyalty for POS devices. for enabling Olo Loyalty for Online ordering, Toast currently require the request to be submitted separately from Toast admin portal. Please refer section 4.3 and follow the link to Toast documentation.
Authorization to Enable Spendgo Loyalty Integration
\n
\n
\n
I grant Toast permission to grant Olo Loyalty with API access to my Toast instance for the following locations:
\n
(list location names as they appear in Toast)
\n
\n\n
\n
\n
\n
\n4.3 Enabling Olo Loyalty for Toast Online orders\n
If enabling Olo Loyalty integration for online ordering, after following the above steps to enable the integration for In-Store orders, some additional step is needed. Please refer to the “Enable Third Party Loyalty on Toast Online Ordering Pro” section in Toast documentation.
\n4.4 If Disabling the Integration\n
Send an email request to Toast and Olo Loyalty to disable the integration using the email template below:
\n
\n
\n
Please note that this authorization applies to enabling Olo Loyalty for POS devices. for enabling Olo Loyalty for Online ordering, Toast currently require the request to be submitted separately from Toast admin portal.
I grant Toast permission to revoke Spendgo with API access to my Toast instance for the following locations:
\n
(list location names as they appear in Toast)
\n
\n\n
\n
\n
\n
\n
Toast Integration Support team enables/disables the integration and informs the Merchant and Olo Loyalty (integrations@spendgo.com, csm@spendgo.com) the Toast GUID of the locations that are enabled/disabled.\n
When the email is sent to integrations@spendgo.com, it automatically creates a Toast Central ticket. Olo Loyalty is copied on the ticket but has no access to the ticket to track all the updates happening on the Ticket.\n
\n
The integration team takes up to 5 business days to work on the ticket. Please note Toast cannot provide a specific time window for enabling the integration and this may happen any time during the day. If switching to Olo Loyalty from Toast or other third party Loyalty, plan accordingly.
\n\n
\n
If enabling the integration the Merchant maps the Toast GUID to the location from the Olo Loyalty Dashboard. If it is being disabled remove the mapping.
\n
Settings → Stores → Manage Edit
If this is Lab or the first location, Olo Loyalty CSM co-ordinates with the Merchant to run some tests to confirm the integration and the rewards are working as expected.
\n4.4 Quick validation steps after enabling the integration:
\n
Once the integration is enabled, it enabled the “Rewards” button on the POS. This is first step to validate that the integration is enabled.
\n
Once the integration is enabled, the order data starts flowing from Toast to Olo Loyalty, but the Loyalty is not processed in Olo Loyalty unless the Toast GUID is correctly mapped to Olo Loyalty Store location.\n
If the integration is enabled and location is mapped, the guest orders should start appearing in Olo Loyalty Dashboard.
\n
If the guest orders are not showing in the Dashboard,\n
Confirm that the “Rewards” button is enabled in the POS. If not, update the Toast Central ticket to let the Toast Integration support team know.
\n
If the Rewards button is enabled but no orders are showing in the Dashboard,\n
Confirm that the location is open and receiving orders.
\n
If the orders are being placed on the POS but it is not showing up in Olo Loyalty Dashboard,\n
Confirm that there are no unpublished changes in Toast Admin Portal.
A “Reward” button will show in the Toast POS when Olo Loyalty is enabled.
\n5.1.1 Looking Up the Loyalty Member
\n
\n
The below screenshots are created from the mobile phone and the actual layout on the POS may vary slightly.
\n
Option 1: Employee looks up Member by phone number on the POS
After ringing in the items and before payment, if the Member wants to make a loyalty claim, bring up the Loyalty Lookup window by clicking on “Rewards” → “Lookup Customer”
Option 1A: Enter the 10 Member’s 10 digit Phone number in the “Key In or Scan” field and then tap “Done”
OR
Option 1B: Tap on the “Lookup” button and enter the Member’s 10 digit Phone number in the “Search Phone #” field and then tap “Done” and then review the returned Member and tap on the listed Member and tap “Done”
If a Member for the entered 10 digit phone number does not exist in the Olo Loyalty network, a “Starter” Member is created and displayed. Starter Members can begin earning points immediately.
For full membership benefits, such as eligibility for certain rewards or rewards redemption, brands may require the Member to complete registration.
\n
3b. If a non 10 digit number then an error message is displayed. Phone number will have to corrected in order to complete the lookup.
Review the Member details, click on the listed Member, and click “Done.”
Option 2: Member scans a QR Code in a Mobile Pass or App
If a QR Code is made available to a Member in the Mobile App or via a Mobile Pass, the Member can scan the QR Code to make the loyalty claim.
\n
\n
Previously we required the QR code to contain the Member’s 10 digit Phone number for the Option 2A and the Olo Loyalty Member ID for the Option 2B below. As of 07/29/2025, both options 2A and 2B require the QR code to contain Phone number.
\n
2A) Scan using the barcode reader device
After ringing in the items and before payment, if the Member wants to make a loyalty claim, bring up the Loyalty Lookup window by clicking on “Rewards” → “Lookup Customer” and then scan the QR Code.
\n
It will present the Member detail window, as shown above.
\n
Click on the listed Member, then click “Done.”
\n
2B) Scan using the POS Device's Camera-
After ringing in the items and before payment, if the Member wants to make a loyalty claim, bring up the Loyalty lookup window by clicking on “Rewards” → “Lookup Customer” and click on “Scan” to bring up the scanner, then ask the Member to scan.
Click on the listed Member, then click “Done.”
\n5.1.2 . Applying the loyalty reward
Once the Member is located, any reward available to the Member to apply on the order is listed in alphabetical order. Only rewards that can be applied to the transaction will appear in the list.\n
If it is an Item Level reward, the qualifying item must be present in the cart at this step to appear as a redemption option.
\n
If the Member wants to apply any of the rewards, click on “Redeem.”
\n
Only one Olo Loyalty reward can be applied per order.
\n\n
The reward is applied to the order and the updated order is displayed.
Please note that even though Olo Loyalty doesn’t support applying multiple rewards to the order, Toast UI does allow adding more than one reward to the order. However when trying to close the order, Toast notices that the Olo Loyalty is returning an error and so removes the applied rewards and keeps the order open. Reward will have to be looked up and applied again.
Complete the payment and close out the transaction.
\n5.1.3 . Removing an applied reward:
If the Reward needs to be removed click on the applied reward. In the Discounts panel the applied reward is highlighted. Click on the reward to remove it.
\n5.1.4. Adding additional non-Olo Loyalty discounts along with the loyalty rewards
An order can have additional non-Olo Loyalty discount(s) added to the order along with a Olo Loyalty reward. To add additional discount, follow the regular steps for adding non Olo Loyalty discount. i.e once order has items, click on the “Discount” button to bring up the discount panel and then select discount(s) to be applied.
Here is how the order looks after applying a Olo Loyalty reward and an additional discount.
\n5.1.5. Updating an Order after applying the reward:
The order can be updated after applying the reward. However when new items are added or removed, or because the order subtotal has changed, it is possible that either the applied reward is no more applicable or order qualifies for some different reward(s). So, before or after updating the order, remove the applied reward and after the order is updated do a fresh rewards look up.
\n5.1.6 Switching/Changing the reward:
If a reward needs to be changed, remove the applied reward and do a fresh rewards lookup.
\n5.1.7. Switching the Loyalty Member
Please note that once the Loyalty member is looked up, the Member is attached to the order. Order can be completed without applying any reward and the order is counted as a loyalty order and the order accrues loyalty points. There is no way to remove the Loyalty Member from the order once attached. However, if the Member needs to be changed, bring up the look up screen and click in the “Switch Customer” and re-enter the phone number.
\n5.1.8 Viewing all rewards available to the member
Please note that when the rewards are looked up after adding items to the reward, only the rewards applicable to the order listed. There may be some rewards that is available to the Member but does not show up because the order does not meet the requirements to qualify for some of the available rewards. If the Member wants to know all available rewards, it can be looked up by following the rewards look up flow (Step 5.1.1) without ringing any item in the order. In this scenario the rewards listed for viewing only and cannot be applied.
The listed rewards do not include:
\n
Any store specific reward that does not apply to the location the Member is at.
\n
Any Point Banking reward defined at higher points tier than the Member’s current points balance. For example if Member’s points balance is less than 100, only the Point Banking rewards defined at points tier less than 100 are shown. If the Member points balance is zero, then no Points Banking reward is shown.
\n
\n
\n
Even though the rewards can be looked up without adding items to the reward, it should be for looking up the rewards only. For applying the reward the rewards need to be look up again after adding items to the order.
\n
\n5.1.9 Processing Voids/Refunds:
Olo Loyalty does not support partial loyalty reversal or partial voids/refunds on a completed order. If a partial void/refund is processed on an order, any loyalty points or rewards are reversed as if it is a fully voided/refunded order. If a partial void/refund is needed, it is recommended to fully refund the order and begin a new order.
Select the Closed Check to Void/Refund.
Click on the available options (3 dots on the top right); select “Void Order” and click on the “Void” button.
Click “Void” on the “Confirm Void” window, then click “Done.”
\n5.2 Kiosk Flow\n
\n
On the Kiosk device, the Member taps the Start button and then adds items to the order.
\n
Member taps on the “Rewards” button.
\n
The Member can select the “Phone number” as a look up type and then enter the Phone number on the lookup screen.
If there is a Mobile App available with the QR code, then the The Member can also choose the “Scan QR code” method.
\n
\n
The QR code should contain the Member’s 10 digit Phone number
\n
4. The Member will be presented with the rewards that are available to the Member for the order. A reward of choice can be applied to the order.
\n5.3 Online Ordering Flow\n
\n5.3.1 Sign In
Click on the “Profile” link and then Sign in by entering the Phone number followed by the one time passcode sent.
\n
\n
\n
Please note that the Phone OTP (One-Time Password) login process is managed entirely through Toast.For a successful sign-in:
\n
\n
A Toast customer profile must be available before the user attempts to sign in.
\n
There should also be a registered Member account in Olo Loyalty corresponding to that phone number.
\n
Upon successful Phone OTP sign-in, Toast retrieves the available rewards associated with that phone number.
\n
\n
\n
When the Sign In in successfully completed, the clicking on the “Profile” icon shows these options.
\n5.3.1 Rewards lookup and redemption
At the order checkout, click on the “Lookup My Rewards” button.
Review and apply a reward.
\n
\n
\n
Only one reward should be applied to the order.
\n
If you want to change the applied rward, remove the applied reward and select a different reward.
\n
You may initially see an “Loyalty Account not found” message even through a Olo Loyalty registered account exists with the Phone number, but page will refresh to show the reward.
A summary of the Olo Loyalty integration with Revel, including supported features and steps for setup.
About
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Revel POS is a based point of sale built on iPad backed by cloud based management tool.
\n
Launched November 2023
\n
Article Last Updated July 25, 2025
\n
Category POS
\n
\n
\n
\n
\nWhat’s Supported?
\n
\n
\n
\n
\n
\n
\n
\n
\n
Feature
\n
Supported
\n
Not Supported
\n
\n\n
\n
Revel Ordering Channels
\n
Revel POS and integrated Customer Display System (CDS)**
\n
\n
Revel Online Ordering
\n
Drive Through
\n
Self Service Kiosk
\n
\n
\n
\n
Olo Loyalty Features
\n
\n
Look up by Phone number
\n
Accrue points for loyalty claimed orders
\n
Claim receipt to accrue points for orders not claimed at the store
\n
Redeem Olo Loyalty offers/rewards***
\n
Combine Olo Loyalty rewards with non-Olo Loyalty rewards
\n
Loyalty reversal on refunded order****\n
\n
\n
\n
Look up by email or Loyalty ID.
\n
Member registration through Revel CDS.
\n
\n
\n
\n
Base Program Types
\n
Points Banking
\n
Shop with points
\n
\n
\n
Basket Level Rewards/Offers Types
\n
\n
$ Discount (Rebate)
\n
% Discount (Discount)
\n
Bonus Points
\n
\n
\n
\n
\n
Item Based Rewards/Offers Types
\n
\n
BOGO
\n
Free Item
\n
$ Discount
\n
% Discount
\n
Bonus Points
\n
Price Adjustment
\n
\n
\n
\n
\n
Rewards shown for selection
\n
\n
When the Member rewards are looked up after adding items to the order, all rewards available to the user are listed. The rewards are categorized into -
\n
Rewards applicable to the order
\n
Rewards that are available but not applicable to the order
\n
\n
\n
If the Member is looked up without adding any items to the order, then all available rewards are listed as available but not applicable.
\n
After applying a reward if the order is changed, the applied reward is removed. The rewards will have to be re looked up and reviewed for applying.
\n
\n
\n
\n
\n
Discount code requirement
\n
\n
No discount code setup needed in Revel for enabling the Olo Loyalty integration with the POS.
\n
Discount code may needs to be setup in Revel and associated with the loyalty rewards while enabling Loyalty on other ordering platforms (such as Olo, Bbot) that connects with Revel POS. Steps for setting up any such discount code in Revel is not covered in this document.
\n
\n
\n
\n
\n
Third Party Online and In-Store Ordering Platforms
** POS App version 2.79 or higher and CDS XT 2.79 or higher is required.
*** Only one Olo Loyalty reward can be applied to the order. Rewards stacking is not supported. However non Olo Loyalty discount/coupons can be applied along with Olo Loyalty reward.
\nThings to Know
\nModifiers:
\n
For items that have the price set at the “Size” modifier level, (as shown in the example below), there are some limitations you need to consider if the qualifying items are configured by Item name.\n
\n
For example, for the item shown below reward such as a “Free Latte” or a “Free Large Latte” cannot configured. This is because when a “Latte - Large” is added to the order the order look like this
\n
\n
So, if the reward is set at “Latte” then because item price is $0 the reward is not applicable. If turn on the “Sum Parent & Modifiers for Qualified Item Discount” setting on the reward, then it will qualify all sizes not just the “Large” size.
b) Reconfigure the menu with each size listed separately, such as “Latte - Small: $10, Latte - Medium: $11, Latte - Large : $12).
\n
\nSupport for Voids/Refunds: This is what happens to loyalty on the order after a closed order is reopened and modified in the POS.
\n
\n
\n
\n
Action
\n
Loyalty Processing
\n
\n\n
\n
Order is fully refunded
\n
\n
Loyalty on the order is revered.
\n
\n
Points accrued on the order is reversed
\n
Any loyalty reward applied to the order is added back to the Member’s balance
\n
\n
\n
\n
\n
Order is partially refunded
\n
\n
Partial loyalty reversal is not supported in Olo Loyalty. Partial refund is also treated same way as the full refund.
\n
In order to keep the loyalty on the partial refund to be processed correctly, it is recommended to fully refund the order and create a new order with the updated order details.
\n
\n
\n
\n
Order is updated
\n
\n
Any further loyalty update on a closed order is not supported in Olo Loyalty.
\n
In order update the loyalty on the order, it is recommended to void the order and create a new order with the updated details.
\n
\n
\n\n
\n
\nQR code requirement for scanning on the CDS:
Members can make loyalty claim by entering the phone number on the CDS. Olo Loyalty does not provide a loyalty card to scan. However if the Merchant wants to support scanning by QR Code from the Mobile App, the QR code should contain the Member’s 10 digit phone number (only the numbers such as 444444444 without the county code).
\n
Order ID Format
All Member or guest orders placed from Revel POS usually show up with numeric order ID such as 123456 that matches with the order ID printed on the receipt . Only known exception is when the order is placed offline. For order placed online the order ID shows up with a suffix such as 123456-75843290890
Notes about the order receipt on Olo Loyalty Dashboard
Please note that the receipt view of the order in Dashboard does not fully match with the customer receipt generated by Revel.
\n
\nReceipt Subtotal:\n
TheSubtotal shown on the Dashboard receipt matches with the Subtotal on the Revel receipt.
\n
Revel’s subtotal reflects the sum of line items and not the applied rewards/discounts/coupons.
\n
Also note that the points accrued on the order does not always match with the subtotal. This is because Olo Loyalty does not compute points based on the receipt subtotal but based on the sum of prices of only those items that are marked as qualifying for the loyalty.
\n\n
\n
\nReceipt Total:\n
\n
The Total shown on the Dashboard receipt matches with the Total on the Revel receipt. However, it may not tally with the other numbers (line item prices, subtotal, Tax etc.) on the receipt. Receipt total reflects the sum of line item prices including modifiers + Tax + Tip + other charges minus the applied rewards/discounts. However the dashboard receipt does not show the tips, service fee, and other charges and non-Olo Loyalty discount/coupon details.
Steps for Exporting the Item IDs from Revel: If Olo Loyalty is configured to use Item IDs instead of Item names, the Item IDs can be exported from Revel using the steps below.
\n
\n
Please use the Barcode as the Item ID for setting up qualifying items.
\n
On the Revel Management Console, navigate to Import/Export → Products → Advanced Filter → Add “Id” as the extra field.
It exports an excel file, The file looks like below. The Item IDs are in the “ID” field.
\nIntegration Setup
\nRequirements
\n
Olo Loyalty integration can be enabled by individual location in Revel. We recommend that if the Revel test lab is available, the integration is enabled and tested at the lab before rolling out to other locations.
\n
If already using Revel POS, check if any of the devices running at the location(s) are on Revel POS App version 2.78 or lower, if so, make sure all devices are upgraded to latest version. If any of the CDS devices are running version 1.0, upgrade it to latest version of CDS XT to take advantage of the customer facing experience.
\n
To check the versions, from the Revel Management Console click on the “Establishment” tab and click on “Version Information”. Contact Revel support to upgrade the POS and CDS versions.
\n
If Revel POS being setup new, make sure that POS setup is completed and tested before enabling Olo Loyalty.
\n
Please note that Olo Loyalty integration is not available with Revel online ordering. If the Revel is integrated with a supported online ordering system such as Olo, make sure that online ordering is fully setup and functional.
\n
Make sure that the Olo Loyalty merchant account, loyalty program and the rewards are setup.
Please note that if Olo is the online ordering, a discount needs to be setup in Revel management system for the Olo integration and Olo Loyalty rewards need to be associated with the discount ID. Please contact your Olo support representative for assistance in creating discounts and what should be mapped to Olo Loyalty for the Discount Code.
\n
\n
\nHow to Enable the Integration\n
\nStep 1.Confirm the location(s) is ready for setting up the integration.\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Identify the locations to enable the Olo Loyalty Integration.
\n
\n
\n
Procedure
\n
\n
Review the requirements mentioned above and confirm the location(s) is ready for enabling Olo Loyalty Integration
\n
Inform Olo Customer Success Manager (CSM) the list of locations that needs to be enabled.
Authorization from the Merchant to enable the integration
\n
\n
\n
Procedure
\n
\n
Co-ordinate with the Merchant the date and time for setting up the integration.
\n
Evaluate if there is any testing required after the integration.
If any testing is required, setup the testing time.
\n
\n
If the integration has not already been enabled for any of the Merchant locations\n
Obtain the Merchant contact to whom the Olo Loyalty API credentials be sent to.
\n
Instruct the Integrations team to setup and share Olo Loyalty API credentials with the Merchant.
\n\n
\n
\n
\n
\n
Data to share
\n
Share with the integration team Merchant contact (Email ID) to whom the API credentials should be sent.
\n
\n
\n
Outcome
\n
\n
The time slot for enabling the integration is setup with the Merchant.
\n
Working session is setup with the Merchant for testing, if required.
\n
Instructions sent to the integration team, if required.
\n
\n
\n\n
\n
\nStep 3: Olo Loyalty Integration team shares API credentials with the Merchant\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Olo Loyalty Integration
\n
\n
\n
Required Input
\n
Authorization from CSM and the Merchant contact to send the credentials to.
\n
\n
\n
Procedure
\n
\n
If the credentials are already not shared with the Merchant,
\n\n
Setup the Loyalty POS API keys in Olo Loyalty Admin portal.
\n
Add the API Key and secret to the Merchant config in Olo Loyalty Admin portal.
\n
Share the API credentials securely in a 1Password link with the Merchant contact
\n\n
Refer to internal documentation for detailed instructions.
\n
\n
\n
\n
Data to share
\n
\n
Include the below information in the 1password secure note.
\n\n
Base URL
\n
X-Class-Key
\n
X-Class-Secret
\n\n
\n
\n
\n
Outcome
\n
API credentials mentioned above are shared with the Merchant
\n
\n\n
\n
\nStep 4: The Merchant enables the integration from the Revel Management Console\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Olo Loyalty API Keys
\n
\n
\n
Procedure
\n
\n
The integration is setup location by location. For setting up a location follow the below steps.
\n
Revel Management Console Steps
\n\n
Login to Revel Management console and select switch to the location (Establishment).
\n
Please note down the establishment ID. This will be needed for mapping to Olo Loyalty location in the Olo Loyalty Dashboard.
\n
Click on the settings tab and search for “open loyalty”. Click the check box next to “Open Loyalty” and then click on “Configure Now”
\n\n
On the Open Loyalty Configuration Window, select “Olo Loyalty” from the Provider dropdown and enter the base url, X-Class-Key and X-Class-Secret shared by Olo Loyalty Integration team in the secured 1Password link. Leave default settings for all other fields.
\n
\n
Click Save.
\n
Reopen the Open Loyalty Configuration and confirm that the integration shows as enabled.
\n\n
\n
Olo Loyalty Dashboard step
\n\n
Login to Olo Loyalty Dashboard.
\n
Navigate to Settings → Stores and open the location for edit.
\n\n
3. Enter the Revel establishment ID in the “Revel Store Id” field and click on save changes.
\n
\n
\n\n
\n
\nStep 5: Refresh all the POS stations at the location\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Procedure
\n
Refresh all the Revel POS stations at the location. The integration does not get enabled until the POS stations are refreshed.
\n
\n
\n
Outcome
\n
Integration should be enabled after this step.
\n
\n\n
\n
\nStep 6: Quick Validation\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Procedure
\n
\n\n
If this is the lab or the first location, Olo Loyalty CSM may setup a working session to test and confirm that the integration is working as epxcted.
\n
Otherwise, after the integration is enabled, confirm that the Loyalty Lookup option shows up in the POS station(s).
\n\n
\n
Tap on the “Loyalty Lookup” button and look up by a 10 digit US phone number.
\n
If the Loyalty lookup button does not show up or the Member look up comes back with an error message, contact Olo Customer Success Manager.
\n\n
\n
\n\n
\n
\nHow to Disable the Integration\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Procedure
\n
\n\n
Inform Olo Customer Success Manager indicating the location(s), date and time.
\n
To disable the integtation\n
Login to Revel Management Console and open the location
\n
Click on the settings tab and search for “open loyalty”. Click the check box next to “Open Loyalty” and then click on “Configure Now”
A summary of the Olo Loyalty integration with Qu, including supported features and steps for setup.
About
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Qu is a restaurant management software company providing on-site and off-prem ordering and management platform. The point of sale system is built on the Windows PC.
\n
Launched September 2022
\n
Article Last Updated February 2024
\n
Category POS ONLINE ORDERING
\n
\n
\n
\n
\nWhat’s Supported?
\n
\n
\n
\n
\n
\n
\n
\n
\n
Feature
\n
Supported
\n
Not Supported
\n
\n\n
\n
Qu Ordering Channels
\n
\n
Qu POS**
\n
Qu Online Ordering
\n
API support for mobile Apps
\n
Kiosk
\n
\n
Drive Through
\n
\n
\n
Olo Loyalty Features
\n
\n
Look up by Phone number
\n
Accrue points for loyalty claimed orders
\n
Claim receipt to accrue points for orders not claimed while ordering
\n
Redeem Olo Loyalty offers/rewards***
\n
Combine Olo Loyalty rewards with non-Olo Loyalty rewards
\n
Loyalty reversal on refunded order****
\n
Lookup by scanning the QR code that contains Member’s 10 Digit Phone No ++
\n
\n
Look up by email or Loyalty ID.
\n
\n
\n
Base Program Types
\n
Points Banking
\n
Shop with points
\n
\n
\n
Basket Level Rewards/Offers Types
\n
\n
$ Discount (Rebate)
\n
% Discount (Discount)
\n
Bonus Points
\n
\n
\n
\n
\n
Item Based Rewards/Offers Types
\n
\n
BOGO
\n
Free Item
\n
$ Discount
\n
% Discount
\n
Bonus Points
\n
Price Adjustment
\n
\n
\n
\n
\n
Rewards shown for selection
\n
\n
Upon looking up the Member after creating the order, only the rewards applicable to the order are shown.
\n
All available rewards can be looked up by looking up the Member without creating the order. The rewards listed at this stage are not redeemable.
\n
If the order changes, the rewards are not validated automatically. Rewards re-lookup is needed if the order changes. On the rewards lookup screen the rewards are not auto refreshed to reflect what’s applicable to the updated order. clock on “Reload Rewards” to refresh the rewards list.
\n
\n
\n
\n
Discount code setup
\n
\n
As part of the integration setup, Qu creates an Open $ discount in Qu, but there is no need to associate Olo Loyalty rewards with the discount code setup in Qu.
\n
An additional discount code may be needed if using a supported third party online ordering or third party in-store or payment platform integration which requires discount codes (such as Olo and Bbot). For Olo and Bbot the discount code needs to be associated with the Olo Loyalty rewards. Please refer to Vendor’s documentation for requirements about the discount code setup and mapping with Olo Loyalty rewards.
\n
\n
\n
\n
Third Party Online and In-Store Ordering Platforms
** Loyalty lookup is available at the cashier facing display only. Not available on customer facing display.
*** Only one Olo Loyalty reward can be applied to the order. Rewards stacking is not supported. However non Olo Loyalty discount/coupons can be applied along with Olo Loyalty reward.
**** Loyalty on the entire order is reversed even if the order is refunded partially.
++ The lookup screen needs to be opened first before scanning.
\nThings to Know
\n
\nSupport for Voids/Refunds:
\n
When an order is fully or partially refunded, the points accrued on the order will be canceled and any loyalty rewards applied will be added back to the Member’s account.
\n
If a partial refund is to be processed, we recommend refunding the entire order and creating a new order.
\n
\n
\n
\nRewards Stacking
Only one Olo Loyalty reward can be applied to a order. Reward stacking is not supported. However, non Olo Loyalty rewards can be applied along with the Olo Loyalty rewards.
\n
\n
\nChanging the order after the loyalty lookup on the POS
A Loyalty member is attached to the order and rewards applicable to the order are fetched. If the order is changed, that may impact the applicable rewards. But when the rewards screen is brought back by clicking on the “Loyalty Rewards” button again, the rewards list is not automatically refreshed. Reward list needs to be refreshed by clicking on the “Reload Rewards” button.
\n
\n
\nKnown issue with priced Modifiers: In Qu, it is possible to configure a priced item to be set up as a free add-on to another item.For such items, currently the price of the main item and the priced add-on both are getting counted and results in over awarding of the loyalty points. For example Olo Loyalty Dashboard receipt shown below, “Lava Ranch” has an item price of $1. However, one quantity of “Lava Ranch” is allowed to be added to “Sunrise Burrito” free. But because the data sent from Qu POS to the Olo Loyalty integration API has the $1 price for “Lava Ranch”, the item price gets counted as $7.99 + $1 = $.8.99 and so an extra loyalty point is awarded. This is a known issue at this time and and fix for this will be COMING SOON.
\nOrder ID Format
\n
All Member or guest orders placed from Qu POS usually show up with numeric order ID such as 1001 that matches with the order ID printed on the receipt.
\n
Qu Online orders have longer number IDs such 240227161755877 as that matches with the order receipt sent to the member by email.
\n
\n
\n
Notes about the order receipt on Olo Loyalty Dashboard
\n
\nReceipt Subtotal :\n
TheSubtotal shown on the Dashboard receipt matches with the Subtotal on the Qu receipt.
\n
Qu’s subtotal reflects the sum of line items and not the applied rewards/discounts/coupons.
\n
Also note that the points accrued on the order does not always match with the subtotal.This is because Olo Loyalty does not compute points based on the receipt subtotal but based on the sum of prices of only those items that are marked as qualifying for the loyalty.
\n\n
\n
\nReceipt Total:\n
\n
The Total shown on the Dashboard receipt matches with the Total on the Qu receipt. Receipt total reflects the sum of line item prices including modifiers + Tax + Tip minus the applied rewards/discounts.
\nIntegration Setup
\nRequirements
\n
Olo Loyalty integration can be enabled location by location in Qu. We recommend that if the Qu test lab is available, the integration is enabled and tested at the lab before rolling out to other locations.
\n
If the Qu is being setup new, make sure that POS/Online setup is completed and tested.
\n
If the Qu is integrated with a supported online ordering system such as Olo, make sure that online ordering is fully setup and functional.
\n
Make sure that the Olo Loyalty account, loyalty program and the rewards are setup.
Please note that if Olo is the online ordering, a discount needs to be setup in Qu management system and Olo Loyalty rewards need to be associated with the discount ID.
\n
\n
\n
\n
Qu production is hardcoded to connect with Olo Loyalty production and likewise for Qu staging to Olo Loyalty Sandbox. For dong the testing with Olo Loyalty Sandbox in the lab store, the POS in the lab store should be connected to Qu Sandbox.
\n
\nHow to Enable the Integration\n
\n
Once all the above setup is ready inform Olo Customer Success Manager and the Qu account manager to enable the integration and indicate the locations.
\n
Olo Loyalty shares the POS, Online and oAuth API credentials with Qu.
Internal note to Olo Loyalty Integrations team: Online and oAuth API credentials are required even when only POS integration is required.
\n
\n
If enabling the lab or the first location, Olo Loyalty customer success manager will co-ordinate integration testing.
\n
\nHow to Disable the Integration\n
\n
Inform Olo Customer Success Manager and the Quaccount manager to disable the integration and indicate the locations.
\n
Qu and Olo Loyalty will work together to disable the integration.
\n
\nLoyalty Flow - POS
\nLoyalty Member Lookup:
Loyalty member look up and reward redemption is supported on the cashier device.
To lookup the reward, after ringing in the items for the check, on the Payment screen click on “Loyalty Rewards” button.
Look up is supported by phone number. Look up by email or QR code is not supported.
\n
\n
\n
The look up by scanning the QR code is supported. QR code should contain Members 10 Digit phone number. Currently, in order to scan the QR code, the look up screen shown above needs to be brought up first. i.e, after bringing up the look up screen, phone number can be entered manually or a QR code can be scanned.
\n
Qu is working on an enhancement to support QR scanning at any point during the Order flow. When that is implemented, the lookup screen the look up happens automatically and look up screen opens up to show the available rewards.
\n
\n
\nApplying the loyalty reward
When looked up the rewards applicable to the order is fetched and listed. If the member does not exist or there is no qualifying reward available, the list will be empty. Order can be completed without applying a reward. To apply a reward click on reward from the list.
When the reward is applied, the the check updates to show the applied reward. Complete the payment to redeem the reward.
If the order needs to be changed, after the look up or after applying the reward, on the payment screen click on the “Loyalty Rewards” and click on “Reload Rewards” to refresh the rewards available to the updated order.
For detaching the Member from the order, click on “Remove Customer from Check”
A non Olo Loyalty discount can be applied to the order along with the Olo Loyalty rewards using the “Discounts” button.
\nProcessing Voids/Refunds
Follow the regular refunding process for refunding the Loyalty order. Please note even if the order is refunded partially the loyalty on the order is fully reversed. If a partial refund is to be processed, we recommend refunding the entire order and creating a new order.
\nLoyalty Flow - Online ordering
\nMember login:
When Olo Loyalty Integration enabled for Qu online ordering, the login on the online ordering site is handled by Olo Loyalty oAuth. Click on the Profile icon and login. Olo Loyalty registered member can login using the Olo Loyalty Credentials.
\n
For registering as a new member, click on “Create Account” link, submit the registration form and complete the email validation.
\n
After login, clicking on the profile icon shows the profile details.
\n
\nApplying the Reward:\n
\n
Add item to the cart and checkout.Av
\n
Rewards available to the Member is validated against the order and listed for redemption. The Member’s available points balance is also displayed.
\n
\n
Click on “Apply” button next to the reward to apply the reward. The cart is updated to show the applied reward and the “Apply” button changes to “Remove”. Other rewards are disabled in the list because only one Olo Loyalty reward can be applied.
\n
Once applied the reward can be removed by clicking on the “Remove” button. Once the Reward is removed, all rewards are enabled in the list. To change the reward, remove the applied reward and apply a different reward.
\n
click on Make a payment and complete the order.
Guest Orders:
Orders placed online without logging come in guest order.
A summary of the Olo Loyalty integration with POSitouch, including supported features and steps for setup.
About
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
POSitouch point-of-sale software solution was designed by restaurant operators for restaurant operators. It’s built on the Windows OS integrated with Olo Loyalty via Fishbowl’s Promotions Manager Application.
\n
Launched October 2021
\n
Article Last Updated February 2022
\n
Category POS
\n
\n
\n
\n
\nWhat’s Supported?
\n
\n
\n
\n
\n
\n
\n
\n
\n
Feature
\n
Supported
\n
Not Supported
\n
\n\n
\n
Ordering Channels
\n
POSitouch POS (versions 5.34 or higher)
\n
Customer Facing display
\n
\n
\n
Loyalty features
\n
\n
Accrue points for loyalty claimed orders
\n
Claim receipt to accrue points for orders not claimed at the store
\n
Redeem Olo Loyalty offers/rewards
\n
Combine Olo Loyalty rewards with non-Olo Loyalty rewards
\n
Loyalty reversal when order is refunded.
\n
\n
\n
\n
\n
Base Program Types
\n
Points Banking
\n
Shop with points
\n
\n
\n
Basket Level Rewards/Offers Types
\n
\n
$ Discount (Rebate)
\n
% Discount (Discount)
\n
Bonus Points
\n
\n
\n
\n
\n
Item Based Rewards/Offers Types
\n
\n
BOGO
\n
Free Item
\n
$ Discount
\n
% Discount
\n
Bonus Points
\n
Price Adjustment
\n
\n
\n
\n
\n
Rewards shown for selection
\n
\n
Rewards are not shown for selection. The available reward expiring soonest will automatically be applied to the order.
\n
\n
\n
Discount code requirement
\n
\n
A discount code needs to be setup in POSitouch Management Console as part of integration setup, however it is not required to be associated with the Olo Loyalty rewards.
\n
A separate discount code may be required for integrating online ordering platform with POSitouch and for the rewards enabled for Online ordering that discount code may have to be associated.
\n
\n
\n
\n
\n
Online and In-Store Ordering Platforms
\n
Olo
\n
\n
\n\n
\n
\nThings to Know
\n
\nPrerequisites:
\n
Operating system
Windows 10 or comparable Windows OS with .NET Framework prerequisite Please contact your Fishowl PM provider to their latest OS requirements.\n
\n
\n
POSitouch v.5.34 or higher
\n
POSitouch Loyalty License (highly preferred approach) or POSitouch Gift License (this will reduce functionality with non-unique codes)
\n
Available POSitouch TranServ channel
\n
Available Card Range under User Defined CC in POSitouch Back Office Setup
\n
\n
\n
Persistent internet connection.
\n
\n
\n
\nReward redemptions: When a member lookup is done and the member has multiple rewards available at the store location of their order, the reward expiring soonest will automatically be applied to their order. There is no option to view or select from their available rewards. If a member does not have a reward, no reward is applied and the member will earn points as usual.
\n
\nVoids/Refunds: This is what happens to loyalty on the order after a closed order is reopened and modified in the POS.
\n
\n
\n
\n
\n
Action
\n
Loyalty Processing
\n
\n\n
\n
Order is fully refunded
\n
\n
Loyalty on the order is reversed.
\n
\n
Points accrued on the order is reversed
\n
Any loyalty reward applied to the order is added back to the Member’s balance
\n
\n
\n
\n
\n
Order is partially refunded
\n
\n
Partial loyalty reversal is not supported in Olo Loyalty. Partial refund is also treated same way as the full refund.
\n
In order to keep the loyalty on the partial refund to be processed correctly, it is recommended to fully refund the order and create a new order with the updated order details.
\n
\n
\n
\n
Order is updated
\n
\n
Any further loyalty update on a closed order is not supported in Olo Loyalty.
\n
In order update the loyalty on the order, it is recommended to void the order and create a new order with the updated details.
\n
\n
\n\n
\n
\nOrder ID Format
The order ID matches with the order ID printed on the receipt and typically starts with 1, 2, 3 and recycles after it reaches a configured limit (such as 4999, 9999).
Making a loyalty claim on a receipt : Olo Loyalty Members who do not make a loyalty claim on the order at the store, they can earn points by claiming the receipt from Member Portal.
Notes about the order receipt on Olo Loyalty Dashboard
\n
\nReceipt Subtotal:\n
TheSubtotal shown on the Dashboard receipt matches with the Subtotal on the printed receipt.
\n
Subtotal reflects the sum of line items and not the applied rewards/discounts/coupons.
\n
Also note that the points accrued on the order does not always match with the subtotal. This is because Olo Loyalty does not compute points based on the receipt subtotal, but based on the sum of prices of items marked as qualifying for points.
\n\n
\n
\nReceipt Total:\n
The Total shown on the Dashboard receipt matches with the Total on the printed receipt. Receipt total reflects the sum of line item prices including modifiers + Tax + Tip minus the applied rewards/discounts.
\n
The tax, tip or other charges are not shown on the receipt.
\n\n
\n
Modifiers details
\n
Modifier details are shown on the Member orders but not on the guest orders.
\n
Sample Guest order
\nLoyalty Flow
\nMember Lookup & Reward Redemption
The following steps are to be performed by a staff member on the POSitouch system. Please refer to your Fishbowl Promotions Manager Documentation for the latest updates.
\n
Open a new order.
\n
Enter the member’s order items.
\n
Click Member Lookup button.
\n
Enter the member’s (10-digit) phone number and click Next.
\n
Select the member for member to earn points on the order. If the member has an available reward to be redeemed at that store, the reward expiring soonest will automatically apply to the order.
* Focus POS does not allow multiple rewards applied on the same item. Item based Sprendo reward cannot mixed with a non-Olo Loyalty discount on the same item.
\nThings to Know
\n
\nSupport for Voids/Refunds:
\n
When an order is fully or partially refunded, the points accrued on the order will be canceled and any loyalty rewards applied will be added back to the Member’s account.
\n
If a partial refund is to be processed, we recommend refunding the entire order and creating a new order.
\n
\n
\n
\nRewards stacking: Olo Loyalty does not support applying multiple rewards to the order. However non Olo Loyalty rewards can be applied along with Olo Loyalty reward.
Focus allows only one discount applied to an item, so if the Olo Loyalty and Non-Olo Loyalty reward cannot be applied together if the discount is on the same item.
\n
\n
\nAvailable rewards shown at the lookup:
\n
When the cashier looks up the reward, all rewards that are available to the Member at the store location is displayed. This list is not validated against the order, so some rewards such as item specific rewards may not be applicable.
\n
When the reward is applied, it gets validated against the order and if it is not applicable then an error message is displayed.
\n
\n
\n
\nChanging the order/reward after applying the reward: If the order is modified after applying the order, then the applied reward may no more be applicable or the order may qualify for the new reward. However the reward is not automatically revalidated modified order. Rewards needs to be re-looked up and removed/changed if necessary.
\n
\nDiscount Code:
\n
For setting up the Olo Loyalty integration for Focus POS, a discount code needs to be setup in focus. However there is no need to associate this discount code with the Olo Loyalty rewards.
\n
Additional discount code may need to be setup and associated with Olo Loyalty rewards when a third party online ordering (such as Olo) or in store payment platform (such as Bbot) is integrated with focus.
Specifically with Olo, the discount code setup in Focus for Olo needs to be also setup as loyalty non qualifying line item in Olo Loyalty. Please refer to Olo Integration documentation for more details.
\n
\n
\n
\n
\nOrder ID format: The order from Focus POS show up in Dashboard with small 1-4 digit number.
\n
\nNotes about the order receipt on Olo Loyalty Dashboard: Please note that the receipt view of the order in Dashboard may not fully match with the customer receipt generated by Focus.
\n
\nReceipt Subtotal: TheSubtotal shown on the Dashboard receipt matches with the Subtotal on the Focus receipt which reflects the sum of line items and not the applied rewards/discounts/coupons.
The points accrued is not based on the subtotal but based on the sum of the prices of loyalty qualifying items.
\n
\n
\nReceipt Total: The Total shown on the Dashboard receipt matches with the Total on the Focus receipt which reflects Subtotal+ Tax + Tip + minus the applied rewards/discounts.
\n
\n
\nIntegration Setup
\nRequirements\n
Olo Loyalty Integration is enabled by the Merchant from myFocus. We recommend that if the Focus test lab is available, the integration is enabled and tested at the lab before rolling out to other locations.
\n
If theFocus POS is being setup new, make sure that POS setup is completed and tested.
\n
Make sure that the Olo Loyalty account, loyalty program and the rewards are setup.
\n
\nIntegration setup steps\n
\nHow to Enable the Integration\n
\n
Once the POS, Olo Loyalty account, loyalty program and the rewards are setup and integration is ready to be enabled, Olo Customer Success Manager will inform the Olo integration team to share the integration API credentials with the Merchant.
\n
Olo Loyalty integrations team shares the following details securely with the person designated by the Merchant to enable the integration.\n
Client ID (API Key)
\n
Shared Secret
\n
Store Codes
\n
Brand Id (Account Id)
\n\n
\n
Merchant sets up the integration from myFocus as follows
\n
Discount Setup: Add a new discount in myFocus.
\n
Name:
loyalty reward
\n
\n
Method
Item $
\n
\n
Item Selection
All Items
\n
\n
In the Options, check the following
\n
Active
\n
Include Modifiers
\n
Item $ Allocate
\n
\n
\n
Package Setup
Place package on any screens you wish to have loyalty accessible
Name: <Enter Desired visible name to staff>
Command = Olo Loyalty
System Setup
In Setup Navigate to Miscellaneous>Credit/Gift/Loyalty/Customer
\n
Gift Cards/Loyalty Tab
Loyalty Options
Type = Olo Loyalty
\n
\n
\n
Loyalty Direct Tab
\n
Client ID = <provided by Olo Loyalty>
\n
Shared Secret = <provided by Olo Loyalty>
\n
Store Code = <provided by Olo Loyalty>
\n
Brand (aka ACCOUNT ID) = <provided by Olo Loyalty>
\n
Discount
Map to Olo Loyalty Discount previously created
\n
\n
\n
\n
(Optional) Enabling force prompting for loyalty before payment
This depends on how the button/package and payment canvas is configured. The idea is to trigger Olo Loyalty before calling the payment canvas. Below instruction is provided for reference.
Call Olo Loyalty from All Payments button/package before calling the App Payments canvas containing all the payment options.
Disable CC Auto Recognize option to ensure they didn’t initiate tendering w/o using the All Payments button/package first.
\nLoyalty Flow
\nLoyalty Member Lookup
\n
Ring Items on Check or retrieve saved check
\n
Execute the OLO LOYALTY REWARDS package
\n
Enter Phone # on user lookup screen\n
If the Member exists in Olo Loyalty, the available rewards are retrieved and shown
\n
If the no Member exists matching the Customer Phone number, a new starter account is added in Olo Loyalty. Merchant will have to follow up with the Member to complete the registration process, if necessary.
\n\n
\n
\nApplying a reward\n
\n
After the Member Lookup, the rewards available to the Member is shown.\n
\n
To Apply a reward, select a reward to apply and click on “Redeem Reward”\n
If no reward is to be applied, close the window by clicking on the X at the right corner. The Member is still attached to the order and will accrue points.
\n
If the reward not applicable, an error message showing why the reward cannot be applied is displayed. The window remains open to allow selection of a different reward.
\n
If the reward is applicable to the order then the window closes and the order is updated.
\n\n
\n
\nRemoving Reward \n
\n
Select Reward line below Subtotal
\n
Press Delete
\n
\nRemoving User\n
\n
Select User
\n
Press Void
\n
\nClosing Check\n
\n
Pay check as normal, when seat is fully paid the loyalty is processed on the order.
\n
If no loyalty member is attached to the order, then the order is saved in Olo Loyalty as “Guest” order.
\n
\nProcessing Payment Voids/Refunds\n
When payment is voided any member and loyalty reward will be reversed.
A summary of the Olo Loyalty integration with PAR Brink, including supported features and steps for setup.
About
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Brink POS from Partech is a cloud-based point of sale system built on the Windows OS.
\n
Launched March 2024
\n
Article Last Updated May 2024
\n
Category POS
\n
\n
\n
\n
\nWhat’s Supported?
\n
\n
\n
\n
\n
\n
\n
\n
\n
Feature
\n
Supported
\n
Not Supported
\n
\n\n
\n
PAR Ordering Channels
\n
\n
PAR Brink POS
\n
(Cashier Facing display only. Customer Facing Display is not supported)
\n
\n
\n
\n
Kiosk
\n
Digital Ordering
\n
\n
\n
\n
Olo Loyalty Features
\n
\n
Accrue points for loyalty claimed orders
\n
Claim receipt to accrue points for orders not claimed at the store
\n
Redeem Olo Loyalty offers/rewards
\n
Combine Olo Loyalty rewards with non-Olo Loyalty rewards
\n
Loyalty reversal when order is refunded.
\n
\n
\n
\n
\n
Base Program Types
\n
Points Banking
\n
Shop with points
\n
\n
\n
Basket Level Rewards/Offers Types
\n
\n
$ Discount (Rebate)
\n
% Discount (Discount)
\n
Bonus Points
\n
\n
\n
\n
\n
Item Based Rewards/Offers Types
\n
\n
BOGO
\n
Free Item
\n
$ Discount
\n
% Discount
\n
Bonus Points
\n
Price Adjustment
\n
\n
\n
\n
\n
Rewards shown for selection
\n
\n
\n
When the Member rewards are looked up after adding items to the order, only the rewards applicable to the order are displayed. This may not reflect the entire list of rewards that are available to the Member at the location because there may be a few rewards that do not qualify for the order.
\n
All rewards available to the Member at the location can be looked up by doing the Member look up when the order is empty. However when the order is empty, the rewards are listed as “view only” and cannot be applied.
\n
After applying a reward if the order is changed, the applied reward is removed. The rewards will have to be re looked up and reviewed for applying.
\n
\n
\n
\n
\n
\n
Discount code requirement
\n
\n
\n
A discount code is setup in Brink as part of enabling the POS integration, but there is no need to input a Discount Code when creating rewards or offers in the Olo Loyalty Dashboard.
\n
Discount code may needs to be setup in Brink and associated with the loyalty rewards while enabling Loyalty on other ordering platforms (such as Olo) that connects Brink POS. However, please note any discount code included in the reward setup would be numeric only. Brink does not support alphanumeric discount codes.
\n
\n
Please refer to the documentation of the Online Ordering platform for the steps to setup Brink discount code. Typically this involves setting up an Open $ discount in Brink as shown below. You can use an existing $ discount. We recommend that you create a new discount for reporting purposes.
\n\n
Log in to the Brink Admin Portal
\n
Click Configuration and then open the Settings Editor
\n
Click Discounts in the left-hand menu
\n
Click Add New Discount. Give the discount a name and save it with a default values. Please note that the below fields are required.
\n
Enter the following information:
\n
\nName: <Discount Name>
\n
\nType: Comp
\n
\nGranularity: Order
\n
\nMust Enter Amount: Enable this checkbox
\n
\nActive:Enable this checkbox
\n
\n
\n\n
\n
\n
Save and publish.
\n
Copy the ID and save it with the Online Ordering and Olo Loyalty.
\n\n
\n
\n
\n
Online and In-Store Ordering Platforms
\n
Olo
\n
\n
\n\n
\n
\nThings to Know
\nSupport for Voids/Refunds: This is what happens to loyalty on the order after a closed order is reopened and modified in the POS.
\n
\n
\n
\n
Action
\n
Loyalty Processing
\n
\n\n
\n
Order is fully refunded
\n
\n
Loyalty on the order is revered.
\n
\n
Points accrued on the order is reversed
\n
Any loyalty reward applied to the order is added back to the Member’s balance
\n
\n
\n
\n
\n
Order is partially refunded
\n
\n
Partial loyalty reversal is not supported in Olo Loyalty. Partial refund is also treated same way as the full refund.
\n
In order to keep the loyalty on the partial refund to be processed correctly, it is recommended to fully refund the order and create a new order with the updated order details.
\n
\n
\n
\n
Order is updated
\n
\n
Any further loyalty update on a closed order is not supported in Olo Loyalty API and may result in inconsistent result.
\n
In order update the loyalty on the order, it is recommended to void the order and create a new order with the updated details.
\n
\n
\n\n
\n
\nOrder ID Format:
Brink POS orders show up with a 12-14 digit numerical ID such as 9323073767425. This is a unique Order ID created by Brink and varies from Merchant to Merchant.
Notes about the order receipt on Olo Loyalty Dashboard
\n
\nReceipt Subtotal:\n
TheSubtotal shown on the Dashboard receipt matches with the Subtotal on the Brink receipt.
\n
Brink’s subtotal reflects the sum of line items and not the applied rewards/discounts/coupons.
\n
Also note that the points accrued on the order does not always match with the subtotal. This is because Olo Loyalty does not compute points based on the receipt subtotal, but based on the sum of prices of items marked as qualifying for points.
\n\n
\n
\nReceipt Total:\n
\n
The Total shown on the Dashboard receipt matches with the Total on the Brink receipt. Receipt total reflects the sum of line item prices including modifiers + Tax + Tip minus the applied rewards/discounts.
\nIntegration Setup
\nRequirements
Brink Requirements:
\n
POS Release 5.14 is needed. If any of the POS is running an older version, the Merchant should follow up with Brink support to get the POS version upgraded.
\n
If the Brink POS is being setup new, make sure that POS setup is completed and tested.
\n
Olo Loyalty integration can be enabled by individual location from the Brink Admin Portal. The Merchant contact needs to have access to Brink Admin Portal is needed for enabling the integration.
\n
We recommend that if the Brink test lab is available, the integration is enabled and tested at the lab before rolling out to other locations.
\n
Olo Loyalty Requirements:
Make sure that the Olo Loyalty Merchant account, loyalty program and the rewards are setup.
\n
\n
If you are switching to Olo Loyalty from Brink Loyalty, please note that all locations need to migrate from Brink Loyalty to Olo Loyalty. You cannot have few locations running Brink Loyalty and few other locations running Olo Loyalty.
\n
\nHow to Enable the Integration\n
\nStep 1. The Merchantconfirms the location(s) is ready for setting up the integration.\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
The locations to enable the integrations are identified.
\n
\n
\n
Procedure
\n
Review the requirements mentioned above and confirm the location(s) is ready for enabling Olo Loyalty Integration
\n
\n\n
\n
\nStep 2: The Merchant sends a request to PAR API support team to enable Generic Loyalty for the location\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Locations meet all the requirements.
\n
\n
\n
Procedure
\n
Send the request to Par API support team. (api.support@partech.com) and indicate the location(s).
\n
\n
\n
Data to share
\n
Location list to enable the integration.
\n
\n\n
\n
\nStep 3:PAR API support team enables the Generic Loyalty for the location\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
PAR API Support Team
\n
\n
\n
Required Input
\n
Authorization and the locations list from The Merchant.
\n
\n
\n
Data to share
\n
After enabling the locations, send the confirmation back to The Merchant.
\n
\n\n
\n
\nStep 4:The Merchant Informs Olo Loyalty CSM to initiate the integration setup\n
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Identify the locations to enable the Olo Loyalty Integration.
\n
\n
\n
Procedure
\n
\n
Inform Olo Customer Success Manager (CSM) the list of locations that needs to be enabled and if the Brink location name is not already shared at the time of initial setup, share the Brink location names.
\n
To find the location name to share:
\n
1a. Login to Brink Admin Portal. It brings up the Dashboard in the admin portal.
\n
1b. From the locations dropdown, select the location.
\n
1c. Copy the location name as shown, and strip off the asterisks ( * ) at the beginning and end. In the example shown below the location name is “***API-LAB-01***”, so the applicable part of the name after stripping off the *s is “API-LAB-01”
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Olo Loyalty CSM
\n
\n
\n
Required Input
\n
Authorization from the Merchant to enable the integration
\n
\n
\n
Procedure
\n
\n
Co-ordinate with the Merchant the date and time for setting up the integration.
\n
Evaluate if there is any testing required after the integration.
If any testing is required, setup the testing time.
\n
\n
From the Olo Loyalty Admin Portal, Map the Brink location code shared by the Merchant in step 4.
\n
If the integration has not already been enabled for any of the Merchant locations\n
Obtain the Merchant contact to whom the Olo Loyalty API credentials be sent to.
\n
Instruct the Integrations team to setup and share Olo Loyalty API credentials with the Merchant.
\n\n
\n
\n
\n
\n
Data to share
\n
Share with the integration team Merchant contact to whom the API credentials should be sent.
\n
\n
\n
Outcome
\n
\n
The time slot for enabling the integration is setup with the Merchant.
\n
Working session is setup with the Merchant for testing, if required.
\n
Instructions sent to the integration team, if required.
\n
\n
\n\n
\n
\n
\nStep 6: Olo Loyalty Integration team shares API credentials with the Merchant\n
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Olo Loyalty Integration Team
\n
\n
\n
Required Input
\n
Authorization from CSM and the Merchant contact to send the credentials to.
\n
\n
\n
Procedure
\n
\n
\n
Before starting, make sure that the the the “Brink Store ID” is mapped in the store configuration to match with the Brink location name shared Step (4). If it is not already configured, configure it.
\n
If the Brink location name is not available, follow up with the Merchant contact to set obtain it and configure it. Without this mapping the integration will fail, so if you are sharing the credentials without this mapping is in place, make sure that the Brink Store ID is mapped before the Merchant step (7).
\n
\n
If the credentials are already not shared with the Merchant,
\n\n
Setup the API keys in Olo Loyalty Admin portal
\n
Add the API Key and API secret to the Merchant config in Olo Loyalty Admin portal.
\n
Make sure that the Brink Store ID in the Store Configuration is mapped. If not, make sure that the Brink Store Id is mapped. This should be available in the Account Configuration sheet or obtain it from CS.
\n
Share the API credentials securely in a 1Password link with the Merchant contact. Include the below information in the 1password secure note.
\n\n
\n
End Point URL
\n
Api Key
\n
For each location - Store ID (Please note that this is what is mapped in the Brink Store Id field in step (3), not the Olo Loyalty Store Code.
\n
\n
Refer to internal documentation for detailed instructions.
\n
\n
\n
\n
Data to share
\n
API credentials and Store IDs with the Merchant in the secure 1Password note.
\n
\n
\n
Outcome
\n
Merchant has all information needed to setup the integration.
\n
\n\n
\n
\n
\nStep 7: The Merchant enables the integration from the Brink Admin Portal\n
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Olo Loyalty API Keys
\n
\n
\n
Procedure
\n
\n
The integration is setup location by location. For setting up a location follow the below steps in the Brink Admin Portal.
\n\n
Login to Brink Admin Portal and switch to the location.
\n
Olo Loyalty integration is implemented as Brink’s “Generic Loyalty integration”. So if the default Brink Loyalty integration is enabled, it should be disabled first. To do this, from the Brink Admin Portal, Open Configurations → Settings Editor, browse to Options → Loyalty. If it not already set to “None”, set it to “None”.
\n\n
\nAdd the Loyalty buttons in the Layout setup: At the payment step, in order for the cashier to be able to look up the loyalty member, look up and redeem available rewards etc.,
from the layout editor choose the right layout and add the following 3 buttons. These buttons may be already existing or may just need to be renamed. The example shown below is with the buttons added on the “Customer” panel.\n
Lookup Customer
\n
Redeem Rewards (or Redeem Offers)
\n
Clear Customer
\n\n
\n
\n
The example shown below is with the buttons added on the “Customer” panel. Please note that “Edit Customer” and “New Customer” button is not required.
\n
\n
\n
\n
\nIdentify/Setup a discount to be associated with Olo Loyalty: This could be an existing discount code or you can create a new one.
If creating a new discount (Configurations → Settings Editor → Discount → Add New Discount)make sure the discount has the configuration as per the below screenshot. If using an existing discount then open it and make sure that the configuration matches this.
\n
\n
\n
Name:
<Name of the discount>
\n
\n
Id
Automatically assigned by Brink
\n
\n
Printed Name
Loyalty $Discount
\n
\n
Type
Comp
\n
\n
Granularity
Order
\n
\n
Percent
100%
\n
\n
Max Items
Leave the default value
\n
\n
Max Amount
Leave the default value
\n
\n
Max Per Order
Leave the default value
\n
\n
Options: Check the following boxes:
\n
Active
\n
Must Enter Amount
\n
Loyalty Discount
\n
Allow Prior Discount
\n
Allow Later Discount
\n
Discounted Items Eligible
\n
\n
\n
\n\n
\nEnable the Olo Loyalty Integration from the Integration Portal:To enable the integration
\n
From the Brink Admin Portal, navigate to Configurations → Integration Portal
\n
Select the location and click on “Generic“
\n\n
\n
c. Setup the Integration as follows.
\n
\n
\n
Type:
Leave as “Generic”
\n
\n
Allow Brink Customer Usage
leave unchecked
\n
\n
Endpoint URL
Shared by Olo Loyalty Integration team in the 1Password note
\n
\n
Api Key
Shared by Olo Loyalty Integration team in the 1Password note
\n
\n
Store Code
Shared by Olo Loyalty Integration team in the 1Password note
\n
\n
\n
\nPublish Configurations: Finally, publish the configurations in Admin Portal so that configuration changes are pushed to the POS stations. Integration should be enabled on the POS stations after this step.
\n
\n
\n
\n
Outcome
\n
The integration setup is complete
\n
\n\n
\n
\n
\nStep 8: Verify the Integration\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Procedure
\n
\n
After setting up the integration, quickest way to check if the integration is working is to do the Loyalty Member look up. Please refer to the “Loyalty Member Lookup” in the “Loyalty Flow” section below.
\n
\n
If the “Lookup Customer” button is showing and brings up the customer lookup window when clicked, enter a 10 digit US/Canada phone number. If it results in an error then there is an issue with the integration. Please report to Olo Customer Success Manager and Olo Loyalty Integration team .
\n
If the basic validation is successful and if this is the first location (preferably the lab store) inform the Olo Customer Success Manager. Olo Customer Success Manager follows up with the Merchant to complete the testing.
\n
If this is not the very first location and the basic validation is successful, the completed orders should start showing up in Dashboard. Wait for a few orders to be completed on the POS stations inform the Olo Loyalty CSM. Olo Loyalty CSM can look up in the Dashboard that the orders are coming in and being processed correctly.
\n
\n
\n
\n\n
\n
\nHow to Disable the Integration\n
To Disable the integration, remove Generic Loyalty configuration from the Integration Portal.
\nLoyalty Flow
\nLoyalty Member Lookup
\n
Add items to the order
\n
Click on “Customer Lookup” and then click “Lookup Customer”
\n
Enter the 10 digit phone number and click on Done. Please note that only looking up by Phone Number is supported.
\n
If an invalid phone number is entered (for ex: it is not 10 digits) then a “There was an error processing the user lookup!” message displays.
\n
If is is an existing loyalty Member, among the rewards available to the user, the ones that are applicable to the order are displayed for selection.
\n
If if it is not an existing loyalty Member, a new “starter” Member is created. The Member will have to complete the registration process to become the “Registered” loyalty member.
\nApplying a reward\n
After the Member lookup, select the reward of choice from the rewards listed. The reward applies to the order and the updated order is shown.
Now close the order by completing the payment.
\nUpdating the check after applying the reward\n
If the order is to be updated after applying the reward, the applied reward may no more be applicable or the order may qualify for some additional rewards. So, the applied reward is automatically removed. Re-look up and review and apply the rewards again.
\nApplying non Olo Loyalty Discounts/Promo along with loyalty reward\n
\n
Please note that only one Olo Loyalty reward can be applied to the order. However, additional non Olo Loyalty discounts/promo can be applied along with loyalty reward.
\n
The order can have only one loyalty reward. It can also have only non Olo Loyalty Discount/promo(s) or Non-Olo Loyalty rewards can be added along with the Olo Loyalty reward.
\n
Olo Loyalty and non Olo Loyalty Discount/Promo can be added to the order in any order.
\n
In the below example, the Olo Loyalty reward is added to the order first. After applying the Olo Loyalty reward, click on the “Discount/Promo” button and select the discount to be applied.
\n
\nLoyalty Reversal on Refunds\n
Process the order refunds using the normal refund process in the POS. When the order is fully or partially refunded, any loyalty applied on the order gets reversed.
A summary of the Olo Loyalty integration with Oracle Micros Simphony 2, including supported features and steps for setup.
About
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Oracle Micros Simphony is a cloud-based point of sale system built on the Windows OS integrated with Olo Loyalty via Fishbowl’s Promotions Manager Application.
\n
Launched November 2023
\n
Article Last Updated April 2024
\n
Category POS
\n
\n
\n
\n
\n2. What’s Supported?
\n
\n
\n
\n
\n
\n
\n
\n
\n
Feature
\n
Supported
\n
Not Supported
\n
\n\n
\n
Ordering Channels
\n
\n
Micros Simphony 2 POS
\n
Supported POS versions - 19.1 and above
\n
\n
\n
Customer Facing display
\n
\n
\n
Olo Loyalty Features
\n
\n
Accrue points for loyalty claimed orders
\n
Claim receipt to accrue points for orders not claimed at the store
\n
Redeem Olo Loyalty offers/rewards
\n
Combine Olo Loyalty rewards with non-Olo Loyalty rewards
\n
Loyalty reversal when order is refunded.
\n
\n
\n
\n
\n
Base Program Types
\n
Points Banking
\n
Shop with points
\n
\n
\n
Basket Level Rewards/Offers Types
\n
\n
$ Discount (Rebate)
\n
% Discount (Discount)
\n
Bonus Points
\n
\n
\n
\n
\n
Item Based Rewards/Offers Types
\n
\n
BOGO
\n
Free Item
\n
$ Discount
\n
% Discount
\n
Bonus Points
\n
Price Adjustment
\n
\n
\n
\n
\n
Rewards shown for selection
\n
Only the rewards applicable to the order are shown for selection.
\n
\n
\n
\n
Discount code requirement
\n
\n
A discount code needs to be setup in Micros Simphony enterprise Management Console as part of integration setup, however it is not required to be associated with the Spendgo rewards.
\n
A separate discount code may be required for integrating online ordering platform with Simphony and for the rewards enabled for Online ordering that discount code may have to be associated.
\n
\n
\n
\n
\n
Online and In-Store Ordering Platforms
\n
Olo
\n
\n
\n\n
\n
\n3. Things to Know
\n
\nPrerequisites:
\n
Operating system
Windows 10 or comparable Windows OS with .NET Framework prerequisite Please contact your Fishowl PM provider to their latest OS requirements.\n
\n
\n
Micros Simphony 2 POS v.19.1 and above
\n
Micros SIM license
\n
Database user account with read-only access
\n
\n
\n
Persistent internet connection
\n
\n
\n
\nSupport for Voids/Refunds: This is what happens to loyalty on the order after a closed order is reopened and modified in the POS.
\n
\n
\n
\n
\n
Action
\n
Loyalty Processing
\n
\n\n
\n
Order is fully refunded
\n
\n
Loyalty on the order is revered.
\n
\n
Points accrued on the order is reversed
\n
Any loyalty reward applied to the order is added back to the Member’s balance
\n
\n
\n
\n
\n
Order is partially refunded
\n
\n
Partial loyalty reversal is not supported in Olo Loyalty. Partial refund is also treated same way as the full refund.
\n
In order to keep the loyalty on the partial refund to be processed correctly, it is recommended to fully refund the order and create a new order with the updated order details.
\n
\n
\n
\n
Order is updated
\n
\n
Any further loyalty update on a closed order is not supported in Olo Loyalty.
\n
In order update the loyalty on the order, it is recommended to void the order and create a new order with the updated details.
\n
\n
\n\n
\n
\nOrder ID Format
The order ID matches with the order ID printed on the receipt and typically starts with 1, 2, 3 and recycles after it reaches a configured limit (such as 4999, 9999).
Making a loyalty claim on a receipt : Olo Loyalty Members who do not make a loyalty claim on the order at the store, they can earn points by claiming the receipt from Member Portal.
Notes about the order receipt on Olo Loyalty Dashboard
\n
\nReceipt Subtotal:\n
TheSubtotal shown on the Dashboard receipt matches with the Subtotal on the printed receipt.
\n
Subtotal reflects the sum of line items and not the applied rewards/discounts/coupons.
\n
Also note that the points accrued on the order does not always match with the subtotal. This is because Olo Loyalty does not compute points based on the receipt subtotal, but based on the sum of prices of items marked as qualifying for points.
\n\n
\n
\nReceipt Total:\n
The Total shown on the Dashboard receipt matches with the Total on the printed receipt. Receipt total reflects the sum of line item prices including modifiers + Tax + Tip minus the applied rewards/discounts.
\n
The tax, tip or other charges are not shown on the receipt.
\n\n
\n
Modifiers details
\n
Modifier details are shown on the Member orders but not on the guest orders.
\n
Sample Guest Order
\n
Sample Member Order
\n4. Integration Setup
\n4.1 Requirements
\n
The Brand must have an account created in Olo Loyalty.
\n
The Brand’s store must meet the following pre-requisites and system requirements
\n
\nSupported Operating Systems: Windows 10 with .NET Framework
Port 12345 open on the Back Office server where the Fishbowl interface is to be installed (typically on the CAPS Server). This port is configurable if a different port is preferred.
\n
\n
\n
\n
\n
The Brand’s store must have at least one Simphony 2 POS version 19.1 up to 19.5 on location.
\n
Fishbowl Promotions Manager must be installed on the Simphony 2 POS at the location.
\n
\n4.2 How to Enable the Integration\n
\nStep 1. The Merchantconfirms the location(s) is ready for setting up the integration.\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
The locations to enable the integrations are identified.
\n
\n
\n
Procedure
\n
Review the requirements mentioned above and confirm the location(s) is ready for enabling Olo Loyalty Integration
\n
\n\n
\n
\nStep 2:The Merchant Informs Olo Loyalty CSM to initiate the integration setup\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Identify the locations to enable the Olo Loyalty Integration.
\n
\n
\n
Procedure
\n
Inform Olo Customer Success Manager (CSM) the list of locations that needs to be enabled.
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Olo Loyalty CSM
\n
\n
\n
Required Input
\n
Authorization from the Merchant to enable the integration
\n
\n
\n
Procedure
\n
\n
Co-ordinate with the Merchant the date and time for setting up the integration.
\n
Evaluate if there is any testing required after the integration.\n
If any testing is required, setup the test data by adding necessary points rewards to the Merchant contact’s Member account.
\n
Setup the testing time.
\n\n
\n
If the integration has not already been enabled for any of the Merchant locations instruct the Integrations team to setup and share Spendgo API credentials with Fishbowl.
\n
\n
\n
\n
Data to share
\n
\n
Share with the integration team
\n
Locations list
\n
\n
\n
\n
Outcome
\n
\n
The time slot for enabling the integration is setup with the Merchant.
\n
Working session is setup with the Merchant for testing, if required.
\n
Instructions sent to the integration team
\n
\n
\n\n
\n
\n
\nStep 4: Olo Loyalty Integration team shares API credentials with Fishbowl\n
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Spendgo Integrations Team
\n
\n
\n
Required Input
\n
Authorization from CSM and the Merchant contact to send the credentials to.
\n
\n
\n
Procedure
\n
\n
If the credentials are already not shared with Fishbowl,
\n\n
Setup the POS API key in Olo Loyalty Admin portal
\n
Share the API credentials securely in a 1Password link with the Merchant contact. Include the below information in the 1password secure note.\n
Merchant’s Account ID (Brand Id) in Olo Loyalty
\n
Account Name
\n
Environment: Olo Loyalty or skuped
\n
Store Codes for the requested Merchant locations in Olo Loyalty
\n
Olo Loyalty Integration API credentials.\n
Api Key
\n
Api Secret
\n\n
\n\n
\n\n
Refer to internal documentation for detailed instructions.
\n
\n
\n
\n
Data to share
\n
\n
API credentials and Brand ID and Store IDs with Fishbowl in the secure 1Password note with
Fishbowl has all information needed to setup the integration in their Admin Tools.
\n
\n\n
\n
\n
\nStep 5: Fishbowl client setup team sets up the integration in Fishbowl\n
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Fishbowl client Support Team
\n
\n
\n
Required Input
\n
API credentials shared by Spendgo
\n
\n
\n
Procedure
\n
\n
Follow the internal setup documentation to enable the integration from the Fishbowl Admin Tools.
\n
Follow up with the Merchant on installations (Fishbowl Promotions Manager, Fishbowl interface for Micros Simphony)
\n
\n
\n
\n
Data to share
\n
After the setup is complete. Respond to Spendgo’s email Spendgo sends to share the API keys (with cc to the Merchant and Spendgo CSM).
\n
\n\n
\n
\n
\nStep 6: Merchant sets up the integration from Micros Simphony Enterprise Management Console (EMC)\n
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Fishbowl completes the Admin Tools setup in Fishbowl.
\n
\n
\n
Procedure
\n
Follow the steps in the “EMC Setup” section in this documentation. If the Lab store is available, setup the integration with in the LAB store and test it before rolling out to other locations.
\n
\n
\n
Data to share
\n
After the setup is complete. Respond to email Olo Loyalty sent to share the API keys (with cc to the Merchant and Olo Loyalty CSM).
\n
\n\n
\n
\n
\nStep 7: Verify the Integration\n
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
After setting up the integration, quickest way to check if the integration is working is to do the Loyalty Member look up. Please refer to the “Loyalty Member Lookup” in the “Loyalty Flow” section below.
\n
\n
\n
Procedure
\n
\n
Attempt a Member look steps 1-4 in the “Loyalty Flow” section below.
\n
If the Member look up fails, there are multiple possible reasons.\n
Verify all the EMC verify steps.
\n
If all EMC steps are as per the documentation, take the screenshots of the EMC configuration, collect the Simphony logs from the device and report it to Spendgo Integrations (integrations@spendgo.com) and Fishbowl Client Support (clientsupport@fishbowl.com), cc Spendgo CSM (csm@spendgo.com).
\n\n
\n
If the Member lookup is fine,\n
If this is Lab store, inform Spendgo CSM. Spendgo CSM will follow up to complete the Lab testing.
\n
For the subsequent locations, run some test orders using steps 1-9 from the “Loyalty Flow” section below. If there is any issue, contact Spendgo CSM.
\n\n
\n
\n
\n\n
\n
\n
\n5. Loyalty Flow
\nMember Lookup & Reward Redemption
The following steps are to be performed by a staff member on the Micros Simphony 2 system. Please refer to your Fishbowl Promotions Manager Documentation for the latest updates.
\n
Open a new order.
\n
Enter the member’s order items.
\n
\n
Click Member Lookup button.
\n
\n
\n
\n
Enter the member’s (10-digit) phone number and click Next.
\n
\n
\n
Select the member for member to earn points on the order.
\n
\n
A prompt will display the member’s Points Balance and available rewards. Click OK.
\n
\n
\n
\n
Click LYL Checkout button.
\n
\n
\n
\n
Select the reward to be redeemed on the order. The loyalty reward and it’s discount value will be applied.
** Loyalty lookup available in the cashier facing display only.
*** Only one Olo Loyalty reward can be applied to the order. Rewards stacking is not supported. However non Olo Loyalty discount/coupons can be applied along with Olo Loyalty reward.
\nThings to Know
\nSupport for Voids/Refunds: This is what happens to loyalty on the order after a closed order is reopened and modified in the POS.
\n
\n
\n
\n
\n
\n
\n
\n
Action
\n
Loyalty Processing
\n
\n\n
\n
Order is fully refunded
\n
\n
Loyalty on the order is revered.
\n
\n
Points accrued on the order is reversed
\n
Any loyalty reward applied to the order is added back to the Member’s balance
\n
\n
\n
\n
\n
Order is partially refunded
\n
\n
Partial loyalty reversal is not supported in Olo Loyalty. Partial refund is also treated same way as the full refund.
\n
In order to keep the loyalty on the partial refund to be processed correctly, it is recommended to fully refund the order and create a new order with the updated order details.
\n
\n
\n
\n
Order is updated
\n
\n
Any further loyalty update on a closed order is not supported in Olo Loyalty.
\n
In order update the loyalty on the order, it is recommended to void the order and create a new order with the updated details.
\n
\n
\n\n
\n
\n
\nLoyalty processing on the order: The loyalty processing (points and rewards balance update) on the order is not in real time. The order from Clover is pulled from Clover system after the order is placed so it takes 30-45 seconds for completing the loyalty processing on the order. This means
\n
The completed order show up in Dashboard after 30-45 seconds.
\n
The claimed reward is not removed from the Member’s balance until 30-45 seconds after the order is completed.
\n
The reward is validated for the order when applying, but there is a rare chance that when the order is completed, the applied reward is not valid but because this re-validation of reward cannot be done in real time, the Member will get discount but the reward balance does not get updated.
\n
\n
\n
\nOrder ID Format: All Member or guest orders placed from Clover POS usually show up an Alphanumeric ID such as XTE83HF9CPSBA.
\n
Notes about the order receipt on Olo Loyalty Dashboard
Please note that the receipt view of the order in Dashboard does not fully match with the customer receipt generated by Clover.
\n
\nReceipt Subtotal: TheSubtotal shown on the Dashboard receipt matches with the Subtotal on the Clover receipt. Clovers subtotal reflects the sum of line items and not the applied rewards/discounts/coupons.
\n
\nReceipt Total: The Total shown on the Dashboard receipt matches with the Total on the Clover receipt. However, it may not tally with the other numbers (line item prices, subtotal, Tax etc.) on the receipt. Receipt total reflects the sum of line item prices including modifiers + Tax + Tip + other charges minus the applied rewards/discounts. However the dashboard receipt does not show tips and other charges.
\n
\nIntegration Setup
\nRequirements
\n
Olo Loyalty integration can be enabled location by location from Clover Dashboard. Access to the Clover Dashboard is required to enable the integration.
\n
If already using Clover POS, check if any of the devices running at the location(s) are on older unsupported Clover devices. The following clover devices are not supported and will have to be upgraded to newer supported devices.
\n
Clover Mini (Series 1)
\n
Clover Flex (Series 1)
\n
Clover Station (Series 1)
\n
\n
\n
We recommend that if the Clover test lab is available, the integration is enabled and tested at the lab before rolling out to other locations.
\n
\nHow to Enable the Integration\n
\nStep 1. The Merchantconfirms the location(s) is ready for setting up the integration.\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
The locations to enable the integrations are identified.
\n
\n
\n
Procedure
\n
Review the requirements mentioned above and confirm the location(s) is ready for enabling Spendgo Integration
\n
\n\n
\n
\nStep 2:The Merchant Informs Olo Loyalty CSM to initiate the integration setup\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Identify the locations to enable the Olo Loyalty Integration.
\n
\n
\n
Procedure
\n
Inform Olo Customer Success Manager the list of locations that needs to be enabled.
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Olo Loyalty CSM
\n
\n
\n
Required Input
\n
Authorization from the Merchant to enable the integration
\n
\n
\n
Procedure
\n
\n
Co-ordinate with the Merchant the date and time for setting up the integration.
\n
Evaluate if there is any testing required after the integration.
If any testing is required, setup the testing time.
\n
\n
If the integration has not already been enabled for any of the Merchant locations\n
Obtain the Merchant contact to whom the Olo Loyalty API credentials be sent to.
\n
Instruct the Integrations team to setup and share Olo Loyalty API credentials with the Merchant.
\n\n
\n
\n
\n
\n
Data to share
\n
\n
Share with the integration team
\n
\n
Merchant contact to whom the API credentials should be sent.
\n
Locations list
\n
\n
\n
\n
\n
Outcome
\n
\n
The time slot for enabling the integration is setup with the Merchant.
\n
Working session is setup with the Merchant for testing, if required.
\n
Instructions sent to the integration team
\n
\n
\n\n
\n
\n
\nStep 4: Olo Loyalty Integration team shares API credentials with the Merchant\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
Olo Loyalty Integrations Team
\n
\n
\n
Required Input
\n
Authorization from CSM and the Merchant contact to send the credentials to.
\n
\n
\n
Procedure
\n
\n
If the credentials are already not shared with the Merchant,
\n\n
Setup the POS API key in Olo Loyalty Admin portal
\n
Share the API credentials securely in a 1Password link with the Merchant contact. Include the below information in the 1password secure note.\n
Merchant’s Brand Id in Olo Loyalty
\n
Store Codes for the requested Merchant locations in Olo Loyalty
\n
Olo Loyalty Integration API credentials.\n
Api Key
\n
Api Secret
\n\n
\n\n
\n\n
Refer to internal documentation for detailed instructions.
\n
\n
\n
\n
Data to share
\n
API credentials and Brand ID and Store IDs with the Merchant in the secure 1Password note.
\n
\n
\n
Outcome
\n
Merchant has all information needed to setup the integration.
\n
\n\n
\n
\nStep 5: The Merchant enables the integration from the Clover Dashboard\n
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Required Input
\n
Olo Loyalty API Credentials and other info shared by Olo Loyalty Integrations team
\n
\n
\n
Procedure
\n
\n
Please note that:
\n
\n
Olo Loyalty is certified as by Clover and set as Private app. Clover does not list the private apps in the App Market and hence cannot be found in the App Market.
\n
The loyalty integration between Spendgo and Clover POS uses the integration platform from Link (https://linktoany.com/ ). This will bring up the list of Merchant Locations. If you are enabling integration for multiple locations, keep this browser tab open. When you click on a location, it brings up the Link integration portal.
\n
\n
For enabling the integration follow the below steps
This will bring up the list of Merchant Locations. If you are enabling integration for multiple locations, keep this browser tab open. Enabling the integration for location has to start from this page. When opening a location, right click on the location and open it in a different browser tab so that this browser tab remains for you to easily come back to.
\n\n
When the location is opened on a different browser tab, it brings up the integration portal hosted by Link. While bringing up this page, the Clover API credentials for the location is automatically pulled from Clover using the Clover oAuth process. There is no other direct way to obtain the Clover API credentials. This is the reason it is important to always start with the above location listing page to enable integration for the location.
\n
\n
It brings up the page to enter the Spendgo API credentials. Enter the details as follows and click “Save”
\n
\n
\n
\nName: Give a name for this location. The location is listed using this name in the Link integration Portal.
\n
\nBrand ID: This is shared by Spendgo in the 1Password note. Please note that Brand ID is same for all locations and therefore needs to be entered only for the very first location. For the rest of the locations this field comes up pre-filled.
\n
\nStore Code: This is the Spendgo Store code for the location shared in the 1Password link.
\n
\nApi Secret: This is shared by Spendgo in the 1Password note. Please note that Brand ID is same for all locations and therefore needs to be entered only for the very first location. For the rest of the locations this field comes up pre-filled.
\n
\nApi Key: This is shared by Spendgo in the 1Password note. Please note that Brand ID is same for all locations and therefore needs to be entered only for the very first location. For the rest of the locations this field comes up pre-filled.
\n
\n\n
In the “Choose a flow to Apply this integration” section, the Spendgo account just created shows up. If not, select the account just created and click on “Add integration”. The integration is listed on the Link portal. But please note that no integration can be directly added from here. After a location is added, close the tab. For enabling any other location, you have to start from the location list in step 3. If you have not saved the tab that lists the location, start from the step 2 again.
\n
At the locations reboot all the POS terminals or do a refresh from the Register App. This will download and install the App on the device(s).
\n
After the reboot, confirm that the Spendgo Loyalty App appears on the listed apps in “More Tools”.
\n\n
\n
\n
\n
\n
\n
Outcome
\n
The integration setup is complete on the Clover Dashboard
\n
\n\n
\n
\n
\nStep 6: The Merchant Refreshes the POS Terminals\n
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Procedure
\n
\n\n
After the integration is enabled on the Clover Dashboard, reboot all the POS terminals or do a refresh from the Register App at the location(s). This will download and install the App on the device(s).
\n
After the reboot, confirm that the Olo Loyalty App appears on the listed apps in “More Tools”.
\n\n
\nDouble click to open the App once and close it. This will enable the “Loyalty Rewards' button in the Register app and disable the “Allow Display over other apps if it is in the enabled state”. There will be no further need to open this app.
\n
\n
\n
\n
\n
\n
Outcome
\n
The integration setup is complete
\n
\n\n
\n
\n
\nStep 7: Verify the Integration\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Task Owner
\n
The Merchant
\n
\n
\n
Procedure
\n
\n
After setting up the integration, quickest way to check if the integration is working is to do the Loyalty Member look up. Please refer to the “Loyalty Member Lookup” in the “Loyalty Flow” section below.
\n
\n
If the “Loyalty Discount” button is showing on the payment screen and brings up the customer lookup window when clicked, enter a 10 digit US/Canada phone number. If it results in an “Something went wrong while processing the request” - make sure the device is rebooted and try again. If still there is an error, then there is an issue with the integration. Please report to Olo Customer Success Manager and Spendgo Integration team.
\n
If the basic validation is successful and if this is the first location (preferably the lab store) inform the Olo Customer Success Manager. Olo Customer Success Manager follows up with the Merchant to complete the testing.
\n
If this is not the very first location and the basic validation is successful, the completed orders should start showing up in Dashboard. Please note that there is a 30-45 seconds delay between when the order is placed and when the oder shows up in the Olo Loyalty Dashboard. Wait for a few orders to be completed on the POS stations inform the Olo Loyalty CSM. Olo Loyalty CSM can look up in the Dashboard that the orders are coming in and being processed
\n
\n
\n
\n\n
\n
\nEditing an integration\n
If configuration needs to be updated for any reason. Open the Shoppinpal page by following step (3) above. Since the integration is already enabled, there is no need to enter any details on the page. Click on the “Integration” link at the top of the page. Look for the location in the list and delete the integration setup integration again using the steps mentioned in the previous section.
\nDisabling the integration\n
To disable the integration the Olo Loyalty App needs to be uninstalled.
\n
Login to the Clover Dashboard.
\n
Click on “More Tools” → My Apps.
\n
Then select the Uninstall app from the “Actions” menu next to “Olo Loyalty” App.
\n
Reboot the devices or Refresh the POS from the “Register” App.
\nLoyalty Flow
The Olo Loyalty loyalty integration is enabled, a “Loyalty Reward” button shows up on the payment screen in the Register App.
\nLoyalty Member Lookup:
After adding the items to the order, Cashier can look up the member by clicking on the “Loyalty Discount” button
\nApplying a reward:\n
\n
After the member lookup, the available rewards are listed for selection.
\n
To proceed without redeeming any reward click on “CLOSE”.
\n
To redeem the reward, cashier selects from the available rewards list and clicks on “CONFIRM”.
\n
After clicking “CONFIRM” the check is updated to show the discount applied.
Please note that, only the rewards applicable to the order is listed after the lookup. However, the rewards is revalidated again when applied. Though it is highly unlikely if for whatever reason the reward fails to apply an error is displayed.
\nUpdating the check after applying the reward:\n
Click on the “Back” arrow to go back to go back and edit the check. New Item can be added or deleted , quantity modified or modifier changed.
If the check is updated, then the applied reward is taken off from the check. Reward will have to be reviewed and reapplied by click on the “Loyalty Discount” button on the checkout screen.
\nChanging the applied reward:\n
To change the applied reward, click on the “Loyalty Discount” again and switch the reward.
\nSwitching the Loyalty Member after the lookup:\n
After looking up a number, if it needs to be changed, click on the “Back” button, change the phone number and lookup again.
\nProcessing Voids/Refunds:\n
Open the completed orders and double click on the order
Click on “Exchange/Refund” and then select “Exchange/Refund”
Double click and open the payment and click “Refund”
Please note that using this menu, the checks can also be updated using “Exchange Items” and “Refund Items” options. We do not support Partial Refunds. So, “Exchange items” and “Refund Items” are treated the same way the “Refund Payment” - i.e. we reverse any points accrued and reward redeemed on the order.
A summary of the Olo Loyalty integration with NCR Aloha Cloud (formerly Silver Pro), including supported features and steps for setup.
About
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
NCR Silver Pro, is a restaurant management software from NCR providing by an all-in-one point of sale system.
\n
Launched May 2021
\n
Article Last Updated March 2024
\n
Category POS
\n
\n
\n
\n
\nWhat’s Supported?
\n
\n
\n
\n
\n
\n
\n
\n\n
\n
Feature
\n
Supported
\n
Not Supported
\n
\n
\n
Ordering Channels
\n
\nPOS: NCR Silver, NCR Silver Pro
\n
\nOnline: NCR Silver Commerce
\n
\n
\n
Loyalty features
\n
\n
Accrue points for loyalty claimed orders
\n
Claim receipt to accrue points for orders not claimed at the store
\n
Redeem Olo Loyalty offers/rewards
\n
Combine Olo Loyalty rewards with non-Olo Loyalty rewards
\n
\n
\n
\n
\n
Base Program Types
\n
Points Banking
\n
Shop with points
\n
\n
\n
Basket Level Rewards/Offers Types
\n
\n
$ Discount (Rebate)
\n
% Discount (Discount)
\n
Bonus Points
\n
\n
\n
\n
\n
Item Based Rewards/Offers Types
\n
\n
BOGO
\n
Free Item
\n
$ Discount
\n
% Discount
\n
Bonus Points
\n
Price Adjustment
\n
\n
\n
\n
\n
Rewards shown for selection
\n
\n
When the cashier looks up the reward, all rewards that are available to the Member at the store location is displayed. However, some rewards may not be applicable to the order because the order does not meet certain reward requirements. The orders that are not applicable are listed as not applicable.
With the Silver Pro versions older than 6.5, NCR also compares the order total with the applicable rewards in the list. It counts the amount of the rewards listed from top to bottom and if it finds that the sum of the reward amount listed exceeds the order amount, marks some of the rewards lower in the list as not applicable. With the version 6.5 or later, it is possible to override this and apply any reward that are applicable to the order.
\n
\n
\n
\n
\n
\n
Discount code setup requirements
\n
\n
Olo Loyalty integration with Silver Pro is implemented using the NCR’s integration framework for third party loyalty integration. No new discount code is setup in NCR while setting up the integration.
\n
Additional discount code may need to be setup and associated with Olo Loyalty rewards when a third party online ordering (such as Olo) or in store payment platform (such as Bbot) is integrated with Silver Pro. Refer to Online ordering partner’s documentation for more details about the discount code setup.
\nProcessing Refunds or Updates to a Closed Order: Here is what happens when a completed order is reopened for update or refund.
\n
Enlarges the table by opening it in a full screen dialog
\n
\n
\n
\n
\n
Action
\n
Loyalty Processing
\n
\n\n
\n
Order is fully refunded
\n
\n
Loyalty on the order is revered.
\n
\n
Points accrued on the order is reversed
\n
Any loyalty reward applied to the order is added back to the Member’s balance
\n
\n
\n
\n
\n
Order is partially refunded
\n
\n
Partial loyalty reversal is not supported in Olo Loyalty. Partial refund is also treated same way as the full refund.
\n
In order to keep the loyalty on the partial refund to be processed correctly, it is recommended to fully refund the order and create a new order with the updated order details.
\n
\n
\n
\n
Order is updated
\n
Olo Loyalty does not support updating the closed order. However, there is no setting in NCR to prevent updates to the closed orders. If the update is needed, it is recommended that the order is voided and a new order created.
\n
\n\n
\n
\n
\n
\nRewards Stacking: Olo Loyalty does not support applying multiple rewards to the order but a non-Olo Loyalty reward can be applied along with a Olo Loyalty reward. However please note that Silver Pro’s UI does allow multiple rewards to be applied to the order. This is known issue. Until this is fixed, the cashiers need to be trained to apply only one reward to the order. If multiple rewards are applied it will have the following implications:
\n
The order does not show up in the Olo Loyalty Dashboard.
\n
The Member incorrectly gets to apply multiple rewards but still the rewards are not removed from the Member’s reward balance.
\n
The order will not accrue loyalty points.
\n
\n
\n
\nNotes about the Member Lookup:
\n
Olo Loyalty loyalty look up is by phone number.
\n
Olo Loyalty does not provide a loyalty card so look up by Member ID, barcode or card swiping is not applicable.
\n
\n
\n
\n
\nChanging the Order/Reward after Applying the Reward: If the order is modified after applying the order, then it may impact the applicable rewards. Click on the “Loyalty” button to review the applicable rewards and make any change if required. Since the loyalty member is already attached, it will skip the lookup step and directly list the applicable rewards for the updated order.
\n
\nOrder ID Format: The order from NCR POS show up in Dashboard with 6-9 digit numeric ID such as 496610.
\n
\nNotes about the Order Receipt on Olo Loyalty Dashboard: Please note that the receipt view of the order in Dashboard may not fully match with the customer receipt generated by NCR.
\n
\nReceipt Subtotal: TheSubtotal shown on the Dashboard receipt matches with the Subtotal on the NCR receipt which reflects the sum of line items and not the applied rewards/discounts/coupons.
The points accrued is not based on the subtotal but based on the sum of the prices of loyalty qualifying items.
\n
\n
\nReceipt Total: The Total shown on the Dashboard receipt reflects Subtotal plus Tax minus the applied rewards/discounts. It does not include the Tip amount.
\n
\n
\nIntegration Setup
\nRequirements\n
Olo Loyalty Integration is enabled by the Merchant from NCR Silver Pro. We recommend that if the NCR test lab is available, the integration is enabled and tested at the lab before rolling out to other locations.
\n
If the NCR silver Pro POS is being setup new, make sure that POS setup is completed and tested.
\n
Make sure that the Olo Loyalty account, loyalty program and the rewards are setup.
\n
\nHow to Enable the Integration\n
\n
Once the POS, Olo Loyalty account, loyalty program and the rewards are setup and integration is ready to be enabled, Olo Customer Success Manager will inform the Olo integration team to share the integration API credentials with the Merchant.
\n
Olo Loyalty integrations team shares the following details securely with the person designated by the Merchant to enable the integration.\n
Webhook Server URL
\n
Access token
\n
Merchant ID
\n
Store IDs
\n\n
\n
Merchant sets up the integration from NCR Silver Pro Back Office using the below steps.
Go to: Customers → Loyalty Program and enable the loyalty integration:
\n
\n
b. Click on “Edit” or click on “Get Started”
c. Under ‘Program,’ select Silver Generic Loyalty API from the ‘Program Type’ drop-down list and setup the Loyalty Integration (see screenshot below)
\n
Program Type: Silver Generic Loyalty API
\n
Server URL: <Shared by Olo Loyalty>
\n
Access Token: <Shared by Olo Loyalty>
\n
Barcode on Receipts without Loyalty Member: Checked (This is needed so that we get Guest order data from NCR. Members can earn loyalty points on the guest order by claiming it from the Loyalty Member Portal)
\n
Message on Receipts without Loyalty Member:
\n
Enter the footer that needs to be printed on the receipts that are not claimed. Here’s a sample message.
Sample message is shown on the screenshot. The Member portal URL specific to your account will be Shared with you by Olo Loyalty after the account is setup.
\n
Merchant ID: <Shared by Olo Loyalty>
\n
Enable Manual Card Entry: Checked
\n
d. (Multi-Site Only) Click Assign Stores and select the store you want to use the third-party loyalty program. Stores not assigned to use the third-party loyalty program will not have a loyalty program.
e. Go into Accounts and set the store API id to map the stores in NCR with the store codes in Olo Loyalty (see screenshots below)
f. Refresh the POS
\nLoyalty Flow
Please refer to NCR documentation on the Loyalty Flow in the POS when third party Loyalty such as Olo Loyalty is enabled. Please note that the following specific points are applicable to Olo Loyalty.
\n
Member look is supported by Phone number or a scan of a valid QR Code.
\n
Olo Loyalty rewards do not apply automatically.
\n
If the order amount is more than the reward amount, the full reward amount of the applied reward applies to the order. If the order subtotal is less than the reward amount, the reward value shown matches with the subtotal. However if the reward is applied, the entire reward available to the user is used up.
\n
It is not possible to manually enter a reward amount to be applied.
\n
The steps mentioned in the “Activating a Loyalty Account” section is not applicable to Olo Loyalty.
A summary of the Olo Loyalty integration with NCR Aloha, including supported features and steps for setup.
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
NCR Aloha is a point of sale system built on the Windows OS integrated with Olo Loyalty via Fishbowl’s Promotions Manager Application.
\n
Launched July 2021
\n
Article Last Updated May 2024
\n
Category POS
\n
\n
\n
\n
\nWhat’s Supported?
\n
\n
\n
\n
\n
\n
\n
\n
\n
Feature
\n
Supported
\n
Not Supported
\n
\n\n
\n
Ordering Channels
\n
NCR Aloha POS (Versions 6.4 and higher) Aloha Connect License and an available EIT is required
\n
Customer Facing display
\n
\n
\n
Olo Loyalty Features
\n
\n
Accrue points for loyalty claimed orders
\n
Claim receipt to accrue points for orders not claimed at the store
\n
Redeem Olo Loyalty offers/rewards
\n
Combine Olo Loyalty rewards with non-Olo Loyalty rewards
\n
Loyalty reversal when order is refunded.
\n
\n
\n
\n
\n
Base Program Types
\n
Points Banking
\n
Shop with points
\n
\n
\n
Basket Level Rewards/Offers Types
\n
\n
$ Discount (Rebate)
\n
% Discount (Discount)
\n
Bonus Points
\n
\n
\n
\n
\n
Item Based Rewards/Offers Types
\n
\n
BOGO
\n
Free Item
\n
$ Discount
\n
% Discount
\n
Bonus Points
\n
\nNote: Price Adjustment Offers are not supported for NCR Aloha integration via Fishbowl Promotions Manager application.
\n
\n
\n
\n
\n
Rewards shown for selection
\n
\n
Only the rewards applicable to the order are shown for selection.
\n
\n
\n
\n
\n
Discount code requirement
\n
\n
The POS integration does not required a discount code to be associated with the Olo Loyalty rewards.
\n
A separate discount code may be required for integrating online ordering platform with Aloha and for the rewards enabled for Online ordering that discount code may have to be associated.
\n
\n
\n
\n
\n
Online and In-Store Ordering Platforms
\n
Olo
\n
\n
\n\n
\n
\nThings to Know
\n
\nPrerequisites:
\n
Operating system
Windows 10, Windows 7 or comparable Windows OS with .NET Framework prerequisite Please contact your Fishowl PM provider to their latest OS requirements.\n
\n
\n
NCR Aloha POS v.6.4 and above
Aloha Connect License and an available EIT is required
\n
\n
Persistent internet connection
\n
\n
\n
\nSupport for Voids/Refunds: This is what happens to loyalty on the order after a closed order is reopened and modified in the POS.
\n
\n
\n
\n
\n
Action
\n
Loyalty Processing
\n
\n\n
\n
Order is fully refunded
\n
\n
Loyalty on the order is revered.
\n
\n
Points accrued on the order is reversed
\n
Any loyalty reward applied to the order is added back to the Member’s balance
\n
\n
\n
\n
\n
Order is partially refunded
\n
\n
Partial loyalty reversal is not supported in Olo Loyalty. Partial refund is also treated same way as the full refund.
\n
In order to keep the loyalty on the partial refund to be processed correctly, it is recommended to fully refund the order and create a new order with the updated order details.
\n
\n
\n
\n
Order is updated
\n
\n
Any further loyalty update on a closed order is not supported in Olo Loyalty.
\n
In order update the loyalty on the order, it is recommended to void the order and create a new order with the updated details.
\n
\n
\n\n
\n
Order ID Format
Aloha orders are shown with the 5 digit order ID in the Olo Loyalty Dashboard. This matches with the order ID printed on the receipt.
Making a loyalty claim on a receipt : Olo Loyalty Members who do not make a loyalty claim on the order at the store, they can earn points by claiming the receipt from Member Portal.
Notes about the order receipt on Olo Loyalty Dashboard
\n
\nReceipt Subtotal :\n
TheSubtotal shown on the Dashboard receipt matches with the Subtotal on the printed receipt.
\n
Subtotal reflects the sum of line items and not the applied rewards/discounts/coupons.
\n
Also note that the points accrued on the order does not always match with the subtotal. This is because Olo Loyalty does not compute points based on the receipt subtotal, but based on the sum of prices of items marked as qualifying for points.
\n\n
\n
\nReceipt Total:\n
The Total shown on the Dashboard receipt matches with the Total on the printed receipt. Receipt total reflects the sum of line item prices including modifiers + Tax + Tip minus the applied rewards/discounts.
\n
The tax, tip or other charges are not shown on the receipt.
\n\n
\n
\n
Sample Receipt
\nLoyalty Flow
\nMember Lookup & Reward Redemption
Create a Check
2. Initiate Loyalty Transaction
Tap Personica E-Club Button
1. For TS
2. For QS
3. Enter Phone Number and Click Ok. It will attach the Member to the check.
3a. If available rewards are shown, select a reward and click Ok.
Click Ok. Discount will apply to the check.
3b. If no the Member has no applicable reward then it shows \"Information: The Member is attached to the transaction, but no rewards available\". Click Ok.
3c. If the reward does not meet a reward criteria, such as the order not having an eligible item, the error is displayed. Click Ok.
A summary of the Olo Loyalty integration with Mobile Passes, including setup steps and branding.
\n
Allow members to easily scan their mobile pass as their method for identifying themselves. When used with loyalty, a Member will pull out their iOS or Android Mobile Pass and scan it on a barcode scanner connected to the Olo Loyalty integration. Based on your account’s settings, the member’s non-PII information — such as the member’s points and offers — will be retrieved and displayed on the integrated platform (most commonly the point of sale).
\n
\nThings to Know
\n
\n
Mobile Passes is an in-store feature add-on. Please contact your CSM for more information on enabling Mobile Passes for your account.
\n
Use of Mobile Passes requires a scanner which can read QR codes and a POS integration which uses the Olo Loyalty Member APIs. Follow your POS guidelines on how to look up a member in their system. The QR code uses either the member’s unique phone number or Olo Loyalty Id to identify a person. Depending on your POS system and what it requires to look up a customer, this will impact how you generate the unique pass link per person. Olo Loyalty must be connected to your connected to your email provider environment in order to populate the matching member information within the pass link.
Toast POS requires Olo Loyalty Id to identify your members in their workflows.
\n
\n
Each Mobile Pass is unique per download. One unqiue pass download link for use with Android and iOS devices will be shared per account. Follow the Add pass to Wallet button in Email steps below. Olo Loyalty SMS does not currently support sharing of the download link to members.
\n
Two passes from the same brand that are installed on one device are considered the same pass, and these will display inline. When there is a push update to all the passes, the old version will automatically be removed. Both passes will be scannable while installed.
\n
When a customer without a Olo Loyalty account downloads a pass, they do not have a Olo Loyalty account until their pass is first scanned. At that point, a Starter — entry level — account is created.
\n
For more information on customizations, follow the Mobile Pass Branding below.
\n
\n
Olo Loyalty Mobile Passes is not supported on watchOS.
\n
\n
\n
\n\n
\nAdd Pass to Wallet Button in Email
\n
Once your pass has been configured, you’re ready to start sharing it with your Members via the Add to Apple Wallet button, or Add to Google Wallet.
\n
For additional ways to share, view the specific OS Add to Wallet documentation:
Before you start, you will be provided with a unique download link for your account. Example: https://app.passcreator.com/integration/createpass/uniquepassid?barcodeValue={memberId}
\n
Note: this above link is not a working link.
\n
\n
\n
Tip: Add both Android and Apple add to wallet button links to your footer of your emails. In particular, we recommend including it in your Welcome email.
\n
\n
\n\n
\nInstructions
\n\n
Select your button image. Images may vary in design, above are the standard images provided by both Apple and Google.
\n
Log into your email provider platform and go to the template or email campaign you will be scheduling.
\n
Insert one of the button images into the template.
\n
\n
Select the image and define the button url using the following format:
\n
Example link with placeholders: https://app.passcreator.com/integration/createpass/{uniquepassid}?MemberID={memberId} This is not a live link, it is meant to illustrate what your unique pass link may look like. Your Olo Loyalty Customer Success Team will provide you your unique pass link with the {uniquepassid} for your brand.
\n
The {memberId} is a unique identifier value per pass consisting of the member’s 10-digit phone number, or their Olo Loyalty Id.
\n
Example link with MemberID: https://app.passcreator.com/integration/createpass/{uniquepassid}?MemberID=4155556123 This is a not a live link meant to illustrate a unique member’s pass link.
\n
To dynamically generate unique pass links for your members in an email campaign, you can use your email provider’s placeholders to populate the member’s phone number or Olo Loyalty Id to the link. Please note, when using placeholders to generate the pass links, the phone number or Olo Loyalty Id must be formatted correctly (without spaces or special characters) in your contact’s profile. If the member does not have the unique identifier in their profile, the pass QR code will not be usable for identifying the member; therefore, when including a pass link in your email, we recommend targeting your campaign to contacts who has the unique identifier for the placeholder to work.
\n
Based on your email provider, the placeholder format may be different. Please use the following url structures with the email provider specific placeholder to generate your member’s pass links.
\n\n
Generate a pass with the member’s phone number as the identifier:\n
For Mailchimp, the link format is: https://app.passcreator.com/integration/createpass/{uniquepassid}?MemberId=|*PHONE*|
\n
For Sendgrid, the link format is: https://app.passcreator.com/integration/createpass/{uniquepassid}?MemberId={{phone} }\n
\n
For Infobip, the link format is: https://app.passcreator.com/integration/createpass/{uniquepassid}?MemberId={msisdn}
\n\n
\n
Generate a pass with the member’s Olo Loyalty Id as the identifier:\n
For Mailchimp, the link format is: https://app.passcreator.com/integration/createpass/{uniquepassid}?MemberId=|*SPENDGOID*|
\n
For Sendgrid, the link format is: https://app.passcreator.com/integration/createpass/{uniquepassid}?MemberId={{spendgo_id} }\n
\n
\n
For Infobip, the link format is: https://app.passcreator.com/integration/createpass/{uniquepassid}?MemberId= {External Person Id}
\n
Note: these are not live links and are only meant to be examples. Your live unique pass link will be provided to you by your Olo Loyalty Customer Sucess Team.
\n
\n\n
\n\n
\n
Complete your template, save your campaign, and schedule your send.
\n\n\n
\nMobile Pass Branding
\n
When customizing your Mobile Pass, please follow the iOS and Android specific requirements below. All set up and push updates to your Mobile Passes will be coordinated with your Olo Customer Success Manager.
\n
\nFor iOS
\n
The iOS pass layout will follow Apple Pass’s store card style.
\n
\n
\n
\n
icon.png
\n
The system includes your icon when displaying information about a relevant pass on the lock screen. Mail also uses the icon to represent your pass in an email message.
\n
Minimum 38 W ✕ 38 H points (87 ✕ 87 pixels). Preserve the ratio if providing a larger image size.
\n
\n
\n
\n
logo.png
\n
The system displays your logo image in the dashboard and detail view, so you want to make sure that people can instantly recognize it at various sizes.
\n
320 W ✕ maximum 320 H pixels PNG. The height is flexible.
\n
\n
\n
strip.png
\n
The system displays your strip image in the primary fields section.
\n
1860 W x 738 H pixels PNG
\n
\n
\n
logo text
This is usually your brand name or program name and is optional. If your logo image already has your brand name/program name you want to display, logo text can be left blank.
\n
\n
background color HEX value
used for the front of the Pass
\n
\n
label color HEX value
used for the labels of the fields on the front of the Pass
\n
\n
\n
\n
\n\n
\nFor Android
\n
The Android pass layout will follow Google Pass’s template.
\n
\n
\n
\n
logo.png
600 W ✕ 600 H pixels PNG
\n
\n
Hero image
1032 W ✕ 336 H pixels PNG
\n
\n
The following fields will follow the iOS settings configured.
A summary of the Olo Loyalty integration with Google Analytics, including the Google Tracking ID, Events, and Dimensions.
Use our built-in integration to connect your Sign In powered by Olo Loyalty to Google Analytics for visitor tracking and other reporting. For details on how to use Google Analytics, please refer to the Google Analytics Help Articles.
\n
\nThings to Know
\n
\n
You must have a Google Analytics Measurement ID or Google Tag Manager Container ID configured on your account to view events in your property. See Set Your Google Tracking ID.
\n
Only one Google tracking ID per account can be configured.
\n
Firefox's Enhanced Tracking Protection feature can block Google Analytics. By default, the Standard level of protection allows tracking in Regular windows and blocks them in Private windows. For more information, see Mozilla’s Enhanced Tracking Protection in Firefox.
\n
If you are using a Google Tag Manager (GTM), you may need to Add your Create/Sign In URL (e.g. my.spendgo.com/brandname) to your Tagged Pages in order to use GTM’s debug mode. Learn more about Add URLs to your Tag Coverage Summary. You can also Troubleshoot with Tag Assistant to add the domain.
\n
\n
\n\n
\nSet Your Google Tracking ID
\n\n
Go to Settings / Advanced Settings.
\n
Enter your Google Measurement ID or Tag Manager Container ID. Only one tracking ID can be configured to your site at a time. To locate either Google Analytics or Google Tag Manager ID, reference Google’s guides: Google Analytics -Find your Measurement ID Google Tag Manager -Find your Google Tag Manager Container ID\n
\n
Click Save Changes.
\n\n\n
\nEvents & Dimensions
\n
\nCustom Events
\n
The following are the custom Olo Loyalty events that will populate in your Google Analytics property. Please note, placeholders are enclosed by <> chevron brackets and in your Google Analytics portal, it will be replaced with the relevant text to the event.
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Event Name
\n
Event Label
\n
Purpose
\n
\n\n
\n
account_creation
\n
New Account Created, Account Upgraded, New Linked Account Created
\n
Tracks the path of a successful new account upgrades, creations and associations to your brand. (e.g. the account_creation event will track whether the user is completely new to Olo Loyalty, was an existing Olo Loyalty member joining your brand for the first time, or an existing Starter member upgrading their account to registered).
\n
\n
\n
account_creation_error
\n
Create - <Error Message>
\n
Tracks the reason why the account creation fails.
\n
\n
\n
api_error
\n
Server Error: <User Flow> - <Error Message>
\n
Tracks general server errors.
\n
\n
\n
click
\n
<Button/Link Label>
\n
Tracks the button/link clicks.
\n
\n
\n
create_account
\n
Create Account Initiated
\n
Tracks the new users who start the account creation process.
\n
\n
\n
grant_authorization
\n
<User Flow> - Grant Authorization
\n
Tracks succesful grant access confirmations.
\n
\n
\n
grant_authorization_error
\n
<User Flow> - Grant Authorization Denied
\n
Tracks grant access failures (e.g. access is denied by the user).
\n
\n
\n
forgot_password
\n
Forgot Password Initiated, Update Password, or Update Password Skipped,
\n
Tracks the different events in the forgot password flow including forgot password flow started, update passwords, and skipped update password update.
\n
\n
\n
forgot_password_error
\n
<User Flow> - <Error Message>
\n
Tracks the different error events in the forgot password flow.
\n
\n
\n
input_time
\n
<Input Name>
\n
Tracks the amount of time in milliseconds a user focuses on a specific input field.
\n
\n
\n
input_error
\n
<Input Name>
\n
Tracks the error events triggered by their entry in a specific input field.
\n
\n
\n
passcode_verification
\n
<User Flow>, <User Flow> + Link to Account
\n
Tracks successful verified codes during sign in, forgot password, member create, and member link flows.
\n
\n
\n
passcode_verification_error
\n
<User Flow> - <Error Message>
\n
Tracks the failed passcode verification attempts during sign in, forgot password, or a member create flows.
\n
\n
\n
screen_time
\n
<Screen Name>
\n
Tracks the amount of time spent on a screen.
\n
\n
\n
sign_in
\n
<User Flow> Initiated
\n
Tracks when the user has initiated their sign in by entering their details and submitting via the methods: sign in with phone, sign in with email, or sign in with password.
\n
\n
\n
sign_in_error
\n
Sign In - <Error Message>
\n
Tracks the failed sign in attempts by each method – sign in with phone, sign in with email, sign in with password.
\n
\n
The following associated with the logged in Member Portal events already exist and will continue to function the same.
\n
\n
AddPoints
\n
AddPoints
\n
User adds points by manually claiming a receipt.
\n
\n
\n
PageView
\n
PageView
\n
User views a page (includes tabs when logged in).
\n
\n
\n
SignOut
\n
SignOut
\n
User signs out of the customer site.
\n
\n
\n
VisitsActivitytab
\n
VisitsActivitytab
\n
User views the Activity section of the customer site.
\n
\n
\n
VisitsBalancetab
\n
VisitsBalancetab
\n
User views the Balance section of the customer site.
\n
\n
\n
VisitsMyProfiletab
\n
VisitsMyProfiletab
\n
User views the My Profile section of the customer site.
\n
\n
\n
VisitsProgramNametab
\n
VisitsProgramNametab
\n
User views the About section of the customer site.
\n
\n\n
\n
\n
\nCustom Dimensions
\n
To display the custom dimensions in your Google Analytics property, follow Google’s instructions on how to Set up custom dimensions and metrics. The scope provided below is the recommended setting for the custom metrics in your Google Analytics environment.
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Dimension Name
\n
Scope
\n
Description
\n
\n\n
\n
event_category
\n
Event
\n
\n
The event categories are:
\n
\n
API Server Error
\n
Create Account
\n
Create Account Error
\n
Forgot Password
\n
Forgot Password Error
\n
Grant Authorization
\n
Grant Authorization Error
\n
Passcode Verification
\n
Passcode Verification Error
\n
Sign In
\n
Sign In Error
\n
\n
\n
\n
\n
event_label
\n
Event
\n
The event label.
\n
\n
\n
method
\n
Event
\n
The sign in method being used. Either “oauth” for an OAuth sign in to 3rd party app or “direct” for direct sign in to the Loyalty Member Portal.
\n
\n
\n
user_flow
\n
Event
\n
\n
The user flows include:
\n
\n
Sign In with Password
\n
Sign In with Phone
\n
Sign In with Email
\n
Create Account
\n
Link to Account
\n
Forgot Password
\n
\n
\n
\n
\n
brand
\n
Event
\n
Your brand name.
\n
\n
\n
screen
\n
Event
\n
\n
The screen names are:
\n
\n
Create Profile
\n
Email OTP
\n
Forgot Password
\n
Grant Authorization
\n
Loading Screen
\n
Phone OTP
\n
Sign In with Phone
\n
Sign In with Email
\n
Sign In with Password
\n
Update Password
\n
\n
\n
\n
\n
identifier_input
\n
Event
\n
\n
The identifier types the user entered are:
\n
\n
phone
\n
email
\n
\n
\n
\n
\n
member_status
\n
User
\n
\n
The user’s starting member statuses are:
\n
\n
new user
\n
starter
\n
registered
\n
\n
\n
\n
\n
linked_to_account
\n
User
\n
\n
The user’s startiing link to account (i.e. whether the user was already associated with your brand) statuses are:
The duration in milliseconds of the event. Available on the screen_time and input_time events.
\n
\n\n
\n
passcode_attempts
\n
Event
\n
The number of times the passcode is entered per session. Available on the passcode_verification events.
\n
\n
\n
","user_segment_ids":[]},{"id":46381837129755,"url":"https://olosupport.zendesk.com/api/v2/help_center/en-us/articles/46381837129755.json","html_url":"https://olosupport.zendesk.com/hc/en-us/articles/46381837129755-Retrieve-My-Infobip-Email-Template-Id","author_id":410246746312,"comments_disabled":true,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":46237369221019,"created_at":"2026-02-07T02:31:52Z","updated_at":"2026-04-24T20:40:14Z","name":"Retrieve My Infobip Email Template Id","title":"Retrieve My Infobip Email Template Id","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-04-24T20:40:13Z","user_segment_id":null,"permission_group_id":1679032,"content_tag_ids":["01KGMP5A7NRMH84AC4N55D24FK"],"label_names":["olo loyalty","spendgo"],"body":"
Learn how to find your Infobip Email Template ID within the Infobip portal.
When you’re setting up an Email Campaign from the Olo Loyalty Dashboard. It will ask you to enter your Infobip Template Id. Follow the steps below to learn how.
A summary of the Olo Loyalty integration with Infobip.
About
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Infobip is a powerful omnichannel messaging platform.
\n
Launched October 1, 2021
\n
Article Last Updated February 2024
\n
Category MARKETING SMS EMAIL PUSH
\n
\n
\n
\n
\nHighlights
\n
Supports Email and SMS marketing messaging direct from the Olo Loyalty platform.
\n
Supports Push notifications to your mobile app users with the install of the Infobip SDK. Please contact your Customer Success Manager to enable Push for your brand.
\n
Use Infobip Moments for further automating further messaging flows.
\n
Supports email-only members who can upgrade to Registered Members.
\n
\nThings To Know
When multiple channel integrations are enabled, it is possible for Infobip API rate limits to be hit and an error to occur while syncing member details. This can lead to the member’s in Infobip being out of date. Olo Loyalty always maintains the source of truth for the member profile and preferences. Members will only be updated when they iniate a change in their account profile.
The loyalty data ingested from Olo Loyalty along with other data available in Olo engage platform cab be leveraged in many ways to get meaningful insights, to launch targeted campaigns and drive up customer loyalty. Please refer to Olo Engage documentation for more details on the growing list of common use cases.
\nThings To Know
\n
\nData Sync Frequency and Interval: Please note that the loyalty data is not synced to Olo Engage in real time. The data is uploaded to Olo Engage as a hourly upload of the csv files. The uploaded files are processed by Olo Engage to ingest the data.
When the hourly upload job runs in Olo Loyalty, all the events that occurred during the 60 minutes interval ending at the top of the previous hour gets uploaded. For example: If the job runs at 8:30AM UTC, the uploaded file contains data from 6:00-7:00AM UTC.
\n
\n
\nCampaign Naming for Olo Engage Integration:The integration between Olo Engage and Olo Loyalty uses Campaign Names to map triggers. Because Campaign Names in Olo Loyalty must be unique, follow these steps when updating a campaign or creating a new version to avoid needing to remap your flow in Engage:
\n
Rename your current Olo Loyalty campaign by adding a version indicator (e.g., rename \"Birthday $6off\" to \"Birthday $6off v1\").
\n
Create your updated campaign in Olo Loyalty using the original Campaign Name (e.g., \"Birthday $6off\").
\n
\n
\n
\nBest Practice for Building Loyalty Journeys with Olo Engage:When setting up Olo Engage journeys triggered by events from Olo Loyalty, it's best to use single-purpose transactional journeys rather than multi-step flows. Complex, multi-step journeys that mirror Olo Loyalty's logic directly can become difficult to manage, test, and maintain.
\n
Example: You want a welcome journey where guests initially receive a welcome offer after signup. If the initial offer expires unused, a second offer with a new expiration is provided. Instead of a single complex journey, set up two distinct transactional journeys in Olo Engage:
\n
Journey 1
\n
Trigger: Olo Loyalty event for earning Welcome Offer #1
\n
Action: Send initial Engage message(s)
\n
Follow-up: Reminder message(s) if the offer is unused after a specific period.
\n
\n
\n
Journey 2
\n
Trigger: Olo Loyalty event for earning Welcome Offer #2
\n
Action: Send secondary Engage message(s)
\n
Follow-up: Reminder message(s) if this offer remains unused after a specific period.
\n
\n
\n
\n
\n
Tip: When possible use defined \"offer earned\" events from Olo Loyalty as your trigger. Avoid triggering based on \"offer unused\" scenarios, since you may later make changes to offer rules in Olo Loyalty which could cause these Olo Engage journeys to run inaccurately.
\n
\n
\n
\nIntegration Setup
\nRequirements\n
Please confirm with your Olo Customer Success Manager (CSM) if the Olo Loyalty Account is ready for setting up the Olo Engage integration.
\nSetting up the integration\n
\n
Authorize the Olo Implementation specialist to initiate the integration setup.
\n
An Olo Implementation specialist will reach out to the Olo Loyalty Integrations team with the credentials needed to setup the data uploads.
\n
Olo Loyalty configures the automatic, recurring hourly data uploads.
\n
Olo configures the integration within Engage and performs data validation
\n
Integration is turned on in Production
\n
Brand can begin using Olo Loyalty data within the Engage Dashboard
\nOlo Expo missing modifiers: Item based rewards/offers cannot be mapped to a modifier item as they are not sent in the API when integrating with Olo Expo. The price of the modifier will roll up to the parent item increasing its price so that the total points calculation remains accurate.
\n
\nSupport for multiple instances: Guest orders can only be sent to Olo Loyalty from 1 Olo instance per merchant account. Typically brands will enable guest orders for the “Mealtime” instance targeting regular orders from guests and when configuring a “Catering” instance the brand will not send guest orders to Olo Loyalty via webhook.
\n
\nAvailability of rewards: When Olo Loyalty is integrated with Olo, Olo login happens through Loyalty Single Sign On. The rewards are fetched and cached at login. The rewards earned while logged in will not appear in the available rewards list in Olo until the next login.
\n
\nItem based rewards:
When setting up Qualifying Items group in Olo Loyalty for the Item based rewards, make sure that the Items names in the Group matches with both the item names maintained in Olo and the POS Vendors as they may be different.
Specifically for the NCR Silver Pro POS systems, when configuring the qualifying items in Olo Loyalty, if the item names in NCR is more than 20 characters long, truncate the name to first 20 characters and add it to the list.
\n
\n
\n
\nSetting up Minimum Purchase amount for the reward
When Olo is integrated with Focus POS, the ExcludeDiscountItemFromLPO in setting need to be set to true in Olo. This is the default setting when Olo is enabling the Olo Loyalty integration. If this is not set, Olo orders come into Olo Loyalty with a extra line item (with a negative amount) for the applied discount and it impacts in a different ways. If any of the below issues are happening with the Focus integration, submit a request with Olo Support to enable ExcludeDiscountItemFromLPO setting.
\n
Points accrual on the orders that has a Olo Loyalty reward applied will be incorrect.
\n
Olo Loyalty reward with a % discounts do not work
\n
If the Olo Loyalty reward require with a minimum qualifying purchase, the purchase amount qualification logic will not work correctly.
\n
\n
\n
\n
\nOlo Switchboard for loyalty transactions
\n
To earn loyalty points through Olo Switchboard, guests must initially log into their Olo Loyalty account at least once within the Olo platform (typically via an Olo integrated app or Ordering website). After this first-time login, no additional sign-ins are required for subsequent Switchboard orders to qualify for points. If your setup includes separate Olo instances for Catering and Mealtime, guests must log into their Olo Loyalty accounts individually through each instance to ensure they can earn points on orders placed in either platform.
\n
During phone orders placed through Switchboard, loyalty offers remain fully accessible. Guests simply need to inform the representative about any available offer they'd like applied. All Switchboard orders are handled identically to standard online orders placed through an Olo integrated digital interface.
\n
\n
\n
\nOrder receipts shown in Dashboard
When looking up the orders in the dashboard, you can identify the Olo Orders by the Order Ids formats such as 24554313361358848 (17 digit number starting with 2)
\n
\n
The Subtotal reflects the Order Subtotal before applying the reward.
\nIntegration Setup
\nRequirements\n
\n
If Olo Sandbox account is available, Olo Loyalty recommends that the integration is setup in the Sandbox before configuring in Production. If a brand is not yet live with Olo you can immediately set up in production to save time.
\n
Make sure that the Olo Loyalty Account and the rewards are configured. The Olo Customer Success Manager will inform when the account and rewards setup is completed.
\n
\nDiscount Code Setup requirements: Olo’s integration with the POS may require a discount code to setup in the POS system and associated with Olo. The Olo Loyalty rewards will have to be associated with this discount code. Please refer to Olo’s support team and help guides for configuring discounts in your particular POS and providing Olo Loyalty with the Discount Code to use.
\nToast: Toast discounts display in the Toast admin with a discount code not the GUID. When the discount is opened for editing the URL contains the discount GUID. It is the GUID not the discount code that we needs to be configured in Olo Loyalty for the integration to work. Refer to the screenshot below how the Toast URL shows the discount GUID. When asked share this discount code your Olo Customer Success Manager during the Spendgo loyalty setup. Please refer to Olo’s documentation.\n
\n
\n
\nFocus: When the Olo is integrated with Focus POS, the ExcludeDiscountItemFromLPO setting in Olo needs to be set to “true” and published.
\n
\n
\n
\nTo Enable the integration\n
\n
If the Olo Sandbox environment is available,\n
Once Olo Loyalty completes the Account setup and Brand is ready to enable the integration, Olo integration team sends the Olo Loyalty Sandbox API and oAuth credentials with Olo. After the Olo Loyalty oAuth is setup, the user logs into Olo using the Olo Loyalty sign up/Sign in page.
\n
Olo sets up the oAuth and the API Integration for processing the Loyalty Member transactions.
\n
Olo shares with the Brand steps for setting up the Webhooks from the Olo Admin portal for sending the guest order details to Olo Loyalty.
\n
Brand configures the Webhooks and share the generate Secret with Olo integration team
\n
Olo integration team configures the secret in Olo Loyalty.
\n
Brand runs the following test orders\n
Place an order without logging in (guest order).
\n
Login and place an order without applying a reward.
\n
Place an order each with different available rewards.
\n
If there are some additional tests need to be run, the Olo Customer Success Manager will send the list of test cases to run.
\n
Inform the Olo Customer Success Manager that the tests orders have been placed.
\n
Olo Loyalty verifies the orders and confirms that everything is working fine.
\n\n
\n\n
\n
If the Sandbox testing is complete or of there is no Sandbox environment available, the Olo integration team will share the Production API and oAuth credentials with Olo. Same steps listed above needs to repeated in the Production environment.\n
If Olo Test Lab is available, Olo enables the integration at the Lab first.
\n
After the orders from the Lab are verified, then Olo enables the integration for other liver locations.
\n\n
\n
\nTo Disable the integration\n
\n
Olo disables the oAuth and API integrations.
\n
Brand disables the configured Webhooks.
\n
\nLoyalty Flow
\nMember Login
Members can login to Olo Loyalty before or after selecting the ordering location.
Click on the “Sign In” link.
It brings up the Olo Loyalty Login page. If the Member is already registered into Olo Loyalty, use the Olo Loyalty credentials to login.
\n
If not a registered member, click on the “Create Account” Link on the Sign in page to bring up the registration page. Enter the details, submit and complete the email verification step to register as a new Olo Loyalty Member.\n
\n
\n
When the login completes, the “Your Account” link shows up instead of the “Sign In” link indicating a successful login.
\n
If the login was done after selecting the ordering location, or the location is selected after the login, if the user has any available rewards at the location a “Rewards Available” link shows up.
\nApplying a Reward
There are two different ways to apply the reward - before or after the checkout. the order can also be completed without applying a reward.
Before Checkout:
\n
Add items to the cart, select the pick up/delivery options.
\n
click on “Rewards Available” link to view the list of available rewards and click on “Apply Reward” link for any of the reward of choice.
\n
If the reward can be applied to the order, the cart shows the applied reward.
checkout and complete the order.
After the Checkout:
\n
Checkout the order
\n
On the checkout screen, list of available rewards are listed. Apply a reward of choice.
\n
If the reward can be applied, the cart updates to show the applied reward.
If the reward cannot be applied to the order, a toast message pops up to indicate the error.
\n
\n
Please note that only one Olo Loyalty reward can be applied to the order. However, any coupon and store discount available outside of the loyalty rewards can also be applied along with the Olo Loyalty Order.
\n
\nRemoving or changing an applied reward
When a reward is applied on the order, the cart shows the applied reward. The other applicable rewards are not shown at this time. If a different reward needs to be applied, first remove the applied reward and then apply the different reward of choice.
\nAccruing points on a Guest order
If an order is placed without a login, loyalty points on the order can be claimed from the Member Portal by entering the Order Date and Order Total from the Olo Receipt.
\nProcessing Voids/Refunds:
The Loyalty point earned or rewards applied on the order are reversed when the order is refunded from the Olo Admin Portal. Please refer to Olo’s documentation on how to cancel a scheduled or completed order.
","user_segment_ids":[]},{"id":46381567369883,"url":"https://olosupport.zendesk.com/api/v2/help_center/en-us/articles/46381567369883.json","html_url":"https://olosupport.zendesk.com/hc/en-us/articles/46381567369883-Storefront-by-DoorDash-Integration","author_id":410246746312,"comments_disabled":true,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":46237369221019,"created_at":"2026-02-07T02:11:29Z","updated_at":"2026-04-25T00:27:19Z","name":"Storefront by DoorDash Integration","title":"Storefront by DoorDash Integration","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-04-25T00:27:19Z","user_segment_id":null,"permission_group_id":1679032,"content_tag_ids":["01KGMP5A7NRMH84AC4N55D24FK"],"label_names":["olo loyalty","spendgo"],"body":"
A summary of the Olo Loyalty integration with Storefront by DoorDash, including supported features and steps for setup.
About
\n
\n
\n
\n
\n
\n
\n
\n
\n
Opens image in full screen\n
\n
\n
\n
StoreFront by Doordash is restaurant online ordering system.
\n
Launched January2023
\n
Article Last Updated May 2024
\n
Category ONLINE ORDERING
\n
\n
\n
\n
\nIntegration Summary
\nWhat’s supported?
\n
\n
\n
\n
\n
\n
\n
\n
\n
Feature
\n
Supported
\n
Not Supported
\n
\n\n
\n
Ordering Channels
\n
\n
Online Ordering
\n
iOS & Android App
\n
\n
\n
\n
\n
\n
Olo Loyalty Features
\n
\n
Accrue points for loyalty claimed orders
\n
Redeem Olo Loyalty offers/rewards
\n
Loyalty reversal**
\n
\n
\n
Accrue points for prior guest checkout orders
\n
Combine Olo Loyalty rewards with non-Olo Loyalty rewards***
\n
\n
\n
\n
Base Program Types
\n
Points Banking
\n
Shop with Points
\n
\n
\n
Basket Level Rewards/Offers Types
\n
\n
$ Discount (Rebate)
\n
% Discount (Discount)
\n
Bonus Points
\n
\n
\n
\n
\n
\n
\n
\n
Item Based Rewards/Offers Types
\n
\n
BOGO
\n
Free Item
\n
$ Discount
\n
% Discount (Discount)
\n
Price Adjustment
\n
Bonus Points (Only at Basket level)
\n
\n
\n
\n
\n
Viewing/Selecting the available Rewards
\n
\n
Listing of Available Rewards after logging in
\n
Online Ordering
\n
Upon login, all rewards available to the Member at the selected location can be viewed by the user on the main page in the rewards panel section. The member can scroll through the banners by clicking on the tab links below the rewards banner.
\n
The rewards listed are for viewing only - reward cannot be selected from here.
\n
\n
\n
App
On the Rewards tab, only the available points balance is shown. Available rewards are not shown.
\n
\n
\n
\n
Rewards shown for selection at checkout
Online Ordering and App
At the checkout screen, only the rewards applicable to the order is listed for selection.
\n
\n
\n
Updates to the order after applying a reward
\n
Online Ordering
\n
If a reward is applied and item(s) are deleted from the order on the checkout screen, the the applied reward is automatically removed and the available rewards list is refreshed.
\n
If items are added to the order with available rewards list is refreshed.
\n
If the order has a reward applied and it is still valid after the items are added, the applied reward is retained.
\n
\n
\n
App:
After applying reward at the checkout, navigating out of the checkout screen will remove the reward.
\n
\n
\n
\n
\n
\n
\n
Discount code requirements
\n
\n
Doordash Storefront’s integration with the POS may require a discount code to setup in the POS system and associated with Storefront. However, Storefront does not require the Olo Loyalty rewards to be associated with this discount code.
\n
For brands already using Discounts with Storefront, no additional POS configuration is required for Olo Loyalty.
\n
\n
\n\n
\n
** Loyalty reversal is supported only on the orders that has reward applied.
*** Either a loyalty reward or a non-Olo Loyalty promo code can be applied to the order. One cannot be combined with other.
\nThings to Know
\n
\nNo support for accruing points on guest orders: The Loyalty orders placed from Storefront after logging in accrues loyalty points. The order can be placed without logging in. For “Guest” orders that are placed without logging in, the orders are not passed from Storefront to Olo Loyalty. This means,
\n
The guest orders do not show up in Olo Loyalty Dashboard events list and in Dashboard reporting.
\n
It will not be possible for the Members to accrue points on the order by claiming the receipt from the Member Portal.
\n
\n
\n
\nNote about the points accrual
\n
For the orders that have Olo Loyalty rewards redeemed, the points accrual happens when the order payment is made while placing the order. If the order changes before the delivery or pickup, then the points still reflect the originally placed order.
\n
For orders without a Olo Loyalty reward redeemed, the points accrual happens after order is picked up or delivered. So, there will be a up to 2 hours delay before the orders show up in Olo Loyalty dashboard after placing the order.
\n
For Pennsylvania locations, as per the a local state regulation Storefront calculates taxes on the Pre-discount amount.
\n
\n
\n
\nDouble counting of transactions when Olo Loyalty integration is enabled both in StoreFront and Toast POS at the location.
\n
The order sent by Storefront and Toast have different orders IDs and hence gets created as separate orders in Olo Loyalty.
\n
As of now, only Member orders are supported in the Storefront integration. When the same orders come through from Toast, it comes in as a Guest orders. So, even thought order is counted and shows in the Olo Loyalty Dashboard twice, this does not result in double awarding of points to the Member (Unless the Member actually also goes into the Member portal and make a loyalty claim on the Toast receipt).
\n
However, since the orders are counted twice - this causes over-reporting of sales and orders counts.
\n
\n
\n
\nLimitation with the Reward Types
Bonus points reward is available only at the basket level.
\n
\n
\nLimitations with the loyalty applying at item level
Bonus points reward is not supported at the item level.
\n
\n
\nLimitations with Voids/Refunds
\n
Loyalty reversal on the refunded order is supported only for orders that have a Olo Loyalty reward applied.
\n
For Member orders without any Olo Loyalty rewards or offers applied, the accrued loyalty points are not reversed after the refund.
\n
Olo Loyalty does not support partial loyalty reversal when the order is partially refunded. Loyalty applied on the order is always fully reversed whether on not the order is fully or partially refunded. If processing a partial refund, it is recommended to fully refund the order first and create a new order.
\n
\n
\n
\n“Delivery” and “Pickup” line items: For every order sent to Olo Loyalty, StoreFront automatically adds a zero-priced line item: either \"Delivery\" (for delivery orders) or \"Pickup\" (for pickup orders). This feature allows you to set up rewards specific to delivery or pickup, such as \"$5 Off Delivery Orders\". While setting up the campaign based “Delivery” or “Pickup” orders, Add “Delivery” or “Pickup” to the “Qualifying item group” and set the “Reward Item Group” according to the reward being offered. Please note that it is not possible to setup a “Free Delivery” campaign because the “Delivery” line item always has the zero price and not the actual delivery cost.
\n
Example 1: $5 Off delivery Orders
Qualifying Item Group : <Item group that has “Delivery” as qualifying item>
Reward Item Group: All Items
Example 2: BOGO on Delivery Orders
Qualifying Item Group : <Item group that has “Delivery” as qualifying item>
Reward Item Group: <Item group that has items qualifying for BOGO for this campaign>
\n
\nRewards Stacking
\n
Only one Olo Loyalty reward can be applied.
\n
Stacking Olo Loyalty reward with non Olo Loyalty promo code is not supported.
\n
\n
\n
\nKnown Issues with the orders that have Storefront promo discount applied
\n
If the entire order is discounted using the promo code making it a - sub total order, then the order is not sent to Olo Loyalty.
\n
Points accrue on the net subtotal (i.e Item Total - Promo Discount)
\n
\n
\n
\nMerging of the User Accounts
Merging of the user accounts in Olo Loyalty, profile update does not get carried over to Storefront.
\n
\n
\nNotes about the order receipts shown in Olo Loyalty Dashboard
\nOrder ID format: Storefront orders show up in Olo Loyalty Dashboard with a long GUID format
\n
\n
Opens image in full screen\n
\n
\nSubtotal matches the subtotal on the Storefront receipt. It is the sum of item prices in the StoreFront receipt before applying the reward discount.
\n
\nTotal matches with the total on the StoreFront receipt. It is Sub total + Tax + Tips + Delivery Charges/Fees minus the reward discount.
\n
\nTax, Tips, Delivery charges/Fees are not shown on the Dashboard receipt.
\n
\n
This is sample receipt without a loyalty reward redeemed.
\n
This is sample receipt with a loyalty reward applied.
Please note that for Pennsylvania locations, as per the a local state regulation Storefront calculates taxes on the Pre-discount amount.
\nIntegration Setup
\nRequirements\n
\n
Doordash Storefront and any integration of Storefront with the POS, if required, is set up.
\n
Olo Loyalty Account and rewards are set up.
\nDiscount Code Setup requirements: Doordash Storefront’s integration with the POS may require a discount code to setup in the POS system and associated with Storefront. However, Storefront does not require the Olo Loyalty rewards to be associated with this discount code. For brands already using Discounts with Storefront, no additional POS configuration is required for Olo Loyalty.
\n
\n
\nSteps to Enable the integration\n
\n
Doordash can enable Olo Loyalty integration by individual location.
\n
Once the StoreFront and Olo Loyalty account including the rewards set up is done, the Merchant informs Olo Customer Success Manager and the Doordash Account Manager to enable the integration with the desired locations.
\n
Olo integration team sends the API and oAuth credentials to Doordash.
\n
After the integration is enabled (This typically takes 2 weeks after the credentials are shared), the user authentication to StoreFront will be powered by Olo Loyalty. In order to test the integration before launching, Doordash enables the integration in test mode
\n
– As part of the integration setup, Doordash also configured necessary branding changes required to the loyalty related UI.
\n
Dooardash, Olo Loyalty and the Merchant tests the integration together.
\n
Once the testing is successful the integration will be enabled at all requested locations.
Please note that the Doordash’s time window for enabling integration is between 12 Noon - 3 PM ET.
\n
\n
\nLoyalty Flow
\nMember Login
\nOnline Ordering
User logs in using the Olo Loyalty SSO using the “Sign in/Sign Up” link at the top right corner of the page OR clicking on the rewards banner and then click on “Sign in/Sign Up”
Olo Loyalty is in the process of moving to Passwordless authentication for Member authorization.\n
For Brands that are not migrated to Passwordless authentication, the authorization flow is as follows.\n
Upon clicking the “Sign In” button it brings up Olo Loyalty Sign in page as shown.
\n
Member login in using Olo Loyalty credentials (Phone Number/Email, Olo Loyalty Password).
\n
\n
After the authorization, Doordash sends an OTP code to enter. The login completes after successful completion of 2FA.
\n
\n
\n
\n
New members can click on the “Create Account” from the Login window to create an account and completing the Olo Loyalty registration process.
\n\n
\n
For Brands that will be using the Olo Loyalty Passwordless authentication, Members can use Phone number (default) or Email to get an OTP and login using the OTP sent by Olo Loyalty. Password based login is also provided as an alternative authentication method.
\n\n
After the successful login, user can view the basic profile info and the available points balance.
\nApp
App uses Olo Loyalty Passwordless authentication.
After launching the App clicking on the “Rewards” or “Accounts” tab brings up the “Sign in with Rewards to Continue” window. Click on “Sign in or Sign up” .
It brings up the Olo Loyalty login with Phone as a default method to request a one time passcode. The login page and the login options are same for Web and App.
After Successful Login, the “Rewards” tab shows the available Points Balance. The Available rewards list is not shown as of now.
\n
Once logged in, the the Member stays logged in for unto two months and there will be no need to login again when the App is launched next time. Only if the App is not launched for two months then the Member will be asked to login at next App launch.
\n
The Member can logout from the “Account” tab.
\n
Member profile can be updated from the Account tab → Manage Account. This will redirect to Loyalty Member Portal. The login from the App is not carried over to the Member portal so it will require the Member to login again into the Member and then click on the profile tab to edit the profile.
\nApplying a Reward to the order:
\nOnline Ordering and App:
At the checkout screen, Storefront retrieves applicable rewards for the offer. The member can view the available order and choose a reward to apply. No stacking of the reward is allowed.
When the reward is applied, the updated order is shown with the reward applied.
\nRemoving an applied reward:
\nOnline Ordering and App:
Applied reward can be removed by viewing the applied reward and clicking on “Remove”
\n
If a reward applied on the order needs to be changed, remove the applied reward first.
\n
An order change may make the order qualify for a different reward or make the applied reward not applicable any more. It is recommended to check the available reward after the order is changed.
\n
\nProcessing Voids/Refunds:
The Loyalty point earned or rewards applied on the order are reversed when the order is refunded from Storefront. Please refer to Storefront’s documentation on how to cancel a scheduled or completed order.
","user_segment_ids":[]},{"id":46371030607515,"url":"https://olosupport.zendesk.com/api/v2/help_center/en-us/articles/46371030607515.json","html_url":"https://olosupport.zendesk.com/hc/en-us/articles/46371030607515-Billing-a-Single-User","author_id":410246746312,"comments_disabled":true,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":46237360852123,"created_at":"2026-02-06T21:00:36Z","updated_at":"2026-04-24T20:40:21Z","name":"Billing a Single User","title":"Billing a Single User","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-04-24T20:40:21Z","user_segment_id":null,"permission_group_id":1679032,"content_tag_ids":["01KGMP5A7NRMH84AC4N55D24FK"],"label_names":["olo loyalty","spendgo"],"body":"
Explore the different processes used to Bill a Single User via Local Store Marketing (LSM) in Olo Loyalty.
Billing a single user for marketing is a feature that comes with the Local Store Marketing add-on. It allows users (e.g. Franchise users) to run their own campaigns and manage their own spend on text message campaigns.
Franchisee users with marketing permissions can securely subscribe and manage their payment information enabling text message campaigns in their account.
\nThings to Know
\n
All payment information is hosted by a 3rd-party application, Chargebee, which allows for a secure way to manage your payment and plan information.
\n
User-level billing is only available to Enterprise accounts with the local store marketing add-on enabled. Billing rules only apply to two roles: Franchisee - Insights & Marketing, and Franchisee - Insights, Marketing & Support. Other roles either do not have marketing permissions or are not restricted by user-level billing rules.
\n
At minimum, a Franchise user must have an active subscription to a “Single-User Marketing” plan for the current calendar month to schedule any campaigns. You can subscribe at anytime in the month, there is no prorated rate; this is a volume based plan. Any overages will be charged to your card on file. Subscription renewals are processed on the first of every month at 00:00 AM PST.
\n
\nTo cancel or downgrade your subscription email billing@spendgo.com before you next monthly renewal, your services will continue to be available until the end of the month and you may be charged overages to your card on file if you exceed your plan’s messaging allocation.\n
\n
\nPlan Status
\n
\n
You must be a Franchisee - Insights & Marketing or Franchisee - Insights, Marketing & Support in a Enterprise account with local store marketing add-on enabled to see the billing settings.
\n
When your payment is good to go, you will see a notification that states “Status: Everything is running smoothly!”. It May take up to 30 minute for your first payment to process and for you account to be enabled.
When your payment needs attention, you will see a red notification that states: “Needs attention: Please check your billing information.”
\nSubscribing to a Plan
To start sending text messages, you need to first subscribe to a plan. If you have already subscribed and want to manage your payment and plan information, skip to the Manage Payment section below.
\n
Navigate to your Dashboard Settings / Profile
\n
Click the Manage Payment button
\n
You will see the standard “Single-User Marketing” plan on-screen. Proceed to checkout.
\n
Your email will be auto-filled. Click Next.
\n
Enter your first and last name and click Next.
\n
Enter your billing information and click Next.
\n
Enter your credit card information and click Next.
\n
Review your information and click Pay & Subscribe.
\n
\nManage Payment
You already have a plan and you want to:
\n
Add a message bundle to your plan
\n
Update your billing information
\n
Add a new payment
\n
Update existing payment
\n
View billing history
\n
Reactivate subscription
\n
\nAdd a Message Bundle
Increase your monthly volume by adding on a message bundle to your plan. Changes are applied to the next calendar month.
\n
Navigate to your Dashboard Settings / Profile.\n
\n
Click the Manage Payment button.
\n
Your email will be auto-filled. Click Next.
\n
A one-time passcode will be sent to your email, enter your one-time passcode on the screen and click Login.
\n
Click on your current plan.
\n
Click Edit Subscription.
\n
Click Add Addons.
\n
Select your Addons and Add.
\n
Click Update Subscription to apply the updates to the next calendar month.
\n
\nAdd Your Payment Information
Add a new credit card.
\n
Navigate to your Dashboard Settings / Profile.\n
\n
Click the Manage Payment button.
\n
Your email will be auto-filled. Click Next.
\n
A one-time passcode will be sent to your email, enter your one-time passcode on the screen and click Login.
\n
Click Payment Methods.
\n
Select Add New to add a new payment.
\n
Enter in your payment details and click Add.
\n
\nUpdate Your Payment Information
Update an existing credit card on file.
\n
Navigate to your Dashboard Settings / Profile.\n
\n
Click the Manage Payment button.
\n
Your email will be auto-filled. Click Next.
\n
A one-time passcode will be sent to your email, enter your one-time passcode on the screen and click Login.
\n
Click Payment Methods.
\n
Select the payment method to edit and click Edit Payment.
\n
Enter in your payment details and click Update.
\n
\nUpdate Your Billing Information\n
Update the billing information we have on file.
\n
Navigate to your Dashboard Settings / Profile.\n
\n
Click the Manage Payment button.
\n
Your email will be auto-filled. Click Next.
\n
A one-time passcode will be sent to your email, enter your one-time passcode on the screen and click Login.
\n
Click Billing & Shipping Addresses.
\n
Click on your Billing or Shipping information.
\n
Enter in your new details and Update.
\n
\nReactivate Subscription
Reactivate your subscription at anytime.
\n
Navigate to your Dashboard Settings / Profile.\n
\n
Click the Manage Payment button.
\n
Your email will be auto-filled. Click Next.
\n
A one-time passcode will be sent to your email, enter your one-time passcode on the screen and click Login.
\n
Click on your current cancelled plan.
\n
Click Reactivate Subscription.
\n
Click Confirm.
\n","user_segment_ids":[]},{"id":46370872884123,"url":"https://olosupport.zendesk.com/api/v2/help_center/en-us/articles/46370872884123.json","html_url":"https://olosupport.zendesk.com/hc/en-us/articles/46370872884123-Billing-Paying-Your-Invoices","author_id":410246746312,"comments_disabled":true,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":46237360852123,"created_at":"2026-02-06T20:57:18Z","updated_at":"2026-04-25T00:27:21Z","name":"Billing | Paying Your Invoices","title":"Billing | Paying Your Invoices","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-04-25T00:27:21Z","user_segment_id":null,"permission_group_id":1679032,"content_tag_ids":["01KGMP5A7NRMH84AC4N55D24FK"],"label_names":["olo loyalty","spendgo"],"body":"
Learn how to pay your open invoices for Olo Loyalty.
The following instructions are for paying your open invoices. Invoices can be accessed from your Olo Loyalty billing email notifications sent to your billing contact’s email address.
\n\n\n
Click the Pay Now button in your invoice email to see a summary of your open invoices and the corresponding amounts, due dates, and billing periods.
\n
Select each invoice you want to pay and click the Pay Now button at the top right. *Your invoice details can be downloaded by clicking on Download PDF\n
\n
A prompt with your saved payment methods will appear. Select the payment method you would like to use and click Pay Now.\n
\n
A popup will notify you that the payment was successful and a confirmation email will be sent to your billing email address.
\n\n
","user_segment_ids":[]},{"id":46370655935003,"url":"https://olosupport.zendesk.com/api/v2/help_center/en-us/articles/46370655935003.json","html_url":"https://olosupport.zendesk.com/hc/en-us/articles/46370655935003-Billing-Manage-Your-Payment-Method-s","author_id":410246746312,"comments_disabled":true,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":46237360852123,"created_at":"2026-02-06T20:52:40Z","updated_at":"2026-04-24T20:40:25Z","name":"Billing | Manage Your Payment Method(s)","title":"Billing | Manage Your Payment Method(s)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-04-24T20:40:25Z","user_segment_id":null,"permission_group_id":1679032,"content_tag_ids":["01KGMP5A7NRMH84AC4N55D24FK"],"label_names":["olo loyalty","spendgo"],"body":"
Learn how to access, update, and add Billing payment methods for Olo Loyalty.
The following instructions will walk you through how to add or update your payment method(s) when:
\n
You want to add a new payment method
\n
You want to update your payment method
\n
Your payment method is expiring
\n
Your payment method is invalid
\n
\nAccess Your Payments
\n
You can access your account by clicking the Log into your account now → link at the bottom of your Olo Loyalty billing emails.
\n
\n
Enter your account billing email and continue. You will be sent a one-time password to that email. The one-time password is valid for 5 minutes from the time it is generated.
\n
\n
\n
\n
Enter your one-time password to log in.
\n
\n
\n
\nUpdate Your Payment Method
\n
\n
To update an existing payment method, select the payment method you want to edit and follow the on-screen instructions to update your payment.
\n
\n
\n
You can select your primary and backup payment options, or skip.
\n
Click on Update to complete the process.
\n
\nAdding a Payment Method
\n
\n
To add a new payment method, click on Add New.
\n
\n
\n
Select Credit Card or ACH and enter or update your payment details and click Proceed to Review. Note: For ACH payments, account verification is required. \n
\n
You can set your primary and backup payment options, or skip this step.
\n
Your newly added payment method will be added to your Olo Loyalty Payment Methods page.
\n","user_segment_ids":[]},{"id":46370425355931,"url":"https://olosupport.zendesk.com/api/v2/help_center/en-us/articles/46370425355931.json","html_url":"https://olosupport.zendesk.com/hc/en-us/articles/46370425355931-Limit-Purchase-Claims-Via-Member-Window","author_id":410246746312,"comments_disabled":true,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"section_id":46237360852123,"created_at":"2026-02-06T20:46:40Z","updated_at":"2026-04-24T20:40:26Z","name":"Limit Purchase Claims Via Member Window","title":"Limit Purchase Claims Via Member Window","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-04-24T20:40:26Z","user_segment_id":null,"permission_group_id":1679032,"content_tag_ids":["01KGMP5A7NRMH84AC4N55D24FK"],"label_names":["olo loyalty","spendgo"],"body":"
Learn the advanced setting of Limiting Purchase Claims via Member Window in Olo Loyalty.
The Limit Purchase Claims feature helps prevent misuse of the Add Points tool in the Member Portal by restricting how often members can attempt to claim purchases. This safeguard is designed to reduce the chances of users submitting receipts or transactions that do not belong to them.
\nWhat This Feature Does
This setting limits the number of purchase claim attempts a member can make within a specific time window.
Default configuration example:
Up to 1 successful claim every 6 hours\n
If a member reaches the limit, they’ll see an on-screen error and must wait for the window to reset before trying again.
\nConfiguration Options
This feature is flexible and can be tailored to your program. Brands can set their own limits for:
\n
Maximum successful submissions
\n
Time window in hours
\n
Custom settings can be requested through your Customer Success Manager (CSM) during onboarding.
\nThings to Know
\n
These limits are configured during onboarding and are not meant to be changed frequently, as doing so may lead to confusion for your members.
\n
To update your settings, contact your CSM for assistance.
![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%2010.47.52%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%2010.48.16%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%2010.48.28%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%2010.49.04%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%2010.49.41%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%2010.50.28%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%2012.57.19%E2%80%AFPM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%201.03.04%E2%80%AFPM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%2010.46.07%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%201.21.18%E2%80%AFPM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%201.21.33%E2%80%AFPM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-04%20at%202.03.44%E2%80%AFPM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%209.55.06%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%209.58.54%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%209.58.39%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%2010.07.51%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-06%20at%2010.59.26%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-06%20at%2011.00.10%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-06%20at%2011.00.19%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-06%20at%2011.07.34%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-06-06%20at%2011.01.58%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%2010.57.31%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%2011.06.40%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%2011.08.52%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%2011.09.51%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%2011.10.06%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-05-16%20at%205.14.58%E2%80%AFPM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202024-05-16%20at%2010.25.34%E2%80%AFAM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%2011.30.19%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%2011.35.38%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%2011.33.05%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%2011.36.22%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![](\"https://support.spendgo.com/__attachments/305594428/Screenshot%202023-08-17%20at%2011.37.05%20AM.png?inst-v=7f68f2e4-5df0-45a6-9998-025c91568274\")
\n \n![\"image-20250507-194728.png\"](\"https://support.spendgo.com/__attachments/532217857/image-20250507-194728.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20250507-221226.png\"](\"https://support.spendgo.com/__attachments/532217857/image-20250507-221226.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20250508-000711.png\"](\"https://support.spendgo.com/__attachments/532217857/image-20250508-000711.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://lh7-rt.googleusercontent.com/docsz/AD_4nXcKNEoNE-9lzKD-uKqV8AzASoXofgtckqlY0SuSnq-YpPveHM82y-Jj-t3lDhMPyKF0hM_xBUclmC4Swe_1AOy8dkop51rL4aByv_frseSI_NWhMjghYZJB9JPSymhc5mjs-I3s?key=8zz6d2v8HPtRUV2M6Mk4vg\")
![](\"https://lh7-rt.googleusercontent.com/docsz/AD_4nXdqcpj1koT00aVf0TOTtPlK7_CewaoQnDvBrZF-bx68jSUwG7Jm2hi8lCE5o1l8S4QkngRjAaCc6Pkb32zgS_T29NHb9uEywKDkBCW_d9z4qlFI4uNHl6N7vIvgE5FzWUFDBKK5BA?key=8zz6d2v8HPtRUV2M6Mk4vg\")
![](\"https://lh7-rt.googleusercontent.com/docsz/AD_4nXcBjugEo2e2kb5XeAj-fKhfTn_dD4upWXLbWec9AmcM97Usrbt8EnvVGhKCvqKdRRqihLTCyTfBzJJlJ1ll2NdNbShNLRzGAUdtBJeqFUX0KQw-FpmvJfdaN36bAzRtC4o61vLE?key=8zz6d2v8HPtRUV2M6Mk4vg\")
![](\"https://support.spendgo.com/__theme/images/common/info-macro-icon--39985156a8a940b9a79d.svg\"){kind=icon}
![](\"https://lh7-rt.googleusercontent.com/docsz/AD_4nXdZTk58_nbi1wSQJzWCY3VuU1cyWq2Ue1sS-49lrrFgwNdGu0d0PYB8sGjKUQ4lP0VMAPu-zRCn0zvfvad5dyCEe4zcwSpnMNUwgpYxgwJ6np6ogTIAK-mMNRTF5MuinG5ygK9gxg?key=8zz6d2v8HPtRUV2M6Mk4vg\")
![](\"https://lh7-rt.googleusercontent.com/docsz/AD_4nXdpI2OFjThlT6aUKLTZSZwRLt577vkNtKOvTRjxlVR2wTW87QGjh4O4M8u3fw4rpgsZ2du-3rbMxDeXe1-Pz6ZROiIjMBtIa-H_VRvYQf3IhKkQM6T12UymF_ibr7Um0H9qL9TAOg?key=8zz6d2v8HPtRUV2M6Mk4vg\")
![](\"https://lh7-rt.googleusercontent.com/docsz/AD_4nXcW860ZzzBUWRNlnBgWvduMUTO_eoXbAfKgduOd77phE9k4NGew-ofG5vItszrA_N7NE_39ZQqcOuihB1dDMGwxpSQxshjig77YcRt7Pd6HzPQocbpDpLq6AEU34wq1nvK_evMC?key=8zz6d2v8HPtRUV2M6Mk4vg\")
![](\"https://lh7-rt.googleusercontent.com/docsz/AD_4nXfup5J38t3X4d8buvT0SNR55YZ-svpkJNr3I4Z0hzkI1GKPUb8WOY0PMwp7jngWcc2YGYDUCrxixPV2Zbi6qpqOTXjyVn7eNf_83PkLsI-1_I2KwyB50EpRNs0GCnCmBHHuXW8V?key=8zz6d2v8HPtRUV2M6Mk4vg\")
![](\"https://lh7-rt.googleusercontent.com/docsz/AD_4nXf-GQFmlbK7Z6Ec2zSMe2-FOxGfTBUswLrs4izOpMmc3rwkHI0dJGl6FJY-lFIrT1Iq1Fd0vD3_b3Ue9zC5TupGd4lsT_qKUuE6NMxEPvG6cHYF1KvzUFLXPrZVujbY-SJ3REz5?key=8zz6d2v8HPtRUV2M6Mk4vg\")
![](\"https://lh7-rt.googleusercontent.com/docsz/AD_4nXe-j19CmAikxBriN11raIk7zaAjY40Qr2wuXhdvppEB9LW-prQ6r4IHmV4g8xcin745qidQTtRZ0766Mb8x4QgczhEKemG8dw0H-i5XWWICBhvKaLpZ1bYhdWtTeFWOazJZFgR2Nw?key=8zz6d2v8HPtRUV2M6Mk4vg\")
![\"image-20250321-182942.png\"](\"https://support.spendgo.com/__attachments/504692738/image-20250321-182942.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241223-205412.png\"](\"https://support.spendgo.com/__attachments/504692738/image-20241223-205412.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241223-205712.png\"](\"https://support.spendgo.com/__attachments/504692738/image-20241223-205712.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241223-210530.png\"](\"https://support.spendgo.com/__attachments/504692738/image-20241223-210530.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241223-211513.png\"](\"https://support.spendgo.com/__attachments/504692738/image-20241223-211513.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241223-220345.png\"](\"https://support.spendgo.com/__attachments/504692738/image-20241223-220345.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241223-215747.png\"](\"https://support.spendgo.com/__attachments/504692738/image-20241223-215747.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241223-223735.png\"](\"https://support.spendgo.com/__attachments/504692738/image-20241223-223735.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241223-224047.png\"](\"https://support.spendgo.com/__attachments/504692738/image-20241223-224047.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241223-224614.png\"](\"https://support.spendgo.com/__attachments/504692738/image-20241223-224614.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241223-225037.png\"](\"https://support.spendgo.com/__attachments/504692738/image-20241223-225037.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374337/toast.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240522-181420.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240522-181420.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"Screenshot](\"https://support.spendgo.com/__attachments/175374337/Screenshot%202025-10-13%20105021.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20250110-053446.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20250110-053446.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240723-175756.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240723-175756.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240208-003219.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240208-003219.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240208-003535.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240208-003535.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240123-002309.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240123-002309.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240123-002326.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240123-002326.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240408-191815.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240408-191815.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
\n![\"image-20240322-172251.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240322-172251.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240123-002450.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240123-002450.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20250721-192639.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20250721-192639.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240123-002542.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240123-002542.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240123-002623.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240123-002623.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240123-002657.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240123-002657.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20250729-064101.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20250729-064101.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20250729-064142.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20250729-064142.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240326-213531.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240326-213531.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240123-002734.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240123-002734.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240123-002804.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240123-002804.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240123-002854.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240123-002854.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240403-193028.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240403-193028.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240403-194712.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240403-194712.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240403-205042.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240403-205042.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240403-205700.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240403-205700.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240403-200413.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240403-200413.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241220-202503.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20241220-202503.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240123-002938.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240123-002938.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240118-170014.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240118-170014.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240118-170127.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240118-170127.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240730-011138.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240730-011138.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240730-011349.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240730-011349.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240730-012052.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240730-012052.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240730-012122.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20240730-012122.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20251107-004305.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20251107-004305.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20251107-004344.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20251107-004344.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20251107-005521.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20251107-005521.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20251107-010036.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20251107-010036.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20251107-010159.png\"](\"https://support.spendgo.com/__attachments/175374337/image-20251107-010159.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240223-010225.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240223-010225.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240404-084803.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240404-084803.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
\n![\"image-20240410-034155.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240410-034155.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240403-015859.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240403-015859.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240223-020636.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240223-020636.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241023-222139.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20241023-222139.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20250726-051412.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20250726-051412.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240223-065315.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240223-065315.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240509-000435.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240509-000435.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240509-001356.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240509-001356.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240509-001603.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240509-001603.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240509-002721.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240509-002721.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240509-003836.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240509-003836.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240509-005357.png\"](\"https://support.spendgo.com/__attachments/237305886/image-20240509-005357.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374466/QuLogoCircle.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-051617.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-051617.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240328-185109.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240328-185109.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-053814.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-053814.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-054144.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-054144.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-055610.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-055610.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-065004.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-065004.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-065906.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-065906.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-071650.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-071650.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-071825.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-071825.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-072315.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-072315.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-072935.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-072935.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-074458.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-074458.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-074659.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-074659.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-075034.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-075034.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-075319.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-075319.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240228-075600.png\"](\"https://support.spendgo.com/__attachments/175374466/image-20240228-075600.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"positouch.png\"](\"https://support.spendgo.com/__attachments/307134465/positouch.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/307134465/Screenshot%202024-06-05%20at%204.23.04%E2%80%AFPM.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240308-212828.png\"](\"https://support.spendgo.com/__attachments/175308801/image-20240308-212828.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240312-002122.png\"](\"https://support.spendgo.com/__attachments/175308801/image-20240312-002122.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240312-005446.png\"](\"https://support.spendgo.com/__attachments/175308801/image-20240312-005446.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20250125-003038.png\"](\"https://support.spendgo.com/__attachments/175308801/image-20250125-003038.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240312-010637.png\"](\"https://support.spendgo.com/__attachments/175308801/image-20240312-010637.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
\n![\"image-20240312-011031.png\"](\"https://support.spendgo.com/__attachments/175308801/image-20240312-011031.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374436/bbBrink-Certified.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241104-161355.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20241104-161355.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240522-163210.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240522-163210.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240301-011415.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240301-011415.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240403-051931.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240403-051931.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240401-200712.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240401-200712.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240801-180534.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240801-180534.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240801-175228.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240801-175228.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240801-175456.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240801-175456.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240801-175906.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240801-175906.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240801-180507.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240801-180507.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240305-005849.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240305-005849.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240305-013243.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240305-013243.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240523-233850.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240523-233850.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240408-160128.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240408-160128.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240305-161454.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240305-161454.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240328-193102.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240328-193102.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240305-162235.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240305-162235.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240305-162628.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240305-162628.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240305-162823.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240305-162823.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240305-170205.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240305-170205.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240305-170310.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240305-170310.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240305-170553.png\"](\"https://support.spendgo.com/__attachments/175374436/image-20240305-170553.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240503-225351.png\"](\"https://support.spendgo.com/__attachments/283443217/image-20240503-225351.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240506-154527.png\"](\"https://support.spendgo.com/__attachments/283443217/image-20240506-154527.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240506-161211.png\"](\"https://support.spendgo.com/__attachments/283443217/image-20240506-161211.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/283443217/Screenshot%202024-06-05%20at%205.04.29%E2%80%AFPM.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/283443217/Screenshot%202024-06-05%20at%205.05.55%E2%80%AFPM.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/283443217/Screenshot%202024-06-05%20at%204.56.00%E2%80%AFPM.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/283443217/Screenshot%202024-06-05%20at%205.04.42%E2%80%AFPM.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/283443217/Screenshot%202024-06-05%20at%205.00.44%E2%80%AFPM.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374506/CloverPOS_logo.jpg?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\"){kind=logo}
![\"image-20240301-184440.png\"](\"https://support.spendgo.com/__attachments/175374506/image-20240301-184440.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240525-004247.png\"](\"https://support.spendgo.com/__attachments/175374506/image-20240525-004247.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240528-220731.png\"](\"https://support.spendgo.com/__attachments/175374506/image-20240528-220731.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240528-221648.png\"](\"https://support.spendgo.com/__attachments/175374506/image-20240528-221648.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240212-210635.png\"](\"https://support.spendgo.com/__attachments/175374506/image-20240212-210635.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240919-204126.png\"](\"https://support.spendgo.com/__attachments/175374506/image-20240919-204126.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374506/image-20231123-051324.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374506/image-20221012-233459.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374506/image-20221012-234434.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374506/image-20221012-235011.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374506/image-20231006-190608.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374506/image-20230405-212909.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374506/image-20230621-190653.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374506/image-20230405-215547.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374506/image-20230405-214706.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175374506/image-20230405-220128.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240312-204301.png\"](\"https://support.spendgo.com/__attachments/251002904/image-20240312-204301.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240313-211157.png\"](\"https://support.spendgo.com/__attachments/251002904/image-20240313-211157.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240313-212300.png\"](\"https://support.spendgo.com/__attachments/251002904/image-20240313-212300.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240313-231423.png\"](\"https://support.spendgo.com/__attachments/251002904/image-20240313-231423.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20250819-233914.png\"](\"https://support.spendgo.com/__attachments/251002904/image-20250819-233914.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240314-001605.png\"](\"https://support.spendgo.com/__attachments/251002904/image-20240314-001605.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240314-173450.png\"](\"https://support.spendgo.com/__attachments/251002904/image-20240314-173450.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240314-180550.png\"](\"https://support.spendgo.com/__attachments/251002904/image-20240314-180550.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240314-180618.png\"](\"https://support.spendgo.com/__attachments/251002904/image-20240314-180618.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240314-180804.png\"](\"https://support.spendgo.com/__attachments/251002904/image-20240314-180804.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240506-154853.png\"](\"https://support.spendgo.com/__attachments/283770905/image-20240506-154853.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240506-161110.png\"](\"https://support.spendgo.com/__attachments/283770905/image-20240506-161110.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"iOS](\"https://support.spendgo.com/__attachments/157581629/iOS_Store_Card_Pass.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"Android](\"https://support.spendgo.com/__attachments/157581629/Android+Pass+Layout.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"Location](\"https://support.spendgo.com/__attachments/175145174/template_id.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175177742/infobip.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20241204-191211.png\"](\"https://support.spendgo.com/__attachments/433192963/image-20241204-191211.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
\n![](\"https://support.spendgo.com/__attachments/175177756/olo.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240210-003859.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240210-003859.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240210-013652.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240210-013652.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240215-061054.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240215-061054.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
\n![\"image-20240215-063729.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240215-063729.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240215-062918.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240215-062918.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240215-063010.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240215-063010.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
\n![\"image-20240215-064325.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240215-064325.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240215-064754.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240215-064754.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240215-065205.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240215-065205.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240215-065944.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240215-065944.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240215-070553.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240215-070553.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240215-070736.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240215-070736.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240215-071045.png\"](\"https://support.spendgo.com/__attachments/175177756/image-20240215-071045.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175308825/doordash+logo.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
\n![\"image-20240307-010546.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240307-010546.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
\n![\"image-20240415-211003.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240415-211003.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240415-213134.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240415-213134.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240415-201235.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240415-201235.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240415-182832.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240415-182832.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240415-215228.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240415-215228.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240415-215300.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240415-215300.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240415-220624.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240415-220624.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240415-220807.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240415-220807.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240415-203744.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240415-203744.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240415-205045.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240415-205045.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240427-002439.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240427-002439.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240429-230503.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240429-230503.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240429-232733.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240429-232733.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240430-180446.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240430-180446.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/175308825/image-20231215-235404.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240307-232931.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240307-232931.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240308-180242.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240308-180242.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"image-20240308-182922.png\"](\"https://support.spendgo.com/__attachments/175308825/image-20240308-182922.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/157516063/Select_Invoices_To_Pay.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![\"PaymentScreen1.png\"](\"https://support.spendgo.com/__attachments/157516122/PaymentScreen1.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/157516122/image-asset.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")
![](\"https://support.spendgo.com/__attachments/157516122/PaymentScreen3.png?inst-v=8927cb78-6018-4f81-bc30-f5cbfe965162\")