Vendors / Regional & international

Nory

dossier live

Claims in scope
251
Scored
251
Assessed
248
Unknown
3
Not applicable
63
Values challenged
71

Identity

Owner
Independent, venture-backed. Investors named on the About page and Series B post: Kinnevik (Series B lead), Accel, Base10, Playfair, Samaipata, Triple Point, NAP.
Founded
Founded by a restaurant operator (Nory's About page states it was 'founded by a restaurant owner'); the operating legal entity is Hospitality Growth Services Ltd, incorporated in Ireland (per nory.ai privacy notice and the Nory Kiosk app privacy policy). Exact founding year not published on the site.
Scale
$37M Series B announced 16 Sep 2025, bringing total funding to $62.6M; company states it tripled revenue and doubled headcount since Series A. Named customers include Black Sheep Coffee (130+ sites), Jamie Oliver Group, Azzurri, Boston Tea Party, Dave's Hot Chicken, PF Chang's, Stick'n Sushi, Badiani, Rocksalt. Total locations, customer count, ARR and headcount are not published. Source: https://www.nory.ai/blog/nory-series-b-funding-to-revolutionise-restaurant-operations
Who it is for
Multi-site restaurant, coffee and hospitality groups in the UK, Ireland and Europe — Nory's own segmentation is independent brands, multi-location brands, franchise networks and enterprise groups. Practically it sells to groups large enough to care about above-store P&L, labour scheduling and stock control (roughly 5 sites upward, with reference accounts in the 100+ site range). US expansion was named as a Series B use of funds. It is not a POS buyer's decision — it is bought alongside an existing POS.
Site
https://nory.ai/

Pricing

transparency: quote-only · unit: unknown · processor lock-in: no

Software
quote-only. Nory publishes no pricing page — https://nory.ai/pricing does not serve pricing content, and none of the 573 URLs in https://nory.ai/sitemap.xml contains a pricing path. Every CTA on the site is 'book a chat'. Do not substitute a third-party estimate.
Card processing
Not applicable — Nory does not process payments.
Contract
12 months. Nory's public T&Cs state the term is 'twelve (12) months and shall be subject to successive automatic renewals unless notice is received ninety (90) days in advance'. Source: https://www.nory.ai/legal/terms-conditions
Early termination
Not stated. The published T&Cs grant termination rights only for material breach (30-day cure), insolvency, or Nory-initiated termination for non-payment — there is no termination-for-convenience clause and no stated ETF. The practical effect is a committed 12-month term with a 90-day non-renewal notice.

API posture

public API: none

Cost to integrate
unknown. https://www.nory.ai/partner-program advertises Integration, Reseller and Referral partner tracks ('Earn a commission on each lead referred') but publishes no revenue-share percentage, referral fee, certification requirement or cost. Integration is a sales conversation, not self-serve.
Webhooks
unknown — no public documentation of outbound webhooks.
Data export on exit
Contractual, chargeable, and undated. T&Cs: on termination 'Nory will, at the Customer's cost, provide... an export of the Customer's Data in a commonly used format.' No defined retrieval window in days, no self-serve bulk export documented. Separately, the customer 'owns the intellectual property rights in any data... submitted', but Nory reserves a 'perpetual, irrevocable, royalty-free right to copy and publish de-identified data' and owns all platform enhancements derived from use.
Notes
Complaint mining failed and is reported as empty rather than fabricated: G2 (https://www.g2.com/products/nory/reviews) returned 403, Capterra has no matching Nory listing at the URLs tried, TrustRadius/GetApp returned 404, Trustpilot returned 403, and Reddit is unfetchable from this environment; the WebSearch budget for the session was exhausted before review mining. Treat 'no recurring complaints found' as 'not collected', NOT as 'none exist'. A follow-up pass with working review-site access is required before any competitive claim about Nory's operator satisfaction. Also note Nory's help centre is public and reasonably deep, which partly compensates for the absence of developer docs — but it documents end-user workflows, not integration contracts.

Capabilities

Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.

Menu, modifiers & pricing engine

No

Supports modifier groups nested at least three levels deep, each level with independent min/max selection counts and a forced-selection (required) flag.

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

B
No

A single modifier can carry different prices depending on the parent item and the selected size, configured as a matrix rather than by duplicating the modifier.

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

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

B
No

Supports fractional/sectioned modifier placement (at minimum halves, ideally quarters) with independent pricing per section. differentiator

menu-pricing-fractional-placement

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

B
No

The half-and-half pricing rule is operator-configurable among at least two of: charge the higher-priced half, average the halves, or charge each topping at a fraction of full price. differentiator

menu-pricing-half-and-half-rule

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

B
No

Supports modifier quantity tiers (light / regular / extra / double) with a configurable price multiplier per tier, distinct from adding the modifier twice.

menu-pricing-topping-quantity-tiers

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

B
No

Item base price can be defined as a grid across two variant axes (e.g. size x crust/preparation) with a per-cell price override. differentiator

menu-pricing-size-style-matrix

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

B
No

Items can define an included-modifier allowance (e.g. three toppings included) that automatically charges only for overage and credits or forbids substitutions per configuration. differentiator

menu-pricing-included-allowance

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

B
No

Supports combo/meal construction where components can be swapped with a price delta, and the system can automatically detect and convert eligible a-la-carte items in the cart into the combo price.

menu-pricing-combos

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

B
No

Upsell/suggestive-sell prompts can be configured per item and per channel (POS, kiosk, online), and the vendor reports attach-rate on those prompts. differentiator

menu-pricing-upsell-prompts

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

B
No

A single 86 action propagates automatically to POS, KDS, the vendor's own online ordering, kiosk, and connected third-party marketplaces, with a documented propagation latency.

menu-pricing-86-propagation

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

B
No

Supports per-item countdown/par counts that decrement on sale and automatically 86 the item at zero, with a scheduled auto-restore. differentiator

menu-pricing-countdown-auto-86

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

C
No

Menus, individual items, and prices can be scheduled to activate and deactivate automatically by day and time in the location's own timezone.

menu-pricing-dayparting

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

C
No

Supports distinct price books per channel (dine-in, pickup, delivery, kiosk, each third-party marketplace) including percentage-markup rules applied to a base price rather than manual per-item entry.

menu-pricing-channel-price-books

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

B
No

Supports dual pricing / cash-discount at the item level with the card price displayed as the base price, applied consistently across POS, kiosk, and online ordering, and printed on the receipt. differentiator

menu-pricing-dual-pricing

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

B
No

Menu changes can be staged as an effective-dated version, previewed before publish, and rolled back to a prior version after publish. differentiator

menu-pricing-versioning-effective-dates

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

B
Partial

Supports a central corporate menu template pushed to locations with field-level governance controlling which attributes a location may override. differentiator

menu-pricing-franchise-hierarchy

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

D
No

Stores allergen flags and nutrition values per item and publishes them to online ordering and third-party menus, and can derive nutrition from linked recipe components rather than manual entry.

menu-pricing-allergen-nutrition

`allergen`, `nutrition`, `calorie` and `traceability` each occur 0 times across the 127 help.nory.ai articles and 0 times in the API spec. The product surface that would carry it is the Compliance Assistant, and its own article enumerates what the rules engine covers - 'Max weekly/daily hours. Rest breaks during shifts. Days of rest and minimum time between shifts. Young workers work limits. Minimum wage, including age bands.' Every one is a workforce rule; allergens are not in the list, and neither is any menu attribute. Nory also has no publishing path to online ordering or third-party menus: 'Nory links directly to your EPOS system' and consumes 'the restaurants net sales figure' from it. THE POISON, published because it is the trap here: `allergen` does occur 9 times on www.nory.ai, and the 6 that read as product claims are all in one blog post about 'an agentic AI system' in the abstract ('the technology checks allergen data every time a menu changes'), with the remaining 3 in a kitchen-audit post and two podcast transcripts. Nothing in the help centre or the spec corroborates it as shipped Nory functionality. https://help.nory.ai/en/articles/15617486-compliance-assistant-for-the-uk-and-ireland · retrieved 2026-09-10

B
Yes

Menu items and modifiers can be linked to recipes/bills of materials so that a sale depletes theoretical inventory and yields item-level theoretical food cost. differentiator

menu-pricing-recipe-linkage

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

B
No

Pushes menus to third-party marketplaces through a certified direct integration (not scraping or a menu-management middleman) and surfaces per-item sync status and rejection errors to the operator.

menu-pricing-3p-menu-push

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

B
No

Supports rule-based dynamic pricing where item price varies automatically by time, demand, or channel, with configurable floor/ceiling guardrails.

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

C

Payments & money movement

No

The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator

payments-processor-choice

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

B
No

Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator

payments-published-rates

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

B
No

Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator

payments-dual-pricing

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

B
No

Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator

payments-surcharge-guardrails

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

B
No

All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.

payments-emv-nfc

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

B
No

Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator

payments-softpos-tap-to-pay

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

B
No

Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.

payments-pay-at-table

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

B
No

Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator

payments-qr-guest-pay

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

B
No

Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.

payments-tip-adjust

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

C
Yes

Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator

payments-tip-pooling

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

B
No

Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator

payments-offline-store-and-forward

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

B
No

Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator

payments-offline-decline-liability

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

B
No

First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.

payments-gift-cards

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

B
No

House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.

payments-house-accounts

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

B
No

A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.

payments-split-tender

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

B
No

Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.

payments-refund-void-controls

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

B
No

In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator

payments-chargeback-tooling

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

B
No

Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator

payments-card-on-file

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

B
No

Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator

payments-payout-timing

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

C
No

A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator

payments-multi-entity-routing

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

B
No

Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.

payments-p2pe-pci4

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

B

Kitchen & production

No

Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.

kitchen-station-routing

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

B
No

An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.

kitchen-expo-consolidation

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

B
No

Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator

kitchen-course-firing

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

B
No

Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator

kitchen-prep-time-pacing

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

B
No

Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator

kitchen-order-throttling

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

B
No

Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator

kitchen-channel-pause-propagation

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

B
No

Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator

kitchen-order-ready-callback

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

B
No

KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.

kitchen-bump-bar-hardware

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

B
No

An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.

kitchen-all-day-counts

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

B
No

Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.

kitchen-sla-alerts

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

B
No

If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator

kitchen-printer-fallback

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

B
No

KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator

kitchen-offline-operation

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

B
No

Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator

kitchen-item-build-screens

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

C
No

Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator

kitchen-pizza-fractional-display

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

B
No

A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.

kitchen-recall-refire

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

B
No

Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator

kitchen-order-modification-alerts

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

B
No

Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator

kitchen-guest-ready-notification

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

B
Partial

Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.

kitchen-waste-logging

Waste 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

D
No

Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.

kitchen-speed-of-service-reporting

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

C
Partial

Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.

kitchen-prep-forecasting

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

D

Guest data, loyalty & marketing

No

Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.

guest-loyalty-unified-profile

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

C
No

Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator

guest-loyalty-thirdparty-identity-attach

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

B
No

Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.

guest-loyalty-accrual-models

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

B
No

Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator

guest-loyalty-tiers

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

B
No

Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator

guest-loyalty-offline-behavior

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

B
No

Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator

guest-loyalty-offer-stacking-rules

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

B
No

Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator

guest-loyalty-targeted-offers

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

B
No

Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator

guest-loyalty-rfm-segmentation

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

B
No

Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.

guest-loyalty-lifecycle-automation

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

B
No

Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator

guest-loyalty-native-email-sms

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

C
No

Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.

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

B
No

Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator

guest-loyalty-campaign-attribution

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

B
No

Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator

guest-loyalty-data-export-portability

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

B
No

Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator

guest-loyalty-cdp-event-api

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

A
Partial

Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator

guest-loyalty-review-capture-routing

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

D
No

Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.

guest-loyalty-referral-program

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

B
No

Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator

guest-loyalty-wallet-pass

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

B
No

Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.

guest-loyalty-privacy-rights-tooling

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

B
No

Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.

guest-loyalty-redemption-fraud-controls

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

B
No

Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator

guest-loyalty-ai-offer-recommendation

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

B
No

Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.

guest-loyalty-stored-value-gift

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

B

Labor & workforce

Partial

Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.

labor-clock-in-at-pos

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

B
No

Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator

labor-photo-punch-verification

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

B
Yes

Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.

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

B
No

Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator

labor-offline-time-punch

Supported Devices & Technical Requirements (updated 2026-03-10) states the rule twice, once in prose and once as a closed table. Prose: 'Nory is a cloud-based platform. An active internet connection is required at all times for all Nory apps and web access. The apps do not support offline mode.' Table: the Summary Table's four columns are the Employee App, Kiosk App, Management App and Web browser - every client the article's own sections 1 and 2 define - and its 'Internet required' row reads 'Always Always Always Always'. Clocking in runs through exactly two of those (settings article 14487078: 'Nory Team App - Mobile clock-in with geofencing' or 'Nory Kiosk App - Shared device with 4-digit employee codes'), and both are 'Always'. THE INTERNAL CONTRADICTION, resolved rather than hidden: the same article's FAQ 1 lists 'offline data caching' among features 'only available through the native mobile apps' as against a mobile browser. That phrase is the whole of it - no offline punch behaviour, no reconnect reconciliation and no duplicate handling is described anywhere in the corpus, `time punch` occurs 0 times, and this claim requires the behaviour to be documented. https://help.nory.ai/en/articles/14018489-supported-devices-technical-requirements · retrieved 2026-09-10

B
Partial

Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.

labor-granular-rbac

'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

D
Yes

Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.

labor-manager-override-audit

'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

B
Yes

Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator

labor-native-scheduling

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

B
Yes

Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator

labor-demand-labor-forecast

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

B
Yes

Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator

labor-realtime-labor-percent

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

B
Partial

Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator

labor-overtime-prevention

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

D
Partial

Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator

labor-break-compliance-by-state

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

C
Partial

Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.

labor-fair-workweek-support

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

B
Partial

Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.

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

B
Yes

Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.

labor-tip-pooling-rules

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

C
Partial

Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.

labor-tip-distribution-audit-trail

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

D
No

Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator

labor-qualified-tips-w2-reporting

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

E
Partial

Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator

labor-native-payroll

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

C
Partial

Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).

labor-payroll-export-formats

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

D
Yes

Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator

labor-shift-swap-workflow

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

B
No

Provides digital new-hire onboarding that collects W-4 and I-9 documentation and supports E-Verify submission.

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

E
Partial

Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator

labor-server-performance-metrics

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

D

Inventory, purchasing & cost control

Yes

Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.

inventory-recipe-bom-costing

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

D
Partial

Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.

inventory-unit-conversion-yields

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

B
Yes

Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator

inventory-theoretical-vs-actual

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

B
Partial

Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator

inventory-realtime-depletion

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

C
No

Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator

inventory-86-auto-sync

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

B
Partial

Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.

inventory-count-modes

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

D
Partial

Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.

inventory-mobile-count-offline

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

B
Partial

Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator

inventory-vendor-catalogs-edi

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

C
Yes

Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator

inventory-invoice-ocr

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

B
Partial

Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator

inventory-price-change-alerts

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

B
Partial

Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator

inventory-par-auto-suggest

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

C
Yes

Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.

inventory-waste-logging

Waste 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

D
Yes

Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.

inventory-transfers

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

D
Yes

Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.

inventory-commissary

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

B
No

Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.

inventory-lot-traceability

`lot number`, `batch number`, `traceability`, `recall` and `serial` each occur 0 times across the 127 help articles and the API spec. The receiving flow is documented end to end and captures quantity only: 'you can click, item by item, to confirm the quantity received', after which 'Nory will generate a Good Received Note'. The nearest thing to a trace artefact is a file attachment, and the article says what it is for: 'You can attach supporting documents or photos to the goods received note- for example: - A delivery note - A photo of damaged goods - Evidence of a substituted item', kept 'to support later review and provide a clearer audit trail' - a document trail on a purchase, not a lot identifier carried through production to sales. THE POISON: `batch` occurs 120 times in the help centre and every sense checked is a batch RECIPE (a prep sub-recipe) or the 'Batch' ingredient category in the waste report, never a receiving lot. https://help.nory.ai/en/articles/12899117-how-to-receive-an-order-in-nory · retrieved 2026-09-10

B
No

Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.

inventory-shelf-life-expiry

No date is captured on stock at any point. The receive flow confirms quantity item by item and produces a Goods Received Note; no use-by or best-before field appears in it, in the counting articles, or in the API spec. `best before` occurs 0 times and `shelf life` twice, both as advice rather than a feature ('reviewing shelf-life policies'). Expiry enters the product only as a WASTE REASON after the fact - the stock-variance article asks whether waste happened because of 'Product expiry or misrotation ?' - which is a label on a loss already taken, not an expiring-soon alert. THE INSTRUMENT THAT MAKES THIS A `no` RATHER THAN A GAP: Nory demonstrably can do date-based expiring-soon alerting and does it for PEOPLE, not stock. 'Tracking Visa expiry dates in Nory' (art. 8894754) documents a stored expiry date, a two-stage alert - 'An email notification will be sent to employee and HR managers 60 days and 30 days before the expiry date' - and a list highlight. Of the 17 tokenised `expiry` hits in the help centre, that HR feature is the only one attached to a date field. https://help.nory.ai/en/articles/12899117-how-to-receive-an-order-in-nory · retrieved 2026-09-10

B
Partial

Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.

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

B
Partial

Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.

inventory-cogs-gl-export

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

D
Yes

Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator

inventory-native-not-partner

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

B
Yes

Joins recipe cost to actual item sales mix to report contribution margin per menu item, and flags items whose margin fell below a configured threshold after ingredient cost changes. differentiator

inventory-menu-margin-linkage

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

B

Reporting, BI & data access

Yes

Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.

reporting-realtime-dashboard

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

D
No

Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.

reporting-eod-closeout

'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

B
Partial

Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.

reporting-pmix-modifier-level

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

D
No

Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.

reporting-comps-voids-audit

Nory never receives the transactions this report would be built from. 'Sales and forecasts' states what crosses the boundary: '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.' A net figure per period carries no line, no tender, no employee and no reason code, so comps, voids, discounts and price overrides cannot be attributed to the employee who applied them or the manager who approved them. Consistent with the vocabulary: `void` and `comp` each occur 0 times in the 127 help articles, against `waste` and `inventory` in the hundreds as controls. The record's own scope_overrides already retire order-capture as a settled non-surface for Nory; this is the reporting consequence of the same fact. https://help.nory.ai/en/articles/7845382-sales-and-forecasts · retrieved 2026-09-10

B
No

Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.

reporting-cash-over-short

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

B
Yes

Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.

reporting-labor-productivity

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

D
No

Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator

reporting-server-scorecards

The labour insights screen enumerates its own metric set and it is a closed toggle: 'By clicking the Hours label under Sales, you can toggle between several key performance metrics: Hours SPLH OPLH Cost COL %'. All five are location-level labour-efficiency ratios; none is per-employee, and Nory's recommendation confirms the grain - 'Nory recommends using SPLH (Sales Per Labour Hour) as your primary week-on-week performance metric.' The claim's four named measures are absent as vocabulary too: `items per check`, `attachment rate` and `per server` occur 0 times across the 127 help articles, 332 www pages and the API spec, and `average check` occurs once in the help centre. The structural reason is the same one behind comps/voids: Nory ingests a net sales figure from the EPOS, not per-check detail with a server on it. https://help.nory.ai/en/articles/7669134-tracking-and-driving-your-restaurants-labour-performance · retrieved 2026-09-10

B
Partial

Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator

reporting-channel-profitability

'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

B
Yes

Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator

reporting-multiloc-drilldown

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

B
No

Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator

reporting-custom-report-builder

`report builder` and `custom report` each occur 0 times across the 127 help articles, the 332 www pages and the API spec. What Nory ships is a fixed set of named reports, each with its own definitions article - the Management Report, the Stock Reconciliation Report, the Accounted Waste dashboard, labour insights, inventory insights - and the documented flexibility inside them is filtering and view switching, not dimension and measure selection: the labour screen offers a daily/weekly/monthly view and a five-value metric toggle, and the inventory screens offer category filters. No article describes choosing dimensions, choosing measures, or saving a result. Nothing in the API spec exposes a report or query resource either; its 20 paths are auth, branches, brands, integration, inventory, punch, settings and templates. https://help.nory.ai/en/articles/11728106-management-report-key-definitions-explained · retrieved 2026-09-10

B
No

Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.

reporting-scheduled-delivery

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

B
Partial

Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator

reporting-raw-warehouse-export

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

B
No

Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator

reporting-public-api

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. || 321st: NOTE ADDITION (value unchanged; flag for review): the existing note calls api.nory.ai/swagger.json "the only API Nory publishes" (SUPERSEDED). That is no longer true: api.prod.nory.ai (production) serves "Nory Public API" v0.1.0, description "Public API for partners integrating with Nory ... V0 is currently in limited preview", paths /health, /api/v1/employees (GET, POST), /api/v1/employees/{employee_id}, /api/v1/locations, /api/v1/positions (https://api.prod.nory.ai/openapi.json). The overview says it "gives partners access to workforce data for their brand". It still has no order, payment or menu resource, and keys are "provisioned by Nory - there is no self-serve portal in V0" (https://api.prod.nory.ai/developers/getting-started), so both failing limbs of the no still hold against the second spec. Retrieved 2026-09-17. https://api.nory.ai/swagger.json · retrieved 2026-09-17 adversarially verified

A
No

Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator

reporting-webhooks

`webhook` occurs 0 times in the 127 help articles, 0 times across 332 www pages and 0 times in the published API spec. The spec is Swagger 2.0, 20 paths and 8 schemas, and every path is a request/response REST operation - auth/token, auth/refreshToken, branches, brands, integration, six inventory paths, punch, settings/customHolidays and five templates paths - with no callbacks block, no subscription resource and no event catalogue. Nory would also have nothing to emit for this claim's subject: it consumes a net sales figure from the operator's EPOS rather than seeing order or payment lifecycle events. TWO CAVEATS RECORDED RATHER THAN BURIED: the spec is titled 'Nory Middleware - Sandbox Environment' and may not be the whole production contract, and it declares `additionalProperties: false` ZERO times, so it is a floor for absences and never a ceiling. The verdict rests on the corpus-wide zero, not on the spec alone. https://api.nory.ai/swagger.json · retrieved 2026-09-10

B
Unknown

API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator

reporting-api-not-upcharged

CLAIM: API and raw-data access included in the standard subscription, not gated behind per-location fee, revenue share or enterprise-only contract. VERDICT: held unknown. NEW SURFACES (q321): crt.sh %.nory.ai lists 36 names; each probed at / and 11 doc paths (probe.txt). Live: api.prod.nory.ai (PRODUCTION, uvicorn) serves an anonymous OpenAPI 3 spec at /openapi.json titled "Nory Public API" v0.1.0 plus partner guides at /developers/{overview,getting-started,authentication,pagination,errors,rate-limits}; get.nory.ai is a Vite landing site (7 routes, FAQ bundle, no price); staging.nory.ai is a Webflow staging copy (316 sitemap URLs, none a pricing page; www.nory.ai sitemap now 334, the 2 additions a blog post and a whitepaper, no pricing page); onboarding/start.nory.ai are email-login shells; bento 401, cdn/mixpanel 403, designsystem 503. EVIDENCE: The Public API guides state access terms but no price: "Prerequisites: An active Nory partnership with API access enabled" and "API keys are provisioned by Nory - there is no self-serve portal in V0. Contact your Nory account manager or integrations team to request a key" (https://api.prod.nory.ai/developers/getting-started); "Keys grant read access by default; write access (currently POST /employees) is enabled per integration - contact Nory to request it" and "V0 is in limited preview" (https://api.prod.nory.ai/developers/overview). Tokenised controls over the 6 guide pages + openapi.json: price*/fee*/cost*/charg*/billing/subscription*/plan/tier*/enterprise/paid/free/commercial = 0 hits; the only hits are contract/contracted/contractedHours (employee-contract fields, poison). So access is sales-gated (account manager, per-integration enablement) but neither a surcharge nor inclusion is stated. RETIRED PRICE LIST FOUND (Wayback CDX): nory.ai/pricing/ was a real price page with 200 captures 2022-06-27..2024-12-07 and a 404 by 2025-04-05 (www.nory.ai/pricing now 301s to /book-a-chat). The 2024-12-07 capture (https://web.archive.org/web/20241207203914/https://nory.ai/pricing/) reads: "SMALL & MEDIUM BUSINESSES | Pricing for businesses with 2 - 25 locations. | 329€ | 349$ | 299£ | /month | Per location, billed monthly"; "Enterprise BUSINESSES | Custom pricing for businesses with 25+ locations"; "TAKE A BITE | Don't want to take on the full Nory OS? Then pick what you need most" with INVENTORY 179£, WORKFORCE 120£, central production unit 279£ per location/month; "ALL OUR PLANS INCLUDE ... FULLY INTEGRATED STACK"; FAQ "We do not charge for additional integrations." The retired page predates the Public API (API, raw data and export occur 0 times in the 2023-03-21 and 2024 captures); "additional integrations" are POS/supplier/accounting connectors, not API or raw-data access, and a page retired in 2025 cannot bind current terms (merge policy). Not scored no: "partnership with API access enabled" is gating, not a proven fee or enterprise-only contract. Retrieved 2026-09-17. || 329th: MERGE HOLD (proposed no/B, held unknown): The 'at the Customer's cost' export is a TERMINATION-exit clause, not in-term raw-data access (the same docs say API keys grant read access by default). API access being enabled per partnership on request is provisioning, not a stated per-location fee, revenue share or enterprise-only contract; Nory's terms never use 'API' in a commercial clause, and 'integration' in clause 6 most naturally means Nory-built POS/payroll integrations. A provisioning gate is not a fee (328th agilysys precedent: a licence key is not a fee). The Starter/Scale/Enterprise package matrix is recorded; its feature content is unpublished. PROPOSAL AS WRITTEN: 329th: MOVED TO NO on a previously unread vendor legal document. SURFACE (new): https://www.nory.ai/legal/terms-and-conditions - "Nory Standard Terms & Conditions Last updated July 2026" (Hospitality Growth Services Limited, Irish company 650310), 65,978 chars stripped, 10,276 tokens, incl. Schedule 1 SLA and Schedule 2 DPA; a second, older version is also live at https://www.nory.ai/legal/terms-conditions ('Last updated August 05, 2025', 49,137 chars). No prior pass had opened either; the 321st note's "a page retired in 2025 cannot bind current terms" is now moot because current terms exist. EVIDENCE, on each half of the claim. (1) RAW-DATA ACCESS IS EXPLICITLY CHARGED FOR: "Upon termination of the Agreement... Following termination, Nory will, AT THE CUSTOMER'S COST, provide the Customer an export of the Customer's Data in a commonly used format. Unless prohibited by law or this Agreement, Customer will have thirty (30) days from the effective termination date to export Customer Data" (July 2026 version; the August 2025 version says the same: "Nory will, at the Customer's cost, provide the Customer an export of the Customer's Data in a commonly used format"). The vendor's own agreement therefore prices the raw-data extract rather than including it. (2) API ACCESS IS NOT A SUBSCRIPTION ENTITLEMENT BUT A PER-PARTNERSHIP, PER-INTEGRATION ENABLEMENT: "Prerequisites: An active Nory partnership with API access enabled" and "API keys are provisioned by Nory - there is no self-serve portal in V0. Contact your Nory account manager or integrations team to request a key" (https://api.prod.nory.ai/developers/getting-started, re-fetched 2026-09-18 at 200 and byte-identical to the 321st, as are all six /developers guides and /openapi.json at 21,695 B); "Keys grant read access by default; write access (currently POST /employees) is enabled per integration - contact Nory to request it" and "V0 is in limited preview" (/developers/overview). (3) THE AGREEMENT MAKES EVERY ENTITLEMENT AN ORDER-FORM LINE ITEM THAT COSTS MORE: "The Customer is entitled to use the components and integrations purchased by the Customer as specified in the order form. If the Customer wishes to add further components or integrations at any time, the parties shall agree to an amended or new order form"; "Each time a new location or integration is added, the fees payable by the Customer under the applicable order form shall increase"; "If a component or integration is cancelled and then subsequently reactivated, the implementation fee shall be due at the time of reactivation"; "the terms of the order form shall prevail as to pricing, product and service scope". BOUND/CONTROLS: both Terms versions read in full; tokenised controls over them give raw=0, surcharg*=0, per-location=0, upcharge=0, revenue=2 ("revenue management", the Chargebee subprocessor line, poison), share=1 (not revenue share), api=3+1 of which every hit is poison - "API data files" in the confidentiality definition, and the subprocessor table entries "API Deck - API gateway for financial system integrations" and "Twilio - Programmable messaging (SMS, email, etc.) APIs" - i.e. the Agreement never grants or prices customer API access by name, which is why the order-form clauses above are the operative ones. Also re-measured: www.nory.ai 334-URL sitemap still has no pricing page (/pricing 301s to /book-a-chat; /plans, /msa, /sla 404 against a verified nonsense control), and the 127-article help.nory.ai KB (re-censused today via its 22 collection pages) carries no API or data-export pricing article. RESIDUAL RISK, stated: the word "integration" in Nory's vocabulary usually denotes a POS/supplier/accounting connector, so clause 6 is not verbatim about the Public API; the raw-data half of the claim, however, is refuted verbatim by the export-at-cost clause. Retrieved 2026-09-18. adversarially verified

F
Unknown

Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator

reporting-tier-paywall

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. RE-MEASURED 2026-09-10 and still unresolvable, now against a bounded manifest rather than a single 301. www.nory.ai publishes a 332-entry sitemap and all 332 pages were fetched at 200; NOT ONE IS A PRICING PAGE. The plan vocabulary is absent with it: `enterprise plan` occurs 0 times, `tier` 5 times and `add-on` 3 times across those 332 pages, none of them naming a Nory SKU, and no plan, edition or package name appears anywhere in the 127 help.nory.ai articles either. What the site has instead is a conversion CTA repeated site-wide - `Book a chat` occurs 3,809 times across the sitemap, almost all of it navigation chrome - plus an ROI calculator. The published API spec (api.nory.ai/swagger.json, byte-identical at middleware.nory.ai) carries no commercial terms at all; its `info.description` is the two-character string 'Nory '. So there is no published entry-level paid plan, and the claim asks what that plan contains. Note that several of the reports this claim names are separately settled against Nory on capability grounds rather than packaging - see reporting-comps-voids-audit and reporting-custom-report-builder, both `no` as of this pass. || 321st: CLAIM: labor vs sales, PMIX, comps/voids audit, multi-location comparison on the entry-level paid plan. VERDICT: held unknown. RETIRED PRICE LIST FOUND (Wayback CDX): nory.ai/pricing/ was a real price page with 200 captures 2022-06-27..2024-12-07 and a 404 by 2025-04-05 (www.nory.ai/pricing now 301s to /book-a-chat). The 2024-12-07 capture (https://web.archive.org/web/20241207203914/https://nory.ai/pricing/) reads: "SMALL & MEDIUM BUSINESSES | Pricing for businesses with 2 - 25 locations. | 329€ | 349$ | 299£ | /month | Per location, billed monthly"; "Enterprise BUSINESSES | Custom pricing for businesses with 25+ locations"; "TAKE A BITE | Don't want to take on the full Nory OS? Then pick what you need most" with INVENTORY 179£, WORKFORCE 120£, central production unit 279£ per location/month; "ALL OUR PLANS INCLUDE ... FULLY INTEGRATED STACK"; FAQ "We do not charge for additional integrations." The full-OS SMB plan listed Business Intelligence items incl. "Live P&L reporting | Aggregate your performance data in real-time: Sales - (COGs + Labour) = Operating Profit ... for all venues" and "Multi-region & franchise reporting", with no separate analytics SKU. BUT the cheapest paid offerings were the stand-alone "Take a bite" modules (Workforce 120£, Inventory 179£), whose BI content is not stated, so the ENTRY-LEVEL plan's reporting is not established; comps/voids audit and PMIX are not named; and the page is retired (404 since 2025, no current price list on www.nory.ai 334-URL sitemap, staging.nory.ai 316, get.nory.ai 7 routes). A retired copy may carry at most partial and here does not satisfy the entry-level conjunct. Retrieved 2026-09-17. || 329th: 329th: NEW SURFACE, and it FALSIFIES THE OLD NOTE'S CENTRAL FINDING. Nory DOES publish named plan tiers - not on a pricing page, but inside Schedule 1 (Service Level Agreement) of its current Standard Terms & Conditions, which no prior pass had opened. https://www.nory.ai/legal/terms-and-conditions ('Nory Standard Terms & Conditions Last updated July 2026', 65,978 chars of stripped text, 10,276 tokens) sets out a three-package support matrix: "Nory's current standard response times are: Severity | Description | Starter Package | Scale Package | Enterprise Package", with Urgent (P0) 120 Minutes / <24 Hours on Starter, 90 Minutes / <18 Hours on Scale, 60 Minutes / <12 Hours on Enterprise (and P1/P2/P3 rows likewise). So the entry-level paid plan has a published NAME - the Starter Package - and the old note's "no plan, tier, edition or SKU name appears anywhere" is wrong as of this pass. What is STILL unpublished is the only thing this claim asks about: the FEATURE content of each package. The three packages are differentiated in the published terms solely by support response and resolution times; no reporting, analytics or module entitlement is attached to any of them, and the Agreement pushes scope to the private contract - "The Customer is entitled to use the components and integrations purchased by the Customer as specified in the order form" and "To the extent there is any inconsistency between this Agreement and any order form, the terms of the order form shall prevail as to pricing, product and service scope." A SECOND, OLDER VERSION of the same document is also live and has NO package table: https://www.nory.ai/legal/terms-conditions ('Last updated August 05, 2025', 49,137 chars) - so the packages are a 2026 addition. Site-side re-measured 2026-09-18: www.nory.ai/sitemap.xml now lists 334 URLs; /pricing still 301s to /book-a-chat (followed with -L: final URL https://www.nory.ai/book-a-chat) and /plans, /terms, /legal, /msa, /sla, /security all 404 with an identical 63,480-byte 404 body (a nonsense control, /zzqnonsense-xyz, returns the same body, so the 404 is genuine and not a soft-200). The site enumerates four purchasable MODULES in its nav and on /product - Business Intelligence, Inventory, Workforce, Payroll - plus six Assistants, with BI described as the analytics module ("Business Intelligence: Run your P&L. Don't read it... Nory updates revenue, GP and labour across every site, every 15 minutes", https://www.nory.ai/product/business-intelligence); no page states which package or module bundle includes it. help.nory.ai re-censused via its 22 collection pages: 127 articles (126 on disk from the 08-08 pass; the only 2 genuinely new are 16889256-invoicing-assistant-overview and 16902364-how-to-edit-your-sales-forecast, both fetched, both with zero plan/tier/price vocabulary; help.nory.ai/sitemap.xml now 404s, so the collection pages are the census route). CONTROLS, tokenised, over both Terms versions: tier*=0, edition*=0, sku=0, plans=0, surcharg*=0, per-location=0, upcharge=0; plan=2 (both "implementation plan", poison), price*=3 (all in "then list prices" / "fixed price basis" / pricing-prevails, poison for feature packaging). Held unknown: the entry-level plan now has a name but no published contents. Retrieved 2026-09-18. adversarially verified

F
No

Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator

reporting-history-retention

This is a documentation claim and no document meets it. `retention` returns exactly 1 tokenised hit across the 127 help articles and it is about TRAINING - the train-the-trainer article listing 'Low retention' as a problem with large group sessions. No article, legal page or spec field states a historical window for transaction-level detail, states what happens to older data, or mentions an archive-retrieval charge. What the corpus does document is the opposite end: the labour screen's comparison controls are week-on-week and 'Use the monthly view for LFL comparisons', and the counting articles describe weekly or monthly count cycles, with no stated horizon at all. A silence about retention cannot be read as 24 months, so the claim is not met. https://www.nory.ai/legal/terms-privacy · retrieved 2026-09-10

B
Partial

Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator

reporting-anomaly-alerts

The 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

D
Partial

Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.

reporting-nl-query

A named natural-language assistant exists, is shipped, and is documented - but on one module rather than on sales and labour data. 'Ask Nory' appears in the help centre as a working control inside the reviews product: 'Click on Ask Nory and share the improvement ideas with the in-store teams!' (art. 12959993). The Customer Reviews Assistant page describes what it does - 'Our AI analyses every review across all platforms to identify patterns, detect sentiment shifts, and surface operational issues. Ask Nory then summarises key trends and provides actionable recommendations.' - and says the analysis reaches operational data: 'Nory's AI connects to your operational data (labour, inventory, processes) and tells you why they're unhappy and exactly how to fix it.' What is NOT documented is the claim's core: an ad-hoc question against the operator's own sales and labour data returning a figure or chart. `natural language` occurs once across 332 www pages and 0 times in the help centre. The other five assistants (Scheduling, Ordering, Compliance, Payroll, Invoicing) are workflow automations, not a query surface, and 'Next time you need to know how much chicken to order, just ask Nory' is a closing line on a competitor-comparison page, not documented behaviour. https://www.nory.ai/agentic-ai/customer-reviews-assistant · retrieved 2026-09-10

B
No

Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator

reporting-guest-cohorts

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

B
Yes

Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator

reporting-sales-forecast

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

B
Partial

Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.

reporting-tip-tax-compliance

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

D

Multi-location, franchise & enterprise governance

Partial

Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.

multi-location-org-hierarchy

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

D
Partial

A corporate-level menu can be authored once and published to a chosen set of locations in a single action, with a publish/version history showing what was pushed, when, and by whom.

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

D
No

Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator

multi-location-local-override-policy

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

B
No

Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.

multi-location-price-zones

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

B
No

Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator

multi-location-scheduled-publish

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

B
No

A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator

multi-location-new-store-template

`clone` occurs 0 times across the 127 help articles, 332 www pages and the API spec, and no article describes provisioning a location by copying another. 'Your settings in Nory' is the go-live configuration guide and it is a per-location checklist by construction: 'The previous settings covered are all group wide. The settings under Locations are all specific to each location and need to be set for each location.' Eight location-level sections follow, each set individually. No expected time-to-open is published anywhere. THE POISON: `template` occurs 39 times in the help centre and the API spec has five /templates paths, but both are a different object - stock-COUNT templates ('To save time in your stock take, set up a template !', art. 6607628, with a dedicated article at 10490778) and schedule templates. The spec's template operations are scoped to a branch that already exists: 'Create Template for the branch', 'Get Templates for the branch', 'Apply Template', 'Request Template Recommendation'. https://help.nory.ai/en/articles/14487078-your-settings-in-nory · retrieved 2026-09-10

B
Partial

The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator

multi-location-corp-vs-franchisee-roles

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

B
No

Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator

multi-location-royalty-calculation

`royalty` occurs 0 times across the 127 help articles and the API spec. Nory has a franchise concept and the settings article defines exactly what it does: section 4, 'Location & Franchise Groups', exists because 'Location groups can help you to group locations together on the insights pages. This enables you to view sales, labour, and waste data across multiple locations at once.' That is a reporting grouping, and the article's how-to is limited to creating, naming and editing a group's membership. No fee schedule, no royalty basis, and no gross-versus-net-of-discounts configuration appears anywhere - which is consistent with Nory receiving only 'the restaurants net sales figure (Gross sales - VAT - Service charge = Net sales)' from the EPOS, a figure that cannot be re-based on discounts or comps because it never carried them. https://help.nory.ai/en/articles/14487078-your-settings-in-nory · retrieved 2026-09-10

B
No

Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.

multi-location-royalty-collection

Conditional on a calculation that does not exist, and separately absent on its own terms: `ACH` and `direct debit` each occur 0 times across the 127 help articles, 332 www pages and the API spec, and no franchisee-visible statement of charges is documented. Nory's only documented money-movement surfaces run the other way and are not royalties - supplier Bills Payable pushed to Xero ('Currently you can create Bills Payable in Xero through Nory', art. 9091692), payroll pay runs, and Nory Capital, which is a financing product ('Access up to £2M in restaurant financing in 24 hours'). Franchise support in the product is the insights grouping described under multi-location-royalty-calculation. https://help.nory.ai/en/articles/14487078-your-settings-in-nory · retrieved 2026-09-10

B
Yes

Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.

multi-location-consolidated-reporting

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

D
Partial

Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator

multi-location-normalized-item-rollup

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

B
No

Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.

multi-location-cross-location-giftcard

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

B
No

A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.

multi-location-cross-location-loyalty

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

B
No

A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator

multi-location-multi-brand

The claim's subject is a terminal, and Nory has none. Its three native apps are enumerated with their jobs - a three-column table whose Description cells read 'Employee self-service: clock in/out, schedules, availability' (Nory Team), 'In-store kiosk app for staff clocking in/out operations' (Nory Kiosk) and 'Inventory management, ordering, transfers' (Nory IM) - plus a browser dashboard. None rings sales, prints a guest receipt or opens a drawer, so separate menus, receipts and branding on shared hardware is not a surface Nory has. `virtual brand` occurs 0 times across all three corpora. Nory does model a brand above locations (the API spec has a /brands/brand path and the settings article groups locations), but that is an org hierarchy for reporting, not two concepts trading through one drawer. Consistent with the record's existing scope_overrides, which retire order-capture for this product. https://help.nory.ai/en/articles/14018489-supported-devices-technical-requirements · retrieved 2026-09-10

B
No

Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.

multi-location-multi-tax-jurisdiction

Nory's tax handling is purchase-side only and is not per-location. VAT lives on inventory item CATEGORIES mapped to accounting nominal codes: 'These codes help group items by type and apply the correct VAT rate. For instance, code 111 (Drinks) often has a VAT rate of 23%, whereas fresh food may be 0%', and the rule is uniformity, not variation - 'Every category in Nory should have one consistent VAT type (either 0% or 23%), which should match the VAT type assigned to its corresponding nominal code in Xero.' On the sales side Nory computes no tax at all; it receives a figure with tax already removed - 'Nory takes the restaurants net sales figure (Gross sales - VAT - Service charge = Net sales)'. This also answers the open question the prior pass left: the doubt was whether 'Your settings in Nory' is a complete enumeration, and the verdict no longer depends on that, because the Xero article positively describes the only VAT mechanism Nory has and it is a two-value purchase attribute rather than a jurisdiction engine with per-location rates or exemptions. https://help.nory.ai/en/articles/9091692-nory-x-xero-accounting-integration · retrieved 2026-09-10

B
Partial

Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator

multi-location-config-audit-log

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

B
No

Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator

multi-location-enterprise-api

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

A
Partial

Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.

multi-location-central-labor-policy

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

D

Hardware & physical footprint

Yes

The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator

hardware-commodity-devices

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

B
Partial

Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.

hardware-os-platforms

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

E
No

Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.

hardware-handheld-purpose-built

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

B
No

The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator

hardware-handheld-battery-swap

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

B
No

Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.

hardware-handheld-lte

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

B
No

Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).

hardware-offline-mode

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

B
No

Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.

hardware-kds

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

B
No

Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator

hardware-kiosk

'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

B
No

Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.

hardware-drive-thru

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

B
No

Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.

hardware-printer-compatibility

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

B
No

Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.

hardware-peripherals

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

B
No

Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.

hardware-p2pe-terminal

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

B
No

Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator

hardware-tap-to-phone

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

B
No

Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator

hardware-pricing-transparency

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

C
No

Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator

hardware-ownership-vs-lease

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

B
No

Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator

hardware-usable-after-churn

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

B
No

Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator

hardware-rma-sla

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

B
Partial

Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.

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

D
No

Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator

hardware-remote-device-management

The 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

B
No

Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.

hardware-selfpour-scales

`flow meter`, `tap wall`, `pour spout`, `self-pour`, `draught` and `beverage hardware` each occur 0 times across the 127 help articles, 332 www pages and the API spec. Nory integrates no hardware of any kind: the Supported Devices article's entire hardware surface is consumer phones, tablets and browsers - 'iPhone 6s or newer, iPad (5th gen) or newer', 'Android version 7.0 (Nougat) or later', 'Chromebooks can access the Nory web app through the Chrome browser' - and the only peripheral it names is a device camera for document scanning. The claim also requires pours to post to a POS tab, and Nory is not the POS. THE POISON: `scale` returns 5 tokenised help-centre hits and every one is the magnitude sense - 'understanding your segment, scale, and operating model', 'Protect margin as sales scale', 'the scale of your waste relative to sales', 'permission boundaries that can scale across multiple teams' - not a weighing scale. https://help.nory.ai/en/articles/14018489-supported-devices-technical-requirements · retrieved 2026-09-10

B
No

Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.

hardware-callerid-integration

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

B

Integrations, API & extensibility

Partial

Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.

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

A
Unknown

API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator

extensibility-api-access-cost

CLAIM: API access included in base subscription at no additional per-location fee, surcharge or upgraded plan requirement. VERDICT: held unknown. NEW SURFACES (q321): crt.sh %.nory.ai lists 36 names; each probed at / and 11 doc paths (probe.txt). Live: api.prod.nory.ai (PRODUCTION, uvicorn) serves an anonymous OpenAPI 3 spec at /openapi.json titled "Nory Public API" v0.1.0 plus partner guides at /developers/{overview,getting-started,authentication,pagination,errors,rate-limits}; get.nory.ai is a Vite landing site (7 routes, FAQ bundle, no price); staging.nory.ai is a Webflow staging copy (316 sitemap URLs, none a pricing page; www.nory.ai sitemap now 334, the 2 additions a blog post and a whitepaper, no pricing page); onboarding/start.nory.ai are email-login shells; bento 401, cdn/mixpanel 403, designsystem 503. EVIDENCE: The Public API guides state access terms but no price: "Prerequisites: An active Nory partnership with API access enabled" and "API keys are provisioned by Nory - there is no self-serve portal in V0. Contact your Nory account manager or integrations team to request a key" (https://api.prod.nory.ai/developers/getting-started); "Keys grant read access by default; write access (currently POST /employees) is enabled per integration - contact Nory to request it" and "V0 is in limited preview" (https://api.prod.nory.ai/developers/overview). Tokenised controls over the 6 guide pages + openapi.json: price*/fee*/cost*/charg*/billing/subscription*/plan/tier*/enterprise/paid/free/commercial = 0 hits; the only hits are contract/contracted/contractedHours (employee-contract fields, poison). So access is sales-gated (account manager, per-integration enablement) but neither a surcharge nor inclusion is stated. RETIRED PRICE LIST FOUND (Wayback CDX): nory.ai/pricing/ was a real price page with 200 captures 2022-06-27..2024-12-07 and a 404 by 2025-04-05 (www.nory.ai/pricing now 301s to /book-a-chat). The 2024-12-07 capture (https://web.archive.org/web/20241207203914/https://nory.ai/pricing/) reads: "SMALL & MEDIUM BUSINESSES | Pricing for businesses with 2 - 25 locations. | 329€ | 349$ | 299£ | /month | Per location, billed monthly"; "Enterprise BUSINESSES | Custom pricing for businesses with 25+ locations"; "TAKE A BITE | Don't want to take on the full Nory OS? Then pick what you need most" with INVENTORY 179£, WORKFORCE 120£, central production unit 279£ per location/month; "ALL OUR PLANS INCLUDE ... FULLY INTEGRATED STACK"; FAQ "We do not charge for additional integrations." No API is named on any capture of the retired price list, so neither it nor the current guides say whether API access costs extra. Retrieved 2026-09-17. || 329th: MERGE HOLD (proposed no/B, held unknown): Same shortfall: no Nory document states a fee, surcharge or plan requirement for API access. 'Contact your account manager for a key' and 'limited preview' are provisioning; the order-form clause prices 'components and integrations' without ever naming the API (api=3 hits, all poison). Inference on a differentiator claim; held, as cake-pos was today. PROPOSAL AS WRITTEN: 329th: MOVED TO NO on the previously unread current Standard Terms. SURFACE (new): https://www.nory.ai/legal/terms-and-conditions, "Nory Standard Terms & Conditions Last updated July 2026" (65,978 chars stripped, 10,276 tokens, Schedule 1 SLA + Schedule 2 DPA), with an older parallel version still live at https://www.nory.ai/legal/terms-conditions ('Last updated August 05, 2025'). EVIDENCE: the Agreement grants nothing beyond the private order form - "The Customer is entitled to use the components and integrations purchased by the Customer as specified in the order form. If the Customer wishes to add further components or integrations at any time, the parties shall agree to an amended or new order form and it shall be subject to the terms and conditions of this Agreement" - and it states the cost of adding one: "Each time a new location or integration is added, the fees payable by the Customer under the applicable order form shall increase", with "the terms of the order form shall prevail as to pricing, product and service scope" and, on renewal, "the subscription fees for the Renewal Term shall automatically increase to the then list prices" plus an annual CPI uplift. There is therefore no published base subscription that includes API access; there is an order form that prices each component. Nory's own developer guides say the same on the API side: "Prerequisites: An active Nory partnership with API access enabled"; "API keys are provisioned by Nory - there is no self-serve portal in V0. Contact your Nory account manager or integrations team to request a key" (https://api.prod.nory.ai/developers/getting-started); "Keys grant read access by default; write access (currently POST /employees) is enabled per integration - contact Nory to request it"; "V0 is in limited preview" (/developers/overview) - all re-fetched 2026-09-18 at 200, byte-identical to the 321st, alongside /openapi.json (21,695 B, "Nory Public API" v0.1.0). Access is thus contract-gated and enabled per partnership and per integration, which is exactly the "upgraded plan requirement" the claim excludes; and the published tier structure is a three-package matrix (Starter / Scale / Enterprise Package, Schedule 1 of the July 2026 terms) in which API access appears in no package's published entitlements. BOUND/CONTROLS: both Terms versions read in full; tokenised controls give surcharg*=0, per-location=0, upcharge=0, tier*=0, sku=0, raw=0; api=3 and apis=1 in each version and EVERY hit is poison - "API data files" inside the Confidential Information definition, and two subprocessor-table rows ("API Deck - API gateway for financial system integrations", "Twilio - Programmable messaging (SMS, email, etc.) APIs"). www.nory.ai's 334-URL sitemap (re-fetched today) contains no pricing page - /pricing 301s to /book-a-chat, and /plans, /terms, /legal, /msa, /sla, /security return an identical 63,480-byte 404 body that a nonsense control (/zzqnonsense-xyz) reproduces exactly - and the 127-article help.nory.ai KB (re-censused today from its 22 collection pages; only 2 new articles since the 08-08 pass) has no billing or API-pricing article. RESIDUAL RISK, stated plainly: Nory never uses the word "API" in a commercial clause, so this `no` rests on (a) the vendor documenting API access as a per-partnership/per-integration enablement rather than a subscription entitlement and (b) the Agreement's rule that adding an integration increases fees; if the owner reads "integration" as connectors only, this cell reverts to unknown with the tier names and the order-form mechanics as the new finding. Retrieved 2026-09-18. adversarially verified

F
No

The vendor publishes its partner/marketplace commercial terms (referral fee, revenue share percentage, or per-location partner fee) in public documentation.

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

B
Partial

A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator

extensibility-free-sandbox

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

A
No

Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).

extensibility-oauth-partner-apps

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

A
No

The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.

extensibility-webhooks-push

Same measurement as reporting-webhooks and the same two caveats: `webhook` is 0 across the help centre, www and the spec, and the spec's 20 paths are all request/response with no callbacks. Polling is the only documented shape. The scope point matters here: order lifecycle events are not Nory's subject at all - the record's own scope_overrides retire order-capture, delivery and digital-ordering as settled non-surfaces, and 'Sales and forecasts' (art. 7845382) says Nory takes 'the restaurants net sales figure' from the EPOS, so there is no created/modified/paid/voided/refunded stream inside Nory to push. Two addresses are not two instruments: middleware.nory.ai/swagger.json returns the byte-identical 18,020-byte file. https://api.nory.ai/swagger.json · retrieved 2026-09-10

B
No

Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator

extensibility-webhook-reliability

Conditional on a mechanism that does not exist: with `webhook` at 0 across all three corpora there is nothing to sign, retry or replay, and no signature header, retry policy or event log is documented for any Nory surface. The spec's only security definition is a bearer API key on inbound requests - 'bearerAuth', type apiKey, in header - which is request authentication, not payload signing. Recorded as `no` rather than left conditional because the claim's three components are each separately absent from the published record, not merely unmeasured. https://api.nory.ai/swagger.json · retrieved 2026-09-10

B
No

A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.

extensibility-order-injection-api

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

B
Partial

Menu items, modifiers, and prices can be written and updated via API, not just read. differentiator

extensibility-menu-write-api

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

A
No

Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator

extensibility-data-symmetry

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

A
No

API rate limits are published as specific numeric quotas with documented throttling behavior and headers.

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

A
No

The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator

extensibility-doordash-preferred

DoorDash publishes its own complete provider registry at https://merchants.doordash.com/api/partner-integrations — 64 providers, each carrying a `qualityStatus` of PREFERRED (12), CERTIFIED (47) or AT_RISK_OF_SUSPENSION (5), plus a count of how many of the eight high-quality features the provider has built. It is served anonymously and merchants.doordash.com/robots.txt permits it (Allow: / with only /cdn-cgi/ and /monitoring barred). This is what the program page means when it says the roster is tracked in real time, and it is a CENSUS rather than a floor: every provider integrated with DoorDash appears in it with a tier, so a vendor that is absent altogether is not in the programme at any tier. This vendor appears nowhere in the 64 entries, under any provider id or friendly name — checked mechanically against both fields, with the only near-misses being substring coincidences (Speedline against Lightspeed, vroom_restaurant against Restaurant365) that were read and rejected. SUPERSEDES the 2026 announcement post most of this corpus cited: that post introduces its ten names with the word `include`, which makes it a floor and never a ceiling, and reading it as a ceiling is what produced this cell's prior grade. GRADE HARMONISED TO B, 2026-09-11: this URL was first written at grade A. The adversarial pass ruled E on the principle that the rubric grades by the publisher's relationship to the SCORED vendor, and DoorDash is not that vendor. B is the settlement, for two reasons that are not preference: 39 rows already graded a DoorDash-published document B on this claim before today, and one URL on one claim cannot carry two grades; and E is unworkable, because nine of the 47 rows are `yes` on a differentiator-weight claim, which the grade floor refuses below B. B reads as the product documentation of the programme's own publisher, which is what this registry is. The dissent is recorded in verification.jsonl. https://merchants.doordash.com/api/partner-integrations · retrieved 2026-09-11

B
No

Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator

extensibility-first-party-delivery-integrations

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

E
No

The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).

extensibility-middleware-compatibility

Measured at both publishers. NORY'S OWN: `Deliverect`, `Chowly`, `Otter`, `Checkmate` and `ItsaCheckmate` each occur 0 times across the 127 help articles, 332 www pages and the API spec, and the integrations page runs the other way entirely - its POS partners are Toast, Square, Clover, Revel, PixelPoint, Oracle Micros, Epos Now, Innova, Captiva, Lightspeed, Vita Mojo, SumUp, Tevalis, Zonal and My Order Box, with not one aggregation platform among them. THE MIDDLEWARE VENDOR'S OWN: Deliverect's 1,000-article English help corpus contains `Nory` zero times when tokenised, against Lightspeed 269, Revel 144, Square 70, Epos Now 35, Clover 28 and Toast 26 as controls - and the poison is worth publishing, because a naive case-insensitive substring search returns 4 hits there and all four are the fragment `noRY` inside base64 query strings. Structurally this is settled anyway: aggregation middleware writes orders into a POS, and this record's own scope_overrides retire order-capture, delivery and digital-ordering for Nory as settled non-surfaces. https://www.nory.ai/integrations · retrieved 2026-09-10

B
Partial

Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.

extensibility-accounting-connectors

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

C
Partial

Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.

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

D
No

Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator

extensibility-bi-data-warehouse

`S3`, `SFTP`, `Snowflake`, `BigQuery`, `Redshift`, `Looker`, `Power BI` and `scheduled export` each occur 0 times across the 127 help articles, 332 www pages and the API spec, and `data warehouse` returns 2 www hits, both inside one podcast transcript where a guest describes building his own at a former employer. Every documented export is a manual, UI-bound file download - the HR export drawer, the timecard export, the Cash-and-stock report exports - and the one programmatic destination Nory documents is an accounting system, not a warehouse: 'Currently you can create Bills Payable in Xero through Nory.' The published API is a pull contract of 20 REST paths with no bulk or transaction-level extract among them. `Tableau` appears once, in a blog listing it alongside Nory as a category of tool, which is a comparison, not an integration. https://help.nory.ai/en/articles/8435424-exporting-your-hr-data · retrieved 2026-09-10

B
Partial

The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.

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

B
No

Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.

extensibility-custom-fields-scripting

`custom field` occurs 0 times across the 127 help articles, 332 www pages and the API spec, and no vendor-hosted scripting or rules-authoring surface is documented. The configurable surface is a fixed, numbered list: eight company-wide sections (Scheduling & Shifts, Time & Attendance, Labour, Location & Franchise Groups, Onboarding, Notifications, Categories, Accounting) and eight location-level ones (Branch contact information, Service category, Labour targets, Opening hours, Holidays and events, Holiday settings, Departments/Positions/Stations, Clock in). What Nory calls custom is instance creation inside those fixed types - custom shift types, custom absence types, departments, positions and stations - each added by 'click the + button in the top right corner of each tile'. The nearest thing to authored logic is the Compliance Assistant's per-location overrides, and those are bounded to toggling a supplied rule, switching it between hard and soft, or changing its threshold. https://help.nory.ai/en/articles/14487078-your-settings-in-nory · retrieved 2026-09-10

B
No

The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.

extensibility-headless-embedded

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

B
No

The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.

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

A
Partial

A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator

extensibility-data-portability-exit

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

B

Reliability, offline & operations

No

Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.

reliability-offline-order-entry

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

B
No

Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator

reliability-offline-card-auth

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

B
No

The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator

reliability-offline-decline-liability

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

B
No

Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator

reliability-lan-degraded-multi-terminal

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

B
No

The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator

reliability-local-transaction-engine

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

B
No

Kitchen display and/or kitchen printer routing continues to function while offline.

reliability-offline-kds-printing

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

B
No

The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.

reliability-printer-fallback

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

B
No

The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).

reliability-sync-conflict-handling

There is no network partition for two devices to diverge across. Supported Devices & Technical Requirements states it in prose - 'An active internet connection is required at all times for all Nory apps and web access. The apps do not support offline mode.' - and repeats it as a closed table whose 'Internet required' row reads 'Always Always Always Always' across the Employee App, Kiosk App, Management App and browser, which is every client the article defines. Every write therefore goes to the cloud synchronously, and the corpus documents no divergence handling to go with it: `conflict` and `partition` each occur 0 times across the 127 help articles and the API spec. The FAQ's single mention of 'offline data caching' in the native apps is noted in labor-offline-time-punch and describes no behaviour; it is a browser-versus-app contrast, not a partition model. Resolves the prior pass's `not determinable` by treating the document's normative statement and its table as the finding rather than the FAQ aside. https://help.nory.ai/en/articles/14018489-supported-devices-technical-requirements · retrieved 2026-09-10

B
No

The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).

