Oracle MICROS Simphony

order-capture-floor-plan-editor

Dining Room Management documents section layout create/edit/activate/close, dining table status, employee lines, server availability and Table Management System gestures — a first-class floor-plan editor, not a static image. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/c_tms.htm · retrieved 2026-08-02

order-capture-seat-level

Documented seat operations: "Filtering a Check by Seat Number", "Removing a Seat from the Filter", "Changing the Seat Number of Menu Items on a Check" and "Printing a Memo Check" per seat. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/c_check_filter_and_memo_check.htm · retrieved 2026-08-02

order-capture-coursing-hold-fire

POS User Guide documents "Firing Menu Items on a Check", "Sending Items to Order Devices While Remaining on the Check", "Re-firing Items to the Order Device", "Holding Menu Items on a Check" and "Holding Selected Items or an Entire Order for a Preset Time"; the KDS guide adds a Dining Courses chapter with course pacing and one-course-at-a-time displays. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

order-capture-split-merge

Documented: "Splitting Off Items", "Splitting Off Items from a Suites Check", "Combining Checks in the Same Revenue Center into One Order", "Combining Checks Across Revenue Centers into One Order" and "Dividing a Check Into Equal Partial Payments". https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

order-capture-bar-tab-preauth differentiator

The Simphony Bar Tab plug-in (19.8.2) is described as "Opens tabs with initial credit card authorization; enables seamless payment settlement." Incremental re-authorisation, a configurable pre-auth amount and stale-tab auto-close are not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-08-02

order-capture-transfer-audit

