Olo

menu-pricing-nested-modifiers

Nesting is documented: 'Custom Boxes' describes 'nested modifier groups', a 'first level nested modifier group' that 'can be either a multi-nested group such as the Burgers and Salads, or a single nested group', with 'required/optional tags' and Min/Max Modifier Quantity per group; 'Modifier Quantities' (115005204683) and Menu Training pt. 1 document per-group Single / Multiple / Unlimited / Set-a-limit min-max / Increments and Modifier Aggregate Quantity. Shortfall: no article states a depth of three or more levels, and the Consolidate-Modifiers-on-Quantity scaling applies 'for the first nested level only'. https://olosupport.zendesk.com/hc/en-us/articles/48021726126747-Custom-Boxes · retrieved 2026-09-03 adversarially verified

menu-pricing-modifier-price-by-parent-size

Menu Admin's modifier-choice config surface carries exactly one Price field per choice ('Price is only required for brands that are not integrated to a point of sale... POS Integrated clients can skip this step since pricing will pull directly from the POS' via a single POS Entity Type + POS Mapping ID per choice). The documented way to vary a group across parents is duplication: 'You have the option to reuse existing modifier groups or make copies and assign them to other products.' Sizes are themselves modifier choices each with its own flat price (the Is Base Product article's worked example: Small $6.99 / Medium $8.99 / Large $10.99). No parent-item or size price matrix exists anywhere in the documented Menu Admin surface - per-parent modifier pricing is achieved only by copying the group, which is exactly the mechanism the claim excludes. https://olosupport.zendesk.com/hc/en-us/articles/360025658332-Company-Menu-Admin-Menu-Training-pt-1 · retrieved 2026-08-04

menu-pricing-fractional-placement differentiator

No Olo documentation on sectioned/half topping placement; Olo generally mirrors the POS modifier tree.

menu-pricing-half-and-half-rule differentiator

The documented Menu Admin surface has no portion primitive at all: products carry modifier groups whose choices have a selection type (Single/Multiple/Unlimited), min/max and aggregate quantities, and exactly one flat Price or POS Mapping ID each - nothing expresses half/whole placement, let alone a configurable pricing rule across halves. Help-centre searches for 'portion', 'half and half' and 'pizza builder' (2026-08-04) return no portions feature. This matches the record's settled grade-B findings that modifier pricing is strictly linear per choice and that no price matrix exists in the documented surface; a half-and-half rule (higher half / average / fractional toppings) has no object to attach to. For POS-integrated pizza brands any such rule lives in the POS, not in Olo. https://olosupport.zendesk.com/hc/en-us/articles/360025658332-Company-Menu-Admin-Menu-Training-pt-1 · retrieved 2026-08-04

menu-pricing-topping-quantity-tiers

Modifier Quantities is a documented first-class feature: per-choice quantity selection with Modifier Aggregate Quantity (min/max on the sum of the group), Min/Max Modifier Quantity per choice, a selectable Increment step, and a Consolidate Modifiers on Quantity product setting that multiplies modifier quantities by the parent quantity. Shortfall: pricing is strictly linear - quantity times the choice's single price - with no per-tier price multiplier, so light/regular/extra/double semantics (zero-charge light, discounted double) must be modeled as separate modifier choices each carrying its own explicit price or POS mapping. The tier-multiplier half of the claim does not exist. https://olosupport.zendesk.com/hc/en-us/articles/115005204683-Modifier-Quantities · retrieved 2026-08-04

menu-pricing-size-style-matrix differentiator

Menu Admin's documented pricing model is one flat price per product or per modifier choice; sizes are themselves modifier choices each carrying a single price (the Is Base Product worked example: Small $6.99 / Medium $8.99 / Large $10.99), and varying a modifier group across parents is done only by duplicating the group. The record's modifier-price-by-parent-size cell already established at grade B that no parent-item or size price matrix exists anywhere in the documented Menu Admin surface; a two-axis size x crust/style grid with per-cell overrides is the same missing object. POS-integrated brands pull prices directly from the POS, where any such matrix would live. https://olosupport.zendesk.com/hc/en-us/articles/360025658332-Company-Menu-Admin-Menu-Training-pt-1 · retrieved 2026-08-04

menu-pricing-included-allowance differentiator

Modifier Quantities enumerates the whole documented quantity/pricing surface: Modifier Aggregate Quantity (min/max on the sum of the group), Min/Max Modifier Quantity per choice, an Increment step, and Consolidate Modifiers on Quantity - and pricing is strictly linear, quantity times the choice's single price. There is no included-allowance field and no charge-only-for-overage behavior anywhere in the documented model (the settled topping-quantity-tiers cell already found no non-linear tier pricing exists). An 'N toppings included' rule can only be faked with $0 choices plus min/max limits, which is the workaround the claim excludes, not the capability. https://olosupport.zendesk.com/hc/en-us/articles/115005204683-Modifier-Quantities · retrieved 2026-08-04

menu-pricing-combos

Combos exist but as a POS-mapping exercise, not an Olo-native pricing engine: 'a QS brand can build and map Quick Combos on the Olo side' and at checkout 'validation will receive a response from POS that auto-applies the Quick Combo price' (Aloha FAQ); per-POS combo-mapping guides exist for Brink, Micros, Revel and SimphonyCloud (linked from Menu Mapping pt. 2), and the Aloha setup even recommends 'a marker item as a component in the Quick Combo... to avoid unwanted auto-application in-store.' Shortfall: the combo price is applied by the POS's validation response, behavior is integration-specific, and no doc describes Olo itself detecting eligible a-la-carte basket items and converting them into the combo. https://olosupport.zendesk.com/hc/en-us/articles/360001988831-Aloha-POS-FAQs · retrieved 2026-08-04

menu-pricing-upsell-prompts differentiator

AI/ML Smart Cross-Sells and 'For You' categories across Olo digital channels, with a Menu Intelligence dashboard tracking item impact on ordering behavior. Digital channels only — no POS or kiosk prompts. https://www.olo.com/ordering · retrieved 2026-08-01

menu-pricing-86-propagation

Availability changes propagate to Olo digital channels and out through Rails to marketplaces in 'near real-time.' No POS/KDS leg (Olo owns neither) and no published latency figure. https://www.olo.com/rails · retrieved 2026-08-01

menu-pricing-countdown-auto-86 differentiator

Winter 2026 shipped automated menu-item scheduling with auto-return after 1-4 hours (the scheduled-restore half). No evidence of par/countdown decrement-on-sale triggering auto-86 at zero. https://www.olo.com/winter-release-2026 · retrieved 2026-08-01

menu-pricing-dayparting

Menu-item scheduling with timed auto-return is documented; per-location-timezone daypart price scheduling is not explicitly published. https://www.olo.com/winter-release-2026 · retrieved 2026-08-01

menu-pricing-channel-price-books

Rails' actual verbatim wording is only 'Adjust menu pricing to maintain margins'. That is one sentence supporting per-marketplace markup; it does not establish named price books, per-channel price sets, or assignment of price books to channels/locations. The Winter 2026 'tiered fees' cited as reinforcement are fees, not item prices. https://www.olo.com/rails · retrieved 2026-08-01 adversarially verified

menu-pricing-dual-pricing differentiator

Searched the public help centre (olosupport.zendesk.com search API, 2026-08-04) for 'dual pricing', 'cash discount', 'surcharge', 'service fee', 'convenience fee' and 'credit card fee': the only fee-configuration docs are Dispatch delivery-fee rules, and the discount hits are Olo Loyalty offer types and Aloha POS tender articles - no cash-discount or card-price-display feature anywhere. olo.com/pay (re-read 2026-08-04) mentions no dual pricing, cash discounting or surcharging. But item prices on Olo channels pull from the integrated POS, and no document enumerates the pricing-display options in a way that would positively rule a card-price-as-base mode out, so this stays unknown rather than no.

menu-pricing-versioning-effective-dates differentiator

Partially documented, decisive page gated. Store Menu Admin (Menu Training pt. 3, public, read 2026-08-04) documents live front-end preview ('As you make changes, you can preview how the menu will appear to customers on the front-end site') and links a dedicated 'Scheduled Menu Changes' help article (id 6514298372507), but that article 302-redirects to the olo.com/zendesksso customer login and has no Wayback capture, so whether changes are staged as effective-dated versions, previewable before publish, and roll-backable after publish cannot be read publicly. Winter 2026 release notes document scheduled item availability with timed auto-return, which is availability scheduling, not menu versioning.

menu-pricing-franchise-hierarchy differentiator

Rails supports menu changes 'for a single location or in bulk' and Olo runs centralized menu management for enterprise brands. Field-level override governance is not documented. https://www.olo.com/rails · retrieved 2026-08-01

menu-pricing-allergen-nutrition

Winter 2026 added dietary tags (vegan, gluten-free) on items and modifiers with guest filtering; Summer 2026 added allergen menu tags meeting California SB 68. No recipe-derived nutrition (Olo has no recipe module). https://www.olo.com/product-release · retrieved 2026-08-01

menu-pricing-recipe-linkage differentiator

Olo's product suite contains no inventory or recipe/BOM module.

menu-pricing-3p-menu-push

Verified verbatim on Rails: '15+ Marketplace Integrations', '99% Delivery market covered', 'Make near real-time menu changes for a single location or in bulk', 'Two-way data synchronization'. This is Olo's genuinely strongest documented cell and survives adversarial reading. https://www.olo.com/rails · retrieved 2026-08-01 adversarially verified

menu-pricing-dynamic-pricing

Channel pricing and order-size-tiered fees exist; rule-based demand/time-varying item pricing with guardrails is not documented.

payments-processor-choice differentiator

Scored yes on inference with partners.olo.com as the source. I fetched partners.olo.com: it names the Standard/Gold/Platinum tiers and references 'over 400 integrated partners' but the directory renders empty ('No relevant partners found') and no payment gateway or processor partner is identified. Olo Pay being a distinct SKU makes non-Olo-Pay operation plausible, but no source affirmatively documents supported alternative processors/gateways. https://partners.olo.com/ · retrieved 2026-08-01 adversarially verified

payments-published-rates differentiator

Affirmatively verified — the Pay page publishes no rate of any kind and olo.com has no pricing page. This is one of the rare cases where no is defensible over unknown, because the absence of a pricing page across the entire site is itself observable. https://www.olo.com/pay · retrieved 2026-08-01 adversarially verified

