Slice / Slice Register

order-capture-floor-plan-editor

Docs define dine-in as counter-service: orders 'placed in-store and consumed in-store' that 'do not require customer information'. No table, section, or floor-plan object appears anywhere in the Register docs. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-01

order-capture-seat-level

The Order Entry article enumerates the whole line-item surface. Adding an item is 'Select the Dining Option / Select a Category / Choose an Item / Select the Item Type / Add Modifiers / Add the Item' - no seat field. After adding, the documented per-line actions are Modify, Item Notes, Line Item Discount, Remove an Item and Adjust Quantity; none assigns a seat. Splitting is payment-side only: 'The Split Payment option lets you accept more than one form of payment for a single order. You can divide the payment evenly, assign custom amounts, or apply a full payment to part of the order', with the three on-screen choices 'Split payment evenly', 'Pay custom amount', 'Pay total owed'. No seat-based split exists. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-08

order-capture-coursing-hold-fire

No coursing, hold, or fire action in Register order entry or order management docs. Counter/delivery product. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-01

order-capture-split-merge

The Register order-entry article (updated February 6, 2026) lists 'Split - Allows splitting checks' among the 'More Order Actions', separately from the 'Splitting a Payment' section that divides a tender. So check splitting exists as a named order action. Shortfalls: the article never states the split granularity (no by-item, by-seat or N-way modes are described), Register has no seat or table model to split by - the dining options are exhaustively 'Dine In, Pickup, Delivery, To Go' - and no merge, combine or recombine action appears anywhere in the Register order-entry, order-management or employee-permission documentation, including the permission list that gates every other order action down to 'Line item clear before send'. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-08

order-capture-bar-tab-preauth differentiator

The Register order-entry article enumerates its payment surface exhaustively - 'There are three ways to pay for an order: Card, Cash, and Other' - and the card flow is only 'Use Card' (customer present) or 'Hand Entry' (over the phone), with the tip taken on the reader at the time of sale. No authorization-and-capture, incremental auth or open-tab flow exists. The dining options are likewise closed - 'Dine In, Pickup, Delivery, To Go' - and the complete 'More Order Actions' list (Add Note, Copy, Split, Discounts, Extra Charge, Hold, Clear Order, Taxes) has no open-tab action; the nearest is 'Hold', which saves an unpaid order to Order Management with no card held against it. End-of-day handling is a cash drawer close-out, not a stale-tab sweep. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-08

order-capture-transfer-audit

Unknown. Re-read the complete Owner's App (web) Register article. Its permission list is genuinely closed as a permission list - "The listed permissions define specific actions employees can be granted access to, categorized under Orders, Shop Operations, Cash Management, Menu Availability, and Shop Availability" - but that is an enumeration of what can be GATED, not of what the Register can DO, and the Order Entry article confirms the gap: "If Employee Permissions are not enabled, all users can access these tools." An ungated transfer would appear nowhere on that list. The supporting points are also weaker than they read: the Financials order tables are worded "Lists all register orders with details such as:", so the absence of an employee column is not a closed schema, and the observation that any logged-in iPad opens the same cloud order list describes cross-device access rather than its absence. Register does appear to have no table model (dining options are Dine In, Pickup, Delivery, To Go), but the claim is conjunctive over servers, tables and devices and cannot be resolved on that alone. adversarially verified

order-capture-native-handheld

Hardware list has no handheld. The mobile device shipped is the NYC1 Mobile Card Reader for door/delivery payment, plus a second iPad (Order Manager Kit) for back of house. https://slice.com/knowledge-hub/order-manager-kit/ · retrieved 2026-08-01

order-capture-offline-order-entry

Still unresolved after pulling Slice's entire first-party documentation set through the open WP REST API on slice.com - all 45 Knowledge Hub articles (wp/v2/epkb_post_type_1), all 30 release notes (epkb_post_type_2) and all 26 FAQs (echo_kb_faq). Not one describes internet-down behaviour. Note the trap: 'offline' occurs 20 times in that corpus and never means disconnected - in Slice's vocabulary 'offline orders' are in-person Register orders as opposed to online ones ('Offline Orders (via Slice Register)' in the Order Activity Report). The only connectivity surfaces published are Register Settings > 'Slice Support: View your Connection Status to confirm your Register is online and connected', a Wi-Fi troubleshooting FAQ, and the onboarding call item 'Review your current POS system, internet setup, and network connection'. The marketing POS page (slice.com/pos) names no offline mode either. Slice publishes no supported/unsupported outage table, so this cannot be resolved either way.

order-capture-qr-same-check differentiator

Slice documents QR codes in exactly one role, and it is not at-table ordering: the online-ordering product page answers 'Can customers order through social media or via QR codes?' with 'you can place ordering links on social pages or QR codes on menus, pizza boxes, or signs' - a link to the shop's Slice online menu. The string 'QR' does not occur once in the 45 Knowledge Hub articles, 30 release notes or 26 FAQs. Orders placed that way arrive as ordinary Slice Online orders: the Register Order Management article shows each landing as a new order requiring confirmation with its own ETA, listed alongside Register orders, never appended to one. There is also no open check to append to - Register's dining options are Dine In, Pickup, Delivery and To Go, with no table or seat model. https://slice.com/knowledge-hub/register-order-management/ · retrieved 2026-08-08

order-capture-kiosk-first-party differentiator

Kiosk appears in neither the 12-product catalog nor the included-hardware list. https://slice.com/pricing · retrieved 2026-08-01

order-capture-drive-thru

No drive-thru functionality in the product catalog or Register docs.

order-capture-drive-thru-timers

No drive-thru product, therefore no segment timers.

order-capture-voice-ai differentiator

Slice Phone is explicitly human agents: 'our trained support team handles order taking', and support is 'No AI, robots, or chat bots — fully human support'. No voice-AI partner API published. https://slice.com/products/phone-ordering/ · retrieved 2026-08-01

order-capture-throttling differentiator

Only manual levers: editable prep-time ETAs in 1- or 5-minute increments and a timed Pause. No automatic capacity limits per slot or load-driven quote extension. https://slice.com/knowledge-hub/register-shop-status/ · retrieved 2026-08-01

order-capture-scheduled-orders

Confirmed: 'Scheduled: Orders set for a future time or date' is a first-class status alongside In Progress and Complete. https://slice.com/knowledge-hub/register-order-management/ · retrieved 2026-08-01 adversarially verified

order-capture-catering

'Catering order support' is claimed on the online-ordering product page. No quote, deposit, balance-due, or event-schedule workflow is documented. https://slice.com/products/online-pizza-ordering-system/ · retrieved 2026-08-01

order-capture-order-ready-signal differentiator

Slice states outright: 'Slice receives the Third-Party orders but does not have a way to communicate back to those providers.' https://slice.com/knowledge-hub/register-third-party-orders/ · retrieved 2026-08-01

order-capture-void-comp-controls

Discounts carry reason codes and permissioned actions require a manager four-digit PIN approval. No exception report and no void documentation; the Employee Permissions Log 'only tracks assigned permissions', not instances. https://slice.com/knowledge-hub/register-employee-permissions/ · retrieved 2026-08-01

menu-pricing-nested-modifiers

Modifier groups with required-selection and maximum-choice rules are documented. Nesting depth is never stated; three-level nesting unverified. https://slice.com/knowledge-hub/owners-app-web-menu/ · retrieved 2026-08-01

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

Confirmed in the menu doc as an explicit three-way toggle per modifier group: 'Modifiers have the same price for all sizes', 'Set different modifier prices for sizes', or 'Modifiers are free for all sizes'. Real per-size modifier pricing, not duplication. https://slice.com/knowledge-hub/owners-app-web-menu/ · retrieved 2026-08-01 adversarially verified

menu-pricing-fractional-placement differentiator

Upheld on a second independent retrieval, this being the conclusion-flipping cell for a pizza record. The order-entry article supports exactly one gesture: 'For pizzas, use Choose Toppings to select half toppings. First, tap the half where you want to add toppings. Then, select the topping.' Halves only — no quarters or thirds, no per-section pricing, and the article carries no pricing statement for half toppings at all. Placement is real; independent per-section pricing is not. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-02 adversarially verified

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

Upheld unknown a second time, now against Slice's complete published menu surface rather than a re-read. Half assignment is captured at order entry - 'For pizzas, use Choose Toppings to select half toppings. First, tap the half where you want to add toppings. Then, select the topping.' The Owner's App (web) Menu article documents the whole configuration side, including the pizza-specific 'Build your own pizza' item type and the modifier-group pricing control, which offers exactly three mutually exclusive modes ('Modifiers have the same price for all sizes', 'Set different modifier prices for sizes', 'Modifiers are free for all sizes' - 'Only one pricing option can be selected'). None of them is a half/fraction rule. I stopped short of `no` because that enumeration is explicitly scoped to pricing ACROSS SIZES, not to fractional placement, so it does not exhaust the pricing surface for a half-and-half pie; nothing states what a half topping costs. Checked the release notes too (the 2026-02-05 'Manage Your Full Menu in One Place' shared-modifier note is the only menu-pricing release note) - no half-pricing rule.

menu-pricing-topping-quantity-tiers

Tap once to add, twice to double, three times to remove. That is a double tier only — no light/extra tiers and no configurable price multiplier per tier. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-01

menu-pricing-size-style-matrix differentiator

Sizes carry prices ('At least one size and price is required') and crust/sauce are modifier groups with per-size modifier pricing — approximates a size x crust grid without being a true two-axis matrix with per-cell override. https://slice.com/knowledge-hub/owners-app-web-menu/ · retrieved 2026-08-01

menu-pricing-included-allowance differentiator

The Owner's App (web) Menu article documents the modifier-group creation screen field by field, and it is the entire configurable surface for how modifiers are charged and chosen: Name, Display name, Size-based pricing (three mutually exclusive modes - same price for all sizes, different prices per size, or free for all sizes; 'Only one pricing option can be selected'), the modifier membership list, and Selection rules, which consist solely of 'Require a selection - Customers must choose at least one modifier before adding the item to the cart' and 'Maximum selections - Set the maximum number of modifiers a customer can select from this group. This limit applies per item and does not vary by size.' A maximum is a cap, not an allowance: there is no free-count field, no overage price, no substitution credit and no per-size allowance. Pricing is all-or-nothing per group, so 'three toppings included, then charge' cannot be expressed. https://slice.com/knowledge-hub/owners-app-web-menu/ · retrieved 2026-08-08

menu-pricing-combos

'Combos' named on the online-ordering marketing page and 'Deals' for item-specific or bundle pricing in the Owner's App. No component-swap price delta or cart auto-detection documented. https://slice.com/knowledge-hub/owners-app-web-marketing/ · retrieved 2026-08-01

menu-pricing-upsell-prompts differentiator

'Built-in upsells' claimed for online ordering. No per-item/per-channel configuration and no attach-rate reporting documented. https://slice.com/products/online-pizza-ordering-system/ · retrieved 2026-08-01

menu-pricing-86-propagation