Check Add/Transfer: "Transferring checks is a procedure that changes ownership of a guest check. Simphony allows privileged workstation operators to transfer checks from another server to themselves by employee number or by employee ID number. Guest checks may also be transferred across revenue centers." The POS User Guide adds transfer by check number, by table number, Auto Block Check Transfer (all of another operator's checks at once) and Team Check Transfers, and the Closed Check Report status-indicator table carries codes X "Transferred from check" and x "Transferred to check". Shortfall: no Oracle page states that the resulting record names BOTH the releasing and the receiving employee. The Audit Trail module has a single Emp # / Emp Name pair and its Application list is EMC, PMC Procedures and PMC Reports - configuration and manager-procedure changes, not transaction-level check transfers - and the Reporting and Analytics Check Journal drill-down exposes only generic "Journal Type" and "Journal Entry Information" columns. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_checks_add_transfer.htm · retrieved 2026-08-08

order-capture-native-handheld

MICROS Tablet 700 series (720/721/721P/722P) technical specifications: purpose-built 7-inch tablets running the Simphony client with integrated magnetic stripe reader, replaceable Li-ion battery and a backup bridge cell. https://docs.oracle.com/en/industries/food-beverage/micros-tablet-700-series/latest/tabss/c_tablet_technical_specifications.htm · retrieved 2026-08-02

order-capture-offline-order-entry

Yellow and red offline modes with a local DataStore and automatic replay on reconnect are documented, but Oracle publishes no complete list of which POS functions do and do not work while offline. https://docs.oracle.com/en/industries/food-beverage/simphony/19.4/sipou/c_workstation_online_offline_modes.htm · retrieved 2026-08-02

order-capture-qr-same-check differentiator

Enumerated the complete flat manifests of the Configuration Guide (docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm, 845 topics) and the POS User Guide (simphony/sipou/toc.htm, 198 topics) and grepped the full text of all 1,193 retrieved topics for QR and scan. Every hit is a payment or hardware flow: sipou c_payment_qr_code.htm (Pay Using QR Code), t_payment_consumer_self_pay.htm and t_paying_check_opera_self_pay_close_check.htm (guest settles an existing check in a mobile browser), and kdscu c_kds_bump_bar_templates_scancodes.htm (bump-bar scancodes). The Kiosks chapter (simcg c_kiosk.htm, t_kiosk_client_add.htm) describes an on-premise Simphony workstation client running in kiosk mode with an optional Generic Barcode Reader peripheral, not a guest-phone ordering surface. Nothing in either book describes a guest scanning a table QR to add items to a server's open check.

order-capture-kiosk-first-party differentiator

A first-party Simphony Kiosk plug-in (19.8.3.4) ships — "Guest-facing self-service kiosk for Simphony POS with Gift and Loyalty Helper and Givex Helper" — and the configuration guide carries a dedicated Kiosks chapter. No ADA/WCAG conformance statement or unattended-EMV specification was found. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-08-02

order-capture-drive-thru

Order Channels documentation names "Drive thru window" as an order channel, assignable to revenue centers, workstations and order types with a documented precedence order, and reportable. Tandem-lane assignment, pull-forward/park and vehicle detection are not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_order_channels.htm · retrieved 2026-08-02

order-capture-drive-thru-timers

The Reporting and Analytics Speed of Service (Quick Service Restaurant) report enumerates its complete metric set: Net Sales, Check Count, Average Speed of Service ("sum of expediter station times / sum of service rounds"), Average Prep Time ("sum of prep station prep times / count of prep station sessions") and Parked Cars Count, plus a previous-14-days bar chart of the same two averages, broken out by location and revenue center. KDS Menu Item Timing times items and orders at prep stations. Shortfall: the timing is kitchen-station based and reported as location/revenue-center averages - there is no menu-board / order / pay / present segmentation and no per-order drive-thru timer record. Simphony's only drive-thru-specific device support is the Texas Digital Order Confirmation Board, which is an order display, not a timer. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/c_speed_of_service_qsr_add.htm · retrieved 2026-08-08

order-capture-voice-ai differentiator

No first-party voice agent is documented anywhere in the Transaction Services Gen2 guide, and Oracle publishes no voice-AI partner programme for Simphony. What it does publish is the order-injection surface third-party voice vendors integrate against: the STS Gen2 Checks API "is used to create and manage the checks within a revenue center", with an explicit "Post a new check" POST /api/v1/checks plus "Post a new round to a check" and "Post calculate totals for a check". Shortfall: that surface is a separately licensed SKU at every tier - the Simphony Cloud licence manual lists Premium Transaction Services, Premium Transaction Services - Revenue Center, Standard Transaction Services - Transaction Services Client, Standard - Revenue Center and both Guest Facing variants, each naming Premium or Standard Cloud Service as a prerequisite - so voice AI is a paid-integration path rather than a shipped capability. (Citation re-pointed 2026-08-09: the previously cited .../simphony/omsstsg2api/ now redirects to .../simphony/stsgg/, the same guide under a new slug.) https://docs.oracle.com/en/industries/food-beverage/simphony/stsgg/api-checks-api.html · retrieved 2026-08-09 adversarially verified

order-capture-throttling differentiator

Grepped the full text of all 1,193 topics in simcg, sipou, kdscu and simgi for throttl, capacity, pacing and quote time. The three near-misses: kdscu KDS Capacity Scheduling (relative capacity per order device, per menu item, per component and per kitchen theme - it paces items onto prep stations and has no channel or time-slot dimension); simcg RVC Parameters Autofire, which has a Maximum Days scheduling horizon and an Order Type Parameters Service Level Time that fires an order a fixed number of minutes before the guest or driver arrives (simgi t_emc_fulfillment_time.htm); and Table Management wait quotes (t_waitlist_parameters.htm - Wait Quote Interval, Wait Quote Alert Threshold), which quote table waits rather than order fulfilment. No per-channel capacity ceiling per time slot and no automatic quote-time extension under kitchen load appears in any of the four books.

order-capture-scheduled-orders

Autofire lets servers "add items to a guest check and hold the order" until a pre-set fire time, at which point Simphony sends the order to remote order devices automatically without a server pressing a fire key; menu items post when the check fires and remaining totals post at tender. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_checks_autofire.htm · retrieved 2026-08-02

order-capture-catering

Rental Deposits: "Rental deposits are used in Simphony to record advance payments on scheduled events, such as banquets, parties, room rentals ... The Rental Deposits feature allows workstation operators to accept, apply, record, report, and refund rental deposits taken at the workstation", and "a check can contain more than one rental deposit"; the POS guide adds Apply / Modify / Remove / View and Search / Refund a Deposit. Banquet Guest Check Printing prints an 8.5x11 banquet check carrying event name, address, contact information, room, maitre d' and catering sales manager. The Events module groups transactions into a dated event across revenue centers, and the menu item definition Guest Count field's own example is "2 Catering Appetizer Platters, each representing 10 guests". Shortfall: there is no catering quote or proposal document, no per-account balance-due ledger, and no event or delivery schedule board separate from the standard open-check queue - forward-dated orders are handled only by Autofire's Maximum Days horizon. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_deposits.htm · retrieved 2026-08-08

order-capture-order-ready-signal differentiator

Read the entire Delivery Connectors chapter as enumerated in simcg/toc.htm: c_delivery_connectors.htm (Deliveroo, DoorDash, Rappi, Skip The Dishes, Uber Eats/Postmates), c_dc_config_checklist.htm, c_dc_info_required.htm (a per-provider Required / Optional / Not Supported matrix of what Simphony pushes) and the full Add Delivery Connector wizard for DoorDash and Uber Eats, whose field list is exhaustive - Order Type, Tender Name, Employee, Parent and Condiment Price Sequence Levels, Image Slot Number, SLU Slot, Combo Sizes, Default Condiments, Exclude, menus, time slots and special hours. No order-status or order-ready callback field appears anywhere in it. The one suggestive row, "KDS Notification" (Optional for DoorDash and Uber Eats, Not Supported for Deliveroo, Rappi and Skip), is listed in c_dc_doordash.htm only among menu-item display considerations and is never defined; Oracle publishes no page saying what it sends. Unresolved rather than absent because that matrix is a configuration checklist, not an enumeration of runtime events - the item-availability push, for instance, is documented outside it.

order-capture-void-comp-controls

Void and comp control is evidenced by its reporting surface: Voided Menu Items, Employee Exceptions, Employee Threshold Exceptions, Adjustments-Voids, Adjustments-Returns, Adjustments-Error Corrects, All Checks with Manager Voids and Check Journal are all published standard reports, and the POS guide documents Voiding a Closed Check and Applying a Return. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

menu-pricing-nested-modifiers

Condiment groups, condiment sets, and Forced condiments with configurable minimum and maximum selection counts are documented, and a condiment may belong to multiple groups. Nesting to three or more independent levels is not documented in the condiments chapter. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_condiments.htm · retrieved 2026-08-02

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

A single condiment carries several price records and the PARENT's menu item class chooses which one applies, so no duplication is needed. Menu Item Classes > Forced Condiments tab: "Specify the number of condiments from the required group that can be selected in the Threshold [1-8] fields before the Threshold [1-8] Level is used. When the Threshold [1-8] quantity is reached, the price sequence associated with the Threshold [1-8] Level is applied to the transaction." Condiment Prefixes add a Prefix Level Override on the menu item definition that selects the price level used for No/Plain deductions, and condiment price records carry a Condiment Parent Tax Class Override with a 1-99 priority. Shortfall: the selector is one-dimensional. A condiment price record has a single "Active on Level" field, and Menu Item Class option 10 forces a class to use EITHER sub-level or main-level pricing, so parent identity and selected size compete for the same axis - there is no parent x size matrix editor. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_condiments_assign_condiments_to_parent_classes.htm · retrieved 2026-08-08

menu-pricing-fractional-placement differentiator

The Condiments chapter enumerates the complete set of condiment prefix types — Description, No, Add, Sub, Plain, Reset and Clear — and none expresses left/right/half or quarter placement. No per-section price multiplier field exists anywhere in the chapter. Oracle's own answer to half-and-half pizza is a Combo Meal pricing rule, not topping placement, which is the vendor recommending a workaround rather than shipping the capability. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_condiments.htm · retrieved 2026-08-02 adversarially verified

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

Simphony 19.9, verbatim: "Use Most or Least Expensive Combo Group Item as Combo Meal Price. A Combo Meal price may now be determined by the most or least expensive Combo Group item, supporting 'half and half' menu items like pizza." Shortfall: of the three rules the claim looks for, Simphony supplies only charge-the-higher-half (the least-expensive rule is the commercial opposite, not a second qualifying rule); there is no average-the-halves and no fraction-of-full-price-per-topping option, and it is a combo-group construct rather than a topping-section pricing engine. https://docs.oracle.com/en/industries/food-beverage/simphony/simrn/simphony_19_9.htm · retrieved 2026-08-02 adversarially verified

menu-pricing-topping-quantity-tiers

Documented quantity handling: prefix types "Lite"/"Extra", an Add prefix that increases quantity on defaults ("2 tomato"), configurable default counts, Threshold [1-8] limits on condiment quantities or group members, and increment/decrement plus Update Selected Item Count functions. A per-tier price multiplier is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_condiments.htm · retrieved 2026-08-02

menu-pricing-size-style-matrix differentiator

Both axes exist, but not as a grid. A menu item master holds multiple definitions, each with its own Menu Level Availability (active main levels, sub levels and custom Menu Level Set levels), and each definition holds multiple price records; the price record field table lists Price, Prep Cost, Tax Class Override, Service Charge Group, "Active on Level - select the main or sub menu level in which this price becomes active", Restricted to Order Types, Options and Effectivity Group. Menu Level Sets can be custom and multiple - the Conversational Ordering example builds separate Size and Temperature sets. Shortfall: a price record binds to exactly one level, and Menu Item Class option 10 makes a class use sub-level pricing OR main-level pricing rather than a (main, sub) pair; the second variant axis has to be modelled as separate menu item definitions and every cell entered as its own price sequence record. There is no per-cell grid editor and no two-axis price lookup. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_menu_items_configure_prices.htm · retrieved 2026-08-08

menu-pricing-included-allowance differentiator

Menu Item Classes > Forced Condiments implements exactly this. For each required condiment group you set a Minimum and Maximum condiment count, then "specify the number of condiments from the required group that can be selected in the Threshold [1-8] fields before the Threshold [1-8] Level is used. When the Threshold [1-8] quantity is reached, the price sequence associated with the Threshold [1-8] Level is applied to the transaction. For example, if you enter 2 and 3 in the Threshold 1 and 2 Levels, Menu Item price sequences 2 and 3 are used for condiment pricing when the Threshold 1 and Threshold 2 quantities are exceeded" - the first N are priced at one sequence and the overage at another, across up to eight bands. Substitution credit is the No/Plain enhanced prefix: removing default condiments applies a negative price, worked through as a Burger with 3 default Tomato priced 0.05 showing -0.05 / -0.10 / -0.15 as they are removed, with a guardrail that blocks any deduction taking the item's net value below zero. Forbidding is the Maximum count plus option 86 - Reset Required Condiments when Maximum count is exceeded. Requires menu item class option 65 - Support Enhanced Prefix Mode (Parent Only). https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_condiments_assign_condiments_to_parent_classes.htm · retrieved 2026-08-08

menu-pricing-combos

Combo Meals and Groups are a documented POS construct with "Creating Combo Meals", the Uber Eats connector exposes up to four configurable Combo Sizes, and Reporting ships a Combo Items Summary report. Automatic conversion of matching a-la-carte items into a combo is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

menu-pricing-upsell-prompts differentiator

Grepped the full text of all 1,193 topics in simcg, sipou, kdscu and simgi for upsell, suggestive, cross-sell and recommend: zero hits in any sense other than "Oracle recommends" configuration advice. The plug-in catalogue at docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html still offers only End of Transaction Prompt (table number / guest check name) and Condiment Carousel. Order Channels do exist as a first-class construct - c_order_channels.htm, "guests can place an order at a kiosk, a drive thru window, inside a restaurant, or via a delivery aggregator", with per-channel headers, trailers, privileges and reporting - so the per-channel half of the claim has a hook, but no prompt engine hangs off it and the Reporting and Analytics report catalogue publishes no attach-rate metric. Not marked absent: Simphony's plug-in and extensibility surface is open-ended, and Oracle Digital Ordering is a separate product with its own upselling documentation that is out of scope for this record.

menu-pricing-86-propagation

The Menu Item Availability plug-in (19.8.1) "Toggles menu item availability from workstation without EMC access or restart", so a server can 86 an item enterprise-wide from the terminal. Propagation to delivery marketplaces is not among any documented connector operation, and no latency figure is published. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-08-02

menu-pricing-countdown-auto-86 differentiator

Read c_menu_item_master_availability_methods.htm, which enumerates Simphony's availability mechanisms: Menu Item Master Core, Disable, Menu Item Master Effectivity Group (start and end dates, overridable down the hierarchy) and Menu Item Price Effectivity Group. All four are on/off or date-window controls; none decrements on sale. The workstation side is the Menu Item Availability function key with its own privilege and RVC Parameters option 66. That option's wording - "66 - Manage Menu Item Availability/Out of Item for each Menu Item Definition" - is the one unresolved thread: Oracle names an "Out of Item" concept but publishes no topic describing whether it holds a remaining quantity, decrements on sale or auto-restores, and the POS User Guide (198 topics, manifest enumerated) contains no menu item availability task at all.

menu-pricing-dayparting

The configuration guide carries dedicated chapters for Serving Periods (33), Menu Levels (18) and Effectivity Groups (19), and delivery connector menus are configured with service-period start/end times and days of week. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

menu-pricing-channel-price-books

Order channels are assignable at revenue center, workstation and order type with a documented precedence order, and connector menus carry their own Parent and Condiment Price Sequence Levels — so per-channel pricing is achievable. A price-book construct applying a percentage markup over a base price is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_order_channels.htm · retrieved 2026-08-02

menu-pricing-dual-pricing differentiator

The Credit Card Surcharge plug-in (19.4.1) "Manages credit card surcharges for non-SPI integrated payments" — so it does not cover Oracle's own semi-integrated payment path, and it is a surcharge rather than a two-price-per-item cash/card model printed on the menu and check. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-08-02

menu-pricing-versioning-effective-dates differentiator

Effectivity Groups are a first-class configuration chapter, and the Vendor Purchase Catalog documents effectivity ranges, so date-scoped menu and price records exist. Staged preview of a pending version and post-publish rollback are not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

menu-pricing-franchise-hierarchy differentiator

Central authoring plus field-level governance are both documented. Configuration is authored at Enterprise, property, revenue center or zone and inherits downward (simcg chapter 4 Hierarchy, with an "Inheritance and Overrides" topic), and Menu Item Field Security gives every field in MI Master, MI Definition, MI Prices, Event Definitions and Effectivity Groups a per-role privilege of 0 Editable, 1 View Only or 2 Exclude — so corporate can pin the fields a location may not change. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_employee_roles_field_level_access.htm · retrieved 2026-08-02 adversarially verified

menu-pricing-allergen-nutrition

Inventory Management master data ships Additive Groups and Additive Management (create allergens, assign to items, copy assignments), Nutrient Groups and a licensable Nutrient Catalog with standard and custom imports; the POS side ships an Allergen and Nutrition Information Display plug-in (19.4.2.1). https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

menu-pricing-recipe-linkage differentiator

Menu Item Linking links POS menu items to recipes, other items and order types, including negative quantities; recipes carry ingredients, scaling and Weighed Stock Depletion, and Booking Sales posts POS sales against those links. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

menu-pricing-3p-menu-push

The Uber Eats connector configuration documents the menu payload explicitly: Parent Price Sequence Levels, Condiment Price Sequence Levels, Image Slot Number, SLU Slot, up to four Combo Sizes, a Default Condiment Group Name and condiment-group exclusions, plus menu selection, display title and service-period hours. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_add_ubereats.htm · retrieved 2026-08-02

menu-pricing-dynamic-pricing

Auto Menu Levels drive price automatically by clock and calendar: each row takes a Start time, an End time, a Main Level, a Sub Level and options 1 - This Entry is Active plus 2-8 for each day of the week, and menu item price records become active on the level then in force (c_menu_items_pricing.htm walks the price-sequence resolution). Price records additionally carry "Restricted to Order Types ... by selecting one or more from the list (up to 32)" and an Effectivity Group for date-windowed prices, so price can also vary by order type/channel and by date. Shortfall: every price is an explicitly authored record, so there is no demand-driven or time-decay price computation and consequently no floor or ceiling guardrail - nothing in the Configuration Guide moves a price to a value the operator did not enumerate in advance. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_menu_items_configure_auto_menu_levels.htm · retrieved 2026-08-08

payments-processor-choice differentiator

Oracle Payment Interface is "a payment card-processing interface that integrates with the Oracle Hospitality Point-of-Sale (POS), OPERA, Suite 8 (PMS) and Retail (POS) systems", and Oracle publishes the validated partner list: ACI Worldwide, Adyen, Aurus, Citcon, Eigen, Fiserv, Fortis, Global Blue, Oracle Retail Payment Service, PayPal/Braintree, Planet Payment, Shift4 Payments, Software Express, Verifone FIPAY and Verifone PSDK. The merchant is not forced onto Oracle MICROS Payment Cloud Service. https://docs.oracle.com/en/industries/retail/retail-eftlink/23.0/reopg/overview.htm · retrieved 2026-08-02 adversarially verified

payments-published-rates differentiator

Oracle publishes a full configuration guide for Oracle MICROS Payment Cloud Service — roles, account holders, accounts, revenue-center-to-store-ID mapping, terminal activation — and states no percentage, per-transaction figure or rate card anywhere in it. The rate is quote-only. https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/config.html · retrieved 2026-08-02

payments-dual-pricing differentiator

Only a Credit Card Surcharge plug-in exists, and it is scoped to "non-SPI integrated payments". No two-price-per-item cash/card model printed on the guest check is documented. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-08-02

payments-surcharge-guardrails differentiator

Enabling Credit Card Surcharge or Charity Donations: you create an open service charge, point Tender Parameters > CC Surcharge Service Charge at it, and set Control Parameters option 76 - Enable a Surcharge to be added to a payment card tender by payment service provider. Control Parameters are settable at Enterprise, property or revenue center, so the per-location enable/disable half of the claim holds. Shortfall: the amount is not Simphony's - "You can configure the SPI to allow payment service providers to apply multiple service charges to a check before processing payment ... Because the Payment Service Provider (PSP) sets the donation and/or fee amount, the service charge must be configured as open", and "This feature requires PSP support". No BIN or product-code lookup, no debit/prepaid exclusion and no network percentage cap appears in the surcharge, SPI or payment driver topics; card-type eligibility and the cap sit with the PSP. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_payments_cc_surcharge_donations.htm · retrieved 2026-08-08

payments-emv-nfc

Adyen documents that its terminals implement Oracle Payment Interface 6.2 and support pay-at-counter and pay-at-table with Simphony — but it does not enumerate EMV, contactless or wallet acceptance, and Oracle publishes no supported-payment-method list at all. Card acceptance is real in the field; it is a property of the merchant's PSP terminal, not a documented Simphony capability. https://docs.adyen.com/plugins/oracle-simphony · retrieved 2026-08-02

payments-softpos-tap-to-pay differentiator

Full-text search of all 1,193 topics in the four Simphony books for tap to pay, tap-to-pay, contactless, softpos and NFC returns nothing. The architecture points the other way: c_properties_android_payments.htm states that Android clients support only the Oracle Payment Interface and the Simphony Payment Interface drivers, and topic_payment_driver_config.htm's Primary Host field is the address of an external PIN entry device - "in Terminal Mode this is http://PEDIPAddress:Port ... if the IP address for each PED is different (network/wireless PEDs in Terminal mode), create workstation devices to enter each POS client's PED's IP address individually". Left open rather than absent because acceptance on a phone would be a payments-platform capability, and the Oracle MICROS Payment Cloud Service configuration guide (docs.oracle.com/en/industries/food-beverage/payments-platform/latest/config.html) covers account holders, accounts and terminal activation without enumerating supported acceptance form factors.

payments-pay-at-table

Pay at Table exists but is gated twice over: it is delivered by the Guest Facing Transaction Services SKU, whose restricted-use licence inside Credit Card Interface Cloud Service (B81483) is "restricted to Pay at the Table services" — and B81483 is itself a separately licensed add-on requiring Premium or Standard Cloud Service. Card acceptance of any kind is a paid module on top of the POS subscription. Adyen independently documents pay-at-table on a portable device with bill display and splitting, which is what the SKU buys. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02

payments-qr-guest-pay differentiator

Documented flow: pressing Service Total prints a QR code on the guest check; "the guest scans the QR code on their check using their mobile device", a browser opens and loads the check, and on payment the check closes in Simphony showing the tender used. Consumer Self Pay additionally prompts the guest for a percentage, custom or no tip. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/c_payment_qr_code.htm · retrieved 2026-08-02 adversarially verified

payments-tip-adjust

Documented closed-check operations include "Adjusting a Closed Check" and "Adjusting a Credit Card Payment", plus Tip Track at start of shift and a Suggested Tip Trailer plug-in for printed tip lines. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

payments-tip-pooling differentiator

Tip pool profiles "collect a percentage of tips from tipped employees for distribution to non-tipped employees" and are assignable to one or many locations. Manual pools distribute by hours — "the system calculates the hourly tip rate based on the total hours worked for the job" — and automatic pools collect "based on percentage of tip and type of sales total", with documented examples of 5% of Net Sales, 3% of Revenue Center Net Sales and 8% of Beer, Wine, and Liquor Gross Sales. Selecting Paycheck includes the computed tips in the employee's pay. https://docs.oracle.com/cd/E80526_01/doc.91/e82051/c_config_pay_tippool.htm · retrieved 2026-08-02 adversarially verified

payments-offline-store-and-forward differentiator

Simphony's documented offline story is about checks, not authorizations: t_properties_offline.htm (Property Parameters option 6 - post offline transactions with the actual transaction time or the upload time), t_check_allow_check_replay.htm (PMC privilege 30001 to manually replay offline checks "if an offline workstation fails to automatically replay its checks before reconnecting online"), c_reset_totals_sod_offline.htm (Start of Day while a property is in Yellow Mode) and the closed-check status indicator O - Offline. The one card-side datum is in the SPI payment module field table (t_payment_module_add_spi.htm), where the driver property "Offline Authorizations" is listed as Numeric and marked "Not applicable to SPI", alongside Manual Card Data Entry Retries and Retry Authorization Reversals on Batch. So an offline-authorization count exists in the older OPI-era driver surface and is explicitly inert under the current SPI driver, and no per-transaction or cumulative floor limit is configurable anywhere in the Configuration Guide. Left unknown because Oracle never states what a workstation or PED does with a card tender while offline - that behaviour belongs to the PSP terminal.

payments-offline-decline-liability differentiator

Searched all 1,193 Simphony topics for chargeback, dispute, representment, liability and floor limit - zero hits for any of them. The reconnect path that is documented (t_check_allow_check_replay.htm, c_reset_totals_sod_offline.htm) covers replaying offline CHECKS into the database and says nothing about a card authorization that fails on replay, and the Reporting and Analytics report catalogue (back-office/20.1/rarrg/toc.htm, 222 topics, enumerated for this sweep) contains no post-reconnect failed-payment report. Also re-checked the Oracle Cloud Hosting and Delivery Policies PDF already cited in this record: it is a service-availability document and allocates no payment loss. Oracle positions itself as an interface to a PSP - c_payments_opi.htm, "PSPs process card data and provide a token to Simphony" - so liability allocation would sit in the PSP's merchant agreement, which Oracle does not publish.

payments-gift-cards

The POS guide documents a full stored-value lifecycle: gift card balance inquiry, issue, activate, reload, transfer balance, authorize, redeem, cash out, void, plus batch issue and batch activate. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

payments-house-accounts

Searched all 1,193 topics for house account, on account, credit limit and statement. The only account constructs are the loyalty and stored-value account number fields in t_loyalty_driver.htm and t_stored_value_driver.htm, the Enhanced Cash Management accounts in the ECM chapter (cash receptacles, count sheets, cash pull and cash count threshold sets - a till-management ledger, not a customer ledger), and PMS room charge to an OPERA folio (t_payments_opera_pms_driver.htm, sipou t_opera_connect_tender_room_charge.htm), which posts to a hotel guest's folio rather than a merchant-maintained house account. No customer account record with a credit limit, running balance or periodic statement/invoice run appears in the Configuration Guide, the POS User Guide or the enumerated Reporting and Analytics report catalogue. Left unknown rather than absent because accounts receivable is a back-office function and the separately licensed back-office suite was not enumerated exhaustively for this cell.

payments-split-tender

Documented: "Tendering with Multiple Credit Cards", "Dividing a Check Into Equal Partial Payments", cash plus card, and PATT with multiple credit cards. No documented cap on tenders per check was found. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

payments-refund-void-controls

Returns and voids are distinct documented constructs (the reports guide carries a "Voids vs. Returns" definition topic) with dedicated exception and drill-down reports including All Checks with Manager Voids, and the POS guide documents Voiding a Closed Check and Applying a Return. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

payments-chargeback-tooling differentiator

The words chargeback, dispute and representment do not occur once across the 1,193 topics of simcg, sipou, kdscu and simgi, and the Reporting and Analytics Reports Guide manifest (back-office/20.1/rarrg/toc.htm, 222 report topics, enumerated) lists no dispute or chargeback report - its payment-side reports are Income Audit by Tender, Adjustments - Voids, All Checks with Voids, All Checks with Manager Voids and the credit card batch reports. That is consistent with the architecture in c_payments_opi.htm, where Simphony never holds card data and settlement is automated out to the PSP, so evidence assembly would necessarily be a PSP-side portal. Not marked absent: that portal is outside Oracle's documentation scope, and the Oracle MICROS Payment Cloud Service configuration guide does not enumerate its merchant-portal features.

payments-card-on-file differentiator

Searched all 1,193 Simphony topics for card on file and token. The only tokenization statement is architectural - c_payments_opi.htm: "Enhances security by not handling or storing card holder or sensitive authentication data in Simphony or OPI. PSPs process card data and provide a token to Simphony." That establishes a PSP-issued token exists for a transaction; it does not establish a guest profile that stores one for reuse. Simphony has no customer or guest profile record in the Configuration Guide manifest at all - the nearest constructs are loyalty accounts through the iCare/Valutec drivers and OPERA guest lookup - so on the POS side there is nothing for a stored credential to attach to. Left unknown because credentials reusable across online ordering would be a Digital Ordering or Payment Cloud Service capability, and both are separate products with separate documentation.

payments-payout-timing differentiator

Re-read the Oracle MICROS Payment Cloud Service configuration guide (docs.oracle.com/en/industries/food-beverage/payments-platform/latest/config.html): it covers account holders, accounts, terminal creation and terminal activation, and contains no deposit schedule, funding cadence or instant-funding option. On the Simphony side the only settlement content is operational rather than financial - c_payments_opi.htm ("Eliminates credit card batch processing in Simphony by automating end-of-day settlement for credit card transactions through the OPI"), the Start of Day autosequence which "batches and settles credit cards" (c_reset_totals_sod.htm), and t_database_run_clear_totals.htm ("you must batch and settle all credit card transactions dated prior to the specified business date"). Simphony documents when it hands the batch to the PSP, never when the merchant is funded. The oracle.com marketing and pricing pages 403 to automated retrieval, as already recorded in this vendor's sources.jsonl, so no first-party funding page is readable.

payments-multi-entity-routing differentiator

Payment Driver records are hierarchy-scoped - topic_payment_driver_config.htm lists Merchant Number as a driver field and Inheritance Type as Inherited / Defined Here, Overriding / Defined Here, No Override, with the record definable at Enterprise, Zone, Property or Revenue Center. Configuring the OPI Driver states the pattern explicitly: "If the property sends transactions to multiple Merchant IDs, create the OPI driver record in the property with the Merchant ID that is used by a majority of the revenue centers, and then override the driver records of the revenue centers that route transactions to other Merchant IDs." So one Simphony enterprise routes card transactions to different MIDs per revenue center or property while Reporting and Analytics continues to report across the whole enterprise hierarchy. The bank account behind each MID is the PSP's record rather than Simphony's. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_payments_configure_opi_driver.htm · retrieved 2026-08-08

payments-p2pe-pci4

Oracle publishes a Simphony PA-DSS 3.2 implementation guide and per-module Security Guides. No current PCI DSS 4.x Attestation of Compliance and no PCI-listed validated P2PE solution for Simphony was found publicly, so the merchant cannot determine their resulting SAQ type from Oracle documentation. https://docs.oracle.com/cd/E76065_01/doc.29/e69884.pdf · retrieved 2026-08-02

kitchen-station-routing

KDS configuration documents Order Devices, Production Lanes and Workflow, KDS Load Balancing with Distribution Groups, Prep Station Linking, Menu Item Prioritization and even Order Device Routing By Guest Check Amount. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm · retrieved 2026-08-02

kitchen-expo-consolidation

Consolidation across stations is documented through Prep Station Linking, Production Lanes and Workflow, Split Order Screens (multiple panels on one display), and Order Chit Sort Priority; KDS Display Types is a dedicated configuration topic. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm · retrieved 2026-08-02

kitchen-course-firing differentiator

A whole chapter — KDS Configuration for Dining Courses — covers showing one course at a time, Dining Course Pacing, course-specific order chits, KDS course overrides and suppressing courses from orders. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm · retrieved 2026-08-02

kitchen-prep-time-pacing differentiator

Menu Item Timing by Order: the KDS Controller takes the longest item prep time as the order prep time, fires that item immediately, and computes each other item's fire time as order prep time minus item prep time. Oracle's worked example fires a hamburger at 0, fries at 6 and a soft drink at 9 minutes so all three finish at 10. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/c_kds_menu_item_timing_by_order.htm · retrieved 2026-08-02 adversarially verified

kitchen-order-throttling differentiator

KDS Capacity Scheduling holds work back: "If a prep station cannot handle the group's order simultaneously, the KDS breaks the order down into groups of items" and "items may have to wait to appear on the display if the capacity is currently unavailable", with relative capacity configurable per order device, per menu item, per component and per kitchen theme. The shortfall is the guest-facing half — nothing extends a quoted prep time or paces inbound digital orders once a ticket-time threshold is crossed. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/c_kds_capacity_scheduling.htm · retrieved 2026-08-02

kitchen-channel-pause-propagation differentiator

Item availability does propagate. Configure Menu Items for DoorDash ends with: "Change the availability status of a menu item to generate a notification through the delivery application, advising DoorDash of the menu item's new status (unavailable or available). These updates are immediately sent to DoorDash and will update in near real time", and t_dc_menu_items_ubereats.htm carries the identical sentence for Uber Eats. Availability is changed from the workstation via the Menu Item Availability function key or in EMC. Shortfall: only two of the five supported providers - the equivalent Configure Menu Items topics for Deliveroo, Rappi and Skip The Dishes have no availability-notification step; the propagation is menu-item level with no documented condiment or modifier equivalent; and store-level pausing is not a POS or KDS action at all - the only documented control is Deactivate Connection in the Delivery Connectors admin UI in Simphony Home. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_menu_items_doordash.htm · retrieved 2026-08-08

kitchen-order-ready-callback differentiator

Read the complete KDS Configuration and User Guide manifest (simphony/kdscu/toc.htm, 129 topics). The KDS Posting File Specification chapter is the only place KDS state leaves the system, and its Distribution State Record field definitions enumerate every state: DS_ORDERED, DS_STARTED, DS_PREP_DONE, DS_ALL_PREP_DONE, DS_READY ("order has been expo done and is ready to be distributed to the customer"), DS_DISPATCHED, DS_UNDISPATCHED, DS_DELIVERED, DS_COMPLETE and DS_CANCELLED - with the dispatch and delivery states footnoted "* = For future use; currently unavailable". The output is a posting FILE generated on the KDS controller (t_kds_generate_posting_files.htm), not a webhook to a marketplace, and nothing in the Delivery Connectors chapter consumes it. The undefined "KDS Notification" row in c_dc_info_required.htm (Optional for DoorDash and Uber Eats, Not Supported for the other three) is the only hint that KDS state might reach a provider, and Oracle publishes no page describing what it carries.

kitchen-bump-bar-hardware

Documented: Configuring the KDS Bump Bar, KDS Bump Bar Templates and Scancodes, and a KDS Bump Bar and Toolbar Functions reference. A named list of supported bump-bar models was not retrieved. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm · retrieved 2026-08-02

kitchen-all-day-counts

Production Items for KDS is a dedicated chapter — configuring production items for menu items, linking them to displays, configuring the behaviour of production counters, and pre-production items — and a Production Items Display plug-in (19.8.1) renders a "full-screen grid showing only production items for prep teams". https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm · retrieved 2026-08-02

kitchen-sla-alerts

KDS Highlight Schemes are configurable and assignable to order types and production items, alongside a configurable KDS Status Bar and Workstation Alerts for Unsuccessful Sending to Order Devices. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm · retrieved 2026-08-02

kitchen-printer-fallback differentiator

Documented: "Configuring a Backup KDS Controller" and a chapter on "Workstation Alerts for Unsuccessful Sending to Order Devices", so failure is detected and the controller tier is redundant. Automatic fallback of a failed KDS display to a backup printer is not documented as a configured behaviour. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm · retrieved 2026-08-02 adversarially verified

kitchen-offline-operation differentiator

The KDS Controller is an on-premise service with a documented backup controller, and yellow mode keeps workstations talking to local services over the LAN, so kitchen routing survives WAN loss. Oracle publishes no explicit statement of what the KDS can and cannot do while the enterprise is unreachable. https://docs.oracle.com/en/industries/food-beverage/simphony/19.4/sipou/c_workstation_online_offline_modes.htm · retrieved 2026-08-02

kitchen-item-build-screens differentiator

Two documented mechanisms come close: Menu Item Components (including Components with Condiments) break an item into assembly components on the display, and Media Viewer associates image and video files with menu items for display at the station. Recipe steps and portioning quantities on the station screen are not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm · retrieved 2026-08-02

kitchen-pizza-fractional-display differentiator

Two enumerations, neither containing a placement construct. First, the Condiments chapter: prefixes "change the state of a condiment" and the documented set is No, Add, Extra, Plain and Descriptor, with quantity handled by menu item class option 54 - Condiment entry/display relational to Parent Item's quantity; no halves, quarters or section attribute exists on a condiment anywhere in the chapter. Second, kdscu r_kds_chit_layouts.htm enumerates every KDS chit layout style Simphony ships - Standard, Standard DOM 1/2/3, order-type and zone variants, cook-time variants and the SEI layouts - and describes what each renders (item lines, status icons, timers, headers, trailers), with no sectioned or graphical topping rendering. The residual doubt that stops this being an absence finding: condiment prefixes are operator-created records (t_condiments_create_condiment_prefix_mi.htm), so a site can create prefixes named for halves and they will print as text on the chit. That is a naming convention rather than a placement model, and Oracle documents neither its use nor its rendering.

kitchen-recall-refire

The POS guide documents "Re-firing Items to the Order Device", and the KDS guide documents bump bar and toolbar functions covering review and recall of bumped orders. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

kitchen-order-modification-alerts differentiator

KDS Highlight Schemes can colour chits by order type and production item, and Menu Item Timing documents Voiding Timed Items. Explicit add/change/remove flagging on a chit already displayed is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm · retrieved 2026-08-02

kitchen-guest-ready-notification differentiator

A first-party Order Status Display plug-in (19.8.4.1) drives a guest-facing status board off "an in-memory snapshot of Kitchen Display System (KDS) data" with multi-revenue-center filtering. The shortfall is the claim's "without a separate product purchase" test: Simphony Kitchen Display Services Cloud Service (B81484) is "required for each Kitchen Display System (KDS) client connected to the Simphony system" and "is required even if the customer is using a non-Oracle KDS client solution". SMS and app push are not documented as first-party at all. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02 adversarially verified

kitchen-waste-logging

Waste is a documented first-class construct — Menu Item Waste, Declaring Waste, Correcting Waste Checks, Menu Item Waste Reports — and Inventory Management books unbooked POS waste checks, so the entry does deplete inventory. The shortfall is where: waste is declared through a waste check at the POS workstation, not from the KDS screen, and reason codes on the POS waste entry are not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

kitchen-speed-of-service-reporting

Reporting and Analytics ships Speed of Service reports in four variants (TSR/QSR x add-on/inclusive tax), plus Kitchen Performance, Kitchen Display Detail by station and Kitchen Display Orders by Check. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

kitchen-prep-forecasting

Inventory Management documents Production, Forecast Out of Stock, and Preparation and Thaw Pull statistics, and Labor Management adds forecast-driven staffing. A kitchen-facing daily prep task list generated from forecast demand is not documented as a shipped screen. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

delivery-driver-roster

No driver as an employee class exists. Labor Management enumerates job codes, roles and shifts for restaurant staff with no driver role, dispatch state or on-shift/on-road distinction, and no delivery module defines one. Oracle publishes a complete Simphony documentation index — Transaction Processing, Simphony Plug-ins, Kitchen Display System, GloriaFood, Labor Management, Gift and Loyalty, Inventory Management, Restaurant Payments, the POS Employee, Manager and Frontline Manager user guides, Reporting and Analytics, Forecasting and Budget, and InMotion Mobile. No delivery-management guide appears anywhere in it, and the delivery documentation that does exist (Delivery Connector Configuration, current and 19.7) covers only third-party marketplace connectors: Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates. Simphony's delivery model is marketplace order injection, not an in-house fleet.

delivery-dispatch-board

No first-party dispatch or expo board for in-house drivers exists. The documented order destinations are the KDS and the marketplace connectors; there is no assign-to-driver surface. Oracle publishes a complete Simphony documentation index — Transaction Processing, Simphony Plug-ins, Kitchen Display System, GloriaFood, Labor Management, Gift and Loyalty, Inventory Management, Restaurant Payments, the POS Employee, Manager and Frontline Manager user guides, Reporting and Analytics, Forecasting and Budget, and InMotion Mobile. No delivery-management guide appears anywhere in it, and the delivery documentation that does exist (Delivery Connector Configuration, current and 19.7) covers only third-party marketplace connectors: Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates. Simphony's delivery model is marketplace order injection, not an in-house fleet.

delivery-route-map differentiator

No route planning or multi-stop sequencing surface exists. Nothing in the guide set renders a map or orders stops for a driver. Oracle publishes a complete Simphony documentation index — Transaction Processing, Simphony Plug-ins, Kitchen Display System, GloriaFood, Labor Management, Gift and Loyalty, Inventory Management, Restaurant Payments, the POS Employee, Manager and Frontline Manager user guides, Reporting and Analytics, Forecasting and Budget, and InMotion Mobile. No delivery-management guide appears anywhere in it, and the delivery documentation that does exist (Delivery Connector Configuration, current and 19.7) covers only third-party marketplace connectors: Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates. Simphony's delivery model is marketplace order injection, not an in-house fleet.

delivery-driver-tracking differentiator

No driver GPS or live-location tracking exists. Simphony tracks no driver entity, so there is nothing to locate; courier position on marketplace orders is held by the marketplace. Oracle publishes a complete Simphony documentation index — Transaction Processing, Simphony Plug-ins, Kitchen Display System, GloriaFood, Labor Management, Gift and Loyalty, Inventory Management, Restaurant Payments, the POS Employee, Manager and Frontline Manager user guides, Reporting and Analytics, Forecasting and Budget, and InMotion Mobile. No delivery-management guide appears anywhere in it, and the delivery documentation that does exist (Delivery Connector Configuration, current and 19.7) covers only third-party marketplace connectors: Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates. Simphony's delivery model is marketplace order injection, not an in-house fleet.

delivery-zones-polygon differentiator

No delivery-area definition exists — neither polygon nor radius nor postcode list. Zones in Simphony are an organisational tier of the Enterprise/Property/Revenue Center hierarchy, a reporting and configuration grouping, and not a geographic delivery boundary. Oracle publishes a complete Simphony documentation index — Transaction Processing, Simphony Plug-ins, Kitchen Display System, GloriaFood, Labor Management, Gift and Loyalty, Inventory Management, Restaurant Payments, the POS Employee, Manager and Frontline Manager user guides, Reporting and Analytics, Forecasting and Budget, and InMotion Mobile. No delivery-management guide appears anywhere in it, and the delivery documentation that does exist (Delivery Connector Configuration, current and 19.7) covers only third-party marketplace connectors: Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates. Simphony's delivery model is marketplace order injection, not an in-house fleet.

delivery-zone-pricing

No per-zone delivery fee or minimum exists, following from the absence of any delivery-zone construct. Delivery charges on marketplace orders are set by the marketplace. Oracle publishes a complete Simphony documentation index — Transaction Processing, Simphony Plug-ins, Kitchen Display System, GloriaFood, Labor Management, Gift and Loyalty, Inventory Management, Restaurant Payments, the POS Employee, Manager and Frontline Manager user guides, Reporting and Analytics, Forecasting and Budget, and InMotion Mobile. No delivery-management guide appears anywhere in it, and the delivery documentation that does exist (Delivery Connector Configuration, current and 19.7) covers only third-party marketplace connectors: Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates. Simphony's delivery model is marketplace order injection, not an in-house fleet.

delivery-address-validation

No guest address capture or validation for first-party delivery exists. Marketplace orders arrive with the address already resolved by the marketplace. Oracle publishes a complete Simphony documentation index — Transaction Processing, Simphony Plug-ins, Kitchen Display System, GloriaFood, Labor Management, Gift and Loyalty, Inventory Management, Restaurant Payments, the POS Employee, Manager and Frontline Manager user guides, Reporting and Analytics, Forecasting and Budget, and InMotion Mobile. No delivery-management guide appears anywhere in it, and the delivery documentation that does exist (Delivery Connector Configuration, current and 19.7) covers only third-party marketplace connectors: Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates. Simphony's delivery model is marketplace order injection, not an in-house fleet.

delivery-driver-comp differentiator

No driver pay, per-run compensation or mileage reimbursement construct exists. Labor Management pays hourly and salaried job codes and has no per-delivery earning type. Oracle publishes a complete Simphony documentation index — Transaction Processing, Simphony Plug-ins, Kitchen Display System, GloriaFood, Labor Management, Gift and Loyalty, Inventory Management, Restaurant Payments, the POS Employee, Manager and Frontline Manager user guides, Reporting and Analytics, Forecasting and Budget, and InMotion Mobile. No delivery-management guide appears anywhere in it, and the delivery documentation that does exist (Delivery Connector Configuration, current and 19.7) covers only third-party marketplace connectors: Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates. Simphony's delivery model is marketplace order injection, not an in-house fleet.

delivery-cash-reconcile

No driver bank or driver cash settlement exists. Enterprise Cash Management enumerates its own constructs — tills, safes and server banks — and a driver bank is not among them. Oracle publishes a complete Simphony documentation index — Transaction Processing, Simphony Plug-ins, Kitchen Display System, GloriaFood, Labor Management, Gift and Loyalty, Inventory Management, Restaurant Payments, the POS Employee, Manager and Frontline Manager user guides, Reporting and Analytics, Forecasting and Budget, and InMotion Mobile. No delivery-management guide appears anywhere in it, and the delivery documentation that does exist (Delivery Connector Configuration, current and 19.7) covers only third-party marketplace connectors: Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates. Simphony's delivery model is marketplace order injection, not an in-house fleet.

delivery-daas-dispatch

Enumerated simcg/toc.htm (845 topics), sipou/toc.htm (198) and kdscu/toc.htm (129): current Simphony has no delivery driver, dispatch, courier or delivery-zone module at all. Delivery Connectors is marketplace order injection only - c_delivery_connectors.htm names Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates as the supported providers and describes the tool as one "that allows you to add, modify, and delete delivery platform integrations" - and the Add Delivery Connector wizard, whose fields I read in full, has no courier quote, fee or tracking field. The nearest thing to driver handling is the KDS posting file's DS_DISPATCHED / DS_UNDISPATCHED / DS_DELIVERED distribution states, all three footnoted "For future use; currently unavailable". Left unknown because first-party delivery for Simphony is fronted by separate Oracle products - Digital Ordering, and the GloriaFood integration in simphony/simgi, whose Delivery Charges topic covers a service charge only - and neither is enumerated for courier handoff here.

delivery-daas-fallback differentiator

This presupposes the in-house driver dispatch that delivery-daas-dispatch shows Simphony does not document: there is no driver roster, no delivery zone, no wait threshold and no courier handoff anywhere in simcg (845 topics), sipou (198) or kdscu (129), so there is nowhere for an overflow rule to live. Searched the full corpus for dispatch, courier, driver and zone - the driver hits are payment, loyalty and stored-value software drivers, and the zone hits are the EMC hierarchy Zone and the KDS chit "zone identifier" used to group delivery orders on a chit layout. Unknown rather than absent for the same reason as the parent claim: Oracle's first-party delivery flow lives in separately documented products.

delivery-3p-direct-integration differentiator

Oracle ships vendor-owned Delivery Connectors for Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates with no middleware. Grubhub is absent from the supported list, so the DoorDash + Uber Eats + Grubhub trio most US operators need is incomplete. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_delivery_connectors.htm · retrieved 2026-08-02

delivery-3p-injection

The Uber Eats connector configuration includes the Order Type applied to orders received from Uber Eats, the Tender Name used to settle them, the Employee they are assigned to, and open-discount handling — i.e. marketplace orders land as real Simphony checks. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_add_ubereats.htm · retrieved 2026-08-02

delivery-menu-push

Menu push is configured field by field: Parent and Condiment Price Sequence Levels, Image Slot Number, SLU Slot, four Combo Sizes, Default Condiment Group Name, condiment-group exclusions, menu display title and service-period hours by day of week. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_add_ubereats.htm · retrieved 2026-08-02

delivery-86-sync

Configure Menu Items (DoorDash): "Change the availability status of a menu item to generate a notification through the delivery application, advising DoorDash of the menu item's new status (unavailable or available). These updates are immediately sent to DoorDash and will update in near real time." t_dc_menu_items_ubereats.htm repeats it verbatim for Uber Eats, and the restore direction is explicit in "unavailable or available". Shortfalls against the claim as worded: only two of the five supported providers - the Configure Menu Items topics for Deliveroo, Rappi and Skip The Dishes contain no availability-notification step; and item level only - Oracle documents no condiment/modifier (item-option) availability push, which is exactly what DoorDash requires of new POS partners. The only condiment-level control published is the static ExcludeFromDeliveryPlatforms data extension, which permanently hides an item or combo group member from the provider menu rather than 86ing it. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_menu_items_doordash.htm · retrieved 2026-08-08

delivery-store-pause

Disable Delivery Service Provider: "Access Delivery Connectors from Simphony Home. Navigate to the location. Click the ellipsis adjacent to the location, and then select Deactivate Connection." It is per location and per provider, applies to all five supported providers, and c_dc_status.htm confirms Inactive is a first-class integration state ("the integration configuration has been completed but is not yet connected to Simphony, or has been deactivated"), so the connection can be turned off and back on from Oracle's own console rather than the marketplace's tablet. Shortfalls: there is no timed auto-reactivation - nothing in the chapter schedules a resume, and reactivation is a manual step whose effect the DoorDash wizard warns is not immediate ("one hour after activation, the store will be visible and ready for ordering on the delivery service provider website"); and it is a cloud admin action in Simphony Home behind a Delivery Connectors access privilege, not a busy-mode button on the POS workstation. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_disable.htm · retrieved 2026-08-08

delivery-3p-reconciliation differentiator

Enumerated the Reporting and Analytics Reports Guide manifest (back-office/20.1/rarrg/toc.htm, 222 report topics): nothing matches delivery, third party, aggregator, commission or payout. The financial reports are Income Audit by Tender / Discount / Major Group / Family Group, Adjustments - Voids, All Checks with Voids, Check Detail with its Check Journal drill-down, and the labor set. On the Simphony side each provider is mapped to a Tender/Media record and an Order Type - c_dc_info_required.htm marks both Required for all five providers - so 3P sales are separable in reporting by tender and order type, but that is POS-recorded revenue only. Nothing in the Delivery Connectors chapter ingests a marketplace payout file, and commission, marketing fees and adjustments are never mentioned. Stopped short of absence because Reporting and Analytics is licensed separately from Simphony and supports customer-authored reports over its data access layer.

delivery-injection-error-visibility differentiator

View Delivery Connector Status gives the operator a per-location, per-provider integration console: "If your enterprise has existing Delivery Connector integrations, you can see an overview of the locations, the delivery service provider for each location, and the status", groupable by Location, Delivery Service or Status, with an enumerated status set - Active ("integration configuration has been completed and the delivery platform is successfully connected to Simphony"), Inactive, In Progress, and Error ("indicates integration failure. If this is an unexpected status, contact Support to start a case to analyze the cause of the issue"). Shortfalls: this is connection health, not order health - there is no failed or rejected order-injection queue, no per-order error detail and no alerting, and the Error state's documented remedy is to open an Oracle Support case. Simphony's own alerting stops at the store boundary: Property Parameters option 53 - Enable Workstation Alerting and the Show Checks With Failed Prints To KDS/Order Device key cover orders failing to reach an order device, and sipou c_workstation_unsent_checks_warning.htm warns on unsent checks from a workstation. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_dc_status.htm · retrieved 2026-08-08

delivery-tracking-page

No first-party guest-facing order tracking page exists. Where a tracking experience is present on a marketplace order it is the marketplace's, not Simphony's. Oracle publishes a complete Simphony documentation index — Transaction Processing, Simphony Plug-ins, Kitchen Display System, GloriaFood, Labor Management, Gift and Loyalty, Inventory Management, Restaurant Payments, the POS Employee, Manager and Frontline Manager user guides, Reporting and Analytics, Forecasting and Budget, and InMotion Mobile. No delivery-management guide appears anywhere in it, and the delivery documentation that does exist (Delivery Connector Configuration, current and 19.7) covers only third-party marketplace connectors: Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates. Simphony's delivery model is marketplace order injection, not an in-house fleet.

delivery-promise-time differentiator

No first-party delivery promise time or quote engine exists. Quote times on marketplace orders are computed by the marketplace. Oracle publishes a complete Simphony documentation index — Transaction Processing, Simphony Plug-ins, Kitchen Display System, GloriaFood, Labor Management, Gift and Loyalty, Inventory Management, Restaurant Payments, the POS Employee, Manager and Frontline Manager user guides, Reporting and Analytics, Forecasting and Budget, and InMotion Mobile. No delivery-management guide appears anywhere in it, and the delivery documentation that does exist (Delivery Connector Configuration, current and 19.7) covers only third-party marketplace connectors: Deliveroo, DoorDash, Rappi, Skip The Dishes and Uber Eats/Postmates. Simphony's delivery model is marketplace order injection, not an in-house fleet.

delivery-offline-behavior

Simphony documents workstation offline behaviour in detail - t_properties_offline.htm (Property Parameters option 6, whether offline checks post with the actual transaction time or the upload time), t_check_allow_check_replay.htm (PMC privilege 30001 to manually replay offline checks that failed to replay automatically), c_reset_totals_sod_offline.htm (Start of Day while a property is in Yellow Mode), the closed-check O - Offline indicator, and kiosk workstation option 17 - Allow Offline Operations - but every one of those concerns a check created AT a workstation. Marketplace orders arrive through Transaction Services Gen 2 into a CAPS Service Host of type POS API Client (t_dc_workstations.htm), and the only resilience Oracle offers there is redundancy rather than queueing: "Oracle Restaurants recommends enabling at least two workstation devices that can receive checks and orders as this will provide resiliency should one of the workstations become unavailable." No page states what happens to inbound DoorDash or Uber Eats orders during an outage, and since Simphony documents no in-house driver model there is no driver-assignment or driver-settlement behaviour to document either.

digital-first-party-web

Oracle publishes a Simphony/GloriaFood integration configuration guide covering EMC setup, tender media for Pay In-Store and Pay Online With Credit Card, order types, discounts, service charges, menu tags, menu items and automatic order acceptance — GloriaFood is an Oracle-owned commission-free ordering product, so this is genuinely first-party. Two shortfalls: the guide is scoped to Simphony Essentials, and orders reach the POS over Transaction Services Gen2, which is a separately licensed SKU. https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/toc.htm · retrieved 2026-08-02

digital-menu-single-source

The GloriaFood guide configures Menu Items, Menu Tags and Screen Lookups on the Simphony side before GloriaFood setup, which implies the POS menu is the source. No documented automatic push keeping the GloriaFood menu in sync with subsequent EMC edits was found. https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/toc.htm · retrieved 2026-08-02

digital-native-app differentiator

GloriaFood (Oracle-owned, and the online-ordering platform Oracle documents for Simphony) sells a white-label app: "This is your own, custom-built mobile app for Android and iOS... The apps are automatically published to Google and Apple stores and any changes you make later are also automatically updated." Shortfall: this is a GloriaFood vendor feature page, not Oracle product documentation -- the Simphony/GloriaFood integration guide (simgi) documents only menu, discount and service-charge sync plus order injection and never mentions a branded app, and simgi/c_version_support.htm caps the integration at "One to three sites" and lists "Customizations to front-end journey or workflow" as not supported. No Oracle-documented first-party branded consumer app exists for Simphony proper. https://www.gloriafood.com/white-label-food-ordering-app · retrieved 2026-08-08

digital-account-saved-payment

GloriaFood's white-label app page states "the checkout form is prefilled based on previous orders, while the delivery address can be selected from a list of saved addresses" -- saved addresses and returning-guest prefill are documented. Shortfalls: no saved/tokenized card on file is documented anywhere (Oracle's simgi/c_version_support.htm states online payment runs through "Stripe and/or PayPal" and simgi/t_emc_tender_cc.htm states "The Simphony Cloud Service does not process GloriaFood credit card transactions"), and no one-tap reorder of a previous order is documented -- prefilling a checkout form is not reorder. https://www.gloriafood.com/white-label-food-ordering-app · retrieved 2026-08-08

