Deliverect

menu-pricing-nested-modifiers

RE-CITED 2026-08-09 off the deleted /docs/how-to-interpret-modifiers-and-the-quantity-ordered.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. subItems remains a documented order-payload structure, but THE DECISIVE FACT IS THAT THE LIVE PAGE DEFERS TO THE DELETED ONE: "Quantity of item ordered, for subItems quantity, see guide [here](https://developers.deliverect.com/docs/how-to-interpret-modifiers-and-the-quantity-ordered)" -- the surviving reference points readers at a 404. Recursive nesting via subItems is still evidenced; per-level min/max and forced-selection flags are still not, and the separate Flatten Nested Modifiers page for channels that cannot represent nesting is still live at /page/flatten-nested-modifiers.md. Partial stands, now on weaker documentation than when it was scored. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/glossary-pos-orders.md · retrieved 2026-08-09

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

Overloads: 'Specific item attributes can be overridden depending on the item or grouping it is offered within', with 'price' as a supported override and a 'scopes' array of PLUs — the worked example prices Avocado (base 50) at 0 inside modifier group FREE-TOP and at 450 'when chosen within a product with PLU: BRGR'. That is a non-duplicating, per-context price matrix keyed to the parent product or group. Sizes are modelled as variant products with their own PLUs (docs/variants.md: pizza sizes, drink options), so size-dependent modifier prices ride the same product-PLU scopes; caveat: no doc example shows a size-variant PLU in a scope explicitly. https://developers.deliverect.com/page/product-configuration.md · retrieved 2026-08-04

menu-pricing-fractional-placement differentiator

Held to the highest bar per the brief. Independent keyword sweep of the full 145-page doc index returned zero hits for 'fractional', 'half' or 'pizza' as page subjects. Combined with the documented flatten-nested-modifiers guidance, the absence is affirmative enough to sustain 'no'. https://developers.deliverect.com/llms.txt · retrieved 2026-08-01 adversarially verified

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

No fractional placement means no half-and-half pricing rule.

menu-pricing-topping-quantity-tiers

RE-CITED 2026-08-09 off the same deleted modifier-quantity guide. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The order payload still carries a per-item quantity and the live page's own field note -- "Quantity of item ordered, for subItems quantity, see guide [here]" -- links to the deleted article, so the multiplication rule the old note stated (total = modifier qty x product qty) IS NO LONGER SOURCEABLE and is withdrawn as a quotation while the field itself remains documented. Light/regular/extra multiplier tiers are still not documented anywhere in the live corpus. Partial stands. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/glossary-pos-orders.md · retrieved 2026-08-09

menu-pricing-size-style-matrix differentiator