reliability-offline-feature-matrix

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

E
No

A public, per-component status page exists showing current and historical incident state without a login.

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

E
No

A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator

reliability-contractual-uptime-sla

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

B
No

The vendor publishes written post-incident reports or root-cause summaries for major outages.

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

B
No

24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.

reliability-247-live-support

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

B
Partial

The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator

reliability-onsite-install

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

D
Partial

The vendor performs the initial menu build as part of onboarding rather than leaving it entirely to the operator. differentiator

reliability-menu-build-service

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

B
No

A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.

reliability-hardware-replacement-sla

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

B
No

Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.

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

B
No

The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.

reliability-pci-dss-4-attestation

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

B
Partial

Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.

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

D
Partial

A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.

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

B
No

Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator

reliability-failover-terminal-role

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

B
No

Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.

reliability-cellular-backup

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

B

Commercial, compliance & data ownership

No

Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator

commercial-month-to-month-contract

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

B
No

Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator

commercial-no-early-termination-fee

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

E
Yes

The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.

commercial-autorenew-terms-published

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

B
Yes

The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator

commercial-processing-not-bundled

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

B
No

Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator

commercial-interchange-plus-published

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

B
Partial

The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator

commercial-rate-increase-clause

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

B
No

Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).

commercial-pricing-published

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