digital-upsell-engine differentiator

Enumerated the whole Simphony/GloriaFood integration book (docs.oracle.com simphony/simgi/toc.htm, 33 topics) -- it covers menu items, menu tags, screen lookups, discounts, service charges, delivery charges, tips, order types, fulfilment time and auto-accept, and contains no suggestive-selling, recommendation or attach-rate topic. Enumerated the 922-entry Configuration Guide manifest (simphony/simcg/toc.htm): the only 'suggestion' topic is t_tms_table_suggestion_factors.htm, which is table-seating suggestion in Table Management, not menu upsell. simgi/c_version_support.htm additionally lists "Customizations to front-end journey or workflow" as not supported with GloriaFood. Nothing found either way on attach-rate reporting for digital suggestions, so this is unresolved rather than absent.

digital-scheduled-pacing

Future/scheduled digital orders are documented and configured in EMC: RVC Parameters > Autofire carries an Autofire Employee, Autofire Workstation, Default Autofire Tender/Media, option "3 - Enable Autofire in this Revenue Center", and a "Maximum Days" field -- "the maximum number of days (in the future) that Autofire checks can be scheduled", which the guide says must match "Minimum time in advance in Table Reservation and Scheduled Orders from GloriaFood". Order Type Parameters > Service Level Time sets "the number of minutes an order will fire to the kitchen before the guest or delivery driver arrives". Shortfall: this is a lead-time and horizon control only -- no per-daypart or per-time-slot capacity limit on orders or items, and no automatic closing of a saturated slot, is documented on the Simphony side of the integration. https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/t_emc_fulfillment_time.htm · retrieved 2026-08-08

digital-fulfillment-modes

The GloriaFood integration configures order types and tenders for online orders including Pay In-Store and Pay Online With Credit Card, and Order Channels separately name kiosk, drive-thru, in-restaurant and delivery aggregator. Curbside arrival check-in is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/toc.htm · retrieved 2026-08-02

digital-qr-table

Simphony documents Guest Pay, which attaches to the existing open check and does handle tipping: Tender Parameters > Guest Pay options, a CreditDebit:Loadable / CreditAuthAndPay payment command, a charge-tip service charge with "9 - Charged Tip Required", and three suggested tip percentages per order type plus "13 - Hide Custom Tip Button" and "14 - Hide No Tip Button". Shortfalls: Guest Pay is explicitly not a guest-facing QR scan -- it is "a means for guests to pay their checks with a credit card through the mobile device that the server uses to take orders" and is "only supported when using workstation types 1 - Mobile and 7 - Oracle Payments Order and Pay"; no check splitting is documented in the Guest Pay flow; and GloriaFood's QR Code Ordering channel opens a new GloriaFood order rather than attaching to an existing POS check. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_payments_configure_guest_pay.htm · retrieved 2026-08-08

digital-kiosk differentiator

The Simphony Kiosk plug-in (19.8.3.4) runs the same EMC menu and modifier engine and ships Gift and Loyalty and Givex helpers, with a Kiosk JavaScript API reference published separately. Accessibility conformance and unattended-EMV specifics are not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-08-02

digital-group-ordering

Enumerated simphony/simgi/toc.htm (33 topics, the Oracle-documented GloriaFood online-ordering integration) and the 922-entry simphony/simcg/toc.htm manifest: no shareable-link group order, per-participant cart, or per-person spend cap topic exists in either. GloriaFood's own channel navigation on www.gloriafood.com enumerates QR Code Ordering, Website Ordering, Facebook Ordering, Scheduled Orders, Delivery, Takeaway, Table Reservations and a Hotel Ordering System, with no group-ordering entry -- but a marketing navigation is not an exhaustive feature list, so this stays unresolved rather than negative.

digital-catering-portal differentiator

Checked the Simphony Configuration Guide manifest (simphony/simcg/toc.htm, 922 entries) for a catering flow: the closest topics are the Banquet Guest Check Printing chapter (c_banquet_guest_chk_print.htm and its four configuration topics), which is banquet check printing from a workstation, not a guest-facing catering ordering portal with lead-time rules, quotes, deposits or invoice terms. simphony/simgi/toc.htm has no catering topic and www.gloriafood.com's channel navigation lists no catering flow. Separate catering menus, minimums, proposals and house-account/ACH terms are unresolved on docs.oracle.com.

digital-voice-ai-phone differentiator

Enumerated simphony/simcg/toc.htm (922 entries) and simphony/simgi/toc.htm (33): no voice, telephony, call-answering or speech topic appears in either, and the Delivery Connectors chapter names only Deliveroo, DoorDash, Rappi, Skip and Uber Eats/Postmates as certified order-injection partners. No Oracle page naming a certified AI voice phone-ordering partner for Simphony was retrieved; oracle.com product pages return 403 to automated retrieval, so the marketing side is unchecked and this stays unresolved.

digital-drivethru-ai

Enumerated simphony/simcg/toc.htm (922 entries) for drive-thru topics and found none that involve speech or AI order-taking; simphony/simgi/toc.htm (33 topics) has no drive-thru content at all. No Oracle documentation for AI voice ordering in the lane, menu/modifier grounding, or escalation-to-human handoff was located on docs.oracle.com. oracle.com marketing pages 403 to automated retrieval, so this is unresolved rather than absent.

digital-sms-ordering

