Vendors / Enterprise & chain restaurant POS
Oracle MICROS Simphony
Oracle Hospitality Simphony Cloud Service
dossier live
- Claims in scope
- 314
- Scored
- 314
- Assessed
- 309
- Unknown
- 5
- Not applicable
- 0
- Values challenged
- 71
Identity
- Owner
- Oracle Corporation (NYSE: ORCL) — Oracle Food and Beverage global business unit
- Parent
- Oracle
- Founded
- MICROS Systems founded 1977; acquired by Oracle in 2014 (~$5.3B). Simphony launched as MICROS's enterprise cloud POS platform before the acquisition and is now the flagship of the Oracle Food and Beverage global business unit.
- Scale
- unknown — Oracle does not disclose Simphony location counts or ARR separately in its 10-K or in any press release. Oracle marketing cites deployment in 180+ countries, but no audited installed-base figure is public.
- Who it is for
- Multi-unit and enterprise hospitality: large restaurant chains, hotels and resorts (tight Oracle OPERA PMS coupling — the POS user guide carries dedicated OPERA Connection, OPERA Guest Packages and room-charge chapters), casinos, stadiums and arenas (Suites Checks, Events and Rental Deposits are first-class documented constructs), cruise (there is a Cruise Ship Time Zone configuration chapter) and airports. Simphony Premium Cloud Service carries a documented minimum of 50 POS clients per provisioned Enterprise. A separate downmarket edition, Simphony Essentials, targets single-site and small multi-unit operators and is the only edition with a published starting price.
- Site
- https://www.oracle.com/food-beverage/restaurant-pos-systems/simphony-pos/
Lineage
- 1977 — founded: MICROS Systems founded; becomes the dominant enterprise hospitality POS vendor over the following three decades.
- 2014-09-08 — acquired: Oracle completes its acquisition of MICROS Systems for approximately $5.3B and folds it into the new Oracle Food and Beverage global business unit. Simphony becomes the flagship cloud POS; the older RES 3700 line is not migratable to it — technicians report that moving to Simphony requires a fresh installation rather than a database conversion.
Pricing
transparency: partial · unit: mixed · processor lock-in: no
- Software
- RETRIEVAL PREMISE CORRECTED 2026-08-10, AND THE CONCLUSION SURVIVES THE CORRECTION. The previous 'every oracle.com marketing and pricing URL returns HTTP 403 to automated retrieval' sentence was stale and is refuted by this record's own re-probe: www.oracle.com does NOT block us. The primary product page returns 200 and 66,689 bytes to an ordinary browser user agent, and oracle-linkcheck.mjs calibrates that host in both directions every run. What is actually true is narrower and worse for the vendor: the pricing page Oracle used to serve at /food-beverage/restaurant-pos-systems/simphony-pos/pricing/ has been WITHDRAWN — it returns that host's calibrated 404, as do three other plausible pricing paths probed the same day — and the live product page carries no price figure at all, only the phrase 'affordable monthly pricing plans'. So no Oracle-authored price is directly readable BECAUSE ORACLE PUBLISHES NONE, not because retrieval is blocked. That also weakens the indexed figures below rather than strengthening them: search engines index Oracle's own pages carrying starting prices for the SMB editions only — Simphony Essentials from $55 per month and a Simphony Plus tier from $75 per month — but the page those snippets came from is the one now gone, so they are stale snapshots of a withdrawn page, not a rate card, and are not verified. What IS directly retrievable is the License Information Manual, which shows the enterprise shape unambiguously: Simphony Premium Cloud Service (B81480, minimum 50 POS clients per Enterprise) and Simphony Standard Cloud Service (B84711) carry no published price at all, and around them sit eleven separately licensed part numbers — Engagement (B81481), Credit Card Interface (B81483), Kitchen Display Services per KDS client (B81484, required even when the customer uses a non-Oracle KDS), Fiscal Interface (B83739), Configuration Data Interface (B87077) and six Transaction Services variants (B81485, B3737, B83738, B90422, B90423, B90424). Premium and Standard each include a restricted-use licence for Reporting and Analytics Advanced and Labor Management; Simphony Essentials includes the same two.
- Card processing
- quote-only. Oracle ships its own Oracle MICROS Payment Cloud Service and publishes a full configuration guide for it — roles, account holders, accounts, revenue-center-to-store-ID mapping, terminal activation — containing no percentage, no per-transaction figure and no rate card of any kind. Merchants may instead use a third-party PSP through the Oracle Payment Interface, in which case the rate is the PSP's.
- Contract
- unknown. Oracle Cloud Services are ordered under Oracle Cloud Services Agreement terms with a services period defined in the order document. No publicly retrievable Simphony term sheet states the subscription term, auto-renewal period or notice window for any tier, and the marketing pages that claim flexible terms are unretrievable.
- Early termination
- unknown — not published. No Oracle-authored public document states an ETF or liquidated-damages clause for Simphony.
- Hardware
- quote-only per SKU, and by choice rather than by retrieval failure — the earlier "its hardware pages 403" sentence was the same stale premise already corrected in `software` above, and it is refuted here too. Every current MICROS hardware page opens to us with HTTP 200 (Workstation 6, Workstation 3, Workstation 8, MICROS Tablet, and the hardware index, 49,758-62,552 bytes, re-read 2026-08-12) and not one carries a list price. The index page answers the cost question with "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 offers only "Request a quote". Workstations 6 and 3 advertise "Get a Workstation 6 for US$1" / "Best-in-class POS terminal for US$1, no strings attached", but that is a switching promotion contingent on adopting Simphony and obtained by "Talk to an Oracle product expert" — a promotional term, not a rate card, and it hides the hardware cost inside a subscription whose price Oracle also does not publish. Oracle and its resellers sell the hardware outright and no mandatory lease is documented. 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.
API posture
public API: paid
- Cost to integrate
- Reading the documentation is free, unauthenticated and unusually complete. Calling it is not. Oracle's License Information Manual gates the two write surfaces behind separate part numbers: Configuration Data Interface Cloud Service (B87077) 'Grants access to the Configuration Data Interface API for direct integrations', and Transaction Services — the order-injection API — is separately licensed at every tier and in per-revenue-center variants (Premium B81485 and B3737, Standard B90422 and B90423), with guest-facing variants B83738 and B90424 whose licence text explicitly forbids using them for an employee-facing solution. Both require Premium or Standard Cloud Service as a prerequisite. This is why public_api is `paid` rather than `open`: the docs are open, the surface is metered, and it can be metered per revenue center. No partner fee, rev-share percentage or certification cost is published.
- Webhooks
- Present and weak. Transaction Services Gen2 pushes Organizations, Configuration, Check and Employees notifications in cloud (Check only on-premise). The subscriber endpoint must implement TLS 1.2 and listen on port 443, and only the .com .net .org .edu .ca .io .site .se .sa top-level domains are supported. Oracle states the subscriber timeout is 15 seconds 'with no retry'. No HMAC or payload signature scheme and no replayable event log are documented, and the webhooks ride on the paid Transaction Services SKU.
- Data export on exit
- Oracle Cloud Hosting and Delivery Policies commit to making Your Content available in a structured, machine-readable format via secure protocols for 60 days after termination, after which Oracle deletes it — a genuine published retrieval window that most POS vendors do not offer at all, though it is a generic Oracle Cloud policy rather than a Simphony-specific commitment. Day-to-day, Reporting and Analytics, the Business Intelligence API, a Standard Export guide and a separately named Database Access Cloud Service provide bulk paths; the text of the last two is in PDFs that did not extract.
- Notes
- Three documented REST API families — Business Intelligence, Configuration and Content (OAuth2 over TLS 1.2, JSON, REST POST, stateless, with a published change history covering menu items, menu item classes, discounts, service charges, locations and workstations), and Transaction Services Gen2 (real-time transactional read/write plus webhooks). Published rate limit: 9 API calls per second for Simphony Cloud Service, Single-Tenant Edition. A long tail of older interfaces persists and is all publicly documented: Transaction Services Gen1, Import/Export API, System Interface Module, Enhanced PMS interface specifications, Inventory Management master-data and POS web services, Labor Management API and Scheduler RESTful API, Gift and Loyalty POS web services, KDS Posting Files with a full field specification, plus JavaScript Extensibility, Kiosk JavaScript, HTML5 Custom Page Control and HTML5 Extensibility references and a .NET client extension API. No free public sandbox with seeded data exists — the GloriaFood integration guide shows the actual model, in which credentials are created as a Transaction Services API Account inside a real customer organisation.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.
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 lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.
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
Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.
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
Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.
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
Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator
order-capture-bar-tab-preauth
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
An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.
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
Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.
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
With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.
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
Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator
order-capture-qr-same-check
Simphony Transaction Services Gen2 exposes POST /api/v1/checks/{checkRef}/round: "API adds a round to an existing check." and "This operation does not alter items already on the check from previous rounds." The companion GET /checks/{checkRef} page states that CheckNotification messages are supported "including when a check was initiated from OPS and STS Gen2 is used to add a round", so a digital ordering channel can append items by checkRef to a check a server opened at the POS rather than creating a separate ticket. PARTIAL because the mechanism is documented at the API layer only: no document in this corpus shows a guest-facing QR at-table ordering front end using it, and Oracle's own first-party guest ordering product (Mobile Order and Pay, Frontline Manager book simfl) documents a dedicated "Order Type for mobile orders" and its own "Employee Number for order processing", which reads as a separate ticket. The QR mechanism Oracle does document on the check itself is staff-side reopen/merge (plug-ins.html, "Check Pickup Via Barcode"), not guest ordering. https://docs.oracle.com/en/industries/food-beverage/simphony/omsstsg2api/op-api-v1-checks-checkref-round-post.html · retrieved 2026-09-05 adversarially verified
Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator
order-capture-kiosk-first-party
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
Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.
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
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
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
Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator
order-capture-voice-ai
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
Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator
order-capture-throttling
CLAIM: order throttling - per-channel capacity limits per time slot, with automatic quote-time extension when kitchen load exceeds a configured threshold. VERDICT: no. The configuration model itself is now bounded and it cannot express either conjunct. NEW SURFACES FOUND IN THE 323rd, none named by any prior note or atlas file. (1) ANONYMOUS OPENAPI SPECS on docs.oracle.com, unlinked from any toc text but referenced by the book toc: https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/swagger.json - Simphony 'Configuration and Content API Guide', info.version 2026.06.15, 5,214,948 bytes, 887 paths / 887 operations, 721 definitions, 2,283 distinct property names; and https://docs.oracle.com/en/industries/food-beverage/simphony/omsstsg2api/swagger.json - 'Simphony Transaction Services Gen2 API Guide', info.version 2026.08.15, 297,397 bytes, 30 paths / 36 operations, 110 definitions. Soft-404 control: the same host answers every unknown path with an identical 15,118-byte HTML 404 (ccapi/openapi.json, simim/swagger.json, simts/swagger.json all 404/15,118), so these two 200s are real bodies, not a catch-all. (2) A COMPLETE CENSUS OF THE sicli BOOK. The Doc-O-Matic search index at https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/fti/FTI_Files.json (795,900 bytes, found from scripts/branding-Website.js) is the publisher's own file manifest: 7,786 entries of title+path. All 7,786 were fetched at HTTP 200, 0 failures, 156,641,767 bytes on disk. This retires the 'sicli is a FLOOR - roughly 700 of 7,600+ pages held' caveat that capped several cells of this record. (3) ssimm.pdf NOW EXTRACTS. https://docs.oracle.com/en/industries/food-beverage/simphony/ssimm/ssimm.pdf (Release 19.10, G49773-01, June 2026, 2,640,247 bytes) extracts with pdftotext -layout to 894,704 characters, positive control Simphony 154 / SIM 488. A prior note's claim that it 'did not text-extract for me' is FALSE of the current file. (4) www.oracle.com NO LONGER 403s. Several notes on this record rest on 'www.oracle.com returns 403 to every retrieval'. It returns 200 today to an ordinary browser UA. robots.txt (2,649 bytes, byte-identical to the copy cached 2026-08-10) NAMES ClaudeBot in a group whose rules are Disallow /a/ocom/docs/gated/, /splash/, /us/, /_qa/, /a/ocom/resources/, /financial-services/ofss/, /a/ocom/docs/corporate/pricing/ and three named PDFs, then Allow: /; none of the pages below is under a barred path and none was fetched with a UA swap. sitemap-core.xml yields a bounded 44-URL food-beverage corpus, all 200. (5) PDF-ONLY BACK-OFFICE API BOOKS, none in any prior corpus: lmapi E90995_32.pdf (Labor Management API, 196,436 chars), lmsch E90996_16.pdf (Scheduler RESTful API, 52,958), glpoa E91264_08.pdf (Gift and Loyalty POS Web Services API, 108,066), impoa E91249_09.pdf (Inventory Master Data Web Services, 55,473), immda E91248_07.pdf (Inventory POS Web Services, 48,212), dacsr G21944_03.pdf (Reporting DB Access, 239,447). EVIDENCE. The per-channel settings object is CLOSED and complete in the spec: definition OrderChannelParametersv2 has exactly 13 properties - hierUnitId, hierUnitObjNum, objectNum, orderChannelId, options (a 32-bit flag string), optionsExt, active, guestCheckHeaderObjNum, guestCheckTrailerObjNum, receiptHeaderObjNum, slaTime, orderDeviceMask, orderDeviceMaskExt - and its optionsExt expansion OrderChannelParameters_OptionsExt has exactly THREE flags: printOnCustomerReceiptAndCheck, printOnOrderPrinter, enableRoutingOrderByOrderChannel. The only time value on a channel is slaTime, '"Service Level Agreement Time. Allowed values are from 0-999."' - one fixed number per channel, not a ceiling per slot. The Gen2 order API agrees: definition OrderChannel is orderChannelId, name, isDefault, serviceLevelTime, and CheckHeader carries fireTime and pickupTime with '"If not provided the current time plus the Service Level Time for the given order type"' - again a fixed offset. BOUND/CONTROLS. Denominator: the 5,214,948-byte ccapi spec (887 operations, 721 definitions, 2,283 property names) plus the 297,397-byte Gen2 spec, tokenised word-boundary case-insensitive, script on disk. Zeros in BOTH specs: throttl 0, pacing 0, timeSlot 0, quota 0, surge 0, geofence 0. Positive controls read: ccapi discount 821, condiment 490, limit 455; Gen2 condiment 44, discount 31. POISON, all of it read: 'capacity' scores 23 in ccapi and 0 in Gen2, and EVERY ccapi hit is one repeated KDS panel field - '"capacity": "The relative capacity of the order devices linked to this panel. This field should only be used with KDS Controllers | General | Options | 13 - Enable Capacity Scheduling."' - i.e. relative weighting of prep stations, with no channel and no time dimension, which is the near-miss the existing note already identified and which the spec now bounds. 'slot' 5 is the SEI card slot number in an OASYS box. 'limit' 455 is field-length and value-range text. The autofire family (enableAutoFireInThisRVC, backAutoFireDelayInMinutes, autoFireEmpObjNum, defaultAutoFireTenderMediaNum) schedules a check to fire at a time the operator set; nothing in it reads kitchen load. SCOPE OF THE NO: this is the Simphony configuration and order-capture model. Oracle's separately sold digital-ordering front ends are not covered by it. Retrieved 2026-09-17. https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/swagger.json · retrieved 2026-09-17 adversarially verified
Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.
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
Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.
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
Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator
order-capture-order-ready-signal
STS Gen2 puts a KDS-derived preparationStatus on the check with allowed values Uninitialized/Submitted/Prepared/AllPrepared/Packaged; AllPrepared "Indicates that all items on the check have been prepared and moved \"bumped\" to the next stage." The page states "Kitchen Display System (KDS) configuration is required for all KDS-driven statuses; without KDS, only Submitted is supported.", and that "CheckNotification messages are supported when check notification options are enabled". So the ready signal is derived from POS/KDS state and pushed, not from a tablet tap. PARTIAL because the push target is any registered STS Gen2 integrator webhook: no document in this corpus shows Simphony's marketplace delivery connectors (DoorDash, Uber Eats, Deliveroo) consuming preparationStatus, and the two marketplace flags in the closed ccapi census (enableUberEatsIntegration, enableDeliverooIntegration) are order-sourcing switches with no status-callback field. https://docs.oracle.com/en/industries/food-beverage/simphony/omsstsg2api/op-api-v1-checks-checkref-get.html · retrieved 2026-09-05 adversarially verified
Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.
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, modifiers & pricing engine
Payments & money movement
The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator
payments-processor-choice
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
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
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
Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator
payments-dual-pricing
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
Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator
payments-surcharge-guardrails
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
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
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
Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator
payments-softpos-tap-to-pay
Not an argument from silence. The Payment Service Configuration book (fbopp, F38623-28, August 2025) is registry-closed at the book level, and its Chapter 5 enumerates the alternatives: it says 'you’ll receive a payment terminal' and lists exactly four devices, 'Castles Device S1F2', 'Verifone e285', 'P400 and V400m', 'Verifone P630' — all separate readers. Phone-based acceptance is not among them. The Payment Service release log (pcswn, F70387-25, current to release 20.4, June 2026, https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/pcswn/c_new.htm) introduces no such feature in any release; its 2025 entries are 'Multiple merchant accounts are now supported for an organization.' and reporting changes. The literal strings Tap to Pay, Tap to Phone and SoftPOS occur zero times across all 4,840 corpus documents, and the only on-device NFC facility Oracle documents is the Android POS client reading NFC tags (IsoDep, Mifare Classic, Mifare Ultralight) for SIM scripts in ssimm — tag reading, not card acceptance. FIRST CITATION of fbopp in this record. https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/fbopp/c_terminals_intro.htm · retrieved 2026-09-05 adversarially verified
Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.
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
Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator
payments-qr-guest-pay
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
Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.
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
Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator
payments-tip-pooling
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
Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator
payments-offline-store-and-forward
Offline card authorization exists and is a configurable EMC payment-driver field. The cited Payments configuration procedure (enterprise, Setup, Payments, SPI driver, Configuration tab) lists 'Offline Authorizations : 0' alongside 'Allow Manual Authorization Credit Card : True' and 'Manual Card Data Entry Retries : 0'. That transactions really are captured while the device is offline is corroborated by the Payment Service release log (https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/pcswn/c_new.htm, retrieved the same day), which records that Oracle 'Added offline authorization information to several reports and the payments transactions screen to identify transactions that were made while the payment device was offline or unable to communicate with the payment processor.' SHORTFALL, which is why this is partial and not yes: the only documented offline control is a count of permitted offline authorizations. No per-transaction amount cap and no cumulative offline amount cap appears anywhere in the registry-closed payments-platform library (fbopp 64 pages, pcsrf 84, pcswn 3, all held whole). FIRST CITATION of fbopp in this record; the URL was verified live at HTTP 200, 10,136 bytes, on 2026-09-05. https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/fbopp/t_emc_payments.htm · retrieved 2026-09-05 adversarially verified
Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator
payments-offline-decline-liability
The reporting half of this claim is satisfied and the liability half is not. Payment Cloud Service publishes a Payment Exceptions report whose metric set includes 'Offline Count', described as 'Number of offline authorizations.', next to 'Exception Count', 'Variance Amount' and 'Total Card Payments Amount'; the report itself is 'Report that shows variances between posted charges and' the POS. Its sibling topic Exception Details (https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/pcsrf/c_exception_details.htm, retrieved the same day) breaks exceptions into 'Processed Card Payments without POS Tender' with 'Alternative titles: POS Tender without Processed Card' Payments - which is exactly the post-reconnect view of POS tenders that never became processed card payments. SHORTFALL, which is why this is partial and not yes: nowhere in the registry-closed payments library (fbopp 64 pages, pcsrf 84, pcswn 3, all held whole) does Oracle state who bears the loss when a stored offline authorization declines on reconnect, and the merchant agreement that would carry that allocation is not among Oracle's publicly posted contract forms. Reporting documented; liability allocation unpublished. https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/pcsrf/c_payment_exceptions.htm · retrieved 2026-09-05 adversarially verified
First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.
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
House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.
payments-house-accounts
Gift and Loyalty (gnlug, release 20.1) documents a House Account credit card program by name. The cited topic sets up 'a credit card for house accounts, which can provide an organization or group with:' 'A consolidated bill for convenience with tracking and accounting' for expenses and 'A credit (expense) limit.' It is configured by entering the 'Default Credit Limit , and' then 'the message to be shown when the limit is reached in Credit Denial Text'; the sibling Credit Card Programs Configuration Reference (https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/c_program_creditcard.htm, retrieved the same day) defines that field as 'the maximum amount that the account can be charged into the negative for the program'. Running balance is native: Managing Customer Transactions (https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/c_customer_balance_manage.htm) drives everything off the Balance column — 'click the number in the Balance column' to get 'a list of transactions by' the customer, plus 'Post Transaction' to 'post credits or debits to customer accounts, or to post corrections.' SHORTFALL: no periodic statement or invoice generation run is documented anywhere in the book — the consolidated bill is asserted as a benefit of the program, not described as a produced statement — and the credit limit is documented only as a program-level default, with no per-account override procedure. gnlug is cited 13 times in this record; these three topics are not. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_using_creditcard_house.htm · retrieved 2026-09-05 adversarially verified
A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.
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
Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.
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
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
YOUR PROPOSED EVIDENCE IS WRONG AND THE VERDICT SURVIVES ON BETTER EVIDENCE. getPaymentChargebacks is indeed a read-only BI reporting endpoint and cannot carry this cell. The cell is carried by pcsrf chapter 7, 'Credit Card Disputes (Issued Through Reporting and Analytics)': 'View, accept, or reject chargebacks.' There is a dashboard - 'Your main dashboard includes a tile with' 'dispute details including disputes requiring action, defenses submitted,' 'charged, and reversed' - and a Disputes tab where 'the chargeback appears'. Evidence submission is explicit: 'Defend : you disagree with the chargeback' 'and you have supporting evidence that you can upload and submit along' 'with a defense reason', and the stage 'Information Supplied : Upload documents' 'that support your defense against the chargeback.' The procedure is in the sibling task Defend a Chargeback (https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/pcsrf/t_disputes_defend.htm, retrieved the same day): 'In Payment Cloud Service, click the Disputes tab.', 'Select the Defense Reason and then' 'upload required documents', with per-scheme limits (JPG 10MB, TIFF 10MB, PDF 2MB, 'Mastercard chargeback: 19 pages'). The POS linkage the cell asks for is in Chargeback Detail (https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/pcsrf/c_chargeback_detail.htm), whose row carries 'Check number.' and 'Drills down to Check Detail .' SUBJECT SCOPE, stated honestly: this is Oracle Payment Cloud Service, so the tooling reaches merchants processing on Oracle Payments, not those on a third-party PSP. FIRST CITATION of the pcsrf dispute topics in this record. https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/pcsrf/c_disputes.htm · retrieved 2026-09-05 adversarially verified
Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator
payments-card-on-file
Oracle Restaurants Suites Management Cloud Service, an advance-ordering application for premium-suite food and beverage that posts to Simphony, sold as a separately named Cloud Service. Its User Guide, smusg/account_settings.htm (docs.oracle.com, G55858-02, dcterms.created 2026-08-11, retrieved 2026-09-13), says: 'Users can securely store multiple credit cards within their account profile and select one as the payment method when placing an order.' The cards are tokens held at the FreedomPay gateway. smcfg/configure_billing_payment_fields.htm (G55857-01, 2026-07-01) says: 'Any changes to the ES Key, Store ID, or Merchant ID in the Billing and Payment settings will invalidate stored credit card tokens for account users in Suites Management. After such changes, users must re-enter their credit card information to continue using electronic payment methods.' A stored card is reused across a suite account's pre-event and event-day orders. smcfg/venue_details_operational_settings.htm: 'Suites automatically authorizes the payment method for the full order amount when an event's status is set to Live'. The link to Simphony is documented. smcfg/connect_venue_to_simphony.htm: 'you must link your venue to Simphony by providing essential information, including your organization details and API credentials'. smusg/items.htm: 'Each serving size is linked to an existing POS item in the Simphony system'. SHORTFALLS: (1) The stored credential belongs to a premium-suite account user (Account Holder or Authorized User), not to a restaurant guest profile. (2) It is reusable only inside the Suites ordering portal. Nothing documents reuse in Simphony online ordering, phone orders or in-store checks, and the Simphony Configuration Guide itself documents no guest card-on-file. (3) No page states outright that the merchant stores no PAN; that is inferred from the gateway-token wording. (4) Oracle's 2026-03-18 announcement said Suites Management 'will be available initially for customers in North America within the next 12 months', and no release note or general-availability statement was found. Hence partial. https://docs.oracle.com/en/industries/food-beverage/suites-management/latest/smusg/account_settings.htm · retrieved 2026-09-13 adversarially verified
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
YOUR PROPOSED EVIDENCE IS DEAD AND THE ANSWER IS BETTER THAN IT. getPaymentPayouts reports payouts after the fact and publishes no schedule. Oracle does publish an actual schedule, in pcsrf 'Timing of Transactions, Settlements, and Payouts': settlements 'are expected to occur two days from' the transaction date and 'Payouts are expected to occur three days from' the transaction date; 'Settlements and payouts do not happen on Sundays or bank holidays.'; 'The default cut-off time for payments is 2:00 a.m. local payment' terminal time in the US and 3:00 a.m. in the UK; transactions after cut-off move to the payout batch four workdays later; and a fifteen-column day-by-day table walks Thursday-through-Monday transactions to 'Funds deposit in bank', including a bank-holiday row. SHORTFALL, which is why this is partial not yes: the published schedule is T+3 workdays and Oracle documents no next-day, same-day or instant funding option anywhere in the payments library or its What's New log through release 20.4 (June 2026). Half the cell is met at grade B; the other half is affirmatively not offered. https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/pcsrf/topic_5.htm · retrieved 2026-09-05 adversarially verified
A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator
payments-multi-entity-routing
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
Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.
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 & production
Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.
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
An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.
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
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
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
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
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 load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
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
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
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
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
The bump-to-callback chain is documented end to end at the API layer. "The STS Gen2 Notifications Service is used to manage call back POST notifications messages that are sent to the integrator when they register to receive organization, configuration, check, and employee events"; the example message body carries messageType CheckNotification with a data.status field; and the Checks API defines that status as the KDS-driven preparationStatus whose AllPrepared value means all items "have been prepared and moved \"bumped\" to the next stage", requiring KDS configuration. PARTIAL on the courier leg only: the notification goes to a registered integrator webhook, and no Simphony document in this corpus shows the third-party marketplace connectors subscribing to it or a courier being dispatched off it. Also note the reliability caveat Oracle states outright: "At present retries are not supported. A notification will be sent only once." https://docs.oracle.com/en/industries/food-beverage/simphony/omsstsg2api/api-notifications-api.html · retrieved 2026-09-05 adversarially verified
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
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
An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.
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
Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.
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
If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator
kitchen-printer-fallback
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
KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator
kitchen-offline-operation
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
Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator
kitchen-item-build-screens
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
Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator
kitchen-pizza-fractional-display
CLAIM: sectioned/fractional topping placement (halves, quarters, specific sections) is rendered on the kitchen line screen or ticket. VERDICT: no. The existing note found no placement construct in two enumerations but left the cell open on the residual doubt that an operator-created condiment prefix could be NAMED for a half. The order API now closes that: the PREFIX TYPE SET ITSELF IS CLOSED AND CONTAINS NO PLACEMENT TYPE. NEW SURFACES FOUND IN THE 323rd, none named by any prior note or atlas file. (1) ANONYMOUS OPENAPI SPECS on docs.oracle.com, unlinked from any toc text but referenced by the book toc: https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/swagger.json - Simphony 'Configuration and Content API Guide', info.version 2026.06.15, 5,214,948 bytes, 887 paths / 887 operations, 721 definitions, 2,283 distinct property names; and https://docs.oracle.com/en/industries/food-beverage/simphony/omsstsg2api/swagger.json - 'Simphony Transaction Services Gen2 API Guide', info.version 2026.08.15, 297,397 bytes, 30 paths / 36 operations, 110 definitions. Soft-404 control: the same host answers every unknown path with an identical 15,118-byte HTML 404 (ccapi/openapi.json, simim/swagger.json, simts/swagger.json all 404/15,118), so these two 200s are real bodies, not a catch-all. (2) A COMPLETE CENSUS OF THE sicli BOOK. The Doc-O-Matic search index at https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/fti/FTI_Files.json (795,900 bytes, found from scripts/branding-Website.js) is the publisher's own file manifest: 7,786 entries of title+path. All 7,786 were fetched at HTTP 200, 0 failures, 156,641,767 bytes on disk. This retires the 'sicli is a FLOOR - roughly 700 of 7,600+ pages held' caveat that capped several cells of this record. (3) ssimm.pdf NOW EXTRACTS. https://docs.oracle.com/en/industries/food-beverage/simphony/ssimm/ssimm.pdf (Release 19.10, G49773-01, June 2026, 2,640,247 bytes) extracts with pdftotext -layout to 894,704 characters, positive control Simphony 154 / SIM 488. A prior note's claim that it 'did not text-extract for me' is FALSE of the current file. (4) www.oracle.com NO LONGER 403s. Several notes on this record rest on 'www.oracle.com returns 403 to every retrieval'. It returns 200 today to an ordinary browser UA. robots.txt (2,649 bytes, byte-identical to the copy cached 2026-08-10) NAMES ClaudeBot in a group whose rules are Disallow /a/ocom/docs/gated/, /splash/, /us/, /_qa/, /a/ocom/resources/, /financial-services/ofss/, /a/ocom/docs/corporate/pricing/ and three named PDFs, then Allow: /; none of the pages below is under a barred path and none was fetched with a UA swap. sitemap-core.xml yields a bounded 44-URL food-beverage corpus, all 200. (5) PDF-ONLY BACK-OFFICE API BOOKS, none in any prior corpus: lmapi E90995_32.pdf (Labor Management API, 196,436 chars), lmsch E90996_16.pdf (Scheduler RESTful API, 52,958), glpoa E91264_08.pdf (Gift and Loyalty POS Web Services API, 108,066), impoa E91249_09.pdf (Inventory Master Data Web Services, 55,473), immda E91248_07.pdf (Inventory POS Web Services, 48,212), dacsr G21944_03.pdf (Reporting DB Access, 239,447). EVIDENCE. In the Gen2 spec, definition condimentPrefixes.prefixType reads: '"Type of a condiment prefix. Possible values: \"description\" \"no\" \"add\" \"substitute\""' - four types, none of them positional. A check condiment (CheckCondimentItem) carries condimentId, prefixes, definitionSequence, name, quantity, unitPrice, priceSequence, total, seat, referenceText, surcharge, isDefault, atDefaultSetting, itemDiscounts: there is no side, section, half, fraction or coordinate property on which a kitchen renderer could act. The configuration API agrees: MenuItemClass2.condimentPrefixType is a single integer and the prefix flags are printMainLevelPrefixAndSuffix, printSubLevelPrefixAndSuffix and supportEnhancedPrefixMode - all print-text switches. So a site that names a 'description' prefix '1/2' gets that string printed as text in front of a condiment; the item is still ordered once and whole, and no renderer is told where on the pie it sits. That is a naming convention, not placement, and it is the trap in this cell. BOUND/CONTROLS. Denominator: the 5,214,948-byte ccapi spec + the 297,397-byte Gen2 spec, tokenised, word-boundary, case-insensitive. Zeros in BOTH: fraction 0, topping 0, placement 0 (Gen2), and in Gen2 also half 0 and quarter 0. Positive controls: ccapi condiment 490, Gen2 condiment 44. POISON, all read: ccapi 'half' 2 is one rounding rule ('"round the change due down instead of up ... exactly half of the rounding number"'); 'quarter' 7 is the fiscal start-of-quarter autosequence (sOQPCAutoSeqObjNum, sOQAlternateDates); 'pizza' 6 is an image altText EXAMPLE VALUE on the menu-item content object; 'placement' 5 in ccapi is kdsProdLocation, '"The placement of production item counters on the display. 1 - Top, 2 - Bottom"'; 'section' 29/23 is JSON prose. This sits alongside the existing note's kdscu r_kds_chit_layouts.htm enumeration of every chit layout style Simphony ships, none of which renders a sectioned or graphical pie. Retrieved 2026-09-17. https://docs.oracle.com/en/industries/food-beverage/simphony/omsstsg2api/swagger.json · retrieved 2026-09-17 adversarially verified
A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.
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
Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator
kitchen-order-modification-alerts
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
Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator
kitchen-guest-ready-notification
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
Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.
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
Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.
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
Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.
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, dispatch & third-party channels
Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).
delivery-driver-roster
REVERSES A FALSE PREMISE. The prior verdict said "No driver as an employee class exists". The Simphony POS Client (.NET) Extension API Reference (sicli, Copyright "2010, 2025") shows the opposite: the EmployeeInfo class carries the properties "IsAvailableForDelivery" and "IsCourier" alongside EmployeeNumber, FirstName, LastName and RevenueCenter, so courier is a flag on the first-class Simphony employee record, not an absent entity. Corroborating members, each in the same book: EmployeeFilterParameters exposes "CourierFilter" and "CourierFilterIndex" and EmployeeInfoList exposes "CourierFilters" (html_31ab9023-243f-eedc-e08f-1e55d193e03c.htm, html_e1d89396-bd25-020d-52cd-df98d03a3974.htm), so the employee list is filterable to couriers; OpsContext has "UpdateCourierList" — "Update Courier List and flag details as changed for DTO Delivery Dispatch screen" (html_293ce7bf-bb93-7337-e3df-c930686c3377.htm); CheckSummaryData carries "DeliveryEmployeeID" ("Delivery employee id") and "DeliveryEmployeeName" ("Delivery Employee name") (html_eaebf60b-d691-4f9b-1241-b52a1c70465d.htm), which is per-run assignment history at check level; and OpsCommandType has "AddDeliveryEmployee", "RemoveDeliveryEmployee" and "RemoveCourier" — "Used to remove courier from a check." (html_2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm). Couriers are Simphony employees, so the labor-clock-in-at-pos punch surface covers their clock-in/out. Partial, not yes, for two reasons. First, source class: an extension API reference proves the client exposes courier objects; it is weaker than a user-guide chapter showing an operator working a roster, and Oracle publishes no such chapter in any prose book held here. Second, the driver-facing half is explicitly reserved: OpsCommandType marks "EmployeeSelfAvailability" and "DeliveryEmployeeAvailability" as "RFU", so a driver marking their own availability is not shipped (the manager-side "IsAvailableForDelivery" property and the OpsRequestType "EmployeeAvailablility" / "Show Delivery Employee Availability" dialog are not so marked). No documented in-store / on-run / returning state machine was found. sicli is a floor (~700 of 7,600+ pages held), so this establishes presence and can never establish the remaining absence. CITATION REPAIRED 2026-09-09: the sicli book was regenerated and every topic moved from /sicli/html_<guid>.htm to /sicli/html/<guid>.htm. The old address returned a 404 byte-identical to a fabricated control; the page itself is unchanged and still serves at 200. https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/html/e905423a-a186-8ac7-ca37-d3a45c38f474.htm · retrieved 2026-09-09 adversarially verified
Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).
delivery-dispatch-board
REVERSES A FALSE PREMISE. The prior verdict said "there is no assign-to-driver surface". Oracle names the screen by name: the OpsContext class documents the method "UpdateCourierList" as "Update Courier List and flag details as changed for DTO Delivery Dispatch screen", and DTO is expanded in the same book as "DTO (Delivery Takeout Order)". OpsContext also carries "SelectedCourierListUpdated" — "Determine if the selected courier list has changed or not" — and "DeliveryCheckActive" ("True if there is a currently active delivery guest check") and "DTOCheckActive" ("True if there is a currently active takeout, curbside or delivery guest check"). The board's other three asks are each evidenced in the same book: driver availability via OpsRequestType "EmployeeAvailablility" — "Show Delivery Employee Availability" — and "DTOViewCourierDialog" — "Displays a DTO view courier dialog given an employee id" (html_25aa611a-211f-ac66-1ecd-74ec9890469b.htm); order filtering via OpsCommandType "DTOApplyDeliveryCheckFilter", "DTOClearDeliveryCheckFilter" and "DTOApplyCourierFilter"; and multi-order run batching via "AssignMultipleDeliveryEmployee" and "UpdateMultipleDeliveryOrderStatus" (html_2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm). Dispatch state is also persisted downstream: the Database Access Cloud Service Reference (back-office/20.1/dacsr, https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/dacsr/G21944_03.pdf) defines a VRO_SOS_GUEST_CHECK_HIST view of speed-of-service data for past business date guest checks whose Date columns include "DISPATCHTIME" ("Dispatch Time") and "UNDISPATCHTIME" ("Undispatched Time") next to "APPROXDELIVERYTIME", "PREPDONETIME", "CALLBEGUNTIME" and "CALLANSWERTIME", so undispatched-vs-dispatched is a reportable order state, not a KDS placeholder. Partial rather than yes: every one of the DTO screen's own commands is annotated "Micros internal use only.", meaning they are the shipped screen's internals rather than an extensibility contract, and Oracle publishes no operator-facing chapter, screenshot or field list for the Delivery Dispatch screen in any prose book held here. Elapsed time per order is inferable from the quote/actual timestamps but is not shown as a board column anywhere. sicli is a floor (~700 of 7,600+ pages). CITATION REPAIRED 2026-09-09: the sicli book was regenerated and every topic moved from /sicli/html_<guid>.htm to /sicli/html/<guid>.htm. The old address returned a 404 byte-identical to a fabricated control; the page itself is unchanged and still serves at 200. https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/html/293ce7bf-bb93-7337-e3df-c930686c3377.htm · retrieved 2026-09-09 adversarially verified
Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator
delivery-route-map
Upheld, but the previous rationale overstated the enumeration and that overstatement is withdrawn. It said the OpsCommandType listing contains no map, route, stop-sequencing, optimize or navigation member of any kind -- that was this record's own wording, and it is wrong. It contains one that is close: DTOLocateDeliveryDriver. That member does not rescue the claim, and cannot, for two reasons. Its entire published description is 'Micros internal use only.', so nothing is documented about what it does -- and it is one of 182 members on this page carrying that same sentence and no behaviour. More decisively, the claim asks for a live map view with GEOCODED STOPS and system-generated route sequencing, and nothing in Simphony geocodes a guest address: across a 1,405-page corpus of the sicli book read 2026-09-09 by href fixpoint from its own default topic, plus the Enterprise Cash Management chapter, the GloriaFood book contents and the Simphony library registry, `geocode`, `geocoding`, `map view`, `live map`, `polyline`, `waypoint`, `route optimization`, `turn by turn`, `stop sequence` and `sequencing` occur zero times, tokenised and as bare substrings alike. The two near-misses are both the wrong sense -- EditRoutingGroups is 'Edit routing groups', which is kitchen order-device routing, and Navigate means 'Navigate to the first page/tab sheet'. A locate command with no geocoded guest address cannot sequence a multi-stop run. Two limits the reader must carry. sicli is enormous -- the fixpoint had 34,883 URLs still queued when the crawl was capped at 1,400 pages -- so a corpus-wide zero here is a bounded absence, not a census. And the OpsCommandType enumeration, which IS a complete member list for its own type, is a ceiling on member NAMES ONLY: 182 of its members are documented with the single sentence 'Micros internal use only.' and carry no behavioural description at all, so the enumeration cannot bound what an undocumented member does. https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/html/2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm · retrieved 2026-09-09 adversarially verified
Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator
delivery-driver-tracking
CLAIM: captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. VERDICT: no. The existing note held this at unknown expressly because sicli was a FLOOR (about 700 of 7,600+ pages) and because OpsCommandType contains a member named DTOLocateDeliveryDriver whose meaning could not be read. Both blockers are now removed. NEW SURFACES FOUND IN THE 323rd, none named by any prior note or atlas file. (1) ANONYMOUS OPENAPI SPECS on docs.oracle.com, unlinked from any toc text but referenced by the book toc: https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/swagger.json - Simphony 'Configuration and Content API Guide', info.version 2026.06.15, 5,214,948 bytes, 887 paths / 887 operations, 721 definitions, 2,283 distinct property names; and https://docs.oracle.com/en/industries/food-beverage/simphony/omsstsg2api/swagger.json - 'Simphony Transaction Services Gen2 API Guide', info.version 2026.08.15, 297,397 bytes, 30 paths / 36 operations, 110 definitions. Soft-404 control: the same host answers every unknown path with an identical 15,118-byte HTML 404 (ccapi/openapi.json, simim/swagger.json, simts/swagger.json all 404/15,118), so these two 200s are real bodies, not a catch-all. (2) A COMPLETE CENSUS OF THE sicli BOOK. The Doc-O-Matic search index at https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/fti/FTI_Files.json (795,900 bytes, found from scripts/branding-Website.js) is the publisher's own file manifest: 7,786 entries of title+path. All 7,786 were fetched at HTTP 200, 0 failures, 156,641,767 bytes on disk. This retires the 'sicli is a FLOOR - roughly 700 of 7,600+ pages held' caveat that capped several cells of this record. (3) ssimm.pdf NOW EXTRACTS. https://docs.oracle.com/en/industries/food-beverage/simphony/ssimm/ssimm.pdf (Release 19.10, G49773-01, June 2026, 2,640,247 bytes) extracts with pdftotext -layout to 894,704 characters, positive control Simphony 154 / SIM 488. A prior note's claim that it 'did not text-extract for me' is FALSE of the current file. (4) www.oracle.com NO LONGER 403s. Several notes on this record rest on 'www.oracle.com returns 403 to every retrieval'. It returns 200 today to an ordinary browser UA. robots.txt (2,649 bytes, byte-identical to the copy cached 2026-08-10) NAMES ClaudeBot in a group whose rules are Disallow /a/ocom/docs/gated/, /splash/, /us/, /_qa/, /a/ocom/resources/, /financial-services/ofss/, /a/ocom/docs/corporate/pricing/ and three named PDFs, then Allow: /; none of the pages below is under a barred path and none was fetched with a UA swap. sitemap-core.xml yields a bounded 44-URL food-beverage corpus, all 200. (5) PDF-ONLY BACK-OFFICE API BOOKS, none in any prior corpus: lmapi E90995_32.pdf (Labor Management API, 196,436 chars), lmsch E90996_16.pdf (Scheduler RESTful API, 52,958), glpoa E91264_08.pdf (Gift and Loyalty POS Web Services API, 108,066), impoa E91249_09.pdf (Inventory Master Data Web Services, 55,473), immda E91248_07.pdf (Inventory POS Web Services, 48,212), dacsr G21944_03.pdf (Reporting DB Access, 239,447). EVIDENCE. (a) OpsCommandType Enumeration (sicli html/2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm, 252,920 bytes) is a CLOSED enumeration of 660 rows, read in full. Its delivery family is: AssignDeliveryEmployee 'RFU'; DeliveryEmployeeAvailability 'RFU'; RemoveCourier 'Used to remove courier from a check.'; DeliveryQuoteTimeOverride 'Change the delivery quote time of the current check'; ChangePickupOrDeliveryDateTime; and 26 DTO* members every one of which reads 'Micros internal use only.' with no description - including DTOLocateDeliveryDriver, DTOViewCourierDialog, DTOApplyCourierFilter and AssignMultipleDeliveryEmployee. 'Locate' is undefined there and sits among dialog, filter and tab commands. (b) Across the COMPLETE 7,786-topic sicli census the words latitude, longitude, GPS, geolocation, coordinate and geofence score ZERO, so no member, parameter, property or remark in the entire POS-client extension API - the API the DTO Delivery Dispatch screen is itself part of - ever carries a position. (c) The two published REST specs agree. In ccapi, latitude/longitude exist on exactly six definitions and all are the RESTAURANT's address: '"The revenue center latitude. Latitude must be within range -90 to +90"' (RevenueCenterInsert/Update/GETv1/GETv2) and '"The property latitude"' (Location, Locationv2, LocationInsert/UpdateRequestBody). In Gen2, the only geo type is GeoLocation, '"Coordinate of a location"', used by distanceLocation ('"The distance in meters between the location and the point defined in the request"'), i.e. a store finder. BOUND/CONTROLS. Denominators: 7,786 sicli topics / 156,641,767 bytes bound to the publisher's own FTI_Files.json manifest with zero unfetched; 5,214,948-byte ccapi spec; 297,397-byte Gen2 spec. Tokenised, word-boundary, case-insensitive. sicli positives: Simphony 54,534 across 7,786 files, OpsContext 6,477, check 3,701. sicli delivery 67 in 22 files, courier 27 in 17 files, dispatch 4 in 3 files - so the vocabulary IS present and it is the absence of position that is being measured, not a dead corpus. POISON: ccapi 'driver' 85 is a SOFTWARE driver (enableLoyaltyDriver, enablePaymentDriver, enableStoredValueDriver) plus printTwoLinesOfDiscretionaryDriverData, a card-receipt print flag; ccapi 'courier' 4 is the font name 'Courier New' on the customer display. SCOPE OF THE NO: Simphony ships no driver-facing mobile app in any of these surfaces, and a third-party marketplace tracking its own courier in its own app is not this claim. Retrieved 2026-09-17. https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/html/2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm · retrieved 2026-09-17 adversarially verified
Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator
delivery-zones-polygon
Upheld and now cited to the enumeration it rests on. Zone in Simphony is a tier of the Enterprise > Property > Revenue Center > Zone configuration hierarchy -- an inheritance scope for records such as payment drivers -- not a geographic boundary, and the cited command surface, which enumerates the Delivery Takeout Order dispatch screen in full (check filters, courier filters, guest-info and delivery-info tabs, order notes, quote refresh, multi-order assignment), carries no zone, area or boundary member. Across a 1,405-page corpus of the sicli book read 2026-09-09 by href fixpoint from its own default topic, plus the Enterprise Cash Management chapter, the GloriaFood book contents and the Simphony library registry, `delivery zone`, `delivery area`, `polygon`, `isochrone`, `drive time`, `radius`, `postcode`, `postal code list`, `boundary` and `geofence` occur zero times, tokenised and as bare substrings alike. The only geospatial construct held anywhere is the store-location and revenue-centre geoLocation latitude/longitude pair in the Transaction Services Gen2 and Kiosk JS APIs, used to find restaurants near a guest -- the inverse of bounding a delivery area. Two limits the reader must carry. sicli is enormous -- the fixpoint had 34,883 URLs still queued when the crawl was capped at 1,400 pages -- so a corpus-wide zero here is a bounded absence, not a census. And the OpsCommandType enumeration, which IS a complete member list for its own type, is a ceiling on member NAMES ONLY: 182 of its members are documented with the single sentence 'Micros internal use only.' and carry no behavioural description at all, so the enumeration cannot bound what an undocumented member does. https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/html/2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm · retrieved 2026-09-09 adversarially verified
Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.
delivery-zone-pricing
Upheld. The claim needs a per-zone fee, a per-zone order minimum and a per-zone promise time, all applied automatically from a validated customer address, and each of the three preconditions fails independently. There is no delivery-zone construct to scope a price to (see delivery-zones-polygon: `delivery zone`, `polygon`, `isochrone`, `radius` and `boundary` are all zero across a 1,405-page corpus of the sicli book read 2026-09-09 by href fixpoint from its own default topic, plus the Enterprise Cash Management chapter, the GloriaFood book contents and the Simphony library registry). There is no address validation to trigger one (see delivery-address-validation). And the quote-time controls the cited enumeration does document are manual, not zone-derived -- DeliveryQuoteTimeOverride and ChangePickupOrDeliveryDateTime are per-check operator actions. The delivery charge Oracle does document is a flat service charge. Note that Simphony DOES run first-party delivery -- the old rationale's claim that delivery charges are only the marketplace's is dead, since this enumeration carries couriers, delivery-employee assignment and first-party quote times -- so this is a real gap in a real product, not an artefact of Simphony being order-injection only. Two limits the reader must carry. sicli is enormous -- the fixpoint had 34,883 URLs still queued when the crawl was capped at 1,400 pages -- so a corpus-wide zero here is a bounded absence, not a census. And the OpsCommandType enumeration, which IS a complete member list for its own type, is a ceiling on member NAMES ONLY: 182 of its members are documented with the single sentence 'Micros internal use only.' and carry no behavioural description at all, so the enumeration cannot bound what an undocumented member does. https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/html/2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm · retrieved 2026-09-09 adversarially verified
Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.
delivery-address-validation
Upheld on the validation ask, with capture conceded. An operator plainly types a delivery address into Simphony: the cited enumeration carries DTOGuestInfoTabSave, DTOGuestInfoTabClear, DTODeliveryInfoTabSave, DTODeliveryInfoTabClear, DTOUpdateCustomerData and DTOUpdateOrderInfoData, and CheckSummaryData carries CustomerDetails, described as 'Customer information - currently used by DTO (Delivery Takeout Order)'. What the claim asks is whether that address is verified -- geocoded, checked against a serviceable boundary, or flagged out of area -- and nothing does: `geocode`, `geocoding`, `boundary`, `geofence` and `delivery area` are zero across a 1,405-page corpus of the sicli book read 2026-09-09 by href fixpoint from its own default topic, plus the Enterprise Cash Management chapter, the GloriaFood book contents and the Simphony library registry, tokenised and as bare substrings, and there is no boundary construct to check an address against in the first place. The only WGS84 coordinates in the whole documentation set describe store locations, not guests. The address print tokens in the Gift and Loyalty guide are loyalty-account fields rendered on a chit, not a validation step. Two limits the reader must carry. sicli is enormous -- the fixpoint had 34,883 URLs still queued when the crawl was capped at 1,400 pages -- so a corpus-wide zero here is a bounded absence, not a census. And the OpsCommandType enumeration, which IS a complete member list for its own type, is a ceiling on member NAMES ONLY: 182 of its members are documented with the single sentence 'Micros internal use only.' and carry no behavioural description at all, so the enumeration cannot bound what an undocumented member does. https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/html/2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm · retrieved 2026-09-09 adversarially verified
Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator
delivery-driver-comp
Upheld. Simphony does have a driver entity -- employees carry IsCourier and IsAvailableForDelivery flags and a check carries a DeliveryEmployeeID -- so the question is compensation, not existence. The claim wants mileage or distance per run, a per-delivery flat reimbursement, and driver-retained tips, exported to payroll as separate reimbursement and wage lines. None of the vocabulary exists: `mileage`, `miles driven`, `distance driven`, `reimbursement`, `run pay` and `trip pay` occur zero times across a 1,405-page corpus of the sicli book read 2026-09-09 by href fixpoint from its own default topic, plus the Enterprise Cash Management chapter, the GloriaFood book contents and the Simphony library registry, tokenised and as bare substrings alike. The cited enumeration's courier members are all assignment, filtering, arrival and removal -- AddDeliveryEmployee, AssignDeliveryEmployee, AssignMultipleDeliveryEmployee, DTOApplyCourierFilter, DTOViewCourierDialog, RemoveCourier, RemoveDeliveryEmployee, DeliveryEmployeeAvailability, PickupPersonArrival -- and not one of them is an earning, a distance or a payout. Labor Management's employee and payroll surface enumerates payroll ID, employee role, address and job codes with no per-delivery earning type. There is no distance field anywhere for a rate to multiply. Two limits the reader must carry. sicli is enormous -- the fixpoint had 34,883 URLs still queued when the crawl was capped at 1,400 pages -- so a corpus-wide zero here is a bounded absence, not a census. And the OpsCommandType enumeration, which IS a complete member list for its own type, is a ceiling on member NAMES ONLY: 182 of its members are documented with the single sentence 'Micros internal use only.' and carry no behavioural description at all, so the enumeration cannot bound what an undocumented member does. https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/html/2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm · retrieved 2026-09-09 adversarially verified
Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.
delivery-cash-reconcile
Upheld, and the citation is the chapter that enumerates the receptacles. Enterprise Cash Management names the containers Simphony can reconcile -- tills, safes and server banks, with count sheets and deposits -- and a driver bank is not among them. Across a 1,405-page corpus of the sicli book read 2026-09-09 by href fixpoint from its own default topic, plus the Enterprise Cash Management chapter, the GloriaFood book contents and the Simphony library registry, `driver bank`, `courier bank`, `settle up`, `over/short`, `over short`, `cash owed` and `driver settlement` occur zero times, tokenised and as bare substrings alike. The command surface does carry cash-management members such as AddToSafe and CashManagementDepositDate, so this is not a gap in what the enumeration covers -- cash management is present and per-driver settlement simply is not in it. What Simphony has instead is an arrival timestamp, PickupPersonArrival, described as recording 'the arrival of pick up person (customer or courier) arrival date and time', plus an order-to-courier assignment. An arrival time and an assignment are not a reconciliation of cash collected against orders assigned and tips owed, and produce no per-driver over/short figure. Two limits the reader must carry. sicli is enormous -- the fixpoint had 34,883 URLs still queued when the crawl was capped at 1,400 pages -- so a corpus-wide zero here is a bounded absence, not a census. And the OpsCommandType enumeration, which IS a complete member list for its own type, is a ceiling on member NAMES ONLY: 182 of its members are documented with the single sentence 'Micros internal use only.' and carry no behavioural description at all, so the enumeration cannot bound what an undocumented member does. https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_ecm.htm · retrieved 2026-09-09 adversarially verified
Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.
delivery-daas-dispatch
328th: THE LAST UNBOUNDED SURFACE THIS NOTE NAMED IS NOW READ, AND IT CARRIES NO COURIER HAND-OFF, SO THE CELL MOVES TO NO. The 326th note closed with 'Unknown stands only because Digital Ordering itself is still unbounded'. Oracle's first-party ordering front end for Simphony is Mobile Order and Pay, and it is configured from the Frontline Manager module: the Oracle Simphony Frontline Manager User Guide (G49756-01, docs.oracle.com/en/industries/food-beverage/simphony/simfl/) was walked from its own toc.htm to a link fixpoint - 25 of 25 topics, 2 rounds, 0 failures, 32,872 characters; the nonsense control is this host's 15,118-byte 404 page, which /simphony/simdo/ and /digital-ordering/ both return (no separate Digital Ordering book is published). Its whole Mobile Order and Pay chapter is a six-step guided connection (map RVC, connection details, images, hours, legal policies, activate) whose entire delivery vocabulary is ONE line in the pre-flight checklist: 'Service Charges (tips, delivery fees if applicable)'. Tokenised word-boundary case-insensitive over the complete book: courier 0, dispatch 0, DoorDash 0, Uber 0, driver 0, 'third party' 0. So Oracle's own ordering product takes delivery money and dispatches nobody. BOUND, four published vendor surfaces, two of them CLOSED enumerations: (1) sicli, the POS Client .NET Extension API Reference, 7,786 of 7,786 topics from the publisher's own fti/FTI_Files.json manifest, whose 660-row OpsCommandType enumeration contains no command to request, quote, cancel or track an on-demand courier job - only in-house members (RemoveCourier, DeliveryQuoteTimeOverride, 26 'Micros internal use only' DTO members, AssignDeliveryEmployee and DeliveryEmployeeAvailability both 'RFU'); (2) ccapi swagger.json (887 operations, 721 definitions, 2,283 property names), whose EMCModule table names all 128 configurable EMC modules and includes no delivery, courier, dispatch or delivery-zone module - POISON already recorded: its courier=4 is the font 'Courier New' and its driver=85 is PaymentDriver/LoyaltyDriver/StoredValueDriver; (3) the Transaction Services Gen2 spec; (4) the GloriaFood Integration Guide, 34/34 topics, courier 0/dispatch 0. The published Delivery Connectors are marketplace order INJECTION (DoorDash Marketplace, Uber Eats/Postmates, Deliveroo, Rappi, Skip), the opposite direction from this claim. No quote, fee or courier-status field returns into the check on any surface. Retrieved 2026-09-18. https://docs.oracle.com/en/industries/food-beverage/simphony/simfl/c_mobile_order_pay.htm · retrieved 2026-09-18 adversarially verified
Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator
delivery-daas-fallback
328th: MOVED TO NO, because the half of this claim that was still open closed. This note has stood at unknown because 'the claim's other half - a DaaS courier to overflow TO - is unresolved in delivery-daas-dispatch'; that cell is now a bounded no (Oracle's first-party ordering product, Mobile Order and Pay, is documented only in the Frontline Manager User Guide G49756-01 - 25 of 25 topics walked to a link fixpoint, 0 failures, 32,872 characters - and scores courier 0, dispatch 0, DoorDash 0, Uber 0, driver 0). With no DaaS hand-off to overflow to, no hybrid rule can exist. The other three inputs remain measured as absent over a complete census rather than a floor: geofence 0, latitude 0, longitude 0, GPS 0, coordinate 0 across all 7,786 sicli topics, so there is no delivery zone or boundary construct; the ccapi spec's 128-name EMCModule enumeration has no delivery-zone or wait-threshold module; and the two commands that would let driver availability drive automatic behaviour, AssignDeliveryEmployee and DeliveryEmployeeAvailability, are both marked 'RFU' in the closed 660-row OpsCommandType enumeration, i.e. reserved rather than shipped. Every shipped delivery command is a manual single-check operator action. Retrieved 2026-09-18. https://docs.oracle.com/en/industries/food-beverage/simphony/simfl/c_mobile_order_pay.htm · retrieved 2026-09-18 adversarially verified
Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator
delivery-3p-direct-integration
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
Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.
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
Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).
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
Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.
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
Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator
delivery-3p-reconciliation
Simphony reports the POS side of the claim and only the POS side. Order Channel Sales Mix is a "Menu item sales and performance report that shows order" channel detail, consisting of charts and a table showing "major group, family group, and menu item sales details" by order channel; the same book also ships Order Channel Sales and Operations, Order Channel Employee Sales and All Checks for an Order Channel. Nothing matches a marketplace PAYOUT. This kills the proposal that the payment endpoints score it: the Payout Reconciliation report in the payments book is card acquiring, scoped by "Follows Oracle Payment Cloud Service data retention", and Payout Transaction Detail drills from Payouts Summary or Reconciliation on payment-service-provider references -- these reconcile Oracle Payments deposits, not DoorDash or Uber Eats remittances. No report in the Reporting and Analytics Reports Reference -- held whole here at 223 topics, zero remaining queue -- itemizes commission or marketing fees or identifies missing/unpaid marketplace orders. Corpus date note: back-office is release 20.1. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/c_order_channel_sales_add.htm · retrieved 2026-09-05 adversarially verified
Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator
delivery-injection-error-visibility
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
Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.
delivery-tracking-page
Upheld on the guest-facing ask. The claim's own precondition is now satisfiable -- Simphony has real driver state (courier-flagged employees, per-check delivery-employee assignment, dispatch and undispatch timestamps in the reporting views) and real order state (requested, quoted and actual delivery date-times) -- so the old premise that this is marketplace injection with no fleet is dead. What is missing is the surface the guest sees. The cited enumeration is entirely operator-side: every DTO member drives a dispatch screen tab, filter or save, and no notification, SMS, status-link or tracking-URL member appears in it. Across a 1,405-page corpus of the sicli book read 2026-09-09 by href fixpoint from its own default topic, plus the Enterprise Cash Management chapter, the GloriaFood book contents and the Simphony library registry, `tracking page`, `order status page`, `track your order`, `sms link`, `status link` and `tracking url` occur zero times, tokenised and as bare substrings alike; notification reads 53 times and never once means a guest message -- it is the .NET event-notification plumbing of the extension API. The digital-ordering surface Oracle documents in this corpus, the GloriaFood integration book, covers menu, discounts, service and delivery charges, tips, order types and fulfilment time with no guest tracking page. Caveat the reader should carry: Oracle's separately documented Digital Ordering product is not in this corpus. Two limits the reader must carry. sicli is enormous -- the fixpoint had 34,883 URLs still queued when the crawl was capped at 1,400 pages -- so a corpus-wide zero here is a bounded absence, not a census. And the OpsCommandType enumeration, which IS a complete member list for its own type, is a ceiling on member NAMES ONLY: 182 of its members are documented with the single sentence 'Micros internal use only.' and carry no behavioural description at all, so the enumeration cannot bound what an undocumented member does. https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/html/2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm · retrieved 2026-09-09 adversarially verified
Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator
delivery-promise-time
REVERSES A FALSE PREMISE. The prior verdict said "No first-party delivery promise time or quote engine exists. Quote times on marketplace orders are computed by the marketplace." Simphony quotes delivery itself, on its own check record. The CheckSummaryData class carries "DeliveryQuoteTime" ("Delivery quote time in minutes"), "DeliveryQuoteType" ("Delivery quote type"), "PickupQuoteTime" ("Preparation quote time in minutes"), "PickupQuoteType", "RequestedDeliveryDateTimeLocal" ("Requested delivery date and time"), "QuotedDeliveryDateTimeLocal" ("Quoted delivery date and time") and "ActualDeliveryDateTimeLocal" ("Actual delivery date and time") — a requested / quoted / actual triple, which is a quote engine with its own accuracy measurement. OpsCommandType adds the override surface: "DeliveryQuoteTimeOverride" — "Change the delivery quote time of the current check"; "CheckQuoteTimeOverride" — "Change the prep quote time of the current check"; "DailyQuoteTimeOverride" — "Change the prep quote time for an Order Type for the rest of the day"; "ChangePickupOrDeliveryDateTime" (html_2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm). Partial, and the shortfall is exactly what the claim asks for: every documented adjustment is a MANUAL override by an operator, per check or per Order Type for the rest of the day. Nothing held states that the quote is computed from current kitchen load, courier availability or zone drive time — and there is no zone drive time to compute from, since no delivery-area construct is evidenced anywhere. The one suggestive member, "RefreshQuote", is annotated "Micros internal use only." with no description. sicli is a floor, so the dynamic half is unevidenced rather than shown absent. CITATION REPAIRED 2026-09-09: the sicli book was regenerated and every topic moved from /sicli/html_<guid>.htm to /sicli/html/<guid>.htm. The old address returned a 404 byte-identical to a fabricated control; the page itself is unchanged and still serves at 200. https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/html/eaebf60b-d691-4f9b-1241-b52a1c70465d.htm · retrieved 2026-09-09 adversarially verified
Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.
delivery-offline-behavior
330th: NEW SURFACE - the two STORE-LEVEL operator manuals and the Networking Excellence Guide, which no prior pass on this record had opened (q323-q328 read sicli, simcg, rause, ccapi, Gen2 and the back-office PDFs). Walked to an href fixpoint at 200: simmu POS Manager User Guide 92 topics, sipou POS Employee User Guide 200 topics, resnw Networking Excellence Guide 77 topics = 369 topics / 548,682 characters, 0 failures (nonsense control: this host answers an absent topic with an identical 15,118-byte 404 page). VALUE MOVED unknown -> partial because these books show Oracle DOES document offline behaviour function-by-function, and one of the claim's three conjuncts is met while two are not. MET - cash continues: simmu/c_ecm_till_offline.htm 'When a workstation that supports a cash drawer is offline, you can open a new offline till and assign or unassign users. These workstation operators can perform most Cash Management functions on an offline till session, including: Tendering transactions on guest checks ... Depositing cash: The application creates an offline bank deposit on the local workstation to accept the cash deposit', and simmu/c_ecm_server_bank_offline.htm gives the same for a server bank plus 'After the workstation re-connects online ... the application synchronizes all offline sessions and activity performed on the offline workstation'. The same books state per-function offline outcomes for Team Service (sipou/c_checks_team_service_check_handling.htm 'Transaction Handling When Offline'), events (t_events_begin_end.htm 'When a workstation is offline and has no connection to the Check and Posting Service (CAPS), events cannot start or end'), clock-in, deposits, workstation lock/unlock (Table 3-1 Workstation Offline Scenarios) and two offline-only reports. NOT MET - driver assignment and driver settlement: the delivery-agent workflow lives in simmu chapter 7 Order Information Service - c_order_information_service.htm, t_order_information_service_assign_check_delivery_agent.htm ('You can assign one or more checks to a delivery agent (also called a runner). This function transfers the check to the delivery agent ... Click the Get Check Detail button. Click the Send Request button. The check changes to the Assigned status.') and t_order_information_service_close_check_after_delivery.htm (Delivered / Delivery Failed / Delivered Without Alcohol / Cancelled) - and the word offline does not occur in any of them. Tokenised word-boundary case-insensitive over all 369 topics: 'offline' 62 hits in 20 files, 'delivery' 21 hits in 10 files, 'courier' 0, 'dispatch' 0, 'delivery dispatch' 0; the offline set and the delivery set intersect in exactly one file, the navigation toc.htm, and in no prose topic. resnw, the book whose whole subject is connectivity loss (wireless.htm, wi-fi-dependenthinderedrestricted_property.htm 'offline mode occurs more frequently in these environments'), lists the consequences as check sharing, recovery and financial discrepancies and never mentions delivery, a runner or a driver. So Simphony documents that an offline workstation can still take and cash-tender an order, and documents nothing about whether check assignment to a runner or the delivered/failed settlement functions work while offline. Retrieved 2026-09-18. https://docs.oracle.com/en/industries/food-beverage/simphony/simmu/c_ecm_till_offline.htm · retrieved 2026-09-18 adversarially verified
Digital ordering & guest-facing channels
Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.
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
Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator
digital-native-app
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
Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.
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 checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Simphony's digital checkout surface with documented upsell is the kiosk: Simphony Kiosk 26.1, released August 24, 2026, "is a guest-facing, self-service UI using core Simphony POS client functionality" whose "application supports menu browsing, item configuration, cart review, optional upsell and tips, payment, and receipt workflows", configured through the Simphony Kiosk Configurator. PARTIAL on three counts. Whether the suggestions are rules-based or personalized from order history is not documented -- 'optional upsell' is the whole of it, and the Kiosk JavaScript API (sikio) documents cart and availability events with no suggestion object. The online-ordering channel is unmeasured: the GloriaFood book simgi holds zero files in this corpus. And attach-rate reporting is absent from the Reporting and Analytics Reports Reference held whole at 223 topics. The stronger-sounding line, "Conversational ordering encourages cross-selling and upselling", is on the www.oracle.com Simphony product page and is grade C marketing, so it is not the citation here. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-09-05 adversarially verified
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
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
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
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
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
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
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
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
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
CLAIM: group ordering - a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment. VERDICT: no. Every conjunct fails and the vocabulary for each is absent from two complete corpora. EVIDENCE: `group order` = 1 of 1,357 documents and that one hit is POISON - marketing prose about large tickets, 'Clients placing large group orders that can overcrowd your kitchen' (https://www.gloriafood.com/restaurant-pre-order-system), on a page whose actual feature is scheduling for later ('Customers can order food in advance, anytime, anywhere, and schedule it for their desired time slot'), not a shared cart. `shareable` 0 of 185 GloriaFood pages and 2 of 1,172 Oracle topics, both unrelated (a menu-item and a service-charge configuration field); `split payment` 0 of 185; no per-participant cart, participant cap or per-person spend cap topic exists in the 845-topic Simphony Configuration Guide or the 33-topic GloriaFood Integration Guide. The closed channel enumeration on all 185 GloriaFood pages ('QR Code Ordering, Website Ordering, Facebook Ordering' / 'Scheduled Orders, Food Delivery, Food for Takeaway, Table Reservations, Hotel Ordering System') has no group-ordering member. BOUND: two independent corpora, both taken to 100% of their own publisher manifest today. (1) Oracle's own DITA book manifests: every topic href in the toc.htm of six Simphony/Back-Office books was fetched live, 1,172 of 1,172 at HTTP 200, 17 MB HTML / 2.60 MB stripped text - simcg Configuration Guide 845 topics, rause Reporting and Analytics User Guide 169, sical Client Deployment 57, gnlug Gift and Loyalty 40, simgi GloriaFood Integration Guide 33 (the WHOLE of Oracle's documented first-party digital-ordering surface), simsg Security Guide 28. Prior passes enumerated these TOCs by TITLE only; this is the first body-level census. Soft-200 control: simcg/t_zzz_nope_qq.htm returns 404 (a 15,118-byte error page), so the 1,172 200s are real bodies (smallest 4,635 bytes). (2) GloriaFood's own site, bounded by its sitemap.xml (186 locs) which is an href FIXPOINT - of 118 internal hrefs on a sampled page only 2 content pages (benefits-of-google-my-business-for-restaurants, gloriafood-success-stories), the 10 locale roots and 5 CSS assets sit outside it - 185 of 186 fetched at 200 (mobile-apps-for-restaurant-owners 404s), 1.11 MB stripped text. Live controls prove both corpora are readable and the vocabulary space is not dead: `google my business` fires 62 times across 51 GloriaFood pages, `SMS` 80 times across 62, `MDM` 20 times across 7 Oracle topics, `offline` 94 times across 36. POISON FOUND AND EXCLUDED: on www.oracle.com's Simphony page the only `Google` and the only `wallet` are the SAME sentence about payment instruments - 'Accept payments from consumers using the method they prefer: debit cards, credit cards, Apple Pay, Samsung Wallet, and Google Pay' - so an untokenised Google/wallet search over Oracle marketing manufactures a false positive; the single `group order` hit in the GloriaFood corpus is marketing prose about big tickets ('Clients placing large group orders that can overcrowd your kitchen') on /restaurant-pre-order-system, not a shared cart; the single `wallet` hit there is 'an empty stomach leads to an empty pocket. Or wallet'; and `conversational` fires 41 times in 18 Oracle topics but is Simphony's CONVERSATIONAL ORDERING order-entry mode, not chat. Retrieved 2026-09-17. https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/index.html · retrieved 2026-09-17 adversarially verified
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Oracle Restaurants Suites Management Cloud Service (docs.oracle.com user guide smusg G55858-02, dcterms.created 2026-08-11; configuration guide smcfg G55857-01, 2026-07-01; retrieved 2026-09-13) is a separately named advance-ordering application for premium-suite food and beverage. It posts orders to Simphony: smcfg/connect_venue_to_simphony.htm says 'you must link your venue to Simphony by providing essential information, including your organization details and API credentials'. Conjuncts met. (1) Separate menu and pricing. smusg/menus.htm: 'You can designate whether the menu will be available for recurring orders, PAR (pre-event) orders, or both.' smusg/items.htm: 'Each serving size can have separate price points for pre-order and event day options.' (2) Lead-time rule. smusg/events_module.htm has events 'specifying attributes such as event type, template, performer or team names, event start date, event code, and pre-order cutoff time', with statuses 'Accepting Pre-Orders' and 'Pre-Orders Closed'. (3) Invoice terms. smusg/account_settings.htm: 'They can choose to either Bill to Invoice (generating an invoice for later payment) or pay by selecting one of the credit cards they have previously stored in Suites.' smcfg/venue_details_operational_settings.htm adds that 'Suites automatically authorizes the payment method for the full order amount when an event's status is set to Live'. SHORTFALLS: (a) Neither book (127 topics) documents order minimums, quotes or proposals, deposits, or ACH payment. The only 'minimum' is a suite PAR restock level, and pre-authorization is not a deposit. (b) The flow is limited to stadium and arena suites whose assigned accounts order against scheduled events. It is not a general restaurant catering channel for off-premise orders. (c) Oracle's 2026-03-18 announcement said Suites Management 'will be available initially for customers in North America within the next 12 months', and no general-availability statement was found. Hence partial. https://docs.oracle.com/en/industries/food-beverage/suites-management/latest/smusg/account_settings.htm · retrieved 2026-09-13 adversarially verified
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Via named third-party partners on Oracle's marketplace, not native. Oracle's own Simphony drive-thru page says 'The Oracle Cloud Marketplace offers a broad collection of fully vetted Simphony integration partners.' Oracle Restaurants Marketplace listing 'SoundHound AI - Automated Food Ordering for Greater Efficiency and Convenience' (created 2026-03-18; read 2026-09-12): 'SoundHound AI helps merchants maximize their revenue and efficiency with Drive-Thru, Kiosk, Call-to-Order, Text-to-Order, Scan-to-Order, In-App and In-Car Voice Ordering.' It also says: 'Integrate seamlessly with Oracle Simphony with a simple and straightforward process'. Its related documents include a press item titled 'Torchy’s Tacos Debuts SoundHound’s Voice AI Phone Ordering Across All Locations' and a report titled 'ISV Partner Validation Report_19.7_Conversational_AI'. That report's link returned 401 'PAR does not exist' on 2026-09-12, so it is unread. Checkmate listing (ItsaCheckmate, updated 2025-01-06): 'Voice AI: Provides innovative voice AI solutions for phone and drive-thru orders' and 'POS System Integration: Ensures compatibility with major POS systems like Oracle Simphony, minimizing manual entry'. SHORTFALLS: (1) no retrieved source states that a completed AI phone order is injected into Simphony without staff transcription. For SoundHound, 'integrate seamlessly' is the only POS statement, and the validation reports that might describe it could not be opened. Checkmate says only 'minimizing manual entry'. (2) Not native. (3) Partner-authored marketing copy only. https://public.marketplace.us-ashburn-1.oci.oraclecloud.com/20180828/listings/ocid1.mktpublisting.oc1.iad.amaaaaaaa6iiraaadgc4svvdjx24x6kvma53vvzbzcv5d3er2xyw3myjq6ea · retrieved 2026-09-12 adversarially verified
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Via a named, Oracle-validated third-party partner, not native. Oracle Restaurants Marketplace listing 'Presto - Leader in drive-thru voice AI' (Presto Automation; version '3.11.0 or later' released 2024-09-19, listing updated 2024-12-03; read 2026-09-12): 'Presto Voice™ integrates with the Oracle Micros POS system and becomes your AI Voice assistant for QSR drive-thru operations.' The linked Oracle Partner Validation Report (Presto, v1.5, April 2024; Oracle validation 'Complete' 17-Sep-2024) says, in the partner-provided section: 'Presto voice is a drive-thru voice assistant, driven by AI with advanced human supervision. When installed, Presto Voice interacts, takes customer drive thru orders and injects them into the Point of Sale System', with 'Check API - Order injection, Pull check' and 'Configuration API - Menu data synchronization'. The Partner Implementation Guide (v1.3) configures 'Menu Item Definitions, Family Groups, and Condiment Group Names'. The SoundHound AI Marketplace listing (created 2026-03-18) also offers 'Drive-Thru ... Voice Ordering' and says 'Integrate seamlessly with Oracle Simphony'. SHORTFALLS: (1) no escalation-to-human handoff to store staff is described by either partner. 'Advanced human supervision' is Presto's own supervision, not a crew takeover in the lane. (2) Not native to Simphony. It needs a Presto agreement and add-on licensing ('Is Add-On Licensing Required? Yes'). (3) All capability statements are partner-authored. https://public.marketplace.us-ashburn-1.oci.oraclecloud.com/20180828/listings/175816627 · retrieved 2026-09-12 adversarially verified
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
CLAIM: conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS. VERDICT: no, and the decisive evidence is affirmative rather than an absence: Oracle's own digital-ordering product instructs the operator to send SMS FROM A HANDSET THEMSELVES, which is incompatible with a platform text-to-order channel. EVIDENCE: the only SMS how-to GloriaFood publishes is titled 'SMS Marketing For Restaurants Using A Standard Phone' - 'How to do SMS marketing using a standard phone' (https://www.gloriafood.com/restaurant-ideas/sms-marketing-for-restaurants); it is outbound marketing from the operator's own handset, with no inbound order path and no platform sending. CONTROLS: `text-to-order` 0 of 1,357 documents; `text message` 5 hits in 3 GloriaFood pages, all marketing advice, and 0 in the 1,172 Oracle topics; `SMS` is live in the corpus (80 hits across 62 GloriaFood pages) yet every occurrence is marketing or notification, and in Oracle's 1,172 topics `SMS` occurs 5 times in 3 topics - two payment-driver topics where SMS is the payment service-model abbreviation, and one MFA topic. Gift and Loyalty's coupon Issue Instructions enumeration (Issue at POS Terminal / Not Issued at POS Terminal / Issued by Email) likewise has no SMS member. BOUND: two independent corpora, both taken to 100% of their own publisher manifest today. (1) Oracle's own DITA book manifests: every topic href in the toc.htm of six Simphony/Back-Office books was fetched live, 1,172 of 1,172 at HTTP 200, 17 MB HTML / 2.60 MB stripped text - simcg Configuration Guide 845 topics, rause Reporting and Analytics User Guide 169, sical Client Deployment 57, gnlug Gift and Loyalty 40, simgi GloriaFood Integration Guide 33 (the WHOLE of Oracle's documented first-party digital-ordering surface), simsg Security Guide 28. Prior passes enumerated these TOCs by TITLE only; this is the first body-level census. Soft-200 control: simcg/t_zzz_nope_qq.htm returns 404 (a 15,118-byte error page), so the 1,172 200s are real bodies (smallest 4,635 bytes). (2) GloriaFood's own site, bounded by its sitemap.xml (186 locs) which is an href FIXPOINT - of 118 internal hrefs on a sampled page only 2 content pages (benefits-of-google-my-business-for-restaurants, gloriafood-success-stories), the 10 locale roots and 5 CSS assets sit outside it - 185 of 186 fetched at 200 (mobile-apps-for-restaurant-owners 404s), 1.11 MB stripped text. Live controls prove both corpora are readable and the vocabulary space is not dead: `google my business` fires 62 times across 51 GloriaFood pages, `SMS` 80 times across 62, `MDM` 20 times across 7 Oracle topics, `offline` 94 times across 36. POISON FOUND AND EXCLUDED: on www.oracle.com's Simphony page the only `Google` and the only `wallet` are the SAME sentence about payment instruments - 'Accept payments from consumers using the method they prefer: debit cards, credit cards, Apple Pay, Samsung Wallet, and Google Pay' - so an untokenised Google/wallet search over Oracle marketing manufactures a false positive; the single `group order` hit in the GloriaFood corpus is marketing prose about big tickets ('Clients placing large group orders that can overcrowd your kitchen') on /restaurant-pre-order-system, not a shared cart; the single `wallet` hit there is 'an empty stomach leads to an empty pocket. Or wallet'; and `conversational` fires 41 times in 18 Oracle topics but is Simphony's CONVERSATIONAL ORDERING order-entry mode, not chat. Retrieved 2026-09-17. https://www.gloriafood.com/restaurant-ideas/sms-marketing-for-restaurants · retrieved 2026-09-17 adversarially verified
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
CLAIM: Order with Google - the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option, ideally 'Preferred by Business'. VERDICT: no. This is the first POSITIVE statement of the absence rather than a failure to find one. EVIDENCE: Oracle's first-party digital-ordering product (GloriaFood, Oracle-owned, documented by Oracle as the simgi book) publishes its OWN instruction for what an operator should do about Google, and it is a manual listing claim with the ordering site in the website field - not link provisioning: 'IMPORTANT: Make sure the website you have online ordering activated on is the URL domain that you will mention on your Google business page as your business website' (https://www.gloriafood.com/restaurant-ideas/google-my-business-for-restaurants). The same page's how-to is 'Step 1: Create a Google account... Step 2: Go to Google My Business and add your business listing', and it closes 'Get these things done and enjoy improved visibility on Google!' - visibility, not an ordering action. The product's own channel enumeration, repeated in the nav of all 185 pages, is closed and has no Google member: 'Food ordering: Overview, QR Code Ordering, Website Ordering, Facebook Ordering' plus 'Restaurant Services: Scheduled Orders, Food Delivery, Food for Takeaway, Table Reservations, Hotel Ordering System'. The 33 publishing/setup topics of Oracle's GloriaFood Integration Guide (https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/) hold zero `google` of any kind. CONTROLS (tokenised, case-insensitive, word-boundary, over both corpora = 1,357 documents): `order with google` 0; `reserve with google` 0; `preferred by business` 0; `google business profile` 1 - the GloriaFood page above, naming the listing, not provisioning an order link. Every `google` inside the 1,172 Oracle topics is simsg's Android OS security chapter (6) or rause's supported-browser list (2). BOUND: two independent corpora, both taken to 100% of their own publisher manifest today. (1) Oracle's own DITA book manifests: every topic href in the toc.htm of six Simphony/Back-Office books was fetched live, 1,172 of 1,172 at HTTP 200, 17 MB HTML / 2.60 MB stripped text - simcg Configuration Guide 845 topics, rause Reporting and Analytics User Guide 169, sical Client Deployment 57, gnlug Gift and Loyalty 40, simgi GloriaFood Integration Guide 33 (the WHOLE of Oracle's documented first-party digital-ordering surface), simsg Security Guide 28. Prior passes enumerated these TOCs by TITLE only; this is the first body-level census. Soft-200 control: simcg/t_zzz_nope_qq.htm returns 404 (a 15,118-byte error page), so the 1,172 200s are real bodies (smallest 4,635 bytes). (2) GloriaFood's own site, bounded by its sitemap.xml (186 locs) which is an href FIXPOINT - of 118 internal hrefs on a sampled page only 2 content pages (benefits-of-google-my-business-for-restaurants, gloriafood-success-stories), the 10 locale roots and 5 CSS assets sit outside it - 185 of 186 fetched at 200 (mobile-apps-for-restaurant-owners 404s), 1.11 MB stripped text. Live controls prove both corpora are readable and the vocabulary space is not dead: `google my business` fires 62 times across 51 GloriaFood pages, `SMS` 80 times across 62, `MDM` 20 times across 7 Oracle topics, `offline` 94 times across 36. POISON FOUND AND EXCLUDED: on www.oracle.com's Simphony page the only `Google` and the only `wallet` are the SAME sentence about payment instruments - 'Accept payments from consumers using the method they prefer: debit cards, credit cards, Apple Pay, Samsung Wallet, and Google Pay' - so an untokenised Google/wallet search over Oracle marketing manufactures a false positive; the single `group order` hit in the GloriaFood corpus is marketing prose about big tickets ('Clients placing large group orders that can overcrowd your kitchen') on /restaurant-pre-order-system, not a shared cart; the single `wallet` hit there is 'an empty stomach leads to an empty pocket. Or wallet'; and `conversational` fires 41 times in 18 Oracle topics but is Simphony's CONVERSATIONAL ORDERING order-entry mode, not chat. Retrieved 2026-09-17. https://www.gloriafood.com/restaurant-ideas/google-my-business-for-restaurants · retrieved 2026-09-17 adversarially verified
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
CLAIM: Apple Business Connect ordering placement - an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow. VERDICT: no. EVIDENCE: `apple business connect` = 0 and `apple maps` = 0 across BOTH complete corpora (1,172 Oracle topic bodies and 185 GloriaFood pages). Oracle's GloriaFood Integration Guide is now held whole (33 of 33 topics, fetched at 200), and the only Apple surface named anywhere in the product's own closed channel enumeration is the branded iOS app; the place-card / custom-action vocabulary does not exist in either publisher's text. That enumeration is closed and published on every one of the 185 pages: 'Food ordering: Overview, QR Code Ordering, Website Ordering, Facebook Ordering' + 'Restaurant Services: Scheduled Orders, Food Delivery, Food for Takeaway, Table Reservations, Hotel Ordering System'. BOUND: two independent corpora, both taken to 100% of their own publisher manifest today. (1) Oracle's own DITA book manifests: every topic href in the toc.htm of six Simphony/Back-Office books was fetched live, 1,172 of 1,172 at HTTP 200, 17 MB HTML / 2.60 MB stripped text - simcg Configuration Guide 845 topics, rause Reporting and Analytics User Guide 169, sical Client Deployment 57, gnlug Gift and Loyalty 40, simgi GloriaFood Integration Guide 33 (the WHOLE of Oracle's documented first-party digital-ordering surface), simsg Security Guide 28. Prior passes enumerated these TOCs by TITLE only; this is the first body-level census. Soft-200 control: simcg/t_zzz_nope_qq.htm returns 404 (a 15,118-byte error page), so the 1,172 200s are real bodies (smallest 4,635 bytes). (2) GloriaFood's own site, bounded by its sitemap.xml (186 locs) which is an href FIXPOINT - of 118 internal hrefs on a sampled page only 2 content pages (benefits-of-google-my-business-for-restaurants, gloriafood-success-stories), the 10 locale roots and 5 CSS assets sit outside it - 185 of 186 fetched at 200 (mobile-apps-for-restaurant-owners 404s), 1.11 MB stripped text. Live controls prove both corpora are readable and the vocabulary space is not dead: `google my business` fires 62 times across 51 GloriaFood pages, `SMS` 80 times across 62, `MDM` 20 times across 7 Oracle topics, `offline` 94 times across 36. POISON FOUND AND EXCLUDED: on www.oracle.com's Simphony page the only `Google` and the only `wallet` are the SAME sentence about payment instruments - 'Accept payments from consumers using the method they prefer: debit cards, credit cards, Apple Pay, Samsung Wallet, and Google Pay' - so an untokenised Google/wallet search over Oracle marketing manufactures a false positive; the single `group order` hit in the GloriaFood corpus is marketing prose about big tickets ('Clients placing large group orders that can overcrowd your kitchen') on /restaurant-pre-order-system, not a shared cart; the single `wallet` hit there is 'an empty stomach leads to an empty pocket. Or wallet'; and `conversational` fires 41 times in 18 Oracle topics but is Simphony's CONVERSATIONAL ORDERING order-entry mode, not chat. Retrieved 2026-09-17. https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/index.html · retrieved 2026-09-17 adversarially verified
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
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
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Gift and Loyalty User Guide (release 20.1), 'Setting Up Reloading Meal Cards', a book-level page previously uncited by this record. It configures a per-period recurring value entitlement on a stored-value account: the operator enters 'Period Reload Amount' and 'Period Carry over Amount' on the Gift or Debit/Credit/Award tab. PARTIAL because this is the entitlement half only -- the book documents no recurring BILLING of the guest, no paid loyalty tier, and no delivery-fee-waiver membership; the nearest related page in the same book sets up membership discount cards, again with no subscription charge. Anything stronger would have to come from the CrowdTwist library, which was not mined this session. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_using_mealcard.htm · retrieved 2026-09-05 adversarially verified
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
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
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
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 uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
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 channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
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 data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
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
Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator
guest-loyalty-thirdparty-identity-attach
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. || 323rd: 323rd, NEW SURFACE, CELL NOT MOVED. The existing note's open question is 'Oracle publishes no schema for the inbound order payload'. Oracle does publish an anonymous order-capture schema - the Simphony Transaction Services Gen2 API spec at https://docs.oracle.com/en/industries/food-beverage/simphony/omsstsg2api/swagger.json (info.version 2026.08.15, 297,397 bytes, 30 paths, 36 operations, 110 definitions; soft-404 control: sibling books answer /swagger.json with an identical 15,118-byte HTML 404) - and IT CARRIES NO GUEST IDENTITY AT ALL. The 110 definitions were listed: there is no Customer, Guest, Member, Profile or Loyalty definition among them. CheckHeader's complete property list is orgShortName, locRef, rvcRef, checkRef, idempotencyId, checkNumber, checkName, checkEmployeeRef, orderTypeRef, orderChannelRef, tableName, tableGroupNumber, openTime, fireTime, pickupTime, guestCount, language, isTrainingCheck, informationLines, paymentStoreId, status, preparationStatus, isCachedResponse - guestCount is a NUMBER OF COVERS, not an identity, and that is the trap in this cell. The only place an integrator can put a name is the free-text ExtensionItem (appName/dataName/dataType/data) or informationLines, neither of which is a profile key. WHY STILL UNKNOWN: Gen2 is the API a partner calls, whereas the marketplace orders in this claim arrive through the Delivery Connectors, whose inbound payload Oracle still does not publish; a zero on the wrong pipe cannot carry the no. Retrieved 2026-09-17. || 330th: 330th: NEW SURFACE - the store-level POS Employee and Manager user guides (sipou 200 topics, simmu 92, walked to an href fixpoint at 200, 0 failures) show what a marketplace order actually looks like to the staff who handle it, and it is a channel label, not an identity. sipou/c_checks_order_channel_change.htm: 'An order channel is where an order is placed. For example, guests can place an order at a kiosk, a drive thru window, inside a restaurant, or via a delivery aggregator. A default channel is assigned to checks, but can be changed if buttons have been configured on the POS ... If configured, the order channel appears in the check header.' That is the ONLY occurrence of 'aggregator' in the 428 topics of sipou+simmu+resnw+sical (665,708 characters); 'marketplace' 0, 'third-party delivery' 0, 'guest profile' 0, 'DoorDash' 0, 'Uber Eats' 0, 'Deliveroo' 0. The loyalty chapter in the same book identifies a guest only by manual operator action - t_loyalty_apply_card_check.htm and t_loyalty_balance_inquiry.htm work from a scanned or keyed account/card number, a guest name or a phone number the operator types - so nothing in the store-level workflow attaches a marketplace guest to a loyalty account automatically. WHY STILL UNKNOWN, unchanged from the 323rd: this is again the outbound/operator end of the pipe. Oracle does not publish the Delivery Connectors INBOUND order payload, the connectors are Oracle's own unpublished partner integrations rather than a documented partner API, and a zero on every published surface cannot bound what an unpublished payload carries. Retrieved 2026-09-18. adversarially verified
Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.
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
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
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
Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator
guest-loyalty-offline-behavior
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
Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator
guest-loyalty-offer-stacking-rules
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
Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator
guest-loyalty-targeted-offers
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
Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator
guest-loyalty-rfm-segmentation
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
Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.
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
Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator
guest-loyalty-native-email-sms
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
Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.
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
Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.
guest-loyalty-10dlc-registration
327th: MOVED unknown -> no. This cell's note has never been re-checked against the corpora the 323rd-326th built, and it is the cheap check the brief asks for. CLAIM: handles or explicitly documents A2P 10DLC brand and campaign registration. VERDICT: no - Oracle documents no SMS SENDING SURFACE AT ALL for Simphony or for Gift and Loyalty, so there is nothing to register, and no registration guidance is published. EVIDENCE: the complete 40-topic Gift and Loyalty User Guide contains no campaign, message or messaging topic - the token 'campaign' scores ZERO across all 40 topics - and its issuance surface is the coupon configuration page's Issue Instructions (POS / non-POS / email) plus card-number account management. BOUND: two censuses, both bound to a publisher manifest. (1) THE SIMPHONY / BACK-OFFICE CORPUS held on disk from the 323rd-326th, re-grepped as one body for the first time: 9,045 documents / 29,944,553 characters, being the complete sicli POS Client (.NET) Extension API book (7,786 of 7,786 topics from its own fti/FTI_Files.json manifest), the complete Gift and Loyalty User Guide gnlug (40 of 40 topics - re-derived today from https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/toc.htm, which lists exactly 40 .htm links, all held), the Configuration Guide simcg (845), Reporting and Analytics rause (169), sical (57), simsg (28), the GloriaFood guide simgi (33), the ccapi Configuration and Content API swagger (887 operations / 721 definitions) and the Gen2 Transaction Services swagger, ssimm, and the seven PDF-only back-office books (glpoa, lmapi, lmsch, impoa, immda, dacsr, invsg). Positive control: 'Simphony' 18,149 hits in 8,261 files. (2) A NEW CENSUS THIS PASS of Oracle's loyalty engagement product: every monthly Release Readiness book listed on https://docs.oracle.com/en/industries/food-beverage/crowdtwist-loyalty-engagement/releases.html (36 months, Jan 2023 - the current release) walked from each book's own index to a link fixpoint = 164 files / 212,952 characters, 0 failures; nonsense control .../crowdtwist-loyalty-engagement/9999 returns the host's 15,118-byte HTML 404. Positive control: 'CrowdTwist' 448 hits in 144 files, 'campaign' 34 in 16. This is the surface prior notes on this record repeatedly flagged as 'a reachable-but-unmined sibling library'; it is now measured. CONTROLS, tokenised, word-boundary, case-insensitive, over BOTH censuses: '10DLC' 0, 'A2P' 0, 'brand registration' 0, 'campaign registration' 0, 'carrier' 0, 'toll-free' 0, 'short code' 0 in the CrowdTwist census, 'text message' 0, 'Twilio' 0, 'marketing automation' 0, 'email marketing' 0, 'SMS' 0 in the 36-month CrowdTwist census. POISON NAMED, because each would flip a naive grep: 'SMS' scores 5 in the Simphony corpus and all five are non-loyalty - two payment-driver topics (simcg topic_payment_driver_config, t_payment_driver_add_spi, where SMS is part of the Simphony Payment Interface vocabulary) and the Security Guide's multi-factor authentication topic; 'short code' scores 15 in the Simphony corpus and every one is an EMC event short code (simcg t_events_create / t_events_linking and sicli members), not a carrier short code; 'opt-in' hits are campaign enrolment in CrowdTwist ('Commerce campaigns can now require a member to opt-in prior to being eligible'), which is consent to a bonus, not carrier consent. Retrieved 2026-09-18. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_coupon_configuring.htm · retrieved 2026-09-18 adversarially verified
Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator
guest-loyalty-campaign-attribution
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
Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator
guest-loyalty-data-export-portability
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
Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator
guest-loyalty-cdp-event-api
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
Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator
guest-loyalty-review-capture-routing
The Simphony plug-ins catalogue (page current to 2026-08-27; this Dynamic Barcode entry is version 19.7.3.1, released August 12, 2026) documents a shipped post-transaction feedback TRIGGER: Simphony Dynamic Barcode 'prints configurable QR codes, EAN-13 and Code 128 barcodes, and survey codes in guest check and receipt headers or trailers', with transaction-specific payloads. Corroborated on the configuration side by the Gift and Loyalty organization-configuration page in gnlug, which exposes Web Survey and POS Survey selectors. PARTIAL because the second half of the cell is unevidenced: neither document describes response capture, score thresholds, routing of low scores to private service recovery, or routing of high scores to public review sites. This URL is already cited 11x in claims.jsonl; the Dynamic Barcode survey-code sentence is what is new here, not the page. https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html · retrieved 2026-09-05 adversarially verified
Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.
guest-loyalty-referral-program
About Oracle CrowdTwist Loyalty and Engagement, a separately licensed Oracle loyalty product. Oracle markets it for restaurants with a Simphony link: www.oracle.com/food-beverage/loyalty-engagement/ (Wayback capture 2025-12-09) says 'Servers can effortlessly enroll new members, check a guest's loyalty status, and instantly redeem rewards—all through the POS.' and 'Native Simphony integration'. The CrowdTwist user documentation (docs.oracle.com crowdtwist-user, dcterms.created 2026-07-02, retrieved 2026-09-13) documents a member referral mechanic. Per-member link. Help/ControlCenter/Program/Widgets/CreatingInviteFriendsWidgets.htm: 'The invite friends widget allows users to invite their friends to the program. The widget generates a link that can be shared with friends through email or any preferred channel.' Help/ControlCenter/Program/Widgets/Widgets.htm: 'Invite Friends - Allows members to refer friends to join the program via referral link.' Attribution. Help/ControlCenter/Program/EmailStyles/EmailStyles.htm: 'Invite Friend Registration Accepted - Informs members the friend they sent a referral URL link to joined the loyalty program.' Referrer reward. Help/GettingStarted/Activities/EngagementActivities.htm lists 'Invite friend activities' with 'Earn points for referring a friend to the loyalty program via: Custom link Social networks Earn points when friends accept the invitation'. Help/ControlCenter/Rewards/AutomaticRewards/AutomaticRewards.htm gives the example 'Create an automatic segment campaign for all members who made 2 purchases and also referred 3 friends in the last month.' SHORTFALLS: (1) Attribution is to the friend's program registration, not to the referred guest's first order. (2) No reward for the referred friend is documented, so the mechanic is not shown to be two-sided. (3) The mechanic belongs to a separately licensed product, not to Simphony. No CrowdTwist documentation topic names Simphony, so the Simphony link rests on Oracle marketing only, hence grade C. The 110 topics read are a floor, not a census, because the library's table-of-contents and sitemap routes redirect away. Hence partial. https://docs.oracle.com/en/cloud/saas/marketing/crowdtwist-user/Help/ControlCenter/Program/Widgets/CreatingInviteFriendsWidgets.htm · retrieved 2026-09-13 adversarially verified
Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator
guest-loyalty-wallet-pass
330th: THE LAST UNBOUNDED ISSUER IS NOW BOUNDED - ORACLE'S OWN CONSUMER APP CATALOGUE. Every prior pass ended by saying the guest-facing side was unenumerated. Oracle America, Inc. (artistId 284793707) publishes 61 iOS apps in the US store, listed in full anonymously via itunes.apple.com/lookup?id=284793707&entity=software&country=us&limit=200: Fusion Applications, Mobile Authenticator, NetSuite, Fusion Expenses, MICROS inMotion, SuiteProjects Pro, OCI, Field Service, Clinical AI Agent, Workforce Management, Primavera P6/Unifier/Cloud, Self-Service HR, Content, Events, CRM On Demand, CX Sales, Management Cloud, Aconex, Mobile Field Service, Timecards, Cloud On Call, Approvals, SuiteCommerce InStore, WebCenter, Oracle Analytics (Deprecated), JD Edwards, iProcurement, Siebel, Supply Chain, WebCenter Content, Sauce Video, Maintenance, Inventory, Hotel Mobile, Procurement, Sales Orders, Mobile SCM, Yard, Health Patient Portal, Enterprise Manager Mobile, Discrete/Process Prod Supervisor, MWM and MWM+, Live Experience, Time Clock, Public Safety Suite and Wearable, Instantis, Quality Manager, Inspector, Hospitality Smart Crew, Municipal Code Officer, Store Operations Cloud Service and the nursing agents. Every one is an employee/operator or enterprise tool: Oracle ships NO guest-facing food-and-beverage loyalty app and no wallet-pass issuer of any kind. VALUE MOVED unknown -> no on the union of five independent, separately bounded censuses that all score zero for the artefact: (a) the Gift and Loyalty user guide gnlug 40/40 and the Simphony + back-office corpus, 9,045 documents / 29,944,553 characters, 'Apple Wallet' 0, 'Google Wallet' 0, 'pkpass' 0; (b) the Gift and Loyalty POS Web Services API E91264-08, wallet/Apple/Google/pkpass/passbook/barcode/QR 0, positives 'card number' 7 and 'phone' 10; (c) the Loyalty/Stored Value Command Module Interface Reference G49743-01, wallet 0; (d) the 36-month CrowdTwist Release Readiness stream, 164 files walked to a link fixpoint, wallet 0, Apple 0, Google 0, pass 0 - three years of shipped loyalty enhancements and the member credential never becomes a provisioned OS wallet object; (e) Oracle's own consumer portal myicard.net, whose credential is 'Card Number / PIN'. A wallet pass is a marketed, documented consumer artefact; five surfaces on which it would have to appear, including the vendor's own release-note stream and its entire consumer app catalogue, carry no trace of it. BOUND: the logged-in member area of myicard.net was not enumerated (a login is a refusal), so this is a no on Oracle's published and shipped surfaces, not on a database read. Retrieved 2026-09-18. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/index.html · retrieved 2026-09-18 adversarially verified
Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.
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
Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.
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
Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator
guest-loyalty-ai-offer-recommendation
327th: MOVED unknown -> no, and the reason this cell stayed open is now retired. The existing note ends 'Oracle's marketing pages ... return 403' (false since the 323rd) and the sibling note at reporting-nl-query records the standing objection - an unmined loyalty sibling library. THAT LIBRARY IS NOW CENSUSED. CLAIM: vendor documents AI/ML-generated recommendations for offer content, target audience or send timing, shipped rather than roadmap. VERDICT: no. EVIDENCE: targeting in Oracle's restaurant loyalty product is wholly operator-authored and deterministic - the Gift and Loyalty rule reference configures Precedence, Point Thresholds, Balance Use Types and eligibility item/time rules - and the 36-month shipped-feature history of Oracle's loyalty engagement product (now branded 'Oracle Unified Loyalty (CrowdTwist)') is the same shape: the enhancements it actually ships are Badges, Bonus Campaigns 'Bonusing Based on Multiple Products Purchased', Frequency Capping, Opt-In Commerce/Activity Campaigns, Product Catalog re-architecture and an Xstore plug-in, i.e. rule and eligibility mechanics, with no generated content, no modelled audience and no send-time optimisation in any month. BOUND: two censuses, both bound to a publisher manifest. (1) THE SIMPHONY / BACK-OFFICE CORPUS held on disk from the 323rd-326th, re-grepped as one body for the first time: 9,045 documents / 29,944,553 characters, being the complete sicli POS Client (.NET) Extension API book (7,786 of 7,786 topics from its own fti/FTI_Files.json manifest), the complete Gift and Loyalty User Guide gnlug (40 of 40 topics - re-derived today from https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/toc.htm, which lists exactly 40 .htm links, all held), the Configuration Guide simcg (845), Reporting and Analytics rause (169), sical (57), simsg (28), the GloriaFood guide simgi (33), the ccapi Configuration and Content API swagger (887 operations / 721 definitions) and the Gen2 Transaction Services swagger, ssimm, and the seven PDF-only back-office books (glpoa, lmapi, lmsch, impoa, immda, dacsr, invsg). Positive control: 'Simphony' 18,149 hits in 8,261 files. (2) A NEW CENSUS THIS PASS of Oracle's loyalty engagement product: every monthly Release Readiness book listed on https://docs.oracle.com/en/industries/food-beverage/crowdtwist-loyalty-engagement/releases.html (36 months, Jan 2023 - the current release) walked from each book's own index to a link fixpoint = 164 files / 212,952 characters, 0 failures; nonsense control .../crowdtwist-loyalty-engagement/9999 returns the host's 15,118-byte HTML 404. Positive control: 'CrowdTwist' 448 hits in 144 files, 'campaign' 34 in 16. This is the surface prior notes on this record repeatedly flagged as 'a reachable-but-unmined sibling library'; it is now measured. CONTROLS over BOTH censuses, tokenised: 'machine learning' 0, 'artificial intelligence' 0, 'AI' 0 (word-boundary, across all 29,944,553 characters), 'generative' 0, 'propensity' 0, 'predictive' 0, 'next best' 0, 'send time' 0, 'recommendation' 3 in the Simphony corpus and 0 in the CrowdTwist census. POISON NAMED: 'suggested' scores 51 in the Simphony corpus and every sampled hit is prose or a field label, not a machine suggestion - glpoa's 'It is suggested that 30 seconds be used for persistent IP connections', simcg's PAR Level Set 'suggested quantity to maintain of each currency denomination' and the Opera topic's 'configure suggested tips'; 'personalized' in CrowdTwist is one Xstore receipt-messaging line. SCOPE, STATED HONESTLY: the one AI feature Oracle does market for this product, Simphony Smart Assistant, was read in the 323rd and is a documentation/knowledge-base assistant that the same page says 'is available to early adopters' - explicitly excluded by this claim's wording. Retrieved 2026-09-18. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/c_rule_reference_loyalty.htm · retrieved 2026-09-18 adversarially verified
Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.
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 & workforce
Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.
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
Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator
labor-photo-punch-verification
KILLS THE PROPOSED yes. The DigitalPersona licence and the sicli FingerPrint class are a fingerprint reader, which is neither a photo at punch nor facial verification, and the cell explicitly wants a photo-only mode storing no biometric template — a fingerprint reader is the opposite (a stored template). The employee-identification mechanisms are enumerated device-by-device in the hardware feature tables, and a camera is never one of them: the Tablet 721P feature table says of the MSR 'Reads magnetic stripe cards for employee sign in, authorization, and loyalty programs' while the camera row says only 'Use to take photographs'; the Workstation 820 feature table (micros-workstation-8/weset/c_basic_features.htm) says of the RFID scan area 'Reads MICROS Contactless Employee ID Cards for employee sign in'. The .NET extension API's only camera surface is barcode scanning ('Opens the camera on an Android device to allow scanning of a barcode'). 'facial' returns zero hits across all 4,840 corpus documents and 'face recogn' returns exactly one — 'Setting face recognition' in the Lenovo Tab K10 end-user manual, an Android device-unlock feature of a validated handset, not a punch record: no document attaches a captured image to a timecard entry. https://docs.oracle.com/en/industries/food-beverage/micros-tablet-700-series/latest/tabss/c_tablet_721p_features.htm · retrieved 2026-09-05 adversarially verified
Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.
labor-geofenced-mobile-punch
324th, CELL MOVED unknown -> no/A on THREE new machine-readable censuses the prior passes never held. CLAIM: mobile clock-in restricted by geofence or location validation. VERDICT: no. EVIDENCE (1) CONFIGURATION SURFACE -- the Simphony Configuration and Content API swagger (https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/swagger.json, retrieved 2026-09-17, 5,214,948 bytes, version 2026.06.15, 887 paths/887 operations, 721 definitions) is Oracle's own complete object model of EMC configuration. The ONLY location restriction it defines on punching is logical, not geographic: Employee_properties_optionsExt has exactly 3 properties, two of them 'limitClkInToWorkstationsInTheClkInRVC' -- 'Flag indicating to prevent the employee from clocking in unless the revenue center of the Clock-In Cycle matches the revenue center on the workstation' -- and 'limitClkOutToWorkstationsInTheClkOutRVC'. LocationParams_timekeeping has exactly 4 properties: enableLaborManagement, propertyLaborManagementURL, printWTDTotalsInClockInOutChits, printAccumulatedLaborShiftTotalsInClockInOutChits. There is no radius, fence, coordinate, site-boundary or device-location option on any employee, employee-class, role or timekeeping object. (2) PERSISTENCE SURFACE -- Oracle Restaurants Database Access Cloud Service Reference Guide G21944-03 September 2025 (https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/dacsr/G21944_03.pdf, 1,164,316 bytes, 102 VRO_* views, every view given field-by-field with Field/Field Type/Description). The row a punch becomes carries no geography in either data model: VRO_TIME_CARD_DETAIL_V1 ('closed employee time card detail information from each location') = TIMECARDDETAILID, ORGANIZATIONID, LOCATIONID, REVENUECENTERID, BUSINESSDATE, HREMPLOYEEID, JOBCODEID, CLOCKINDATETIME, CLOCKOUTDATETIME, REGULARHOURS/PAY, OVERTIME1-4 HOURS/PAY, sales and tip totals, CLOCKINSTATUS, CLOCKOUTSTATUS, POSRESETDATETIME, laborPeriodClosedFlag, adjustedTimeCardFlag, pay rates, authorizingHrEmployeeID, REASONCODEID; VRO_LM_TIME_CARD_DETAIL_V1 ('time tracking information (Labor Management only)') is the same shape plus payAtMinimumWage and CLOCKINGMTDATETIME. CLOCKINSTATUS is a CLOSED code list of 14 values -- 0 None, 65 Early from Break, 66 On Break, 67 Late from Break, 68 Schedule Disabled, 69 Early, 73 Inserted, 76 Late, 77 Manager Clock Out, 78 Not Scheduled, 80 On Paid Break, 82 Revenue Center Change, 84 On Time, 85 Auto Clock Out -- with no off-site, out-of-area or location-violation status. (3) REST SURFACE -- Labor Management API Programmer's Guide E90995-32 (back-office/20.1/lmapi/E90995_32.pdf, 672,800 bytes) GET /rest/services/v1/locations/{locationRef}/timecards takes only startBusinessDate/endBusinessDate and returns businessDate, clockInStatus, clockOutStatus, clockInDateTime, clockOutDateTime, externalPayrollId, tips, timecardId, jobCodeRef, shiftType, receipts -- no coordinate. The Labor Management RESTful API and Supporting Interfaces Guide E90996-16 (lmsch/E90996_16.pdf) gives the job-definition clock-in payload field by field -- clockinprivilege, declaredirecttipsonclockout, declareindirecttipsonclockout, allowearlylateclockout, printtips, each mapped to 'Human Resources | Admin | Job Definitions' -- again with no location rule. BOUND/CONTROLS: tokenised, word-boundary, case-insensitive controls over all five documents (ccapi swagger 5.21 MB + G21944_03 239 KB + E90995_32 196 KB + E90996_16 53 KB) return ZERO for geofence, geofencing, geolocation, GPS, coordinates, proximity(*), beacon in the four PDFs. POISON NAMED AND CONTROLLED: 'latitude' and 'longitude' DO occur 36 times each in the swagger -- a naive search would have produced the opposite verdict -- but they occur on exactly 8 definitions, all of them site address records (Location, Locationv2, LocationInsertRequestBody, LocationUpdateRequestBody, RevenueCenterInsert/Update/GETv1/GETv2, alongside address1..3, city, stateOrRegion, zipOrPostalCode, countryCode), and on none of the 85 Employee/Role/Job definitions. 'proximity' occurs 8 times in G21944_03 and is the card entry mode ('Proximity via ICC', 'Proximity via Magnetic Stripe'), not location. RESIDUAL: this bounds Oracle's own configuration, persistence and REST surfaces; the InMotion Mobile client's own user guide is not inside this bound, but a fence that gated a punch would have to be configured in one of these objects and recorded in one of these columns, and is in neither. Retrieved 2026-09-17. https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/swagger.json · retrieved 2026-09-17 adversarially verified
Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator
labor-offline-time-punch
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
Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.
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
Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.
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
Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator
labor-native-scheduling
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
Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator
labor-demand-labor-forecast
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
Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator
labor-realtime-labor-percent
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
Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator
labor-overtime-prevention
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
Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator
labor-break-compliance-by-state
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
Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.
labor-fair-workweek-support
The location-configuration page enumerates every compliance rule set that can be assigned to a location: Labor Pay Rule, Pay Period Calendar, Wage and Tip Law ('Compliance with regional wage laws and tip laws'), Child Labor Law, Tip Pool, and 'Time card adjustment acknowledgement required'. No predictive-scheduling or advance-notice rule set exists in that list. 'predictab', 'advance notice', 'fair work' and 'predictability pay' return zero hits across all 4,840 corpus documents; the only 'premium pay' is a manually configured pay-rate modifier for 'night shifts, holiday work, Sunday work, and standby duty' (lmusg/c_config_pay_premium.htm), not a calculated predictability penalty. Schedules are published and approved (lmusg 'Can Edit Approved Schedule') but no advance-notice deadline is tracked. The gap that kept this cell unknown is now closed: the record's prior rationale left it undetermined because 'the Labor Management Scheduler RESTful API guide (back-office/20.1/lmsch) is published as a PDF I could not text-extract'. That PDF is held and text-extracted in this corpus (lmsch/E90996_16.pdf, 37,567 characters) and contains no advance-notice, predictability or fair-workweek field. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/t_config_locations.htm · retrieved 2026-09-05 adversarially verified
Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.
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
Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.
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
Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.
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
Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator
labor-qualified-tips-w2-reporting
PARTIAL — the tip-type separation is real, the 2026 W-2 apparatus is not. The Get time card details endpoint (Business Intelligence API, a registry-closed 56-endpoint census) separates the tip classes at the timecard level: 'chrgTips ... The value of tips posted to charge payments such as credit cards or room charges', alongside direct and indirect (cash) tips, while the payroll handoff key 'External Payroll ID' sits on the sibling Get Employee Dimensions endpoint (https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/biapi/op-bi-v1-orgidentifier-getemployeedimensions-post.html), 'External payroll id for the employee.'. What is absent from that field census, and from the whole corpus, is any Treasury tipped-occupation code, any 'Box 12', and any code TP: 'occupation' matches only lmusg prose about 'a labor category for tipped employees and a labor category for non-tipped employees', which is a reporting label the operator invents, not a Treasury code. Corpus date: back-office release 20.1; the endpoint's own version stamps run to 20.1.14.13. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/biapi/op-bi-v1-orgidentifier-gettimecarddetails-post.html · retrieved 2026-09-05 adversarially verified
Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator
labor-native-payroll
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
Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).
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
Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator
labor-shift-swap-workflow
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
Provides digital new-hire onboarding that collects W-4 and I-9 documentation and supports E-Verify submission.
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
Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator
labor-server-performance-metrics
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, purchasing & cost control
Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.
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
Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.
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
Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator
inventory-theoretical-vs-actual
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
Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator
inventory-realtime-depletion
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
Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator
inventory-86-auto-sync
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
Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.
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
Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.
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
Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator
inventory-vendor-catalogs-edi
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
Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator
inventory-invoice-ocr
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
Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator
inventory-price-change-alerts
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
Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator
inventory-par-auto-suggest
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
Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.
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
Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.
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
Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.
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
Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.
inventory-lot-traceability
324th, CELL MOVED unknown -> no/A. The existing note's stated blocker was that the Inventory Management item page 'claims no completeness'. Two never-opened Oracle API guides supply the completeness the user guide did not: they define every field of every data structure Inventory Management exchanges, and neither carries a lot or batch dimension. CLAIM: capture lot/batch at receiving and link through production to sales/transfers for a recall trace. VERDICT: no. EVIDENCE (1) Oracle MICROS Inventory Management Master Data Web Services API, E91249-09, Release 8.0, August 2023 (https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/impoa/E91249_09.pdf, 329,765 bytes): 22 numbered parameter tables covering the whole master-data payload -- MasterData, Unit, UnitConversion, ItemGroup, OverGroup, MajorGroup, Item, ItemCostCenterAssignment, Vendor, PriceQuote, PriceQuoteOffer, Customer, RecipeGroup, Recipe, RecipeIngredient, Result, plus the ConversionOperation/CountInterval/OverGroupType enumerations. Table 10, the full Item structure, is SEVEN properties: Number, Name, UnitNumber, ItemGroupNumber, CountInterval, CostCenterAssignments, Active. No lot, batch, serial, trace or expiry field exists on the item. (2) Oracle MICROS Inventory Management Point-of-Sale Web Services API Guide, E91248-07 (back-office/20.1/immda/E91248_07.pdf, 368,340 bytes): 40 parameter tables. The RECEIVING document is Table 37 Receipt = ReceiptID, VendorID, VendorTaxID, Number, Date, NetValue, VATValue, GrossValue, DocumentType (Normal or RTV), CostCenterList -- no lot capture at receipt. The STOCK record is Table 30 StockOnHand = CostCenter, ItemNumber, Item, Qty, where Table 27 Quantity is only Amount + Unit -- stock is not lot-dimensioned, so no forward or backward trace can be constructed from it. Table 34 Transaction (the POS depletion record) = RevenueCenter, PLU, Timestamp, Qty, Total, Tax, Type, WasteCode, MenuLevel, OrderType -- no lot link from sale back to receipt. (3) Confirmed against the reporting warehouse: the Database Access Cloud Service Reference G21944-03 (dacsr/G21944_03.pdf, 102 VRO_* views, every column listed) has no lot or batch column on any view. BOUND/CONTROLS: tokenised, word-boundary, case-insensitive over E91248_07 (48,212 chars), E91249_09 (55,473) and G21944_03 (239,447): lot=0, lots=0, batch=0, batches=0, traceability=0, trace=0, recall=0, serial=0 in both inventory guides. POISON NAMED: in the warehouse reference 'batch' appears only as the enum member B37_UsvcBatch and 'recall' only as the column recalledMenuItemsCount (a re-opened menu item, a homonym of a product recall) -- both would have faked a positive on an untokenised grep. The one near-miss in the inventory guides is Recipe.ExpiresIn, 'Expiry duration in days' (Table 28), which is a recipe shelf life, not a received lot. Retrieved 2026-09-17. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/impoa/E91249_09.pdf · retrieved 2026-09-17 adversarially verified
Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.
inventory-shelf-life-expiry
PARTIAL — expiry is tracked and surfaced for prepped and thawed items, not captured at receiving. The Preparation and Thaw Pull page carries a 'Shelf Life' column, 'This column shows the length of time the item stays fresh or is usable', and a 'Perish On' column, 'This column shows the day the item is no longer usable and needs to be classified as waste' — i.e. a computed expiring-soon view, gated by the 'Preparation and Thaw Pull Reporting' user right, 'Access Preparation and Thaw Pull reporting.', which is defined on the sibling page invug/r_userrights_production.htm. Recipes carry their own expiry: 'Expires In : Enter how many days in advance the recipe can be made and used. For example, you determine cheesecake has a shelf life of three to seven days' (invug/t_recipes_create_recipe.htm), and waste groups can be keyed to expiry, 'for example, breakage, spoilage, expiration date' (invug/c_waste.htm). What is missing for a full yes is any expiration or use-by date captured against a received delivery: the receiving chapter and the item master name no such field, and no alert (as opposed to a viewed report) is documented. Corpus date: back-office release 20.1. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/c_prep_and_thawpull.htm · retrieved 2026-09-05 adversarially verified
Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.
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
Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.
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 and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator
inventory-native-not-partner
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
Reporting, BI & data access
Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.
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
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
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
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
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
Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.
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
Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.
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
Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.
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
Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator
reporting-server-scorecards
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
Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator
reporting-channel-profitability
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
Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator
reporting-multiloc-drilldown
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
Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator
reporting-custom-report-builder
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
Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.
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
Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator
reporting-raw-warehouse-export
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
Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator
reporting-public-api
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
Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator
reporting-webhooks
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
API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator
reporting-api-not-upcharged
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
Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator
reporting-tier-paywall
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
Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator
reporting-history-retention
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
Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator
reporting-anomaly-alerts
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
Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.
reporting-nl-query
Reverted to unknown. What was searched: rause (170 topics) including c_reports.htm and c_iquery_permissions.htm, plus corpus-wide /natural language|AI [Aa]ssistant|chatbot|generative/ = 0 of 4,840. Why that is not a no: the cited page is a 1,056-byte chapter blurb ('Build original reports, manage the reports on your dashboard, organize your most frequently viewed reports, and create custom reports in Excel with iquery.'), which summarises the Reports chapter of one book — it is not a census of every way a Simphony operator interrogates their data. And Oracle itself routes Simphony operators off this surface: the (now-verified-live, HTTP 200) Simphony product page says operators can 'Centralize and normalize data from multiple POS and front- and back-office systems with Oracle Analytics Cloud or third-party BI'. Oracle Analytics Cloud ships a natural-language AI assistant, its documentation library is reachable and was NOT mined this session, and the string 'Oracle Analytics' appears 0 times in all 4,840 documents — the corpus has no coverage of it at all. That is the CrowdTwist shape the brief itself forbids scoring no on: a reachable-but-unmined sibling library is an unmeasured absence. What would settle it: the Oracle Analytics Cloud documentation, plus whether an OAC tenant is included in a Simphony Reporting and Analytics subscription or sold separately. || 323rd: 323rd, NEW SURFACE, CELL NOT MOVED, AND A TRAP RECORDED. The existing note rests partly on 'Oracle's marketing pages at www.oracle.com/food-beverage/ return 403 to automated retrieval'. They return 200 today. The bounded 44-URL food-beverage corpus from sitemap-core.xml was read, and it contains an AI assistant that is NOT this claim and that a later reader could easily mis-score as a yes: 'Oracle Simphony Smart Assistant - AI-powered, in-context help for the front line. Embedded into Oracle Simphony Cloud Point of Sale (POS), Smart Assistant gives restaurant teams self-service suggestions and immediate, actionable answers to common technical and operational questions - right from their workstation. Staff can ask support-related questions in plain language. For example, "Why can't I log in to Simphony?" They receive context-aware guidance informed by Oracle Simphony documentation and knowledge base' (https://www.oracle.com/food-beverage/, #smart-assistant). It is a DOCUMENTATION/KB assistant - precisely the 'generic knowledge-article response' the claim excludes - it answers about the software rather than against the operator's own sales and labor data, it returns guidance rather than a figure or chart, and the same page states 'Smart Assistant is available to early adopters and is planned for broader availability to Oracle Restaurants customers later this year', so it is not yet generally shipped either. Separately, the Simphony product page positions Oracle Analytics Cloud as an EXTERNAL destination rather than an included surface - 'Centralize and normalize data from multiple POS and front- and back-office systems with Oracle Analytics Cloud or third-party BI' - which weakens but does not close the unmined-sibling caveat this note already records. Controls over the 44 pages, tokenised: 'natural language' 0, chatbot 0 (the one /chatbots/ link is Oracle Digital Assistant for HCM, a different product), 'artificial intelligence' 0. Retrieved 2026-09-17. || 327th: 327th: one of this note's two open objections is now closed and the other is not. The note warns against 'the CrowdTwist shape' - scoring an absence while a reachable sibling library is unmined. That library is now measured: all 36 monthly Release Readiness books listed at docs.oracle.com/en/industries/food-beverage/crowdtwist-loyalty-engagement/releases.html were walked to a link fixpoint (164 files, 212,952 characters, 0 failures; nonsense control /9999 -> the host's 15,118-byte 404) and they carry no query, reporting or assistant feature of any kind - 'AI' 0, 'natural language' 0, 'chatbot' 0, 'generative' 0. Separately, the token 'AI' scores ZERO (word-boundary) across the 9,045-document / 29,944,553-character Simphony and back-office corpus re-grepped this pass (sicli 7,786 complete + gnlug 40/40 + simcg 845 + rause 169 + ccapi + Gen2 + the seven PDF-only back-office books; positive control 'Simphony' 18,149). WHAT STILL BLOCKS THE CELL, unchanged: Oracle Analytics Cloud, which the Simphony product page positions as an external destination ('Centralize and normalize data ... with Oracle Analytics Cloud or third-party BI'), ships its own NL assistant and was not mined, and no public document settles whether an OAC tenant is included in a Simphony Reporting and Analytics subscription. Retrieved 2026-09-18. || 328th: 328th: one more first-party manager surface read, no NL query in it. The Oracle Simphony Frontline Manager User Guide (G49756-01) - the web application 'used to view and change settings' that Simphony Home exposes to store managers, walked to a link fixpoint at 25 of 25 topics, 0 failures, 32,872 characters - is menu items, effectivity groups, a bulk price editor and Mobile Order and Pay setup. Tokenised word-boundary case-insensitive over the complete book: 'natural language' 0, 'assistant' 0, 'AI' 0, 'chat' 0. The blocker recorded in the 327th is unchanged: Oracle Analytics Cloud is positioned by the Simphony product page as an external destination, ships its own NL assistant, and no public document settles whether an OAC tenant is included in a Simphony Reporting and Analytics subscription. Retrieved 2026-09-18. || 330th: 330th: the store-level operator surface is now censused too, and it holds no NL query. simmu POS Manager User Guide (92 topics), sipou POS Employee User Guide (200) and resnw Networking Excellence Guide (77) were walked to an href fixpoint at 200, 0 failures, 369 topics / 548,682 characters - the first time any pass on this record has held the manuals the people who actually run the reports use. Tokenised word-boundary case-insensitive: 'natural language' 0, 'assistant' 0, 'chatbot' 0; the reporting topics are a fixed list of workstation reports (t_start_shift_run_reports.htm: Employee Financial, Employee Financial - VAT, Employee Tip, Cashier Financial, Offline Employee Financial, Offline Employee Cashier, selected by report number). The 44-URL oracle.com food-beverage corpus was also re-derived this pass from sitemap-core.xml (still 44, all 200): 'natural language' 0, 'AI assistant' 0, 'chatbot' 0, 'Smart Assistant' 5 (all on /food-beverage/, the documentation-and-KB assistant this cell's 323rd note already records as excluded by the claim). The blocker is unchanged and is unchanged by design: Oracle Analytics Cloud appears on the Simphony product page only as an external destination - 'Centralize and normalize data from multiple POS and front- and back-office systems with Oracle Analytics Cloud or third-party BI' - alongside third-party BI, 'OAC' scores 0 across the marketing corpus, and no public document states whether an OAC tenant is included in a Simphony Reporting and Analytics subscription. Retrieved 2026-09-18. adversarially verified
Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator
reporting-guest-cohorts
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
Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator
reporting-sales-forecast
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
Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.
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, franchise & enterprise governance
Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.
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
Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator
multi-location-local-override-policy
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
Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.
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
Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator
multi-location-scheduled-publish
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
A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator
multi-location-new-store-template
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
The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator
multi-location-corp-vs-franchisee-roles
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
Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator
multi-location-royalty-calculation
Simphony markets to franchises — simcg/c_simphony_intro.htm calls it a platform for 'global, franchised, multi-unit enterprises' — but publishes no royalty engine. The iQuery subject-area table is a complete enumeration of the reporting warehouse's subject areas (Discount Daily Total, Employee Daily Total, Job Code Daily Total, Inventory Daily Total, Gift and Loyalty …) and contains no royalty, ad-fund or franchise-fee subject area; the Reports Reference Guide (rarrg, 223 report pages, whole book held) contains no royalty report. 'royalt' returns 37 hits corpus-wide and every one is inside an open-source licence text (Mozilla Public License, Apache, Creative Commons, the Crossmatch SDK EULA); 'ad fund' and 'marketing fee' return zero. Oracle's own Restaurants library index names its book set and contains no franchise or royalty title. Corpus date: back-office release 20.1. (Financials sit in the sibling SKU 'Oracle NetSuite Restaurant Operations Cloud Service', which is out of subject for this record.) https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_iquery_permissions.htm · retrieved 2026-09-05 adversarially verified
Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.
multi-location-royalty-collection
Follows from the calculation cell: there is no calculated royalty to collect. The iQuery subject-area enumeration and the 223-page Reports Reference Guide contain no royalty, ad-fund or franchise-fee object, and 'royalt' appears corpus-wide only inside open-source licence texts. The payments library (payments-platform, registry-closed at the book level) documents merchant payouts to the operator, not debits from franchisee accounts, and no franchisee-visible fee statement is documented anywhere in the 4,840-document corpus. Corpus date: back-office release 20.1. https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_iquery_permissions.htm · retrieved 2026-09-05 adversarially verified
Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.
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
Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator
multi-location-normalized-item-rollup
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
Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.
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
A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.
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
A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator
multi-location-multi-brand
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
Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.
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
Supports locations operating in different currencies and languages within one enterprise account, with consolidated reporting converted to a reporting currency.
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
Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator
multi-location-config-audit-log
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
Supports SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. differentiator
multi-location-enterprise-sso
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
Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator
multi-location-enterprise-api
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
Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.
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 & physical footprint
The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator
hardware-commodity-devices
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
Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.
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
Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.
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
The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator
hardware-handheld-battery-swap
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
Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.
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
Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).
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
Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.
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
Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator
hardware-kiosk
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
Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.
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
Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.
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
Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.
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
Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.
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
Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator
hardware-tap-to-phone
Same enumeration as payments-softpos-tap-to-pay, read from the hardware side. Oracle payment hardware for Simphony is issued rather than commodity: the cited chapter says 'you’ll receive a payment terminal' on purchase of Payment Cloud Service, and enumerates 'Castles Device S1F2', 'Verifone e285', 'P400 and V400m', 'Verifone P630'. Where Oracle documents NFC on its own mobile devices it is a reader accessory, not phone-based acceptance: the Tablet 700 series specification (https://docs.oracle.com/en/industries/food-beverage/micros-tablet-700-series/latest/tabss/c_tablet_technical_specifications.htm, already cited 4 times in this record) lists NFC/RFID as 'Optional; Supports ISO/IEC 14443 A Reader/Writer' Mode @ 13.56MHz, and the Workstation 820 RFID scan area (https://docs.oracle.com/en/industries/food-beverage/micros-workstation-8/weset/c_basic_features.htm) 'Reads MICROS Contactless Employee ID Cards for employee' sign in. The product page enumerates the hardware line as Workstation 8, Workstation 6 and Tablet 700 Series, with no phone option. The literal strings Tap to Pay, Tap to Phone and SoftPOS occur zero times across all 4,840 corpus documents. https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/fbopp/c_terminals_intro.htm · retrieved 2026-09-05 adversarially verified
Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator
hardware-pricing-transparency
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 can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator
hardware-ownership-vs-lease
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
Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator
hardware-usable-after-churn
326th: NEW SURFACE - the Oracle MICROS HARDWARE documentation library at docs.oracle.com/en/industries/food-beverage/hardware.html, which no prior pass on this record has opened (q323-q325 read intrg and fbcom/comp_matrix.pdf only). It is a per-device library with Setup Guides, Security Guides, Licensing Information User Manuals and Site Preparation docs for MICROS Workstation 8, Compact Workstation 3 Series, Express Station 4, Tablet 700 Series, Workstation 6/5a/5/4, the Lenovo Tab K10 and the Verifone/Castles payment terminals. Four of those books were walked to a link fixpoint and fetched whole: Workstation 8 Setup Guide (51 topics), Workstation 8 Security Guide (21), Tablet 700 Setup Guide (50), Compact Workstation 3 Setup Guide (75) - 197 topic bodies, 298,110 characters. MOVED unknown -> partial. This note previously said 'the corpus does not confirm post-cancellation usability and does not confirm bricking' and asked for the Oracle Master Agreement (ClaudeBot-barred, not fetched). The hardware books answer the operative half - is the device software-locked or remotely bricked - in Oracle's own words. (1) THIRD-PARTY SOFTWARE IS AN EXPLICIT, DOCUMENTED USE OF THE DEVICE: the Compact Workstation 3 Series and Workstation 8 Series platform sections both list 'The OPOS Driver that allows third-party applications to use integrated peripherals and custom ports, such as the magnetic card reader, customer display, and cash drawer ports through industry-standard OPOS commands.' (2) THE OS IS A GENERAL-PURPOSE COMMERCIAL ONE: 'The Workstation 820 is available with Microsoft Windows 10 IoT Enterprise LTSC 2021 64bit, Oracle Linux for MICROS (Linux 7), and the Oracle Linux for Simphony (Linux 9) operating system', the Compact Workstation 3 likewise, and Oracle Linux for MICROS/Simphony is described as 'Free to use, free to distribute, free to update.' (3) THE OWNER CONTROLS THE FIRMWARE AND CAN RE-IMAGE LOCALLY: the BIOS Security table sets 'Secure Boot Configuration Disabled by default', the supervisor and HDD passwords are optional owner-set values, and 'System Recovery' states 'A system recovery is used to: Wipe the hard drive. Restore all PC settings to factory settings. Remove all user accounts and settings. Remove all after factory installed applications. To perform a system recovery, you can use the BIOS, the workstation's recovery button, or the Microsoft Windows operating system recovery function' - with separate documented paths 'Performing a Factory Reset from BIOS (Microsoft Windows)' and 'Performing a Factory Reset from BIOS (Oracle Linux for MICROS and Oracle Linux for Simphony)'. No remote disable, kill switch, subscription check or entitlement lock appears in 298,110 characters; tokenised 'repurpose' 0, 'decommission' 0, 'ownership' 0. This also bounds the appliance quote the record leans on: 'eliminates the potential for users to run other applications' is the Oracle Linux for MICROS image's posture, not a property of the hardware, which also ships Windows 10 IoT with an OPOS driver for third-party applications. WHY PARTIAL AND NOT YES: Oracle never uses the words cancellation, termination or end of subscription anywhere in these books, so the claim's explicit conjunct is unaddressed; and the recovery OS image is distributed through My Oracle Support ('Check My Oracle Support for updated OS image before performing factory recovery'; the Tablet 720 recovery .iso requires a My Oracle Support login), which a churned customer may not hold. POISON named: the Workstation 8 Security Guide's 'the HDD will become permanently locked ... the device must be repaired by a qualified Oracle repair facility' is an OWNER-SET UEFI/HDD password being forgotten, not a vendor lock. Retrieved 2026-09-18. https://docs.oracle.com/en/industries/food-beverage/compact-workstation-3-series/latest/cwssu/c_software_components_platform.htm · retrieved 2026-09-18 adversarially verified
Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator
hardware-rma-sla
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
Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.
hardware-byod
Reverted to unknown. What was searched: fbcom/comp_matrix.pdf read in full around Table 2-1/2-2/2-3, plus corpus-wide /BYOD|bring your own|personally owned|personal device|employee-owned/ = 0 of 4,840. Why that is not a no: the matrix is a validation table, not an ownership policy — it says 'The Simphony software has been validated on the following operating system and device combinations' and then validates generic consumer product families ('Samsung Galaxy Tablet', 'Google Pixel', 'Lenovo Tab K10') rather than Oracle SKUs, which if anything cuts toward commodity hardware rather than away from it. Nothing in the matrix or the Security Guide addresses who owns the device. The record's existing rationale states the position correctly: the mobile-client and Security Guide topics '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.' What would settle it: an Oracle statement on device ownership or a personal-device security model, neither of which exists in this corpus. || 325th: NEW SURFACE (325th), cell NOT moved. The first body-level census of the Simphony Configuration Guide (845 of 845 topics fetched at 200, where prior passes read only the TOC titles) turns up one topic no pass has cited, and it cuts slightly TOWARD operator-supplied devices without answering ownership: simcg/t_properties_android_third_party_psp.htm, 'Enabling a Third Party Mobile Device Management (MDM) to Distribute Simphony Software' - 'You can use a third party Payment Service Provider (PSP) and its proprietary external Mobile Device Management (MDM) platform to distribute Simphony software to Android devices. The Third Party Managed Device option is only available for use with the following types of POS workstations: 1 - Mobile, 2 - Workstation Client, 6 - Tablet Client.' So distribution can leave Oracle's own CAL entirely - but the device must still be selected as 'an Android workstation record' under EMC Setup > Workstations, i.e. every device remains a property-provisioned workstation object, which is the model the existing rationale describes. The security model is device-level, not person-device-level: simsg/google_android.htm says only 'Google Android offers native application sandboxing and other isolation features that provide a higher security level for any application including POS clients. Avoid installing unnecessary applications. Follow the best security practices and settings provided by the vendor of your Google Android device', and 'POS clients running on Google Android use employee ID'. `BYOD` 0 and `personal / personally-owned / own device|phone` 0 across the 1,172 topic bodies, while `MDM` fires 20 times in 7 topics, so the corpus is readable. Ownership is still unaddressed by Oracle, so unknown stands. Retrieved 2026-09-17. || 326th: 326th: NEW SURFACE - the Oracle MICROS HARDWARE documentation library at docs.oracle.com/en/industries/food-beverage/hardware.html, which no prior pass on this record has opened (q323-q325 read intrg and fbcom/comp_matrix.pdf only). It is a per-device library with Setup Guides, Security Guides, Licensing Information User Manuals and Site Preparation docs for MICROS Workstation 8, Compact Workstation 3 Series, Express Station 4, Tablet 700 Series, Workstation 6/5a/5/4, the Lenovo Tab K10 and the Verifone/Castles payment terminals. Four of those books were walked to a link fixpoint and fetched whole: Workstation 8 Setup Guide (51 topics), Workstation 8 Security Guide (21), Tablet 700 Setup Guide (50), Compact Workstation 3 Setup Guide (75) - 197 topic bodies, 298,110 characters. On this claim it adds one fact and settles nothing: the library documents a COMMODITY CONSUMER tablet as a first-class Simphony device - docs.oracle.com/en/industries/food-beverage/lenovo/ ships an Oracle-badged 'Lenovo Tab K10 Quick Start Guide' (F75896_01) and 'Lenovo Tab K10 User Guide' (F75895_01) - which strengthens the reading that Simphony's Android client is not tied to Oracle SKUs. But across the 197 fetched topic bodies (298,110 characters) tokenised word-boundary case-insensitive 'BYOD' 0, 'ownership' 0, 'repurpose' 0 and 'Android' 0 in the x86 workstation books - POISON: 'personal' scores 11 and every hit is either safety-warning boilerplate ('risk of personal injury') or a Windows recovery option ('Keeps personal files', 'Deletes personal files and User accounts'); every setup procedure treats the device as a property-installed workstation. Oracle still publishes no statement on who owns the device and no person-level (as opposed to device-level) security model, so unknown stands. Retrieved 2026-09-18. || 330th: 330th: NEW SURFACE - the Simphony Client Deployment Guide (sical), 59 topics walked to an href fixpoint at 200, 0 failures, never opened by q323-q328. It supplies the device-provisioning requirements the record has been missing, and they cut AGAINST a personal handset without ever naming ownership. t_properties_android_configure_workstation.htm: the device must be inserted as a Workstation record in EMC with Type '1 - Mobile' or '6 - Tablet Client', assigned to at least one revenue centre, and 'Enter the Internet Protocol (IP) address or host name of the Android workstation device in the Address/Host Name field ... On the Android device, perform the following tasks before installing the Simphony software: Configure the network settings to use a static Internet Protocol (IP) address ... Turn off Trusted Sources on the device.' A static IP and a disabled Trusted Sources setting are property-network provisioning steps, not things a member of staff does to their own phone. The security model that IS documented is device-level: t_properties_android_install_servicehost.htm 'Simphony requires you to ensure that data encryption and a lock mechanism is enabled on the device that prevents unauthorized people from accessing it ... configure a Personal Identification Number (PIN) by accessing the device's Settings, select Security, and then select Encrypt Device', with an enterprise override (Control Parameters option 80 - Do not require PIN/Pattern lock on Android clients) and an EMC privilege 10064 - Can Access CAL Admin Application governing who may whitelist apps or leave the CAL launcher. The install route is self-service (download AndroidServiceHost.apk from the Simphony Web Portal with EMC credentials), which is the one fact that would make a staff-owned device technically possible. Tokenised word-boundary case-insensitive over sical + simcm + simpu + resnw (172 topics, 334,710 characters): 'BYOD' 0, 'bring your own' 0, 'personally owned' 0, 'personal device' 0, 'personal phone' 0, 'employee-owned' 0, 'MDM' 0, 'consumer device' 0, 'ownership' 3 (all in certificates1.htm, about certificate ownership); positive control 'Android' 128 in 11 topics, so the corpus is readable. Still unknown: Oracle documents a device permission and security model but never a person-owned-device one, and never states who owns the device. Retrieved 2026-09-18. adversarially verified
Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator
hardware-remote-device-management
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
Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.
hardware-selfpour-scales
Via a third-party partner, not native. Oracle Restaurants Marketplace listing 'PourMyBeer POS Integration' (publisher Innovative Tap Solutions; version 1.3.0 released 2023-03-01, listing updated 2023-03-09; read via Oracle's public Marketplace API 2026-09-12): 'This integration will allow establishments that use PourMyBeer self-pour beverage systems to link their guest's RFID beverage cards to open checks on their Simphony POS. Guest's self-serve pours are added to their check on the POS for a seamless self-pour experience.' The linked Oracle Partner Validation Report (v1.3, Sept 2022; Oracle validation 'Complete' 3/6/2023; STS Gen2, 'POS v19.4') describes the workflow: 'Staff opens a check for customer on the POS'; staff 'links/pairs an RFID card to the check'; 'Customer uses the RFID card to select and pour beverage and transaction is posted to their open check on POS'; the card stops working once the check is closed. SHORTFALLS: (1) not native to Simphony. It is partner middleware ('.Net application, SQL database, running on Windows 10 or 11 PC located on-site'). (2) Staff must pair a card to each check by hand. (3) Every beverage must be 'manually mapped using our Product Mapping App', or unmapped pours post as a 'PMB Fallback Item'. (4) Only the PourMyBeer tap wall is covered. No flow-meter or liquor-spout integration is shown. (5) Oracle's validation section lists 'Post Check' among the Checks API functions NOT included in the validation. The listing and the functional sections are partner-authored. https://public.marketplace.us-ashburn-1.oci.oraclecloud.com/20180828/listings/143640202 · retrieved 2026-09-12 adversarially verified
Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.
hardware-callerid-integration
CLAIM: supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call. VERDICT: no. The existing note named exactly one thing that could overturn it - the System Interface Module Manual, 'which Oracle publishes only as ssimm.pdf and which did not text-extract for me'. It extracts now, it was read in full, and it describes the opposite workflow. NEW SURFACES FOUND IN THE 323rd, none named by any prior note or atlas file. (1) ANONYMOUS OPENAPI SPECS on docs.oracle.com, unlinked from any toc text but referenced by the book toc: https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/swagger.json - Simphony 'Configuration and Content API Guide', info.version 2026.06.15, 5,214,948 bytes, 887 paths / 887 operations, 721 definitions, 2,283 distinct property names; and https://docs.oracle.com/en/industries/food-beverage/simphony/omsstsg2api/swagger.json - 'Simphony Transaction Services Gen2 API Guide', info.version 2026.08.15, 297,397 bytes, 30 paths / 36 operations, 110 definitions. Soft-404 control: the same host answers every unknown path with an identical 15,118-byte HTML 404 (ccapi/openapi.json, simim/swagger.json, simts/swagger.json all 404/15,118), so these two 200s are real bodies, not a catch-all. (2) A COMPLETE CENSUS OF THE sicli BOOK. The Doc-O-Matic search index at https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/fti/FTI_Files.json (795,900 bytes, found from scripts/branding-Website.js) is the publisher's own file manifest: 7,786 entries of title+path. All 7,786 were fetched at HTTP 200, 0 failures, 156,641,767 bytes on disk. This retires the 'sicli is a FLOOR - roughly 700 of 7,600+ pages held' caveat that capped several cells of this record. (3) ssimm.pdf NOW EXTRACTS. https://docs.oracle.com/en/industries/food-beverage/simphony/ssimm/ssimm.pdf (Release 19.10, G49773-01, June 2026, 2,640,247 bytes) extracts with pdftotext -layout to 894,704 characters, positive control Simphony 154 / SIM 488. A prior note's claim that it 'did not text-extract for me' is FALSE of the current file. (4) www.oracle.com NO LONGER 403s. Several notes on this record rest on 'www.oracle.com returns 403 to every retrieval'. It returns 200 today to an ordinary browser UA. robots.txt (2,649 bytes, byte-identical to the copy cached 2026-08-10) NAMES ClaudeBot in a group whose rules are Disallow /a/ocom/docs/gated/, /splash/, /us/, /_qa/, /a/ocom/resources/, /financial-services/ofss/, /a/ocom/docs/corporate/pricing/ and three named PDFs, then Allow: /; none of the pages below is under a barred path and none was fetched with a UA swap. sitemap-core.xml yields a bounded 44-URL food-beverage corpus, all 200. (5) PDF-ONLY BACK-OFFICE API BOOKS, none in any prior corpus: lmapi E90995_32.pdf (Labor Management API, 196,436 chars), lmsch E90996_16.pdf (Scheduler RESTful API, 52,958), glpoa E91264_08.pdf (Gift and Loyalty POS Web Services API, 108,066), impoa E91249_09.pdf (Inventory Master Data Web Services, 55,473), immda E91248_07.pdf (Inventory POS Web Services, 48,212), dacsr G21944_03.pdf (Reporting DB Access, 239,447). EVIDENCE, and it is positive rather than an absence. ssimm.pdf's own worked pizza-delivery scenario states the lookup is OPERATOR-KEYED: 'Information that might be captured and stored in a third-party database includes the name and address information, the customer's telephone number, as well as directions to the customer's residence. When a customer telephones the pizzeria, an operator uses the customer's telephone number to access any existing information in the pizza delivery system's database.' The SIM sample code is consistent: 'display 2,2, "Phone Number:" displayinput 2, 18, phone_num{:###-####}, "Enter phone number"' followed by 'rxmsg status, phone_num if status = "N" exitwitherror "Phone Number Not Found"'. So the interface Oracle publishes for exactly this integration puts a human typing the number, with no inbound event and no device. BOUND/CONTROLS, tokenised, word-boundary, case-insensitive, over three corpora. (1) ssimm.pdf, 894,704 characters, positives Simphony 154 / SIM 488 / delivery 19 / pizza 7: caller 0, 'caller id' 0, ANI 0, modem 0, 'incoming call' 0, 'screen pop' 0, VoIP 0, SIP 0, peripheral 0, inbound 0. (2) The complete 7,786-topic sicli census, positives Simphony 54,534 / OpsContext 6,477: callerid 0, ANI 0, telephony 0, serial 0, 'COM port' 0, peripheral 0, modem 0, SIP 0, VoIP 0, 'incoming call' 0, 'screen pop' 0. THE POISON IS THE WORD 'caller' ITSELF: it scores 2 in sicli and BOTH are software callers, not telephones - OpsContext.CommandLogEntry.CallerDuration (a command-log timing property) and one occurrence inside ExtensibilityDataService.AddExtensibilityDataInfo; Gen2's 2 hits are '(defined by the caller)' on ExtensionItem.appName and .dataType. A reader counting the string would publish a false yes. (3) ccapi, 5,214,948 bytes, 2,283 property names: caller 0, telephony 0; the only phone fields are Location.phoneNumberPrefix and RevenueCenter.phoneNumberPrefix, i.e. the restaurant's own number. (4) The bounded 44-URL www.oracle.com food-beverage corpus: 'caller ID' 0. SCOPE: a SIM script can read a serial device only if Oracle documents one, and across the SIM manual and the whole extension API it does not. Retrieved 2026-09-17. https://docs.oracle.com/en/industries/food-beverage/simphony/ssimm/ssimm.pdf · retrieved 2026-09-17 adversarially verified
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
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
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
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
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
Oracle Restaurants article 'Next-Gen Simphony APIs Accelerate POS Integrations' by Keshav Kiran, Senior Director, Global Strategic Partnerships (live 200 on 2026-09-12; Wayback 2025-07-15): 'Our developer-friendly program provides partners with access to POS integration resources during development for guidance, free temporary Simphony Lab for development/testing, and validation once their integration is ready.' The Lab is free and needs no paid Simphony production subscription. The gate is on the live partners page (/pos-integrations/partners/, 200 on 2026-09-12): 'Enroll in the Oracle Partner Network (OPN)' then 'Once your company's OPN enrollment is approved, submit a Simphony Integrations Program inquiry'. SHORTFALLS: (1) Not free to reach. OPN is a paid annual membership: the OPN join page (www.oracle.com/partner/, 200 on 2026-09-12) lists 'Level 0 USD $500 | Level 1 USD $5K | Level 2 USD $100K | Level 3 USD $500K'. The partners page does not say which level is required. (2) Not open to developers in general. OPN is 'geared toward established companies that are at least six (6) months old and have a baseline level of at least five (5) employees', and the program needs Oracle's approval. (3) The Lab is 'temporary', and seeded data is never stated. (4) The live partners page does not mention the Lab, so whether it is still offered rests on an article that appears to date from the programme's 2021 launch. Evidence grade C (marketing article). https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-integrations/next-gen-api-for-restaurant-pos/ · retrieved 2026-09-12 adversarially verified
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
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
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
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
Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator
extensibility-webhook-reliability
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
A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.
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
Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator
extensibility-data-symmetry
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
API rate limits are published as specific numeric quotas with documented throttling behavior and headers.
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
The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator
extensibility-doordash-preferred
DoorDash publishes its own complete provider registry at https://merchants.doordash.com/api/partner-integrations — 64 providers, each carrying a `qualityStatus` of PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), plus a features-completed count against the eight high-quality features the program requires. It is served anonymously and merchants.doordash.com/robots.txt permits it (Allow: / with only /cdn-cgi/ and /monitoring barred). This is the instrument the program page points to when it says the roster is tracked in real time, and it supersedes the 2026 announcement post most of this corpus cited — that post introduces its ten names with the word `include`, which makes it a floor, not a ceiling. In that registry this vendor is the entry `oracle_iad`, rendered as 'Oracle Micros', with qualityStatus CERTIFIED and 5 of the 8 high-quality features built. CERTIFIED and AT_RISK are the program's other two tiers, so this is positive evidence of non-membership rather than a failure to find the vendor: it is present in the registry and carries a status that is not PREFERRED. GRADE HARMONISED TO B, 2026-09-11: this URL was first written at grade A. The adversarial pass ruled E on the principle that the rubric grades by the publisher's relationship to the SCORED vendor, and DoorDash is not that vendor. B is the settlement, for two reasons that are not preference: 39 rows already graded a DoorDash-published document B on this claim before today, and one URL on one claim cannot carry two grades; and E is unworkable, because nine of the 47 rows are `yes` on a differentiator-weight claim, which the grade floor refuses below B. B reads as the product documentation of the programme's own publisher, which is what this registry is. The dissent is recorded in verification.jsonl. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-11
Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator
extensibility-first-party-delivery-integrations
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
The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).
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
Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.
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
Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.
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
Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator
extensibility-bi-data-warehouse
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
The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.
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
Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.
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
The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.
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
The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.
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
A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator
extensibility-data-portability-exit
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 & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
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
Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator
reliability-offline-card-auth
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
The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator
reliability-offline-decline-liability
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
Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator
reliability-lan-degraded-multi-terminal
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
The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator
reliability-local-transaction-engine
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
Kitchen display and/or kitchen printer routing continues to function while offline.
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
The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.
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
The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).
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
The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).
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
A public, per-component status page exists showing current and historical incident state without a login.
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
A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator
reliability-contractual-uptime-sla
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
The vendor publishes written post-incident reports or root-cause summaries for major outages.
reliability-incident-postmortems
330th: THE PUBLICATION CENSUS IS COMPLETE AND THE CLAIM IS A PUBLICATION CLAIM, SO THE ABSENCE CARRIES. The claim asks whether the vendor PUBLISHES written post-incident reports or root-cause summaries; it is not a capability claim, so a bounded census of every public Oracle surface for this product settles it. Four surfaces, all re-probed today with curl and a browser UA: (1) Oracle's own Global Business Unit status platform statuspage.gbucnss.oci.oraclecloud.com serves exactly one Food and Beverage tenant, xgbu_CrowdTwist (200, 19,541 bytes, real per-region component table plus /atom and /rss); xgbu_Simphony, xgbu_Restaurants, xgbu_FoodBeverage, the platform root and a fabricated xgbu_ZZZNONSENSE ALL return the identical 503 at 107 bytes, so 503 is the platform's answer for a tenant that does not exist rather than a refusal aimed at us - there is no Simphony status page to publish an RCA on. (2) ocistatus.oraclecloud.com is a client-rendered shell and /api/v2/incidents.json 404s at 10 bytes. (3) The Oracle Help Center Food and Beverage library was enumerated from docs.oracle.com/en/industries/food-beverage/simphony/index.html this pass - 62 books (Release Notes, Configuration, POS user guides, Networking Excellence, Security, the API references and the back-office set) - and not one is an incident, outage, RCA or availability report; tokenised over the 44-URL oracle.com food-beverage marketing corpus 'root cause' 0, 'postmortem' 0, 'post-incident' 0, 'status page' 0, 'uptime' 0. (4) The only per-incident channel Oracle names, the Customer Support Portal answers the Release Notes cite by id (iccp.custhelp.com), returns an auto-submitting POST form to signon.oracle.com/signin - and a login gate is not a refusal of evidence here, it is the finding: it establishes that Oracle delivers incident detail privately to contracted customers rather than publishing it. BOUND: this bounds PUBLIC publication for Simphony only; Oracle may well issue RCAs to customers through My Oracle Support, and the Hosting and Delivery Policies (already cited on this cell) commit to no publication either way. Retrieved 2026-09-18. https://statuspage.gbucnss.oci.oraclecloud.com/status/xgbu_CrowdTwist/ · retrieved 2026-09-18 adversarially verified
24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.
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
The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator
reliability-onsite-install
Oracle Restaurants consulting services page (www.oracle.com/food-beverage/consulting-services/, live 200 on 2026-09-12; /food-beverage/professional-services/ serves the same page). Services offered: 'Our experts can provide onsite and/or remote installation and deployment assistance, including site-readiness evaluations, device placement and installation, configuration, training, live support, and post go-live hypercare services.' Also: 'Before installing your hardware, we'll work with you to review the placement of your devices, as well as your location's infrastructure and environment' and 'We'll set up, test, configure, and repackage your hardware ... and then ship it to your location for easy out-of-the-box installation.' SHORTFALLS: (1) This is evidence grade C, a marketing page. On a differentiator a yes needs an A or B source, and none was found. The Service Descriptions and Metrics (11 June 2026) list no install or go-live entitlement for any production edition. (2) It is sold separately, not included: the Hospitality F&B service descriptions say 'You must separately purchase Oracle Cloud Professional Services to set up and configure this Oracle Cloud Service'. (3) 'onsite and/or remote' promises no on-site visit for any particular deployment, and the page publishes no scope, price or eligibility. https://www.oracle.com/food-beverage/consulting-services/ · retrieved 2026-09-12 adversarially verified
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
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
Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.
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
The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.
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
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
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
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
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
Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator
reliability-failover-terminal-role
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
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
CLAIM: terminals support an automatic cellular/LTE failover for connectivity, first-party or documented. MET, for one Oracle-sold payment terminal only. Oracle's Restaurants hardware library (docs.oracle.com/en/industries/food-beverage/hardware.html, retrieved 2026-09-15) lists the 'Castles S1F4 Pro Mobile Order and Payment Terminal' under 'Payment Terminals, Mobile Devices, and Accessories'. Its setup guide, section 'Cellular 3G/4G Failover', says: 'Your S1F4 Pro terminal can automatically switch to processing payments using a cellular connection when the internet connection fails. It has a pre-installed and activated eSIM.' That failover is automatic and documented by the first party. SHORTFALLS: (1) The failover covers payments only. The guide's setup is Wi-Fi plus payment menus, with passcodes from a 'Payment Administrator'. It has no Simphony login or client step and never uses the word 'Simphony', and its own library landing page calls it a 'Mobile Payment Terminal'. The Restaurants Compatibility Matrix (fbcom/comp_matrix.pdf, byte-identical on re-fetch) does not list the S1F4 at all. It validates only the Castles S1F2 among Castles devices, which is the model Table 2-15 says runs the POS client. So the S1F4 is not shown running Simphony POS. (2) For the POS terminals themselves Oracle states the opposite. The Simphony Configuration Guide, Android Network Requirements (simcg/c_properties_android_network.htm), says: 'Simphony does not support the use of a 3G or 4G connection through a telecommunications provider to these local devices'. The Android device must use a WLAN on the LAN of the Check and Posting Service. The Workstation 8 Series technical specifications list only an Ethernet port and optional Wi-Fi 6E, with no WWAN or SIM. (3) The same S1F4 page contradicts itself on the SIM. It says there is a 'pre-installed and activated eSIM', but its closing section says 'customers must obtain and maintain a SIM card with an active data plan... Carrier services, fees, and connectivity are not included'. So the cellular service is the operator's cost and responsibility. (4) The guide does not say whether payments taken over cellular settle normally or how an outage is handled. Net: automatic cellular failover exists for card payments on an optional Oracle payment terminal. Simphony order capture and posting on workstations and Android POS devices is explicitly WLAN/LAN-bound. https://docs.oracle.com/en/industries/food-beverage/castles-s1f4-terminal/cslsf/c_intro_es4.htm · retrieved 2026-09-15 adversarially verified
Commercial, compliance & data ownership
Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator
commercial-month-to-month-contract
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. || 323rd: 323rd, NEW SURFACE, CELL NOT MOVED. The blocker recorded here - 'The Simphony pricing and product pages on www.oracle.com return 403 to every retrieval attempted, including a Googlebot user agent' - HAS DECAYED. www.oracle.com answers 200 to an ordinary browser UA today, and its robots.txt (2,649 bytes, byte-identical to the 2026-08-10 cached copy) names ClaudeBot in a group that allows / apart from /a/ocom/docs/gated/, /splash/, /us/, /_qa/, /a/ocom/resources/, /financial-services/ofss/ and /a/ocom/docs/corporate/pricing/; nothing below is under a barred path and no UA swap was used. sitemap-core.xml gives a bounded 44-URL food-beverage corpus, every one fetched at 200. Across those 44 pages, tokenised word-boundary case-insensitive, 'month-to-month' scores exactly 1 and 'no long-term' exactly 3 - AND ALL FOUR ARE ABOUT PAYMENT PROCESSING, NOT THE POS SUBSCRIPTION, which is the trap in this cell: 'Month-to-month terms - Flexible terms, and no annual contract. If you're not selling food, you're not paying payment processor fees.' (/restaurant-pos-systems/payment-processing/), and 'Our payment processing fees are fixed ... Our contract terms are flexible with no long-term commitment required.' on the Simphony product page, where the sentence sits inside the payments panel. A /food-beverage/restaurant-pos-systems/pricing/ path 404s and no page in the 44 carries a POS term length. Also 'no contract' 0. So the marketing corpus is now readable, is bounded, and still says nothing about the core POS software tier's term. Retrieved 2026-09-17. adversarially verified
Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator
commercial-no-early-termination-fee
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
The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.
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
The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator
commercial-processing-not-bundled
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
Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator
commercial-interchange-plus-published
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
The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator
commercial-rate-increase-clause
CLAIM: the processing agreement caps or prohibits unilateral vendor-initiated rate increases outside pass-through interchange/network changes, OR grants penalty-free exit on any increase. VERDICT: partial - Oracle publishes a penalty-free-exit position for Oracle Payments, but publishes no agreement text and no cap, so only the second disjunct is met and only at marketing grade. THE BLOCKER IN THE EXISTING NOTE HAS DECAYED: it says 'www.oracle.com/contracts/cloud-services returns 403 to every user agent tried, so the contracts index cannot be enumerated'. NEW SURFACES FOUND IN THE 323rd, none named by any prior note or atlas file. (1) ANONYMOUS OPENAPI SPECS on docs.oracle.com, unlinked from any toc text but referenced by the book toc: https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/swagger.json - Simphony 'Configuration and Content API Guide', info.version 2026.06.15, 5,214,948 bytes, 887 paths / 887 operations, 721 definitions, 2,283 distinct property names; and https://docs.oracle.com/en/industries/food-beverage/simphony/omsstsg2api/swagger.json - 'Simphony Transaction Services Gen2 API Guide', info.version 2026.08.15, 297,397 bytes, 30 paths / 36 operations, 110 definitions. Soft-404 control: the same host answers every unknown path with an identical 15,118-byte HTML 404 (ccapi/openapi.json, simim/swagger.json, simts/swagger.json all 404/15,118), so these two 200s are real bodies, not a catch-all. (2) A COMPLETE CENSUS OF THE sicli BOOK. The Doc-O-Matic search index at https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/fti/FTI_Files.json (795,900 bytes, found from scripts/branding-Website.js) is the publisher's own file manifest: 7,786 entries of title+path. All 7,786 were fetched at HTTP 200, 0 failures, 156,641,767 bytes on disk. This retires the 'sicli is a FLOOR - roughly 700 of 7,600+ pages held' caveat that capped several cells of this record. (3) ssimm.pdf NOW EXTRACTS. https://docs.oracle.com/en/industries/food-beverage/simphony/ssimm/ssimm.pdf (Release 19.10, G49773-01, June 2026, 2,640,247 bytes) extracts with pdftotext -layout to 894,704 characters, positive control Simphony 154 / SIM 488. A prior note's claim that it 'did not text-extract for me' is FALSE of the current file. (4) www.oracle.com NO LONGER 403s. Several notes on this record rest on 'www.oracle.com returns 403 to every retrieval'. It returns 200 today to an ordinary browser UA. robots.txt (2,649 bytes, byte-identical to the copy cached 2026-08-10) NAMES ClaudeBot in a group whose rules are Disallow /a/ocom/docs/gated/, /splash/, /us/, /_qa/, /a/ocom/resources/, /financial-services/ofss/, /a/ocom/docs/corporate/pricing/ and three named PDFs, then Allow: /; none of the pages below is under a barred path and none was fetched with a UA swap. sitemap-core.xml yields a bounded 44-URL food-beverage corpus, all 200. (5) PDF-ONLY BACK-OFFICE API BOOKS, none in any prior corpus: lmapi E90995_32.pdf (Labor Management API, 196,436 chars), lmsch E90996_16.pdf (Scheduler RESTful API, 52,958), glpoa E91264_08.pdf (Gift and Loyalty POS Web Services API, 108,066), impoa E91249_09.pdf (Inventory Master Data Web Services, 55,473), immda E91248_07.pdf (Inventory POS Web Services, 48,212), dacsr G21944_03.pdf (Reporting DB Access, 239,447). EVIDENCE, from the bounded 44-URL corpus (all 200): 'No long-term contracts or cancelation fees ... Oracle Payments is available in a flexible pay-as-you-go model that allows customers to try at no risk; meaning you don't have to sign multi-year contracts to lock in your rate. And while other payment processing providers slap merchants with fees for canceling' (/food-beverage/restaurant-pos-systems/what-is-restaurant-payment-processing/); 'Month-to-month terms - Flexible terms, and no annual contract. If you're not selling food, you're not paying payment processor fees.' and 'fees are fixed with no hidden service or convenience fees' (/food-beverage/restaurant-pos-systems/payment-processing/); 'Our payment processing fees are fixed, and we have no hidden service fees. Our contract terms are flexible with no long-term commitment required.' (/food-beverage/restaurant-pos-systems/simphony-pos/ and /food-beverage/restaurant-pos-systems/). WHY PARTIAL AND NOT YES: a month-to-month term with no cancellation fee does give penalty-free exit on any increase, which is the claim's second disjunct, but (a) these are marketing pages, grade C, and this is a differentiator-weight claim whose yes needs A or B; (b) no rate-change clause, and no cap, is published anywhere - re-confirmed that the Oracle Restaurants Cloud Services Service Descriptions and Metrics (11 June 2026) and the Oracle Cloud Services Agreement (Online, v062223) still attach no fee or rate language to Oracle Restaurants Payment Cloud Service; (c) no separate Oracle payment services agreement was located on the now-readable https://www.oracle.com/corporate/contracts/ index (200, 36,369 bytes). WHAT WOULD SETTLE IT: the Oracle Payments merchant agreement itself. Retrieved 2026-09-17. https://www.oracle.com/food-beverage/restaurant-pos-systems/what-is-restaurant-payment-processing/ · retrieved 2026-09-17 adversarially verified
Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).
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
Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator
commercial-module-unbundling
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
All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.
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
Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator
commercial-hardware-not-locked
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
One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.
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
Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.
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
Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator
commercial-export-customer-and-loyalty
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
Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator
commercial-post-termination-export-window
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
Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator
commercial-data-ownership-clause
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
The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).
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
Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.
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
Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.
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
Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.
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
Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.
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
Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator
commercial-wcag-kiosk-accessibility
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
POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator
commercial-dual-pricing-compliant
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
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 71 values — 51 upheld, 13 downgraded, 7 upgraded. It separately resolved 99 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Pricing and identity
| Field | Verdict | What the verifier found |
|---|---|---|
| pricing.hardware | downgrade-to-no | The conclusion is right and the stated reason is false — the same stale 403 premise already corrected in pricing.software on 2026-08-10 was left standing here. Every current MICROS hardware page returns HTTP 200 to our ordinary UA (Workstation 6, 3, 8, MICROS Tablet, and the hardware index, 49,758-62,552 bytes). Oracle publishes no per-SKU list price because it has chosen not to, not because retrieval is blocked, and its index page says so: 'Our product experts can help you build a package ... Get in touch, and we can help you calculate your total cost of ownership', CTA 'Get my free consultation and quote'. Workstation 8 offers 'Request a quote'. Workstations 6 and 3 advertise a US$1 switching promotion gated behind 'Talk to an Oracle product expert', which is a promotional term rather than a rate card. Prose rewritten to say quote-only-by-choice and to record the US$1 offer. Oracle's price-list paths under /us/ and /a/ocom/docs/corporate/pricing/ are robots-disallowed to ClaudeBot and were not fetched, so nothing here rests on them. source |
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| menu-pricing-franchise-hierarchy | yes / grade B, cites the bare simcg toc.htm | upheld | I went looking for the field-level governance half of this claim expecting to downgrade it, because the record scores multi-location-local-override-policy as partial on the grounds that per-attribute locking 'is not documented'. It is documented. Menu Item Field Security: 'EMC employee role privileges grant access to all of the fields within the Menu Item (MI) Master, MI Definition, MI Prices, Event Definitions, and Effectivity Groups... 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.' Combined with simcg chapter 4 Hierarchy (Enterprise, Properties, Revenue Centers, Zones, and a dedicated 'Inheritance and Overrides' topic), corporate can author centrally and pin individual fields against a store-scoped role. Yes stands, on a real page rather than a table of contents. source |
| multi-location-local-override-policy | partial / 'Field-level lock policy per attribute — corporate pins the price, the store may edit the description — is not documented.' | upgrade-to-yes | The stated shortfall is factually wrong and I found the page that disproves it. Menu Item Field Security gives every field in MI Master, MI Definition and MI Prices a three-state privilege — 0 Editable, 1 View Only, 2 Exclude — configured per employee role on the Roles module Fields tab. That is exactly 'corporate locks some attributes, the store may edit others, and locked fields are not editable at store level'. The researcher had the mechanism in hand (they cited People and Privileges as 'the override control') but stopped at role-level scoping and never opened the field-level page. source |
| multi-location-config-audit-log | yes / grade B, 'Oracle states it is reportable with documented search parameters and results' | downgrade-to-partial | I read the Audit Trail page. It does record 'All changes, additions, and deletions made in the EMC and PMC Procedures... successful/failed sign ins to the EMC, users taking PMC Reports and Audit Trail Reports, Key Manager activity, Audit Trail purges, activity from credit card modules, and even activity from the DbProcs utility'. Two parts of the claim fail. The claim asks for an IMMUTABLE log, and Oracle documents 'Audit Trail Purging' as a first-class administrative topic — a log an administrator can purge is not immutable. The claim also asks for exportable-or-queryable-by-corporate; queryable is documented (Audit Trail Search Parameters / Search Results), export is not documented anywhere on the page. Partial, with those two named shortfalls. source |
| kitchen-guest-ready-notification | yes / grade B, first-party Order Status Display plug-in 19.8.4.1 | downgrade-to-partial | The plug-in is real — I read the catalogue entry, and OSD v19.8.4.1 'maintains an in-memory snapshot of Kitchen Display System (KDS) data' with multi-RVC filtering. But the claim requires the notification to work 'without a separate product purchase', and OSD is a view onto KDS data. Oracle's License Information Manual is unambiguous: 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', with Premium or Standard as prerequisite. The status board therefore sits on top of a separately licensed, per-client SKU. SMS and app push remain undocumented as first-party either way. source |
| reporting-sales-forecast | yes / grade B, 'Budget and Forecast Metrics Comparison reports ship in four variants, backed by a first-party Forecasting and Budget module' | downgrade-to-partial | The report names are real — I confirmed all four Budget and Forecast Metrics Comparison variants in the Reports Reference Guide contents. But a comparison report consumes a forecast; it does not establish that the system produces one. I opened the Forecasting and Budget guide contents, and what Oracle documents is 'Manual Forecasts' / 'Generating a Manual Forecast' plus 'Historical Seed Data' and 'Assigning Historical Seed Data'. So the forecast is operator-generated from a historical seed, not machine-produced, and no daypart or hourly granularity is documented in the contents at all. The claim asks for a forward forecast produced from the location's own history at daypart or hourly granularity — history-seeded manual forecasting is a genuine but partial answer. source |
| reporting-multiloc-drilldown | yes / grade B, 'comparison reports sit above a full drill-down family reaching Check Detail, Check Journal and Customer Check View — rollup to receipt in one tool' | downgrade-to-partial | The side-by-side half is solid: eight Daily Operations Location Comparison and Revenue Center Comparison variants exist, and Check Detail, Check Journal and Customer Check View all exist. What I could not find is the drill-through that binds them. The only drill-down Oracle actually documents is organizational: 'You can create a report that allows the user to drill down the organizational levels' and the worked example stops at 'a comparison of sales at the district and location levels'. Check Detail and Check Journal are separate report objects you run, not a destination you click into from a group total. The researcher inferred a 'drill-down family' from adjacency in a table of contents. Shortfall: drill-down is documented across organizational levels only, not down to an individual check. source |
| extensibility-data-portability-exit | yes / grade B, 60-day structured machine-readable retrieval window | downgrade-to-partial | I retrieved the policy text (the cited oracle.com PDF 403s to me at both of the URLs in this record; the docs.oracle.com HTML reproduction does not). Section 6.1 reads: 'For a period of 60 days upon termination of the Oracle Cloud Services, 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 disjunction is the whole finding. Oracle discharges the obligation by leaving the tenant switched on for 60 days; nothing compels a complete structured dump of orders, customers, menu and payment metadata, and no format or mechanism is named. The claim asks for a complete historical export on demand in a documented machine-readable format — this is a right to retrieve, not a documented export. source |
| commercial-post-termination-export-window | yes / grade B, cites www.oracle.com/contracts/docs/ocloud_hosting_delivery_policies_3089853.pdf | upheld | The value survives but the evidence does not: the cited PDF returns HTTP 403 to me, as does the /a/ocom/ variant used in product.yaml, so no one in this research chain has demonstrably opened it. I found the same policy reproduced as retrievable HTML on docs.oracle.com and confirmed the clause verbatim — 60 days upon termination (30 for free trials), after which 'Oracle will delete Your Content from the Oracle Cloud Services environments'. This claim only asks for a defined window rather than an immediate cutoff, and 60 days is defined. Evidence repointed to a URL that actually opens. source |
| reliability-contractual-uptime-sla | partial / 'The specific target percentage for Simphony lives in the Food and Beverage Cloud Service Descriptions document, which is on oracle.com and returns 403 to retrieval.' | upgrade-to-yes | The percentage is published; it is just not where the researcher looked. Oracle Cloud Hosting and Delivery Policies 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, and section 3.2.3 provides Service Credits as the remedy when the target is missed. The claim requires a stated percentage AND a service credit remedy in the standard agreement, and both are in the standard agreement. The residual caveat — credit AMOUNTS are deferred to the Pillar document, which 403s — belongs in the note, not in the value. source |
| labor-shift-swap-workflow | yes / grade B, 'Employee Self Service documents Requesting Shift Changes and Approving Shift Change Requests, gated by configurable ESS permissions' | downgrade-to-partial | I opened the procedure rather than the contents page. Requesting a shift change is done by logging in to Reporting and Analytics, opening Employee Self Service > Employee Schedule, selecting the shift and clicking Request Change; the employee may 'Change Start Time' or 'Send to another Employee', and the recipient may 'Accept Request' or 'Reject Request'. So peer-to-peer swap plus a manager approval step is genuine. Two parts of the claim are not met: nothing in the procedure checks or enforces overtime thresholds or job/role eligibility at request or approval time, and there is no open-shift claim board — the shift must be directed at a named employee. It is also a Reporting and Analytics web module, not a self-service app. source |
| payments-processor-choice | yes / grade B, cites the OPI overview page | upheld | I read the cited OPI page first and nearly downgraded it: it describes OPI generically as 'a bridge between Simphony and the Payment Service Provider credit processing solution' and names no PSP at all, while this claim explicitly requires a documented list of supported processors. The list exists elsewhere. Oracle's Validated OPI Partners Guide — which states OPI 'integrates with the Oracle Hospitality Point-of-Sale (POS), OPERA, Suite 8 (PMS) and Retail (POS) systems' — names 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. Fifteen named third-party PSPs is a documented list. Upheld, evidence replaced. source |
| payments-tip-pooling | yes / grade B, cites the Labor Management toc.htm | upheld | Held to the differentiator bar, which requires a named allocation basis and a payroll-consumable output, and it clears it on a real page rather than a contents listing. Oracle: tip pools 'let organizations collect a percentage of tips from tipped employees for distribution to non-tipped employees'; manual pools distribute by hours — 'The system calculates the hourly tip rate based on the total hours worked for the job' and 'applies the hourly rates to each employee's hours worked'; automatic pools collect 'based on percentage of tip and type of sales total', with the documented examples '5 percent of Net Sales', '3 percent of Revenue Center Net Sales' and '8 percent of Beer, Wine, and Liquor Gross Sales'. Payroll consumption is explicit: 'If you select Paycheck, then Labor Management calculates how tips are divided amongst the staff and the tips are included in their paycheck'. source |
| payments-qr-guest-pay | yes / grade B | upheld | Verified on the cited page, which does open. Pressing Service Total prints the QR code on the guest check; the guest scans it, a browser opens on their own device and loads the check; on completion 'the check is closed in Simphony and shows the payment method that was used by the guest'. That is the whole claim including the automatic close. One thing the page does not state, which I checked for: whether a specific payment provider or module is required — in practice card acceptance rides on Credit Card Interface Cloud Service (B81483), a separately licensed add-on, which is captured in the commercial cells rather than here. source |
| kitchen-prep-time-pacing | yes / grade B, with a worked hamburger/fries/drink example | upheld | Quoted back verbatim from the page, and it is one of the better-evidenced cells in the file. 'The item/suborder with the longest preparation time is fired immediately. This becomes the order's minimum prep time. Fire times for the rest of the menu items are then calculated to ensure that they are all ready at the same time. This is done by subtracting each item's prep time from the order prep time.' The example — hamburger 10 min fired at 0, fries 4 min fired at the 6-minute mark, drink 1 min not displayed until 9 minutes — is Oracle's, not the researcher's. Configurable per-item cook times plus staggered display is exactly the claim. source |
| menu-pricing-fractional-placement | no / grade B, condiment prefix types enumerated with no placement construct | upheld | This is a conclusion-flipping cell and a `no` against a named vendor, so I tried hard to break it. The Condiments chapter does close the set: 'There are seven condiment prefix types' — Description, No, Add, Sub, Plain, Reset, Clear — with worked examples for each, and pricing is a binary Priced/Non-Priced attribute of the condiment, not a per-section multiplier. I then searched for any other placement construct and found only the Combo Meal route, which does not rescue the cell: a max/min rule over combo group items yields ONE of the two prices, not independent pricing per section, and offers no quarters. The vendor pointing at a combo workaround for half-and-half is the documented-workaround pattern the evidence rules accept as grounds for `no`. Upheld — and note this does not generalise to the market, where Toast ships documented per-section portions. source |
| menu-pricing-half-and-half-rule | partial / Combo Meal price rule taking the most or least expensive Combo Group item | upheld | Confirmed the 19.9 release note 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.' The claim needs at least two of {charge the higher half, average the halves, charge each topping at a fraction}. Simphony supplies exactly one of those three — charge the higher half — plus a cheapest-half rule that is not on the list and is commercially the opposite. Partial is the correct ceiling and the researcher did not inflate it. source |
| extensibility-menu-write-api | yes / grade A, Configuration and Content API menu item class endpoint | upheld | Opened the endpoint reference myself. POST /config/sim/v1/menuItems/updateMenuItemClasses, with a MenuItemClassCUDRequestBody (create/update/delete) requiring hierUnitId, objectNum and name, and the documented behaviour 'If No Menu Item Class is found, it creates a new Menu Item Class' — upsert, not read-only. Condiment group membership (required/allowed/member condiment groups) is writable on the same body. Oracle's License Information Manual independently confirms the intent: B87077 is 'used to allow third parties to create or modify POS configuration data such as menu item prices'. A real write surface; the licensing cost is scored separately at extensibility-api-access-cost. source |
| extensibility-api-access-cost | no / grade B, API access gated behind separate part numbers | upheld | Read the License Information Manual line by line rather than trusting the summary. Every programmatic write path has its own SKU with Premium or Standard as a stated prerequisite: Configuration Data Interface (B87077); Transaction Services Premium (B81485) and per-revenue-center (B3737); Standard client (B90422) and per-revenue-center (B90423); 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 precisely what the claim rules out. One nuance the record should carry: B87077 is 'not required for the Simphony Import Export feature', so manual file-based import/export is not upcharged — which is why this is a documented `no` on API cost rather than on data access generally. source |
| commercial-module-unbundling | yes / grade B, eleven separately licensed part numbers | upheld | Verified against the licence text directly, and the record's characterisation is accurate including the sting in the tail. Premium (B81480, 'minimum requirement: 50 POS clients for each customer's provisioned Enterprise') and Standard (B84711) each carry restricted-use Reporting and Analytics Advanced and Labor Management; everything else is a-la-carte with a stated prerequisite — KDS per client (B81484), Credit Card Interface (B81483), Configuration Data Interface (B87077) and the six Transaction Services variants. This genuinely is modular purchasing, and it is also the mechanism behind add-on cost creep. Upheld as scored, with the 50-client Premium minimum independently confirmed. source |
| inventory-theoretical-vs-actual | yes / grade B, cites the Inventory Management toc.htm | upheld | A contents page is thin evidence for a differentiator, so I checked that the named chain actually exists as documented topics, and it does: chapter 22 Menu Item Linking ('Linking a Menu Item to Recipes', 'Linking a Menu Item to Other Menu Items', 'Menu Item Linking With Negative Quantities'), chapter 23 Booking Sales (including 'Booking the Sales of Menu Items Not Linked to Items or Recipes' and 'Booking Unbooked POS Waste Checks'), chapter 15 Recipes with ingredient scaling, and 'Generating the Inventory Variance Report' under chapter 11. Sale-depletes-theoretical plus a variance report against counted stock is the complete claim. source |
| labor-demand-labor-forecast | yes / grade B, staffing profiles with General Forecast Requirements etc. | upheld | The cited contents page names the topics but proves nothing, so I opened Choosing a Staffing Method. Productivity method: 'Define productivity factors and then apply the factors to the forecasted values to determine the staffing requirements', worked as forecast 832 x factor 0.042 = 35. Recipe/effort method: '90 seconds as the effort required to prepare a pizza, and the forecasted value of pizza sales for a shift is 250... 22,500 seconds or 375 minutes'. General step method assigns staffing by forecast threshold. Staffing is computed from forecast volume, not read off a fixed template, and the forecast itself is seeded from the location's historical data. Yes stands — though note the same evidence caps reporting-sales-forecast at partial, because the forecast is manually generated. source |
| labor-native-scheduling | yes / grade B, cites the Labor Management toc.htm | upheld | Checked because a differentiator resting on a table of contents is the record's most common evidence pattern and deserved a spot audit. The chapter is substantive and the researcher's list is accurate: Creating Schedule Profiles, Configuring Schedule Profile Properties, Configuring Blackout Periods, Configuring Staffing Placeholders, Configuring Schedule Edit Restrictions, Creating / Editing / Submitting / Approving / Printing Schedules, Sending Schedules by Email, Creating Schedule Templates, plus a Schedule Approval Process. First-party scheduling with an approval workflow, not an export to a partner. source |
| kitchen-printer-fallback | partial / backup KDS controller and workstation alerts documented, automatic display-to-printer fallback not | upheld | Spot-audited the three kitchen partials that all cite the same KDS contents page, because a shared generic URL is where fabricated section names hide. They are all real: 'Configuring a Backup KDS Controller' (t_kds_controller_backup_config.htm) and chapter 17 'Workstation Alerts for Unsuccessful Sending to Order Devices' exist, as do chapter 15 'Menu Item Components' with 'Components with Condiments', chapter 22 'Media Viewer Configuration' and chapter 19 'KDS Highlight Schemes' cited by the neighbouring cells. So the controller tier is redundant and send failures are surfaced, but no chapter describes tickets automatically failing over from a dead display to a designated backup printer. Partial with the shortfall correctly named. source |
| hardware-pricing-transparency | no / grade C, cites the Workstation 6 page with the admission that it 403s | upheld | Weakest evidence in the file and I tried to break it. The cited oracle.com hardware page returns HTTP 403 to me too, so the record cites a page nobody in the chain has read — that must be stated rather than papered over. The value nonetheless survives on independent grounds: searching for a Workstation 6 list price surfaces only resellers (themicrosman.com, retailtechoutlet.com, eBay, possystemsforrestaurants.com) quoting their own figures, with no oracle.com price anywhere in the index. Resellers publishing prices while the manufacturer does not is the ordinary signature of quote-only hardware. Upheld as `no`, but the note must carry the 403. source |
| delivery-driver-roster | unknown / grade F, "Re-checked the whole delivery documentation set at both the current and 19.7 ver" | resolve-to-no | Resolved from unknown to no on positive evidence of absence. 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. 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. The prior pass recorded these as unknown on the grounds that they were "not documented"; the distinction applied here is that Oracle enumerates its own module set and this whole functional area is missing from it, which the evidence rules define as `no` rather than absence of evidence. Connector behaviours in this category are deliberately left unknown. |
| delivery-dispatch-board | unknown / grade F, "No first-party dispatch or expo board for in-house drivers is documented." | resolve-to-no | Resolved from unknown to no on positive evidence of absence. 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. 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. The prior pass recorded these as unknown on the grounds that they were "not documented"; the distinction applied here is that Oracle enumerates its own module set and this whole functional area is missing from it, which the evidence rules define as `no` rather than absence of evidence. Connector behaviours in this category are deliberately left unknown. |
| delivery-route-map | unknown / grade F, "Not documented." | resolve-to-no | Resolved from unknown to no on positive evidence of absence. 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. No route planning or multi-stop sequencing surface exists. Nothing in the guide set renders a map or orders stops for a driver. The prior pass recorded these as unknown on the grounds that they were "not documented"; the distinction applied here is that Oracle enumerates its own module set and this whole functional area is missing from it, which the evidence rules define as `no` rather than absence of evidence. Connector behaviours in this category are deliberately left unknown. |
| delivery-driver-tracking | unknown / grade F, "Not documented." | resolve-to-no | Resolved from unknown to no on positive evidence of absence. 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. 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. The prior pass recorded these as unknown on the grounds that they were "not documented"; the distinction applied here is that Oracle enumerates its own module set and this whole functional area is missing from it, which the evidence rules define as `no` rather than absence of evidence. Connector behaviours in this category are deliberately left unknown. |
| delivery-zones-polygon | unknown / grade F, "Not documented." | resolve-to-no | Resolved from unknown to no on positive evidence of absence. 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. 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. The prior pass recorded these as unknown on the grounds that they were "not documented"; the distinction applied here is that Oracle enumerates its own module set and this whole functional area is missing from it, which the evidence rules define as `no` rather than absence of evidence. Connector behaviours in this category are deliberately left unknown. |
| delivery-zone-pricing | unknown / grade F, "Not documented." | resolve-to-no | Resolved from unknown to no on positive evidence of absence. 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. 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. The prior pass recorded these as unknown on the grounds that they were "not documented"; the distinction applied here is that Oracle enumerates its own module set and this whole functional area is missing from it, which the evidence rules define as `no` rather than absence of evidence. Connector behaviours in this category are deliberately left unknown. |
| delivery-address-validation | unknown / grade F, "Not documented for first-party delivery." | resolve-to-no | Resolved from unknown to no on positive evidence of absence. 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. No guest address capture or validation for first-party delivery exists. Marketplace orders arrive with the address already resolved by the marketplace. The prior pass recorded these as unknown on the grounds that they were "not documented"; the distinction applied here is that Oracle enumerates its own module set and this whole functional area is missing from it, which the evidence rules define as `no` rather than absence of evidence. Connector behaviours in this category are deliberately left unknown. |
| delivery-driver-comp | unknown / grade F, "Not documented." | resolve-to-no | Resolved from unknown to no on positive evidence of absence. 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. 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. The prior pass recorded these as unknown on the grounds that they were "not documented"; the distinction applied here is that Oracle enumerates its own module set and this whole functional area is missing from it, which the evidence rules define as `no` rather than absence of evidence. Connector behaviours in this category are deliberately left unknown. |
| delivery-cash-reconcile | unknown / grade F, "Not documented. Enterprise Cash Management tracks tills, safes and server banks " | resolve-to-no | Resolved from unknown to no on positive evidence of absence. 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. 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. The prior pass recorded these as unknown on the grounds that they were "not documented"; the distinction applied here is that Oracle enumerates its own module set and this whole functional area is missing from it, which the evidence rules define as `no` rather than absence of evidence. Connector behaviours in this category are deliberately left unknown. |
| delivery-tracking-page | unknown / grade F, "Not documented for first-party delivery." | resolve-to-no | Resolved from unknown to no on positive evidence of absence. 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. 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. The prior pass recorded these as unknown on the grounds that they were "not documented"; the distinction applied here is that Oracle enumerates its own module set and this whole functional area is missing from it, which the evidence rules define as `no` rather than absence of evidence. Connector behaviours in this category are deliberately left unknown. |
| delivery-promise-time | unknown / grade F, "Not documented." | resolve-to-no | Resolved from unknown to no on positive evidence of absence. 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. No first-party delivery promise time or quote engine exists. Quote times on marketplace orders are computed by the marketplace. The prior pass recorded these as unknown on the grounds that they were "not documented"; the distinction applied here is that Oracle enumerates its own module set and this whole functional area is missing from it, which the evidence rules define as `no` rather than absence of evidence. Connector behaviours in this category are deliberately left unknown. |
| order-capture-transfer-audit | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-partial | Read c_checks_add_transfer.htm, sipou t_checks_transfer_same_rvc.htm / t_checks_transfer_btwn_rvc.htm / c_checks_transfer_team_check.htm, the whole Audit Trail chapter and rarrg c_check_journal.htm. Transfer exists in every form the claim asks about; no documented audit record names both employees. source |
| order-capture-drive-thru-timers | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-partial | Enumerated the Reporting and Analytics Reports Guide manifest (back-office/20.1/rarrg/toc.htm, 222 topics) - it holds four Speed of Service report topics and no drive-thru timer report - then read the QSR variant's full metric tables plus the KDS timing chapter and c_order_confirmation_board.htm. source |
| order-capture-catering | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-partial | Read c_deposits.htm, t_deposits_config_mi_deposits.htm, the five sipou deposit tasks, c_banquet_guest_chk_print.htm, sipou c_events.htm, t_menu_items_configure_mi_definitions.htm and the Autofire topics. source |
| menu-pricing-modifier-price-by-parent-size | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-partial | Read the whole Condiments chapter, including t_condiments_assign_condiments_to_parent_classes.htm - which the record's prior rationale had not reached and which carries the Threshold [1-8] Level mechanism - plus c_condiments_prefixes_config_tasks.htm, t_menu_items_configure_prices.htm and t_menu_items_configure_active_menu_levels_mi_definitions.htm. source |
| menu-pricing-size-style-matrix | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-partial | Read t_menu_items_configure_prices.htm (full price-record field table), c_menu_items_pricing.htm (price sequence resolution logic and the worked correct/incorrect level examples), t_menu_items_set_main_sub_custom_menu_levels.htm, t_menu_items_configure_active_menu_levels_mi_definitions.htm and the five Conversational Ordering topics. source |
| menu-pricing-included-allowance | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-yes | The prior rationale asserted no included-topping allowance is documented; t_condiments_assign_condiments_to_parent_classes.htm and c_condiments_prefixes_config_tasks.htm both document one at grade B, covering the allowance, the overage charge, the credit and the forbid. source |
| menu-pricing-dynamic-pricing | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-partial | Read t_menu_items_configure_auto_menu_levels.htm, c_menu_items_pricing.htm, t_menu_items_configure_prices.htm (Restricted to Order Types, Effectivity Group) and t_menu_items_set_main_sub_custom_menu_levels.htm. source |
| payments-surcharge-guardrails | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-partial | Read t_payments_cc_surcharge_donations.htm, c_taxes_surcharges.htm and t_taxes_surcharges.htm (a different feature - item-level surcharges for tax jurisdictions), t_payment_module_add_spi.htm and the full Payment Driver Configuration field enumeration. source |
| payments-multi-entity-routing | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-yes | Read t_payments_configure_opi_driver.htm and the complete Payment Driver Configuration field enumeration in topic_payment_driver_config.htm. source |
| kitchen-channel-pause-propagation | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-partial | Read all five Configure Menu Items topics, c_dc_info_required.htm, c_dc_status.htm and t_dc_disable.htm; the record's prior rationale had reached only the Uber Eats setup page, which does not contain this paragraph. source |
| delivery-86-sync | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-partial | Read all five Configure Menu Items topics in the Delivery Connectors chapter plus c_dc_info_required.htm. The record previously cited only the Uber Eats setup page, which does not contain this paragraph. source |
| delivery-store-pause | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-partial | Read t_dc_disable.htm, c_dc_status.htm, t_dc_enable_privs.htm and the DoorDash and Uber Eats Add Delivery Connector wizards. source |
| delivery-injection-error-visibility | unknown / grade F; bare-assertion rationale in a record no sweep had touched | resolve-to-partial | Read c_dc_status.htm, the full Delivery Connectors chapter, kdscu t_kds_enable_workstation_alerts.htm and sipou c_workstation_unsent_checks_warning.htm. source |
| digital-native-app | unknown | resolve-to-partial | GloriaFood's own feature page documents a restaurant-branded iOS/Android app auto-published to both stores, but it is grade C marketing and Oracle's Simphony integration book neither mentions the app nor supports more than one to three sites. source |
| digital-account-saved-payment | unknown | resolve-to-partial | Saved delivery addresses and previous-order prefill are documented on GloriaFood's app page; tokenized card-on-file and one-tap reorder are not, and card handling is delegated to Stripe/PayPal outside Simphony. source |
| digital-scheduled-pacing | unknown | resolve-to-partial | Scheduled orders with a configurable day horizon and kitchen lead time are documented in EMC Autofire, but nothing throttles or closes individual time slots by capacity. source |
| digital-qr-table | unknown | resolve-to-partial | Guest Pay gives guest-facing pay-at-table with configurable suggested tips against the open check, but it runs on the server's handheld rather than a guest QR scan and documents no split. source |
| digital-promo-parity | unknown | resolve-to-partial | Oracle's GloriaFood prerequisites page carries an explicit unsupported list that names Gift and Loyalty and first-buy promo discounts, so discounts sync to digital but loyalty offers do not. source |
| digital-checkout-pci-sca | unknown | resolve-to-partial | Oracle documents that Simphony never handles GloriaFood card data and that payment runs through Stripe or PayPal, but publishes no PCI DSS 4.0, script-integrity or 3DS statement for the digital checkout. source |
| digital-surcharge-transparency | unknown | resolve-to-partial | Service charges, delivery charges and tips configured in EMC do carry to GloriaFood, but card-surcharge configuration lives in the Simphony payment driver and Simphony never touches GloriaFood card transactions, so surcharge parity and its disclosure do not extend to digital. source |
| guest-loyalty-tiers | unknown | resolve-to-partial | Point-threshold award tiers with precedence and an optional reset are fully documented, and accounts carry a Program Level, but program level is changed manually under the Change Account Tier permission with no rolling-window auto-promotion or demotion. source |
| guest-loyalty-offline-behavior | unknown | resolve-to-yes | The EMC Loyalty option table documents the offline answer directly -- "loyalty transactions are not supported in offline mode" -- which is exactly what this claim asks the vendor to state. source |
| guest-loyalty-offer-stacking-rules | unknown | resolve-to-yes | Coupon, loyalty-award and redemption rules each expose a Precedence field with a documented conflict-resolution rule, alongside Allow Multiple Redemptions, Max Coupons Per Program and Cross Point Threshold as combinability controls. source |
| guest-loyalty-targeted-offers | unknown | resolve-to-partial | Eligibility rules genuinely target by spend, items and rolling-period frequency and can issue by email, but they fire on a qualifying transaction rather than over a defined audience, and the only list path is manual ad-hoc issue. source |
| guest-loyalty-rfm-segmentation | unknown | resolve-to-partial | Reporting and Analytics publishes recency, frequency and monetary attributes per loyalty customer as subject-area fields, but no lifecycle segment is computed for the operator. source |
| guest-loyalty-lifecycle-automation | unknown | resolve-to-partial | Birthday and registration-bonus automations are documented as always-on rules, but the enumerated time-rule types include no lapsed win-back trigger and the awards fire at the POS rather than as outbound campaigns. source |
| guest-loyalty-consent-management | unknown | resolve-to-partial | Three named consent purposes with operator-authored statements and required registration-form contact fields are configurable, but no consent timestamp, source of consent, or revocation handling is documented. source |
| guest-loyalty-10dlc-registration | unknown | resolve-to-no | The coupon Issue Instructions field is the complete issuance-channel surface and offers only POS, non-POS and email; the loyalty reporting schema likewise has email offer subject areas and no SMS counterpart, so there is no platform SMS send and no 10DLC registration to document. source |
| guest-loyalty-campaign-attribution | unknown | resolve-to-partial | Redemption is reportable by Campaign Name, Offer Name and Promotion with sent/opened and redeemed timestamps, but the schema exposes coupon amount rather than check total and no incremental-sales measure, and the campaign data comes from a third-party product. source |
| guest-loyalty-privacy-rights-tooling | unknown | resolve-to-partial | The de-identify and Personal Data Report tools exist but operate on People Management users; for loyalty guests the documented surface is consent configuration, account closure and myicard.net self-edit, with no export or deletion propagation. source |
| guest-loyalty-redemption-fraud-controls | unknown | resolve-to-partial | Permission-gated adjustments, an account red flag, a delay-redemption waiting period and check-digit coupon serials are documented, but there is no per-account velocity cap, no employee-self-redemption flag and no loyalty audit log. source |
| labor-photo-punch-verification | unknown / grade F, 'Not documented.' | resolve-to-no | Checked the enumerating pages rather than searching: simsg/pos_client_user_authentication.htm lists the identification methods (magnetic card, RFID card, employee ID, fingerprint; Android = employee ID only), lmusg/t_config_pay_timekeeping.htm lists every timekeeping setting, and sipou/t_start_shift_clock_in_out.htm gives the whole punch procedure. Photo capture and facial verification are absent from all three surfaces, and the biometric Simphony does ship is a fingerprint reader, which is a stored template rather than a photo-only mode. source |
| labor-geofenced-mobile-punch | unknown / grade F, 'Not documented.' | resolve-to-no | Three converging function enumerations: sipou/t_start_shift_clock_in_out.htm (the punch procedure itself, workstation-bound, no location), inmqr/toc.htm (the manager mobile app's four-chapter contents, dashboards and detail screens only) and lmusg/toc.htm (Employee Self Service = view/print/email schedule, request time off, request shift change). Simphony punches at a fixed terminal; there is no mobile clock-in for a geofence to restrict. source |
| labor-offline-time-punch | unknown / grade F, 'Punches are POS transactions and would follow the documented offline replay path, but Oracle does not state this and does not list timekeeping in the offline function set.' | resolve-to-partial | The prior rationale was inference; the POS User Guide answers it directly. sipou/t_start_shift_clock_in_out.htm draws the line between a workstation offline from the enterprise (punch works, because it still reaches CAPS and peer workstations) and a workstation with no network communication at all (punch refused). That is documented behaviour with a real shortfall, so partial rather than unknown; the reconciliation half of the claim remains undocumented. source |
| labor-digital-onboarding-i9 | unknown / grade F, 'Not documented.' | resolve-to-partial | lmusg/c_add_employee.htm redirects employee creation to Reporting and Analytics People Management, and rause/t_add_lm_details.htm enumerates the employment-detail pages - which do include I9 Information and Exemptions. So part of the claim's substance (I-9 eligibility data held against the employee record) is documented, while the digital-collection and E-Verify halves are not. Absent the referral chain the earlier bare assertion missed the I9 page entirely. source |
| inventory-86-auto-sync | unknown / grade F, 'Forecast Out of Stock exists in Inventory Management, but no automatic 86 of a POS menu item when a linked ingredient reaches zero is documented.' | resolve-to-partial | The POS Manager User Guide documents the mechanism the earlier pass never reached: a per-item Count Available that decrements on each order and refuses the sale at zero. That is a real 86 capability, so partial rather than unknown; the automatic and cross-channel halves of the claim stay unmet - simcg/c_menu_item_master_availability_methods.htm enumerates the availability methods and none is inventory-driven, and Menu Item Linking in Inventory Management links menu items to recipes for depletion costing, not for availability. source |
| inventory-invoice-ocr | unknown / grade F, 'Invoices are created from a receipt or blank and sent to Accounts Payable. No OCR or document-capture ingestion is documented.' | resolve-to-no | Went past the chapter listing to the settings screen: r_maintenance_invoice_settings.htm is the complete configurable invoice surface and has six options, none of them ingestion. Combined with the four-procedure Invoicing chapter and the B2B chapter, which is Oracle's own stated alternative for loading vendor invoices, this is positive evidence of absence rather than a failed search. source |
| inventory-lot-traceability | unknown / grade F, 'No lot or batch number capture on receiving, and no forward/backward trace, appears in the Inventory Management contents.' | resolve-to-no | Upgraded the basis from a contents listing to two field enumerations: t_masterdata_create_item.htm (the item master, all tabs) and t_receiving_create_blank_receipt.htm (the receipt header fields). Neither has a lot or batch field, so no lot identity ever enters the ledger; the traceability the claim describes has no data to run on. The item Barcode field on the Production tab is an identifier for the item, not a batch. source |
| reporting-anomaly-alerts | unknown / grade F, 'No anomaly detection or threshold alerting over sales data is documented. Employee Threshold Exceptions is a fixed report, not a configurable alert.' | resolve-to-partial | The earlier pass looked only at the Reports Reference Guide. The alerting actually lives in the InMotion Mobile app: inmqr/c_alerts.htm enumerates eleven alerts fired off a deviation from the six-week historical average and pushed to users at the location, which is precisely the 'deviates from its historical pattern' half of the claim. It is not operator-configurable, so partial, not yes. source |
| reporting-nl-query | unknown / grade F, 'No natural-language or AI query assistant over Simphony operator data is documented.' | resolve-to-no | Oracle does now ship a generative AI assistant, so the bare assertion was out of date - but its published scope is support and SOP troubleshooting, which is the exact carve-out in the claim wording. Paired with the complete Reporting and Analytics user guide contents, whose ad-hoc tooling is the report builder, Excel iQuery and Audit & Analysis, that is positive evidence rather than a failed search. oracle.com/news 403s to automated retrieval, so the release was read on PR Newswire. source |
| multi-location-corp-vs-franchisee-roles | unknown / grade F, 'Multi-level privilege scoping exists, but a documented franchisor-versus-franchisee tenancy separation - separate employee records, banking and labour ownership under one enterprise - was not found.' | resolve-to-partial | rause/c_org_hierarchy.htm answers both halves explicitly: one hierarchy per enterprise with a single corporate root and role-to-level scoping (the corporate-sees-franchisee-sales and enforce-config half), and no tenancy construct at all (the franchisee-owns-its-own-data half). simcg/c_menu_item_master_availability_methods.htm supplies the franchisor-enforced Core designation. Documented capability with a named structural shortfall, so partial. source |
| multi-location-enterprise-sso | unknown / grade F, 'EMC uses Oracle's own authentication with default-on emailed OTP MFA. No SAML/OIDC federation against a customer IdP, and no SCIM provisioning, appears in the Simphony security documentation.' | resolve-to-partial | The prior pass searched the Simphony Security Guide, which is genuinely silent - the feature is documented in the back-office book instead. rause has a whole SSO chapter: bring your own IdP, bring your own OCI IAM identity domain, federate, migrate existing cloud users. The earlier statement about EMC turns out to be right and is now sourced ('EMC does not support SSO and requires a separate password'), and the provisioning half fails on Oracle's own limitation list (no SAML JIT provisioning, no direct user management in the domain). Capability present, materially limited. source |
| extensibility-doordash-preferred | unknown / grade F, 'The DoorDash Preferred Integration Partner cohort page could not be retrieved - the cited blog URL redirects to merchants.doordash.com and then 404s.' | resolve-to-no | Found the enumerated cohort on DoorDash's own newsroom rather than the learning centre: eleven named partners, Oracle absent. get.doordash.com/en-us/learning-center/preferred-integration-partners does 301 to merchants.doordash.com and then 404, which is what defeated the earlier pass, but merchants.doordash.com/en-us/learning-center/doordash-preferred-integrations-program serves the thresholds and about.doordash.com/en-us/news/doordash-preferred-integrations-program serves the list. A named cohort is a genuine enumeration, so absence from it is a finding, qualified by there being no 2026 refresh. source |
| extensibility-accounting-connectors | unknown / grade F, 'No Oracle-maintained QuickBooks or Xero connector for Simphony is documented. Inventory Management sends invoices to Accounts Payable generically.' | resolve-to-no | Pinned down what 'generically' means: invug/c_maintenance_interface_definition.htm states the AP interface is a custom export-format template, and rause/toc.htm shows the reporting side is export configurations delivered on a schedule by delivery profile. That is the vendor documenting the file-export workaround in place of a connector, which is positive evidence against a table-stakes claim that explicitly requires mapped journal entries rather than CSV-only export. Third-party middleware may bridge this, but the claim asks for vendor-maintained connectors. source |
| reliability-offline-card-auth | unknown / grade F, 'The offline modes page contains no mention of credit card authorisation at all.' | resolve-to-yes | The prior pass looked in the POS User Guide's Online and Offline Communication Modes topic, which is about workstation-to-CAPS/Enterprise connectivity and genuinely says nothing about cards. Offline card handling is documented in a different book entirely - payments-platform/latest/pcsrf (Payments Processing), topic_13 Offline Transactions - which distinguishes the workstation-offline case from the terminal-offline-from-host case and describes stored payments being forwarded to the processor on reconnect. source |
| reliability-offline-decline-liability | unknown / grade F, 'No public Oracle statement on who bears an offline-approved decline.' | resolve-to-partial | Oracle does publish the decline-after-reconnect behaviour - REFUSED settlement journal type, zero settlement amount, negative cancel amount, no payout - which is the loss landing on the operator, but it is documented as reporting mechanics rather than as a liability statement, and no offline cap of any kind is published. Half the claim is met, so partial rather than yes or unknown. source |
| reliability-sync-conflict-handling | unknown / grade F, 'Replay on reconnect is documented; conflict resolution for concurrent edits to the same check across a partition is not.' | resolve-to-partial | The Check and Posting Service chapter does document a conflict strategy - CAPS as 'arbitrator of check sharing by maintaining a record of check ownership' - which is a lock/ownership answer to the question the claim asks. It stops short of a resolution rule for the concurrent-edit case, and the guide's own hedge ('minimizes the likelihood') plus red mode, where CAPS is unreachable, leaves that case unspecified. Partial with the shortfall named. source |
| reliability-247-live-support | unknown / grade F, 'whether 24/7 live support is included in the base Simphony subscription or is a premium tier is not published' | resolve-to-partial | It is published, in the contract policy rather than on a marketing page. HDP v3.12 section 5.1.4 puts 24x7x365 technical service-request assistance inside base Oracle Cloud Support, and the Oracle Restaurants Cloud Services Service Descriptions (11 June 2026) subject every Simphony edition's order to that policy. It falls short of the claim as worded because 5.2.2 offers telephone only 'as available' beside web support and restricts it to designated technical contacts, and non-technical service is 8:00-17:00 local. source |
| reliability-hardware-replacement-sla | unknown / grade F, 'No published turnaround figure.' | resolve-to-yes | There are published turnaround figures, in Oracle's contract policy PDFs rather than in the Simphony documentation. The Hardware and Systems Support Policies name an advance-exchange program specific to MICROS point-of-service hardware with 'Next business day parts exchange', and the Hardware Warranty adds a 2-business-day CRU shipment target and a 2-business-day on-site response target within designated service locations. The claim asks only that such a program with a stated turnaround be included or purchasable, and it is purchasable. source |
| commercial-no-early-termination-fee | unknown / grade F, 'No published Oracle terms address a Simphony early termination fee.' | resolve-to-no | Published Oracle terms do address it, in the direction opposite the claim. oracle.com HTML 403s to retrieval but the contract PDFs under oracle.com/contracts/docs do not; the current Online CSA v062223 states at 2.1 that an order is non-cancelable and sums paid nonrefundable, and grants a refund only under the 6.3 warranty remedy. That is positive evidence that no no-ETF provision exists in the vendor's published terms, not mere absence of evidence. source |
| commercial-autorenew-terms-published | unknown / grade F, 'Auto-renewal term and cancellation notice window live in the order document and the Oracle Cloud Services Agreement, not in any publicly retrievable Simphony term sheet.' | resolve-to-no | Tested the prior assumption by retrieving the CSA itself rather than reasoning about it: the agreement has no renewal clause, and section 9.2 affirmatively points at the order document for the Services Period. The Restaurants service descriptions, the other public document incorporated into every Simphony order, likewise state no renewal term or notice window. Because the claim is about publication, and the complete public contract surface reachable to me states neither, this is positive evidence of absence rather than a failure to find. source |
| commercial-soc2-attestation | unknown / grade F, 'Oracle states it cannot provide SOC 2 attestations for on-premises products ... no Simphony Cloud Service SOC 2 Type II statement was located.' | resolve-to-partial | For the cloud service, which is what the claim is about, Oracle does publish both the attestation programme and the delivery mechanism, in HDP v3.12 section 1.12, and the Restaurants service descriptions bind every Simphony order to that policy. It falls short of yes because the language is permissive rather than an assertion of a current attestation ('may conduct', 'to the extent such reports are maintained', scope 'may vary by Service and country') and never says Type II or names Simphony. source |
| commercial-privacy-dsar-tooling | unknown / grade F, 'Oracle publishes corporate DPAs, but Simphony-specific in-app DSAR locate/export/delete tooling is not documented.' | resolve-to-partial | In-app DSAR tooling is documented, in the back-office Reporting and Analytics user guide rather than in simcg: a Data Privacy module with a machine-readable Personal Data Report download and an irreversible De-identify action, mirrored by consent withdrawal and DTS de-identification in the Simphony EMC. It is partial rather than yes because every documented surface operates on People Management records - employees and system users - and the claim asks for an individual guest's records. source |
| commercial-wcag-kiosk-accessibility | unknown / grade F, 'no Simphony kiosk or consumer-ordering ACR/VPAT was located.' | resolve-to-partial | A Simphony ACR does exist and is retrievable on docs.oracle.com even though the oracle.com VPAT index 403s: Simphony Cloud Suite 6.0, VPAT 2.3, 23-MAY-24, claiming WCAG 2.1 A and AA and Revised Section 508, and its covered-items list includes the guest-facing QR Pay surface. It cannot be a yes because the kiosk is neither covered by it nor covered by any separate MICROS ACR I could locate, and the tactile/audio non-visual access mode the claim requires on kiosks is documented nowhere in the Simphony documentation set. source |
| guest-loyalty-10dlc-registration | no / grade B, 'Gift and Loyalty has no SMS send path, so there is no A2P 10DLC brand or campaig' | downgrade-to-unknown | Re-read the cited coupon configuration page. It lists three Issue Instructions values and nowhere claims to enumerate every channel by which an offer can reach a guest; it is a task procedure, not a supported/unsupported table. The enumeration is also narrower than the claim, which asks about A2P 10DLC brand and campaign registration for SMS sent through the platform - and Oracle's Gift and Loyalty feature page says campaigning runs 'in conjunction with third-party sales marketing and campaigning products', leaving the SMS path unenumerated. No Oracle page addresses 10DLC in either direction, so this is absence of evidence. source |
| labor-photo-punch-verification | no / grade B, 'The Security Guide's POS Client User Authentication topic enumerates how a user ' | downgrade-to-unknown | Retrieved the cited security topic myself: it enumerates how an employee provides an ID at the POS client and includes fingerprint biometrics, but it is a security guide topic about authentication, not an enumeration of what a timecard entry may capture - and the claim's first half (a photo attached to the punch) is not an authentication method. The timekeeping settings page the verifier leaned on returns 404 at the Simphony path; the release-9.1 page at cd/E80526_01 is a step procedure over clock-in timing rules with no claim to list every option. On a differentiator claim, an authentication list is not positive evidence that photo punch is absent. source |
| labor-geofenced-mobile-punch | no / grade B, 'Clocking In and Out is a workstation procedure - press the Clock In key, acknowl' | downgrade-to-unknown | Retrieved the cited procedure: it is the six-step Clocking In and Out task (Clock In key, Time Card Changes acknowledgement, close checks, Clock Out) and makes no claim to be the only clock-in path. The supporting evidence was two guide tables of contents, which the enumeration bar excludes. I also retrieved the Labor Management guide TOC (15 chapters, Employee Self Service = schedules, time off, shift changes) and found no location or geofence setting anywhere, but equally no Oracle statement that mobile or location-restricted punching is unsupported. That is absence of evidence. source |
| inventory-lot-traceability | no / grade B, 'Creating a New Item enumerates the item master fields - Type, Item No., Item Gro' | downgrade-to-unknown | Retrieved the cited item master page and the blank receipt procedure. Neither carries completeness language - the item page's instruction is 'enter information in the following fields' - and the item form's HACCP tab, the food-safety surface where lot identity would sit, is documented only as a HACCP Required checkbox with further settings deferred to the Cost Centers module, which the enumeration does not cover. I found no MICROS Inventory Management lot or batch documentation and no counter-evidence that the capability exists, but a field list that disclaims exhaustiveness and skips the relevant tab is not positive evidence of absence. source |
| reporting-nl-query | no / grade D, 'Oracle's 18 March 2026 announcement of the Simphony Smart Assistant describes a ' | downgrade-to-unknown | Retrieved the cited press release: it announces a single capability, a generative assistant for troubleshooting, with 'no invoice scanning, natural language reporting, or analytics query capabilities' described - that is silence on this claim, not a denial. The supporting enumeration is a user-guide table of contents, which the bar excludes. Counter-evidence cuts the other way: Oracle Analytics' 2026 updates added a natural-language AI Assistant and AI Data Agents, and I could not establish whether those reach the Simphony Reporting and Analytics tenant. A grade-D `no` built on marketing scope plus a TOC does not meet the bar. source |
| extensibility-accounting-connectors | no / grade B, 'Inventory Management's accounts-payable hand-off runs through Interface Definiti' | upgrade-to-partial | The `no` rested on the absence of any named accounting package in the Inventory Management guide, which I confirmed (Interface Definitions really are 'custom templates that define the format for exported data') - but the enumeration is the wrong book. Oracle NetSuite publishes a first-party NetSuite Connector for Oracle MICROS Simphony, announced 28 March 2024 and documented in the NetSuite Applications Suite help on docs.oracle.com, which performs a daily import of Simphony financial data into NetSuite over SFTP. That is a vendor-maintained connector to a named GL, so the absence assertion is refuted; it falls short of the claim only because no QuickBooks Online connector exists. source |
| commercial-autorenew-terms-published | no / grade A, 'Neither publicly posted governing document states a renewal term or a cancellati' | upgrade-to-partial | The prior pass read one published form (Online CSA v062223) and generalised. Oracle publishes several CSA forms, and the transactional US CSA I retrieved (saas_csa_us_2069270.pdf, via a browser user agent - the contract PDFs serve even though oracle.com HTML 403s) contains an Auto Renew definition at s1.2 and, at s9.1, an explicit thirty (30) day customer non-renewal notice window and a ninety (90) day Oracle one. The claim asks whether the auto-renewal term and notice window are publicly stated: the notice window plainly is. It stays partial because s1.2 defers eligibility and any renewal terms to the Service Specifications in the order, so the term length is still quote-resident. source |
| extensibility-doordash-preferred | no / grade E, 'DoorDash's programme announcement (as of 12 May 2025) names the inaugural Preferred In' | upheld | Retrieved about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 (HTTP 200, full article body, not an SPA shell). It is a genuine refresh of the programme dated 18 May 2026 and enumerates ten partners - Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper - with Oracle, MICROS and Simphony absent, and ChowNow dropped relative to the 2025 list. The value therefore stands on a current enumeration rather than a year-old one, and the record's caveat that no 2026 cohort existed was factually wrong and has been deleted. Grade stays E: this is a third-party programme roster, not vendor documentation. source |
| inventory-cogs-gl-export | partial / grade B, 'Invoicing documents "Sending to Accounts Payable", and master data carries Account Cla' | upheld | Re-retrieved the Inventory Management guide contents (200, 26 chapters) and opened the four relevant leaf topics myself. The value survives but the reasoning did not: the note claimed no configurable GL account mapping screen is documented, and t_masterdata_create_accnt_class.htm plainly documents one - account numbers per item group across Inventory, Expense, COS and Accruals accounting departments. The real and only shortfall is the export FORMAT: c_maintenance_interface_definition.htm defines interface definitions as "custom templates that define the format for exported data", so the operator authors the layout and no named accounting package appears in the guide. I also checked whether the NetSuite Connector supplies the named format and it does not - its documented and announced scope is POS transactional financials, with no AP, COGS, GL or journal-entry payload. Partial stands, on corrected grounds. source |
| extensibility-accounting-connectors | partial / grade B, 'One vendor-maintained connector exists, to Oracle's own GL: the NetSuite Connector fo' | upheld | Independently re-retrieved both NetSuite help pages (200, real content, not SPA shells). The connector is real and first-party: the supported-connector chapter enumerates Oracle Simphony among NetSuite Connector's targets, and the Simphony topic gives the full credential field list. But the record attributed the daily-import payload to that help topic, and the topic contains no payload description at all - it stops at credentials. The tender-name / carry-over / daypart / items-sold wording is from NetSuite's 28 March 2024 launch release, which I re-read and which also names no accounts-payable, COGS, general-ledger or journal-entry content. Partial stands, with the citation split correctly and a second shortfall added: the claim asks for mapped journal entries and nothing published describes any. source |
| order-capture-voice-ai | partial / grade A, "No first-party voice agent is documented. Transaction Services Gen2 is the pub" | upheld | Citation-staleness check. The recorded URL .../simphony/omsstsg2api/ 301s to .../simphony/stsgg/ (200, 8027 bytes), and per the standing rule I read the destination rather than re-pointing blind: it is the same document, titled "Simphony Transaction Services Gen2 API Guide - About the REST APIs", F77391-30, dateModified 2026-07-27, describing the Organizations, Configuration, Checks, Employee and Notifications APIs. I then verified the specific assertion at leaf level - stsgg/api-checks-api.html enumerates "Post a new check" (POST /api/v1/checks), "Post a new round to a check" and "Post calculate totals for a check" - which is the order-injection capability the note claims, now confirmed at a live URL rather than a directory root. The licensing shortfall rests on a separate page I re-retrieved the same day (c_lic_simphony_cloud.htm, 200, 21076 bytes), which still lists six separately licensed Transaction Services part families each with Premium or Standard as a stated prerequisite. Neither leg of the cell depended on the dead path. No first-party Oracle voice agent is documented in the STS Gen2 guide, so the cell does not rise to yes; a licensed-SKU integration path is not a published voice-AI partner programme, so it does not fall to no. Value unchanged, URL and note corrected. source |
| hardware-pricing-transparency | no / grade C, cites the Workstation 6 page with the admission that it 403s and that 'the record cites a page nobody in the chain has read' | upheld | Re-opened because the 2026-08-11 link-check refuted the 403 premise and found a dollar figure on the cited page. Read www.oracle.com/robots.txt in full first (2,649 bytes, HTTP 200, 16 groups; ClaudeBot is named and given Allow: / with ten Disallows). Matched every path mechanically with scripts/lib/robots.mjs: /food-beverage/** is permitted (longest match is Allow: /), while Oracle's actual price-list trees /us/corporate/pricing/ and /a/ocom/docs/corporate/pricing/ are Disallow'd to ClaudeBot and were not fetched. Then read the five permitted hardware pages, all HTTP 200: Workstation 6 (62,125 bytes), Workstation 3 (59,672), Workstation 8 (55,692), MICROS Tablet (62,552) and the hardware index (49,758); /pos-hardware/workstation-625/ and /655/ are 404 (2,993 bytes, byte-identical to each other and to the withdrawn /pricing/ path — that is this host's calibrated 404 body, and the 625/655 SKUs are the retired Workstation 6xx generation, not current). No list price on any of them. The index page states the posture in Oracle's own words: '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', with a 'Get my free consultation and quote' CTA; Workstation 8 offers only 'Request a quote'. The US$1 figure on Workstations 6 and 3 is real but is not a SKU price and does not move the cell: it is a conditional switching promotion ('Get a Workstation 6 for US$1', 'Ask about how you can make the switch to a Workstation 6 for just US$1'), contingent on adopting Simphony and obtained only by 'Talk to an Oracle product expert'. The claim is 'hardware prices are published per SKU ... rather than quote-only' and its purpose is estimating a build-out without sales contact; a promotional US$1 that requires sales contact and hides the hardware cost inside an unpublished subscription defeats that test rather than passing it. Considered upgrade-to-partial for the published figure and rejected it: partial would need a real per-SKU number for at least some of the line, and four of five current SKUs carry no figure at all. Upheld as `no`, now on first-hand positive evidence instead of a reseller-asymmetry inference, and the note's false 403 admission is removed. Also correcting the citation from the Workstation 6 page to the hardware index, which is where the quote-only statement lives. source |
| hardware-ownership-vs-lease | unknown / grade F, "www.oracle.com returns 403 to automated retrieval ... and the hardware warranty PDF also returned 403" | resolve-to-partial | Seven sessions carried this cell behind a barrier that does not exist for the client that would fetch it. www.oracle.com answers HTTP 200 to POSAtlasBot on every page tried; the named warranty PDF is 404, not 403. Oracle then states the acquisition model itself, in the Hardware and Systems Support Policies: covered equipment is "sold by Oracle (either directly or by an Oracle-authorized distributor)", and the customer has an "original equipment purchase" and may relocate the hardware on notice. Not a yes: Oracle never names a lease alternative and no transfer-of-title clause was retrieved -- that is in the Master Agreement under /corporate/contracts/, which `*` Disallows. source |
| hardware-rma-sla | unknown / grade F, "Tried the Oracle hardware warranty policy directly (…hardware-warranty-policy.pdf, HTTP 403)" | resolve-to-partial | The premise is wrong twice: that URL is 404 rather than 403, and the answer was already in this record. reliability-hardware-replacement-sla cites the Hardware and Systems Support Policies at grade A for exactly this content. Re-verified first-hand: "Oracle Advanced Parts Exchange for Oracle Point of Service Hardware consists of: ... Next business day parts exchange". Partial not yes because the warranty TERM sits in a separate document I did not retrieve. source |
| hardware-usable-after-churn | unknown / grade F, "Oracle's contractual pages and the hardware warranty PDF on www.oracle.com return 403 to automated retrieval" | upheld | Value survives, premise does not. The 403 is a property of the ClaudeBot-family client, not of the host: the checker gets 200. Re-read the support policies in full; they govern support entitlement and say nothing about post-termination use of the hardware. Stating the corpus rather than generalising, per the enumeration rule. source |
| payments-softpos-tap-to-pay | unknown / F - Full-text search of all 1,193 topics in the four Simphony books for tap to pay, tap-to-pay, contactl | resolve-to-no | Positive control checked and it holds. Re-read fbopp/c_terminals_intro.htm in the corpus: the quoted 'you’ll receive a payment terminal' and the four device topics (Castles Device S1F2, Verifone e285, P400 and V400m, Verifone P630) are byte-present, and the page is the Payment Terminals chapter of a book-level registry-closed library (fbopp 64, pcsrf 84, pcswn 3, all held). That is a real acceptance-device enumeration with room for a phone-acceptance option, not a floor. Re-ran the lexical test myself: /Tap to Pay|Tap to Phone|SoftPOS/ matches 0 of 4,840 documents. DROPPED the analyst's closing retrieval note as false: the corpus index holds this page under the SLASH form at 402 bytes of extracted text, not a 'broken underscore form' (the underscore mangling affects tabss and weset, not fbopp), so the claim that the indexed form 404s is wrong and has been removed. Value, grade and URL unchanged. source |
| payments-offline-store-and-forward | unknown / F - Simphony's documented offline story is about checks, not authorizations: t_properties_offline.htm (P | resolve-to-partial | Every quote verified byte-present. 'Offline Authorizations', 'Allow Manual Authorization Credit Card' and 'Manual Card Data Entry Retries' are on the cited fbopp/t_emc_payments.htm; the corroborating 'Added offline authorization information to several reports...' sentence is on pcswn/c_new.htm and IS attributed to that sibling URL in the note. Shortfall is honestly stated and matches the cell's 'configurable per-transaction and cumulative offline limits' leg, which is genuinely unmet. Grade B correct (vendor product documentation). source |
| payments-offline-decline-liability | unknown / F - Searched all 1,193 Simphony topics for chargeback, dispute, representment, liability and floor limit | resolve-to-partial | Quotes verified on pcsrf/c_payment_exceptions.htm ('Offline Count', 'Number of offline authorizations.', 'Exception Count', 'Variance Amount'); the Exception Details material is attributed to its own sibling URL. The liability half is correctly withheld. Precedent (52% no, 28% partial) does not embarrass a partial that rests on a positively-evidenced reporting leg. source |
| payments-house-accounts | unknown / F - Searched all 1,193 topics for house account, on account, credit limit and statement. The only accoun | resolve-to-partial | All three gnlug topics verified: 'a credit card for house accounts', 'A consolidated bill', 'Default Credit Limit', 'Credit Denial Text', 'Balance column', 'Post Transaction'. Sibling pages are each cited by their own URL rather than credited to the row URL. The withheld leg (periodic statement/invoice generation) is the cell's third element and is genuinely absent from the book. Upheld unchanged. source |
| payments-chargeback-tooling | unknown / F - The words chargeback, dispute and representment do not occur once across the 1,193 topics of simcg, | resolve-to-yes | MY SUSPICION WAS WRONG AND I TESTED IT. I read pcsrf/c_disputes.htm, t_disputes_defend.htm and c_chargeback_detail.htm directly. Chapter 7 is titled 'Credit Card Disputes (Issued Through Reporting and Analytics)' — i.e. the tooling lives inside Simphony's own Reporting and Analytics back office, not a detached PSP portal. Verified byte-present: 'View, accept, or reject chargebacks.'; 'Your main dashboard includes a tile with' dispute details; 'Defend : you disagree with the chargeback' 'and you have supporting evidence that you can upload and submit'; on the task page 'click the Disputes tab', 'Select the Defense Reason' and the per-scheme limit '19 pages'; and on Chargeback Detail both 'Check number' and 'Drills down to Check Detail', which is the POS-record linkage the cell demands. All three legs of the cell (dashboard, evidence submission, assembly from the POS transaction record) are met. The Oracle-Payments scoping is not a downgrade: the four precedent yes records (toast, square-for-restaurants, stripe-terminal, lightspeed-restaurant) are scoped to their own processing too, so scoping the subject to first-party payments is the norm for a yes on this cell, not an exception. The record's prior unknown said 'the Oracle MICROS Payment Cloud Service configuration guide does not enumerate its merchant-portal features' — pcsrf now does, and that is genuinely new. Upheld at yes, grade B. source |
| payments-payout-timing | unknown / F - Re-read the Oracle MICROS Payment Cloud Service configuration guide (docs.oracle.com/en/industries/f | resolve-to-partial | Verified on pcsrf/topic_5.htm: 'two days from', 'three days from', 'Settlements and payouts do not happen on Sundays or bank holidays.' and the '2:00 a.m.' cut-off are all byte-present. The published-schedule leg is met; the instant/next-day funding leg is affirmatively absent from a registry-closed library. Partial is the correct split. Grade B correct. source |
| hardware-tap-to-phone | unknown / F - Read the Oracle Restaurants Payment Service feature reference contents (payments-platform/latest/pcs | resolve-to-no | Same fbopp enumeration, verified. The two supporting hardware quotes were checked against the corpus and are real, though the index stores those two pages under mangled underscore filenames (tabss_c_tablet_technical_specifications.htm, weset_c_basic_features.htm): 'Optional; Supports ISO/IEC 14443 A Reader/Writer' and 'Reads MICROS Contactless Employee ID Cards for employee' are both present and both are attributed to their own URLs in the note. /Tap to Pay|Tap to Phone|SoftPOS/ = 0 of 4,840 confirmed by my own run. Upheld. source |
| order-capture-qr-same-check | unknown / F - Enumerated the complete flat manifests of the Configuration Guide (docs.oracle.com/en/industries/foo | resolve-to-partial | MY SUSPICION WAS WRONG. I read the STS Gen2 pages and the API does the specific thing the cell asks. Verified byte-present on the cited page: 'API adds a round to an existing check.' and 'This operation does not alter items already on the check from previous rounds.'; and on the attributed GET sibling, notifications are supported 'including when a check was initiated from OPS and STS Gen2 is used to add a round' — a check opened by a server at the POS, appended to by an external channel keyed on checkRef. That is not a generic check mechanism read as a product capability; it is the exact append-to-an-open-check semantics. The guest-facing QR front end is correctly withheld, and the note does not overclaim it. Grade A is right by source class (vendor API reference), not by effort. source |
| order-capture-order-ready-signal | unknown / F - Read the entire Delivery Connectors chapter as enumerated in simcg/toc.htm: c_delivery_connectors.ht | resolve-to-partial | Verified: preparationStatus with Uninitialized/Submitted/Prepared/AllPrepared/Packaged, the AllPrepared 'bumped' gloss, the 'KDS configuration is required for all KDS-driven statuses; without KDS, only Submitted is supported.' sentence, and the CheckNotification line are all byte-present on the cited GET page. The marketplace leg is correctly withheld, and the ccapi census check (enableUberEatsIntegration / enableDeliverooIntegration being order-sourcing switches with no status-callback field) is a legitimate use of a registry-closed surface. Grade A correct. source |
| menu-pricing-upsell-prompts | unknown / F - Grepped the full text of all 1,193 topics in simcg, sipou, kdscu and simgi for upsell, suggestive, c | resolve-to-partial | Verified on plug-ins.html: 'supports menu browsing, item configuration, cart review, optional upsell and tips, payment, and receipt workflows' and the Enhanced Next Page Config wording are byte-present. I re-ran /attach rate/ myself: 0 of 4,840. rarrg is held whole (223 topics, zero queue) so the attach-rate absence rests on a report census with room, not a floor. Partial matches precedent exactly (74% partial, 0% yes). Grade B correct — plug-ins.html is vendor product documentation, not marketing. source |
| menu-pricing-countdown-auto-86 | unknown / F - Read c_menu_item_master_availability_methods.htm, which enumerates Simphony's availability mechanism | resolve-to-partial | Both ccapi field names verified byte-present on the cited registry-closed op page, with the quoted descriptions intact. The withheld leg (scheduled auto-restore) is real: the corpus's own workstation tool is manual toggling. Grade A correct by source class (vendor API reference). source |
| kitchen-order-ready-callback | unknown / F - Read the complete KDS Configuration and User Guide manifest (simphony/kdscu/toc.htm, 129 topics). Th | resolve-to-partial | MY SUSPICION WAS WRONG. Verified on api-notifications-api.html: 'The STS Gen2 Notifications Service is used to manage call back POST notifications messages...' and 'At present retries are not supported. A notification will be sent only once.' are byte-present, and the status field is defined as the KDS-driven preparationStatus on the attributed Checks page. The analyst did NOT read a generic notification mechanism as the product capability — the courier/marketplace leg, which is what the cell actually turns on, is explicitly withheld, which is why this is partial and not yes. Grade A correct by source class. source |
| delivery-3p-reconciliation | unknown / F - Enumerated the Reporting and Analytics Reports Guide manifest (back-office/20.1/rarrg/toc.htm, 222 r | resolve-to-partial | Verified on rarrg/c_order_channel_sales_add.htm: 'Menu item sales and performance report that shows order' and 'major group, family group, and menu item sales details' are byte-present. The note correctly kills the brief's proposed payment-endpoint evidence and states the marketplace-payout half is absent from a whole-held 223-topic report census. Precedent (35% partial, 3% yes) supports partial. Grade B correct. source |
| digital-upsell-engine | unknown / F - Enumerated the whole Simphony/GloriaFood integration book (docs.oracle.com simphony/simgi/toc.htm, 3 | resolve-to-partial | Verified on plug-ins.html. The note itself declines the stronger marketing sentence from the www.oracle.com product page and says so — exactly the grade discipline required — and it names the simgi (GloriaFood) zero-file hole rather than treating it as absence. Partial matches precedent (60%). Grade B correct. source |
| digital-subscriptions | unknown / F - Checked the Gift and Loyalty user guide manifest (back-office/20.1/gnlug/toc.htm), whose program typ | resolve-to-partial | Verified on gnlug/t_using_mealcard.htm: 'Period Reload Amount' and 'Period Carry over Amount' are byte-present. Note that the cell allows 'a per-period item entitlement' as one satisfying form, so this is arguably under-scored rather than over-scored; the analyst's conservatism (no recurring billing, no paid tier, CrowdTwist unmined) is the right side to err on. Upheld at partial, grade B. source |
| guest-loyalty-review-capture-routing | unknown / F - Enumerated the Gift and Loyalty user guide (back-office/20.1/gnlug/toc.htm) end to end -- FAQ, card | resolve-to-partial | Verified: 'Dynamic Barcode', 'survey codes' and the barcode/QR trailer wording are byte-present on plug-ins.html. MOVE 8 handled honestly by the analyst — the note itself states 'This URL is already cited 11x in claims.jsonl' and names the new sentence rather than the page as the find. The routing half is correctly withheld. Partial matches precedent (57%). Grade B correct. source |
| labor-photo-punch-verification | unknown / F - Simphony's POS Client User Authentication topic enumerates identification methods (magnetic card, RF | resolve-to-no | Value survives; one factual claim in the note did not. This is the auditor brief's own example of a legitimate positive control — device feature tables that enumerate employee sign-in mechanisms — and it checks out: on the Tablet 721P table the MSR row reads 'Reads magnetic stripe cards for employee sign in, authorization, and loyalty programs' while the camera row reads only 'Use to take photographs', and the Workstation 820 table gives RFID as 'Reads MICROS Contactless Employee ID Cards for employee sign in'. Both quotes verified byte-present (the corpus stores those pages under mangled underscore filenames; the cited slash URLs are the canonical ones). BUT the note's lexical claim was wrong: I ran /facial|face recogn/ myself and got 1 of 4,840 — 'Setting face recognition' in the Lenovo Tab K10 manual. Corrected in the note above; it is an OS unlock feature on a validated device, not a timecard photo, so the verdict is unaffected. Precedent: 56% no, 0% yes. source |
| labor-geofenced-mobile-punch | unknown / F - The prior `no` rested on a clock-in task procedure plus two tables of contents (the InMotion Mobile | upheld | Downgraded. THE AUDITOR'S SUSPICION 5 WAS HALF RIGHT and this is the half that falls. Test applied: does the cited page have room for the claim's subject? The ESS chapter TOC enumerates ESS topics, so it has room only for 'is clocking an ESS function' — it has no room for 'can a punch on the Android POS client be location-restricted', which is where the cell actually lives. Second test: does the record already hold and reject this argument? Yes — verbatim, in the current claims.jsonl rationale, including the Android-handheld counter-premise the new note never addresses. Third: the note's lexical claim is also partly false — I ran /\bGPS\b/ and it matches the Lenovo Tab K10 spec sheet ('GPS/GLONASS/Beidou/A-GPS'), i.e. a validated Simphony Android device that carries the sensor. Precedent is 50% no / 41% unknown, so unknown is not out of line. |
| labor-fair-workweek-support | unknown / F - Checked the Labor Management User Guide contents (docs.oracle.com/en/industries/food-beverage/back-o | resolve-to-no | UPHELD, and I strengthened it rather than weakening it. THE AUDITOR'S SUSPICION 5 IS WRONG ON THIS HALF. Test: is the cited page a floor in enumeration's clothing? No — I read lmusg/t_config_locations.htm in full and it is a genuine configuration screen enumeration. Its procedure steps assign exactly Labor Pay Rule, Pay Period Calendar, Wage and Tip Law, Child Labor Law, Tip Pool and 'Time card adjustment acknowledgement required', and its preceding table enumerates the configuration areas (Timekeeping, Overtime, Premium Pay, Labor Law Compliance, Pay Periods, Work Hours and Break Periods, Tip Pools, Employee Management, Scheduling, Staffing). A predictive-scheduling rule set would have to be assignable there and is not. Every quoted string verified byte-present. Second test, decisive: the record's own prior rationale named ONE reason for unknown rather than no — the unextractable lmsch PDF — and this corpus holds it text-extracted. I ran /predictab|advance notice|fair work/ across all 4,840 documents including lmsch: 0 matches. The named blocker is discharged, so the promotion to no is legitimate. Grade B correct. source |
| labor-qualified-tips-w2-reporting | unknown / F - Opened lmusg/t_config_org_pay.htm (Configuring Payroll Preprocessing Behavior and Overtime Labels): | resolve-to-partial | Value and grade survive; an attribution did not. Verified byte-present on the cited timecard endpoint: 'chrgTips', 'The value of tips posted to charge payments such as credit cards or room charges', and the indirTips gloss 'Cash tips that an employee (like a bus person) receives indirectly from servers or bartenders'. The tip-class separation is real and the 2026 W-2 apparatus is genuinely absent. BUT 'External Payroll ID' is NOT on the cited page and NOT in lmapi — I searched the string corpus-wide and it appears on biapi Get Employee Dimensions and in the ebsse export spec. The note credited the row's URL with another page's field; re-attributed above. Grade A correct by source class (vendor API reference). source |
| inventory-shelf-life-expiry | unknown / F - Read the complete Inventory Management User Guide contents (26 chapters at back-office/20.1/invug/to | resolve-to-partial | MY SUSPICION 8 WAS WRONG AND THE TWO POSITIONS ARE CONSISTENT. Verified byte-present on the cited page: 'Shelf Life', 'This column shows the length of time the item stays fresh', 'Perish On', 'This column shows the day the item is no longer usable and needs to be classified as waste'. The consistency test: shelf-life gets a partial because there is POSITIVE, quotable evidence of an expiry-bearing surface, while lot-traceability stays unknown because there is NO positive evidence and its absence is unmeasurable behind an unpublished HACCP tab. Positive evidence supports a partial; unmeasured absence supports unknown. Those are the same rule applied to different evidence, not two rules. One attribution fixed: the 'Preparation and Thaw Pull Reporting' user right is not on the cited page, it is on invug/r_userrights_production.htm; re-attributed above. Grade B correct. source |
| reporting-nl-query | unknown / F - Oracle's 18 March 2026 Simphony Smart Assistant announcement describes only support and SOP troubles | upheld | Downgraded. THE AUDITOR'S SUSPICION 3 WAS RIGHT, with a twist. Test one: is the cited enumeration real? I read c_reports.htm in full — it is a chapter introduction of about a thousand bytes, and its opening sentence is a summary of the chapter's own topics, not a closed statement of every query interface available to the operator. It has no room for a product Oracle sells alongside Simphony. Test two: is OAC in subject? I fetched the product-page text and confirmed the sentence verbatim; Oracle offers OAC as the analytics layer FOR Simphony data, which puts it inside the operator's reach even though it is a separate SKU. Test three: did the corpus measure it? /Oracle Analytics/ = 0 of 4,840 — zero coverage, so nothing here could have disagreed. The record's own prior rationale had already reached this conclusion ('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') and the new note does not engage with it. Precedent: unknown is the modal value at 46%; only 20% score no. |
| multi-location-royalty-calculation | unknown / F - Checked the complete Reporting and Analytics User Guide contents (back-office/20.1/rause/toc.htm, in | resolve-to-no | UPHELD after I tried hard to break it. THE AUDITOR'S SUSPICION 4 IS WRONG. I ran /royalt/ myself: 14 files, and I listed every one — Apache 2.0, Creative Commons 4.0, GPLv2, LGPL 2.1, EPL 1.0 and 2.0, Mozilla 1.1, Ms-PL, the SQLite Encryption Extension licence, the U.are.U SDK EULA and a Lenovo manual. Every hit is open-source or third-party licence boilerplate; none is a product feature. /ad fund|marketing fee/ = 0. The suspicion was that royalty would live in EMC configuration (simcg, a declared subset here) rather than in the reporting books — but the enumeration doing the work is not simcg-shaped. Three independent closures have room and are silent: (1) the cited iQuery subject-area table, which opens 'The following table lists each subject area available in iQuery' and is a closed list of the reporting warehouse's subject areas; (2) rarrg, the Reports Reference Guide, held whole at 223 report topics with a zero remaining queue — a franchise royalty engine that produced no report in a 223-report census would be remarkable; (3) ccapi, a REGISTRY-CLOSED census of 887 configuration operations, which is the EMC configuration surface exposed as an API and carries no royalty object. Add the publisher's own library registry naming ~40 books with no franchise or royalty title. That is a positive control, not a bare zero-hit over a floor. The one premise the prior rationale rested on — 'oracle.com's franchise and product pages return 403 to automated retrieval' — is now dead (the product page answers 200), which removes the reason the record previously withheld. Precedent 36% no is the modal non-unknown value. Grade B correct. source |
| multi-location-royalty-collection | unknown / F - Checked Reporting and Analytics (rause/toc.htm - Export Configurations, Delivery Profiles and Export | resolve-to-no | Upheld on the same three closures. The derivation ('there is no calculated royalty to collect') is not the whole argument — the collection mechanism has its own measurable absence: the payments library is registry-closed at the book level (fbopp 64, pcsrf 84, pcswn 3, all held whole), it documents payouts TO the operator and card disputes, and it carries no franchisee debit, no fee schedule and no franchisee-visible statement. /royalt/ verified by me as licence text only. Grade B correct. source |
| hardware-usable-after-churn | unknown / F - STILL unknown, but the barrier it was resting on was measured and is not there. The prior rationale | upheld | Downgraded. THE AUDITOR'S SUSPICION 1 WAS RIGHT. Test one: does the appliance lock answer the cell? The cell asks whether documentation confirms the hardware remains usable with OTHER SOFTWARE AFTER CANCELLATION. intrg answers a different question — what an integrator may install on a running Simphony appliance — and the note's own closing sentence concedes the point ('No Oracle document confirms post-cancellation usability, which is what this cell asks for'), which is an argument from silence wearing a positive-evidence coat. Test two: does the same book contradict the lock reading? Yes, on the same page: RES 3700, e7 and Workstation 5A conversion paths are Oracle's own documented instances of MICROS hardware surviving a change of software. Test three: adjacent ground already in the record? Yes — verification.jsonl already carries an UPHELD verdict on this cell at unknown, reasoned 'Stating the corpus rather than generalising, per the enumeration rule', sourced to the Hardware and Systems Support Policies, and the new note never addresses it. Test four: the '$1 POS hardware options' line is on the www.oracle.com product page (verified byte-present) and is grade C marketing used inferentially ('a subsidy consistent with'), which cannot carry a no. Precedent: 22% no, 31% unknown, 36% partial. |
| hardware-byod | unknown / F - Read the mobile-client topics in the configuration guide - Simphony POS Operations Running on Androi | upheld | Downgraded. THE AUDITOR'S SUSPICION 2 WAS RIGHT, and the CAL argument is NOT enough — it is worse than not enough, it is misattributed. The note props the no on '(The CAL service runs applications using the unprivileged posuser account)' with no source given, so the fbcom PDF gets credit for it. I searched the string: it comes from intrg/c_runtime_environment.htm, the Oracle LINUX for MICROS integrator guide, which does not govern the Android devices the argument is about. So the only mechanism offered against BYOD is drawn from a platform the Pixel and Galaxy rows are not on. Second test: does the matrix say anything about device ownership? I read it — it does not; it is a software-validation table listing OS versions per device family across releases 19.1-19.10. CAL enrolment is a provisioning step, not an ownership constraint (MDM-enrolled BYOD is commonplace). I did NOT promote this to partial: validating a Google Pixel establishes that the client runs on a consumer handset, but the cell also requires 'a documented permission and security model' for personal devices, and that is wholly absent, so the honest state is undetermined on both halves rather than half-met. Precedent: only 14% score no, and the record's own careful prior verdict was unknown. |
| reliability-incident-postmortems | unknown / F - Checked ocistatus.oraclecloud.com, which returns a 2.4 KB client-rendered shell to both a browser UA | upheld | Downgraded on the move-8 test. The URL is already cited 5x by this record — the note says so itself — and, more damagingly, the record's own rationale for THIS cell already quotes the same document to the same effect and concludes unknown. Nothing was added. Second test: does the instrument have room? It enumerates delivery COMMITMENTS, so it has room only for 'did Oracle promise to publish RCAs', not for 'does Oracle publish them'; the surface that would answer the cell is the status page, and the record measured it as unreachable rather than empty — a gate, not an absence, per the project's own 403-is-not-a-deletion rule. Third: the grade is wrong in the other direction — the Oracle Cloud Hosting and Delivery Policies is a binding legal instrument incorporated into the cloud order, which is grade A on the stated scale, not the B the analyst assigned; that is moot now that the value falls. Precedent: 0% yes, 20% no, 40% unknown, 40% partial. |
| reliability-cellular-backup | unknown / F - Read the technical-specification tables for the current terminals on docs.oracle.com. Tablet 700 Ser | upheld | Downgraded. Test one, the word 'various': I read the cited page and the sentence that introduces the table is self-limiting, so it cannot function as a closed enumeration — this is a bare zero-hit dressed as an enumeration, which is exactly what the brief says dies. Test two, room: a cellular failover lives in a terminal's radio specification, not in a WAN-type table. Test three, is the record's own blocker discharged? No — I searched the index for the three hardware books the prior rationale named as unextractable and none of them is present in the 4,840, so the exact gap that made this unknown is unchanged. Precedent 43% no does not rescue a control that self-describes as partial. Grade B would have been correct had the value survived. |
| delivery-driver-roster | no / F - No driver as an employee class exists. Labor Management enumerates job codes, roles and shifts for r | upgrade-to-partial | REVERSES A FALSE PREMISE. The prior verdict said "No driver as an employee class exists". The Simphony POS Client (.NET) Extension API Reference (sicli, Copyright "2010, 2025") shows the opposite: the EmployeeInfo class carries the properties "IsAvailableForDelivery" and "IsCourier" alongside EmployeeNumber, FirstName, LastName and RevenueCenter, so courier is a flag on the first-class Simphony employee record, not an absent entity. Corroborating members, each in the same book: EmployeeFilterParameters exposes "CourierFilter" and "CourierFilterIndex" and EmployeeInfoList exposes "CourierFilters" (html_31ab9023-243f-eedc-e08f-1e55d193e03c.htm, html_e1d89396-bd25-020d-52cd-df98d03a3974.htm), so the employee list is filterable to couriers; OpsContext has "UpdateCourierList" — "Update Courier List and flag details as changed for DTO Delivery Dispatch screen" (html_293ce7bf-bb93-7337-e3df-c930686c3377.htm); CheckSummaryData carries "DeliveryEmployeeID" ("Delivery employee id") and "DeliveryEmployeeName" ("Delivery Employee name") (html_eaebf60b-d691-4f9b-1241-b52a1c70465d.htm), which is per-run assignment history at check level; and OpsCommandType has "AddDeliveryEmployee", "RemoveDeliveryEmployee" and "RemoveCourier" — "Used to remove courier from a check." (html_2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm). Couriers are Simphony employees, so the labor-clock-in-at-pos punch surface covers their clock-in/out. Partial, not yes, for two reasons. First, source class: an extension API reference proves the client exposes courier objects; it is weaker than a user-guide chapter showing an operator working a roster, and Oracle publishes no such chapter in any prose book held here. Second, the driver-facing half is explicitly reserved: OpsCommandType marks "EmployeeSelfAvailability" and "DeliveryEmployeeAvailability" as "RFU", so a driver marking their own availability is not shipped (the manager-side "IsAvailableForDelivery" property and the OpsRequestType "EmployeeAvailablility" / "Show Delivery Employee Availability" dialog are not so marked). No documented in-store / on-run / returning state machine was found. sicli is a floor (~700 of 7,600+ pages held), so this establishes presence and can never establish the remaining absence. source |
| delivery-dispatch-board | no / F - No first-party dispatch or expo board for in-house drivers exists. The documented order destinations | upgrade-to-partial | REVERSES A FALSE PREMISE. The prior verdict said "there is no assign-to-driver surface". Oracle names the screen by name: the OpsContext class documents the method "UpdateCourierList" as "Update Courier List and flag details as changed for DTO Delivery Dispatch screen", and DTO is expanded in the same book as "DTO (Delivery Takeout Order)". OpsContext also carries "SelectedCourierListUpdated" — "Determine if the selected courier list has changed or not" — and "DeliveryCheckActive" ("True if there is a currently active delivery guest check") and "DTOCheckActive" ("True if there is a currently active takeout, curbside or delivery guest check"). The board's other three asks are each evidenced in the same book: driver availability via OpsRequestType "EmployeeAvailablility" — "Show Delivery Employee Availability" — and "DTOViewCourierDialog" — "Displays a DTO view courier dialog given an employee id" (html_25aa611a-211f-ac66-1ecd-74ec9890469b.htm); order filtering via OpsCommandType "DTOApplyDeliveryCheckFilter", "DTOClearDeliveryCheckFilter" and "DTOApplyCourierFilter"; and multi-order run batching via "AssignMultipleDeliveryEmployee" and "UpdateMultipleDeliveryOrderStatus" (html_2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm). Dispatch state is also persisted downstream: the Database Access Cloud Service Reference (back-office/20.1/dacsr, https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/dacsr/G21944_03.pdf) defines a VRO_SOS_GUEST_CHECK_HIST view of speed-of-service data for past business date guest checks whose Date columns include "DISPATCHTIME" ("Dispatch Time") and "UNDISPATCHTIME" ("Undispatched Time") next to "APPROXDELIVERYTIME", "PREPDONETIME", "CALLBEGUNTIME" and "CALLANSWERTIME", so undispatched-vs-dispatched is a reportable order state, not a KDS placeholder. Partial rather than yes: every one of the DTO screen's own commands is annotated "Micros internal use only.", meaning they are the shipped screen's internals rather than an extensibility contract, and Oracle publishes no operator-facing chapter, screenshot or field list for the Delivery Dispatch screen in any prose book held here. Elapsed time per order is inferable from the quote/actual timestamps but is not shown as a board column anywhere. sicli is a floor (~700 of 7,600+ pages). source |
| delivery-promise-time | no / F - No first-party delivery promise time or quote engine exists. Quote times on marketplace orders are c | upgrade-to-partial | REVERSES A FALSE PREMISE. The prior verdict said "No first-party delivery promise time or quote engine exists. Quote times on marketplace orders are computed by the marketplace." Simphony quotes delivery itself, on its own check record. The CheckSummaryData class carries "DeliveryQuoteTime" ("Delivery quote time in minutes"), "DeliveryQuoteType" ("Delivery quote type"), "PickupQuoteTime" ("Preparation quote time in minutes"), "PickupQuoteType", "RequestedDeliveryDateTimeLocal" ("Requested delivery date and time"), "QuotedDeliveryDateTimeLocal" ("Quoted delivery date and time") and "ActualDeliveryDateTimeLocal" ("Actual delivery date and time") — a requested / quoted / actual triple, which is a quote engine with its own accuracy measurement. OpsCommandType adds the override surface: "DeliveryQuoteTimeOverride" — "Change the delivery quote time of the current check"; "CheckQuoteTimeOverride" — "Change the prep quote time of the current check"; "DailyQuoteTimeOverride" — "Change the prep quote time for an Order Type for the rest of the day"; "ChangePickupOrDeliveryDateTime" (html_2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm). Partial, and the shortfall is exactly what the claim asks for: every documented adjustment is a MANUAL override by an operator, per check or per Order Type for the rest of the day. Nothing held states that the quote is computed from current kitchen load, courier availability or zone drive time — and there is no zone drive time to compute from, since no delivery-area construct is evidenced anywhere. The one suggestive member, "RefreshQuote", is annotated "Micros internal use only." with no description. sicli is a floor, so the dynamic half is unevidenced rather than shown absent. source |
| delivery-driver-tracking | no / F - No driver GPS or live-location tracking exists. Simphony tracks no driver entity, so there is nothin | downgrade-to-unknown | WAS no/F ON A PREMISE THAT IS NOW FALSE. The prior rationale read "Simphony tracks no driver entity, so there is nothing to locate". There is: the Simphony POS Client (.NET) Extension API Reference (simphony/sicli) gives couriers a first-class employee flag (EmployeeInfo "IsCourier", "IsAvailableForDelivery"), a courier list feeding a named "DTO Delivery Dispatch screen", and per-check "DeliveryEmployeeID". It also contains an OpsCommandType member literally named "DTOLocateDeliveryDriver" — but it is annotated "Micros internal use only." with no description, and "locate" there is as likely to mean selecting a courier record from the dispatch list as reading a GPS fix. Nothing else supports live position capture: no driver-facing mobile app is documented in any book held (InMotion Mobile is a manager KPI/alert app), and the only WGS84 latitude/longitude in the corpus belongs to store locations and revenue centers in the Transaction Services Gen2 API and the Kiosk JS API, not to people. Unknown rather than no because sicli is a FLOOR — roughly 700 of 7,600+ pages held, with 2,160 referenced topic files not held at all — and a positively named locate-driver command is the wrong shape of evidence to call absence on. What would settle it: the sicli topic set under simphony/html/, or any Oracle page describing the DTO Delivery Dispatch screen for an operator. |
| delivery-route-map | no / F - No route planning or multi-stop sequencing surface exists. Nothing in the guide set renders a map or | upheld | RATIONALE REWRITTEN; VALUE STANDS. The old rationale's premise — that Simphony's delivery model is marketplace order injection with no in-house fleet — is false: sicli documents couriers as employees, a DTO Delivery Dispatch screen, courier filters and per-check delivery-employee assignment. Route mapping is a separate question and remains unevidenced in the strongest place it would have to appear. The OpsCommandType and OpsRequestType enumerations in sicli are complete member listings for their own types and they enumerate the DTO screen's entire command surface — check filters, courier filters, guest-info and delivery-info tabs, order notes, quote refresh, multi-order assignment — with no map, route, stop-sequencing, optimize or navigation member of any kind. No geocoding of a guest address appears anywhere in the corpus: the only WGS84 coordinates held are the store-location and revenue-center "geoLocation" objects in the Transaction Services Gen2 and Kiosk JS APIs, used for a proximity search of restaurants, and the only mapping product named is Bing Maps under the Microsoft license terms for Power View and SQL Reporting Services (simphony/simlg). Kept at no rather than unknown because a route view is a named feature that would surface as a command or request member, and both enumerations are closed; note nonetheless that sicli as a whole is a floor. |
| delivery-zones-polygon | no / F - No delivery-area definition exists — neither polygon nor radius nor postcode list. Zones in Simphony | upheld | RATIONALE REWRITTEN; VALUE STANDS. Drop the old closing premise that Simphony has no in-house fleet — sicli shows couriers, a DTO Delivery Dispatch screen and delivery-employee assignment on the check. The zone finding is unaffected and still holds: Zone in Simphony is a tier of the Enterprise > Property > Revenue Center > Zone configuration hierarchy, an organisational and inheritance scope for records such as payment drivers, not a geographic delivery boundary. Nothing in the corpus defines a delivery area by polygon, isochrone, radius or postcode list; no polygon, isochrone or drive-time term appears anywhere, and the only geospatial construct held is a store-location "geoLocation" latitude/longitude pair used for proximity search of restaurants in the Transaction Services Gen2 and Kiosk JS APIs. The sicli DTO command surface — which enumerates the dispatch screen's filters, tabs and assignment operations in full — contains no zone, area or boundary member. sicli is a floor (~700 of 7,600+ pages), so this is a bounded absence across the enumerations held, not a census. |
| delivery-zone-pricing | no / F - No per-zone delivery fee or minimum exists, following from the absence of any delivery-zone construc | upheld | RATIONALE REWRITTEN; VALUE STANDS. Two clauses of the old rationale are dead: Simphony does run first-party delivery (sicli documents couriers, a DTO Delivery Dispatch screen, delivery-employee assignment and its own delivery quote times), and delivery charges are therefore not only the marketplace's — the GloriaFood integration book carries an EMC-side Delivery Charges topic and the sicli check model carries first-party delivery quote times. What the claim asks for still fails on its own terms: it requires a per-zone fee, per-zone order minimum and per-zone promise time applied automatically from a validated customer address, and there is no delivery-zone construct at all to hang any of those on (see delivery-zones-polygon), no address validation to trigger them (see delivery-address-validation), and the only quote-time controls documented are manual per-check and per-Order-Type overrides. The delivery charge Oracle does document is a service charge, which is flat and not zone-scoped. Kept at no; the corpus is a floor outside the four registry-closed API surfaces. |
| delivery-address-validation | no / F - No guest address capture or validation for first-party delivery exists. Marketplace orders arrive wi | upheld | RATIONALE REWRITTEN; VALUE STANDS, BUT HALF THE OLD REASONING WAS WRONG. The old rationale said "No guest address capture or validation for first-party delivery exists" and that addresses arrive pre-resolved from the marketplace. Capture plainly exists: sicli's DTO (Delivery Takeout Order) workflow has an OpsCommandType group for "DTOGuestInfoTabSave", "DTOGuestInfoTabClear", "DTODeliveryInfoTabSave", "DTODeliveryInfoTabClear", "DTOUpdateCustomerData" and "DTOUpdateOrderInfoData", and CheckSummaryData carries "CustomerDetails" described as "Customer information - currently used by DTO (Delivery Takeout Order)"; OpsApplyDepositRequest / OpsEditDepositRequest carry "CustomerAddress1" and an "AddressHeader" ("Translated address header."). So an operator types a delivery address into Simphony. Validation is the part that fails: nothing in the corpus geocodes or verifies that address, flags it out of area, or checks it against a boundary — there is no boundary to check against, no geocoding service is named for guest addresses, and the only WGS84 coordinates held describe store locations, not guests. The address print tokens in the Gift and Loyalty guide (@CustomerAddressLine1@, @CustomerCity@, @CustomerPostalCode@) are loyalty-account fields printed on a chit and are not a delivery validation step. Kept at no on the validation ask; note sicli is a floor. |
| delivery-driver-comp | no / F - No driver pay, per-run compensation or mileage reimbursement construct exists. Labor Management pays | upheld | RATIONALE REWRITTEN; VALUE STANDS. Correct the premise: Simphony does have a driver entity — sicli flags employees "IsCourier" and "IsAvailableForDelivery" and assigns a "DeliveryEmployeeID" to a check — so the old sentence about there being no driver to pay is wrong. The compensation finding survives on its own evidence. Labor Management's employee and payroll surface (back-office/20.1/lmapi) enumerates its employee fields — payroll ID, employee role, address, job codes — with no per-delivery earning type, no mileage or distance field and no run-based reimbursement line, and no mileage term of any kind appears anywhere in the corpus. The sicli DTO command enumeration, which is complete for its type, has no mileage, distance, run-pay or driver-reimbursement member; the courier-related members are assignment, filtering, arrival and removal. Driver-retained tips are not separable from ordinary tip handling in anything held. Kept at no on the specific ask — per-run mileage and per-delivery reimbursement exported to payroll as distinct lines — while noting that sicli is a floor (~700 of 7,600+ pages) and Labor Management's user guide (lmusg) is capped here at 900 of a much larger queue. |
| delivery-cash-reconcile | no / F - No driver bank or driver cash settlement exists. Enterprise Cash Management enumerates its own const | upheld | RATIONALE REWRITTEN; VALUE STANDS. Strike the old closing premise that Simphony has no in-house fleet: sicli documents couriers as flagged employees, a DTO Delivery Dispatch screen, courier filters and per-check delivery-employee assignment, and OpsCommandType records courier arrival via "PickupPersonArrival" — "Records the arrival of pick up person (customer or courier) arrival date and time". The settle-up finding is unchanged and rests on its own enumeration: Enterprise Cash Management names its cash receptacles — tills, safes and server banks — and a driver bank is not among them, no corpus document contains a driver-bank or courier-bank construct, and the sicli command surface (which does carry cash-management members such as "AddToSafe" and "CashManagementDepositDate") has no per-driver settlement, over/short or cash-owed member. There is therefore an arrival timestamp and an order-to-courier assignment but no documented flow reconciling cash collected against orders assigned and tips owed to produce a per-driver over/short. Kept at no; the ECM chapter is an enumeration of receptacle types, but sicli itself is a floor. |
| delivery-tracking-page | no / F - No first-party guest-facing order tracking page exists. Where a tracking experience is present on a | upheld | RATIONALE REWRITTEN; VALUE STANDS. The old premise — marketplace injection only, no in-house fleet — is false, and the claim's own precondition ("driven by real order and driver state") is now partly satisfiable: sicli gives Simphony real driver state (courier employees, delivery-employee assignment per check, dispatch/undispatch timestamps in the dacsr reporting views) and real order state (requested / quoted / actual delivery date-times). What is still missing is the guest-facing surface. Nothing held publishes a branded order-status or driver-tracking page or an SMS status link on the restaurant's domain: the sicli DTO command enumeration is entirely operator-side, no notification, SMS, status-link or tracking-URL member appears in it, and the digital-ordering surface Oracle documents (the GloriaFood integration book, simgi) covers menu, discounts, service and delivery charges, tips, order types and fulfilment time with no guest tracking page. Kept at no on the guest-facing ask. Caveat the reader should carry: Oracle's separately documented Digital Ordering product is not in this corpus, and sicli is a floor. |
| delivery-daas-dispatch | unknown / F - Enumerated simcg/toc.htm (845 topics), sipou/toc.htm (198) and kdscu/toc.htm (129): current Simphony | upheld | RATIONALE REWRITTEN; VALUE STANDS AT UNKNOWN. The old rationale asserted that "current Simphony has no delivery driver, dispatch, courier or delivery-zone module at all". The driver, dispatch and courier third of that is now false: the Simphony POS Client (.NET) Extension API Reference (simphony/sicli) documents "IsCourier" and "IsAvailableForDelivery" on EmployeeInfo, "CourierFilter" on EmployeeFilterParameters, OpsContext "UpdateCourierList" — "Update Courier List and flag details as changed for DTO Delivery Dispatch screen" — "DeliveryEmployeeID" on the check, and a DTO (Delivery Takeout Order) command family including "AssignMultipleDeliveryEmployee" and "RemoveCourier". Simphony therefore has an in-house dispatch model, which makes this claim's subject sharper rather than moot: the question is whether that dispatch can hand an order to an on-demand courier MARKETPLACE (DoorDash Drive, Uber Direct, Nash, Relay) with the courier quote and status returning into the order record. Nothing held shows that. The Delivery Connectors chapter is marketplace order INJECTION only — five providers, an add/modify/delete integration tool, and a wizard with no courier quote, fee or tracking field — and the sicli courier members address employees of the restaurant, not a third-party courier network. Still unknown, not no: sicli is a floor (~700 of 7,600+ pages, 2,160 referenced topics unheld), and Oracle's first-party delivery front ends (Digital Ordering; the GloriaFood integration) are documented outside this corpus. The old note that the KDS posting file's DS_DISPATCHED / DS_UNDISPATCHED / DS_DELIVERED states are footnoted "For future use; currently unavailable" still stands for the KDS interface, but should no longer be read as evidence that dispatch itself is unbuilt — dacsr's VRO_SOS_GUEST_CHECK_HIST_V1 carries live "DISPATCHTIME" and "UNDISPATCHTIME" columns. |
| delivery-daas-fallback | unknown / F - This presupposes the in-house driver dispatch that delivery-daas-dispatch shows Simphony does not do | upheld | RATIONALE REWRITTEN; VALUE STANDS AT UNKNOWN. The old rationale's load-bearing sentence — "there is no driver roster, no delivery zone, no wait threshold and no courier handoff anywhere" — is now half false. sicli documents a courier roster (EmployeeInfo "IsCourier", "IsAvailableForDelivery"; EmployeeInfoList "CourierFilters") and a dispatch surface (OpsContext "UpdateCourierList" — "Update Courier List and flag details as changed for DTO Delivery Dispatch screen"), so the in-house half of a hybrid rule now has somewhere to live. The other three inputs the claim needs are still missing: no delivery zone or boundary construct exists in anything held, no wait-threshold or overflow rule appears in the sicli DTO command enumeration, and there is no DaaS courier handoff to overflow TO (see delivery-daas-dispatch). Availability is expressed as a flag on the employee, and the two commands that would let that flag drive automatic behaviour — "DeliveryEmployeeAvailability" and "EmployeeSelfAvailability" — are both marked "RFU" in OpsCommandType, i.e. reserved rather than shipped. Unknown rather than no because sicli is a floor and Oracle's first-party delivery front ends are documented outside this corpus. |
| delivery-offline-behavior | unknown / F - Simphony documents workstation offline behaviour in detail - t_properties_offline.htm (Property Para | upheld | RATIONALE REWRITTEN; VALUE STANDS AT UNKNOWN. Everything the old rationale says about workstation offline behaviour is unchanged and still correct — t_properties_offline.htm (Property Parameters option 6), t_check_allow_check_replay.htm (PMC privilege 30001), c_reset_totals_sod_offline.htm, the O - Offline closed-check indicator, kiosk workstation option 17, and the Delivery Connectors resiliency advice that "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." Only the closing clause changes: it read "since Simphony documents no in-house driver model there is no driver-assignment or driver-settlement behaviour to document either", and that is false. Simphony does have an in-house driver model — sicli documents courier-flagged employees, a DTO Delivery Dispatch screen, courier list updates and per-check delivery-employee assignment — so driver assignment IS a behaviour that could go offline, and Oracle simply does not document what happens to it in Yellow or Red mode. That makes this a genuine documentation gap on a real feature rather than a question with no subject. What would settle it: an Oracle page describing DTO / Delivery Dispatch behaviour under workstation offline mode. |
| delivery-route-map | no (grade F), uncited: RATIONALE REWRITTEN; VALUE STANDS. The old rationale's premise — that Simphony's delivery model is marketplace order injection with no in-house fleet — is false: sicli documents couriers as employees, a DTO Delivery Dispatch screen, courier filters and per-check delivery-employee assignment. Route mapping is a separate question and remains unevidenced in the strongest place it would have to appear | upheld | Upheld, but the previous rationale overstated the enumeration and that overstatement is withdrawn. It said the OpsCommandType listing contains no map, route, stop-sequencing, optimize or navigation member of any kind -- that was this record's own wording, and it is wrong. It contains one that is close: DTOLocateDeliveryDriver. That member does not rescue the claim, and cannot, for two reasons. Its entire published description is 'Micros internal use only.', so nothing is documented about what it does -- and it is one of 182 members on this page carrying that same sentence and no behaviour. More decisively, the claim asks for a live map view with GEOCODED STOPS and system-generated route sequ source |
| delivery-zones-polygon | no (grade F), uncited: RATIONALE REWRITTEN; VALUE STANDS. Drop the old closing premise that Simphony has no in-house fleet — sicli shows couriers, a DTO Delivery Dispatch screen and delivery-employee assignment on the check. The zone finding is unaffected and still holds: Zone in Simphony is a tier of the Enterprise > Property > Revenue Center > Zone configuration hierarchy, an organisational and inheritance scope for r | upheld | Upheld and now cited to the enumeration it rests on. Zone in Simphony is a tier of the Enterprise > Property > Revenue Center > Zone configuration hierarchy -- an inheritance scope for records such as payment drivers -- not a geographic boundary, and the cited command surface, which enumerates the Delivery Takeout Order dispatch screen in full (check filters, courier filters, guest-info and delivery-info tabs, order notes, quote refresh, multi-order assignment), carries no zone, area or boundary member. Across a 1,405-page corpus of the sicli book read 2026-09-09 by href fixpoint from its own default topic, plus the Enterprise Cash Management chapter, the GloriaFood book contents and the Sim source |
| delivery-zone-pricing | no (grade F), uncited: RATIONALE REWRITTEN; VALUE STANDS. Two clauses of the old rationale are dead: Simphony does run first-party delivery (sicli documents couriers, a DTO Delivery Dispatch screen, delivery-employee assignment and its own delivery quote times), and delivery charges are therefore not only the marketplace's — the GloriaFood integration book carries an EMC-side Delivery Charges topic and the sicli check m | upheld | Upheld. The claim needs a per-zone fee, a per-zone order minimum and a per-zone promise time, all applied automatically from a validated customer address, and each of the three preconditions fails independently. There is no delivery-zone construct to scope a price to (see delivery-zones-polygon: `delivery zone`, `polygon`, `isochrone`, `radius` and `boundary` are all zero across a 1,405-page corpus of the sicli book read 2026-09-09 by href fixpoint from its own default topic, plus the Enterprise Cash Management chapter, the GloriaFood book contents and the Simphony library registry). There is no address validation to trigger one (see delivery-address-validation). And the quote-time controls source |
| delivery-address-validation | no (grade F), uncited: RATIONALE REWRITTEN; VALUE STANDS, BUT HALF THE OLD REASONING WAS WRONG. The old rationale said "No guest address capture or validation for first-party delivery exists" and that addresses arrive pre-resolved from the marketplace. Capture plainly exists: sicli's DTO (Delivery Takeout Order) workflow has an OpsCommandType group for "DTOGuestInfoTabSave", "DTOGuestInfoTabClear", "DTODeliveryInfoTabSa | upheld | Upheld on the validation ask, with capture conceded. An operator plainly types a delivery address into Simphony: the cited enumeration carries DTOGuestInfoTabSave, DTOGuestInfoTabClear, DTODeliveryInfoTabSave, DTODeliveryInfoTabClear, DTOUpdateCustomerData and DTOUpdateOrderInfoData, and CheckSummaryData carries CustomerDetails, described as 'Customer information - currently used by DTO (Delivery Takeout Order)'. What the claim asks is whether that address is verified -- geocoded, checked against a serviceable boundary, or flagged out of area -- and nothing does: `geocode`, `geocoding`, `boundary`, `geofence` and `delivery area` are zero across a 1,405-page corpus of the sicli book read 2026 source |
| delivery-driver-comp | no (grade F), uncited: RATIONALE REWRITTEN; VALUE STANDS. Correct the premise: Simphony does have a driver entity — sicli flags employees "IsCourier" and "IsAvailableForDelivery" and assigns a "DeliveryEmployeeID" to a check — so the old sentence about there being no driver to pay is wrong. The compensation finding survives on its own evidence. Labor Management's employee and payroll surface (back-office/20.1/lmapi) enu | upheld | Upheld. Simphony does have a driver entity -- employees carry IsCourier and IsAvailableForDelivery flags and a check carries a DeliveryEmployeeID -- so the question is compensation, not existence. The claim wants mileage or distance per run, a per-delivery flat reimbursement, and driver-retained tips, exported to payroll as separate reimbursement and wage lines. None of the vocabulary exists: `mileage`, `miles driven`, `distance driven`, `reimbursement`, `run pay` and `trip pay` occur zero times across a 1,405-page corpus of the sicli book read 2026-09-09 by href fixpoint from its own default topic, plus the Enterprise Cash Management chapter, the GloriaFood book contents and the Simphony li source |
| delivery-cash-reconcile | no (grade F), uncited: RATIONALE REWRITTEN; VALUE STANDS. Strike the old closing premise that Simphony has no in-house fleet: sicli documents couriers as flagged employees, a DTO Delivery Dispatch screen, courier filters and per-check delivery-employee assignment, and OpsCommandType records courier arrival via "PickupPersonArrival" — "Records the arrival of pick up person (customer or courier) arrival date and time". Th | upheld | Upheld, and the citation is the chapter that enumerates the receptacles. Enterprise Cash Management names the containers Simphony can reconcile -- tills, safes and server banks, with count sheets and deposits -- and a driver bank is not among them. Across a 1,405-page corpus of the sicli book read 2026-09-09 by href fixpoint from its own default topic, plus the Enterprise Cash Management chapter, the GloriaFood book contents and the Simphony library registry, `driver bank`, `courier bank`, `settle up`, `over/short`, `over short`, `cash owed` and `driver settlement` occur zero times, tokenised and as bare substrings alike. The command surface does carry cash-management members such as AddToSa source |
| delivery-tracking-page | no (grade F), uncited: RATIONALE REWRITTEN; VALUE STANDS. The old premise — marketplace injection only, no in-house fleet — is false, and the claim's own precondition ("driven by real order and driver state") is now partly satisfiable: sicli gives Simphony real driver state (courier employees, delivery-employee assignment per check, dispatch/undispatch timestamps in the dacsr reporting views) and real order state (reque | upheld | Upheld on the guest-facing ask. The claim's own precondition is now satisfiable -- Simphony has real driver state (courier-flagged employees, per-check delivery-employee assignment, dispatch and undispatch timestamps in the reporting views) and real order state (requested, quoted and actual delivery date-times) -- so the old premise that this is marketplace injection with no fleet is dead. What is missing is the surface the guest sees. The cited enumeration is entirely operator-side: every DTO member drives a dispatch screen tab, filter or save, and no notification, SMS, status-link or tracking-URL member appears in it. Across a 1,405-page corpus of the sicli book read 2026-09-09 by href fix source |
| reliability-onsite-install | unknown, grade F | resolve-to-partial | Quote confirmed verbatim and contiguous in raw bytes of the live page (one text run, no inner tags). Re-fetched 2026-09-12 with get.mjs: consulting-services 200; /food-beverage/professional-services/ lands on /consulting-services/ with the same body. Page title 'Restaurants consulting experts | Oracle', H1 'Oracle Restaurants consulting experts', Simphony named 3 times, 0 hits for OPERA or hotel, so it is first-party Oracle and about restaurant POS. Its services include 'Site readiness', 'Staging and kitting' and 'Installation and deployment'. That covers the claim's conjuncts: in-person on-site installation ('onsite and/or remote') and go-live support ('live support, and post go-live hypercare'). Proposed yes is not allowed: this is a differentiator claim, a yes needs grade A or B, and this is a sales page (grade C). No A or B source exists; the record's service descriptions list no install entitlement for any edition. Amended to partial. Proposal text I could not confirm: 'more than 100 countries' has 0 hits in the raw page, and every '600' hit I pulled was inside SVG path data, so neither is quoted. source |
| extensibility-free-sandbox | unknown, grade F | resolve-to-partial | Quote confirmed in raw bytes. The only inline markup is an ordinary in-sentence link ('access to <a ...>POS integration</a> resources'); no table cells or separate blocks were joined. Re-fetched 2026-09-12: article 200; partners page 200. The article is still served (Wayback 2025-07-15; raw page carries a 2024-01-08T18:39:59Z timestamp). The partners page's inquiry link has campaign code RC_WWMK210630...SimphonyIntegrationPartnerProgram, which suggests a mid-2021 launch. The live partners page still describes the enrol-in-OPN, then inquiry, then validation testing, then Marketplace listing flow, but it never mentions the Lab (0 hits for lab/sandbox). So the Lab being free and current rests on the article alone. Checked the 'free' conjunct: I fetched www.oracle.com/partnernetwork/program/join/ (200, lands on /partner/). OPN membership is PAID, and it lists 'Membership payment details ... Level 0 USD $500 | Level 1 USD $5K | Level 2 USD $100K | Level 3 USD $500K' billed annually. Level 1 is the first level listing 'Integration qualification and validation'. The partners page does not say which level Simphony integrators need. It also sets eligibility: 'OPN membership is geared toward established companies that are at least six (6) months old and have a baseline level of at least five (5) employees'. The Lab is free and needs no production Simphony subscription, which meets one conjunct. But it is not free to reach, not open to any developer, is temporary, and seeded data is never stated. Each named shortfall is real and several conjuncts are partly met, so partial holds. The note is amended to add the paid OPN gate that the proposal left out. source |
| reliability-menu-build-service | unknown, grade F | upheld | Proposed partial from the full Oracle F&B docs tree (3,621 topics), live and archived www.oracle.com food-beverage pages (now reachable, previously 403) and the Oracle Restaurants Marketplace API (271st session); rejected on verification: The proposal's quote is verbatim in the archived EMM text (Wayback 2023-05-10, and the same text at the /industries/ URL on 2022-05-25). Live, /food-beverage/products/enterprise-menu-management/ now lands on /food-beverage/restaurant-pos-systems/ (200, generic POS page), so the dedicated EMM page is retired. The claim needs two things: (1) Oracle performs the INITIAL menu build, (2) as part of onboarding. EMM is described only as upkeep: 'eliminates the burden of maintaining ... point of sale and inventory data', 'all menu, pricing, and inventory updates'. The 2019 Thwaites blog supports the same reading: 'EMM efficiently handles all menu and pricing updates', 'taking the menu maintenance in-house', 'handing over the task to EMM in 2015' by a group that was already a Simphony operator. None of it covers an initial build. On the live consulting page the word 'menu' occurs only in site navigation. The 'Configuration architecture and design' section ('set up an enterprise configuration utilizing a template-based approach that reduces the time, complexity, and effort of deploying your properties') and 'Configuration services' ('help with configuration change requests, upgrades, ad-hoc training') never mention menus. Reading enterprise configuration as including a menu build is analyst inference. Oracle maintaining menus as a retired add-on service meets neither conjunct, so a partial would fall short of everything the claim asks. Rejected: stays unknown. The existing rationale still stands, and these sources can be added to it. Open lead for later: a Simphony implementation-services scope document naming a menu or database build. source |
| hardware-selfpour-scales | unknown, grade F | resolve-to-partial | Quote verified verbatim in the raw longDescription (ASCII apostrophes, no welded spans; trailing ). Every conjunct is met: a self-pour tap wall integration where pours post to the Simphony check automatically. The proposal's 'VALIDATEDON empty, validated version not stated' is wrong, because the listing links an Oracle ISV Partner Validation Report (marketplace.oracle.com/media/143640202/other/ISV_Partner_Validation_Report_Innovative_Tap_Solutions_v1.3.pdf, fetched 2026-09-12, HTTP 200). It records Oracle validation 'Complete' on 3/6/2023 over Simphony Transaction Services Gen2, and the partner states 'We are using the Simphony Transaction Services Gen2 API & POS v19.4'. Precedent: arryved hardware-selfpour-scales is a partner-route partial. Capped at partial because it is partner-delivered, not native (a 'yes' means native), and it is partner-authored copy, so grade C. source |
| digital-drivethru-ai | unknown, grade F | resolve-to-partial | Quote verified verbatim in the raw longDescription. The listing text itself names 'Oracle Micros POS'. The linked Oracle Partner Validation Report for Presto (v1.5, fetched 2026-09-12, HTTP 200) closes the menu-integration conjunct the proposal called 'only implied'. Oracle recorded validation 'Complete' on 17-Sep-2024, and the partner sections describe 'Check API - Order injection' and 'Configuration API - Menu data synchronization'. The Partner Implementation Guide configures 'Menu Item Definitions, Family Groups, and Condiment Group Names' (condiments are Simphony's modifiers). The escalation-to-human conjunct is still unmet. 'Driven by AI with advanced human supervision' describes Presto's own back-office supervision, not a lane handoff to store staff. One conjunct missing, so partial. Niche weight; grade C because every capability statement is partner-authored. source |
| digital-voice-ai-phone | unknown, grade F | resolve-to-partial | Re-fetched the SoundHound listing (HTTP 200, 12,653 bytes). The quote is verbatim, and 'Integrate seamlessly with Oracle Simphony with a simple and straightforward process' is present. The proposal's Checkmate quote is NOT byte-verbatim: the raw HTML has 'voice AI (phone & drive-thru)' (the entity decodes to the proposed text), and a separate bullet reads 'Voice AI: Provides innovative voice AI solutions for phone and drive-thru orders'. The cell explicitly admits 'a named certified partner', and SoundHound is on Oracle's marketplace, which Oracle calls 'fully vetted Simphony integration partners'. The listing links two Oracle validation reports titled 'ISV Partner Validation Report_19.7_Conversational_AI' and 'Partner Validation Report_19.4', but both links returned 401 {"code":"NotAuthenticated","message":"PAR does not exist"} on two probes (expired pre-authenticated request). They are unread, not absent, and nothing is cited from them. The injection conjunct is unmet for phone orders: nothing states that a phone order lands in Simphony without transcription. Checkmate's 'minimizing manual entry' is a marketing bullet and does not say 'without staff transcription'. The partner and call-answering conjuncts are met, so partial, not rejected. source |
| hardware-callerid-integration | unknown, grade F | upheld | Proposed partial from the full Oracle F&B docs tree (3,621 topics), live and archived www.oracle.com food-beverage pages (now reachable, previously 403) and the Oracle Restaurants Marketplace API (271st session); rejected on verification: The quote is verbatim (curly apostrophe in 'customer’s' as proposed). The proposal's premise that 'the listing text never names Simphony' is false: the listing says 'Our product is integrated bi-directionally with Oracle-Simphony 2.0 and Micro Res3700'. But the claim's defining conjunct fails. The cell requires the customer record and order history to pop AT THE POS on an incoming call. Call2kitchen pops the caller on its own centralised call-centre agent desktop ('The Agent Desktop Solution delivers caller-ID information from the phone line to the order entry module'). The Oracle Partner Validation Report (Aug 2021 v1.1, fetched 2026-09-12) confirms the architecture: 'a Call Center VoIP and Delivery Management System, designed to help restaurant chains ... from a centralized point', which places finished orders into Simphony ('The data that will be sent to Simphony are Orders and Void Transactions'). The Simphony workstation receives a guest check, never a caller-ID pop or customer record. Its validated functionality is only 'Menu Item Synchronization' and 'Ordering'. The material is also old (Oracle validation 10/15/2019 on 'Simphony v18.2'; listing version 2, released 2019-05-31). A call-centre ordering app with its own screen pop is a different surface from POS caller-ID, so no partial. source |
| order-capture-throttling | unknown, grade F | upheld | Proposed partial from the full Oracle F&B docs tree (3,621 topics), live and archived www.oracle.com food-beverage pages (now reachable, previously 403) and the Oracle Restaurants Marketplace API (271st session); rejected on verification: The Future Ordering quote is verbatim (trailing ). No listing meets the per-channel capacity-per-time-slot conjunct. Tillster's 'order throttling solution that allows you easily turn third-party orders on and off' is an on/off channel switch (and the Tillster listing never names Simphony). xDine's 'Order Throttling' is a bare feature label in a bullet list (no Simphony mention either). The only automatic quote-time element is one marketing bullet in Future Ordering's feature list: 'Promise Time™ - Calculate an accurate Promise Time™ based on all orders in the POS and the kitchens production capacity.' It names no configured threshold and no extension behaviour, and the listing says 'Oracle POS', not Simphony. Future Ordering's Oracle Partner Validation Report (STS Gen2; Oracle 'PASS' June 4th, 2021; fetched 2026-09-12) validates only 'Get Organization, Location and Revenue Center', 'Get Menus' and 'Create Guest Check (Post checks)'. No capacity, promise-time or throttling function appears. So the documented Simphony integration is order placement only, and Promise Time is a slogan-level bullet about the partner's own web/app/kiosk channels. A differentiator claim short on its core conjunct, backed by bare labels and a switch, is not a partial. source |
| guest-loyalty-referral-program | unknown, grade F | upheld | Proposed partial from the full Oracle F&B docs tree (3,621 topics), live and archived www.oracle.com food-beverage pages (now reachable, previously 403) and the Oracle Restaurants Marketplace API (271st session); rejected on verification: The quote is verbatim, from the Kaizen Loyalty Platform listing (re-fetched, HTTP 200). The cell's wording requires 'a NATIVE referral mechanic', and a third-party loyalty platform on Oracle's marketplace cannot satisfy a native requirement. The proposal concedes this in its own shortfall. The other conjuncts also fail: 'per-guest codes or links' and 'attribution of the referred guest's first order' appear nowhere in the listing ('first order' returns zero hits; the only 'code' and 'link' hits are JSON keys). The only two-sided reward is a hypothetical example ('e.g: A coffee chain ...'). Punchh's listing mentions 'referrals' as a bare word. The record's existing rationale (Oracle's Gift and Loyalty guides have no referral trigger) stands unchanged. source |
| guest-loyalty-wallet-pass | unknown, grade F | upheld | Proposed partial from the full Oracle F&B docs tree (3,621 topics), live and archived www.oracle.com food-beverage pages (now reachable, previously 403) and the Oracle Restaurants Marketplace API (271st session); rejected on verification: The quote is verbatim in the re-fetched Lava.ai listing (HTTP 200, 9,479 bytes), but it establishes nothing for Simphony. (1) The listing text contains ZERO occurrences of 'Simphony', 'Micros', 'Oracle' or 'POS'. The only tie is its presence in the marketplace. Its Oracle validation report link returned 401 'PAR does not exist' on two probes, so no validated Simphony function can be read. (2) It is live-event fan engagement ('instant action for ultimate fan engagement'; 'engage customers (fans) “in-the-moment” ... during live or online events'; 'when a fan uses their team branded credit card'), not a restaurant loyalty programme. (3) The push-updatable balance conjunct is unmet: 'balance' and 'points' return zero hits. 'Transferrable stored valued value' is a garbled phrase about value, not a balance shown on a pass that updates by push. The wallet-pass conjunct is met only for a third-party offers/VIP-access pass with no documented POS link. A differentiator partial whose POS tie is unevidenced and whose balance conjunct is unmet is rejected. source |
| guest-loyalty-ai-offer-recommendation | unknown, grade F | upheld | Proposed partial from the full Oracle F&B docs tree (3,621 topics), live and archived www.oracle.com food-beverage pages (now reachable, previously 403) and the Oracle Restaurants Marketplace API (271st session); rejected on verification: The quote is verbatim in the Punchh listing (updated 2023-08-31). Punchh's tie to Simphony is real: the linked Oracle Partner Validation Report 'Punchh Extensibility v19.5.x' (April 2023, fetched 2026-09-12) describes a PunchhSimphony.dll extension. But that report's Simphony functions are only loyalty discount redemption, check-in/earn and guest signup at the POS, with no recommendation feature. The AI sentence is a marketing slogan: 'can predict customer behavior and help marketers define the right offer at the right moment' is heading copy under 'PREDICT BEHAVIOR' and names no shipped feature, output or setting. 'Combining AI and machine learning technologies' is from the publisher's corporate description field. The cell explicitly demands a shipped product feature, not a slogan. Tillster's 'Recommender' curates 'upsell and cross-sell opportunities' (item upsell at ordering, not offer content, audience or send time), and Tillster's listing does not name Simphony. Rejected, and the record's rationale stands. source |
| extensibility-partner-revshare | unknown, grade F | resolve-to-partial | Re-fetched the Wayback id_ capture 20240913162005 raw (HTTP 200, 18,715 bytes). After stripping <!-- --> comments, the quote is verbatim and contiguous inside one <p> with no tags inside the span. The speaker is Simon de Montfort Walker, SVP and GM of Oracle Food and Beverage, and the quote follows the sentence about MICROS Simphony as the hub for partner solutions. The paragraph after it lists OPN member integrations on Oracle Cloud Marketplace, so the quote is about Simphony ISVs. Grade corrected from C to D: under the evidence rules a press release is a vendor marketing claim (D), not a pricing or feature page (C). Weight is niche, so the grade floor does not bar a yes. The value is downgraded to partial for three reasons. (1) This is a single executive sentence in a 2022 press release, not published partner terms. (2) The press release is 4 years old. Neither the Simphony partners page capture 20260609095306 nor the OPN ISV page capture 20260510032931 repeats the no-revenue-share statement, though neither contradicts it; tokenised 'revenue share' has 0 hits on both. (3) The current fee schedule is incomplete. The OPN page capture 20260811191042 (200) lists Level 0 to Level 3 fees and says Level 0 is 'a low cost option if you only want to list solutions on Oracle Marketplace'. It also says '(A validation fee is required.)' for Oracle Validated Integrations but gives no amount, and the Simphony partners page does not say which OPN level or validation fee Simphony integrators need. Neither page mentions a referral or per-location partner fee (tokenised 'referral' 0 and 'per location' 0). No Oracle Cloud Marketplace publisher-terms page exists in the Wayback CDX for cloudmarketplace.oracle.com, and I found none under www.oracle.com/partner/*. Oracle has no robots bars. Poison found while tokenising: in the press release, raw 'fee' (2 hits) is 'coffee' (0 as a token); 'commission' is gratuity income distributed by a tip-management partner, not a partner commission; raw 'listing' (7 hits) is Marketplace listing URL paths; raw '%' (30 hits) is URL encoding and CSS. On the OPN page, 'royalty' refers to ASFU/ESL support royalties for Oracle licence resellers, an unrelated programme, and not a Simphony marketplace royalty. source |
| payments-card-on-file | unknown, grade F | resolve-to-partial | Re-fetched 2026-09-13 (HTTP 200): smusg/account_settings.htm, smcfg/configure_billing_payment_fields.htm, smcfg/venue_details_operational_settings.htm, smcfg/connect_venue_to_simphony.htm, smusg/items.htm. The headline quote and the token, Simphony-link and serving-size quotes are verbatim and contiguous in RAW bytes after removing <!-- -->. The pre-authorize quote is split by <span class="uicontrol bold"> around 'Live', so it is inline markup rather than welded cells, and it holds after stripping. The value holds but the note needed corrections. (1) The dates were wrong: the pages carry dcterms.created 2026-07-01 (smcfg, G55857-01) and 2026-08-11 (smusg, G55858-02), not a datePublished range. (2) The Simphony tie comes from Oracle's own documentation, not marketing: the venue is linked to Simphony with API credentials and serving sizes map to Simphony POS items. Suites is still a separately named Cloud Service ('Oracle Restaurants Suites Management Cloud Service' in the docs.oracle.com Restaurants nav). This record already counts separate Oracle products, e.g. the GloriaFood digital-account-saved-payment cell at partial/C. (3) Shipping is not fully settled. The 2026-03-18 press release says it 'will be available initially for customers in North America within the next 12 months'. A second-revision user guide with live FreedomPay configuration fields points to a shipped product, but I found no release note or GA statement, so this is stated as a shortfall. (4) Tokenisation is inferred from 'stored credit card tokens' being invalidated and users having to re-enter card details. No page says outright that the merchant stores no PAN. (5) The card holders are suite account users (Account Holder or Authorized User, smusg/account_user_roles.htm), not restaurant guests. Conjunct test: tokenised = met by inference; guest profile = only a B2B suite-account profile; reuse across online, phone and in-store = not met, because it is one ordering channel (the Suites portal: pre-orders and event-day orders). Word-bounded controls over all 127 Suites topics: 'card on file' 0, 'online ordering' 0. 'token' has 3 hits and 'tokens' 1, but only the billing topic is a card token; the others are OAuth API tokens (smcfg/connections.htm, provide_api_and_authentication_details.htm), a trap for anyone counting the word. All 8 'phone' hits are contact-number fields, not a phone-order channel. The simcg/sipou gap is carried over from the record's own prior rationale, not re-measured. On a differentiator cell, partial/B is the most this evidence supports; a yes would need cross-channel reuse. source |
| digital-catering-portal | unknown, grade F | resolve-to-partial | Re-fetched 2026-09-13 (all HTTP 200): smusg/account_settings.htm, menus.htm, items.htm, events_module.htm and smcfg/venue_details_operational_settings.htm. All six quotes are verbatim in RAW bytes after removing <!-- -->, including the status labels 'Accepting Pre-Orders' and 'Pre-Orders Closed' in events_module.htm. smusg/events.htm uses the variants 'Accept Pre-Orders' and 'Pre-Order Closed'. Conjunct test: separate menu = met (menus designated for recurring or PAR orders; separate pre-order and event-day prices); lead-time rules = met (pre-order cutoff; smusg/events.htm: 'accounts can only place orders up to a specified time before the event'); invoice/house-account terms = met ('Bill to Invoice'). Minimums, quotes/proposals, deposits and ACH = not documented. I counted word-bounded tokens over all 127 Suites topics: minimums 0, deposit(s) 0, ACH 0, quote(s) 0, proposal(s) 0, catering 0, 'house account' 0. There are traps in the raw counts. The only 2 'minimum' hits are 'The minimum supported version of Outlook' and 'PAR Level: The minimum desired quantity... to keep in the suite', a restock level rather than an order minimum. Some of the 7 'invoice' hits are FreedomPay's 'Invoice Number... returned by FreedomPay at authorization', a payment reference rather than invoice terms. Pre-authorizing the full order amount is not a deposit. These are absences inside the Suites books only, so they are shortfalls against this product, not a 'no' for Simphony. The scope shortfall is accurate: orders are placed by assigned suite accounts against scheduled events. Grade B holds because the capability and the Simphony link both rest on docs.oracle.com. One addition: availability. The 2026-03-18 press release says 'within the next 12 months' for North America, and no GA statement was found. I added this shortfall and corrected the dates to dcterms.created. source |
| guest-loyalty-referral-program | unknown, grade F | resolve-to-partial | Re-fetched 2026-09-13 (all HTTP 200): CreatingInviteFriendsWidgets.htm, Widgets.htm, EmailStyles.htm, AutomaticRewards.htm, GettingStarted/Activities/EngagementActivities.htm and Activities/BonusPoints/BonusPoints.htm. The headline, EmailStyles and AutomaticRewards quotes are verbatim in RAW bytes. The Widgets.htm quote is '<a>Invite Friends</a> - Allows members to refer friends to join the program via referral link.' with a double space; that is link text plus same-line prose, not welded cells, so it is contiguous once whitespace is collapsed. SCOPING OBJECTION: it does not defeat a partial. The sources.jsonl row for crowdtwist-user/index.html left the library unmined for this session ('not mined this session' is the recurring wording in claims), and it says no guest-loyalty cell may be scored 'no' because of it. That treats CrowdTwist as part of this vendor's capability surface, not as out of scope. Precedent agrees: koala partial/B off its Punchh partner, par-brink yes/D off Punchh, and this record's own GloriaFood cells counted at partial/C. BUT THE GRADE MUST DROP TO C. None of the 110 held CrowdTwist topics names Simphony or MICROS; the POS hits are only generic 'POS activities' and a partner 'POS API' key. The only link between CrowdTwist and Simphony is marketing: www.oracle.com/food-beverage/loyalty-engagement/ (Wayback 2025-12-09, and a live capture in the q271 cache) with 'Native Simphony integration' as a link to the Simphony page and 'Servers can effortlessly enroll new members, check a guest's loyalty status, and instantly redeem rewards—all through the POS.' A docs.oracle.com nav entry that lists CrowdTwist under Restaurants groups products; it does not document an integration. A cell whose vendor scope rests on a marketing page is capped at C, as with GloriaFood. CORRECTION to the proposal's shortfalls: it said the referrer reward is only an operator-built segment campaign. That is wrong. EngagementActivities.htm documents a built-in 'Invite friend activities' earn: 'Earn points for referring a friend to the loyalty program via: Custom link Social networks Earn points when friends accept the invitation', and BonusPoints.htm offers 'double the points when members refer a friend'. Conjunct test: per-guest link = met (the widget is shown to logged-in members and generates a link to share); attribution of the referred guest's FIRST ORDER = not met, since attribution is to registration ('the friend they sent a referral URL link to joined the loyalty program'); two-sided rewards = not met, since no reward for the referred friend is documented. Word-bounded refer* tokens over ctuser give 12 hits. Poison found: 'The CrowdTwist Control Center refers to', 'Data export refers to', 'Tiering refers to', 'Engagement ... activities refer to' and 'Refer to the product catalog documentation' are definitional or cross-reference hits, not referral mechanics. The corpus is a floor, not a census (110 topics reached by following in-body links), so undocumented friend rewards are a documentation shortfall, not a 'no'. source |
| reliability-cellular-backup | unknown, grade F | resolve-to-partial | All three sources re-fetched 2026-09-15. The S1F4 page returned 200 and both quotes match verbatim. The simcg page returned 200 and its 3G/4G sentence matches verbatim. The matrix PDF returned 200 and is SHA-256 identical to the cached copy; its text has no S1F4 and no cellular/LTE/3G/4G/5G hit. Scope: the claim says 'terminals' and 'connectivity'. It does not say 'payment device', but it does not exclude one, and Oracle sells the S1F4 Pro in its Restaurants hardware library next to the MICROS Handheld 500 and S1F2. That library is shared across Simphony, RSM and NetSuite products. Is the S1F4 a Simphony component? Not shown. Its guide is payment-only, it never names Simphony, and the matrix omits it. A 'no' would therefore require reading 'terminals' as POS workstations only and discarding a documented first-party automatic cellular failover, so a no is too strong. A 'yes' is also barred: Simphony explicitly refuses 3G/4G for its Android POS devices, which is a positive, first-party absence on the POS side, and it is the dominant shortfall. Partial holds, with that shortfall named first. The grade stays B: this is vendor hardware setup documentation, and so is the contrary simcg statement. The proposer's note was amended because it overstated one thing and missed three. It said Oracle 'sells and documents' the S1F4 as a POS component, but Oracle sells it only as a payment terminal with no Simphony link. It missed the page's own SIM contradiction. It missed the hardware-index placement. And it left the Simphony linkage asserted rather than shown as unestablished. source |
Sources
Every URL this record cites. 198 in total.
- https://www.oracle.com/food-beverage/restaurant-pos-systems/simphony-pos/pricing/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/simphony-pos/
- https://docs.oracle.com/en/industries/food-beverage/simphony/
- https://docs.oracle.com/cd/F14820_01/doc.191/f15063/c_lic_simphony_cloud.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony-essentials/ssllg/c_lic_simphony.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/toc.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/index.html
- https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/c_check_filter_and_memo_check.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/c_payment_qr_code.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/t_payment_consumer_self_pay.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/c_tms.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/toc.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_checks_autofire.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_audit_trail.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_ecm.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_condiments.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_order_channels.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_consumer_payments.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_delivery_connectors.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/19.7/simcg/c_delivery_connectors.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_add_ubereats.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/toc.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/c_kds_menu_item_timing_by_order.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/c_kds_capacity_scheduling.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/plug-ins.html
- https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/toc.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/toc.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/index.html
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/c_data_retention_limits.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/toc.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/toc.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rardg/index.html
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/dacsr/index.html
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/dacsr/G21944_03.pdf
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/ebsse/index.html
- https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/index.html
- https://docs.oracle.com/en/industries/food-beverage/simphony/stsgg/api-notifications-api-webhook.html
- https://docs.oracle.com/en/industries/food-beverage/payments-platform/latest/config.html
- not refetchable
- https://dcrs.com/2025/12/08/micros-simphony-help-desk-support-escalation/
- https://www.deliverect.com/en-us/integrations/micros-simphony
- https://docs.adyen.com/plugins/oracle-simphony
- https://www.oracle.com/contracts/docs/ocloud_hosting_delivery_policies_3089853.pdf
- https://docs.oracle.com/cd/E76065_01/doc.29/e69884.pdf
- https://docs.oracle.com/en/industries/food-beverage/micros-tablet-700-series/latest/tabss/c_tablet_technical_specifications.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/19.4/sipou/c_workstation_online_offline_modes.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simsg/multi-factor_authentication.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcm/t_shared_services_overview_opi.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/19.3/simcg/c_loyalty_gift_programs.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/19.3/simcg/t_workstation_android_service_host_apk_upgrade_downgrade.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/op-config-sim-v1-menuitems-updatemenuitemclasses-post.html
- https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/op-config-sim-v1-devices-updateworkstations-post.html
- https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/find_URL.html
- https://docs.oracle.com/en/industries/food-beverage/simphony/ccapi/change_history.html
- https://docs.oracle.com/en/industries/food-beverage/simphony/stsgg/
- https://ocistatus.oraclecloud.com/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-hardware/oracle-micros-workstation-6/
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_checks_add_transfer.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/r_reporting_closed_check_codes.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_audit_trail_search_results.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/c_check_journal.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rarrg/c_speed_of_service_qsr_add.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_order_confirmation_board.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_deposits.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_banquet_guest_chk_print.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/c_events.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_dc_info_required.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_add_doordash.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_condiments_assign_condiments_to_parent_classes.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_condiments_prefixes_config_tasks.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_menu_items_configure_prices.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_menu_items_pricing.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_menu_items_set_main_sub_custom_menu_levels.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_checks_conversational_ordering_config_menu_level_sets.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_menu_item_master_availability_methods.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_menu_items_configure_mi_availability_at_workstation.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_menu_items_configure_auto_menu_levels.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_payments_cc_surcharge_donations.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_payment_module_add_spi.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_properties_android_payments.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/topic_payment_driver_config.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_properties_offline.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_check_allow_check_replay.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_payments_opi.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_payments_configure_opi_driver.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_menu_items_doordash.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_menu_items_ubereats.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_disable.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/t_kds_pfs_definitions_dist_state_record_v3.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/r_kds_chit_layouts.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_dc_status.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/kdscu/t_kds_enable_workstation_alerts.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/c_workstation_unsent_checks_warning.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_dc_workstations.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/toc.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/c_faq.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_using_loyalty_award_tiers.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_using_birthday_discount.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_using_loyalty_registration.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/c_notices_consent.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_notices_consent_configure.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/c_rule_reference_eligibility.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_coupon_configuring.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_loyalty_creating_awards.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/t_redemption_configuring.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/c_customer_account_permissions.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/gnlug/c_customer_account_manage.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_subj_area_gl.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_data_privacy.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/t_download_personal_data.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/t_data_privacy_settings.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/c_integrate_gf_essentials.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/c_version_support.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/t_emc_fulfillment_time.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simgi/t_emc_tender_cc.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_loyalty_options.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/t_payments_configure_guest_pay.htm
- https://www.gloriafood.com/white-label-food-ordering-app
- https://www.gloriafood.com/restaurant-pre-order-system
- https://docs.oracle.com/en/industries/food-beverage/simphony/simsg/pos_client_user_authentication.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/t_config_pay_timekeeping.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/sipou/t_start_shift_clock_in_out.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/inmqr/toc.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/t_add_lm_details.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/t_add_person.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/lmusg/c_add_employee.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simmu/t_manager_procedures_adjust_mi_availability.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simmu/toc.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/r_maintenance_invoice_settings.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/t_masterdata_create_item.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/t_receiving_create_blank_receipt.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/inmqr/c_alerts.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/inmqr/c_push_notifications.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/toc.htm
- https://www.prnewswire.com/news-releases/new-oracle-ai-smart-assistant-capabilities-help-restaurants-streamline-operations-and-support-302716313.html
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_org_hierarchy.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_prereqs.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/rause/c_understanding_sso.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simsg/enterprise_management_console_authentication.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/simsg/toc.htm
- https://about.doordash.com/en-us/news/doordash-preferred-integrations-program
- https://merchants.doordash.com/en-us/learning-center/doordash-preferred-integrations-program
- https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/c_maintenance_interface_definition.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/ebsse/F77908_15.pdf
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_0628034824.html
- https://www.prnewswire.com/news-releases/netsuite-launches-netsuite-connector-for-oracle-micros-simphony-302101937.html
- https://www.oracle.com/contracts/docs/saas_csa_us_2069270.pdf
- https://www.oracle.com/contracts/docs/cloud_csa_us_en_2351289.pdf
- https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/c_masterdata_acc_classes.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/t_masterdata_create_accnt_class.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/t_invoicing_send_approved_invoice_to_ap.htm
- https://docs.oracle.com/en/industries/food-beverage/back-office/20.1/invug/t_config_export_inv_totals.htm
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/article_165036447599.html
- https://www.netsuite.com/portal/company/newsroom/netsuite-launches-netsuite-connector-for-oracle-micros-simphony.shtml
- https://docs.oracle.com/en/industries/food-beverage/simphony/stsgg/
- https://docs.oracle.com/en/industries/food-beverage/simphony/stsgg/api-checks-api.html
- https://www.oracle.com/food-beverage/restaurant-pos-systems/simphony-pos/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/simphony-pos/pricing/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-hardware/oracle-micros-workstation-6/
- https://www.oracle.com/robots.txt
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-hardware/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-hardware/oracle-micros-workstation-6/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-hardware/oracle-micros-workstation-3/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-hardware/oracle-micros-workstation-8/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-hardware/oracle-micros-tablet/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-hardware/workstation-625/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-hardware/workstation-655/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pricing/
- https://www.oracle.com/robots.txt
- https://www.oracle.com/contracts/docs/hardware-systems-support-policies-069182.pdf
- https://www.oracle.com/a/ocom/docs/dc/hardware-warranty-policy.pdf
- https://www.oracle.com/contracts/hardware/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-hardware/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/res-3700/
- https://search.oracle.com/robots.txt
- https://www.oracle.com/food-beverage/restaurant-pos-systems/simphony-pos/
- https://docs.oracle.com/en/industries/food-beverage/simphony/index.html
- https://docs.oracle.com/en/industries/food-beverage/simphony/simcg/c_qqzzxx_fabricated_control.htm
- https://docs.oracle.com/en/cloud/saas/marketing/crowdtwist-user/index.html
- https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/html/2bc1a16d-0660-d84f-3fd1-51ec307768dc.htm
- https://docs.oracle.com/en/industries/food-beverage/simphony/sicli/index.html
- https://www.oracle.com/food-beverage/consulting-services/
- https://www.oracle.com/food-beverage/restaurant-pos-systems/pos-integrations/next-gen-api-for-restaurant-pos/
- https://www.oracle.com/food-beverage/products/enterprise-menu-management/
- https://public.marketplace.us-ashburn-1.oci.oraclecloud.com/20180828/listings/143640202
- https://public.marketplace.us-ashburn-1.oci.oraclecloud.com/20180828/listings/175816627
- https://public.marketplace.us-ashburn-1.oci.oraclecloud.com/20180828/listings/ocid1.mktpublisting.oc1.iad.amaaaaaaa6iiraaadgc4svvdjx24x6kvma53vvzbzcv5d3er2xyw3myjq6ea
- https://public.marketplace.us-ashburn-1.oci.oraclecloud.com/20180828/listings/66723789
- https://public.marketplace.us-ashburn-1.oci.oraclecloud.com/20180828/listings/100372985
- https://public.marketplace.us-ashburn-1.oci.oraclecloud.com/20180828/listings/ocid1.mktpublisting.oc1.iad.amaaaaaahy2nr6iaytefoynz6iwmtwbj6ufflogbzowo23o6k56cvdrbd37a
- https://public.marketplace.us-ashburn-1.oci.oraclecloud.com/20180828/listings/ocid1.mktpublisting.oc1.iad.amaaaaaa47qrylqaz4ku5n2jummz5wqroxdfvqj4dcdvvcbv747rj3poztta
- https://public.marketplace.us-ashburn-1.oci.oraclecloud.com/20180828/listings/68747783
- https://web.archive.org/web/20240913162005/https://www.oracle.com/news/announcement/oracle-cloud-drives-restaurant-automation-and-efficiency-2022-09-20/
- https://docs.oracle.com/en/industries/food-beverage/suites-management/latest/smusg/account_settings.htm
- https://docs.oracle.com/en/cloud/saas/marketing/crowdtwist-user/Help/ControlCenter/Program/Widgets/CreatingInviteFriendsWidgets.htm
- https://docs.oracle.com/en/industries/food-beverage/castles-s1f4-terminal/cslsf/c_intro_es4.htm