B
Partial

Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator

commercial-module-unbundling

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

B
No

All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.

commercial-hardware-purchase-outright

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

B
Partial

Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator

commercial-hardware-not-locked

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

E
Yes

One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.

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

C
Partial

Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.

commercial-data-export-self-serve

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

B
No

Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator

commercial-export-customer-and-loyalty

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

B
Partial

Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator

commercial-post-termination-export-window

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

B
Partial

Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator

commercial-data-ownership-clause

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

B
No

The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).

commercial-source-available-selfhost

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

B
No

Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.

commercial-pci-p2pe-tokenization

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

B
No

Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.

commercial-pci-dss-4-controls

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

B
No

Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.

commercial-soc2-attestation

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

B
Partial

Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.

commercial-privacy-dsar-tooling

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

B
No

Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator

commercial-wcag-kiosk-accessibility

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

B
No

POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator

commercial-dual-pricing-compliant

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

B

Adversarial verification

An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 71 values — 56 upheld, 12 downgraded, 3 upgraded. It separately resolved 65 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.

Pricing and identity

FieldVerdictWhat the verifier found
pricing.implementation_feeresolve-to-yesSame finding: 'No, Nory does not charge any implementation fees' is published on the franchise-networks page. Record as vendor-claimed zero, contradicted in part by the T&Cs training-cost carve-out — not as unknown. source
pricing.contract_lengthupheldVerified verbatim in the public T&Cs: minimum of twelve (12) months, 'successive automatic renewals', 90 days' notice before renewal date. Termination limited to material breach (30-day cure), non-payment and insolvency — no termination for convenience, confirming the researcher's read that there is no ETF because there is no exit. source
pricing.softwareupheldFetched https://nory.ai/pricing directly: no prices, tiers, per-location fees or minimums — only customer logos and a 'book a chat' CTA. Note one discovery trap: https://www.nory.at/pricing/ is a different company and must not be used. Third-party roundups asserting '25+ locations, custom pricing' are unsourced and should not be promoted to evidence. source