payments-dual-pricing differentiator

Checked 2026-08-04: olo.com/pay, the Olo Pay Terms and Conditions, the Spring 2025 / Spring 2026 / Summer 2026 release pages, and help-centre searches - no mention of dual pricing or cash discounting anywhere. Olo Pay spans digital card-not-present checkout and card-present payment terminals (kiosk and pay-at-table), but its merchant-facing configuration docs are login-gated, so a two-price cash/card display cannot be positively confirmed or excluded.

payments-surcharge-guardrails differentiator

Fee configuration exists (tiered %/flat fees, separated fee and tax line items) but no documented debit/prepaid BIN exclusion or network cap enforcement.

payments-emv-nfc

Olo Pay handles card-present and card-not-present, supporting Apple Pay, Google Pay, contactless and mobile wallets. https://www.olo.com/pay · retrieved 2026-08-01

payments-softpos-tap-to-pay differentiator

Olo Pay card-present is documented exclusively as dedicated terminal hardware: 'Experience Olo Pay's POS-integrated payments on modern, reliable payment terminals' - EMV devices, USB-connected readers, with 'Pay-at-table and mobile payment available' running on those terminals. The kiosk variant is literally named 'Olo Pay Card-Present for Kiosk' (Summer 2026 terminal-management note), and the July 2023 launch described guests paying 'through an attached payment terminal.' No Olo material anywhere - release pages, help centre, olo.com/pay - offers phone-based readerless acceptance, and Olo ships no staff-facing payment app that could host Tap to Pay on iPhone or Android. https://www.olo.com/quarterly-release/spring-2025 · retrieved 2026-08-04

payments-pay-at-table

Olo Pay Card-Present terminals exist but Olo ships no server handheld and documents no tableside tip/split flow.

payments-qr-guest-pay differentiator

Not scored by the 2026-08-01 research pass.

payments-tip-adjust

Checked 2026-08-04: Olo's public tip documentation covers digital-checkout tips and Dispatch driver tip distribution (help-centre articles 35828711816219 and 360026943032); Olo Pay card-present includes pay-at-table terminals (Spring 2025 release) where some tip flow must exist, but no public page documents whether it is an on-device prompt or pre-auth-then-adjust, any batch/adjust window, or an unadjusted-tips manager screen. Olo Pay merchant configuration docs are login-gated, so the claim cannot be resolved either way.

payments-tip-pooling differentiator

No labor/workforce product in Olo's suite.

payments-offline-store-and-forward differentiator

Summer 2026 'POS offline fallback mode' covers order acceptance during POS backend outages, not card store-and-forward.

payments-offline-decline-liability differentiator

Olo advertises the surface but not the liability. The Spring 2025 release page markets Olo Pay card-present with 'Offline capabilities (store and forward) ensure your restaurant won't lose out if connection is lost' - a claim pointing the opposite direction from a loss disclosure. The public Olo Pay Terms & Conditions (last updated 2024-06-27), the document that does allocate transaction risk (s.11: unauthorized, irregular or fraudulent charges 'shall remain the full responsibility of Merchant'; s.2.6 settlement only for funds received), contain no offline, store-and-forward or deferred-authorization provision at all. Help-centre searches for 'offline', 'store and forward' and 'declined payment' (2026-08-04) surface no offline-payments article and no post-reconnect failed-offline-payments report. Neither limb of the claim - published decline-loss allocation, post-reconnect failure report - is publicly documented. https://www.olo.com/olo-pay-terms-and-conditions · retrieved 2026-08-04

payments-gift-cards

Verified against the homepage's fully enumerated 16-SKU suite (Ordering, Serve, Dispatch, Rails, Catering+, Loyalty, Order with Google, Switchboard, Olo Network, Pay, Host, Sync, Marketing, GDP, Sentiment, Accounts). No stored-value/gift product, and likewise no kiosk, KDS, labor, or inventory SKU — which validates the blanket no across the labor, inventory and kitchen sections. https://www.olo.com/ · retrieved 2026-08-01 adversarially verified

payments-house-accounts

Catering+ ships Preferred Accounts, invoicing, and tax-exempt certificate upload. Per-account credit limits and periodic statement generation are not documented. https://www.olo.com/product-release · retrieved 2026-08-01

payments-split-tender

Checked 2026-08-04: help-centre searches ('split payment', 'gift card split', 'checkout payment methods') return only Dispatch payment-flow and POS tender-configuration articles; the Summer 2026 release notes an 'Ecard systems integration for gift cards' without split detail. Whether one Olo order can settle across multiple tenders (e.g. gift card plus card), and whether pay-at-table supports seat/item/even splits, is not publicly documented; the developer portal that would settle it is login-gated.

payments-refund-void-controls

Winter 2026 added dashboard void-before-capture; Dispatch supports refunds. Role-based authorization and an immutable approver audit log are not documented. https://www.olo.com/winter-release-2026 · retrieved 2026-08-01

payments-chargeback-tooling differentiator

The Olo Pay page publishes outcome statistics ('Saved in $11M in chargeback fees', '$240,000 won in response to fraudulent disputes') but describes no dispute-management tooling, evidence submission workflow, or deadline tracking. Outcome stats are not a capability. Spring 2026 in-store dispute tracking supports partial, not yes. https://www.olo.com/pay · retrieved 2026-08-01 adversarially verified

payments-card-on-file differentiator

Verified verbatim on the Olo Accounts page: guests 'securely save their contact, delivery, and payment information on file for faster checkouts' with one-time-code verification, and 'passwordless checkout at any restaurant in the Olo Accounts network'. Note the page states '25M+ guests on the network' and 'more than 500 restaurant brands', which conflicts with the dossier identity section's '108 million connected guests' — the researcher should reconcile which metric counts what. https://www.olo.com/olo-accounts · retrieved 2026-08-01 adversarially verified

payments-payout-timing differentiator

Olo Pay page references 'flexible payment schedules' with no published deposit schedule or instant-funding option.

payments-multi-entity-routing differentiator

Per-location banking is visible but the routing structure is not: the Summer 2026 release ships 'Bulk assigning banking account details in onboarding' for Olo Pay - bulk assignment only makes sense across many location/entity accounts - and the Olo Pay T&C settle funds 'to Merchant's designated bank account' per merchant agreement, consistent with each franchisee/legal entity holding its own account under the brand's unified Dashboard reporting (e.g. the Daily Credit Card Placed Orders by Store report). Shortfall: no public document describes the MID or split-settlement structure or per-legal-entity routing rules, so the mechanism is inferred from onboarding tooling rather than documented. https://www.olo.com/product-release · retrieved 2026-08-04

payments-p2pe-pci4

Olo Pay claims 'point-to-point encryption'; Olo's DPA requires compliance with 'PCI-DSS version 4.0 and any subsequent versions.' No AoC or P2PE listing published or offered on request in public materials. https://www.olo.com/data-protection-addendum · retrieved 2026-08-01

delivery-driver-roster

Strengthened, not weakened. The Dispatch page's own framing is 'Forget about managing your own drivers', and its stated purpose is to 'eliminate the need to manage a courier fleet'. It does list 'Delivery providers and self-delivery options' as a setting, but there is no driver entity, clock-in/out, or run history. No is correct and now affirmatively supported rather than inferred. https://www.olo.com/dispatch · retrieved 2026-08-01 adversarially verified

delivery-dispatch-board

Single dashboard managing multiple provider integrations with delivery monitoring and performance analytics. Multi-order run batching to one driver is not documented (DSP-brokered model). https://www.olo.com/dispatch · retrieved 2026-08-01

delivery-route-map differentiator

Route sequencing belongs to the DSP in Olo's brokerage model; no multi-stop optimization surface is documented.

delivery-driver-tracking differentiator

'Driver tracking and delivery monitoring' is not language on the cited Dispatch page. The page markets a branded direct-delivery guest experience and DSP orchestration. Guest-facing courier tracking is highly likely in a DSP-brokered model and is implied by 'consistent guest experience', but operator-side live driver tracking is not documented. Marketing-page inference presented as documented capability. https://www.olo.com/dispatch · retrieved 2026-08-01 adversarially verified

delivery-zones-polygon differentiator

'Customizable delivery zones' is not present on olo.com/dispatch. The only geographic/limit controls published are fee limits and max transit times; a transit-time cap is not a zone. Zone configuration presumably lives behind dispatch-portal.olo.com, which is login-gated. Nothing public. adversarially verified

delivery-zone-pricing

The source does not say 'customizable delivery zones and pricing controls'. It says 'Set fee limits and max transit times'. A fee cap is a real cost control, but the 'zone' half of the cell is not supported by the cited page at all. Partial on fee limits only. https://www.olo.com/dispatch · retrieved 2026-08-01 adversarially verified

delivery-address-validation

I pulled the full body of olo.com/dispatch twice. Its complete feature inventory is: 27+ DSPs, 96% covered by 2+ providers, 28-min average delivery, 35% basket lift, Skip the Line, 'Delivery providers and self-delivery options', 'Set fee limits and max transit times', 'Automated delivery rescues', 'Easily process refunds'. The phrase 'address validation for order accuracy' appears nowhere on the cited page, and a site-scoped search found no Olo page documenting it. The researcher quoted language that is not in the source. No affirmative absence statement, so unknown, not no. adversarially verified

delivery-driver-comp differentiator

No payroll or labor module; couriers are DSP employees/contractors.

delivery-cash-reconcile

Migrated from the 2026-08-01 research pass; no source URL was recorded.

delivery-daas-dispatch

Verified verbatim on the Dispatch page: '27+ delivery service providers', '96% Of Olo brands covered by 2+ DSPs', '28 min Average delivery time', 'Automated delivery rescues'. This is the one delivery cell where the quoted numbers are actually on the page. https://www.olo.com/dispatch · retrieved 2026-08-01 adversarially verified

delivery-daas-fallback differentiator

Fallback rules for provider failures and 'automated delivery rescues' are documented, with 96% of locations covered by 2+ providers — but this is DSP-to-DSP overflow, not in-house-driver-to-DaaS overflow. https://www.olo.com/dispatch · retrieved 2026-08-01

delivery-3p-direct-integration differentiator