Re-read against the menu article: Update Stock Availability marks an item unavailable for '12 hours', '24 hours' or 'indefinitely', and a bulk edit can mark many items at once (the earlier note's 48-hour option is not in the documentation). Shortfall: propagation reaches the Register and Slice's own online channels only — Slice states it 'does not have a way to communicate back to' the third-party providers — and no propagation latency is published. https://slice.com/knowledge-hub/owners-app-web-menu/ · retrieved 2026-08-02

menu-pricing-countdown-auto-86 differentiator

Value upheld, enumeration corrected: the stock dropdown offers 12 hours, 24 hours, indefinitely and a Custom user-defined return date, the last of which the previous note omitted while asserting the list was exhaustive. All four are timed or manual windows restored on expiry. No per-item unit count decrements as units sell and nothing 86s an item at zero, so the value stands. https://slice.com/knowledge-hub/owners-app-web-menu/ · retrieved 2026-08-02 adversarially verified

menu-pricing-dayparting

Category management supports day-specific availability. Time-of-day activation and scheduled price changes are not documented. https://slice.com/knowledge-hub/owners-app-web-menu/ · retrieved 2026-08-01

menu-pricing-channel-price-books

Moved up from unknown: a percentage-markup rule per channel is documented after all. The Third-Party Orders article states the operator can 'set fixed percentage upcharges for each third-party platform to help cover their fees' — a rule applied to the base price per marketplace rather than manual per-item entry, which is the mechanism the claim names. Shortfall: it exists only for third-party platforms. No distinct price book for dine-in, pickup, first-party delivery or kiosk is documented; the only other channel control is a pair of availability toggles ('Item available online', 'Item available on Slice Register'). https://slice.com/knowledge-hub/register-third-party-orders/ · retrieved 2026-08-02 adversarially verified

menu-pricing-dual-pricing differentiator

Upheld unknown, with more evidence than the previous pass had but still not the claim. Slice does operate a cash/non-cash price differential: the Register Sales Summary Report defines 'Credit Card Surcharge - A fee charged when a customer pays with a credit or debit card' and 'Cash Discounts - Discounts applied to orders paid in cash', the Owner's App (web) Sales Summary CSV carries 'Credit Card Surcharges' and '# of Credit Card Surcharges Collected' columns, and 'non-cash adjustment fees' appear in the Dining Option and Non-Taxable Sales lines. Every one of those is a tender-time line item. The claim asks for something structurally different - a card price stored as the item's BASE price at item level, shown identically on POS, kiosk and online ordering, and printed on the receipt. The Menu article's item and modifier field lists contain no second price, no cash/card price pair; the Kitchen and Customer Receipt Settings documentation lists only font and content-ordering options, so receipt rendering of the two prices is unstated; and nothing addresses parity with online ordering. Checked Owner's App (web) Settings, Register Settings, Menu and both Sales Summary definitions.

menu-pricing-versioning-effective-dates differentiator

Still unresolved. I read the complete Owner's App (web) Menu article (updated April 9, 2026), the Owner's App Manage > Menu article and the menu FAQs. What is documented is immediate-effect editing: 'Once you save your changes, they will go live instantly' (menu FAQ), bulk price change by flat amount or percentage, bulk printer assignment, bulk out-of-stock with a timed return (12 hours, 24 hours, custom, indefinitely), category availability by day of week, and a 'View Online' link that previews how the CURRENT item looks to customers. There is no staged version, no publish step, no effective-date field on an item or price, and no revision history to roll back to. I stopped short of `no` because the Menu article's opening scope statement ('Here is what you can do') is an overview framing rather than a completeness assertion, and no settings screen enumerates a versioning surface that could be shown to lack these options.

menu-pricing-franchise-hierarchy differentiator

Single-shop product. No corporate template, no location groups, no field-level governance anywhere in the Owner's App documentation.

menu-pricing-allergen-nutrition

The Owner's App (web) Menu article documents the New Item page as a complete field list - 'Here is what you can manage on the New Item page' - and the fields are: Name, Display name, Kitchen name, Category, Description, Photo; then Sizes and pricing; then Options, itself an enumerated toggle set (Loyalty reward, Item available online, Item available on Slice Register, Feature this item as a house favorite, Contains alcohol, Discount ineligible); then Register printing (Customer receipt, Kitchen). The Edit Item screen adds only Stock and Delete. There is no allergen field and no nutrition field, and 'allergen' and 'nutrition' occur zero times across all 45 Knowledge Hub articles, 30 release notes and 26 FAQs. The only allergy handling Slice documents is free text at order entry: 'Item Notes - Use this to enter special requests, allergies, or custom add-ons.' With no stored value there is nothing to publish to online ordering or third-party menus, and Slice has no recipe/component model to derive nutrition from (the record already scopes inventory out). https://slice.com/knowledge-hub/owners-app-web-menu/ · retrieved 2026-08-08

menu-pricing-recipe-linkage differentiator

Slice ships no inventory or recipe product — inventory is absent from the 12-product catalog and from every Knowledge Hub section. https://slice.com/knowledge-hub/ · retrieved 2026-08-01

menu-pricing-3p-menu-push

'Your Slice Menu is your source of truth—third-party menus are controlled by Slice.' But operators are warned 'Do not edit third-party menus directly—this will break the integration', and no per-item sync status or rejection errors are surfaced. https://slice.com/knowledge-hub/register-third-party-orders/ · retrieved 2026-08-01

menu-pricing-dynamic-pricing

One channel dimension is real: the Register Third Party Orders article (updated January 16, 2026) documents 'Pricing Control: You can set fixed percentage upcharges for each third-party platform to help cover their fees', so the price a customer sees varies automatically by channel from a single source menu ('Your Slice Menu is your source of truth - third-party menus are controlled by Slice'). Shortfalls, and they are most of the claim: the variation is a static per-platform percentage, not a rule; nothing varies by time of day or demand; the upcharge applies to the whole platform menu rather than per item; and no floor or ceiling guardrail is configurable or documented. Slice online ordering has only a flat all-menu 'Online Discount' percentage, in the other direction. https://slice.com/knowledge-hub/register-third-party-orders/ · retrieved 2026-08-08

payments-processor-choice differentiator

2.90% + $0.30 Slice processing is the single published rate on both memberships; the payment terminal ships in the Family bundle. No supported third-party processor or gateway list exists. https://slice.com/pricing · retrieved 2026-08-01

payments-published-rates differentiator

A single blended headline rate is published on the pricing page - '2.90% + $0.30 card processing' on both the Family ($399/month + $2.00/order) and Online ($39/month + $3.00/order) columns - but that is a first-party sales page, not documentation. Named shortfalls: no interchange-plus schedule, no card-type, AmEx or keyed/manual-entry differential, and no monthly, PCI, gateway or statement fee disclosed. Slice's own Owner's Portal Help defines Card Present and Card Not Present processing fees as 'any percentage and swipe fees outlined in your agreement for card processing' (https://sites.google.com/slicelife.com/owners-portal-help/home/statement-definitions/slice-payments, retrieved 2026-08-06), i.e. the rate that actually applies is set in the non-public merchant agreement; the Slice Register site quotes no percentage at all and offers a Cash Discount alternative. Searched: slice.com/pricing, slice.com/knowledge-hub help centre (no pricing, fee or billing article exists - it directs financial questions to a phone number), slice.com/terms-of-service, sliceregister.com, and the sites.google.com/slicelife.com Register product help site, whose pages redirect to a Google account login. https://slice.com/pricing/ · retrieved 2026-08-06

payments-dual-pricing differentiator

Moved up from unknown: cash discounting is evidenced downstream even though no setting is documented. The Financials article lists 'Cash Discounts' as an Orders Report column and, in the Sales Summary, as 'Total discounts applied when customers paid with cash', and the Sales Summary's Service Fees section includes 'Credit Card Surcharges'. Shortfall: Register Settings documents no cash-discount or surcharge configuration at all, nothing states that two prices are stored per item, and neither the guest check nor the receipt is documented as printing both cash and card totals. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-02 adversarially verified

payments-surcharge-guardrails differentiator

Surcharging itself is real and reported: the Register Sales Summary Report has a 'Credit Card Surcharge' line under Payments and the Owner's App (web) Sales Summary CSV carries 'Credit Card Surcharges - Total surcharges applied to credit card transactions' and '# of Credit Card Surcharges Collected'. The guardrails the claim asks about are absent, and one is contradicted: Slice's own definition is 'Credit Card Surcharge - A fee charged when a customer pays with a credit OR DEBIT card', which is the opposite of BIN-based debit exclusion. No prepaid exclusion, no network percentage cap, and no per-location enable/disable control appear in the Owner's App (web) Settings page, the Register Settings page or the Register configuration article - and surcharge configuration is not self-service anywhere in the documentation. https://slice.com/knowledge-hub/register-cash-management-and-reporting/ · retrieved 2026-08-08

payments-emv-nfc

Moved up from unknown on evidence no earlier pass cited. The Slice Driver App article documents chip and contactless acceptance in Slice's own words: 'Ask the customer to insert, tap, or swipe their card on the reader', on a reader paired over Bluetooth ('Double-tap the button on the reader's side to confirm the connection'). Shortfall: this covers only the mobile reader used at the door. The countertop Payment Terminal shipped in the Family bundle is never named or described in any Slice document, PIN debit is not mentioned, and Apple Pay / Google Pay acceptance appears only at online checkout, never at a physical reader. https://slice.com/knowledge-hub/register-slice-driver-app/ · retrieved 2026-08-02 adversarially verified

payments-softpos-tap-to-pay differentiator

Mobile acceptance requires the separate NYC1 Mobile Card Reader, which is the documented alternative to phone-native tap. https://slice.com/knowledge-hub/order-manager-kit/ · retrieved 2026-08-01

payments-pay-at-table

Slice's only mobile reader is a Driver App accessory: it pairs over Bluetooth to the driver's own phone (Settings > Card Readers > Pair Reader), requires that 'the driver has an assigned order', and the payment procedure is headed 'here's how to accept a card payment at the door' - tap 'Pay with card reader', customer is prompted to add a tip, then insert/tap/swipe. There is no server handheld: the Register kit is 'iPad, printer, card reader, and cash drawer', and Order Entry states 'Credit card payments and tipping are still completed through the shop's credit card reader' at the counter, with the iPad flipped toward the customer as the customer-facing display. https://slice.com/knowledge-hub/register-slice-driver-app/ · retrieved 2026-08-08

payments-qr-guest-pay differentiator

Unknown. The `no` leaned on Order Entry's "There are three ways to pay for an order: Card, Cash, and Other" as a closure statement. That sentence is a closed list of cashier-driven TENDER TYPES at the Register, and it demonstrably does not bound Slice's guest-side payment surfaces, because Slice operates one outside it: the release note "Let Phone Customers Pay by Text" (February 5, 2026) says customers "receive a text with their order details and a secure link to pay online if they have not paid upfront". A hosted guest pay-link therefore exists and is not enumerated by the cited sentence, so the same sentence cannot exclude a QR-delivered one. Slice publishes no supported/unsupported statement on scanning a printed check, and the SMS link is documented only for Slice Phone orders with nothing said about whether an equivalent is reachable by QR or whether settlement closes the order automatically - so this resolves neither to yes nor to no. adversarially verified

payments-tip-adjust

On-device tip prompt is documented ('the customer will be prompted to add a tip'); order management shows tip-present/absent icons. No pre-auth-then-adjust flow, batch window, or unadjusted-tips manager screen documented. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-01

payments-tip-pooling differentiator

No labor module and no time clock exist, so there is no hours or role basis for pooling. Not present in any documentation. https://slice.com/knowledge-hub/register-employee-permissions/ · retrieved 2026-08-01

payments-offline-store-and-forward differentiator

Still unresolved, and now checked against everything Slice publishes rather than asserted. I pulled all 45 Knowledge Hub articles, all 30 release notes and all 26 FAQs through slice.com/wp-json/wp/v2/ and read every payment-related one: Order Entry (the card flow is Use Card or Hand Entry on the reader), Register Getting Started (Payment Terminal Setup), Register Settings (Payment Terminals - assign a default reader for this iPad, and 'Slice Support: View your Connection Status to confirm your Register is online and connected'), Cash Management and Reporting, and Owner's App (web) Financials. None mentions storing a card transaction locally, forwarding it later, or any offline limit. Beware the vocabulary trap: 'offline' throughout Slice's reporting means an in-person Register order ('Offline Orders (via Slice Register)'), not a disconnected one. The absence of any published outage behaviour is not evidence that store-and-forward is absent.

payments-offline-decline-liability differentiator

Still unresolved. This claim is about disclosure, so I looked for the disclosure itself rather than for the underlying behaviour: nothing in the 45 Knowledge Hub articles, 30 release notes or 26 FAQs retrieved from slice.com/wp-json/wp/v2/ addresses who bears a declined stored transaction. The Owner's App (web) Financials Statement Summary does publish a full liability breakdown for other failure modes - 'Chargebacks: Refunds due to customer disputes through their bank or credit card issuer, including reversed chargebacks', 'Order Issue Reimbursements: Refunds from Slice for order issues for which Slice is responsible', 'Past Due Amount' - which shows Slice does publish loss-allocation language where it has any, and none of it covers offline declines. No post-reconnect failed-payment report exists in the enumerated report set (Order Activity, Orders, Tax, Sales Mix, Sales Summary). Left unknown because no offline capture is documented in the first place.

payments-gift-cards

The Register order-entry article closes its tender set - 'There are three ways to pay for an order: Card, Cash, and Other' - and then tells the operator what to do about gift instruments under the third: 'Other - Used for anything that is not cash or card, e.g., check, PAPER GIFT CERTIFICATE, running your own invoices, etc.' That is Slice documenting the manual workaround in place of the feature: the amount is recorded as an Other tender with no balance held by Slice. Consistent with that, the string 'gift card' occurs zero times across all 45 Knowledge Hub articles, 30 release notes and 26 FAQs, and zero times on the Slice Register marketing page; the Owner's App (web) Financials report columns track Credit Card, Cash, Other, Slice Online payments and discounts (promo codes, loyalty rewards, Slice Credit) with no gift-card liability or balance line anywhere. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-08

payments-house-accounts

Slice documents the workaround instead of the feature. The Register order-entry article closes the tender set at 'Card, Cash, and Other' and defines Other as 'anything that is not cash or card, e.g., check, paper gift certificate, RUNNING YOUR OWN INVOICES, etc.' - the shop keeps the account, Slice records a tender. The one occurrence of the phrase in the corpus confirms the same shape: the Delivery Management Report's driver settlement line reads 'Other: Any payments that do not fall under cash or card (such as house account or Slice Pay)', i.e. house account is a label for an Other-tender payment, not an object Slice maintains. There is no account entity anywhere - no credit limit, no running balance, and no invoice or statement generator for customers; the enumerated Statements/Payouts surface in Owner's App (web) Financials is Slice paying the shop, not the shop billing a customer. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-08

payments-split-tender

Split payments exist — refunds can target 'specific payments' when a payment was split, and checks divide evenly or by custom portions. No documented split cap, no split-by-item or by-seat. https://slice.com/knowledge-hub/register-order-management/ · retrieved 2026-08-01

payments-refund-void-controls

Refunds and discounts are permission-gated with manager four-digit PIN approval. But the Employee Permissions Log 'only tracks assigned permissions' and is explicitly not an activity log — no immutable approver-attributed audit trail is documented. https://slice.com/knowledge-hub/register-employee-permissions/ · retrieved 2026-08-01

payments-chargeback-tooling differentiator

Statement Summary carries a Chargebacks line: 'Refunds due to customer disputes through their bank or credit card issuer, including reversed chargebacks.' No dispute dashboard or evidence-submission workflow documented. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-01

payments-card-on-file differentiator

'Saved payment accounts for repeat customers' on first-party digital ordering. Tokenization, cross-channel reuse at the Register, and no-PAN-stored assurance are not documented. https://slice.com/products/online-pizza-ordering-system/ · retrieved 2026-08-01

payments-payout-timing differentiator

Both halves are published. Schedule: the FAQ 'When and how will I receive my payout?' states 'Payouts are sent via Direct Deposit to your bank account based on your preferred schedule - daily, weekly, bi-weekly, or monthly', changed by calling Slice. Accelerated funding: the Owner's App (web) Financials Payouts table documents a payout 'Method: Indicates the payout method (e.g., INSTANT)', the Statement Summary's bottom line is 'Total: The expected funds paid by Slice to your Debit Card TODAY', and the Owner's App (web) Settings article documents how to switch it on - 'Payout management: This is where you can add a debit card to receive your Slice payouts faster. Adding a debit card is optional, but it is required to receive the fastest possible payouts.' Caveat for the reader: Slice publishes the cadence and the instant option but not a cut-off time or a guaranteed settlement window. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-08

payments-multi-entity-routing differentiator

Still unresolved after checking the surfaces where it would live. Multi-location accounts do exist - Register Getting Started says 'If you have multiple shops, select the location you are in' at login - and the Owner's App (web) Financials Statements/Payouts pages are the settlement surface, listing statement period, payout ID, date created, date paid, amount, method and status with no bank-account or entity column and no per-location split. The Owner's App (web) Settings article documents the whole Payments section and it contains exactly two things: a card for paying Slice for Goods, and 'Payout management' for adding a debit card to speed payouts - no bank account per location. Crucially, the actual bank-account control is not published at all: the FAQ 'How do I add or update my bank account?' answers in full, 'Please call (888) 974-9928 to change your direct deposit settings.' With deposit routing handled off-platform by phone, the documentation cannot show either that multi-entity routing exists or that it does not.

payments-p2pe-pci4

Still unresolved, and the one page that speaks to it is too thin to score. The FAQ 'How secure are payments?' is the whole of Slice's published security posture: 'Slice partners with industry-leading payment processors to ensure all transactions are secure and encrypted. Your payment information is protected and used only for processing orders - it is never shared or stored beyond what is necessary to complete the transaction.' That names neither P2PE nor a validated solution, does not identify the processor, and makes no attestation available. The strings 'PCI' and 'P2PE' occur zero times across the 45 Knowledge Hub articles, 30 release notes and 26 FAQs pulled from slice.com/wp-json/wp/v2/, and there is no trust, security or compliance page in the slice.com page list (wp/v2/pages). Note also that the record's cited developer host does not exist: developers.slicelife.com returns the same consumer storefront shell as any invented *.slicelife.com subdomain, so no technical security documentation is reachable there. Generic 'encrypted' marketing language cannot establish P2PE or a current PCI DSS 4.x AoC.

kitchen-station-routing

Verified and slightly stronger than described — routing targets are named ('kitchen, pizza, bar, etc.') and bulk edit can reassign printers across many items. Still printer-only routing with no KDS, so partial is the right ceiling. https://slice.com/knowledge-hub/owners-app-web-menu/ · retrieved 2026-08-01 adversarially verified

kitchen-expo-consolidation

Corrected 2026-08-08: the previous note's 'No KDS product exists' is withdrawn as stated, because https://slice.com/family-membership/ advertises 'Discounted kitchen displays & kiosks (coming soon)'. An expo screen still cannot exist, because no display device ships: the Slice Register product page answers 'What hardware is included with Slice Register?' with 'an iPad interface, kitchen printer, cash drawer, receipt printer, credit card terminal, router, and delivery card reader', and /pricing's Hardware list adds only a Network Kit and Stand. Kitchen output is print - register-order-management says 'Moving the order will trigger printing from both the customer receipt printer and the kitchen printer' - and printed tickets have no bump state to consolidate across stations. 'expo', 'bump' and 'kitchen display' occur zero times in the 45 Knowledge Hub articles, 30 release notes and 26 FAQs retrieved from the WP REST API on 2026-08-08. https://slice.com/products/point-of-sale-for-pizza-shops/ · retrieved 2026-08-08 adversarially verified

kitchen-course-firing differentiator

Re-evidenced 2026-08-08; the earlier "no coursing anywhere in the documentation" rationale is withdrawn as absence-of-mention. Register > Order Entry (updated February 6, 2026) walks the whole order lifecycle and enumerates the complete item-level action set once an item is on the check - "Modify", "Item Notes", "Line Item Discount", "Remove an Item", "Adjust Quantity" - with no course or seat assignment, and the complete order-level set under More: "Add Note", "Copy", "Split", "Discounts", "Extra Charge", "Hold", "Clear Order", "Taxes". The one hold Slice ships is whole-order and releases on tender, not on demand per course: "Hold - Saves the order in Order Management In Progress. The order will not print to the kitchen until it is paid for or sent." Firing time is likewise whole-order and binary - Owner's App (web) > Register > Printer Settings offers exactly two Print Modes, "Incremental: Prints as items are ordered" and "After Payments: Prints only after full payment has been accepted". There is no expo screen to fire from: Slice ships no KDS ("Discounted kitchen displays & kiosks (coming soon)"). "course", "coursing" and "fire" occur zero times across all 101 first-party articles - 45 Knowledge Hub, 30 release notes, 26 FAQs - re-pulled from slice.com/wp-json/wp/v2/ on 2026-08-08. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-08 adversarially verified

kitchen-prep-time-pacing differentiator

Re-evidenced 2026-08-08 on a field enumeration rather than on silence. Owner's App (web) > Menu (updated April 9, 2026) enumerates every field on the New Item page - Item type ("Build your own pizza" / "Regular menu item"), Item details (Name, Display name, Kitchen name, Category, Description, Photo), modifier groups, "Sizes and pricing", Options (Loyalty reward, Item available online, Item available on Slice Register, house favorite, Contains alcohol, Discount ineligible) and "Register printing" (Customer receipt / Kitchen) - and there is no cook-time or prep-time field anywhere on it. The only prep timing Slice exposes is order-level and manual: Owner's Portal > Time Management > ETA sets shop-wide defaults where "Delivery and pickup ETAs are set separately" and "Manually adjusting the ETA for a specific order in the Register will override the default ETA only for that order", and Register > Settings > Order Settings offers "Custom ETAs for Online Orders: Allows your shop to adjust prep times in one- or five-minute increments when confirming Slice Online Orders. Pickup ETAs must stay between 10 and 90 minutes, and delivery ETAs must stay between 20 and 120 minutes." There is also no display to stagger onto - Slice ships no KDS ("Discounted kitchen displays & kiosks (coming soon)") and kitchen output is a thermal ticket that prints once, in Incremental or After Payments mode. "cook time", "prep time", "stagger" and "pacing" occur zero times across the 101 first-party articles re-pulled from slice.com/wp-json/wp/v2/ on 2026-08-08. https://slice.com/knowledge-hub/owners-app-web-menu/ · retrieved 2026-08-08 adversarially verified

kitchen-order-throttling differentiator

Only manual Pause with a timer and manual ETA editing. No load-triggered automatic pacing. https://slice.com/knowledge-hub/register-shop-status/ · retrieved 2026-08-01

kitchen-channel-pause-propagation differentiator

Explicit: 'Pausing or closing orders affects Slice online orders and Slice Phone orders—third-party orders will not be impacted.' https://slice.com/knowledge-hub/register-shop-status/ · retrieved 2026-08-01

kitchen-order-ready-callback differentiator

Slice 'does not have a way to communicate back to those providers'. No order-ready event reaches DoorDash/Uber Eats. https://slice.com/knowledge-hub/register-third-party-orders/ · retrieved 2026-08-01

kitchen-bump-bar-hardware

Corrected 2026-08-08: the old rationale 'No KDS, therefore no bump bar' rested on a premise that is refuted as stated - Slice does advertise kitchen displays, but as unavailable: the Family Membership benefits list reads 'Discounted kitchen displays & kiosks (coming soon)'. That is a stated limitation, not silence, and it is what carries the no. Consistent with it, the Slice Register product page's included-hardware answer names 'an iPad interface, kitchen printer, cash drawer, receipt printer, credit card terminal, router, and delivery card reader' - no display and no keypad - and 'bump' occurs zero times across the 45 Knowledge Hub articles, 30 release notes and 26 FAQs pulled from the WP REST API on 2026-08-08, so no supported bump-bar models are documented anywhere. Re-check when the 'coming soon' displays ship. https://slice.com/family-membership/ · retrieved 2026-08-08 adversarially verified

kitchen-all-day-counts

Re-evidenced 2026-08-08. The claim is about an all-day view on the station, and no station display ships: Family Membership lists "Discounted kitchen displays & kiosks (coming soon)" and the Slice Register included-hardware answer is a closed list - "iPad interface, kitchen printer, cash drawer, receipt printer, credit card terminal, router, and delivery card reader" - with no display. Station output is a printed ticket per order. On the Register itself, Order Management is enumerated as the "central hub for handling all incoming and active orders" with exactly three status tabs - "Scheduled", "In Progress", "Complete" - and bottom filters "To Go, Delivery, Pickup, Dine In"; every view is order-by-order, none aggregates outstanding quantities per item or per modifier. "all day" and "all-day" occur zero times across the 45 Knowledge Hub articles retrieved from the WP REST API on 2026-08-08. https://slice.com/knowledge-hub/register-order-management/ · retrieved 2026-08-08 adversarially verified

kitchen-sla-alerts

Re-evidenced 2026-08-08. The entire per-station configuration surface is enumerated in Owner's App (web) > Register > Printer Settings - "Create New Setting: Add a new printer setting to direct menu items to specific prep stations", with fields "Name", "Print Modes" (Incremental / After Payments) and "Print Quantity" - and it holds no target time, no colour escalation and no audible alert. The station-display alternative is closed by Slice's own wording: Family Membership lists "Discounted kitchen displays & kiosks (coming soon)", i.e. not available, and the Register included-hardware answer names no display. "cook time" occurs zero times across the 45 Knowledge Hub articles pulled from the WP REST API on 2026-08-08. The only alerting Slice documents is on intake (scheduled-order banners at two hours and one hour, New Order Alert Sound in Register Settings), which is not per-station cook-time escalation. https://slice.com/knowledge-hub/owners-app-web-register/ · retrieved 2026-08-08 adversarially verified

kitchen-printer-fallback differentiator

Re-evidenced 2026-08-08. Register Settings > Receipt Settings enumerates the whole printer surface - "Receipt Printers: Discover, install, rename, delete, and test receipt printers" - and Owner's App (web) > Register > Printer Settings offers only "Create New Setting" with "Name", "Print Modes" and "Print Quantity". No device is designated as a backup and no automatic re-route exists; the documented remedy for a printer that does not produce a ticket is manual - check paper, re-select the Epson TM-m30III, print a test page - plus Order Management's manual reprint of an In Progress order. The screen half of the claim is closed by Slice's own statement that displays are not available: Family Membership lists "Discounted kitchen displays & kiosks (coming soon)", and the Register included-hardware answer names no display. "backup printer", "failover" and "fail over" occur zero times across the 45 Knowledge Hub articles retrieved from the WP REST API on 2026-08-08. https://slice.com/knowledge-hub/register-settings/ · retrieved 2026-08-08 adversarially verified

kitchen-offline-operation differentiator

Re-evidenced 2026-08-08. The prior `unknown` rested on treating KDS existence as unsettled; it is settled in the other direction. Slice's own Family Membership benefits list reads "Discounted kitchen displays & kiosks (coming soon)" - a vendor statement that the surface is not available yet - and the Slice Register product page answers "What hardware is included with Slice Register?" with a closed list: "iPad interface, kitchen printer, cash drawer, receipt printer, credit card terminal, router, and delivery card reader". No display device ships, so no KDS can continue to receive and display tickets during an outage. Corroborating: "kitchen display" and "KDS" occur zero times across the 45 Knowledge Hub articles pulled from the WP REST API (epkb_post_type_1) on 2026-08-08, and the only documented kitchen output is print ("Moving the order will trigger printing from both the customer receipt printer and the kitchen printer"). This is a `no` about the claim's subject, not about outage behaviour, which remains undocumented separately. Re-check when the "coming soon" displays ship. https://slice.com/products/point-of-sale-for-pizza-shops/ · retrieved 2026-08-08 adversarially verified

kitchen-item-build-screens differentiator

Kitchen tickets are customizable (font, item order, additional information) and items carry a distinct 'kitchen name'. Ticket-level detail only; no build/assembly screens. https://slice.com/knowledge-hub/register-settings/ · retrieved 2026-08-01

kitchen-pizza-fractional-display differentiator

Still unresolved, and I can now say precisely where the gap is. Capture is unambiguous - Order Entry: 'For pizzas, use Choose Toppings to select half toppings. First, tap the half where you want to add toppings. Then, select the topping.' Rendering is not published. The only kitchen-ticket formatting documentation Slice has is Register Settings > Receipt Settings > 'Kitchen Receipt Settings: Customize kitchen tickets by choosing the font, order of items on the ticket, and the additional information included', repeated verbatim in Online Ordering > Settings, with 'Kitchen Tickets only display items and relevant kitchen details by default'. Neither enumerates the fields on the ticket nor shows a sample, so how a half assignment prints - a LEFT/RIGHT label, an indent, or not at all - is simply not stated. The Menu article's 'Kitchen name (optional) - A short name printed on kitchen tickets' is the only other ticket-content control and it is per item, not per section. Note the kitchen surface is thermal paper, not a make-line screen: Slice ships no KDS.

kitchen-recall-refire

Order Management (updated April 30, 2026) documents a manual whole-ticket reprint: 'Print : Print a receipt or kitchen ticket for an In Progress order if your Register app is connected to a printer', and 'Moving the order will trigger printing from both the customer receipt printer and the kitchen printer.' Shortfall, restated 2026-08-08 without the earlier 'no KDS' framing: the action is order-level and is offered only while the order is In Progress ('Orders stay In Progress until they are manually moved to Complete'), there is no recall of a ticket already sent and no way to refire a single item - 'reprint', 'refire' and 'bump' occur zero times across the 45 Knowledge Hub articles, 30 release notes and 26 FAQs retrieved from the WP REST API on 2026-08-08. Reprinting the whole ticket is the documented substitute for both. https://slice.com/knowledge-hub/register-order-management/ · retrieved 2026-08-08 adversarially verified

kitchen-order-modification-alerts differentiator

Re-evidenced 2026-08-08. Kitchen output at Slice is paper only: the Family Membership benefits list reads "Discounted kitchen displays & kiosks (coming soon)" and the Slice Register included-hardware answer is a closed list - "iPad interface, kitchen printer, cash drawer, receipt printer, credit card terminal, router, and delivery card reader" - with no display, so there is no live ticket to flag. The full print-routing surface is enumerated in Owner's App (web) > Register > Printer Settings: "Create New Setting", "Name", "Print Modes: Incremental / After Payments", "Print Quantity", plus edit/delete. Nothing sends a change notice, and "reprint" and "refire" occur zero times across the 45 Knowledge Hub articles retrieved from the WP REST API on 2026-08-08. An incremental-mode printer prints newly added items as separate lines, which is not a visual flag of added/changed/removed items on a live ticket. https://slice.com/knowledge-hub/owners-app-web-register/ · retrieved 2026-08-08 adversarially verified

kitchen-guest-ready-notification differentiator

Re-quoted 2026-08-08 - the page was rewritten (modified 2026-06-15) and the old citation's wording no longer appears. It now reads: 'Do my customers get order tracking? Yes. Customers get an order confirmation by text and via the Slice app, and can track their order's progress in real time in the app.' Included, no separate purchase, so partial. Shortfall, restated without the earlier 'no KDS bump event' framing: this is a Slice-channel notification tied to order placement and in-app status, and nothing ties it to the shop marking food ready. Register has no ready state to trigger it - Order Management's statuses are Scheduled, In Progress and Complete, 'Orders stay In Progress until they are manually moved to Complete' - and the word 'ready' occurs zero times in the 30 release notes and 26 FAQs pulled from the WP REST API on 2026-08-08. Counter and phone orders entered on the Register are outside the Slice-app channel this describes. https://slice.com/products/online-pizza-ordering-system/ · retrieved 2026-08-08 adversarially verified

kitchen-waste-logging

No inventory module, so no waste logging or depletion.

kitchen-speed-of-service-reporting

Unknown. Re-read the cited Owner's App (web) Financials article in full from the WP REST API. It never claims to enumerate its reports or their columns: the report set is introduced as "The Reports page provides access to various financial and sales reports to track your business performance", the summaries as "Displays key financial metrics for the selected timeframe, including:" and the order tables as "Lists all register orders with details such as:". 'Various', 'including' and 'such as' are open-ended by construction, so the absence of a ticket-time or per-station timing column from those lists is absence of evidence rather than evidence of absence. The one report that does assert completeness is the Register Sales Summary ("The Sales Summary Report consists of:"), and it is a single end-of-day cash-and-sales report, not the whole reporting surface. The separate observation that there is no public API to export from is unaffected, but it cannot by itself make the claim false. adversarially verified

kitchen-prep-forecasting

Unknown. The `no` rested on treating Slice's analytical surfaces as exhaustive lists, and they are not. The Owner's App (web) Financials article introduces its reports as "access to various financial and sales reports", and the Analytics article is descriptive prose ("The Analytics page provides detailed insights into your shop's performance, focusing on orders, sales, and menu items") rather than a closed inventory. The one surface where a forecast or prep list would plausibly appear - Insights, documented as "business recommendations from Slice based on your shop's activity" - is described in a single sentence that neither shows nor excludes predicted quantities. The associated 'kitchen staff have only a thermal printer' reasoning is also unsafe now: https://slice.com/pricing-test/ lists "Kitchen Display System" for Family Membership and https://slice.com/family-membership/ lists "Discounted kitchen displays & kiosks (coming soon)". adversarially verified

delivery-driver-roster

Downgraded from yes on independent retrieval of the Driver App article, which no earlier pass cited. Drivers are app logins, not first-class entities the operator administers: 'contact Slice Support at (888) 974-9928 to add your driver's login to your account. Each driver needs a unique email address.' Assignment state is one binary toggle — 'Tap the Available toggle to receive batch assignments... Drivers must be logged in and marked Available to be assigned' — not in-store / on-run / returning. Shortfall: no operator-managed roster, no driver clock-in/out or shift concept anywhere in the Driver App article, and per-driver history exists only as the Delivery Management Report's batch settlement. https://slice.com/knowledge-hub/register-slice-driver-app/ · retrieved 2026-08-02 adversarially verified

delivery-dispatch-board

Upheld on my own retrieval. The four sections are as described — Unassigned, Awaiting, In progress, Delivered — driver selection is real ('tap the arrow to open the list of active drivers and select the driver for the batch'), and sequencing is explicit ('The order in which you select the deliveries sets the delivery route'). The in-progress view shows which orders were delivered, the time each was delivered, and the driver's location. A genuine native dispatch surface, not marketing. https://slice.com/knowledge-hub/register-delivery-management/ · retrieved 2026-08-02 adversarially verified

delivery-route-map differentiator

Live map with geocoded stops and an editable delivery sequence, but the sequence is operator-set ('Change the sequence') — no system-generated route optimization is documented. https://slice.com/knowledge-hub/register-delivery-management/ · retrieved 2026-08-01

delivery-driver-tracking differentiator

Downgraded from yes; a differentiator held to the highest bar. The dispatch article surfaces 'The driver's current location on the map' with no refresh cadence, and the Driver App article documents GPS only in the driver's own direction — 'Tap Start Navigation to use GPS directions to the customer' — never as position reported back to the shop. The only feature Slice describes as real-time tracking belongs to its outsourced couriers: the release note Track Slice Delivery Drivers in Real Time covers 'your Slice Delivery driver's progress... real-time updates like driver name, status, and estimated timing'. Shortfall: continuous in-house driver GPS with a stated update interval is not documented. https://slice.com/knowledge-hub/register-slice-driver-app/ · retrieved 2026-08-02 adversarially verified

delivery-zones-polygon differentiator

The zone FAQ states the geometry directly: 'Your delivery zone is the distance where you will fulfill delivery orders. To guarantee accuracy, we work with you to DRAW a virtual delivery zone around your neighborhood or city. You can have multiple delivery zones with multiple different delivery fees/minimums.' A drawn zone around a neighborhood is not a radius and not a postcode list, and multiple zones are supported. Named shortfalls: it is not operator-configurable at all - 'Call (888) 974-9928 to add or edit delivery zones' - so there is no map editor in the Owner's App (web) or the Register; the FAQ never says the shape is an arbitrary polygon rather than a bounded neighbourhood selection; and drive-time isochrones are not offered in any form. https://slice.com/?echo_kb_faq=what-is-my-delivery-zone-and-how-do-i-edit-it · retrieved 2026-08-08

delivery-zone-pricing

Two of the three per-zone attributes are documented, and automatic application from the address is documented separately. The zone FAQ: 'You can have multiple delivery zones with multiple different delivery fees/minimums.' Order Entry, on taking a delivery order: 'If you have delivery fees configured for Slice Online Ordering, they will be automatically applied based on the address' - with a per-order override by 'tapping the pencil icon next to the fee amount'. Named shortfalls: there is no per-zone promise time - ETAs are shop-wide, set in Owner's App (web) or adjusted per order on the Register within global bounds ('Pickup ETAs must stay between 10 and 90 minutes, and delivery ETAs must stay between 20 and 120 minutes'), never per zone; and neither fee nor minimum is operator-editable, since both the zone FAQ and the fee FAQ route the change to Slice ('We can update these for you - contact (888) 974-9928 for support'). https://slice.com/?echo_kb_faq=what-is-my-delivery-zone-and-how-do-i-edit-it · retrieved 2026-08-08

delivery-address-validation

The Register order-entry article documents the whole flow for a delivery order. Geocoding at order time: 'Address Line 1 uses GOOGLE MAPS to suggest nearby addresses for accuracy' and 'The system will auto-fill city, state, and ZIP code.' Zone evaluation before the order is accepted: 'If you have delivery fees configured for Slice Online Ordering, they will be automatically applied based on the address' and 'If the address is OUTSIDE YOUR SLICE ONLINE DELIVERY ZONE, YOU WILL BE NOTIFIED but allowed to proceed.' That satisfies the claim as worded, which asks for rejection OR flagging - Slice flags, on the customer screen, before the items are entered and the order submitted. Reader caveat: the flag is advisory rather than blocking, and it is deliberately so, since a shop may choose to deliver outside its online zone on a phone order. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-08

delivery-driver-comp differentiator

The Delivery Management Report captures cash collected, credit-card payments, tips and cash settlement per driver. Shortfall: no per-delivery or mileage-based driver pay is computed, no reimbursement rate is configurable, and the Driver App article documents no mileage capture, so nothing feeds a payroll figure. https://slice.com/knowledge-hub/register-cash-management-and-reporting/ · retrieved 2026-08-02

delivery-cash-reconcile

Upheld on my own retrieval of the Cash Management article. The Delivery Management Report settles each driver: 'Total amount', 'Cash collected', 'Credit card' with a nested tips line, 'Delivery fees', and 'Cash due to driver' — computed by comparing cash collected against card tips, so the shop pays the difference when tips exceed cash and the driver returns the surplus when cash exceeds tips. That is a settle-up flow, not merely a report of takings. Caveat: no explicit over/short variance figure per driver. https://slice.com/knowledge-hub/register-cash-management-and-reporting/ · retrieved 2026-08-02 adversarially verified

delivery-daas-dispatch

Upheld; I re-retrieved the page and the sentence is intact: 'If you are using Flex Delivery, you can also choose to assign a delivery to your selected Slice Delivery provider, Uber or DoorDash.' The same page adds 'Simply select that option, tap Reassign Delivery, and we will send an outsourced driver', and Register Settings carries the toggle 'Outsource delivery orders: Toggle this setting on to have our partners deliver your Slice orders'. Caveat retained: the per-delivery courier cost is published nowhere, and the handoff covers Slice-channel orders, not marketplace orders. https://slice.com/knowledge-hub/register-delivery-management/ · retrieved 2026-08-02 adversarially verified

delivery-daas-fallback differentiator

Register Settings has a Flex Delivery toggle to 'switch between using your in-house drivers and our delivery partners' and dispatch allows per-order assignment to Uber/DoorDash. Automatic rules (no driver available / out of zone / wait threshold) are not documented. https://slice.com/knowledge-hub/register-settings/ · retrieved 2026-08-01

delivery-3p-direct-integration differentiator

'Integrates with 30+ delivery apps including DoorDash, Grubhub, and Uber Eats' with no separate tablet. Slice never states whether these are first-party certified or middleware-brokered, and Slice is absent from DoorDash's 2026 Preferred Integration Partner list. https://slice.com/products/point-of-sale-for-pizza-shops/ · retrieved 2026-08-01

delivery-3p-injection

Upheld on my own retrieval. Marketplace orders 'appear in their own column on the New Orders page', are confirmed with a tap or automatically — 'enable Auto-Confirm Orders so they go straight to the kitchen as soon as they arrive' — and Register Settings confirms auto-confirm 'allows Slice and third-party orders to be automatically confirmed', with automatic kitchen-ticket printing for online and third-party orders. No tablet farm, no re-keying. Inbound injection is the one direction of this integration that works. https://slice.com/knowledge-hub/register-third-party-orders/ · retrieved 2026-08-02 adversarially verified

delivery-menu-push

Verified verbatim, but the same paragraph shows the operator has no control of the push: menus are 'controlled by Slice', direct edits 'will break the integration and cause service interruptions', and order edits 'need to be communicated with the third party'. There is no sync status, no rejection surface, and no operator-initiated publish. Vendor-operated menu maintenance is not a menu-push capability the buyer holds. https://slice.com/knowledge-hub/register-third-party-orders/ · retrieved 2026-08-01 adversarially verified

delivery-86-sync

Item availability cannot reach the marketplaces: Slice 'does not have a way to communicate back to those providers'. Stock toggles affect Register and Slice online only. https://slice.com/knowledge-hub/register-third-party-orders/ · retrieved 2026-08-01

delivery-store-pause

Upheld; positive evidence of absence re-retrieved verbatim: 'Pausing or closing orders affects Slice online orders and Slice Phone orders—third-party orders will not be impacted.' Pause 'temporarily stops receiving pickup, delivery, or both for a set time' and Close stops orders for the remainder of the day, but neither reaches the marketplaces — the operator must still pause each one in its own portal. https://slice.com/knowledge-hub/register-shop-status/ · retrieved 2026-08-02 adversarially verified

delivery-3p-reconciliation differentiator

Slice separates third-party sales but never reconciles them to a marketplace payout. The Register Sales Summary Report's Third-Party section is enumerated in full and holds three lines: 'Total Order Sales', 'Total Tips' and 'Average Order Value', prefaced by 'All Third-Party Orders are prepaid.' The Owner's App (web) statement and report set is likewise enumerated column by column - Statement Summary, Transactions CSV, Order Activity, Orders, Tax, Sales Mix, Sales Summary - and every fee line in it is a SLICE fee (Card Processing Fees, Slice Partnership Fees, Slice Delivery Fees, Phone Order Fees, Register Subscriptions, Chargebacks). No marketplace commission, marketing fee, marketplace payout deposit, or missing/unpaid-order line appears anywhere, and none could: Slice states the integration is one-way - 'Slice receives the Third-Party orders but does not have a way to communicate back to those providers' - so it never sees DoorDash or Uber Eats remittance data. https://slice.com/knowledge-hub/register-cash-management-and-reporting/ · retrieved 2026-08-08

delivery-injection-error-visibility differentiator

Still unresolved, but the picture is sharper than 'not documented'. What Slice publishes on integration health is: a device-level indicator in Register Settings - 'Slice Support: View your Connection Status to confirm your Register is online and connected' (repeated in Online Ordering > Settings as 'Displays the Connection Status to confirm your system is online') - which is about this iPad's connectivity, not about a channel; a hard deadline with a consequence, 'Third-party orders must be confirmed within three minutes, or they may be canceled by the provider'; new-order alerting that is arrival-side only ('Visual New Order Alerts', 'New Order Alert Sound' and its repeat frequency); and a warning that operator action can silently break the feed, 'Do not edit third-party menus directly - this will break the integration and cause service interruptions.' Slice also states the link is one-way: 'Slice receives the Third-Party orders but does not have a way to communicate back to those providers.' What is nowhere documented is a per-channel connection state, a list of failed or rejected injections, or an alert on integration failure. I stopped short of `no` because Register Settings introduces itself as 'key configuration areas' rather than a complete list, so it does not exhaust the surface where such a view could sit.

delivery-tracking-page

'Real-time order tracking via text and app' for Slice-channel orders. Whether the tracking page sits on the restaurant's own domain, and whether it reflects live driver state for in-house drivers, is not documented. https://slice.com/products/online-pizza-ordering-system/ · retrieved 2026-08-01

delivery-promise-time differentiator

Promise times are manually set prep-time ETAs editable in 1- or 5-minute increments, with 15-minute slot laddering. No dynamic adjustment from kitchen load or driver availability is documented. https://slice.com/knowledge-hub/register-shop-status/ · retrieved 2026-08-01

delivery-offline-behavior

Still unresolved. This claim asks whether the vendor DOCUMENTS offline delivery behaviour, and having pulled all 45 Knowledge Hub articles, 30 release notes and 26 FAQs through slice.com/wp-json/wp/v2/, it does not - not for cash delivery orders, not for driver assignment, not for settlement. The relevant articles are detailed about the online path and silent about the disconnected one: Order Management's Delivery Management sections describe batching, driver assignment and the note that 'Drivers must be logged in and marked Available to receive batch assignments. The Driver App does not send alerts for new batches, so drivers must check the app', and Cash Management's Delivery Management Report computes cash due to driver against card tips - all of it assuming connectivity. The Driver App article documents no offline queue. Beware the vocabulary trap: 'offline' in Slice's reports means an in-person Register order, not a disconnected system, so keyword matches in the corpus are false positives. Nothing published states what happens during an outage, so this cannot be resolved either way.

digital-first-party-web

Downgraded from yes: the evidence was the pricing page, and the 'own branding/domain' half of the claim is undocumented. The Website Tools article describes a Slice-hosted, Slice-controlled site — the operator picks 'font and background color that best represent your shop' and edits the tagline and 'Our story', but designs are set by Slice's team and a different one must be requested from support — plus Smart Buttons, Smart Popups and 'a direct URL to your shop's menu for seamless online ordering' to paste into a site the operator runs elsewhere. Shortfall: connecting a custom domain is documented nowhere, the template is not operator-controlled, and ordering carries a per-order charge ($2.00/order Family, $3.00/order Online, waived under $10) in place of a percentage commission. https://slice.com/knowledge-hub/owners-app-web-website-tools/ · retrieved 2026-08-02 adversarially verified

digital-menu-single-source

The POS page text I fetched is narrower than quoted: 'Update your menu one time and it changes on your website, your app, and your Slice Register at the same time' — third-party is not in that sentence. Third-party menus are covered separately and are 'controlled by Slice', with the operator warned 'Do not edit third-party menus directly—this will break the integration', no per-item sync status, and 86ing that provably does not reach the marketplaces. Single source for three Slice-owned surfaces, brokered and unverifiable for the rest. https://slice.com/products/point-of-sale-for-pizza-shops/ · retrieved 2026-08-01 adversarially verified

digital-native-app differentiator

Verified verbatim and stronger than cited: 'This means you get the benefits of having an app, without the cost or work of building your own.' Slice explicitly positions the shared marketplace app as the substitute for a branded app. https://slice.com/products/slice-app/ · retrieved 2026-08-01 adversarially verified

digital-account-saved-payment

Downgraded from yes: the cited source does not support the payment half of the claim. The Register customer article documents editing 'their name, phone number, or address', that 'All Slice Online Customers are already in the system', search by phone as 'the most unique identifier', and order history with a 'Reorder button in the top right to place the same order' — and says nothing about stored cards. Saved payment survives only as a marketing bullet on the online-ordering page ('Saved payment accounts for repeat customers'), the same grade-D evidence on which this record already scores payments-card-on-file partial. Shortfall: no documented tokenization and no documented card reuse at the Register. https://slice.com/knowledge-hub/register-customer-management/ · retrieved 2026-08-02 adversarially verified

digital-upsell-engine differentiator

'Built-in upsells' claimed. No configuration model and no attach-rate reporting documented.

digital-scheduled-pacing

Scheduled orders supported with 15-minute slot laddering off the configured prep time. No per-slot capacity limits or automatic slot closure when saturated. https://slice.com/knowledge-hub/register-shop-status/ · retrieved 2026-08-01

digital-fulfillment-modes

Marketing-page-only evidence, and it conflicts with product documentation: the Register docs define dine-in as counter-service orders that 'do not require customer information', with no table or check object. Pickup and delivery are documented; curbside and QR dine-in are claim-level with no supporting Knowledge Hub article. https://slice.com/products/online-pizza-ordering-system/ · retrieved 2026-08-01 adversarially verified

digital-qr-table

The only QR statement on the retrieved page is 'you can place ordering links on social pages or QR codes on menus, pizza boxes, or signs' - a marketing-grade deep link into the shop's Slice online-ordering page, which a guest could scan at a table. The named shortfall: it opens a new online order, never an existing check. Order Entry enumerates the Register payment surface as closed - 'There are three ways to pay for an order: Card, Cash, and Other' - all cashier-initiated, with tipping taken on the shop's card reader and the three split modes ('Split payment evenly', 'Pay custom amount', 'Pay total owed') driven from the iPad. No guest-facing scan-to-pay, split or tip against an open check. Earlier notes citing 'curbside and dine-in QR' from this page are withdrawn: neither phrase appears on it. https://slice.com/products/online-pizza-ordering-system/ · retrieved 2026-08-08

digital-kiosk differentiator

No kiosk in the product catalog or hardware bundle.

digital-group-ordering

Checked all 45 slice.com/knowledge-hub articles, all 30 slice.com/release-notes-2 posts and all 26 echo_kb_faq entries via the open WP REST API. The Slice App article walks the consumer checkout end to end (browse menu, customize item, review bag, log in or enter contact info, choose pickup/delivery, payment method, tip, pickup instructions, promo code) and never mentions a shareable order link, multiple participants on one cart, or a per-person or total spend cap; the Pizzeria Website and Online Ordering Getting Started articles describe the same single-cart flow. The walkthrough does not assert it is the complete feature set, so this is undocumented rather than proven absent.

digital-catering-portal differentiator

'Catering order support' claimed. No separate catering menu, lead-time rules, quotes, deposits, or invoice/ACH terms documented. https://slice.com/products/online-pizza-ordering-system/ · retrieved 2026-08-01

digital-voice-ai-phone differentiator

Slice Phone uses live human agents by design — 'No AI, robots, or chat bots — fully human support'. No AI voice partner is named. https://slice.com/support/24-7-365-customer-support/ · retrieved 2026-08-01

digital-drivethru-ai

No drive-thru product at all.

digital-sms-ordering

knowledge-hub/slice-phone/ and release-notes-2/let-phone-customers-pay-by-text/ (dated 2026-02-05) document the only SMS surface Slice publishes: after a Slice Phone team member takes a VOICE order, the customer receives a text with order details, an ETA and a link to a secure order summary where an unpaid order can be paid online. The article's own limits section says it 'only applies to phone orders taken by the Slice Phone team', that it 'does not apply to orders entered directly on the Slice Register', and that 'Orders cannot be edited through the text' - customers 'must call back'. So no order is created or modified by text. Nothing on any host documents an inbound text-to-order or chat-ordering channel, and the limits section covers only this feature rather than enumerating Slice's ordering channels, so inbound SMS ordering is unresolved rather than proven absent.

digital-google-order differentiator

Downgraded from yes under the differentiator grade floor. The only source is a vendor feature page written to sell, with no configuration steps and no Knowledge Hub counterpart: 'It's the Order Online button on your GBP listing. We make sure it links to a direct ordering channel — not a third-party app', and Slice 'manages your Google Food Ordering (GFO) so Google orders go directly to your own ordering link, not third-party marketplaces that take a cut'. Shortfall: the 'Preferred by Business' designation the claim names appears nowhere on the page, the provisioning mechanism is undocumented, and the operator holds no configuration surface — Slice claims and manages the listing on their behalf. https://slice.com/products/google-business-profile/ · retrieved 2026-08-02 adversarially verified

digital-apple-business-connect

Listings claimed across 'Google, Apple, Bing, OneBite, and TripAdvisor'. Whether an Apple Maps 'Order Food' custom action is provisioned is not stated. https://slice.com/products/online-pizza-ordering-system/ · retrieved 2026-08-01

digital-loyalty-attach

The loyalty program is Slice's marketplace-wide diner program, not the operator's. The Slice App page gives the shop no configuration surface and never states who funds the free pizza, whether points are portable to the shop's own channels, or whether the operator can see or adjust a balance. A vendor-run diner loyalty scheme the operator cannot configure is not a 'yes' on native loyalty attach. https://slice.com/products/slice-app/ · retrieved 2026-08-01 adversarially verified

digital-subscriptions

knowledge-hub/owners-app-web-marketing/ enumerates the entire guest-facing promotion surface as Online Discount (a flat percentage on all online orders), Promo Codes (fixed or percentage, order minimum, usage limit, dates, channels) and Deals (item or bundle pricing, built by the Slice Menu team); none is recurring and none carries a billing cycle or entitlement. The only 'Subscriptions' string in the corpus is in the merchant statement breakdown at knowledge-hub/owners-app-web-financials/ ('Register Subscriptions: Deductions for POS register subscriptions'), which is the operator's own POS fee, not a guest membership. No delivery-fee-waiver or paid loyalty tier appears in the Slice App checkout article or any of the 30 release notes.

digital-promo-parity

Promo codes support fixed or percentage discounts, order minimums, usage limits, date ranges and channel selection; an Online Discount applies to all online orders. Identical honoring at the Register is not documented. https://slice.com/knowledge-hub/owners-app-web-marketing/ · retrieved 2026-08-01

digital-guest-data-ownership differentiator

The Profiles page holds 'a detailed database of your customers' with 'name, address, email, phone number, creation date, and the date of the most recent order', and its Import and Export section documents both directions: 'Import: Add your customer database from another system, with a maximum of 10,000 customers per import. The file must be a CSV...' and 'Export: Download your Slice customer database for further analysis or record-keeping.' No fee, ticket or approval is mentioned. Shortfall: no consented marketing status field exists in the documented profile or export (Slice sends the email and push campaigns itself per knowledge-hub/owners-app-getting-started/), the export's column set and format are not stated, order history is only available as a separate order-level CSV under Financials > Reports, and no merchant terms page addresses ownership - the published consumer ToS still grants Slice a 'world-wide, perpetual, irrevocable, royalty-free' content license. https://slice.com/knowledge-hub/owners-app-web-customers/ · retrieved 2026-08-08

digital-checkout-pci-sca

Slice hosts the entire digital checkout: knowledge-hub/online-ordering-slice-app/ states 'All payments are processed through the Slice App checkout', and the shop website is built and published by Slice itself (knowledge-hub/owners-app-web-website-tools/), so card entry never occurs on a page the restaurant controls. The security FAQ says Slice 'partners with industry-leading payment processors to ensure all transactions are secure and encrypted' and that payment information is 'never shared or stored beyond what's necessary to complete the transaction'. Shortfall: nowhere on slice.com does Slice publish a PCI DSS 4.0 compliance statement or AOC, say anything about the client-side script-integrity requirements effective March 2025, or mention 3DS / SCA; the FAQ names no processor and no standard. https://slice.com/?echo_kb_faq=how-secure-are-payments · retrieved 2026-08-08

digital-surcharge-transparency differentiator

The Sales Summary and Order Activity field lists document the fees as live objects: 'Credit Card Surcharge - A fee charged when a customer pays with a credit or debit card', 'Service Fees - Fees collected from customers for Register and Online orders', 'Cash Discounts - Discounts applied to orders paid in cash', and 'non-cash adjustment fees' folded into Dining Option and Gross Sales; the Order Activity report counts them separately ('Credit Card Surcharges: Total surcharges applied to credit card transactions', '# of Credit Card Surcharges Collected'). Service fees are explicitly reported for both channels. Shortfall: the surcharge is reported but never configured in any documented screen - it appears in no Owner's App (web) settings article, the Register Settings and Owner's App (web) Register articles expose only tips, discounts, printers and profiles, and Slice publishes nothing on the guest-facing surcharge disclosure, on states where surcharging is prohibited, or on debit-card and card-brand exclusions. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-08

guest-loyalty-unified-profile

'All Slice Online Customers are already in the system'; Register staff search by phone ('the most unique identifier') and can attach a profile to a dine-in order. Dedup/merge behavior is not documented. https://slice.com/knowledge-hub/register-customer-management/ · retrieved 2026-08-01

guest-loyalty-thirdparty-identity-attach differentiator

The Customers dropdown 'provides detailed customer information for your Slice online and Register orders'. Its filter options are the whole configurable surface and exclude marketplaces: Analytics lets you 'filter by Register customers, Online customers, or both', and Segments shows 'all online and register customers who ordered in the last 30 days' with a filter of 'All Customers or Online + Register'. Profiles is described the same way. Meanwhile knowledge-hub/register-third-party-orders/ says third-party orders arrive in their own column and 'Slice receives the Third-Party orders but does not have a way to communicate back to those providers.' DoorDash, Uber Eats and Grubhub orders therefore do not attach to a Slice guest profile - they are not part of the customer database at all. https://slice.com/knowledge-hub/owners-app-web-customers/ · retrieved 2026-08-08

guest-loyalty-accrual-models

One model only: points per order toward free pizza. Visit/punch and spend-tier accrual are not documented, and the program is Slice-wide rather than shop-configured. https://slice.com/products/online-pizza-ordering-system/ · retrieved 2026-08-01

guest-loyalty-tiers differentiator

Customers > Analytics defines an automatic three-band classification on a rolling window: 'New Customers: First-time buyers. Repeat Customers: Customers who ordered less than three times in the last three months. Loyal Customers: Customers who ordered more than three times in the last three months.' Membership recomputes as the window moves, so guests are promoted and demoted without operator action, and the label is carried on the Top 10 Customers list, the Segments table and the end-of-day report. Shortfall: the bands are fixed and not configurable (no threshold, spend basis or additional tier can be set), they are analytics segments only - no entitlement, discount or benefit attaches to a tier, and the status is never shown to the guest in the Slice App or on the shop website. https://slice.com/knowledge-hub/owners-app-web-customers/ · retrieved 2026-08-08

guest-loyalty-offline-behavior differentiator

Searched the full text of all 45 knowledge-hub articles, 30 release notes and 26 FAQs pulled from slice.com/wp-json/wp/v2/. The word 'offline' appears only as an accounting term for Register orders in knowledge-hub/marketplace-facilitator-and-tax-responsibilities/ and knowledge-hub/owners-app-web-financials/ ('Offline Sales Subtotal - Register (POS) orders'), never as a connectivity state. The only connectivity content is the FAQ 'How do I reconnect to Wi-Fi if I'm having internet issues?' and the iPad setup steps, neither of which says what the Register does to an order, a payment or a loyalty lookup while disconnected. Slice publishes no offline-mode article, and there is no developer portal to check (developers.slicelife.com returns the consumer storefront shell, as do docs. and support.slicelife.com and any invented subdomain).

guest-loyalty-offer-stacking-rules differentiator

The Register Discounts page lists each discount's Discount Details as 'Code', 'Amount', 'Combinable: Indicates whether the discount can be used with other discounts' and 'Start and End Dates' - an explicit exclusive-vs-combinable setting exposed as configuration. Item-level eligibility is separately configurable via the menu item option 'Discount ineligible: Prevents the item from being discounted' (knowledge-hub/owners-app-web-menu/). Shortfall: the Combinable flag exists only on Register discounts; the Owner's App (web) Marketing screens that create the Online Discount, Promo Codes and Deals enumerate their fields (name, type, order minimum, usage limit of none/one-time/once per customer, start and end dates, channels) with no combinability option, and no article anywhere states the order in which discounts, promo codes, loyalty rewards and Slice credit are applied to a check. https://slice.com/knowledge-hub/owners-app-web-register/ · retrieved 2026-08-08

guest-loyalty-targeted-offers differentiator

'Push personalized discounts and deals straight to your customers' mobile device' plus 'Abandoned order alerts to recover missed sales'. No operator-facing audience rule builder is documented — Slice's marketing team operates it. https://slice.com/products/marketing-for-pizza-shops/ · retrieved 2026-08-01

guest-loyalty-rfm-segmentation differentiator

Moved up from unknown on the Analytics article. Slice precomputes two guest views with no query-building by the operator: 'Most Valuable Customers' on spending and order frequency, and recently-ordered customers with an engagement level — recency, frequency and monetary in substance. Shortfall: no named lifecycle segments (new, regular, at-risk, lapsed, VIP), no segment membership counts, and no documented path from a view to a campaign audience — Slice's own marketing staff, not the operator, build the sends. https://slice.com/knowledge-hub/owners-app-web-analytics/ · retrieved 2026-08-02 adversarially verified

guest-loyalty-lifecycle-automation

Managed-service automations exist (holiday/big-day emails, timed texts, abandoned-order alerts) but as 'Our marketing experts handle all emails, texts, and app messages — you don't lift a finger', not as operator-configurable always-on campaigns. https://slice.com/products/marketing-for-pizza-shops/ · retrieved 2026-08-01

guest-loyalty-native-email-sms differentiator

Sourced only to a marketing page, and the same page frames it as a done-for-you service ('Our marketing experts handle all emails, texts, and app messages — you don't lift a finger'). No operator-facing composer, audience builder, send scheduler, or consent surface appears in the Knowledge Hub. Native sending by the vendor on the operator's behalf is a managed service, not an operator messaging capability. https://slice.com/products/marketing-for-pizza-shops/ · retrieved 2026-08-01 adversarially verified

guest-loyalty-consent-management

Checked every marketing-adjacent article on slice.com: knowledge-hub/owners-app-web-marketing/ (Discounts, Online Discount, Promo Codes, Deals, Branding Studio - no audience or consent surface at all), knowledge-hub/owners-app-getting-started/ ('Your marketing: See how your emails, push notifications, and promotions perform... Emails: Shows how many customers received your emails and total orders and sales from email campaigns sent through Slice'), knowledge-hub/slice-local-tv-ads/ (which names 'automated email and text marketing' as a Slice-run tool), and knowledge-hub/owners-app-web-customers/ whose profile fields are name, address, email, phone, creation date and most recent order - with no opt-in flag, consent source or timestamp among them. The Slice App checkout article describes 'Log in or enter contact information' with no marketing opt-in step. Nothing on slice.com or in the 26 FAQs describes revocation handling, a STOP keyword, or per-channel preferences; because Slice sends on its own infrastructure the operator may never see the consent record, but that is not documented either way.

guest-loyalty-10dlc-registration

Full-text searched all 45 knowledge-hub articles, 30 release notes and 26 FAQs from slice.com/wp-json/wp/v2/: the strings '10DLC', 'A2P', 'brand registration' and 'campaign registration' do not occur. The SMS that Slice does document is sent by Slice, not the operator - knowledge-hub/slice-phone/ describes Slice Phone order-detail and pay-by-text messages, and knowledge-hub/slice-local-tv-ads/ names 'automated email and text marketing' as a Slice-operated service - which would normally place registration on Slice's own brand and campaign, but no Slice page says so. There is no developer or trust-and-compliance portal to check: developers.slicelife.com, docs.slicelife.com and support.slicelife.com all return the same consumer storefront shell, and slice.com/help-center has no compliance section.

guest-loyalty-campaign-attribution differentiator

'Check your marketing results anytime in your Owner's App. Real-time reports show exactly which campaigns are bringing in sales.' No offer-to-check-total redemption tie-out is documented. https://slice.com/products/marketing-for-pizza-shops/ · retrieved 2026-08-01

guest-loyalty-data-export-portability differentiator

Customers > Profiles is 'a detailed database of your customers, including their contact information and order history' holding 'name, address, email, phone number, creation date, and the date of the most recent order', and its Import and Export section documents a one-click 'Export: Download your Slice customer database for further analysis or record-keeping' beside the 10,000-row CSV import - the operator performs both, with no fee, approval or support ticket mentioned. Transaction-level history is separately self-serve: knowledge-hub/owners-app-web-financials/ documents Reports > Order Activity, Orders, Tax, Sales Mix and Sales Summary, each generated by 'Create New Report' and downloaded as CSV, plus a per-statement 'Transaction CSV or PDF for a full breakdown of each transaction'. https://slice.com/knowledge-hub/owners-app-web-customers/ · retrieved 2026-08-08

guest-loyalty-cdp-event-api differentiator

Slice publishes no API and no webhooks of any kind, so no CDP subscription surface exists.

guest-loyalty-review-capture-routing differentiator

No feedback-request or review-routing feature is documented. An Owner's Portal reviewer had to ask whether owners can even see customer reviews. https://itunes.apple.com/us/rss/customerreviews/id=1402632571/sortBy=mostRecent/json · retrieved 2026-08-01 · not refetchable · site policy

guest-loyalty-referral-program

Searched all 45 knowledge-hub articles, 30 release notes and 26 FAQs: 'refer', 'referral' and 'invite a friend' do not appear in any guest context. knowledge-hub/online-ordering-slice-app/ describes the consumer app's returning-customer experience (house favorites, best sellers, 'Coupons and loyalty points, which update automatically when you add offers in the Owner's App') with no per-guest share code or link, and knowledge-hub/owners-app-web-marketing/ enumerates the promotion types as Online Discount, Promo Codes and Deals - promo codes are shop-wide strings with a usage limit of none, one-time, or once per customer, with no attribution of a referred guest's first order and no two-sided reward. Slice's operator referral bounty on slice.com marketing remains the only referral mechanic published.

guest-loyalty-wallet-pass differentiator

Full-text search of the WP REST corpus (45 knowledge-hub articles, 30 release notes, 26 FAQs) returns no occurrence of 'Wallet', 'Apple Wallet', 'Google Wallet', 'pass' in a loyalty sense, or PKPass. The only wallet-adjacent mention is card acceptance at the Register - 'a physical or virtual card like Apple Pay or Google Pay' in knowledge-hub/slice-register-order-entry/ - which is a payment credential, not a loyalty pass. knowledge-hub/online-ordering-slice-app/ shows the Slice consumer app carrying 'Coupons and loyalty points', so the app is the documented loyalty carrier, but Slice never says whether any pass alternative exists for guests who do not install it.

guest-loyalty-privacy-rights-tooling

Slice operates a consumer data-rights portal at privacy.slicelife.com. This is Slice-run and diner-facing — no operator-side admin tooling to locate, export or delete an individual guest's records is documented. https://privacy.slicelife.com · retrieved 2026-08-01

guest-loyalty-redemption-fraud-controls

Employee Permissions gate the redemption-adjacent actions and produce an audit trail: per knowledge-hub/register-employee-permissions/, 'certain actions - like applying discounts, issuing refunds... require additional permissions' and 'if an employee tries to perform an action outside their assigned permissions, the system will block them until a user with approval grants or denies the request.' The Permissions Log in the Owner's App (web) 'records sensitive actions performed by employees and the details of who approved them' with columns Actioned By, Authorized By, Action, Status and Date, described as 'a clear audit trail for tracking sensitive activities performed and approved within your system' and as a tool to 'address potential shrinkage'; release-notes-2/control-who-manages-the-cash-drawer/ (2025-10-09) extends the same pattern to the cash drawer. Shortfall: none of this is loyalty-specific - there is no redemption velocity limit, no manual point-adjustment surface to approve (loyalty points are issued by the Slice Rewards Program, not the shop), and no flagging of an employee redeeming against their own guest profile. https://slice.com/knowledge-hub/owners-app-web-register/ · retrieved 2026-08-08

guest-loyalty-ai-offer-recommendation differentiator

The strings 'AI', 'artificial intelligence', 'machine learning' and 'predictive' do not occur in any of the 45 knowledge-hub articles, 30 release notes or 26 FAQs. The nearest surfaces are knowledge-hub/owners-app-report/ ('Business Recommendations: Slice provides suggestions to improve your shop's performance, such as adding menu photos, adjusting delivery fees, or offering promotions') and the Pizzeria Score success list in knowledge-hub/owners-app-getting-started/ - operational nudges, not offer content, audience or send-time recommendations, and nowhere attributed to a model. release-notes-2/highlight-your-best-sellers/ (2025-10-09) describes an automatic ranking ('Your top five menu items are automatically labeled as Best Sellers based on sales from the last 30 days. The labels update weekly'), which is a fixed rule rather than a claimed AI feature. Slice's marketing positions its marketing service as run by its own team, so no AI/ML claim exists to verify.

guest-loyalty-stored-value-gift

The Register tender surface is enumerated exhaustively: 'There are three ways to pay for an order: Card, Cash, and Other', where Other is 'used for anything that is not cash or card, e.g., check, paper gift certificate, running your own invoices' - a paper certificate is keyed as an untracked miscellaneous tender, with no balance looked up or decremented. The payment-type breakdown in knowledge-hub/owners-app-web-financials/ matches with no stored-value line: Credit Card Collected, Other Payment Collected, Cash Collected and Slice Online Payment, and the only balance-bearing instrument named anywhere is 'Slice credit', which the same article treats as a Slice-issued discount on online orders, not a shop-sold card. The customer profile schema in knowledge-hub/owners-app-web-customers/ (name, address, email, phone, creation date, most recent order) carries no balance field. Slice therefore sells no native gift card or stored-value account tied to the guest profile. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-08

labor-clock-in-at-pos

Value upheld on retrieval, with one misattributed quote corrected: the employee-permissions article does not say the Register is not a time clock, it says 'The Employee Permissions Log in the Owner's App (web) only tracks assigned permissions—it does not function as a time clock or track when employees log in or out.' The Time Clock itself is real — 'Time Clock is powered by Homebase, a Slice Partner', added to the Register iPad, punched by PIN on the iPad or on employees' own phones. Shortfall: it is the partner's product. The operator must already hold a Homebase account from joinhomebase.com, must 'reach out to Slice Support for help getting started', timecards live in Homebase, and Slice discloses no price for the Homebase side. https://slice.com/knowledge-hub/homebase-partnership/ · retrieved 2026-08-02 adversarially verified

labor-photo-punch-verification differentiator

knowledge-hub/homebase-partnership/ (updated 2026-02-18) and knowledge-hub/homebase/ (updated 2026-02-05) are the entire published timekeeping surface and carry identical text. The clock-in sequence is: exit the Slice Register app, open the Time Clock app, 'Enter your PIN on the keypad', see your name, tap Clock In; clock-out adds an optional shift rating and note. No camera, photo, selfie, facial or biometric step appears, and neither article states whether the Homebase app offers one. The word 'photo' occurs in the corpus only for menu photography. Slice explicitly scopes itself out of the surrounding functions ('You'll use the Homebase website or mobile app separately to set up schedules, manage employees, and run payroll'), so the photo-punch option would live in Homebase's own product, which is outside anything Slice publishes and not scoreable from a Slice source.

labor-geofenced-mobile-punch

knowledge-hub/homebase-partnership/ and knowledge-hub/homebase/ both state 'Your team can clock in using the Register iPad or their own phones - whichever works best for your shop', which establishes the mobile punch, but the documented punch flow is PIN entry only. The words 'geofence', 'GPS', 'location' and 'radius' never appear in a timekeeping context anywhere in the 45 knowledge-hub articles - GPS appears only in the Slice Driver App article for delivery navigation and in the Slice Delivery live driver map. Neither article says whether a phone punch is restricted to the shop, whether coordinates are captured, or whether Homebase's own location settings are exposed to a Slice shop. The restriction, which is the substance of the claim, is therefore unresolved rather than absent.

labor-offline-time-punch differentiator

The two Homebase articles (knowledge-hub/homebase-partnership/, knowledge-hub/homebase/) describe the punch as a PIN entry in a separate Time Clock app on the Register iPad or an employee phone, with a confirmation message on success. Neither mentions connectivity, queuing, sync, reconnection or duplicate handling; the only connectivity content in the whole corpus is the Wi-Fi troubleshooting FAQ and the iPad setup steps. Because the timecard is written by the partner's app rather than by Slice Register, Slice arguably has nothing to document here - but it does not say that either, and there is no Slice API or developer portal to inspect (developers.slicelife.com returns the consumer storefront shell, not documentation). Unresolved.

labor-granular-rbac

Per-employee, per-action permissions assigned in the Owner's App — 'applying discounts, issuing refunds, or accessing reports' are named. The full grantable action list is not published and there is no per-location scoping (single-shop product). https://slice.com/knowledge-hub/register-employee-permissions/ · retrieved 2026-08-01

labor-manager-override-audit

Overrides require an approving user's four-digit PIN to grant or deny. But the Employee Permissions Log 'only tracks assigned permissions' — no immutable, queryable record of who approved which override. https://slice.com/knowledge-hub/register-employee-permissions/ · retrieved 2026-08-01

labor-native-scheduling differentiator

Positive evidence of absence, and stronger than the previous inference: Slice's own article states "You'll use the Homebase website or mobile app separately to set up schedules, manage employees, and run payroll." Scheduling is deliberately outside the platform that now holds the punch data. https://slice.com/knowledge-hub/homebase/ · retrieved 2026-08-02

labor-demand-labor-forecast differentiator

Searched the full WP REST corpus: 'forecast', 'projected', 'predicted' and 'recommended staffing' do not occur. The analytics surfaces are all backward-looking - knowledge-hub/owners-app-web-analytics/ (sales by day, top and least selling items, customer engagement), knowledge-hub/owners-app-report/ (Sales Insights comparing this week to prior periods) and the Financials reports - and none produces hours or headcount. The Homebase articles say scheduling is done 'separately' on Homebase's own website or app and describe no data flowing from Slice to Homebase beyond the shared Time Clock login, so whether Slice sales history is even available to a Homebase forecast is undocumented on Slice's side. Homebase's own capabilities are outside Slice's published scope.

labor-realtime-labor-percent differentiator

The Owner's App report set is enumerated in the Financials article — Order Activity, Orders, Tax, Sales Mix, Sales Summary — and the Register adds only the Cash Drawer and Delivery Management reports. Not one carries a labour cost or hours dimension, and clocked hours are held by partner Homebase, so no live labour-percent view exists on any Slice surface. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-02

labor-overtime-prevention differentiator

'Overtime', 'OT' and 'threshold' do not occur anywhere in the 45 knowledge-hub articles, 30 release notes or 26 FAQs. knowledge-hub/homebase-partnership/ and knowledge-hub/homebase/ document the clock-in as PIN entry followed by 'Tap Clock In to begin your shift' with a confirmation message - there is no approaching-hours warning, no block, and no configurable weekly or daily threshold on the Slice side. Slice states that scheduling, employee management and payroll are done separately in Homebase, so any overtime enforcement would be Homebase's; Slice neither claims nor disclaims that it surfaces at the Register iPad punch, so this is unresolved.

labor-break-compliance-by-state differentiator

The clock-out sequence in knowledge-hub/homebase-partnership/ and knowledge-hub/homebase/ is: open the Time Clock app, enter PIN, 'Tap Clock Out', optionally 'Rate your shift and leave a note for your manager', then a confirmation showing the time clocked out. There is no break start/end action, no meal or rest attestation prompt, and no missed-break flag. 'Meal break', 'rest break', 'attestation' and 'premium pay' return no hits across the corpus, and Slice publishes no state-by-state labor content (the only jurisdiction-aware article is knowledge-hub/marketplace-facilitator-and-tax-responsibilities/, which is about sales tax). Break rules would be configured in Homebase, which Slice does not document.

labor-fair-workweek-support

Predictive-scheduling support requires a schedule inside the platform. Slice states scheduling happens 'separately' in Homebase's own website or app, so Slice tracks no advance-notice deadline and calculates no predictability pay. https://slice.com/knowledge-hub/homebase/ · retrieved 2026-08-02

labor-minor-labor-rules

The claim requires enforcement at both scheduling and clock-in. Slice has no scheduling at all — 'You'll use the Homebase website or mobile app separately to set up schedules' — and documents no age-based hour or time-window restriction at punch. https://slice.com/knowledge-hub/homebase/ · retrieved 2026-08-02

labor-tip-pooling-rules

The Delivery Management Report computes a per-driver, per-batch tip settlement automatically: each driver gets a summary of total amount, cash collected, credit card, tips, other, delivery fees and 'Cash due to driver: Amount the shop owes the driver - or the driver owes the shop - based on tip handling', with the rule stated explicitly - 'If the cash collected is more than the driver's credit card tips, the driver keeps the value of their credit card tips and returns the rest to the shop. This shows as Cash Due to Drawer. If the credit card tips are more than the cash collected, the driver keeps the cash they collected and is paid additional cash by the shop to cover the full tip amount.' Shortfall: this is a single hard-coded cash-versus-card reconciliation for delivery drivers only. There is no pool: no percentage-of-sales, hours-worked, points or role-weighted allocation is configurable anywhere, no tip-out from one role to another exists, cashiers and kitchen staff are not covered, and hours now live in partner Homebase with no documented link to Slice tips. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-08

labor-tip-distribution-audit-trail

Card and cash tips are reported in the Sales Summary and per-driver in the Delivery Management Report. No per-shift contributed/distributed pool record exists because there is no pooling engine. https://slice.com/knowledge-hub/register-cash-management-and-reporting/ · retrieved 2026-08-01

labor-qualified-tips-w2-reporting differentiator

knowledge-hub/owners-app-web-financials/ does separate tips by channel and tender - 'Tips - All tips collected through card transactions', 'Register Tips - Tips collected from Register card payments', 'Online Tips', 'Total Online Prepaid Tips', plus per-driver cash-versus-card tip reconciliation - so the underlying split exists in reporting. But there is no payroll export at all: the Reports page enumerates exactly five reports (Order Activity, Orders, Tax, Sales Mix, Sales Summary), none of them payroll, and knowledge-hub/homebase-partnership/ says payroll is run separately in Homebase. 'W-2', 'Box 12', 'TP', 'tipped occupation' and 'qualified tips' return no hits anywhere in the corpus, and Slice does not document what tip data, if any, flows to Homebase. Unresolved on the Slice side.

labor-native-payroll differentiator

Explicit: "You'll use the Homebase website or mobile app separately to set up schedules, manage employees, and run payroll." Payroll is the partner's product; Slice files no taxes and runs no direct deposit. https://slice.com/knowledge-hub/homebase/ · retrieved 2026-08-02

labor-payroll-export-formats

Hours punched on the Register reach exactly one payroll destination — Homebase, which 'helps you manage schedules, hours, and team communication' and where the operator runs payroll. Shortfall: one provider, not the two the claim requires; no Gusto, ADP, Paychex or QuickBooks path is named; no file format or field list is published; and Slice itself exports no timecard file — the data is captured in the partner's app rather than exported from Slice. https://slice.com/knowledge-hub/homebase-partnership/ · retrieved 2026-08-02

labor-shift-swap-workflow differentiator

Shift swaps and open-shift claiming presuppose a schedule. Slice holds none; scheduling is done separately in Homebase, and Slice documents no request or manager-approval workflow of its own. https://slice.com/knowledge-hub/homebase/ · retrieved 2026-08-02

labor-digital-onboarding-i9

Slice's article places employee management outside its platform — 'manage employees' happens in Homebase — and Slice ships no new-hire onboarding, W-4 or I-9 collection, or E-Verify submission anywhere in the Owner's App. https://slice.com/knowledge-hub/homebase/ · retrieved 2026-08-02

labor-server-performance-metrics differentiator

Two per-employee surfaces exist and neither answers the claim as worded. knowledge-hub/owners-app-web-financials/ Delivery Management Report gives each assigned DRIVER a summary (total amount, cash collected, credit card, tips, other, delivery fees, cash due to driver) - drivers are not servers or cashiers and no check-level metric is derived. knowledge-hub/owners-app-web-register/ Permissions Log records who performed and who authorized each sensitive action (Actioned By, Authorized By, Action, Status, Date), which would identify who voided or discounted but is presented as a shrinkage log, not a rate. The sales reports themselves are enumerated field by field in the Financials article and none carries an employee dimension: Sales Summary, Order Activity, Orders, Tax and Sales Mix break down by channel, dining option, tender and item, never by user. Average check, item attachment and void/comp rates by cashier are therefore not documented; whether the underlying user id on each order is exposed anywhere is unstated.

reporting-realtime-dashboard

Value upheld but the earlier basis was wrong: the record reasoned from the Financials article that only five fixed CSV reports exist, when the Owner's App also ships an Analytics section nobody had cited. It carries visual dashboards — Delivery & Pickup split, Sales by Day, Top and Least Selling Menu Items, Your Customers, Most Valuable Customers — with a period filter and an 'Online Only or Register' source toggle, on web and in the Owner's App. Shortfall that keeps this partial: no refresh interval or latency is stated anywhere, and no Slice document uses the words live or real-time for sales figures. https://slice.com/knowledge-hub/owners-app-web-analytics/ · retrieved 2026-08-02 adversarially verified

reporting-eod-closeout

Sales Summary Report covers 'Total sales, payment methods, taxes, and tips for Register, Online, and Third-Party orders' with net/gross sales, service fees, discounts and average order value, paired with drawer close and cash reconciliation. https://slice.com/knowledge-hub/register-cash-management-and-reporting/ · retrieved 2026-08-01

reporting-pmix-modifier-level

Sales Mix Report tracks 'the quantity and sales performance of individual menu items'. Modifier-level PMIX and revenue-center slicing are not documented; date and order-type filters exist. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-01

reporting-comps-voids-audit

Discounts carry reason codes and appear in the Sales Summary, but there is no report attributing comps/voids/overrides to the applying employee and approving manager — the permission log explicitly is not an activity log. https://slice.com/knowledge-hub/register-employee-permissions/ · retrieved 2026-08-01

reporting-cash-over-short

Drawer open/close with opening and closing balances, No Sale / Pay Out / Pay In, and 'reconcile cash discrepancies'. Per-employee over/short attribution is not explicitly documented. https://slice.com/knowledge-hub/register-cash-management-and-reporting/ · retrieved 2026-08-01

reporting-labor-productivity

Value upheld but on a wider base than the record used. The earlier note treated the Financials article as the whole report catalogue; it is not — the Owner's App also ships an Analytics section. I read it: Orders (Delivery & Pickup, Sales by Day, Top and Least Selling Menu Items) and Customers (Your Customers, Most Valuable Customers). Not one dimension is labour hours, labour cost or sales per labour hour, and clocked hours sit in partner Homebase rather than on any Slice surface. Positive evidence of absence across both report surfaces. https://slice.com/knowledge-hub/owners-app-web-analytics/ · retrieved 2026-08-02 adversarially verified

reporting-server-scorecards differentiator

knowledge-hub/owners-app-web-financials/ enumerates the whole reporting menu - 'Order Activity Report, Orders Report, Tax Reports, Sales Mix Report, Sales Summary' - and then lists every field of each; the dimensions are channel (Register / Slice Online / third-party), dining option, tender, discount type, tax and item, with no server, cashier or user column and no items-per-check or attachment metric. The only per-person report is the Delivery Management Report, which scores drivers on batch value, cash collected, card, tips and delivery fees. Tips exist only at shop and channel level ('Register Tips', 'Online Tips'), so tips as a percentage of an individual's sales cannot be produced from anything documented. No scorecard screen appears in knowledge-hub/owners-app-web-analytics/ or knowledge-hub/owners-app-report/ either.

reporting-channel-profitability differentiator

Upheld with the shortfall sharpened on my own retrieval. Net Sales splits only 'Register Sales' and 'Online Sales'; Payments splits Credit Card Collected, Cash Collected, Slice Online Payment and Other Payment; Dining Option splits Delivery, Pickup, To Go, Dine In and the Slice online variants. Third-party appears in a single aggregate block at the end — 'All Third-Party Orders are prepaid', with total order sales, total tips and average order value. Shortfall: marketplaces are not broken out individually, and the Service Fees line covers Register delivery fees, credit-card surcharges and Slice online delivery fees only — no marketplace commission is netted anywhere. https://slice.com/knowledge-hub/register-cash-management-and-reporting/ · retrieved 2026-08-02 adversarially verified

reporting-multiloc-drilldown differentiator

Multi-shop operators are handled by switching context, not by consolidation: knowledge-hub/owners-app-getting-started/ says 'If you have multiple shop locations, select the appropriate location to proceed' at login, and knowledge-hub/slice-register-getting-started/ repeats it for the Register ('If you have multiple shops, select the location you are in'). The Financials article then enumerates the entire reporting surface - 'Order Activity Report, Orders Report, Tax Reports, Sales Mix Report, Sales Summary' - and lists the complete field set of each ('The Sales Summary Report consists of:', 'Here's a breakdown for each row'); not one field is a location, shop or store dimension, and no group-total, side-by-side comparison or roll-up view appears in the Analytics, Report or Customers articles either. Drill-down to an individual transaction does exist, but only within the single shop context you logged into. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-08

reporting-custom-report-builder differentiator

Five fixed report types with date/order-type/dining-type filters. No dimension-and-measure builder or saved custom reports. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-01

reporting-scheduled-delivery

The article closes its Sales Summary section with: 'You can get automated daily sales summaries by calling your Account Manager at (888) 974-9928 to set up daily Sales Summary Report (SSR) emails. These reports provide a breakdown of the day's sales and can be sent to multiple recipients, including managers and accountants.' So recurring email delivery to a recipient list is real. Shortfall: it covers exactly one report of the five documented (Order Activity, Orders, Tax, Sales Mix, Sales Summary) - the rest are 'Create New Report' then download the CSV on demand; the cadence is fixed at daily with no other option offered; and there is no self-serve scheduler - setup requires a phone call to a Slice Account Manager, so the operator cannot define or change the schedule or recipients from the Owner's App (web). https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-08

reporting-raw-warehouse-export differentiator

Manual CSV download only. No S3/SFTP/Snowflake/BigQuery destination and no scheduled bulk export. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-01

reporting-public-api differentiator

No developer portal exists (developers.slicelife.com serves marketing content). No REST or GraphQL reference is published anywhere.

reporting-webhooks differentiator

No webhook documentation exists.

reporting-api-not-upcharged differentiator

There is no API to include or upcharge.

reporting-tier-paywall differentiator

Owner's Portal reporting is included on both memberships, but every Register-derived report (Sales Summary, drawer/cash, Delivery Management) requires the $399/mo Family tier since the POS itself is Family-only. https://slice.com/pricing · retrieved 2026-08-01

reporting-history-retention differentiator

Checked every reporting surface on slice.com: knowledge-hub/owners-app-web-financials/ (Reports run from a chosen date range; Statements list payout history; Transactions available as CSV or PDF per statement), knowledge-hub/owners-app-web-analytics/ ('select a period like the last seven days'), knowledge-hub/owners-app-report/ ('Use the date picker to adjust the time range') and knowledge-hub/owners-app-web-customers/ (whose segment views are fixed at 'the last 30 days' and whose review responses are capped at 90 days - the only two explicit time limits in the corpus, and neither is a data-retention statement). No maximum lookback, archival tier, truncation warning or retrieval fee appears in any of the 45 articles, 30 release notes or 26 FAQs, and Slice publishes no merchant terms page covering data retention (slice.com/terms-of-service/ is consumer-facing). Unresolved.

reporting-anomaly-alerts differentiator

The Insights page 'provides recommendations and sales trends': 'Sales Insights: Highlights weekly sales performance compared to previous periods. Notifications indicate whether your sales have increased or decreased and by how much', with 'Unread Insights: New insights are marked with a colored dot.' That is a deviation-from-historical-pattern notification the operator does not have to run a report to see, and the Owner's App home also shows today's sales, orders and voids against the same day last week. Shortfall: nothing is operator-configured - there is no metric picker, no threshold, and no rule builder; the surface is limited to weekly sales movement (voids, discount rate and forecast variance are not alertable); and delivery is an in-app Insights feed with an unread dot, not a push notification or email to a recipient list. The only push notifications Slice documents are guest-facing marketing sends. https://slice.com/knowledge-hub/owners-app-report/ · retrieved 2026-08-08

reporting-nl-query

'AI', 'assistant', 'ask', 'natural language' and 'chatbot' return no product hits across the 45 knowledge-hub articles, 30 release notes and 26 FAQs. Reporting is entirely pick-a-report-and-a-date-range: knowledge-hub/owners-app-web-financials/ enumerates Order Activity, Orders, Tax, Sales Mix and Sales Summary, each generated with 'Create New Report' and downloaded; knowledge-hub/owners-app-web-analytics/ and knowledge-hub/owners-app-report/ are fixed dashboards. The only chat surface is human: knowledge-hub/owners-app-connect/ describes 'Get in Touch - Start a live chat to ask questions about your shop, Slice products, or account management', which routes to Slice staff and returns support answers, not figures from the operator's data. There is no API or developer portal to query either.

reporting-guest-cohorts differentiator

Moved up from unknown. The Owner's App Analytics article — a report surface no previous pass cited, and one that refutes this record's repeated assertion that the Financials article enumerates the whole report catalogue — carries a Customers section with 'Your Customers' (recently ordered customers and engagement level) and 'Most Valuable Customers' ranked on spending, order frequency and loyalty, filterable by period and by 'Online Only or Register'. Shortfall: no new-versus-returning counts, no lifetime-spend cohort bands, and no export of the guest list behind the view. https://slice.com/knowledge-hub/owners-app-web-analytics/ · retrieved 2026-08-02 adversarially verified

reporting-sales-forecast differentiator

Full-text search of the WP REST corpus finds no 'forecast', 'projection' or 'predicted sales'. knowledge-hub/owners-app-web-analytics/ reports sales by day, top and least selling items and customer segments for a chosen past period; knowledge-hub/owners-app-report/ compares this week to previous periods and today to the same day last week; knowledge-hub/owners-app-web-financials/ enumerates five reports, all retrospective. The forward-looking objects Slice does publish are manual, not modelled: scheduled orders (knowledge-hub/owners-app-web-financials/, 'Scheduled Orders - Track orders placed for future fulfillment'), operator-set delivery and pickup ETAs, and Adjusted Time rules where the operator picks days, a time window and a plus/minus minute amount (knowledge-hub/owners-app-web-time-management/). Nothing produces a predicted sales figure at daypart or hourly granularity, and no scheduling or ordering workflow consumes one - scheduling is done in partner Homebase and inventory is not a Slice surface.

reporting-tip-tax-compliance

Card and cash tips are reported, and Tax Reports show gross sales, total tax collected and 'Total Withheld: The portion of sales tax withheld by Slice for remittance to tax authorities, where applicable'. Declared-vs-charged tips per employee and pool distribution detail are absent. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-01

multi-location-org-hierarchy

Multi-shop accounts do exist and locations are a real object: at login, 'If you have multiple shop locations, select the appropriate location to proceed', and on the dashboard 'the location selector lets you switch between multiple shop locations using a dropdown menu. If you manage more than one shop, tap the selector to choose the location you want to view.' Slice Register repeats it: 'If you have multiple shops, select the location you are in.' Shortfall: this is exactly one flat level. No enterprise/region/group object is named anywhere in the 45 Knowledge Hub articles, and every reporting and permission surface documented is scoped to the single selected shop rather than to a group. https://slice.com/knowledge-hub/owners-app-getting-started/ · retrieved 2026-08-08

multi-location-central-menu-publish

Walked the whole slice.com Knowledge Hub through the open WP REST API (wp-json/wp/v2/epkb_post_type_1, 45 articles; epkb_post_type_2, 30 release notes; echo_kb_faq, 26 entries). The two menu-authoring articles - knowledge-hub/owners-app-web-menu (Menu Item Matrix, item fields, modifier groups, categories) and the Register Menu Layout section of knowledge-hub/owners-app-web-register - operate on one shop's menu, and the 2026-02-05 release note 'Manage Your Full Menu in One Place' is about shared modifiers within a shop, not cross-location publishing. Multi-shop accounts do exist (knowledge-hub/owners-app-getting-started), but no article, release note or the merchant Online Restaurant Agreement describes choosing target locations, a publish action, or a version/push history. Unresolved rather than absent: nothing published enumerates the multi-shop feature set, so an unpublished corporate tool cannot be ruled out.

multi-location-local-override-policy differentiator

knowledge-hub/owners-app-web-menu enumerates the item record (Item name, Price, Category, Availability, Print Routing, Stock) and the per-item Options list (loyalty reward, available online, available on Slice Register, house favorite, contains alcohol, discount ineligible, register printing); none of these fields is lockable, ownable by a parent, or marked corporate-vs-local, and no field-level lock appears in knowledge-hub/owners-app-web-register either. No article in the 45-article Knowledge Hub or the 30 release notes uses the words corporate, parent, or locked field. Left unknown because the docs never address a multi-shop menu at all, so this is silence about the governance model rather than documented absence of one.

multi-location-price-zones

The Menu Item Matrix enumerates the item record - 'Item name', 'Price: The item's current price', 'Category', 'Availability', 'Print Routing', 'Stock dropdown' - a single price value per item. The per-item Options list controls channel by availability only ('Item available online', 'Item available on Slice Register'), never by price, and category availability can be set to specific days of the week while price cannot. The only price dimension Slice documents is per size (and per-size modifier pricing). There is no location group to price against - locations are a flat selector - so no price tier by location group, order channel or daypart exists. https://slice.com/knowledge-hub/owners-app-web-menu/ · retrieved 2026-08-08

multi-location-scheduled-publish differentiator

Checked knowledge-hub/owners-app-web-register (Register Discounts carry a 'Start Date' and optional 'End Date'; promo codes carry an expiration in knowledge-hub/owners-app-manage) and knowledge-hub/owners-app-manage (Hours offers 'View All Scheduled Changes' and 'Schedule Closing' with a future date). So future-dating exists for discounts and trading hours only. Menu and price changes have no scheduling field in knowledge-hub/owners-app-web-menu, and menu changes instead propagate by a manual pull - 'Changes made on this page will not take effect until each iPad downloads the updated menu through the Download Changes From Slice option'. No article mentions per-location timezone interpretation or rolling an activated change back. Unknown rather than no: the multi-shop publish surface is undocumented, so I cannot enumerate what a corporate view would offer.

multi-location-new-store-template differentiator

knowledge-hub/slice-register-getting-started documents onboarding as a call with an Implementation Lead who will 'Review your current POS system, internet setup, and network connection', 'Assist with training, menu configuration' and 'Verify any existing contracts with other POS or card processors' - a bespoke human build, with an on-site install; slice.com/pricing prices this as a '$1,000 implementation fee' on the Family Membership. No article mentions cloning, templating or copying a configuration from an existing shop. On time-to-open, the vendor's own FAQ on slice.com/products/point-of-sale-for-pizza-shops/ asks 'How long does setup take?' and answers 'Our team comes to your shop, sets up your hardware, and trains your staff in person... We stay until your team feels ready' - no figure. Left unknown because neither page is an enumeration of the provisioning toolset.

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

knowledge-hub/owners-app-web-register enumerates the whole permission model - Register Users, Register Permission groups, and every grantable permission under five categories (Orders, Shop Operations, Cash Management, Menu Availability, Shop Availability) - and every one is an action on one shop's Register; there is no tenant, owner-of-record, or corporate-visibility concept. The merchant Online Restaurant Agreement at slice.com/online-restaurant-agreement/ mentions franchising once, and only as a restaurant warranty that its use of the Platform 'does not and will not conflict with Restaurant's obligations to any third parties, including, without limitation, franchise agreements' - it defines no franchisor party. Left unknown because Slice never describes a multi-entity account structure at all, so the absence of a franchisor/franchisee split is undocumented rather than enumerated.

multi-location-royalty-calculation differentiator

Read knowledge-hub/owners-app-web-financials in full (Online Orders, Register Orders, statements with 'Online Order Activity: Sales Subtotal / Tax Collected / Delivery Fees', payout detail) and knowledge-hub/owners-app-report ('In this Article: Orders report, Scheduled Orders report, Statements, End of day report, Sales Report, Insights'). Every fee construct is a Slice-to-restaurant fee; there is no royalty, ad fund, marketing fee, royalty basis, or fee schedule object. Searched the full merchant Online Restaurant Agreement at slice.com/online-restaurant-agreement/ for 'royalt' - zero hits. Left unknown because these are the shop's own financial reports, not an enumeration of a franchise product Slice never claims to sell.

multi-location-royalty-collection

The only automated debit mechanics Slice documents are its own: the merchant Online Restaurant Agreement at slice.com/online-restaurant-agreement/ lets Slice 'obtain payment from Restaurant's credit card, bank account or other approved facility' or 'deduct such amount from the Merchant Deposit Account, Sales Proceeds or Grand Total' for hardware and other fees, and knowledge-hub/settings covers only 'Goods payments' and 'Payout management' (a debit card for faster payouts). knowledge-hub/owners-app-web-financials documents statements as Slice-to-shop payouts. Nothing in the 45 Knowledge Hub articles, the 30 release notes or the agreement mentions royalties, franchisee accounts, or franchisee-visible statements, so there is no collection mechanism to assess - left unknown for want of any enumerated franchise surface.

multi-location-consolidated-reporting

Slice's three back-office reporting surfaces are each enumerated and each is scoped to one shop. Owner's App Report lists its entire contents - 'In this Article: Orders report, Scheduled Orders report, Statements, End of day report, Sales Report, Insights' - all described as 'your shop's performance'. Owner's App (web) Analytics enumerates Filters/Orders/Sales by Day/Top and Least Selling Menu Items/Customers, and Owner's App (web) Financials enumerates Online Orders, Register Orders and Statements. Viewing is explicitly one location at a time: the dashboard 'location selector lets you switch between multiple shop locations... tap the selector to choose the location you want to view'. No aggregate-across-locations view, no store-vs-store ranking, and no variance flags exist in any of the three. https://slice.com/knowledge-hub/owners-app-report/ · retrieved 2026-08-08

multi-location-normalized-item-rollup differentiator

Item-level reporting is documented in knowledge-hub/owners-app-web-analytics ('Top Selling Menu Items', 'Least Selling Menu Items') and knowledge-hub/owners-app-report (End of day 'Products: Identify your most and least popular menu items'), and both are scoped to the one shop selected in the location dropdown. The item record enumerated in knowledge-hub/owners-app-web-menu carries no corporate/parent identifier - Item name, Price, Category, Availability, Print Routing, Stock. Left unknown because no Slice document describes cross-location reporting in any form, so there is no enumeration of a rollup model to find this missing from.

multi-location-cross-location-giftcard

The order-entry guide enumerates the tenders exhaustively: 'There are three ways to pay for an order: Card, Cash, and Other.' Other is defined as the catch-all for 'anything that is not cash or card, e.g., check, paper gift certificate, running your own invoices, etc.' - i.e. a gift certificate is rung as an untracked generic tender. There is therefore no gift card account, no stored balance, no outstanding-liability figure in any report (Owner's App Report and Financials enumerate their contents and none includes gift liability), and nothing to redeem or settle between locations. https://slice.com/knowledge-hub/slice-register-order-entry/ · retrieved 2026-08-08

multi-location-cross-location-loyalty

Slice's pizza-points loyalty lives in the Slice consumer app and follows the diner across all Slice shops — marketplace-wide rather than brand-wide. Whether a multi-shop owner gets a unified brand-level profile is not documented. https://slice.com/products/online-pizza-ordering-system/ · retrieved 2026-08-01

multi-location-multi-brand differentiator

Searched the whole retrievable corpus (45 Knowledge Hub articles, 30 release notes, 26 FAQs via slice.com/wp-json/wp/v2/, plus slice.com/online-restaurant-agreement/) for virtual brand, multi-brand and second concept - zero occurrences. The docs assume one shop identity per account: knowledge-hub/register-shop-status and knowledge-hub/owners-app-getting-started treat 'your shop logo' and shop status as singular, and System Profiles in knowledge-hub/owners-app-web-register are per-iPad stations ('You do not need more profiles than iPads running the Register app in your shop'), not brands. Left unknown because no page enumerates receipt branding or revenue-segmentation options, so this is silence, not a documented limit.

multi-location-multi-tax-jurisdiction

Tax is configured per shop and Slice withholds and remits marketplace-facilitator sales tax 'where applicable'. Multiple simultaneous rates, inclusive-vs-exclusive handling and exemptions are not documented. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-01

multi-location-config-audit-log differentiator

The Permissions Log in the Owner's App (web) records 'Actioned By', 'Authorized By', 'Register Profile Name', 'Task' (examples given: 'Turn off tax at order level', 'Line item clear before send'), 'Status' and a timestamped 'Date', and the doc calls it 'a clear audit trail for tracking sensitive activities performed and approved within your system'. Shortfall: it logs permissioned register ACTIONS, not configuration objects - edits to prices, tax rates, permission groups and discounts are nowhere described as logged - and no export, query, retention or immutability guarantee is documented, nor any corporate/above-store view; the log is scoped to the one shop selected in the location dropdown. https://slice.com/knowledge-hub/owners-app-web-register/ · retrieved 2026-08-08

multi-location-enterprise-api differentiator

No API of any kind is published, so no cross-location authenticated data call exists.

multi-location-central-labor-policy

No labor module exists to configure or enforce.

hardware-commodity-devices differentiator

The POS runs on a standard iPad and prints to off-the-shelf Epson units, but hardware is supplied bundled with the Family Membership; buying your own iPad and running Register on it is not documented as supported. https://slice.com/knowledge-hub/slice-register-getting-started/ · retrieved 2026-08-01

hardware-os-platforms

iPad/iPadOS is named as the Register client and the Owner's App ships for iOS and web. No iPad model requirement, minimum iPadOS version, or device spec is published. https://slice.com/knowledge-hub/slice-register-getting-started/ · retrieved 2026-08-01

hardware-handheld-purpose-built

The included-hardware list is Register, Stand, Payment Terminal, Cash Drawer, Receipt Printer, Kitchen Printer, Network Kit. No handheld. Mobility is a second iPad plus the NYC1 Mobile Card Reader. https://slice.com/pricing · retrieved 2026-08-01

hardware-handheld-battery-swap differentiator

No handheld device exists, so no battery rating is published.

hardware-handheld-lte

Searched all 45 Knowledge Hub articles, 30 release notes and 26 FAQs pulled from slice.com/wp-json/wp/v2/ for cellular, LTE, SIM and 4G/5G - zero occurrences. Every connectivity instruction is Wi-Fi only: knowledge-hub/online-ordering-getting-started ('Connect to Wi-Fi: Go to Settings > Wi-Fi and connect to your shop's network'), knowledge-hub/register-settings (troubleshooting starts 'Check the WiFi connection'), and the FAQ on internet issues ('restart your iPad and router'). Slice's nearest thing to a handheld is the Order Manager Kit, documented at knowledge-hub/order-manager-kit as a second in-store iPad on a stand, and the Slice Driver App, which runs on the driver's own phone. slice.com/online-restaurant-agreement/ puts connectivity wholly on the merchant ('Restaurant is responsible for obtaining and maintaining a high-speed internet connection') and disclaims liability for outages, which is consistent with no vendor failover but does not enumerate device connectivity options - hence unknown, not no.

hardware-offline-mode

Annex 3 (Slice POS Terms) of the Online Restaurant Agreement states it directly: 'Except as provided in an Order Form, Restaurant may use Slice Register and Slice Standalone Payments to conduct point of sale activities offline. Transactions initiated offline will be queued and submitted for authorization when Internet connectivity to the applicable Hardware is restored. Slice reserves the right to limit the number of offline transactions that may be queued. Unless otherwise specified in an Order Form, offline transactions may not exceed $100 per transaction. Restaurant assumes all risk, responsibility and liability associated with any transaction that Restaurant conducts while Slice Register... is offline.' Shortfall: that is the contract, not operating documentation. No Knowledge Hub article covers offline behaviour at all; nothing states whether order entry, kitchen printing or cash-sale recording continue, the queue depth limit is unstated, and no degrade list for loyalty lookup or refunds is published. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

hardware-kds

Corrected 2026-08-08: the earlier note's 'no KDS product appears in the catalog' is withdrawn - https://slice.com/family-membership/ does list 'Discounted kitchen displays & kiosks (coming soon)' and the unlinked draft page https://slice.com/pricing-test/ lists 'Kitchen Display System' under Family Membership. What carries the no is that neither describes a shipping first-party product. Slice's POS page answers 'What hardware is included with Slice Register?' with a closed list - 'It comes with an iPad interface, kitchen printer, cash drawer, receipt printer, credit card terminal, router, and delivery card reader' - no display; /pricing's Hardware key-features list is Register and Stand, Payment Terminal, Cash Drawer, Receipt Printer, Kitchen Printer, Network Kit; and Slice's own wording is 'coming soon' and 'discounted', i.e. a future reseller discount, not a first-party product today. The strings 'kitchen display', 'KDS' and 'bump' occur zero times across the 45 Knowledge Hub articles, 30 release notes and 26 FAQs pulled from the WP REST API on 2026-08-08, so nothing establishes station routing or course/fire timing either. Re-check when the 'coming soon' item ships. https://slice.com/products/point-of-sale-for-pizza-shops/ · retrieved 2026-08-08 adversarially verified

hardware-kiosk differentiator

No kiosk in the product catalog or hardware bundle.

hardware-drive-thru

No drive-thru hardware, menu boards, or headset integration.

hardware-printer-compatibility

Two Epson models are named and configurable (TM-m30III for receipts, U220 for kitchen), with discovery, naming, deletion and test-print. Only one manufacturer is documented and no compatibility list is published. https://slice.com/knowledge-hub/register-settings/ · retrieved 2026-08-01

hardware-peripherals

Cash drawer, receipt printer, kitchen printer, payment terminal, mobile card reader, stand and caller-ID line are documented. Barcode scanners, scales and customer-facing displays are not, and no compatibility list is published. https://slice.com/pricing · retrieved 2026-08-01

hardware-p2pe-terminal

Card entry is on a dedicated reader, not the tablet: knowledge-hub/register-settings documents a 'Payment Terminals' screen that lets you 'set a default card reader for orders taken on this iPad', and Annex 3 of the Online Restaurant Agreement states 'Slice does not receive full payment card details in its provision of Slice Register and Slice Standalone Payments. Slice has engaged a Processor that conducts payment processing.' Annex 7 identifies the acquiring stack: an 'ACQUIRING ADDENDUM - WELLS FARGO BANK, N.A. (USA)' for merchants who 'entered into a Merchant Agreement with Adyen N.V.' with 'card transactions acquired via Adyen'. Shortfall: no PTS-listed model is named for the counter terminal (the only model named anywhere is the 'NYC1 Mobile Card Reader' for delivery and MOTO, in knowledge-hub/order-manager-kit), no validated P2PE listing is cited, and no merchant SAQ type is stated on any slice.com page - the strings PCI, P2PE and SAQ do not occur in the agreement or in any of the 45 Knowledge Hub articles. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

hardware-tap-to-phone differentiator

Mobile acceptance is documented as requiring the separate NYC1 Mobile Card Reader. https://slice.com/knowledge-hub/order-manager-kit/ · retrieved 2026-08-01

hardware-pricing-transparency differentiator

No per-SKU hardware price is published — hardware is bundled into the $399/mo Family Membership at no separate charge, which is arguably better for the buyer but fails the per-SKU transparency test. https://slice.com/pricing · retrieved 2026-08-01

hardware-ownership-vs-lease differentiator

Annex 4 (Hardware Terms) answers this in both directions. Default: 'Any Hardware (including, without limitation, printers, tablets or other hardware) provided by Slice will remain Slice's sole property'; 'Restaurant shall have no right, title or interest in or to the Hardware except the right to possession and use thereof during the applicable Order Form Service Term'; the merchant pays 'the non-refundable monthly fee set forth in the applicable Order Form (Hardware Fee)' and must return the kit on termination. An outright-purchase alternative exists as a contractual category: provisions 7-10 apply to 'any Hardware designated as purchased (or other similar term) on the Order Form', where 'Title and all risk of loss of or damage to the Designated Hardware will pass to Restaurant upon delivery by Slice to the carrier.' Shortfall: which mode a given shop gets is set on a non-public Order Form, and slice.com/pricing bundles 'Register and Stand, Payment Terminal, Cash Drawer, Receipt Printer, Kitchen Printer, Network Kit' into the Family Membership without stating that the kit falls under the rental terms. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

hardware-usable-after-churn differentiator

For subscription-provided hardware, Annex 4 answers the question and answers it negatively: 'Restaurant shall only use the Hardware in connection with, as applicable, the Platform or other Services provided by Slice', and 'Upon termination of the applicable Order Form or this Agreement for any reason... Restaurant shall promptly return the Hardware to Slice... in good working order (at Restaurant's expense)', backed by a restocking fee 'of up to $100.00' and a Failure to Return Fee 'of up to $349.00' per item. Shortfall: for Hardware 'designated as purchased', title passes to the restaurant on delivery, but the agreement never states whether that hardware runs any other software after cancellation, and no Slice document addresses software locking or remote disablement in either direction. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

hardware-rma-sla differentiator

Annex 4 publishes a warranty term for purchased Designated Hardware: 'Slice warrants that for six (6) months after the installation date (Warranty Period), the Designated Hardware will perform in accordance with the specifications provided together with the Designated Hardware', and the remedy is shaped like an advance exchange - the merchant returns the faulty unit 'within thirty (30) days of Restaurant's receipt of the replacement Designated Hardware', with replacements 'warranted for the unexpired portion of the original Warranty Period'. Shortfall: no turnaround commitment is stated for the replacement itself (nothing like next-business-day or a depot SLA), 'Restaurant is responsible for all costs of shipping in connection with any repair or replacement', and for subscription-provided Hardware the same annex 'EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS, EXPRESS OR IMPLIED, IN CONNECTION WITH THE HARDWARE', with installation explicitly excluding 'warranty service or support'. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

hardware-byod

BYOD is documented for delivery staff: 'To download the Slice Driver App, go to the App Store (iOS, Android) on your phone and search for Slice Driver', 'Each driver needs a unique email address to log in', and drivers take card-present payments on that personal phone via a paired Bluetooth reader. The documented prerequisites are a security model of sorts - 'Bluetooth is turned on in their phone's settings', 'The phone has a passcode or Face ID set up', and 'The reader is compatible with iPhones (iOS 17 and later) and Android phones (Android 7 and later)'. Shortfall: only the delivery app is BYOD; the ordering Register app runs on Slice-supplied iPads (knowledge-hub/slice-register-getting-started) and the Order Manager Kit ships its own iPad. Driver logins cannot be self-provisioned - 'contact Slice Support at (888) 974-9928 to add your driver's login' - and sit outside the Register Employee Permissions groups enumerated in knowledge-hub/owners-app-web-register. No MDM, remote wipe, session timeout or data-at-rest policy is documented for the personal device. https://slice.com/knowledge-hub/register-slice-driver-app/ · retrieved 2026-08-08

hardware-remote-device-management differentiator

The entire back-office device surface is enumerated: 'The Register dropdown provides access to tools and settings for managing your Slice Register system' - Register Menu Layout, Employee Permissions, Printer Settings, Register Discounts, Tip Settings, System Profiles and a User Guide link. None is a device console; System Profiles only allocates one profile per iPad ('Each iPad using Slice Register will need its profile. You do not need more profiles than iPads running the Register app in your shop'). Rollout is explicitly pull-based and per-device: 'Changes made on this page will not take effect until each iPad downloads the updated menu through the Download Changes From Slice option', and knowledge-hub/register-settings repeats 'If you use multiple Register iPads, you must download changes on each device.' The only status indicator lives on the device itself (Settings > Slice Support > 'View your Connection Status to confirm your Register is online and connected'). There is no fleet view of terminals, printers or KDS, no remote reboot, no software-version visibility and no staged rollout. https://slice.com/knowledge-hub/owners-app-web-register/ · retrieved 2026-08-08

hardware-callerid-integration

Verified: 'Their phone number appears on your screen, and if they've ordered before, you'll see their name and order history.' The dossier's limitations are real and if anything understated — the doc also notes the customer info disappears once the call ends and simultaneous calls queue rather than ring independently. https://slice.com/knowledge-hub/register-caller-id/ · retrieved 2026-08-01 adversarially verified

extensibility-public-api-docs

Upheld and re-sourced, this being the open-API conclusion-flipping cell. I fetched developers.slicelife.com myself: it serves Slice's consumer marketplace content — city browsing, pizza types, support, careers — with no API reference, no OpenAPI spec, no sandbox and no developer resources of any kind. The Knowledge Hub index has no API section either. The absence is affirmative rather than merely unfound: the host that would carry a developer portal exists and carries none. https://developers.slicelife.com · retrieved 2026-08-02 adversarially verified

extensibility-api-access-cost differentiator

There is no API to price.

extensibility-partner-revshare

No partner or marketplace commercial terms published. The only public bounty is $1,500 per referred pizzeria location, which is an operator referral program. https://slice.com/ · retrieved 2026-08-01

extensibility-free-sandbox differentiator

No sandbox or test environment exists without an API.

extensibility-oauth-partner-apps

No OAuth, no scopes, no operator-granted app permissions documented.

extensibility-webhooks-push

No outbound event delivery documented.

extensibility-webhook-reliability differentiator

No webhooks exist, so no signing, retry, or replay behavior.

extensibility-order-injection-api

Third-party orders do inject into Order Management, but through Slice-operated private integrations — no public write API is offered to an operator or third-party developer. https://slice.com/knowledge-hub/register-third-party-orders/ · retrieved 2026-08-01

extensibility-menu-write-api differentiator

Menu is editable only through the Owner's App UI; no API.

extensibility-data-symmetry differentiator

No API exists in either direction.

extensibility-published-rate-limits

No API, no rate limits.

extensibility-doordash-preferred differentiator

Conclusion correct, sourcing invalid — a Slice page cannot evidence a DoorDash program roster. Independently confirmed against DoorDash's own newsroom: the 2026 DPIP cohort is Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper, and DPIP requires live item availability and order-ready notifications, both of which Slice's own docs say it cannot do. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

extensibility-first-party-delivery-integrations differentiator

'Integrates with 30+ delivery apps including DoorDash, Grubhub, and Uber Eats' with no separate tablet or re-keying. Slice never states whether these are first-party certified or brokered through paid middleware, and the integration is one-way inbound only. https://slice.com/products/point-of-sale-for-pizza-shops/ · retrieved 2026-08-01

extensibility-middleware-compatibility

Slice does name middleware endpoints, but in the opposite direction to the claim. Online Ordering setup lists order transmission methods as 'iPad or other order transmission methods (Square, Clover, Checkmate POS, Fax, or Phone TM)', and knowledge-hub/settings documents a 'Point of sale integrations' section where 'Available integrations include Square, Clover, and Facebook'. Shortfall: these route Slice Online orders OUT to whatever POS the shop already runs, for shops that are not on Slice Register. Slice Register itself is documented nowhere as a supported endpoint for Deliverect, Chowly, Otter or Checkmate; knowledge-hub/register-third-party-orders describes the marketplace integration as one-way with menus 'controlled by Slice'; and there is no public API - I re-tested the host the record cites, and https://developers.slicelife.com returns the same 51.5KB consumer-storefront shell as a fabricated subdomain (zzznotreal9.slicelife.com, also HTTP 200, byte-identical layout), so it is a wildcard, not a developer portal. https://slice.com/knowledge-hub/online-ordering-getting-started/ · retrieved 2026-08-08

extensibility-accounting-connectors

No QuickBooks Online or other GL connector is named anywhere. Accounting output is manual CSV download from the Owner's App Financials section. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-01

extensibility-payroll-export

One named destination exists where previously none did: Homebase, integrated as a Time Clock app on the Register iPad. Shortfall: the claim asks for at least two named payroll providers, and the hours are captured directly in the partner's system rather than exported by Slice — there is no Slice-side export file, no documented field mapping, and no second provider. https://slice.com/knowledge-hub/homebase-partnership/ · retrieved 2026-08-02

extensibility-bi-data-warehouse differentiator

CSV download only; no scheduled export to a customer-controlled destination.

extensibility-app-marketplace

'Integrations' is a checkbox on the pricing page, but no browsable, self-install integrations marketplace exists on any Slice property. https://slice.com/pricing · retrieved 2026-08-01

extensibility-custom-fields-scripting

No custom fields or hosted scripting surface documented.

extensibility-headless-embedded

No headless or embedded transaction-engine mode; no API to drive it.

extensibility-api-versioning-deprecation

No API, no changelog, no deprecation policy. The Register app has a 'What's New' in-app notice, which is not an API policy. https://slice.com/knowledge-hub/register-settings/ · retrieved 2026-08-01

extensibility-data-portability-exit differentiator

Self-serve CSV download exists for Orders, Order Activity, Tax, Sales Mix and Sales Summary. Customers, loyalty balances, menu and payments metadata are not documented as exportable, and no contract-end export process is described. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-01

reliability-offline-order-entry

Annex 3 (Slice POS Terms), Offline Transactions: 'Restaurant may use Slice Register and Slice Standalone Payments to conduct point of sale activities offline. Transactions initiated offline will be queued and submitted for authorization when Internet connectivity to the applicable Hardware is restored.' Shortfall: offline operation is documented only as a contractual permission covering order-taking and queued payment. Neither the agreement nor any of the 45 Knowledge Hub articles says kitchen ticket routing or customer receipt printing continues offline, and the same Annex states 'Slice Register requires a consistent wired or wireless broadband connection to the Internet.' https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

reliability-offline-card-auth differentiator

Annex 3 (Slice POS Terms), Offline Transactions: 'Transactions initiated offline will be queued and submitted for authorization when Internet connectivity to the applicable Hardware is restored.' That is store-and-forward, not a cash-only fallback. Limits are stated in the same clause: 'Slice reserves the right to limit the number of offline transactions that may be queued' and 'Unless otherwise specified in an Order Form, offline transactions may not exceed $100 per transaction.' https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

reliability-offline-decline-liability differentiator

Annex 3 (Slice POS Terms), Offline Transactions: 'Restaurant assumes all risk, responsibility and liability associated with any transaction that Restaurant conducts while Slice Register and/or Slice Standalone Payments is offline.' The same clause publishes the cap: 'offline transactions may not exceed $100 per transaction' unless an Order Form specifies otherwise, plus 'Slice reserves the right to limit the number of offline transactions that may be queued' (a reserved rather than numeric cumulative limit). Loss on a post-restoration decline sits entirely with the merchant. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

reliability-lan-degraded-multi-terminal differentiator

Re-checked against sources the earlier pass did not have. Read Annex 3 of the Pizzeria Agreement (slice.com/online-restaurant-agreement/) in full: its Offline Transactions clause is written per device -- transactions are queued until 'Internet connectivity to the applicable Hardware is restored' -- and says nothing about check or table state shared between iPads. Pulled all 45 Knowledge Hub articles, 30 release notes and 26 FAQs via slice.com/wp-json/wp/v2/ (epkb_post_type_1, epkb_post_type_2, echo_kb_faq). register-settings documents only a manual cloud pull ('Download changes from Slice... If you use multiple Register iPads, you must download changes on each device') and order-manager-kit documents a second back-of-house iPad, but neither describes LAN-only shared state nor per-terminal islanding during an outage. Suggestive of cloud-mediated sync rather than a LAN, but that is inference, not documentation.

reliability-local-transaction-engine differentiator

Annex 3 (Slice POS Terms) documents a device-local store-and-forward queue: offline-initiated transactions are 'queued and submitted for authorization when Internet connectivity to the applicable Hardware is restored', capped at $100 per transaction. Shortfall: that queue is the only local processing Slice documents. No on-premise server, edge appliance or local transaction engine appears in the agreement or in any of the 45 Knowledge Hub articles; the same Annex states 'Slice Register requires a consistent wired or wireless broadband connection to the Internet', and the only on-site network device mentioned is a 'Slice-provided wireless router' which Slice expressly says does not provide Internet access. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

reliability-offline-kds-printing

The earlier rationale reasoned from 'printers are LAN-attached'; that premise is wrong. slice.com/knowledge-hub/online-ordering-getting-started/ says 'All printers come preconfigured to work with Bluetooth, which is the recommended setup for most shops' (Epson TM-M30III; 'Non-Epson printers are not supported'), and register-settings falls back to a same-network check only when a printer is not discovered. Either way, Annex 3 of the Pizzeria Agreement (slice.com/online-restaurant-agreement/) covers offline behaviour solely in terms of queued payment authorization and is silent on printing, and no Knowledge Hub article, release note or FAQ (all 45/30/26 pulled via slice.com/wp-json/wp/v2/) states whether kitchen tickets print while the internet is down. Slice ships no KDS. Bluetooth pairing makes local printing plausible; plausible is not documented.

reliability-printer-fallback

Read slice.com/knowledge-hub/register-settings/ end to end. Its Receipt Settings section enumerates the printer surface -- 'Discover, install, rename, delete, and test receipt printers', automatic-printing toggles for customer receipts and kitchen tickets on online and third-party orders, and font and ticket-content options -- with no backup-printer assignment, no failover and no unreachable-printer alert. online-ordering-getting-started covers manual test prints and Bluetooth pairing only, and the FAQ 'Can I connect a printer to my tablet?' limits supported models to the Epson TM-M30III. The Pizzeria Agreement is silent on printing. A settings page that does not claim to be exhaustive is not proof that automatic failover is absent, so this stays unknown rather than no.

reliability-sync-conflict-handling

slice.com/knowledge-hub/register-settings/ documents the only sync primitive Slice publishes: 'Download changes from Slice: Sync updates made in the Slice Owner's App (web) to this iPad. If you use multiple Register iPads, you must download changes on each device.' That is a one-way manual pull for menu and settings, with no statement of what happens to simultaneous edits on two devices, or to an order edited on the Register and on the Order Manager iPad at the same time. Also read order-manager-kit (which explicitly allows editing orders and issuing refunds from a second iPad), register-order-management, and Annex 3 of the Pizzeria Agreement -- none states a conflict-resolution rule such as last-write-wins, merge or operator prompt.

reliability-offline-feature-matrix

I checked independently. Register Settings offers only a Slice Support 'Connection Status' check to 'confirm your Register is online and connected'; the in-store-ordering product page and the POS page contain nothing on outages. An exhaustive operator Knowledge Hub with zero offline content is affirmative evidence that no offline matrix is published — though the underlying capability itself remains correctly scored unknown elsewhere. https://slice.com/knowledge-hub/register-settings/ · retrieved 2026-08-01 adversarially verified

reliability-public-status-page

Probed hosts rather than searching. status.slice.com does not connect; status.slicelife.com returns the same ~51.5KB consumer-storefront shell that every *.slicelife.com wildcard returns, so it is not a status page; slicelife.statuspage.io redirects to atlassian.com/software/statuspage (an unclaimed subdomain); slice.statuspage.io returns a page titled 'Slice Status - Page Inactive', which suggests a Statuspage was provisioned and then disabled but cannot be attributed to Slice Solutions, Inc. rather than to some other company named Slice. The complete slice.com page list (76 pages, via wp-json/wp/v2/pages) contains no status, trust or security page, and the only availability feature documented anywhere is the in-app 'Slice Support: View your Connection Status' check in register-settings. No public per-component status page located; the attribution gap is what keeps this unknown.

reliability-contractual-uptime-sla differentiator

The standard Pizzeria Agreement (updated 2026-03-05) is published in full and contains no uptime percentage, no service level and no service credit -- the strings 'service level' and 'service credit' do not occur in its ~178KB of text. The General Terms state the opposite of a commitment: 'SLICE DISCLAIMS ANY WARRANTY THAT THE PLATFORM WILL BE AVAILABLE AT ALL TIMES, FREE OF ERRORS OR THAT EVERY ERROR IN THE PLATFORM OR PROBLEM RAISED BY RESTAURANT WILL BE RESOLVED. THE PLATFORM, THE SERVICES, AND THEIR COMPONENTS... ARE PROVIDED "AS IS" AND "AS AVAILABLE."' Annex 3 adds that Slice bears no liability for 'any termination, suspension, delay or disruption of Slice Register' arising from connectivity issues. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

reliability-incident-postmortems

Pulled all 30 release notes (slice.com/wp-json/wp/v2/epkb_post_type_2, dated 2025-10-09 and 2026-02-05) and all 45 Knowledge Hub articles: every one is a feature announcement or a how-to, none is an outage report or root-cause summary. There is no status page to host postmortems (see reliability-public-status-page: slice.statuspage.io reads 'Page Inactive'), and the complete slice.com page list has no engineering or trust section. Not checked exhaustively: the slice.com/blog/ post archive, which is marketing-led but was not read post by post, so this stays unknown rather than no.

reliability-247-live-support

Confirmed verbatim: 'We answer the phone 24/7/365 — for you and your customers' and 'No AI, robots, or chat bots — fully human support'. Included on both memberships. https://slice.com/support/24-7-365-customer-support/ · retrieved 2026-08-01 adversarially verified

reliability-onsite-install differentiator

Citation re-pointed 2026-08-08: slice.com/in-store-ordering no longer exists in the site's page index (all 71 pages enumerated via /wp-json/wp/v2/pages). Both quotes survive on the live Slice Register product page - body copy 'Our team comes to your shop to install your hardware and train your staff in person. And whenever you need help - day or night - a real human always answers', with badges LOCAL TEAMS / ON-SITE SETUP / PERSONALIZED TRAINING / 24/7 SUPPORT, and the FAQ 'Our team comes to your shop, sets up your hardware, and trains your staff in person. You do not need to do a long self-install. We stay until your team feels ready.' Corroborated at https://slice.com/support/full-service-setup-and-training/: 'Our in-person implementation team ensures that your equipment is properly set up and ready to handle your next dinner rush' and 'white-glove implementation, a dedicated Account Manager, and 24/7/365 live support are built in'. Held at partial under the differentiator grade floor: these are vendor product pages, not documentation - nothing in the 45-article Knowledge Hub describes the on-site process. Shortfall unchanged: no coverage map or market list ('We also have in-market teams available to help in person' is unquantified), no published go-live timeline, and the service reaches only $399 Family shops, since Point of Sale and the $1,000 implementation fee appear only in that column on https://slice.com/pricing/. https://slice.com/products/point-of-sale-for-pizza-shops/ · retrieved 2026-08-08 adversarially verified

reliability-menu-build-service differentiator

'Full-service setup and dedicated account management' and 'Fast setup. Hands-on training', backed by a $1,000 implementation fee. Slice does not explicitly state that it builds the initial menu, nor publish a go-live timeline. https://slice.com/support/24-7-365-customer-support/ · retrieved 2026-08-01

reliability-hardware-replacement-sla

Annex 4 (Hardware Terms) section 8 gives a six-month limited warranty on 'Designated Hardware' with an advance-exchange flow: Slice ships the replacement first and 'Restaurant shall return the malfunctioning Designated Hardware to Slice within thirty (30) days of Restaurant's receipt of the replacement Designated Hardware.' Shortfalls: (1) no turnaround time is stated for Slice's side -- the 30 days is the merchant's return deadline, not a dispatch commitment; (2) it applies only to Designated Hardware, meaning hardware acquired before 16 April 2024 or 'designated as purchased... on the Order Form'; (3) for the standard rented hardware Slice merely 'may elect to replace any Hardware with such other Hardware as Slice deems appropriate', and Annex 4 section 5 'EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS, EXPRESS OR IMPLIED, IN CONNECTION WITH THE HARDWARE'. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

reliability-backup-restore

Checked both limbs of the claim. Self-service: owners-app-web-financials and owners-app-web-customers document CSV report generation and a customer-database export, but no snapshot, no restore and no point-in-time recovery. Contract: the Pizzeria Agreement's 'Portability and Deletion of Restaurant Data' clause obliges Slice, on request within 30 days of termination, to 'make Restaurant Data available to Restaurant for export or download' -- a portability right, not a backup/restore feature. RPO/RTO: the words 'backup', 'recovery point' and 'recovery time' do not appear in the 178KB agreement, and Annex 4 expressly excludes 'virus removal or disaster recovery' from installation services. Neither limb is met and neither is affirmatively denied.

reliability-pci-dss-4-attestation

Enumerated the whole first-party corpus rather than searching it: all 76 published slice.com pages (wp-json/wp/v2/pages), all 45 Knowledge Hub articles, all 30 release notes, all 26 FAQs, and the full 178KB Pizzeria Agreement. The strings 'PCI', 'attestation', 'AoC' and 'P2PE' occur zero times in any of them, and there is no trust, security or compliance page in the page list (slice.com/security, /legal and /terms return 403 and are absent from it). The only security statement Slice publishes is the FAQ 'How secure are payments?': 'Slice partners with industry-leading payment processors to ensure all transactions are secure and encrypted.' Annex 7 names the acquiring chain (Adyen N.V., with Wells Fargo Bank, N.A. as acquirer of record), but their compliance is not Slice's attestation. An AoC is customarily given to merchants on request rather than posted publicly, so this stays unknown rather than no.

reliability-mfa-role-based-access

Role-based access is real — per-action permissions and a four-digit PIN for login and manager approval. But a four-digit PIN is single-factor, and MFA on Owner's App back-office logins is not documented. https://slice.com/knowledge-hub/register-employee-permissions/ · retrieved 2026-08-01

reliability-self-serve-training

A free, public, login-free Knowledge Hub covers Register, Online Ordering, Owner's App and Delivery, and Slice markets an 'Owner Learning Center'. No terminal training/practice mode is documented. https://slice.com/knowledge-hub/ · retrieved 2026-08-01

reliability-failover-terminal-role differentiator

slice.com/knowledge-hub/order-manager-kit/ describes the only role concept Slice publishes: 'In Owner's Portal, you can now set profiles as either "Front of House" or "Back of House" profiles. If you set a profile as "Back of House", it will automatically open up to the Order Management page' -- a cloud-side profile that changes the landing screen, not a master/server role. No article describes a primary terminal, a local server, or promotion of a secondary device when the primary fails, and register-settings offers no such option. Annex 3 of the Pizzeria Agreement treats each unit independently ('Internet connectivity to the applicable Hardware'). Nothing found either asserting or excluding automatic role failover.

reliability-cellular-backup

Annex 3 of the Pizzeria Agreement (slice.com/online-restaurant-agreement/) is the only place the shipped network gear is described: 'Slice Register requires a consistent wired or wireless broadband connection to the Internet. Even where the applicable Order Form includes a Slice-provided wireless router, Slice does not provide Internet access or any related services needed to access the Internet.' The words 'cellular', 'LTE', '4G', '5G' and 'SIM' occur zero times in the agreement and zero times across the 45 Knowledge Hub articles, 30 release notes and 26 FAQs pulled from slice.com/wp-json/wp/v2/. The router is therefore documented as a LAN device with connectivity explicitly the merchant's responsibility, but no source states that automatic cellular failover is unavailable.

commercial-month-to-month-contract differentiator

The pricing page labels both memberships 'Month-to-Month' with 'Zero locked-in contracts' and states no minimum term, but that is a sales page rather than documentation. Named shortfalls: no merchant subscription agreement is publicly readable - the public Terms of Service (https://slice.com/terms-of-service/, retrieved 2026-08-06) says only 'You may cancel your account at any time by sending us an email' and states that services 'may be governed by other terms and conditions you agree to when you sign up for such Services', so the actual term, renewal and notice provisions for the paid $399/month Family membership sit in unpublished Services Terms; and the disposition on cancellation of the $1,000 implementation fee and the bundled hardware (iPad, Epson printers, Verifone terminal, Meraki router) is undisclosed, which is why the sibling early-termination cell remains unknown. Searched: slice.com/pricing, slice.com/terms-of-service, slice.com/knowledge-hub help centre (no billing, subscription or cancellation article), sliceregister.com, and the sites.google.com/slicelife.com Register help site, which redirects to a Google login. https://slice.com/pricing/ · retrieved 2026-08-06

commercial-no-early-termination-fee differentiator

General Terms, 'Early Termination Fee': if the Restaurant terminates a Service before the end of the initial or renewal Order Form Service Term other than for Slice's material breach, it must immediately pay amounts due (including Annex 4 hardware return fees) plus 'an amount equal to the aggregate fees (calculated without any discounts) that would otherwise have been payable by Restaurant during the initial Order Form Service Term or relevant renewal term, as applicable, for all terminated Services (including, without limitation, any subscription Fees and Hardware Fees, and excluding per transaction fees)'. The agreement calls this 'a reasonable estimate of the damages' and 'a genuine estimate of damages and not a penalty' -- liquidated damages -- and adds that paying it 'shall not limit Slice's right to seek other remedies available under this Agreement or at law'. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

commercial-autorenew-terms-published

General Terms, Term: 'After the initial Order Form Service Term ends... the Order Form Service Term for each Service will automatically renew for consecutive periods of the same duration as the initial Order Form Service Term, unless either party provides the other with at least thirty (30) days' written notice of its intent not to renew the then-current Order Form Service Term for such Service.' A default is published for silent Order Forms: 'the initial Order Form Service Term for such Service will be one month, and such Order Form Service Term will renew for consecutive one-month periods' on the same 30 days' notice. Subscriptions are expressly auto-renewing under the Subscription Fees clause. The per-merchant term length itself still comes from the Order Form. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

commercial-processing-not-bundled differentiator

2.90% + $0.30 Slice processing is the single published rate on both memberships, the terminal ships in the bundle, and 'One payout for all orders' consolidates online, phone and in-store funds. No third-party processor option is documented. https://slice.com/products/point-of-sale-for-pizza-shops/ · retrieved 2026-08-01

commercial-interchange-plus-published differentiator

Slice publishes a single flat blended rate (2.90% + $0.30) on both plans. No interchange-plus option is offered or priced. https://slice.com/pricing · retrieved 2026-08-01

commercial-rate-increase-clause differentiator

General Terms, Fees: Fees are 'subject to the possibility for Slice to revise such Fees from time to time in its sole discretion, upon written notice to Restaurant (email is sufficient). In the event that Slice implements a change to its Fees, Restaurant may terminate the Services subject to such revised Fees upon written notice to Slice within fourteen (14) days of receiving the Fee change notice from Slice'; silence is deemed acceptance. Shortfalls: no cap on the size or frequency of increases and no restriction to pass-through interchange or network changes; the exit is a 14-day window rather than an open right; and the agreement nowhere states that exercising it waives the Early Termination Fee, so 'penalty-free' is not established. Card processing rates themselves sit in the Order Form and the Adyen/Wells Fargo Acquiring Addendum (Annex 7), which imposes no merchant-side rate cap. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

commercial-pricing-published

Exact figures published with no sales call: $399/mo + $2.00/order (Family), $39/mo + $3.00/order (Online), no per-order fee under $10, 2.90% + $0.30 processing, $1,000 implementation. Caveat: pricing for an additional terminal (the Order Manager Kit second iPad) is not published. https://slice.com/pricing · retrieved 2026-08-01

commercial-module-unbundling differentiator

The pricing page offers exactly two all-or-nothing bundles. Online ordering, phone ordering, loyalty, marketing, Flex Delivery and the POS cannot be bought or cancelled individually — dropping the POS means dropping to the $39 Online tier and losing phone ordering, Flex Delivery and the account manager. https://slice.com/pricing · retrieved 2026-08-01

commercial-hardware-purchase-outright

Annex 4 (Hardware Terms) governs all hardware acquired after 16 April 2024: 'Any Hardware (including, without limitation, printers, tablets or other hardware) provided by Slice will remain Slice's sole property'; 'Restaurant shall have no right, title or interest in or to the Hardware except the right to possession and use thereof during the applicable Order Form Service Term'; the merchant pays a 'non-refundable monthly fee set forth in the applicable Order Form (Hardware Fee)'; and on termination 'Restaurant shall promptly return the Hardware to Slice... (at Restaurant's expense)', exposed to a Restocking Fee of up to $100.00 and a Failure to Return Fee of up to $349.00 per item. That is a rental and it is the default. A purchase path survives only for hardware 'designated as purchased (or other similar term) on the Order Form' (Annex 4 sections 7-10, the Designated Hardware provisions), a negotiated designation for which no outright price is published on slice.com/pricing/ or anywhere in the 76-page site. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

commercial-hardware-not-locked differentiator

The devices are genuinely standard — Apple iPad, Epson TM-m30III and Epson U220 — but Slice does not document supporting operator-supplied equivalents, and no compatibility list is published. https://slice.com/knowledge-hub/slice-register-getting-started/ · retrieved 2026-08-01

commercial-implementation-fee-published

'$1,000 implementation fee' published on the pricing page for Family Membership; Online Membership shows none. https://slice.com/pricing · retrieved 2026-08-01

commercial-data-export-self-serve

Self-serve CSV download without a support ticket for Order Activity, Orders, Tax, Sales Mix and the Sales Summary. Line-item detail depth is unclear, and labor data does not exist to export. https://slice.com/knowledge-hub/owners-app-web-financials/ · retrieved 2026-08-01

commercial-export-customer-and-loyalty differentiator

Owner's App (web) > Customers > Profiles documents both directions: 'Import: Add your customer database from another system, with a maximum of 10,000 customers per import. The file must be a CSV in the format shown in the CSV Template' and 'Export: Download your Slice customer database for further analysis or record-keeping.' Shortfall: that is the guest record only. Loyalty exists as a feature (menu items carry a 'Loyalty reward' flag and reports show 'loyalty rewards' as a discount category) but no point ledger or per-customer balance is exportable or even displayed anywhere in the Owner's App documentation; no gift-card product is documented in any of the 45 Knowledge Hub articles, so there is no gift-card liability balance to export. The contract adds only a vendor-mediated route: on request within 30 days of termination 'Slice will make Restaurant Data available to Restaurant for export or download'. https://slice.com/knowledge-hub/owners-app-web-customers/ · retrieved 2026-08-08

commercial-post-termination-export-window differentiator

General Terms, 'Portability and Deletion of Restaurant Data': 'Upon request by Restaurant made within thirty (30) days after the effective date of termination or expiration of this Agreement, Slice will make Restaurant Data available to Restaurant for export or download. After that thirty (30) day period, Slice will have no obligation to maintain Restaurant Data, and may thereafter delete or destroy all copies of Restaurant Data maintained by Slice.' A defined window with a defined cutoff rather than immediate loss of access; the merchant must ask within the window and the export is vendor-mediated. https://slice.com/online-restaurant-agreement/ · retrieved 2026-08-08

commercial-data-ownership-clause differentiator

Slice publishes no merchant terms, so no clause states that the operator owns its transaction and customer data or constrains Slice's use of it. The one published ToS grants Slice a 'world-wide, perpetual, irrevocable, royalty-free' license to submitted content — and Slice operates a consumer marketplace on the same guest data. https://slicelife.com/pages/terms-of-service · retrieved 2026-08-01

commercial-source-available-selfhost

Fully proprietary SaaS. No source repository, no license, no self-hosting option, and not even a public API.

commercial-pci-p2pe-tokenization

Checked the two places this would appear. Annex 3 of the Pizzeria Agreement says only 'Slice does not receive full payment card details in its provision of Slice Register and Slice Standalone Payments. Slice has engaged a Processor that conducts payment processing of transactions submitted through Slice Register', and Annex 7 identifies that chain as Adyen N.V. with Wells Fargo Bank, N.A. as acquirer of record. Nowhere does Slice claim validated P2PE, describe a tokenization scheme, or name a merchant SAQ type: 'P2PE', 'SAQ' and 'tokeniz' occur zero times in the 178KB agreement and zero times across all 45 Knowledge Hub articles, 30 release notes and 26 FAQs pulled from slice.com/wp-json/wp/v2/. The customer-facing FAQ 'How secure are payments?' goes no further than 'secure and encrypted'. Scope reduction is plausible on an Adyen-processed estate, but Slice documents none of it and the claim asks what the vendor documents.

commercial-pci-dss-4-controls

Release note dated 2026-02-05: 'Two-step verification adds an extra layer of security to your Owner's App account. After entering your password, a 6-digit code is sent by text to confirm it's really you logging in. Available on web and mobile.' The mechanism is described in owners-app-web-getting-started ('you will be asked to confirm your login with a one-time code sent to your mobile phone... You can turn two-step verification on or off from Settings in the Owner's App (web)'). Shortfalls against the claim: (1) it is opt-in and merchant-disableable, so it is not MFA for all access; (2) it covers the Owner's App only -- Register access is per-employee PINs (register-employee-permissions) with no MFA documented; (3) no payment-page script integrity monitoring per Req 6.4.3 / 11.6.1 is described for the hosted ordering pages; (4) the string 'PCI' appears nowhere in Slice's published material, including the 178KB Pizzeria Agreement, so none of this is framed as a v4.0.1 control. https://slice.com/release-notes-2/extra-protection-for-your-owners-portal-login/ · retrieved 2026-08-08

commercial-soc2-attestation

Tested against the complete first-party corpus: 76 published slice.com pages (wp-json/wp/v2/pages), 45 Knowledge Hub articles, 30 release notes, 26 FAQs and the 178KB Pizzeria Agreement. 'SOC 2', 'SOC2', 'ISO 27001' and 'trust center' occur zero times in any of them; trust.slice.com does not connect and slice.com/security returns 403 with no such page in the page list. The agreement's security obligations run the other way -- Annex 3 makes the merchant 'solely responsible for... collection, handling and use of any cardholder data, Restaurant Consumer Data, customer information, and other point of sale information collected' -- and the data-protection commitments sit in the Annex 8 DPA, which does not reference an audit report. The claim's second limb, whether Slice will provide a report under NDA on request, is not testable from published sources, so this stays unknown.

commercial-privacy-dsar-tooling

Slice runs a consumer data-rights portal at privacy.slicelife.com covering diner CCPA/GDPR requests. No operator-facing in-app DSAR tooling and no publicly available DPA for restaurants were found. https://privacy.slicelife.com · retrieved 2026-08-01

commercial-wcag-kiosk-accessibility differentiator

No kiosk product exists, and no VPAT/ACR or WCAG conformance claim is published for the consumer web-ordering surfaces.

commercial-dual-pricing-compliant differentiator

The Register Sales Summary Report itemises both mechanisms as things the POS actually applies: 'Credit Card Surcharge - A fee charged when a customer pays with a credit or debit card' and 'Cash Discounts - Discounts applied to orders paid in cash', with Register Sales defined as gross sales 'minus refunds, discounts, and cash discounts'. owners-app-web-financials repeats them as report columns ('Credit Card Surcharges', '# of Credit Card Surcharges Collected', 'Cash Discounts', '# of Cash Discounts'). Shortfalls against the claim's compliance requirements: Slice's own wording applies the surcharge to debit cards, which the card networks prohibit, and no documentation describes automatic exclusion of debit or prepaid cards; no receipt-line or menu-board disclosure control is documented; no Knowledge Hub article covers enabling the surcharge or setting its rate; and the Pizzeria Agreement pushes the entire compliance burden onto the merchant -- 'Restaurant agrees that it shall not add a surcharge to transactions, except as expressly permitted by, and in full compliance with, applicable law and any relevant Scheme Rules.' https://slice.com/knowledge-hub/register-cash-management-and-reporting/ · retrieved 2026-08-08