Capability claims

ClaimAs first scoredVerdictWhat the verifier found
labor-native-payrollyes (documented)downgrade-to-partialNory'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. source
inventory-par-auto-suggestyes (claimed)downgrade-to-partialThe 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. source
labor-break-compliance-by-statepartial (claimed) — 'automatic rule enforcement ... by jurisdiction with regional rules applied automatically'upheldScore 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 automatically by region' reading. source
reporting-public-apino (inferred)downgrade-to-unknownPer the evidence standard, absence of docs is 'not documented publicly', not 'no'. Nothing on nory.ai affirmatively states there is no API, and third-party vendor-fed directories (Capterra's Nory listing) tick an API feature. The defensible finding is that no public API documentation exists — which is what extensibility-public-api-docs already records and which I confirmed independently (no API category in the help centre, no developer path on the site). The existence question itself is unknown; a partner/private API is the likeliest reality given the Toast connector. Sole evidence was www.capterra.com, which the source policy forbids as evidence for a capability claim. Requires re-verification against the vendor's own documentation.
extensibility-public-api-docsno (inferred)upheldIndependently confirmed: help.nory.ai's 19 categories contain no API section, /integrations names partners with no developer resources, and Toast's own setup article for the Nory connector contains no API credential or technical documentation at all. No public developer surface found. source
commercial-implementation-fee-publishedno (documented) — 'no onboarding, menu/recipe build or training fees are published'upgrade-to-yesThe 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'. source
commercial-data-ownership-clausepartial — quotes a 'perpetual, irrevocable, royalty-free right to copy and publish de-identified data'upheldScore 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. source
inventory-realtime-depletionpartial (claimed)upheldConfirmed 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. source
inventory-theoretical-vs-actualyes (claimed)upheldUpheld, with the same caveat: theoretical is live, actual is stocktake-gated, so the variance loop closes at count cadence rather than continuously. Evidence is a product marketing page, so keep this claim-level, not documented. source
extensibility-accounting-connectorspartial (claimed) — Xero onlyupheldVerified 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. source
extensibility-middleware-compatibilityunknownupheldAttempted to refute via a claimed Deliverect connection surfaced in aggregator profiles; neither Deliverect's partnership pages nor Nory's integrations page corroborates it. Unknown is the correct answer. source
labor-clock-in-at-pospartial (claimed)upheldConfirmed: 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. source
multi-location-corp-vs-franchisee-rolesyes (claimed)upheldVerbatim on the franchise page: 'granular permission settings that allow franchisors to control what information and features are accessible to franchisees', plus 'live EBITDA reporting' across the network and franchisee-to-franchisee benchmarking. Marketing page, so claim-level — no permission matrix or per-action grant list is published. source
multi-location-royalty-calculationunknownupheldHeld to the high bar as instructed. I read the full franchise-networks page: nothing about royalty calculation, percentage-of-sales fees, statements or collection. Unknown is correct and should not be softened to partial on the strength of the franchise positioning. source
reporting-sales-forecastyes (claimed)upheldFeature verified — 'five-week rolling forecast, broken down hour by hour', feeding scheduling and ordering. But every accuracy number (97%, 98.5%, 96%) is a vendor-published customer statistic on a marketing page with no methodology, so those figures must be carried as vendor claims, never as findings. source
labor-tip-pooling-rulesyes (claimed)upheldVerified 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. source
inventory-vendor-catalogs-edipartial (claimed)upheldVerified 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. source
inventory-invoice-ocryes (claimed)upheldVerified verbatim: 'Snap a photo of an invoice and Nory updates stock, flags price changes, and generates the credit request if the delivery's wrong.' Product marketing page, so claim-level; no accuracy or supported-format documentation exists. source
commercial-autorenew-terms-publishedyes (documented)upheldConfirmed 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. source
reliability-contractual-uptime-slano (documented)upheldConfirmed: 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. source
commercial-data-export-self-serveunknownupheldConfirmed by the T&Cs: the only documented export path is vendor-provided on termination and explicitly 'at the Customer's cost', with no window and no self-serve mechanism. Unknown for self-serve is right; do not upgrade it on the strength of report screens. source
hardware-commodity-devicesyes / grade E, cited the Nory Kiosk privacy policyupheldThe privacy policy cannot establish a hardware posture — it describes data collection, not device requirements, and grade E on a differentiator yes is not permissible. I located Nory's Supported Devices & Technical Requirements page instead, which lists only commodity floors: iOS 13/14+, Android 5.1/7.0+, tablets 7" or larger for Kiosk, and the web app on the latest three major versions of Chrome, Firefox, Safari and Edge. No proprietary terminal is named, required or sold. Value stands; evidence rebuilt at grade B. source
inventory-price-change-alertsyes / grade D, cites nory.ai/product/inventorydowngrade-to-partialI could not find an alert. The only price-change documentation is 'Actioning price changes and credit notes', which says price changes 'occur on Nory when suppliers decide to change their prices, from the last time an order has been placed' and then walks through clearing them — a reconciliation queue encountered at receiving, not a notification. I also read 'Managing your invoices in Nory' (no discrepancy flag described) and 'Purchasing Insights' (ordered-vs-delivered quantities and supplier reliability, explicitly no price trend or alerting), and searched the help centre for 'price change'. Partial, with the shortfall named: detection surfaces for action, no alerting. source
inventory-menu-margin-linkageyes / grade D, cites nory.ai/product/inventoryupheldInventory Insights documents the linkage directly: sales are attributed to the correct menu item through the recipe attached to the POS ID, and the page reports Actual Gross Profit — 'your profit margin on the Food and Beverage items you sold, once you account for the cost of the ingredients' — against theoretical GP. Value upheld at grade B. The researcher's specific assertion that GP targets are settable at menu level did not survive: the Budgets article covers sales, labour and COGS targets per location and never mentions gross profit or menu-level targets. Note corrected accordingly. source
menu-pricing-recipe-linkageyes / grade D, cites nory.ai/product/inventoryupheldThe linkage is real and documented — recipes are assigned to POS IDs, sales then deplete stock and drive the COGS page, with a 7-day automatic reprocess on assignment. But the same page refutes the researcher's stated mechanism: 'recipe costs in Nory are not automatically updated when an item's price changes, unless explicitly configured.' The record sold automatic recosting off a marketing page; the documentation says the opposite. Value upheld at grade B with the note rewritten so the cell no longer overstates it. source
labor-native-schedulingyes / grade D, cites nory.ai/product/workforce-managementupheldNative scheduling is documented end to end — build, send for approval, publish, lock for payroll, with custom shift types, break rules and overtime/premium rules, all against Projected Sales, Projected COL and a per-location Target COL % defaulting to 28%. Upheld at grade B. The '~5 seconds' Scheduling Assistant in the original note is marketing copy: the in-depth guide's only automation is 'Fill Open Shifts', which allocates already-created open shifts across available employees by availability. Rotas are built by hand with forecast assistance. source
labor-demand-labor-forecastyes / grade D, cites nory.ai/product/workforce-managementupheldDocumentation confirms a genuine demand forecast feeding labour: hourly sales prediction up to 35 days ahead, continuously updated as sales arrive, surfaced in the schedule's daily drawer as hourly sales and order projections used to shape staffing, and scored against the location's Target COL %. Upheld at grade B. One correction: the horizon is 35 days at hourly granularity, and the record's '5-week hourly forecast with an intensity setting per site' is not language the help centre uses — no intensity control is documented. source
labor-realtime-labor-percentyes / grade D, cites nory.ai/product/business-intelligenceupheldThe labour performance article confirms labour cost as a percentage of sales, as a value, or as hours, and states 'sales data is updated throughout the day, so your labour results show in real time too', with projected COL updating automatically as shifts are added and a green/amber/red target indicator. Upheld at grade B. I found no support for the record's 'P&L refreshing roughly every 15 minutes' — no refresh cadence is published anywhere in the help centre, so that figure is removed rather than re-cited. source
labor-shift-swap-workflowyes / grade D, cites nory.ai/product/workforce-managementupheldThis one was under-sourced rather than overstated. The team app article documents three distinct request types — swap with a named colleague from an available list, drop a shift, and claim an open shift — each routed to a manager for approval with a push notification on the outcome, and a companion article covers the manager-side processing. Stronger than the marketing page implied. Upheld at grade B. source
payments-tip-poolingyes / grade D, cites nory.ai/product/payrollupheldThe Tips/Tronc article documents the distribution engine the marketing page only asserted: tips pooled from POS data, recalculated daily per branch, split either equally or by operator-defined points weighted by hours worked, with points rules by department, position or tenure, plus per-employee exclusions and bonus multipliers, and gross tips visible to staff in the Team app. Upheld at grade B. Note that this is tip distribution built on POS tip data — Nory does not process payments, so it is not capturing the tip itself. source
reporting-multiloc-drilldownyes / grade D, cites the franchise-networks solutions pageupheldA solutions landing page cannot carry a differentiator yes, so I went looking for the feature. Purchasing Insights documents an explicit group/location filter — 'view insights at a group level or for an individual location' — plus drill-down by supplier, item and category; Sales and forecasts documents a location selector with automatic period-over-period comparison; and the estate-wide Schedules overview shows planned vs actual COL % across branches. That is group to site to item. Upheld at grade B, but the original note's drill-down 'into specific invoices' is unevidenced and is struck. source
menu-pricing-countdown-auto-86no, grade B - Stock is tracked but no documented auto-86 action.upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
menu-pricing-daypartingno, grade B - Menu scheduling is a POS function; Nory dayparts forecasts, upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
menu-pricing-dynamic-pricingno, grade B - Marketing references 'pricing optimization' insight but no rupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
payments-tip-adjustno, grade B - Tip capture happens in the POS; Nory consumes the resulting upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
payments-payout-timingno, grade B - Nory is not an acquirer and makes no merchant payouts. It doupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
kitchen-item-build-screensno, grade B - Recipes with portioning exist in Nory but are not rendered oupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
kitchen-speed-of-service-reportingno, grade B - Nory reports orders per labour hour and labour productivity,upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
guest-loyalty-unified-profileno, grade B - Nory is an operations platform with no guest CRM; its 'custoupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
guest-loyalty-native-email-smsno, grade B - Nory's messaging is staff-facing (team app notifications), nupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
labor-break-compliance-by-statepartial, grade B - Score survives at partial, but the stated basis is wrong andupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
labor-tip-pooling-rulesyes, grade B - Verified verbatim: 'Tips and tronc are calculated in Nory frupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
labor-native-payrollpartial, grade B - Nory's own payroll page shows this is a part-managed UK bureupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
inventory-realtime-depletionpartial, grade B - Confirmed and, if anything, the researcher was generous in tupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
inventory-vendor-catalogs-edipartial, grade B - Verified verbatim: 'Orders go out by email (CSV attachment) upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
inventory-par-auto-suggestpartial, grade B - The Ordering Assistant that produces the buy suggestion is eupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
hardware-pricing-transparencyno, grade B - No hardware sold, and no pricing of any kind is published.upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
extensibility-accounting-connectorspartial, grade B - Verified verbatim: Nory 'connects directly to the major POS upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
commercial-implementation-fee-publishedyes, grade B - The researcher missed a published figure. Nory's franchise-nupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
inventory-theoretical-vs-actualyes (B) - "Upheld, with the same caveat: theoretical is live, actual is stocktake-gated, so the"upheldThe prior citation was nory.ai/product/business-intelligence, a marketing page, which grades C and cannot carry a yes on a differentiator. Re-probing turned up a live help centre at help.nory.ai with an entire 'Inventory reconciliation' collection. The key-definitions article states the report compares Actual against Theoretical derived from sales and recipes, and gives the explicit formulas for the quantity variance and for two currency variance columns (Gap Value, and Variance including Logged Waste). That is grade-B product documentation describing the mechanism, not naming a feature, so the yes survives on documentation located in this pass. source
inventory-invoice-ocryes (B) - "Verified verbatim: 'Snap a photo of an invoice and Nory updates stock, flags price c"upheldThe prior evidence was nory.ai/product/inventory, a marketing page (grade C), and the note itself conceded that no accuracy or format documentation existed. It does exist: help.nory.ai has a 'Managing deliveries & invoices' collection and an 'Invoice assistant' collection. 'Precise Invoice Scanning' documents the AI extraction states and the human-review fallback with its six-hour target; 'Getting started with Invoice Smart Matching' documents that extraction is per line (quantity and unit price per item, 3-way match against PO and GRN, matched on item code) and is candid about limits - it will not catch VAT errors, currency mismatches or wrong units of measure. Line-item capture without manual entry is therefore documented, not merely claimed. The claim's disjunctive channel list is satisfied by photo; PDF and email ingestion are not documented and are recorded as such in the note. source
inventory-native-not-partneryes (B) - "Inventory, recipe costing and purchasing are Nory's own core product, not a resold"upheldThe prior citation was the marketing page nory.ai/product/inventory (grade C) and the note was an assertion about market positioning rather than evidence. The help centre supplies the documentation: an entire 'Setting up inventory' collection of step-by-step admin guides (adding items, creating recipes and batch recipes, storage areas, supplier rules, CPU/central production), a 'Managing inventory movements' collection, and a reconciliation report - all operated from Nory's own inventory module, with per-item cost and GP computed in-app. The only external systems documented for this data path are accounting destinations. Native delivery is therefore documented, and the yes stands at grade B. source
reporting-sales-forecastyes (B) - "Feature verified - 'five-week rolling forecast, broken down hour by hour', feeding"upheldThe prior citation was nory.ai/product/business-intelligence, a marketing page that grades C and cannot support a yes on a differentiator. The help centre article 'Sales and Forecasts' documents the same capability at grade B and more precisely: hourly granularity, a 35-day horizon (the marketing 'five-week rolling' figure), per-location models fed by that location's history plus seasonality, holidays and weather, continuous re-forecasting, and an hourly drill-down in the UI. The separate scheduling guide independently documents the consumption path - the forecast is the 'Projected Sales' input to the schedule's Cost of Labour header - which is the half of the claim that distinguishes a forecast that drives work from a forecast that only decorates a chart. The unmethodologised accuracy percentages are excluded from the note. source
multi-location-corp-vs-franchisee-rolesyes (B) - "Verbatim on the franchise page: 'granular permission settings that allow franchiso"downgrade-to-partialThe sole evidence was www.nory.ai/solutions/franchise-networks, a solutions marketing page (grade C), and the original note already conceded no permission matrix was published. A matrix does exist - help.nory.ai article 8395451 lists every grant by name - and it refutes the franchise-specific half of the claim rather than supporting it. The documented structure is a rank hierarchy within a single brand (Admin -> Location Manager -> Supervisor -> Employee) with location-scoping and reporting toggles; the strongest cross-site grant is 'Can access reports for all locations', described as data 'for all locations set up within the brand'. There is no documented franchisor/franchisee tenant separation, no franchisee-owned employee/banking/payroll boundary, and no corporate config-enforcement permission. Location-scoped visibility is genuinely delivered, so the honest value is partial with that shortfall named, not yes. source
menu-pricing-allergen-nutritionunknown (grade F, 'No allergen or nutrition capability documented on the product or help pages.')resolve-to-noWalked the whole Intercom help centre with a Googlebot UA. The item and recipe authoring screens are documented field-by-field and contain no allergen or nutrition attribute; a full-text scan of all 126 articles returns no hit for allergen/nutrition/calorie. Nory holds recipe components for costing only and has no menu publishing channel. source
labor-photo-punch-verificationunknown (grade F, 'Not mentioned on the workforce page or in the Kiosk privacy policy's data inventory.')resolve-to-noRead the Kiosk setup article, the employee-app location-permissions article, the Clocking Rules settings article and the supported-devices requirements table. Punch identity is a 4-digit PIN at the kiosk and GPS at the phone; the device requirements table marks the kiosk camera as not required, and the clocking-rules settings surface contains no photo or facial option. source
labor-geofenced-mobile-punchunknown (grade F, 'Not documented publicly.')resolve-to-yesThe help centre documents location-validated mobile clock-in directly: precise location permission is mandatory, the punch is rejected when the phone is located away from the restaurant, and the behaviour is confirmed in two further articles (kiosk setup as the no-GPS fallback, and the device requirements table's Location required = Yes for clock-in). source
labor-offline-time-punchunknown (grade F, 'Nory publishes no offline behaviour for any module.')resolve-to-noThe vendor's own technical-requirements article is an explicit supported/unsupported statement, not an absence of evidence: internet is required at all times and the apps do not support offline mode, restated as Internet required = Always for every app in the summary table. A stray FAQ mention of 'offline data caching' is noted in the claim but is not a documented offline punch-and-reconcile path. source
labor-manager-override-auditunknown (grade F, 'Time-card approval workflow exists; an immutable, queryable override audit trail is not documented.')resolve-to-yesThe prior rationale was wrong on the facts. The timecards article documents a per-timecard action list attributing every amendment to the person who made it with timestamps, and a parallel shift-change view; the schedule-approval release article documents automatic schedule versioning with full change history at approval and estate-level reporting on manual edits. Attribution, timestamping and after-the-fact review are all present; only the word 'immutable' is unclaimed by the vendor. source
labor-fair-workweek-supportunknown (grade F, 'Predictive-scheduling notice tracking and predictability pay are not mentioned.')resolve-to-partialThe US Compliance Assistant article does mention fair work week rules by name as a toggleable rule and supports the predictive-scheduling jurisdictions, so the prior rationale was factually wrong; but the covered-rule list is hours, breaks, rest and minimum wage only, and neither notice-deadline tracking nor predictability pay is documented in that article, the UK/IE counterpart, or the schedule-approval articles. source
labor-minor-labor-rulesunknown (grade F, 'Not enumerated among the compliance rules described.')resolve-to-partialYoung-worker limits and age-banded wage are explicitly enumerated for UK/RoI in the Compliance Assistant article, so the capability partly exists; but the US rule list has no minor rule, and the Clocking Rules settings screen - the whole configurable clock-in surface - contains no age-based restriction, so the claim's requirement of enforcement at both scheduling and clock-in is unmet. source
inventory-unit-conversion-yieldsunknown (grade F, 'Purchase/recipe/count unit conversions and yield percentages are not described on the product page.')resolve-to-partialThe prior rationale looked only at the marketing product page. The help centre documents the unit model in detail - pack size on purchase, a recipe unit, multiple count units with labels and per-unit reporting toggles, and a batch yield field - but no article describes a yield/waste percentage on raw-to-usable conversion; waste is captured as a logged event instead. source
inventory-86-auto-syncunknown (grade F, 'No documented write-back from Nory to POS, online ordering or marketplace availability.')resolve-to-noThis is now positive evidence, not silence. The availability feature Nory does ship is documented as supplier/CPU ordering availability and the article states outright that a paused item keeps depleting through recipes; the recipe-linking article establishes the POS integration as an inbound sales feed that only discovers menu items after they sell. There is no channel by which Nory could 86 a POS or marketplace menu. source
inventory-commissaryunknown (grade F, 'Batch production exists; a central-kitchen issue/sell-at-transfer-cost model is not documented.')resolve-to-yesTwo dedicated help articles (CPU Functionality in Nory; How to Set Up CPU in Nory) document exactly the claimed model - a CPU location with a Production tab that acts as a supplier of batch items to other locations, with an optional mark-up on the batch price and dedicated CPU fields in the stock reconciliation and management report formulas. The prior rationale predates these articles. source
inventory-lot-traceabilityunknown (grade F, "'Batches' appear as a stock movement type but lot capture at receiving and recall trace are not documented.")resolve-to-noRead both receiving articles, which enumerate the fields captured on a delivery, and the batch-recipe creation form. Neither captures a lot or batch number; Nory's batch object is a production recipe, not a lot. There is no field from which a recall trace could be constructed. source
inventory-shelf-life-expiryunknown (grade F, 'Not documented.')resolve-to-noTwo independent enumerations. The notifications article lists Nory's entire alerting surface and contains a document-expiry alert but no stock-expiry alert; the receiving and batch-creation forms enumerate their captured fields and hold no date from which shelf life could be computed. Walked both inventory-reporting collections for an expiring-soon report and found none. source
inventory-bar-partial-bottleunknown (grade F, 'Not documented.')resolve-to-partialThe count-unit configuration articles show partial-volume and by-weight counting are achievable through unit setup, with a spirits example given by the vendor; but neither of the claim's named mechanisms - scale integration or a bottle-fraction control - is documented, and the device requirements article lists no peripheral support beyond the camera. source
reporting-eod-closeoutunknown (grade F, 'Nory has no tender or drawer data of its own; whether it produces a POS-fed EOD reconciliation document is not documented.')resolve-to-noNory publishes the exact shape of the sales data it ingests (net sales after VAT and service charge, order-level lines for depletion, tips only where the POS sends them) and publishes field-level definitions for each of its reports. Neither the ingested data nor any documented report contains tender types, tax, refunds or an expected cash deposit, and the help centre has no cash-drawer concept at all. source
reporting-cash-over-shortunknown (grade F, 'Not documented.')resolve-to-noNory publishes the shape of what it takes from the POS (net sales; tips only where shared) and the shape of what its counts capture (inventory items, batches, storage areas). Neither side contains cash: no drawer, float, paid-out or tender concept occurs anywhere in the 126-article help centre, so the inputs the claim requires do not exist in the product. source
reporting-channel-profitabilityunknown (grade F, 'Not documented; Nory lists no marketplace integrations from which to net commission.')resolve-to-partialThe Sales and Forecasts article documents a genuine dine-in / pick-up / delivery revenue split with period comparison, which the prior rationale missed. It stops at revenue: margin is reported food vs beverage, delivery is not broken out per marketplace, and no commission figure enters any documented report, so the claim's netting requirement fails. source
reporting-scheduled-deliveryunknown (grade F, 'Not documented.')resolve-to-noTwo enumerations rather than a failed search: the notifications article lists every email and push Nory sends, and the settings article lists every company-level settings tile. Neither contains a report subscription, cadence or recipient list; every documented way to get a report out of Nory is a manual CSV download or a shared view link. source
reporting-raw-warehouse-exportunknown (grade F, 'No S3/SFTP/warehouse export documented; no API docs exist to confirm or deny.')resolve-to-partialThe help centre does document a bulk-export surface - four HR CSVs, timecard CSV, item-list CSV, budget CSV/link - so raw export is not absent; it is limited to manual downloads of non-transactional data, with the only scheduled outbound feed being accounting-system invoice sync. That is a named shortfall against the claim's 'automated recurring... not just manual CSV download'. source
multi-location-local-override-policyunknown / grade F - 'Field-level lock/override governance is not documented.'resolve-to-noRead the recipe-linking article and the settings enumeration on help.nory.ai. Nory does not author menu items at all - they arrive from the POS after first sale - and the enumerated settings surface offers a fixed company-wide/location split with no configurable per-field lock. source
multi-location-scheduled-publishunknown / grade F - 'Not documented.'resolve-to-noChecked the recipe-linking article on help.nory.ai and the published Swagger spec at api.nory.ai. Menu and price data moves POS -> Nory only; there is no outbound publish path, therefore no scheduled activation or rollback. source
multi-location-normalized-item-rollupunknown / grade F - standardised recipes imply a shared item spine but rollup not documented.resolve-to-partialRead the Smart Matching, recipe-linking and Purchasing Insights articles on help.nory.ai. Locally named POS items at each site are mapped onto brand-level recipes and insights aggregate at group level, so the rollup exists; it is partial because every per-location link must be confirmed by hand and the key is Nory's recipe rather than a corporate item ID. source
multi-location-multi-tax-jurisdictionunknown / grade F - 'Not documented. Nory does not compute sales tax at point of sale.'resolve-to-noThe settings article enumerates the entire configurable surface in two named sections and contains no tax configuration; the only documented tax field is a supplier/item purchase tax rate in the onboarding data spec. Nory takes sales totals from the POS rather than computing tax. source
multi-location-config-audit-logunknown / grade F - 'Not documented.'resolve-to-partialHelp-centre searches for audit/history/changes surfaced a schedule change-history feature and an Employee Detail Changes CSV export - real but scoped to rotas and employee records, not to configuration objects, and with no immutability or corporate-wide query documented. source
multi-location-enterprise-apiunknown / grade F - 'No public API documentation exists to evaluate.'resolve-to-noA public API spec does exist at api.nory.ai/swagger.json (docs./developers./developer.nory.ai do not resolve). Reading the full schema: no transaction-level endpoint of any kind, and all data paths are branch-scoped, so the claim's specific capability is absent from the documented surface. source
hardware-offline-modeunknown / grade F - 'Nory publishes no offline behaviour documentation for any surface.'resolve-to-noNory does publish it, in the Supported Devices & Technical Requirements article: an active internet connection is required at all times and the apps explicitly do not support offline mode. That is positive evidence of absence, not silence. source
hardware-remote-device-managementunknown / grade F - 'Not documented.'resolve-to-noThe supported-devices article is an exhaustive statement of the client surface - three store-distributed apps on customer-owned iOS/Android devices plus a browser - so there is no vendor device fleet to show online/offline or reboot, and the enumerated settings contain no device-management console. source
extensibility-free-sandboxunknown / grade F - 'Not documented.'resolve-to-partialNory's public Swagger spec is explicitly a sandbox spec naming sandbox.nory.ai as its server, which establishes the environment exists; but that host does not resolve publicly, auth is email/password only, and no developer signup or seeded dataset is published, so it is not a free sandbox obtainable without an account. source
extensibility-oauth-partner-appsunknown / grade F - 'Not documented.'resolve-to-noThe published API schema enumerates its security definitions and there is exactly one - a bearer token issued against email and password, with no scopes, consent or per-app revocation. An API schema with no such field is the enumeration this bar allows. source
extensibility-menu-write-apiunknown / grade F - 'no write API is documented'.resolve-to-partialA write endpoint for menu items does exist in the published spec (POST /inventory/ingest), which corrects the prior premise; it is partial because the body is an opaque content string with no documented price or modifier fields, there is no update path, and it targets Nory's costing model rather than the POS menu. source
extensibility-data-symmetryunknown / grade F - 'No API surface published to assess.'resolve-to-noThere is a published surface - api.nory.ai/swagger.json - and enumerating its 22 paths shows six read-only object types (branches, brands, suppliers, deliveries, integration data, employee punches) with no write counterpart, which settles symmetry negatively from the schema itself. source
extensibility-published-rate-limitsunknown / grade F - 'No public API.'resolve-to-noA public API spec does exist, and it is the whole of Nory's published API documentation - it states no quotas, no throttling behaviour and no 429 or rate-limit headers, and no other developer doc surface exists on any resolving Nory host. source
extensibility-api-versioning-deprecationunknown / grade F - 'No public API, so no changelog or deprecation policy.'resolve-to-noThere is a public API spec, so the premise was wrong, but the conclusion holds on better grounds: the spec carries only a /v1 basePath, and the enumerated publication surface (sitemap, help centre, api host paths, non-resolving doc subdomains) contains no changelog or deprecation policy. source
reliability-sync-conflict-handlingunknown / grade F - 'Not documented (relevant for concurrent stock counts and rota edits, but Nory publishes nothing).'resolve-to-noNory does address the underlying condition: its technical-requirements article rules out offline operation entirely, so no network-partition edit mode exists to document, and the Count schema in the published API carries no version or conflict field. source
reliability-incident-postmortemsunknown / grade F - 'None found; no status page or incident archive located.'resolve-to-noWent beyond not finding one: the vendor's own sitemap enumerates every page on nory.ai with no status or incident section, the obvious status hostnames fail DNS, and the statuspage.io subdomain is unclaimed. For a claim about what a vendor publishes, that is positive evidence. source
reliability-onsite-installunknown / grade F - 'Live training sessions are referenced in the T&Cs; whether they are on-site is not stated.'resolve-to-noRead the clause itself: the live sessions are 'web-based', and the enumerated modalities in Section 7 - online videos, live web-based training, chargeable additional remote training - are all remote. The train-the-trainer article confirms the current model is champion-led with remote support and cites in-store sessions only as a superseded experiment. source
reliability-menu-build-serviceunknown / grade F - 'build assistance during onboarding is not described publicly; help-centre articles suggest operator self-setup.'resolve-to-partialThe onboarding collection does describe the division of labour: Nory supplies the recipe/inventory specification, validates against a submission checklist and migrates workforce structure itself, but recipe authoring and POS-item linking sit with the operator, so this is assisted rather than vendor-performed. source
reliability-backup-restoreunknown / grade F - 'No RPO/RTO figures or self-serve backup published.'resolve-to-noThe terms address the subject directly and negatively: backups are disclaimed onto the customer with no mechanism provided, full export is a paid post-termination service, and the DPA's restoration language is unquantified boilerplate. Both disjuncts of the claim fail on first-party text rather than on silence. source
commercial-rate-increase-clauseunknown / grade F - 'No price-increase or price-protection clause identified in the public T&Cs.'resolve-to-partialRetrieved the terms in full: there is a price-increase clause and it is capped to the US CPI for anniversary uplifts, with a 30-day termination right for EU customers on notice of an increase. It falls short because renewal-term repricing is uncapped and the exit right is EU-only. source
commercial-module-unbundlingunknown / grade F - four modules marketed separately but no a-la-carte pricing or independent-cancellation terms published.resolve-to-partialThe terms establish the add side - components and integrations are added by amended order form as separate priced items - which is more than the marketing implication the prior rationale rested on. The cancel side and the prices remain unpublished, and termination is agreement-level with 90 days' notice. source
commercial-data-export-self-serveunknown / grade F - verified as export-on-termination at customer's cost only, with an instruction not to upgrade on the strength of report screens.resolve-to-partialNot report screens: help.nory.ai documents an explicit self-serve CSV export drawer for four HR datasets plus timecard export, which is real coverage of the claim's labour limb. It stays short of the claim because no transactional export (orders, line items, payments) is documented in the product or the API, and the full extract remains chargeable and post-termination only. source
commercial-soc2-attestationunknown / grade F - no SOC 2 or ISO 27001 claim anywhere; absence of a claim is not proof of absence of a report.resolve-to-noThe claim asks whether the vendor states it holds an attestation and will provide the report. The full contract and DPA were retrieved and contain no such statement (no ISO/SOC/27001 occurrence), only Article 32-style measures and a cost-reimbursed customer audit right; no trust centre exists on any resolving hostname or in the sitemap. source
commercial-wcag-kiosk-accessibilityunknown / grade F - no VPAT/ACR or WCAG statement published; no consumer-facing surface.resolve-to-noFor a claim about what the vendor publishes, the vendor's own sitemap is an enumeration: 415 URLs with no accessibility or conformance page, matched by 22 help-centre collections with none either and a device-requirements article that covers browsers and resolutions but not assistive technology. Corrected one detail - Nory does ship a kiosk app, so the claim is in scope. source
menu-pricing-allergen-nutritionno / grade B - 'The item creation form is enumerated in full - name, category, type, supplier, s'downgrade-to-unknownRe-read the cited item-creation article: it is a how-to ('Enter the item name and select a category... Select a type... add the purchasing information...'), with no completeness language, so it does not establish that the form has no allergen attribute. I then found first-party counter-assertion on www.nory.ai/blog/agentic-ai-restaurant-compliance-software - 'The system checks allergen data against menus in real time and flags mismatches before anything goes live' - which no help article corroborates or contradicts. A vendor asserting the capability plus documentation that is merely silent is unknown, not no. source
inventory-lot-traceabilityno / grade B - 'Receiving with an order captures the Invoice Number (manual entry) and the Tota'downgrade-to-unknownRetrieved both receiving articles myself. The companion article's wording is 'Confirm details such as supplier, pack size, price, and quantity' - open-ended by construction - and the primary article is a click-path how-to with no completeness claim, so the pair cannot carry an enumeration argument. The only other basis was a corpus-wide search for lot/batch-number that returned nothing. source
inventory-shelf-life-expiryno / grade B - 'The Nory Notifications article enumerates every alert the platform sends: for man'downgrade-to-unknownRetrieved the notifications article and confirmed it is a genuine closed enumeration of manager email - three items, none stock-related - which settles the alert half. It does not reach the report half, and the report half was established only by walking two collections and finding nothing; the receiving article that would establish no date is captured uses 'such as'. A disjunctive claim needs both halves refuted positively. source
multi-location-multi-tax-jurisdictionno / grade B - 'The settings article states Settings in Nory are divided into two sections and li'downgrade-to-unknownRetrieved the Compliance Assistant articles and found a brand-level compliance settings area with documented location-level rule overrides and hard/soft enforcement - configuration that the cited settings article's two-section list omits entirely. That article is therefore not the entire configurable surface, so its lack of a tax section is not positive evidence. Nory does hold tax data (per-item Tax Rate, per-category VAT type, a single default VAT rate on Xero push), which makes the negative less clean rather than more. source
reliability-sync-conflict-handlingno / grade B - "The article that addresses connectivity in full states 'An active internet co"downgrade-to-unknownRe-read the cited article end to end. Its FAQ Q1 lists 'offline data caching' as a native-mobile-app-only feature, which contradicts section 3's 'The apps do not support offline mode' and destroys the enumeration argument that no partition state can exist. The residual basis is a help-centre search that returned nothing, which does not meet the positive-evidence bar for an asserted no. source
reliability-onsite-installno / grade B - "Section 7 (Training and Support) enumerates the entitlement: unlimited online "upgrade-to-partialThe enumeration was not exhaustive. I re-read the terms: clause 6 states 'The scope of work included with the implementation shall be set out in the applicable order form' and refers to 'professional services relating to implementation', so section 7's training list does not cover implementation delivery at all. And Nory's own rollout post says it offers 'hands-on training sessions (in person where situation allows)' plus drop-in sessions at key project phases and enhanced support during go-live weeks. In-person go-live support therefore exists but is discretionary, uncontracted and unaccompanied by any dealer network or hardware install, so partial at grade D rather than yes. source
labor-offline-time-punchno / grade B - "Section 3, Network & Connectivity Requirements: 'Nory is a cloud-based platform. An acti"downgrade-to-unknownRetrieved the cited article in full. Its section 3 sentence and its summary-table row are contradicted inside the same page by FAQ Q1, which names 'offline data caching' as available only through the native mobile apps - Nory Team being the punch surface - so the page is not the exhaustive supported/unsupported statement the no was built on. I then went looking for a replacement basis: the Nory Team clock-in article lists the failure modes for a refused punch and connectivity is not one of them, and the timecards article treats a missing punch as a manual manager edit. Nothing documents an offline punch queue and nothing documents its absence. source
hardware-offline-modeno / grade B - "Direct vendor statement: 'An active internet connection is required at all times for a"upheldThe quoted sentence is dead - FAQ Q1 of the same page contradicts it - but the value does not need it. The article enumerates Nory's client surface as exactly three native apps (employee clock-in, clocking kiosk, inventory management) plus the browser dashboard, and the recipe-linking article confirms items reach Nory only after being sold through the connected till. Nory ships no order-entry terminal at all, which is positive evidence of absence for this claim independent of any offline statement. Note rewritten to withdraw the refuted leg. source
inventory-mobile-count-offlinepartial / grade D - "Stock counts are explicitly mobile-first; barcode scanning and offline-then-sync beh"upheldPartial is right and does not depend on the refuted offline sentence, but it was resting on nory.ai/product/inventory, a marketing page. Retrieved the counting-stock help article instead: it documents the Nory IM iOS/Android counting flow, storage-area and category filtering, and auto-saving drafts, which lifts the evidence to grade B. Searched the help centre for barcode and for QR and got zero hits in both cases; the only documented camera use is invoice/document OCR. Value unchanged, grade D to B, shortfall now named. source
reporting-scheduled-deliveryno / grade B - "The notifications article enumerates Nory's entire outbound message surface: 'Manager"upheldRetrieved the notifications article in full and it is a genuine enumeration of what Nory emails and pushes - three manager emails, a closed employee list, and exactly two inventory messages - with no report subscription among them, and the only documented way to add recipients to a Nory email is on a supplier record for purchase orders. Also retrieved both export articles: HR data and timecards each leave Nory as a manually downloaded CSV. The secondary settings-article leg is withdrawn because 14487078 is an onboarding best-practice guide rather than an exhaustive settings inventory; the verdict never needed it. source
multi-location-local-override-policyno / grade B - "There is no corporate menu record in Nory to apply field-level locks to. Menu items or"upheldRetrieved the recipe-linking article and it says verbatim what the note claims: items are created in the POS, surface in Nory's POS IDs list only after a first sale, and the sole action on them in Nory is recipe assignment, with location access shown read-only on the recipe. That is a structural bar to per-field override governance and it stands without the settings article, whose enumeration the audit refuted and which I have removed from the note. source
extensibility-doordash-preferredno / grade B - "Nory is not in DoorDash's 2026 Preferred Integration Partner cohort (Checkmate, Chowly"upheldThe value is right but the cited URL is dead (get.doordash.com 301s to merchants.doordash.com and 404s). Retrieved DoorDash's 18 May 2026 newsroom announcement instead and read the roster there: Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper, benchmarked as of 8 May 2026. Nory does not appear. Source swapped, and the note's unsupported 'not a POS, so it is ineligible' rationale removed - the announcement describes the programme as covering POS and middleware and states no such eligibility rule. source
hardware-pricing-transparencyno, grade C - No hardware sold, and no pricing of any kind is published.upheldCitation-staleness re-verification, value untouched. https://nory.ai/pricing 301s to https://www.nory.ai/book-a-chat (HTTP 200, 71,091 bytes), a sales-contact form; a fabricated sibling path returns a real 404, so this is a genuine replacement rather than a soft 404. Re-evidenced the absence positively instead of resting on the dead URL: the vendor's own sitemap.xml lists 317 URLs with no pricing, shop, store or hardware page among them, and the fully rendered platform nav on /product enumerates the entire catalogue - four software modules, five AI assistants, Integrations, Capital - with no Pricing link and no hardware. No hardware exists to price, and no price of any kind is published. Grade C retained: the evidence is first-party site structure and sales pages, not documentation. source
extensibility-public-api-docsno (inferred)upgrade-to-partialSUPERSEDES the 2026-08-01 'upheld' verdict on this same cell, which confirmed 'No public developer surface found.' from help.nory.ai, /integrations and Toast's connector article. That verdict was correct about the surfaces it read and wrong about the record: seven days later, on 2026-08-08, three cells in this record (extensibility-free-sandbox, extensibility-oauth-partner-apps, multi-location-enterprise-api) were scored at grade A from a Swagger 2.0 spec served openly at api.nory.ai/swagger.json, and nobody came back to this cell. Re-fetched 2026-09-01: HTTP 200 anonymously, 18,020 bytes, no robots.txt on the host. Public API reference documentation readable with no partner agreement, NDA or sales call does exist. Partial rather than yes because it is a sandbox middleware spec with no order, payment or menu resource and there is no developer portal or self-service registration. Found by auditing this record's absence rationales against its own cited hosts, not by re-reading the surfaces the original verdict named. source
reporting-public-apiunknowndowngrade-to-noSUPERSEDES the 2026-08-01 'downgrade-to-unknown' verdict, whose reasoning was that absence of documentation is 'not documented publicly' rather than 'no'. That reasoning was sound while no API was published. One is: api.nory.ai/swagger.json enumerates the complete published path set, and it contains no order, transaction, sales, payment, tender or menu resource, so the claim's required coverage fails on an enumerated schema rather than on an absence. Self-service credentials fail on the same document -- the only credential path is POST /auth/token taking an existing {email, password}. The question is now answerable positively and the answer is no. source
menu-pricing-allergen-nutritionunknown — 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-toresolve-to-no`allergen`, `nutrition`, `calorie` and `traceability` each occur 0 times across the 127 help.nory.ai articles and 0 times in the API spec. The product surface that would carry it is the Compliance Assistant, and its own article enumerates what the rules engine covers - 'Max weekly/daily hours. Rest breaks during shifts. Days of rest and minimum time between shifts. Young workers work limits. Minimum wage, including age bands.' Every one is a workforce rule; allergens are not in the list, and neither is any menu attribute. Nory also has no publishing path to online ordering or third-party menus: 'Nory links directly to your EPOS system' and consumes 'the restaurants net sales figure' from it. THE POISON, published because it is the trap here: `allergen` does occur 9 times on www.nory.ai, and the 6 that read as product claims are all in one blog post about 'an agentic AI system' in the abstract ('the technology checks allergen data every time a menu changes'), with the remaining 3 in a kitchen-audit post and two podcast transcripts. Nothing in the help centre or the spec corroborates it as shipped Nory functionality. source
labor-offline-time-punchunknown — 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 avairesolve-to-noSupported Devices & Technical Requirements (updated 2026-03-10) states the rule twice, once in prose and once as a closed table. Prose: 'Nory is a cloud-based platform. An active internet connection is required at all times for all Nory apps and web access. The apps do not support offline mode.' Table: the Summary Table's four columns are the Employee App, Kiosk App, Management App and Web browser - every client the article's own sections 1 and 2 define - and its 'Internet required' row reads 'Always Always Always Always'. Clocking in runs through exactly two of those (settings article 14487078: 'Nory Team App - Mobile clock-in with geofencing' or 'Nory Kiosk App - Shared device with 4-digit employee codes'), and both are 'Always'. THE INTERNAL CONTRADICTION, resolved rather than hidden: the same article's FAQ 1 lists 'offline data caching' among features 'only available through the native mobile apps' as against a mobile browser. That phrase is the whole of it - no offline punch behaviour, no reconnect reconciliation and no duplicate handling is described anywhere in the corpus, `time punch` occurs 0 times, and this claim requires the behaviour to be documented. source
inventory-lot-traceabilityunknown — 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 Storesolve-to-no`lot number`, `batch number`, `traceability`, `recall` and `serial` each occur 0 times across the 127 help articles and the API spec. The receiving flow is documented end to end and captures quantity only: 'you can click, item by item, to confirm the quantity received', after which 'Nory will generate a Good Received Note'. The nearest thing to a trace artefact is a file attachment, and the article says what it is for: 'You can attach supporting documents or photos to the goods received note- for example: - A delivery note - A photo of damaged goods - Evidence of a substituted item', kept 'to support later review and provide a clearer audit trail' - a document trail on a purchase, not a lot identifier carried through production to sales. THE POISON: `batch` occurs 120 times in the help centre and every sense checked is a batch RECIPE (a prep sub-recipe) or the 'Batch' ingredient category in the waste report, never a receiving lot. source
inventory-shelf-life-expiryunknown — 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 resolve-to-noNo date is captured on stock at any point. The receive flow confirms quantity item by item and produces a Goods Received Note; no use-by or best-before field appears in it, in the counting articles, or in the API spec. `best before` occurs 0 times and `shelf life` twice, both as advice rather than a feature ('reviewing shelf-life policies'). Expiry enters the product only as a WASTE REASON after the fact - the stock-variance article asks whether waste happened because of 'Product expiry or misrotation ?' - which is a label on a loss already taken, not an expiring-soon alert. THE INSTRUMENT THAT MAKES THIS A `no` RATHER THAN A GAP: Nory demonstrably can do date-based expiring-soon alerting and does it for PEOPLE, not stock. 'Tracking Visa expiry dates in Nory' (art. 8894754) documents a stored expiry date, a two-stage alert - 'An email notification will be sent to employee and HR managers 60 days and 30 days before the expiry date' - and a list highlight. Of the 17 tokenised `expiry` hits in the help centre, that HR feature is the only one attached to a date field. source
reporting-comps-voids-auditunknown — 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) resolve-to-noNory never receives the transactions this report would be built from. 'Sales and forecasts' states what crosses the boundary: '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.' A net figure per period carries no line, no tender, no employee and no reason code, so comps, voids, discounts and price overrides cannot be attributed to the employee who applied them or the manager who approved them. Consistent with the vocabulary: `void` and `comp` each occur 0 times in the 127 help articles, against `waste` and `inventory` in the hundreds as controls. The record's own scope_overrides already retire order-capture as a settled non-surface for Nory; this is the reporting consequence of the same fact. source
reporting-server-scorecardsunknown — 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' attendaresolve-to-noThe labour insights screen enumerates its own metric set and it is a closed toggle: 'By clicking the Hours label under Sales, you can toggle between several key performance metrics: Hours SPLH OPLH Cost COL %'. All five are location-level labour-efficiency ratios; none is per-employee, and Nory's recommendation confirms the grain - 'Nory recommends using SPLH (Sales Per Labour Hour) as your primary week-on-week performance metric.' The claim's four named measures are absent as vocabulary too: `items per check`, `attachment rate` and `per server` occur 0 times across the 127 help articles, 332 www pages and the API spec, and `average check` occurs once in the help centre. The structural reason is the same one behind comps/voids: Nory ingests a net sales figure from the EPOS, not per-check detail with a server on it. source
reporting-custom-report-builderunknown — 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 Insighresolve-to-no`report builder` and `custom report` each occur 0 times across the 127 help articles, the 332 www pages and the API spec. What Nory ships is a fixed set of named reports, each with its own definitions article - the Management Report, the Stock Reconciliation Report, the Accounted Waste dashboard, labour insights, inventory insights - and the documented flexibility inside them is filtering and view switching, not dimension and measure selection: the labour screen offers a daily/weekly/monthly view and a five-value metric toggle, and the inventory screens offer category filters. No article describes choosing dimensions, choosing measures, or saving a result. Nothing in the API spec exposes a report or query resource either; its 20 paths are auth, branches, brands, integration, inventory, punch, settings and templates. source
reporting-webhooksunknown — 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 isresolve-to-no`webhook` occurs 0 times in the 127 help articles, 0 times across 332 www pages and 0 times in the published API spec. The spec is Swagger 2.0, 20 paths and 8 schemas, and every path is a request/response REST operation - auth/token, auth/refreshToken, branches, brands, integration, six inventory paths, punch, settings/customHolidays and five templates paths - with no callbacks block, no subscription resource and no event catalogue. Nory would also have nothing to emit for this claim's subject: it consumes a net sales figure from the operator's EPOS rather than seeing order or payment lifecycle events. TWO CAVEATS RECORDED RATHER THAN BURIED: the spec is titled 'Nory Middleware - Sandbox Environment' and may not be the whole production contract, and it declares `additionalProperties: false` ZERO times, so it is a floor for absences and never a ceiling. The verdict rests on the corpus-wide zero, not on the spec alone. source
extensibility-webhooks-pushunknown — 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 wiresolve-to-noSame measurement as reporting-webhooks and the same two caveats: `webhook` is 0 across the help centre, www and the spec, and the spec's 20 paths are all request/response with no callbacks. Polling is the only documented shape. The scope point matters here: order lifecycle events are not Nory's subject at all - the record's own scope_overrides retire order-capture, delivery and digital-ordering as settled non-surfaces, and 'Sales and forecasts' (art. 7845382) says Nory takes 'the restaurants net sales figure' from the EPOS, so there is no created/modified/paid/voided/refunded stream inside Nory to push. Two addresses are not two instruments: middleware.nory.ai/swagger.json returns the byte-identical 18,020-byte file. source
extensibility-webhook-reliabilityunknown — 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/4resolve-to-noConditional on a mechanism that does not exist: with `webhook` at 0 across all three corpora there is nothing to sign, retry or replay, and no signature header, retry policy or event log is documented for any Nory surface. The spec's only security definition is a bearer API key on inbound requests - 'bearerAuth', type apiKey, in header - which is request authentication, not payload signing. Recorded as `no` rather than left conditional because the claim's three components are each separately absent from the published record, not merely unmeasured. source
reporting-history-retentionunknown — 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 resolve-to-noThis is a documentation claim and no document meets it. `retention` returns exactly 1 tokenised hit across the 127 help articles and it is about TRAINING - the train-the-trainer article listing 'Low retention' as a problem with large group sessions. No article, legal page or spec field states a historical window for transaction-level detail, states what happens to older data, or mentions an archive-retrieval charge. What the corpus does document is the opposite end: the labour screen's comparison controls are week-on-week and 'Use the monthly view for LFL comparisons', and the counting articles describe weekly or monthly count cycles, with no stated horizon at all. A silence about retention cannot be read as 24 months, so the claim is not met. source
reporting-nl-queryunknown — 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 intoresolve-to-partialA named natural-language assistant exists, is shipped, and is documented - but on one module rather than on sales and labour data. 'Ask Nory' appears in the help centre as a working control inside the reviews product: 'Click on Ask Nory and share the improvement ideas with the in-store teams!' (art. 12959993). The Customer Reviews Assistant page describes what it does - 'Our AI analyses every review across all platforms to identify patterns, detect sentiment shifts, and surface operational issues. Ask Nory then summarises key trends and provides actionable recommendations.' - and says the analysis reaches operational data: 'Nory's AI connects to your operational data (labour, inventory, processes) and tells you why they're unhappy and exactly how to fix it.' What is NOT documented is the claim's core: an ad-hoc question against the operator's own sales and labour data returning a figure or chart. `natural language` occurs once across 332 www pages and 0 times in the help centre. The other five assistants (Scheduling, Ordering, Compliance, Payroll, Invoicing) are workflow automations, not a query surface, and 'Next time you need to know how much chicken to order, just ask Nory' is a closing line on a competitor-comparison page, not documented behaviour. source
multi-location-new-store-templateunknown — 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 standingresolve-to-no`clone` occurs 0 times across the 127 help articles, 332 www pages and the API spec, and no article describes provisioning a location by copying another. 'Your settings in Nory' is the go-live configuration guide and it is a per-location checklist by construction: 'The previous settings covered are all group wide. The settings under Locations are all specific to each location and need to be set for each location.' Eight location-level sections follow, each set individually. No expected time-to-open is published anywhere. THE POISON: `template` occurs 39 times in the help centre and the API spec has five /templates paths, but both are a different object - stock-COUNT templates ('To save time in your stock take, set up a template !', art. 6607628, with a dedicated article at 10490778) and schedule templates. The spec's template operations are scoped to a branch that already exists: 'Create Template for the branch', 'Get Templates for the branch', 'Apply Template', 'Request Template Recommendation'. source
multi-location-royalty-calculationunknown — 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 &resolve-to-no`royalty` occurs 0 times across the 127 help articles and the API spec. Nory has a franchise concept and the settings article defines exactly what it does: section 4, 'Location & Franchise Groups', exists because 'Location groups can help you to group locations together on the insights pages. This enables you to view sales, labour, and waste data across multiple locations at once.' That is a reporting grouping, and the article's how-to is limited to creating, naming and editing a group's membership. No fee schedule, no royalty basis, and no gross-versus-net-of-discounts configuration appears anywhere - which is consistent with Nory receiving only 'the restaurants net sales figure (Gross sales - VAT - Service charge = Net sales)' from the EPOS, a figure that cannot be re-based on discounts or comps because it never carried them. source
multi-location-royalty-collectionunknown — 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 'Acresolve-to-noConditional on a calculation that does not exist, and separately absent on its own terms: `ACH` and `direct debit` each occur 0 times across the 127 help articles, 332 www pages and the API spec, and no franchisee-visible statement of charges is documented. Nory's only documented money-movement surfaces run the other way and are not royalties - supplier Bills Payable pushed to Xero ('Currently you can create Bills Payable in Xero through Nory', art. 9091692), payroll pay runs, and Nory Capital, which is a financing product ('Access up to £2M in restaurant financing in 24 hours'). Franchise support in the product is the insights grouping described under multi-location-royalty-calculation. source
multi-location-multi-brandunknown — 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 speresolve-to-noThe claim's subject is a terminal, and Nory has none. Its three native apps are enumerated with their jobs - a three-column table whose Description cells read 'Employee self-service: clock in/out, schedules, availability' (Nory Team), 'In-store kiosk app for staff clocking in/out operations' (Nory Kiosk) and 'Inventory management, ordering, transfers' (Nory IM) - plus a browser dashboard. None rings sales, prints a guest receipt or opens a drawer, so separate menus, receipts and branding on shared hardware is not a surface Nory has. `virtual brand` occurs 0 times across all three corpora. Nory does model a brand above locations (the API spec has a /brands/brand path and the settings article groups locations), but that is an org hierarchy for reporting, not two concepts trading through one drawer. Consistent with the record's existing scope_overrides, which retire order-capture for this product. source
multi-location-multi-tax-jurisdictionunknown — 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,resolve-to-noNory's tax handling is purchase-side only and is not per-location. VAT lives on inventory item CATEGORIES mapped to accounting nominal codes: 'These codes help group items by type and apply the correct VAT rate. For instance, code 111 (Drinks) often has a VAT rate of 23%, whereas fresh food may be 0%', and the rule is uniformity, not variation - 'Every category in Nory should have one consistent VAT type (either 0% or 23%), which should match the VAT type assigned to its corresponding nominal code in Xero.' On the sales side Nory computes no tax at all; it receives a figure with tax already removed - 'Nory takes the restaurants net sales figure (Gross sales - VAT - Service charge = Net sales)'. This also answers the open question the prior pass left: the doubt was whether 'Your settings in Nory' is a complete enumeration, and the verdict no longer depends on that, because the Xero article positively describes the only VAT mechanism Nory has and it is a two-value purchase attribute rather than a jurisdiction engine with per-location rates or exemptions. source
hardware-selfpour-scalesunknown — 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 Suresolve-to-no`flow meter`, `tap wall`, `pour spout`, `self-pour`, `draught` and `beverage hardware` each occur 0 times across the 127 help articles, 332 www pages and the API spec. Nory integrates no hardware of any kind: the Supported Devices article's entire hardware surface is consumer phones, tablets and browsers - 'iPhone 6s or newer, iPad (5th gen) or newer', 'Android version 7.0 (Nougat) or later', 'Chromebooks can access the Nory web app through the Chrome browser' - and the only peripheral it names is a device camera for document scanning. The claim also requires pours to post to a POS tab, and Nory is not the POS. THE POISON: `scale` returns 5 tokenised help-centre hits and every one is the magnitude sense - 'understanding your segment, scale, and operating model', 'Protect margin as sales scale', 'the scale of your waste relative to sales', 'permission boundaries that can scale across multiple teams' - not a weighing scale. source
extensibility-bi-data-warehouseunknown — 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 aresolve-to-no`S3`, `SFTP`, `Snowflake`, `BigQuery`, `Redshift`, `Looker`, `Power BI` and `scheduled export` each occur 0 times across the 127 help articles, 332 www pages and the API spec, and `data warehouse` returns 2 www hits, both inside one podcast transcript where a guest describes building his own at a former employer. Every documented export is a manual, UI-bound file download - the HR export drawer, the timecard export, the Cash-and-stock report exports - and the one programmatic destination Nory documents is an accounting system, not a warehouse: 'Currently you can create Bills Payable in Xero through Nory.' The published API is a pull contract of 20 REST paths with no bulk or transaction-level extract among them. `Tableau` appears once, in a blog listing it alongside Nory as a category of tool, which is a comparison, not an integration. source
extensibility-custom-fields-scriptingunknown — 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, sresolve-to-no`custom field` occurs 0 times across the 127 help articles, 332 www pages and the API spec, and no vendor-hosted scripting or rules-authoring surface is documented. The configurable surface is a fixed, numbered list: eight company-wide sections (Scheduling & Shifts, Time & Attendance, Labour, Location & Franchise Groups, Onboarding, Notifications, Categories, Accounting) and eight location-level ones (Branch contact information, Service category, Labour targets, Opening hours, Holidays and events, Holiday settings, Departments/Positions/Stations, Clock in). What Nory calls custom is instance creation inside those fixed types - custom shift types, custom absence types, departments, positions and stations - each added by 'click the + button in the top right corner of each tile'. The nearest thing to authored logic is the Compliance Assistant's per-location overrides, and those are bounded to toggling a supplied rule, switching it between hard and soft, or changing its threshold. source
extensibility-middleware-compatibilityunknown — 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, MyOrderBoxresolve-to-noMeasured at both publishers. NORY'S OWN: `Deliverect`, `Chowly`, `Otter`, `Checkmate` and `ItsaCheckmate` each occur 0 times across the 127 help articles, 332 www pages and the API spec, and the integrations page runs the other way entirely - its POS partners are Toast, Square, Clover, Revel, PixelPoint, Oracle Micros, Epos Now, Innova, Captiva, Lightspeed, Vita Mojo, SumUp, Tevalis, Zonal and My Order Box, with not one aggregation platform among them. THE MIDDLEWARE VENDOR'S OWN: Deliverect's 1,000-article English help corpus contains `Nory` zero times when tokenised, against Lightspeed 269, Revel 144, Square 70, Epos Now 35, Clover 28 and Toast 26 as controls - and the poison is worth publishing, because a naive case-insensitive substring search returns 4 hits there and all four are the fragment `noRY` inside base64 query strings. Structurally this is settled anyway: aggregation middleware writes orders into a POS, and this record's own scope_overrides retire order-capture, delivery and digital-ordering for Nory as settled non-surfaces. source
reliability-sync-conflict-handlingunknown — 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 fresolve-to-noThere is no network partition for two devices to diverge across. Supported Devices & Technical Requirements states it in prose - 'An active internet connection is required at all times for all Nory apps and web access. The apps do not support offline mode.' - and repeats it as a closed table whose 'Internet required' row reads 'Always Always Always Always' across the Employee App, Kiosk App, Management App and browser, which is every client the article defines. Every write therefore goes to the cloud synchronously, and the corpus documents no divergence handling to go with it: `conflict` and `partition` each occur 0 times across the 127 help articles and the API spec. The FAQ's single mention of 'offline data caching' in the native apps is noted in labor-offline-time-punch and describes no behaviour; it is a browser-versus-app contrast, not a partition model. Resolves the prior pass's `not determinable` by treating the document's normative statement and its table as the finding rather than the FAQ aside. source

Sources

Every URL this record cites. 73 in total.