Checked the Oracle-documented digital channels: simphony/simgi/toc.htm (33 topics) covers only GloriaFood web/app order injection, and GloriaFood's own channel list on www.gloriafood.com is QR Code, Website, Facebook, Scheduled Orders, Delivery, Takeaway, Table Reservations and Hotel Ordering. The Gift and Loyalty guide's coupon Issue Instructions dropdown (back-office/20.1/gnlug/t_coupon_configuring.htm) offers only "Issue at POS Terminal", "Not Issued at POS Terminal" and "Issued by Email" -- no SMS send path. No text-to-order or text-a-link ordering flow was found, but no Oracle page states its absence either.

digital-google-order differentiator

Searched the Oracle Simphony documentation tree for Order with Google provisioning: simphony/simgi/toc.htm (33 topics) documents GloriaFood publishing only to the restaurant's own website, Facebook page and mobile app, and simphony/simcg/toc.htm (922 entries) has no Google Business Profile or ordering-link provisioning topic. GloriaFood's publishing pages on www.gloriafood.com describe website, Facebook, WordPress/Wix/Squarespace/Joomla/Weebly plugins and the branded app, with no Order with Google or 'Preferred by Business' provisioning claim located. Unresolved -- no page states it is unsupported.

digital-apple-business-connect

Checked simphony/simgi/toc.htm and simphony/simcg/toc.htm for any Apple Maps, Apple Business Connect or place-card integration and found none; GloriaFood's documented publishing surfaces (www.gloriafood.com) are the restaurant website, Facebook, the CMS plugins and the branded iOS/Android app. No Oracle or GloriaFood page describing an 'Order Food' custom action on an Apple Maps place card was retrieved. Unresolved.

digital-loyalty-attach

The POS guide documents loyalty balance inquiry, issuing and redeeming points and coupons and applying a loyalty card to a check, and the GloriaFood integration configures discounts on the Simphony side. Loyalty enrolment and redemption inside the GloriaFood ordering flow is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

digital-subscriptions

Checked the Gift and Loyalty user guide manifest (back-office/20.1/gnlug/toc.htm), whose program types are enumerated in c_faq.htm as gift cards, meal, loyalty, awards and credit, with card programs covering basic gift cards, bonus stored value, reloading meal cards, spend-or-lose, house account credit cards and discount cards -- none is a recurring-billing subscription or paid membership tier, and no recurring-charge scheduler appears in the rule references. Also checked simphony/simgi/toc.htm for subscription handling on the digital channel: none. Recurring billing for a delivery-fee waiver or per-period entitlement is unresolved on docs.oracle.com.

digital-promo-parity

Discounts genuinely are defined once and pushed to the digital channel: simgi documents "Managing the Simphony content that appears in GloriaFood, including... Discounts", with separate topics for GloriaFood Managed Discounts and Simphony Automatic Discounts, plus service charges, delivery charges and tips. Named shortfall, from Oracle's own unsupported list in c_version_support.htm: "The following features are not supported with GloriaFood: ... First buy promo discounts ... Gift and Loyalty". Loyalty offers and coupons therefore do NOT carry to the first-party digital channel at all, so parity across POS, kiosk and digital is broken for the loyalty half of the claim; no channel-eligibility flag on a discount record is documented. https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/c_version_support.htm · retrieved 2026-08-08

digital-guest-data-ownership differentiator

Oracle Cloud Hosting and Delivery Policies commit to making Your Content retrievable in a structured, machine-readable format for 60 days after termination. No Simphony-specific self-serve bulk guest export in the product UI is documented, and the policy is generic to Oracle Cloud rather than Simphony. https://www.oracle.com/contracts/docs/ocloud_hosting_delivery_policies_3089853.pdf · retrieved 2026-08-02

digital-checkout-pci-sca

Card data does not touch the restaurant's page: Oracle states "Stripe and/or PayPal are allowed as payment solutions" for GloriaFood online payment (c_version_support.htm) and, in t_emc_tender_cc.htm, that "The Simphony Cloud Service does not process GloriaFood credit card transactions. GloriaFood credit card payment amounts are stored in this tender and appear in POS reports" -- the digital checkout is a gateway-hosted flow reconciled back as a tender record 999999. Shortfalls: Oracle publishes no Simphony- or GloriaFood-specific PCI DSS 4.0 attestation covering the hosted payment page, nothing addressing the client-side script-integrity requirements effective March 2025, and no 3DS/SCA statement for this channel. https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/c_version_support.htm · retrieved 2026-08-08

digital-surcharge-transparency differentiator

Fee configuration is partly shared: the GloriaFood integration book carries EMC-side topics for Service Charges, Delivery Charges, Tips and Other Service Charges, so service-fee definitions made in EMC do reach the digital channel. Shortfall: credit-card surcharging is a POS payment path feature (simcg t_payments_cc_surcharge_donations.htm, "Enabling Credit Card Surcharge or Charity Donations") and Simphony does not process GloriaFood card transactions at all -- c_version_support.htm names Stripe and/or PayPal as the online payment solutions -- so card surcharge and its guest-facing disclosure cannot be applied to the first-party digital channel from the same configuration. No jurisdiction-level or card-brand prohibition handling for surcharging is documented for either channel. https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/c_version_support.htm · retrieved 2026-08-08

guest-loyalty-unified-profile

Gift and Loyalty is an account-based CRM tracking visits, spend and balances, reported through enterprise reporting, and the POS guide documents applying a loyalty card to a check. Documented dedup/merge of the same guest across POS, web and kiosk was not found. https://docs.oracle.com/en/industries/food-beverage/simphony/19.3/simcg/c_loyalty_gift_programs.htm · retrieved 2026-08-02

guest-loyalty-thirdparty-identity-attach differentiator

Read the whole Delivery Connectors chapter of the Configuration Guide (simphony/simcg/c_delivery_connectors.htm and children). Table 14-3 in c_dc_info_required.htm is a Required/Optional/Not Supported matrix of every Simphony item configured for Deliveroo, DoorDash, Rappi, Skip and Uber Eats/Postmates -- Tender/Media, Order Type for Delivery and Remakes, Open Discount, Open Service Charge, Delivery Service Provider Employee, Currency, Language Culture, Menu Tags, customer-facing names/descriptions/images/prices, SLUs, condiments, nutrients, allergens, combo meals and filters -- and carries no guest-identity item. t_dc_add_doordash.htm's connector setup asks only for Location, store, Revenue Center, Order Type, Tender Name and Employee, and the word customer/guest/loyalty never appears. That matrix is the OUTBOUND (Simphony-to-marketplace) surface, however, and Oracle publishes no schema for the inbound order payload, so whether a marketplace guest name or contact lands on the check or attaches to a Gift and Loyalty account remains undetermined.

guest-loyalty-accrual-models

Program types include loyalty (point-based), meal, awards, gift and credit, and the POS guide documents Issuing Loyalty Points and Redeeming a Gift Card and Issuing Points. Visit/punch and spend-tier accrual are not documented as configurable models. https://docs.oracle.com/en/industries/food-beverage/simphony/19.3/simcg/c_loyalty_gift_programs.htm · retrieved 2026-08-02

guest-loyalty-tiers differentiator

Gift and Loyalty documents tiering in two forms. Tiered awards: "Setting Up Tiered Loyalty Awards" builds multiple point thresholds ordered by descending Precedence, each a Points Awards Rule with a Point Threshold and Cross Point Threshold selected, "a $5 discount at 50 points, a $10 discount at 100 points and a free entree at 200 points", plus an optional lowest-precedence rule whose Point Cost equals its Point Threshold to reset the balance. Member status tiers also exist as an entity: accounts carry a Program Level, changed via the customer's information hub (c_customer_account_manage.htm, "Change Program Level") and gated by the Change Account Tier permission. Shortfall: those program-level changes are a manual administrative action, and the automatic movement documented is point-threshold crossing and an optional points reset -- no rolling-window spend or visit-count promotion, and no automatic demotion, is documented. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_using_loyalty_award_tiers.htm · retrieved 2026-08-08

guest-loyalty-offline-behavior differentiator

The EMC Loyalty module's option table (Table 36-3 Loyalty Options) states the behaviour explicitly and normatively: option "1 - Support Offline Transactions -- Disable this option as loyalty transactions are not supported in offline mode." That is a published, unambiguous answer of the blocked kind for lookup, accrual and redemption alike: when the workstation is offline, loyalty operations do not run and are not queued. The remaining options in the same table (2 Always Print Loyalty Results, 3 Never Display Loyalty Results, 5 Remove Loyalty Results Print Button, 6/7 remove the Guest Name and Phone Number Lookup buttons, 8 Use Loyalty Account for Stored Value) are the whole configurable surface of the Loyalty module and add no offline queue-and-reconcile alternative. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_loyalty_options.htm · retrieved 2026-08-08

guest-loyalty-offer-stacking-rules differentiator

Precedence is a first-class configuration field on all three rule types, with the conflict semantic spelled out. Coupon types: "Select the priority for the coupon in Precedence. If there is a coupon conflict for a transaction, such as two coupons that discount the same item but prohibit usage with other offers, Gift and Loyalty processes the coupon with the highest precedence value." Loyalty point award rules (t_loyalty_creating_awards.htm): "If more than one loyalty rule would apply to a transaction, Gift and Loyalty uses the rule with the highest precedence value." Redemption rules (t_redemption_configuring.htm): a Type of Exclusive or Inclusive plus "If more than one redemption rule would apply to a transaction, Gift and Loyalty uses the rule with the highest precedence value." Combinability is configured too: Allow Multiple Redemptions on a coupon type, Max Coupons Per Program on an award, and Cross Point Threshold to "allow customers to continue earning points for additional awards after being issued this award." https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_coupon_configuring.htm · retrieved 2026-08-08

guest-loyalty-targeted-offers differentiator

Offers are issued by rule, not only broadcast. An Issue Eligibility Rule on a coupon type, and an Eligibility Rule on a points award rule, select on spend (Check Min Value, with Include Service Charges / Include Taxes / Exclude Payment switches), on items purchased (Menu Item, Major Group or Family Group by POS object number or master, Combo Group Number, Items must be unique), on frequency within a window (Item Rule Types "Num Items in Transaction this Period" and "Num Combos in Transaction this Period", with Unique Item Expiration Methods including "Expire items after x rolling periods" and "Reset all items after x rolling periods"), and on recency-style time rules (Table 8-3: Bonus Period, Blackout Period, Birthday Anniversary, Signup Anniversary, Consecutive Period, Active Period). Awards can also key off Balance Use Type Lifetime, Year to Date or Month to Date. Coupons can then be Issued by Email. Shortfall: every one of these is evaluated against a qualifying transaction at the moment of issue -- there is no documented audience query that selects an existing customer set by recency or lapse for an outbound send, and the only list-style path is Allow Ad Hoc Issue, which issues to specific customers chosen by hand or in bulk. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/c_rule_reference_eligibility.htm · retrieved 2026-08-08

guest-loyalty-rfm-segmentation differentiator

The Gift and Loyalty subject areas expose the RFM inputs per customer as first-class reportable attributes: Gift and Loyalty Customer Summary carries First Transaction Business Date, Last Transaction Date, Check Count, Guest Count, Sales Amount, Sign-up Date and an Active flag; Gift and Loyalty CA Customer Program adds Transactions Count, Net Sales, Account Lifetime Credit Amount and a Category attribute; the Account subject area adds Lifetime, Year to Date and Month to Date credit totals. Shortfall: the guide lists fields, not computed segments -- no new / regular / at-risk / lapsed / VIP label is produced by the platform, and the operator must build the iQuery or report over these attributes themselves, which is precisely what this claim excludes. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_subj_area_gl.htm · retrieved 2026-08-08

guest-loyalty-lifecycle-automation

Two of the three named automations ship as always-on configurable rules. Birthday: an eligibility rule with a Birthday Anniversary Rule time rule, a Period Range Type and Periods Before or After to bracket the date, wired to a Points Awards Rule with Issue Immediate Discount, Point Threshold 0, Require Customer Info and Once Per Year. First-visit: "Setting Up a Registration Bonus" uses Balance Use Type "New customer info provided" with Once Per Life Time, fired by the overnight sync. A Signup Anniversary time rule also exists. Shortfalls: Table 8-3 enumerates the time-rule types (Bonus Period, Blackout Period, Activate Blackout Period, Birthday Anniversary, Signup Anniversary, Consecutive Period, Active Period) and contains no lapsed or inactivity trigger, so no win-back automation is configurable; and these rules issue POS-side awards and coupons rather than outbound campaign sends -- the Gift and Loyalty FAQ states campaigning is provided "in conjunction with third-party sales marketing and campaigning products". https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_using_birthday_discount.htm · retrieved 2026-08-08

guest-loyalty-native-email-sms differentiator

Oracle states campaigning functionality is provided in conjunction with third-party sales marketing and campaigning products — so the send channel is not native. A Digital Receipts plug-in (19.8.5) covers transactional email receipts only. https://docs.oracle.com/en/industries/food-beverage/simphony/19.3/simcg/c_loyalty_gift_programs.htm · retrieved 2026-08-02

guest-loyalty-consent-management

Per-purpose consent is configurable and stored on the guest profile. In Reporting and Analytics 20.1 and higher, iCare > iCare GPL > Guest Consent Configuration > Enabled exposes three consent options -- transaction processing consent, segmentation consent and marketing consent (c_notices_consent.htm) -- each with operator-authored statement text ("I consent to have my transaction data used by this company") and an Enable Privacy Documentation link. If marketing consent is enabled, at least one contact rule field must be placed on the customer registration form via iCare GPL > Customer Fields Display, positioned and marked optional or required. Shortfalls: the guide documents no consent timestamp and no source-of-consent capture, and documents no revocation mechanics at all -- neither a guest-initiated opt-out path beyond editing the profile on myicard.net nor propagation of a revocation across channels. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_notices_consent_configure.htm · retrieved 2026-08-08

guest-loyalty-10dlc-registration

Oracle publishes nothing on A2P 10DLC brand or campaign registration for Simphony or Gift and Loyalty. The prior `no` rested on the Issue Instructions dropdown of the coupon type configuration page (POS / non-POS / email), which is one object's issuance-channel field and asserts no completeness, plus the absence of an SMS subject area in the loyalty reporting schema. Gift and Loyalty's own feature description states that campaigning is performed 'in conjunction with third-party sales marketing and campaigning products', so the SMS send may sit outside the enumerated surface entirely. Unresolved rather than absent. adversarially verified

guest-loyalty-campaign-attribution differentiator

Campaign-level redemption reporting is a published schema. The "Gift and Loyalty CA Email Sent Opened" subject area carries Campaign Name, Offer Name, Promotion, Coupon Code, Coupon Serial Number, Sent Date and Time and Received Date and Time, filterable by campaign, coupon, offer and promotion in iQuery; "Gift and Loyalty Redeemed Coupon" carries Coupon Code, Coupon Type, Promotion, Serial Number, Amount, Issued and Redeemed Host/Local date-times, Issued and Redeemed Location and Reversal Status. So redemptions do tie back to a named campaign, offer and promotion. Shortfalls: the redeemed-coupon subject area records the coupon Amount, not the check total the offer was redeemed against, and no incremental-sales or lift measure is exposed -- incrementality would have to be constructed by the operator; and the CA (campaign) data originates from an integrated third-party campaigning product, since the Gift and Loyalty FAQ states campaigning is provided "in conjunction with third-party sales marketing and campaigning products". https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_subj_area_gl.htm · retrieved 2026-08-08

guest-loyalty-data-export-portability differentiator

Oracle publishes a Gift and Loyalty POS Web Services API Guide in the Simphony documentation set, and the 60-day post-termination retrieval policy applies. A fee-free self-serve bulk guest export in the product UI is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/ · retrieved 2026-08-02

guest-loyalty-cdp-event-api differentiator

Verified verbatim again: four notification resources (Organizations, Configuration, Check, Employees; Check only on-premise), endpoint must implement TLS 1.2 on port 443, only .com .net .org .edu .ca .io .site .se .sa top-level domains are supported, "Timeout for HTTP requests to subscribers is 15 seconds" "with no retry". No HMAC or signature scheme is documented. A feed that drops silently on a 15-second blip, restricts the TLD of your endpoint, and rides on a separately licensed SKU is not a dependable CDP source. https://docs.oracle.com/en/industries/food-beverage/simphony/stsgg/api-notifications-api-webhook.html · retrieved 2026-08-02

guest-loyalty-review-capture-routing differentiator

Enumerated the Gift and Loyalty user guide (back-office/20.1/gnlug/toc.htm) end to end -- FAQ, card programs, loyalty programs, awards, customer account administration, GPL setup, program configuration references, rule configuration references and configuration references. Its stated capabilities in c_faq.htm are account administration, the GPL card program, coupon administration, and campaigning "in conjunction with third-party sales marketing and campaigning products". No post-transaction survey, feedback request, score threshold, service-recovery routing or public-review-site handoff appears in any of those chapters, and the Reporting and Analytics Gift and Loyalty subject areas (rause/c_subj_area_gl.htm) contain no survey or score field. Because the FAQ is an overview rather than an exhaustive feature enumeration, and because any such capability could sit in the unnamed third-party campaigning product, this is unresolved rather than absent.

guest-loyalty-referral-program

Read the Gift and Loyalty rule configuration references in full (back-office/20.1/gnlug/): card rules, eligibility rules, coupon types, loyalty point issuance, loyalty point awards, redemption rules and stored value bonuses. Per-guest codes do exist in a narrow sense -- coupon types generate serial numbers in All Numeric, All Alpha (Limited Length) or Alpha with Check Digits formats -- but nothing binds a code to a referring account, attributes a referred guest's first order back to the referrer, or issues two-sided rewards. The award Balance Use Types are Point Balance Type, Lifetime, Year to Date, Month to Date and New customer info provided, none of which is a referral trigger. No Oracle page states referral is unsupported, so this stays unresolved.

guest-loyalty-wallet-pass differentiator

The Gift and Loyalty account model is card-and-account-number based throughout: c_cards_numbers.htm covers reviewing and creating card numbers, t_customer_account_new.htm and t_customer_account_batch.htm issue accounts against them, and the guest self-service surface is myicard.net (c_gpl.htm "Setting Up myicard.net", plus Review Customer Changes for changes a customer makes there). The POS lookup paths documented in the EMC Loyalty options are account number entry, Guest Name Lookup and Phone Number Lookup. No Apple Wallet or Google Wallet pass, and no push-updatable balance on a mobile pass, appears in gnlug or in simphony/simcg/c_loyalty_gift_programs.htm. Unresolved -- no page rules it out.

guest-loyalty-privacy-rights-tooling

Reporting and Analytics ships real DSAR tooling, but scoped to the wrong data subject. Its Data Privacy chapter states "People Management stores personally identifiable information such as names, email addresses, and sign-in date and time stamps... you can de-identify users", with Administration > System > Data Privacy > De-identify, a Personal Data Retention Period (Days) setting and optional automatic de-identification after N days since last sign-in, plus a downloadable machine-readable Personal Data Report under People > More Actions. Shortfall: every one of those acts on a People Management user record, not on a Gift and Loyalty guest account. Guest-side tooling in gnlug is limited to Guest Consent Configuration, closing an account (c_customer_account_manage.htm) and myicard.net self-service edits an administrator then approves or discards via Review Customer Changes -- there is no guest data export and no documented deletion propagation into loyalty or marketing records. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_data_privacy.htm · retrieved 2026-08-08

guest-loyalty-redemption-fraud-controls

Several of the named controls are documented. Manual adjustment is permission-gated: the Gift and Loyalty account administration portlet enumerates discrete permissions including Post Transactions ("post transactions and balance adjustments"), Reverse Transactions, Add/Edit Account Info, Change Account Tier, Allow Custom Transactions, Set Red Flag (flag an account) and Set Test Account. A velocity-style brake exists on redemption: "Delay Redemption of New Points (hours)" on a redemption rule imposes a waiting period before newly earned points can be spent (t_redemption_configuring.htm). Coupon serial numbers can be issued in an "Alpha with Check Digits" format that "includes two check digits to catch fraudulent redemption attempts". Shortfalls: no redemption-count or per-period velocity limit per account, no flagging of employee self-redemption, and no loyalty-specific audit log of who adjusted a balance is documented -- Review Customer Changes covers only edits a customer made on myicard.net. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/c_customer_account_permissions.htm · retrieved 2026-08-08

guest-loyalty-ai-offer-recommendation differentiator

Enumerated the Gift and Loyalty user guide manifest (back-office/20.1/gnlug/toc.htm) and read its rule configuration references: award and coupon targeting is entirely deterministic -- operator-chosen Precedence values, Point Thresholds, Balance Use Types, eligibility item and time rules. Nothing in the guide, in the Reporting and Analytics Gift and Loyalty subject areas (rause/c_subj_area_gl.htm), or in the Simphony Configuration Guide's Loyalty and Gift Card Interfaces chapter (simphony/simcg/c_loyalty_gift_programs.htm) describes machine-generated offer content, audience or send-time recommendation. Oracle's marketing pages at www.oracle.com/food-beverage/ return 403 to automated retrieval, so any shipped-vs-roadmap AI claim there could not be read and this stays unresolved.