RE-CITED 2026-08-09 off the deleted /docs/variants.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The Variants concept survives on the Menu Product Configuration page and it CONFIRMS the partial rather than merely restating it: "A variant structure indicates when a product has selectable options, typically sizes or quantitiesthat affect its price" [the missing space is the vendor's], carried by two UI-hint markers, `"isVariant": true` on the main product and `"isVariantGroup": true` on the associated modifier group, with the parent showing the lowest price across options. THAT IS ONE AXIS IMPLEMENTED AS A MODIFIER GROUP, not a two-axis size-by-style grid with a per-cell price override. Partial stands. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/product-types.md · retrieved 2026-08-09

menu-pricing-included-allowance differentiator

Audit re-based the evidence: the earlier rationale ('does not provide the menu-entry surface') was wrong — Deliverect does ship a menu builder with modifier groups. But the product-configuration reference enumerates the entire modifier-quantity model — min, max, multiMax, defaultQuantity, and isIngredientGroup ('It is only possible to define items with zero price within modifier groups with the flag isIngredientGroup: true') — and no included-allowance / charge-only-for-overage mechanism is among the documented options. Value no stands on that enumeration. https://developers.deliverect.com/page/product-configuration.md · retrieved 2026-08-05 adversarially verified

menu-pricing-combos

Meal deals are 'a combination of products with a fixed price', built from meal deal sections that each carry 'Minimum selection', 'Maximum selection' and 'Allow customers to select an item more than once'. Component swap-with-delta is explicit: 'If you want some products to cost extra, activate the Surcharge option and set a price', repeated in the Simphony combo article as 'To change the price of a product inside a meal deal section, select the Surcharge option and enter the additional charge'. Named shortfall: nothing in the 984-article English help centre describes the system detecting eligible a-la-carte items already in a cart and converting them to the combo price - a meal deal is a Deal-type product the guest selects, and modifier groups cannot be added inside meal deal sections. https://help.deliverect.com/en/articles/7979030-create-a-meal-deal · retrieved 2026-08-09

menu-pricing-upsell-prompts differentiator

Kiosk upselling plus a Deliverect AI 'Autonomous Menu Agent' that deploys upsells and tracks performance in Mission Control. Per-channel config and attach-rate reporting are claim-level. https://www.deliverect.com/en-us/deliverect-ai · retrieved 2026-08-01

menu-pricing-86-propagation

Snoozing an item propagates from the menu hub to connected marketplaces, Kiosk and first-party channels. No numeric propagation latency published. https://www.deliverect.com/en-us/deliverect-restaurants · retrieved 2026-08-01

menu-pricing-countdown-auto-86 differentiator

Retail-side Post Inventory Update and Inventory JSONL endpoints drive availability from stock levels; automatic 86-at-zero with scheduled restore for restaurants is not documented. https://developers.deliverect.com/llms.txt · retrieved 2026-08-01

menu-pricing-dayparting

Scheduling is at menu and category level, not per item. 'Add menu availability: Create a schedule for the entire menu. Add category availability: Create a schedule for specific categories. This is not supported by all channels' -- e.g. 'select a Breakfast category and specify that it should only be available from 7 am to 12 pm', chosen per location. Menus/Schedules lets you 'Schedule one or multiple menus to be published at different times of the week', which is how prices are dayparted (a different menu carries different prices). The API models the same thing: availabilities[] with dayOfWeek 1-7, startTime and endTime 'expressed in the local time of the location', on the menu and on categories.availabilities. Shortfall: no per-item day/time schedule -- an individual product is controlled by Snoozing, a manual pause 'for one hour, multiple hours, indefinitely, or until a chosen date', not a recurring calendar. https://help.deliverect.com/en/articles/7978991-add-or-edit-menu-availability · retrieved 2026-08-09

menu-pricing-channel-price-books

RE-CITED 2026-08-09: the cited /docs/price-level-configuration.md is deleted (404). Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The mechanism survives, and on a better surface -- the schema page the record already cites elsewhere. "Optionally, additional prices can be defined using `"priceLevels"` in order to support different pricing for specific ordering channels and menu fulfilment type", with a worked example on one product record: `"priceLevels": { "TA": 350, "DL": 400, "1PO": 300 }` against named levels Takeaway, Delivery and First Party. THE OLD NOTE'S WORKED EXAMPLE (a Hawaiian pizza at EUR8 / 8.25 / 9) IS NOT RECOVERABLE -- it lived only on the deleted page and appears nowhere in the 64-document /page/ corpus or the 983-article help centre -- so it is withdrawn and replaced rather than restated. The researcher's caveat is UNCHANGED and still correct: prices originate in the POS payload and Deliverect selects the applicable level, it does not compute a markup. This page itself links to the dead guide. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/product-configuration.md · retrieved 2026-08-09 adversarially verified

menu-pricing-dual-pricing differentiator

The POS Product Configuration doc enumerates the platform's complete pricing axes: a base 'price', optional 'priceLevels' keyed to ordering channel and fulfilment type (delivery/pickup/eat-in), and scope-keyed 'overloads'. Tender type (cash vs card) is not a pricing axis anywhere in the model. Zero matches for 'surcharge', 'cash discount' or 'dual pricing' across the 144-page developer index; help-centre 'surcharge' hits are meal-deal price bumps and delivery-cost pass-through to the POS, not tender-based pricing. Deliverect also ships no card-present POS or first-party receipt surface (payments-emv-nfc: no), and Direct/kiosk checkout is Deliverect Pay (Adyen) card/wallet — there is no cash tender on its own channels to discount against. https://developers.deliverect.com/page/product-configuration.md · retrieved 2026-08-04

menu-pricing-versioning-effective-dates differentiator

Menus do carry a draft/published split with a diff: 'You can compare a menu to the existing published version or a different menu', with a 'Compare to online menu' action, an option to 'view the current online menu or the draft (unpublished) version', new/unavailable item highlighting and a 'Show changes only' filter. Preview before publish is documented separately - 'We recommend previewing a menu before publishing it to your channels' - filtered by 'locations, channels, languages, and dates', with an Inspect mode that reveals a field's original value. Named shortfalls: staging is not effective-dated (Schedules is a recurring weekly grid of menus per day published to stores, not a go-live date attached to a version), and there is no rollback to a prior published version - the only revert is 'Reset menu products', which returns overrides to defaults and states 'It is not possible to undo this action.' https://help.deliverect.com/en/articles/9204130-compare-menus · retrieved 2026-08-09

menu-pricing-franchise-hierarchy differentiator

Master/main location pushes a catalogue to child locations; field-level override governance is not documented. CITATION QUARANTINED 2026-08-09: https://developers.deliverect.com/docs/use-master-location.md is DELETED (404 at the ~237KB ReadMe shell) and NO REPLACEMENT WAS LOCATED. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. Searched and came up empty: /docs/ and root .md routes, the /v1.1/ version prefix, all 64 live /page/ documents (369,527 chars), the 7 live /reference/ pages, and the 983-article English help centre. The specific sentence this cell rested on -- "Deliverect does not push products from other locations when those locations use products from the main location" -- returns zero hits corpus-wide, as does the phrase "main location" itself, so it cannot be re-verified and must not be re-attached to a lookalike page. The verdict and its reasoning are KEPT -- the page was read and quoted on the date recorded -- but the URL is moved to dead_url and stamped do-not-refetch, because a live URL is an instruction to future tooling. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/docs/use-master-location.md · retrieved 2026-08-01 · not refetchable · page gone · graded B when read

menu-pricing-allergen-nutrition

Allergens are a first-class enum on the product: 34 values (CELERY 100 through SOURCES_OF_GLUTEN 134) plus exclusions NO_ALLERGENS/GLUTEN_FREE/SUGAR_FREE/LAC_FREE, carried in productTags and pushed to channels in the menu payload; help.deliverect.com publishes the same list for CSV import. Nutrition is a per-product nutritionalInfo block (netQuantity, servingSize, fat, saturatedFat, trans/mono/poly fat, carbohydrates, sugar, addedSugar, fiber, starch, polyols, protein, cholesterol, sodium, salt, minerals, vitaminC) alongside supplementalInfo (additives, ingredients, legalName, FBO) and calories/caloriesRangeHigh. Shortfall: every one of those values is entered or imported on the product record -- Deliverect documents no recipe or bill-of-materials engine, so nothing derives nutrition from components. Docs also warn channels may not display the info unless 'prepackaged' is true. https://developers.deliverect.com/page/custom-tags-and-allergens.md · retrieved 2026-08-09

menu-pricing-recipe-linkage differentiator

No recipe/BOM object across 145 doc pages. Ingredient Groups exist as modifier semantics, not costing.

menu-pricing-3p-menu-push

Core product: certified direct channel integrations with menu push, PLU/suffix handling, missing-product protection, and per-item sync error surfacing. https://developers.deliverect.com/page/menu-push-protection-against-missing-products-at-location.md · retrieved 2026-08-01

menu-pricing-dynamic-pricing

Deliverect Plus (paid add-on) offers price increases at peak hours and weekends with before/after revenue comparison. Floor/ceiling guardrails not documented. https://www.deliverect.com/en-us/deliverect-plus · retrieved 2026-08-01

payments-processor-choice differentiator

Deliverect Pay is explicitly powered by Adyen. That is a single named processor with no documented alternative and no BYO path for Direct/Kiosk/QR checkout. 'Unknown' overstated the merchant's freedom here. https://www.deliverect.com/en-us/online-ordering · retrieved 2026-08-01 adversarially verified

payments-published-rates differentiator

Pricing page publishes no card-processing rate of any kind - no flat rate, no interchange-plus markup, no per-transaction figure. Its only cost statement is 'Deliverect offers flexible pricing based on your business's specific needs' with a 'Get a personalized quote' / 'Book a 1-on-1 with our team to discuss pricing' call to action. Raw-HTML extraction of the page returns zero currency amounts. Same result on the en-us and en-ca locale variants. https://www.deliverect.com/en/pricing · retrieved 2026-08-08

payments-dual-pricing differentiator

Pricing axes documented: base price, priceLevels by channel/fulfillment, and scope-keyed overloads. Tender type (cash vs card) is not a pricing axis. https://developers.deliverect.com/page/product-configuration.md · retrieved 2026-08-04

payments-surcharge-guardrails differentiator

Surcharge guardrails (excluding debit, enforcing network caps) are POS-terminal payment features. Deliverect is not a POS vendor and handles payment flow only for its own Direct/Kiosk channels through Adyen — no surcharging logic documented anywhere.

payments-emv-nfc

Sustained on affirmative evidence, not just inference: the Kiosk page states compatibility with external payment devices, i.e. Deliverect explicitly does not provide the EMV/NFC hardware itself. https://www.deliverect.com/en-us/deliverect-kiosk · retrieved 2026-08-01 adversarially verified

payments-softpos-tap-to-pay differentiator

Checked the entire card-present surface Deliverect documents. Its only card-accepting product in the 984-article English help centre is the Kiosk, whose activation article requires a Deliverect Pay payment profile plus Adyen KYC, and the two devices it troubleshoots are the PAX D200 and PAX Q25 - dedicated terminals, not phones. 'Tap to pay', 'contactless', 'SoftPOS' and 'card reader' return zero hits across the dump. Deliverect Pay's own articles (Configure a Payment Gateway, Details Needed to Add a Payment Profile, View and Refund Payments, View and Export Payouts) describe gateway onboarding, cash/card/invoice/online tenders and refunds without ever naming a card-entry method. Unresolved rather than absent: none of those pages claims to enumerate accepted entry methods, Adyen Tap to Pay could be exposed to kiosk or courier hardware without a help article, developers.deliverect.com would not serve me content on 2026-08-09 (its .md endpoints return a ReadMe 'Hello there, human!' block to a browser UA, an empty SPA shell to a plain curl, and 404/429 to the fetch tool), and the six non-English help centres are not dumped.

payments-pay-at-table

No vendor handheld exists. Table payment is guest-phone QR instead of a server-carried EMV device. https://www.deliverect.com/en-us/order-and-pay · retrieved 2026-08-01

payments-qr-guest-pay differentiator

QR at-table lets the guest pay from their phone with Apple Pay, Google Pay or card. Whether payment auto-closes an existing POS check is not documented. https://www.deliverect.com/en-us/order-and-pay · retrieved 2026-08-01

payments-tip-adjust

Deliverect's own checkout collects a guest-entered tip: the Online Ordering settings screen exposes 'Enable restaurant tips: Activate this to allow customers to provide tips when ordering', and POS integration settings carry 'Send Tip: If activated, tips will be sent to the POS'. Tips are modelled downstream too - Analytics' Revenue Breakdown reports tips as a line, and Dispatch's My Couriers stats show 'earned tips' per courier. Named shortfall: only a pre-payment, guest-entered tip on a card-not-present order is documented. No pre-auth-then-tip-adjust flow, no batch or adjust window, and no manager screen for unadjusted tips appears anywhere in the 984-article English help centre; 'PAR Brink: Configure Tips' pushes the mechanism the other way - 'Tips need to be configured in PAR Brink POS in order for Deliverect to be able to send tips' - so adjustment sits on the POS. https://help.deliverect.com/en/articles/7979314-deliverect-online-ordering-edit-your-settings · retrieved 2026-08-09

payments-tip-pooling differentiator

No labor or payroll surface in the product.

payments-offline-store-and-forward differentiator

Cloud middleware; no offline capture path documented.

payments-offline-decline-liability differentiator

Publication-observable claim held to the published-rate-limits standard: zero pages in the 144-page developer index match 'offline', and no store-and-forward payment capability is documented on any surface (settled reliability-offline-order-entry: no — pure cloud, webhook/HTTP order delivery). No offline-decline liability statement and no post-reconnect failed-payment report exist to be published; help-centre search likewise surfaces no offline-payments documentation. https://developers.deliverect.com/llms.txt · retrieved 2026-08-04

payments-gift-cards

RE-CITED 2026-08-09 off the deleted /docs/checkout-basket-1.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The payment-methods TABLE the old note quoted ("Gift Card -- Gift Card provider connected via Deliverect") is gone with the page; the surviving glossary carries the same fact as an enum instead -- "Payment types: `dpay` |`gift_card` |`third_party`", with externalId documented as "for `gift_card` it'd be the transaction ID". Gift-card tender therefore exists at Direct/Commerce checkout and settles against an external transaction id, which is if anything clearer evidence that the balance lives with a third-party provider. Named shortfall UNCHANGED and still measured: no first-party gift-card program -- no issuance, balance tracking or cross-location card is documented in the 64-document /page/ corpus or the 983-article help centre. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/commerce-checkout-glossary.md · retrieved 2026-08-09

payments-house-accounts

Catering supports 'customer whitelisting for offline invoicing'. Credit limits, running balances and statement generation are not documented. https://www.deliverect.com/en-us/catering · retrieved 2026-08-01

payments-split-tender

RE-CITED 2026-08-09 off the deleted /docs/checkout-basket-1.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. THE VERDICT IS UNCHANGED AND THE EVIDENCE IS NOW STRONGER, but the old quotation is withdrawn: "Multiple -- Combination of various methods" appears nowhere in the live corpus and cannot be restated. What the surviving Commerce Checkout glossary says is more precise: `payments` is an "Array of one or more payment entries. The sum of all `amount` values must equal the basket total", each entry carrying "Payment types: `dpay` |`gift_card` |`third_party`", an externalId, an amount, and "Whether the amount has already been collected. `false` means the amount is still due" (e.g. cash on delivery). So one basket settled across several tenders by amount is documented at the schema level. Named shortfall UNCHANGED: Direct/kiosk digital checkout only -- no split by seat, by item or by even shares, and no POS-terminal split flow. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/commerce-checkout-glossary.md · retrieved 2026-08-09 adversarially verified

payments-refund-void-controls

Overturned on audit: refunds on Deliverect's own payment surfaces ARE role-gated. The help centre documents granular role permissions including 'Refund payments' ('To perform a refund, you are required to have the Refund payments permission' — Deliverect Pay: View and Refund Payments, article 7979060), plus 'View Refund Reasons', 'Manage Cancelled Orders' and report-export permissions. Named shortfall: covers Deliverect Pay/Direct refunds only — no manager-PIN approval flow, no documented immutable audit log identifying the approver, and POS-terminal voids, discounts and no-sales remain outside Deliverect's surface. https://help.deliverect.com/en/articles/7979053-role-permissions · retrieved 2026-08-05 adversarially verified

payments-chargeback-tooling differentiator

Reclaim disputes marketplace refund deductions (not card chargebacks) with a claimed 80-85% win rate — but it is a managed service billed on success, not a self-serve dispute dashboard. https://www.deliverect.com/en-us/reclaim-by-deliverect · retrieved 2026-08-01

payments-card-on-file differentiator

Direct offers accounts with saved payment methods, and a payment token flow is documented. Reuse of the same token in-store is not documented. https://www.deliverect.com/en-us/deliverect-direct · retrieved 2026-08-01

payments-payout-timing differentiator

Deliverect Pay does publish a payouts surface I had not seen: 'Deliverect Pay: View and Export Payouts' documents a Platform page filtered by 'date range, business, or account' with a per-payout CSV export, gated by a 'View payouts' role permission, and the Kiosk activation article names Adyen as the payment partner and asks for 'a bank statement or voided cheque for the payout account verification' - so settlement runs on Adyen's balance platform. What is still missing is the schedule itself: no T+n figure, no cut-off time, no payout-frequency setting and no instant or same-day funding option appears in any of the 984 English help articles, and deliverect.com/pricing publishes no figures at all. Left unknown because a deposit schedule is normally a contractual term rather than a help article, and developers.deliverect.com (which carries a 'Glossary - Payment API' page) would not serve me content on 2026-08-09 - ReadMe bot block to a browser UA, empty SPA shell to a plain curl, 404/429 to the fetch tool.

payments-multi-entity-routing differentiator

'Deliverect Online Ordering: Configure Multiple Bank Accounts' walks the whole flow: Locations > More > Payment profiles > + Payment profile > Add Gateway, then 'To use a new bank account, leave the Account field as Create new', 'Enter the bank account settings. The required fields vary per country', then 'Select the Store dropdown and choose the store to use for this bank account or leave it as Create new to configure one', ending 'Repeat these steps to add additional bank accounts.' Deliverect Pay's gateway article says the same from the other side - 'For online payments, repeat these steps if your locations use different bank accounts', 'You can only upload one bank statement per location' - and adds a Link step mapping 'one or multiple gateway profiles' to selected stores, filterable by location and channel. Each profile is a separately verified legal entity (legal business name, company registration number, stakeholders, IBAN). Reporting stays unified: the Payouts page filters 'payouts from a chosen date range, business, or account' in one view and exports CSV. https://help.deliverect.com/en/articles/8000397-deliverect-online-ordering-configure-multiple-bank-accounts · retrieved 2026-08-09

payments-p2pe-pci4

Re-checked against the newly dumped help centre as well as the security page. 'PCI', 'P2PE', 'point-to-point' and 'encryption' return zero substantive hits across the 984 English articles - the sole compliance construct documented is a per-POS 'Anonymize customer data (GDPR)' toggle. Deliverect is not the acquirer: Deliverect Pay is configured on top of Adyen (Balance Platform), Airwallex, Mollie, Paymob or Stripe, and the Kiosk's card acceptance runs through Adyen with merchant-side KYC, so a P2PE listing would attach to the terminal estate rather than to Deliverect. Left unknown, not no: an Attestation of Compliance is normally supplied under NDA on request and deliverect.com/security directs such enquiries to security@deliverect.com, so its absence from a public help centre is not evidence it does not exist.

delivery-driver-roster

Courier App manages an in-house fleet with driver assignment and real-time arrival times. Driver clock-in/out and per-driver run history reporting are not documented. https://www.deliverect.com/en-us/dispatch · retrieved 2026-08-01

delivery-dispatch-board

Real-time delivery overview across owned and third-party fleets. Multi-order run batching is not documented ('Multiple Couriers for Split Orders' covers order splitting, not batching). https://www.deliverect.com/en-us/dispatch · retrieved 2026-08-01

delivery-route-map differentiator

Dispatch Introduction's order-stacking FAQ is explicit: drivers can be assigned multiple orders, 'you can assign orders to available drivers using the Live Map view', and under 'Optimized Routing' - 'As soon as the driver goes en route, we use the Google Maps API to automatically optimize the drop-off sequence. The route is calculated based on their transport type (bike, car, etc.) and ensures the quickest return to the restaurant for the next delivery' - with 'Drivers can override the suggested route at any time by simply selecting the next drop-off they prefer.' The map itself is documented in 'Dispatch: Using the Live View Page': a map view of orders and courier positions with per-job delivery address, expected delivery time and assigned courier, plus full-screen mode, gated by a 'View dispatch live map view' role permission. Scope caveat recorded rather than a downgrade: the map view requires the Courier App, i.e. the operator's own couriers. https://help.deliverect.com/en/articles/7979513-dispatch-introduction · retrieved 2026-08-09

delivery-driver-tracking differentiator

RE-CITED 2026-08-09 off the deleted /docs/courier-status-update-webhook.md, AND ONE SENTENCE OF THE OLD NOTE IS CORRECTED. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The surviving Courier Status Update Model documents the payload directly: a `coordinates` object, "The name of the dispatch partner company", and "This will be sent as `true` when the delivery is split across more than one driver". THE CORRECTION: the old note said "First-party Courier App GPS is a marketing claim only". The API model itself now names the product -- `courierId` is documented as "this is the unique Id of the courier" where Deliverect's own Courier App is used, linking to the help centre article -- so the Courier App is referenced in first-party technical documentation, not only in marketing. The old note's exact quotation ("Updated courier coordinates from the dispatch partner") died with its page and is withdrawn. Partial still stands: the coordinate feed is relayed from dispatch partners and the model does not demonstrate first-party GPS capture. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/courier-status-update-model.md · retrieved 2026-08-09 adversarially verified

delivery-zones-polygon differentiator

Direct Suite locations expose 'Delivery areas' with an 'Add delivery areas' button offering a choice of 'Polygon area: Create a shape over a map to specify where orders can be delivered' or 'Radius area: Provide the maximum delivery radius from your location'. The polygon is directly manipulable - 'Manipulate the polygon by dragging the corners. Addresses inside the polygon are eligible for delivery' - and each area carries Area name, Min. basket value, Delivery fee and Delivery fee tax rate, so multiple named polygons with independent economics can be drawn per location. No drive-time isochrone option is offered, but the claim is satisfied by arbitrary map polygons. The older Deliverect Online Ordering channel settings screen (7979314) offers only 'By PostalCode and By Radius'; Direct Suite is the successor surface ('We are currently moving customers to Direct Suite'). https://help.deliverect.com/en/articles/8031423-direct-suite-manage-your-locations · retrieved 2026-08-09

delivery-zone-pricing

Each delivery area carries its own money settings in the current product. Direct Suite locations expose 'Add delivery areas' offering a 'Polygon area' or a 'Radius area', and both variants carry the same per-area fields: 'Area name', 'Min. basket value: Enter the minimum basket value of an order to qualify for delivery', 'Delivery fee: Provide the delivery fee to add to orders within this radius' and 'Delivery fee tax rate (%)'. Areas are added, edited and deleted individually, and the applicable area follows from the guest's address ('Addresses inside the polygon are eligible for delivery'). The legacy Deliverect Online Ordering settings screen shows the same shape - per-radius and per-postcode 'Delivery Fee', 'Min Order Amount' and 'Free Delivery From' (https://help.deliverect.com/en/articles/7979314-deliverect-online-ordering-edit-your-settings). Named shortfall: there is no per-zone quoted promise time in either product. The Direct Suite per-area field list contains no time field, and order timing is set once for the whole site - 'Timeslots Minute Skip', 'Enable Delivery Asap', 'Pre Order (Days)', 'Order Time Window Settings' - while preparation time is a per-location lever (Busy mode 'increase the preparation time of orders'), so a farther area cannot be quoted a longer promise. https://help.deliverect.com/en/articles/8031423-direct-suite-manage-your-locations · retrieved 2026-08-09

delivery-address-validation

RE-CITED 2026-08-09 off the deleted /docs/validating-dispatch-partner-availability.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The capability survives inside the checkout glossary, which documents a validation call as a prerequisite to committing an order -- an "endpoint which helps to secure a courier and pre-validated delivery job quote". That is courier-coverage validation for an address before commitment, which is what the old note claimed. What is still NOT documented is the other half of the claim: geocoding validation and out-of-zone rejection at guest order entry. Partial stands. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/commerce-checkout-glossary.md · retrieved 2026-08-09

delivery-driver-comp differentiator

Dispatch > My Couriers carries a Stats section: 'Find out the total deliveries, distance, and earned tips of each courier. Use the filters at the top of the page to change the location and time frame.' Two of the three compensation inputs the claim names - distance driven per period and driver-retained tips - are therefore tracked per driver, first-party. Named shortfall: no per-delivery flat reimbursement or per-distance rate is configurable anywhere; the page's Settings are enumerated and are cash payments, partner fallback, manager-only job assignment, enforced location sharing, geofencing and breaks - none monetary. And there is no payroll export: the only export in the Dispatch product is the Live View delivery-jobs CSV, with no separation of reimbursement from wage lines and no payroll destination documented. https://help.deliverect.com/en/articles/9399812-dispatch-my-couriers · retrieved 2026-08-09

delivery-cash-reconcile

A driver cash bank is documented on both ends. Settings: 'Enable cash payments: Activate to track the amount of cash your couriers are holding. You can also set how much cash they can hold until they are required to cash out.' Operation: on Dispatch > Live View's map view 'you can also view the status of the couriers and manage their cash', and on the Couriers tab 'The current cash of your couriers is displayed if you have activated the Enable cash payments setting on the My Couriers page. Select the current cash amount of the courier to log cash returned.' Named shortfall: this is a running held-cash balance with a manual cash-returned entry and a ceiling, not a settle-up. Nothing reconciles cash collected against the orders assigned and the tips owed for a shift, and no per-driver over/short figure or end-of-shift report is documented in the 984-article English help centre. https://help.deliverect.com/en/articles/9398761-dispatch-using-the-live-view-page · retrieved 2026-08-09

delivery-daas-dispatch

Capability upheld — multi-DaaS brokering is documented and the eight named partners match exactly. But the '40+' figure does NOT appear on the cited Dispatch page; I could not find it there at all. Strike the number or downgrade it to claim-level pending a source. The eight named partners are what the page actually supports. https://www.deliverect.com/en-us/dispatch · retrieved 2026-08-01 adversarially verified

delivery-daas-fallback differentiator

My Couriers > Settings documents the toggle 'Assign orders to a delivery partner when none of my couriers are available': 'If nobody can deliver the order, a delivery partner is sent the job instead (requires at least one delivery partner to be configured for the location).' Native hybrid overflow, own fleet to DaaS. Shortfall: availability is the only documented trigger — no out-of-zone or wait-threshold overflow rule from the in-house fleet; Auto-selection's Maximum pickup time, Delivery ranges and Cheapest/Fastest tie-breaker rank third-party partners against each other, not own fleet vs DaaS. Requires the Deliverect for Couriers module. https://help.deliverect.com/en/articles/9399812-dispatch-my-couriers · retrieved 2026-08-02 adversarially verified

delivery-3p-direct-integration differentiator

Deliverect is itself the certified integrator — it holds direct connections to DoorDash, Uber Eats, Grubhub and dozens more, and is a named DoorDash 2026 Preferred Integration Partner. CITATION QUARANTINED 2026-08-09: https://developers.deliverect.com/docs/building-a-channel-integration-overview.md is DELETED (404 at the ~237KB ReadMe shell) and NO REPLACEMENT WAS LOCATED. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. Searched and came up empty: /docs/ and root .md routes, the /v1.1/ version prefix, all 64 live /page/ documents (369,527 chars), the 7 live /reference/ pages, and the 983-article English help centre. The surviving channel documentation is /page/channel-flow.md, which is a sequence diagram and does NOT carry the claim that Deliverect holds the direct DoorDash, Uber Eats and Grubhub connections itself. Re-pointing there would have been slug-similarity re-homing of exactly the kind that has produced two near-misses on this atlas. The verdict and its reasoning are KEPT -- the page was read and quoted on the date recorded -- but the URL is moved to dead_url and stamped do-not-refetch, because a live URL is an instruction to future tooling. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/docs/building-a-channel-integration-overview.md · retrieved 2026-08-01 · not refetchable · page gone · graded B when read

delivery-3p-injection

Core product. Vendor-claimed 99.95% order injection rate into the POS with no tablet re-keying. https://www.deliverect.com/en-us/deliverect-restaurants · retrieved 2026-08-01

delivery-menu-push

RE-CITED 2026-08-09 off the deleted /docs/how-do-i-receive-a-customer-menu.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. One menu hub publishing to connected channels survives across two live pages: the menu glossary's field set (categories, products, modifiers, images, sorting, and priceLevels for per-channel prices) and the flow diagram's "POST menuUpdate webhook (menu published)". Menu Push protection against missing products at a location is also still live and already cited by this record. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/menu-glossary.md · retrieved 2026-08-09

delivery-86-sync

Snooze propagates out-of-stock status per channel and per menu, with restore. https://developers.deliverect.com/page/lce-set-visible-status-per-menu.md · retrieved 2026-08-01

delivery-store-pause

Verified verbatim: 'Sentinel detects downtime, send you email alerts, and reopens stores automatically or with one click', with stores integrated to Deliverect Restaurants reopening automatically. Burger King UK case data (97% to >99% uptime; ~4,000 auto-reopens/month) is on the page as a customer-attributed claim. https://www.deliverect.com/en-us/sentinel · retrieved 2026-08-01 adversarially verified

delivery-3p-reconciliation differentiator

Reclaim reconciles marketplace refund deductions and disputes them as a managed success-fee service; the dashboard compares revenue by channel. Full payout-to-POS-sales matching itemizing commission and marketing fees is not documented. https://www.deliverect.com/en-us/reclaim-by-deliverect · retrieved 2026-08-01

delivery-injection-error-visibility differentiator

Sentinel surfaces store downtime and out-of-stock leakage with email alerts and a live map; Deliverect AI's support agent monitors failed injections, mismatched PLUs and sync issues; a public per-component status page exists. https://www.deliverect.com/en-us/sentinel · retrieved 2026-08-01

delivery-tracking-page

Dispatch provides real-time delivery tracking and ETAs. A branded status page on the restaurant's own domain is not explicitly documented. https://www.deliverect.com/en-us/dispatch · retrieved 2026-08-01

delivery-promise-time differentiator

RE-CITED 2026-08-09 off the deleted /docs/how-to-update-the-preparationtime-when-you-receive-an-order.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. Busy Mode and prep-time extension survive in the Stores glossary as store state plus a numeric field: a store is `busy` when "the store is open, but with a delay in the preparation time which is shown as `preparationTimeDelay` in minutes", and the field itself is "Additional delay (in minutes) added to preparation time before an order is ready". Partial stands, and the shortfall is unchanged and now better framed: this is an operator-set additive delay, not dynamic computation from kitchen load, driver availability or zone drive time. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/stores-glossary.md · retrieved 2026-08-09

delivery-offline-behavior

No offline behaviour is documented for delivery or anything else; the platform is cloud-only.

digital-first-party-web

Corroborated and strengthened: branded storefront with the operator's 'logo, colors, and menus', geolocation landing pages routing to the nearest location, configurable tip amounts, order tracking, Deliverect Pay checkout. The dossier's caveat that commission-free could not be confirmed is correct — no commission-free claim exists on either page. https://www.deliverect.com/en-us/online-ordering · retrieved 2026-08-01 adversarially verified

digital-menu-single-source

One menu hub drives first-party and third-party channels: 'Update all menus across all your channels at the same time'. https://www.deliverect.com/en-us/deliverect-restaurants · retrieved 2026-08-01

digital-native-app differentiator

'Branded website & app' appears only as a navigation-menu label. The dedicated Online Ordering page describes a responsive web storefront working 'across mobile and desktop' and mentions no mobile app and no app store at all. A responsive web app being labelled 'app' in nav copy is the weakest possible basis for a 'yes' on native app. https://www.deliverect.com/en-us/online-ordering · retrieved 2026-08-01 adversarially verified

digital-account-saved-payment

Guest accounts are real and first-party: 'Customers can create their own login on your Online Ordering site. By doing so, they are able to store their personal information to save time for future orders', with the resulting records listed under Online Ordering > Customers. Direct Suite reinforces it - its loyalty program has a 'Sign up bonus ... to incentivize customers to create an account', and Direct Suite > Customers shows each guest's contact details, transactions, last purchase and order count. Named shortfall: the two other halves of the claim are undocumented. No article describes storing a tokenized card on a guest account - Deliverect Pay is documented only as gateway onboarding, payment listing and refunds - and no one-tap reorder of a previous order is described anywhere; 'reorder' in the 984-article English dump refers only to dragging menu items into a different order. https://help.deliverect.com/en/articles/7979317-deliverect-online-ordering-view-and-export-customers · retrieved 2026-08-09

digital-upsell-engine differentiator

Kiosk upselling plus Deliverect AI's Autonomous Menu Agent, which deploys upsells from sales performance and reports in Mission Control. Attach-rate reporting specifically is not evidenced. https://www.deliverect.com/en-us/deliverect-ai · retrieved 2026-08-01

digital-scheduled-pacing

Scheduled ordering plus per-menu cut-off times for catering and Buffer Orders. Per-daypart slot capacity limits that auto-close saturated slots are not documented. https://www.deliverect.com/en-us/catering · retrieved 2026-08-01

digital-fulfillment-modes

Delivery, pickup and table ordering are corroborated. Curbside is not mentioned on either the Direct page or the Online Ordering page. Drop curbside from the note. https://www.deliverect.com/en-us/online-ordering · retrieved 2026-08-01 adversarially verified

digital-qr-table

QR scan-to-order and scan-to-pay with Apple Pay/Google Pay/cards, tied to a table number. Attaching to an existing open POS check, splitting and tipping are not documented. https://www.deliverect.com/en-us/order-and-pay · retrieved 2026-08-01

digital-kiosk differentiator

First-party Kiosk on the shared menu hub with external EMV terminal support and optional printer. No accessibility compliance claim published. https://www.deliverect.com/en-us/deliverect-kiosk · retrieved 2026-08-01

digital-group-ordering

US homepage, Catering section: 'Offer group ordering, set menus, and à la carte options with menu-specific cut-off times', alongside 'support for offline invoicing, deposits, and split payments.' Marketing claim only, and scoped to the enterprise Catering product. Named shortfalls: none of the claim's mechanics (shareable link, participants adding their own items, per-person or total spend caps) are documented anywhere — the Catering product page describes single-orderer 'specify party size' ordering, the Commerce basket API models exactly one customer (update surface: customer, items, discounts, fulfillment, tips), and standard Direct/Online Ordering shows no group-order concept in its help collection or settings article. https://www.deliverect.com/en-us · retrieved 2026-08-04

digital-catering-portal differentiator

Distinct branded catering portal with separate packages/a-la-carte menus, per-menu cut-off times, pre-injection order review, and offline invoicing via customer whitelisting. Quotes, deposits and proposals are not documented. https://www.deliverect.com/en-us/catering · retrieved 2026-08-01

digital-voice-ai-phone differentiator

The claim allows a named certified partner, and Deliverect has two. ConverseNow (announced 16 April 2026) integrates its Voice AI so that 'phone and drive-thru voice orders' flow into Deliverect alongside marketplace and first-party digital orders. SoundHound AI (announced 23 July 2026, NEW YORK dateline) has its voice agents 'access real-time menu and location data' from Deliverect and 'route them straight to kitchen fulfillment through Deliverect's certified POS integrations', across 'drive-thru, phone, kiosk, and in-car channels'. Named shortfall: nothing native - Deliverect's own AI catalogue (12981597) is three menu/ops agents with no telephony - and neither partner has an Integration Overview article in the 983-article English help centre, so there is no first-party documentation of setup, certification status or availability; both sources are vendor press releases with no stated rollout date. https://www.prnewswire.com/news-releases/conversenow-and-deliverect-announce-partnership-to-bring-voice-ai-ordering-into-unified-restaurant-order--menu-management-302743431.html · retrieved 2026-08-09

digital-drivethru-ai

Deliverect's SoundHound AI partnership (NEW YORK, 23 July 2026) covers 'drive-thru, phone, kiosk, and in-car channels' in more than 100 languages, with SoundHound's agents accessing 'real-time menu and location data' from Deliverect and routing orders 'straight to kitchen fulfillment through Deliverect's certified POS integrations' - which is the menu/modifier integration the claim asks for. The ConverseNow partnership (16 April 2026) likewise brings 'phone and drive-thru voice orders' into Deliverect. Named shortfall: the lane agent belongs to the partner, not to Deliverect; no escalation-to-human handoff is described in either announcement; and neither partnership has any help-centre or developer documentation, so configuration, certification and availability are unevidenced. Deliverect's own AI catalogue (12981597) contains no lane-side agent. https://www.prnewswire.com/news-releases/deliverect-and-soundhound-ai-partner-to-turn-voice-into-a-fully-automated-ordering-channel-for-restaurants-302833315.html · retrieved 2026-08-09

digital-sms-ordering

Direct markets ordering via WhatsApp, Facebook, Instagram and Google. Conversational text-to-order mechanics are not documented. https://www.deliverect.com/en-us/deliverect-direct · retrieved 2026-08-01

digital-google-order differentiator

What the page actually says about Google is 'Add delivery and pickup options to your profile' — that is Google Business Profile enrichment, which is not the same as the Order with Google end-to-end transaction program. No 'Preferred by Business' provisioning, no order-injection-from-Google statement. https://www.deliverect.com/en-us/deliverect-direct · retrieved 2026-08-01 adversarially verified

digital-apple-business-connect

The newly dumped help centre documents Direct Suite's ordering placements one how-to article each, and Apple is absent from all of them: a Facebook page Start Order button, a Facebook Shop Buy Now button, an Instagram Order Food button and stickers, a TikTok ordering link, a WhatsApp menu, a website ordering widget, downloadable QR codes, a deep link into an existing mobile app, and a Google Review URL. 'Apple Business Connect', 'Apple Maps' and 'Business Connect' return zero hits across the 984 English articles; 'Apple' appears only in Safari, App Store and iPad support links. Left unknown rather than no because that set is a collection of separate how-tos rather than a settings screen or table asserting it is the complete list of placements, and because an Apple Business Connect Order Food action is registered by the merchant against any ordering URL in Apple's own console - it can point at a Deliverect Direct link without Deliverect documenting or supporting it.

digital-loyalty-attach

Direct and Catering both cite loyalty program integration, and the integrations hub has a Loyalty & CRM category — indicating partner loyalty rather than a native engine sharing in-store identity. https://www.deliverect.com/en-us/integrations · retrieved 2026-08-01

digital-subscriptions

Checked every guest-facing monetisation surface in the dumped help centre. Direct Suite Marketing holds Coupons (basket or item, fixed amount or percentage or free item, validity window, usage limit, location / fulfilment-type / channel scope), Loyalty (store credit earned as a percentage of order value, spent under a redeemable-percentage and maximum-value cap, plus a one-off sign-up bonus), Campaigns (a triggered email a set number of days after a guest's last order) and Reviews. 'Recurring', 'membership' and 'subscriber' return zero guest-facing hits across the 984 English articles - 'Cancel a Subscription' and the Billing role permissions are the operator's own Deliverect plan, not a guest product - and Deliverect Pay's enumerated payment statuses (Pending, Authorised, Refused, Refund requested, Refunded, Partially refunded, Failed, Expired) contain no recurring or mandate state. Left unknown rather than no: no single page claims to enumerate Direct's product set, the six non-English help centres are not dumped, and developers.deliverect.com would not serve me content on 2026-08-09 (ReadMe bot block to a browser UA, empty SPA shell to a plain curl, 404/429 to the fetch tool).

digital-promo-parity

Discounts are modelled centrally (discount types, discount provider type, BOGO in menu) and pushed per channel. Parity with an in-store POS discount engine is not guaranteed and channel eligibility controls are not documented. https://developers.deliverect.com/page/list-of-discount-types.md · retrieved 2026-08-01

digital-guest-data-ownership differentiator

Direct markets 'guest data ownership' and first-hand guest profiles, but no documented bulk self-serve export without fee or approval. https://www.deliverect.com/en-us/deliverect-direct · retrieved 2026-08-01

digital-checkout-pci-sca

A Deliverect Pay payment-token flow and a Commerce API payment request/checkout flow are documented, implying hosted card capture. No PCI DSS 4.0 attestation, no script-integrity statement, no 3DS documentation found. https://developers.deliverect.com/page/deliverect-pay-payment-token-flow.md · retrieved 2026-08-01

digital-surcharge-transparency differentiator

Service charges, delivery costs, tips, bag fee, small order fee and bottle deposits are modelled per channel. Card surcharging, dual pricing and jurisdictional disclosure rules are not documented. https://developers.deliverect.com/page/payment-types.md · retrieved 2026-08-01

guest-loyalty-unified-profile

Direct builds 'detail-rich guest profiles' across its own channels. Automatic merge with in-store POS transactions and documented dedup behaviour are absent. https://www.deliverect.com/en-us/deliverect-direct · retrieved 2026-08-01

guest-loyalty-thirdparty-identity-attach differentiator

Marketplace orders are not anonymous tickets: the channel order model carries a customer object, and Deliverect Pay's payments list shows a 'Customer: The customer's name' column beside 'Channel: The delivery platform'. Named shortfall: there is no attach to a native profile. The guest database is documented as first-party only - 'You can view a list of customers who placed an order on a Direct Suite channel', with contact details, transactions, last purchase and order count - and the Online Ordering customer list is built from guests who 'create their own login on your Online Ordering site'. No article in the 984-article English help centre describes a DoorDash, Uber Eats or Grubhub order creating or matching one of those records, so marketplace identity stays on the order and never becomes a usable guest profile for loyalty or marketing. https://help.deliverect.com/en/articles/8045310-direct-suite-view-your-customers · retrieved 2026-08-09

guest-loyalty-accrual-models

The Direct Suite loyalty admin guide documents one earning model: 'Earning: a % of each order returned as credit'. Named shortfall: only percentage-of-order accrual is documented; per-item, per-quantity, tiered-by-spend, and operator-choice models are not documented. https://help.deliverect.com/en/articles/8041162-direct-suite-activate-and-manage-a-loyalty-program · retrieved 2026-08-04

guest-loyalty-tiers differentiator

The loyalty admin guide enumerates the entire program configuration: Details (title, description), Rules (Earning, Spending), Sign up bonus, and Scope (locations). No tier levels (bronze, silver, gold, etc.) or tier-based rules are documented. https://help.deliverect.com/en/articles/8041162-direct-suite-activate-and-manage-a-loyalty-program · retrieved 2026-08-04

guest-loyalty-offline-behavior differentiator

Cloud-only; no offline behaviour documented for anything.

guest-loyalty-offer-stacking-rules differentiator

The Online Ordering discount form states 'The following options are available for discounts' and then lists the complete field set: Discount code, Applicable on, Deactivate, Expired; Type (Lump, Percentage or Product) with its value fields; Availability (Valid from, Valid until, Day of the week); Extra configuration (Min order amount, Max order amount, Discount usage type limited by budget or by orders, with remaining-budget and remaining-order counters). The Direct Suite coupon form is equally fully enumerated - Code, Description, Amount, Limits, Valid from, Valid to, and Scope of locations, fulfillment types and channels. Neither exposes an exclusive-versus-combinable flag, a priority or precedence value, or an order-of-application setting. The only precedence Deliverect publishes is fixed behaviour inside loyalty spending - 'Define maximum limits when redeeming credits. The lowest value is always applied at checkout' - which is not configuration. https://help.deliverect.com/en/articles/7979308-deliverect-online-ordering-create-and-manage-discounts · retrieved 2026-08-09

guest-loyalty-targeted-offers differentiator

Direct markets 'time-sensitive promotions' and 'bespoke, tailor-made offers'. No documented audience rule builder over recency/frequency/spend/items. https://www.deliverect.com/en-us/deliverect-direct · retrieved 2026-08-01

guest-loyalty-rfm-segmentation differentiator

Deliverect computes the RFM inputs without the operator building a query: the Direct Suite Customers table lists each guest's contact details, transactions, last purchase date and order count, and opening a guest shows 'Total purchase amount', 'Average order value', 'Total orders' and the full order history. One lifecycle dimension is also automated end to end - an email campaign is triggered by 'Days after last order: Choose how long after a customer's previous order they will receive the email. The minimum is 7 days.' Named shortfall: recency is the only actionable dimension. There are no computed lifecycle segments (no new, regular, at-risk, lapsed or VIP labels), no segment builder, and no way to target a campaign on frequency or monetary value - those two remain display-only columns. https://help.deliverect.com/en/articles/8045310-direct-suite-view-your-customers · retrieved 2026-08-09

guest-loyalty-lifecycle-automation

'Marketing automation through personalized email campaigns' is claimed; named always-on birthday/win-back/first-visit triggers are not documented. https://www.deliverect.com/en-us/deliverect-direct · retrieved 2026-08-01

guest-loyalty-native-email-sms differentiator

Native email campaigns are claimed for Direct. Native SMS sending is not mentioned. https://www.deliverect.com/en-us/deliverect-direct · retrieved 2026-08-01

guest-loyalty-consent-management

Consent is captured per guest at signup and surfaced to the operator: 'Customers can choose if they are willing to receive marketing communication (offers, personalized benefits, and money-saving promotions). This is indicated in the Subscribed to marketing column', and that column travels with the self-serve customer CSV export. Named shortfall: it is a single boolean covering the one channel Deliverect sends on (email). No timestamp of consent and no source-of-consent field is recorded or displayed, there is no per-channel consent breakdown, and no article describes how a revocation received by any other means is honoured. The only adjacent control is a support-activated GDPR anonymisation setting rather than a consent ledger. https://help.deliverect.com/en/articles/7979317-deliverect-online-ordering-view-and-export-customers · retrieved 2026-08-09

guest-loyalty-10dlc-registration

Deliverect's outbound guest marketing is email and only email. The Direct Suite campaign builder's creation step is 'Select the Create campaign button and choose Email campaign', its configurable fields are campaign name, days after last order, reminder sending time and an optional attached discount code, its customisation is cover image, email subject, message headline, message content, offer headline and button text, and its test action is 'Enter an email address and select the Send button'. The operator-facing Alerts feature enumerates its delivery methods the same way - 'Notify me by: Email'. Across the 984-article English help centre, 'A2P', '10DLC', brand registration and campaign registration return zero hits, and the only SMS strings in the corpus are UI translations belonging to a third-party French loyalty integration rather than to Deliverect. With no SMS sending through the platform there is no A2P 10DLC registration for Deliverect to handle, and it documents none. https://help.deliverect.com/en/articles/10713992-deliverect-direct-create-and-manage-email-campaigns · retrieved 2026-08-09

guest-loyalty-campaign-attribution differentiator

Redemption of a specific offer is counted first-party: a discount can be capped by 'Total budget' or 'Total discount orders' and the form reports 'Remaining budget' and 'Remaining discount orders' as it is consumed, while Analytics' Revenue Breakdown reports total discounts alongside revenue, orders and average order value with CSV export. Order-level linkage is published too, but outward: Direct Suite's Google Tag Manager integration fires a 'place_order' event carrying id, revenue, tax, shipping, tips, discount, loyalty, serviceCharges, coupon, fulfillment, channel and products together, plus an 'initiate_checkout' event carrying coupon and total. Named shortfall: the attribution has to be assembled in the operator's own analytics stack. Deliverect publishes no in-product report tying a named campaign or offer's redemptions to the check totals they rode on, and no incremental-sales or lift measurement of any kind. https://help.deliverect.com/en/articles/7979308-deliverect-online-ordering-create-and-manage-discounts · retrieved 2026-08-09

guest-loyalty-data-export-portability differentiator

Guest list: 'To create a CSV file of your customers, select the Export customers button. Go to your Operation reports page to download the file.' The exported record is the one shown on the Customers page - the personal information the guest stored on their login, plus the 'Subscribed to marketing' flag - and access is gated only by the 'View Online Ordering customers' / 'Edit Online Ordering customers' role permissions, with no support step. Transaction history exports the same way and equally self-serve: 'Export orders' and 'Export analytics' are role permissions in their own right, the Analytics page states 'For each option, an export can be created to be used by an external application. Click on the Export button', and there is a dedicated 'Export Order Reports' article; every CSV lands on the same Operation reports page, whose 'Export' operation type simply 'Provides the download link'. Recorded caveat rather than a downgrade: the guest list and the order history are two exports, not one combined file. https://help.deliverect.com/en/articles/7979317-deliverect-online-ordering-view-and-export-customers · retrieved 2026-08-09

guest-loyalty-cdp-event-api differentiator

RE-CITED 2026-08-09 off the deleted /docs/reporting-endpoints.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The outbound event contract survives and is enumerated on the flow diagram -- orderStatusUpdate, courierStatusUpdate, menuUpdate, busyMode, paymentUpdate, checkoutUpdate. A CAVEAT THE DELETED PAGE'S ABSENCE MAKES MORE IMPORTANT, and it is the vendor's own words on the surviving FAQ: "Deliverect does not have a Reporting API, however you will be able to collect order data using our Reporting Endpoint feature" -- and that FAQ links to the now-deleted guide. So transaction-level events are pushed to a customer endpoint; a queryable event API is explicitly denied by the vendor. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/commerce-api-flow-diagram.md · retrieved 2026-08-09

guest-loyalty-review-capture-routing differentiator

Confirmed: 'AI-powered sentiment analysis' that 'transforms delivery reviews into actionable insights' across locations. Correctly scored partial — it is inbound analysis of marketplace reviews only, with no feedback solicitation and no score-based routing. https://www.deliverect.com/en-us/sentinel · retrieved 2026-08-01 adversarially verified

guest-loyalty-referral-program

The Direct Suite loyalty admin guide enumerates the entire program configuration: Details (title, description), Rules (Earning: a % of each order returned as credit; Spending: redeemable % and maximum redeemable value), Sign up bonus ('incentivize customers to create an account' with bonus credits), and Scope (locations). The sign-up bonus is the only acquisition incentive — no referral codes or links, no referred-first-order attribution, no two-sided reward. The Marketing collection's full surface is coupons, loyalty, visitor tracking and email campaigns, and help-centre plus 144-page dev-index searches for 'referral' return nothing. https://help.deliverect.com/en/articles/8041162-direct-suite-activate-and-manage-a-loyalty-program · retrieved 2026-08-04

guest-loyalty-wallet-pass differentiator

The loyalty program form is the entire configurable surface of Direct Suite loyalty and it is enumerated in full: Details (Title, Description); Rules > Earning ('Set how much credit customers receive with each order'); Spending ('Redeemable (%)' and 'Maximum redeemable value', with 'The lowest value is always applied at checkout'); Sign up bonus ('Bonus credits'); Scope (locations). The mechanic is store credit attached to a Direct Suite web account and redeemed at that channel's checkout, so there is no card, membership number or pass artifact in the model to push to a wallet - and no branded app download for the claim's alternative to substitute for, since Direct ordering runs in the browser. 'Apple Wallet', 'Google Wallet' and pass issuance return zero hits across the 984-article English help centre. https://help.deliverect.com/en/articles/8041162-direct-suite-activate-and-manage-a-loyalty-program · retrieved 2026-08-09

guest-loyalty-privacy-rights-tooling

Some admin tooling exists, but only for minimisation: at least ten POS integration settings pages carry an 'Anonymize customer data (GDPR)' toggle - 'Activate to hide order customer info and delivery address details ... Updates the customer's name to Anonymized when the order is finalized ... The customer information is available until the order receives the Finalized order status.' That is operator-configurable, in-app, per integration. Named shortfall: anything beyond it is a ticket. Account-level anonymisation is explicitly not self-serve - 'Your customers' data can be anonymized in Deliverect. To request this, please reach out to your account manager or our support team and ask them to activate the GDPR setting for your locations.' There is no in-app subject-access or deletion request queue, no per-guest delete or export action on the Customers page, and no documented propagation of a deletion to loyalty credit balances or email-campaign audiences. https://help.deliverect.com/en/articles/9595607-anonymize-customer-data · retrieved 2026-08-09

guest-loyalty-redemption-fraud-controls

Two enumerations close this. The loyalty program form is the whole configurable surface and contains only Earning (credit as a percentage of order value), Spending ('Redeemable (%)' and 'Maximum redeemable value'), a sign-up bonus and location scope - a per-order value cap, not a redemption velocity limit. And 'Role Permissions' opens 'In this article, you can find every permission you can activate for a user role' and then lists every permission across all 25 sections; loyalty appears exactly once, as 'Manage loyalty integrations', with no manual credit or point adjustment permission, no approval permission and no audit-log permission to gate. Consistently, nothing in the 984-article English help centre documents manual credit adjustment, manager approval of one, employee self-redemption flagging, or a loyalty audit log; 'velocity' returns zero hits. https://help.deliverect.com/en/articles/8041162-direct-suite-activate-and-manage-a-loyalty-program · retrieved 2026-08-09

guest-loyalty-ai-offer-recommendation differentiator

The page uses present-tense verbs but makes no general-availability statement, gives no launch date, names no customer using it, and publishes no pricing. Present-tense marketing copy is not evidence of a shipped feature, and this is a paid-add-on-adjacent AI surface — exactly the category where vendors pre-announce. Partial with an explicit availability-unverified flag. https://www.deliverect.com/en-us/deliverect-ai · retrieved 2026-08-01 adversarially verified

guest-loyalty-stored-value-gift

RE-CITED 2026-08-09 off the deleted /docs/checkout-basket-1.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. Same evidence as payments-gift-cards, deliberately kept consistent so one fact does not yield two answers: gift_card is one of three documented payment types at Commerce checkout and its externalId is "the transaction ID", i.e. a reference into someone else's ledger. No first-party issuance, balance or cross-location card is documented. Partial stands. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/commerce-checkout-glossary.md · retrieved 2026-08-09

labor-clock-in-at-pos

Deliverect sells no workforce product. Product nav covers ordering, marketplace, dispatch and revenue protection only; the Quest App is grocery order-picking, not labor. https://www.deliverect.com/en-us/quest-app · retrieved 2026-08-01

labor-photo-punch-verification differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-geofenced-mobile-punch

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-offline-time-punch differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-granular-rbac

Deliverect documents a real per-permission model rather than fixed tiers: the Role Permissions article covers 'every permission that can be activated for a user role', roles can be created and edited on the Roles page beyond the Finance, Manager, Store staff and Technical support defaults, a user 'cannot activate permissions that you do not have yourself', and location scoping exists via Restrict Menu Edits Based on Location. Shortfall: the permissions govern the Deliverect portal — menus, products, orders, analytics and billing — and not the discrete POS-terminal actions this claim enumerates (void, comp, discount, refund, drawer open, price change), which Deliverect has no terminal to perform. Granular and per-location, over a different action surface. https://help.deliverect.com/en/articles/7979053-role-permissions · retrieved 2026-08-03

labor-manager-override-audit

Deliverect does keep a queryable action log with individual attribution. 'View Operation Reports' is gated by a 'View operation reports' permission and filterable after the fact by 'Date and time', 'Operation type', 'Location', 'Delivery channel' and 'Status', and its enumerated operation types name the actor: 'Close store - User who initiated the closure'; 'Busy mode - User who made the change, Channel, Preparation time, Busy Mode status'; 'Product sync - User who initiated the sync'; 'CSV product update - User who initiated the update'; 'Update holidays - User who initiated the update'; 'Health check - User who initiated the check'. The store-closure troubleshooting article confirms the intended use: 'Examining Deliverect's activity logs can help identify who initiated the closure'. Named shortfalls: there is no manager-override or approval workflow to attribute - Deliverect runs no terminal, and the nearest control is role-scoped rather than approval-based ('Deliverect Pay: Specify Which Roles Can Perform Refunds'); several enumerated operation types record no user at all, including Menu publish, Open store, Channel activation/deactivation and Update store opening hours; and neither immutability nor retention is stated anywhere. https://help.deliverect.com/en/articles/7979010-view-operation-reports · retrieved 2026-08-09

labor-native-scheduling differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-demand-labor-forecast differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-realtime-labor-percent differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-overtime-prevention differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-break-compliance-by-state differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-fair-workweek-support

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-minor-labor-rules

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-tip-pooling-rules

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-tip-distribution-audit-trail

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-qualified-tips-w2-reporting differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-native-payroll differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-payroll-export-formats

No labor data exists to export; no payroll provider is named anywhere.

labor-shift-swap-workflow differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-digital-onboarding-i9

Migrated from the 2026-08-01 research pass; no source URL was recorded.

labor-server-performance-metrics differentiator

No employee dimension in Deliverect's data — orders arrive from channels, not from servers.

inventory-recipe-bom-costing

No recipe or BOM object in the entire published API surface.

inventory-unit-conversion-yields

The admin guide enumerates inventory management in full: import a CSV, 'Update status: Choose to activate or deactivate the items', 'Update stock status: Mark the item as in or out of stock', and Sync, which sends 'current stock status' to channels (companion article 10226230). There is no on-hand quantity beyond binary stock status, no purchase/recipe/count units, no conversion factors, and no yield or waste percentage; zero 'yield' or 'recipe' pages exist in the 144-page developer index. Deliverect's inventory concept is channel availability, not back-of-house stock accounting. https://help.deliverect.com/en/articles/10682905-manage-your-inventory · retrieved 2026-08-04

inventory-theoretical-vs-actual differentiator

Requires recipe costing, which does not exist.

inventory-realtime-depletion differentiator

Retail-side inventory endpoints (Post Inventory Update, Inventory JSONL flow) sync stock levels into channel availability. Deliverect consumes stock from the merchant's system; it does not compute ingredient depletion from modifier selections. https://developers.deliverect.com/page/post-inventory-update.md · retrieved 2026-08-01

inventory-86-auto-sync differentiator

Stock-level updates drive channel availability and item-unavailable actions for retail. Ingredient-threshold-driven menu-item 86 for restaurants is not documented. https://developers.deliverect.com/page/retail-orders-item-unavailable-actions.md · retrieved 2026-08-01

inventory-count-modes

No counting workflow; Deliverect ingests stock from an external system.

inventory-mobile-count-offline

The Quest App scans and flags out-of-stock items during grocery picking on Zebra scanners, but it is a picking app, not an inventory counting app, and no offline mode is documented. https://www.deliverect.com/en-us/quest-app · retrieved 2026-08-01

inventory-vendor-catalogs-edi differentiator

No broadline distributor integrations; no purchasing module.

inventory-invoice-ocr differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

inventory-price-change-alerts differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

inventory-par-auto-suggest differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

inventory-waste-logging

Migrated from the 2026-08-01 research pass; no source URL was recorded.

inventory-transfers

Migrated from the 2026-08-01 research pass; no source URL was recorded.

inventory-commissary

Migrated from the 2026-08-01 research pass; no source URL was recorded.

inventory-lot-traceability

Migrated from the 2026-08-01 research pass; no source URL was recorded.

inventory-shelf-life-expiry

Migrated from the 2026-08-01 research pass; no source URL was recorded.

inventory-bar-partial-bottle

Migrated from the 2026-08-01 research pass; no source URL was recorded.

inventory-cogs-gl-export

Deliverect has no inventory or recipe module; inventory management is limited to binary stock status (in/out) for channel availability. Theoretical inventory costing, GL export, and COGS calculations are entirely out of scope.

inventory-native-not-partner differentiator

Inventory and recipe costing are entirely outside Deliverect's scope; operators must contract a separate product.

inventory-menu-margin-linkage differentiator

Deliverect AI's menu agent ranks items by sales performance, not contribution margin — there is no ingredient cost to join against. https://www.deliverect.com/en-us/deliverect-ai · retrieved 2026-08-01

reporting-realtime-dashboard

Analytics dashboard consolidating sales across locations and channels, plus a live store-status map in Sentinel. A dedicated off-premise mobile reporting app is not documented (the DMA is an operations app). https://www.deliverect.com/en-us/deliverect-restaurants · retrieved 2026-08-01

reporting-eod-closeout

Analytics (article 7978952) has a date filter and a 'Revenue Breakdown' showing 'your total revenue, delivery costs, discounts, tips, service charges, and taxes', with gross sales and AOV per location; orders export to CSV (7979015). Shortfall: no single daily close-out document, no tender-type breakdown and no expected cash deposit -- Deliverect never holds the drawer. Article 9104394 'Reporting Differences Between Your POS, Channel, and Deliverect' states 'Revenue displayed in Deliverect does not include the following: Delivery fees, Discounts, Tips' and tells operators to export one day and match order IDs against POS and channel reports, i.e. Deliverect is one of three divergent sources rather than the reconciler. https://help.deliverect.com/en/articles/7978952-track-performance-using-the-analytics-page · retrieved 2026-08-09

reporting-pmix-modifier-level

The Menu Items analytics page reports items sold with quantity ('Items sold as item') and revenue (base vs extended, upsell and variation revenue), with a type selector spanning products, meal deals AND modifiers, per-modifier related-item tables ('Products that contained the modifier'), and CSV export carrying SuccessfulQuantity/SuccessfulRevenue per item. Named shortfalls: filters are location, custom tag, channel and date only — no daypart filter and no revenue-center dimension (channel is the closest analogue); revenue is defined net of delivery fees, tips, service charges and discounts with taxes included (Analytics page article 7978952), with no per-item gross-vs-net split. https://help.deliverect.com/en/articles/7978954-view-menu-items-sold-on-your-channels · retrieved 2026-08-04

reporting-comps-voids-audit

Comps and voids are POS-terminal transaction types. Deliverect is an order-aggregation platform and sees only orders flowing in from channels; it does not see POS-side comps, voids, or their audit trails.

reporting-cash-over-short

No drawer or cash-handling surface.

reporting-labor-productivity

No labor data.

reporting-server-scorecards differentiator

No employee dimension.

reporting-channel-profitability differentiator

Revenue comparison by channel and location is a headline dashboard feature, and Reclaim quantifies refund deductions. Margin net of each marketplace's commission is not documented as a report. https://www.deliverect.com/en-us/deliverect-restaurants · retrieved 2026-08-01

reporting-multiloc-drilldown differentiator

'Comparing revenue across locations and channels' is claimed; drill-down from group total to individual transaction is not documented. https://www.deliverect.com/en-us/deliverect-restaurants · retrieved 2026-08-01

reporting-custom-report-builder differentiator

'Introduction to Your Dashboard' enumerates the reporting surface exhaustively -- 'The dashboard is split into multiple tabs. The articles listed below explain the functionality of each: Main page, Menu items, Orders, Custom tags, Reviews, Insights, Order issues'. Every tab is a canned view whose filters are fixed (locations, custom tags, channels, date). The nearest thing to authoring is the CSV export dialog, which lets you pick fields and group 'by day, week, or all' (7978954) or choose Fields/Format/Split items (7979015) -- but the selection is not saved and produces a file, not a saved report. No dimension/measure builder or query interface appears in the 984-article English help centre. https://help.deliverect.com/en/articles/7978951-introduction-to-your-dashboard · retrieved 2026-08-09

reporting-scheduled-delivery

No scheduled or recurring report delivery is documented: the alert-creation screen is event-driven ('An email is sent immediately when the event first occurs') with 'Notify me by: Email' and no cadence field, and order exports are pull-only ('Request export' then a manual download from Operation reports, 7979015). But absence here is not established. The Role Permissions article lists a whole 'Reporting Endpoints' permission group (Create, Remove, Edit, View reporting endpoints) for a feature that has no explanatory article anywhere in the 983-article English help centre, so a configurable report-delivery destination exists in the product that the help centre does not describe. Neither cited screen claims to enumerate the platform's report-delivery options, so the earlier 'no' rested on the wrong enumeration.

reporting-raw-warehouse-export differentiator

RE-CITED 2026-08-09 off the deleted /docs/reporting-endpoints.md, ONTO A VENDOR-STATED DENIAL, WHICH IS BETTER EVIDENCE THAN THE PAGE IT REPLACES. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The surviving FAQ answers the question directly: "Deliverect does not have a Reporting API, however you will be able to collect order data using our Reporting Endpoint feature" -- and its link to that feature's guide is itself a 404. So the documented mechanism is webhook push of transaction-level events to a customer endpoint, and no scheduled bulk drop to S3/SFTP/Snowflake/BigQuery is documented. Partial stands on a first-party denial rather than on an absence. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/faq.md · retrieved 2026-08-09

reporting-public-api differentiator

Comprehensive public REST docs covering orders, menu, availability, stores, dispatch and payments — but no labor data, and credentials are not self-serve: staging keys come from the API team and production keys are issued through a certification meeting. https://developers.deliverect.com/docs/certification-process.md · retrieved 2026-08-01

reporting-webhooks differentiator

Order lifecycle, courier status and reporting webhooks, HMAC-signed, with a documented POS order webhook failover flow and IP/domain whitelisting. https://developers.deliverect.com/reference/hmac-authentication.md · retrieved 2026-08-01

reporting-api-not-upcharged differentiator

Checked four surfaces on 2026-08-09 and none prices API access either way. (1) deliverect.com/en-us/pricing is quote-only -- 'Deliverect offers flexible pricing based on your business's specific needs' -- and its only API sentence is marketing: 'we offer fully customizable APIs. Our dedicated team ensures smooth integrations with 99.998% store uptime'. (2) The US Terms of Service addresses subscription and transaction fees but contains no API-access fee clause. (3) The help centre's exhaustive Role Permissions article (7979053) shows API keys are created inside the ordinary portal -- an Applications group with 'Create application: Allows creating new application keys', Edit, View, Revoke, Unrevoke -- which shows access is self-serve but says nothing about cost. (4) developers.deliverect.com/llms.txt (84 links) has no commercial page. Deliverect Plus and Deliverect AI are documented as priced add-ons, so a paid gate on data access cannot be excluded by inference.

reporting-tier-paywall differentiator

The Deliverect Plus article's 'What's included?' list is Sales comparisons ('Use in-depth stats to compare the performance of your channels and locations over set periods'), Menu optimization, Notifications and Refund reasons, reached by 'Try for free' then a paid subscription. The Sales Comparison article (7978950) states flatly 'This feature is included in Deliverect Plus.' Four of the seven documented alert topics -- Item snoozed, Store closed by channel, Store closed by user, Order delayed -- are also marked '(requires Deliverect Plus)', as is refund-reason analysis (7978960). So cross-location/period comparison and refund analytics sit behind an add-on SKU rather than the entry-level plan; base Analytics is limited to revenue/orders/AOV, item mix, per-location and per-channel lists. https://help.deliverect.com/en/articles/7978935-deliverect-plus · retrieved 2026-08-09

reporting-history-retention differentiator

Searched the full English help centre dump (983 of 984 articles from help.deliverect.com/sitemap.xml) on 2026-08-09 for 'retention', 'archive', 'months of data', 'date range' and 'older than'. The only retention hit is a GDPR boilerplate line inside a channel-specific article; the only archival hit is 'Archive or Delete a Menu' (7978997), which archives menu objects, not history. Analytics (7978952), Menu Items (7978954) and the order export (7979015) all expose an unqualified date filter with no stated earliest date, no truncation warning and no archive-retrieval step. The US Terms of Service says only that on termination 'Customer will lose access to the data, information, and content associated with such subscription'. No minimum queryable window -- 24 months or otherwise -- is published on help.deliverect.com, deliverect.com or developers.deliverect.com, and nothing states a cap either, so neither yes nor no is supportable.

reporting-anomaly-alerts differentiator

Email alerting on downtime plus a live map with real-time out-of-stock monitoring confirmed on the page. Note it remains a marketing page rather than product documentation, and Sentinel's pricing relationship to the base product is not stated anywhere — so this may be a paid add-on capability, which the dossier should flag alongside Plus/Reclaim. https://www.deliverect.com/en-us/sentinel · retrieved 2026-08-01 adversarially verified

reporting-nl-query

Deliverect ships a Model Context Protocol server (https://developers.deliverect.com/mcp) that lets an AI assistant query the tenant's own account: the docs describe 'Direct API access to Deliverect functionality', 'Documentation search capabilities' and 'Real-time data from your Deliverect account', with setup instructions for 'AI-powered code editors like Cursor and Windsurf, plus general-purpose tools like Claude Desktop' and authentication headers passed by the client. Named shortfall: there is no in-product ask-a-question surface - the Deliverect AI catalogue (12981597) is three menu and order-repair agents, and Analytics is seven fixed tabs (7978951) - so the operator must run a third-party MCP client with API credentials; the server returns API data and text, not a figure or chart; and Deliverect holds no labor data for the claim's second data domain. https://developers.deliverect.com/docs/mcp.md · retrieved 2026-08-09

reporting-guest-cohorts differentiator

'Direct Suite: View Your Customers' shows 'a list of customers who placed an order on a Direct Suite channel', with 'names ... contact details, transactions, last purchase data, and order count', and per customer 'Total purchase amount', 'Average order value', 'Total orders' plus the order history table. Identifiable guest records therefore exist with lifetime spend and frequency inputs. Shortfalls: no cohorting -- no new-vs-returning counts, no visit-frequency bands, no lifetime-spend brackets, and no analytics tab for guests (the dashboard's seven tabs are Main, Menu items, Orders, Custom tags, Reviews, Insights, Order issues, per 7978951); and coverage is limited to Direct Suite channels, since marketplace orders arrive without identifiable guests and customer data can be anonymised account-wide via the GDPR setting (9615604). https://help.deliverect.com/en/articles/8045310-direct-suite-view-your-customers · retrieved 2026-08-09

reporting-sales-forecast differentiator

The dashboard enumeration (Main page, Menu items, Orders, Custom tags, Reviews, Insights, Order issues) is entirely historical: 'On the main Analytics page, explore historical data about your locations' (7978952). Comparison, where it exists, is backwards-looking -- the Plus-gated Sales Comparison compares a chosen period 'to a period of' N prior weeks (7978950). The three AI agents (12981597) optimise menus and fix failed orders; none forecasts. A grep of all 983 dumped English articles returns zero hits for 'forecast' and only one for 'predict' (a marketing line about the Courier App). No forward projection at daypart or hourly granularity is exposed in the reporting UI, and Deliverect holds no scheduling or ordering workflow to consume one. https://help.deliverect.com/en/articles/7978951-introduction-to-your-dashboard · retrieved 2026-08-09

reporting-tip-tax-compliance

No payroll or employee data; tips are passed through to the POS only.

multi-location-org-hierarchy

Account > brands > locations, with a main/master location concept and automation configurable at 'store or group level'. A named three-level hierarchy object that reporting and permissions scope to is not documented. CITATION QUARANTINED 2026-08-09: https://developers.deliverect.com/docs/use-master-location.md is DELETED (404 at the ~237KB ReadMe shell) and NO REPLACEMENT WAS LOCATED. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. Searched and came up empty: /docs/ and root .md routes, the /v1.1/ version prefix, all 64 live /page/ documents (369,527 chars), the 7 live /reference/ pages, and the 983-article English help centre. The specific sentence this cell rested on -- "Deliverect does not push products from other locations when those locations use products from the main location" -- returns zero hits corpus-wide, as does the phrase "main location" itself, so it cannot be re-verified and must not be re-attached to a lookalike page. The verdict and its reasoning are KEPT -- the page was read and quoted on the date recorded -- but the URL is moved to dead_url and stamped do-not-refetch, because a live URL is an instruction to future tooling. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/docs/use-master-location.md · retrieved 2026-08-01 · not refetchable · page gone · graded B when read

multi-location-central-menu-publish

The mechanism described in the docs is materially different from the score's wording. The page describes a SHARED product inventory that child locations reference via a 'Use main location' toggle, and states explicitly: 'Deliverect does not push products from other locations when those locations use products from the main location.' There is no authored-once-then-published pipeline, no described publish event, and no field-level override or governance model. One shared catalogue for many locations is achieved; central menu PUBLISH as scored is not documented. CITATION QUARANTINED 2026-08-09: https://developers.deliverect.com/docs/use-master-location.md is DELETED (404 at the ~237KB ReadMe shell) and NO REPLACEMENT WAS LOCATED. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. Searched and came up empty: /docs/ and root .md routes, the /v1.1/ version prefix, all 64 live /page/ documents (369,527 chars), the 7 live /reference/ pages, and the 983-article English help centre. The specific sentence this cell rested on -- "Deliverect does not push products from other locations when those locations use products from the main location" -- returns zero hits corpus-wide, as does the phrase "main location" itself, so it cannot be re-verified and must not be re-attached to a lookalike page. The verdict and its reasoning are KEPT -- the page was read and quoted on the date recorded -- but the URL is moved to dead_url and stamped do-not-refetch, because a live URL is an instruction to future tooling. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/docs/use-master-location.md · retrieved 2026-08-01 · not refetchable · page gone · graded B when read adversarially verified

multi-location-local-override-policy differentiator

'Edit Product Information for a Single Location' (7979040): 'Any edits you make on this page will only be made for that location', with a per-field Revert button, and an explicit central lock -- 'Some information can only be edited for all locations (product specifications, packaging). Change to All Locations ... to edit that information.' The customisation feature names the overridable set: 'The customizable fields include prices, taxes, visibility status, names, descriptions, categories, and images', scoped to Locations, Location groups, Channels, Custom tag or Order type (7978996). Shortfalls: the locked set is hard-coded by Deliverect (specifications and packaging only), so corporate cannot lock name, image or price while leaving others open; governance is instead coarse -- 'Menu edit restrictions' picks which locations may edit a menu at all and a per-user 'Restrict to locations' toggle enforces it (7979005). There is no per-field override policy object. https://help.deliverect.com/en/articles/7979040-edit-product-information-for-a-single-location · retrieved 2026-08-09

multi-location-price-zones

RE-CITED 2026-08-09 off the deleted /docs/price-level-configuration.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. Value unchanged and the shortfall is now sharper, because the surviving schema page states the axis explicitly: priceLevels support "different pricing for specific ordering channels and menu fulfilment type" -- channel and fulfilment type, NOT geography. The example levels are Takeaway, Delivery and First Party. So per-channel and per-order-type pricing is documented from one product record, while a per-location-group price tier and per-daypart variance are not. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/product-configuration.md · retrieved 2026-08-09

multi-location-scheduled-publish differentiator

Menus can be scheduled by time, day and location. Per-location timezone interpretation and post-activation rollback are not documented. https://www.deliverect.com/en-us/deliverect-kiosk · retrieved 2026-08-01

multi-location-new-store-template differentiator

Reusable pieces exist: menus can be duplicated ('create or duplicate an existing menu, and then assign a single location', 7979005); a new menu's catalogue source is chosen with 'Use products from ... choose which location to use to build your menu if you have synced products from multiple locations' (9129049); tablet settings are cloned by device profiles linked to a location (7979054); and location groups batch locations (7978966). Shortfalls: there is no clone-a-location action -- 'Add a Location' (7978962) is a request form, 'You may be asked to provide your information so that a Deliverect representative can contact you', and adding a brand states 'A representative from Deliverect will be in touch with you typically within three days' (7978963). Taxes, user roles, printers and tenders are configured per object with no template, and no expected time-to-open is published anywhere on help.deliverect.com or deliverect.com; the only activation figure documented is per-channel (e.g. Deliveroo 'can take 48 hours', 7979326). https://help.deliverect.com/en/articles/7978962-add-a-location · retrieved 2026-08-09

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

Read the Role Permissions article (7979053) in full on 2026-08-09; it opens 'In this article, you can find every permission you can activate for a user role' and lists ~150 permissions across 27 groups. There is no franchisor/franchisee, tenant or ownership construct in it: separation is achieved only by scoping a user to locations ('Manage locations: Allows modifying the allowed locations of other users') plus the 'Restrict to locations' toggle in 7979005/9423492. Two undocumented mechanisms block a verdict. First, the permission 'Access linked accounts -- Allows accessing accounts linked to your accounts' implies cross-account visibility, but no article in the 983-article English dump explains linked accounts. Second, 'Log in to Deliverect' (7978937) Tip 9 says 'One email address cannot be linked to multiple accounts except in the case of Group or Partner accounts. Contact our support team if you require this' -- a support-provisioned multi-account structure with no published permission model. The claim's other half is also untestable: Deliverect holds no employee, banking or labor data, so franchisee ownership of it cannot be evidenced either way. enterprise.deliverect.com, a separate portal named in 7978937/7978940, is not documented in the help centre at all.

multi-location-royalty-calculation differentiator

Held to the highest bar. Zero pages in the 145-page index match 'royalty' or 'franchise'. No franchise-fee surface in any product page. Sustained. https://developers.deliverect.com/llms.txt · retrieved 2026-08-01 adversarially verified

multi-location-royalty-collection

Migrated from the 2026-08-01 research pass; no source URL was recorded.

multi-location-consolidated-reporting

Analytics dashboard aggregates and compares revenue across locations and channels; Sentinel gives a portfolio-wide uptime map. Labor/void/comp aggregation is out of scope. https://www.deliverect.com/en-us/deliverect-restaurants · retrieved 2026-08-01

multi-location-normalized-item-rollup differentiator

'View Menu Items Sold on Your Channels' filters 'On locations', 'On custom tags', 'On channels', 'On date' -- 'It is possible to utilize all filters at once and with multiple locations' -- and returns one row per item with Items sold, Revenue base, Successful revenue extended, Revenue from upsells and variations; the Times Snoozed column is explicitly cross-location ('an item snoozed once on 5 locations would show 5'), confirming rows aggregate locations rather than splitting by them. Local renames and prices are customisations on the same product ('The customizable fields include prices, taxes, ... names', 7978996; 7979040), so a locally renamed or repriced item still reports under the one product. Shortfalls: no document states the rollup key is a shared corporate item ID, and product identity comes from the POS PLU -- where a chain has no master location the docs tell operators to export and import catalogues 'so that item PLUs don't have to be written manually on every location' (23512 / National Soft), meaning locations that carry different PLUs for the same dish are not documented to consolidate. https://help.deliverect.com/en/articles/7978954-view-menu-items-sold-on-your-channels · retrieved 2026-08-09

multi-location-cross-location-giftcard

No gift-card or stored-value product.

multi-location-cross-location-loyalty

'Direct Suite: Activate and Manage a Loyalty Program' defines one programme with Earning ('10% of an order totaling EUR15 gives the customer EUR1.50 credit to use on future orders'), Spending caps (Redeemable %, Maximum redeemable value), a sign-up bonus, and a Scope section: 'Select the Add location button to choose which locations have access to this loyalty program.' One programme therefore spans many locations. Shortfalls: the article never states that a customer's credit balance and history are shared across those locations, only that the locations share the programme definition; and the whole feature is confined to Direct Suite, Deliverect's own ordering channel -- customer records are 'customers who placed an order on a Direct Suite channel' (8045310), so marketplace orders (Uber Eats, DoorDash, Deliveroo) and any in-store POS sales earn and redeem nothing. Third-party loyalty is a separate integration category ('Manage loyalty integrations' permission, 7979053). https://help.deliverect.com/en/articles/8041162-direct-suite-activate-and-manage-a-loyalty-program · retrieved 2026-08-09

multi-location-multi-brand differentiator

RE-CITED 2026-08-09 off the deleted /docs/how-do-i-get-account-brands.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The object survives as an order-payload field with the multi-brand use case stated in the field definition itself: `brandId` "Appears where customer operates multiple brands from one location", linking to the Get account brands reference. So brands remain a first-class API object and orders are attributable to a brand, which is what the yes rests on. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/glossary-pos-orders.md · retrieved 2026-08-09

multi-location-multi-tax-jurisdiction

RE-CITED 2026-08-09 off the deleted /docs/how-to-calculate-taxes.md, AND THE OLD SHORTFALL WAS TOO STRONG. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. It read: "The tax doc documents exactly one axis ... Nothing about multiple rates, rate tables, jurisdictional rules, or per-item tax classes." THE SURVIVING PAGES REFUTE PART OF THAT. Tax is a repeating structure with named entries and a class id -- `"taxes": [ { "name": "GST", "taxClassId": 0, "total": 51 } ], "taxTotal": 51, "taxRemitted": 51` -- so multiple named taxes per order and a per-item tax class ARE documented. And rates vary by fulfilment type in the published menu: `"deliveryTax": 6000, "takeawayTax":6000, "eatInTax": 6000`, with tax-exclusive regions such as the United States handled by a separate `"taxes"` array the channel computes into. WHAT IS STILL ABSENT is the jurisdictional half: no rate table keyed to a state, county or municipality, and no rule engine that picks a rate from a location's address -- the merchant's tax-exclusive setting is configured by Deliverect per account. Partial is therefore UNCHANGED, but it now rests on a real gap rather than on an understatement. This is the fifth session running that a shortfall sentence measured on one surface understated the product. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/pos-payments-taxes-discount-other-charges.md · retrieved 2026-08-09 adversarially verified

multi-location-multi-currency-locale

Published currency list and translation language codes with translatable menu elements; operates in 65+ countries. Consolidated conversion to a single reporting currency is not documented. https://developers.deliverect.com/page/list-of-currencies.md · retrieved 2026-08-01

multi-location-config-audit-log differentiator

'View Operation Reports' gives 'the complete list of filters ... Date and time, Operation type, Location, Delivery channel, Status' and then enumerates every operation type with the fields each records. Many carry actor attribution: Close store ('User who initiated the closure'), Busy mode ('User who made the change'), CSV product update and Pending CSV product update ('User who initiated the update'), Product sync and Product sync preview ('User who initiated the sync'), Update holidays ('User who initiated the update'), Health check, plus Billing, Bulk onboarding, Bulk user import, Channel activation/deactivation, Courier update, Export, Insert order, Menu API import, Menu import, Menu publish, Open store, Order update, Snooze report, Update store opening hours. Exporting it is a distinct permission ('Export operation reports', 7979053), so corporate can pull it. Shortfalls: the enumerated types contain no configuration-change record for prices, taxes, discounts, promotions or user permissions -- the audit stops at menu/product/store operations -- and no article asserts the log is immutable or states a retention period. The only other reference to change forensics is indirect: 'Examining Deliverect's activity logs can help identify who initiated the closure' (article on unexpected store closures). https://help.deliverect.com/en/articles/7979010-view-operation-reports · retrieved 2026-08-09

multi-location-enterprise-sso differentiator

'Log in to Deliverect' states: 'To verify your identity, you can use: An email address and password / A Google account', and the troubleshooting article adds 'Use the same login method that you used to sign up (email and password or Google)' and describes Google Workspace account-linking behaviour (7978940). So an operator whose IdP is Google Workspace does get federated sign-in. Shortfalls: no SAML or bring-your-own-OIDC configuration exists in the 983-article English help centre (zero hits for SAML, OIDC, SSO or 'single sign-on'), so any other IdP falls back to passwords; and there is no SCIM or automated deprovisioning -- users are removed by hand ('Deactivate users', 'Remove users', articles 7979094 and 9423492). The separate enterprise.deliverect.com portal is named in 7978937 but its authentication is undocumented, so an enterprise-only SSO path cannot be excluded. https://help.deliverect.com/en/articles/7978937-log-in-to-deliverect · retrieved 2026-08-09

multi-location-enterprise-api differentiator

Partner accounts hold one credential pair that accesses customer accounts across locations; order, menu and reporting APIs are location-scoped by parameter, not by separate per-location credentials. https://developers.deliverect.com/docs/staging-and-production-environment.md · retrieved 2026-08-01

multi-location-central-labor-policy

No labor module.

extensibility-public-api-docs

developers.deliverect.com is fully readable with no NDA, login or sales call — 145 pages indexed in llms.txt across six API surfaces, plus a public forum and changelog. https://developers.deliverect.com/llms.txt · retrieved 2026-08-01

extensibility-api-access-cost differentiator

Checked on 2026-08-09. deliverect.com/en-us/pricing publishes no tiers or figures at all ('Deliverect offers flexible pricing based on your business's specific needs'), and its only API line is marketing ('we offer fully customizable APIs'). The US Terms of Service (deliverect.com/en-us/terms-of-service) covers subscription and transaction fees but has no API-access fee clause. The help centre's exhaustive Role Permissions article (7979053) shows API credentials are self-serve inside the normal portal -- an Applications permission group with Create/Edit/View/Revoke/Unrevoke 'application keys', plus 'Create account credentials' and 'View account credentials' under Accounts -- which establishes access is not a special contract, but says nothing about price. developers.deliverect.com/llms.txt (84 links, plus byte-identical /v1/ and /v1.0/ aliases) lists no commercial or pricing page; the certification doc says only 'You will receive the certification document when we provide the API keys'. Since Deliverect Plus and Deliverect AI are both documented per-location paid add-ons, silence cannot be read as 'included'.

extensibility-partner-revshare

This claim asks whether the terms are PUBLISHED, not whether a revenue share exists. The help centre's own partner article is 501 bytes and entirely non-commercial: 'Do you want to integrate your solution with Deliverect? If so, visit this page to sign up ... You should receive a response from our team within 14 business days', with benefits listed as 'Reliable and scalable tech', 'Access to our API support team', 'Easily expand to new regions/countries'. The partner landing pages (deliverect.com/en/partner, /en-us/become-a-partner) describe referral and reseller tracks in the same qualitative register -- referrers 'get rewarded', partners gain 'access to discounts' -- with no percentage, referral fee or per-location figure. developers.deliverect.com's certification-process doc states only 'You will receive the certification document when we provide the API keys'. Every commercial term is therefore behind a sign-up form and a sales conversation. https://help.deliverect.com/en/articles/8347495-become-a-partner · retrieved 2026-08-09

extensibility-free-sandbox differentiator

Confirmed and if anything the gating is tighter than described: the certification doc's only statement on credentials is 'You will receive the certification document when we provide the API keys' — it does not even document a request path. Not self-serve. https://developers.deliverect.com/docs/certification-process · retrieved 2026-08-01 adversarially verified

extensibility-oauth-partner-apps

OAuth 2.0 machine-to-machine: client_id/client_secret exchanged at /oauth/token for a short-lived access token with an audience. Scoped, operator-granted, individually revocable permissions are not documented — this reads as partner-level credentials, not per-merchant consent grants. https://developers.deliverect.com/reference/access-token.md · retrieved 2026-08-01

extensibility-webhooks-push

RE-CITED 2026-08-09 off the deleted /docs/register-pos-webhook-url-how-to-register-a-location.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The Commerce API flow diagram survives and enumerates the push contract more completely than the deleted registration how-to did: "POST orderStatusUpdate webhook", "POST courierStatusUpdate webhook (delivery updates)", "POST menuUpdate webhook (menu published)", "POST busyMode webhook (store open/closed)", plus paymentUpdate and checkoutUpdate, and snooze/unsnooze for item availability. Push, not polling, is documented across order, courier, menu, payment and store-state events. The registration mechanics themselves are no longer published on this host, so the yes now rests on the event contract rather than on the setup guide. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/commerce-api-flow-diagram.md · retrieved 2026-08-09

extensibility-webhook-reliability differentiator

HMAC signing is documented in both directions (validating orders received, and validating requests from Deliverect), and a POS Order Webhook Failover Flow is published. Specific retry/backoff numbers and a replayable missed-delivery event log were not found. https://developers.deliverect.com/page/pos-order-webhook-failover-flow.md · retrieved 2026-08-01

extensibility-order-injection-api

RE-CITED 2026-08-09 off the deleted /docs/how-to-create-orders.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. Injection survives as an explicit step in the flow: the platform POSTs to /v2/checkouts and "Deliverect->>POS: Inject order into POS", followed by "POST checkoutUpdate webhook (status=completed / failed)" with the instruction to treat the order as successful only on "status": "completed". So an externally originated order reaching the POS as a first-class ticket, with a terminal success signal, is documented. The eat-in-with-table-number detail from the old note lived on the deleted page; Eat-in Orders remains live at /page/eat-in-orders.md. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/commerce-api-flow-diagram.md · retrieved 2026-08-09

extensibility-menu-write-api differentiator

RE-CITED 2026-08-09 off the deleted /docs/create-a-menu.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The write surface survives as a full field glossary -- menus, categories with sorting via subProducts, products, modifiers, images, prices via priceLevels, availability, and nutritional fields including items.`nutritionalInfo` -- and the publish event is documented on the flow diagram as "POST menuUpdate webhook (menu published)". So menu authorship by API is still evidenced. Noting the corpus damage honestly: this page links to at least two deleted guides (product sorting, nutritional supplemental info), so the field list survives while its worked examples do not. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/menu-glossary.md · retrieved 2026-08-09

extensibility-data-symmetry differentiator

Orders, menu, products, availability, stores, opening hours, inventory and dispatch jobs are all read/write. Customers are thin, and employees/labor do not exist as objects at all. https://developers.deliverect.com/llms.txt · retrieved 2026-08-01

extensibility-published-rate-limits

Legitimate 'no' because the cell scores whether limits are PUBLISHED, which is directly observable. I searched the full 145-page index at llms.txt: zero pages match 'rate limit'. Confirmed. https://developers.deliverect.com/llms.txt · retrieved 2026-08-01 adversarially verified

extensibility-doordash-preferred differentiator

Membership is real and I confirmed it independently: DoorDash's 18 May 2026 announcement names Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper (Deliverect for the second consecutive year). Two corrections: (a) the cited URL now 301s and then 404s — replace with the about.doordash.com newsroom URL; (b) the dossier's claim that DPIP 'requires an order-ready signal' is NOT in the announcement. Stated requirements are real-time item availability, integrated reporting, detailed error reporting and promotion visibility, with thresholds undisclosed. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

extensibility-first-party-delivery-integrations differentiator

Deliverect IS the certified middleware — it holds the direct DoorDash, Uber Eats and Grubhub integrations itself rather than reselling another aggregator's. CITATION QUARANTINED 2026-08-09: https://developers.deliverect.com/docs/building-a-channel-integration-overview.md is DELETED (404 at the ~237KB ReadMe shell) and NO REPLACEMENT WAS LOCATED. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. Searched and came up empty: /docs/ and root .md routes, the /v1.1/ version prefix, all 64 live /page/ documents (369,527 chars), the 7 live /reference/ pages, and the 983-article English help centre. The surviving channel documentation is /page/channel-flow.md, which is a sequence diagram and does NOT carry the claim that Deliverect holds the direct DoorDash, Uber Eats and Grubhub connections itself. Re-pointing there would have been slug-similarity re-homing of exactly the kind that has produced two near-misses on this atlas. The verdict and its reasoning are KEPT -- the page was read and quoted on the date recorded -- but the URL is moved to dead_url and stamped do-not-refetch, because a live URL is an instruction to future tooling. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/docs/building-a-channel-integration-overview.md · retrieved 2026-08-01 · not refetchable · page gone · graded B when read

extensibility-middleware-compatibility

Inverted for this vendor: Deliverect is the aggregation middleware and POS vendors integrate to it. It is not itself an endpoint on Chowly/Otter/Checkmate.

extensibility-accounting-connectors

No accounting or GL connector is documented: 'QuickBooks', 'Xero', 'Sage Intacct', 'NetSuite', 'MYOB', 'DATEV' and 'accounting' all return zero hits across the 983 dumped English help-centre articles, the integrations directory's categories are POS, 3P Marketplace, Online ordering, On-Site Ordering, 3P Dispatch and Loyalty & CRM with no finance category, and financial data leaves Deliverect as CSV order and payout exports rather than mapped journal entries. That is not enough for a 'no'. Deliverect advertises '1000+ Integrations' while the help centre publishes 292 per-partner Integration Overview articles, and the incompleteness is demonstrable: the ConverseNow (2026-04-16) and SoundHound AI (2026-07-23) partnerships have no article and are absent from the directory. A partner catalogue that omits announced partners cannot be read as an exhaustive enumeration, which is the point the earlier adversarial pass made and which still stands.

extensibility-payroll-export

No labor hours exist in the platform to export.

extensibility-bi-data-warehouse differentiator

RE-CITED 2026-08-09 off the deleted /docs/reporting-endpoints.md, deliberately onto the same evidence as reporting-raw-warehouse-export so that one fact does not yield two answers. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. "Deliverect does not have a Reporting API, however you will be able to collect order data using our Reporting Endpoint feature." Reporting webhooks push transaction-level data to a customer endpoint; no scheduled bulk export to a warehouse is documented. Partial stands. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/page/faq.md · retrieved 2026-08-09

extensibility-app-marketplace

The 1000+ headline and the categories are confirmed (POS, 3P Marketplace, Online ordering, On-Site Ordering, 3P Dispatch, Loyalty & CRM). But this is a partner DIRECTORY, not an app marketplace: no self-install flow, no operator-side enable/disable, and the page's own call to action is 'Request a New Integration'. An app marketplace the operator cannot install from is a partial at best. Note also the dossier lists a 'Retail' category that did not appear in my fetch. https://www.deliverect.com/en-us/integrations · retrieved 2026-08-01 adversarially verified

extensibility-custom-fields-scripting

A product 'metaData' attribute and custom tags allow operator-defined data on POS objects. No vendor-hosted custom logic or scripting. https://developers.deliverect.com/changelog/product-metadata-attribute.md · retrieved 2026-08-01

extensibility-headless-embedded

I could not resolve the cited page or any Commerce API page at three URL variants — all 404. The only verification available is that llms.txt indexes the titles 'Commerce API - Flow Diagram', 'Commerce Checkout - Glossary', 'How to Request a Payment' and 'How to Checkout a Basket'. Index titles establish that a basket/payment/checkout API exists; they do not establish that a third party can drive the full transaction engine, nor whether access is partner-gated. Downgrade until a page body is actually read. https://developers.deliverect.com/llms.txt · retrieved 2026-08-01 adversarially verified

extensibility-api-versioning-deprecation

Verbatim confirmed: 'Deprecated API elements are maintained for at least three months after the announcement on the Deliverect Developer Hub', with expected retirement dates and migration paths. Two caveats the dossier omitted and should carry: beta features are explicitly exempt and may change at any time, and Deliverect reserves the right to break backward compatibility for security reasons or when the policy 'impedes the development of an API'. The three-month floor is therefore softer than presented. https://developers.deliverect.com/docs/deprecation-policy · retrieved 2026-08-01 adversarially verified

extensibility-data-portability-exit differentiator

On-demand exports are real and documented while the subscription is live: orders to CSV with a field picker and format choice (7979015), menu-item sales with grouping by day/week/all (7978954), analytics (7978952), products and menus (7979008), Direct Suite customers (15223), locations (30494), devices (7979054) and Deliverect Pay payouts (30523), each requested then downloaded from the Operation reports page; APIs and reporting endpoints cover the same ground programmatically. Shortfall: nothing survives termination. The US Terms of Service says the customer 'will lose access to the data, information, and content associated with such subscription' and that the 'right to access and use the Deliverect Services shall immediately cease', with no export period, no retrieval window and no documented post-termination format. No article on help.deliverect.com describes an exit export, and the cancellation article (7978942) covers notice periods and billing only. https://www.deliverect.com/en-us/terms-of-service · retrieved 2026-08-09

reliability-offline-order-entry

Held to the highest bar. Zero pages in the doc index match 'offline'. No offline capability is documented for any surface, and the architecture (webhook/HTTP order delivery) makes it structurally absent. Sustained across the whole offline block. https://developers.deliverect.com/llms.txt · retrieved 2026-08-01 adversarially verified

reliability-offline-card-auth differentiator

Migrated from the 2026-08-01 research pass; no source URL was recorded.

reliability-offline-decline-liability differentiator

Deliverect is cloud-only with no offline capability anywhere in the product (settled: reliability-offline-order-entry: no, reliability-offline-card-auth: no). Offline payment scenarios do not apply; there is no offline-decline liability to document.

reliability-lan-degraded-multi-terminal differentiator

No LAN topology; every path is cloud HTTP/webhook.

reliability-local-transaction-engine differentiator

No edge server or on-premise engine documented. Buffer Orders holds orders in Deliverect's cloud, not locally.

reliability-offline-kds-printing

Deliverect does ship a KDS (help-centre collection of 14 articles: a browser/iPad web app requiring a cloud account, with a LAN receipt printer configured by IP per screen profile — articles 9527403 and 7979527), but no offline mode is documented for it or any other surface: zero pages match 'offline' in the 144-page developer index, the KDS articles document no offline behaviour, and orders reach the kitchen screen only via the cloud platform. The settled reliability-offline-order-entry: no (pure cloud middleware) makes continue-while-offline routing structurally absent — with connectivity down, no orders can arrive to display or print. https://developers.deliverect.com/llms.txt · retrieved 2026-08-04

reliability-printer-fallback

Printing in Deliverect is the Delivery Manager App's. Setting up a printer is discover-add-configure, and the configure step's whole option set is 'print bag or kitchen tickets by enabling them via the toggles ... adjust the number of tickets to be printed and the font size ... Print test tickets ... an option to disconnect the printer' (7979068). Workstation creation likewise enumerates Station name, Station type (Items or Brands), Print kitchen tickets, Print bag tickets, 'Assign printers: Choose the printer to use' -- singular, with no alternate or fallback (7979091). The tablet-profile Printing section (7979054) lists automatic printing, print trigger, ticket counts, fonts, logos and QR codes, again with no failover. Nor is there an alarm: the create-alert screen's topic list is Order cancelled, Order injection failed, Menu publish failed, Item snoozed, Store closed by channel, Store closed by user, Order delayed (7979009) -- no printer or device offline topic. Failover in Deliverect exists only for order delivery to the POS endpoint (developers.deliverect.com POS Order Webhook Failover Flow), and where the POS owns printing Deliverect defers to it entirely ('The management of receipts and printing must be done on Epos Now', 7979145). https://help.deliverect.com/en/articles/7979068-dma-set-up-a-printer · retrieved 2026-08-09

reliability-sync-conflict-handling

Publication-observable claim — the cell scores whether conflict-resolution behaviour is DOCUMENTED. Zero pages match 'conflict' in the 144-page developer index, and the help centre documents no partition or concurrent-edit semantics (closest is 'Reporting Differences Between Your POS, Channel, and Deliverect', article 9104394, a reconciliation explainer, not a concurrency policy). With no offline editing on any surface (settled offline block: no), the vendor documents no partition-edit scenario and no resolution behaviour. https://developers.deliverect.com/llms.txt · retrieved 2026-08-04

reliability-offline-feature-matrix

No offline feature matrix is published because there is no offline mode.

reliability-public-status-page

Verified exactly: all 13 named components present, 90-day uptime shown for 12 of them at 100.0% (DoorDash Orders shows no percentage). Worth adding one skeptical note the dossier missed — the incident history shows 'No incidents reported' for every date in the visible window while 12 components sit at a flat 100.0%, which is unusually clean and suggests conservative incident declaration rather than perfect uptime. https://status.deliverect.com/ · retrieved 2026-08-01 adversarially verified

reliability-contractual-uptime-sla differentiator

The US Terms of Service states: 'Deliverect will make commercially reasonable efforts to make Deliverect Services available in accordance with Deliverect's current service-level agreements, which may be shared upon request or accessed online if that option is made available by Deliverect', and adds that Deliverect 'reserves the right to modify the scope of its service-level agreements at any time and for any reason'. No uptime percentage and no service credit, refund or remedy appears in the standard agreement. status.deliverect.com (fetched 2026-08-09) shows 100.0% uptime over 90 days per component with no SLA statement -- observed performance, not a commitment. The only percentage Deliverect publishes is marketing: '99.998% store uptime' on the pricing page, with no remedy attached. So the standard agreement contains no stated percentage and no credit remedy, and the SLA document itself is not published. https://www.deliverect.com/en-us/terms-of-service · retrieved 2026-08-09

reliability-incident-postmortems

Re-checked 2026-08-09. status.deliverect.com reports '100.0 % uptime' over the trailing 90 days for every component (API, Manager App, Management Portal, Click & Collect and the integration services) and 'No incidents reported' for each day from 2026-07-26 to 2026-08-09; status.deliverect.com/history renders the same incident feed with no entries, offering only Atom/RSS subscription. The page publishes no postmortem template, no severity policy and no root-cause section. The 983-article English help centre contains no incident-communication or outage-report article, and the US Terms of Service says nothing about incident disclosure. With zero incidents on the record there is nothing to judge, so this is neither evidence that postmortems are published nor evidence that they are withheld.

reliability-247-live-support

'Contact Us' (7978926): 'our support team is here to help ... We are available 24/7.' The primary route is in-product chat -- 'Our technical support team typically responds to live chats within a few minutes' and 'our agents can initiate voice calling or screen sharing' -- reachable from the web portal and from the Delivery Manager App, plus four regional WhatsApp numbers (Asia/Oceania +61 481 606 504, EMEA/North Africa +44 7401 275062, North America +1 646 933 0428, LATAM +52 55 9225 2033), gated on the number being listed on the account. Shortfalls: no inbound support telephone number is published anywhere -- voice is agent-initiated out of a chat, and WhatsApp is messaging; and inclusion in the base subscription is not established, because Deliverect sells a separate 'Support as a Service' subscription with non-refundable Support Fees applied at account level (deliverect.com/en/support-as-service-terms-and-conditions), while the Terms of Service reserve the right to 'suspend the provision of technical and operational support, or to change the scope of support services'. No response-time SLA is published. https://help.deliverect.com/en/articles/7978926-contact-us · retrieved 2026-08-09

reliability-onsite-install differentiator

Checked the whole documented onboarding path on 2026-08-09 and it is remote end to end: 'Get Started 1' (8447408) is a five-step self-serve sequence -- ready your POS, complete the sign-up wizard, sync or create products, create or import a menu, set opening hours; 'DMA: App Requirements and Installation' (7979065) is a tablet app download with a supported Star/Epson printer list and network troubleshooting; 'DMA: Set Up a Printer' (7979068) is done by the operator. Adding a location or brand routes to a form and a callback ('a Deliverect representative can contact you', 7978962; 'A representative from Deliverect will be in touch with you typically within three days', 7978963), and several partner integrations are configured by Deliverect support remotely (e.g. Uber Direct, 15551034). No on-site installation, go-live visit, field-service or certified-installer programme is named in the 983-article English help centre, on deliverect.com/en-us/pricing, or in the Terms of Service, and the paid 'Support as a Service' terms do not describe its channels. Deliverect is also sold through POS and channel partners who may install on site under their own contracts, which is not documented either way -- so neither a yes nor an affirmative no is supportable.

reliability-menu-build-service differentiator

Deliverect AI's Smart Assistant Agent performs bulk menu content work (harmonising images, standardising descriptions, applying allergen tags at scale) — closest available, but not a documented onboarding menu-build service. https://www.deliverect.com/en-us/deliverect-ai · retrieved 2026-08-01

reliability-hardware-replacement-sla

No first-party hardware.

reliability-backup-restore

Deliverect documents an operator-triggered backup and restore of the product catalogue in those exact terms: the Bulk Edit Products workflow has the operator request a CSV export (Products > Export > Request export, then Get download link / Download CSV from Operation reports) and states 'We highly recommend creating an un-edited backup, which will allow you to restore the original values of your products if necessary', with steps 10-13 documenting the Import CSV path that writes the values back. Object-level reversion also exists ('Revert all product changes', 7978989). Named shortfall: it covers products only and depends on the operator storing the file themselves - there is no platform-side snapshot or point-in-time recovery (Role Permissions, which states 'you can find every permission you can activate for a user role', has no backup, restore or snapshot permission), deleted menus cannot be restored at all (7978997), force sync is 'irreversible', and no RPO or RTO figure is published: deliverect.com/en-us/security names 'High availability and disaster recovery capabilities' without any recovery point or recovery time objective. https://help.deliverect.com/en/articles/7979048-bulk-edit-products · retrieved 2026-08-09

reliability-pci-dss-4-attestation

Re-checked 2026-08-09. deliverect.com/en-us/security enumerates what Deliverect discloses -- data encryption, authentication and authorization, high availability and disaster recovery, vulnerability detection and remediation, firewalls and IDS, GDPR and privacy compliance, and alignment with NIST SP 800-218 (SSDF) -- and names no PCI DSS, SOC 2 or ISO 27001 status, directing further questions to security@deliverect.com. A grep of all 983 dumped English help-centre articles returns no PCI DSS reference. No AoC, ROC, P2PE listing or compliance portal is linked from deliverect.com, help.deliverect.com or developers.deliverect.com. The tension noted by the earlier pass stands: card capture on Direct and Kiosk runs through Adyen (Deliverect Pay 'powered by Adyen'), so PCI scope is plausibly largely inherited, and developers.deliverect.com documents a payment-token flow rather than raw PAN handling -- which would explain non-publication without implying non-compliance. Not scored 'no' because a prior verification pass reached the same wall and because Deliverect may hold an attestation it shares only under NDA.

reliability-mfa-role-based-access

RBAC is fully met: 'In this article, you can find every permission you can activate for a user role' introduces ~150 discrete permissions across 27 groups, roles are user-authored (9420014 Create or Edit User Roles; 31211 Default Roles), permission grants are bounded by the granter ('You can not activate permissions that you do not have yourself'), access can be scoped per location ('Manage locations: Allows modifying the allowed locations of other users' plus the per-user 'Restrict to locations' toggle, 7979005), and sensitive actions are separable -- Deliverect Pay refunds can be limited to named roles (31165). Shortfall: MFA. 'Log in to Deliverect' (7978937) enumerates identity verification as 'An email address and password' or 'A Google account'; the password article documents only reset and lockout after repeated failures (7978939). The strings MFA, 2FA, two-factor, multi-factor and authenticator appear nowhere in the 983-article English help centre, no MFA-enforcement setting appears in the permission list or account settings articles, and deliverect.com/en-us/security names 'authentication and authorization' without any second-factor claim. So a second factor is only available to operators who sign in through Google, and cannot be enforced by Deliverect for password accounts. https://help.deliverect.com/en/articles/7979053-role-permissions · retrieved 2026-08-09

reliability-self-serve-training

RE-CITED 2026-08-09 off the deleted /docs/how-do-i-make-test-orders.md. Measured 2026-08-09 with a known-good control (/docs/staging-and-production-environment.md, 200/2445b) and a fabricated control (404 at the ~237KB ReadMe shell), on a prober that retries 429 rather than scoring it. The practice surface survives across live pages: a staging environment provisioned with both a Partner and a Customer account, where the customer account is "Used to test Deliverect functionality. Such as creating test orders and publishing menus"; the Delivery Manager App install guide, whose stated purpose is that channel partners "can test updating order statuses" and dispatch partners "can test the delivery job order flow"; and the order payload's own `testOrder` flag, "only applicable as '`true`' in staging environment via menu preview orders". The "Dummy POS" named in the old note appears nowhere in the live corpus and is withdrawn. Partial stands: this is integrator tooling, not a staff-facing video/LMS library or a terminal training mode. PORTAL CONTEXT: developers.deliverect.com deleted its /docs/ how-to tier in a restructure. The surviving pages still LINK to the deleted articles, the site nav links to five slugs that 404, and llms.txt publishes 64 custom-page URLs without their /page/ route prefix so that every one of them 404s as published. The content on /page/ is alive; the vendor index is malformed. https://developers.deliverect.com/docs/staging-and-production-environment.md · retrieved 2026-08-09

reliability-failover-terminal-role differentiator

No terminal topology exists.

reliability-cellular-backup

No vendor-supplied connectivity failover; devices are the operator's own.

commercial-month-to-month-contract differentiator

General Terms cl.13: 'Deliverect offers subscription periods of 30 days, 90 days, 6 months, or 12 months ("Subscription Period"). Longer Subscription Periods may apply for Deliverect Kiosks.' A 30-day period is therefore publicly offered, and the longest period in the published set is 12 months - the terms contain no multi-year minimum and the words 'liquidated damages' and 'early termination' do not appear in the document. Caveats: the kiosk carve-out is the one place a longer term is contemplated, and which period a given customer gets is set in the quote (pricing remains quote-only), so this establishes that month-to-month is on offer, not that it is the default. https://www.deliverect.com/en-us/terms-of-service · retrieved 2026-08-09

commercial-no-early-termination-fee differentiator

The whole General Terms document was fetched and searched: 'liquidated damages' and 'early termination' return zero hits, and cl.40 bounds the exit cost - on termination 'Customer shall immediately pay all outstanding and undisputed fees due up to the effective date of termination', with no acceleration of the remaining Subscription Period. Named shortfall: cl.40 gives the CUSTOMER a termination right only for cause (material breach, insolvency, fraudulent or unlawful activity) while reserving termination 'for convenience' to Deliverect alone; the customer's ordinary exit is the cl.13 notice route (15/30/90 days before the end of the Subscription Period), and cl.8 states fees are non-refundable. So there is no penalty for leaving at the term boundary and no ETF anywhere in the contract, but no published right to cancel early either. https://www.deliverect.com/en-us/terms-of-service · retrieved 2026-08-09

commercial-autorenew-terms-published

General Terms cl.13: 'The Subscription Period shall automatically renew for an additional Subscription Periods of the same length, unless Customer provides notice to Deliverect ... as follows: (i) 15 days notice if the Subscription Period is 30 or 90 days; (ii) 30 days notice if the Subscription Period is 6 months, and; (iii) 90 days notice if the Subscription Period is 12 months.' The same windows are restated in the public help centre (help.deliverect.com/en/articles/7978942-cancel-a-subscription: 'Notice periods are: 15 days for subscriptions with a renewal period of 1 month. 30 days ... 6 months. 90 days ... 12 months'), so both the renewal term and the cancellation notice window are published rather than confined to a signed quote. https://www.deliverect.com/en-us/terms-of-service · retrieved 2026-08-09

commercial-processing-not-bundled differentiator

'Deliverect Pay: Configure a Payment Gateway' has the operator add a gateway and link stores to it; separate articles walk through supplying the operator's OWN credentials for Mollie ('Copy the Live API key' from the Mollie dashboard, art. 7979305), Stripe ('Copy the Secret key' from the Stripe dashboard, art. 7979306), Adyen (art. 14321835), Paymob and Airwallex, plus offline gateways (cash, card, invoice) needing no verification. The General Terms, Direct supplemental cl.2, confirm the boundary: payments are 'provided by third party payment processors integrated with Deliverect', and 'Deliverect may offer a functionality - subject to additional fees - that allows the Customer to use its current payment processor'. Deliverect is not the acquirer and there is no in-house processing lock; the practical limit is that a processor outside the integrated set is a paid-for option rather than a standard connector. https://help.deliverect.com/en/articles/7979307-deliverect-pay-configure-a-payment-gateway · retrieved 2026-08-09

commercial-interchange-plus-published differentiator

No processing rate of any structure is published - neither blended/flat card-present rates nor an interchange-plus option with a stated bps + per-transaction markup. The page's entire cost content is 'Deliverect offers flexible pricing based on your business's specific needs' plus 'CUSTOMIZED PRICING FOR ENTERPRISES / Get a personalized quote'. Zero currency or bps figures in the page source. https://www.deliverect.com/en/pricing · retrieved 2026-08-08

commercial-rate-increase-clause differentiator

General Terms cl.14 'Changes to the Fees': 'Deliverect reserves the right to increase the fees and/or change the fee structure by providing thirty (30) days' notice to Customer. Continued use ... will be interpreted and construed as Customer's express acceptance of the updated fees. Customer's sole recourse if Customer does not agree with the updated fees is to terminate these Terms and cease using the Deliverect Services.' So an exit right on any increase is granted and 30 days' notice is guaranteed. Named shortfalls: there is no cap, no index and no carve-out limiting increases to pass-through costs ('indexation' returns zero hits); the exit is not stated to be penalty-free - fees are non-refundable and cl.14 does not waive the cl.13 15/30/90-day notice windows or the current Subscription Period. Separately, card processing rates are set by the third-party Payment Processor under the customer's own contract with it (Direct supplemental cl.2-3), not by this document, so no processing rate-escalation term is published at all. https://www.deliverect.com/en-us/terms-of-service · retrieved 2026-08-09

commercial-pricing-published

Explicitly quote-only. Verbatim from the FAQ block 'How much does Deliverect cost?': 'Deliverect offers flexible pricing based on your business's specific needs. Factors like your location, the scale of your digital operations, number of locations, and the Deliverect solution you choose (Restaurants, Retail, Direct, or Dispatch) all influence the cost.' followed by 'Book a 1-on-1 with our team to discuss pricing'. No per-location or per-terminal software figure is published. https://www.deliverect.com/en/pricing · retrieved 2026-08-08

commercial-module-unbundling differentiator

Products are distinct SKUs (Restaurants, Direct, Catering, Kiosk, Dispatch, Sentinel, Reclaim, Quest) and Deliverect Plus is stated to be 'An Add-on'. Whether each can be cancelled independently without repricing the base is not published. https://www.deliverect.com/en-us/deliverect-plus · retrieved 2026-08-01

commercial-hardware-purchase-outright

'DMA: App Requirements and Installation' says verbatim 'Deliverect does not provide any hardware', then lists what the operator must supply: iPads (5th gen or higher, iPad Pro, iPad Air 2nd gen+, iPad Mini 4th gen+) or iPhones on iOS 15+, or Android 9+ devices, plus named Star (TSP100III/TSP143III family) and Epson (TM-m30II/III, TM-m50, TM-P20/P20II/P60II/P80) printers. 'Deliverect KDS: Supported Hardware' (art. 7979532) likewise says the KDS screen is 'any device that has a web browser' and lists supported Epson and Star models. All of it is third-party retail hardware the operator buys outright; there is no Deliverect terminal SKU, hardware bundle, lease or rental in the software product. The one lease that exists in the General Terms is a French-market Financial Lease Agreement for the Deliverect KIOSK terminal only - explicitly optional, 'exclusively available for Customer that are located in France', and with a purchase option at expiry - and kiosks are outside the required hardware for order/menu management. https://help.deliverect.com/en/articles/7979065-dma-app-requirements-and-installation · retrieved 2026-08-09

commercial-hardware-not-locked differentiator

Runs on commodity tablets and 'any mobile device, including Zebra scanners, with no special hardware needed'; the Kiosk works with external payment devices and optional standard printers. https://www.deliverect.com/en-us/quest-app · retrieved 2026-08-01

commercial-implementation-fee-published

No implementation, onboarding, menu-build or training fee is published as an amount, and there is no statement that any of them is $0. The pricing FAQ addresses setup only qualitatively - 'Once you sign up, our expert team will be ready to guide you through setup. We offer personalized onboarding' - with no figure attached and no 'included' or 'free' wording, while cost overall is directed to a personalized quote. https://www.deliverect.com/en/pricing · retrieved 2026-08-08

commercial-data-export-self-serve

Reporting webhooks and the order/menu APIs give machine-readable transaction access — but API credentials are issued through Deliverect's API team and a certification process, so it is not operator self-serve without vendor contact. https://developers.deliverect.com/docs/certification-process.md · retrieved 2026-08-01

commercial-export-customer-and-loyalty differentiator

Guest records: documented. 'To create a CSV file of your customers, select the Export customers button. Go to your Operation reports page to download the file' - the table carries contact details, transactions, last-purchase data and order count, plus the marketing-consent flag. Named shortfall: the loyalty half is not covered. Direct Suite loyalty is a stored-credit scheme ('Set how much credit customers receive with each order ... Redeemable (%) ... Maximum redeemable value', art. 8041162) and neither that article nor 'Direct Suite: View Your Customers' (art. 8045310) documents any export of per-customer credit or point balances; gift cards appear in the help centre only as user-permission rows ('Create/Remove/Link/Unlink/View gift card profiles'), with no gift-card article and no liability-balance report. Deliverect Pay payouts have their own export (art. 11515027 'Deliverect Pay: View and Export Payouts'), which is settlement, not liability. https://help.deliverect.com/en/articles/7979317-deliverect-online-ordering-view-and-export-customers · retrieved 2026-08-09

commercial-post-termination-export-window differentiator

'Cancel a Subscription', section 'What happens after cancellation': 'Once your cancellation request is processed, the related services will remain accessible until the end of the billing period. All integrated channels are disconnected after your cancellation request is processed. Download any necessary reports or data from Deliverect before the end of your subscription, as data will be permanently removed.' The General Terms agree twice - cl.13 'If the subscription is terminated, Customer will lose access to the data, information, and content associated with such subscription', and cl.40 'Deliverect shall terminate Customer's access to Customer's Deliverect account, and the data residing therein, and Customer will lose access to all of the data'. So the documented window runs to the end of the paid billing period and there is no post-termination retrieval period; the vendor addresses the question directly and instructs operators to export first. (Narrow exception outside the software subscription: the EU Data Act appendix for Kiosk/Tabesto promises readily-available data on request in a machine-readable format, but it is kiosk product data and states no post-termination window either.) https://help.deliverect.com/en/articles/7978942-cancel-a-subscription · retrieved 2026-08-09

commercial-data-ownership-clause differentiator

Direct's marketing asserts operator guest-data ownership and first-hand data. No published contract clause constraining Deliverect's own use or resale of transaction data was found. https://www.deliverect.com/en-us/deliverect-direct · retrieved 2026-08-01

commercial-source-available-selfhost

Proprietary cloud SaaS. No source availability, no self-hosting option; the only open artefact is the API documentation. https://developers.deliverect.com/ · retrieved 2026-08-01

commercial-pci-p2pe-tokenization

A Deliverect Pay payment-token flow is documented, implying tokenized hosted capture for digital channels. No P2PE validation, no named SAQ type, no card-present scope statement. https://developers.deliverect.com/page/deliverect-pay-payment-token-flow.md · retrieved 2026-08-01

commercial-pci-dss-4-controls

Checked 2026-08-09 across four first-party surfaces. (1) The 984-article English help centre dump of help.deliverect.com: zero substantive hits for 'PCI', and zero for 'two-factor', '2FA', 'multi-factor' or 'MFA' - there is no article on account MFA at all, and the login articles (7978939 password reset, 7978940 resolve login issues) describe only email/password and Google sign-in, with no second factor. (2) www.deliverect.com/en-us/terms-of-service, fetched in full: 'PCI' zero hits. (3) www.deliverect.com/en-us/security, fetched: no PCI, no MFA, one generic mention of encryption. (4) developers.deliverect.com/llms.txt (84 links): no PCI or CDE page. Unresolved rather than negative because Deliverect is not the acquirer - card data for Direct is handled by third-party Payment Processors (Adyen, Stripe, Mollie, Paymob, Airwallex) under the operator's own contract with them, so Deliverect's CDE scope and any v4.0.1 attestation would sit in a trust package obtained under NDA from security@deliverect.com, and the six non-English help-centre locales (4,757 sitemap URLs total, only the 997 English ones dumped) were not searched.

commercial-soc2-attestation

Re-checked 2026-08-09. www.deliverect.com/en-us/security was fetched again and still names GDPR and NIST SP 800-218 (SSDF) only - no SOC 2, no ISO 27001, no trust center, and control detail is routed to security@deliverect.com. Two further surfaces were searched this time and are also silent: the published General Terms at deliverect.com/en-us/terms-of-service (zero hits for 'SOC 2', 'ISO 27' or 'audit report') and the EU Data Processing Terms at deliverect.com/en/dpaeu (zero hits; it commits to 'appropriate technical and organizational measures' and a sub-processor regime without naming a certification). The 984-article English help centre likewise has no security-attestation article. Stays unknown, not no: an attestation is normally disclosed under NDA to prospects rather than published, and the security page explicitly offers that route, so absence from public pages is not evidence the report does not exist. adversarially verified

commercial-privacy-dsar-tooling

DPA half: satisfied. Deliverect publishes Data Processing Terms at www.deliverect.com/en/dpaeu, incorporated by reference in the Direct supplemental terms ('Customer Personal Data will be processed under the Data Processing Terms available at www.deliverect.com/en/dpaeu'), so the operator does not have to negotiate one; it names Deliverect as processor, carries a sub-processor regime, and includes 'Processes to Comply with Rights of Data Subject Rights ... Deliverect shall assist Customer and/or Franchisees by implementing appropriate technical and organizational measures for the fulfillment of Customer's obligations to respond to requests to exercise Data Subject rights'. Tooling half - named shortfall: the in-app surface is locate and export only (Direct Suite / Online Ordering customer list with search, plus the Export customers CSV, art. 7979317). Deletion is not self-serve: 'Anonymize Customer Data' (art. 9595607) reads in its entirety 'Your customers' data can be anonymized in Deliverect. To request this, please reach out to your account manager or our support team and ask them to activate the GDPR setting for your locations.' There is no documented per-guest DSAR workflow and no CCPA/CPRA-specific mechanism; the EU Data Act appendix likewise routes access and erasure requests through the support chat. https://www.deliverect.com/en/dpaeu · retrieved 2026-08-09

commercial-wcag-kiosk-accessibility differentiator

The Kiosk product page makes no accessibility, ADA or WCAG claim, and no VPAT/ACR is published for the kiosk or the consumer ordering surfaces. https://www.deliverect.com/en-us/deliverect-kiosk · retrieved 2026-08-01

commercial-dual-pricing-compliant differentiator

Checked 2026-08-09, and the previous rationale's premise was wrong: what Deliverect calls a 'surcharge' is not a card surcharge. Every 'surcharge' hit in the 984-article English help centre dump is either a meal-deal item upcharge ('If you want some products to cost extra, activate the Surcharge option and set a price'), a POS-side delivery-cost or service-charge mapping (PAR Brink art. 7979244, Revel art. 9739705), or a marketplace fee - and 'cash discount', 'dual pricing' and 'debit card surcharge' return zero hits. What does exist is per-channel price levels (e.g. 'DoorDash: Use Different Prices for Delivery and Pickup', art. 11426942), which is delivery-vs-pickup menu pricing, not a cash-vs-card price pair. The published General Terms (deliverect.com/en-us/terms-of-service) return zero hits for 'dual pric' and 'cash discount'. Unresolved rather than negative: none of these is an exhaustive enumeration of the Direct checkout's fee configuration, card acceptance for Direct sits with third-party Payment Processors (Adyen, Stripe, Mollie, Paymob, Airwallex) whose own rules would govern any surcharge, and the six non-English help locales were not dumped.