Olo Help Center, Supported Rails Marketplaces, enumerates the marketplaces 'we're currently live with' and names DoorDash, Grubhub and Uber Eats explicitly alongside Caviar, ezCater, delivery.com, 7NOW, Allset, DeliverLogic, EatStreet, Favor, Food Dudes, Kitchen United, Ritual and Zifty. The brand signs its own contract with each marketplace; Olo owns the integration. The Rails DoorDash self-service article documents a direct DoorDash OAuth login, store mapping and menu qualification driven from the Olo Dashboard, with no middleware vendor in the path. https://olosupport.zendesk.com/hc/en-us/articles/360032449272-Supported-Rails-Marketplaces · retrieved 2026-08-02 adversarially verified

delivery-3p-injection

Rails consolidates all digital orders regardless of origin 'without manual entry into the POS system.' https://www.olo.com/rails · retrieved 2026-08-01

delivery-menu-push

Rails pushes menu and pricing to marketplaces with per-channel markups, single-location or bulk. https://www.olo.com/rails · retrieved 2026-08-01

delivery-86-sync

Near-real-time menu changes propagate to marketplaces; item- and item-option-level 86 with restore is not explicitly enumerated as a named capability. https://www.olo.com/rails · retrieved 2026-08-01

delivery-store-pause

Rails Management lets managers 'give and remove access' to each marketplace per store, or 'for all stores and all marketplaces in bulk', from the Dashboard, and Enable/Disable Store (115000122283) switches off all online ordering with an audited reason. Shortfall, in Olo's own words: 'This feature should not be used as a means to temporarily deactivate a marketplace... Marketplaces do not quickly deactivate a store on their interface based on this feature. If orders are submitted after a marketplace has been deactivated, the orders will fail'; Olo recommends 'working directly with the marketplace' for temporary pauses. https://olosupport.zendesk.com/hc/en-us/articles/360045286812-Rails-Management-Access-Markup-Pricing-and-Roundup · retrieved 2026-09-03 adversarially verified

delivery-3p-reconciliation differentiator

Spring 2026 made marketplace discounts pass through to the POS, described by Olo as 'closing a long-standing reconciliation gap'; Rails gives near-real-time sales data by location and marketplace. Full payout-deposit matching with commission itemization and missing-order detection is not documented. https://www.olo.com/2026-spring-release · retrieved 2026-08-01

delivery-injection-error-visibility differentiator

Verified verbatim: 'Access near real-time sales and error data by location and marketplace.' Corroborated by public per-integration component health on status.olo.com. https://www.olo.com/rails · retrieved 2026-08-01 adversarially verified

delivery-tracking-page

The Dispatch page supports a branded direct-delivery experience and 'Skip the Line', but does not describe a branded order-tracking page with live status/ETA. Same over-read as the driver-tracking cell. https://www.olo.com/dispatch · retrieved 2026-08-01 adversarially verified

delivery-promise-time differentiator

Sourced to olo.com/ordering, which lists 'Order throttling' and 'Customizable capacity rules engine' but says nothing about dynamically computed quote times. Combining that with Dispatch's 'max transit times' to conclude dynamic promise-time calculation is researcher synthesis, not documentation. https://www.olo.com/ordering · retrieved 2026-08-01 adversarially verified

delivery-offline-behavior