guest-loyalty-stored-value-gift

Stored value is a full documented lifecycle at the POS: issue, activate, reload, transfer balance, authorize, redeem, cash out and void, plus batch issue and batch activate, with balances tracked enterprise-wide in Gift and Loyalty. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

labor-clock-in-at-pos

Start of Shift documents Clocking In and Out and Incrementing a Shift at the workstation, and Labor Management consumes those time card operations. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

labor-photo-punch-verification differentiator

Simphony's POS Client User Authentication topic enumerates identification methods (magnetic card, RFID card, employee ID, fingerprint; Android clients employee ID only) with 'Employees can provide IDs through one of the following methods', but that is the sign-in surface, not the timecard record, and the claim also covers a photo merely attached to a punch rather than used to authenticate. The Labor Pay Rules timekeeping page cited as the settings enumeration 404s at the Simphony path, and the release-9.1 version is a procedure listing clock-in timing rules, not an exhaustive option table. The Time Cards configuration hub links its related topics (adjustment notification, chit printing, shifts, breaks, auto clock-out, tip declaration) but asserts no completeness. Photo-at-punch is undocumented in either direction. adversarially verified

labor-geofenced-mobile-punch

The prior `no` rested on a clock-in task procedure plus two tables of contents (the InMotion Mobile guide and the Labor Management guide, whose Employee Self Service chapter covers schedules, time-off and shift-change requests). None of these asserts completeness, and none is a settings surface where a location or geofence option would have to appear. The Labor Pay Rules timekeeping settings do list clock-in restrictions with no location option, but that page presents itself as a procedure rather than an exhaustive option table. Simphony POS clients also run on Android handhelds, so the premise that punching is workstation-bound is not established. Undetermined. adversarially verified

labor-offline-time-punch differentiator

Clocking In and Out states that employees can clock in when a workstation is offline but can still communicate with other workstations and services, and that they cannot clock in when the workstation is fully offline (no network communication) and unable to communicate. Shortfalls: a genuinely isolated terminal blocks the punch outright, and Oracle documents no replay, reconciliation or duplicate-suppression behaviour for time cards on reconnect - the Setting Offline Transaction Posting Time option in the configuration guide (option 6, Post Offline Transactions with Actual Transaction Time) governs offline checks, not timekeeping. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/t_start_shift_clock_in_out.htm · retrieved 2026-08-08

labor-granular-rbac

People and Privileges is a dedicated configuration chapter and privileges are scoped through the Enterprise/property/revenue-center hierarchy; Inventory Management separately ships eight documented user/role rights reference tables (purchase, B2B, store, production, master data, mobile, system). https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

labor-manager-override-audit

The EMC Audit Trail records "All changes, additions, and deletions made in the EMC and PMC Procedures", successful and failed EMC sign-ins, PMC and audit-trail report activity, Key Manager activity, audit trail purges, credit card module activity and DbProcs utility activity, and Oracle states these are reportable. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_audit_trail.htm · retrieved 2026-08-02

labor-native-scheduling differentiator

Labor Management documents schedule profiles, blackout periods, staffing placeholders, schedule edit restrictions, creating, editing, submitting, approving, printing and emailing schedules, and schedule templates. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm · retrieved 2026-08-02 adversarially verified

labor-demand-labor-forecast differentiator

Staffing requirements are computed from forecast volume, not a fixed template. Productivity method: "define productivity factors and then apply the factors to the forecasted values to determine the staffing requirements" (forecast 832 x 0.042 = 35). Recipe/effort method: 90 seconds per pizza against a forecast of 250 pizzas = 22,500 seconds or 375 minutes of labor. General step method assigns headcount by forecast threshold. The underlying forecast is seeded from the location's own historical data, though it is generated manually. https://docs.oracle.com/cd/E80526_01/doc.91/e82051/c_config_staffing_profile.htm · retrieved 2026-08-02 adversarially verified

labor-realtime-labor-percent differentiator

Labor cost updates from live time card operations and Reporting ships Labor Summary and Employee Productivity reports. A during-service manager view showing labour as a live percentage of sales is not documented as a screen. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm · retrieved 2026-08-02

labor-overtime-prevention differentiator

Documented: Weighted Average Overtime, Weighted Average Overtime with Tip Credit, Configuring Work Requirements for Overtime Eligibility, and Configuring Calculations and Rules for Overtime Pay. All of it computes overtime; nothing documented blocks or warns at clock-in before overtime is incurred. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm · retrieved 2026-08-02

labor-break-compliance-by-state differentiator

Break Rules are configurable and assignable to locations, alongside Work Hour Restrictions, Store Work Hours and Configuring Compliance with Wage and Tip Laws. Oracle ships no per-US-state prebuilt jurisdiction rule set, and break attestation and premium-pay flagging are not documented. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm · retrieved 2026-08-02

labor-fair-workweek-support

Checked the Labor Management User Guide contents (docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm) and opened t_schedule_edit_restrictions.htm, which turns out to be only 'restriction percentages for the roles that can edit schedules', i.e. a cap on the labour-cost change a role may make - not an advance-notice window. The scheduling chapter enumerates Creating Schedule Profiles, Creating/Editing/Submitting/Approving/Printing/Emailing Schedules and the Schedule Approval Process, and Employee Self Service adds only Request Time Off and Request Shift Changes; none carries a publish deadline, a predictability-pay premium, or a rest-between-shifts (clopening) rule. The Labor Management Scheduler RESTful API guide (back-office/20.1/lmsch) is published as a PDF I could not text-extract, so an advance-notice field exposed only through the Advanced Scheduler API remains unchecked - which is why this is unknown rather than no.

labor-minor-labor-rules

Labor Management documents "Configuring Compliance with Child Labor Laws" as a dedicated organisation-level configuration topic, alongside Work Hour Restrictions assignable per location. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm · retrieved 2026-08-02

labor-tip-pooling-rules

Both models are documented with their own configuration procedures: Manual Tip Pools (configuring tip pooling, entering a manual tip pool amount) and Automatic Tip Pools (automatic tip pool collection, configuring automatic tip pooling). https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm · retrieved 2026-08-02

labor-tip-distribution-audit-trail

Tips are reportable in detail — Tips reports, All Checks with Charged Tips, Adjusted Time Cards, Time Card Adjustment Details and Time Card Adjustments for an Employee — and Labor Management ships configurable reason codes. A dedicated immutable tip-distribution ledger showing the pooled-to-distributed chain per employee is not documented. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

labor-qualified-tips-w2-reporting differentiator

Opened lmusg/t_config_org_pay.htm (Configuring Payroll Preprocessing Behavior and Overtime Labels): the entire option set is Hide Indirect Tips Prompt, Hide Cash Tips Prompt, Allocate Overtime to Away Store, Delay Labor Aggregation After Adjustment, the three overtime labels, and Show terminated employees in Other Pay. Simphony does separate declared cash tips from indirect tips at the time card, and rause/t_add_lm_details.htm carries an External Payroll ID, but no Treasury tipped-occupation code, W-2 Box 12 code TP or Box 14b field appears on any retrievable page, and Oracle publishes nothing dated to tax year 2026 on this. The Labor Management API Programmer's Guide is PDF-only (back-office/20.1/lmapi/E90995_32.pdf) and did not text-extract for me, so the payroll export schema itself is unverified - hence unknown, not no.

labor-native-payroll differentiator

Labor Management stops at Payroll Preprocessing, time card adjustment and closing/reopening pay periods — the documented output is a payroll hand-off. Oracle Food and Beverage does not file payroll taxes or run direct deposit as a first-party product. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm · retrieved 2026-08-02

labor-payroll-export-formats

"Using Payroll Preprocessing" and pay-period close are documented and a Labor Management API Programmer's Guide and Scheduler RESTful API guide are published. No named major US payroll provider format is documented by Oracle. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm · retrieved 2026-08-02

labor-shift-swap-workflow differentiator

Employee Self Service supports peer-to-peer shift handoff with approval: select the shift, Request Change, then either Change Start Time or "Send to another Employee"; the recipient chooses Accept Request or Reject Request, and a separate Approving Shift Change Requests procedure covers the manager step. Shortfalls: no open-shift claim board (the shift must be sent to a named employee), no documented overtime or job/role eligibility enforcement at request or approval time, and it runs inside Reporting and Analytics rather than a self-service mobile app. https://docs.oracle.com/cd/E80526_01/doc.91/e82051/t_ess_request_change.htm · retrieved 2026-08-02 adversarially verified

labor-digital-onboarding-i9

Specify Employment Details in Reporting and Analytics People Management includes an I9 Information page for employment eligibility verification, an Exemptions page for tax exemption information, plus SSN/Confirm SSN, Date of Birth, External Payroll ID, Work Permit Number and expiration, Age Certificate Number and expiration, a Payroll Information page with direct deposit bank account details, and a Veteran Status page. Shortfalls: these are fields an administrator keys into the employee record - no W-4 is collected, no document upload or e-signature and no employee-facing new-hire flow appears anywhere in the People Management chapter (Add a Person captures only Name, User Name, Email Address, Enterprise Role and Enterprise Level), and no E-Verify submission is documented. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/t_add_lm_details.htm · retrieved 2026-08-08

labor-server-performance-metrics differentiator

Reporting ships Employee Productivity, Employee Financial and Employee Financial Detail, Employee Sales Mix and Employee Sales Mix Detail, Employee Exceptions and Employee Threshold Exceptions — average check, category sales mix and void/comp exposure per employee. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

inventory-recipe-bom-costing

Recipes are a first-class module: creating recipes, editing ingredients, scaling recipes, search/replace ingredients across recipes, Weighed Stock Depletion, plus configurable global Costing Methods. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-unit-conversion-yields

Master data documents Units and Production Units with base unit names configurable, and Yield Management is its own module (creating yields by list or blank, viewing yields) alongside Preparation and Thaw Pull statistics. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-theoretical-vs-actual differentiator

Menu Item Linking ties POS items to recipes, Booking Sales posts POS sales (and unbooked POS waste checks) against those links to produce theoretical usage, and "Generating Inventory Variance Report" compares that to counted stock. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02 adversarially verified

inventory-realtime-depletion differentiator

Depletion is present and modifier-aware — Menu Item Linking links items, recipes and order types and supports negative quantities — but it runs through a Booking Sales process by cost center and period, with a documented view of "Cost Centers With Missing Sales". Nothing documents decrement at fire time. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-86-auto-sync differentiator

Adjusting Menu Item Availability: a manager presses the Menu Item Availability key, enables Out Of Menu Item to stop an item selling, or enables Check Menu Item Availability and enters a Count Available - 'The count is reduced each time the menu item is ordered', and at zero the operator gets 'No more <menu item definition name> remaining'. Shortfalls: the count is keyed manually and Managing Menu Item Availability in the configuration guide enumerates only three availability methods (Core, Disable, Menu Item Master Effectivity Group), none linked to a recipe ingredient or to Inventory Management stock; Inventory Management's own contents offer Forecast Out of Stock as a report only; and no propagation of an 86 to online ordering or to third-party delivery menus is documented. https://docs.oracle.com/en/industries/food-beverage/simphony/simmu/t_manager_procedures_adjust_mi_availability.htm · retrieved 2026-08-08

inventory-count-modes

Counts can be created by cycle, by list or blank; Count Cycles are configurable with templates, assigned cost centers and item lists; counts can be frozen/unfrozen, booked/unbooked and cancelled, with a variance report. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-mobile-count-offline

Oracle publishes Inventory Management Mobile Solutions with its own configuration guide and dedicated user/role rights tables. Offline counting with sync-on-reconnect is not documented. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-vendor-catalogs-edi differentiator

A real electronic procurement path is documented: B2B Solutions loads vendor item catalogs and order cycles, links vendor purchase items, accepts price variances, and vendor master data carries B2B settings and FTP configuration, with Central Ordering for B2B orders. No named broadline distributor (Sysco, US Foods, PFG) appears anywhere in the documentation, so the pre-built-integration half of the claim is unevidenced. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-invoice-ocr differentiator

The Invoice Settings reference lists the entire configurable invoice surface - Automatic Rounding of Invoice, Return to Create New Page, Force Invoice Value, Maximum Deviation %, Maximum Deviation, Result Set Quantity - and none concerns scanning, OCR or document capture. The Invoicing chapter itself contains exactly four procedures: Creating an Invoice by Receipt, Creating a Blank Invoice, Viewing an Invoice, Sending an Approved Invoice to Accounts Payable. Oracle's documented way to avoid manual line entry is instead structured B2B exchange - 'Loading Item Catalogs, Order Cycles, and Invoices to a Vendor' over vendor B2B/FTP settings - which requires a participating vendor feed rather than a photo, PDF or emailed document. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/r_maintenance_invoice_settings.htm · retrieved 2026-08-08

inventory-price-change-alerts differentiator

B2B Solutions documents "Accepting Price Variances" as an explicit receiving step, so a received price differing from catalogue is surfaced for action. Per-item price history across invoices and a configurable alert threshold are not documented. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-par-auto-suggest differentiator

Orders can be created "by suggested quantity", and Order Calculation plus Order Calculation Lookup are configurable modules with Order Cycles and Count Cycles behind them. No par-level object appears anywhere in the Inventory Management contents, and no forecast-driven suggestion mode is documented — Forecast Out of Stock is a separate viewing screen. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-waste-logging

Waste is a documented module with waste documents created by list or blank, Waste Lists, Waste Settings, Waste Over Groups and Waste Groups in master data, and configurable Reason Codes with ratings; POS waste checks are booked into it. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-transfers

Three documented transfer surfaces: Issue Requests with a request/transfer process, Transfers with a requisition process and accept/decline, and Transfer To/From, all governed by Cost Center Areas that configure which cost centers may transfer or request. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-commissary

The commissary model is documented end to end: a Production module creates production runs from lists, recipes can be added to issue requests and transfers, inventory moves between cost centers, and a configurable global Costing Method values the movement. Master Cost Centers propagate menu item links to member cost centers. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-lot-traceability

No lot or batch field appears in the Inventory Management item master (Edit Item, Item Description, Production, HACCP, Order Qty Calculation, Categories, Nutrients, Other Settings) or in the Blank Receipt procedure, whose captured values are Vendor, Receipt number, Delivery Date, Reference, and per line Cost Center and quantity, and the guide's contents list no recall or trace function. But the item page states only 'enter information in the following fields' and claims no completeness, and its HACCP tab is documented as a single HACCP Required checkbox with the remaining HACCP configuration deferred to the Cost Centers module, which is not published in the same enumeration. The lot-processing documentation Oracle does publish belongs to other Oracle products (WMS, JD Edwards, EBS), not MICROS Inventory Management. Undetermined rather than absent. adversarially verified

inventory-shelf-life-expiry

Read the complete Inventory Management User Guide contents (26 chapters at back-office/20.1/invug/toc.htm): the only date-adjacent functions are Preparation and Thaw Pull statistics and Forecast Out of Stock, and there is no expiring-soon report anywhere. The item master (t_masterdata_create_item.htm) has Thaw Time and Lead Days on the Production tab and no shelf-life, expiry or use-by field on the Edit Item tab, and Item Settings (r_maintenance_item_settings.htm) contains only the two default weight-factor options. The gap in my check is the item master's HACCP tab, whose only documented control is 'HACCP Required' with its own fields unpublished - a shelf-life date could sit there - so this stays unknown rather than no.

inventory-bar-partial-bottle

A "Weighed Stock Depletion" topic is documented under Recipes, which is the primitive weight-based depletion needs. Bar-specific partial-bottle counting by fraction, and integration with a counting scale, are not documented. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-cogs-gl-export

Two of the claim's three legs are documented; the third is not. GL account mapping per item category IS configurable and this record previously denied it: Master Data > Account Classes "enables you to organize item groups together in preparation for a Back Office export" (c_masterdata_acc_classes.htm), and creating one means "enter account numbers for the item groups in as many accounting departments as necessary. The four accounting department are Inventory, Expense, COS, and Accruals" - a per-item-group cost-of-sales account number, with Account Classes then assignable to cost centers. AP invoice detail does leave the system: "When an approved invoice is sent to AP, it is added to the system export file. You can no longer edit the invoice" (t_invoicing_send_approved_invoice_to_ap.htm), and Maintenance > Settings exposes a Maximum Number of Days for Daily Totals Export and a Maximum Number of Days for Menu Item Cost Export (t_config_export_inv_totals.htm), the latter being the period item-cost feed. Shortfall: no named accounting system's import format. The only export-format construct in the 26-chapter Inventory Management guide is Interface Definition - "Interface definitions are custom templates that define the format for exported data" (c_maintenance_interface_definition.htm), i.e. the operator authors the layout, and the guide's contents name no accounting package anywhere. Oracle's own NetSuite Connector for Simphony does not close this gap: its announced payload is POS financial data (tender by tender name, carry-over amounts, dayparts, totals, items sold, service charges, discounts) and names no accounts-payable, COGS, general-ledger or journal-entry content. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/t_masterdata_create_accnt_class.htm · retrieved 2026-08-08 adversarially verified

inventory-native-not-partner differentiator

Oracle Hospitality Inventory Management is a first-party Oracle module with its own 26-chapter user guide, master data, user/role rights model and web service APIs, published inside the Simphony documentation set. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

inventory-menu-margin-linkage differentiator

Reporting ships a Menu Engineering report and Cost of Goods Sold reports alongside Average Price by Item Group and Menu Item Affinity, so per-item margin analysis is a shipped report. An automatic contribution-margin threshold alert is not documented. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

reporting-realtime-dashboard

Reporting and Analytics Advanced Cloud Service is a restricted-use inclusion in both Simphony Premium (B81480) and Standard (B84711) Cloud Service, and Oracle ships InMotion Mobile for off-premise access. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02

reporting-eod-closeout

Daily Operations and Daily Operations Summary reports ship in four variants each (TSR/QSR x add-on/inclusive tax), alongside System Financial, Income Audit by Tender, Tender Media and Open Checks. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

reporting-pmix-modifier-level

Sales Mix, Menu Item Sales, Top Menu Items Summary and Order Channel Sales Mix are all published in add-on and inclusive-tax variants. No report in the reference guide is described at condiment or modifier level, so the modifier half of the claim is unevidenced. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

reporting-comps-voids-audit

Voided Menu Items, Employee Exceptions, Employee Threshold Exceptions, Adjustments-Voids, Adjustments-Returns, Adjustments-Cancels, Adjustments-Error Corrects, All Checks with Manager Voids, Unacknowledged Adjustments and Check Journal, plus a "Voids vs. Returns" definition topic. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

reporting-cash-over-short

Enterprise Cash Management is a documented module tracking cash into, within and out of the property across tills, safes, server banks and bank deposits, with count sheets, receptacles, threshold sets, deposit reconciliation and variance analysis. The shortfall is the report itself: no cash over/short report per drawer, per shift and per employee appears in the Reports Reference Guide contents. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_ecm.htm · retrieved 2026-08-02

reporting-labor-productivity

Labor Summary, Employee Productivity (TSR and QSR variants), Time Card Detail and Time Card Summary reports post clocked hours and labour cost against POS sales. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

reporting-server-scorecards differentiator

The component metrics all exist as separate reports — Employee Productivity, Employee Sales Mix and Sales Mix Detail, Employee Financial, Tips, Employee Exceptions. No single per-server scorecard combining average check, items per check, attachment rate for named categories and tips as a percentage of sales is published. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

reporting-channel-profitability differentiator

Order Channel Sales and Operations, Order Channel Sales Mix, Order Channel Employee Sales and All Checks for an Order Channel report revenue and operations by channel in TSR/QSR and tax variants. Margin net of marketplace commission is not a documented report. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

reporting-multiloc-drilldown differentiator

Side-by-side comparison is fully shipped: eight Daily Operations Location Comparison and Revenue Center Comparison variants, alongside Check Detail, Check Journal and Customer Check View. The shortfall is the drill path — the only drill-down Oracle documents is organizational ("drill down the organizational levels", with the worked example stopping at "a comparison of sales at the district and location levels"). Drill-through from a group total into an individual check is not documented; check-level reports are separate report objects. https://docs.oracle.com/cd/E71871_01/doc.90/e72023/c_reports_analysis_examples.htm · retrieved 2026-08-02 adversarially verified

reporting-custom-report-builder differentiator

Oracle publishes a "Restaurants Reporting and Analytics Report Designer's Guide" (Release 20.x, F30460-10, April 2025), so a report designer exists as a shipped, documented component. The guide body renders client-side and only the title page was retrievable, so whether it is genuinely non-developer self-service is unverified. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rardg/index.html · retrieved 2026-08-02

reporting-scheduled-delivery

Scheduling primitives are documented but not for Reporting and Analytics: Inventory Management ships a Scheduler with configurable jobs and an executed-jobs view, and Labor Management documents sending schedules by email. No scheduled recurring delivery of a Reporting and Analytics report to a recipient list is documented. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm · retrieved 2026-08-02

reporting-raw-warehouse-export differentiator

