Nory

menu-pricing-nested-modifiers

No menu engine; menus are authored in the POS. Nory maps POS menu items to recipes for costing. https://help.nory.ai/en/ · retrieved 2026-08-01

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

No pricing engine. https://nory.ai/integrations · retrieved 2026-08-01

menu-pricing-fractional-placement differentiator

No menu/modifier engine; half-and-half is a POS concern. https://nory.ai/integrations · retrieved 2026-08-01

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

No pricing rules engine. https://nory.ai/integrations · retrieved 2026-08-01

menu-pricing-topping-quantity-tiers

No modifier engine. https://nory.ai/integrations · retrieved 2026-08-01

menu-pricing-size-style-matrix differentiator

No item pricing engine. https://nory.ai/integrations · retrieved 2026-08-01

menu-pricing-included-allowance differentiator

No modifier allowance logic. https://nory.ai/integrations · retrieved 2026-08-01

menu-pricing-combos

No combo builder; combos are POS-side. https://nory.ai/integrations · retrieved 2026-08-01

menu-pricing-upsell-prompts differentiator

No guest-facing ordering surface to prompt on. https://nory.ai/ · retrieved 2026-08-01

menu-pricing-86-propagation

No documented write-back of availability to POS, online ordering or marketplaces. https://nory.ai/integrations · retrieved 2026-08-01

menu-pricing-countdown-auto-86 differentiator

Stock is tracked but no documented auto-86 action. https://nory.ai/product/inventory · retrieved 2026-08-01

menu-pricing-dayparting

Menu scheduling is a POS function; Nory dayparts forecasts, not menus. https://nory.ai/product/business-intelligence · retrieved 2026-08-01

menu-pricing-channel-price-books

No pricing engine. https://nory.ai/integrations · retrieved 2026-08-01

menu-pricing-dual-pricing differentiator

No pricing or payment layer. https://nory.ai/integrations · retrieved 2026-08-01

menu-pricing-versioning-effective-dates differentiator

No menu publish/version pipeline. https://nory.ai/integrations · retrieved 2026-08-01

menu-pricing-franchise-hierarchy differentiator

Central control exists over recipes, portioning and network GP targets with granular franchisor permissions — but over recipes/costs, not over POS menu records. https://www.nory.ai/solutions/franchise-networks · retrieved 2026-08-01

menu-pricing-allergen-nutrition

Re-walked all 22 help.nory.ai collections and all 126 articles (plain fetch and Googlebot UA both return full server-rendered HTML) and confirmed zero occurrences of allergen, nutrition or calorie. But the two documents the no rested on are step-by-step how-tos - 'Adding Items to Nory' (8142361) and 'Creating a Recipe in Nory' (8135926) - which walk a user through creating an item without ever claiming to enumerate the form, and the remaining basis is a search that returned nothing, which is absence of evidence. Against that, www.nory.ai/blog/agentic-ai-restaurant-compliance-software states 'The system checks allergen data against menus in real time and flags mismatches before anything goes live' and 'the technology checks allergen data every time a menu changes', a first-party assertion that allergen data exists in the product - though it is written in generic category voice ('with real-time compliance software...'), it is grade D at best, and the Compliance Assistant help articles (15617486, 15900973) cover only workforce rules. Separately, the claim's publishing leg is well documented as absent: menu items reach Nory from the POS only after first sale (11792150) and no outbound menu channel exists. Unresolved: the vendor markets allergen handling that its documentation nowhere describes, so neither yes nor no is supportable. adversarially verified

menu-pricing-recipe-linkage differentiator

Recipes link to POS menu items by assigning a recipe to the POS ID that appears when an item first sells; on assignment Nory 'automatically goes back and reprocesses the last 7 days of sales for that item' and 'your COGS page will update automatically'. The record's claim that supplier price changes recost recipes automatically is contradicted by this page: 'recipe costs in Nory are not automatically updated when an item's price changes, unless explicitly configured.' Backfill beyond 7 days requires Nory Support. https://help.nory.ai/en/articles/11792150-turn-sales-into-stock-movement-how-recipe-linking-works · retrieved 2026-08-02 adversarially verified

menu-pricing-3p-menu-push

No marketplace menu publishing; no DoorDash/Uber Eats/Deliveroo integrations listed. https://nory.ai/integrations · retrieved 2026-08-01

menu-pricing-dynamic-pricing

Marketing references 'pricing optimization' insight but no rule-based price-setting engine; Nory cannot write prices. https://nory.ai/product/business-intelligence · retrieved 2026-08-01

payments-processor-choice differentiator

N/A — Nory has no payment layer at all. It also imposes no processing lock (see commercial-processing-not-bundled). https://nory.ai/integrations · retrieved 2026-08-01

payments-published-rates differentiator

Nory does not process card payments, so publishes no rates. https://nory.ai/integrations · retrieved 2026-08-01

payments-dual-pricing differentiator

No payment layer. https://nory.ai/integrations · retrieved 2026-08-01

payments-surcharge-guardrails differentiator

No payment layer. https://nory.ai/integrations · retrieved 2026-08-01

payments-emv-nfc

No first-party payment terminals. https://nory.ai/integrations · retrieved 2026-08-01

payments-softpos-tap-to-pay differentiator

No payment acceptance. https://nory.ai/integrations · retrieved 2026-08-01

payments-pay-at-table

No handheld payment device. https://nory.ai/integrations · retrieved 2026-08-01

payments-qr-guest-pay differentiator

No guest payment surface. https://nory.ai/integrations · retrieved 2026-08-01

payments-tip-adjust

Tip capture happens in the POS; Nory consumes the resulting tip data. https://nory.ai/product/payroll · retrieved 2026-08-01

payments-tip-pooling differentiator

Documented tronc engine: tips are pulled from POS data and distributed per branch per day, either equally across eligible employees or by points, where 'every employee earns points based on the rules you define' by department, position or tenure and 'the system automatically calculates each person's proportion based on the total points across the team', weighted by hours worked that day. Individual exclusions and bonus multipliers are supported, and the gross tips amount surfaces in the Team app alongside gross earnings. https://help.nory.ai/en/articles/8912455-nory-tips-tronc · retrieved 2026-08-02 adversarially verified

payments-offline-store-and-forward differentiator

No payment capture. https://nory.ai/integrations · retrieved 2026-08-01

payments-offline-decline-liability differentiator

No payment capture, so no liability position to publish. https://nory.ai/integrations · retrieved 2026-08-01

payments-gift-cards

No stored-value product. https://nory.ai/ · retrieved 2026-08-01

payments-house-accounts

No guest accounts receivable product. https://nory.ai/ · retrieved 2026-08-01

payments-split-tender

No tendering. https://nory.ai/integrations · retrieved 2026-08-01

payments-refund-void-controls

POS-side function. https://nory.ai/integrations · retrieved 2026-08-01

payments-chargeback-tooling differentiator

No payment layer. https://nory.ai/integrations · retrieved 2026-08-01

payments-card-on-file differentiator

No guest payment tokenisation. https://nory.ai/integrations · retrieved 2026-08-01

payments-payout-timing differentiator

Nory is not an acquirer and makes no merchant payouts. It does run BACS payments for UK payroll, which is a different thing. https://nory.ai/product/payroll · retrieved 2026-08-01

payments-multi-entity-routing differentiator

No settlement layer. https://nory.ai/integrations · retrieved 2026-08-01

payments-p2pe-pci4

Nory is out of the cardholder data environment entirely; no P2PE listing or PCI AoC is applicable or published. https://www.nory.ai/legal/customer-privacy-notice · retrieved 2026-08-01

kitchen-station-routing

Nory ships no KDS. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-expo-consolidation

No KDS. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-course-firing differentiator

No KDS or order-firing surface. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-prep-time-pacing differentiator

No KDS. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-order-throttling differentiator

No order intake path. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-channel-pause-propagation differentiator

No marketplace integrations listed. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-order-ready-callback differentiator

No KDS and no marketplace integrations. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-bump-bar-hardware

No KDS hardware. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-all-day-counts

No KDS. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-sla-alerts

No KDS ticket timing. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-printer-fallback differentiator

No kitchen printing. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-offline-operation differentiator

No KDS. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-item-build-screens differentiator

Recipes with portioning exist in Nory but are not rendered on a kitchen station screen; Nory has no KDS. https://nory.ai/product/inventory · retrieved 2026-08-01

kitchen-pizza-fractional-display differentiator

No make-line display. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-recall-refire

No KDS. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-order-modification-alerts differentiator

No KDS. https://nory.ai/integrations · retrieved 2026-08-01

kitchen-guest-ready-notification differentiator

No guest-facing messaging. https://nory.ai/ · retrieved 2026-08-01

kitchen-waste-logging

Waste logging with reason codes is built into daily workflows and depletes stock — but in Nory's mobile app, not at a KDS screen (there is no KDS). https://nory.ai/product/inventory · retrieved 2026-08-01

kitchen-speed-of-service-reporting

Nory reports orders per labour hour and labour productivity, not ticket or station times. https://nory.ai/product/business-intelligence · retrieved 2026-08-01

kitchen-prep-forecasting

Hourly 5-week forecast drives the Ordering Assistant's purchase suggestions; no kitchen-facing daily prep task list is documented. https://nory.ai/product/inventory · retrieved 2026-08-01

guest-loyalty-unified-profile

Nory is an operations platform with no guest CRM; its 'customer' data is aggregate demand and public reviews. https://nory.ai/product/business-intelligence · retrieved 2026-08-01

guest-loyalty-thirdparty-identity-attach differentiator

No guest profiles and no marketplace integrations. https://nory.ai/integrations · retrieved 2026-08-01

guest-loyalty-accrual-models

No loyalty product. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-tiers differentiator

No loyalty product. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-offline-behavior differentiator

No loyalty product. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-offer-stacking-rules differentiator

No offer engine. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-targeted-offers differentiator

No offer engine. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-rfm-segmentation differentiator

No guest-level data. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-lifecycle-automation

No guest marketing product. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-native-email-sms differentiator

Nory's messaging is staff-facing (team app notifications), not guest marketing. https://nory.ai/product/workforce-management · retrieved 2026-08-01

guest-loyalty-consent-management

No guest marketing channel. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-10dlc-registration

No guest SMS product; Nory is primarily UK/EU where 10DLC does not apply. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-campaign-attribution differentiator

No campaign product. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-data-export-portability differentiator

No guest list held. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-cdp-event-api differentiator

CORRECTS the rationale, not the verdict. The cell was a grade-B no on 'No public API or webhook stream of any kind is documented.', dated 2026-08-01 and citing help.nory.ai -- and its first limb is refuted by this record's own grade-A citations of api.nory.ai/swagger.json from 2026-08-08. A public API is documented. The verdict survives on the evidence that actually bears: the spec's twenty paths cover auth, branches, brands, integration, inventory, punch, settings and templates, with no guest, customer, profile, loyalty, event or stream resource of any kind, and no order or transaction resource that a CDP could subscribe to. Re-grounded at grade A on that enumeration. The webhook half is left where the record already puts it: this is a Swagger 2.0 document, a format with no construct for expressing webhooks, so its silence on them is a limit of the format and is recorded in extensibility-webhooks-push as suggestive rather than decisive. https://api.nory.ai/swagger.json · retrieved 2026-09-01

guest-loyalty-review-capture-routing differentiator

A shipped Customer Reviews Assistant ingests and analyses guest reviews and surfaces themes; no documented post-transaction request triggering or score-based routing to service recovery. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-referral-program

No guest referral mechanic (the referral programme on the site is for sales partners). https://www.nory.ai/partner-program · retrieved 2026-08-01

guest-loyalty-wallet-pass differentiator

No loyalty product. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-privacy-rights-tooling

Nory's DSAR process covers its own users/employees via privacy@nory.ai and a data-deletion request page; there is no guest-record tooling because there are no guest records. https://www.nory.ai/legal/customer-privacy-notice · retrieved 2026-08-01

guest-loyalty-redemption-fraud-controls

No loyalty product. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-ai-offer-recommendation differentiator

Nory's AI assistants target rotas, ordering, compliance, payroll and review analysis — not guest offers. https://nory.ai/ · retrieved 2026-08-01

guest-loyalty-stored-value-gift

No gift-card product. https://nory.ai/ · retrieved 2026-08-01

labor-clock-in-at-pos