Olo does not document explicit offline behavior for delivery. The Dispatch FAQ and Dispatch Payment Flow articles (both read 2026-08-04) walk through how Dispatch works - DSP selection, Dashboard features, setup, and the guest-pays-at-checkout money flow ('payment for the delivery quote... is added directly to the restaurant's merchant account') - with no outage/offline section, and help-centre searches for 'offline'/'outage' surface nothing for Dispatch. The claim's cash-delivery-order and driver-settlement scenarios do not exist in Dispatch's documented model at all: delivery is performed by third-party DSPs under Olo's agreements and paid digitally at checkout. https://olosupport.zendesk.com/hc/en-us/articles/360019209451-Dispatch-FAQ · retrieved 2026-08-04

digital-first-party-web

Serve is Olo's hosted white-label storefront on the brand's own domain and branding, self-service designable without engineering, with commission-free direct ordering. https://www.olo.com/serve · retrieved 2026-08-01

digital-menu-single-source

'Centralized menu management for all digital channels' from a single dashboard, synced with the integrated POS. https://www.olo.com/ordering · retrieved 2026-08-01

digital-native-app differentiator

Serve includes a branded mobile app; Summer 2026 shipped native push notifications to Serve mobile app users, and Fall 2025 added Apple ID login. Distinct from the separate Olo Network second-party app. https://www.olo.com/product-release · retrieved 2026-08-01

digital-account-saved-payment

Olo Accounts: passwordless one-time-code sign-in with saved contact, payment and delivery data, auto-filled on repeat purchase, recognized cross-brand across the Olo network. https://www.olo.com/olo-accounts · retrieved 2026-08-01

digital-upsell-engine differentiator

Olo Help Center, Sales and Orders Reports Overview, documents a 'Product Recommendation Source' report: 'Product-level sales data with attribution to where each item was added to the basket (e.g., Smart Cross Sells).' Its enumerated sources include 'Smart Cross Sell Product', 'Static Cross Sell Product', 'Cross Sell Product' and 'For You Product', filterable by Client Platform, Source and Vendor. This satisfies both limbs of the claim: rules-based (Static) and algorithmic (Smart) suggestions, plus per-item attach attribution reporting on those suggestions. Note the 10-K's Ordering-module capability list does not mention cross-sell at all - the help center is the load-bearing source here. https://olosupport.zendesk.com/hc/en-us/articles/115000124306-Sales-and-Orders-Reports-Overview · retrieved 2026-08-02 adversarially verified

digital-scheduled-pacing

Customizable capacity rules engine plus order throttling, applied to scheduled and immediate digital orders. https://www.olo.com/ordering · retrieved 2026-08-01

digital-fulfillment-modes

Pickup, delivery, curbside and 'other handoff modes' documented with mode-specific fees. Dine-in/QR table ordering is not documented as a handoff mode. https://www.olo.com/ordering · retrieved 2026-08-01

digital-qr-table

'How to Enable Dine-In' documents a Dine-In handoff mode on Serve web, the mobile app, API and Switchboard with 'Cash, credit card, and gift card payment', loyalty earn/redeem, and 'Custom fields triggered by Dine-in handoff mode selection (i.e. Table Number)' so staff know where to bring the food; Dine-In orders are exempt from throttling. Shortfall: no QR-code generation or table tent is documented, the order is prepaid rather than attached to an open POS check, and no split or tip-at-table flow is described. https://olosupport.zendesk.com/hc/en-us/articles/360050334652-How-to-Enable-Dine-In · retrieved 2026-09-03 adversarially verified

digital-kiosk differentiator

'Creating a Kiosk Experience': 'Through Olo's Ordering API, a restaurant can work with an agency to create a digital interface optimized for a physical device' (Shake Shack cited); interested brands 'reach out to your Customer Success Manager or Deployment Manager'. Olo Pay card-present terminals are marketed for kiosks. Shortfall: Olo ships no kiosk application of its own; the kiosk UI is agency-built on the API, and no accessibility or unattended-EMV documentation exists for it. https://olosupport.zendesk.com/hc/en-us/articles/115003300826-Creating-a-Kiosk-Experience · retrieved 2026-09-03 adversarially verified

digital-group-ordering

Direct hit. I reproduced olo.com/ordering's feature list: free custom-branded storefront, passwordless sign-in + checkout, pickup/delivery/curbside/other handoff modes, API + webhook library, coupon manager, AI/ML cross-selling, order throttling, capacity rules engine, centralized menu management, virtual brands. Group ordering is NOT named on the cited page. This is a fabricated citation. adversarially verified

digital-catering-portal differentiator

Catering+ is a distinct flow with guest-facing quotes, branded PDF proposals with embedded payment links, lead-time settings, invoicing, Preferred Accounts, tax-exempt certificate upload, and event/delivery calendar scheduling. https://www.olo.com/catering · retrieved 2026-08-01

digital-voice-ai-phone differentiator

Switchboard is explicitly a human-operated tool for 'staff or call center agents to quickly digitize and route phone orders' — not AI answering calls. No named certified voice-AI partner verified. https://www.olo.com/switchboard · retrieved 2026-08-01

digital-drivethru-ai

No drive-thru product of any kind.

digital-sms-ordering

Switchboard sends SMS payment links (text-to-pay) and Marketing sends SMS/MMS campaigns, but conversational text-to-order is not documented despite Olo's 2005 origin as a text-ordering product.

digital-google-order differentiator

Olo Help Center, Order with Google FAQ and Onboarding: the brand's Google Business Profile 'Food Ordering button' is toggled on and Google is enabled as a Rails partner on the Rails Management page, after which 'the location should appear on Google for ordering within the same day.' 'The Branded ordering option at the top of the OwG Ordering page is your official branded Olo-OwG integration - with images, menus, etc being syndicated from Olo.' Direct link is provisioned to the GBP and sits above 'Third Party Ordering'. Caveat on the 'Preferred by Business' limb: exclusivity is not automatic - to remove marketplace links 'the brand needs to email their marketplace contact.' Priced as a per-order 'Order with Google Fee' line item; the FY2024 10-K places it in the Network add-on module requiring Ordering and/or Rails. https://olosupport.zendesk.com/hc/en-us/articles/360050780871-Order-with-Google-FAQ · retrieved 2026-08-02 adversarially verified

digital-apple-business-connect

Sync pushes hours, phone and direct ordering links to '50+ publishers' but names none, and Apple Business Connect is not mentioned anywhere on olo.com.

digital-loyalty-attach

Olo Loyalty gives direct in-flow access: points balance and progress visible during checkout, real-time accrual and redemption, passwordless enrollment tied to the same Olo Accounts identity. https://www.olo.com/loyalty · retrieved 2026-08-01

digital-subscriptions

Checked 2026-08-04: help-centre searches for 'subscription' and 'membership' return only Loyalty campaign automations and Olo's own invoice-billing articles; the Loyalty enumerations (Campaign Types - Automations, Offers) contain no recurring-billing construct; and the ordering, loyalty and marketing product pages plus the 2026 release pages never mention a guest subscription or membership program. Absence from these surfaces is suggestive, but the ordering/loyalty admin docs are partially gated, so scored unknown rather than no.

digital-promo-parity

Coupon manager plus location-based promotional banners (Summer 2026) span Olo digital channels; POS and kiosk parity depends entirely on the integrated POS, which Olo does not control. https://www.olo.com/ordering · retrieved 2026-08-01

digital-guest-data-ownership differentiator

Olo markets 'full guest data ownership' and GDP 'without vendor lock-in,' but publishes no bulk export mechanism, format, or fee position. Its DPA designates Olo a joint Controller, which qualifies the ownership claim. https://www.olo.com/gdp · retrieved 2026-08-01

digital-checkout-pci-sca

Checkout is Olo-hosted so card data never touches the brand's page, and Olo's DPA mandates PCI DSS v4.0. Script-integrity monitoring (6.4.3/11.6.1) and 3DS support are not documented publicly. https://www.olo.com/data-protection-addendum · retrieved 2026-08-01

digital-surcharge-transparency differentiator

Winter 2026 tiered fees (percentage or flat, varying by order size) and Summer 2026 transparent display of Fees and Estimated Taxes as separate guest-facing line items. Card-surcharge jurisdiction and brand-rule handling is not documented. https://www.olo.com/product-release · retrieved 2026-08-01

guest-loyalty-unified-profile

GDP unifies transactional, behavioral, demographic and offline data for known and unknown guests across POS, ordering, loyalty, payments, reservations, web and email/SMS. Olo Pay Card-Present pulls in-store card transactions into the same profile. Dedup/merge rules not published. https://www.olo.com/gdp · retrieved 2026-08-01

guest-loyalty-thirdparty-identity-attach differentiator

Marketplace orders cannot attach automatically: for Rails orders 'the marketplace... own[s] customer data. In most cases, customer data shared with Olo is limited to the customer's first name and last initial.' What exists is manual and partner-specific: the Loyalty Dashboard 'Link a Purchase' (46361210581403) attaches an unclaimed purchase to a member by phone number, members can claim receipts in the Member Portal, and the 'Storefront by DoorDash Integration' (46381567369883) credits points only to members who log in ('No support for accruing points on guest orders'). Shortfall: no automatic identity match on DoorDash/Uber Eats/Grubhub marketplace orders. https://olosupport.zendesk.com/hc/en-us/articles/13470115810203-What-is-the-difference-between-Rails-and-Dispatch · retrieved 2026-09-03 adversarially verified

guest-loyalty-accrual-models

Verified verbatim on the Loyalty page: 'Flexible reward structures (points, visits, spend-based)', alongside 'Gamification & tiering systems', 'Multi-concept loyalty programs' and 'Points balance & progress tracking at checkout'. Claim-level marketing, but the quotation is accurate and the capability is explicit. https://www.olo.com/loyalty · retrieved 2026-08-01 adversarially verified

guest-loyalty-tiers differentiator

'Gamification & tiering systems' are marketed. Automatic promotion/demotion on a rolling spend or visit window is not documented. https://www.olo.com/loyalty · retrieved 2026-08-01

guest-loyalty-offline-behavior differentiator

Olo Loyalty's POS-integration docs state offline behavior explicitly: 'Olo Loyalty functionality is unavailable when the POS is in Offline Mode' - the documented answer is blocked, not queue-and-reconcile - and the same article documents the reconciliation edge case: if an order with an applied reward transitions to offline mode before completion, the reward remains in the member's balance despite being applied to the transaction, a stated duplicate-redemption risk. Behavior is documented per POS integration (Toast article read 2026-08-04; a parallel Revel integration article exists). https://olosupport.zendesk.com/hc/en-us/articles/46383252653979-Toast-Integration · retrieved 2026-08-04

guest-loyalty-offer-stacking-rules differentiator

The 'Offers' article has a section 'Olo Loyalty Offer Stacking Is Not Supported': 'Olo Loyalty does not allow multiple Olo Loyalty offers to be applied in a single transaction. A guest can only use one Olo Loyalty offer at a time'; rewards 'can't be stacked'; combining with non-Olo coupons 'is up to your system rules'. 'Offer Configuration Options' adds that Multiply Points multiples 'do not stack' and a Maximum Applications Per Purchase cap. Shortfall: the rule is fixed (exclusive only); there is no operator-configurable stackable/exclusive flag or precedence order. https://olosupport.zendesk.com/hc/en-us/articles/46336823229979-Offers · retrieved 2026-09-03 adversarially verified

guest-loyalty-targeted-offers differentiator

Olo Help Center, Create and Send to an Audience: in the campaign builder the operator selects an action to 'send an offer, email, or text message,' turns the audience 'Segment ON,' and defines filters matching 'any' or 'all' - the worked example being 'to target those who lapsed 90 days, enter Visits | is | 0 | with last (hours) | 2160.' Offers are therefore issuable to a dynamically defined audience, not broadcast-only. Campaign Types (Automations) adds item- and spend-triggered issuance: Purchase Items Campaign 'triggers when specific item(s) are purchased (by PLU or Item Name)', Purchase Total, Visit Threshold and Point Threshold campaigns. Rules over recency, frequency, spend and items purchased are all present. https://olosupport.zendesk.com/hc/en-us/articles/46359010493083-Create-and-Send-to-an-Audience · retrieved 2026-08-02 adversarially verified

guest-loyalty-rfm-segmentation differentiator

SHORTFALL: the segments are not precomputed - the operator builds every query. The claim requires lifecycle segments computed automatically 'without the operator building the queries.' Olo Help Center, Common Audience Filter Combinations, is a cookbook teaching operators to hand-assemble them: 'Lapsed Members' is 'Visits | is | 0 | with last (hours) | 2160'; 'New Registered Members' is a pair of Brand Join Date conditions with an hour value the operator computes as '24 hours (1 day) plus 10 hours, resulting in 34 hours.' The underlying filter dimensions are genuinely rich (Visits, Brand Join Date, Offer Expiry, Offer Not Used, opt-in state), so rules-based segmentation is real - but no shipped RFM or new/regular/at-risk/lapsed/VIP segment set exists. Help center search for 'recency' and 'cohort' returns zero articles. Downgraded from yes. https://olosupport.zendesk.com/hc/en-us/articles/46359153784731-Common-Audience-Filter-Combinations · retrieved 2026-08-02 adversarially verified

guest-loyalty-lifecycle-automation

Guided automation builder plus a library of prebuilt automations; Olo cites 75% open rates on automated welcome emails and 15% re-order rates from automated takeout reminders. https://www.olo.com/marketing · retrieved 2026-08-01

guest-loyalty-native-email-sms differentiator

SHORTFALL: email is not native - it is delivered by the third-party Infobip integration. Olo Help Center, Email Actions: 'Email campaigns are only supported with the Infobip integration'; 'For an Infobip email integration, you must use a Infobip Broadcast Email Template'; the operator authors the creative in Infobip's portal and pastes a Template ID into Olo; and 'Infobip emails triggered from the Olo Loyalty Dashboard do not support substitutions,' so per-guest personalization is unavailable on that path. Email Notifications additionally support Mailchimp. SMS is stronger - Text Message Actions composes body copy natively in the campaign builder - but the Infobip Integration article states Infobip is the channel for 'Email and SMS marketing messaging' and 'Contact your Customer Success Manager to enable Infobip.' Downgraded from yes; the record's cited marketing page claimed a single-dashboard native send. https://olosupport.zendesk.com/hc/en-us/articles/46339840523291-Email-Actions · retrieved 2026-08-02 adversarially verified

guest-loyalty-consent-management

Summer 2026 shipped an automatic TCPA litigator check protecting campaigns from problematic numbers. Per-channel consent capture with timestamp and source of consent, and revocation handling beyond STOP, is not documented. https://www.olo.com/product-release · retrieved 2026-08-01

guest-loyalty-10dlc-registration

Olo sends SMS/MMS natively so 10DLC is necessarily handled somewhere, but Olo publishes nothing about brand/campaign registration responsibility.

guest-loyalty-campaign-attribution differentiator

Campaign performance reporting with order and sales lift measurement; Fall 2025 added Holdout Groups so marketers can measure incrementality against a control group. https://www.olo.com/quarterly-release/fall-2025 · retrieved 2026-08-01

guest-loyalty-data-export-portability differentiator

Data-ownership and no-lock-in claims are prominent, but no self-serve CSV/API export path for the full guest list and transaction history is documented. https://www.olo.com/gdp · retrieved 2026-08-01

guest-loyalty-cdp-event-api differentiator

GDP is itself a restaurant CDP ingesting from dozens of systems and distributing across the Engage suite, and status.olo.com lists a 'Webhooks' component — but the outbound event schema and subscription model are behind the login-gated developer portal. https://status.olo.com/ · retrieved 2026-08-01

guest-loyalty-review-capture-routing differentiator

Sentiment runs automated post-visit surveys, intercepts and routes negative feedback into service recovery, and steers satisfied guests toward Google, Facebook, Yelp, Grubhub, OpenTable and TripAdvisor. Summer 2026 added 24/7 automated AI review responses. https://www.olo.com/sentiment · retrieved 2026-08-01

guest-loyalty-referral-program

Olo Loyalty's 'Full List of Campaign Types' enumerates all ten automations - Date & Time, Recurring, Next Visit, Purchase Items, Purchase Total, Registration, Visit Threshold, Birthday, Point Threshold, Direct Trigger - and no referral mechanic is among them. The companion Offers article's offer-type list (Add Points, BOGO, Dollar Discount, Percentage Discount, Free Item, Multiply Points, Price Adjustment) likewise has no two-sided referral reward, and help-centre searches for 'referral' and 'refer a friend' (2026-08-04) return nothing on point. Per-guest referral codes/links, referred-first-order attribution and two-sided rewards do not exist in Olo Loyalty; the closest primitive is the Direct Trigger Campaign, which fires from an external API call and would require the brand to build referral tracking itself. https://olosupport.zendesk.com/hc/en-us/articles/46322497040923-Campaign-Types-Automations · retrieved 2026-08-04

guest-loyalty-wallet-pass differentiator

'Mobile Passes Integration': members 'pull out their iOS or Android Mobile Pass and scan it', shared via 'Add to Apple Wallet' / 'Add to Google Wallet' buttons; 'When there is a push update to all the passes, the old version will automatically be removed.' Shortfalls: it is 'an in-store feature add-on' enabled by the CSM; passes are generated by a third party (app.passcreator.com links); the pass identifies the member (phone or Olo Loyalty Id in a QR) and the points balance is 'retrieved and displayed on the integrated platform', not stated as shown on the pass itself; 'not supported on watchOS'; SMS cannot share the download link. https://olosupport.zendesk.com/hc/en-us/articles/46382083496987-Mobile-Passes-Integration · retrieved 2026-09-03 adversarially verified

guest-loyalty-privacy-rights-tooling

Deletion paths are documented, but guest-side and vendor-side rather than operator tooling. Olo Account holders self-serve: 'Click Delete Account' in Olo Account Settings, after which 'Olo will disassociate all of your personal information from your account'. Olo Loyalty members use a 'Delete My Accounts form' reviewed by 'A customer support representative' (46380474871579). Operators route requests through Olo Support: the intake form's User Access & Management category covers 'deactivate a guest' (44765456164635). Shortfall: no operator-facing admin tool to locate, export or delete a guest's data is documented, and no access/export request path is described. https://ologuesthelp.zendesk.com/hc/en-us/articles/6025270811035-How-can-I-delete-my-account · retrieved 2026-09-03 adversarially verified

guest-loyalty-redemption-fraud-controls

Three documented controls. 'Limit Purchase Claims Via Member Window' restricts receipt/purchase claims to a window, 'Up to 1 successful claim every 6 hours' by default, with max submissions and window hours set 'through your Customer Success Manager during onboarding'. 'Offer Configuration Options' documents Multiple-use Limits ('use 2 times in 7 days', 'use 1 time in 12 hours'), Maximum Offer Uses Per Member and Maximum Applications Per Purchase. 'Fraud Detection Export' flags members whose daily transaction count exceeds a chosen 'Minimum Txn/Day' over a 7-day window. Shortfall: no manager approval on redemption and no employee self-redemption flagging; the claim-window limit is CSM-configured, not self-serve. https://olosupport.zendesk.com/hc/en-us/articles/46370425355931-Limit-Purchase-Claims-Via-Member-Window · retrieved 2026-09-03 adversarially verified

guest-loyalty-ai-offer-recommendation differentiator

SHORTFALL: content drafting only, no audience or send-time recommendation, and no product documentation. The only A/B-grade AI evidence located is one line in the FY2024 10-K Marketing module capability list: 'Advanced tools such as our AI creative assistant that leverages generative AI to empower marketers to instantly craft new content.' That reaches the claim's 'offer content' limb and nothing else - no documented AI/ML recommendation of target audience or send timing. The Olo Help Center returns zero articles for the creative assistant, for 'AI', or for 'Guest Intelligence Signals', the Summer 2026 release-note item the record relied on; that basis is a marketing page with no documentation behind it. Downgraded from yes. https://www.sec.gov/Archives/edgar/data/1431695/000143169525000010/olo-20241231.htm · retrieved 2026-08-02 adversarially verified

guest-loyalty-stored-value-gift

No stored-value/gift product in Olo's enumerated suite; gift cards arrive via integrated third-party providers.

reporting-realtime-dashboard

Olo Dashboard shows near-real-time sales and error data by location and marketplace. A dedicated off-premise mobile reporting app is not documented. https://www.olo.com/rails · retrieved 2026-08-01

reporting-eod-closeout

No drawer, no cash tender, no tax settlement — EOD closeout is a POS artifact.

reporting-pmix-modifier-level

Fall 2025 Menu Intelligence dashboard tracks how menu items affect ordering behavior for digital channels. Modifier-level quantity and net sales, and revenue-center slicing, are not documented. https://www.olo.com/quarterly-release/fall-2025 · retrieved 2026-08-01

reporting-comps-voids-audit

Migrated from the 2026-08-01 research pass; no source URL was recorded.

reporting-cash-over-short

Migrated from the 2026-08-01 research pass; no source URL was recorded.

reporting-labor-productivity

No clocked-hours data source.

reporting-server-scorecards differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

reporting-channel-profitability differentiator

Sales by location and marketplace, guest segmentation by channel (Fall 2025), Spring 2026 IC+ interchange and network fee breakdown, and marketplace discount pass-through to the POS. Full margin net of each marketplace's commission is not documented as a single report. https://www.olo.com/2026-spring-release · retrieved 2026-08-01

reporting-multiloc-drilldown differentiator

Olo Help Center, Sales and Orders Reports Overview: reports are generated by selecting 'Report Category, Report Date Range, and Store Locations,' giving a group rollup over a selected estate. Side-by-side location comparison is served by the by-store report types - 'Closed Orders by Store', 'Daily Credit Card Placed Orders by Store', 'Product Breakdown - products broken out by restaurant', 'Time of Day Breakdown... by restaurant', 'Failed Orders by Store'. Drill to the individual transaction is served by 'Itemized Orders - list of orders', 'Itemized Adjusted Orders' and 'Coupon Redemptions - broken out by restaurant and order'. Mechanism caveat: this is report generation with .xlsx/.csv download rather than click-through drill-through in a single view. Replaces the record's prior reasoning, which inferred the cell from Olo's customer size rather than from any report inventory. https://olosupport.zendesk.com/hc/en-us/articles/115000124306-Sales-and-Orders-Reports-Overview · retrieved 2026-08-02 adversarially verified

reporting-custom-report-builder differentiator

The reporting docs enumerate the surface and a builder is not in it: 'There are several pre-configured sales reports available' - 19 named report categories (Daily Placed Orders through Third Party Coupon Redemptions), each parameterized only by report category, date range and store selection, downloadable as .xlsx/.csv - and the Insights product is fixed dashboards (Overview | Insights, read 2026-08-04) offering filters and CSV download of 'the visible report' only. Help-centre and release searches for a dimension/measure report builder (2026-08-04) return nothing; the Spring 2026 release's new IC+ fee report is itself another canned report. https://olosupport.zendesk.com/hc/en-us/articles/115000124306-Sales-and-Orders-Reports-Overview · retrieved 2026-08-04

reporting-scheduled-delivery

Sentiment offers 'dynamic dashboards and schedulable reports.' Whether scheduling extends to all Olo reports is not documented. https://www.olo.com/sentiment · retrieved 2026-08-01

reporting-raw-warehouse-export differentiator

No documented S3/SFTP/Snowflake/BigQuery scheduled export. Enterprise Olo deployments commonly do this, but it is not published.

reporting-public-api differentiator

Verified verbatim: 'Credentials for production will only be granted after certification, which must be completed separately for each Olo API.' Combined with developer.olo.com serving only a login form, partner-gated/partial is the right call — this is one of the few cells where the researcher resisted the marketing read. https://www.olo.com/api-usage-terms · retrieved 2026-08-01 adversarially verified

reporting-webhooks differentiator

'Webhooks' is a monitored component on Olo's public status page, confirming the capability exists. Retry semantics and payload signing are undocumented publicly. https://status.olo.com/ · retrieved 2026-08-01

reporting-api-not-upcharged differentiator

No pricing published at all, so API cost position cannot be determined.

reporting-tier-paywall differentiator

No published tiers.

reporting-history-retention differentiator

Checked 2026-08-04: the Sales and Orders Reports Overview exposes a free-form 'Report Date Range' picker with no stated retention floor, truncation policy, or archive fee; Loyalty Insights allows a start date 'any date in the past' but caps each query window at 31 days. No public Olo page commits to - or denies - 24 months of queryable transaction-level detail, and a retention window could be stated in the gated Dashboard/admin docs, so the claim stays unresolved.

reporting-anomaly-alerts differentiator

Guest Intelligence Signals surfaces monthly behavioral anomalies with recommendations; Sentiment flags emerging trends 'before they impact revenue'; Spring 2026 added real-time payment terminal health monitoring. Operator-configured metric thresholds are not documented. https://www.olo.com/product-release · retrieved 2026-08-01

reporting-nl-query

Guest Intelligence Signals returns plain-English recommendations, but that is generated insight, not an ad-hoc natural-language query interface.

reporting-guest-cohorts differentiator

SHORTFALL: no lifetime-spend cohort reporting, and the analysis window is capped. Olo Help Center, Overview Insights, does deliver two of the claim's three limbs against identifiable loyalty records: new-versus-returning ('Total Unique Members', 'New Members', and member-versus-non-member splits including 'Member Adoption Rate', 'Non-Member Sales'), and visit frequency ('Member Frequency - the ratio of unique members who made at least one visit to the total number of member visits'). The lifetime-spend cohort limb is absent: 'Member Sales' is period revenue, comparison is only to Prior Period or Prior Year, and 'End Date - select any date in the past, up to 31 days after the chosen Start Date' caps the window at 31 days, which forecloses cohort tracking. Help center search for 'cohort' returns zero articles. Downgraded from yes. https://olosupport.zendesk.com/hc/en-us/articles/46272000417947-Overview-Insights · retrieved 2026-08-02 adversarially verified

reporting-sales-forecast differentiator

ML predictive analytics is documented for guest behavior and churn, not for forward sales at daypart granularity.

reporting-tip-tax-compliance

No payroll or employee tip data.

multi-location-org-hierarchy

Olo serves 800+ brands across ~90,000 locations with location grouping and multi-concept loyalty programs, but a named 3-level hierarchy object that reporting and permissions scope to is not documented. https://www.olo.com/about-us · retrieved 2026-08-01

multi-location-central-menu-publish

Centralized menu management publishes 'for a single location or in bulk' in near real time. A publish/version history recording what was pushed, when and by whom is not documented. https://www.olo.com/rails · retrieved 2026-08-01

multi-location-local-override-policy differentiator

The corporate-master / store-override split is documented: 'The Store Menu Admin is where you can turn on and off items from the Company Menu, which serves as the master menu, and apply them to specific locations'; stores can add or remove modifier groups per store menu (dedicated article 115000090243), and for POS-integrated brands each store's prices 'pull directly from the POS' - so availability and effective price vary locally while item definitions live in the corporate Company Menu. Shortfall: no per-field lock rules are documented - nothing shows corporate locking name/image/description while exposing price, or that locked fields are non-editable at store level. https://olosupport.zendesk.com/hc/en-us/articles/360026137891-Store-Menu-Admin-Menu-Training-pt-3 · retrieved 2026-08-04

multi-location-price-zones

Per-channel and per-marketplace pricing adjustment is documented; per-location-group and per-daypart price tiers on a single item record are not. https://www.olo.com/rails · retrieved 2026-08-01

multi-location-scheduled-publish differentiator

Menu item scheduling with timed auto-return exists (Winter 2026). Future-dated publish interpreted per location timezone with post-activation rollback is not documented. https://www.olo.com/winter-release-2026 · retrieved 2026-08-01

multi-location-new-store-template differentiator

New stores inherit configuration from a corporate template in two places: the Company Menu 'is considered the master menu, which provides information to each of the Store Menus' (Menu Training pt. 1, 360025658332), and the Loyalty Dashboard 'Manage Stores' (46364209387931) adds stores singly or by CSV import against a downloadable template. Shortfall: launching a location is a support workflow ('Launch, Transfer, or Close a Location' is an intake-form category; 'Contact your Customer Success Manager to fully enable your store'), no configuration-clone action or time-to-open is published. https://olosupport.zendesk.com/hc/en-us/articles/360026284851-Menu-Training-Introduction · retrieved 2026-09-03 adversarially verified

multi-location-corp-vs-franchisee-roles differentiator

Two dashboards, both documented. Ordering: 'User Management Overview' (360051811792) gives the Brand Administrator role the power to 'Create Dashboard roles and manage the permissions that make up each role', 'Manage store assignments for users' and manage partner permissions; the Company Menu is 'the master menu, which provides information to each of the Store menus' with a per-product 'Restaurants can change base cost?' flag. Loyalty: 'Dashboard User Permissions' defines named Franchisee roles ('Insights', 'Insights & Support', 'Insights & Lite', 'Insights & Marketing'...) that 'can view their insights (excluding campaign data)' with store-scoped permissions, and 'SMS Send Limits for Franchise Users (LSM Accounts)' caps franchisee sends. Note: Ordering's User Management tool is enabled through the CSM. https://olosupport.zendesk.com/hc/en-us/articles/46365406425115-Dashboard-User-Permissions · retrieved 2026-09-03 adversarially verified

multi-location-royalty-calculation differentiator

No franchise financial management product in Olo's suite.

multi-location-royalty-collection

Migrated from the 2026-08-01 research pass; no source URL was recorded.

multi-location-consolidated-reporting

Above-store aggregation across sales, marketplaces and guest segments is Olo's default reporting posture for enterprise brands, with by-location and by-marketplace slicing. https://www.olo.com/rails · retrieved 2026-08-01

multi-location-normalized-item-rollup differentiator

Cross-location item rollup exists: the 'Product Breakdown' report gives 'Products broken out by restaurant' across whatever store set is selected, and store menus are instances of the corporate Company Menu ('the master menu'), so reporting keys to shared corporate products rather than per-store item lists. Shortfall: the docs never address the claim's hard case - whether rollup survives a store renaming or locally diverging an item - and store menus can carry store-specific deviations whose normalization is undocumented. https://olosupport.zendesk.com/hc/en-us/articles/115000124306-Sales-and-Orders-Reports-Overview · retrieved 2026-08-04

multi-location-cross-location-giftcard

No first-party stored-value product.

multi-location-cross-location-loyalty

Olo Loyalty supports multi-concept programs on a brand-wide guest profile; Olo Accounts recognizes a guest across the entire Olo network, not just one location. https://www.olo.com/loyalty · retrieved 2026-08-01

multi-location-multi-brand differentiator

The Ordering product explicitly supports virtual brands, and Loyalty supports multi-concept programs. The 'same hardware and drawer' half of the requirement is POS-side and outside Olo's control. https://www.olo.com/ordering · retrieved 2026-08-01

multi-location-multi-tax-jurisdiction

Per-location tax handling with marketplace tax-exempt order support (Fall 2025), catering tax-exempt certificate upload (Summer 2026), and estimated taxes shown as a separate guest line item. Authoritative tax calculation generally originates in the integrated POS. https://www.olo.com/product-release · retrieved 2026-08-01

multi-location-multi-currency-locale

Olo is predominantly US-focused; no multi-currency capability is documented.

multi-location-config-audit-log differentiator

The Menu Audit Log records 'a full history of menu updates, who is making them, how often, and the specific change details': edit date/time in local time, company vs vendor (store) menu, the action performed, 'Manager that performed the action', stores affected, and the place on the menu where the change was made - with search, filtering, .csv export, and review 'up to 30 days at a time.' Shortfall: it covers menu changes only - permissions, discounts/coupon setup, tax and other configuration objects have no documented audit trail - no immutability or retention statement exists, and the live article now sits behind customer SSO (the live URL 302s to olo.com/zendesksso; the cited 2022-01-29 Wayback capture is the page actually read). http://web.archive.org/web/20220129041947/https://olosupport.zendesk.com/hc/en-us/articles/360019752171-Menu-Audit-Log-Overview · retrieved 2026-08-04

multi-location-enterprise-sso differentiator

'Dashboard Login & Account Creation': 'if your company uses Single Sign On (SSO), then you must log in to Dashboard using your company's "Identity Provider" (rather than using the Olo Dashboard login page)', and private help-centre articles require login 'via SSO' when the brand uses 'a Third Party Identity Provider'. Shortfall: the protocol (SAML vs OIDC) is not named, no IdP setup guide is public, and SCIM provisioning/deprovisioning is not documented. https://olosupport.zendesk.com/hc/en-us/articles/4422086507035-Dashboard-Login-Account-Creation · retrieved 2026-09-03 adversarially verified

multi-location-enterprise-api differentiator

Withdrawing the old citation: developer.olo.com now 302s to /Account/Login (5,710-byte form, re-probed 2026-08-09), so no public endpoint contract is readable. What is readable is the public help centre. Reports are built by selecting 'the Report Category, Report Date Range, and Store Locations', and the catalogue includes 'Orders placed for a restaurant or group of restaurants by day', 'Closed Orders by Store', 'Itemized Orders' and 'Product Breakdown - Products broken out by restaurant', downloadable as .xlsx or .csv - transaction-level data across an arbitrary set of locations from one authenticated Dashboard session, no per-location credentials. Webhooks Overview (article 115005291346) adds a brand-wide push channel: webhooks 'provide order, menu, user, and vendor data as it changes', enabled per brand in the Dashboard. Shortfall: the multi-location export is an interactive Dashboard report, not a documented programmatic endpoint - for the webhook and API contract that same article says 'reference the Developer Portal documentation' and 'Olo can provide access to the Developer Portal', which is customer-gated. So the cross-estate data exists and is retrievable, but no publicly documented single-call API contract does. https://olosupport.zendesk.com/hc/en-us/articles/115000124306-Sales-and-Orders-Reports-Overview · retrieved 2026-08-09 adversarially verified

multi-location-central-labor-policy

No labor module.

extensibility-public-api-docs

Re-evidenced 2026-08-09 - the old citation (developer.olo.com) is now only a login form and a gate is not by itself proof of absence, so the cell now rests on Olo's own published API Terms of Use, which state the position affirmatively. Section 3: "'Confidential Information' means the Olo APIs, all information provided by Olo about the Olo APIs, performance and any other specifications for the Olo APIs, including any Olo-provided specifications used by you to build your own API(s) for integration with Olo... You shall not disclose Confidential Information to any third party." Section 1(e): "Olo will make credentials available to you through the Olo developer portal... Credentials for production will only be granted after certification, which must be completed separately for each Olo API." Corroborated by Olo's own public SDK README, which links developer.olo.com/docs/load/olopay and annotates it "(Note: requires an Olo Developer account)", and by the live probe: developer.olo.com and every path under it 302 to /Account/Login (5,710 bytes; /robots.txt and /sitemap.xml return the portal's own NotFound page). Omnivore's docs sit behind panel.omnivore.io/login (403 to anonymous fetch). One narrow carve-out, which does not change the value: the Olo Pay client SDK class reference is public at ololabs.github.io, and signature-auth code samples are public at github.com/ololabs/dev-support-code-samples - but those are client-side helpers, and the Ordering, Rails, POS and webhook API references they point at are the confidential, credentialed material. https://www.olo.com/api-usage-terms · retrieved 2026-08-09 adversarially verified

extensibility-api-access-cost differentiator

No pricing published; API Usage Terms mention only a discretionary penalty fee for breach.

extensibility-partner-revshare

Verified that partners.olo.com discloses no referral fee, revenue share, or certification cost — but that is silence, not an affirmative statement that no revenue share exists. Per the ground rules this must be unknown. The note's own text ('discloses no...') describes absence of documentation, which the researcher then scored as a factual no. adversarially verified

extensibility-free-sandbox differentiator

A test environment exists: 'What is OloCloud?' says 'Once we've tested the integration in our test environment, we'll connect you with a developer who will approve the integration for testing in our production environment'; the Loyalty 'Olo Ordering Integration' article refers to 'the Olo Sandbox account', 'Sandbox API and oAuth credentials' and an 'Olo Test Lab'. Shortfall: the sandbox is provisioned by Olo for contracted brands and certifying partners ('If Olo Sandbox account is available'); it is not free, self-serve, or documented with seeded data. https://olosupport.zendesk.com/hc/en-us/articles/115005674526-What-is-OloCloud · retrieved 2026-09-03 adversarially verified

extensibility-oauth-partner-apps

'Olo Ordering Integration' (Loyalty): 'the Olo integration team sends the Olo Loyalty Sandbox API and oAuth credentials', 'Olo sets up the oAuth and the API Integration', and to disable, 'Olo disables the oAuth and API integrations'. So the Loyalty API authenticates integrations with OAuth credentials that Olo issues and revokes per integration. Shortfalls: credentials are issued by Olo's integration team, not granted by the operator; scopes are not documented; the Ordering platform API's own auth model remains behind the login-gated developer portal. https://olosupport.zendesk.com/hc/en-us/articles/46381686489883-Olo-Ordering-Integration · retrieved 2026-09-03 adversarially verified

extensibility-webhooks-push

'Webhooks' is a first-class monitored component on Olo's status page, confirming push exists; the event catalog and lifecycle coverage are not publicly readable. https://status.olo.com/ · retrieved 2026-08-01

extensibility-webhook-reliability differentiator

Signing is documented: in the Olo Ordering Integration the 'Brand configures the Webhooks and share the generate Secret with Olo integration team', who configure 'the secret in Olo Loyalty' to verify the order-event webhooks; the OloCloud POS interface likewise lists 'Signature validation' as a requirement (115005674526). Shortfall: no public page documents retry with backoff, redelivery, or replay; the Webhooks Overview (115005291346) defers those to the login-gated Developer Portal. https://olosupport.zendesk.com/hc/en-us/articles/46381686489883-Olo-Ordering-Integration · retrieved 2026-09-03 adversarially verified

extensibility-order-injection-api

Order injection is Olo's central function — Rails marketplaces, Order with Google, Switchboard, the Olo Network app and partner front-ends all inject through Olo's Ordering API into the brand's POS as normal tickets. https://www.olo.com/rails · retrieved 2026-08-01

extensibility-menu-write-api differentiator

Menus are managed in Olo's dashboard and pushed outward; whether the API accepts menu writes is not publicly documented.

extensibility-data-symmetry differentiator

Checked 2026-08-04: developer.olo.com is login-gated and the public API Usage Terms grant production credentials only after per-API certification, so no endpoint reference is publicly readable. Olo's public surface names the API families (Ordering, Dispatch, Point of Sale on status.olo.com; Omnivore's POS middleware APIs) but shows nothing about which objects are readable versus writable, so read/write parity across orders, menu and customers cannot be assessed.

extensibility-published-rate-limits

Verified verbatim in the API Usage Terms: Olo 'may at any time, and over any given period of time, delay or limit the number of Calls', and prohibits exceeding 'reasonable request volume, as set by Olo from time to time... as determined by Olo in its sole discretion.' Affirmative refusal to publish numerics, so no is correct rather than unknown. https://www.olo.com/api-usage-terms · retrieved 2026-08-01 adversarially verified

extensibility-doordash-preferred differentiator

Cited URL 404s (get.doordash.com path is dead; it redirects to merchants.doordash.com, which also returns 404), but the underlying fact checks out independently: the 2026 DPIP cohort is Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper. Olo is absent. Conclusion upheld; citation should be repointed to about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

extensibility-first-party-delivery-integrations differentiator

Olo Help Center, Set Up the Rails DoorDash Integration (Self-Service): brands 'log in with their DoorDash account, using DoorDash's secure login (oAuth), then select the Olo and DoorDash stores they want to map,' then Activate Integration to reach 'Live on Marketplace'. The article explicitly covers migrating off competing middleware - 'You can move your store integration from another provider to Olo through the screen... once you integrate the store through Olo orders will start to be directed to Olo.' Uber Eats and Grubhub are named on Supported Rails Marketplaces. No Otter/Chowly/Deliverect/Checkmate layer is involved; Rails is Olo's own module, though the docs note 'Rails billing will need to be setup for the Olo store.' https://olosupport.zendesk.com/hc/en-us/articles/27060912955035-Set-Up-the-Rails-DoorDash-Integration-Self-Service · retrieved 2026-08-02 adversarially verified

extensibility-middleware-compatibility

Olo's partner directory lists Chowly and Cuboh, each stamped 'This integration is currently only supported through the Omnivore API', i.e. they inject into the POS through Olo's Omnivore middleware arm rather than treating Olo Ordering as an endpoint. The olo.com sitemap (661 URLs) has no Deliverect, Otter or Checkmate partner page. Shortfall: two aggregators, both via Omnivore only; Olo itself is not documented as a middleware endpoint. https://www.olo.com/partners/chowly · retrieved 2026-09-03 adversarially verified

extensibility-accounting-connectors

Restaurant365 is a listed Olo Connect partner ('restaurant-specific accounting and back-office software platform'), but the page names no data flow, journal mapping or ownership of the connector. The 661-URL olo.com sitemap contains no QuickBooks Online, Xero or Sage partner page. Shortfall: no QuickBooks Online connector, and the R365 listing does not establish a vendor-maintained journal-entry integration. https://www.olo.com/partners/restaurant365 · retrieved 2026-09-03 adversarially verified

extensibility-payroll-export

No labor hours data to export.

extensibility-bi-data-warehouse differentiator

Checked 2026-08-04: olo.com/gdp markets 'no data silos or vendor lock-in' and pushing guest data to 'other destinations' but names no export mechanism; the Loyalty 'Export Data' article documents manual CSV downloads only; the Spring and Summer 2026 release pages and help-centre searches for 'Snowflake' and 'data share' surface no scheduled export to a customer-controlled warehouse/S3/SFTP destination. An enterprise data feed could exist behind the gated developer portal or as a contracted service, so unresolved rather than no.

extensibility-app-marketplace

A public, filterable Partner Directory of 400+ integrated partners is browsable without login. Operator self-install (vs. a partnership inquiry / sales-assisted enablement) is not documented. https://partners.olo.com/ · retrieved 2026-08-01

extensibility-custom-fields-scripting

Custom fields exist on the ordering flow: 'Custom fields can be leveraged to capture the customer's table number, number of guests, etc.', appearing when the guest selects a handoff mode, with an operator-chosen label (max 128 characters) and required flag. Shortfall: fields are provisioned by Olo Support from a request, not defined self-serve, and there is no vendor-hosted scripting or custom logic against platform objects. https://olosupport.zendesk.com/hc/en-us/articles/360050334652-How-to-Enable-Dine-In · retrieved 2026-09-03 adversarially verified

extensibility-headless-embedded

Cited to olo.com/serve, which does not mention headless use, API-driven front-ends, or Serve being optional. It markets Serve as 'Your digital no-cost front-end' with '$0 setup'. Supporting evidence exists elsewhere (Ordering API exists; API Usage Terms contemplate per-platform credentials for 'iOS, Android, Web, Kiosk'), but production credentials require per-API certification, so a brand cannot build headless against Olo without a signed, certified relationship. Partner-gated headless, not open headless. https://www.olo.com/serve · retrieved 2026-08-01 adversarially verified

extensibility-api-versioning-deprecation

No public changelog or deprecation policy; the docs portal is login-gated.

extensibility-data-portability-exit differentiator

Data-ownership marketing exists but no documented machine-readable full export at contract end.

reliability-offline-order-entry

Olo is a cloud platform with no on-premise terminal. Its Summer 2026 'POS offline fallback mode' keeps Olo accepting digital orders when the POS backend is unreachable — the opposite direction from terminal-side offline. https://www.olo.com/product-release · retrieved 2026-08-01

reliability-offline-card-auth differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

reliability-offline-decline-liability differentiator

Olo Pay card-present advertises store-and-forward - the Spring 2025 release's exact words are 'Offline capabilities (store and forward) ensure your restaurant won't lose out if connection is lost' - so the liability question is live, and the public Olo Pay Terms & Conditions are where Olo allocates transaction risk: unauthorized, irregular or fraudulent charges 'shall remain the full responsibility of Merchant', chargebacks and settlement suspension are specified, yet no offline, store-and-forward or deferred-authorization clause appears and no per-transaction or cumulative offline cap is stated anywhere public. The vendor does not publicly document who bears a post-reconnect decline. (Mirrors the settled payments-offline-decline-liability cell in this record.) https://www.olo.com/olo-pay-terms-and-conditions · retrieved 2026-08-04

reliability-lan-degraded-multi-terminal differentiator

No terminals and no LAN component.

reliability-local-transaction-engine differentiator

Olo documents no edge server or on-premise engine; the ordering path is entirely cloud request/response, which is why 'POS offline fallback' had to be built as a cloud-side queue. https://www.olo.com/product-release · retrieved 2026-08-01

reliability-offline-kds-printing

Migrated from the 2026-08-01 research pass; no source URL was recorded.

reliability-printer-fallback

Olo's only native printing surface is the Expo tablet, and it is a single-printer, largely manual affair: iOS requires an AirPrint or CloudPRNT printer ('A CloudPRNT compatible printer is required for Auto-Printing'), Android prints through a third-party ESC/POS print-service plugin configured as the OS default printer, with the operator opening the order PDF and printing from the viewer. The Expo FAQ states 'Auto printing from Expo is not currently supported, but action-based printing and bulk printing is available', and the Expo Mode Comparison Chart's Printing section enumerates the entire printing feature set as chit layout, letter layout and group/batch printing. No backup-printer designation, no failover on an unreachable printer, no print-failure alert exists; for POS-integrated brands kitchen-ticket printing is performed by the POS, outside Olo. https://olosupport.zendesk.com/hc/en-us/articles/360029271212-Expo-Device-Browser-and-Software-Requirements · retrieved 2026-08-04

reliability-sync-conflict-handling

Searched the public help centre (olosupport.zendesk.com search API, 2026-08-04): 'conflict' returns one irrelevant hit (Delivery Guidelines), 'sync' returns only the Olo Sync local-listings product, and 'offline' returns six articles none of which cover multi-device edit reconciliation. Olo's device surfaces are online-only thin clients - Expo requires safelisted access to api.olo.com and the FAQ says the app must be open and on-screen to stay up to date - so partition-time edits may simply be impossible, but no public page states the conflict or reconnect behavior for the documented multiple-devices-per-location setup, and the technical docs at developer.olo.com sit behind login. No published conflict-resolution policy found; cannot verify absence across the gated docs.

reliability-offline-feature-matrix

Olo documents one specific degraded-mode behavior (POS offline fallback mode, Summer 2026) but publishes no comprehensive matrix of what is unavailable during an outage. https://www.olo.com/product-release · retrieved 2026-08-01

reliability-public-status-page

Verified independently: status.olo.com is fully public with no login, ~40 monitored components including Ordering API, Dispatch API, Point of Sale API and Webhooks, with subscription options. No uptime percentages published, as stated. Note the researcher missed that olo.com/ordering separately advertises '99.99% uptime' — a marketing figure, not a contractual SLA, so reliability-contractual-uptime-sla correctly stays unknown. https://status.olo.com/ · retrieved 2026-08-01 adversarially verified

reliability-contractual-uptime-sla differentiator

Olo's published Security Policy (an exhibit to the MSA, last updated 2020-09-08) states that a security-driven suspension 'shall not be considered Downtime as defined under the Digital Ordering Terms & Conditions Addendum, if applicable to Customer's use of the Services'. So a contractual Downtime definition exists in an addendum. Shortfall: the addendum is not published, so neither the uptime percentage nor any service-credit remedy can be read. https://www.olo.com/security-policy · retrieved 2026-09-03 adversarially verified

reliability-incident-postmortems

status.olo.com publishes a full incident history (Atlassian Statuspage; the Atom feed read 2026-09-03 carries 25 incidents such as 'Ordering Disruption', 'Menu Eighty Sixing Processing Delays', 'Some reporting data is delayed'). Each entry is a timeline of Investigating / Identified / Monitoring / Resolved updates with one-line causes ('Our image provider has notified us that they are aware of the issue'). Shortfall: no entry carries a written postmortem or root-cause report; the feed contains no 'postmortem' or 'root cause' text at all. https://status.olo.com/history.atom · retrieved 2026-09-03 adversarially verified

reliability-247-live-support

Olo runs a Zendesk support portal (olosupport.zendesk.com) with a ticket-submission path; the portal returned 403 to automated fetch and 24/7 phone support is not publicly stated.

reliability-onsite-install differentiator

Olo is software-only and enterprise-implemented; on-site go-live support is not documented either way.

reliability-menu-build-service differentiator

Checked 2026-08-04: the four-part Menu Training series (Introduction, Company Menu Admin, Menu Mapping, Store Menu Admin) trains brand staff to build the company menu, perform POS mapping and manage store menus themselves - consistent with operator-led menu work after go-live - but Olo publishes nothing about its onboarding/implementation services, so whether Olo's deployment team performs the initial menu build for new brands (plausible for a sales-led enterprise product) cannot be determined publicly.

reliability-hardware-replacement-sla

Checked 2026-08-04: Olo fields real payment hardware - 'modern, reliable payment terminals' (Spring 2025 release) whose fleet status the Dashboard's terminal-management portal now monitors (Summer 2026) - while Expo runs in a browser on operator-chosen tablets (requirements article lists 'Suggested Devices (not mandatory)'). No public page says who supplies the terminals or documents any replacement/advance-exchange program or turnaround time, and Olo Pay merchant onboarding docs are gated, so the claim is unresolved.

reliability-backup-restore

No RPO/RTO figures published.

reliability-pci-dss-4-attestation

Olo's Data Protection Addendum requires compliance with 'PCI-DSS version 4.0 and any subsequent versions' for Card Present Services and obliges customer subcontractors to the same standard. No AoC or P2PE listing is published or offered on request in public materials. https://www.olo.com/data-protection-addendum · retrieved 2026-08-01

reliability-mfa-role-based-access

Summer 2026 shipped SMS 2FA for Dashboard login; Fall 2025 shipped 'enhanced dashboard security.' SMS is the weakest MFA factor and no role-based permission model is documented publicly. https://www.olo.com/product-release · retrieved 2026-08-01

reliability-self-serve-training

A public training library exists: the four-part Menu Training Series (Introduction, Company Menu Admin, Menu Mapping, Store Menu Admin) with stated learning objectives, the 'Expo User Guide (Videos)' (360042794592) and the Loyalty Insights and Campaign guides are all readable without login. Shortfalls: 'For security purposes, you will need to log in to Dashboard to access most Olo Help Center content' (4422086507035), and there is no terminal practice/training mode because Olo ships no terminal software beyond the browser-based Expo. https://olosupport.zendesk.com/hc/en-us/articles/360026284851-Menu-Training-Introduction · retrieved 2026-09-03 adversarially verified

reliability-failover-terminal-role differentiator

No terminals.

reliability-cellular-backup

Migrated from the 2026-08-01 research pass; no source URL was recorded.

commercial-month-to-month-contract differentiator

No public MSA and no published pricing. Enterprise-negotiated.

commercial-no-early-termination-fee differentiator

Checked 2026-08-04: no public MSA exists (olo.com/terms-of-use is consumer website terms, last updated 2020-04-27). The public Olo Pay Terms & Conditions contain termination mechanics - including a merchant right to exit after a materially adverse change on notice - but state no early-termination fee either way, and the commercial terms (term length, fees, any liquidated damages) live in the unpublished Merchant Agreement and SaaS order forms. Silence is not a published 'no ETF', so unresolved.

commercial-autorenew-terms-published

olo.com/terms-of-use is consumer/website terms last updated April 27, 2020 and explicitly not a service agreement; no auto-renewal term or cancellation notice window is published anywhere. https://www.olo.com/terms-of-use · retrieved 2026-08-01

commercial-processing-not-bundled differentiator

Olo Help Center, Order with Google Onboarding: 'All of the Olo-supported credit card processors can be used except for the deprecated Worldpay platform,' and payments run on 'the merchant account ID (MID) set up in the store' with 'the brand is the merchant of record.' Olo therefore supports a plurality of third-party processors on the brand's own MID. Corroborated by the FY2024 10-K: Olo Pay is a separately-sold module ('Olo Pay is currently available to brands and locations utilizing Olo's Ordering module' - Pay is optional on Order, not the reverse) and GPV of ~$2.8B against GMV of ~$29B means roughly 90% of platform order volume settled on processing Olo did not provide. https://olosupport.zendesk.com/hc/en-us/articles/360050177472-Order-with-Google-Onboarding · retrieved 2026-08-02 adversarially verified