Oracle publishes two relevant guides — an Enterprise Back Office Standard Export User Guide and a Database Access Cloud Service Reference Guide, the latter being a separately named cloud service implying direct database access to your own data. Both are PDFs whose text did not extract on retrieval, so the destination, cadence and whether the access is push or pull remain unverified. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/dacsr/index.html · retrieved 2026-08-02

reporting-public-api differentiator

Read-only Business Intelligence is bundled, but everything else is metered: Configuration Data Interface (B87077) and every Transaction Services variant (B81485, B3737, B83738, B90422, B90423, B90424) are separately licensed add-ons requiring Premium or Standard. The documentation is open; the surface is not. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02

reporting-webhooks differentiator

STS Gen2 pushes Organizations, Configuration, Check and Employees notifications, but Oracle documents a 15-second timeout "with no retry", restricts the subscriber TLD set, and documents no payload signature. https://docs.oracle.com/en/industries/food-beverage/simphony/stsgg/api-notifications-api-webhook.html · retrieved 2026-08-02

reporting-api-not-upcharged differentiator

Configuration Data Interface Cloud Service (B87077) "Grants access to the Configuration Data Interface API for direct integrations" and requires Premium or Standard Cloud Service as a prerequisite. Transaction Services is separately licensed at every tier as well. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02

reporting-tier-paywall differentiator

The Simphony Essentials licensing page states Essentials includes Oracle Hospitality Reporting and Analytics Advanced Cloud Service (restricted-use) and Labor Management (restricted-use) — the same bundle Premium and Standard carry. Above-store reporting is not paywalled at any tier. https://docs.oracle.com/en/industries/food-beverage/simphony-essentials/ssllg/c_lic_simphony.htm · retrieved 2026-08-02

reporting-history-retention differentiator

Oracle publishes the numbers, which almost no POS vendor does: transaction and KDS detail is retained 3 months by default and can be increased to 36; daily and fixed-period totals 13 months default, 48 maximum; transaction journal records and time cards 13 months default, 120 maximum. It falls short of the claim because the DEFAULT detail window is 3 months, well under 24, and Oracle does not state whether raising it is free. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/c_data_retention_limits.htm · retrieved 2026-08-02

reporting-anomaly-alerts differentiator

The InMotion Mobile app ships eleven alerts - Discount % is too high, Labor % is too high, Void count is too high, No Sale count is too high, Cancelled Check count is too high, Return % is too high, Reopened Check count is too high, Credit Cards did not settle, Employee about to enter overtime, Employee is in overtime, Posting exception - triggered when the metric runs 50% higher than the average of the past six weeks and delivered as a push notification to all users for the location. Shortfalls: the alert list and the 50%-over-six-week-average threshold are fixed, with no operator-configured metric or threshold documented; delivery is push to the mobile app only (Reporting and Analytics itself offers Scheduled Reports for email and Export Status Notifications, neither of which is conditional); and sales-below-forecast is not among the alerts. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/inmqr/c_alerts.htm · retrieved 2026-08-08

reporting-nl-query

Oracle's 18 March 2026 Simphony Smart Assistant announcement describes only support and SOP troubleshooting ('common technical and operational issues', example questions about printers and logins) - it is silent on ad-hoc analytics rather than evidence against it. The other leg was the Reporting and Analytics user guide contents (Reports, Dashboards, report editors, subject areas, Excel iQuery, Audit & Analysis), a table of contents that asserts no completeness. Oracle Analytics shipped a natural-language AI Assistant and AI Data Agents in its 2026 updates and Simphony Reporting and Analytics is an Oracle analytics tenant, so whether an NL query surface is available to a Simphony operator is undetermined. adversarially verified

reporting-guest-cohorts differentiator

Guests, Processed Customer Transactions and Customer Check View reports exist, and Gift and Loyalty tracks visits and spend per account. New-versus-returning and lifetime-spend cohort reporting is not published. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

reporting-sales-forecast differentiator

A first-party Forecasting and Budget module exists and feeds Labor Management staffing calculations, and four Budget and Forecast Metrics Comparison reports ship in TSR/QSR and tax variants. The shortfall: what Oracle documents is "Manual Forecasts" and "Generating a Manual Forecast" seeded by "Historical Seed Data", i.e. an operator-generated forecast primed from the location's history rather than a system-produced one, and no daypart or hourly forecast granularity is documented. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/fbuse/toc.htm · retrieved 2026-08-02 adversarially verified

reporting-tip-tax-compliance

Tips reports, All Checks with Charged Tips and Tips and Service Charge Metrics definitions are published, and Labor Management handles tip credit and wage/tip law configuration. A declared-versus-charged tip shortfall report and a jurisdictional tip tax liability summary are not documented. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

multi-location-org-hierarchy

Hierarchy is chapter 4 of the configuration guide and Enterprise > Property > Revenue Center > Zone is the object model configuration, reporting and privileges all scope to. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

multi-location-central-menu-publish

Menu Items, Menu Levels and Effectivity Groups are authored in EMC above the store and inherit downward through the hierarchy; Importing and Exporting Data is a separate documented chapter. A publish history showing what was pushed, when and by whom is not documented separately from the Audit Trail. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

multi-location-local-override-policy differentiator

Menu Item Field Security: "all of the fields within these files have Editable, View Only, and Exclude privileges available for configuration. By default, all of the field access levels are set to Editable." Configured per employee role on the Roles module Fields tab across MI Master, MI Definition and MI Prices — corporate can leave price editable at store level while locking name or recipe fields to View Only or Exclude. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_employee_roles_field_level_access.htm · retrieved 2026-08-02 adversarially verified

multi-location-price-zones

The composable pieces exist: hierarchy zones, Menu Levels, price sequence levels per connector, and order channels with a documented precedence chain. No Oracle page documents a price-zone object spanning location group, channel and daypart on a single item record. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_order_channels.htm · retrieved 2026-08-02

multi-location-scheduled-publish differentiator

Effectivity Groups date-scope configuration records, so future-dated activation exists. Timezone-aware activation per target location and post-activation rollback are not documented — and a Cruise Ship Time Zone chapter exists precisely because timezone handling is a special case. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

multi-location-new-store-template differentiator

Oracle publishes a Property Device Configuration Guide, a Client Deployment Guide and a Location Upgrade Guide, and property cloning is standard EMC practice. No expected time-to-open or documented new-store template object was found. https://docs.oracle.com/en/industries/food-beverage/simphony/ · retrieved 2026-08-02

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

Organizational Hierarchies: 'The enterprise has only one organizational hierarchy... The hierarchy ensures totals from all locations are available for reports', built so that 'you only have a single level that represents the enterprise or corporation and all other levels and locations are linked underneath it', and access is scoped by role against a level so 'the District Manager can only see information for those locations and cannot see information for the locations related to the other districts'. Corporate enforcement of config is real: Core menu items are those 'that the corporate office or franchisor requires to be sold' and cannot be disabled by Effectivity Groups. Shortfall: there is no separate franchisee tenant - people are created centrally in Reporting and Analytics People Management under the one enterprise, and no documented boundary gives a franchisee ownership of its own employee records, banking or labour data while corporate retains sales visibility. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_org_hierarchy.htm · retrieved 2026-08-08

multi-location-royalty-calculation differentiator

Checked the complete Reporting and Analytics User Guide contents (back-office/20.1/rause/toc.htm, including its subject-area list: daily aggregate, quarter-hour, transactions, common currency, labor, inventory, gift and loyalty, other), the Reports Reference Guide contents (rarrg/toc.htm) and the Inventory Management contents (invug/toc.htm). Nothing calculates a royalty percentage, an advertising-fund accrual or a franchisee statement, and the only franchisor construct I found is the Core menu item designation in simcg. What I cannot do is turn that into a factual assertion: no Oracle page enumerates the financial calculations Simphony performs and declares the list closed, and oracle.com's franchise and product pages return 403 to automated retrieval, so a franchise module sold outside the documented back office cannot be excluded.

multi-location-royalty-collection

Checked Reporting and Analytics (rause/toc.htm - Export Configurations, Delivery Profiles and Export Schedules deliver files, not debits), Inventory Management (invug/toc.htm - invoices go to Accounts Payable through custom export templates) and the Oracle Restaurants payments documentation (payments-platform/latest/config.html and pcsrf/toc.htm), whose account-holder banking details serve card settlement to the merchant, not fee collection from a franchisee. No ACH or debit collection of franchise fees and no franchisee-visible fee statement appears in any of them. Since Simphony documents no royalty calculation upstream of this either, and oracle.com is 403 to automated retrieval, I am leaving this unresolved rather than asserting absence.

multi-location-consolidated-reporting

Daily Operations Location Comparison reports in four variants sit over the enterprise hierarchy, and Inventory reporting spans cost centers across locations. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm · retrieved 2026-08-02

multi-location-normalized-item-rollup differentiator

Enterprise-level menu item records inherit to properties, which is the mechanism for rollup under a shared corporate identifier, and Inventory Management adds Master Cost Centers that copy menu item links to members. What happens to the rollup when a store renames or re-prices locally is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

multi-location-cross-location-giftcard

Gift card issue, activate, reload, transfer balance, redeem and cash out are POS operations against enterprise-wide Gift and Loyalty accounts. https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm · retrieved 2026-08-02

multi-location-cross-location-loyalty

Loyalty programs are defined as rules governing a group of accounts across the enterprise and are reported centrally; the POS guide documents transferring a points balance between accounts. https://docs.oracle.com/en/industries/food-beverage/simphony/19.3/simcg/c_loyalty_gift_programs.htm · retrieved 2026-08-02

multi-location-multi-brand differentiator

Multiple revenue centers with distinct menus, order channels and separately reportable revenue on shared hardware is the native model, and Order Channel reporting separates virtual-brand volume. Distinct receipt branding per virtual brand is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

multi-location-multi-tax-jurisdiction

Taxes is a dedicated configuration chapter including surcharges, Inventory master data carries its own Taxes and Fiscal Fields, and Oracle ships a Fiscal Interface Cloud Service (B83739) plus country-specific fiscal documentation such as the Spanish VERIFACTU declaration. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

multi-location-multi-currency-locale

Currency (chapter 9) and Languages (chapter 8) are first-class configuration chapters, the POS guide documents printing guest receipts in multiple languages, and Inventory master data carries Foreign Currency with vendor linkage and Master Data Translation. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

multi-location-config-audit-log differentiator

Audit Trail records "all changes, additions, and deletions made in the EMC and PMC Procedures", plus EMC sign-in successes and failures, report activity, Key Manager activity, credit card module activity and DbProcs activity, and is queryable via documented search parameters and results. Two shortfalls against the claim: Oracle documents Audit Trail Purging as an administrative operation, so the log is not immutable; and no export path for the audit log is documented. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_audit_trail.htm · retrieved 2026-08-02 adversarially verified

multi-location-enterprise-sso differentiator

SSO prerequisites: 'You must provide your own IdP', 'You must provide your own OCI IAM identity domain', Simphony 19.10+ and Reporting and Analytics 20.4+; the customer 'configure[s] federation from the OCI IAM identity domain to your existing identity provider' (six documented steps ending in Configure Federation and Bulk Update Federation Status). 'All Oracle Restaurant cloud applications (such as Reporting and Analytics, Frontline Manager, Delivery Connectors, and Oracle Restaurants Payment) support SSO.' Shortfalls: 'Simphony's Enterprise Maintenance Console (EMC) does not support SSO and requires a separate password' - so the main configuration console stays outside the IdP - local POS clients are excluded by design, Inventory Management Mobile Solutions is unsupported, SAML JIT provisioning is explicitly not supported and direct creation or management of users in the domain is prohibited (people are still created in Reporting and Analytics People Management), so there is no SCIM-equivalent automated deprovisioning path. The protocol is never named beyond OCI IAM federation. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_prereqs.htm · retrieved 2026-08-08

multi-location-enterprise-api differentiator

The enterprise integration path is Transaction Services, which is licensed per revenue center in several of its variants (B3737, B90423, B90424) — so a single enterprise credential can itself be metered by location. Licence-free enterprise-wide API access is not documented. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02

multi-location-central-labor-policy

Labor rules are authored above the store and assigned down: "Assigning Work Hour Restrictions and Setting Store Hours", "Assigning Break Rules to Locations", "Assigning Store Work Hours to a Location", plus organisation-level child labour and wage/tip law configuration. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm · retrieved 2026-08-02

hardware-commodity-devices differentiator

Android and Windows service hosts exist and Oracle publishes a Client Deployment Guide, so non-Oracle Android and Windows devices are technically in scope. Oracle documents no supported third-party terminal or tablet SKU and sells its own Workstation and Tablet 700 lines, and technicians on operator forums recommend replacing the Oracle tablets with third-party hardware rather than treating them as interchangeable. https://docs.oracle.com/en/industries/food-beverage/simphony/19.3/simcg/t_workstation_android_service_host_apk_upgrade_downgrade.htm · retrieved 2026-08-02

hardware-os-platforms

Oracle publishes a Client Deployment Guide, a Property Device Configuration Guide and an Oracle Linux for MICROS Integrators Reference Guide, together naming the supported client platforms (Windows, Android, Oracle Linux for MICROS). https://docs.oracle.com/en/industries/food-beverage/simphony/ · retrieved 2026-08-02

hardware-handheld-purpose-built

MICROS Tablet 700 series (720/721/721P/722P) are purpose-built rugged 7-inch tablets with integrated magnetic stripe reader, over-moulded corners, tether points and optically bonded touch. No published drop-height or IP ingress rating was found. https://docs.oracle.com/en/industries/food-beverage/micros-tablet-700-series/latest/tabss/c_tablet_technical_specifications.htm · retrieved 2026-08-02

hardware-handheld-battery-swap differentiator

Technical specifications state a replaceable rechargeable Li-ion battery (3.6V, 8800mAh) plus a 240mAh backup bridge battery — the bridge cell is what makes an undocked hot swap real rather than nominal. https://docs.oracle.com/en/industries/food-beverage/micros-tablet-700-series/latest/tabss/c_tablet_technical_specifications.htm · retrieved 2026-08-02

hardware-handheld-lte

The Tablet 700 series technical specifications affirmatively enumerate connectivity as Wi-Fi and Bluetooth across 720/721/721P/722P with no cellular or LTE option. This is a documented absence, not a gap in my search. https://docs.oracle.com/en/industries/food-beverage/micros-tablet-700-series/latest/tabss/c_tablet_technical_specifications.htm · retrieved 2026-08-02

hardware-offline-mode

Yellow and red offline modes with a local DataStore and automatic replay are documented, and offline financial reports name the fields they omit. Oracle publishes no complete degrade matrix covering card authorisation, loyalty and refunds. https://docs.oracle.com/en/industries/food-beverage/simphony/19.4/sipou/c_workstation_online_offline_modes.htm · retrieved 2026-08-02

hardware-kds

First-party KDS with its own Cloud Service SKU (B81484, required per KDS client), a KDS Controller with backup controller support, bump bars, production lanes and expo-style displays — note the SKU is required "even if the customer is using a non-Oracle KDS client solution". https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02

hardware-kiosk differentiator

A first-party Simphony Kiosk plug-in and a dedicated Kiosks configuration chapter exist, and Oracle sells kiosk hardware. Countertop versus freestanding form factors, unattended EMV and ADA conformance are not documented in retrievable sources. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-08-02

hardware-drive-thru

Drive-thru is a documented order channel assignable to workstations and order types, and Oracle documents an Order Confirmation Board integration. Menu boards, speaker/headset integration and a documented timer methodology were not found. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_order_channels.htm · retrieved 2026-08-02

hardware-printer-compatibility

The Label Printing plug-in (19.7.1.1) names Bixolon and Epson printers explicitly, the Dynamic Barcode plug-in prints QR, EAN-13 and Code 128 through order devices, and Oracle publishes Printers, Logo Printing and Banquet Guest Check Printing configuration chapters. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-08-02

hardware-peripherals

Cash drawers, printers and barcode peripherals are documented (chapter 29 Printers, a Peripherals-Barcode topic, and the Check Pickup Via Barcode plug-in reading QR codes). Scales and customer-facing displays are not evidenced by any consolidated compatibility matrix I could retrieve. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

hardware-p2pe-terminal

OPI drives PCI PTS payment terminals belonging to the merchant's PSP so PAN does not transit the POS application, and Oracle publishes PA-DSS 3.2 implementation guidance. Oracle does not state the merchant's resulting SAQ type and lists no PCI-validated P2PE solution for Simphony. https://docs.oracle.com/cd/E76065_01/doc.29/e69884.pdf · retrieved 2026-08-02

hardware-tap-to-phone differentiator

Read the Oracle Restaurants Payment Service feature reference contents (payments-platform/latest/pcsrf/toc.htm - authorization, incremental authorization, adjust closed check, manual authorization, refunds, disputes, payment reports and reconciliation) and the payments Initial Setup guide (payments-platform/latest/config.html), whose seventh step is 'set up and activate the payments terminal', a physical unit unpacked, cabled and activated by a call to Oracle Support. Neither names Tap to Pay on iPhone, Tap to Pay on Android or SoftPOS, and the configuration guide's peripheral and payment-device chapters (simcg c_peripherals.htm, c_payments_spi.htm, c_payments_opi.htm, c_properties_android_payments.htm) describe reader-attached flows. Neither book claims to enumerate every acceptance method, and oracle.com product and press pages return 403 to automated retrieval, so absence is not established.

hardware-pricing-transparency differentiator

READ DIRECTLY THIS TIME — the 403 the earlier note admitted to was wrong, and the value survives anyway on better evidence. Every current-generation SKU page opens to us (Workstation 6 62,125 bytes, Workstation 3 59,672, Workstation 8 55,692, MICROS Tablet 62,552, hardware index 49,758; all HTTP 200). None carries a list price. The index page answers the question outright: 'What will my restaurant POS system cost? Our product experts can help you build a package that works best for business and budget. Get in touch, and we can help you calculate your total cost of ownership' under a 'Get my free consultation and quote' button. Workstation 8 says only 'Request a quote'; the Tablet page names no figure at all. Workstations 6 and 3 do carry a dollar figure — 'Get a Workstation 6 for US$1', 'Best-in-class POS terminal for US$1, no strings attached' — but it is a conditional switching promotion, not a SKU price: it is contingent on 'switching to Simphony, our cloud-based restaurant management platform' and is obtained by 'Talk to an Oracle product expert'. The hardware cost is folded into the subscription, whose price Oracle also does not publish, so a US$1 headline moves the buyer further from a cost estimate rather than closer. Oracle's own price-list trees (/us/corporate/pricing/, /a/ocom/docs/corporate/pricing/) are Disallow'd to ClaudeBot in www.oracle.com/robots.txt and were not fetched. `no` is positive evidence of absence in the vendor's own words, not an absence of evidence. https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-hardware/ · retrieved 2026-08-12 adversarially verified

hardware-ownership-vs-lease differentiator

RESOLVED OFF unknown/F, AND THE PREMISE THAT HELD IT THERE WAS FALSE. The prior rationale said "www.oracle.com returns 403 to automated retrieval" and that the warranty PDF "also returned 403". Measured 2026-08-13 as the checker (POSAtlasBot): seven www.oracle.com pages answered HTTP 200, and https://www.oracle.com/a/ocom/docs/dc/hardware-warranty-policy.pdf answers 404, not 403 -- a deletion, not a refusal. The 403 is real only for the ClaudeBot-family research client, which is walled host-wide including /robots.txt; every rationale in this cluster was written by that client. See workflows/block-premise-audit.mjs. ORACLE STATES THE ACQUISITION MODEL IS A SALE. Oracle Hardware and Systems Support Policies (07-Aug-2026, HTTP 200, 474,831 bytes, application/pdf) defines the covered equipment as "point of service products manufactured by or for Oracle and sold by Oracle (either directly or by an Oracle-authorized distributor) (\"hardware system\")", and speaks throughout of the customer's own purchase: "Components and options purchased separately from Oracle from your original equipment purchase are included in the definition of hardware system for the purposes of determining the technical support fee", and "If technical support lapses or was not originally purchased with your hardware system, a reinstatement". It also contemplates the customer moving the equipment at will -- "For Oracle to provide technical support for hardware relocated outside the original country of delivery, notice of hardware relocation is required" -- which a lease or subscription rental does not. All four verified byte-exact against the extracted text under scripts/lib/quotes.mjs normalize(). WHY partial AND NOT yes: the claim asks the vendor to state outright purchase AS AN ALTERNATIVE TO a mandatory lease. Oracle nowhere mentions a lease, and no transfer-of-title or risk-of-loss clause was retrieved. That clause lives in the Oracle Master Agreement under /corporate/contracts/, which `*` Disallows -- so it is barred to the checker and 403 to the agent that robots permits there by name. Marketing corroborates the direction but cannot carry the claim: the current offer is a $1 price tag ("Best-in-class POS terminal for US$1, no strings attached"), which is a sale price, not a rental. https://www.oracle.com/contracts/docs/hardware-systems-support-policies-069182.pdf · retrieved 2026-08-13

hardware-usable-after-churn differentiator