Confirmed: clock-in happens on Nory's own surfaces (Nory Kiosk tablet app, Nory Team app), not at the POS terminal. The workforce page itself only says 'time cards approved on the floor' and never names the device, so the Play listing is the load-bearing evidence. https://play.google.com/store/apps/details?id=ai.nory.kiosk · retrieved 2026-08-01 adversarially verified

labor-photo-punch-verification differentiator

Kiosk employee setup is enumerated as: 'For clocking in and out all employees will need their own unique 4 digit pin number' (Schedule & Workforce > People > Role > Punch clock PIN). The mobile alternative verifies by location, not image. The Supported Devices & Technical Requirements table (article 14018489) states Camera required = No for the Kiosk App and Optional for the Team app, while Location required = Yes (clock-in) - if a photo were captured at punch the kiosk camera would be a requirement. Clocking Rules settings (article 9311371) expose only break rules, rounding rules and early/late clock-in restrictions; no photo or biometric option exists. https://help.nory.ai/en/articles/13906805-how-to-set-up-nory-kiosk-app · retrieved 2026-08-08

labor-geofenced-mobile-punch

'Nory Team relies on your phone's location to clock you in and out of a shift. For this to work, you need to enable Location Permissions' - precise location must be allowed, and 'You won't be able to clock in if Nory Team locates you away from the restaurant.' Mobile clock-in is a per-location toggle (Settings > Clock-In Methods; a location can be set to 'Only allow clock ins via Nory Kiosk app'). The supported-devices table lists Location required = Yes (clock-in) for the Team app, and the Kiosk article gives the fallback for sites where 'we can't get the GPS coordinates to verify employee location'. https://help.nory.ai/en/articles/6046807-employee-app-location-permissions-for-nory-team · retrieved 2026-08-08

labor-offline-time-punch differentiator

Not determinable. The prior no quoted 'The apps do not support offline mode' and 'Internet required: Always' from the Supported Devices & Technical Requirements article, but FAQ Q1 of that same article lists 'offline data caching' among the features 'only available through the native mobile apps' - and Nory Team, the app employees punch on, is one of them. The article therefore cannot establish that no punch is ever taken without a connection. Nothing replaces it: the Nory Team clock-in article enumerates why a clock-in can be refused (location permission not granted, employee located away from the restaurant, poor GPS accuracy, clock-in restricted to kiosk-only) and connectivity is not among them; the timecards article treats a missing punch as something a manager edits after the fact, not a queue draining; and a help-centre search for offline, offline mode, sync, cache and connection surfaces no reconcile-on-reconnect behaviour. Offline caching of some kind exists and is undocumented, which is unknown, not no.

labor-granular-rbac

'Granular permission settings that allow franchisors to control what information and features are accessible to franchisees'; per-action grants and per-location scoping are not enumerated. https://www.nory.ai/solutions/franchise-networks · retrieved 2026-08-01

labor-manager-override-audit

'All changes to timecards and schedules are tracked and can be viewed from the timecard tab... Select a timecard to view a list of all actions that have been made to that timecard and the person who made the change. Each timecard amendment is time stamped', with a separate 'all shift changes' view for schedule-side edits. Approval is a distinct attributed step (approve / bulk approve, green tick, CSV export of approved timecards). Schedules are 'versioned automatically, providing a complete history of changes', approvers see the full change history plus the manager's notes, and new reporting covers 'manual edits made to schedules' (article 15694014). Order actions carry the same treatment (Show History: who placed, modified and received, each time-stamped). Shortfall to note: Nory does not assert the log is immutable. https://help.nory.ai/en/articles/8389646-reviewing-editing-approving-and-exporting-timecards · retrieved 2026-08-08

labor-native-scheduling differentiator

Native scheduling is documented — shifts are built, approved and published inside Nory against Projected Sales, Projected COL and a per-location Target COL % (28% default) with red/amber/green budget indicators. But the record's '~5 second Scheduling Assistant builds rotas' framing is marketing: the only automation the guide describes is 'Fill Open Shifts', which 'will allocate shifts across available employees based on availability' — it populates pre-created open shifts, it does not generate a rota. https://help.nory.ai/en/articles/15402192-creating-and-managing-schedules-in-nory-an-in-depth-guide · retrieved 2026-08-02 adversarially verified

labor-demand-labor-forecast differentiator

Documented, not just marketed: Nory 'predicts your restaurant's sales at an hourly level, up to 35 days in advance' and 'continuously updates predictions as new sales data comes in, helping you plan staffing and inventory'. The scheduling guide consumes it as 'Projected Sales: Nory's forecast for the week based on your sales history' against a per-location Target COL %. Note the horizon is 35 days, not the 5 weeks of hourly forecast the record's original note implied. https://help.nory.ai/en/articles/7845382-sales-and-forecasts · retrieved 2026-08-02 adversarially verified

labor-realtime-labor-percent differentiator

Documented: labour can be viewed as a percentage of sales, as a money value, or as hours, and 'sales data is updated throughout the day, so your labour results show in real time too'. Projected COL updates automatically as shifts are added, with a green/amber/red indicator against target. The record's 'P&L refreshing roughly every 15 minutes' is not stated anywhere in the docs — no refresh interval is published. https://help.nory.ai/en/articles/7669134-tracking-and-driving-your-restaurants-labour-performance · retrieved 2026-08-02 adversarially verified

labor-overtime-prevention differentiator

The Compliance Assistant flags overtime and break violations before a schedule is published; a block or warning at the moment of clock-in is not documented. https://nory.ai/product/workforce-management · retrieved 2026-08-01

labor-break-compliance-by-state differentiator

Score survives at partial, but the stated basis is wrong and materially over-generous. The workforce page FAQ says the platform enforces rules 'you configure' for your jurisdiction and adds: 'Nory does not independently verify that your configured rules meet your jurisdiction's law.' Automated compliance verification is on the roadmap 'for later in 2026'. So there is a configurable rules engine, not a vendor-maintained jurisdictional rule pack. Same correction applies to labor-overtime-prevention and multi-location-central-labor-policy, both of which lean on the same false 'applied automatical https://nory.ai/product/workforce-management · retrieved 2026-08-01 adversarially verified

labor-fair-workweek-support

Predictive-scheduling jurisdictions are supported by the rules engine - the location-override section offers 'Turn a rule off if it doesn't apply to your business (e.g. a fair work week rule)', and the supported-jurisdiction list includes Seattle, Oregon, New York City, Pennsylvania and DC - and rules can be hard (blocks publishing/approval) or soft (warning). Shortfall: the rules the article says are covered are 'Maximum number of worked hours per week/day, Rest and meal breaks, Days of rest and minimum time between shifts, Minimum wage'. No advance-notice deadline countdown for published schedules and no calculation of predictability pay owed for employer-initiated changes is documented anywhere in the help centre; schedule changes are versioned and reported (article 15694014) but not priced. https://help.nory.ai/en/articles/15900973-us-compliance-assistant · retrieved 2026-08-08

labor-minor-labor-rules

For UK and RoI locations the rules engine covers 'Young workers work limits' and 'Minimum wage, including age bands', applied automatically by jurisdiction: 'As you build a schedule, Nory checks it against these rules and flags issues before you publish', with hard rules blocking publish/approval and soft rules warning. Two shortfalls: (1) the US Compliance Assistant article's rule list is max hours, rest/meal breaks, days of rest and minimum wage only - no minor/school-day rule is named for any of its 21 supported US jurisdictions; (2) enforcement is documented at schedule build and publish only. The Clocking Rules settings surface (article 9311371) exposes break rules, rounding rules and early/late clock-in windows and contains no age-based restriction, so there is no documented block at clock-in. https://help.nory.ai/en/articles/15617486-compliance-assistant-for-the-uk-and-ireland · retrieved 2026-08-08

labor-tip-pooling-rules

Verified verbatim: 'Tips and tronc are calculated in Nory from your POS data and your configured distribution rules (equal, points-based by department, position, or tenure)' with Employment (Allocation of Tips) compliance 'built in'. Claim-level (product marketing page) and UK-tronc-shaped; the same evidence carries payments-tip-pooling. https://nory.ai/product/payroll · retrieved 2026-08-01 adversarially verified

labor-tip-distribution-audit-trail

Per-employee tip amounts flow automatically into the pay run; a per-shift contributed-vs-distributed audit export is not documented. https://nory.ai/product/payroll · retrieved 2026-08-01

labor-qualified-tips-w2-reporting differentiator

Nory's payroll product is UK/HMRC-specific (BACS, SMP, SPP, P11D, pensions). No US W-2 Box 12 TP / Box 14b tipped-occupation support is documented. https://nory.ai/product/payroll · retrieved 2026-08-01

labor-native-payroll differentiator