commercial-interchange-plus-published differentiator

No rate is published. Spring 2026 added an IC+ interchange and network fee breakdown report, indicating an interchange-plus model exists commercially — but the bps + per-transaction markup is not disclosed. https://www.olo.com/2026-spring-release · retrieved 2026-08-01

commercial-rate-increase-clause differentiator

The public Olo Pay T&C give change-with-exit protection: 'Payment Facilitator may revise these Terms and Conditions from time to time on 30 days written notice to the Merchant', and 'If the change has a material adverse impact on Merchant and Merchant does not agree to the change, Merchant may terminate the Merchant Agreement by giving at least one month written notice' (that notice due within 30 days of the change notice) - a penalty-free exit on adverse changes, with shorter notice only for changes imposed by law or the schemes. Shortfall: the exit right triggers only on 'material adverse impact', not on any increase, and the actual processing rates sit in the unpublished Merchant Agreement, so no published cap on vendor-initiated rate increases can be verified. https://www.olo.com/olo-pay-terms-and-conditions · retrieved 2026-08-04

commercial-pricing-published

olo.com has no pricing page. Every product page terminates in Request a Demo. No per-location or per-terminal figure exists publicly. https://www.olo.com/ · retrieved 2026-08-01

commercial-module-unbundling differentiator

Olo sells 16 discretely named SKUs (Ordering, Serve, Dispatch, Rails, Catering+, Loyalty, Order with Google, Switchboard, Olo Network, Pay, Host, Sync, Marketing, GDP, Sentiment, Accounts) that are clearly separately purchasable, but independent cancellation without repricing is not documented. https://www.olo.com/ · retrieved 2026-08-01

