Vendors / Bar, brewery & taproom

Arryved

dossier live

Claims in scope
224
Scored
224
Assessed
221
Unknown
3
Not applicable
90
Values challenged
24

Identity

Owner
Fullsteam. Arryved is listed as a brand on Fullsteam's hospitality portfolio page alongside Maestro, Silverware, Club Prophet and The Flybook (https://www.fullsteam.com/hospitality), and the relationship is corroborated operationally: the privacy policy routes data-subject requests to compliance@fullsteam.com / Fullsteam Operations LLC, the responsible-disclosure page routes vulnerability reports to ResponsibleDisclosure@fullsteam.com, chargeback notices come from payments.chargebacks@fullsteam.com, and the PCI programme prescribes "FullsteamPay Hosted Payments". No acquisition announcement or date was located on either newsroom, so the acquisition date is unknown. Fullsteam self-describes as founded 2018, HQ Auburn AL and Atlanta GA, 50+ acquisitions, 2,100+ employees, 60,000+ customers across all brands — those are Fullsteam-wide, NOT Arryved figures. Arryved itself acquired SimpleCircle in March 2024, which became Arryved Brewery Management (https://arryved.com/media-center/).
Founded
Early 2017. Arryved's own about page describes founders who "love craft beer" building in taprooms for six months before commercial launch in 2017. Founder names, HQ city and employee count are not disclosed on the site (https://arryved.com/company/about-arryved/).
Scale
unknown. Arryved publishes no customer count, location count, ARR or market-share figure on its site or in its media center. Fullsteam's 60,000+ customer figure spans ~50 acquired brands and must not be attributed to Arryved.
Who it is for
Single-location and small-group craft beverage producers with on-premise service: breweries, brewpubs, taprooms, cideries, wineries, distilleries, plus food halls, music venues and food trucks. Published self-serve pricing covers 1-9 devices at one location; 10+ devices or 2+ locations is quote-only (https://arryved.com/pricing/), which is a fair read of where the product's self-serve ICP ends. The Portal models hierarchy as location > venue (revenue centre) with no above-store or franchise construct documented.
Site
https://arryved.com/

Pricing

transparency: partial · unit: mixed · processor lock-in: yes

Software
Published: "Starting at $99.99/month" for 1-9 devices at a single location, stated to include the cloud software, mobile devices, online-ordering tools, software integrations, phone and email support 7 days/week, unlimited on-demand training, and onboarded setup with a dedicated representative. "Contact us for a quote" for 10+ devices or 2+ locations. No tier names, no per-additional-device increment, and no module pricing (Digital Menus, loyalty, KDS, brewery management, web solutions) are published; the Digital Menus quickstart guide confirms that module is "an additional subscription service" priced through sales.
Card processing
One published rate, conditional on one program; otherwise quote-only. Arryved's Dual Pricing Overview states that "the Dual Pricing program eliminates the fluctuation of the per transaction fees and offers a flat rate of 3.99%", said to cover interchange, association fees and per-transaction costs (https://support.arryved.com/portal/en/kb/articles/dual-pricing-overview). That is the only card rate Arryved publishes anywhere, and it applies only to merchants who adopt Dual Pricing. Neither the pricing page nor the Arryved Pay product page publishes a rate for anyone else. Arryved's own Arryved Pay Fee Structure article names eleven fee lines — Terminal Lease Fee, Card Monthly Fees, Card Brand Network Fees, Full Settlement Fee, PCI/Breach Protection, Accelerated Funding, Chargeback Fee, Terminal Purchase Fee, Terminal Sales Tax, Shipping & Handling, Arryved Platform Fee — and then states that "the actual dollar amounts of the fees are not mentioned in this guide because they may fluctuate over time or vary depending on your processing volume and business operations." This matters more than usual because the MSA makes Arryved's own processing mandatory, so the unpublished number is the real price of the product.
Contract
12-month Initial Term, auto-renewing for successive 12-month terms unless either party gives written notice "no less than ninety (90) days prior to the end of the then current term" (MSA §8.1). Company separately reserves the right to terminate at any time on thirty days' notice (§8.3). Source: https://arryved.com/master-services-agreement/
Early termination
Yes — liquidated damages. MSA §8.4: "Client shall forfeit all pre-paid amounts for Fees, and for those arrangements in which the Fees are not paid in advance, Client shall pay Company an amount equal to the monthly Fee multiplied by the number of months remaining in the Term." Fees are separately adjustable at Company's discretion: §5.1, "Company may adjust Fees at any time with thirty (30) days' notice."

API posture

public API: none

Cost to integrate
Not published for ISVs. There is no partner programme page (arryved.com/integration-partners/become-a-partner/ 404s), no certification path and no listing fee. The only published integration-adjacent commercial term is a customer-referral bounty of "a one-time payment of five hundred dollars ($500)" per referral that signs, launches and processes within 12 months (https://arryved.com/referral-terms-and-conditions/), which is not partner or API pricing.
Webhooks
None documented. No webhook, event-stream or callback documentation exists publicly. The one publicly described outbound pipe is a scheduled one-way batch push to a single hard-wired partner endpoint: Yellow Dog's setup guide says "Arryved Service sync application pushes sales data to the Yellow Dog API at a frequency determined by Arryved Service" — the hourly default in that guide belongs to Yellow Dog's own sync applications, not to Arryved (https://help.yellowdogsoftware.com/arryved). Sales data only, not order lifecycle events, and not to a customer-supplied endpoint.
Data export on exit
Contractually granted but time-boxed and request-based. MSA §4.4: "Upon termination or expiration of this Agreement, or at Client's request, Company shall provide access to all Client Data in a commonly used machine-readable format... Company shall provide access to the Client Data for no more than thirty (30) days after the termination or expiration of the Agreement. After this thirty (30) day period, Company may delete Client Data." Some self-serve export does exist in-product — the Insider Members page exports the full member list with contact info, point balance and visit history, and Rosie can deliver any Portal report as PDF, XLS or CSV — but Rosie schedules must be set up by Arryved Support or an Implementation Manager, and there is no self-serve bulk export of the transaction record. Client retains rights to Client Data, but Company owns Anonymized Data, Feedback and Professional Service Deliverables and takes a broad licence including AI model improvement.
Notes
Arryved does have an API — Yellow Dog's integrator documentation instructs the merchant to fetch an "API URL" and "API Key" from Arryved Service and describes a one-way push of sales transaction data — but it is a partner-provisioned key, not a product. There is no developer portal (developer.arryved.com does not resolve), no reference, no auth model, no rate limits, no sandbox, and none of the twelve top-level categories in the public support knowledge base is a developer or API section. The entire published integration surface is nine named partners: Fresh KDS (KDS), QuickBooks and Shogo (accounting), 7shifts and Schedulefly (scheduling), MarginEdge (invoice/cost), BarTrack (draft monitoring), Ekos (brewery ERP), Yellow Dog (inventory), plus eCard Systems (physical gift cards) in the support KB and TapWyse for memberships. Absent from both enumerated lists: DoorDash, Uber Eats, Grubhub, and every middleware layer (Deliverect, Chowly, Otter, Checkmate, UrbanPiper). Arryved is not in DoorDash's 2026 Preferred Integration Partner cohort. For an integration-first buyer this remains the single most consequential finding in the dossier.

Capabilities

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

Order capture & FOH workflow

Yes

Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.

order-capture-floor-plan-editor

MAP Screen Overview: "For each of your Venues, you can create a Floor Plan in your Arryved Portal for a visual representation of your table layout in that Venue." The Venue KB carries a dedicated "Tables & Floor Plans" section covering floor plan design, table configuration and table numbering. https://support.arryved.com/portal/en/kb/articles/using-the-floor-map · retrieved 2026-08-02

B
Yes

Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.

order-capture-seat-level

Seat Numbers are configured per Venue; as items are added "you can update the seat number next to each item", and they are "helpful for splitting a check later or delivering the correct food and beverage to the correct person." Table numbers are selected from the Venue's configured list. https://support.arryved.com/portal/en/kb/articles/assigning-seats-to-guests · retrieved 2026-08-02

B
Yes

Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.

order-capture-coursing-hold-fire

"Add all the items to the order screen, place the entrees on hold, and send the other items through." Held items show red; Send quick-fires all held items, or Change un-holds selected items. No named course levels — holds are per-item. https://support.arryved.com/portal/en/kb/articles/holding-items · retrieved 2026-08-02

B
Yes

Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.

order-capture-split-merge

The Running Tab Window documents splitting, merging, comping and applying gratuity on a tab. Corroborated negatively by the Offline Mode article, which lists "splitting and merging tabs" among the functions unavailable while offline. https://support.arryved.com/portal/en/kb/articles/running-tab-window-overview · retrieved 2026-08-02

B
Yes

Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator

order-capture-bar-tab-preauth

"Your Pre-auth amount is initially set to $20" and "when a tab is opened with a card-on-file, a $20 hold is placed on the card" (the amount is adjustable via Support). "If the final bill is more than the Pre-auth amount, we run an additional authorization when closing the tab to charge for the difference." "For any tabs rolling over to the next day, the pre-auth will automatically drop off after 48 hours if the tab is still open." Unused hold funds reverse in 3-4 business days on average, up to 7-10. https://support.arryved.com/portal/en/kb/articles/pre-authorization-with-arryved-pay · retrieved 2026-08-02 adversarially verified

B
Partial

An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.

order-capture-transfer-audit

A TRANSFER permission exists and transferring without it "requires approval...by someone with the Permission", so transfers are gated and manager-approved. Shortfall: no report or log dedicated to transfer history is documented — the Altered Tab Forensics report covers voided payments and removed items, not tab ownership changes. https://support.arryved.com/portal/en/kb/articles/labor-roles-permissions · retrieved 2026-08-02

B
Yes

Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.

order-capture-native-handheld

Hardware KB category "POS Devices — POS handhelds and tablets that house Arryved Service"; the product is documented and marketed as mobile-first, with staff carrying handhelds to the guest. https://support.arryved.com/portal/en/kb/arryved-support/hardware · retrieved 2026-08-02

B
Yes

With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.

order-capture-offline-order-entry

Offline Mode Overview documents continuing to complete transactions and work tabs with no internet, syncing offline actions on return. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

B
Partial

Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator

order-capture-qr-same-check

OpenTab is documented with a "How To Claim A Tab In OpenTab" article and an "OpenTab Order Flow" article, so guest phone orders attach to a tab object. Shortfall: the documentation does not state that a guest can claim or add to a tab a server opened on the same check, and OpenTab orders are explicitly not received while the POS is in Offline Mode. https://support.arryved.com/portal/en/kb/arryved-support/opentab/opentab-overview · retrieved 2026-08-02

B
No

Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator

order-capture-kiosk-first-party

The Hardware knowledge base enumerates the whole catalogue in eight categories — POS Devices, Card Readers, Printers, Print Controller, Cash Drawer, Barcode Scanners, Your Network, Epson KDS — with no kiosk, no kiosk enclosure and no kiosk application. Arryved positions self-service as QR ordering on the guest’s own phone (OpenTab), and publishes no ADA or accessibility conformance statement. https://support.arryved.com/portal/en/kb/arryved-support/hardware · retrieved 2026-08-02 adversarially verified

B
No

Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator

order-capture-throttling

Positive absence by in-document enumeration. The Pickup Modality guide closes the set of time controls: 'Select one of the three choices below to offer Pickup Time Options to your guests' - NONE, FREEFORM ('This enables a textbox for guests to hand-type a desired time for pickup'), OPTION ('This allows you to create a list of pickup times for your guests to choose from... Use the plus sign to add time options and hand-type them in'). The slots are hand-typed strings with no per-slot capacity, and the Delivery modality repeats the same three choices. The Online Store Settings article enumerates every store-wide setting and the only volume lever is per-cart, not per-slot: 'Max Number Of Items Per Order: Enter a number here to limit the total number of items a guest can add to their cart... The guest isn't restricted from placing another order after they've checked out.' No automatic quote-time extension exists anywhere; the documented remedy for excess load is manually turning the whole store off. https://support.arryved.com/portal/en/kb/articles/pickup-modality-setup-guide · retrieved 2026-09-04

B
Partial

Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.

order-capture-scheduled-orders

Future-timed online orders exist: the Pickup modality offers Pickup Time Options of NONE, FREEFORM (guest types a desired time) or OPTION (a merchant-typed list of pickup times, 15-30 minute intervals suggested), and the ORDER screen can be filtered to a chosen time to see what must be ready then. Shortfalls: no per-channel lead-time rule, no computed fire time (orders print on receipt via Print Controller and the Epson KDS 'does not indicate pick-up times from Arryved Online orders'), and times are free text rather than validated slots. https://support.arryved.com/portal/en/kb/articles/pickup-modality-setup-guide · retrieved 2026-09-03 adversarially verified

B
No

Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.

order-capture-catering

CLAIM: distinct catering order flow with quotes, deposits, balance-due tracking. VERDICT: no. EVIDENCE: the order-type set is a closed enumeration the vendor declares closed. Arryved Online Order Modality Overview: "There are 5 Order Modalities you can offer in your Arryved Online Store: Pickup Curbside Delivery Ship It In Person" and under Limitations "You cannot rename the Order Modalities nor create custom ones." and "The Shipping Fee and Delivery Fee are one set price each (of your choice). You can't create variable fees depending on cart totals." (https://support.arryved.com/portal/en/kb/articles/arryved-online-order-modality-overview). The same enumeration already carries digital-catering-portal = no. On the POS side the only order-level money mechanics documented are tabs, pre-auth, splits and partial payments ("You'll create partial payments if a guest wants to divide the check by a certain dollar amount", https://support.arryved.com/portal/en/kb/articles/partial-payments) - a tender split, not a deposit/balance-due ledger. The prior note's "Deposits & Distribution" is keg/container deposit handling (deposit-screen-in-arryved-service, ABM Keg Tool), not event deposits. SURFACE (new 2026-09-16): the Zoho Desk portal's anonymous JSON API, https://support.arryved.com/portal/api/kbArticles?portalId=<portal id from the KB page>&from=N&limit=50, lists 539 articles across 4 root categories (Product Support 400, Onboarding 42, Release Notes 68, remainder not returned under a root filter); per-article /portal/api/kbArticles/<id> returned 510 bodies at 200 and 29 at 403 (all 29 are Arryved Insider loyalty or Arryved View digital-menu articles; their listing summaries are readable). Href fixpoint over the 510 bodies found 64 article slugs not in the listing; articleByPermalink probes: 37 resolve (200) to already-listed articles under old slugs, 5 are 403 (all card-reader pairing/troubleshooting: pairing-a-new-bluetooth-swiper-ble, bbpos-chipper-credit-card-reader-initial-setup, bluetooth-swiper-ble-troubleshooting, sw, troubleshootingbbposchipper), 22 are 404, and a nonsense-slug control is 404. The listing is therefore a census of anonymous-readable bodies plus 34 gated articles whose topics are known. The portal's own search API (/portal/api/kbArticles/search?searchStr=) was also queried. BOUND/CONTROLS: tokenised, word-boundary, case-insensitive over all 539 listed articles (bodies, or summaries for the 29 gated): \bcater\w* 0, "balance due" 0, \bquotes?\b 3 matches in 1 article (POISON: a ShipCompliant "quote number" for alcohol-compliance lookups, not a sales quote); portal search API searchStr=catering returned {"data":[]}. On arryved.com's WP corpus (267 posts + 125 pages via wp-json; post bodies fetched as HTML because REST content is empty - a page-builder hole) every "catering" hit is the English verb ("catering to older generations") or a staff bio. The 34 gated articles are loyalty, digital-menu-designer and card-reader topics. Retrieved 2026-09-16. https://support.arryved.com/portal/en/kb/articles/arryved-online-order-modality-overview · retrieved 2026-09-16 adversarially verified

B
No

Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator

order-capture-order-ready-signal

There is no marketplace to signal: Arryved integrates with no third-party delivery marketplace, and the ORDER Screen Overview enumerates the screen functions — display tickets from Arryved Service, Arryved Online and OpenTab, colour status, filter by pickup or delivery time, mark complete, reprint — with no outbound ready signal. Do not upgrade this on the Fresh KDS announcement: the customisable order-received and order-ready texts described there are guest SMS delivered by the partner, not a state push back to a marketplace. https://support.arryved.com/portal/en/kb/articles/order-screen-overview · retrieved 2026-08-02 adversarially verified

B
Yes

Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.

order-capture-void-comp-controls

Named per-role permissions COMP, ORDER ITEM VOID and AUTH CANCEL. A manager "can apply Comps without needing approval or...use their login code to approve a Comp for someone else"; ORDER ITEM VOID gates voiding items from placed orders and the Trashcan tool. The Altered Tab Forensics report records voided payments and orders with items removed. https://support.arryved.com/portal/en/kb/articles/labor-roles-permissions · retrieved 2026-08-02

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

Enhanced Modifiers states plainly: "Modifiers are not nested, meaning you can't modify a modifier." This is positive documented absence, not an inference. https://support.arryved.com/portal/en/kb/articles/new-enhanced-modifiers · retrieved 2026-08-02

B
Yes

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

"If you're applying a Modifier Group to a specific Size of the Item, it will now apply to that size on your Arryved Online and OpenTab Menus, too!" Modifier groups bind to a specific Unit Size of an inventory item, and Unit Sizes carry their own prices. https://support.arryved.com/portal/en/kb/articles/new-enhanced-modifiers · retrieved 2026-08-02

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

Positive absence by field enumeration plus a documented workaround. The Item Modifier page's fields are enumerated 1-8 in full - State, Modifier Group(s), Modifier Name, Search Hints, Ticket Display Name, Type, Price, Restrict to Category - and the price is a single flat upcharge with no tier or multiplier: '7) Price : If this Item Modifier has an upcharge, enter the price of the upcharge here.' The Type field is inert: '6) Type: At this time, only the Temperature Type has an action. The other Types are not in use.' The token 'multiplier' occurs zero times in the corpus. Arryved's own Best Practices For BYO Pizza guide (separate article) prescribes dummy modifiers rather than tiers: 'Create "1st Half" and "2nd Half" Item Modifiers... then use the Add/No/Sub actions with another Item Modifier to specify what they want on that half.' Light/regular/extra with a per-tier multiplier would have to be modelled as separate flat-priced modifiers. https://support.arryved.com/portal/en/kb/articles/item-modifiers · retrieved 2026-09-04

B
Partial

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

"Only Required Modifier Groups will auto-prompt the Modifier Screen" — a forced-choice prompt exists, and modifiers can carry upcharges. Shortfall: this is a required-selection prompt bound to the item, not a configurable suggestive-sell or attach-rate engine, and no upsell prompt is documented for Arryved Online or OpenTab checkout. https://support.arryved.com/portal/en/kb/articles/new-enhanced-modifiers · retrieved 2026-08-02

B
Partial

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

The INV screen's Kick buttons "make the Item unavailable and remove it from menus", and kicked items grey out in Arryved Service. Shortfall: the article does not state that a kick propagates to the Arryved Online store or OpenTab menus, and no article documents cross-channel 86 propagation. https://support.arryved.com/portal/en/kb/articles/managing · retrieved 2026-08-02

B
Partial

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

Items tracked by quantity show a count on the INV screen that staff can adjust, and setting the quantity to 0 depletes the item. Shortfall: the documentation does not describe automatic removal at zero without staff action, nor any scheduled auto-restore at the next business day. https://support.arryved.com/portal/en/kb/articles/managing · retrieved 2026-08-02

B
Yes

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

The Venue configuration KB carries a scheduled-menus section covering dayparting and menu scheduling; menus are built per Venue and each Venue "can have their own configuration and their own menus". https://support.arryved.com/portal/en/kb/arryved-support/portal/venue/scheduled-menus · retrieved 2026-08-02

B
Partial

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

Arryved Online has its own Menus and Inventory sections separate from the in-venue menus, so channel-specific menus exist. Shortfall: no documentation of channel-specific prices for the same item — Unit Size prices appear to be the single source, and no price-book or channel-markup construct is described. https://support.arryved.com/portal/en/kb/arryved-support/arryved-online-ordering-store/menus-arryved-online · retrieved 2026-08-02

B
Partial

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

Item-level dual pricing ships and prints: two prices per item (current prices become Cash Prices, with Standard Prices set 4-5% higher) and the printed bill shows both the Non-cash Total and the Cash Total. Shortfall: the article is scoped to the POS app and states its prerequisites as "Android 9 OS or higher" and "Arryved Service v1.24+" — nothing documents behaviour in Arryved Online or OpenTab, there is no kiosk channel to be consistent with, and the statement that the displayed menu price is the card price ("Menus list everything in card prices, including sales tax") appears only on a marketing blog. https://support.arryved.com/portal/en/kb/articles/dual-pricing-overview · retrieved 2026-08-02 adversarially verified

B
Partial

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

Arryved Brewery Management's Production module lets brewers "Create Recipes and schedule Batches", and POS inventory items carry costs (cloning an item copies "unit sizes, costs, attributes"). Shortfall: recipe-to-menu-item ingredient linkage for food is not documented on the POS side — ABM recipes are brewhouse production recipes, and ABM is a separately onboarded module. https://support.arryved.com/portal/en/kb/arryved-support/arryved-brewery-management-abm/production · retrieved 2026-08-02

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

The support KB's integration list enumerates nine partners — Fresh KDS, Shogo, QuickBooks, BarTrack, Ekos, Yellow Dog, MarginEdge, eCard Systems, 7shifts — and the vendor's own integration-partners page enumerates the same set plus Schedulefly. No delivery marketplace and no menu-syndication middleware appears on either list, so there is no channel to push a menu to. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations · retrieved 2026-08-02

B

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

MSA §6.6: "Unless otherwise stated in an applicable Order Form, Client must be enrolled in and processing payments through Company's integrated payments processing platform within sixty (60) days of the Effective Date of this Agreement." https://arryved.com/master-services-agreement/ · retrieved 2026-08-02

B
Partial

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

payments-published-rates

One rate is published in first-party documentation: "The Dual Pricing program eliminates the fluctuation of the per transaction fees and offers a flat rate of 3.99%", stated to cover interchange, association fees and per-transaction costs. Shortfall: it applies only to merchants who adopt Dual Pricing. Standard processing stays quote-only — the Arryved Pay Fee Structure article names eleven fee lines and then says "the actual dollar amounts of the fees are not mentioned in this guide because they may fluctuate over time or vary depending on your processing volume and business operations", and the pricing page publishes no rate. https://support.arryved.com/portal/en/kb/articles/dual-pricing-overview · retrieved 2026-08-02 adversarially verified

B
Yes

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

Native and documented. Structured as a cash discount: "Dual Pricing is NOT surcharging", applies to credit and debit, and the printed bill shows both the Non-cash Total and the Cash Total. https://support.arryved.com/portal/en/kb/articles/dual-pricing-overview · retrieved 2026-08-02 adversarially verified

B
Partial

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

The compliance posture is stated — dual pricing is a cash discount rather than a surcharge, said to be permitted in all 50 states for credit and debit, and both totals are disclosed on the printed bill. Shortfall: no configurable guardrails are documented (no cap enforcement, no card-brand rate ceiling, no debit exclusion switch, no state-by-state rule table), because the product avoids surcharging rather than governing it. https://support.arryved.com/portal/en/kb/articles/dual-pricing-overview · retrieved 2026-08-02

B
Yes

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

payments-emv-nfc

Two documented readers: tDynamo, "the white EMV card reader with tap, dip, swipe, and digital wallets", and DynaFlex II Go, "the black EMV reader with tap, dip, swipe, and digital wallets". https://support.arryved.com/portal/en/kb/arryved-support/hardware/credit-card-swipers · retrieved 2026-08-02

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

The hardware guide makes a separate reader mandatory per device and forbids sourcing one elsewhere: 'Arryved currently offers the MagTek DynaFlex II Go card reader that supports tap, dip, swipe, and digital wallets all in one! You'll need one card reader per POS device' and, under Sourcing Your Own Hardware, 'Card Readers must be purchased from the Arryved Catalog because they are approved by and encrypted with our payment processor. No exceptions.' The POS device itself is a commodity Samsung Android tablet or handheld, so the acceptance path is always device plus paired MagTek reader; contactless is real but happens at the reader - 'Tap: Present an EMV-supported card or an Apple Pay, or Google Pay digital wallet to the card reader for a tap.' Disclosed hole: 9 help-centre articles return a deterministic 403 to us - chargeback-faqs, dual-pricing-processing-faqs, pairing-a-new-bluetooth-swiper-ble, bbpos-chipper-credit-card-reader-initial-setup, bluetooth-swiper-ble-troubleshooting, troubleshootingbbposchipper, freshkds-app-settings-overview, accessing-the-arryved-view-designer, sw - all legacy-reader, KDS or view-designer titles, none softPOS-shaped. https://support.arryved.com/portal/en/kb/articles/things-to-consider-when-making-your-first-hardware-order-9-5-2022-1 · retrieved 2026-09-04

B
Yes

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

Payment is taken on the handheld with a paired portable reader — the product is documented as mobile-first with staff carrying the POS and reader to the guest — and OpenTab additionally lets the guest pay from their own phone. https://support.arryved.com/portal/en/kb/arryved-support/hardware/credit-card-swipers · retrieved 2026-08-02

B
Partial

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

OpenTab is documented as guests placing orders and viewing digital menus from their smartphones, with tab claiming. Shortfall: the retrieved documentation does not describe a guest paying off a server-opened check by QR, nor tip-on-QR-pay behaviour, so scan-to-pay on an existing check is unconfirmed. https://support.arryved.com/portal/en/kb/arryved-support/opentab/opentab-overview · retrieved 2026-08-02

B
Yes

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

The Portal's Tab Management Tool lets a manager "comp, void, move tabs to a different date, or close and add a tip to tabs" — post-close tip adjustment from the back office. A TIP PAY labor-role permission gates tip handling at the POS. https://support.arryved.com/portal/en/kb/articles/tab-management-tool-22-11-2024 · retrieved 2026-08-02

B
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

Three tipping models are documented as configurable options: "Tip Pooling: Tip sharing by day or by shift" and "Individual Tip Outs: Employees keep the tips they have earned. No tip pooling." Pooling by shift allocates on labour hours — "tip pool segments are created throughout the day by clock in and out times" — surfaced through the Tips By Labor Hours report, with the End of Day Tool as "your all-in-one solution to managing your daily tip pool and nightly cash deposit", including adjusting tipped hours and adding cash tips to the pool. Per-employee allocation lands in a Payroll Report and an Employee Time Card With Tips report. Limit worth knowing: allocation is hours-based; no role-percentage or points weighting is documented. https://support.arryved.com/portal/en/kb/arryved-onboarding/tips · retrieved 2026-08-02 adversarially verified

B
Partial

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

Cards are captured offline and verified on reconnect: "Credit or debit card transactions are verified for funds after you exit Offline Mode and return online. Some payments may fail." Shortfall: no offline limits of any kind are documented — no floor limit, no per-transaction cap, no cumulative exposure cap, no card-type restriction — and the stored batch is time-boxed: "You must sync your Offline Mode actions within 72 hours of the time of the initial transaction." Manual card entry and gift-card payment do not work offline at all. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02 adversarially verified

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

The merchant carries the loss. "Credit or debit card transactions are verified for funds after you exit Offline Mode and return online. Some payments may fail." No guarantee, floor limit or vendor-absorbed liability is offered. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

B
Yes

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

Native gift cards: a Portal Gift Card Tool for creating cards and updating balances covering physical and digital cards, a "How To Pay With Gift Cards In Arryved Service" article, Digital Gift Cards in the Arryved Online store, a monthly Gift Card Liability summary in Rosie, and eCard Systems as the physical-card supplier. https://support.arryved.com/portal/en/kb/articles/creating-new-gift-cards-or-accounts · retrieved 2026-08-02

B
Partial

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

payments-house-accounts

House Accounts exist as a documented use of the Gift Card Tool: 'Use the Tool to create House Accounts, too!' An account 'works like a Credit Card, it has a limit and a balance', goods consumed raise the balance to the limit and payments lower it; the tool searches by name, email or phone, adjusts balances with debit/credit/set actions and an adjustment note, and accounts appear on the Gift Card Liability report. Shortfalls: no periodic statement or invoice generation, no per-account terms, and the construct is a gift-card record redeemed with the gift-card tender rather than a distinct on-account payment type; creation requires a Portal Super Admin. https://support.arryved.com/portal/en/kb/articles/creating-new-gift-cards-or-accounts · retrieved 2026-09-03 adversarially verified

B
Yes

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

"Arryved Service can accept multiple payment types to pay a single tab", documented via the How To Complete A Partial Payment article alongside gift card, cash, written check and manual payment methods. https://support.arryved.com/portal/en/kb/arryved-support/venyu/payment-options · retrieved 2026-08-02

B
Yes

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

Refunds are issued from Arryved Portal via Tab Search against a tab's history, gated by a REFUND labor-role permission; AUTH CANCEL gates voiding paid tabs and ORDER ITEM VOID gates removing placed items. https://support.arryved.com/portal/en/kb/articles/refund · retrieved 2026-08-02

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

The documented process is email, not product. Notices come from payments.chargebacks@fullsteam.com and "you'll submit your documentation by replying to the email"; questions go to a Fullsteam phone line. No in-product dispute queue, evidence upload or deadline tracker is described. https://support.arryved.com/portal/en/kb/articles/chargeback-overview-arryved-pay · retrieved 2026-08-02

B
Partial

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

payments-payout-timing

Timing is published: deposits land "2-3 business days after the original transaction date (2 days with accelerated funding, 3 days standard)". Shortfall: two-day funding is chargeable — Accelerated Funding appears as an optional monthly fee — and the arryved.com/products/arryved-pay/ "next-day deposits" claim is not supported by the support documentation. https://support.arryved.com/portal/en/kb/articles/how-to-reconcile-your-arryved-pay-bank-deposits · retrieved 2026-08-02

B
Partial

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

PCI DSS v4 is named, compliance is validated through SecurityMetrics, merchants complete an SAQ and scans, "FullsteamPay Hosted Payments" is the prescribed processing method, and $100,000 breach protection is bundled. Shortfall: no validated P2PE solution or listing is named, tokenization is not described, and "if you fail to become compliant, you're charged an additional monthly fee" — the burden sits with the merchant. https://support.arryved.com/portal/en/kb/articles/pci-compliance-overview-arryved-pay · retrieved 2026-08-02

B

Kitchen & production

Yes

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

"The Peripheral Matrix is used to route orders to your Peripherals based on the Item Category and the Venue they were ordered from." Expanded ticket types Stations 1-4 plus the Printer Override feature let individual inventory items be routed to a named station; printers and KDS screens are both bound to ticket types through the same matrix. https://support.arryved.com/portal/en/kb/articles/expanded-printers-setup-guide · retrieved 2026-08-02

B
Yes

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

"The 'Default Expo Printers' combine all items that were routed to the Kitchen and Stations 1-4 Peripherals into one single ticket." https://support.arryved.com/portal/en/kb/articles/expanded-printers-setup-guide · retrieved 2026-08-02

B
Partial

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

Firing is real but lives on the POS, not the kitchen screen: items are held on the order screen and fired with Send. Shortfall: the Epson KDS documentation describes ticket display, custom layouts and time tracking and does not describe course levels, course firing from the KDS, or a coursed-ticket view. https://support.arryved.com/portal/en/kb/articles/holding-items · retrieved 2026-08-02

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

Positive absence on both limbs. The Inventory Item page's field list is closed - 'This is the bare minimum you need to create an Inventory Item; everything else is optional', then 'The rest of the fields on the New Inventory Item page are optional, but often necessary! This section will show you how and when to use the rest of the fields available' - followed by every one of them (State, Guest Menu Name, Button Override, Printer Override, Printer Order, Menus, Conversion Type, Availability By Size, Cash Price, COGs, Quantity in Stock, Conversion ID, SKU, Pricing, CRV, Loyalty Cost, Max # per Guest Order, Attributes, Modifiers, Display Information, Item Tags). There is no prep, cook or hold time among them, so there is nothing to stagger from. The KDS side is order-level colour escalation only: 'Priority Time: Set the amount of time an order can remain active before it gets marked as Prioritized. Rush Time: Set the amount of time an order can remain active before it gets marked as Rush' - per order, never per item. Items reach the kitchen when staff tap Send. https://support.arryved.com/portal/en/kb/articles/building-inventory-items · retrieved 2026-09-04

B
Partial

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

kitchen-bump-bar-hardware

Bump bars are documented with models on both KDS paths: the Epson KDS Hardware Checklist names the Bematech KB1700 (one per managed monitor) and a full Bump Bar Guide covers its buttons, scroll and recall modes; the Fresh KDS Hardware Overview names the Logic KB1700 from the Arryved catalog for screens out of reach. Shortfall against the claim's 'in addition to touchscreen interaction': the native Epson KDS states 'Touch screen monitors are not supported', so touch is available only through the Fresh KDS partner subscription (21.5in and 10.5in touchscreens). https://support.arryved.com/portal/en/kb/articles/kds-hardware · retrieved 2026-09-03 adversarially verified

B
Partial

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

kitchen-all-day-counts

A cross-ticket aggregate view exists but it is an Epson feature Arryved disclaims and it must be hand-configured per item. 'Summary Tile: This adds a "Summary Tile" to your KDS screen. This will look at all of your orders and compile them together so your staff can see organized order information at a glance. This requires further configuration to work properly.' Shortfall: it is not menu-driven - every item must be typed into the Summary Tile Filter by hand and kept in sync manually ('NOTE: Name must match the Short Name of the inventory item in Arryved Portal exactly, including the size if there is one'); Arryved disowns the filter ('This is optional and not directly associated with Arryved's KDS offering. Use this Epson Guide for more information.'); no modifier-level aggregation is documented; and it exists only on the Epson KDS, not on the Fresh KDS integration or on printed tickets. https://support.arryved.com/portal/en/kb/articles/customizing-the-kds-display · retrieved 2026-09-04

B
Partial

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

There is a documented time-based escalation, but on the POS ORDER screen rather than the KDS: tickets show green when new and turn red after five minutes. Shortfall: the threshold is not documented as configurable, there is no escalation beyond a colour change, and no comparable alerting is documented for the Epson KDS. https://support.arryved.com/portal/en/kb/articles/order-screen-overview · retrieved 2026-08-02

B
Partial

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

Automatic failover to a designated backup is a first-class per-peripheral field, but the no-ticket-loss limb is not met. How To Enter Your Merchant Peripherals: 'Fallback To - Fallback is a failsafe method. If a print job fails or devices that route orders to this Peripheral go into Offline Mode, the ticket will print (fallback) to another printer of choice. Select a fallback printer. It can't be a KDS device. A KDS device, however, can have a fallback printer.' A separate 'Mirror To' field gives unconditional duplication on top of it. Shortfall: the documented trigger is a failed print job or the routing POS devices entering Offline Mode rather than a dead KDS screen as such; and a whole-network outage is not covered at all - 'Printers can't go into Offline Mode, so if your network is down, tickets and receipts won't print', with pending jobs queuing and needing a Flush Tasks sweep afterwards. https://support.arryved.com/portal/en/kb/articles/adding-a-printer-to-the-portal-for-arryved-service · retrieved 2026-09-04

B
Partial

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

kitchen-offline-operation

Printing survives an internet outage: printing works if "your Internal Network's router is functioning", subject to successful gateway and printer pings. Shortfall: KDS behaviour during an outage is not documented anywhere, and OpenTab orders are explicitly not received while offline, so the digital kitchen path is unverified. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

B
Partial

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

kitchen-recall-refire

The ORDER screen's More button exposes order details with reprint. Shortfall: reprinting a ticket is not recalling a bumped ticket back onto a KDS and refiring it, and no recall or refire function is documented for the Epson KDS. https://support.arryved.com/portal/en/kb/articles/order-screen-overview · retrieved 2026-08-02

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

Positive absence by enumeration of the only two documented behaviours for a re-sent order. 'Consider Orders Unique: If this box is checked, anytime an order is placed, it will create a new order tile on the display. If this box is unchecked, and an order is placed on a tab that has an order still in circulation, it will be added to the same order tile on the monitor.' Neither branch flags what changed. Tile colour cannot be driven by order content - 'You can customize color options for your Order Tiles, but color coding based on item types ordered is not available' (worded 'is not supported' in the KDS Overview) - and the link is one-way: 'Arryved sends orders to the KDS, but the KDS does not send anything back to Arryved.' On the printed path the documented behaviour is a plain full reprint, not a change ticket: with the 'Print when orders are updated' Location Preference enabled, 'a ticket will reprint anytime a change is made to an order'. https://support.arryved.com/portal/en/kb/articles/kds-configuration-utility-settings · retrieved 2026-09-04

B
Partial

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

Through the Fresh KDS partner only. Fresh KDS colour-codes ticket times and its Fresh Tools portal carries 'reporting', which arryved.com's FreshKDS page describes as Kitchen Performance Analytics tracking prep times, bottlenecks and throughput. Shortfalls: it is a separate subscription billed by Fresh KDS; the native Epson KDS 'does not send anything back to Arryved', so no ticket-time or station-time report exists in Arryved Portal's reporting sections; no percentile, daypart or channel slicing and no CSV/API export is documented for the kitchen timings. https://support.arryved.com/portal/en/kb/articles/freshkds-integration-overview · retrieved 2026-09-03 adversarially verified

B

Delivery, dispatch & third-party channels

No

Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).

delivery-driver-roster

The Delivery Modality Setup Guide is the canonical delivery document and covers exactly two things: zone enforcement (radius, postal codes, or none) and creating a delivery fee. No driver record, driver assignment, driver bank or cash-out appears in it or anywhere else in the Arryved Online documentation. https://support.arryved.com/portal/en/kb/articles/delivery-modality-set-up-guide · retrieved 2026-08-02

B
Partial

Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator

delivery-zones-polygon

Zones exist in two forms: "Deliver to a radius from a designated center point" with an address and mileage, and "Deliver to one or more valid postal codes". Shortfall: no drawn-polygon or arbitrary-boundary zone is offered; the enumerated choices are radius, postal-code list, or "No delivery zone enforcements". https://support.arryved.com/portal/en/kb/articles/delivery-modality-set-up-guide · retrieved 2026-08-02

B
No

Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.

delivery-zone-pricing

The delivery fee is modelled as a single Inventory Item synced to the Arryved Online store. The three enumerated zone options govern serviceability only — radius, postal codes, or none — and carry no per-zone fee, distance band or minimum-order tier. https://support.arryved.com/portal/en/kb/articles/delivery-modality-set-up-guide · retrieved 2026-08-02

B
Partial

Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.

delivery-address-validation

Guests see a map of the delivery radius or the list of serviceable zip codes and receive warnings if their address falls outside it, so serviceability is checked at checkout. Shortfall: that is a zone test, not address normalisation or geocoded validation, and no address-verification provider is named. https://support.arryved.com/portal/en/kb/articles/delivery-modality-set-up-guide · retrieved 2026-08-02

B
No

Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.

delivery-daas-dispatch

No delivery-as-a-service courier is available. Both enumerated partner lists — the vendor site (Fresh KDS, QuickBooks, 7shifts, MarginEdge, Shogo, BarTrack, Ekos, Yellow Dog, Schedulefly) and the support KB (same set plus eCard Systems) — contain no DoorDash Drive, Uber Direct, Relay, Nash or equivalent. https://arryved.com/integration-partners/ · retrieved 2026-08-02

B
No

Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator

delivery-3p-direct-integration

The vendor integration directory enumerates its entire catalogue as nine partners — Fresh KDS, QuickBooks, 7shifts, MarginEdge, Shogo, BarTrack, Ekos, Yellow Dog, Schedulefly. No DoorDash, Uber Eats or Grubhub, and no middleware (Deliverect, Chowly, Otter, Checkmate, UrbanPiper). The support knowledge base integration list agrees. https://arryved.com/integration-partners/ · retrieved 2026-08-02 adversarially verified

B
No

Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.

delivery-3p-injection

With no marketplace integration on either enumerated partner list, there is no path by which a third-party order could be injected into a tab. The ORDER screen article enumerates its ticket sources as Arryved Service, Arryved Online and OpenTab only. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations · retrieved 2026-08-02

B
No

Menu, pricing, modifiers, and photos publish from the POS master menu out to connected third-party marketplaces, including channel-specific price markups, without maintaining a separate menu in each portal.

delivery-menu-push

No marketplace or middleware appears on either enumerated integration list, so there is no third-party menu to publish to. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations · retrieved 2026-08-02

B
No

Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).

delivery-86-sync

No marketplace integration exists on either enumerated list, so an INV screen kick has no third-party channel to propagate to. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations · retrieved 2026-08-02

B
No

Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.

delivery-store-pause

Pausing a store on DoorDash, Uber Eats or Grubhub from the POS presupposes an integration with them; neither enumerated partner list contains one. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations · retrieved 2026-08-02

B
No

Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator

delivery-3p-reconciliation

No marketplace integration exists on either enumerated list, and the Portal's reporting sections contain no third-party payout or commission reconciliation report. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations · retrieved 2026-08-02

B
No

Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator

delivery-injection-error-visibility

There is no third-party order injection to monitor: neither enumerated partner list contains a marketplace or middleware, and no integration health, failed-order queue or error dashboard is documented. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations · retrieved 2026-08-02

B
No

Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.

delivery-tracking-page

Positive absence by enumeration plus the vendor's own manual workaround. The Delivery Modality setup is a closed seven-step list - online Venue, Delivery Instructions, Delivery Minimum, Delivery Fee, Delivery Time Options, Delivery Zone, Review and save Settings - with no guest status page, tracking link or driver state; the only guest-facing communication is a static text box ('use this textbox next to "Delivery Instructions" to write some helpful info that guests will read just after they place their delivery order online', example: 'Delivery may take 35-50 minutes'). The one SMS touchpoint in checkout belongs to a partner and is not tracking ('You may text instead of calling - This checkbox is used for the Fresh KDS Integration that offers an SMS feature'). Arryved's own Routing Deliveries guide shows there is no driver state in the product at all: deliveries are routed by exporting orders to a spreadsheet and pasting them into Google My Maps - 'we'll importing the delivery orders as dynamic waypoints into Google Maps. From there you will be able to route the deliveries yourself or pass the way-pointed map along to the driver.' https://support.arryved.com/portal/en/kb/articles/delivery-modality-set-up-guide · retrieved 2026-09-04

B

Digital ordering & guest-facing channels

Yes

Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.

digital-first-party-web

Arryved Online is a first-party e-commerce store documented across seven sections — overview, inventory, menus, order modalities, store settings, order management and digital gift cards — supporting "pickup, curbside, delivery, and shipping". https://support.arryved.com/portal/en/kb/arryved-support/arryved-online-ordering-store · retrieved 2026-08-02

B
Yes

The web/app ordering menu is generated from the same POS menu record as in-store — one item edit propagates to all first-party digital channels without a separate digital menu build.

digital-menu-single-source

Menus and modifiers flow from the same Portal inventory: a modifier group applied to a specific Unit Size "will now apply to that size on your Arryved Online and OpenTab Menus, too", and Arryved Online has an Inventory section that syncs Portal items into the store. https://support.arryved.com/portal/en/kb/articles/new-enhanced-modifiers · retrieved 2026-08-02

B
Partial

Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.

digital-account-saved-payment

A card can be stored on an Insider member's account, and card-on-file tabs are core to the POS. Shortfall: saved payment is tied to the Insider loyalty account rather than a general Arryved Online guest account, and no guest-account/saved-card flow is documented for the online store on its own. https://support.arryved.com/portal/en/kb/articles/store-a-new-card-on-an-insider-account · retrieved 2026-08-02

B
Partial

Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator

digital-upsell-engine

Operator-configured up-sell and cross-sell placements do exist, but only in Arryved Web Solutions (the acquired Craftpeak WooCommerce shop), not in Arryved Online. How To Link Products Together: “Products can be Related to each other in three ways: Up-Sells, Cross-Sells or by having the same tags or categories… Go to WooCommerce > Products and select the product on which you’d like to show an up-sell or cross-sell… Cross-sells are products that you promote in the cart, based on the current product… Cross-sells (user defined) show on the cart page.” Shortfalls, both material: (1) the surface is the separately-sold Web Solutions website product configured in the WooCommerce admin, while the POS-native store is Arryved Online, whose Online Store Settings guide (“Use this guide to learn about each Setting and how to customize them”) enumerates every store-wide setting and contains no suggestion, add-on or recommendation control; (2) no attach-rate or suggestion-performance reporting is documented anywhere — the linked-products placements are static merchandising, and Related Products is category/tag matching, not personalisation from order history. https://support.arryved.com/portal/en/kb/articles/linked-products · retrieved 2026-09-04

B
Partial

Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.

digital-scheduled-pacing

Guest-selectable pickup time slots exist (OPTION mode lists merchant-defined times; FREEFORM accepts any typed time). Shortfalls: no capacity limit per slot, no order or item throttling, and no automatic closing of a saturated slot is documented anywhere in the Online Store Settings or modality guides; the merchant's only pacing lever is the fixed list of times. https://support.arryved.com/portal/en/kb/articles/pickup-modality-setup-guide · retrieved 2026-09-03 adversarially verified

B
Yes

Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.

digital-fulfillment-modes

Five documented modalities, each with its own setup guide: Pickup, Curbside, In Person, Delivery and Ship It (DTC shipping with a configurable shipping fee). https://support.arryved.com/portal/en/kb/arryved-support/arryved-online-ordering-store/online-order-modalities · retrieved 2026-08-02

B
Yes

Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.

digital-qr-table

OpenTab "empowers your guests to place orders and view digital menus right from their smartphones", documented with an overview, setup guide, order flow, tab claiming and service-model considerations. https://support.arryved.com/portal/en/kb/arryved-support/opentab · retrieved 2026-08-02

B
No

Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.

digital-group-ordering

CLAIM: shareable group-order link where multiple participants add their own items/pay. VERDICT: no. EVIDENCE: commerce.arryved.com (the Arryved Online storefront SPA; every path incl. a nonsense path returns the same 965-byte shell, so it is a catch-all and only the bundle is evidence): main bundle https://commerce.arryved.com/main.bundle.975df0c6778ac8f72628.js (1,444,629 bytes) carries a webpack chunk map of 64 lazy chunks; all 64 fetched at 200 (1,607,437 bytes), so the app is held COMPLETE (0 of 64 missing). Its route table enumerates the storefront screens: chooseModality, pickupDetails, curbsideDetails, deliveryDetails, shippingDetails, served (In Person), menus, itemDetail, reviewOrder, payment, thankYou, ageVerification, and ~35 /opentab/* screens (scan, startOrView, claim, claimEnterPhoneNumber, runningTab, pay, receipt ...). The five storefront modalities match the KB's closed list ("There are 5 Order Modalities you can offer in your Arryved Online Store: Pickup Curbside Delivery Ship It In Person", https://support.arryved.com/portal/en/kb/articles/arryved-online-order-modality-overview). No route, screen or string implements a shared or multi-participant cart. The only guest-side multi-order concept is OpenTab, and it is strictly one guest per tab keyed to that guest's card: "Please enter the details of the card you used initially, so we can find your tab", "If you see your tab, tap it to review and confirm it's yours", "Multiple tabs cannot use the same payment info", "We'll send a 6-digit code so we can link your device to your tab" (all string literals in the bundle). BOUND: the complete storefront bundle (65 of 65 files) plus its route enumeration, and the 539-article KB API census (0 hits for "group order(ing)", "shared cart", "join the tab", "share the tab"; the 34 gated KB articles are Insider loyalty, Arryved View and card-reader topics, none ordering). CONTROLS (tokenised, word-boundary, case-insensitive over the 1.6 MB bundle): "group order" 0, groupOrder 0, shareable 0, invite 0, participant 0, "friends?" 0, "each person" 0. POISON found and excluded: \bgroup\b 10 = Google Analytics content_group1-5 and CSS box-ordinal-group; \bshare\b 1 = "Preview Only - Do NOT Share URL" (menu-preview banner); \bsplit\b 170 = tab-status enum SPLIT (staff-side tab split) and String.split; \bjoin\b 158 = Array.join; \beveryone\b 7 = age-gate enum EVERYONE_ALL; \btogether\b 1 = React SuspenseList revealOrder. SURFACE (new 2026-09-16): crt.sh certificate listing for %.arryved.com (https://crt.sh/?q=%25.arryved.com&output=json) named ~300 hosts; probed with a nonsense-path control per host. Retrieved 2026-09-16. https://commerce.arryved.com/main.bundle.975df0c6778ac8f72628.js · retrieved 2026-09-16 adversarially verified

B
No

Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator

digital-catering-portal

Positive absence by a closed enumeration that the vendor explicitly declares closed. Arryved Online Order Modality Overview: “There are 5 Order Modalities you can offer in your Arryved Online Store: Pickup / Curbside / Delivery / Ship It / In Person”, and under Limitations: “You cannot rename the Order Modalities nor create custom ones.” The same Limitations block forecloses the commercial mechanics a catering flow needs: “The Shipping Fee and Delivery Fee are one set price each (of your choice). You can’t create variable fees depending on cart totals.” No catering menu, minimum, lead-time rule, quote, proposal, deposit or house-account/ACH term appears in the Arryved Online documentation, and the word “catering” occurs nowhere in the 546-article help centre (its only near-hits are the phrase “a loyalty program catered to your brand”). https://support.arryved.com/portal/en/kb/articles/arryved-online-order-modality-overview · retrieved 2026-09-04

B
No

Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator

digital-voice-ai-phone

The order-origination surface is enumerated and telephony is not in it. ORDER Screen Overview: “The ORDER screen shows a list of digital tickets for each order placed through Arryved Service, Arryved Online, or OpenTab.” Three channels, none of them a phone line. The claim’s partner limb fails on the other enumerated list: the vendor integration directory is nine named partners (Fresh KDS, QuickBooks, 7shifts, MarginEdge, Shogo, BarTrack, Ekos, Yellow Dog, Schedulefly, plus eCard Systems and TapWyse), with no voice-AI or telephony vendor among them, and no such partner is claimed on arryved.com. The strings “voice order”, “phone order”, “call-in order” and “artificial intelligence” return zero hits across the entire 546-article help centre. https://support.arryved.com/portal/en/kb/articles/order-screen-overview · retrieved 2026-09-04

B
No

Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator

digital-google-order

327th, NEW SURFACE - the vendor's own MARKETING SITE, which no prior pass had censused (the 315th-322nd used the Zoho KB and the app bundles only). arryved.com is WordPress; its sitemap at https://arryved.com/sitemap.xml lists 380 URLs and ALL 380 were fetched today at 200 (375 with real bodies, 5 sub-5 KB redirect stubs), giving 3,704,288 chars of tag-stripped text. IMPORTANT METHOD NOTE for later passes: do NOT use this site's WP REST API as the corpus - it is a Beaver Builder site and 286 of its 392 REST items return an EMPTY `content.rendered` (median length 0), a textbook page-builder hole that would manufacture zeros. The rendered HTML is the only valid corpus. CONTROLS over all 375 bodies, tokenised, word-boundary, case-insensitive: 'Order with Google' 0, 'Google Business' 0, 'Google Order' 0, 'order button' 0. The only Google integration the site advertises anywhere is map directions on a beverage finder ('Quickly get retail location information and Google directions'), i.e. a link OUT to Google, not an ordering link provisioned INTO it. Combined with the two COMPLETE first-party app censuses already on record - commerce.arryved.com's storefront (main bundle + all 64 of its 64 lazy chunks, 0 missing, whose route table is the closed list of 5 order modalities Pickup/Curbside/Delivery/Ship It/In Person) and portal.arryved.com/v2/main.js (no chunk loader, 206-entry navigation enumeration) - the vendor neither ships nor claims Order with Google. Retrieved 2026-09-18. https://arryved.com/sitemap.xml · retrieved 2026-09-18 adversarially verified

B
No

Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.

digital-apple-business-connect

327th, NEW SURFACE: the first full census of arryved.com itself - 380/380 sitemap URLs fetched today, 375 real bodies, 3,704,288 chars (see the digital-google-order cell for the method, including the Beaver Builder REST hole that makes the WP API unusable as a corpus here). CONTROLS, tokenised: 'Apple Business' 0, 'Apple Maps' 0, 'Apple Business Connect' 0 across the whole site. This closes the last unexamined first-party surface: the 319th/322nd had already shown \bapple\b to be 4 POISON hits in portal.arryved.com/v2/main.js (the CSS vendor-prefix probe '-apple-trailing-word') with the storefront bundle held complete at 64/64 chunks, and the 539-article Zoho Desk KB census carries nothing either. The vendor's published direct-ordering channels are its own storefront's five modalities and QR OpenTab; an Apple Maps 'Order Food' action is absent from every surface Arryved publishes. Retrieved 2026-09-18. https://arryved.com/sitemap.xml · retrieved 2026-09-18 adversarially verified

B
Partial

Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.

digital-loyalty-attach

Insider members are identified in Arryved Service so points accrue on in-venue tabs, and offers are redeemed from the member's Insider Wallet. Shortfall: no article documents identifying a member or accruing points on an Arryved Online or OpenTab order, so loyalty attach on the digital channel is unconfirmed. https://support.arryved.com/portal/en/kb/articles/how-to-identify-members-in-service · retrieved 2026-08-02

B
Partial

Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.

digital-promo-parity

Discount Codes are a documented Insider Perk alongside Offers and Rewards, so codes exist. Shortfall: the documentation does not state that a code or offer redeems identically at the POS and in the Arryved Online store, and comps are configured separately under Location Settings. https://support.arryved.com/portal/en/kb/arryved-support/loyalty/insider-perks/discount-codes · retrieved 2026-08-02

B
Partial

Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator

digital-guest-data-ownership

MSA §4.4 obliges Arryved to "provide access to all Client Data in a commonly used machine-readable format" on request, and the Insider Member Report and Customer Contact List give the merchant guest contact data directly. Shortfall: access is capped at 30 days post-termination, Company owns Anonymized Data outright, and Client grants Company a broad licence including AI model improvement. https://arryved.com/master-services-agreement/ · retrieved 2026-08-02

B
Partial

Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.

digital-checkout-pci-sca

E-commerce checkout is inside the PCI programme: "As of March 31, 2025, PCI DSS V4 has a new requirement for merchants using Ecommerce", with FullsteamPay Hosted Payments as the prescribed method. Shortfall: no 3-D Secure, SCA or strong-authentication support is documented, and the compliance obligation and non-compliance fee fall on the merchant. https://support.arryved.com/portal/en/kb/articles/pci-compliance-overview-arryved-pay · retrieved 2026-08-02

B
Partial

Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator

digital-surcharge-transparency

In-venue disclosure is explicit — the printed bill shows both the Non-cash Total and the Cash Total before the guest chooses. Shortfall: the article is scoped to Arryved Service and says nothing about how or whether dual pricing is disclosed in the Arryved Online store or OpenTab checkout. https://support.arryved.com/portal/en/kb/articles/dual-pricing-overview · retrieved 2026-08-02

B

Guest data, loyalty & marketing

Yes

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

An Insider Member is a real profile: the member report carries "a full list of your Insider Members with their contact info, Loyalty Point balance, visit history", with per-member stats, a Wallet holding offers and points, a card that can be stored on the account, and identification at the POS in Arryved Service. https://support.arryved.com/portal/en/kb/articles/how-to-get-your-insider-member-report · retrieved 2026-08-02

B
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

There are no marketplace orders to attach. ORDER Screen Overview: “The ORDER screen shows a list of digital tickets for each order placed through Arryved Service, Arryved Online, or OpenTab.” Those three are the entire set of order sources, and this record already carries ten grade-B cells resting on the same finding (delivery-3p-direct-integration, delivery-3p-injection, delivery-store-pause and others): neither enumerated partner list — the arryved.com integration directory nor the support KB integration section — contains DoorDash, Uber Eats or Grubhub, or any middleware (Deliverect, Chowly, Otter, Checkmate, UrbanPiper). “DoorDash”, “Uber Eats” and “Grubhub” return zero hits across all 546 help-centre articles. With no marketplace channel, no marketplace ticket can carry a guest identity into an Insider profile. https://support.arryved.com/portal/en/kb/articles/order-screen-overview · retrieved 2026-09-04

B
Partial

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

Accrual is spend-based and fixed at "1 point per 1¢ spent", excluding tax, tips, donations, comps and gift-card payments. Shortfall: the ratio cannot be modified, and there is no visit-based, item-based, category-multiplier or bonus-event accrual model — only manual balance adjustment. https://support.arryved.com/portal/en/kb/articles/loyalty-points-overview · retrieved 2026-08-02

B
No

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

guest-loyalty-tiers

The Insider model is enumerated in full and is flat. Arryved Insider Overview (For Merchants) enumerates the membership axis as exactly two options — “Public Membership” (“Allows anyone and everyone to become an Insider Member”) and “Private Membership” (“Guests won’t be able to sign up themselves, you’ll create Memberships in your Arryved Portal manually”) — and the earn axis as a single immutable rate: “Insider Members accrue Loyalty Points at the rate of 1 point per 1¢ spent. This ratio can’t be changed, but you can manually adjust the total points a Member has, individually.” The four enumerated Perk types (Loyalty Points, Rewards, Offers, Discount Codes) contain no status level, and no rolling-window promotion or demotion rule exists. Not contradicted by Web Solutions: the separate Arryved Web Solutions shop does offer “membership tiers that offer different levels of benefits”, but those are manually assigned or purchased benefit levels in a WooCommerce storefront, not spend-driven status, and that article states “Members and Memberships do not sync with your Arryved POS.” https://support.arryved.com/portal/en/kb/articles/what-is-arryved-insider · retrieved 2026-09-04

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

This claim is about publication, and the document that promises to be exhaustive is silent on loyalty. Offline Mode Overview: “This article tells you everything you need to know about Arryved’s Offline Mode”, then enumerates the Limitations item by item — devices don’t communicate, 72-hour sync window, “Employees can’t clock in or out when offline”, no OpenTab order receipt, “Splitting and Merging tabs can’t be done in Offline Mode”, “Manual card entry is not supported when in Offline Mode”, “Gift cards can’t be sold or used for payment”, no Portal-to-Service updates, order timestamps set at sync. The sibling stored-value feature is named explicitly and loyalty is never named — neither Insider lookup, nor Point accrual, nor Offer/Reward redemption — in this article, in How To Exit Offline Mode And Sync Devices, or in either checkpoint-file recovery article. “Insider” returns zero hits in all three Offline Mode articles, and no Insider article mentions offline behaviour. Staff cannot be trained on what is not written. https://support.arryved.com/portal/en/kb/articles/offline-mode-25-4-2019 · retrieved 2026-09-04

B
Partial

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

guest-loyalty-targeted-offers

Offers are targeted on one axis: "If there is a Loyalty Cost, the Offer will only email out to your Members who have enough Points." Shortfall: point balance is the only documented targeting criterion — no visit recency, spend band, product affinity or custom segment is available. https://support.arryved.com/portal/en/kb/articles/insider-faqs · retrieved 2026-08-02

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

The complete audience-selection mechanism is two states and neither is a lifecycle segment. How To Create And Send Insider Offers walks “each field on the Offer creation page” and the only targeting control over people (as opposed to menu items) is Point Cost: “If a Point Cost is entered here, this Offer only emails out to your Members who currently have enough Loyalty Points to redeem it. If the field is left blank, the Offer is sent to all of your Members.” Everything else on the enumerated page — Offer Type, Short Name, Name, Description, Offer Targets/Exclusions (Item Types, Unit Sizes, Inventory Items), (Max) Dollar Value of Discount, Minimum Spend, Expires Morning Of, Max Total Saves Allowed, Maximum Saves Per Member, Subject Line, Email Body Text, Target Activation Time — targets items or limits the offer, not the audience. No recency/frequency/monetary scoring, no new/regular/at-risk/lapsed/VIP construct and no saved audience appears on the Insider Members page, whose per-member dashboard (Visits, Avg. Spend, Avg. # of Guests, Avg. Tip, Avg. Duration, Visit Distribution, Purchase Distribution, last 10 visits) is per-person analytics with no segment builder — and its own list-level search is out of service: “The Member Search button at the top is NOT in use at this time.” https://support.arryved.com/portal/en/kb/articles/how-to-create-insider-offers · retrieved 2026-09-04

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

The vendor answers the automation question directly, and the answer is no. Arryved Insider FAQs: “Will active Offers auto-send to Members after they’ve earned enough Points? No. The Offer only sends to Members who have enough Points at the time it was sent.” Offers are one-shot manual sends: How To Create And Send Insider Offers requires a “Target Activation Time” picked from a calendar and enumerates the offer lifecycle states as “Preview / Queued / Active / Exhausted / Expired / Retired” — a queue for one scheduled send, not a standing trigger. No birthday, first-visit thank-you or lapsed win-back campaign exists anywhere in the Insider documentation; the only automatic email the program sends is a points notice (“You can set up your Insider program to send emails to Insider Members when they accumulate Loyalty Points at your establishment”), which is a balance notification, not a lifecycle campaign. https://support.arryved.com/portal/en/kb/articles/insider-faqs · retrieved 2026-09-04

B
Partial

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

Email is native: offers are ones "you create in your Arryved Portal and email out to your Members in the form of a digital coupon", and sign-ups are verified by email. Shortfall: no SMS or push channel is documented for Insider — push messaging appears only in the TapWyse membership partnership, a third-party app. https://support.arryved.com/portal/en/kb/articles/insider-faqs · retrieved 2026-08-02

B
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

There is no platform SMS path to register. Insider marketing is email and only email: “You’ll create unique Offers in your Arryved Portal and send them to your Insider Members via email”, the required fields include a “Subject Line” and “Email Body Text”, and the Limitations state the consequence plainly — “If your Members unsubscribe from Insider Offer emails, they won’t be able to receive Offers at all.” The strings “10DLC”, “A2P”, “campaign registry” and “Twilio” appear in none of the 546 help-centre articles. The only guest SMS anywhere in the corpus belongs to a named partner and is transactional, not marketing: the Pickup and Curbside modality guides describe a checkbox that “is used for the Fresh KDS Integration that offers an SMS feature”, i.e. Fresh KDS sends order-status texts under its own registration, making the partner the subject. https://support.arryved.com/portal/en/kb/articles/how-to-create-insider-offers · retrieved 2026-09-04

B
Partial

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

guest-loyalty-campaign-attribution

Redemption is tied to real check totals, but only in aggregate across all offers. The Insider Activity Report (Arryved Portal → Reporting → Statistics) reports per Member: “Total spend / Total visits / Number of tabs with a redeemed Reward or Offer / Total spend on tabs with a redeemed Reward or Offer / Total discounts in Offers / Total Discounts in Rewards / Current Point balance / Lifetime Point balance”. Per-offer counting exists on the send side — an Offer capped by “Max Total Saves Allowed” enters the state “Exhausted… once it reaches its max” — and the member dashboard’s Current Wallet table names the individual Offer with its Issued, State and Redemption Date, alongside a last-10-visits table carrying Check Size. Shortfalls: nothing rolls those up per campaign — the check-total column lumps every Reward and Offer together and cannot separate one offer from another; there is no sends/opens/saves/redemptions funnel for a given Offer; and no incremental or control-group measure is published, so a redeeming regular is indistinguishable from an incremental visit. https://support.arryved.com/portal/en/kb/articles/what-is-arryved-insider · retrieved 2026-09-04

B
Partial

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

Self-serve and free: a Super Admin presses Get Report on the Insider Members page and the file is emailed to them; "the report can only be sent in a .CSV format", carrying first and last name, email, phone, Visits, Last Visit, Avg Spend, Balance and Lifetime points. Shortfall: this is the guest list plus aggregates, not transaction history — there is no self-serve bulk export of the transaction record, and scheduled report delivery must be configured by Arryved Support or an Implementation Manager. https://support.arryved.com/portal/en/kb/articles/how-to-get-your-insider-member-report · retrieved 2026-08-02 adversarially verified

B
No

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

329th, NEW SURFACE and it is the census the prior passes lacked: a COMPLETE anonymous census of the Arryved Portal operator back office (portal.arryved.com), the app where any feedback/review setting would live. Method: /js/scriptLoader.js is the app's own script table; crawled its 'urls' array to a FIXPOINT (3 rounds, 225 paths, 225/225 HTTP 200, 0 misses, 2,687,045 chars). Nonsense-path control passed: /html/zzz-nope.html and /js/zzz-nope.js both return 404 (18 bytes), so the 200s are real files, not an SPA shell. WHAT IT HOLDS: (1) the full REPORT CATALOGUE in /js/reporting/reportConfiguration.js (109,675 bytes, 174 report ids, 176 display names) - the server-side report list a bundle normally cannot see; the ONLY feedback report in all 174 is superuser-only and retired: `SU_CONSUMER_APP_FEEDBACK: { display: "Arryved Mobile Feedback", description: "Consumer feedback from the Arryved Mobile app. Please note that the Arryved Mobile App was sunset on April 29, 2024." }`. So Arryved's one guest-feedback capture was a consumer app it shut down in 2024, and even then it was a raw report, never a score-routed workflow. (2) the whole Insider/loyalty configuration surface: /html/offers/editLoyalty.html, /html/offers/editOffers.html, /html/offers/pendingSignups.html plus /js/pages/offers/manageOffers.js (106,915 bytes). The offer engine's closed category enumeration is EMAIL | LIFETIME | ONGOING | ONLINE and its trigger/limit fields are Point Cost, Min Check, Max Value, Max/Member, Max Overall, Good Thru, Target Groups/Sizes/Items, Excluded Groups/Sizes/Items, Minimum Spend, Limit Redemption by Days Of Week - points, visits and spend only. No survey send, no score, no routing branch. CONTROLS over the 225-file census, tokenised, word-boundary, case-insensitive, known-positive `the` 1,477: survey 0, rating 0, NPS 0, 'net promoter' 0, stars 0, thumbs 0, sentiment 0, 'service recovery' 0, Yelp 0, TripAdvisor 0, 'Google review' 0, 'star rating' 0, 'low score' 0, 'post-visit' 0, 'how did we do' 0. POISON NAMED: `feedback` scores 8 and every hit is a UI status span ($('<span id="feedback"/>') that prints 'Saving...'/'Saved') or a TODO comment ('to make it easier for Pierre to get user feedback'), plus the sunset-app report above; all 5 `review` hits are chrome ('Please review the offer details, and confirm they are all correct'). RESIDUAL WEAKNESS, stated: 29 of the 539 Zoho KB articles are still customer-gated - re-probed today by id, by permalink (`articleByPermalink`), by /locale/en, /locale/en/attachments and /locale/en/relatedArticles, all 403 FORBIDDEN, and Wayback holds no copy of any of the 29 (CDX for support.arryved.com/* returns 24 rows total, none of them an Insider slug). Those 29 are the Insider/View-Designer set, i.e. member-facing prose about the same program whose operator-side configuration is now held complete and contains no feedback mechanic. Retrieved 2026-09-18. https://portal.arryved.com/js/reporting/reportConfiguration.js · retrieved 2026-09-18 adversarially verified

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

Positive absence by a closed enumeration of every way a member is recognised. How To Identify Insider Members In Arryved Service: “There are four ways to identify a Membership in Arryved Service, Card on file with a stored card. Lookup from the tab naming screen. From the Wallet Query. On the Digital Signature Screen.” All four are a staff-driven card-on-file match or a Name/Email/Phone lookup; none is a scanned pass or barcode. The “Insider Wallet” is not a wallet pass — Wallet Query Overview defines it as an in-product container held by the vendor (“Your Insider Members have an Insider Wallet where their Offers are saved and Loyalty Points are stored… Offers are sent to Members via email. The Member needs to save the Offer from their email for it to appear in their Insider Wallet”), read by staff in Arryved Service. The member-facing alternative is a passwordless web portal at insider.arryved.com, not a pass. “Apple Wallet”, “Google Wallet”, “PassKit” and “.pkpass” return zero hits across all 546 help-centre articles. https://support.arryved.com/portal/en/kb/articles/how-to-identify-members-in-service · retrieved 2026-09-04

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

The documented mechanism for a data-subject request is an email to compliance@fullsteam.com / Fullsteam Operations LLC. No self-serve delete, export or consent-withdrawal tool exists in Arryved Portal for guest privacy rights. https://arryved.com/privacy-policy/ · retrieved 2026-08-02

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

All three things the claim names — offer content, target audience and send timing — are documented as manual operator inputs on a page the vendor enumerates field by field (“Required or not, this section explains how to customize each field on the Offer creation page”). Content: “Short Name… Name… Description* Enter a few words or sentences to describe the full details of this Offer to your Members”, plus a manually chosen type from “7 Offer types” and manually picked Target/Exclusion Item Types, Sizes and Items. Audience: “If a Point Cost is entered here, this Offer only emails out to your Members who currently have enough Loyalty Points to redeem it. If the field is left blank, the Offer is sent to all of your Members.” Timing: “Target Activation Time — Use the calendar to select a date and time you’d like this Offer to be emailed out to your Members”, with a fixed “3-day delay in sending Offers”. The FAQ closes the automated-send door explicitly: “Will active Offers auto-send to Members after they’ve earned enough Points? No.” No AI, ML, predictive or recommendation language appears anywhere in the 546-article help centre or on arryved.com. https://support.arryved.com/portal/en/kb/articles/how-to-create-insider-offers · retrieved 2026-09-04

B
Yes

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

Native stored value: a Portal Gift Card Tool creates cards and updates balances for physical and digital cards, gift cards are a payment option in Arryved Service, digital gift cards are sold through Arryved Online, and Rosie delivers a monthly Gift Card Liability summary. https://support.arryved.com/portal/en/kb/articles/creating-new-gift-cards-or-accounts · retrieved 2026-08-02

B

Labor & workforce

Yes

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

"Arryved Service tracks the hours worked by each Labor Role for every employee who clocks in and out." Employees carry a clock-in code on their profile and clock in on the POS device; hours can be viewed, added and adjusted in the Portal. https://support.arryved.com/portal/en/kb/articles/viewing-hour · retrieved 2026-08-02

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

The Offline Mode overview enumerates what stops working while offline and "employee clock in/out" is the first item on that list. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

B
Yes

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

Fourteen named permissions assigned per labor role: AUTH CANCEL, CASH, COMP, EIGHTY SIX, HARDWARE, HOURS ADJUST, MGR REPORT, ORDER, ORDER ITEM VOID, OWNED TABS ONLY, REFUND, REPORTS, TIP PAY, TRANSFER. Employees inherit them from the role they are logged in under. https://support.arryved.com/portal/en/kb/articles/labor-roles-permissions · retrieved 2026-08-02

B
Partial

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

Overrides are real and code-based: a manager can "use their login code to approve a Comp for someone else", and a transfer without the permission "requires approval...by someone with the Permission". Shortfall: only the Altered Tab Forensics report (voided payments, orders with items removed, Super Admin only) records after-the-fact activity — no general override log naming who approved what and when is documented. https://support.arryved.com/portal/en/kb/articles/labor-roles-permissions · retrieved 2026-08-02

B
No

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

Scheduling is delivered by a partner: 7shifts is documented as "an employee schedule management system" integrated with Arryved, and Schedulefly appears on the vendor partner page. The Portal's Employees section enumerates exactly three areas — View Employees, View Hours, Labor Roles — with no schedule builder. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations/7shifts · retrieved 2026-08-02

B
No

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

Forecasting is the partner's: the KB describes 7shifts as "Employee Management, Scheduling, and Sales Forecasting". Arryved's own Employees section (View Employees, View Hours, Labor Roles) and its enumerated reporting sections contain no demand or labour forecast. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations · retrieved 2026-08-02

B
Partial

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

Via the 7shifts partner integration: Arryved syncs net sales, wages and time punches to 7shifts, whose Sales & Labor dashboard shows 'real-time sales and labor costs plus projections', and the arryved.com partner page sells 'labor as a percentage of sales in real time'. Shortfalls: the figure lives in 7shifts, not on an Arryved manager view or POS; Arryved's own KB states data 'is not updated in real time' and may lag; 7shifts is a separate account billed per location. https://support.arryved.com/portal/en/kb/articles/7shifts-integration-overview-2-7-2025-1 · retrieved 2026-09-03 adversarially verified

B
No

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

Overtime in Arryved is a pay calculation applied after the fact, and the clock-in flow is documented end to end with no gate. How To Clock In: “If your Labor Role is clock-in required, you’ll need to clock in first, then log in with the same code”; “Open Arryved Service on your device. From the log-in screen, enter your clock-in code using the number pad. Tap Clock In. If you work under various Labor Roles, you’ll choose one from the list that appears. If you only have one Labor Role assigned to you, the clock-in will happen automatically. If your clock-in was successful, ‘clocking in as {Labor Role name}’ appears at the bottom of the screen.” No threshold check, warning or block appears in the sequence. The whole overtime surface is retrospective and is not even operator-configurable: the Payroll Report and Employee Time Card articles state “The bottom left of the report will show the Overtime Rule, including the calculation that has been set for your Company’s Location. This is determined by your state laws” (https://support.arryved.com/portal/en/kb/articles/payroll-report-overview, https://support.arryved.com/portal/en/kb/articles/employee-timecard-with-tips-9-5-2022), and the Portal Dashboard only reports “Labor Less Overtime = Total Labor Hours minus Total Overtime Hours (quantity)”. The word “threshold” occurs in zero of the 546 help-centre articles reached by fixpoint href crawl on 2026-09-04, and neither the Location Preferences page (11 enumerated sections: Arryved Cloud, Arryved Insider, Tipping, Donations, Date & Time, Modifiers, Payment, Arryved Service, Printing, Peripheral Matrix, Receipt Layout) nor the Labor Role form carries an overtime setting. https://support.arryved.com/portal/en/kb/articles/clocking-in-and-out-logging-in-and-out-25-4-2019 · retrieved 2026-09-04

B
No

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

The entire labour-rule configuration surface is enumerated and contains no break construct of any kind — no break punch type, no meal-period rule, no jurisdiction set, no attestation prompt, no missed-break flag. How To Create Labor Roles enumerates every field on the role: “Role … Per Hour … Tipped … Clockin Required … Type … Points … Labor Role Permissions … Save / Retire”, with “Check the Clockin Required box to require the employee to clock in and out when working under this Labor Role. This is essential for roles that have an hourly rate of pay. Clocking in and out of Arryved Service tracks their hours worked and calculates their pay accordingly”, and its stated limitations are only “Employees can only be clocked in or logged into Arryved Service under one Labor Role at a time” and one pay rate per role. The two other places a rule could live are enumerated too and do not carry one: Labor Role Permissions (“There are 14 Labor Role Permissions”, https://support.arryved.com/portal/en/kb/articles/labor-roles-permissions) and Location Preferences (11 named sections, none labour, https://support.arryved.com/portal/en/kb/articles/location-preferences-overview). Across all 546 help-centre articles crawled 2026-09-04 there is no meal-break, rest-break, break-rule, missed-break or premium-pay content; the only punch-time prompt documented is Forced Tip Claim at clock-out. Scheduling is routed to 7shifts/Schedulefly, so any compliance feature there is the partner’s, not Arryved’s. https://support.arryved.com/portal/en/kb/articles/labor-roles · retrieved 2026-09-04

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

Native and documented across a 20-article Tips course on the vendor KB that the earlier pass never opened (it sits under arryved-onboarding, not arryved-support). Tip pooling by day: one pool for all tipped employees, divided by hours worked, or weighted by per-labor-role Tip Points (points per hour; formula published) via the Employee Time Card report or the End of Day Tool, which also lets a manager adjust the pool amount and tipped hours. Tip pooling by shift: the Tips By Labor Hours report creates pool segments bookended by clock-in/out times, in a tab-close or an order-timestamp variant; the Tips By Item Type report supports category-based pools such as a kitchen share of food tips. Cash tips enter the pool through a cash tip tab. Caveats: every tip report and Tip Points must be enabled by the Implementation Manager; exact percentage splits are stated to be hard to reproduce with points; reports are meant to be run after batch time the next day. https://support.arryved.com/portal/en/kb/articles/reports-with-tips · retrieved 2026-09-03 adversarially verified

B
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-day, per-employee allocation records exist and download: the End of Day Tip Summary shows each employee's hours, tips earned from the daily pool, and paid versus still owed; the Employee Time Card and Tips By Labor Hours reports show per-employee allocations per day or per shift segment; the Cash Action Log lists declared tips in order performed. Shortfalls: the reports show the pool's distribution but not each employee's contribution into it (tips are not differentiated by type and are pooled from the whole day or segment); the End of Day Tool may be used only once per day and re-entry causes double reporting; changing Tip Points rewrites past tip reports retroactively, which the KB itself warns about, so the trail is not immutable. https://support.arryved.com/portal/en/kb/articles/end-of-day-tip-tool-general-info-9-5-2022 · retrieved 2026-09-03 adversarially verified

B
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

DOWNGRADED FROM PARTIAL. Every element the claim names is absent and the vendor states the decisive one itself. The claim's subject is a payroll export separating cash from charged qualified tips and carrying a Treasury tipped-occupation code for W-2 Box 12 code TP and Box 14b. Arryved runs no payroll and publishes no payroll file format — "payroll export", "payroll provider" and every named payroll processor return zero hits across the 546-article help centre — and the one report actually named Payroll states that the split does not exist in it: "Tips in this report are not differentiated by type (cash, card, gift card)" (Payroll Report Overview), a limitation repeated verbatim on Payroll Report By Shift, Employee Performance, Tips By Item Type and Venue Stats. The nearest partner pipe excludes tips by name: the 7shifts integration article lists "Tips & Tip Pooling" under "It Does Not Support" (https://support.arryved.com/portal/en/kb/articles/7shifts-integration-overview-2-7-2025-1). No Treasury tipped-occupation code, no Box 12 code TP and no Box 14b field appears anywhere in the corpus or in the Reports With Tips enumeration of all 12 tip reports. What does exist is an Employee Tip Collection report with Cash/Check Tips, Card/Other Tips and Total Tips columns per employee (https://support.arryved.com/portal/en/kb/articles/employee-tip-collection-report-overview) — a viewing report, not an export, and not the surface the claim asks about. https://support.arryved.com/portal/en/kb/articles/payroll-report-overview · retrieved 2026-09-04

B
No

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

There is no payroll product. The Portal's Employees section enumerates View Employees, View Hours and Labor Roles; the KB's twelve top-level categories contain no payroll; and payroll-adjacent workflows are routed to the 7shifts integration. https://support.arryved.com/portal/en/kb/arryved-support/portal/employees · retrieved 2026-08-02

B
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

Hours are viewable and adjustable per employee in the Portal, and Rosie can deliver "any Arryved Portal report" on a schedule as PDF, XLS or CSV, so hours data can be got out. Shortfall: no payroll-provider-specific export format is named, and the 7shifts integration is the documented route to payroll systems. https://support.arryved.com/portal/en/kb/articles/rosie-reports-overview · retrieved 2026-08-02

B
No

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

A swap workflow presupposes a schedule, and Arryved has none — the Employees section covers only View Employees, View Hours and Labor Roles, with scheduling delegated to 7shifts or Schedulefly. https://support.arryved.com/portal/en/kb/arryved-support/portal/employees · retrieved 2026-08-02

B
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

Employee attribution exists in reporting: the Daily Sales Report lists closed tabs with employee names, and the Purchase Items Report breaks item sales down by employee, time and location. Shortfall: there is no server scorecard — no per-server average check, items-per-cover, attach rate or ranking view is documented. https://support.arryved.com/portal/en/kb/arryved-support/portal/analytics-reporting/sales · retrieved 2026-08-02

B

Inventory, purchasing & cost control

Partial

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

Recipe and batch costing exists on the brewhouse side: ABM's Production module lets a brewer "Create Recipes and schedule Batches", with an Items & Inventory module behind it, and POS inventory items carry costs. Shortfall: ABM is a separately onboarded module, its recipes are production recipes rather than menu-item bills of material, and no food recipe/BOM builder is documented in Arryved Portal's Inventory section. https://support.arryved.com/portal/en/kb/arryved-support/arryved-brewery-management-abm/production · retrieved 2026-08-02

B
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

"Unit Sizes are how different sizes and prices can be applied to an Inventory Item", and quantity tracking is held per unit size — so a keg-to-pour size hierarchy exists on the sales side. Shortfall: no purchase-unit-to-usage-unit conversion factor, yield percentage or waste allowance is documented. https://support.arryved.com/portal/en/kb/articles/how-to-add-unit-sizes-to-inventory-items · retrieved 2026-08-02

B
No

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

CLAIM: theoretical-vs-actual usage variance report per item for a defined count period. VERDICT: no (weaker than ideal; see caveat). EVIDENCE: Arryved's own blog says this report comes from the partner, not the POS: "Arryved POS' integration with MarginEdge unlocks cost management reports like Controllable P&L, Theoretical vs. Actual Usage, Category Budgets, Sales Performance, and Labor Spend" (https://arryved.com/point-of-sale/4-hidden-gems-your-pos-system-offers-your-staff/; same list on https://arryved.com/integration-partners/marginedge-integration/). The native count tool records a difference as an adjustment, not a usage variance against theoretical depletion. ABM Inventory Counts: "you can update Inventory Counts to account for any overages, shortages, or sales/purchases outside of your ABM Invoices and Purchase Orders" ... "click Diff to update the count ... update the count in the Actual field. Choose one of the 'Assign Difference to' options ... This Inventory Count is logged as an Inventory Adjustment." (https://support.arryved.com/portal/en/kb/articles/abm-inventory-counts). The Portal report ids referenced across all KB bodies (33 distinct report= keys incl. INVENTORY_ITEM_LIST_REPORT, INVENTORY_ITEM_LIST_EXTENDED, UNIT_SIZE_REPORT, DUP_SKU_REPORT, DRAFT_BEER) include no usage/variance report. SURFACE (new 2026-09-16): the Zoho Desk portal's anonymous JSON API, https://support.arryved.com/portal/api/kbArticles?portalId=<portal id from the KB page>&from=N&limit=50, lists 539 articles across 4 root categories (Product Support 400, Onboarding 42, Release Notes 68, remainder not returned under a root filter); per-article /portal/api/kbArticles/<id> returned 510 bodies at 200 and 29 at 403 (all 29 are Arryved Insider loyalty or Arryved View digital-menu articles; their listing summaries are readable). Href fixpoint over the 510 bodies found 64 article slugs not in the listing; articleByPermalink probes: 37 resolve (200) to already-listed articles under old slugs, 5 are 403 (all card-reader pairing/troubleshooting: pairing-a-new-bluetooth-swiper-ble, bbpos-chipper-credit-card-reader-initial-setup, bluetooth-swiper-ble-troubleshooting, sw, troubleshootingbbposchipper), 22 are 404, and a nonsense-slug control is 404. The listing is therefore a census of anonymous-readable bodies plus 34 gated articles whose topics are known. The portal's own search API (/portal/api/kbArticles/search?searchStr=) was also queried. BOUND/CONTROLS over 539 listed articles, tokenised case-insensitive: \btheoretical\b 0, \bvariance\b 0, "actual usage" 0, "usage report" 0; "expected" hits are POISON (cash-drawer "Expected End Amt", PO/transfer "Expected" inventory state). CAVEAT for the verifier: the report-id list is harvested from hrefs, not a published report catalogue, so this rests mainly on the vendor attributing the report to MarginEdge (SpotOn precedent: partner-delivered variance = no). Retrieved 2026-09-16. https://support.arryved.com/portal/en/kb/articles/abm-inventory-counts · retrieved 2026-09-16 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

Items tracked by quantity show a live count on the INV screen that staff can adjust, and "How To Track Inventory Items By Quantity" tracks stock per unit size as items sell. Shortfall: depletion is at the sold-item level; no ingredient-level depletion from a recipe on sale is documented on the POS side. https://support.arryved.com/portal/en/kb/articles/managing · retrieved 2026-08-02

B
Partial

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

Kicking an item on the INV screen makes it unavailable and removes it from menus, and quantity-tracked items can be depleted to zero. Shortfall: propagation of a kick to the Arryved Online store and OpenTab menus is not documented, and there is no documented automatic 86 the moment a tracked count hits zero. https://support.arryved.com/portal/en/kb/articles/managing · retrieved 2026-08-02

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

Real count sessions with retained per-count history exist, but only in the separately-sold ABM brewery module and with no scheduled cycle counts. 'The table on this page shows a history of all your Inventory Counts, each with a unique ID. At any time, you can click on an Inventory Count to view its details' - counts are separate history, not an overwrite. Both a subset count and a full physical count are supported: 'you can add Inventory Counts by individual Items or bulk update Inventory Counts from a specific Inventory Location', with variance captured per line ('click Exact if the count shown is correct. Or, click Diff to update the count... Choose one of the "Assign Difference to" options that speaks to the reason for this count update'), each finalised count logging as an Inventory Adjustment. Shortfall: (1) no scheduled or recurring cycle-count mode is documented - every count is created ad hoc via New Count; (2) it is Arryved Brewery Management, a separately-sold module, not the POS, whose own INV screen is a per-unit-size hard count edited item by item with no count session at all, and 'Modifiers cannot be tracked by quantity, therefore cannot be placed on a count.' https://support.arryved.com/portal/en/kb/articles/abm-inventory-counts · retrieved 2026-09-04

B
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

Counts can be entered on the handheld, but neither scanning nor offline capture is part of counting. On the INV screen of Arryved Service (the Android handheld POS app), 'For Items that are tracked by quantity, tap on the Item to open a window that allows you to adjust the count.' Shortfall: (1) no barcode/QR scan-to-count - the scanner's documented purpose is order entry only, 'Scanning an item's barcode is a quick and easy way to add the item to the order screen', and the scan path ends with the item on the order screen; (2) Offline Mode's documented scope is transactions and tabs, not counting - 'You can continue to complete transactions in Arryved Service while offline... it only remembers the actions placed on that device until devices are later synced when back online' - with no statement that a count entered offline is captured or synced, and a hard 72-hour sync deadline; (3) ABM's Inventory Counts tool is a browser workflow with no offline mode documented. https://support.arryved.com/portal/en/kb/articles/managing · retrieved 2026-09-04

B
No

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

Positive absence stated outright in the vendor's own Limitations section: 'Submitting a Purchase Order in your ABM does not notify your Supplier in any way. You can print/export a copy of the Purchase Order and use that as you see fit.' There is no order transmission at all, electronic or otherwise. Suppliers are hand-entered free-text company records with a name, short name, website, addresses and contacts, and item costs are hand-typed per size ('Enter a Default Cost. This is the cost that you would purchase this Item for from the Supplier'); nothing is imported from a distributor catalog. Receiving is a manual line-by-line count verification, not an electronic invoice. No broadline distributor - Sysco, US Foods, PFG or any other - is named anywhere in the corpus; invoice ingestion is routed entirely to the MarginEdge partner ('Smart invoice processing: Scan or take pictures of any type of invoice'). https://support.arryved.com/portal/en/kb/articles/abm-purchase-orders · retrieved 2026-09-04

B
No

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

Invoice capture is a named partner's job: MarginEdge is listed for invoice and cost management. Arryved's own Inventory documentation enumerates settings, item creation, unique items and modifiers, with no invoice upload, OCR or line-item extraction. https://arryved.com/integration-partners/ · retrieved 2026-08-02

B
No

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

CLAIM: per-item purchase price history across invoices with an alert when a received price exceeds prior/contracted price by a configurable threshold. VERDICT: no. EVIDENCE: the only purchase-receiving workflow Arryved documents (ABM, the inventory master once synced) checks QUANTITY only and takes cost as a hand-edited field. ABM Purchase Orders: "Adjust the Cost Per Unit if needed." ... Receiving: "Each Item now has an Exact and a Diff button next to it on the list. You need to verify that the quantity that was delivered matches the quantity recorded on the Purchase Order. If there's any variation, click the Diff button and update the actual amount." ... "Finalize Receiving ... An Inventory Adjustment has been logged." and Limitations "Submitting a Purchase Order in your ABM does not notify your Supplier in any way." (https://support.arryved.com/portal/en/kb/articles/abm-purchase-orders). Cost is rolled into an Average Weighted Cost, not a price series (Arryved Cloud 2.62.2: "Improving Average Weighted Cost (AWC) ... we've changed the behavior of the 'Default Cost' field", https://support.arryved.com/portal/en/kb/articles/arryved-cloud-2-62-2). Arryved's own site assigns price-increase alerting to a partner: "get notified about increasing ingredient prices immediately" appears only on the MarginEdge integration page (https://arryved.com/integration-partners/marginedge-integration/), consistent with inventory-invoice-ocr = no. SURFACE (new 2026-09-16): the Zoho Desk portal's anonymous JSON API, https://support.arryved.com/portal/api/kbArticles?portalId=<portal id from the KB page>&from=N&limit=50, lists 539 articles across 4 root categories (Product Support 400, Onboarding 42, Release Notes 68, remainder not returned under a root filter); per-article /portal/api/kbArticles/<id> returned 510 bodies at 200 and 29 at 403 (all 29 are Arryved Insider loyalty or Arryved View digital-menu articles; their listing summaries are readable). Href fixpoint over the 510 bodies found 64 article slugs not in the listing; articleByPermalink probes: 37 resolve (200) to already-listed articles under old slugs, 5 are 403 (all card-reader pairing/troubleshooting: pairing-a-new-bluetooth-swiper-ble, bbpos-chipper-credit-card-reader-initial-setup, bluetooth-swiper-ble-troubleshooting, sw, troubleshootingbbposchipper), 22 are 404, and a nonsense-slug control is 404. The listing is therefore a census of anonymous-readable bodies plus 34 gated articles whose topics are known. The portal's own search API (/portal/api/kbArticles/search?searchStr=) was also queried. BOUND/CONTROLS over 539 listed articles, tokenised case-insensitive: "price history" 0, "price alert" 0, "cost alert" 0, "cost change"/"cost increase" 0; "price change(s)"/"price increase" hits are all POISON - the Dual Pricing setup's menu-price "bulk price increase", not purchase cost; "weighted" hits are Tip Points plus the one AWC note. None of the 34 gated articles is an inventory topic. Retrieved 2026-09-16. https://support.arryved.com/portal/en/kb/articles/abm-purchase-orders · retrieved 2026-09-16 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

Par levels with a consumption-rate calculation exist, but they raise a warning rather than generate an order. 'Reorder Point is a tool that allows you to set safety net parameters to help make sure you don't run out of a Material before it's too late. Your ABM will warn you when your Inventory falls below your safety net.' Two levers: 'Safety Stock... If a "10" is entered, then ABM will provide a warning that it may be time to reorder this Item when the On Hand Inventory count reaches 10 or below', and 'Lead Time allows you to enter the time (in days) it takes to receive this item after a Purchase Order is sent... Inventory On-Hand / Rate of Use = On-Hand Coverage. If the On-Hand Coverage is less than the Lead Time, you'll receive a warning.' Shortfall: (1) no suggested purchase-order quantity is produced - drafting a PO is entirely manual, with the operator typing the Purchase Quantity; (2) the only non-static driver is Rate of Use, historical consumption, not a sales forecast; (3) the reorder point is a per-Item-Size field in ABM, the separately-sold brewery module, not a per-location par in the POS, whose enumerated Inventory Item page carries only a bare 'Quantity in Stock'. https://support.arryved.com/portal/en/kb/articles/abm-materials · retrieved 2026-09-04

B
Partial

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

inventory-waste-logging

Structured waste categories that debit inventory do exist, in ABM: 'These Reduction Locations allow you to account for Inventory removal due to damage. There are 3 types of Reduction Locations: Loss & Breakage / Spoilage / Destroyed', and moving stock to one is an Inventory Adjustment against On Hand that carries through to regulatory reporting ('Reduction - Destroyed: Counts to Line 13. Reduction - Loss: Counts to Line 14'). Shortfall: (1) the reason set is three fixed built-in locations, not a configurable reason-code list; (2) the logging path is a generic manual Inventory Adjustment with a free-text Summary rather than a waste workflow - 'you may want to create a manual Adjustment to account for damaged/unsellable Items or some other unique reason... In the Summary field, provide some context to the reason for this adjustment' (ABM Inventory Adjustments); (3) no waste-cost report separate from usage variance is documented - the output is the Inventory Adjustments log, the QBO accounting effect and the TTB BROP lines; (4) it is ABM-only, and the POS's INV screen offers no waste path at all. https://support.arryved.com/portal/en/kb/articles/abm-inventory-location-behavior · retrieved 2026-09-04

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

Positive absence by field enumeration on the item type the vendor names as its most granular. The Add Size walkthrough is given step by step for beer, chosen because it 'is the most popular and allows for the most granularity' - Item Format, Item Size, Wholesale Price, Wholesale checkbox, Default Cost, Deposit Value, Est. Taproom Revenue, SKU, UPC, Not Inventoried, Allow fractional units, Reorder Point (Safety Stock, Lead Time) and Item Parts. There is no packaged-on, best-by, use-by or expiry field and no shelf-life duration. The Materials size fields are the same list minus the beverage-specific ones, and the Portal's Inventory Item enumeration (State, Quantity in Stock, SKU, CRV, Loyalty Cost, Attributes limited to 'ABV / Allergens / IBU / Rarity / Vintage', etc.) carries no date either. No expiring-soon report or alert exists; the sole documented inventory alert is the Reorder Point warning. https://support.arryved.com/portal/en/kb/articles/abm-finished-goods · retrieved 2026-09-04

B
Partial

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

inventory-bar-partial-bottle

Unit Sizes plus per-unit-size quantity tracking give a workable draft model — a keg sold down in pours of several named sizes — and BarTrack is integrated for draft-line volume monitoring. Shortfall: no tenthing, weighing or partial-bottle depletion for spirits is documented, and the precise draft measurement comes from BarTrack, a third party. https://support.arryved.com/portal/en/kb/articles/how-to-add-unit-sizes-to-inventory-items · retrieved 2026-08-02

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

Accounting posting is documented through partners — QuickBooks directly and Shogo for accounting automation — and any Portal report can be delivered as XLS or CSV via Rosie. Shortfall: no native COGS calculation or general-ledger mapping is documented in Arryved Portal; the journal is built in the accounting package. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations/shogo · retrieved 2026-08-02

B
Partial

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

A genuine first-party inventory layer exists — item creation, item types, tax types, unit sizes, SKUs and barcodes, folders and filtering, cloning, quantity tracking, and 86ing from the INV screen. Shortfall: everything above sold-item stock is partner or module territory — Yellow Dog for F&B inventory, MarginEdge for invoice costing, Ekos for brewery ERP, and ABM as a separately onboarded production module. https://support.arryved.com/portal/en/kb/arryved-support/portal/inventory · retrieved 2026-08-02

B
Partial

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

Cost and sales can be seen side by side per item, but no margin is computed and no threshold is flagged. The Purchase Items report lists every item sold and can add a cost column: 'COGS: Cost of Goods Sold. COGS are entered manually to Inventory Items in Arryved Portal. COGS is not available in Portal by default. Contact Arryved Support for more information.' The aggregate appears on the System Sales Summary: 'If COGS is enabled for your establishment, a cost would be added to each Inventory Item for each Unit Size applicable. As inventory depletes from orders placed through any of Arryved's products (Service, Online Store, OpenTab, and Arryved Mobile App), the total of COGS for each item sold is added up here.' Shortfall: (1) cost is a manually typed per-unit-size figure that is off by default and must be switched on by Arryved, not derived from a recipe or from received invoice prices; (2) no contribution-margin-per-item view is produced - the operator subtracts columns themselves, and the report does not even total repeat sales of an item; (3) there is no margin threshold, alert or flag on ingredient cost change anywhere; (4) actual margin analysis is routed to MarginEdge, which 'uses this data to calculate COGS and provide profitability reporting', making MarginEdge the subject of that capability. https://support.arryved.com/portal/en/kb/articles/purchase-items-repor · retrieved 2026-09-04

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

"The homepage of your Arryved Portal is known as the Dashboard", giving a visual summary of sales and tab data for the current or a previous business day, alongside a Sales Summary covering bookkeeping for the current business day. https://support.arryved.com/portal/en/kb/articles/dashboard · retrieved 2026-08-02

B
Yes

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

The Sales Summary is the day's close-out view with revenue breakdown, viewable for the current day, a past date or a range; Rosie sends it each morning "based on the batch time set by the location", together with an open-tabs notification. https://support.arryved.com/portal/en/kb/articles/system-sales-summary · retrieved 2026-08-02

B
Yes

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

The Item Modifiers Analysis Report "reveals an insightful analysis of how and how often your Menu Items are modified"; the Added Modifiers Report lists modifiers ordered in a date range with frequency and associated revenue; the Purchase Items Report gives item-level sales by employee, time and location. https://support.arryved.com/portal/en/kb/articles/item-modifiers-analysis-report · retrieved 2026-08-02

B
Yes

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

The Altered Tab Forensics Report documents "voided payments or orders with items removed" and requires Super Admin access to view. Comps are separately configured under Location Settings and carry a COMP permission with manager-code approval. https://support.arryved.com/portal/en/kb/arryved-support/portal/analytics-reporting/operations · retrieved 2026-08-02

B
Partial

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

A genuine counted-versus-expected variance exists and is computed, not eyeballed. Cash Handling Summary: “Expected End Amt — Your Expected End Til Amount = Starting Amt + Cash Sales + Cash Tips + Pay-ins - Pay-outs”; “Actual End Amt — The ‘End Til’ amount(s) entered through Cash Actions or Forced Tip Claim”; “Difference — The difference between the Expected and Actual Til amounts. If there is a positive or negative difference, this is how you can tell if your drawer is over or under”, and “Use this report to see if your drawer is over or under. If there’s a number in the Difference field, a positive number indicates the drawer is over, a negative number tells you the drawer is under.” SHORTFALL: the variance figure carries none of the claim’s three dimensions, and the article says so in its own Limitations — “The Cash Handling Summary shows totals for the entire day. There are no separate shifts in this report” (no per-shift), “This report doesn’t differentiate between different cash drawers” (no per-drawer), and it is a location-wide total with no per-employee attribution of the difference. It is also a Service-device quick report for the current day only — “This report can only be viewed for the current business day” — so there is no Portal over/short history. The per-employee surface, Emp. Cash Handling, is a log of Start Till / End Till / Pay In / Pay Out / Shift Tip / Employee Bank actions grouped by employee with no expected-cash column and no variance; the Location/Venue/Individual closeout reports print sales totals only and leave the count and comparison manual (“Count your cash drawer. Use the Location CO Report to manage your cash sales drop.”). https://support.arryved.com/portal/en/kb/articles/cash-handling-summary-overview-9-5-2022-1 · retrieved 2026-09-04

B
Partial

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

The Employee Performance report joins total sales, comps, tips, hours worked and tab/order counts per tipped employee from clocked hours, filterable by labor role, so sales per employee-hour is one division away; the 7shifts integration adds labor as a percentage of sales in 7shifts' dashboard. Shortfalls: no sales-per-labor-hour or labor-percentage column in an Arryved report, no by-hour or by-department cut, non-tipped roles are excluded from the report, and the report totals a date range rather than breaking it down by day. https://support.arryved.com/portal/en/kb/articles/employee-performance-report-overview · retrieved 2026-09-03 adversarially verified

B
Partial

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

A dedicated per-server report exists: “The Employee Performance report shows performance metrics per tipped employee including total sales, comps, tips, hours worked, and the number of tabs and orders. Filter this report by Labor Role to see a narrowed view of the metrics.” Its complete column set is enumerated: “Amount Sold — The combined dollar amount of items sold”, “Number of Tabs”, “Number Of Orders”, “Number Of Tables — This column is not in use at this time”, “Total Comps”, “Tips Decl.” and “Hours”, with tabs attributed by ownership (“tab data is allocated to employees from the tabs they own”). SHORTFALL, measured against the four metrics the claim names: average check is not a column (Amount Sold / Number of Tabs is derivable but never reported), items per check is absent entirely, there is no attachment rate for named categories, and tips are dollars, not a percentage of sales — the article states outright “Tips in this report are not differentiated by type (cash, card, gift card, etc.)”. Coverage is partial too: “Employees logged in under a Non-tipped Labor Role aren’t included in this report”, transactions in Offline Mode are excluded, and a multi-day range is “totaled together, not broken down by date”. There is no ranking, league table or benchmark view. https://support.arryved.com/portal/en/kb/articles/employee-performance-report-overview · retrieved 2026-09-04

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

A channel dimension exists and is reported. Daily Sales Report: “When the box is checked, the report lists each closed tab with detailed information. The bottom of the report sums up the tab information by Venue, Employee, method of payment, and Arryved Channel”, and “When the box is unchecked, the report does not include the individual tab information, just the Venue, employee, method of payment, and Arryved Channel totals.” The channel set is named elsewhere in the corpus as the three first-party surfaces — “all sales transactions from all Arryved channels (Arryved Service, OpenTab, & Arryved Online)” (https://support.arryved.com/portal/en/kb/articles/marginedge-integration-overview). SHORTFALL, both halves of the claim. (1) Revenue only, no margin: COGS exists but is aggregated across every channel at once — “As inventory depletes from orders placed through any of Arryved’s products (Service, Online Store, OpenTab, and Arryved Mobile App), the total of COGS for each item sold is added up here” (Sales Summary, https://support.arryved.com/portal/en/kb/articles/system-sales-summary) — and no report crosses channel with COGS or contribution. (2) No marketplace dimension and no commission netting: Arryved integrates with no third-party marketplace at all (the published integration set is Fresh KDS, QuickBooks, Shogo, 7shifts, Schedulefly, MarginEdge, BarTrack, Ekos, Yellow Dog — no DoorDash, Uber Eats or Grubhub), so “each third-party marketplace separately … net of marketplace commission fees” has no surface, and first-party delivery is a fulfilment option inside Arryved Online rather than a reported channel. https://support.arryved.com/portal/en/kb/articles/daily-sales-report-13-7-2020 · retrieved 2026-09-04

B
Partial

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

Rosie sends "any Arryved Portal report" on a daily, weekly, monthly or specific-weekday cadence as PDF, XLS or CSV, to "one or a number of email addresses for each report, for each location" with no limit on recipients. Shortfall: it is not self-serve — adding or changing a scheduled report requires contacting Arryved Support or an Implementation Manager. https://support.arryved.com/portal/en/kb/articles/rosie-reports-overview · retrieved 2026-08-02

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

The support knowledge base enumerates twelve top-level categories — Arryved Pay, Portal, Service, Hardware, OpenTab, Arryved Online, Insider, Integrations, Web Solutions, ABM, Capital, Emergency Guide — and none is a developer or API section. developer.arryved.com does not resolve in DNS. Data leaves the platform by scheduled report or by a named partner integration, not by a documented reporting API. https://support.arryved.com/portal/en/kb/arryved-support · retrieved 2026-08-02

B
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

No webhook product is documented — no callback registration, no event catalogue, no retry policy and no payload signing appear in any Arryved or partner document. The one publicly described outbound pipe is a scheduled batch push to a single hard-wired partner endpoint: "Arryved Service sync application pushes sales data to the Yellow Dog API at a frequency determined by Arryved Service" (the hourly default in that guide belongs to Yellow Dog’s own applications, not to Arryved). Sales data only, not order lifecycle events, and not to a customer-supplied endpoint. https://help.yellowdogsoftware.com/arryved · retrieved 2026-08-02 adversarially verified

E
Partial

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

UPGRADED FROM NO. The claim guards against data access sold as an upsell, and Arryved does not sell it as one — it simply has no API. Raw-data access is included and carries no published charge: Portal reports download as CSV ("Download this report as a CSV", https://support.arryved.com/portal/en/kb/articles/arryved-inventory-sync-integration) and Rosie will email any Arryved Portal report on a schedule "in PDF, XLS (Excel), or CSV (plain text spreadsheet) form" (https://support.arryved.com/portal/en/kb/articles/rosie-reports-overview), both inside the published subscription — "1-9 Devices Starting at $99.99/month", with the quote path taking "all the same profit-building features". SHORTFALL, two parts. (1) The API half of the claim has no subject at all: the support knowledge base's twelve top-level categories include no developer or API section, developer.arryved.com does not resolve, API keys are partner-provisioned per integration rather than merchant-obtainable, and this record already carries reporting-public-api = no at grade B. Nothing is upcharged because nothing exists to buy. (2) Raw-data delivery is not self-serve: Rosie schedules are set up through the Implementation Manager or Support ("provide this information to your Implementation Manager or a member of Arryved Support"), and COGS, RSF, the Payroll Report, Tips By Labor Hours and End Of Day Tip Summary each require an activation request for which Arryved publishes no commercial terms, so whether any of them costs money is not determinable from the published set. https://arryved.com/pricing/ · retrieved 2026-09-04

C
Partial

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

Nothing is tier-gated because there are no feature tiers: the pricing page publishes one price point and one quote path and states they carry the same feature set — “1–9 Devices Starting at $99.99/month” against “10+ Devices or 2+ Locations — Contact us for a quote. Work with a Growth Rep to get a customized quote for your business. Take advantage of all the same profit-building features (Software, Support, and Onboarding) …”. There is no plan matrix, no analytics SKU and no advanced-reporting upsell anywhere on arryved.com, and the help centre’s report catalogue carries no tier or SKU annotation — report access is governed by permission, not plan (“they must be a Super Admin or an Admin with one of the following Portal Permissions: REPORTING, ALL ACCESS, FULL ADMIN”, repeated on every report article; the Payroll Report additionally needs VIEW HOURS and VIEW PAY). SHORTFALL: reporting is never named among the published inclusions, so ‘included’ is inferred from the absence of a tier rather than stated; and a material slice of the reporting surface is gated behind an unpriced sales conversation rather than shipped — the Payroll Report (“If you would like to use this report, contact your Implementation Manager to enable it”), the Tips By Labor Hours and End Of Day Tip Summary reports (“Please contact your Implementation Manager to discuss and activate any of these reports for you”), COGS and RSF (“Contact your Customer Success Manager … to activate”) and every Rosie scheduled delivery. Arryved publishes no commercial terms for those activations, so whether any of them costs money is not determinable from the published set. https://arryved.com/pricing/ · retrieved 2026-09-04

C
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

Positive evidence of absence in the contract, twice over, on a claim whose operative verb is ‘documents’. The MSA, read to its end, defers retention entirely to an unpublished internal schedule and then disclaims availability: “Client Data and other Confidential Information may be retained subject to the receiving party’s retention practices until such information is scheduled to be deleted in accordance with the receiving party’s policies and procedures”; “Company shall provide access to the Client Data for no more than thirty (30) days after the termination or expiration of the Agreement. After this thirty (30) day period, Company may delete Client Data in accordance with its standard schedule and procedures”; and “COMPANY DOES NOT MAKE ANY REPRESENTATIONS OR WARRANTIES ABOUT THE SECURITY AND PROTECTION OF CLIENT DATA NOR GUARANTEE DATA AVAILABILITY. CLIENT BEARS THE SOLE RESPONSIBILITY AND LIABILITY FOR MAINTAINING BACKUP AND ARCHIVE COPIES OF CLIENT DATA.” The publication surface was measured, not assumed: ‘retention’ and ‘retain’ occur in zero of the 546 help-centre articles reached by fixpoint href crawl on 2026-09-04, including every article that would carry a window, and the one in-UI range statement runs the other way — “if a date range is selected to view this report, it can only be up to 31 days. If a range of more than 31 days is selected, a PDF will be emailed to you” (Sales Summary). No 24-month figure, no figure of any length, and no statement that history is not silently truncated. https://arryved.com/master-services-agreement/ · retrieved 2026-09-04

B
No

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

Rosie is the entire push surface and its configuration is enumerated in four steps, all of which are time-based. “Step 2: Choose A Cadence. Choose one or a number of the following cadences: DAILY: Sent every day, after batch time, with data from the preceding day. WEEKLY: Sent once a week, after batch time, based on the pay week start day set by the location. MONTHLY: Sent on the 1st of each month … MON: Sent every Monday, after batch time, for the preceding Monday thru Sunday … and so on for each individual day of the week.” The other three steps are Choose A Report, Choose A Form (PDF, XLS, CSV) and Choose Email Recipients — there is no condition, threshold, comparison or deviation option anywhere in the model. The only non-cadence email is a fixed operational exception the operator cannot configure or parameterise: “Rosie will also send out a separate email with details of any tabs left open after batch time”, which is neither an operator-set metric nor a threshold nor a deviation from history. Measured across the whole corpus: the word ‘threshold’ occurs in zero of the 546 help-centre articles crawled 2026-09-04, ‘anomaly/anomalies’ in none in an analytics sense, and the only ‘alert’ hits are the website alert-bar banner, KDS ticket colour and a PCI notice. Pulse, the Arryved Pay hub, enumerates five navigation options (Dashboard, Reporting, Transaction Search, Business Financing, Settings) and carries no alerting either. https://support.arryved.com/portal/en/kb/articles/rosie-reports-overview · retrieved 2026-09-04

B
No

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

CLAIM: an NL query / AI assistant answering ad-hoc questions against the operator's own sales and labor data. VERDICT: unknown -> no/B. The prior note held this unknown for three stated reasons: (1) the PV1 Portal scripts were not enumerated, (2) the MSA reserves AI features, (3) a zero-hit alone had been overturned before. (1) is now closed and (2) is now explained. NEW SURFACE (2026-09-17): the LEGACY Portal (PV1) is now a closed census. https://portal.arryved.com/js/scriptLoader.js (production, anonymous, 7,059 bytes; "const version = '2.27'") holds the literal ordered list of every PV1 script ("Loads all the scripts in order"; a TODO says on-demand loading is NOT implemented). All 125 listed scripts fetched at 200 (2,109,784 bytes, unminified source, none a soft-404 shell), plus the 92 page templates they load via app.Ajax.page('./html/...') (all 200, 523,980 bytes; a nonsense /html/ path returns 404 "Resource not found", so these are real). The only other dynamic loads are ag-grid vendor imports and the Google Maps loader; app.Pages.guideLoader reads app.Guides.config, which no script defines (/guides/tooltips.html 404), so it is dead code. Together with the complete PV2 bundle (portal.arryved.com/v2/main.js, prior note) both generations of the operator Portal are now held whole. BOUND (the operator's reporting surfaces, all first-party, all production): PV1 125 scripts + 92 templates (incl. pages/analytics/dashboard, salesSummary, dateRangeComparison, reporting/editReport, getReport, reportPreview, favoriteReportsLanding, reportManager, reportConfiguration, locationAssets/emailReports); PV2 single bundle with its 206-entry nav (Analytics: Dashboard, Sales Summary; Reporting: Favorites, Sales, Statistics, Operations, Inventory, Accounting, Discrepancy, Online and App, Portal Logging, Custom; Rosie Reports); the 539-article Zoho KB API census (release notes to Arryved Cloud 2.85). CONTROLS over PV1 JS+HTML (tokenised, word-boundary, case-insensitive except AI/LLM): AI 0, assistant 0, GPT 0, OpenAI 0, LLM 0, chat ?bot 0, "natural language" 0, insight(s) 0, copilot 0, claude 0, gemini 0, "machine learning" 0; prompt 4 all POISON (confirmation-dialog prompts, e.g. manageOffers.js "cancelText: \"Cancel\" }); // End prompt."); ask 2 POISON (UI copy). KB and PV2 controls: 0 (prior notes; PV2 AI 6 are a minified React component named AI). WHAT THE MSA AI CLAUSE MAPS TO: the only generative-AI feature found in any Arryved bundle is in the SIBLING product Arryved Brewery Management (https://abm.arryved.com/, Vite app, 16 JS modules followed to closure, 0 missing): a "Product Description Generator" with labels "Item description prompt" / "Use AI" that sends erp.api.CompletePromptRequest {prompt} and writes completions[0].text into an item's description - content generation, not a data query; its only other query-shaped RPC, erp.api.ReportSvc/ExecuteQuery {query, parameters}, is called from ReportQuery-CiGPRsV7.js as executeQuery({query:e.sql, parameters:...}) with a report definition's predefined SQL and decodes an Arrow IPC table - canned reports, not natural language. NOT COVERED: the Arryved Service Android POS app binary (its features are covered only through the KB release notes). Retrieved 2026-09-17. https://portal.arryved.com/js/scriptLoader.js · retrieved 2026-09-17 adversarially verified

B
Partial

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

Guest-level history exists: per-member stats dashboards, and a member report carrying contact info, point balance and visit history for the whole member base. Shortfall: there is no cohort builder — no first-visit cohorting, retention curve or repeat-rate report is documented, and analysis has to happen in the exported file. https://support.arryved.com/portal/en/kb/articles/view-insider-member-stats · retrieved 2026-08-02

B
Partial

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

Via the 7shifts partner integration: Arryved sends a 90-day sales history on activation and ongoing net sales, and 7shifts produces Sales Projections and Labor Projections used to build schedules ('Forecast future sales based on POS sales history'). Shortfalls: no forecast in Arryved Portal's own reporting; the projection lives in 7shifts' dashboard, is billed by 7shifts per location, and its granularity is 7shifts' (daily projections for scheduling), not an Arryved daypart or hourly report. https://support.arryved.com/portal/en/kb/articles/7shifts-integration-overview-2-7-2025-1 · retrieved 2026-09-03 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

Declared versus charged tips exist per employee: the Employee Tip Collection report breaks tips down by payment type (card and gift card versus cash/check), Cash Actions and Forced Tip Claim record tips declared at clock-out into the Cash Action Log and Emp. Cash Handling report, and the Payroll (Shift Tip) and Employee Time Card reports carry tips beside regular and overtime pay. Shortfalls: no tax liability summary by jurisdiction, no allocated-tip or 8027-style output, no named payroll-provider export format (the 7shifts integration explicitly does not carry tips), and the reports are only valid after batch time. https://support.arryved.com/portal/en/kb/articles/employee-tip-collection-report-overview · retrieved 2026-09-03 adversarially verified

B

Hardware & physical footprint

Partial

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

Merchant-sourced hardware is permitted but explicitly not guaranteed: "Arryved will make a best attempt to support devices purchased independently by customers. However, self-sourced devices are not guaranteed to be compatible or function correctly." Devices sold by Arryved are supported while they still receive security updates. https://support.arryved.com/portal/en/kb/articles/device-lifecycle-policy · retrieved 2026-08-02

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 only. The lifecycle policy points merchants to endoflife.date/android and uses Samsung Galaxy Tab as its worked example; the KB carries Android-specific articles (TalkBack on/off, offline checkpoint recovery for Android 10 or lower, 11+ and 15+). Shortfall: no iOS, Windows or browser-based POS client is documented. https://support.arryved.com/portal/en/kb/articles/device-lifecycle-policy · retrieved 2026-08-02

B
Partial

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

Arryved sells and supports "POS handhelds and tablets that house Arryved Service" and the product is designed around roaming staff. Shortfall: the devices are commodity Android tablets and phones rather than a purpose-built Arryved terminal — no model is named on any public page, and the lifecycle policy tracks third-party manufacturer end-of-life dates. https://support.arryved.com/portal/en/kb/arryved-support/hardware · retrieved 2026-08-02

B
Unknown

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

CLAIM: handheld hot-swap/field-replaceable batteries or a published full-shift battery rating. VERDICT: unknown (unchanged). NEW: the handheld is a smartphone-class Android device with no published model or battery spec: "Handhelds are the size of an Android smartphone ... generally sold in their protective case with their supported card reader attached to the back" and "POS Devices must have an Operating System (OS) of Android 14 or higher ... Samsung products work best with our system" (Arryved Hardware Considerations). Battery ratings exist only for the attached CARD READER, which does not satisfy the handheld claim: "The tDynamo lasts up to 6 hours with continuous use or 11 hours if sitting idle" (tdynamo-card-reader-overview); the app warns at 25% "to charge or swap out the reader" (arryved-service-2-1-1); DynaFlex II Go: "charge your DynaFlex card readers at the end of each day" (dynaflex-card-reader-overview). The Hardware Catalog "with specs and pricing" is referenced but not publicly linked. SURFACE (new 2026-09-16): the Zoho Desk portal's anonymous JSON API, https://support.arryved.com/portal/api/kbArticles?portalId=<portal id from the KB page>&from=N&limit=50, lists 539 articles across 4 root categories (Product Support 400, Onboarding 42, Release Notes 68, remainder not returned under a root filter); per-article /portal/api/kbArticles/<id> returned 510 bodies at 200 and 29 at 403 (all 29 are Arryved Insider loyalty or Arryved View digital-menu articles; their listing summaries are readable). Href fixpoint over the 510 bodies found 64 article slugs not in the listing; articleByPermalink probes: 37 resolve (200) to already-listed articles under old slugs, 5 are 403 (all card-reader pairing/troubleshooting: pairing-a-new-bluetooth-swiper-ble, bbpos-chipper-credit-card-reader-initial-setup, bluetooth-swiper-ble-troubleshooting, sw, troubleshootingbbposchipper), 22 are 404, and a nonsense-slug control is 404. The listing is therefore a census of anonymous-readable bodies plus 34 gated articles whose topics are known. The portal's own search API (/portal/api/kbArticles/search?searchStr=) was also queried. Retrieved 2026-09-16. || 327th: 327th, NEW SURFACE, negative and now bounded on the marketing side too: across the first full census of arryved.com (380/380 sitemap URLs, 375 bodies, 3,704,288 chars) the token 'battery' scores 0 and 'hot-swap' 0. The 14 'handheld' hits are all customer-story prose about mobility ('To be able to carry a handheld device, and send orders, and perform all of the functions of a POS system in the palm of your hand') with no device model, no battery rating and no swap procedure. So neither the KB (539 articles) nor the marketing site publishes a handheld battery spec, consistent with the handheld being a customer-supplied Android smartphone; the claim's premise is absent rather than denied, so this is held unknown per the lacks-entirely rule rather than turned into a `no`. Retrieved 2026-09-18. || 328th: 328th: the MSA (69,277 chars stripped, the vendor's only public hardware-bearing contract - it defines 'hardware' as part of the Company Platforms and the 327th pricing page sells devices) scores `battery` 0 and `hot-swap` 0, so the legal surface publishes no device spec either. No new surface; recorded so the next pass does not re-read the MSA for this cell. Retrieved 2026-09-18. || 329th: MERGE HOLD (proposed no/B, held unknown): Arryved sells Android handhelds whose specs live in an EMAIL-GATED Hardware Catalog. The KB census bounds what the KB publishes, but the device model is unnamed and a hot-swap battery is a property of the hardware, which no public Arryved corpus describes. A gated spec sheet is a refusal, not an absence; hold until the handheld model is identified (then the manufacturer's sheet settles disjunct 1). PROPOSAL AS WRITTEN: 329th: the 327th held this unknown on a 'lacks entirely / customer-supplied phone' reading. That reading is WRONG and the vendor's own hardware docs, read individually against this cell for the first time, say so: Arryved SELLS the handheld. 'Arryved offers Tablet and Handheld options for your POS devices ... Handhelds are the size of an Android smartphone. They can be held in one hand and typically fit in a server's apron, pocket, or fanny pack. Handhelds are generally sold in their protective case with their supported card reader attached to the back' (https://support.arryved.com/portal/en/kb/articles/things-to-consider-when-making-your-first-hardware-order-9-5-2022-1, Hardware, mod 2026-03-12), and the catalogue it points to lists 'POS Android tablets, POS Android handheld devices, Card Readers ...'. So the claim's premise holds and the disjuncts can be tested. DISJUNCT 2 (vendor publishes a rated battery life) is a publication-shaped claim and it fails on a publication census: `battery life` scores 15 in the 510 held KB articles and ALL 15 are CARD READER prose (tDynamo / DynaFlex II Go: 'Best Practices For EMV Card Reader Battery', 'The battery may take up to 5 hours to fully charge using a USB-C cable', 'may have a hard time connecting to the POS when the battery level dips below 10%'); 0 on the 375-page arryved.com census; 0 in the MSA; 0 in the 225-file portal census. mAh 0, 'full shift' 0, 'all-day battery' 0. DISJUNCT 1 (hot-swap / field-replaceable) fails positively too: 'hot swap' 0, 'hot-swappable' 0, swappable 0, replaceable 0, 'field-replaceable' 0, removable 0, 'spare battery' 0, 'extra battery' 0, 'battery pack' 0 across ALL of those corpora, and the POISON is instructive - all 5 `swap` hits in the KB are swapping a CARD READER or a payment card ('you can swap it for the fully charged one that was sitting in the charging dock', 'purchase an extra reader or two to swap out during service'), i.e. where Arryved does support swapping a depleted unit it says so explicitly, and it says it about the reader, never the POS device. The device policy makes the mechanism plain: supported devices are commodity Android units 'actively receiving Android Operating System (OS) security updates from its manufacturer (e.g., Samsung)' with Google Play access, either 'Devices Purchased from Arryved' or customer-sourced (https://support.arryved.com/portal/en/kb/articles/device-lifecycle-policy, eff. 2025-09-01), and the warranty page says 'Arryved doesn't manufacture these products, we partner with Samsung, Magtak, Epson' with the Samsung defect list running 'Dead screen pixels, Loss or faulty touchscreen capabilities, Inability to charge' - a charging failure is a whole-device warranty return, not a battery swap (https://support.arryved.com/portal/en/kb/articles/warran). Mitigation guidance is cabling, not swapping: 'find a short charging cord ... this will keep your reader charged without draining the POS battery ... you can do this to tablets sitting stationary or handheld devices moving around all day'. BOUND: 510/539 Zoho KB articles held (the 29 gated are the Insider / Arryved View Designer / Managing-Inventory sets - ZERO of them in the Hardware, POS Devices, tDynamo or DynaFlex categories, all of which are fully held), 375/380 arryved.com pages, the 69,277-char MSA, and the 225/225-file portal census. WEAKNESS, stated plainly: the 'Arryved Hardware Catalog', which the same article says carries 'specs and pricing', is NOT public ('Contact Arryved Support at support@arryved.com to view the catalog'), so a model-level spec sheet exists that we do not hold - which is itself why disjunct 2 fails, since a catalogue handed out by email is not published. Retrieved 2026-09-18. adversarially verified

F
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

Positive absence. The network documentation is where a cellular fallback would be specified and what it specifies instead is a merchant-supplied manual link: under Connectivity Testing and Maintenance, 'Keep a backup hotspot or secondary internet connection for redundancy during outages.' Arryved disclaims the WAN entirely - 'the setup, management, and maintenance of your network are the sole responsibility of your team and your ISP' - and the documented product response to losing the network is Offline Mode, not a second radio. The hardware catalogue is enumerated ('POS Android tablets, POS Android handheld devices, Card Readers, Ticket and receipt printers, Kitchen Display System (KDS) hardware, Arryved Print Controller, Cash Drawer, Barcode Scanner, Accessories') and contains no LTE handheld SKU, SIM, carrier or data plan. The single cellular reference to a POS device in the corpus is off-premise and is not a fallback: Using Arryved Service For Keg Distribution, 'the best way to facilitate live and accurate transactions is with the use of a mobile hotspot or through the use of a handheld with cell reception and the Arryved Service app to process orders.' https://support.arryved.com/portal/en/kb/articles/network-best-practices · retrieved 2026-09-04

B
Yes

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

Offline Mode is a documented, supported state with its own KB section: manual entry from Settings by a holder of the HARDWARE permission, on-device checkpoint files, an emergency entry code, an exit-and-sync procedure and per-Android-version recovery articles. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

B
Partial

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

Two documented KDS paths: an Epson KDS with its own overview, setup and hardware articles under Arryved's Hardware section, addressed through the same Peripheral Matrix as printers, and the Fresh KDS partner integration. Shortfall: neither is Arryved-built software — the Epson unit is a printer-vendor display product and Fresh KDS is a third party — and the documented KDS feature set is limited to displaying tickets, custom layouts and time tracking. https://support.arryved.com/portal/en/kb/arryved-support/hardware/kds-system · retrieved 2026-08-02

B
Partial

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

Printers are documented in depth — setup, testing, troubleshooting and off-site printing — with bar, kitchen and receipt roles and a Print Controller required for Arryved Online and OpenTab tickets. Shortfall: no supported printer make or model list is published, so compatibility with hardware a merchant already owns cannot be checked before buying. https://support.arryved.com/portal/en/kb/arryved-support/hardware/printer · retrieved 2026-08-02

B
Yes

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

The Hardware section documents the full peripheral set: POS devices, card readers, printers, a print controller, cash drawer, barcode scanners ("for quicker checkout", with SKU setup and scanning documented) and Epson KDS. https://support.arryved.com/portal/en/kb/arryved-support/hardware · retrieved 2026-08-02

B
Partial

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

Card entry is confined to a dedicated encrypted reader, but no validated P2PE solution, no PCI PTS listing and no SAQ type is stated, and the merchant is enrolled in a full paid PCI programme rather than a reduced scope. Present: 'Card Readers must be purchased from the Arryved Catalog because they are approved by and encrypted with our payment processor. No exceptions', and 'The new card readers are encrypted through Arryved Pay and can't be supported by TSYS' - the readers are MagTek tDynamo and DynaFlex II Go and the Android tablet never takes the card. Shortfall: (1) the PCI article names no SAQ type and routes the question away from Arryved entirely - 'Send all SAQ, scan, or PCI-requirement questions to support@securitymetrics.com', and 'The Arryved Support Team has little power in assisting with PCI Compliance'; (2) scope is not removed - a monthly PCI/Breach Protection fee is charged and 'If you fail to become compliant, you're charged an additional monthly fee until you pass compliance'; (3) no PCI-listed P2PE solution name or listing number appears in the corpus or the MSA, whose PCI section is a generic shared-responsibility clause. https://support.arryved.com/portal/en/kb/articles/pci-compliance-overview-arryved-pay · retrieved 2026-09-04

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

Same enumeration read for the reader-less half of the question. The hardware article enumerates what Arryved sells - 'POS Android tablets, POS Android handheld devices, Card Readers, Ticket and receipt printers, Kitchen Display System (KDS) hardware, Arryved Print Controller, Cash Drawer, Barcode Scanner, Accessories' - introduced as 'a full list of the hardware products we offer', and then states the requirement: 'You'll need one card reader per POS device.' Reader sourcing is closed: 'Card Readers must be purchased from the Arryved Catalog... No exceptions.' Both documented readers are external MagTek units attached to the device ('The DynaFlex II Go card reader (the black one) can only be Bluetooth paired to your handheld POS devices. POS Tablets (running on any Android OS) need to be hardwired to the DynaFlex.'). No NFC acceptance on the Android device itself is documented, and Arryved's own answer to reader-less ordering is the guest's phone, not the staff's: OpenTab QR self-ordering. Same 9-article 403 hole disclosed. https://support.arryved.com/portal/en/kb/articles/things-to-consider-when-making-your-first-hardware-order-9-5-2022-1 · retrieved 2026-09-04

B
No

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

hardware-pricing-transparency

Arryved names the hardware fees but publishes none of the amounts: Terminal Lease Fee, Terminal Purchase Fee, Terminal Sales Tax and Shipping & Handling all appear on the fee list, under an explicit statement that "the actual dollar amounts of the fees are not mentioned in this guide". The pricing page publishes no hardware price either. https://support.arryved.com/portal/en/kb/articles/arryved-pay-fee-structure · retrieved 2026-08-02

B
Yes

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

Both routes exist and outright purchase conveys title: MSA §15 provides that "for Equipment purchased from Company, title to such Equipment shall not pass to Client until all amounts for the purchase of such Equipment have been paid". The fee list carries both a Terminal Lease Fee and a Terminal Purchase Fee, and the Arryved Pay page states "lease or buy, you decide". https://arryved.com/master-services-agreement/ · retrieved 2026-08-02 adversarially verified

B
Partial

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

The two halves of the estate go opposite ways and Arryved documents both. Reusable: the POS devices are commodity Samsung Android units the merchant may source themselves - 'We understand if you want to make your own hardware purchases outside of the Arryved Catalog... POS Devices must have an Operating System (OS) of Android 14 or higher... Samsung products work best with our system' - installed from the public app store ('Download and install the Arryved Service app from the Google Play Store'), with printers required to be Epson brand. Not reusable, and this is the named shortfall: 'Card Readers must be purchased from the Arryved Catalog because they are approved by and encrypted with our payment processor. No exceptions.' The lock bites on a processor change, not merely a vendor change: 'The new card readers are encrypted through Arryved Pay and can't be supported by TSYS' and 'BBPOS card readers will no longer be supported when you switch to Arryved Pay, even if you keep your TSYS account open.' MSA sec.15 EQUIPMENT settles ownership on payment and contains no repossession, remote-disable or return-on-termination clause. No article describes unlocking, de-keying or re-injecting a reader for another processor. https://support.arryved.com/portal/en/kb/articles/things-to-consider-when-making-your-first-hardware-order-9-5-2022-1 · retrieved 2026-09-04

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

Bringing your own Android device is allowed: "Arryved will make a best attempt to support devices purchased independently by customers." Shortfall: the same passage continues "self-sourced devices are not guaranteed to be compatible or function correctly", no supported-model list is published, and a paired MagTek reader is still required to take cards. https://support.arryved.com/portal/en/kb/articles/device-lifecycle-policy · retrieved 2026-08-02

B
Partial

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

BarTrack is an integrated draft-beverage monitoring partner giving volume and quality telemetry on the draft system. Shortfall: this is line monitoring, not self-pour — no self-pour wall, RFID/NFC pour-card system or scale integration (PourMyBeer, iPourIt, Table Tap) is documented. https://arryved.com/integration-partners/bartrack/ · retrieved 2026-08-02

B

Integrations, API & extensibility

Yes

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

extensibility-public-api-docs

CLAIM: public, self-serve API reference readable without a signed partner agreement, NDA or sales call. VERDICT: yes/B (was no/B; the old note 'There is no public API documentation' is FALSE). EVIDENCE: https://partner.arryved.com/docs/ (HTTP 200, 1,239,015 bytes, anonymous; same page at integration.arryved.com/docs/ and canary-partner.arryved.com/docs/) embeds an OpenAPI 3.0.0 spec 'Arryved Partner APIs' v1.0.5: 'This is the API documentation for Arryved Partners. This API is developed for the purpose of providing external clients with a limited set of functionality provided by our core POS system, such as inventory counts and sales data.' 8 operations (accounting/sales, sales/{tabId}, authentication/authenticate + preauth, inventory/adjust, order/list, products, products/{productId}); servers: production, sandbox-partner and dev. CAVEATS: the page is not linked from arryved.com or the KB (found via crt.sh); API credentials require becoming a partner ('contact us at integrations@arryved.com'); the reference is narrow. The claim asks only that the reference be readable, and it is. Found by the 318th arryved agent via crt.sh; verified live 2026-09-16. Retrieved 2026-09-16. https://partner.arryved.com/docs/ · retrieved 2026-09-16 adversarially verified

B
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

NEW (2026-09-16): an anonymous Redoc page https://partner.arryved.com/docs/ (1,239,015 bytes; identical at integration.arryved.com/docs/ and canary-partner.arryved.com/docs/; sandbox-partner.arryved.com/docs/ differs only in securitySchemes null) embeds a full OpenAPI 3.0.0 spec, "Arryved Partner APIs" v1.0.5, 8 operations (GET /accounting/sales, GET /accounting/sales/{tabId}, POST /authentication/authenticate, POST /authentication/preauth, POST /inventory/adjust, POST /order/list, GET /products, GET /products/{productId}), servers Production https://partner.arryved.com/api/v1 and Sandbox https://sandbox-partner.arryved.com/api/v1, auth apiKey header X-API-KEY. It is silent on price: "This API is developed for the purpose of providing external clients with a limited set of functionality provided by our core POS system, such as inventory counts and sales data ... If you are not currently a partner and would like to be, please contact us at integrations@arryved.com in order to get started." Tokens fee/price/pricing/charge/subscription/billing 0; the one \bcost\b is a field description ("tracked by the individual size/cost of the item"). So access is partner-gated by contact with no published cost either way. SURFACE (new 2026-09-16): crt.sh certificate listing for %.arryved.com (https://crt.sh/?q=%25.arryved.com&output=json) named ~300 hosts; probed with a nonsense-path control per host. Retrieved 2026-09-16. || 319th: NEW SURFACES (2026-09-16): (1) the arryved.com WordPress media library (wp-json/wp/v2/media, x-wp-total 2033; 1,860 source_urls read) holds only two non-image files, one being the current MSA PDF https://craftpeak-cooler-uploads.s3-accelerate.amazonaws.com/arryved/New-MSA_Arryved_03.05.2026.pdf (258,683 bytes). Its only API mention is the IP-ownership definition ("portals, applications, and Application Programming Interfaces ("API"s)"); its only integration fee language concerns payments ("charge a non-integrated payment processing fee", "non-integration payment processing fees"). Nothing prices API access either way. The bucket is not listable (AccessDenied). (2) crt.sh host census of %.arryved.com (283 names) probed at 14 doc paths each (3,724 requests): the only API documentation is the already-cited Partner APIs Redoc on partner/integration/canary-partner/sandbox-partner; docs.arryved.com is a Slab login wiki, academy.arryved.com an Articulate Reach 360 LMS login, dev-merchant-api.arryved.com/docs/ 403. Still no published API price or tier requirement. Retrieved 2026-09-16. || 327th: 327th, NEW SURFACE: Arryved publishes a full merchant MASTER SERVICES AGREEMENT at https://arryved.com/master-services-agreement/ (200, 65,988 chars stripped) - an unlinked-from-nav legal document no prior pass had read. It defines APIs as part of the licensed Services ('any websites, platforms ... and Application Programming Interfaces ("API"s) ... owned or operated by Company') but sets NO price, fee, tier or surcharge for API access anywhere: across the whole 375-page site census (3,704,288 chars) 'API' scores only 2 hits, the MSA definition above and a BevFinder line offering 'a custom API integration with our partner VIP'. This complements the partner spec already on record (partner.arryved.com/docs, 8 operations, 'If you are not currently a partner and would like to be, please contact us at integrations@arryved.com'), which is likewise silent on price. Both of the vendor's own commercial documents are now held and neither prices API access, so the cell stays unknown rather than moving on silence. Retrieved 2026-09-18. || 328th: 328th, re-verified independently and with a structural reason to STOP mining this cell: on my own tokenised run over the 69,277-char stripped MSA (known-positive `the` 501) `API` scores exactly 1 - the definition inside Company Platforms ('any websites, platforms ... software, hardware, portals, applications, and Application Programming Interfaces ("API"s) ... owned or operated by Company') - and there is no fee, tier, surcharge or per-location charge attached to it. The MSA explains why no public document will ever price it: all commercial terms live in the Order Form, which the MSA defines as 'a separate ordering agreement (including but not limited to a statement of work, proposal, or change order)' and to which it subordinates itself ('the terms of the Order Form shall prevail'). Order Form is referenced 28 times and is never published. Also newly recorded from the MSA: the contracting entity is 'FS Operations Corp DBA Arryved, a subsidiary of Fullsteam Operations LLC', so any Fullsteam-level commercial schedule would be the next surface, not an arryved.com page. Retrieved 2026-09-18. || 329th: 329th, two new surfaces, neither of which can carry the cell, and one NAMED LEAD CLOSED. (1) Arryved's only published FEE ENUMERATION: 'Arryved Pay Fee Structure' (https://support.arryved.com/portal/en/kb/articles/arryved-pay-fee-structure, mod 2026-05-07) itemises every fee a merchant can see - Monthly: Terminal Lease Fee, Card Monthly Fees, Card Brand Network Fees, Full Settlement Fee, PCI/Breach Protection, Accelerated Funding (optional); One-time: Chargeback Fee, Terminal Purchase Fee, Terminal Sales Tax, Shipping & Handling; Other: 'Arryved Platform Fee - Arryved charges a competitive monthly fee to use a wide range of products and services. The Arryved Platform Fee is billed separately through NetSuite.' There is NO API, integration, developer or per-location technology line in that enumeration. It still cannot settle the claim, because the article states its own limit - 'The actual dollar amounts of the fees are not mentioned in this guide' - and it scopes itself to Pulse processing statements while explicitly excluding the one software fee ('Your monthly Arryved Platform Fee is not included in your Merchant Statements', https://support.arryved.com/portal/en/kb/articles/how-to-access-my-monthly-merchant-statements). A processing-statement fee list does not bound the SaaS side, and the MSA already routes all commercial terms to the unpublished Order Form. (2) THE FULLSTEAM PARENT LEAD IS CLOSED, so no later pass should re-run it: www.fullsteam.com publishes a 20-URL sitemap and all 20 were fetched at 200 today (66,771 chars stripped); it carries only /privacy and /complaints as legal pages - no MSA, no merchant agreement, no terms of service, no fee schedule (/legal, /terms, /terms-of-service, /terms-of-use, /msa, /merchant-agreement, /merchant-terms all 404 to the same 18,245-byte error page; fullsteampay.com does not resolve). Tokenised over that census with known-positive `the` 212: API 0, Arryved 0, 'merchant agreement' 0, 'per location' 0. Also re-checked: arryved.com's sitemap is byte-for-byte the same 380 URLs as the 327th (0 new), and /terms, /sla, /dpa, /eula, /order-form, /hardware-catalog are all 404. Separately, the KB's own 3 `API` hits are all THIRD-PARTY APIs (ShipCompliant 'Tax API Username', UPS 'API type - REST'), so Arryved's own API is documented nowhere a customer can read and priced nowhere - the partner spec at partner.arryved.com/docs remains the only published API surface and it is silent on cost. Retrieved 2026-09-18. adversarially verified

F
Partial

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

extensibility-free-sandbox

CLAIM: a free sandbox/test environment with seeded data available to developers without a paid production account. VERDICT: partial (was no/B). The prior note's premises are falsified in part: it said there is no partner programme and nothing offered to a developer. EVIDENCE: Arryved's anonymous OpenAPI spec "Arryved Partner APIs" v1.0.5 (https://sandbox-partner.arryved.com/docs/, also partner.arryved.com/docs/) lists servers {"description":"Production API","url":"https://partner.arryved.com/api/v1"} and {"description":"Sandbox API","url":"https://sandbox-partner.arryved.com/api/v1"}, and the sandbox is LIVE: an unauthenticated GET https://sandbox-partner.arryved.com/api/v1/products returns Arryved's JSON envelope {"responseInfo":{"serverApiVersion":"1.0.5","serverVersion":"2.73.1"},"errorInfo":{"code":"4301","name":"AUTH_TOKEN_EXPIRED",...}} while the nonsense path /api/v1/zzqq returns 404, so it is a running environment, not a catch-all. The route in is a partner programme, not a merchant account: "If you are not currently a partner and would like to be, please contact us at integrations@arryved.com in order to get started." SHORTFALL (why not yes): access is by contacting integrations@arryved.com (no self-serve signup), and neither the spec nor any readable page says the sandbox is free or seeded with test data (spec tokens free 0, seed 0, "test data" 0). WEAKNESS: rests on a server list plus a live endpoint; the terms of sandbox access are unpublished. Retrieved 2026-09-16. https://sandbox-partner.arryved.com/docs/ · retrieved 2026-09-16 adversarially verified

B
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

CLAIM: third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions. VERDICT: no (value unchanged; grade E -> B, now sourced to Arryved's own API reference instead of a Yellow Dog help page). EVIDENCE: the anonymous OpenAPI 3.0.0 spec "Arryved Partner APIs" v1.0.5 embedded in https://partner.arryved.com/docs/ (same spec at sandbox-partner.arryved.com/docs/, integration.arryved.com/docs/, canary-partner.arryved.com/docs/) declares exactly ONE security scheme: {"ApiKeyAuth":{"type":"apiKey","in":"header","name":"X-API-KEY"}}. Its auth operations are a static token exchange, not a delegated grant: POST /authentication/authenticate "Exchange an integration authentication token for a session token to be included in the X-API header", where AuthenticationDto requires "companyId ... the registered company id associated with the token" and "authToken ... the issued authentication token by the server, used to get a session token"; POST /authentication/preauth is keyed to a "networkId ... either an IMEI number or IP address". The 401 response: "Requestor does not have a token in the X-API-KEY header, the token has expired, the token is invalid, or the token isn't of sufficient authority for the requested operation". BOUND: the spec's components.securitySchemes is a closed enumeration (1 entry) over all 8 operations. CONTROLS, word-boundary case-insensitive over the 36,336-byte spec JSON: oauth 0, oauth2 0, bearer 0, scope/scopes 0, client_id/clientId 0, redirect_uri 0, revoke/revocable 0, refresh 0, consent 0, openIdConnect 0. POISON: the 1.24 MB Redoc HTML page shows oauth2 14, scopes 34, openIdConnect 8, bearer 2, all inside the bundled Redoc/AJV OpenAPI-schema validator (e.g. case"oauth2":switch(...flow){case"implicit":return["type","flow","authorizationUrl","scopes"]), not Arryved's API. Live check: GET https://partner.arryved.com/api/v1/products without a token returns errorInfo code 4301 AUTH_TOKEN_EXPIRED, serverVersion 2.99.0. Retrieved 2026-09-16. https://partner.arryved.com/docs/ · retrieved 2026-09-16 adversarially verified

B
No

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

extensibility-webhooks-push

Arryved does emit outbound data, but not as webhooks: its sync application "pushes sales data to the Yellow Dog API at a frequency determined by Arryved Service" — a scheduled batch to one named partner, carrying sales data. No subscribable order-lifecycle event (created, modified, paid, voided, refunded) and no customer-configurable callback URL is documented anywhere. https://help.yellowdogsoftware.com/arryved · retrieved 2026-08-02 adversarially verified

E
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

Upheld, and the premise ("no webhook product exists") is now measured against the vendor's own integrations catalogue rather than assumed. The Integrations category is described as "Arryved partners with other 3rd parties to offer you the best business solutions. See what you can integrate your POS with, here" and enumerates NINE named partners and nothing else: Fresh KDS (Kitchen Display System), Shogo (Accounting Automation), QuickBooks, BarTrack (Beverage Management), Ekos, Yellow Dog, MarginEdge, eCard Systems and 7shifts (Employee management, scheduling, and sales forecasting). Every entry is a brokered partnership, not a self-service integration surface. The twelve-category help-centre index carries no developer or API section, and developer.arryved.com and api.arryved.com are both NXDOMAIN as of 2026-09-09. With no published webhook there is no retry policy, signing scheme, replay window or delivery log to document. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations · retrieved 2026-09-09

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

The one documented programmatic pipe runs outward only and carries closed sales, not orders: 'With the 1-way sync, for Food & Beverage Management, Arryved sends your sales data to Yellow Dog to deplete automatically inventory and update reporting in your Yellow Dog account', on a fixed schedule - 'Arryved sends the following sales data to Yellow Dog every 15 minutes: Check number; Date/Time closed; Name; Item ID; Size IDs; Price; Comps; Quantity; Modifiers; Employee ID.' Arryved's integration catalogue is enumerated as a closed list - 'Consult your Implementation Manager if you're interested in integrating your Arryved POS with any of the following 3rd-party services: Fresh KDS, QuickBooks, QBO w/ Shogo, QBO w/ Ekos, BarTrack, Yellow Dog, Encompass (O'beer)...' - and every member consumes Arryved data rather than writing orders into it. No delivery aggregator or order middleware appears anywhere in the corpus. The only inbound order channels documented are first-party (Arryved Online, OpenTab), routed through the Arryved Print Controller app rather than a public endpoint. developer.arryved.com and api.arryved.com are NXDOMAIN (re-probed 2026-09-04 with the CA bundle armed). Arryved does issue partners a credential - Yellow Dog's own setup guide has the merchant fetch an 'API URL' and 'API Key' from Arryved Service - so this is an outbound-only finding, not a no-API-at-all finding. https://support.arryved.com/portal/en/kb/articles/yellow-dog-integration-overview · retrieved 2026-09-04

B
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

The vendor's integration-partners page enumerates Fresh KDS, QuickBooks, 7shifts, MarginEdge, Shogo, BarTrack, Ekos, Yellow Dog and Schedulefly. Not one is a delivery marketplace, and the support KB's list adds only eCard Systems. https://arryved.com/integration-partners/ · retrieved 2026-08-02

B
No

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

extensibility-middleware-compatibility

Neither enumerated partner list contains Deliverect, Chowly, Otter, Checkmate, UrbanPiper or any other order-aggregation middleware, and no public API exists for one to build against unaided. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations · retrieved 2026-08-02

B
Yes

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

Two documented accounting paths with their own KB sections: a direct QuickBooks integration, and Shogo for accounting automation, described on the vendor site as routing to QuickBooks, Xero, Sage and Exact. MarginEdge covers invoice and cost management. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations/quickbooks · retrieved 2026-08-02

B
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

Labour data leaves the platform: the 7shifts integration syncs POS sales and labour data, and any Portal report including hours can be scheduled out as XLS or CSV through Rosie. Shortfall: no payroll provider is integrated directly and no payroll-specific export format is named — the route to payroll runs through 7shifts. https://support.arryved.com/portal/en/kb/arryved-support/arryved-integrations/7shifts · retrieved 2026-08-02

B
No

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

extensibility-app-marketplace

There is no marketplace — just a static page of nine named partners, mirrored by a nine-entry KB section. There is no listing process, no self-serve install or connect flow, no app directory search, and no developer route onto it. https://arryved.com/integration-partners/ · retrieved 2026-08-02

B
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

The MSA §4.4 commitment is real: "Company shall provide access to all Client Data in a commonly used machine-readable format or such other format as agreed by Client and Company." Shortfall: access lasts "no more than thirty (30) days after the termination or expiration", after which "Company may delete Client Data"; it is a request-based process, not a self-serve export; and no format, scope or delivery SLA is specified. https://arryved.com/master-services-agreement/ · retrieved 2026-08-02

B

Reliability, offline & operations

Yes

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

reliability-offline-order-entry

Orders and tabs continue during an outage, with the guidance to prefer Quick Close pay-as-you-go transactions and to let one device manage tabs. Offline actions are checkpointed on-device and replayed on sync. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

B
Partial

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

reliability-offline-card-auth

Cards are accepted offline and settled on reconnect, and Arryved Pay markets "offline EMV payments". Shortfall: there is no authorisation while offline — "credit or debit card transactions are verified for funds after you exit Offline Mode and return online. Some payments may fail" — manual card entry and gift-card payments do not work offline at all, and the offline batch must be synced "within 72 hours of the time of the initial transaction". The vendor marketing page claiming you can "take credit cards, open and close tabs, process orders — all while offline" is contradicted by its own knowledge base. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02 adversarially verified

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 liability is assumed by the vendor or processor. The documentation warns plainly that some offline payments may fail on later verification, and offers no guarantee, floor limit or reimbursement. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

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

Multi-terminal operation does not survive the outage. The Offline Mode article lists device-to-device communication among the functions that stop working until synced, and advises using a single device to manage tabs — so terminals cannot see each other's tabs over the LAN while offline. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

B
Partial

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

There is real local durability: transactions are written to on-device checkpoint files, with dedicated recovery articles for Android 10 or lower, 11+ and 15+, and an exit-and-sync procedure. Shortfall: it is a manual fallback a manager must switch on, it degrades to one authoritative device, sync must happen within 72 hours or data can be lost permanently, and it is not a continuously-running local engine the cloud merely mirrors. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

B
Partial

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

reliability-offline-kds-printing

Printing survives an internet outage provided "your Internal Network's router is functioning", verified by gateway and printer pings in diagnostics. Shortfall: KDS behaviour offline is documented nowhere, and OpenTab orders are explicitly not received while offline, so a digital-ticket kitchen loses a channel. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

B
Partial

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

Automatic failover is a first-class per-peripheral field; the alerting half of the claim is undocumented. Every Merchant Peripheral in Arryved Portal carries a 'Fallback To' setting: 'Fallback is a failsafe method. If a print job fails or devices that route orders to this Peripheral go into Offline Mode, the ticket will print (fallback) to another printer of choice. Select a fallback printer. It can't be a KDS device. A KDS device, however, can have a fallback printer.' A separate 'Mirror To' field gives unconditional duplication on top of it. Named shortfall: nothing in this article, in Printer Diagnostics In Arryved Service, in Printing Preferences or anywhere else in the corpus describes any notification, banner, badge or alert telling staff that a printer has failed and its fallback has engaged - the reroute is silent. https://support.arryved.com/portal/en/kb/articles/adding-a-printer-to-the-portal-for-arryved-service · retrieved 2026-09-04

B
Partial

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

Sync is a documented, deliberate procedure with per-Android-version checkpoint recovery articles behind it when it goes wrong. Shortfall: conflict semantics are never described — the guidance is preventative (one device manages tabs, sync within 72 hours or risk permanent data loss) rather than a documented merge or last-writer-wins rule. https://support.arryved.com/portal/en/kb/articles/exit-offline-mode-and-sync · retrieved 2026-08-02

B
Yes

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

Arryved publishes an explicit list of what does not work offline: employee clock in/out, splitting and merging tabs, manual card entry, gift card sales and payments, receiving OpenTab orders, syncing Portal changes to devices, and device-to-device communication — plus the warning that card funds are only verified after returning online. It directly contradicts the marketing page's "take credit cards, open and close tabs, process orders — all while offline", and the honest document is the one in the KB. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

B
No

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

reliability-public-status-page

Upheld and re-homed off a DNS lookup onto the vendor's own documentation index. The Arryved Merchant Help Center publishes exactly twelve top-level categories, re-read live 2026-09-09 -- Arryved Pay, Portal, Service, Hardware, OpenTab, Online, Insider, Integrations, Web Solutions, ABM, Capital and Emergency Guide -- and the last of those is what Arryved offers INSTEAD of a status page: "Print the 'Oh Snap! Arryved Emergency Guide' for staff to quickly access POS and hardware troubleshooting tips". No status, uptime, incident or trust category exists. Two corroborating measurements, neither of which is the citation: status.arryved.com is NXDOMAIN, and arryved.statuspage.io answers byte-identically (127,605 b, redirected to atlassian.com/software/statuspage) to two fabricated statuspage.io subdomains -- i.e. Arryved has no Statuspage tenant at all, which is a sharper result than a bare failed lookup because the control discriminates. https://support.arryved.com/portal/en/kb/arryved-support · retrieved 2026-09-09

B
Partial

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

The published base plan includes "7 days/week phone & email support" plus unlimited on-demand training. Shortfall: seven days a week is not 24/7 — no hours are published, no overnight coverage is claimed, and no response-time commitment appears on any public page. https://arryved.com/pricing/ · retrieved 2026-08-02

C
No

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

Install is remote-guided self-install throughout, and Arryved says so where an on-site visit would have to be named. Hardware Considerations: 'Your Printers won't come pre-configured from our hardware department; you'll have to configure them yourself at home. However, your Implementation Manager will schedule a hardware installation call with you to help you through it', and 'You'll need to configure your POS Device at home.' Hardware ships rather than arrives with a technician: 'We ship hardware through FedEx Ground from our warehouse in Boulder, CO 80301.' The KDS article puts the boundary explicitly on the merchant's side of the door: 'You can call your Implementation Manager or the Arryved Support team to help you with configuration needs, but a PC on site is needed for our staff to guide you through it.' The onboarding path is enumerated twice and an on-site visit is in neither - the Launch Call is a video call ('You'll need access to your Google account so can join the Launch Call via Google Hangout') and arryved.com/pricing/ gives Onboarding as exactly two bullets, 'Work with a dedicated Arryved rep from start to finish' and 'Choose from a variety of training options to fit your needs'. There is no dealer, VAR or reseller channel anywhere on arryved.com or in the corpus. https://support.arryved.com/portal/en/kb/articles/things-to-consider-when-making-your-first-hardware-order-9-5-2022-1 · retrieved 2026-09-04

B
Unknown

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

reliability-menu-build-service

CLAIM: vendor performs initial menu build in onboarding. VERDICT: unknown (unchanged). NEW: the onboarding root (42 articles) is now read in full via the KB API. What Is A Launch Call? enumerates the agenda - "Discuss Your Launch Timeline / Review Documentation / Discuss Arryved Products / Introduce The Arryved Academy Training" - and its three documents (Underwriting; an Onboarding Guide used "to collect all other relevant information about your business, network, and main points of contact"; Hardware Catalog); no menu or inventory build is named (https://support.arryved.com/portal/en/kb/articles/what-is-the-launch-call). Signals toward vendor help: "Your Implementation Manager may have entered some for you during the launch process" (peripherals; adding-a-printer-to-the-portal-for-arryved-service); for ABM, "During your ABM onboarding, your Implementation Manager helps add your initial Inventory to your ABM" (abm-inventory); "An Arryved specialist can help bulk upload your Online Shop Product SKUs" (arryved-inventory-sync-integration). Signals away: the menu/inventory articles are written for the merchant to build. The "Arryved Portal Build Self-Implementation" article named in the prior note is not in the 539-article listing, is not returned by the portal search API (searchStr "portal build", "self-implementation"), and guessed permalinks 404 - it is no longer published. SURFACE (new 2026-09-16): the Zoho Desk portal's anonymous JSON API, https://support.arryved.com/portal/api/kbArticles?portalId=<portal id from the KB page>&from=N&limit=50, lists 539 articles across 4 root categories (Product Support 400, Onboarding 42, Release Notes 68, remainder not returned under a root filter); per-article /portal/api/kbArticles/<id> returned 510 bodies at 200 and 29 at 403 (all 29 are Arryved Insider loyalty or Arryved View digital-menu articles; their listing summaries are readable). Href fixpoint over the 510 bodies found 64 article slugs not in the listing; articleByPermalink probes: 37 resolve (200) to already-listed articles under old slugs, 5 are 403 (all card-reader pairing/troubleshooting: pairing-a-new-bluetooth-swiper-ble, bbpos-chipper-credit-card-reader-initial-setup, bluetooth-swiper-ble-troubleshooting, sw, troubleshootingbbposchipper), 22 are 404, and a nonsense-slug control is 404. The listing is therefore a census of anonymous-readable bodies plus 34 gated articles whose topics are known. The portal's own search API (/portal/api/kbArticles/search?searchStr=) was also queried. Retrieved 2026-09-16. || 318th: NEW (2026-09-16): the complete Portal v2 bundle (https://portal.arryved.com/v2/main.js, 206-entry nav) lists Arryved-internal SUPERUSER tools; the only import tools are gift-card importers ("DATA_IMPORT_UPLOADER ... Arryved Internal: Gift card data importer tool for .csv files", DATA_IMPORT_LIST, GIFT_CARD_UPLOADER). No internal menu/inventory import or build tool is exposed to Arryved staff in the Portal, which weakly leans away from a staff-performed menu build but does not exclude one done through the ordinary merchant screens. Retrieved 2026-09-16. || 322nd: VERDICT: unknown (held). NEW SURFACE (2026-09-17): the LEGACY Portal (PV1) is now a closed census. https://portal.arryved.com/js/scriptLoader.js (production, anonymous, 7,059 bytes; "const version = '2.27'") holds the literal ordered list of every PV1 script ("Loads all the scripts in order"; a TODO says on-demand loading is NOT implemented). All 125 listed scripts fetched at 200 (2,109,784 bytes, unminified source, none a soft-404 shell), plus the 92 page templates they load via app.Ajax.page('./html/...') (all 200, 523,980 bytes; a nonsense /html/ path returns 404 "Resource not found", so these are real). The only other dynamic loads are ag-grid vendor imports and the Google Maps loader; app.Pages.guideLoader reads app.Guides.config, which no script defines (/guides/tooltips.html 404), so it is dead code. Together with the complete PV2 bundle (portal.arryved.com/v2/main.js, prior note) both generations of the operator Portal are now held whole. The PV1 SUPERUSER (Arryved-internal) tools are enumerated: bpeiManagement, companyIds, consumerTool, createCompany, dataImportList, dataImportUploader, device* reports, discrepancyList, domainObjects, experiments, giftCardUploader, locPrefUsage, locationNotes, loyaltyToolsNew, optimisticAuthDashboard, tabDataNew/tabDataTools. The Data Import Uploader handles only gift cards: `var importTypes = ["ngc","egc"];` (pages/superUser/dataImportUploader.js). No internal menu/inventory import tool exists for staff in either Portal generation; the only menu copy tools are merchant-facing "Clone Menu" / "Clone Item" buttons (venue/createMenu, editMenu templates). Weakly leans away from a staff-run bulk menu build but does not exclude implementation staff using the ordinary screens, so not a no. Retrieved 2026-09-17. || 327th: 327th, NEW SURFACE with evidence pointing BOTH ways, which is why this stays unknown rather than moving. (1) The public pricing page enumerates exactly what Onboarding includes and a menu build is NOT in it: 'Onboarding - Quickly get started with onboarding tailored to you: Work with a dedicated Arryved rep from start to finish; Choose from a variety of training options to fit your needs' (https://arryved.com/pricing/). That is the second enumeration to omit it, after the KB's Launch Call agenda. (2) But the same 375-page site census surfaces Arryved's own cost blog treating a menu build as a CHARGEABLE extra that vendors may levy - 'Some companies charge for onboarding ... Here are some typical prices for those that do: Custom Menu Build: $400+' - which is industry framing, not a statement about Arryved's own practice, and it cuts against reading the pricing page's silence as a denial. With the KB's contrary signals still on record ('During your ABM onboarding, your Implementation Manager helps add your initial Inventory to your ABM'), a `no` would over-read two omissions. BOUND: arryved.com sitemap 380/380 fetched today, 3,704,288 chars; 'menu build' 1 hit (quoted above), 'build your menu' 0. Retrieved 2026-09-18. || 328th: 328th: the Master Services Agreement was read against THIS cell for the first time (the 327th read it only for the API-cost cell). Re-derived corpus: the MSA page stripped to 69,277 chars, tokenised controls run with a known-positive (`the` 501). RESULT: `onboarding` 0, `implementation` 0, `installation` 0, `install` 0, `setup` 0, `menu build` 0. The only three `menu` hits are the site's global nav chrome present on every page ('Digital Menu Hub', 'Streamlined service with powerful menu control'), and all five `training` hits are poison - the Documentation licence ('for training and education of Authorized Users') and the AI clauses ('training, improving, and enhancing AI models'). WHAT THE MSA DOES ESTABLISH, and it is new: every service beyond the subscription is routed to an unpublished separate document. 'Order Form means a separate ordering agreement (including but not limited to a statement of work, proposal, or change order), or page on the Site pursuant to which Client purchases Services'; 'All work product, customizations, improvements, and/or enhancements to the Services performed by Company for Client pursuant to this Agreement or as identified on any separate Order Form executed by the parties (collectively, "Professional Service Deliverables")'; and 'In the event there is any conflict between the terms and conditions in this Master Service Agreement and the terms and conditions in any applicable Order Form, the terms of the Order Form shall prevail.' So Arryved's own contract structure puts implementation scope in an SOW it does not publish - which is why the pricing page's Onboarding bullet list and the KB's Launch Call agenda can omit a menu build without that omission being a denial. This is the THIRD vendor enumeration to omit it and the reason it still cannot become a `no`. Retrieved 2026-09-18. || 329th: MERGE HOLD (proposed partial/B, held unknown): The vendor-performed load is documented for the ABM brewery-inventory module and Shop SKUs, not the POS menu; every POS menu guide assigns the build to the operator. An adjacent module's onboarding is not part of this claim (326th: adjacent feature is not a partial), and the agent notes it could equally read as no. Held. PROPOSAL AS WRITTEN: 329th: worked per-cell against the KB onboarding path, which no prior pass had read end to end, and it resolves the 327th's both-ways deadlock into a PARTIAL with a nameable shortfall rather than another omission argument. WHAT THE VENDOR DOES DO: 'During your ABM onboarding, your Implementation Manager helps add your initial Inventory to your ABM' (https://support.arryved.com/portal/en/kb/articles/abm-inventory), and on the Shop side 'If you're working with a long list of Inventory Items, we can help save you some time. An Arryved specialist can help bulk upload your Online Shop Product SKUs to your Arryved Portal Inventory Items' (https://support.arryved.com/portal/en/kb/articles/arryved-inventory-sync-integration). So a vendor-performed initial item load is documented, not absent. THE SHORTFALL, which is why this is not a `yes`: every guide that covers the POS menu/item build itself assigns the work to the operator, not to Arryved. 'Anything you'd like to offer on your menus, such as food, drinks, and merch, will be added to your Arryved Portal as Inventory Items. Use this guide to learn how to create and customize your Inventory Items ... Head to your Arryved Portal ... Click New Item + to create a new Inventory Item. Fill out the Inventory Item page' (https://support.arryved.com/portal/en/kb/articles/building-inventory-items, mod 2025-10-01); the ABM Onboarding Guide's own five steps are addressed to 'an ABM User with the Admin User Role' ('Step 2: Add Items ... Use the Materials guide. Use the Finished Goods guide'); and the Launch Call article enumerates the Implementation Manager's deliverables in full - 'Discuss Your Launch Timeline, Review Documentation, Discuss Arryved Products, Introduce The Arryved Academy Training', with the three documents being Underwriting, the Onboarding Guide and the Hardware Catalog - with no build and no data-entry deliverable (https://support.arryved.com/portal/en/kb/articles/what-is-the-launch-call). So the vendor's assistance is a helping hand on ABM inventory and a spreadsheet-driven SKU bulk load, while the POS menu build is the operator's job through the Arryved Academy. BOUND: 510/539 KB articles (the 29 gated are Insider / View Designer / Managing-Inventory-Items; the First Steps, ABM Onboarding, Creating Inventory and Menus categories are fully held), plus the 375-page arryved.com census and the MSA. Controls: 'white glove' 0, 'done for you' 0, "we'll build" 0, 'build it for you' 0, 'menu build' 1 (the cost-blog line about other vendors already on record), 'build your menu' 0. Retrieved 2026-09-18. adversarially verified

F
Partial

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

reliability-hardware-replacement-sla

A documented warranty programme, not a turnaround SLA: Samsung tablets carry a 1-year manufacturer warranty with an optional purchased 3-year accident cover limited to one replacement, MagTek readers and Epson printers 2 years; Arryved handles the return process and pays shipping for in-warranty defects, and offers a loaner device 'for an additional per-week cost' to merchants who bought their own hardware. Shortfalls: no stated replacement or advance-exchange turnaround time, no loaner terms for catalog-bought devices, and warranties are 'non-negotiable since they are set by the hardware manufacturer'. https://support.arryved.com/portal/en/kb/articles/warran · retrieved 2026-09-03 adversarially verified

B
Partial

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

A real, named PCI DSS v4 programme exists: SecurityMetrics is the compliance partner, merchants complete SAQs and scans against a deadline, FullsteamPay Hosted Payments is the prescribed method, and $100,000 breach protection is bundled. Shortfall: no Arryved or Fullsteam Attestation of Compliance is published for merchants to review, and the obligation is pushed onto the merchant — "if you fail to become compliant, you're charged an additional monthly fee until you pass compliance". https://support.arryved.com/portal/en/kb/articles/pci-compliance-overview-arryved-pay · retrieved 2026-08-02

B
Partial

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

reliability-mfa-role-based-access

Role-based access is strong and granular — fourteen named permissions per labor role, an OWNED TABS ONLY restriction, a Super Admin gate on forensic reporting, and manager-code approval for comps and transfers. Shortfall: no multi-factor authentication on Arryved Portal login is documented in the Logging In section or anywhere else, and POS identification is a numeric clock-in code. https://support.arryved.com/portal/en/kb/articles/labor-roles-permissions · retrieved 2026-08-02

B
Yes

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

reliability-self-serve-training

A fully public, unauthenticated knowledge base across twelve product areas with hundreds of task-level articles, plus a printable Emergency Guide for POS and hardware failures, plus "unlimited on-demand training" in the published base plan. https://support.arryved.com/portal/en/kb/arryved-support · retrieved 2026-08-02

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

There is no designated master or failover terminal. Offline Mode is entered manually per device by a holder of the HARDWARE permission, device-to-device communication stops, and the documented mitigation is a convention — use one device to manage tabs — rather than an elected local server role. https://support.arryved.com/portal/en/kb/articles/enter-offline-mode · retrieved 2026-08-02

B
No

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

reliability-cellular-backup

The network article is where automatic failover would be specified, and what it specifies instead is a human plugging in a hotspot: under Connectivity Testing and Maintenance, 'Keep a backup hotspot or secondary internet connection for redundancy during outages.' The same article disclaims the WAN entirely - 'Your business network is handled by your Internet Service Provider (such as Comcast, Quantum Fiber, etc.). Although Arryved provides best-practice recommendations... the setup, management, and maintenance of your network are the sole responsibility of your team and your ISP' - and its topology diagram enumerates only Wi-Fi SSIDs and hardwired devices, with no WAN failover leg. The documented product response to losing internet is Offline Mode, not a second link ('Offline Mode is your uncanny fail-safe plan to continue business when you can't connect to the network'). No Arryved-sold LTE router, modem or data plan appears in the Hardware Catalog's enumerated categories. https://support.arryved.com/portal/en/kb/articles/network-best-practices · retrieved 2026-09-04

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

MSA §8.1: the Agreement "shall continue for twelve (12) months thereafter (the 'Initial Term')" and "shall automatically renew for additional, successive twelve (12) month terms unless either party provides written notice of termination...no less than ninety (90) days prior to the end of the then current term." https://arryved.com/master-services-agreement/ · retrieved 2026-08-02

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

MSA §8.4 imposes liquidated damages: "Client shall forfeit all pre-paid amounts for Fees, and for those arrangements in which the Fees are not paid in advance, Client shall pay Company an amount equal to the monthly Fee multiplied by the number of months remaining in the Term." https://arryved.com/master-services-agreement/ · retrieved 2026-08-02

B
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

The auto-renewal mechanics are published in full and in public on the vendor's own site: twelve-month initial term, successive twelve-month renewals, ninety days' written notice to stop it, plus a stated right for Company to terminate on thirty days' notice. https://arryved.com/master-services-agreement/ · retrieved 2026-08-02

B
No

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

MSA §6.6 makes Arryved's own processing mandatory: "Client must be enrolled in and processing payments through Company's integrated payments processing platform within sixty (60) days of the Effective Date." Software and processing cannot be bought apart. https://arryved.com/master-services-agreement/ · retrieved 2026-08-02

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

No pricing model is published at all, let alone interchange-plus. The fee-structure article names eleven fee lines and states outright that "the actual dollar amounts of the fees are not mentioned in this guide because they may fluctuate over time or vary depending on your processing volume and business operations". https://support.arryved.com/portal/en/kb/articles/arryved-pay-fee-structure · retrieved 2026-08-02

B
No

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

The clause exists and is entirely one-sided: MSA §5.1, "Company may adjust Fees at any time with thirty (30) days' notice." There is no cap, no index, no cure period and no matching right for the merchant to exit without the §8.4 liquidated damages. https://arryved.com/master-services-agreement/ · retrieved 2026-08-02

B
Partial

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

One real published figure — "starting at $99.99/month" for 1-9 devices at a single location, including cloud software, mobile devices, online ordering tools, integrations, 7-day phone and email support, unlimited on-demand training and onboarded setup. Shortfall: 10+ devices or 2+ locations is "contact us for a quote", and no per-additional-device increment, module price, hardware price or card rate is published anywhere. https://arryved.com/pricing/ · retrieved 2026-08-02

C
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

Modules are genuinely separable and separately sold — the Digital Menus guide states it is "an additional subscription service" requiring a conversation with sales, and Arryved Brewery Management, Web Solutions, Insider and Arryved Capital each have their own onboarding. Shortfall: not one module price is published, so the unbundling is visible in the product structure but not in the commercials. https://support.arryved.com/portal/en/kb/articles/digital-menus-quickstart-guide · retrieved 2026-08-02

B
Yes

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

Outright purchase is offered and conveys title. MSA §15: "For Equipment purchased from Company, title to such Equipment shall not pass to Client until all amounts for the purchase of such Equipment have been paid by Client to Company." The fee list carries a Terminal Purchase Fee alongside a Terminal Lease Fee, and Arryved Pay states "lease or buy, you decide". https://arryved.com/master-services-agreement/ · retrieved 2026-08-02

B
Yes

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

Arryved 'doesn't manufacture these products, we partner with Samsung, Magtak, Epson, and other hardware creators', and the warranty article explicitly contemplates merchants who 'purchased your own devices'; the End Of Life guide has merchants install Arryved Service from the Google Play Store onto supported devices, and the Fresh KDS hardware article allows 'other devices you may already have' provided they are Google Play certified. Standard Samsung Android tablets, Epson printers and a generic RJ12 cash drawer are the documented stack. Caveat: Arryved Pay card readers are leased MagTek units (a Terminal Lease Fee appears on statements), so the payment device is the one vendor-tied component. https://support.arryved.com/portal/en/kb/articles/warran · retrieved 2026-09-03 adversarially verified

B
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

Some exports are genuinely self-serve: the Insider Member list exports from the Insider Members page, and Portal reports can be produced on demand. Shortfall: scheduled report delivery must be set up by Arryved Support or an Implementation Manager, bulk gift-card changes are a support request, and the full data set under MSA §4.4 is obtained by asking Arryved rather than by pressing a button. https://support.arryved.com/portal/en/kb/articles/how-to-get-your-insider-member-report · retrieved 2026-08-02

B
Yes

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

All three asset classes are exportable. Guest records and loyalty: "In Arryved Portal, from the Insider Members page, you can export a full list of your Members" as CSV with contact info, Balance and Lifetime points. Gift-card liability: the Gift Cards Overview documents a Gift Card Liability Report that "displays a list of all gift cards and their current balance with a summary line with the total gift card liability", alongside a Gift Card Activity Report and a Gift Card Modification Log. https://support.arryved.com/portal/en/kb/articles/how-to-get-your-insider-member-report · retrieved 2026-08-02 adversarially verified

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

A window is contractually granted, which many vendors do not do: MSA §4.4 obliges Arryved to provide access to all Client Data in a commonly used machine-readable format on termination. Shortfall: it lasts "no more than thirty (30) days after the termination or expiration of the Agreement. After this thirty (30) day period, Company may delete Client Data in accordance with its standard schedule and procedures." https://arryved.com/master-services-agreement/ · retrieved 2026-08-02

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

The MSA does leave Client Data with the client — Client retains rights to Client Data and can demand it back in machine-readable form under §4.4. Shortfall: Company owns Anonymized Data, Feedback and Professional Service Deliverables outright, and Client grants Company a broad licence to use Client Data for service provision and for AI model improvement, so the derived layer belongs to the vendor. https://arryved.com/master-services-agreement/ · retrieved 2026-08-02

B
Partial

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

Cardholder data is kept out of the merchant's hands in practice — FullsteamPay Hosted Payments is the prescribed e-commerce method, EMV card-on-file is marketed, and cards can be stored against Insider accounts and tabs, all of which implies a vault. Shortfall: no validated P2PE solution is named and no tokenization architecture, token scope or key-management description is published. https://support.arryved.com/portal/en/kb/articles/pci-compliance-overview-arryved-pay · retrieved 2026-08-02

B
Partial

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

PCI DSS v4 is explicitly in force with a named validation partner (SecurityMetrics), merchant SAQs and scans, the March 2025 e-commerce requirement called out, and $100,000 breach protection bundled. Shortfall: the controls documented are the merchant's obligations and the penalty for missing them; no vendor-side control description, AOC, SOC 2 report or security whitepaper is published. https://support.arryved.com/portal/en/kb/articles/pci-compliance-overview-arryved-pay · retrieved 2026-08-02

B
No

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

Data-subject requests are handled by email to compliance@fullsteam.com / Fullsteam Operations LLC. There is no self-serve DSAR intake, no guest-data lookup-and-delete tool in Arryved Portal, and no documented turnaround commitment. https://arryved.com/privacy-policy/ · retrieved 2026-08-02

B
Partial

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

Structured as a cash discount rather than a surcharge — "Dual Pricing is NOT surcharging" — applying to credit and debit in all 50 states, with receipt disclosure documented: "The printed bill is your friend! It shows the Non-cash Total and the Cash Total." Shortfall: no debit or prepaid exclusion mechanism exists (the model deliberately covers both), no network percentage cap is enforced or described, and menu-board disclosure is asserted only on a marketing blog, not in the setup documentation. https://support.arryved.com/portal/en/kb/articles/dual-pricing-overview · retrieved 2026-08-02 adversarially verified

B

Adversarial verification

An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 24 values — 17 upheld, 7 downgraded, 0 upgraded. It separately resolved 60 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.processing_ratedowngrade-to-partialCorrection in Arryved's favour, mislabelled by the verdict vocabulary. The field is too absolute: Arryved's own knowledge base publishes one rate, "a flat rate of 3.99%" for the Dual Pricing program, stated to roll up interchange, association fees and per-transaction costs. The rest of the field survives — the fee-structure article still names eleven fee lines and declines to publish amounts, and standard non-dual-pricing processing remains quote-only. Field text amended to lead with the 3.99% and then state its condition, because a buyer comparing effective card cost needs that number and would not have found it in this record. source
api_posture.webhooksupheldConclusion upheld, supporting statement corrected. Yellow Dog's page describes Arryved pushing sales data to Yellow Dog's API on an Arryved-determined schedule; the hourly default belongs to Yellow Dog's own sync applications, not to Arryved. The accurate characterisation is a scheduled one-way batch push to a single partner endpoint, not polling of Arryved. Either way there is no webhook product, no callback registration, no signing and no retry documentation, so "none documented" stands. source
pricing.softwareupheldPricing figures are the second-most-challenged thing in this corpus, so I re-fetched rather than assumed. The pricing page reads "Starting at $99.99/month" for 1-9 devices, bundling mobile devices, online ordering tools, integrations, 7-day phone and email support, unlimited on-demand training and a dedicated rep; 10+ devices or 2+ locations is "a customized quote for your business". No tier names, no per-device increment and no module prices are published. Figure and framing both confirmed. source
pricing.early_termination_feeupheldRead the MSA rather than the summary. Section 8.4 imposes remaining-term damages on early termination: forfeiture of prepaid fees, and otherwise "the monthly Fee multiplied by the number of months remaining in the Term". Section 5.1 confirms "Company may adjust Fees at any time with thirty (30) days' notice", and §8.1 confirms the twelve-month auto-renewing term with ninety days' notice. One provision the record carries only in prose and should not lose: §6.6 requires enrolment in Company's integrated payment solution "within sixty (60) days of the Effective Date", with suspension, feature restriction, fee increases or processing penalties available to Company if the client does not. source
org.nameupheldOwnership assertions about a named business get checked directly. Fullsteam's hospitality page lists Arryved alongside Maestro, Silverware, Club Prophet and The Flybook. I found no acquisition announcement or date on either newsroom, so the record's refusal to state one is correct. Fullsteam's 60,000+ customer figure remains a portfolio-wide number and is correctly kept out of identity.scale. source

Capability claims

ClaimAs first scoredVerdictWhat the verifier found
payments-offline-store-and-forwardyes / B, cites enter-offline-mode: "Cards are captured while offline and settled later... Offline actions are checkpointed on-device and synced on reconnect"downgrade-to-partialI retrieved the Offline Mode article myself. It confirms cards are taken offline and verified later, but the taxonomy claim requires store-and-forward WITH configurable per-transaction and cumulative offline limits, and Arryved documents no limit of any kind — no floor limit, no per-ticket cap, no aggregate exposure cap, no card-type restriction. What it documents instead is a hard deadline and an explicit failure mode: "You must sync your Offline Mode actions within 72 hours of the time of the initial transaction", and "Credit or debit card transactions are verified for funds after you exit Offline Mode and return online. Some payments may fail." Manual card entry and gift-card payment do not work offline at all. Unbounded offline exposure plus a 72-hour data-loss window is the second half of the claim failing, not a footnote. source
guest-loyalty-data-export-portabilityyes / B, cites how-to-get-your-insider-member-report: "you can export a full list of your Members"downgrade-to-partialI pulled the Insider Member Report article. The export is real and genuinely self-serve — Super Admin, Insider Members page, Get Report, emailed to the logged-in user, and "The report can only be sent in a .CSV format" — carrying first/last name, email, phone, Visits, Last Visit, Avg Spend, Balance and Lifetime points. But the claim is "the full guest list AND transaction history", and this file contains aggregates (visit count, average spend), not the transaction record. The record contradicts itself here: api_posture.data_export_on_exit already states "there is no self-serve bulk export of the transaction record", and the sibling cell commercial-data-export-self-serve is scored partial on the same facts. Guest list yes, transaction history no. source
menu-pricing-dual-pricingyes / B, cites dual-pricing-overview: "prices depend on the payment method chosen, cash or non-cash", printed bill shows both totalsdowngrade-to-partialThe claim requires dual pricing "applied consistently across POS, kiosk, and online ordering". I read the Dual Pricing Overview: it is scoped to the POS app, and says so through its prerequisites — "Android 9 OS or higher" and "Arryved Service v1.24+". Nothing in it addresses Arryved Online or OpenTab, and the record's own digital-surcharge-transparency cell concedes the same gap. Separately, the claim wants the card price displayed as the base price; the KB describes the opposite configuration direction ("current prices become Cash Prices, with Standard Prices set 4-5% higher"), and the only statement that the displayed menu price is the card price — "Menus list everything in card prices, including sales tax" — is on a marketing blog, grade D, not in documentation. Shortfall: documented for the POS only, with online-channel behaviour unevidenced. source
commercial-dual-pricing-compliantyes / B, cites dual-pricing-overview: "Dual Pricing is NOT surcharging", permitted in all 50 states, both totals on the printed billdowngrade-to-partialI confirmed the article's compliance framing verbatim and the receipt disclosure — "The printed bill is your friend! It shows the Non-cash Total and the Cash Total." But the claim has three limbs and only one is documented. There is no debit/prepaid exclusion mechanism: the article states dual pricing deliberately applies to both credit and debit, which is defensible for a cash discount but means no BIN or product-code exclusion exists to point at. And the required menu-board disclosure is attested only on a marketing blog ("Menus list everything in card prices, including sales tax"), not in the setup documentation — the dual-pricing setup-guide slug the overview points to 404s to me. A compliance cell scored on a blog post is exactly the pattern this pass exists to catch. source
payments-published-ratesno / B, cites arryved-pay-fee-structure: "the actual dollar amounts of the fees are not mentioned in this guide"downgrade-to-partialThis correction runs in Arryved's favour — the verdict vocabulary has no upgrade-to-partial token, so read it as no moving to partial. The researcher's premise is refuted by Arryved's own knowledge base: the Dual Pricing Overview states "The Dual Pricing program eliminates the fluctuation of the per transaction fees and offers a flat rate of 3.99%", covering interchange, association fees and per-transaction costs. That is a specific published flat rate in first-party documentation, which is precisely what the claim asks for. It is not a full yes: the 3.99% applies only to merchants who adopt Dual Pricing, and for everyone else the fee-structure article still names eleven fee lines and publishes no number. Shortfall named: one published rate, conditional on one program. source
payments-tip-poolingunknown / Fresolve-to-yesGenuine miss, and a host-coverage miss rather than a judgement error: tips are documented on onboarding.arryved.com, a third Zoho knowledge base this pass never walked (it used support.arryved.com and help.arryved.com). The Tips section documents three tipping models as first-class options — "Tip Pooling: Tip sharing by day or by shift" and "Individual Tip Outs: Employees keep the tips they've earned. No tip pooling." Pooling by shift works on labour hours: "Tip pool segments are created throughout the day by clock in and out times", allocated through the Tips By Labor Hours report, with the End of Day Tool as "your all-in-one solution to managing your daily tip pool and nightly cash deposit" and the ability to adjust tipped hours and add cash tips to the pool. Per-employee allocation lands in a named Payroll Report and an Employee Time Card With Tips report. The claim's parenthetical is disjunctive (hours worked, sales, role percentage, or points) and the hours-worked branch is fully documented. Role-weighted and points-based splits are not documented and are stated as a limit in the note. source
reliability-menu-build-servicepartial / C, cites arryved.com/pricing: base plan includes "onboarded setup with a dedicated representative"downgrade-to-unknownA differentiator scored partial on a pricing page, where the note itself concedes "a menu-build service is not named as a deliverable anywhere". I fetched the pricing page: it lists a dedicated rep, training options and onboarding support, and says nothing about who enters the menu. The evidence points mildly the other way — the onboarding knowledge base carries a section titled "Arryved Portal Build Self-Implementation" — but that article 404s to me, so I will not score a no on it either. Nothing retrievable establishes that Arryved performs the initial build, so this is unresolved rather than partly true. source
payments-dual-pricingyes / B, cites dual-pricing-overviewupheldHeld to the differentiator bar and it clears on its own terms, unlike the two sibling dual-pricing cells. This claim asks only for two stored prices per item and both totals printed on the check. Both are documented: current prices become Cash Prices with Standard Prices set 4-5% higher, and "The printed bill is your friend! It shows the Non-cash Total and the Cash Total", with the digital signature screen showing the guest only the total for the method they chose. Grade B documentation, retrieved by me. source
order-capture-bar-tab-preauthyes / B, cites pre-authorization-with-arryved-pay: "$20" default, 48-hour drop-offupheldRetrieved the article and confirmed every figure: "Your Pre-auth amount is initially set to $20", "when a tab is opened with a card-on-file, a $20 hold is placed on the card", "If the final bill is more than the Pre-auth amount, we run an additional authorization when closing the tab to charge for the difference", and "For any tabs rolling over to the next day, the pre-auth will automatically drop off after 48 hours if the tab is still open." One detail the researcher omitted and an operator will be asked about: unused hold funds reverse in 3-4 business days on average and can take 7-10. source
hardware-ownership-vs-leaseyes / B, cites MSA §15 title provision plus Terminal Lease Fee and Terminal Purchase FeeupheldRead the MSA myself. Section 15 conveys title on outright purchase — "title to such Equipment shall not pass to Client until all amounts for the purchase of such Equipment have been paid by Client to Company" — which only makes sense if purchase is an available route, and the Arryved Pay fee schedule carries both a Terminal Lease Fee and a Terminal Purchase Fee. The claim requires purchase as an alternative to a mandatory lease and that the vendor states which; both hold. No purchase price is published anywhere, which is correctly scored no on hardware-pricing-transparency and is not double-counted here. source
commercial-export-customer-and-loyaltyyes / B, cites the Insider Member Report for guest records and loyalty balancesupheldThis claim has three limbs — guest records, loyalty balances, and gift-card liability balances — and the researcher evidenced only the first two. I went looking for the third expecting to downgrade and found it instead: the Gift Cards Overview documents a "Gift Card Liability Report" that "displays a list of all gift cards and their current balance with a summary line with the total gift card liability", alongside a Gift Card Activity Report and a Gift Card Modification Log. Combined with the Insider Member CSV (contact PII, Balance, Lifetime points), all three limbs are documented. Upheld on evidence the record did not cite, now carried in the note. source
reliability-offline-card-authpartial / B, shortfall named as no authorisation while offlineupheldChecked because a conclusion-flipping cell deserves it, and the partial is right for a reason the researcher understated. The support article and the marketing page disagree outright: arryved.com/solutions/offline-mode claims "Take credit cards, open and close tabs, process orders — all while offline", while the knowledge base says funds are "verified for funds after you exit Offline Mode and return online. Some payments may fail", manual entry is unsupported, and tabs cannot be split or merged. The knowledge base is the document to score. The 72-hour sync deadline belongs in the shortfall — it is the hard edge of the capability. source
reporting-webhooksno / E, cites Yellow Dog: "the one publicly documented data pipe out of Arryved is scheduled polling, not push"upheldVerdict stands but the stated reasoning is wrong and would embarrass the record if a partner read it. I retrieved the Yellow Dog page: the hourly schedule belongs to Yellow Dog's own applications ("can be run at any interval, but will be scheduled at the top of each hour by default"), while Arryved's side is described as a push — "Arryved Service's sync application pushes sales data to the Yellow Dog API at a frequency determined by Arryved Service." So Arryved does emit outbound data, but as a scheduled batch push to one partner's hard-wired endpoint. The claim needs webhooks to a customer-supplied endpoint with documented retry and payload signing; none of that is published, and a claim phrased around documentation fails definitively when no documentation exists. Note corrected accordingly. source
extensibility-webhooks-pushno / E, cites Yellow Dog: "The documented integration pattern is scheduled polling"upheldSame misreading as reporting-webhooks, same corrected conclusion. Arryved pushes rather than being polled, but on a schedule Arryved sets, to a single named partner API, carrying sales data only. There is no subscribable order-lifecycle event (created, modified, paid, voided, refunded) and no customer-configurable callback URL in any Arryved or partner document I could retrieve. Value unchanged; note rewritten so it no longer asserts polling. source
extensibility-oauth-partner-appsno / E, cites Yellow Dog: static shared secret rather than delegated authorisationupheldConfirmed from the integrator page directly. Setup requires the merchant to obtain an "API URL" and "API Key" plus "a list of all Location IDs (Revenue Center Codes)" from Arryved and hand them over. A bearer key scoped to the whole account, with no consent screen, no scopes and no per-app revocation, is positive evidence against OAuth rather than mere absence of it — this is the one documented auth model Arryved has. source
order-capture-kiosk-first-partyno / B, cites the Hardware KB enumerating eight device categories with no kioskupheldVerified the enumeration myself rather than trusting it: the Hardware section lists POS Devices, Card Readers, Printers, Print Controller, Cash Drawer, Barcode Scanners, Your Network and Epson KDS. No kiosk, no kiosk enclosure, no kiosk app. Arryved positions self-service as the guest's own phone via QR ordering, not merchant-owned hardware, and no ADA or accessibility conformance statement exists to satisfy the second half of the claim. A vendor hardware catalogue that enumerates its categories is legitimate positive evidence of absence. source
order-capture-order-ready-signalno / B, cites ORDER Screen Overview: no guest-facing ready notification documentedupheldChallenged because a trap sits next to it: Arryved's Fresh KDS announcement does advertise customisable texts telling a guest when an order is received and when it is ready. That is guest SMS, and it is a partner's feature. This claim is narrower — an order-ready signal pushed back to third-party marketplaces from POS or KDS state. Arryved integrates with no marketplace at all, so there is nothing to signal. No is correct; the note now says why the Fresh KDS texting does not satisfy it, so a later pass does not upgrade the cell on that press release. source
delivery-3p-direct-integrationno / B, cites arryved.com/integration-partners enumerating nine partnersupheldRe-enumerated the partner page independently and got exactly the same nine: Fresh KDS, QuickBooks, 7shifts, MarginEdge, Shogo, BarTrack, Ekos, Yellow Dog, Schedulefly. No DoorDash, Uber Eats or Grubhub, and no middleware — no Deliverect, Chowly, Otter, Checkmate or UrbanPiper. A first-party integration directory that enumerates its entire catalogue is the strongest form of positive absence available, and it is what makes the eight no values across the delivery block defensible rather than lazy. source
labor-tip-pooling-rulesunknown / F -- A TIP PAY permission exists and tips can be added to closed tabs, but no tip pool, tip-out percentage or distribution rule configuration is documented....resolve-to-yesThe prior rationale searched the arryved-support KB tree and found only a TIP PAY permission. The tip documentation lives in a sibling tree, arryved-onboarding/tips, with four subcategories and 20 articles. Read all of them: Reports With Tips Overview (12 tip reports), Tip Points Overview (weighted per-role points per hour, published formula), End of Day Tool and its Summary (daily pool, adjustable amount and tipped hours), Tips By Labor Hours in two variants (shift pools bookended by punches, by tab close or by order timestamp), Employee Time Card With Tips, and the cash tip tab article. That is automatic computation from hours, points and role rules, natively, at grade B. Caveats recorded in the note: Implementation Manager must enable each report, exact percentage splits are stated as hard to reproduce, reports run after batch time. Table-stakes weight; B evidence; yes. source
labor-tip-distribution-audit-trailunknown / F -- With no documented tip pooling engine, no distribution ledger or audit trail is documented either; tips appear only as amounts on tabs and in the Sales Summary....resolve-to-partialRead End of Day Tip Summary, Employee Time Card, TBLH and Cash Action Log. Per-employee, per-day or per-segment distribution records exist and download, and the Summary tracks paid versus owed. But the reports do not itemise what each employee contributed to the pool, the End of Day Tool is single-entry per day, and Tip Points Overview warns that altering points 'will affect your tip reporting retroactively' and tells merchants to keep copies of past reports -- an audit trail that can be rewritten. Partial with those three shortfalls. source
reporting-tip-tax-complianceunknown / F -- Tips appear on tabs and in the Sales Summary and can be added post-close, but no tip-reporting, allocated-tip or tax-compliance report is documented....resolve-to-partialRead Employee Tip Collection (tips per employee by payment type: card/gift versus cash/check), Cash Action Log and Emp. Cash Handling (declared tips via Cash Actions and Forced Tip Claim at clock-out), and Payroll (Shift Tip). Declared-versus-charged per employee and pool distribution detail are covered; a tax liability summary by jurisdiction and any payroll-provider format are not, and the 7shifts integration overview states it 'Does Not Support: Tips & Tip Pooling'. Partial. source
reporting-labor-productivityunknown / F -- Hours are tracked per labor role and sales are attributed to employees, but no report joining the two into sales-per-labour-hour or labour productivity is documented....resolve-to-partialRead the Employee Performance report overview: total sales, comps, tips, hours worked, tabs and orders per tipped employee from clocked hours, filterable by labor role, downloadable. The productivity ratio is derivable but not reported, there is no by-hour or by-department cut, non-tipped roles are excluded, and ranges total rather than break down by day. 7shifts adds a labor-percentage view outside Arryved. Partial. source
payments-house-accountsunknown / F -- Card-on-file tabs and Insider stored cards are documented, but no house account, member charge account, or invoice-on-account payment type appears in the Payment Options section, which enumerates written check, tax exemp...resolve-to-partialThe Payment Options enumeration the prior pass relied on was incomplete: the Gift Card Tool article (Portal > Operations) states 'Use the Tool to create House Accounts, too!' and describes an account with a limit and a running balance that rises with consumption and falls with payment, adjustable with debit/credit/set actions and reported on the Gift Card Liability report. No statement or invoice generation and no distinct on-account tender, so partial. source
kitchen-bump-bar-hardwareunknown / F -- An Epson KDS Hardware article exists in the KB but its content was not retrievable; no bump bar model, touchscreen bump behaviour, or peripheral list is published on the pages that were reachable....resolve-to-partialThe 'Epson KDS Hardware' article the prior pass could not retrieve is at the slug kds-hardware; it and the Bump Bar Guide name the Bematech KB1700 and document its operation, and the Fresh KDS Hardware Overview names the Logic KB1700. Supported models are documented. The native Epson KDS, however, states 'Touch screen monitors are not supported', so the claim's 'in addition to touchscreen' holds only on the Fresh KDS partner path. Partial, not yes. source
kitchen-speed-of-service-reportingunknown / F -- The Epson KDS overview refers to time-tracking orders, but no report in the Portal's Sales, Operations, Statistics, Accounting, Discrepancy or General reporting sections is documented as producing ticket times, throughpu...resolve-to-partialTwo facts were located. Native: the Epson KDS Overview says 'Arryved sends orders to the KDS, but the KDS does not send anything back to Arryved', which closes the native reporting path. Partner: the Fresh KDS Integration Overview describes Fresh Tools as the portal for 'reporting', and arryved.com's FreshKDS page describes Kitchen Performance Analytics with prep times, bottlenecks and throughput. Kitchen timing reporting therefore exists only in a separately-billed partner product, without percentile, daypart or export detail. Partial. source
order-capture-scheduled-ordersunknown / F -- The ORDER screen article mentions filtering by pickup/delivery times, which implies a future time can exist on an order, but no article documents guest-selected future ordering, lead times or scheduling windows....resolve-to-partialThe Pickup Modality Setup Guide documents Pickup Time Options (NONE / FREEFORM / OPTION) and the ORDER screen time filter, which the prior rationale only inferred. Future-timed orders exist; lead-time rules, validated slots and a computed fire time do not (the KDS explicitly does not show pickup times; tickets route on receipt). Partial. source
digital-scheduled-pacingunknown / F -- The ORDER screen can be filtered by pickup/delivery times, implying a fulfilment time exists on an order, but no article documents guest-selectable time slots, per-slot capacity, or quote-time throttling....resolve-to-partialSame document as order-capture-scheduled-orders, read for the pacing half. Time slots are a merchant-typed list; nothing caps orders or items per slot or closes a saturated slot, and the Online Store Settings overview names no such control. Partial: slots without throttling. source
labor-realtime-labor-percentunknown / F -- Hours are tracked per labor role and pay is held on the labor role, so the inputs exist, but no article documents a live labour-cost-percentage figure on the Dashboard or in Arryved Service....resolve-to-partialRead Arryved's own 7shifts Integration Overview (2025-02-07): sales, wages and punches sync to 7shifts, whose Sales & Labor dashboard shows real-time sales and labor costs; but 'Data sent from Arryved to 7shifts is not updated in real time' and the view is in 7shifts, billed separately per location. Partial via partner, with the vendor's own caveat. source
reporting-sales-forecastunknown / F -- Sales forecasting is described as something the 7shifts integration provides, and no forecast report appears in the Portal reporting sections that were reachable, but Arryved does not state that it has none of its own....resolve-to-partialThe prior rationale noted the 7shifts route but left the cell open because Arryved does not deny having its own forecast. Arryved's KB now documents the exchange: 90-day history on activation, ongoing net sales, and Sales and Labor Projections shown in 7shifts. No Arryved-side forecast appears in any reporting category page read (sales, operations, statistics, general, accounting, discrepancy). Partial via partner. source
reliability-hardware-replacement-slaunknown / F -- An "Arryved Hardware Warranties" article exists in the KB but its content was not retrievable, and the Device Lifecycle Support Policy covers only which devices qualify for software support — it states no warranty period...resolve-to-partialThe 'Arryved Hardware Warranties' article the prior pass could not retrieve sits at the slug 'warran'. It states manufacturer warranties (Samsung 1 year, MagTek and Epson 2 years), an optional 3-year accident cover with one replacement, Arryved-paid return shipping, and a per-week loaner for merchants on their own devices. No turnaround time or advance exchange. Partial. source
commercial-hardware-not-lockedunknown / F -- Title to purchased equipment passes to the merchant under MSA §15, and merchants may source their own Android devices, but nothing states whether Arryved-sold tablets or the MagTek readers are provisioned in a way that p...resolve-to-yesThe prior rationale folded this cell into the post-churn question. Read against the claim as written -- at least one documented non-proprietary hardware option -- the warranty article (Samsung, MagTek, Epson partners; merchants who 'purchased your own devices'), the End Of Life guide (install Arryved Service from Google Play), and the Fresh KDS hardware article ('other devices you may already have', Google Play certified) establish it at grade B. The leased MagTek reader is noted as the one vendor-tied component. Differentiator weight, grade B: yes. source
order-capture-throttlingunknown — never examined against the 2026-09-04 corpusresolve-to-noVerified the load-bearing enumeration myself in pickup-modality-setup-guide.txt lines 102-105: the three Pickup Time Options are stated as a closed choice set and none carries a capacity. That is an enumeration, not a failed search over the corpus floor - per-slot capacity is exactly the field that would have to appear in that list. 'Max Number Of Items Per Order' confirmed at arryved-online-settings-overview.txt line 201. Grepping the corpus for throttl/capacity/pace-orders returns only a network-bandwidth sentence in basic-troubleshooting, so nothing contradicts. Peer distribution partial 17 / no 9 / unknown 6 / yes 3 - a normal minority, not an outlier. source
menu-pricing-topping-quantity-tiersunknown — never examined against the 2026-09-04 corpusresolve-to-noListed WRONG-DOC in the mechanical defect report, but the defect is in the corroborating quote, not the citation. I confirmed the load-bearing propositions ARE in the cited article: item-modifiers.txt lines 119-120 carry the inert Type field and the single flat Price, inside a numbered field walkthrough. The '1st Half' / 'Additional Notes' quotes live in best-practices-for-byo-pizza.txt lines 190/198/202 - real, but supporting. The citation carries its own proposition so no re-pointing is needed; the note now attributes the BYO quotes to the pizza guide. `no` is the plurality peer value (38 of 82). source
payments-softpos-tap-to-payunknown — never examined against the 2026-09-04 corpusresolve-to-noThe corpus zero-hit counts for 'Tap to Pay on Android' / 'softPOS' are a floor argument and I discounted them. What carries this verdict is affirmative and in-document: things-to-consider... line 88 requires a card reader per POS device and line 166 closes reader sourcing entirely. A mandatory per-device external reader is positive evidence that reader-less acceptance is not offered. Both lines read directly. The 403s are correctly treated as refusals, not absences, and none of the nine titles is softPOS-adjacent. Peer distribution: no 19 / unknown 18 - `no` sits with the crowd. source
kitchen-prep-time-pacingunknown — never examined against the 2026-09-04 corpusresolve-to-noConfirmed the enumeration frame at building-inventory-items.txt lines 60/105/107 - the article explicitly declares it is walking the rest of the available fields, which makes the omission of a cook time an enumeration rather than a search miss. Priority Time / Rush Time confirmed at customizing-the-kds-display.txt lines 77-78 and are order-scoped, so the staggering limb has no input even in principle. Peer distribution: no 15 / unknown 8 / partial 7 / yes 4. source
kitchen-all-day-countsunknown — never examined against the 2026-09-04 corpusresolve-to-partialRead customizing-the-kds-display.txt lines 76 and 94-97 directly. Both halves check out: the Summary Tile is a first-class field in Arryved's own display-file settings, so the capability is genuinely present rather than a partner bolt-on, while the filter that makes it useful is explicitly outside Arryved's KDS offering and is hand-maintained. I pressed for `no` on the strength of the disclaimer and rejected it - the disclaimer attaches to the Filter section, not to the tile itself. Correctly named shortfall; `partial` is the plurality peer value (10 of 34). source
kitchen-printer-fallbackunknown — never examined against the 2026-09-04 corpusresolve-to-partialPRINTER-FALLBACK RECONCILIATION. The author's `no` rests on a statement that is factually false: they wrote that 'no backup, failover, redundant or reroute language appears in any of the printer, print-controller, peripheral-matrix, printer-override or KDS articles in the 546-article help centre'. It does. adding-a-printer-to-the-portal-for-arryved-service.txt carries a named 'Fallback To' field describing exactly the mechanism the claim needs, and 'fallback' appears in four corpus files. Their cited quote - 'You can only have one default Peripheral for each Venue in each ticket type on the Matrix' (default-printers-setup-guide.txt line 60) - is real but governs routing DEFAULTS, not failover, and does not exclude a fallback target. The chunk-4 author read the right article; the chunk-2 author read an adjacent one and generalised. Both cells now sit at `partial` off the same Fallback To text with different named shortfalls: reliability-* lacks the staff alert, kitchen-* lacks the no-ticket-loss guarantee. I stopped short of `yes` because exit-offline-mode-and-sync.txt line 68 and offline-mode-cheat-sheet.txt line 68 confirm print is simply lost during a network outage, and because only 2 of 33 peers hold `yes`. source
kitchen-order-modification-alertsunknown — never examined against the 2026-09-04 corpusresolve-to-noThe author flagged this as enumeration-plus-workaround with no vendor denial, so I looked for what they missed and found evidence that strengthens it. Confirmed 'Consider Orders Unique' at kds-configuration-utility-settings.txt line 77; the colour-coding denial appears independently in four articles (customizing-kds-order-tiles, kds-configuration, kds-overview, kds-setup-guide), one of them phrased 'is not supported' - that is a vendor denial of content-driven flagging. I then checked the printed path myself, which neither author did: printing-preferences.txt line 90 and the Arryved Service 2.7.1 release note document the update behaviour as a whole-ticket reprint with no diff marking. Both documented output paths are enumerated and neither flags changes. `no` is a minority (6 of 34) but is carried by an explicit denial plus two enumerations. source
delivery-tracking-pageunknown — never examined against the 2026-09-04 corpusresolve-to-noI retrieved routing-deliveries.txt myself (line 113) because that, and not the zero-hit search for 'tracking', is what carries this verdict. A vendor whose documented dispatch procedure is a manual export into Google My Maps has no driver state from which to drive a guest tracking page - that is the 'vendor's own documentation recommends a workaround' pattern the rules name as positive absence, not a floor search. The seven-step setup enumeration confirmed at delivery-modality-set-up-guide.txt lines 66-76. `no` is a minority (5 of 39, against partial 24) and I note that, but the workaround document is affirmative evidence rather than silence. source
digital-upsell-engineunknown — never examined against the 2026-09-04 corpusresolve-to-partialRead linked-products.txt and arryved-online-settings-overview.txt in full. The WooCommerce Up-Sells/Cross-Sells quote is real and lives in the cited article. Ruled explicitly on the subject-scope challenge: Arryved Web Solutions is an Arryved-sold product whose docs sit on support.arryved.com, so its checkout merchandising is in scope for the vendor record PROVIDED the shortfall names the separation — and the note already does, in its first shortfall. The claim has two limbs and the second (attach-rate reporting on those suggestions) is absent in every product, so partial cannot inflate to yes. Distinguished from guest-loyalty-tiers, where the Web Solutions feature fails the claim on its own terms as well as on subject. Partial with two named shortfalls stands; it is also the peer mode (23 partial / 12 no / 8 unknown). source
digital-catering-portalunknown — never examined against the 2026-09-04 corpusresolve-to-noConfirmed both load-bearing sentences at lines 63 and 67 of arryved-online-order-modality-overview.txt: "There are 5 Order Modalities you can offer in your Arryved Online Store" and "You cannot rename the Order Modalities nor create custom ones." That is an enumeration the vendor declares closed — not a failed search over the 546-article floor — and it forecloses a distinct catering ordering flow at the modality level. The corpus-wide zero-hit count on "catering" is corroboration only and the verdict does not need it. Peers 13 no / 15 partial / 12 unknown; not an outlier. source
digital-voice-ai-phoneunknown — never examined against the 2026-09-04 corpusresolve-to-noConfirmed the ORDER Screen sentence at line 38 of order-screen-overview.txt. On its own it is a feature description of an optional screen, so I did not rest the verdict on it. What carries it is structural and independent of the corpus floor: this record already holds extensibility-order-injection-api = no at grade B, and the claim requires the completed call to be injected into the POS without staff transcription. With no order-injection surface, neither a native agent nor a certified partner can satisfy the claim, and the vendor publishes no telephony product and names no voice partner in its integration directory. Peers 12 no / 18 unknown — upheld against the modal peer, which I flag, but a structural bar is stronger than a census. source
guest-loyalty-thirdparty-identity-attachunknown — never examined against the 2026-09-04 corpusresolve-to-noSame premise-failure test, and it survives. The claim is conditioned on marketplace orders existing; ten grade-B cells already in this record (delivery-3p-direct-integration, delivery-3p-injection, delivery-store-pause and others) establish that Arryved integrates with no marketplace and no middleware, and extensibility-order-injection-api = no means none can be bolted on. There is no ticket that could carry a marketplace identity into an Insider profile, so the answer to what the claim asks is genuinely negative rather than merely unfound. Peers 15 no / 16 unknown; within the crowd. source
guest-loyalty-tiersunknown — never examined against the 2026-09-04 corpusresolve-to-noTwo independent legs, both verified. (1) what-is-arryved-insider.txt enumerates the membership axis as exactly Public/Private (lines 82-84) and fixes the earn rate as immutable, and the four Perk types contain no status level. (2) The subject-scope challenge is answered by the vendor in terms: web-solutions-memberships.txt line 42 — "Members and Memberships do not sync with your Arryved POS. Everything is managed in your Web Solutions Online Shop." I checked this because if the Web Solutions tiers were in scope the verdict would fall; they are not, and separately they are manually assigned or purchased benefit levels, so they fail the claim's "automatic promotion and demotion driven by rolling-window spend" on their own terms. Uphold no/B. source
guest-loyalty-offline-behaviorunknown — never examined against the 2026-09-04 corpusresolve-to-noThis claim's operative verb is "Documents", which makes an exhaustive document's silence the evidence rather than the absence of evidence. Offline Mode Overview declares itself exhaustive ("everything you need to know about Arryved's Offline Mode") and then enumerates limitations item by item, naming the sibling stored-value feature ("Gift cards can't be sold or used for payment") while never naming Insider lookup, Point accrual or Offer/Reward redemption. A limitations list that reaches gift cards and stops short of loyalty is a hole, not a floor artefact. Peers 15 no / 17 unknown. Uphold. source
guest-loyalty-rfm-segmentationunknown — never examined against the 2026-09-04 corpusresolve-to-noThe load-bearing document is self-declaredly field-by-field ("this section explains how to customize each field on the Offer creation page"), so this is an in-document enumeration and not a corpus census. Within it the sole audience control is Point Cost, a balance filter; every other enumerated field targets items or caps the offer. The Insider Members page is per-person analytics with no segment builder and its own list-level search is out of service. The claim requires precomputed lifecycle segments the operator does not build. Uphold no/B. source
guest-loyalty-lifecycle-automationunknown — never examined against the 2026-09-04 corpusresolve-to-noThe strongest cell in either chunk. Confirmed insider-faqs.txt line 125 carries the question verbatim and the vendor answers its own automation question in the negative. That is a support page saying it is not supported — the textbook basis for no under the evidence rules — and the offer lifecycle states (Preview/Queued/Active/Exhausted/Expired/Retired) describe one scheduled send, not a standing trigger. Peers 30 no, the joint mode. Uphold. source
guest-loyalty-10dlc-registrationunknown — never examined against the 2026-09-04 corpusresolve-to-noTested this against the same premise-failure objection I sustained on reporting-api-not-upcharged, and it comes out the other way. There, half the claim's subject (raw-data access) existed and was not upcharged, so no was too strong. Here nothing of the claim's subject exists: this record's own guest-loyalty-native-email-sms already stands at partial/B with "no SMS or push channel is documented for Insider", the Offer form's enumerated required fields are Subject Line and Email Body Text, and the only guest SMS in the corpus is Fresh KDS sending order-status texts under its own registration, which makes the partner the subject. The vendor therefore neither handles nor documents 10DLC. Uphold no, against a modal peer of unknown (24 of 43), which I flag. source
guest-loyalty-campaign-attributionunknown — never examined against the 2026-09-04 corpusresolve-to-partialAdjudicated the NOT-FOUND defect: false positive. The Insider Activity Report column list is in the cited article at what-is-arryved-insider.txt lines 259-268, split one metric per line, which is why a 30-character span search missed it. The citation carries its own proposition and needs no re-pointing. Substantively partial is correct and conservative — per-offer redemption with an Issued/State/Redemption Date row exists on the member wallet and check size on the last-10-visits table, but nothing rolls up per campaign, the spend column lumps every Reward and Offer together, and there is no funnel and no control group. Shortfall named. Peer mode is partial (29 of 45). Uphold. source
guest-loyalty-wallet-passunknown — never examined against the 2026-09-04 corpusresolve-to-noAdjudicated the WRONG-DOC defect: the primary proposition IS in the cited article — how-to-identify-members-in-service.txt carries "There are four ways to identify a Membership in Arryved Service" and lists all four. The detector fired on the secondary Wallet Query definition, which the note already attributes inline to Wallet Query Overview. Citation stands as cited. The enumeration is closed and covers exactly the surface where a pass would be scanned, and none of the four is a scan; the member-facing surface is documented as a passwordless web portal, which is an enumerated alternative to a pass rather than a silence. Uphold no/B. source
guest-loyalty-ai-offer-recommendationunknown — never examined against the 2026-09-04 corpusresolve-to-noThe claim names three things — offer content, target audience, send timing — and the field-by-field Offer creation enumeration documents all three as manual operator inputs, with the FAQ closing the automated-send door outright. That is in-document, so it survives the corpus-floor objection that killed reporting-nl-query, where the only support was a category list plus a zero-hit count. The MSA AI-Features clause is a reserved right naming no product and does not reach offer recommendation. Uphold no/B. source
labor-overtime-preventionunknown — never examined against the 2026-09-04 corpusresolve-to-noThree separate enumerations, none of them a census: the clock-in sequence documented step by step with no gate, the Labor Role form's complete field list, and Location Preferences' 11 named sections. The detail that decides it is one the author found and I confirm matters — the Overtime Rule is printed on report footers as "determined by your state laws" for the Company's Location, so it is not an operator-configured threshold at all, and the claim requires warning or blocking at a configured threshold. Retrospective calculation only. Peer mode is no (20 of 43). Uphold. source
labor-break-compliance-by-stateunknown — never examined against the 2026-09-04 corpusresolve-to-noThe whole labour-rule configuration surface is enumerated in three places I checked — the Labor Role form fields, "There are 14 Labor Role Permissions", and the 11 Location Preference sections — and no break construct appears in any of them. The claim needs three things (per-jurisdiction rules, attestation prompt, missed-break flag) and the only documented punch-time prompt is Forced Tip Claim at clock-out. Scheduling is routed to 7shifts/Schedulefly, so any break tooling there belongs to the partner. Peer mode is no (19 of 41). Uphold. source
labor-qualified-tips-w2-reportingunknown — never examined against the 2026-09-04 corpusresolve-to-noThe only cell I moved downward in value. The author's partial rests on the cash-versus-charged split existing per employee, which is true — but true of a report, while the claim's subject is a payroll export carrying tax codes. A partial must name a shortfall that leaves the claim partly met; here the shortfall consumes the claim. I verified all four negatives myself: zero corpus hits for payroll export or any named payroll processor; "Tips in this report are not differentiated by type" present in five report articles including payroll-report-overview line 71; "Tips & Tip Pooling" under It Does Not Support at 7shifts-integration-overview line 63; no tax-code content anywhere. Three of those are affirmative vendor statements rather than census artefacts, so this no is not built on the floor. Peer mode is no (18 of 42). Re-pointed the citation from employee-tip-collection-report-overview, which carries only the surviving half, to payroll-report-overview, which carries the vendor-stated negative the verdict now rests on. source
inventory-count-modesunknown — never examined against the 2026-09-04 corpusresolve-to-partialABM SUBJECT RULING, applied identically to all six ABM-backed cells. ABM's inventory IS in subject for Arryved. It is a first-party Arryved-branded product (the acquired SimpleCircle, per the record's own org note), and abm-pos-sync-overview.txt states that once synced 'All Inventory will always live in your ABM moving forward', with Portal Unit Sizes becoming read-only and every POS sale creating an ABM Inventory Adjustment - so where ABM is present it does not sit beside the POS's inventory, it IS the POS's inventory master. Arryved's peer group is bar-brewery-taproom, so a brewery ERP's Materials and Finished Goods are the stock this vendor's ICP actually holds. Ruling it out of subject would be a scope judgement, and scope belongs in peer-groups.yaml or scope_overrides, not in a claim value. Being a separately-sold module is a real shortfall, correctly named - which is what `partial` is for. Quotes confirmed at abm-inventory-counts.txt lines 48, 58 and 84. source
inventory-mobile-count-offlineunknown — never examined against the 2026-09-04 corpusresolve-to-partialFlagged WRONG-DOC by the mechanical checker, but the citation is sound: /articles/managing resolves to the article titled 'INV Screen Overview' and line 77 carries the load-bearing quote, which is the only occurrence of that string in the corpus. The barcode quote that tripped the checker lives in how-to-scan-barcodes and is corroborating. No re-pointing needed. I considered downgrading to `no` since both distinguishing limbs fail, and rejected it: Offline Mode's scope statement is a description, not an enumeration excluding counts, so positive absence is not established. `partial` with both shortfalls named is correct; peer split partial 16 / no 14. source
inventory-vendor-catalogs-ediunknown — never examined against the 2026-09-04 corpusresolve-to-noThe strongest `no` in either chunk and the one that does not depend on the corpus floor at all. Confirmed at abm-purchase-orders.txt line 43, inside a section the article itself heads 'Limitations' - a vendor statement that the capability does not exist, which is precisely what the rules require. The claim additionally demands named broadline distributor integrations, and the transmission limb alone already fails outright. Peer distribution: no is the plurality (18 of 41). source
inventory-par-auto-suggestunknown — never examined against the 2026-09-04 corpusresolve-to-partialConfirmed verbatim at abm-materials.txt lines 122-129, and the same Reorder Point block appears again on Finished Goods (abm-finished-goods.txt lines 100-110), so the mechanism is real and repeated rather than a one-off sentence. The claim's differentiating limb - a forecast-driven suggested order quantity - is absent and the shortfall is named on all three axes. Same ABM subject ruling as inventory-count-modes. Peer distribution has partial as the clear majority (25 of 40). source
inventory-waste-loggingunknown — never examined against the 2026-09-04 corpusresolve-to-partialFlagged WRONG-DOC, but the citation holds: abm-inventory-location-behavior.txt lines 110-114 carry the three Reduction Locations and line 101 the TTB line mapping - that is the load-bearing proposition. The quote that tripped the checker ('damaged/unsellable Items... In the Summary field') is at abm-inventory-adjustments.txt lines 60-62 and is corroborating; the note now attributes it there. No re-pointing needed. Same ABM subject ruling. Peer distribution: partial 18 / no 8 / yes 8. source
inventory-shelf-life-expiryunknown — never examined against the 2026-09-04 corpusresolve-to-noI re-read abm-finished-goods.txt lines 70-110 as a step-by-step Add Size walkthrough - it introduces every field in sequence and none is a date, so this is a genuine enumeration rather than a summary. I then independently grepped every ABM, batch and production article for best-by / use-by / packaged-on / expiration / expiry / shelf-life / lot code / born-on and got zero, including on the Batch surface where a production or packaging date would most plausibly live. Enumeration plus a targeted search on the two surfaces that could carry it. Peer distribution: no 15 / unknown 16 / partial 9 - `no` sits with the crowd. source
inventory-menu-margin-linkageunknown — never examined against the 2026-09-04 corpusresolve-to-partialConfirmed both quotes myself - purchase-items-repor.txt line 124 (the slug is genuinely truncated upstream; the article resolves and is titled 'Purchase Items Report Overview') and system-sales-summary.txt line 116. This is the partial I pressed hardest, because both of the claim's stated limbs fail and the surviving fact is an off-by-default, support-enabled, manually-typed cost column. It stays `partial` rather than `no` because the vendor does produce a per-item join of cost against actual sales depletion, which is the first half of the claim genuinely working, and `partial` is the peer majority (22 of 41). Borderline - one of my three least certain rulings. source
reporting-cash-over-shortunknown — never examined against the 2026-09-04 corpusresolve-to-partialUpheld as a downgrade the author already made correctly. The Difference field is a real computed counted-versus-expected variance, so unknown is wrong; but the claim names three dimensions — per drawer, per shift, per employee — and the article's own Limitations deny the first two verbatim while the per-employee report (Emp. Cash Handling) has no expected-cash column and no variance. Current business day only, so no Portal over/short history. Every shortfall is vendor-stated rather than analyst-asserted. Resisted the pull to yes that 15 peers took. Uphold partial/B. source
reporting-server-scorecardsunknown — never examined against the 2026-09-04 corpusresolve-to-partialA dedicated per-tipped-employee report exists with an enumerated column set, so partial is floored. Checked it against the four metrics the claim names and none is reported: average check is derivable but never printed, items per check is absent, there is no attachment rate for named categories, and tips are dollars with the article stating outright that they are not differentiated by type. The coverage gaps are vendor-stated (non-tipped roles excluded, Offline Mode excluded, multi-day ranges totalled not broken out) and there is no ranking view. Peer mode is partial (24 of 43). Uphold. source
reporting-channel-profitabilityunknown — never examined against the 2026-09-04 corpusresolve-to-partialAdjudicated the WRONG-DOC defect: false positive on the primary. The Arryved Channel sentences are in the cited daily-sales-report-13-7-2020.txt at lines 89 and 93; the flagged spans are the MarginEdge and Sales Summary quotes, which the note already carries with their own URLs inline. Substantively the channel dimension is revenue-only over three first-party surfaces, COGS is aggregated across every channel at once so no report crosses channel with margin, and with no marketplace integration the commission-netting half of the claim has no surface at all. Peer mode is partial (35 of 44). Uphold. source
reporting-api-not-upchargedunknown — never examined against the 2026-09-04 corpusresolve-to-partialThis is the challenge the brief named and it holds. The author derived no from "there is no API to upcharge" and cited the microworks-prism precedent, which I read — that record's note says "There is no public API at all ... so there is nothing to be included or upcharged." The precedent is real, but Arryved is not the same fact pattern: the claim's subject is "API and raw-data access", and I verified that raw-data access does exist and is not upcharged. A no would assert that the harm the claim exists to detect — data access priced as an upsell, per its own why_it_matters — is present here, and it is not. Partial, with the API half named as absent and the unpriced activation request named as the residual gate, is the honest reading. Grade stays C because the load-bearing document for a pricing-posture claim is the pricing page; the grade floor binds only a yes on a differentiator. Peers are split with no mode (15 unknown / 13 partial / 11 no / 7 yes), so partial is not an outlier. source
reporting-tier-paywallunknown — never examined against the 2026-09-04 corpusresolve-to-partialUpheld because it turns on a published positive proposition rather than on an absence: the quote path takes "all the same profit-building features", there is one price point, no plan matrix and no analytics SKU anywhere on arryved.com, and report access is governed by Portal permission rather than by plan. The shortfall is real and correctly named — Payroll Report, Tips By Labor Hours, End Of Day Tip Summary, COGS, RSF and every Rosie schedule sit behind an Implementation-Manager or CSM activation for which Arryved publishes no commercial terms. I confirmed the Rosie activation language independently (rosie-reports-overview.txt: "All you have to do is ask!" and "provide this information to your Implementation Manager or a member of Arryved Support"). Grade C is right for a pricing-posture claim and the grade floor binds only a yes on a differentiator. Peer mode is partial (23 of 46). Uphold. source
reporting-history-retentionunknown — never examined against the 2026-09-04 corpusresolve-to-noTested exactly the challenge put to me — that a reserved deletion right is not the proposition "documents a retention window" — and the claim text decides it: the operative verb is "Documents" and the object is a stated window of at least 24 months with no silent truncation. The MSA does not merely reserve deletion; it affirmatively states the schedule is the vendor's own internal one ("until such information is scheduled to be deleted in accordance with the receiving party's policies and procedures"), caps post-termination access at thirty days, and disclaims data availability outright while pushing backup and archive onto the client. That is a vendor document saying on the record that no window is committed, which is a different and stronger thing than a failed search. I gave the zero-hit corpus count no weight because it is a floor. Uphold no/B — but see my flag: only 4 of 44 peers went no and 23 went unknown, so this is the ruling I would revisit first. source
reporting-anomaly-alertsunknown — never examined against the 2026-09-04 corpusresolve-to-noRosie is the entire scheduled-push surface and its model is enumerated in four steps — Report, Cadence, Form, Recipients — every cadence option a calendar rule, with no condition, threshold, comparison or deviation option in it. I confirmed Step 3 and the PDF/XLS/CSV forms at rosie-reports-overview.txt lines 81-82. The author correctly surfaced and dismissed the one counter-example: the open-tabs-after-batch email is a fixed operational exception with no operator-set metric and no threshold, which is what the claim requires. Pulse's five enumerated navigation options carry no alerting either. Two enumerations, not a census. Uphold no/B, flagged — 21 of 45 peers say partial and I suspect several of those rest on exactly the fixed-exception email I am declining to count. source
hardware-handheld-lteunknown — never examined against the 2026-09-04 corpusresolve-to-noThe author confessed this one and their own note concedes the point: 'automatic cellular fallback when store Wi-Fi drops is not [documented]'. The claim is specifically cellular as a documented FALLBACK when store Wi-Fi drops, built into the device or vendor-supplied. A keg-delivery aside about carrying a hotspot on a route is neither, so the `partial` rested on an off-subject fact and named no shortfall against the actual claim. I did not send it to `unknown` because the same three pieces of evidence - the network article prescribing a manual merchant hotspot (network-best-practices.txt lines 42 and 194), the enumerated catalogue with no cellular SKU, and Offline Mode as the documented outage response - are exactly what the same author used to score reliability-cellular-backup `no`, which I am upholding. The two cells describe the same fact pattern and must move together. Peer distribution: no 11 / unknown 15 / yes 5 / partial 4. source
hardware-p2pe-terminalunknown — never examined against the 2026-09-04 corpusresolve-to-partialRead pci-compliance-overview-arryved-pay.txt myself. The SAQ shortfall is stronger than the author stated and is affirmative rather than a search miss: line 170 explicitly directs all SAQ questions to SecurityMetrics and line 47 disclaims Arryved's involvement, so the vendor documents that it does NOT state the merchant's SAQ type. I confirmed zero corpus files contain 'p2pe' or 'point-to-point' - a floor argument, but here it only corroborates. The encrypted-reader half is confirmed at tdynamo-card-reader-overview.txt line 55. `partial` is the dominant peer value (24 of 35) and this record fits the pattern exactly. source
hardware-tap-to-phoneunknown — never examined against the 2026-09-04 corpusresolve-to-noVerified the catalogue enumeration at things-to-consider... lines 38-57, the per-device reader requirement at line 88 and the sourcing lock at line 166. As with the softPOS twin the verdict rests on an affirmative requirement rather than a search over the corpus floor, which is why the false 'entire help centre' premise does not damage it. Peer distribution: no 16 / unknown 14. source
hardware-usable-after-churnunknown — never examined against the 2026-09-04 corpusresolve-to-partialThe claim asks whether vendor documentation CONFIRMS post-cancellation usability, and Arryved documents both answers for different device classes, which is the definition of partial. Confirmed the self-sourcing allowance at things-to-consider... line 183, the reader lock at line 166, and the processor-lock consequences at tdynamo-card-reader-overview.txt lines 55 and 58 - that second quote is the strongest single piece of evidence here because it shows the lock operating in a real transition rather than as a policy statement. Peer distribution: partial 10 / unknown 15 / no 6 / yes 4. source
extensibility-free-sandboxunknown — never examined against the 2026-09-04 corpusresolve-to-noThe author flagged this as their weakest cell because of the sandbox slug, so I opened that file first. The slug/title mismatch is ordinary Zoho Desk behaviour - the slug is frozen at creation and the title edited later - so it is the same article retitled, not an orphan the crawl failed to reach, and it does not reopen the floor problem for this cell. More importantly the verdict does not rest on the corpus at all: the 404 on become-a-partner and NXDOMAIN on developer.arryved.com are affirmative live probes of the public web showing no developer channel exists to hand out a sandbox. Even if an internal sandbox tenant exists, it is issued by an Implementation Manager to a merchant, which fails the claim's 'without owning a paid production account' condition on its face. `no` is a minority (11 of 46) but is carried by live evidence, not silence. source
extensibility-order-injection-apiunknown — never examined against the 2026-09-04 corpusresolve-to-noThe mechanical checker's NOT-FOUND was an artifact: both quoted spans are present verbatim at yellow-dog-integration-overview.txt lines 38 and 59-60. I discounted the author's 'the token API appears exactly twice in 546 articles', which is a floor argument, and re-based the verdict on two things that are not: the closed integration list I read at what-is-the-launch-call.txt lines 108-123, and the NXDOMAIN result on both plausible developer hosts, which is a live probe of the public web rather than a search of an incomplete mirror. `no` is a minority (7 of 46, against yes 13 / partial 23), which is why I re-based it rather than accepting the corpus count, and I corrected the note so it no longer implies Arryved has no API surface at all. source
reliability-printer-fallbackunknown — never examined against the 2026-09-04 corpusresolve-to-partialUpheld on my own reading of adding-a-printer-to-the-portal-for-arryved-service.txt, where Fallback To and Mirror To appear verbatim in the Merchant Peripheral field walkthrough. This is the correct side of the printer-fallback conflict: the chunk-4 author read the right article, while the chunk-2 author's contrary `no` asserted that no failover language exists in any printer article, which is false. `partial` is generous against the peer crowd (47 of 84 peers are `no`), but it is carried by a named vendor field with an explicit failsafe description - stronger evidence than most of those peers had - and the alert shortfall is correctly named, mirroring the microworks precedent. source
reliability-onsite-installunknown — never examined against the 2026-09-04 corpusresolve-to-noThe author flagged that no page says 'we do not come on site', which is true, but the verdict does not need one. I read kds-hardware.txt line 92 directly and it is close to a denial: Arryved staff are described as needing a PC ON SITE in order to GUIDE the merchant through configuration - staff who are guiding remotely and require the customer to be at the machine. Combined with the install procedure documented end to end as merchant self-configuration at home plus a scheduled call, and hardware arriving by FedEx, that is an enumerated process from which an on-site visit is absent, not a failed keyword search. `no` is a minority (7 of 45, against partial 22) and I record that; a `partial` here would have to name a partly-present on-site service and none exists. One of my three least certain rulings. source
reliability-cellular-backupunknown — never examined against the 2026-09-04 corpusresolve-to-noConfirmed both load-bearing sentences at network-best-practices.txt lines 42 and 194. The verdict does not depend on the zero-hit counts for LTE/4G/5G/failover: the article that owns this subject prescribes a manual merchant-supplied hotspot as the redundancy plan and the vendor disclaims responsibility for the WAN altogether. That is a documented workaround standing in place of the capability, which the rules name as positive absence. The catalogue enumeration at things-to-consider... lines 38-57 contains no cellular product. Peer distribution: no is the plurality (18 of 46). This is the anchor I used to move hardware-handheld-lte from `partial` to `no` for consistency. source
reliability-public-status-pageno (grade F), uncited: status.arryved.com does not resolve in DNS, and no status, uptime or incident-history page is linked from arryved.com or from any of the twelve top-level support KB categories. Outage communication is routed through the printable Emergency Guide and the support desk instead.upheldUpheld and re-homed. The help centre's own twelve-category index carries an Emergency Guide ("Print the 'Oh Snap! Arryved Emergency Guide'...") and no status, uptime or incident category. The corroboration is stronger than the original DNS lookup: arryved.statuspage.io answers byte-identically to two fabricated statuspage.io subdomains, so there is no Statuspage tenant, not merely no CNAME. source
extensibility-webhook-reliabilityno (grade F), uncited: No webhook product exists to have delivery guarantees, so no retry policy, signing scheme, replay window or delivery log is published. Recorded as absent rather than unknown because the absence follows from the absence of webhooks themselves.upheldUpheld against the vendor's own integrations catalogue: nine named brokered partners (Fresh KDS, Shogo, QuickBooks, BarTrack, Ekos, Yellow Dog, MarginEdge, eCard Systems, 7shifts) and no developer or API category anywhere in the twelve-category index. developer.arryved.com and api.arryved.com are NXDOMAIN. source

Sources

Every URL this record cites. 154 in total.