Nory's own payroll page shows this is a part-managed UK bureau service, not native operator-run payroll: 'Nory handles real-time reporting to HMRC at launch (submitted by Nory's payroll team)' and 'Nory's team handles the final submission to HMRC, BACS payments, and statutory items like SMP, SPP, P11D and pension submissions', with 'Full self-serve, including operator-controlled payments, is coming soon.' A capability the vendor's staff performs on your behalf, in one country, with self-serve on the roadmap, is partial — not a shipped native payroll engine. https://nory.ai/product/payroll · retrieved 2026-08-01 adversarially verified

labor-payroll-export-formats

The Payroll Assistant exports approved hours 'clean to payroll', but no named payroll providers or documented file formats are published; Sage, BrightPay, Xero and Fourth are named as competitors, not partners. https://nory.ai/product/payroll · retrieved 2026-08-01

labor-shift-swap-workflow differentiator

Three documented request types in the team app: swap (pick your shift, 'choose the shift you would like to swap with from the available list', both employees agree, then manager approves), drop ('drop this shift' with an optional note, 'the request has now gone to your manager for approval'), and claim an open shift ('request this shift, your request will be sent to a manager for approval'). Push notification on approval or rejection; a companion article covers the manager side. https://help.nory.ai/en/articles/8480726-requesting-shift-changes-in-the-team-app · retrieved 2026-08-02 adversarially verified

labor-digital-onboarding-i9

US I-9/E-Verify is out of scope for a UK/EU-first payroll product and is not documented; general digital onboarding is also not described. https://nory.ai/product/payroll · retrieved 2026-08-01

labor-server-performance-metrics differentiator

Productivity metrics such as orders per labour hour are reported for fair site-to-site comparison; per-server average check, attachment rate and void/comp rate are not documented. https://nory.ai/product/business-intelligence · retrieved 2026-08-01

inventory-recipe-bom-costing

Every recipe is costed and recosts automatically when supplier prices change; 'batches' are tracked as a distinct stock movement, implying prep sub-recipes, though multi-level nesting is not explicitly stated. https://nory.ai/product/inventory · retrieved 2026-08-01

inventory-unit-conversion-yields

Per item the stock-count section lets you tick which units the item may be counted in, choose the 'show as' label for each, and toggle independently which unit is used in reports; item creation captures supplier, supplier code, pack size and price as the purchase side (article 8142361). The worked example is explicit: 'a 700ml bottle of gin can be set up as ml to use in recipes but counted as 1 bottle, and viewed in the report as bottles rather than in ml' (article 9099951) - purchase, recipe and count units with conversion. Batch recipes take a yield ('the amount of the product the batch will make') plus their own count units (article 8135780). Shortfall: no yield, shrink or waste percentage is applied to raw-to-usable conversion at item level - waste in Nory is an after-the-fact logged event with a reason code (article 8141635), not a conversion factor, so theoretical usage is computed from recipe quantity alone. https://help.nory.ai/en/articles/8172911-unit-labels-and-reporting-preferences · retrieved 2026-08-08

inventory-theoretical-vs-actual differentiator

Help-centre reference for the Stock Reconciliation Report: it 'compares what your team actually used (aka Actual) with what your system expected based on sales and recipes (aka Theoretical)'. Published formulas: Variance Gap Quantity = sold quantity - (opening stock + deliveries + transfers in + produced - closing stock - transfers out - used in batches); Gap Value and 'Variance (including Logged Waste)' express the same gap in currency, the latter netting off logged waste value. A per-item Deep Dive breaks a line down into deliveries (invoice number, received date, quantity, item cost), transfers, waste and batch usage for root-cause work. Confirms the earlier caveat: theoretical is continuous but actual is stocktake-gated, so the variance closes at count cadence. https://help.nory.ai/en/articles/10741975-stock-reconciliation-report-key-definitions-explained · retrieved 2026-08-06 adversarially verified

inventory-realtime-depletion differentiator

Confirmed and, if anything, the researcher was generous in the note. The BI page distinguishes: 'Revenue, GP and labour updated live, every 15 mins' and theoretical GP refreshing 'live as orders come in', but actual GP updates only 'when you complete a stocktake'. So true depletion-to-actual is periodic count-driven, not continuous. Partial is correct. https://nory.ai/product/business-intelligence · retrieved 2026-08-01 adversarially verified

inventory-86-auto-sync differentiator

Pausing is purchasing-side only: 'Mark items as unavailable to order from your supplier or central production unit (CPU)', paused items 'will show on the orders screen... and will not be available to order until the end date has been reached'. The article's own caveats confirm no menu effect: 'Recipes won't be paused... if a paused item is in a recipe the stock will continue to be deducted as normal', and pausing cannot even be scoped to one location. The POS connection runs the other way: 'You won't be able to assign a recipe to a POS item until it's been sold at least once through the till. This is how Nory knows the item exists' (article 11792150). No write-back to POS, online ordering or marketplace availability exists in any of the 126 help articles. https://help.nory.ai/en/articles/10531804-pausing-items · retrieved 2026-08-08

inventory-count-modes

Opening and closing stock counts are core and mobile-optimised, with per-count reconciliation history; distinct ad-hoc spot and scheduled cycle-count modes are not documented. https://nory.ai/product/inventory · retrieved 2026-08-01

inventory-mobile-count-offline

Mobile counting is documented and real: 'Nory allows you to count stock using the web application on your laptop, but the fastest way is the Nory IM mobile apps on Android and iOS phones', with storage-area and category filters, an item search bar, and 'please note that your count auto-saves' into a draft that can be reopened from the counts list. Two named shortfalls. (1) No barcode or QR scanning: a help-centre search returns zero articles for 'barcode' and zero for 'QR', and the only scanning Nory documents is camera OCR of supplier invoices and delivery documents - the technical-requirements article lists the Nory IM camera permission as '(document scanning)'. Counts are keyed by finding the item in a filtered list or the search bar. (2) No documented offline capture or sync-on-reconnect: the auto-save is not described as local, and while that article's FAQ Q1 lists 'offline data caching' among native-app-only features, Nory publishes nothing about counting without a connection or reconciling on reconnect. Note also the documented cap of one count per day per category. https://help.nory.ai/en/articles/6607628-getting-started-with-counting-stock-in-nory · retrieved 2026-08-08

inventory-vendor-catalogs-edi differentiator

Verified verbatim: 'Orders go out by email (CSV attachment) for suppliers without EDI, or directly into supported suppliers' ERPs.' No named distributors, no EDI standard, and the phrase 'supported suppliers' is undefined. Partial, not yes. https://nory.ai/product/inventory · retrieved 2026-08-01 adversarially verified

inventory-invoice-ocr differentiator

Documented scan pipeline: after a scan, "Nory's AI is working in the background to extract information from your invoice and process it into the system", moving through Scan Processing, Scan Processed (review and accept the order), Scan in Review ("if the AI couldn't accurately read the information" a Nory team member reviews, target six hours including weekends) and Scan Failed. Extraction is line-item: the invoice detail view shows "individual line items" plus related credit notes (article 6335694), and the smart-matching engine compares per-item quantity against the goods-received note and per-item price against the purchase order, matching "by code, not by name", with zero tolerance (article 15230867). Documented capture channel is in-app photo/scan (there is a 'Taking Better Invoice Photos' guide); no PDF-upload or email-forwarding inbox is documented, and 'Enter Manually' remains the fallback when a scan fails. https://help.nory.ai/en/articles/10154949-precise-invoice-scanning · retrieved 2026-08-06 adversarially verified

inventory-price-change-alerts differentiator

Shortfall: price changes surface only as an actionable queue tied to receiving, not as an alert. The docs say 'Price changes occur on Nory when suppliers decide to change their prices, from the last time an order has been placed' and cover actioning them; no notification, threshold, or subscription-style alert is documented anywhere in the help centre. Purchasing Insights tracks ordered-vs-delivered quantities and supplier reliability, not price trends, and the invoice-management article describes no price-discrepancy flag. https://help.nory.ai/en/articles/13178123-actioning-price-changes-and-credit-notes · retrieved 2026-08-02 adversarially verified

inventory-par-auto-suggest differentiator

The Ordering Assistant that produces the buy suggestion is explicitly labelled 'in Beta' on Nory's own inventory page. The researcher noted the beta label in the cell text and then scored it yes anyway. A beta feature is partial by definition. https://nory.ai/product/inventory · retrieved 2026-08-01 adversarially verified

inventory-waste-logging

Waste logging is embedded in daily workflows, appears as a distinct stock movement alongside deliveries/transfers/batches, and is surfaced in reconciliation and team leaderboards. https://nory.ai/product/inventory · retrieved 2026-08-01

inventory-transfers

Transfers in and out are first-class stock movements shown per item alongside deliveries, batches, waste and sales; an explicit in-transit/approval state is not documented. https://nory.ai/product/inventory · retrieved 2026-08-01

inventory-commissary

Setup is a four-step documented workflow: identify the CPU location ('Once CPU is enabled you will see "Production" section enabled'), set up CPU suppliers with the CPU location's email so purchase orders route to it, and 'If you are setting up the CPU as a supplier for batches, make sure the markup is also shown' - 'Click on "+ Supplier" inside your batch under the recipe, Enable "Mark up" for your price' - so downstream sites receive prep items at a computed transfer cost. CPU deliveries feed reporting as first-class terms: CPU Received Value in the Stock Reconciliation Report and CPU Delivered Quantity inside the published COGS and Cost of Sales (actual) formulas (article 14600654). Enabling CPU requires contacting your Customer Success Manager. https://help.nory.ai/en/articles/14600684-how-to-set-up-cpu-in-nory · retrieved 2026-08-08

inventory-lot-traceability

Re-read both receiving articles and the two video walkthroughs (13178492, 13178529, which carry no field list at all). 'How to Receive an Order in Nory' is a click-path how-to ('Enter the Invoice Number (manual entry), Add the Total Quantity') and 'Keeping Stock Accurate When Receiving Orders' says 'Confirm details such as supplier, pack size, price, and quantity' - 'such as' is explicitly open-ended, so neither article establishes the full set of captured fields. Nory's 'batch' is indeed a production recipe rather than a lot (8135780, form is name, yield, ingredients, storage areas, count units), and a full-text scan of all 126 articles across 22 collections finds no 'batch number' and no lot-in-the-inventory-sense usage - but that is a search that returned nothing, not positive evidence of absence, and Nory publishes no admin guide, data dictionary or API reference covering the delivery-line schema (api.nory.ai/swagger.json exposes GET /inventory/branches/{branchId}/deliveries but its response definition is not a documented field spec of the receiving form). Unresolved: lot capture is plausibly absent but nothing published asserts it. adversarially verified

inventory-shelf-life-expiry

Re-read the Nory Notifications article, which does enumerate manager email with a closed count - 'Managers receive 3 notifications via email: Schedule request created/resubmitted by employee; Schedule request cancelled by employee; Visa/document expiry alerts (60/30 days)' - so Nory's date-based alerting is demonstrably employee-document only. But the claim is satisfied by an expiring-soon REPORT as well as an alert, and the only basis for ruling that out was walking the Reporting on Inventory and Inventory Reconciliation collections and finding none, which is a search that returned nothing. The date-capture leg rests on the receiving articles, and 'Keeping Stock Accurate When Receiving Orders' says 'Confirm details such as supplier, pack size, price, and quantity' - open-ended. A full-text scan of all 126 articles finds no 'shelf life', 'use by' or 'best before', and the batch-recipe form (8135780) records name, yield, ingredients, storage areas and count units with no date. Unresolved: expiry tracking is probably absent, but half the claim is refuted only by a failed search. adversarially verified

inventory-bar-partial-bottle

'Label your counting options... a 700ml bottle of gin can be set up as ml to use in recipes but counted as 1 bottle, and viewed in the report as bottles rather than in ml', and per item you tick every unit the team may count in, with an independent reporting unit (article 8172911) - so an operator can enable a ml/l count line to capture an open bottle, and batch guidance advises weighing the storage container and counting in kg for accuracy (article 8135780). Shortfalls: no integration with a bar scale or any weighing hardware is documented anywhere in the help centre (the IM app's only hardware use is the camera, for invoice scanning - article 14018489), and there is no bottle-fraction/tenths entry control; the item-setup guidance actually pushes the other way for unit-sold drinks ('enter the unit as each regardless of the volume as you will always count 1 unit'). https://help.nory.ai/en/articles/9099951-getting-ready-to-count-and-reconcile-stock · retrieved 2026-08-08

inventory-cogs-gl-export

Xero is named as an accounting integration and Nory produces live COGS/GP; QuickBooks/Sage Intacct/NetSuite connectors and configurable per-category GL mapping are not documented. https://nory.ai/product/business-intelligence · retrieved 2026-08-01

inventory-native-not-partner differentiator

Nory's own admin guide describes recipe costing inside Nory: click the inventory icon, Recipes, Add recipe, set the sales price and recipe type, 'add the ingredients, or batches and the quantity to make up the recipe', then 'the recipe cost and GP will now be displayed'; the recipe is assigned to a POS ID 'so you can account for inventory as part of sales'. Sibling articles cover batch recipes, storage areas, supplier delivery rules, multiple suppliers per item, stock counts and the reconciliation report - all Nory-native screens. Permissions are granted inside Nory ('Can add and edit inventory items, recipes and suppliers'), and the documented third-party links are accounting exports (Xero, QuickBooks), not an inventory or costing engine. No MarginEdge/MarketMan/Restaurant365-class dependency appears anywhere in the documentation. https://help.nory.ai/en/articles/8135926-creating-a-recipe-in-nory · retrieved 2026-08-06 adversarially verified

inventory-menu-margin-linkage differentiator

Inventory Insights attributes each sale to a menu item via the recipe linked to its POS ID ('Because Nory knows which recipe is attached, it can automatically deplete stock and attribute the sale to the correct menu item') and reports 'Actual Gross Profit: this is your profit margin on the Food and Beverage items you sold, once you account for the cost of the ingredients' against theoretical GP. The researcher's claim that GP targets are settable at menu level is not documented — Budgets covers sales, labour and COGS targets, not menu-level GP. https://help.nory.ai/en/articles/6752734-getting-started-with-inventory-insights · retrieved 2026-08-02 adversarially verified

reporting-realtime-dashboard

Live P&L across locations updating every 15 minutes — revenue, gross profit and labour cost — with mobile-first access off premise. https://nory.ai/product/business-intelligence · retrieved 2026-08-01

reporting-eod-closeout

'Nory links directly to your EPOS system. Nory takes the restaurants net sales figure (Gross sales - VAT - Service charge = Net sales) and displays that on your sales insights page.' The POS-sales explainer draws the boundary explicitly: 'Your POS focuses on accounting, meaning when payment is taken. Nory focuses on operations, meaning when food is prepared and costs occur' (article 13397068). The documented reports - Sales Insights, Labour Insights, Inventory Insights, Stock Reconciliation Report, Management Report, Accounted Waste Dashboard, Purchasing Insights, Budgets - are enumerated field by field; the Management Report's fields are beginning inventory, deliveries, transfers, ending inventory, COGS, sales, cost of sales theoretical and actual, GP and variance (article 11728106). No tender-type, tax, refund, paid-out or cash-deposit line appears in any of them, and the words drawer and tender do not occur in the help centre in an operational sense. https://help.nory.ai/en/articles/7845382-sales-and-forecasts · retrieved 2026-08-08

reporting-pmix-modifier-level

Item-level drill-down from group GP into specific items is documented; modifier-level PMIX with gross/net split by daypart and revenue centre is not. https://nory.ai/product/inventory · retrieved 2026-08-01

reporting-comps-voids-audit

Walked all 22 help.nory.ai collections (126 articles, Googlebot UA - the site serves full server-rendered HTML; its /en/search endpoint returns an empty body and is unusable). Nory does receive item-level POS data (POS IDs mapped to recipes, article 11792150) and does have a discount concept - 'Meal deal / discount' is a recipe type used to split sales across food and beverage (article 8135926) - and its audit machinery elsewhere is real (per-timecard action log with actor and timestamp, order Show History). But nothing in the sales articles (7845382, 13397068), the Insights articles (6752734, 7669134, 8123742) or the Stock Reconciliation and Management Report definitions (10741975, 11728106) says whether comps, voids, refunds or price overrides are ingested from the POS at all, let alone reported with the applying employee, the approving manager, reason codes and timestamps. www.nory.ai/product/business-intelligence describes the reporting surface as revenue, GP, labour, budgets and reviews and is marketing in any case. Unresolved: the ingest schema is not published and no report definition covers it.

reporting-cash-over-short

Nory's own boundary statement: 'Your POS focuses on accounting, meaning when payment is taken. Nory focuses on operations, meaning when food is prepared and costs occur', and the data it takes from the EPOS is the net sales figure (gross - VAT - service charge) plus order-level lines for stock depletion (article 7845382). Tips are the one payment-adjacent item Nory ingests, and only where the POS can share them, for tronc distribution (article 8912455). Nory's counts are inventory counts - the count workflow covers items, batches and storage areas with no cash or float line (article 6607628) - and the Stock Reconciliation and Management Reports are valued in stock, not tender (article 11728106). With no expected-cash figure and no counted-cash entry, no per-drawer, per-shift or per-employee over/short comparison can exist. https://help.nory.ai/en/articles/13397068-understanding-your-pos-sales-in-nory · retrieved 2026-08-08

reporting-labor-productivity

Projected vs actual labour cost tracked hourly plus orders-per-labour-hour productivity for site-to-site comparison, driven by Nory's own clock-in data. https://nory.ai/product/business-intelligence · retrieved 2026-08-01

reporting-server-scorecards differentiator

Checked help.nory.ai/en/articles/7669134 (labour performance), whose metric toggle is enumerated as Hours, SPLH, OPLH, Cost and COL% and which operates at group, location, daily/weekly/monthly level - no employee dimension. 8545680 (tracking employees' attendance), 8389646 (timecards) and 8435424 (HR exports: new starter, leavers, employee details, employee detail changes) are attendance and payroll records, not sales performance. 8912455 (Nory Tips/Tronc) does show money per employee per day, but it is pooled POS tip totals redistributed by hours worked and department/position/tenure points - 'Tips distribution is calculated per day, per branch' - so it is not tips as a percentage of that server's own sales. Average check size is documented only as a location-level forecast metric (7845382). Unresolved because Nory never publishes the schema of the POS sales feed: 14005466 says the POS provides 'sales data, revenue breakdown, covers (where applicable), and menu item performance' without saying whether an employee/server identifier travels with it, and there is no public API reference to check.

reporting-channel-profitability differentiator

'Nory also provides detailed forecasts for: Dine-in revenue, Pick-up revenue, Delivery revenue, Average check size', each automatically compared against the previous equivalent period, with sales-versus-forecast tiles and an Orders view. Shortfalls: (1) revenue only - margin is split food vs beverage (article 7845663) and the GP/COGS engine is driven by recipe depletion and stock counts, with no channel dimension in the Management Report or Stock Reconciliation Report definitions (11728106, 10741975); (2) delivery is a single line, not one line per marketplace; (3) no commission, marketplace fee or net-of-fee figure is captured anywhere in the help centre, so channel revenue is gross of marketplace commission. https://help.nory.ai/en/articles/7845382-sales-and-forecasts · retrieved 2026-08-08

reporting-multiloc-drilldown differentiator

Re-sourced off the franchise marketing page. Purchasing Insights documents an explicit group/site toggle — filter 'by location or group' to 'view insights at a group level or for an individual location' — with further drill-down by supplier, item and category. Corroborated by the location selector in Sales and forecasts and by the estate-wide Schedules overview, which surfaces planned vs actual COL % per branch so operators can 'quickly see which branches are suffering from high planned COL'. Drill-down to individual invoices, asserted in the original note, is not documented. https://help.nory.ai/en/articles/8123742-purchasing-insights · retrieved 2026-08-02 adversarially verified

reporting-custom-report-builder differentiator

Read every reporting article in the two relevant collections - help.nory.ai/en/collections/6619222-reporting-on-inventory and /2693559-monitoring-and-driving-business-performance - plus the reconciliation collection: Inventory Insights (6752734), Labour Insights (7669134), Purchasing Insights (8123742), Accounted Waste Dashboard (12630212), Stock Reconciliation Report (11723716, 10741975, 11693760), Management Report (11728106), Sales and Forecasts (7845382) and Budgets (11496364). All are fixed dashboards with enumerated fields; the only user-controlled dimensions are date range, location, location group and category filters, and the only save/share affordances found are Budgets' 'Export to CSV or share a view via link'. No dimension/measure/filter builder and no saved-report object is described. Left unknown because these are per-report how-to articles rather than an exhaustive statement of the analytics surface, www.nory.ai/product/business-intelligence is marketing (grade D) and simply lists the same dashboards, and Nory publishes no admin guide or API reference against which to check.

reporting-scheduled-delivery

The notifications article enumerates Nory's entire outbound message surface under two headings. Workforce: 'Managers receive 3 notifications via email: Schedule request created/resubmitted by employee; Schedule request cancelled by employee; Visa/document expiry alerts (60/30 days)', plus a fixed employee list (document rejected, document upload reminder, schedule published, schedule updated, request approved/rejected, swap cancelled/rejected, invitation to join, signature request, visa expiry). Inventory Management: only scan-completion push to the user who scanned, and an email copy of a placed supplier order to the user who placed it - whose tip, 'To send email copies of supplier orders to additional recipients, go to Suppliers, select the supplier, and open the Location tab', is the single documented way to add addresses to any Nory email, and it applies to purchase orders, not reports. No report subscription, cadence or recipient list exists anywhere in that surface. Every documented route for getting a report out of Nory is manual: 'Select export to download a CSV of the report you have selected' (HR data export, four report types) and the timecards approve-and-export flow. Withdrawn from this note: an earlier version also cited article 14487078 as a settings enumeration - it is an onboarding best-practice walkthrough rather than an exhaustive inventory, and is not relied on here. https://help.nory.ai/en/articles/14005382-nory-notifications · retrieved 2026-08-08

reporting-raw-warehouse-export differentiator

Documented exports: four HR reports (new starter, leavers, employee details, employee detail changes) with a date range and location filter, 'Select export to download a CSV'; approved timecards ('Select the download button to export a CSV of the approved timecards', article 8389646); the inventory item list including paused items, downloaded from the side menu (article 10531804); and budgets ('Export to CSV or share a view via link', article 11496364). Shortfalls: all are user-initiated downloads, none is transaction-level sales data, and no recurring push to a customer-controlled destination is documented - the only automated outbound flows in the Integrations collection are invoice and nominal-code syncs to Xero (9091692, 15869964) and QuickBooks (15899738). No S3, SFTP, Snowflake or BigQuery destination appears anywhere on help.nory.ai, and www.nory.ai has no developer or API section (/api and /docs return 404). https://help.nory.ai/en/articles/8435424-exporting-your-hr-data · retrieved 2026-08-08

reporting-public-api differentiator

RESOLVES a cell held at unknown on 2026-08-08 with the reasoning that 'www.nory.ai's full navigation ... has no developer, API or documentation entry' and that nothing on nory.ai denies an API -- written the same day sibling cells were scoring api.nory.ai/swagger.json at grade A. The published API is now the operand rather than its absence, and it fails this claim on limbs that a published spec can settle positively. The complete path list is auth/token, auth/refreshToken, branches/{id}, brands/brand, integration/{id}/{integrationName}/{type}, inventory/ingest, inventory/branches/{branchId}/counts, inventory/branches/{branchId}/deliveries, inventory/suppliers, the three inventory recommended-order paths, punch and punch/{id}, settings/customHolidays/{id}, and the five templates paths. There is no order, transaction, sales, payment, tender or menu resource anywhere in it, so the claim's required coverage of orders, payments and menu data is absent from the only API Nory publishes; labor is the one covered domain (punch, templates, customHolidays). Self-service credentials also fail: the only credential path is POST /auth/token taking an existing {email, password}, and this record's extensibility-free-sandbox cell records that no self-service developer registration exists anywhere on nory.ai. Scored no rather than unknown because publication is observable and the published surface is enumerable in full; a private partner API, if one exists, is not a published one. https://api.nory.ai/swagger.json · retrieved 2026-09-01

reporting-webhooks differentiator

Full-text checked all 126 articles across the 22 help.nory.ai collections (fetched with a Googlebot UA; the site's /en/search endpoint returns an empty body and cannot be used): zero occurrences of 'webhook', and the only outbound event machinery documented is the notification set in article 14005382 (three manager emails, a fixed employee list, scan-complete push, order email copy) - all human-addressed, none to a customer-supplied endpoint. The Integrations collection contains only Xero, QuickBooks, Hastee, POS sales and reviews connectors, all vendor-built. www.nory.ai has no developer, API or docs path (/api, /docs, /developers all 404). Unresolved rather than no: outbound webhooks would be documented in a developer reference, and Nory publishes none, so there is no exhaustive surface to argue from - and Nory's own POS ingest is event-driven, so the machinery may exist privately.

reporting-api-not-upcharged differentiator

Checked on 2026-08-08: www.nory.ai/pricing returns 301 to /book-a-chat, the site navigation offers no pricing entry (only 'Book a chat' and an ROI calculator), and no plan names, tiers, per-location fees or list prices appear on the home page, /product/business-intelligence, /product/inventory or /integrations. help.nory.ai carries no commercial terms either; the closest signals are that CPU functionality must be enabled by a Customer Success Manager (article 14600684) and that POS connections are arranged through Support (article 6272780), which shows a sales-gated feature model but says nothing about API pricing. With no published API (see reporting-public-api) and no published price list, both halves of this claim are unavailable; a quote-only vendor cannot be scored no on an upcharge question.

reporting-tier-paywall differentiator

Checked on 2026-08-08: www.nory.ai/pricing 301-redirects to /book-a-chat; the site nav has no pricing item; no plan, tier, edition or SKU name appears on www.nory.ai (home, /product/business-intelligence, /product/inventory, /integrations, /agentic-ai) or anywhere in the 126 help.nory.ai articles. The help centre documents the reports themselves - Sales, Labour and Inventory Insights, Stock Reconciliation and Management Reports, Accounted Waste, Purchasing Insights, Budgets - without any 'available on plan X' gating language; the only gating signals are operational rather than commercial (CPU must be enabled by your Customer Success Manager, article 14600684; the previous Insights dashboard is still served to some customers, article 6752734). Multi-location comparison and labour-vs-sales are documented as standard behaviour of those dashboards, but with no published tier structure it cannot be established what an entry-level paid plan includes.

reporting-history-retention differentiator

Searched all 126 help.nory.ai articles for retention, archive and history language and checked www.nory.ai/legal/terms-privacy and /legal/terms-and-conditions from the footer. No article states how far back transaction-level detail remains queryable. Indirect signals conflict: Labour Insights advises using 'the monthly view for LFL comparisons', implying at least prior-year data (article 7669134), forecasting draws on historical trading patterns and seasonality (7845382), onboarding requests 'Historical sales data (if available)' for migration (14005466), and any two completed counts can be compared (8394219) - but recipe linking only reprocesses 'the last 7 days of sales' automatically and anything older requires Nory Support to run a manual re-ingestion (11792150), which shows a bounded self-service window over historical sales. No archive-retrieval fee is mentioned either way. The privacy notice's 12-month post-deactivation window concerns personal data, not reporting depth. Unresolved: the vendor publishes no retention statement and no API/schema documentation to infer one from.

reporting-anomaly-alerts differentiator

The GP variance gap is flagged with attributed causes and the Compliance Assistant flags rule breaches; operator-configurable metric thresholds with push/email alerting are not documented. https://nory.ai/product/business-intelligence · retrieved 2026-08-01

reporting-nl-query

Checked www.nory.ai/agentic-ai and its five sub-pages (scheduling-assistant, ordering-assistant, compliance-assistant, payroll-assistant, customer-reviews-assistant) and the corresponding help-centre articles: Compliance Assistant is 'a rules engine built into Nory' that checks schedules before publish (15900973, 15617486), Payroll Assistant 'builds pay runs from the real shifts and timecards that already exist in Nory' (15878412), the Ordering Assistant checks stock against forecast and sends supplier POs, Invoice Smart Matching matches scanned invoice lines to items (15230867), and the Reviews Assistant analyses guest reviews (12959993). Each acts on data rather than answering questions about it, and none is described as taking a typed question and returning a figure or chart. www.nory.ai/product/business-intelligence describes the analytics surface as fixed dashboards - 'Revenue, GP and labour in one view. Updated every 15 minutes' - with AI that 'tells you where and why to act', not an ask-anything box; there is no 'Ask Nory' feature in the help centre and the only in-app chat is Intercom support (article 14018489 lists .intercom.io as a required domain). Left unknown because these are marketing pages and per-assistant how-tos, not an exhaustive statement of the AI surface, and the product is under active AI development.

reporting-guest-cohorts differentiator

Nory holds no identifiable guest records — no loyalty and no first-party ordering channel. https://nory.ai/ · retrieved 2026-08-01

reporting-sales-forecast differentiator

Help-centre documentation: "Nory's AI-powered forecasting model predicts your restaurant's sales at an hourly level, up to 35 days in advance", built from the location's own history - "forecasts are tailored to each individual location, taking into account historical trading patterns, seasonality, holidays, and weather where relevant" - and "continuously updates predictions as new sales data comes in". Exposed in the reporting UI: sales-versus-forecast tiles, an Orders view, separate forecasts for dine-in, pick-up and delivery revenue and average check, and "by clicking on a specific day in the chart, you can view hourly sales versus forecast". Consumed by scheduling: the schedule labour header shows "Projected Sales: Nory's forecast for the week based on your sales history" against the location's Cost of Labour target, and Projected COL updates in real time as shifts are added (article 15402192). The vendor's marketing accuracy percentages (97%, 98.5%, 96%) carry no published methodology and remain vendor claims, not findings. https://help.nory.ai/en/articles/7845382-sales-and-forecasts · retrieved 2026-08-06 adversarially verified

reporting-tip-tax-compliance

Tip pool distribution detail per employee flows into the UK pay run under the Employment (Allocation of Tips) rules; declared-vs-charged tip reporting and multi-jurisdiction tax liability summaries are not documented. https://nory.ai/product/payroll · retrieved 2026-08-01

multi-location-org-hierarchy

Group-level and site-level scoping is first-class, with franchisor/franchisee separation; a named three-tier enterprise > region > location object is not documented. https://www.nory.ai/solutions/franchise-networks · retrieved 2026-08-01

multi-location-central-menu-publish

Standardised recipes, portion control and network-wide GP targets are enforced centrally across all locations — but the sellable menu itself lives in the POS, and Nory publishes no menu-push versioning history. https://www.nory.ai/solutions/franchise-networks · retrieved 2026-08-01

multi-location-local-override-policy differentiator

There is no corporate menu record in Nory for field-level locks to apply to. Menu items are authored in the connected POS, not in Nory: 'You'll create that item in your POS as usual. The first time someone buys it, the item appears in Nory under POS IDs', and 'You won't be able to assign a recipe to a POS item until it's been sold at least once through the till. This is how Nory knows the item exists.' The only action a user then takes on that item in Nory is linking it to a recipe; the article documents no name, price, image or availability field on it, and the nearest thing to a locality control is read-only - 'Scroll down to see which locations have access to that specific item', with the caveat that the Last Seen column 'indicates where the item was last sold, not necessarily the only location where it's available'. Item attributes and pricing stay with the POS, so per-field corporate-lock-versus-store-override governance cannot exist here. Withdrawn from this note: an earlier version leaned additionally on article 14487078's company-wide-versus-location settings split as an enumeration - that article is an onboarding best-practice walkthrough, not an exhaustive settings inventory, and in any case it covers operational settings rather than item attributes. https://help.nory.ai/en/articles/11792150-turn-sales-into-stock-movement-how-recipe-linking-works · retrieved 2026-08-08

multi-location-price-zones

Nory has no menu pricing engine; price tiers are a POS concern. https://nory.ai/integrations · retrieved 2026-08-01

multi-location-scheduled-publish differentiator

Nory does not publish menus, prices or promos to anything, so there is no activation to schedule or roll back. The documented direction of travel is POS -> Nory: an item 'only appears in Nory's POS IDs section after it's been sold at least once', and Nory then reprocesses the last 7 days of sales for that item once a recipe is linked. Recipe sale prices in Nory are costing inputs and 'are not automatically updated when an item's price changes'. The publicly served API spec (api.nory.ai/swagger.json) has a single write path into Nory's own inventory model (POST /inventory/ingest) and no menu, price or promo push endpoint. https://help.nory.ai/en/articles/11792150-turn-sales-into-stock-movement-how-recipe-linking-works · retrieved 2026-08-08

multi-location-new-store-template differentiator

Searched help.nory.ai for 'adding a new location / opening a new site' and for 'multi site locations copy duplicate'; the returned articles are about adding USERS, sharing employees between locations and transferring stock between locations, not about standing up a new site. The 'Your settings in Nory' article documents location-specific settings (labour targets, opening hours, departments/positions/stations, clock-in) without describing how a location is created or whether an existing one can be cloned. The published API spec at api.nory.ai/swagger.json exposes GET /branches/{id} only - there is no branch-creation endpoint - and its /templates endpoints (GET, POST, DELETE, POST /apply, POST /recommendation) are branch-scoped templates of unspecified type, not site provisioning. No time-to-open figure appears on nory.ai/solutions/franchise-networks or anywhere in the 415-URL sitemap. Unresolved because Nory documents its onboarding as a data-submission exercise and never describes location creation either way.

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

Named shortfall: the documented model is location-scoped roles inside ONE brand tenant, not a franchisor tenant versus an independently-owned franchisee tenant. 'Permissions in Nory' documents four ordered levels - 'Admin -> Location Manager -> Supervisor -> Employee', all users defaulting to Employee, only an Admin able to change a profile - plus per-user toggles including 'Can access all locations', 'Can access reports for all locations' ('access data for all locations set up within the brand'), 'Can access and edit location groups', 'Can deactivate users from other locations' (Admin only) and a wage-visibility toggle that is explicitly rank-aware (a Location Manager with it on sees Supervisor and Employee wages but not other Location Managers' or Admins'). So corporate can see site-level sales and labour while a site manager is confined to assigned locations. What is NOT documented: any tenancy or ownership boundary making the franchisee a separate legal employer, any ring-fencing of franchisee banking or payroll from the brand admin, and any franchisor config-enforcement grant. The franchisor/franchisee framing and 'granular permission settings that allow franchisors to control what information and features are accessible to franchisees' appear only on the marketing page www.nory.ai/solutions/franchise-networks, which is not admissible for a differentiator yes. https://help.nory.ai/en/articles/8395451-permissions-in-nory · retrieved 2026-08-06 adversarially verified

multi-location-royalty-calculation differentiator

Re-examined on the help centre, not only the marketing site. Searching help.nory.ai for 'franchise' returns exactly two articles - 'Newsfeed' and 'Your settings in Nory' - and the only franchise construct documented is a company-wide setting called 'Location & Franchise Groups', which is a grouping/reporting construct with no fee mechanics described. nory.ai/solutions/franchise-networks talks about brand-standard compliance, standardised recipes and network-wide GP% targets, never royalties, ad funds or percentage-of-sales fees. The published API spec (api.nory.ai/swagger.json) has no fee, royalty or billing endpoint, but it is a partial middleware spec and cannot carry an absence argument on its own. Nothing on either host enumerates the finance module's scope, so this stays unresolved rather than becoming a no.

multi-location-royalty-collection

Checked help.nory.ai (search for 'franchise', the Integrations collection of five articles - Hastee, Xero x2, QuickBooks, connecting sales data - and the 'Your settings in Nory' enumeration, whose only relevant entries are 'Location & Franchise Groups' and 'Accounting'), plus nory.ai/solutions/franchise-networks and the nory.ai sitemap. Nory's documented money movement is payroll and supplier invoices, not franchisee debits; no ACH/direct-debit collection mechanism and no franchisee-visible fee statement appears anywhere. Unresolved because none of those pages purports to enumerate Nory's billing capabilities.

multi-location-consolidated-reporting

Live consolidated P&L across all locations with store-vs-store benchmarking so franchisees can compare against other network sites and identify top performers. https://www.nory.ai/solutions/franchise-networks · retrieved 2026-08-01

multi-location-normalized-item-rollup differentiator

A shared spine exists and tolerates local naming: Smart Matching compares POS item names to recipe names 'accounting for minor spelling variations and word order differences', using price only as a secondary confidence signal, and can be filtered by location; the underlying model is brand-level (the API's counts and orders are keyed on 'brand_item' with a branch id). Purchasing Insights groups by Location, Supplier, Item and Category and can be viewed 'at a group level or for an individual location'. Shortfall: the rollup key is Nory's recipe, not a corporate POS item ID, and nothing is automatic - 'It only suggests matches. You must confirm each link individually', per location, and an item can read as Matched in one location filter and not another. Item-level SALES rollup specifically is documented only through this recipe linkage (sales -> recipe -> theoretical usage); the POS-sales article does not describe a cross-location item sales report. https://help.nory.ai/en/articles/13870043-smart-matching-automatically-link-pos-items-to-recipes · retrieved 2026-08-08

multi-location-cross-location-giftcard

No gift-card product. https://nory.ai/ · retrieved 2026-08-01

multi-location-cross-location-loyalty

No loyalty product. https://nory.ai/ · retrieved 2026-08-01

multi-location-multi-brand differentiator

The claim is about one location/terminal running two brands on the same hardware and drawer with separate receipts - all of which are POS surfaces Nory does not own (it consumes POS sales). What Nory does have is a brand/branch hierarchy: the published API spec at api.nory.ai/swagger.json exposes GET /brands/brand ('Get Brand associated with the User', singular) and branch-scoped inventory, and 'Location & Franchise Groups' appears as a company-wide setting in help.nory.ai's settings article. Neither establishes whether one branch can carry two brands with separately reportable revenue. Checked the settings, permissions and POS-sales articles on help.nory.ai and nory.ai/solutions/multi-location-brands via the sitemap listing; multi-brand groups appear only as named customers. Unresolved.

multi-location-multi-tax-jurisdiction

The no rested entirely on 'Your settings in Nory' (14487078) being a complete enumeration - 'Settings in Nory are divided into two sections' followed by 8 company and 8 location items. I refuted that: the Compliance Assistant articles (15617486 for UK/Ireland, 15900973 for the US, both newer than the settings article) document a separate brand-level compliance settings area with location-level overrides - 'Rules start from the defaults for the jurisdiction. Where a single location needs something different, you can override a specific rule for that location without changing the defaults everywhere else' - which the settings article does not list at all. So Nory demonstrably does run jurisdiction-aware per-location configuration, and the article's silence on tax proves nothing. Nory also plainly holds tax configuration: items carry a Tax Rate in the onboarding spec, categories carry a consistent VAT type mapped to Xero nominal codes ('code 111 (Drinks) often has a VAT rate of 23%, whereas fresh food may be 0%', 9091692), and 'Nory applies a default VAT rate when pushing bills to Xero' (15869964) - purchase-side and category-scoped rather than per-location, but tax configuration nonetheless. Nory does not compute sales tax, taking 'the restaurants net sales figure (Gross sales - VAT - Service charge)' from the EPOS (7845382). Unresolved: whether any per-location tax scoping, exemption or inclusive/exclusive setting exists cannot be determined from any complete published surface. adversarially verified

multi-location-config-audit-log differentiator

Two documented change trails, both narrow. Scheduling keeps 'a complete history of changes throughout the scheduling process' - edits made after the Scheduling Assistant generated a rota, with manager notes, and on resubmission approvers 'can easily identify only the changes made since the previous submission'. Separately, the HR export drawer offers an 'Employee Detail Changes Export' giving 'details on any changes that have been made to an employee file within a pre-selected time frame' as CSV. Shortfall: neither is a configuration audit log. Nothing records who changed a price, tax rate, permission or discount at which location; the schedule history's user attribution, timestamping and exportability are not documented, and no source claims immutability. https://help.nory.ai/en/articles/15694014-greater-visibility-into-schedule-changes-and-updates · retrieved 2026-08-08

multi-location-enterprise-api differentiator

api.nory.ai serves a Swagger 2.0 spec ('Nory Middleware - Sandbox Environment', basePath /app/v1/). Its complete path list is: POST /auth/token, POST /auth/refreshToken, GET /branches/{id}, GET /brands/brand, GET /integration/{id}/{integrationName}/{type}, POST /inventory/ingest, GET+POST /inventory/branches/{branchId}/counts, GET /inventory/branches/{branchId}/deliveries, GET /inventory/suppliers, GET+POST /inventory/brands/{brandId}/branches/{branchId}/recommended-order (+ /accept, /draft), GET /punch and GET /punch/{id}, GET+POST /settings/customHolidays/{id}, and the /templates endpoints. There is no order, transaction, sales or line-item endpoint anywhere in the schema, so transaction-level data cannot be returned at all, let alone for all locations in one call; every inventory and order path takes an explicit {branchId}, and /branches/{id} and /brands/brand return 'the Branch/Brand associated with the User'. No BI/warehouse export is described here or on help.nory.ai. https://api.nory.ai/swagger.json · retrieved 2026-08-08

multi-location-central-labor-policy

Compliance rules (overtime, breaks, minimum wage) are applied automatically by region and enforced at schedule-publication time; terminal-level enforcement is not applicable as Nory owns no terminal. https://nory.ai/product/workforce-management · retrieved 2026-08-01

hardware-commodity-devices differentiator

Re-sourced from the privacy policy to Nory's own Supported Devices & Technical Requirements page, which enumerates commodity requirements only: Nory Team on iOS 14.0+ (iPhone 6s+, iPad 5th gen+) or Android 7.0+ (API 24); Nory Kiosk on iOS 13.0+ or Android 5.1+ (API 22), tablets 7" or larger; Nory IM on the same floors; web app on latest 3 major versions of Chrome, Firefox, Safari (15.6+) and Edge at 956px minimum width. No proprietary or vendor-specific device is required or sold. https://help.nory.ai/en/articles/14018489-supported-devices-technical-requirements · retrieved 2026-08-02 adversarially verified

hardware-os-platforms

Android is evidenced by the Kiosk app's Google Play Services dependency and a web/mobile-first back office is described; no published minimum OS versions or device specs. https://www.nory.ai/legal/nory-kiosk-privacy-policy · retrieved 2026-08-01

hardware-handheld-purpose-built

No ordering handheld — Nory sells no hardware. https://nory.ai/integrations · retrieved 2026-08-01

hardware-handheld-battery-swap differentiator

No first-party handheld. https://nory.ai/integrations · retrieved 2026-08-01

hardware-handheld-lte

No first-party handheld. https://nory.ai/integrations · retrieved 2026-08-01

hardware-offline-mode

Withdrawing the earlier basis: this article's section 3 ('An active internet connection is required at all times... The apps do not support offline mode') is contradicted by its own FAQ Q1, which lists 'offline data caching' among features 'only available through the native mobile apps', so that sentence carries nothing. The value rests instead on the article's closed enumeration of Nory's whole client surface: 'Nory offers three native mobile applications' - Nory Team ('Employee self-service: clock in/out, schedules, availability'), Nory Kiosk ('In-store kiosk app for staff clocking in/out operations') and Nory IM ('Inventory management, ordering, transfers') - plus the app.nory.ai web dashboard for 'scheduling, labour insights, sales reporting, inventory oversight, and restaurant settings'. Not one is an order-entry terminal. Nory is not the POS: the recipe-linking article states a menu item reaches Nory only 'after it's been sold at least once' through the till, so order entry, kitchen printing and cash tendering all happen in the connected POS and their offline behaviour is that vendor's, not Nory's. There is no Nory terminal that could keep taking orders offline, and Nory publishes no staged-degradation list. https://help.nory.ai/en/articles/14018489-supported-devices-technical-requirements · retrieved 2026-08-08

hardware-kds

No KDS product. https://nory.ai/integrations · retrieved 2026-08-01

hardware-kiosk differentiator

'Nory Kiosk' (Google Play, published by Hospitality Growth Services Limited) is a staff-facing app that lets team members clock in for shifts on site. It is not a guest self-order kiosk and has no integrated payment. Re-sourced from the Nory Kiosk privacy policy, which the adversarial pass found described data collection only and said nothing about what the app does; the Play listing is the same evidence already load-bearing for labor-clock-in-at-pos in this record. https://play.google.com/store/apps/details?id=ai.nory.kiosk · retrieved 2026-08-01 adversarially verified

hardware-drive-thru

No drive-thru hardware or timing product. https://nory.ai/integrations · retrieved 2026-08-01

hardware-printer-compatibility

N/A — Nory does no order or kitchen printing. https://nory.ai/integrations · retrieved 2026-08-01

hardware-peripherals

N/A — no drawers, scanners, scales or customer displays; no compatibility list published. https://nory.ai/integrations · retrieved 2026-08-01

hardware-p2pe-terminal

No card entry anywhere in Nory. https://nory.ai/integrations · retrieved 2026-08-01

hardware-tap-to-phone differentiator

No payment acceptance. https://nory.ai/integrations · retrieved 2026-08-01

hardware-pricing-transparency differentiator

Nory sells restaurant management software (Business Intelligence, Inventory, Workforce, Payroll, AI assistants) and no hardware; nothing in its catalogue is a SKU. Pricing is quote-only: the former https://nory.ai/pricing now 301s to this book-a-chat sales form, the vendor's published sitemap.xml (317 URLs) contains no pricing, shop or hardware page, and the site-wide platform nav carries no Pricing link. Citation re-pointed 2026-08-09 after the corpus redirect check; prior URL is dead as a pricing document. https://www.nory.ai/book-a-chat · retrieved 2026-08-09

hardware-ownership-vs-lease differentiator

N/A — no hardware sold or leased. https://nory.ai/integrations · retrieved 2026-08-01

hardware-usable-after-churn differentiator

N/A — the operator's hardware belongs to the POS vendor, so Nory cannot lock it. https://nory.ai/integrations · retrieved 2026-08-01

hardware-rma-sla differentiator

N/A — no hardware, so no warranty or advance-exchange programme. https://nory.ai/integrations · retrieved 2026-08-01

hardware-byod

Staff use the Nory team app on their own phones for shifts, swaps and time off; the permission and device-security model is not documented. https://nory.ai/product/workforce-management · retrieved 2026-08-01

hardware-remote-device-management differentiator

The technical-requirements article enumerates Nory's entire client estate: three customer-installed apps distributed via the Apple App Store and Google Play (Nory Team, Nory Kiosk, Nory IM) with minimum OS versions and storage, plus the web app at app.nory.ai in Chrome/Firefox/Safari 15.6+/Edge. There are no vendor-supplied terminals, printers or KDS, and no hardware of any kind is named. The settings article's two-section enumeration (company-wide and location-specific) contains no device, terminal or software-version management screen, and nothing documents remote reboot, online/offline device status or staged update rollout - app updates come from the platform app stores. https://help.nory.ai/en/articles/14018489-supported-devices-technical-requirements · retrieved 2026-08-08

hardware-selfpour-scales

Searched help.nory.ai for 'scale weight weigh' - the hits are batch recipes, storage areas, prep station and waste articles, none of which mentions weighing hardware; counting is documented as manual entry through count templates in the Nory IM app, and the Supported Devices article names no peripherals at all. The Integrations collection on help.nory.ai holds only five articles (Hastee payroll, Xero x2, QuickBooks, connecting sales data) and nory.ai/integrations shows 15 POS/payment logos (Toast, Lightspeed, Vita Mojo, Square, SumUp, Tevalis, Clover, Zonal, Revel, PixelPoint, Oracle Micros, MyOrderBox, Epos Now, Innova, Captiva) with no claim of completeness and no beverage hardware. Also note the claim requires pours to post to a POS tab, which is the connected POS's function, not Nory's. Unresolved: an integration directory is not an exhaustive enumeration.

hardware-callerid-integration

No telephony or order-entry surface. https://nory.ai/integrations · retrieved 2026-08-01

extensibility-public-api-docs

OVERTURNS a grade-B no dated 2026-08-01 whose rationale ended 'No public developer surface found.' -- written a week before three cells in this same record (extensibility-free-sandbox, extensibility-oauth-partner-apps, multi-location-enterprise-api) were scored at grade A on 2026-08-08 from a spec served openly at api.nory.ai/swagger.json, and never revisited. Re-fetched 2026-09-01: HTTP 200 anonymously, 18,020 bytes, no robots.txt on the host (404, allowed under RFC 9309). It is a Swagger 2.0 document, 'Nory Middleware - Sandbox Environment' v1.0.0, basePath /app/v1/, declaring servers ['https://sandbox.nory.ai', 'http://localhost:8000'], one securityDefinition (bearerAuth) and twenty documented paths with request and response schemas. That is public API reference documentation readable with no partner agreement, NDA or sales call. PARTIAL rather than yes on two shortfalls: it is a sandbox middleware spec covering only auth, branches, brands, integration, inventory, punch, settings and templates -- there is no order, payment or menu resource -- and there is no developer portal, no rendered reference and no self-service registration anywhere on nory.ai (no developer, API or docs entry in the site navigation; /api, /docs and /developers 404; docs./developers./developer.nory.ai do not resolve). https://api.nory.ai/swagger.json · retrieved 2026-09-01

extensibility-api-access-cost differentiator

Corrected the premise: an API does exist and is publicly described at api.nory.ai/swagger.json. What is missing is price. nory.ai/pricing resolves to the 'See Nory in action' demo-booking page with no plans or figures, and the sitemap at www.nory.ai/sitemap.xml contains no pricing page among its 415 URLs. The terms at nory.ai/legal/terms-and-conditions make everything order-form driven - if the customer 'wishes to add components or integrations, the parties shall agree to an amended or new order form' - and never mention API access as an entitlement, a module or a surcharge. Nothing on help.nory.ai's Integrations collection addresses cost either. Unresolved because Nory publishes no price list of any kind.

extensibility-partner-revshare

The partner programme advertises Integration, Reseller and Referral tracks and 'a commission on each lead referred' but publishes no percentage, fee or certification cost. https://www.nory.ai/partner-program · retrieved 2026-08-01

extensibility-free-sandbox differentiator

The publicly served spec is titled 'Nory Middleware - Sandbox Environment' and declares servers ['https://sandbox.nory.ai', 'http://localhost:8000'], so a distinct sandbox tier exists and its surface is documented. Shortfalls: sandbox.nory.ai does not resolve from the public internet (DNS failure on retrieval), the only authentication is POST /auth/token taking an existing email and password - there is no self-service developer registration anywhere on nory.ai (no developer, signup or portal page in the 415-URL sitemap; docs./developers./developer.nory.ai do not resolve) - and no seeded test data is described. Access therefore appears to require credentials issued by Nory rather than being open to any developer. https://api.nory.ai/swagger.json · retrieved 2026-08-08

extensibility-oauth-partner-apps

The spec declares exactly one securityDefinition: {'bearerAuth': {'type':'apiKey','name':'Authorization','scheme':'bearer','in':'header'}}, and the only way to obtain one is POST /auth/token with a body of {email, password}, refreshed via POST /auth/refreshToken. That is a resource-owner password grant with the operator's own login credentials handed to the integrator - precisely the credential sharing the claim excludes. There is no authorization endpoint, no client_id/client_secret, no scopes, no consent step and no per-app revocation anywhere in the schema, and no OAuth documentation exists elsewhere (help.nory.ai search for 'API' returns only two articles, both about enabling the customer's POS API for Nory, and docs./developers.nory.ai do not resolve). https://api.nory.ai/swagger.json · retrieved 2026-08-08

extensibility-webhooks-push

Retrieved the full spec at api.nory.ai/swagger.json: 22 paths, all request/response REST, with no callback or subscription endpoint and nothing named webhook, event or subscription. That is suggestive but not decisive - the document is Swagger 2.0, a format with no way to express webhooks, and it is labelled a sandbox middleware spec rather than a complete platform reference. Also checked: help.nory.ai search for 'API' (two hits, both about connecting the customer's POS to Nory), the five-article Integrations collection, and the nory.ai sitemap, which has no developer or API page among 415 URLs; docs.nory.ai, developers.nory.ai and developer.nory.ai do not resolve. Nory's own inbound sales ingestion is described only as a partner integration arranged during onboarding. Unresolved - no source states whether Nory emits order-lifecycle events (and order lifecycle is in any case the connected POS's domain).

extensibility-webhook-reliability differentiator

Conditional on a webhook mechanism that is itself undocumented. The published spec at api.nory.ai/swagger.json contains no callbacks, no signature header, no retry or backoff language and no event log; it also documents no error semantics beyond bare 400/401/403/500 descriptions. No developer documentation site exists (docs./developers./developer.nory.ai do not resolve; the www.nory.ai sitemap's 415 URLs include no developer page) and help.nory.ai returns nothing on the subject. Unresolved rather than no, because Swagger 2.0 cannot express webhook delivery semantics even where they exist, so the spec's silence is not an enumeration.

extensibility-order-injection-api

Nory has no POS to inject orders into. https://nory.ai/integrations · retrieved 2026-08-01

extensibility-menu-write-api differentiator

POST /inventory/ingest is summarised as 'Ingest items / batch items / menu items' and is the spec's one menu-related write. Shortfalls: its request body is the Ingest definition - {brand_id: string, ingest_type: string, content: string} - so the payload shape, and with it any price or modifier fields, is undocumented; there is no corresponding read endpoint for menu items and no update or delete path, making this a one-way ingest rather than read/write; and what is being written is Nory's own recipe/menu-item costing records, not the connected POS's menu, which Nory receives rather than authors (POS items appear in Nory only after first sale). Modifiers are handled in Nory as separate 'Remove'-type recipes created in the UI, not as an API object. https://api.nory.ai/swagger.json · retrieved 2026-08-08

extensibility-data-symmetry differentiator

Read-only in the full schema: GET /branches/{id}, GET /brands/brand, GET /inventory/suppliers, GET /inventory/branches/{branchId}/deliveries, GET /integration/{id}/{integrationName}/{type}, GET /punch and GET /punch/{id} (employee punch data). Only counts (GET+POST), recommended orders, custom holidays and templates have write paths, and /inventory/ingest writes without a matching read. Employees exist only as punch reads with no create/update; suppliers, deliveries and branches cannot be written at all; orders and customers are not present in either direction. The claim requires every readable core object to be writable through the same API, and the schema itself shows that is not the case. https://api.nory.ai/swagger.json · retrieved 2026-08-08

extensibility-published-rate-limits

The claim is about publication, and the entire published surface was retrieved. api.nory.ai/swagger.json declares response codes per operation (200/204/400/401/403/500) with no 429 anywhere, no rate-limit or retry-after headers in any parameter or response object, and empty top-level 'responses' and 'parameters' sections. No numeric quota, burst allowance or throttling description appears in the info block or any summary. There is no other developer documentation to consult: docs.nory.ai, developers.nory.ai and developer.nory.ai do not resolve, api.nory.ai/ redirects to nory.ai, /docs, /api-docs and /redoc return 404, and the 415-URL sitemap at www.nory.ai contains no developer page. https://api.nory.ai/swagger.json · retrieved 2026-08-08

extensibility-doordash-preferred differentiator

Nory is absent from DoorDash's 2026 Preferred Integration Partner cohort. DoorDash's own newsroom post of 18 May 2026 names it in full - 'the 2026* cohort DoorDash Preferred Integration Partners include Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, and UrbanPiper' - with the footnote that the list 'was generated based on performance and feature sets as of May 8, 2026'. The programme covers POS and middleware providers alike, and the announcement's stated standards are real-time item availability, integrated reporting, detailed error reporting and promotion-funding transparency. Citation corrected: the previously cited get.doordash.com learning-center URL 301s to merchants.doordash.com and then 404s. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-08

extensibility-first-party-delivery-integrations differentiator

Nory's published integration list is POS, payments-adjacent and accounting only — no DoorDash, Uber Eats, Grubhub or Deliveroo appear. https://nory.ai/integrations · retrieved 2026-08-01

extensibility-middleware-compatibility

Checked first-party surfaces this pass rather than aggregator profiles. www.nory.ai/integrations lists 15 logos, all POS or payment providers (Toast, Lightspeed, Vita Mojo, Square, SumUp, Tevalis, Clover, Zonal, Revel, PixelPoint/PAR, Oracle Micros, MyOrderBox, Epos Now, Innova, Captiva) - no Deliverect, Chowly, Otter or Checkmate - and the page makes no completeness claim. The Integrations collection on help.nory.ai holds five articles (Hastee, Xero x2, QuickBooks, connecting sales data) and 'Connecting your sales data to Nory' says only 'Nory partners with leading EPOS providers around the world, simply reach out to our Support team and ask if we work with your provider', which is an explicit statement that the public list is not the whole list. The published API spec has a generic GET /integration/{id}/{integrationName}/{type} that names no partners. Note also the claim asks whether the POS is a supported endpoint for middleware - Nory is not the POS. Unresolved; a directory is never an exhaustive enumeration.

extensibility-accounting-connectors

Verified verbatim: Nory 'connects directly to the major POS systems and accounting tools ... including: Toast, Lightspeed, Vita Mojo, SumUp, Shift4 and Xero.' Xero is the only accounting platform named anywhere; no QuickBooks, no GL journal mapping. Partial is right. Also note Shift4 appears here but is missing from the dossier's integrations roster. https://nory.ai/product/business-intelligence · retrieved 2026-08-01 adversarially verified

extensibility-payroll-export

Approved hours export 'clean to payroll' and Nory runs UK payroll natively, but no two named third-party payroll providers with documented formats are published. https://nory.ai/product/payroll · retrieved 2026-08-01

extensibility-bi-data-warehouse differentiator

What is documented is UI-bound and manual: CSV downloads from the HR export drawer (New Starter, Leavers, Employee Details, Employee Detail Changes) and timecard exports, both self-serve but per-report; Purchasing and Inventory Insights are described without any export option; the terms at nory.ai/legal/terms-and-conditions provide only a one-off vendor-supplied export 'at the Customer's cost' following termination. The published API spec at api.nory.ai/swagger.json has no bulk, scheduled or destination-targeted export path (and no transaction object at all). Nothing on help.nory.ai mentions S3, SFTP, Snowflake, BigQuery or a warehouse share. Unresolved rather than no: a REST middleware spec and a help centre are not where an enterprise data-share offering would necessarily be published, and Nory's BI module is sold via quote.

extensibility-app-marketplace

A public integrations page names POS and other partners (Toast, Square, Lightspeed, Clover, Zonal, Revel, PAR PixelPoint, Oracle Micros, Epos Now, Innova, Captiva, Vita Mojo, SumUp, Tevalis, My Order Box) but it is a logo directory, not a self-install marketplace. https://nory.ai/integrations · retrieved 2026-08-01

extensibility-custom-fields-scripting

The configurable surface documented in help.nory.ai's 'Your settings in Nory' is a fixed list of company-wide and location-level sections with no custom-field, formula or script facility; the closest user-defined objects are count templates, item categories, shift/absence types, overtime rules and custom holidays (the last exposed as GET/POST /settings/customHolidays/{id} in the API), all of which are typed features rather than user-defined fields or logic. The published spec at api.nory.ai/swagger.json has no scripting, function or custom-attribute endpoint. Unresolved because neither the settings article nor a sandbox middleware spec claims to enumerate Nory's extensibility, and no developer documentation site exists to check (docs./developers./developer.nory.ai do not resolve).

extensibility-headless-embedded

Nory has no transaction engine to drive headlessly. https://nory.ai/integrations · retrieved 2026-08-01

extensibility-api-versioning-deprecation

Versioning exists only as a URL segment: basePath '/app/v1/' with info.version '1.0.0' and description 'Nory'. No changelog, release-notes, deprecation, sunset or notice-period text appears in the spec, and no operation is marked deprecated. The complete publication surface was checked: docs.nory.ai, developers.nory.ai and developer.nory.ai do not resolve; api.nory.ai/docs, /api-docs and /redoc return 404 and api.nory.ai/ redirects to nory.ai; the www.nory.ai sitemap's 415 URLs contain no developer, API, changelog or release-notes page; and help.nory.ai's search for 'API' returns only two articles, both about enabling the customer's POS API during onboarding. The terms at nory.ai/legal/terms-and-conditions state no notice period for service changes beyond fee and renewal notices. https://api.nory.ai/swagger.json · retrieved 2026-08-08

extensibility-data-portability-exit differentiator

T&Cs commit to an export 'in a commonly used format' on termination but explicitly 'at the Customer's cost', with no defined window and no self-serve mechanism. https://www.nory.ai/legal/terms-conditions · retrieved 2026-08-01

reliability-offline-order-entry

No order entry. https://nory.ai/integrations · retrieved 2026-08-01

reliability-offline-card-auth differentiator

No card acceptance. https://nory.ai/integrations · retrieved 2026-08-01

reliability-offline-decline-liability differentiator

No store-and-forward payments. https://nory.ai/integrations · retrieved 2026-08-01

reliability-lan-degraded-multi-terminal differentiator

No terminals or shared check state. https://nory.ai/integrations · retrieved 2026-08-01

reliability-local-transaction-engine differentiator

Nory describes itself as cloud-native; there is no on-premise engine and no ordering path. https://nory.ai/integrations · retrieved 2026-08-01

reliability-offline-kds-printing

No KDS or kitchen printing. https://nory.ai/integrations · retrieved 2026-08-01

reliability-printer-fallback

No printing. https://nory.ai/integrations · retrieved 2026-08-01

reliability-sync-conflict-handling

Not determinable. The prior no rested on Nory having no offline mode at all, but the Supported Devices & Technical Requirements article is internally inconsistent on exactly that point: section 3 states 'An active internet connection is required at all times for all Nory apps and web access. The apps do not support offline mode', while FAQ Q1 on the same page lists 'offline data caching' among the features 'only available through the native mobile apps'. Some local-then-sync behaviour therefore exists on iOS/Android, but Nory publishes no description of it and no conflict-resolution rule - no last-write-wins, merge or operator-prompt statement anywhere on help.nory.ai (searched via its /en/search JSON endpoint for offline, sync, conflict and backup), and the sandbox spec at api.nory.ai/swagger.json carries no version, etag or conflict field on its count objects. Absence of documentation for a mode that does exist is unknown, not no.

reliability-offline-feature-matrix

No offline feature matrix is published anywhere on the site or help centre for any Nory surface. https://help.nory.ai/en/ · retrieved 2026-08-01

reliability-public-status-page

status.nory.ai does not resolve (DNS NXDOMAIN) and no status URL appears among the 573 sitemap entries. Not proof of absence, but no public status page could be located. https://nory.ai/sitemap.xml · retrieved 2026-08-01

reliability-contractual-uptime-sla differentiator

Confirmed: the T&Cs publish only support response/resolution targets (P0 60 min / <12h, P1 <3h / <48h, P3 72h / TBD) and support hours of '9am to 6pm, 7 days a week' excluding 25 December. No uptime percentage, no service credits. This also confirms reliability-247-live-support = no. https://www.nory.ai/legal/terms-conditions · retrieved 2026-08-01 adversarially verified

reliability-incident-postmortems

The sitemap enumerates the whole of www.nory.ai - 415 URLs covering product, solutions, agentic-AI, legal, success stories, podcasts, content library and ~280 blog posts - and contains no status, uptime, incident, trust or security page. status.nory.ai, trust.nory.ai and security.nory.ai fail DNS resolution; https://nory.statuspage.io returns a 302 to https://www.statuspage.io, i.e. no claimed status page. help.nory.ai has 22 collections, none of them about incidents or service status. The terms at nory.ai/legal/terms-and-conditions provide a support-response SLA (P0 60-120 minutes response, service credits as sole remedy) but no uptime commitment and no incident-reporting obligation. https://www.nory.ai/sitemap.xml · retrieved 2026-08-08

reliability-247-live-support

T&Cs state support is available '9am to 6pm, 7 days a week' via in-app chat. Seven days, but not 24/7 and not phone-first. https://www.nory.ai/legal/terms-conditions · retrieved 2026-08-01

reliability-onsite-install differentiator

Nory states it offers 'hands-on training sessions (in person where situation allows), tutorials, and workshops tailored to different user groups', plus 'drop-in support sessions at key project phases' on larger rollouts and 'enhanced support to the project team during go-live weeks' on smaller ones (rollout best-practice post by Stephen Mannion, 25 Feb 2025). Shortfalls, all named: in-person delivery is discretionary ('where situation allows'), not an entitlement - the T&Cs section 7 grants only online training videos, live training via web-conferencing and chargeable 'additional remote (i.e. online) training', and the help centre's train-the-trainer article describes the current default as training 2-3 internal champions with remote backup (help centre, 60-second Looms, in-app chat), listing in-store sessions among approaches Nory 'tested' before it 'evolved' the approach. There is no certified dealer or installer network (nory.ai/partner-program is a referral/affiliate scheme) and no hardware install to perform - the client estate is three app-store apps on customer-owned devices plus a browser. Implementation scope is contractually deferred: 'The scope of work included with the implementation shall be set out in the applicable order form', so an on-site go-live is a per-deal negotiation, not a published offering. Evidence is a vendor blog post, hence grade D. https://www.nory.ai/blog/what-ive-learned-from-tech-rollouts · retrieved 2026-08-08

reliability-menu-build-service differentiator

Nory runs the onboarding and defines the data model, but the authoring is the operator's. The onboarding article sets a full inventory and recipe specification (supplier-specific name, SKU, item size, unit of measure, ordered-in-multiples-of, price, tax rate; batch recipes for conversions; a measurable menu-item recipe for every sold item; the 'Critical Rule: Units Must Match Inventory'; the 'Remove' modifier pattern) and closes with a 'Recipe & Inventory Submission Checklist' the customer completes - 'Every menu item has a recipe', 'All ingredients are measurable'. Nory's own build work is stated for workforce, not menu: 'we will request that an account is created for Nory within your existing WFM system so we can migrate and configure your workforce structure'. Shortfall: no source says Nory writes the recipes or performs the menu build; in-product recipe creation (Lightning Recipe Creation, Creating a Recipe in Nory) is documented as self-service, and POS item to recipe linking must be confirmed one item at a time by the operator. https://help.nory.ai/en/articles/14086602-what-to-expect-in-your-onboarding-journey · retrieved 2026-08-08

reliability-hardware-replacement-sla

N/A — Nory supplies no hardware. https://nory.ai/integrations · retrieved 2026-08-01

reliability-backup-restore

The terms state 'Customer acknowledges and agrees that Customer is responsible for performing any backups of Customer data', yet no operator-triggered backup or restore function is documented anywhere on help.nory.ai - the only self-serve extractions are per-report CSVs (New Starter, Leavers, Employee Details, Employee Detail Changes, timecards). A full data extract exists only at the end of the relationship: 'Following termination, Nory will, at the Customer's cost, provide the Customer an export of the Customer's Data in a commonly used format', with 30 days to take it. On recovery figures, the DPA's technical and organisational measures recite the GDPR formula - 'Measures for ensuring the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident' - with no RPO, RTO or uptime number; the SLA schedule quantifies support response and resolution targets only. https://www.nory.ai/legal/terms-and-conditions · retrieved 2026-08-08

reliability-pci-dss-4-attestation

Not applicable and not published — Nory is outside the cardholder data environment. https://www.nory.ai/legal/customer-privacy-notice · retrieved 2026-08-01

reliability-mfa-role-based-access

The privacy notice names encryption and multi-factor authentication among security measures, and franchise permissions are granular; enforceable MFA policy configuration is not documented. https://www.nory.ai/legal/customer-privacy-notice · retrieved 2026-08-01

reliability-self-serve-training

T&Cs grant customers 'unlimited access to the on-line training videos' plus scheduled live training, and help.nory.ai is public — but the video library is customer-gated and no terminal training/practice mode exists. https://www.nory.ai/legal/terms-conditions · retrieved 2026-08-01

reliability-failover-terminal-role differentiator

No terminal architecture. https://nory.ai/integrations · retrieved 2026-08-01

reliability-cellular-backup

No vendor-supplied connectivity or terminals. https://nory.ai/integrations · retrieved 2026-08-01

commercial-month-to-month-contract differentiator

Public T&Cs fix the term at twelve months with successive automatic renewals. https://www.nory.ai/legal/terms-conditions · retrieved 2026-08-01

commercial-no-early-termination-fee differentiator

No ETF is stated, but there is also no termination-for-convenience right — termination is limited to material breach, insolvency and non-payment — so the 12-month commitment stands. Nory does not publish a no-ETF promise. https://www.nory.ai/legal/terms-conditions · retrieved 2026-08-01

commercial-autorenew-terms-published

Confirmed in the publicly accessible T&Cs — term, automatic renewal and the 90-day notice window are all published, which is genuinely rare and is one of the few 'documented' confidences in this dossier that survives scrutiny. https://www.nory.ai/legal/terms-conditions · retrieved 2026-08-01 adversarially verified

commercial-processing-not-bundled differentiator

Nory sells no payment processing and is explicitly POS- and vendor-agnostic; it integrates with Toast, Square, Lightspeed, Clover, Zonal, Revel, PAR PixelPoint, Oracle Micros, Epos Now, SumUp and others. There is no processing lock of any kind. https://nory.ai/integrations · retrieved 2026-08-01

commercial-interchange-plus-published differentiator

N/A — Nory is not a payment provider. https://nory.ai/integrations · retrieved 2026-08-01

commercial-rate-increase-clause differentiator

Section 5 caps the in-term uplift: 'Nory may increase subscription fees annually, effective on each anniversary of the commencement of the Initial Term, by an amount equal to the percentage increase in the United States Consumer Price Index over the preceding 12-month period.' EU customers may terminate within 30 days of notice of a proposed fee increase, effective at end of term. Shortfalls: the same section then allows Nory to 'propose revised subscription fees for any Renewal Term by providing written notice', with no cap and only an order-acknowledgment email at least 30 days before renewal - so the CPI ceiling governs anniversary uplifts, not renewals; the penalty-free exit on an increase is available to EU-contracted customers only, while others must give 90 days' notice before term end (and EU customers terminating early owe the remaining subscription fees); and the claim's subject, a card-processing agreement with pass-through interchange, does not exist here - Nory is not a payment processor and its fees are subscription fees under an order form. https://www.nory.ai/legal/terms-and-conditions · retrieved 2026-08-08

commercial-pricing-published

No pricing is published. /pricing serves no prices and no pricing URL exists among the 573 sitemap entries; every path leads to 'book a chat'. https://nory.ai/sitemap.xml · retrieved 2026-08-01

commercial-module-unbundling differentiator

Separable purchase is documented: Section 2 provides that where the customer 'wishes to add components or integrations, the parties shall agree to an amended or new order form', and fees increase accordingly when locations or integrations are added - consistent with the four separately marketed modules (Business Intelligence, Inventory, Workforce Management, Payroll). Shortfalls: there is no corresponding mechanism to remove a module - termination operates on the agreement, with automatic renewal unless either party gives 90 days' written notice before the term ends, so a module cannot be cancelled independently mid-term; nothing addresses whether removing one reprices the rest; and no a-la-carte price exists to inspect, since nory.ai publishes no pricing page at all (nory.ai/pricing is a demo-booking form and the 415-URL sitemap contains no pricing page). Nory also sells no base POS subscription - it is not a POS. https://www.nory.ai/legal/terms-and-conditions · retrieved 2026-08-08

commercial-hardware-purchase-outright

N/A — Nory requires and sells no terminals, KDS screens or printers; those come from the incumbent POS vendor. https://nory.ai/integrations · retrieved 2026-08-01

commercial-hardware-not-locked differentiator

Nory is wholly hardware-agnostic: browser back office plus apps on standard Android/iOS devices, no proprietary device requirement — but it also publishes no supported-device documentation. https://www.nory.ai/legal/nory-kiosk-privacy-policy · retrieved 2026-08-01

commercial-implementation-fee-published

The researcher missed a published figure. Nory's franchise-networks FAQ states outright: 'No, Nory does not charge any implementation fees' — deployment, integration, training and setup included. That is a published implementation-fee position (zero). Caveat it: it is a marketing-FAQ claim, not a contract term, and the T&Cs still say additional remote training 'may be an additional cost'. The pricing.implementation_fee field should move from 'unknown — not published' to 'vendor states none, claim-level'. https://www.nory.ai/solutions/franchise-networks · retrieved 2026-08-01 adversarially verified

commercial-data-export-self-serve

Documented self-serve exports exist: from Scheduling & Workforce > People, a download drawer produces four CSVs - New Starter, Leavers, Employee Details and Employee Detail Changes - with a date range and all-locations or single-location selection, and a separate article covers reviewing, editing, approving and exporting timecards. No support contact or fee is mentioned for these. Shortfalls, each named: the labour side is covered but the transactional side is not - no article documents exporting POS sales, order line items or payments, and Purchasing Insights, Inventory Insights and the reconciliation reports are described as on-screen views with no export control; the published API has no order or transaction object at all; and the terms still make a full data extract a vendor-performed, chargeable act available only after termination - 'Nory will, at the Customer's cost, provide the Customer an export of the Customer's Data', with 30 days to collect it. https://help.nory.ai/en/articles/8435424-exporting-your-hr-data · retrieved 2026-08-08

commercial-export-customer-and-loyalty differentiator

Nory holds no guest records, loyalty ledgers or gift-card liabilities to export. https://nory.ai/ · retrieved 2026-08-01

commercial-post-termination-export-window differentiator

T&Cs promise an export in a commonly used format on termination, but at the customer's cost and with no defined number of days. https://www.nory.ai/legal/terms-conditions · retrieved 2026-08-01

commercial-data-ownership-clause differentiator

Score stands but the quotation is not what the T&Cs say and should not be reproduced. The actual clause is stronger for Nory in one respect and narrower in another: customer 'owns the intellectual property rights in any data in any form submitted', while 'Nory shall own all right, title and interest' in de-identified data generated by the Services, used 'for Nory's internal business purposes (including training its proprietary AI models)'. I could not verify the words 'irrevocable', 'royalty-free' or 'publish'. Re-quote before this goes in front of anyone. https://www.nory.ai/legal/terms-conditions · retrieved 2026-08-01 adversarially verified

commercial-source-available-selfhost

Proprietary closed-source SaaS; cloud-native only, no source or self-hosting option. https://nory.ai/ · retrieved 2026-08-01

commercial-pci-p2pe-tokenization

N/A — no card data touches Nory; no SAQ type is named because none applies. https://www.nory.ai/legal/customer-privacy-notice · retrieved 2026-08-01

commercial-pci-dss-4-controls

No PCI DSS 4.0.1 posture is published; Nory is outside the CDE. MFA is described generically as a security measure in the privacy notice, not as a PCI control. https://www.nory.ai/legal/customer-privacy-notice · retrieved 2026-08-01

commercial-soc2-attestation

Retrieved the full terms and DPA text and searched it: the strings ISO, 27001 and SOC do not appear anywhere. Security is expressed only as 'commercially reasonable administrative, physical, and technical safeguards' plus a DPA schedule of technical and organisational measures written in GDPR Article 32 language (confidentiality, integrity, availability and resilience; ability to restore availability; regular testing and evaluation), with a customer audit right that Nory will 'allow for and contribute to' subject to reimbursement of its costs - the arrangement a vendor uses when it has no third-party report to hand over. trust.nory.ai and security.nory.ai do not resolve, and the 415-URL sitemap for www.nory.ai contains no security, trust or compliance page. Absence of a stated attestation is not proof no report exists - request it in diligence - but the claim is about the vendor's own statement, and there is none. https://www.nory.ai/legal/terms-and-conditions · retrieved 2026-08-08

commercial-privacy-dsar-tooling

Documented rights process via privacy@nory.ai (access, deletion, restriction, portability) plus a public /legal/request-data-deletion page, and a DPA is referenced as governing Nory-as-processor. No in-app DSAR tooling and no published DPA text. https://www.nory.ai/legal/customer-privacy-notice · retrieved 2026-08-01

commercial-wcag-kiosk-accessibility differentiator

The sitemap enumerates all 415 URLs on www.nory.ai - product, solutions, agentic-AI, integrations, partner program, nine legal pages (terms, privacy notices for Nory IM, Nory Kiosk and Nory Team, customer privacy notice, cookie policy, data deletion), content library, success stories, podcasts and blog - and contains no accessibility, VPAT, ACR or conformance page. help.nory.ai's 22 collections include no accessibility article, and the Supported Devices & Technical Requirements article specifies OS versions, browsers, screen resolutions and bandwidth without any accessibility or assistive-technology statement; the terms and privacy pages are silent on WCAG. Scope note: the claim is not inapplicable - Nory publishes a Nory Kiosk app (ai.nory.kiosk) with its own privacy policy - though that kiosk is a staff clock-in surface rather than a consumer self-order kiosk, and Nory ships no consumer web-ordering product. https://www.nory.ai/sitemap.xml · retrieved 2026-08-08

commercial-dual-pricing-compliant differentiator

No payment or pricing engine. https://nory.ai/integrations · retrieved 2026-08-01