commercial-hardware-purchase-outright

No published hardware terms for Olo Pay terminals.

commercial-hardware-not-locked differentiator

Host runs on a standard iPad and Serve is browser-based, so most of Olo requires no vendor hardware at all. Olo Pay Card-Present terminal openness is undocumented. https://www.olo.com/host · retrieved 2026-08-01

commercial-implementation-fee-published

No implementation, menu-build, onboarding or training fee is published, nor stated as $0. https://www.olo.com/ · retrieved 2026-08-01

commercial-data-export-self-serve

Self-serve exports exist per report: Dashboard Reports are built from 'the Report Category, Report Date Range, and Store Locations' with transaction-level types (Itemized Orders, Closed Orders by Store, Product Breakdown) exported to xlsx/csv, and the Loyalty Dashboard 'Export Data' section (46322256871579) offers eleven CSV exports (Store Performance, Offer Events, Loyalty Liability, Fraud Detection...). Shortfall: exports are report-by-report over a chosen date range, no single full-history export or documented bulk API is public, and payment-level detail is not among the listed report types. https://olosupport.zendesk.com/hc/en-us/articles/115000124306-Sales-and-Orders-Reports-Overview · retrieved 2026-09-03 adversarially verified

commercial-export-customer-and-loyalty differentiator

Olo markets restaurant ownership of first-party guest data and GDP 'without vendor lock-in,' but publishes no export format, mechanism, or fee position for guest records and loyalty ledgers. https://www.olo.com/gdp · retrieved 2026-08-01