STILL unknown, but the barrier it was resting on was measured and is not there. The prior rationale said Oracle's contractual pages and the hardware warranty PDF "return 403 to automated retrieval". Measured 2026-08-13 as the checker: www.oracle.com answers HTTP 200 (the apex oracle.com does 403 -- a distinction the old prose elided), and the warranty PDF is 404. The 403 is real only for the ClaudeBot-family client. So this stays unknown on the EVIDENCE, not on the wall. What was read this session: the Oracle Hardware and Systems Support Policies (07-Aug-2026, 474,831 bytes, read in full as text) establishes that the customer purchases and may relocate the equipment, but says nothing about whether it remains usable with third-party software once a Simphony subscription ends -- it governs support entitlement, not post-termination use. Naming the corpus: that one policy document plus the Simphony documentation index previously checked. It is NOT the whole of Oracle's published terms. The document that would settle it is the Oracle Master Agreement under www.oracle.com/corporate/contracts/, which `*` Disallows -- barred to the checker, and 403 to the research client that robots permits there by name. Neither may be worked around.

hardware-rma-sla differentiator

RESOLVED OFF unknown/F BY A DOCUMENT THIS RECORD ALREADY CITED. The prior rationale said the Oracle hardware warranty policy was "tried directly ... HTTP 403". Two errors: that URL is 404 (the document has been withdrawn, which is evidence about Oracle, not about us), and the answer was never there -- it is in the Oracle Hardware and Systems Support Policies PDF that this same record already cites at grade A under reliability-hardware-replacement-sla. Same shape as the reliability-contractual-uptime-sla correction: the figure is published, just not where the researcher looked. Re-fetched and verified first-hand 2026-08-13 (HTTP 200, 474,831 bytes): "Oracle Advanced Parts Exchange for Oracle Point of Service Hardware consists of:" / "Assistance with service request 24 hours per day, 7 days a week" / "Next business day parts exchange" / "Non-technical customer service during normal business hours". The programme is named for this hardware specifically -- "Oracle Advanced Parts Exchange for MICROS Hardware has been renamed to Oracle Advanced Parts Exchange for Oracle Point of Service Hardware". WHY partial AND NOT yes: the claim wants a warranty TERM as well as an exchange turnaround. The turnaround is verified above; the term lives in a separate Oracle Hardware Warranty document which I did NOT retrieve this session, so it is not cited here. Resolving that document is the remaining work. https://www.oracle.com/contracts/docs/hardware-systems-support-policies-069182.pdf · retrieved 2026-08-13

hardware-byod

Read the mobile-client topics in the configuration guide - Simphony POS Operations Running on Android Mobile Operating System (c_properties_android_os.htm) with its network, payments, file-editing and device-log subtopics, and 'Using Simphony POS Operations and Mobile Solution Application on One Device' - plus the Security Guide's Google Android topic and 'Running a Workstation Securely with Windows Standard Users'. All of them treat the device as a property-provisioned workstation deployed through CAL and authenticated as a device; none describes staff installing the ordering or payment app on a personally-owned handset, and none prohibits it either. The Security Guide's Android topic is written as hardening guidance rather than an ownership policy, so it does not settle the question.

hardware-remote-device-management differentiator

The Configuration and Content API exposes an Update Workstations operation, EMC surfaces workstation and CAPS online/offline state, a Remote Support plug-in (19.4.2) opens BeyondTrust sessions from Windows workstations, and the KDS guide documents a Remote Support Tool with support-session buttons. A device console with remote reboot and staged rollout is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/op-config-sim-v1-devices-updateworkstations-post.html · retrieved 2026-08-02

hardware-selfpour-scales

Opened simcg/c_scales.htm expecting a beverage interface and found the opposite: 'A scale connects to the workstation and is used for menu items that are priced by weight (for example, salad bar). You can configure Simphony to calculate weight in ounces, pounds, or kilograms' - no pour spout, flow meter or tap wall. The Peripheral Devices chapter (c_peripherals.htm) lists Coin Dispenser, Magnetic Stripe Reader, Barcode Reader, Fingerprint Scanning, Scales, Cash Drawer and the Texas Digital order confirmation board, but it introduces these as 'common POS peripheral devices' rather than an exhaustive supported-hardware table, and Simphony's extensibility surface (System Interface Module, .NET and JavaScript extensibility, Transaction Services Gen 2) is where a self-pour vendor would attach without appearing in Oracle's own contents. Absence therefore is not established.

hardware-callerid-integration

Enumerated the Configuration Guide contents (simcg/toc.htm) for peripheral and interface topics: coin dispenser, MSR, barcode reader, fingerprint, scales, cash drawer, order confirmation board, printers, SPI/OPI payment interfaces - no caller ID or telephony device, and no customer-record pop on an inbound call. The Order Information Service topics in the POS Manager guide handle delivery-agent assignment rather than call handling. The one place this could be documented is the System Interface Module Manual, which Oracle publishes only as ssimm.pdf and which did not text-extract for me, so a SIM-based caller-ID interface cannot be excluded; the peripherals chapter also describes itself as covering 'common' devices, not all supported ones.

extensibility-public-api-docs

The full REST reference for the Configuration and Content API is publicly readable on docs.oracle.com with no login, NDA or sales call, documenting OAuth2 auth, TLS 1.2, JSON messages, stateless calls and a published change history; the Transaction Services Gen2 and Business Intelligence API references are equally open. https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/index.html · retrieved 2026-08-02

extensibility-api-access-cost differentiator

Every programmatic write path carries its own part number with Premium or Standard as a stated prerequisite: Configuration Data Interface (B87077), Transaction Services Premium (B81485) and Premium per-revenue-center (B3737), Standard client (B90422) and Standard per-revenue-center (B90423), plus Guest Facing variants (B83738, B90424) whose licence text states employee-facing solutions are not permitted. The per-revenue-center variants mean API access can be metered by location, which is exactly what the claim rules out. One documented exception: B87077 is "not required for the Simphony Import Export feature", so manual file-based import/export is not upcharged. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02 adversarially verified

extensibility-partner-revshare

The Simphony documentation index enumerates the integration surface Oracle publishes - Transaction Services Gen 1 and Gen 2, Configuration and Content API, Business Intelligence API, JavaScript/HTML5/Kiosk extensibility, .NET client extension API, System Interface Module, Extensibility Compatibility Guide - and every one of them is a technical reference with no commercial terms. Oracle PartnerNetwork and the Simphony partner and integration pages live on www.oracle.com, which returns 403 to automated retrieval (already recorded for the product and pricing pages in this record), so no referral fee, revenue-share percentage or per-location partner charge was readable. I am recording that as unreachable rather than as unpublished.

extensibility-free-sandbox differentiator

Traced the documented access path: Transaction Services Gen 2 is 'provisioned by Oracle' (omsstsg2api/index.html), and credentials are created as an API account inside a live customer tenant - Reporting and Analytics, Administration, System, API Accounts, Add API Account, choosing type Simphony Transaction Services, a location authorization scope and a client scope, after which a Client ID is issued (rause/c_STSG2_API_permissions.htm); the same chapter covers Business Intelligence and Configuration and Content API accounts the same way, and no test or sandbox environment is mentioned in any of them. That establishes how a customer's integrator gets credentials, not that Oracle offers no separate developer sandbox: the Oracle developer and partner programme pages are on www.oracle.com, which 403s to automated retrieval, so I am leaving this unresolved.

extensibility-oauth-partner-apps

OAuth2 over TLS 1.2 is the documented auth mechanism with per-integration API accounts created in EMC. Operator-granted, individually revocable fine-grained scopes are not documented — the account is provisioned by an administrator, not consented to by the merchant. https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/index.html · retrieved 2026-08-02

extensibility-webhooks-push

STS Gen2 pushes Check notifications on-premise and adds Organizations, Configuration and Employees in cloud. Granular created/modified/paid/voided/refunded event types are not enumerated. https://docs.oracle.com/en/industries/food-beverage/simphony/stsgg/api-notifications-api-webhook.html · retrieved 2026-08-02

extensibility-webhook-reliability differentiator

Oracle states the subscriber timeout is 15 seconds "with no retry", documents no HMAC or payload signature, and offers no replayable event log. A missed delivery is simply lost. https://docs.oracle.com/en/industries/food-beverage/simphony/stsgg/api-notifications-api-webhook.html · retrieved 2026-08-02

extensibility-order-injection-api

Transaction Services is the order-injection API and it is separately licensed at every tier: Premium (B81485), Premium per Revenue Center (B3737), Standard (B90422), Standard per Revenue Center (B90423), plus guest-facing variants. A public REST API you must buy another SKU to post a single order through is gated, not open. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02

extensibility-menu-write-api differentiator

The Configuration and Content API reads, updates and deletes menu items and menu item classes, and covers discounts, service charges and locations — a genuine write surface, though the enabling SKU is separately licensed. https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/op-config-sim-v1-menuitems-updatemenuitemclasses-post.html · retrieved 2026-08-02 adversarially verified

extensibility-data-symmetry differentiator

Menu, discounts, locations, workstations and employees are writable through the Configuration and Content API and checks through STS Gen2, but inventory, labour and gift/loyalty each have their own older web-service APIs with different capability profiles, and Business Intelligence is read-only. https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/index.html · retrieved 2026-08-02

extensibility-published-rate-limits

Oracle publishes 9 API calls per second for Simphony Cloud Service, Single-Tenant Edition in the Configuration and Content API documentation. Throttle response behaviour and the multi-tenant limit remain unpublished. https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/find_URL.html · retrieved 2026-08-02

extensibility-doordash-preferred differentiator

DoorDash's 18 May 2026 newsroom post refreshes the Preferred Integrations Program and names the 2026 cohort in full: "Based on current performance and feature capabilities, the 2026* cohort DoorDash Preferred Integration Partners include Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, and UrbanPiper", footnoted "generated based on performance and feature sets as of May 8, 2026". Oracle, MICROS and Simphony appear nowhere in it. The roster is actively maintained rather than stale - ChowNow, named in the 2025 inaugural cohort, has dropped off. The merchant learning-centre page (merchants.doordash.com/en-us/learning-center/doordash-preferred-integrations-program) states the requirements without naming partners: at least 250 DoorDash stores on the integration, POS proactive cancel rate below 1%, merchant-avoidable cancellation rate below 1%, and eight high-quality features including self-serve onboarding, real-time menu sync, live item availability and order-ready signals. A named cohort is a genuine enumeration, so absence from it is positive evidence of absence. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-08 adversarially verified

extensibility-first-party-delivery-integrations differentiator

Vendor-owned Delivery Connectors cover DoorDash and Uber Eats/Postmates with no middleware, plus Deliveroo, Rappi and Skip The Dishes. Grubhub is absent from the supported list. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_delivery_connectors.htm · retrieved 2026-08-02

extensibility-middleware-compatibility

Deliverect states it has 'partnered with Oracle's Micros Simphony to build a reliable two-way integration' supported across the US, Canada, Australia, France, Germany, Mexico, Spain, the UK and the Middle East; ItsaCheckmate, Chowly and Otter also list Simphony. Grade E because this is the middleware vendors' own documentation, not Oracle's. https://www.deliverect.com/en-us/integrations/micros-simphony · retrieved 2026-08-02

extensibility-accounting-connectors

One vendor-maintained connector exists, to Oracle's own GL. NetSuite Connector's supported-connector chapter enumerates its targets - Amazon, eBay, Loop Returns, Magento 2, Oracle Simphony, Shopify and Square - so Simphony is a first-class first-party connector, not a partner build. "Integrating NetSuite Connector with Oracle Simphony" then documents the setup: at connector.netsuite.com the operator opens Oracle Simphony > Settings > Credentials and enters Simphony User Name, Endpoint, Dataport, Private Key, Orders Path, Orders Archive Path and Passphrase, plus an RSA private key to decrypt the exports. That help topic covers credentials only; the payload description comes from NetSuite's launch release of 28 March 2024, which describes "a daily import of core financial data from Simphony into NetSuite", with "tender data segmented by tender name and carry over amounts" and imports "segmented by dayparts and include detailed transactional data such as totals, items sold, service charges, and discounts". Shortfalls against the claim as worded: (1) the claim requires QuickBooks Online plus at least one other, and no Oracle-maintained QuickBooks Online, Xero or Sage connector for Simphony is published; (2) the claim requires mapped journal entries rather than file export, and neither the help topic nor the launch release describes GL account mapping or journal-entry creation - the mechanism is an Oracle-hosted SFTP file drop of transactional data consumed on a daily schedule; (3) Oracle's own Inventory Management path to accounts payable remains Interface Definitions, "custom templates that define the format for exported data". https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_165036447599.html · retrieved 2026-08-08 adversarially verified

extensibility-payroll-export

Payroll Preprocessing, pay-period close/reopen, a Labor Management API Programmer's Guide and a Scheduler RESTful API guide are all published. No named payroll provider integration is documented by Oracle; third parties such as 7shifts publish their own Simphony connectors. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm · retrieved 2026-08-02

extensibility-bi-data-warehouse differentiator

A Business Intelligence REST API, an Import/Export API, a Standard Export User Guide and a Database Access Cloud Service Reference Guide are all published — a wider warehouse surface than most POS vendors. The two export guides are PDFs whose text did not extract, so the delivery mechanism and destination remain unverified. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/dacsr/index.html · retrieved 2026-08-02

extensibility-app-marketplace

Oracle publishes a public Simphony Plug-Ins catalogue with 27 named first-party plug-ins and versions. Self-install by the operator is not the model — plug-ins are deployed through EMC by an administrator, and there is no consent-based install flow. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-08-02

extensibility-custom-fields-scripting

Four extensibility references are published: JavaScript Extensibility API Reference Guide, Kiosk JavaScript API Reference Guide, HTML5 Custom Page Control API and HTML5 Extensibility Developer Reference Guide, alongside a .NET client extension API, the System Interface Module manual and an Extensibility Compatibility Guide. https://docs.oracle.com/en/industries/food-beverage/simphony/ · retrieved 2026-08-02

extensibility-headless-embedded

Guest Facing Transaction Services is the documented headless surface for kiosks and tabletop devices and is a distinct SKU (B83738 Premium, B90424 Standard), with the licence explicitly forbidding its use to integrate an employee-facing solution. Headless is possible and separately paid for. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02

extensibility-api-versioning-deprecation

A Change History page is published for the Configuration and Content API and referenced from the API index as the record of new endpoints and changes. A stated breaking-change notice period or deprecation policy was not found. https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/change_history.html · retrieved 2026-08-02

extensibility-data-portability-exit differentiator

Oracle Cloud Hosting and Delivery Policies section 6.1 gives 60 days after termination in which Oracle "will make available, via secure protocols and in a structured, machine-readable format, Your Content residing in the production Cloud Services environment, or keep the service system accessible, for the purpose of data retrieval by You." The shortfall is that disjunction: Oracle can discharge the obligation by leaving the tenant switched on, and no export mechanism, file format or scope (orders, customers, menu, payments metadata) is documented. It is a retrieval right, not a documented complete export. https://docs.oracle.com/en/applications/peoplesoft/financials-and-supply-chain-management/licensing-information-user-manual-for-peoplesoft-financials-and-supply-chain-management-9-2/oracle-cloud-hosting-delivery-policies.html · retrieved 2026-08-02 adversarially verified

reliability-offline-order-entry

Yellow mode: the workstation still communicates with other workstations and services and writes transactions to the Offline Cache. Red mode: no communication, transactions go to the local DataStore. On reconnect the workstation attempts to replay transactions to the central database automatically. https://docs.oracle.com/en/industries/food-beverage/simphony/19.4/sipou/c_workstation_online_offline_modes.htm · retrieved 2026-08-02

reliability-offline-card-auth differentiator

Oracle MICROS Payment Cloud Service documents the offline card path end to end. Scenario 2 is 'The Simphony workstation is online and the payment terminal is offline from the payment host', and on reconnect 'it forwards the stored payments to the payment processor'. Offline-approved payments are flagged in Payment Transaction Details with 'offline type' 1. The worked use case pays a 45.00 check plus 5.00 tip by credit card 'using an offline terminal' on day 0 and the check 'is paid and closed in Simphony', with the terminal reconnecting on day 2. That is store-and-forward card acceptance, not a cash-only fallback. https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/pcsrf/topic_13.htm · retrieved 2026-08-08

reliability-offline-decline-liability differentiator

Oracle documents the outcome but not the liability or the limits. When the terminal reconnects, forwards the stored payment and 'the card issuer subsequently refuses the payment', Simphony records a second Payment Transaction Details row with 0 transaction amount and 'a negative cancelled amount of the original payment amount', plus 'A row in Payment Settlement Details with a Journal Type of REFUSED and a settlement amount of 0', and 'No Payment Payout Details are produced for this transaction' - the operator is simply not paid on a check already closed. Shortfall: no Oracle document states who bears that loss in liability terms, and no per-transaction floor limit or cumulative offline ceiling is published anywhere in the payments-platform books or the Simphony Configuration Guide; the only offline threshold Oracle publishes is that 'If Simphony is offline for more than three days' downstream systems may receive settlement or payout details before transaction details. https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/pcsrf/topic_13.htm · retrieved 2026-08-08

reliability-lan-degraded-multi-terminal differentiator

Yellow mode is defined precisely as workstations continuing to communicate with each other and with local services when the enterprise is unreachable, so shared check state survives WAN loss — and the POS guide documents reloading and refreshing the CAPS database from the workstation. https://docs.oracle.com/en/industries/food-beverage/simphony/19.4/sipou/c_workstation_online_offline_modes.htm · retrieved 2026-08-02

reliability-local-transaction-engine differentiator

Check and Posting Service (CAPS) has its own configuration chapter (28), the KDS Controller is a local service with a documented backup, and workstations carry an on-device DataStore. This is a real on-premise transaction tier, not a cache. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

reliability-offline-kds-printing

The KDS Controller and order-device printing are local network services with a documented backup controller, so kitchen output survives WAN loss in principle. Oracle publishes no explicit guarantee of KDS behaviour while the enterprise is unreachable. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm · retrieved 2026-08-02

reliability-printer-fallback

Workstation Alerts for Unsuccessful Sending to Order Devices is a documented chapter, so staff are told when output fails, and the POS guide documents setting and changing the default printer. Automatic reroute to a backup printer is not documented as a configured behaviour. https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm · retrieved 2026-08-02

reliability-sync-conflict-handling

Simphony's documented model is ownership arbitration, not merge: 'CAPS also serves as the arbitrator of check sharing by maintaining a record of check ownership. This minimizes the likelihood of multiple workstations having conflicting versions of a check.' Partition behaviour is documented alongside it - a red-mode workstation 'stores all transaction and timekeeping information in its local DataStore', replays automatically on reconnect, and only returns online 'when the replay queue has no transactions remaining', with a PMC privilege (30069 - Replay Checks) for manual replay when automatic replay fails. Shortfall: Oracle names no resolution behaviour - last-write-wins, merge, or operator prompt - for the residual case its own sentence concedes, and the arbitration depends on reaching CAPS, which a red-mode workstation by definition cannot. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_caps.htm · retrieved 2026-08-08

reliability-offline-feature-matrix

Oracle does enumerate what offline financial reports omit — Returns, Void Total, Training Total, Checks Carried Over/Begun/Paid/Outstanding, Check Error Corrections and Total Net Sales — which is more than most vendors publish. There is still no degrade matrix for card authorisation, gift cards, loyalty or refunds. https://docs.oracle.com/en/industries/food-beverage/simphony/19.4/sipou/c_workstation_online_offline_modes.htm · retrieved 2026-08-02

reliability-public-status-page

OCI publishes a public status page but it does not cover Simphony or Oracle Food and Beverage components; Simphony service status is behind My Oracle Support. There is no public Simphony status page. https://ocistatus.oraclecloud.com/ · retrieved 2026-08-02

reliability-contractual-uptime-sla differentiator

Section 3.2: "Oracle works to meet the Target Service Availability Level, or Target Service Uptime of 99.9%", measured monthly as (total minutes minus unplanned downtime) / total minutes, conditioned on the customer meeting Oracle's minimum technical configuration. Section 3.2.3 provides Service Credits as the remedy when the target is missed. Both halves of the claim are in the standard agreement; the specific credit amounts are deferred to the Pillar document or Service Description, which returns 403 on oracle.com. https://docs.oracle.com/en/applications/peoplesoft/financials-and-supply-chain-management/licensing-information-user-manual-for-peoplesoft-financials-and-supply-chain-management-9-2/oracle-cloud-hosting-delivery-policies.html · retrieved 2026-08-02 adversarially verified

reliability-incident-postmortems

Checked ocistatus.oraclecloud.com, which returns a 2.4 KB client-rendered shell to both a browser UA and a Googlebot UA and whose Statuspage-style JSON path /api/v2/summary.json 404s, so no incident history or Food-and-Beverage component is reachable unauthenticated. Checked the Oracle Cloud Hosting and Delivery Policies v3.12 (May 2026), the document that governs every Simphony Cloud Service order: its only uses of 'incident' are data-centre continuity and security-incident notification, and it contains no occurrence of root cause, RCA or post-incident and no commitment to publish outage analyses. Checked the simrn release-notes book on docs.oracle.com, which carries Known Issues and Resolved Issues rather than outage post-mortems. Oracle's Food and Beverage support portal (iccp.custhelp.com) and My Oracle Support are login-gated, and RCA delivery there would not be public. Unresolved, not absent.