commercial-post-termination-export-window differentiator

No public MSA.

commercial-data-ownership-clause differentiator

Marketing asserts full guest data ownership, but the only published contractual document — the Data Protection Addendum — states 'Customer is a Controller and Olo is a Controller,' i.e. Olo claims joint controllership of guest data rather than processor status. No published clause constrains Olo's own use of that data. https://www.olo.com/data-protection-addendum · retrieved 2026-08-01

commercial-source-available-selfhost

Verified verbatim in the API Usage Terms: licensees may not 'substantially replicate products or services offered by Olo' or 'use the Olo API specifications in a product or service that competes with products or services offered by Olo.' Proprietary SaaS, affirmatively documented. https://www.olo.com/api-usage-terms · retrieved 2026-08-01 adversarially verified

commercial-pci-p2pe-tokenization

Olo Pay claims point-to-point encryption and Olo Accounts implies tokenized card-on-file, but no SAQ type (A / P2PE-HW) is named and no validated P2PE listing is cited. https://www.olo.com/pay · retrieved 2026-08-01

commercial-pci-dss-4-controls

The DPA mandates PCI DSS v4.0, and Summer 2026 shipped SMS 2FA on Dashboard login (partially addressing the MFA requirement). Payment-page script-integrity monitoring per Req 6.4.3/11.6.1 is not documented despite Olo hosting the checkout page. https://www.olo.com/data-protection-addendum · retrieved 2026-08-01

commercial-soc2-attestation

trust.olo.com (SafeBase, read 2026-09-03) lists 'SOC 2 Type 2' and 'SOC 1 Type 2' reports and a 'PCI DSS v4.0.1' AoC under Compliance, with the report downloads behind an access request. The help-centre article 'Olo PCI Compliance Overview' (360043119711) sends customers to trust.olo.com for the AoC, the PCI responsibility matrix and the ASV scan attestations, and states Olo is a Level 1 PCI-DSS service provider on Visa's listing. https://trust.olo.com/ · retrieved 2026-09-03 adversarially verified

commercial-privacy-dsar-tooling

Olo publishes an executable Data Protection Addendum and a CCPA notice of right to opt out of sale/sharing. In-app tooling for the operator to locate, export and delete an individual guest's records is not documented, and the DPA specifies no DSAR procedure. https://www.olo.com/data-protection-addendum · retrieved 2026-08-01

commercial-wcag-kiosk-accessibility differentiator

Olo's accessibility statement references WCAG 2.1 but names no conformance level (A/AA/AAA), publishes no VPAT or ACR, identifies no specific surfaces, and directs enquiries to esg-team@olo.com. There is also no kiosk product. https://www.olo.com/accessibility-statement · retrieved 2026-08-01

commercial-dual-pricing-compliant differentiator

Olo supports configurable service fees (tiered %/flat) with guest-facing fee/tax line-item disclosure, but card-network-compliant surcharging with debit/prepaid exclusion is not documented.