reliability-247-live-support

Oracle Cloud Hosting and Delivery Policies v3.12 (May 2026) section 5.1.4 states that Oracle Cloud Support 'consists of ... Assistance with technical service requests 24x7x365' and '24x7x365 access to a Cloud Customer Support Portal designated by Oracle to log service requests', and every Simphony edition's service description says 'Your order for this Oracle Cloud Service is subject to the Oracle Cloud Hosting and Delivery Policies' - so this is included with the base subscription, not a premium tier. Shortfalls: telephone specifically is conditional under 5.2.2 - 'Your technical contacts may access live support using Oracle's web-based customer support systems or by telephone, as available' - access is limited to designated technical contacts rather than any staff member, and 'Non-technical customer service assistance during normal Oracle business hours (8:00 to 17:00) local country time'. The 24x7 dedicated toll-free number Oracle does publish belongs to OPERA Cloud Elite Support, a hotel add-on in the Hospitality Hotel service descriptions, not to Simphony. https://www.oracle.com/contracts/docs/ocloud_hosting_delivery_policies_3089853.pdf · retrieved 2026-08-08

reliability-onsite-install differentiator

Read the Oracle Restaurants Cloud Services Service Descriptions and Metrics (effective 11 June 2026, 117 pages, oracle.com/contracts/docs/corporate_fbgu_service_descriptions_oracle_micros_cloud_service.pdf) in full text. The entitlement list for every production edition - Single-Tenant, Enterprise, Plus (B92456), Essentials - is software modules plus 'Access to standard online learning material, including guides, videos, release notes'; the strings install, deploy, on-site, onsite, go-live and onboard do not appear against any production edition. The only implementation reference is Service Provider Edition, where the OPN partner, not Oracle, is responsible for providing End-Customers with 'Implementation services', 'Software upgrades' and 'Support'. The companion Hospitality Food and Beverage service descriptions show Oracle sells set-up separately - 'You must separately purchase Oracle Cloud Professional Services to set up and configure this Oracle Cloud Service' - without describing its scope or whether it is delivered on site. Oracle's partner, services and Simphony product pages on www.oracle.com return 403 to every retrieval attempted, including a Googlebot user agent, so a first-party or certified-dealer on-site install and go-live offering can be neither confirmed nor ruled out.

reliability-menu-build-service differentiator

Checked the Oracle Restaurants Cloud Services Service Descriptions and Metrics (11 June 2026): no Simphony edition's entitlement list includes menu configuration or any onboarding deliverable, the phrase menu build appears nowhere in its 117 pages, and the glossary defines 'Menu Content' as 'information configured within any Simphony Cloud Service that describes a menu' - i.e. authored by the customer. Chapter 17 of the Simphony Configuration Guide (simcg) documents menu item, class, definition and price build as EMC work the operator performs, with no reference to an Oracle-delivered build. Against that, the Hospitality Food and Beverage service descriptions confirm Oracle sells 'Oracle Cloud Professional Services' for set-up and configuration as a separate purchase without publishing its scope, and oracle.com services pages 403 to retrieval, so a paid or bundled initial menu build may well exist. The entitlement list governs what the subscription grants access to, not the full set of services Oracle will sell, so it cannot carry a no.

reliability-hardware-replacement-sla

Oracle Hardware and Systems Support Policies (07-Aug-2026) defines 'Oracle Advanced Parts Exchange for Oracle Point of Service Hardware' - renamed from Oracle Advanced Parts Exchange for MICROS Hardware on 13 September 2024 - covering 'workstations, tablets, handhelds, scanners, printers, cash drawers, displays and payment solutions'. It 'consists of: Assistance with service request 24 hours per day, 7 days a week; Next business day parts exchange; Non-technical customer service during normal business hours', with response-time goals of Severity 1 five minutes / one hour update and Severity 2 two hours / six hours. The alternative tier, Oracle Premier Support for Oracle Point of Service Hardware, adds 'Onsite hardware support for Oracle Point of Service Hardware specified as Field Replaceable Units'. The base Oracle Hardware Warranty (07-August-2026) separately commits to shipping a Replacement CRU 'within 2 business days starting once the diagnostic analysis is done', an on-site response within two business days inside a designated Oracle Service Location, and 48-hour advanced parts exchange for ships and island countries. https://www.oracle.com/contracts/docs/hardware-systems-support-policies-069182.pdf · retrieved 2026-08-08

reliability-backup-restore

Oracle Cloud Hosting and Delivery Policies cover backup and disaster recovery for Oracle Cloud Services generally. Simphony-specific RPO and RTO figures, and any operator-triggered point-in-time restore, are not documented. https://www.oracle.com/contracts/docs/ocloud_hosting_delivery_policies_3089853.pdf · retrieved 2026-08-02

reliability-pci-dss-4-attestation

Oracle publishes Simphony PA-DSS 3.2 implementation guidance and per-module Security Guides for Transactions, Back Office and Inventory. A current PCI DSS 4.0/4.0.1 Attestation of Compliance covering the post-March-2025 future-dated requirements was not found publicly. https://docs.oracle.com/cd/E76065_01/doc.29/e69884.pdf · retrieved 2026-08-02

reliability-mfa-role-based-access

MFA has been enabled by default for Simphony EMC since release 18.1 using emailed one-time passwords with a five-minute expiry, layered on the role-based privilege model, with MFA EMC access privileges separately assignable. https://docs.oracle.com/en/industries/food-beverage/simphony/simsg/multi-factor_authentication.htm · retrieved 2026-08-02

reliability-self-serve-training

Oracle publishes an unusually complete free documentation set — POS User Guide, POS Manager, Frontline Manager, Reporting and Analytics, Inventory, Labor, Forecasting, plus every API reference — and the POS supports a training mode and training total. A free public video or LMS library was not found; Oracle University training is paid. https://docs.oracle.com/en/industries/food-beverage/simphony/ · retrieved 2026-08-02

reliability-failover-terminal-role differentiator

CAPS has its own configuration chapter and can be hosted on a workstation, and the KDS guide documents Configuring a Backup KDS Controller. Fully automatic assumption of the master role by an arbitrary surviving terminal is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

reliability-cellular-backup

Read the technical-specification tables for the current terminals on docs.oracle.com. Tablet 700 Series (tabss/c_tablet_technical_specifications.htm) lists, for the 720 and the 721/721P/722P, 'WLAN Wi-Fi 802.11a/b/g/n' and 'a/b/g/n/ac' plus Bluetooth, with no WWAN or LTE row. Workstation 8 (weset/c_intro_technical_specifications.htm) lists Network as '1 - Network port' plus 'Wi-Fi (optional): Intel Wi-Fi 6E AX210'. The Networking Excellence Guide (simphony/resnw) enumerates network hardware in chapter 7 as router, gateway, switch, network interface card, powerline extender and modem, and its modem topic covers cable, DSL and CSU/DSU leased-line only; there is no cellular, LTE or failover topic in the book's table of contents. Not scored no because the Handheld 500, Compact Workstation 3 Series and Express Station 4 Series publish their setup guides as PDFs whose text I could not extract (docs.oracle.com/en/industries/food-beverage/micros-handheld-500/omhhf/F78951_01.pdf returns 200 but resists text extraction, and the compact-workstation-3-series and micros-express-station index pages 404 at the paths linked from the hardware library), so the terminal enumeration is not exhaustive.

commercial-month-to-month-contract differentiator

Retrieved the current Oracle Cloud Services Agreement (Online, v062223) PDF directly from oracle.com/contracts/docs/cloud_csa_online_v062223_us_eng.pdf: section 9.2 says only 'Services shall be provided for the Services Period defined in Your order' and section 2.1 that 'Once placed, Your order is non-cancelable and the sums paid nonrefundable', so no term length is published at the master-agreement level. Read the Oracle Restaurants Cloud Services Service Descriptions and Metrics (11 June 2026): 'A minimum Service Period of 12 months' is imposed on the Plus and Premium Non-Production Environments, on Service Provider Edition environments and on the Essentials partner environment, but no term at all is stated for the core production editions (Plus B92456, Enterprise, Single-Tenant). So the only publicly retrievable Oracle contract documents neither offer nor forbid a month-to-month core POS subscription. The Simphony pricing and product pages on www.oracle.com return 403 to every retrieval attempted, including a Googlebot user agent, so any marketing claim of flexible terms remains unverifiable.

commercial-no-early-termination-fee differentiator

The published Oracle Cloud Services Agreement (Online, v062223), the master terms Simphony Cloud Service orders are placed under, says the reverse of this claim at section 2.1: 'Once placed, Your order is non-cancelable and the sums paid nonrefundable, except as provided in this Agreement or Your order.' The only refund the agreement grants is the warranty remedy at 6.3 - pre-paid fees for the terminated services returned if Oracle 'cannot substantially correct the deficiency in a commercially reasonable manner' - and section 9 TERM AND TERMINATION adds nothing but 'Services shall be provided for the Services Period defined in Your order'. There is no clause disclaiming early termination fees or liquidated damages; a customer cancelling before term end remains liable for the ordered fees. https://www.oracle.com/contracts/docs/cloud_csa_online_v062223_us_eng.pdf · retrieved 2026-08-08

commercial-autorenew-terms-published

A publicly posted Oracle Cloud Services Agreement does state the mechanism and the notice window. Cloud_CSA Transactional_v090213_US_ENG s9.1: 'certain Cloud Services that are ordered will Auto Renew for additional Services Periods unless (i) You provide Oracle with written notice no later than thirty (30) days prior to the end of the applicable Services Period of Your intention not to renew such Cloud Services, or (ii) Oracle provides You with written notice no later than ninety (90) days prior to the end of the applicable Services Period of its intention not to renew such Cloud Services.' s1.2 defines Auto Renewal as the Services Period being 'automatically extended for an additional Services Period'. Shortfall: the renewal term is not stated as a fixed length and which services auto-renew is not stated either - s1.2 sends both to 'the Service Specifications incorporated into Your order', and no Simphony-specific statement is published; the Online CSA v062223 and CSA v031916, the other publicly posted forms, contain no renewal clause at all. So the 30-day notice window is public while the renewal term itself still resolves in the signed order. https://www.oracle.com/contracts/docs/saas_csa_us_2069270.pdf · retrieved 2026-08-08 adversarially verified

commercial-processing-not-bundled differentiator

Oracle Payment Interface is documented specifically so Simphony can work with the merchant's chosen PSP, and Oracle's own Payment Cloud Service is a separate configuration path. The Credit Card Interface Cloud Service (B81483) remains a paid Simphony add-on whichever processor is chosen. https://docs.oracle.com/en/industries/food-beverage/simphony/simcm/t_shared_services_overview_opi.htm · retrieved 2026-08-02

commercial-interchange-plus-published differentiator

The Payment Cloud Service configuration guide documents account and terminal setup with no pricing model of any kind; no interchange-plus option with a stated basis-point and per-transaction markup is published anywhere Oracle-authored. https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/config.html · retrieved 2026-08-02

commercial-rate-increase-clause differentiator

Checked every public Oracle document that could carry a processing-rate term. The Oracle Restaurants Cloud Services Service Descriptions and Metrics (11 June 2026) names 'Oracle Restaurants Payment Cloud Service' as an entitled module in ten places but attaches no fee, rate or rate-change language to it; the strings interchange, discount rate, processing fee and rate increase appear nowhere in its 117 pages, nor in the Oracle Cloud Services Agreement (Online, v062223), nor in the Oracle Cloud Hosting and Delivery Policies v3.12. The MICROS Payment Cloud Service documentation on docs.oracle.com (payments-platform/latest config.html and the pcsrf Payments Processing book, whose 90-topic table of contents I enumerated) is purely operational - authorization flows, refunds, chargebacks, payouts, reconciliation reports - with no rate card and no fee-change clause. A separate Oracle payment services agreement, if one is published, is not reachable: www.oracle.com/contracts/cloud-services returns 403 to every user agent tried, so the contracts index cannot be enumerated and absence cannot be asserted.

commercial-pricing-published

Partial, and the shortfall is large. Search-indexed Oracle pages carry starting prices for the SMB editions only — Simphony Essentials from $55/month and a Plus tier from $75/month — and I could not retrieve either page directly, because every oracle.com marketing and pricing URL returns 403 to automated retrieval. What IS retrievable is the License Information Manual, which shows the enterprise structure: Premium (B81480, minimum 50 POS clients per Enterprise) and Standard (B84711) with no list price, and eleven separately licensed add-on part numbers around them. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02

commercial-module-unbundling differentiator

Genuinely a-la-carte and documented as such: Engagement (B81481), Credit Card Interface (B81483), Kitchen Display Services per KDS client (B81484), Fiscal Interface (B83739), Configuration Data Interface (B87077) and six Transaction Services variants, each with Premium or Standard as a stated prerequisite. This cuts both ways — it is also the mechanism behind the add-on cost creep operators report. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02 adversarially verified

commercial-hardware-purchase-outright

Oracle and its resellers sell MICROS hardware outright and no mandatory lease is documented anywhere. The claim fails its other half: Oracle publishes no per-SKU price, and its hardware pages 403 to retrieval. https://docs.oracle.com/en/industries/food-beverage/simphony/ · retrieved 2026-08-02

commercial-hardware-not-locked differentiator

Standard ESC/POS LAN printers are supported (the Label Printing plug-in names Bixolon and Epson) and Android and Windows service hosts exist, so the peripheral tier is open. Oracle documents no supported third-party workstation or tablet SKU, and technicians on operator forums treat the Oracle tablets as the part you replace rather than the part you standardise on. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm · retrieved 2026-08-02

commercial-implementation-fee-published

Oracle publishes no implementation, menu-build, onboarding or training fee, and does not state them as included. The License Information Manual prices nothing and the pricing pages are unretrievable; the recurring operator report is that post-go-live configuration changes are billable professional services. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02

commercial-data-export-self-serve

Reporting and Analytics, the Business Intelligence API, the Import/Export API, a Standard Export guide and a Database Access Cloud Service all provide export paths. The write/configuration API is a paid SKU, database access is its own named cloud service, and no fee-free self-serve full-history dump is documented. https://docs.oracle.com/en/industries/food-beverage/simphony/ · retrieved 2026-08-02

commercial-export-customer-and-loyalty differentiator

A Gift and Loyalty POS Web Services API Guide is published, covering account and balance access. A bulk operator export of guest records, point ledgers and outstanding gift card liability is not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/ · retrieved 2026-08-02

commercial-post-termination-export-window differentiator

Section 6.1: for 60 days after termination (30 for a free trial) Oracle makes Your Content available via secure protocols in a structured, machine-readable format, or keeps the system accessible for retrieval; afterwards "Oracle will delete Your Content from the Oracle Cloud Services environments". A defined window rather than an immediate cutoff. Note this is a generic Oracle Cloud policy, not a Simphony-specific commitment, and the oracle.com PDF copies return HTTP 403 — this docs.oracle.com reproduction is the retrievable one. https://docs.oracle.com/en/applications/peoplesoft/financials-and-supply-chain-management/licensing-information-user-manual-for-peoplesoft-financials-and-supply-chain-management-9-2/oracle-cloud-hosting-delivery-policies.html · retrieved 2026-08-02 adversarially verified

commercial-data-ownership-clause differentiator

Oracle Cloud policies treat transaction data as "Your Content" and commit to returning then deleting it, which implies customer ownership. No Simphony-specific clause constraining Oracle's use or resale of merchant data beyond aggregated and de-identified use was located. https://www.oracle.com/contracts/docs/ocloud_hosting_delivery_policies_3089853.pdf · retrieved 2026-08-02

commercial-source-available-selfhost

Simphony is proprietary software licensed per part number in Oracle's License Information Manual. No source-available or self-host option exists. https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm · retrieved 2026-08-02

commercial-pci-p2pe-tokenization

OPI plus PSP-owned terminals keep PAN off the POS application and Oracle publishes PA-DSS implementation guidance. Oracle names neither the merchant's resulting SAQ type nor any PCI-listed validated P2PE solution for Simphony. https://docs.oracle.com/cd/E76065_01/doc.29/e69884.pdf · retrieved 2026-08-02

commercial-pci-dss-4-controls

Default-on MFA for EMC since 18.1 satisfies part of Requirement 8, and the Audit Trail covers logging requirements. Payment-page script integrity per 6.4.3 and 11.6.1 for hosted ordering is not addressed in any retrievable Simphony document. https://docs.oracle.com/en/industries/food-beverage/simphony/simsg/multi-factor_authentication.htm · retrieved 2026-08-02

commercial-soc2-attestation

Oracle Cloud Hosting and Delivery Policies v3.12 (May 2026) section 1.12 External Reviews states that Oracle 'may conduct independent reviews of Oracle Cloud Services utilizing third parties' including 'SOC 1 (based on Statement on Standards for Attestation Engagements (SSAE) No 18) and/or SOC 2 reports (based upon Trust Services Criteria)', and that 'During the Services Period, You may obtain the then-current Service Organization Control (SOC) report(s) by the methods made available to You (e.g., self-service console or Service Request (SR))', to be protected as Oracle Confidential Information under the nondisclosure provisions - that is the report-under-NDA-on-request half of the claim, and it applies to Simphony because every Simphony service description subjects the order to this policy. Shortfalls: the commitment is expressly conditional - 'the scope of any such reviews may vary by Service and country' and reports are available only 'to the extent such reports are maintained for the in-scope Cloud Services' - Type II is never specified, and no Oracle statement or trust-centre entry naming Oracle Simphony Cloud Service or Oracle Restaurants Payment Cloud Service as currently SOC 2 Type II attested was located. https://www.oracle.com/contracts/docs/ocloud_hosting_delivery_policies_3089853.pdf · retrieved 2026-08-08

commercial-privacy-dsar-tooling

The tooling exists but is scoped to people, not guests. The Reporting and Analytics Data Privacy module states 'People Management stores personally identifiable information such as names, email addresses, and sign-in date and time stamps. Reporting and Analytics provides tools that let you quickly address user privacy requests.' Locate and export: 'The Personal Data Report lets the administrator collate all personal data related to a user and download it in a machine-readable format' (People, More Actions, Download Personal Data Report). Delete: De-identify 'overwrites their information with generic or empty values so activity cannot be traced back to the user', irreversibly. Simphony EMC adds consent capture, consent withdrawal and a scheduled DTS de-identification job plus a manual 'De-identify Now' in Employee Maintenance. The DPA half of the claim is met: Oracle publishes the Data Processing Agreement for Oracle Services v14082025, which covers 'Individual requests to access, delete or erase, restrict, rectify, receive and transmit (data portability), block access to or object to Processing of specific Personal Information' and directs the controller to 'securely access Your Services environment that holds Personal Information to address the request'. Shortfall: no locate, export or delete tooling for an individual GUEST's records is documented - the Configuration Guide's Privacy and Personal Data Management chapter and the R&A Data Privacy topics are entirely employee/user scoped, and the reports reference offers guest-check search rather than a guest DSAR workflow. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_data_privacy.htm · retrieved 2026-08-08

commercial-wcag-kiosk-accessibility differentiator

Oracle publishes 'ACR: Oracle MICROS Simphony Cloud Suite 6.0', VPAT version 2.3, dated 23-MAY-24, reporting against 'Web Content Accessibility Guidelines 2.1 Level A - Yes, Level AA - Yes, Level AAA - No' and the Revised Section 508 standards. It covers one guest-facing surface - 'Oracle MICROS Simphony Cloud Quick Response (QR) Pay' - alongside Frontline Manager, Simphony Telemetry, the Delivery Interface Cloud Service Provisioning Portal and the Oracle Linux for MICROS configuration utility. Shortfalls: the self-order kiosk is not among the covered items, and no kiosk ACR exists among the Oracle MICROS reports published under docs.oracle.com/en/corporate/accessibility/templates (the MICROS entries located are Simphony Cloud Suite 2.0/5.0/6.0, Simphony Telemetry 22.3, the Service Provider Edition provisioning tool, Compact Workstation 310, Peripherals and Accessories, and POS repair parts); the ACR expressly excludes Simphony Ops, the EMC, Engagement, Reporting and Analytics, Transaction Services and Oracle MICROS Payment Cloud Service; and a search of the 894-topic Simphony Configuration Guide table of contents returns accessibility topics only under the EMC - high-contrast visibility, home-page keystroke navigation, keyboard shortcuts, module accessibility - with no tactile or audio non-visual access mode for kiosks anywhere. https://docs.oracle.com/en/corporate/accessibility/templates/t2-14703.html · retrieved 2026-08-08

commercial-dual-pricing-compliant differentiator

The Credit Card Surcharge plug-in is scoped to "non-SPI integrated payments", so it does not cover Oracle's own semi-integrated payment path. Debit and prepaid exclusion, network cap enforcement and required menu-board and receipt disclosure handling are not documented. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-08-02