Microworks Prism POS

order-capture-floor-plan-editor

Table Setup is a real graphical layout editor: a table wizard picks "a table image that best represents your table", names tables with prefix/suffix and starting number, lays out rows/columns with spacing, and tables are then "moved by clicking on the table and dragging it", multi-selected with shift, and aligned or centred with buttons. Table Sections gives multiple named layouts per location ("Many restaurants have a dining room and a bar"). Shortfall: no per-table seat-capacity attribute is documented, section-to-server assignment is not documented on either screen, and only two stock backdrops ship (SECTIONA.JPG and BAR.JPG). https://help.microworks.com/webhelp/Table_Setup_Update.htm · retrieved 2026-08-02

order-capture-seat-level

Checked the complete order-entry and check surface: Table Setup (table wizard, drag-position, sections — no per-table seat-capacity or seat-number attribute), Splitting Checks (splits by entering "the number of checks you would like to add" or by moving individual items — no seat-based split), and Ordering Advanced Options (Sold Out Item, Reprint History, Re-Assign Orders — no seat function). No topic anywhere in the 488-topic manual assigns an order line to a seat number; the complete Ordering Module book (New Order, Creating An Order, Updating An Order, Settling An Order, Splitting Checks, Customer Last Order, Customer Information, Ordering Advanced Options, Time Clock) has no seat concept. https://help.microworks.com/webhelp/Splitting_Checks.htm · retrieved 2026-08-04

order-capture-coursing-hold-fire

Advanced Kitchen Printing routes items "based on order type" and "based on level" with Primary/Secondary printer rules — the complete kitchen-routing mechanism — with no course concept. The Ordering Module book has no hold/fire or course-assignment topic, and the Makeline Monitor's complete field set (Ord#, Qty, Description, Elaps, Type, Clear, Made) has no course grouping or fire-next-course action from a handheld/terminal/expo screen. https://help.microworks.com/webhelp/Advanced_Kitchen_Printing_Tab.htm · retrieved 2026-08-04

order-capture-split-merge

Check Management is documented: "a single order may have multiple checks, either by splitting existing items into different checks or by creating a new check", Split prompts "for the number of checks you would like to add" (even N-way), and Move re-assigns individual items between checks with Undo. Shortfall: splitting by seat and by arbitrary dollar/percentage amount is not documented, no merge of two separate order numbers is documented (consolidation only moves items between checks of one order), and nothing states whether a check can be split after partial payment. https://help.microworks.com/webhelp/Splitting_Checks.htm · retrieved 2026-08-02

order-capture-bar-tab-preauth differentiator

The complete card-authorization documentation describes one tender pattern only: "When a charge is made in PrISM, the amount of the sale is simply authorized... The actual transaction is not completed until the batch of validations are processed." No open-tab, incremental re-authorization, or auto-close-at-end-of-day workflow is described, and no "tab" topic exists anywhere in the 488-topic manual or the Ordering Module book. https://help.microworks.com/webhelp/Authorizer_Overview.htm · retrieved 2026-08-04

order-capture-transfer-audit

Item transfer between checks is documented; server/device transfer with named-employee audit log is not.

order-capture-native-handheld

Windows 2-in-1 tablet running "the exact same user interface as our fixed POS station" — native, not mirrored. Tableside card payment on the handheld is not documented. https://www.microworks.com/products/Handheld-Ordering.htm · retrieved 2026-08-01

order-capture-offline-order-entry

On-premise store database with only nightly sync to hosted Storenet implies local ordering survives an internet outage, but no offline feature matrix is published. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01

order-capture-qr-same-check differentiator

QR ordering exists; whether it attaches to an open POS check is not documented.

order-capture-kiosk-first-party differentiator

First-party kiosk reusing the WebOrder menu/UI. No ADA/accessibility conformance documented. https://www.microworks.com/products/kiosk-qr-ordering.htm · retrieved 2026-08-01

order-capture-drive-thru

The vendor's complete product catalogue (WebOrder, RapidRun, Kiosk/QR Ordering, Digital Surveillance, Enterprise Management/Storenet, Notification Service, Handheld Ordering, plus core POS) contains no drive-thru product, and no drive-thru topic exists anywhere in the 488-topic administrator manual. Microworks positions itself as a pizza/delivery/takeout POS; order-point/pay-window/pickup-window flow is not part of the documented or marketed product. https://www.microworks.com/products.htm · retrieved 2026-08-04

order-capture-drive-thru-timers

Dependent on order-capture-drive-thru (no evidence): the vendor sells no drive-thru product or hardware, so there is no drive-thru order to time. No speed-of-service-by-segment topic exists anywhere in the manual. https://www.microworks.com/products.htm · retrieved 2026-08-04

order-capture-voice-ai differentiator

The complete 488-topic help TOC across all eleven books, plus the full vendor product catalogue, contains no AI, voice, speech, or virtual-agent topic anywhere. The only phone-related feature documented is Caller ID Customer Link (inbound call pops the customer record) — a lookup, not order-taking. No named voice-AI partner program is published. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

order-capture-throttling differentiator

The Ordering tab of Location Maintenance is the complete set of order-intake configuration: Use Customer Last Order, Maximum orders retrieved, Timed Order Check Interval, Sales Tax, Use Comeback Coupon, Use Buyer's Club, Customer Survey Invitation, Force Street Check, Currency Selection/Conversion. No capacity limit, per-slot order cap, or automatic quote-time extension field exists among them. https://help.microworks.com/webhelp/Ordering_Tab.htm · retrieved 2026-08-04

order-capture-scheduled-orders

"Orders can be placed for immediate attention or queued for delivery or pick-up later." Per-channel lead time and computed fire-time injection not documented. https://www.microworks.com/products/web-ordering.htm · retrieved 2026-08-01

order-capture-catering

Catering named as a supported order type alongside table-service/delivery/take-out. Quotes, deposits, balance-due, and event schedule not documented. https://www.microworks.com/products/pizza-pos.htm · retrieved 2026-08-01

order-capture-order-ready-signal differentiator

Whether any third-party marketplace order ever reaches PrISM at all is itself unestablished (delivery-3p-direct-integration, unknown) — the complete help TOC has no marketplace-integration topic. With no documented ingestion path, there is no basis to determine whether POS/KDS state pushes a ready signal back to a marketplace. Checked Makeline_Monitor_Overview.htm (Clear/Made bump actions, no outbound status push) and the full TOC; unresolved until the underlying integration's existence is established.

order-capture-void-comp-controls

All three halves are documented. Reason codes: the Advertised Coupon "Force Explanation" option "will require the order taker to enter an explanation when using this coupon. The explanation can be viewed on the Weekly Exceptions Report." Role gating: each coupon has a "Password Required" flag, and Setup Password Functions makes every discrete system function individually password-gated by Password Group. Exception report: "Every time a password is used, an entry is created in the Weekly Exceptions browser", with an optional camera recording per function. https://help.microworks.com/webhelp/Advertised_Coupons.htm · retrieved 2026-08-02

menu-pricing-nested-modifiers

Modifier lists chain — each list carries a "Next List Label" that renames the Modify button onto the following list — and the menu item Advanced tab exposes an "Alternate Modifier Level" section to "define more complex modifiers based on levels". Shortfall: the manual documents no per-group min/max selection counts and no forced-selection flag (only an "Auto Show" display toggle and an Optional flag on Includes), never states a supported nesting depth, and refers the level features to "Microworks Tech Support" rather than documenting them. https://help.microworks.com/webhelp/Modifier_Lists.htm · retrieved 2026-08-02

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

Documented explicitly: one shared modifier list carries multiple pricing levels and "Each menu item will then be assigned a size, and that size corresponds to which pricing level is used to calculate modifier price" — with pizza toppings on small/medium/large given as the worked example. https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-01 adversarially verified

menu-pricing-fractional-placement differentiator

Verified independently by the adversarial pass against the retrieved page. The Fraction field is first-class on modifier price rows: "This field is used for fractional topping pricing such as half and quarter. Fractions only apply to modifiers," with the worked row set "(Price=1.00, Count=1, Fraction=Whole), (Price=0.50, Count=1, Fraction=1st Half) and (Price=0.50, Count=1, Fraction=2nd Half)." Per-fraction placement with per-fraction pricing, in first-party product documentation. https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-02 adversarially verified

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

Half-and-half is priced by hand-entered additive rows: separate 1st Half and 2nd Half modifier price entries that sum onto the pizza. Shortfall named by the verification pass: Pricing.htm enumerates its pricing axes (Count, Fraction, Size, Store Rule, Order Type, Double Count, Level) and documents no half-and-half resolution rule at all — no charge-the-higher-half, no average-the-halves, no whole-pizza reconciliation. The operator encodes the convention in price rows; the system applies no rule. https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-02 adversarially verified

menu-pricing-topping-quantity-tiers

Documented Count field drives price by quantity of the same modifier: "If you offer one dressing for free on a salad and charge $0.50 for each additional dressing, your count 1 price would be 0.00 and your count 2 price would be 0.50." That is a per-quantity price tier table. https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-01 adversarially verified

menu-pricing-size-style-matrix differentiator

One axis only. "The Size field relates the pricing level selected to the menu item that you are working on," and Size_Setup.htm makes size a first-class attribute driving both item and modifier price levels. Shortfall: crust/style is not a pricing dimension — it appears in none of the documented axes (Count, Fraction, Size, Store Rule, Order Type, Double Count, Level) and there is no style-setup topic in the 488-topic help TOC, so crust variants must be modelled as separate menu items or modifiers rather than a second matrix axis. https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-02 adversarially verified

menu-pricing-included-allowance differentiator

The Includes tab "allows you to define what modifiers, or toppings, are included on a menu item", each include carrying a Qty for the serving amount included ("if this were a specialty pizza that comes with a double portion of pepperoni, the Qty amount for Pepperoni would be 2"), an Inc./Optional flag and a Show On Web flag. The modifier list "Allow Substitutions" option lets an included topping be swapped "with another topping at no extra charge". Corroborated by the Count field on Pricing.htm, where count 1 = 0.00 and count 2 = 0.50. https://help.microworks.com/webhelp/Includes_Tab.htm · retrieved 2026-08-02

menu-pricing-combos

Meal deals are constructed as Advertised Coupons with requirement lines: "a Meal Deal coupon that consists of a large pizza, one dozen wings, and a choice of either an order of breadsticks or fried dough" — the breadsticks and fried dough marked Optional with Required Optional Items set to 1. Requirements match by Menu Item, Menu Size or Menu Class, with Quantity, Item Min., Least Expensive and Set Price for the price delta. Shortfall: there is no first-class combo entity; the coupon is applied by the order taker from the ordering module's Coupons screen, and no automatic detection or conversion of an eligible a-la-carte cart into the combo price is documented. https://help.microworks.com/webhelp/Advertised_Coupons.htm · retrieved 2026-08-02

menu-pricing-upsell-prompts differentiator

WebOrder claims it raises average ticket "by over 20%" but no configurable per-item/per-channel prompt or attach-rate report is documented.

menu-pricing-86-propagation

A manual 86 mechanism exists at the terminal: "Sold Out Item — Mark menu items as unavailable. The interface displays available items in green and 'Sold Out' items in red," toggled by pressing the Sold Out button then the item, or Avail. to re-enable. Shortfall: this is a single-terminal manual toggle documented nowhere as propagating to WebOrder, kiosk, or third-party marketplaces — the Web tab's Visibility field (store/web/both) is a separate, independently-set flag — and no propagation latency is stated anywhere. https://help.microworks.com/webhelp/Ordering_Advanced_Options.htm · retrieved 2026-08-04

menu-pricing-countdown-auto-86 differentiator

The menu item Advanced tab and Web tab are fully enumerated (UPC, Advanced Web images, Doubles Class, Points, Fav. Sort, Auto Note, Key Item, Password Protect, Visibility, Web Sort/Group/Label/Desc.) and contain no countdown/par-count field. Inventory_Master_u.htm's Reorder Level is a purchase-order threshold ("the level at which you would like the system to prompt you to order more"), not a per-item sale counter that zeroes and auto-86s a menu item, and no scheduled auto-restore exists anywhere in the manual. https://help.microworks.com/webhelp/Advanced_Tab.htm · retrieved 2026-08-04

menu-pricing-dayparting

Documented price levels: "This is used when pricing changes based on the day of the week, the time of the day, or for certain types of advanced coupons." https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-01 adversarially verified

menu-pricing-channel-price-books

Order-type-specific pricing is documented with an explicit resolution rule: "The PrISM system checks order type pricing from the top down, meaning that any specific order type pricing must be physically higher in the price group than the 'All' price entry." That is a per-channel price book with a defined fallback. https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-01 adversarially verified

menu-pricing-dual-pricing differentiator

Positive absence by enumeration of the pricing engine. Pricing.htm enumerates every dimension a price row can vary on — Count, Fraction (portion), Size, Store Rule, Order Type, Double Count, and Level — and payment tender is not among them: there is no cash-vs-card price dimension anywhere in the pricing setup, and Advanced_Pricing_Tab.htm adds only level- and modifier-based methods. The complete help TOC (whtdata0-6.xml) has no dual-pricing, cash-discount, or surcharge topic, and the vendor's own payments page (microworks.com/products/payments.htm, re-read 2026-08-04) sells the integrated PrISM Merchant Services stack with no dual-pricing or cash-discount program mentioned. Caveat: the manual documents on-premise PrISM; the payments page references "Prism V8.1 or Prism Cloud", whose settings are not separately documented in public — but the page where such a processing program would be sold is itself silent. https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-04

menu-pricing-versioning-effective-dates differentiator

Pricing Level Exceptions is the complete mechanism for time-varying prices: Level Name, Level Type, Level Priority, Inactive, and Triggered By (most commonly Time of Day, combinable with other conditions), with an Advanced tab letting one level override another. Every documented trigger is a recurring day/time window, not a one-time future effective date; there is no staged-version preview, publish action, or rollback-to-prior-version concept anywhere in Pricing.htm or Pricing_Level_Exceptions.htm. https://help.microworks.com/webhelp/Pricing_Level_Exceptions.htm · retrieved 2026-08-04

menu-pricing-franchise-hierarchy differentiator

Verbatim first-party claim: Storenet "creates the ability for a single 'Master' menu and inventory to be shared by multiple locations, and provides the tools to sort out differences in price, costs and selection." Shortfall: propagation is nightly, not real-time ("Hosted Server and Unit Locations Can Update Database Nightly"); no field-level lock, approval workflow or corporate-vs-franchisee role governance is described; and the page mentions no franchise royalty reporting at all, which is why the royalty cells remain unknown. Grade corrected D to C — a first-party product feature page, not a press release. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-02 adversarially verified

menu-pricing-allergen-nutrition

The menu item Web tab (Visibility, Reference, Web Sort, Web Group, Instructions, Base Item, Web Label, Web Desc., Web Special, Special Image File, Web Thumbnail, Web Image) and Advanced tab are the complete set of documented per-item metadata fields, and neither carries an allergen flag or nutrition value. Includes_Tab.htm (ingredient/topping allowances) likewise has no allergen field. No allergen or nutrition topic exists anywhere in the 488-topic manual. https://help.microworks.com/webhelp/Web_Tab.htm · retrieved 2026-08-04

menu-pricing-recipe-linkage differentiator

The Recipe Cost Manager links menu items to inventory items ("specify which inventory items, and in what amounts, are always used to assemble a given menu item"), has a dedicated Modifiers section so modifiers included with an item carry their own portion cost, and varies the bill of materials by Order Type ("utensils may not be provided on a carry-out order but would be included on a delivery order") and by Size. It yields item-level Recipe Cost and Cost % against the menu price. Shortfall: the depletion half is not documented here — no statement that a sale decrements theoretical on-hand in real time; depletion is reconciled on the Daily Inventory screen against Ideal Food Cost. https://help.microworks.com/webhelp/Recipe_Cost_Setup.htm · retrieved 2026-08-02

menu-pricing-3p-menu-push

Whether Microworks pushes menu data to any third-party marketplace depends on the marketplace integration itself, whose existence is unestablished (delivery-3p-direct-integration, unknown) — the complete help TOC has no marketplace, aggregator, or menu-sync topic. Checked Web_Tab.htm and the Web Ordering book (menu publishes only to the vendor's own WebOrder channel); no certified-direct-vs-middleman distinction can be evaluated without a documented integration to examine.

menu-pricing-dynamic-pricing

Pricing.htm enumerates every dimension a price row can vary on — Count, Fraction, Size, Store Rule, Order Type, Double Count, Level — and Advanced_Pricing_Tab.htm adds only level- and modifier-based methods. None is demand-based or algorithmic; all are operator-set tables activated by fixed rules (day/time, order type, size). No floor/ceiling guardrail concept and no automatic demand-responsive adjustment is documented anywhere. https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-04

payments-processor-choice differentiator

The gateway is fixed and singular — "PCCharge is currently the authorization software package chosen for integration with the PrISM system", supporting "both traditional dial-up as well as broadband Internet-based authorizations". Merchant processor choice exists but is brokered: Microworks requires "information pertaining to your primary credit card processing company" and configures it through tech support. Shortfall: no supported-processor list is published, the operator cannot self-configure or switch, and PCCharge is a discontinued Verifone product, so the available choice is bounded by what an end-of-life gateway still certifies. https://help.microworks.com/webhelp/Authorizer_Overview.htm · retrieved 2026-08-02 adversarially verified

payments-published-rates differentiator

No rate is published anywhere; the quote page routes all pricing to phone/email. https://www.microworks.com/quote.htm · retrieved 2026-08-01

payments-dual-pricing differentiator

Same finding as menu-pricing-dual-pricing: Pricing.htm enumerates every price dimension (Count, Fraction, Size, Store Rule, Order Type, Double Count, Level) and payment tender is not among them. Advanced_Pricing_Tab.htm adds only level- and modifier-based pricing. No cash-vs-card price field, no dual-pricing or cash-discount topic exists anywhere in the 488-topic TOC, and the payments marketing page (microworks.com/products/payments.htm, re-read 2026-08-04) sells the integrated processing stack with no dual-pricing program mentioned. https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-04

payments-surcharge-guardrails differentiator

A surcharge/dual-pricing engine does not exist in the documented pricing model (payments-dual-pricing, no), so there is no BIN-detection debit/prepaid exclusion, network percentage cap, or per-location enable/disable to document. The complete pricing surface (Pricing.htm, Advanced_Pricing_Tab.htm) has no tender-based pricing dimension at all. https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-04

payments-emv-nfc

Sourced to a marketing page, and that page attaches a material gate the dossier omitted: counter-top and mobile payment solutions require "running Prism V8.1 or Prism Cloud and using integrated processing platform." So tap/wallet acceptance is conditional on a current version plus PrISM Merchant Services, the vendor's own integrated processing. No terminal model, no PTS listing, no EMV certification named. Claim-level partial, not yes. https://www.microworks.com/products/payments.htm · retrieved 2026-08-01 adversarially verified

payments-softpos-tap-to-pay differentiator

The payments page states counter-top and mobile payment solutions require "running Prism V8.1 or Prism Cloud and using integrated processing platform" but does not specify whether tap acceptance runs through a certified card reader or a phone acting as the reader (SoftPOS/Tap to Pay). Checked payments.htm (re-read 2026-08-04) and the Handheld-Ordering page, neither of which names a reader model or describes phone-as-terminal acceptance. Unresolved rather than absent.

payments-pay-at-table

Pay-at-the-door EMV on the RapidRun driver app is documented; tableside EMV on the server handheld is not — the POS page says servers "swipe credit cards into any available POS station." https://www.microworks.com/products/rapidrun.htm · retrieved 2026-08-01

payments-qr-guest-pay differentiator

QR "scan, order, and pay" is offered; whether it settles an existing open POS check is not documented. https://www.microworks.com/products/kiosk-qr-ordering.htm · retrieved 2026-08-01

payments-tip-adjust

The pre-auth-then-batch model and its window are documented: "When a charge is made in PrISM, the amount of the sale is simply authorized... The actual transaction is not completed until the batch of validations are processed", and "Close Day ... must be run before the End-Of-Day procedure is begun". Shortfall: no tip-adjust screen, no on-device tip prompt flow, and no manager view of unadjusted tips is documented anywhere in the help system; after the batch closes "the Transaction List will only be available for review from within the PCCharge application's history reports section". https://help.microworks.com/webhelp/Authorizer_Overview.htm · retrieved 2026-08-02

payments-tip-pooling differentiator

The Payroll tab of Location Maintenance is fully enumerated — Level 1/2 Overtime Rate, Labor Percentage Goal, pay-rate display toggles, daily/weekly/period OT hour thresholds — and contains no tip pooling, tip-out, or distribution field. No tip-pool topic exists anywhere else in the 488-topic manual; the only tip-related report is a per-server Server Tip listing (labor-tip-distribution-audit-trail), not a pooling/allocation engine. https://help.microworks.com/webhelp/Payroll_Tab.htm · retrieved 2026-08-04

payments-offline-store-and-forward differentiator

The complete card-authorization documentation describes an authorize-at-order, settle-at-batch model through the integrated PCCharge gateway and contains no store-and-forward concept, no offline capture, and no per-transaction or cumulative offline cap. No other topic in the complete help TOC covers offline card capture. Consistent with the already-established payments-offline-decline-liability finding (no) on the same page. https://help.microworks.com/webhelp/Authorizer_Overview.htm · retrieved 2026-08-04

payments-offline-decline-liability differentiator

The claim asks whether the vendor publicly documents who bears the loss on an offline decline. It does not. The manual's complete card-authorization documentation (Authorizer_Overview.htm) describes an authorize-at-order, settle-at-batch model through the integrated authorizer and contains no store-and-forward or offline-capture concept at all — hence no decline-on-reconnect liability statement and no post-reconnect failed-offline-payments report. No other topic in the complete help TOC (whtdata0-6.xml) covers offline payments, and the payments marketing page (microworks.com/products/payments.htm, re-read 2026-08-04) is silent on offline behaviour and liability. The documentation the claim requires does not exist in the vendor's public corpus. https://help.microworks.com/webhelp/Authorizer_Overview.htm · retrieved 2026-08-04

payments-gift-cards

Native prepaid accounts are documented, not just a marketing bullet: "Gift Certificate accounts are very similar in function to Customer Accounts with the exception that these accounts are pre-paid", with a Gift Number, a Transaction History tab showing "payments, credits, and balance", Credit Account, Print Statement, and an Open Gift Activity Report in the reports tree; "under normal circumstances, gift certificates should be created and modified during the order taking process". Shortfall: balances live in the store-local database with only nightly StoreNet upload, so no cross-location balance sharing is documented; redemption through the WebOrder channel is not documented; and integrated plastic gift cards run through third-party authorisation set up on the CC/Gift/Check tab, which the manual says only Microworks Tech Support may touch. https://help.microworks.com/webhelp/Gift_Certificates.htm · retrieved 2026-08-02

payments-house-accounts

Documented: "Customer Accounts can be created, at your discretion, allowing customers to purchase merchandise on account", linked to a customer record by phone, with a Transaction History section detailing "payments, credits, and balance", Add Payment, Credit Account, Print Selected Invoice, Print All Invoices and Print Statement; Account Terms exist "to separate accounts into different billing cycles". Shortfall: no per-account credit limit field is documented, and Account Terms are explicitly "free-form text fields; you may enter any name you wish" rather than enforced terms. https://help.microworks.com/webhelp/Customer_Accounts.htm · retrieved 2026-08-02

payments-split-tender

"Prism POS allows multiple tenders and tips to be used on a single check" and "Split checks are settled independently of each other allowing single or multiple credit cards to be used for each check." No cap is stated. https://www.microworks.com/products/restaurant-pos.htm · retrieved 2026-08-01

payments-refund-void-controls

Exception reporting and POS-overlay video surveillance with a searchable System Event Log exist; role-based authorization and an immutable approver-identified audit log are not documented. https://www.microworks.com/products/Digital-Surveillance.htm · retrieved 2026-08-01

payments-chargeback-tooling differentiator

The gateway's documented surface ends at settlement: "the Transaction List will only be available for review from within the PCCharge application's history reports section" once the batch closes. No dispute, chargeback, or evidence-assembly topic exists anywhere in the manual; disputes would be handled entirely inside the third-party PCCharge/processor tooling, outside PrISM. https://help.microworks.com/webhelp/Authorizer_Overview.htm · retrieved 2026-08-04

payments-card-on-file differentiator

Tokenization is documented and WebOrder gives customers "a secure way to manage their orders while you maintain a single shared credit card batch." Cross-channel reuse of the token in-store is not documented. https://www.microworks.com/products/payments.htm · retrieved 2026-08-01

payments-payout-timing differentiator

No deposit-schedule or funding-speed statement is published anywhere; the payments marketing page (re-read 2026-08-04) and the complete help TOC are both silent on payout timing, and processing is brokered per-merchant through Microworks' processing partner rather than a single named acquirer, so no vendor-wide schedule could exist to publish.

payments-multi-entity-routing differentiator

No MID/settlement-routing documentation exists anywhere on the vendor site or in the manual; processing is configured per store via the CC/Gift/Check tab, which is reserved to Microworks Tech Support (CC_Gift_Check_Tab_LM.htm), so how a multi-store operator's settlement is split across bank accounts is not addressed.

payments-p2pe-pci4

"Tokenization and point-to-point encryption" and "keep cardholder data off the POS" are claimed. No PCI DSS 4.x AoC, no P2PE listing, and no SAQ type are published. https://www.microworks.com/products/payments.htm · retrieved 2026-08-01

kitchen-station-routing

Advanced Kitchen Printing routes per item to multiple destinations: "the ability to print items to multiple kitchen printers at once, the ability to print items differently based on order type, and the ability to print items differently based on level", with a Primary/Secondary rule so a pizza prints at the wing station only when wings are on the same order. Two shortfalls against the claim: the routing targets are kitchen printers, not KDS stations (the Makeline Monitor is configured location-wide on a single Makeline tab, with no per-station routing), and it is not operator-configurable without vendor involvement — "For most new systems, Advanced Kitchen Printing is disabled by default... it must be enabled by Microworks Tech Support." https://help.microworks.com/webhelp/Advanced_Kitchen_Printing_Tab.htm · retrieved 2026-08-02

kitchen-expo-consolidation

The Makeline Monitor is the product's only kitchen display, and its overview enumerates the entire screen and every control: a flat list of items to make (Ord#, Qty, Description, Elaps, Type) with per-item Clear, an order-type Filter, a Select mode for clearing several items at once, Font, Made (view previously made items), and list navigation. There is no expo or consolidation view, no prep-station concept on the display, and no order-level completion state — items are cleared individually and nothing tracks whether every contributing station has bumped its items. The makeline book in the complete help TOC contains only this screen plus the Makeline tab of Location Maintenance (Makeline_Tab.htm: a refresh interval and an aging timer). https://help.microworks.com/webhelp/Makeline_Monitor_Overview.htm · retrieved 2026-08-04

kitchen-course-firing differentiator

Kitchen routing is fully documented as printer/level/order-type based ("print items to multiple kitchen printers at once... print items differently based on order type... based on level"), with no course concept. Makeline_Monitor_Overview.htm's complete field set (Ord#, Qty, Description, Elaps, Type, Clear, Made) has no course grouping, hold state, or fire-on-demand action from a handheld/terminal/expo screen. https://help.microworks.com/webhelp/Advanced_Kitchen_Printing_Tab.htm · retrieved 2026-08-04

kitchen-prep-time-pacing differentiator

The Makeline tab's complete configuration is a Makeline Timer (flags an item "old" after an elapsed threshold) and a Makeline Refresh interval — both location-wide constants, not per-item cook times. Makeline_Monitor_Overview.htm shows a flat, un-staggered item list with a single Elaps column; no per-item configurable cook time and no staggered start/display logic to synchronize finish times is documented anywhere. https://help.microworks.com/webhelp/Makeline_Tab.htm · retrieved 2026-08-04

kitchen-order-throttling differentiator

The Ordering tab of Location Maintenance is the complete order-intake configuration (Timed Order Check Interval, Sales Tax, coupons, Survey, Force Street Check, Currency) and contains no load-based throttling or quote-time extension. Makeline_Tab.htm's only thresholds are a display aging timer and refresh interval, not an order-release pacing rule. https://help.microworks.com/webhelp/Ordering_Tab.htm · retrieved 2026-08-04

kitchen-channel-pause-propagation differentiator

Depends on the third-party marketplace integration whose existence is unestablished (delivery-3p-direct-integration, unknown); the complete help TOC has no marketplace topic. Checked Advanced_Kitchen_Printing_Tab.htm and Makeline_Monitor_Overview.htm — both describe purely in-store routing with no outbound channel-pause action. Unresolved rather than absent.

kitchen-order-ready-callback differentiator

Same dependency as kitchen-channel-pause-propagation: no marketplace integration is documented to receive a callback. Makeline_Monitor_Overview.htm's Clear/Made actions are local state changes only, with no outbound event to any external system documented.

kitchen-bump-bar-hardware

Directly documented: "An optional add-on component to the PrISM for Windows system is the Makeline bump bar. Bump bars are built to withstand the demanding requirements of the kitchen environment" — with standard keyboards or touchscreen monitors replaced by the bump bar for "faster manipulation of makeline items." Note it is an optional paid add-on, not base. https://help.microworks.com/webhelp/Advanced_Features.htm · retrieved 2026-08-01 adversarially verified

kitchen-all-day-counts

Partial aggregation exists: "Marking an inventory item as a Key Ingredient will allow it to be tracked on a Makeline Monitor", with a Key Ing. Code "displayed on the Makeline Monitor next to the Count of the Key Ingredient". Shortfall: the aggregate is per key ingredient, not an all-day view of outstanding quantities per menu item and per modifier, and the manual states the feature "must be configured by Microworks Tech Support" rather than by the operator. https://help.microworks.com/webhelp/Inventory_Master_u.htm · retrieved 2026-08-02

kitchen-sla-alerts

The Makeline tab exposes "Makeline Timer — This is the amount of time that may pass before an item on the Makeline Monitor is flagged as being 'old'", alongside a Makeline Refresh interval; the monitor itself shows an "Elaps" column, "the amount of time that has elapsed since the order was placed". Shortfall: one location-level timer, not configurable target cook times per station or per order type, and the manual describes only an "old" flag — no colour escalation ladder and no audible alert are documented. https://help.microworks.com/webhelp/Makeline_Tab.htm · retrieved 2026-08-02

kitchen-printer-fallback differentiator

Printer_Setup.htm documents a per-device Backup Device field: "Choose another device to act as a backup in case PrISM cannot print to this device" — failover to a designated backup printer is a configured, documented behaviour, not an operator workaround. Named shortfall: the docs state no no-ticket-loss guarantee for the failover, describe no staff alert when it engages, and document nothing for a failed Makeline Monitor screen — the Backup Device field is framed entirely around printing ("cannot print to this device"), so KDS-screen failover is unevidenced. https://help.microworks.com/webhelp/Printer_Setup.htm · retrieved 2026-08-04

kitchen-offline-operation differentiator

The Makeline Monitor runs on the same store LAN as the POS terminals (Setting_Up_Workstations.htm), which structurally implies it does not depend on the internet, but no topic in the complete help TOC states explicitly that the makeline continues to receive and display tickets during a cloud/internet outage. Checked Makeline_Monitor_Overview.htm and Makeline_Tab.htm — neither addresses connectivity loss. Consistent with the established pattern on the sibling reliability-offline-* cells (structural inference, not vendor statement).

kitchen-item-build-screens differentiator

The Makeline Monitor's complete field set — Ord#, Qty, Description, Elaps, Type, plus Clear/Select/Made/Font/Filter controls — is fully enumerated. Description is a single text line; there is no dedicated recipe-step, portioning-diagram, or full modifier-breakout view. No item-build or assembly-detail screen is documented anywhere in the manual. https://help.microworks.com/webhelp/Makeline_Monitor_Overview.htm · retrieved 2026-08-04

kitchen-pizza-fractional-display differentiator

The complete makeline screen (Ord#, Qty, Description, Elaps, Type) has no dedicated visual rendering for half/quarter topping placement — Description is plain text. Fractional pricing is a pricing-engine attribute (Pricing.htm's Fraction field), and nothing documents it carrying through to a graphic or unambiguous half-and-half rendering on the makeline or ticket. https://help.microworks.com/webhelp/Makeline_Monitor_Overview.htm · retrieved 2026-08-04

kitchen-recall-refire

The Makeline Monitor has a "Made" button — "This allows you to view previously made items" — after Clear removes an item from the list. Shortfall: viewing is all that is documented; there is no un-bump/restore action returning a cleared item to the active list, and no per-item refire or reprint from the makeline. Recall of a settled order is a separate Ordering Module function. https://help.microworks.com/webhelp/Makeline_Monitor_Overview.htm · retrieved 2026-08-02

kitchen-order-modification-alerts differentiator

The makeline's documented controls are Clear, Select (multi-clear), Made (view cleared items), Font and Filter — there is no flag, highlight, or notification state for an item added, changed, or removed after the ticket first displayed. No modification-alert topic exists anywhere in the manual. https://help.microworks.com/webhelp/Makeline_Monitor_Overview.htm · retrieved 2026-08-04

kitchen-guest-ready-notification differentiator

Prism Notification Service sends SMS "when the order is ready for pickup" and on out-for-delivery/arrival. It is listed as a distinct product, so whether it is bundled or separately priced is unknown. https://www.microworks.com/products/pizza-pos.htm · retrieved 2026-08-01

kitchen-waste-logging

The two topics that constitute the complete physical-inventory documentation — Daily_Inventory_Screen.htm (beginning/delivery/ending/ideal/variance) and Inventory_Master_u.htm (item, cost, reorder, key-ingredient fields) — contain no waste, spoilage, or remake logging workflow and no reason-code field. Variance from Ideal is a single aggregate number (the "Food Gap" on the Weekly Sales Recap), not an itemized, reason-coded waste entry, and there is no KDS-side logging screen documented. https://help.microworks.com/webhelp/Daily_Inventory_Screen.htm · retrieved 2026-08-04

kitchen-speed-of-service-reporting

Per-order Elaps (elapsed time since order placed) is a live field on the Makeline Monitor, and Server_Report.htm provides a per-server daily activity summary, but neither is a ticket/station-time report sliced by daypart and channel with average/percentile figures. The complete reporting surface (Scheduled_Reports.htm export types are PDF/HTML, no CSV/API) has no dedicated speed-of-service report by that name; reporting-server-scorecards (existing cell) already established the manual has no cross-server or trend reporting. https://help.microworks.com/webhelp/Server_Report.htm · retrieved 2026-08-04

kitchen-prep-forecasting

Forecast Indicators — the only forecast mechanism documented anywhere in the 488-topic manual — computes a labour headcount ratio ("how many employees... need to be scheduled based on the average volume forecast") from operator-defined Numerator/Denominator volume measures, for the Employee Scheduling Module. It is not a per-item prep-quantity prediction and is not surfaced to kitchen staff as a prep list; no separate prep-forecasting topic exists. https://help.microworks.com/webhelp/Forecast_Indicators.htm · retrieved 2026-08-04

delivery-driver-roster

Verbatim: the module "displays a list of all employees that are currently clocked in as a Driver job classification and allows simple touch screen access for order assignment." Driver is a first-class job class in the manual — Driver_Tab.htm carries Driver Reimbursement by (Per Mile, Per Order, Percent of Total Sales, Percent of Pre-Tax Sales, Sector/Streets Reimbursement, Manual), Personal Bank, Default Company Car, Check Ins. Exp. Date and Force Odometer Miles — so the roster is driven by clock-in state against a real role. Grade corrected B to C: the roster screen itself is described only on the marketing page. https://www.microworks.com/products/delivery-pos.htm · retrieved 2026-08-02 adversarially verified

delivery-dispatch-board

Native in-house dispatch, confirmed on two sources. The manual establishes the module — "The Assign Orders function launches the Driver Routing module. Within this module, orders may be routed, or assigned, to drivers for delivery" — and the delivery product page supplies the board behaviour verbatim: "Orders are listed in an easy-to-read, oldest order first format with sectors displayed for creating smarter multi-order runs." Routing_Tab.htm adds the lateness policing (Mark Lates Automatic, Auto Late Minutes, flashing warn). Not a DaaS handoff. https://help.microworks.com/webhelp/Assign_Orders.htm · retrieved 2026-08-02 adversarially verified

delivery-route-map differentiator

Live map with driver position and "turn-by-turn mapping directions to each location in the run." Automatic stop-order optimization is not explicitly claimed. https://www.microworks.com/products/rapidrun.htm · retrieved 2026-08-01

delivery-driver-tracking differentiator

The vendor claims it — "The store can view driver's location from route screen" and "Turn-by-turn mapping directions to each location in the run" — but RapidRun appears nowhere in the 488-topic PrISM administrator manual: no RapidRun book, no GPS or tracking topic, and Driver_Tab.htm covers only reimbursement method, personal bank, company car and forced odometer entry. Shortfall: live driver position is a marketing claim for an undocumented companion mobile app, with no documented refresh interval, geofence or breadcrumb history, and the page's "No additional Licensing is necessary" applies only to the store-side viewer, implying the driver app is separately licensed. Grade corrected B to C. https://www.microworks.com/products/rapidrun.htm · retrieved 2026-08-02 adversarially verified

delivery-zones-polygon differentiator

Positive evidence of the alternative design. Delivery areas are Sectors built from street lists: "you may create a sector called 'A1' where the delivery charge is $1.00 and the driver reimbursement is $0.50. Then, simply attach this sector to all applicable streets within that area", and "Sectors are used system-wide; one defined sector may be applied to multiple streets." Mapping is a MapPoint store-address lookup on the Routing tab. No polygon drawing tool and no drive-time isochrone appears anywhere in the help system. https://help.microworks.com/webhelp/Update_Sectors.htm · retrieved 2026-08-02

delivery-zone-pricing

Fees are genuinely per zone and automatic: Location Maintenance carries a Default Delivery Charge plus a "Per Sector Delivery Charge" switch — "If you are using per sector delivery charges or street-specific delivery charges, this option must be enabled" — and Variable Delivery Charges band the fee by order total ("Orders totaling between $0.00 and $4.99 could have a delivery charge of $1.50, while orders of $5.00 or more could be free"), with the sector attached to the customer's street. Shortfall: the quoted promise time is a single location-level "Estimated Delivery Minutes" constant on the Routing tab, not per zone, and no per-zone order minimum is documented. https://help.microworks.com/webhelp/Delivery_Charges_Tab.htm · retrieved 2026-08-02

delivery-address-validation

Addresses resolve against operator-maintained Update Streets / Update City / Update Carrier Routes tables, which is what attaches the sector, delivery charge and driver reimbursement to an order. Mapping depends on MapPoint: "If the store address configured on the General Tab is unable to be located in Map Point, an alternate store address can be entered here. If the store can not be located in Map Point, the mapping functionality will not work properly." Shortfall: validation is against the operator's own street table, not a third-party address-verification or geocoding service, and MapPoint is a Microsoft product retired in 2014 — the manual names no successor. https://help.microworks.com/webhelp/Routing_Tab.htm · retrieved 2026-08-02

delivery-driver-comp differentiator

Driver Detail and Cash Drop reports track per-driver runs and cash. Mileage capture and separate reimbursement-vs-wage payroll export lines are not documented. https://www.microworks.com/products/reporting.htm · retrieved 2026-08-01

delivery-cash-reconcile

Re-sourced from report names to the mechanism. A cash drop lets you "take any amount of money from the employee, place it in a secure location, and reflect that action as a credit to the employee's cash responsibilities"; the drop is recorded against the employee in the Employee List, and "till totals will reflect receiving cash drops when balancing the till." A per-driver cash-responsibility ledger reconciled against the till, corroborated by Till_List.htm and Driver_Report.htm in the same book. https://help.microworks.com/webhelp/Cash_Drop.htm · retrieved 2026-08-02 adversarially verified

delivery-daas-dispatch

Every delivery-dispatch topic and page checked (Assign_Orders.htm, Routing_Tab.htm, Delivery_Charges_Tab.htm, Driver_Tab.htm, rapidrun.htm) describes exclusively an in-house driver fleet — clocked-in Driver job class, RapidRun turn-by-turn routing and live position, Sector-based reimbursement. No DoorDash Drive, Uber Direct, Nash, Relay, or generic on-demand-courier hand-off is named anywhere in the manual or on the vendor site. https://www.microworks.com/products/rapidrun.htm · retrieved 2026-08-04

delivery-daas-fallback differentiator

Dependent on delivery-daas-dispatch (no evidence): since no on-demand courier marketplace integration exists at all, there is no overflow/hybrid dispatch rule to document. Routing_Tab.htm's only automation is Mark Lates Automatic / Auto Late Minutes, which flags a late in-house delivery — it does not reassign the order to an outside courier. https://www.microworks.com/products/rapidrun.htm · retrieved 2026-08-04

delivery-3p-direct-integration differentiator

Downgraded from partial by the verification pass. The entire basis was one hedged marketing sentence — Prism "integrates with 3rd party Apps like GrubHub, UberEats, DoorDash and Postmates (to name just a few)" — with no named integration partner, no middleware vendor, no certification and no setup screen. The complete 488-topic help TOC across all eleven books contains no marketplace, aggregator, GrubHub, Uber Eats, DoorDash or injection topic. Microworks is absent from DoorDash's 2026 Preferred Integration Partner cohort, and every downstream cell here (injection, menu push, 86 sync, store pause, reconciliation, error visibility) is unknown. Existence itself is unestablished, so partial was an inference. adversarially verified

delivery-3p-injection

Integration is claimed but the injection mechanism (auto-fire vs tablet accept) is not described.

delivery-menu-push

Depends on the third-party marketplace integration whose existence is unestablished (delivery-3p-direct-integration, unknown). Menu publishing is documented only to the vendor's own WebOrder channel (Web_Tab.htm Visibility flag); no marketplace-menu-sync topic exists in the complete help TOC. Unresolved until the underlying integration is established.

delivery-86-sync

Same dependency: with the marketplace integration itself unestablished, there is no basis to determine whether the manual Sold Out Item toggle (Ordering_Advanced_Options.htm) propagates to any connected channel. No marketplace-sync topic exists anywhere in the manual.

delivery-store-pause

Same dependency as delivery-86-sync and delivery-menu-push. No store-pause-to-marketplace topic exists anywhere in the manual; whether a store-level pause on any connected channel is even possible cannot be assessed without a documented integration.

delivery-3p-reconciliation differentiator

Same dependency. No topic anywhere in the manual reconciles marketplace payouts against POS-recorded sales; the only reconciliation documented is in-house (Cash_Drop.htm, Till_List.htm, Driver_Report.htm for the in-house driver fleet).

delivery-injection-error-visibility differentiator

Same dependency. With no documented marketplace ingestion path (delivery-3p-direct-integration, unknown), there is no connection-health, failed-injection, or per-channel-alert surface to find; none exists in the complete help TOC.

delivery-tracking-page

Customer-facing tracking is stated in its own right, distinct from the store-side route screen: "Customers can see if their order picked up and where the delivery is located on a map," tracked through the web order status page, with SMS alerts when the order is out for delivery and "when the delivery has arrived at the customers door." Grade corrected B to C — the page is marketing, which the floor permits for a table-stakes claim. https://www.microworks.com/products/rapidrun.htm · retrieved 2026-08-02 adversarially verified

delivery-promise-time differentiator

Documented mechanism, not just the feature name: "Estimated Delivery Minutes — This is the number of minutes which will be added to the time a delivery order is placed. This is used to calculate the Estimated Delivery Time, which can be displayed on the ordering screen at the completion of a delivery order." Lateness is policed alongside it by Mark Lates Automatic, Auto Late Minutes and a Route Late Order Warn that makes waiting orders flash. Worth carrying: the quote is a flat configured constant, not a load- or distance-computed promise. https://help.microworks.com/webhelp/Routing_Tab.htm · retrieved 2026-08-02

delivery-offline-behavior

The on-premise architecture — store-local Windows terminals and database with only nightly sync to hosted Storenet ("Hosted Server and Unit Locations Can Update Database Nightly") — structurally implies cash delivery orders, driver assignment (Assign_Orders.htm) and driver settlement (Cash_Drop.htm, Till_List.htm) continue to function during an internet outage, since none of that machinery depends on the cloud link. Shortfall: the vendor never states this explicitly for delivery specifically, so it remains an inference rather than a documented behavior. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-04

digital-first-party-web

WebOrder — custom-branded online ordering portal tightly integrated with the store POS. No marketplace commission model; per-order economics not published. https://www.microworks.com/products/web-ordering.htm · retrieved 2026-08-01

digital-menu-single-source

WebOrder "uses all of the same menu and location settings that are pre-programmed into your store POS system." https://www.microworks.com/products/web-ordering.htm · retrieved 2026-08-01

digital-native-app differentiator

Branded native apps do exist: the App Store lists the Greco Pizza consumer ordering app with seller "Microworks POS Solutions, Inc.", and the same developer publishes Greco Pizza (com.microworks.weborder.grecopizza) and Mark's Pizzeria on Google Play. Shortfall: two bespoke builds for two named chains is not a productised capability. The PrISM consumer-facing book is Web Ordering Overview and Customer Interface — browser ordering — with no native-app, branding or store-submission topic anywhere in the help TOC, and Microworks publishes no app product page, pricing or self-serve path. The Apple listing shows 2.1/5 across 50 ratings. https://apps.apple.com/ca/app/greco-pizza/id881537471 · retrieved 2026-08-02 adversarially verified

digital-account-saved-payment

Customer accounts with managed orders and saved card handling, plus POS-side "Customer Profile and Order Statistics." Guest checkout also supported. One-tap reorder is not documented. https://www.microworks.com/products/web-ordering.htm · retrieved 2026-08-01

digital-upsell-engine differentiator

The complete Web Ordering book — Web_Ordering_Overview.htm, Customer_Interface.htm, Reporting.htm — was read in full. The checkout flow is documented step by step (menu browse, item customization, order-type/schedule/coupon/payment selection, confirmation, favorite-order save) with no upsell, cross-sell, or suggested-item prompt at any step, and no attach-rate report exists in Reporting.htm's Order List/User List/Performance Report set. https://help.microworks.com/webhelp/Customer_Interface.htm · retrieved 2026-08-04

digital-scheduled-pacing

Future/scheduled orders supported; per-daypart capacity throttling and automatic slot closure are not documented. https://www.microworks.com/products/web-ordering.htm · retrieved 2026-08-01

digital-fulfillment-modes

Verified verbatim: "Pick-Up and Pay, Pre-Pay and Pick Up, Pre-Pay and Delivery, Delivery and Pay at the Door, Contactless Delivery, Curbside," with customers texting "HERE" for curbside arrival. Also worth adding to digital-account-saved-payment: "favorite order recall" is documented, which the dossier called undocumented. https://www.microworks.com/products/web-ordering.htm · retrieved 2026-08-01 adversarially verified

digital-qr-table

QR scan-to-order-and-pay is offered; attachment to an existing POS check, splitting, and tipping are not documented. https://www.microworks.com/products/kiosk-qr-ordering.htm · retrieved 2026-08-01

digital-kiosk differentiator

Self-order kiosk reuses the existing WebOrder menu, pricing, and UI and takes contactless payment. ADA/accessibility conformance is not documented. https://www.microworks.com/products/kiosk-qr-ordering.htm · retrieved 2026-08-01

digital-group-ordering

Flagging a trap the dossier avoided and that a re-researcher might fall into: a PMQ spotlight page surfaces "half-and-half pizzas, group ordering and SMS texting" adjacent to the Microworks entry, but those features belong to One Click Dining, a different vendor on the same page, and the article is from 2013. Do not attribute group ordering to Microworks. adversarially verified

digital-catering-portal differentiator

Catering exists as a POS order type; a distinct digital catering flow with minimums, quotes, deposits, or invoicing is not documented.

digital-voice-ai-phone differentiator

The complete 488-topic help TOC and full vendor product catalogue contain no AI, voice, or phone-ordering-automation topic. The only phone-adjacent feature documented anywhere is Caller ID Customer Link, an inbound-call customer-record lookup, not order transcription or injection. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

digital-drivethru-ai

No drive-thru product or hardware is sold (order-capture-drive-thru, no), so there can be no drive-thru voice-AI layered on top of it; none is named anywhere on the vendor site or in the manual. https://www.microworks.com/products.htm · retrieved 2026-08-04

digital-sms-ordering

The Notification Service handles inbound keyword replies (customer texts "HERE" for curbside) but text-to-order is not documented.

digital-google-order differentiator

Examined 2026-08-04, unresolved. The complete Web Ordering book of the administrator manual (Web_Ordering_Overview.htm, Customer_Interface.htm, Reporting.htm — its full extent per the help TOC) mentions Google only as Google Maps: delivery-address mapping in the overview and address verification against Google Maps in the customer interface. The web-ordering marketing page (microworks.com/products/web-ordering.htm, re-read 2026-08-04) mentions Google only inside analytics scripts. Nothing anywhere addresses Order with Google or provisioning the direct ordering link to a Google Business Profile — but GBP provisioning is a service-side act performed in Google's dashboard that would not necessarily appear in a manual of this vintage, so absence of mention cannot carry a no.

digital-apple-business-connect

The complete Web Ordering book mentions Google only as Google Maps for delivery-address mapping (digital-google-order, existing cell) and never mentions Apple Maps, Apple Business Connect, or an 'Order Food' place-card action. No such topic exists anywhere in the manual or on the marketing site. https://help.microworks.com/webhelp/Web_Ordering_Overview.htm · retrieved 2026-08-04

digital-loyalty-attach

Loyalty exists in the POS; whether it accrues and redeems inside WebOrder under the same identity is not documented.

digital-subscriptions

The complete Web Ordering book documents account creation, guest checkout, favorite-order recall, and one-time payment at checkout, with no recurring-billing, membership, or subscription concept anywhere. No subscription topic exists elsewhere in the 488-topic manual. https://help.microworks.com/webhelp/Customer_Interface.htm · retrieved 2026-08-04

digital-promo-parity

Channel scoping is explicit: the Advertised Coupon Advanced tab lets you "control whether the coupon is available for Online Ordering", and modifier lists carry a Visibility flag of All / In-Store Only / Web Only. Shortfall: this is a per-coupon opt-in rather than parity — the manual documents no mechanism guaranteeing that in-store promotions appear on the web channel, and third-party marketplace channels are not addressed at all. https://help.microworks.com/webhelp/Advertised_Coupons.htm · retrieved 2026-08-02

digital-guest-data-ownership differentiator

The Web Ordering Reporting book documents a self-serve bulk guest export: the User List report is filterable by Name/Email/Phone and by Registered/First Order/Last Order/Ordered date ranges, carries a "NoEmails" column recording promotional opt-out, and exports to XML or CSV; the separate Order List report exports full order history the same way. Both are standard reporting-screen functions with no fee or vendor-approval step documented. https://help.microworks.com/webhelp/Reporting.htm · retrieved 2026-08-04

digital-checkout-pci-sca

Tokenization and P2PE are claimed platform-wide and WebOrder is described as a "secure" pre-pay flow. Hosted fields/hosted page, 3DS, and PCI DSS 4.0 script-integrity compliance are not documented. https://www.microworks.com/products/payments.htm · retrieved 2026-08-01

digital-surcharge-transparency differentiator

No dual-pricing/surcharge/service-fee configuration exists anywhere in the pricing engine (payments-dual-pricing, no), so digital channels cannot mirror one. The complete web-ordering checkout flow (Customer_Interface.htm) documents coupon and payment-type selection with no fee-disclosure step of any kind. https://help.microworks.com/webhelp/Customer_Interface.htm · retrieved 2026-08-04

guest-loyalty-unified-profile

WebOrder writes into the same store POS database that holds "Customer Profile and Order Statistics," so in-store and online share one record. Dedup/merge behavior and kiosk attachment are undocumented. https://www.microworks.com/products/web-ordering.htm · retrieved 2026-08-01

guest-loyalty-thirdparty-identity-attach differentiator

Examined 2026-08-04, unresolved for a prior reason: whether third-party marketplace orders reach PrISM at all is itself unestablished — the 2026-08-02 adversarial pass moved both third-party-delivery cells to unknown because their only basis was one hedged marketing sentence, and the complete help TOC (whtdata0-6.xml) has no marketplace-integration topic. With no documented ingestion path there is no way to determine whether an arriving DoorDash/Uber Eats/Grubhub order would attach to the phone/address-keyed PrISM customer file (Update_Customers.htm, Marketing Module) or land as an anonymous ticket. Unresolvable until the integration's existence is established.

guest-loyalty-accrual-models

Two configurable accrual models are documented. Spend-based: "The Buyer's Club is based on a point system, where point values can be set up based on order ticket totals. In turn, points can be awarded to customers each time they order if they meet your minimum order value requirements." Item-based: the menu item Advanced tab has a Points field — "Assigning a value to this field will cause this item to add that number of points to the customer's total when ordered." Redemption is by point-threshold coupons ("Club Points — This is the number of points required for this coupon to be issued"), with the matching Advertised Coupon carrying a Points Req. that "will deduct that number of points from the customer's total". Native, no bolt-on vendor. https://help.microworks.com/webhelp/Buyer_s_Club_Setup.htm · retrieved 2026-08-02

guest-loyalty-tiers differentiator

The complete loyalty/marketing surface — Buyer's Club Setup (flat point accrual and threshold-coupon redemption), Comeback Coupons (recency-triggered, not status-based), and the 13-topic Marketing Module book (Overview, Customer Activity, Order History, Mailing History, Menu, Other, Sectors, Carrier Routes, Exclusions, Area Type, Labels) — has no status-tier concept, no promotion/demotion rule, and no rolling-window spend or visit-count threshold that changes a customer's standing. https://help.microworks.com/webhelp/Buyer_s_Club_Setup.htm · retrieved 2026-08-04

guest-loyalty-offline-behavior differentiator

No topic anywhere in the manual addresses loyalty lookup, accrual, or redemption behavior specifically during a connectivity loss. Buyer's Club and Gift Certificate balances live in the store-local database (queried locally, not cloud-dependent), which structurally suggests continuity, but the vendor never states this for loyalty specifically.

guest-loyalty-offer-stacking-rules differentiator

Precedence controls exist inside one coupon: "Ask Discount — This will override all other discounts set up on the coupon", Allow Multiple decides whether Set Price hits every qualifying item or only one, Apply % Off restricts the order-level percentage "only to this item, rather than all items on the order", and requirement lines are evaluated independently ("if you set up a requirement line of one pizza and then a second requirement line of one pizza, the system will not check for two pizzas"). Shortfall: nothing documents interaction between two different coupons on one order — no exclusive-versus-combinable flag and no order-of-application rule across coupons. https://help.microworks.com/webhelp/Advertised_Coupons.htm · retrieved 2026-08-02

guest-loyalty-targeted-offers differentiator

Offers are issued to a rule-defined audience, not broadcast. Comeback Coupons "can be created to target specific customers based on the frequency, or infrequency, of their ordering habits", keyed on "Days Since Last Order" with "Days Before Expiration" and a percentage off. Buyer's Club issues coupons on a points threshold derived from ticket totals, and the Marketing Module "uses your system order history data to allow you to target specific customers to print or export". Caveat carried: issuance is by printed coupon on the customer's next receipt or by direct mail, not by email or SMS. https://help.microworks.com/webhelp/Comeback_Coupons.htm · retrieved 2026-08-02

guest-loyalty-rfm-segmentation differentiator

Recency is computed by the system without the operator writing a query — Comeback Coupons evaluate "Days Since Last Order" per customer at order time, and the published report catalogue carries "Welcome Back" and "Late-New Customers" lists. Shortfall: no frequency or monetary scoring, no named lifecycle segments (new / regular / at-risk / VIP), and the Marketing Module's own targeting is geographic (Sectors, Carrier Routes, Area Type, Exclusions) rather than value-based. https://help.microworks.com/webhelp/Comeback_Coupons.htm · retrieved 2026-08-02

guest-loyalty-lifecycle-automation

Always-on triggered automations, configured once and left running. First-visit thank-you: "if you wish to create a coupon for customers who have never ordered, this value would be set to zero. As such, the Comeback Coupon will print out with their first order." Lapsed win-back: any positive Days Since Last Order value. Expiry is computed automatically — "Based on the date when the coupon is issued, the system will read this value and calculate the appropriate expiration date." Caveats: no birthday trigger is documented, and delivery is limited to thermal receipt printing. https://help.microworks.com/webhelp/Comeback_Coupons.htm · retrieved 2026-08-02

guest-loyalty-native-email-sms differentiator

Grade upgraded from a marketing page to the admin manual, and the shortfall is now precisely nameable. The Marketing Module's documented output is physical direct mail: "The PrISM Marketing Module supports three Avery-compatible label formats - 4144, 5160, and 5335", with Address to Name and "Or Current Resident" handling. The only native email and SMS in the 488-topic help system is Advanced Reporting, which sends *reports* to staff contacts ("send reports and other information via email or even cellular phone text message"). Shortfall: no in-product guest campaign builder for either channel; guest SMS is the transactional Prism Notification Service, and email campaigns are sold as a Microworks in-house marketing services engagement. https://help.microworks.com/webhelp/Labels.htm · retrieved 2026-08-02

guest-loyalty-consent-management

The site footer links an SMS Policy, indicating some consent framing, but per-channel consent capture with timestamp/source and revocation handling is not documented.

guest-loyalty-10dlc-registration

SMS capability exists (Prism Notification Service for transactional texts; Advanced Reporting can deliver reports by cellular text), but no topic anywhere addresses A2P 10DLC brand/campaign registration, carrier requirements, or who is responsible for it. Checked Advanced_Reporting_Overview.htm and the Marketing Module book; neither mentions SMS compliance registration.

guest-loyalty-campaign-attribution differentiator

A Coupon Count report tracks coupon redemption in the Products/Promotion Analysis category. Incremental-sales attribution tied to check totals is not documented. https://www.microworks.com/products/reporting.htm · retrieved 2026-08-01

guest-loyalty-data-export-portability differentiator

The Marketing Module "uses your system order history data to allow you to target specific customers to print or export", so a self-serve guest export exists. Shortfall: the manual documents no export file format, no field list, and no transaction-history export — the export is scoped to a targeted mailing audience — and there is no API, so a full guest-plus-history extract is not evidenced. https://help.microworks.com/webhelp/Marketing_Module_Overview.htm · retrieved 2026-08-02

guest-loyalty-cdp-event-api differentiator

There is no public API or webhook of any kind (extensibility-webhooks-push, no; reporting-public-api, no) — the complete 488-topic help TOC has no API, event, or integration topic. With no outbound event mechanism to build on, no CDP/marketing-platform subscription surface (Olo, Punchh, Bridg, Klaviyo or otherwise) can exist. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

guest-loyalty-review-capture-routing differentiator

The vendor states the absence directly: the survey feature only prints an invitation on the receipt directing the customer to a survey "you have set up elsewhere; a website, for example," and "there is no actual survey response tracking built into the PrISM system." With no response collection, there is no score-based routing to private recovery or public review sites. https://help.microworks.com/webhelp/Customer_Survey.htm · retrieved 2026-08-04

guest-loyalty-referral-program

Positive absence by enumeration of the complete marketing/loyalty toolset. The help TOC enumerates every marketing mechanic in the product: Buyer's Club points accrual/redemption (Buyer_s_Club_Setup.htm), Comeback Coupons (recency-triggered win-back), Advertised Coupons, Customer Survey, and the Marketing Module whose output channel is direct-mail Labels. No referral topic exists anywhere in the TOC, and none of the retrieved loyalty topics mention per-guest codes or links, attribution of a referred guest's first order, or two-sided rewards. A native referral mechanic could not be configured without appearing in this enumerated surface. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

guest-loyalty-wallet-pass differentiator

Gift Certificates and Buyer's Club points are documented as store-printed receipts and in-database balances only; neither topic, nor any topic in the Marketing Module or Web Ordering books, mentions an Apple Wallet or Google Wallet pass. No wallet-pass topic exists anywhere in the 488-topic manual. https://help.microworks.com/webhelp/Gift_Certificates.htm · retrieved 2026-08-04

guest-loyalty-privacy-rights-tooling

Attempted to check the customer-record maintenance screen for deletion/export tooling; the expected topic (Update_Customer.htm) returned the marketing homepage rather than manual content, so its field list could not be confirmed. No CCPA/CPRA/GDPR, data-subject-request, or deletion-propagation topic is named anywhere else in the manual or on the site. Genuinely unresolved rather than established absent.

guest-loyalty-redemption-fraud-controls

A general-purpose control applies to any gated function including coupon and points overrides: each coupon carries a Password Required flag, and every password use "creates an entry... in the Weekly Exceptions browser," optionally with a recorded video (Setup_Password_Functions.htm). Shortfall: this is generic manager-password gating, not a loyalty-specific control — no redemption velocity limit, no employee-self-redemption flag, and no points-adjustment-specific approval step is documented. https://help.microworks.com/webhelp/Advertised_Coupons.htm · retrieved 2026-08-04

guest-loyalty-ai-offer-recommendation differentiator

The complete offer-targeting mechanism is deterministic and rule-based: Comeback Coupons key on operator-set "Days Since Last Order" thresholds, and Buyer's Club redemption is a flat points threshold. Neither topic, nor any topic in the Marketing Module book, describes any AI/ML-generated recommendation for offer content, audience, or send timing. https://help.microworks.com/webhelp/Comeback_Coupons.htm · retrieved 2026-08-04

guest-loyalty-stored-value-gift

A genuine native prepaid ledger: "Gift Certificate accounts are very similar in function to Customer Accounts with the exception that these accounts are pre-paid," created during order taking, with a transaction history of "payments, credits, and balance", a Credit Account function and Print Statement, plus an Open Gift Activity Report showing "all gift card activity for the date range you specify... the activation of new certificates as well as redemption of existing certificates" grouped per certificate. Shortfall: the activity report is transactional, not a period-end outstanding-liability total, and balances live in the store-local database with only a nightly StoreNet upload, so brand-wide cross-store redemption is undocumented. https://help.microworks.com/webhelp/Gift_Certificates.htm · retrieved 2026-08-02 adversarially verified

labor-clock-in-at-pos

"Employee Card or Fingerprint ID" at the POS station; Shift Sheet report in the Employee report family. https://www.microworks.com/products/restaurant-pos.htm · retrieved 2026-08-01

labor-photo-punch-verification differentiator

Fingerprint ID is documented, which is biometric rather than the photo/facial verification this item asks for; a photo-only mode is not documented.

labor-geofenced-mobile-punch

The complete time-clock documentation is a fixed-terminal punch (Clock In/Out, Start/Stop Break) tied to Employee Card or fingerprint ID at a POS station. No mobile app, GPS, or geofence validation is documented anywhere in the manual, and the Employee Scheduling Module's 12-topic book has no mobile-punch topic either. https://help.microworks.com/webhelp/Ordering_Module_Time_Clock.htm · retrieved 2026-08-04

labor-offline-time-punch differentiator

The time clock (Ordering_Module_Time_Clock.htm) is part of the store-local Ordering Module database, which structurally suggests punches record locally regardless of internet status, but no topic states this explicitly or describes reconciliation behavior on reconnect. Genuinely unresolved.

labor-granular-rbac

Permissions are per discrete action, not fixed tiers. "The Password Functions section controls which features of the PrISM system require passwords and which don't. The Password Functions browser is divided into various tabs representing different areas of the system", each function carrying Required / Camera / Log checkboxes. Password Groups are the roles: "Password Groups are essentially tiers of access; each group represents a set of permissions which is then assigned to one or more employees", built by moving individual functions into an Included list, with a Super User override checkbox. Individual menu items and coupons carry their own Password Protect / Password Required flags. Caveat: per-location scoping of a group is not documented — the password files are store-local. https://help.microworks.com/webhelp/Setup_Password_Functions.htm · retrieved 2026-08-02

labor-manager-override-audit

Every password-gated action is attributed and logged: "Every time a password is used, an entry is created in the Weekly Exceptions browser. If 'Log' is checked a second entry is created with additional information about the event." A per-function Camera option "tells the system to record and save a video when the function in question is accessed", viewable from the Weekly Exceptions Report. Discounts additionally capture a free-text Force Explanation onto the same report. Caveat: the manual makes no immutability or tamper-evidence claim about the exceptions log. https://help.microworks.com/webhelp/Setup_Password_Functions.htm · retrieved 2026-08-02

labor-native-scheduling differentiator

Re-tested by the verification pass because this cell had been scored three ways. "The PrISM Employee Scheduling Module provides comprehensive creation and modification of employee schedules, as well as access to all employee information defined within the system," with "access to key store volume, shift, and scheduling reports" and the ability to open an existing schedule or create a new one. The help TOC carries the whole book beneath it — Create Schedule, Schedule Management, New Schedule, Shifts, Shift Map, Availability, Forecast Indicators — plus an Availability tab on the employee file. Caveat: no publish-to-staff, shift-swap or mobile notification is documented; the schedule is a back-office artefact. https://help.microworks.com/webhelp/Employee_Scheduling_Overview.htm · retrieved 2026-08-02 adversarially verified

labor-demand-labor-forecast differentiator

Forecast Indicators are built from the operator's own POS data, not a static template: "You may create a Forecast Indicator based on any of the system volume measures. What this allows you to do is view how many employees represented by the Forecast Indicator need to be scheduled based on the average volume forecast", with a Numerator/Operator/Denominator formula over system volume measures. Shortfall: the output is a headcount from an operator-defined ratio against an "average volume forecast" whose derivation the manual never documents; there is no daypart-level recommendation and no labour-hour or labour-cost target. https://help.microworks.com/webhelp/Forecast_Indicators.htm · retrieved 2026-08-02

labor-realtime-labor-percent differentiator

Payroll_Tab.htm documents a "Labor Percentage Goal" field, which implies some percentage tracking exists, but no report or screen documenting a live actual-vs-goal display was found: Hourly_Reports.htm does not resolve to real content (redirects to the marketing homepage) and Server_Report.htm's complete field list (daily activity by server, order summary, server totals) has no labor-percentage figure. Where the goal is surfaced, and whether in real time, is not documented.

labor-overtime-prevention differentiator

The complete overtime configuration — Level 1/2 Overtime Rate, and Hours Before OT Level 1/2 Applies for Daily, Weekly, and Period periods — is a rate multiplier applied retroactively once a threshold is crossed, calculated at payroll/reporting time. No warning or block at clock-in, and no approaching-threshold notice, is documented anywhere in the manual. https://help.microworks.com/webhelp/Payroll_Tab.htm · retrieved 2026-08-04

labor-break-compliance-by-state differentiator

The time clock's break handling is documented in full and is a manual punch: "The Break function is used when an employee needs to take an unpaid break during their shift", with Start Break / Stop Break buttons and nothing else. The labour-law configuration surface (Payroll_Tab.htm) enumerates its four parts — overtime rate multipliers, daily/weekly hours-before-OT thresholds, a labor percentage goal, and pay-rate display toggles — so state-tunable rules exist for overtime only. No per-state or per-jurisdiction break rule configuration, no break attestation prompt, and no missed-break premium-pay flag appears in either topic or anywhere else in the complete help TOC. https://help.microworks.com/webhelp/Ordering_Module_Time_Clock.htm · retrieved 2026-08-04

labor-fair-workweek-support

The complete 12-topic Employee Scheduling Module book (Overview, Reports, Updates, Create Schedule, Schedule Management, New Schedule, Shifts, Shift Map, Availability, Forecast Indicators, Update Jobs, Employee Information) has no advance-notice deadline, schedule-change tracking, or predictability-pay calculation. The schedule is described (labor-native-scheduling, existing cell) as a back-office artefact with no publish-to-staff mechanism to even measure notice against. https://help.microworks.com/webhelp/Employee_Scheduling_Overview.htm · retrieved 2026-08-04

labor-minor-labor-rules

The employee file's Details tab — the only place ancillary employee data such as a birth date could live — states in the vendor's own words: "All fields on this tab are optional and are not used elsewhere in the system", which forecloses any age-driven enforcement. The Availability tab is manually entered Available/Preferred/Not Available time frames per day with no age dimension; the complete Employee Scheduling Module book (Create Schedule, Shifts, Shift Map, Availability, Forecast Indicators per whtdata3.xml) and the time clock documentation contain no minor-labor, age-based hours, prohibited-window, or school-day rule at either scheduling or clock-in. https://help.microworks.com/webhelp/Edit_Employee_File_-_Employee_Detail_Tab.htm · retrieved 2026-08-04

labor-tip-pooling-rules

Same finding as payments-tip-pooling: the complete Payroll tab field set has no tip-pool, tip-out, or distribution-rule field, and no such topic exists anywhere else in the manual. The only tip report is a per-server Server Tip listing, not an allocation engine. https://help.microworks.com/webhelp/Payroll_Tab.htm · retrieved 2026-08-04

labor-tip-distribution-audit-trail

A Server Tip report ships in the Cash Control catalog. Pool contribution and distribution detail per shift are not documented. https://www.microworks.com/products/reporting.htm · retrieved 2026-08-01

labor-qualified-tips-w2-reporting differentiator

The Payroll tab's complete field set has no cash-vs-charged-tip separation and no Treasury tipped-occupation code field. The only external payroll/accounting interface documented anywhere is the QuickBooks Pro 2002 desktop connector (QuickBooks_Interface_Module.htm), which carries no tip-specific W-2 coding. https://help.microworks.com/webhelp/Payroll_Tab.htm · retrieved 2026-08-04

labor-native-payroll differentiator

No payroll product appears in the 12-item catalog; the only accounting linkage documented is the QuickBooks Pro interface.

labor-payroll-export-formats

"Intuit QuickBooks Pro Interface" is the only named integration. A second major payroll provider is not documented. https://www.microworks.com/products/restaurant-pos.htm · retrieved 2026-08-01

labor-shift-swap-workflow differentiator

The complete Employee Scheduling Module book (12 topics, listed under labor-fair-workweek-support) has no shift-swap request, open-shift claim, or manager-approval-workflow topic. The module is described as a back-office scheduling tool with no employee self-service surface documented. https://help.microworks.com/webhelp/Employee_Scheduling_Overview.htm · retrieved 2026-08-04

labor-digital-onboarding-i9

The Employee Detail tab — the only place ancillary hire paperwork could live — states "all fields on this tab are optional and are not used elsewhere in the system." No W-4, I-9, or E-Verify topic exists anywhere in the Employee Scheduling Module book or the core Employee Information section of the manual. https://help.microworks.com/webhelp/Edit_Employee_File_-_Employee_Detail_Tab.htm · retrieved 2026-08-04

labor-server-performance-metrics differentiator

Per-employee sales metrics exist: Server Report carries "all of the server's totals for the day" by server number, under an Employee Reports book. Shortfall: average check per server, tip percentage, item mix and sales-per-labour-hour appear only as report names on the vendor marketing page (grade C) and are defined nowhere in the administrator manual; no productivity ratio against hours worked is documented anywhere in the help system. https://help.microworks.com/webhelp/Server_Report.htm · retrieved 2026-08-02 adversarially verified

inventory-recipe-bom-costing

Multi-level BOM is documented explicitly. Assembly Items "are those inventory items which are created by combining other inventory items, such as sauce or dough", and are themselves inventory items ("Because of this, the Stock Price is automatically calculated based on the portions of each inventory item that is used to assemble this item"), so a recipe containing Marinara Sauce inherits its component cost — the manual makes exactly that point: "setting up a menu item that contains Marinara Sauce no longer requires figuring out what inventory items are contained in that very small portion of sauce." The Recipe Cost Manager then rolls ingredients and modifiers to a Recipe Cost and Cost %. Caveat: costs are described as auto-calculated from Inventory Master portion price, but no statement guarantees an automatic re-run when an ingredient cost changes. https://help.microworks.com/webhelp/Assembly_Item_Setup.htm · retrieved 2026-08-02

inventory-unit-conversion-yields

A full three-tier conversion chain with explicit factors is documented: Stocking Unit (cases, bags) → "Stocking Mult — the number of Counting Units in the Stocking Unit" → Counting Unit ("the unit in which you count the item when doing a physical inventory") → "Portion Mult — the number of portioned units per Counting Unit" (32oz can portioned by ounce = 32) → Portion Unit, with Price and Portion Price auto-derived at each step. Alternate vendors may carry their own units and portions. Shortfall: no yield or waste percentage is applied to the raw-to-usable conversion anywhere in the item file. https://help.microworks.com/webhelp/Inventory_Master_u.htm · retrieved 2026-08-02

inventory-theoretical-vs-actual differentiator

The Daily Inventory screen is a theoretical-vs-actual variance sheet per item per count period: it "details the beginning inventory amount for each item, any delivery amount for the day as entered by the Add Invoice function, the ending inventory amount, the ideal ending amount (assuming Ideal Food Cost has been properly set up), and any variance from Ideal." The currency expression is the "Food Gap number on the Weekly Sales Recap", which the manual says goes to zero if the physical count is skipped. Theoretical usage comes from the Recipe Cost Manager BOM; actual comes from counts plus invoiced deliveries. https://help.microworks.com/webhelp/Daily_Inventory_Screen.htm · retrieved 2026-08-02

inventory-realtime-depletion differentiator

Recipe_Cost_Setup.htm defines the bill-of-materials that theoretical usage is computed from, but the actual on-hand decrement happens through the Daily Inventory screen's periodic reconciliation against Ideal Food Cost (Daily_Inventory_Screen.htm), not as each order fires. No topic anywhere states that a sale decrements on-hand inventory in real time; the documented model is theoretical-vs-actual variance at count-period boundaries. https://help.microworks.com/webhelp/Recipe_Cost_Setup.htm · retrieved 2026-08-04

inventory-86-auto-sync differentiator

Inventory_Master_u.htm's Reorder Level field only triggers a purchase-order suggestion ("the level at which you would like the system to prompt you to order more"); it has no link to menu-item availability. The menu item Advanced and Web tabs (fully enumerated) have no inventory-driven availability field, and Ordering_Advanced_Options.htm's Sold Out Item is a manual toggle, not inventory-threshold-triggered. https://help.microworks.com/webhelp/Inventory_Master_u.htm · retrieved 2026-08-04

inventory-count-modes

Recurring cycle counts are configured per item — "Inv. Cycle — This is the frequency of when a physical inventory is taken for this item. Your choices are D - Daily, W - Weekly, M - Monthly, B - Biweekly, or N - None" — and a full physical count is entered on the Daily Inventory screen, with Inventory Locations (Freezer, Dry Storage) to sort the count sheet. Two shortfalls, one of them serious: no ad-hoc spot-count mode for an arbitrary subset is documented, and counts are overwritable rather than kept as separate history — "If you enter a manual ending inventory count and you are using the Ideal Food Cost feature, do not go back into the Daily Inventory Screen after entering your count. The system will automatically recalculate the ending inventory values based on Ideal Food Cost, and the manual figures you had entered will be replaced." https://help.microworks.com/webhelp/Inventory_Master_u.htm · retrieved 2026-08-02

inventory-mobile-count-offline

The complete physical-counting documentation — Daily_Inventory_Screen.htm's Count column entry and Inventory_Master_u.htm's Inv. Cycle field — describes desktop-terminal entry only. No mobile app, tablet, barcode, or QR scanning device is named anywhere in the two topics that constitute the entire inventory-counting surface of the 488-topic manual. https://help.microworks.com/webhelp/Daily_Inventory_Screen.htm · retrieved 2026-08-04

inventory-vendor-catalogs-edi differentiator

The manual enumerates the alternative and it is entirely manual. Vendors are free-form per-item fields — "Item Number — The vendor's item number. If you do not purchase this item from a specific vendor, you may assign an arbitrary number", plus a Vendors/Stocking table where "you may specify alternate vendors... alternate means of pricing, stocking units, counting units, and portion amounts" typed in by hand. Receiving is manual invoice entry via Add/Modify Invoice, and purchase orders are printed forms ("allows you to print out a form with the quantities you wish to order"). No distributor integration, catalogue import or electronic PO/invoice transmission topic exists anywhere in the 488-topic help system. https://help.microworks.com/webhelp/Inventory_Master_u.htm · retrieved 2026-08-02

inventory-invoice-ocr differentiator

The complete invoice-entry mechanism is manual: "Add Invoice" records delivery amounts by hand, and the "Load PO" button imports items from an existing PrISM-generated purchase order — not from a photographed, PDF, or emailed supplier invoice. No OCR, image-ingestion, or email-parsing topic exists anywhere in the manual. https://help.microworks.com/webhelp/Daily_Inventory_Screen.htm · retrieved 2026-08-04

inventory-price-change-alerts differentiator

Weekly Invoice and Weekly Invoice Detail reports track received invoice pricing, but no threshold alerting is documented.

inventory-par-auto-suggest differentiator

Both halves are documented. Static par per item: "Reorder Level — This is the level at which you would like the system to prompt you to order more of the item. Enter this value as Stocking Units", with a Reorder Qty and a Re-order Level report. Forecast-driven mode: "The Purchase Orders function will prompt the system to suggest reorder quantities based on a future theoretical sales figure and allows you to print out a form with the quantities you wish to order", and the resulting PO loads into an invoice with the 'load PO' button on receipt. Caveat: par is per item in a store-local file — there is no above-store par management. https://help.microworks.com/webhelp/Daily_Inventory_Screen.htm · retrieved 2026-08-02

inventory-waste-logging

Same finding as kitchen-waste-logging: the complete inventory documentation (Daily_Inventory_Screen.htm, Inventory_Master_u.htm) has no waste/spoilage logging workflow, no reason-code field, and no waste-cost-separate-from-variance report. Variance from Ideal is a single aggregate figure, not itemized waste entries. https://help.microworks.com/webhelp/Daily_Inventory_Screen.htm · retrieved 2026-08-04

inventory-transfers

Inventory_Master_u.htm's Location field only attaches an item to a single Inventory Location (e.g., Freezer, Dry Storage) within one store. inventory-commissary (existing cell) already established that only the receiving store's view is documented, with "no inter-location transfer document." No transfer, in-transit, or approval-state topic exists anywhere in the manual. https://help.microworks.com/webhelp/Inventory_Master_u.htm · retrieved 2026-08-04

inventory-commissary

The purchasing side is explicitly built for it: the Purchase Orders function "was designed specifically for franchise-type operations that use a central commissary for inventory ordering/delivery", and in-store production of prep items is handled by Assembly Items, where counting the finished batch "will also take the appropriate amounts out of your inventory for the items used to create the batch". Shortfall: only the receiving store's view is documented — there is no commissary-side production run, no inter-location transfer document, and no computed transfer cost or inter-company billing. https://help.microworks.com/webhelp/Daily_Inventory_Screen.htm · retrieved 2026-08-02

inventory-lot-traceability

The complete inventory item field set (Item Number, Stock Price, Stocking/Counting/Portion Units and Multipliers, Reorder Level/Qty, Key Ingredient, Assembly Item, Batch Description) has no lot or batch number field for received or produced stock — "Batch Description" is a free-text label for an Assembly Item recipe, not a traceable lot ID. No recall-trace topic exists anywhere in the manual. https://help.microworks.com/webhelp/Inventory_Master_u.htm · retrieved 2026-08-04

inventory-shelf-life-expiry

The complete inventory item field set has no expiration or use-by date field and no expiring-soon report or alert. Inv. Cycle governs count frequency (D/W/M/B/N), not shelf life. https://help.microworks.com/webhelp/Inventory_Master_u.htm · retrieved 2026-08-04

inventory-bar-partial-bottle

The unit-conversion chain (Stocking Unit → Counting Unit → Portion Unit, with Stocking Mult and Portion Mult) is generic and manually typed for any item; no scale/weight integration and no bottle-fraction counting mode is documented, and no bar/beverage-specific counting topic exists anywhere in the manual. https://help.microworks.com/webhelp/Inventory_Master_u.htm · retrieved 2026-08-04

inventory-cogs-gl-export

Intuit QuickBooks Pro interface is named. Per-category GL account mapping and a second named accounting system are not documented. https://www.microworks.com/products/restaurant-pos.htm · retrieved 2026-08-01

inventory-native-not-partner differentiator

Re-sourced from marketing to the manual by the verification pass. Recipe Cost Manager lets you "specify which inventory items, and in what amounts, are always used to assemble a given menu item. This aides in the providing accurate food cost calculations," with portion units, auto-derived assembly cost, order-type-dependent components and modifier costs. Assembly Item Setup, Inventory Master, Inventory Prices, Inventory Location and the Daily Inventory variance sheet are all first-party PrISM topics; no third-party product is named in the inventory books. https://help.microworks.com/webhelp/Recipe_Cost_Setup.htm · retrieved 2026-08-02 adversarially verified

inventory-menu-margin-linkage differentiator

Product Mix and recipe costing both exist but a joined contribution-margin-per-item report with threshold flagging is not documented.

reporting-realtime-dashboard

Confirmed, and if anything the partial is generous-leaning-correct: Storenet is browser/mobile accessible but the documented mechanism is a nightly full-database upload per store, so above-store figures are next-day. There is no evidence of intraday polling. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01 adversarially verified

reporting-eod-closeout

Daily Paperwork, Simple Sales, and the Cash Control family (Weekly/Monthly Cash, Cash Drop, Settle, System Transaction) constitute a daily close-out set. https://www.microworks.com/products/reporting.htm · retrieved 2026-08-01

reporting-pmix-modifier-level

The Mix Detail report is modifier-level by default and the manual proves it by documenting the switch that turns it off: "Hide Modifiers — This hides all modifiers that were added to items, but still displays a separate line for each menu item", alongside "Hide all detail" for group totals only. It is daypart-filterable ("Start Time / End Time — The report will display items sold between the start time and the end time"), groupable "by menu group, by primary or secondary product code", sortable by quantity or dollar value, with an item filter for food / beverage / other and a Show Zero Values option. Revenue-centre scoping comes from the shared Report Filter / Cost Center selector. https://help.microworks.com/webhelp/Scheduled_Reports.htm · retrieved 2026-08-02

reporting-comps-voids-audit

The Exceptions report carries every element the claim asks for: "Exception Type — You may choose to show all exceptions that took place during the set time frame, to only display Reduced/Canceled/Bad orders, or to only display exceptions other than Reduced/Canceled/Bad orders", filtered by Start Time / End Time and by "all employees, or only one specific employee", with Show Detail adding "any additional information about events". Reason codes arrive via the coupon Force Explanation option, whose free text "can be viewed on the Weekly Exceptions Report", and approver attribution via the password log entry written on every gated action. https://help.microworks.com/webhelp/Scheduled_Reports.htm · retrieved 2026-08-02

reporting-cash-over-short

Cash Control family: Weekly Cash, Monthly Cash, Cash Drop, Settle, System Transaction — plus "Detailed Cash Control options for Servers and Tills" on the POS page. https://www.microworks.com/products/reporting.htm · retrieved 2026-08-01

reporting-labor-productivity

"Food & labor cost analysis" plus employee shift/schedule reports. Sales-per-labor-hour and labor-percent-by-hour slicing are not documented. https://www.microworks.com/products/pizza-pos.htm · retrieved 2026-08-01

reporting-server-scorecards differentiator

Server Report is "a summary of a server's activity for the day", "generated according to server number", with an optional "one-line summary of each order assigned to the server" and the server's totals. Shortfall: that is a per-server day sheet run one server at a time — no cross-server ranking, league table, benchmark or trend. The scorecard metrics previously cited (Average Ticket, Server Ticket, Server Mix, Server Tip) are report titles on the marketing reporting page, which is grade C, and are defined nowhere in the manual. https://help.microworks.com/webhelp/Server_Report.htm · retrieved 2026-08-02 adversarially verified

reporting-channel-profitability differentiator

Profit Center Ledger supports revenue/order-type separation. Marketplace-commission-net margin per third-party channel is not documented. https://www.microworks.com/products/reporting.htm · retrieved 2026-08-01

reporting-multiloc-drilldown differentiator

Storenet reports by individual store or across all stores, in spreadsheet format. Drill-down from group total to individual transaction is not documented. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01

reporting-custom-report-builder differentiator

A saved, operator-built report definition exists: "Custom reports, also referred to as simple reports, allow you to custom-tailor reports that show only the information you want", where each candidate Field has a checkbox controlling whether "this value will appear on the report", plus Column and Sort placement, a one- or two-column layout, an SMS format, and a saved Report Name; Report Filter and Cost Center can then be applied when it is scheduled. Shortfall: it selects and arranges fields from a fixed list into a summary sheet — there is no choice of dimension or measure, no grouping or aggregation control, no filter expression, and it cannot reach the transaction detail the canned reports expose. https://help.microworks.com/webhelp/Setup_Custom_Reports.htm · retrieved 2026-08-02

reporting-scheduled-delivery

"The Scheduled Reports section is used to configure reports that are emailed out, saved as a new file, or printed out automatically, as well as when these events take place." Cadence: "End of Day", "Specific Time", or "Interval" with a Start time and Repeat Minutes ("if the Start time is 12:00 PM and the Repeat Minutes is 60, the report will activate at 12 PM, then again at 1 PM"). Recipient list: "All email addresses you wish to send reports to must be set up in the Contacts section." Destinations: Save Report, Save Report As a chosen folder, Email Report To, or Print Report To a named printer; formats PDF or HTML; custom reports may be formatted as an SMS to a cellular phone. https://help.microworks.com/webhelp/Scheduled_Reports.htm · retrieved 2026-08-02

reporting-raw-warehouse-export differentiator

The automated-export destinations are enumerated in full and none is a customer-controlled data destination: "Export Type... Save Report — This will save the report as a new file in the default reports folder. On most systems, this default folder is located at C:\VPSM\REPORTS", Save Report As a chosen local path, Email Report To, or Print Report To. The only formats offered are "a PDF file (opens in Adobe Acrobat Reader), or HTML". There is no CSV, no SQL or flat-file extract, no SFTP/S3/warehouse target, and no API in the help system to carry one. The operator does physically possess the store-local database, but that is file access, not a documented export. https://help.microworks.com/webhelp/Scheduled_Reports.htm · retrieved 2026-08-02

reporting-public-api differentiator

Citation replaced. The previous evidence was microworks.com/sitemap.xml, which the verification pass correctly ruled unsafe because it does not cover the documentation host. The replacement is the documentation host's own table of contents: the complete PrISM WebHelp TOC enumerates every topic in the system across eleven books (Getting Started, Manager, Ordering, Marketing, Makeline Monitor, Employee Scheduling, Integrated Credit Card Authorization, QuickBooks Integration, Software Installation, Advanced Features, Help & Troubleshooting) and contains no API, developer, integration, webhook or export topic. The only documented outbound interface is a desktop QuickBooks file interface. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-02

reporting-webhooks differentiator

Consistent with the already-established extensibility-webhooks-push (no) on the same citation: the complete help TOC across eleven books contains no webhook, event, or callback topic. The only outbound surfaces are Scheduled_Reports.htm (PDF/HTML files to folder/email/printer) and the QuickBooks desktop file interface. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

reporting-api-not-upcharged differentiator

There is no public API at all (reporting-public-api, no; api_posture.public_api: none), so there is nothing to be included or upcharged. The claim's premise — API and raw-data access, at some price point — does not exist in the documented product. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

reporting-tier-paywall differentiator

No published plan tiers exist, so whether reporting is tier-gated cannot be determined. All ~39 sample reports are published openly as one catalog, which suggests a single bundled report set.

reporting-history-retention differentiator

No topic anywhere in the manual or on the marketing site states a retention window for transaction-level detail. The store-local database architecture (nightly sync to Storenet) means retention is structurally a function of local disk space and store practice, not a published policy; checked Scheduled_Reports.htm and Daily_Inventory_Screen.htm, neither of which mentions retention or archival.

reporting-anomaly-alerts differentiator

Scheduled_Reports.htm documents all three report-trigger mechanisms in full: End of Day, Specific Time, and Interval (Start time plus Repeat Minutes). All three are time-based; none is conditioned on a metric threshold or a deviation from historical pattern. No anomaly, alert, or push-notification topic exists anywhere else in the manual. https://help.microworks.com/webhelp/Scheduled_Reports.htm · retrieved 2026-08-04

reporting-nl-query

The complete 488-topic help TOC has no AI, natural-language, chat, or assistant topic anywhere; the only report-building surfaces are canned reports and the field-selection Custom Report builder (Setup_Custom_Reports.htm), which requires manually checking fixed fields, not asking a question in plain language. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

reporting-guest-cohorts differentiator

Score stands but the underlying evidence is misread in both this cell and guest-loyalty-targeted-offers. The report is "No/Bad Check List" — an NSF/bad-check list — not a "No Checks" lapsed-customer report. The lapsed/win-back function is carried by "Welcome Back" and "Late-New Customers" alone. Correct the note before anyone builds a claim on it. https://www.microworks.com/products/reporting.htm · retrieved 2026-08-01 adversarially verified

reporting-sales-forecast differentiator

Forecast Indicators — the only forecast mechanism documented anywhere — computes a labour-to-volume ratio for staffing purposes ("how many employees... need to be scheduled based on the average volume forecast"), not a forward sales figure at daypart/hourly granularity exposed in the reporting UI. No separate sales-forecast topic exists in the manual. https://help.microworks.com/webhelp/Forecast_Indicators.htm · retrieved 2026-08-04

reporting-tip-tax-compliance

Server Tip report exists. Declared-vs-charged split, pool distribution detail, and jurisdictional tax liability summary are not documented. https://www.microworks.com/products/reporting.htm · retrieved 2026-08-01

multi-location-org-hierarchy

Storenet manages an enterprise over its stores — two levels. A named region/group tier as a first-class scoping object is not documented.

multi-location-central-menu-publish

A single "Master" menu and inventory is shared across locations via Storenet. Selective publish to a chosen location set, and publish/version history with who-and-when, are not documented. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01

multi-location-local-override-policy differentiator

Storenet provides "tools to manage differences in pricing, costs, and product selection" per store. Per-field lock/unlock governance enforced at store level is not documented. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01

multi-location-price-zones

Per-location price differences are managed centrally off one master item. Per-channel and per-daypart price tiers are not documented. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01

multi-location-scheduled-publish differentiator

Storenet Satellite's master-data distribution is documented as immediate and irreversible, not scheduled or rollback-able: a franchise master upload "cannot be undone," and stores "download the updated data at the next prescribed interval" — a fixed sync cadence, not a chosen future activation time interpreted per store timezone. No preview, staged-activation, or rollback mechanism is documented anywhere. https://help.microworks.com/webhelp/Upload_Dataset_Satellite.htm · retrieved 2026-08-04

multi-location-new-store-template differentiator

The complete Software Installation book (Overview, Installing PrISM for Windows, USB Software License Keylok, Users Accounts & Passwords, Network Protocols, Computer Name and Workgroup, Installing Workstations and Devices) documents a from-scratch install process, not cloning a saved configuration template. No template, clone, or time-to-open figure is published anywhere on the vendor site or in the manual. https://help.microworks.com/webhelp/whxdata/whtdata5.xml · retrieved 2026-08-04

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

Franchise use is evidenced only by customer testimonials (Sarpino's, Glass Nickel franchising); the permission model separating franchisor from franchisee tenant is not documented.

multi-location-royalty-calculation differentiator

Enterprise-management.htm, the sole Storenet documentation, describes shared master menu/inventory and centrally managed pricing but says nothing about franchise royalty, ad-fund, or marketing-fee calculation from net sales. No royalty topic exists anywhere in the manual. Genuine absence of evidence, consistent with the existing menu-pricing-franchise-hierarchy finding that flagged this gap.

multi-location-royalty-collection

Same basis as multi-location-royalty-calculation: no royalty concept is documented at all, so ACH/debit collection of a royalty that is itself unestablished cannot be assessed.

multi-location-consolidated-reporting

Storenet delivers reporting by individual store or across all locations, accessible by browser or mobile, in spreadsheet format. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01

multi-location-normalized-item-rollup differentiator

Enterprise-management.htm states Storenet shares a single master menu and inventory across locations and provides tools to manage per-store price/cost/selection differences, which implies some corporate item identity, but no topic states whether item-level sales still roll up under a shared corporate ID after a store locally renames or reprices an item. No rollup-reporting topic exists in the manual.

multi-location-cross-location-giftcard

Gift cards are listed as a Storenet centrally managed capability across locations. Outstanding-liability reporting and inter-store redemption settlement are not documented. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01

multi-location-cross-location-loyalty

Customer loyalty programs are listed as a Storenet centrally managed capability. A single shared profile/balance/history across all stores is implied but not explicitly stated. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01

multi-location-multi-brand differentiator

Storenet's documented purpose throughout enterprise-management.htm is a single 'Master' menu and inventory shared by multiple locations of one operation, with tools to manage per-store differences in price/cost/selection — not two distinct brands with separate menus, receipts, and reportable revenue on shared hardware. No virtual-brand, multi-brand, or dual-menu-on-one-terminal topic exists anywhere in the manual. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-04

multi-location-multi-tax-jurisdiction

A per-location tax rate is documented: "Sales Tax — The location's total sales tax rate," configured on the Ordering tab of Location Maintenance, so each location can carry its own rate. Shortfall: the field is a single total rate, not multiple simultaneous jurisdiction-specific rates, and the documentation warns changing it "will update every order in the system (on the current day)" including settled orders — the opposite of clean multi-jurisdiction handling. No prepared-food-vs-grocery split, inclusive/exclusive toggle, or per-location exemption is documented. https://help.microworks.com/webhelp/Ordering_Tab.htm · retrieved 2026-08-04

multi-location-config-audit-log differentiator

Storenet has "activity logs tracking data uploads and synchronization" — sync logs, not a configuration-change audit trail.

multi-location-enterprise-api differentiator

There is no public API of any kind (reporting-public-api, no), and Storenet's own reporting is described (reporting-realtime-dashboard, existing cell) as a nightly full-database upload viewed in a browser/mobile UI, not a queryable multi-location data warehouse or authenticated bulk-transaction API. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

multi-location-central-labor-policy

Labor rules are configured per individual location — each Location Maintenance record carries its own Payroll tab with OT rate multipliers and Hours Before OT thresholds, enforced at that location's terminals during clock-in/payroll calculation. Shortfall: this is single-location configuration, not a location-group policy tier; Storenet's one-way nightly menu/inventory distribution (Upload_Dataset_Satellite.htm) does not extend to labor policy, and no predictive-scheduling or break-rule enforcement exists at any level (labor-break-compliance-by-state, existing cell: no). https://help.microworks.com/webhelp/Payroll_Tab.htm · retrieved 2026-08-04

hardware-commodity-devices differentiator

Documented directly: "Microworks PrISM for Windows turn-key systems ship on Dell(TM) hardware," naming a Mini Tower (MANAGER1) and a Low Profile (POS1) with ordinary parallel, serial, network, video and USB connectors. Commodity x86 Windows PCs, not proprietary terminals. Note the previously cited demo.htm does not mention Dell at all — it says only "your home or office Windows based computer" — and the citation was corrected by the verification pass. https://help.microworks.com/webhelp/Setting_Up_Workstations.htm · retrieved 2026-08-02 adversarially verified

hardware-os-platforms

Windows is named for the POS; RapidRun is named for Android and iOS. Minimum OS versions and device specs are not published. https://www.microworks.com/products/rapidrun.htm · retrieved 2026-08-01

hardware-handheld-purpose-built

Verified: 12.3" PixelSense 2-in-1, Intel Core, Wi-Fi 6, under 2 lb, ">10.5 hours" battery — a consumer tablet. The page never mentions a card reader and never claims payment at the table, which also independently supports the partial on payments-pay-at-table. https://www.microworks.com/products/Handheld-Ordering.htm · retrieved 2026-08-01 adversarially verified

hardware-handheld-battery-swap differentiator

Rated "10.5+ hour battery life" is published, satisfying the full-shift alternative. Hot-swap/field-replaceable batteries are not offered on this form factor. https://www.microworks.com/products/Handheld-Ordering.htm · retrieved 2026-08-01

hardware-handheld-lte

Only Wi-Fi 6 is named; cellular fallback is not documented.

hardware-offline-mode

Store-local Windows architecture with nightly sync to the hosted server means terminals are not cloud-request-dependent, but the vendor publishes no explicit list of what degrades offline. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01

hardware-kds

Refutes the earlier "no" and resolves the verification pass's "unknown": there is a documented first-party KDS. "The PrISM system's Makeline Monitor is an easy-to-read video display that lists all of the order items that the kitchen needs to make", with Ord#, Qty, Description, an Elaps elapsed-time column and order Type; touch Select mode for multi-item bump, Clear, Made to view previously made items, an order-type Filter, two font sizes, and a Dash button opening a sales dashboard. Input hardware is first-party too — the optional Makeline Bump Bar "built to withstand the demanding requirements of the kitchen environment". Shortfall: it is "an optional system component that is, in many cases, replaced by a Kitchen Printer"; routing rules target printers rather than makeline stations (the Makeline tab holds only a refresh interval and an aging timer for the location); and no course or fire timing is documented. https://help.microworks.com/webhelp/Makeline_Monitor_Overview.htm · retrieved 2026-08-02

hardware-kiosk differentiator

Self-order kiosk offered, running the WebOrder menu/UI with contactless payment; an ELO-class touchscreen is pictured. Countertop-vs-freestanding options and ADA conformance are not documented. https://www.microworks.com/products/kiosk-qr-ordering.htm · retrieved 2026-08-01

hardware-drive-thru

Same basis as order-capture-drive-thru: the complete vendor product/hardware catalogue names no drive-thru menu board, order-confirmation display, or headset system, and no drive-thru topic exists anywhere in the 488-topic manual. https://www.microworks.com/products.htm · retrieved 2026-08-04

hardware-printer-compatibility

Kitchen and receipt printers are referenced throughout but no supported-manufacturer or model compatibility list is published.

hardware-peripherals

Documented peripherals include cash drawers/tills, touchscreens, fingerprint readers, caller-ID hardware, and barcode label printing ("Barcode blaster pizza box labels"). No published compatibility list; scales and customer-facing displays are not mentioned. https://www.microworks.com/products/restaurant-pos.htm · retrieved 2026-08-01

hardware-p2pe-terminal

"Keep cardholder data off the POS" via P2PE and tokenization is claimed, but no PCI-listed PTS device model is named and no merchant SAQ type is stated. https://www.microworks.com/products/payments.htm · retrieved 2026-08-01

hardware-tap-to-phone differentiator

Tap-to-pay acceptance is claimed but on terminals; Tap to Pay on iPhone/Android on a commodity device is not documented.

hardware-pricing-transparency differentiator

No hardware SKU prices anywhere on the site; the quote page routes to phone/email. https://www.microworks.com/quote.htm · retrieved 2026-08-01

hardware-ownership-vs-lease differentiator

Both paths documented: turn-key purchase (Dell hardware with 3-year on-site warranty) and leasing through partner leasing companies. Neither is priced. https://www.microworks.com/home/faq.htm · retrieved 2026-08-01

hardware-usable-after-churn differentiator

Structurally the hardware is standard Dell PCs, so remote bricking is implausible, but the vendor makes no statement.

hardware-rma-sla differentiator

Warranty terms published: Dell computers three years with on-site support; other peripherals one year; touchscreens two years. No advance-exchange turnaround SLA is stated. https://www.microworks.com/home/faq.htm · retrieved 2026-08-01

hardware-byod

The only mobile ordering hardware documented anywhere is the vendor-supplied Handheld-Ordering device — a 12.3" Windows 2-in-1 tablet running "the exact same user interface as our fixed POS station." No personal-phone, BYOD, or bring-your-own-device permission model is named on this page, in the RapidRun driver-app documentation, or anywhere in the manual. https://www.microworks.com/products/Handheld-Ordering.htm · retrieved 2026-08-04

hardware-remote-device-management differentiator

Station Setup (General, Devices, Advanced) and Printer_Setup.htm are per-terminal, locally-configured screens — Printer_Setup's only fleet-adjacent feature is a per-device Backup Device failover field. Neither topic, nor any other in the manual, documents a remote console showing terminal/printer/KDS online/offline status, remote reboot, software-version visibility, or staged update rollout. https://help.microworks.com/webhelp/Printer_Setup.htm · retrieved 2026-08-04

hardware-callerid-integration

"Caller ID Customer Link" is listed as an integrated add-on POS feature — inbound call pops the customer record. https://www.microworks.com/products/restaurant-pos.htm · retrieved 2026-08-01

extensibility-public-api-docs

Upheld with the citation the previous pass said was needed. The PrISM WebHelp table of contents enumerates all 488 topics across the eleven books of the system and contains no API, developer, SDK, webhook or integration topic; the vendor's 13-item product catalogue contains no platform product; and the FAQ frames extension as vendor-performed work — "We are one of a handful of POS vendors that actually customize our product for your specific needs." https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-02

extensibility-api-access-cost differentiator

There is no API at all (extensibility-public-api-docs, no; api_posture.public_api: none), so there is no access to be included in or excluded from the base subscription. The claim's premise does not exist in the documented product. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

extensibility-partner-revshare

No partner program, marketplace, or commercial terms are published anywhere on the vendor site. https://www.microworks.com/products.htm · retrieved 2026-08-01

extensibility-free-sandbox differentiator

A free Windows software evaluation download exists for prospective operators, but it is a product trial, not a developer sandbox with API credentials and seeded data. https://www.microworks.com/demo.htm · retrieved 2026-08-01

extensibility-oauth-partner-apps

There is no third-party app surface to authenticate. The complete help TOC — the authoritative enumeration of the product across eleven books — contains no API, developer, OAuth, token, scope, or partner-app topic of any kind; the only documented integrations are vendor-built point connections (the desktop QuickBooks Interface Module, Caller ID Customer Link, WebOrder-to-POS injection). With no public API and no app marketplace, there are no operator-granted, individually revocable app credentials, OAuth or otherwise — integration is a sales conversation with the vendor, not a permission grant. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

extensibility-webhooks-push

The complete help TOC enumerates every topic in the product across eleven books and contains no webhook, event, callback, or push-notification topic. The product's only documented outbound surfaces are scheduled report files delivered as PDF/HTML to a folder, an email address, or a printer (Scheduled_Reports.htm) and the desktop QuickBooks file interface. Order lifecycle events are not exposed outside the system by any documented mechanism — there is not even a polling API as the alternative, because there is no API at all (see api_posture). https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

extensibility-webhook-reliability differentiator

Consistent with extensibility-webhooks-push (no): no webhook mechanism exists at all, so there is nothing to be HMAC-signed, retried with backoff, or replayed from an event log. The complete help TOC confirms the absence across all eleven books. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

extensibility-order-injection-api

WebOrder and third-party marketplace orders do land in the POS, so an ingestion path exists internally, but no public write API is documented.

extensibility-menu-write-api differentiator

There is no API of any kind, read or write (extensibility-public-api-docs, no). Menu items, modifiers, and prices are entered only through the on-terminal Product Information screens documented in the manual. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

extensibility-data-symmetry differentiator

With no public API to read or write any object (extensibility-public-api-docs, no), there is no basis for read/write symmetry across orders, menu, customers, employees, or inventory. All access is through the desktop application itself. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

extensibility-published-rate-limits

Citation replaced (was the marketing-host sitemap, which the verification pass ruled unsafe). The documentation host's own complete topic index contains no API reference, so there is nothing on which rate limits could be published; no throttling, quota or fair-use topic exists in the help system. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-02

extensibility-doordash-preferred differentiator

Verified, but the cited URL (get.doordash.com/...) now 301s and then 404s. The 2026 cohort — Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper — is confirmed via DoorDash's own newsroom, and Microworks is absent. Swap the source. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

extensibility-first-party-delivery-integrations differentiator

Downgraded from partial by the verification pass, same evidence and same defect as delivery-3p-direct-integration: the sole source is the marketing sentence "integrates with 3rd party Apps like GrubHub, UberEats, DoorDash and Postmates (to name just a few)". This claim tests specifically whether such integrations are first-party and direct rather than middleware-brokered, and that is precisely the property the vendor never states — no partner page, no integration directory, no certification, nothing in the help TOC. adversarially verified

extensibility-middleware-compatibility

No middleware platform (Deliverect, Chowly, Otter, Checkmate) names Microworks in any source reachable here, and Microworks names none.

extensibility-accounting-connectors

A real, documented connector exists: the QuickBooks Interface Module has its own book in the manual — Requirements, Installing & Configuring QIM, QuickBooks Item List, Sales Receipts, Invoices. Shortfall, and it is a sharp one: the configuration chapter is titled "Configuring QuickBooks Pro 2002", i.e. the documented target is a desktop QuickBooks release from 2002. No cloud accounting connector (QuickBooks Online, Xero, Sage, NetSuite) is documented anywhere, and there is no general GL-mapped journal export for anything else. https://help.microworks.com/webhelp/QuickBooks_Interface_Module.htm · retrieved 2026-08-02

extensibility-payroll-export

Only QuickBooks is named, and as an accounting rather than payroll interface. No second named payroll provider.

extensibility-bi-data-warehouse differentiator

The complete automated-export mechanism is enumerated on reporting-raw-warehouse-export (existing cell, no): Save Report, Save Report As, Email Report To, or Print Report To, in PDF or HTML only. No S3, SFTP, database, or Snowflake-share destination exists, and no API exists to build one outside the documented export types. https://help.microworks.com/webhelp/Scheduled_Reports.htm · retrieved 2026-08-04

extensibility-app-marketplace

No integrations marketplace exists; the site's full product catalog and sitemap contain no partner directory. https://www.microworks.com/products.htm · retrieved 2026-08-01

extensibility-custom-fields-scripting

Downgraded from "no". The prior basis was a single FAQ sentence framing customisation as vendor-performed, which establishes the vendor's sales posture, not the absence of operator-configurable custom fields. The admin manual in fact shows several operator-defined extension points that cut the other way — free-form Cost Types, Cost Centers, Inventory Locations, Menu Classes as a "wild card" attribute, Report Filters, and free-form Account Terms — while no general custom-field or scripting facility is documented either. That is genuinely unresolved, and under the rules absence of evidence is unknown rather than no.

extensibility-headless-embedded

A headless mode requires an API for a third-party UI to drive the transaction engine through; none exists (extensibility-public-api-docs, no). WebOrder, the kiosk, and the handheld all run Microworks' own first-party UI, not a third-party front end over an API. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-04

extensibility-api-versioning-deprecation

Citation replaced (was the marketing-host sitemap). The complete WebHelp topic index has no API changelog, no versioning policy and no deprecation notice topic, because it documents no public API. Product versions are referenced only in prose ("Prism V8.1 or Prism Cloud" on the payments page), with no published support-window or upgrade policy. https://help.microworks.com/webhelp/whxdata/whtdata0.xml · retrieved 2026-08-02

extensibility-data-portability-exit differentiator

Reports covering sales, inventory, customer, and driver activity can be exported on demand as PDF or HTML files (Scheduled_Reports.htm), and the operator physically holds the store-local production database on their own hardware (reliability-local-transaction-engine, existing cell). Shortfall: no complete raw export of orders, customers, menu, and payments metadata in a machine-readable format (CSV/JSON/SQL) is documented, and no contractual export window at termination exists because no public MSA exists at all (commercial-autorenew-terms-published, existing cell: no). https://help.microworks.com/webhelp/Scheduled_Reports.htm · retrieved 2026-08-04

reliability-offline-order-entry

On-premise store server plus local Windows terminals with only nightly cloud sync strongly implies local order entry and printing survive an internet outage, but the vendor never states it. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01

reliability-offline-card-auth differentiator

Tested by the verification pass against the card-authorisation chapter rather than left unexamined. Authorizer_Overview.htm documents a deferred-capture model — "When a charge is made in PrISM, the amount of the sale is simply authorized... The actual transaction is not completed until the batch of validations are processed" — which is auth-now/settle-at-batch, not offline authorisation. The chapter states nothing about behaviour when the dial-up or broadband link is down, no store-and-forward queue, no floor limit and no allocation of decline risk. Unresolved, not absent. adversarially verified

reliability-offline-decline-liability differentiator

Same finding, same page, as the already-established payments-offline-decline-liability (no): the complete card-authorization documentation describes an authorize-at-order, settle-at-batch model with no store-and-forward concept at all, hence no decline-on-reconnect liability statement and no offline cap. No other topic in the complete help TOC covers offline payments. https://help.microworks.com/webhelp/Authorizer_Overview.htm · retrieved 2026-08-04

reliability-lan-degraded-multi-terminal differentiator

Multiple POS stations share check state — "Servers can swipe credit cards into any available POS station" and real-time table status across stations — against a store-local database. LAN-degraded behavior during an internet outage is not explicitly documented. https://www.microworks.com/products/restaurant-pos.htm · retrieved 2026-08-01

reliability-local-transaction-engine differentiator

The manual documents an in-store estate of named Windows machines — a MANAGER1 mini tower and POS1/POS2 low-profile stations wired to a store LAN — so the transaction engine is on-premise by construction. Corroborated verbatim on the Storenet page: "each store can upload its entire database nightly" and "Hosted Server and Unit Locations Can Update Database Nightly", i.e. the hosted copy is a nightly extract of a store-local production database. Caveat: the payments page gates current devices on "Prism V8.1 or Prism Cloud" and Prism Cloud has no published architecture, so this applies to the on-premise product only. https://help.microworks.com/webhelp/Setting_Up_Workstations.htm · retrieved 2026-08-02 adversarially verified

reliability-offline-kds-printing

Kitchen output is LAN-attached printers driven by the local POS, so printing should continue offline; no KDS exists and no offline statement is published. https://www.microworks.com/products/web-ordering.htm · retrieved 2026-08-01

reliability-printer-fallback

Failover itself is documented: every device defined in Printer Setup takes a Backup Device — "Choose another device to act as a backup in case PrISM cannot print to this device" — so tickets reroute to a designated backup when a configured printer is unreachable. Named shortfall: the second half of the claim, alerting staff, is documented nowhere — neither Printer_Setup.htm nor the troubleshooting topics describe any notification to staff when a printer is down and its backup engages. https://help.microworks.com/webhelp/Printer_Setup.htm · retrieved 2026-08-04

reliability-sync-conflict-handling

The claim asks whether the vendor documents conflict-resolution behaviour; it documents none. The only multi-node data flow in the manual is StoreNet Satellite: a franchise master uploads a menu or inventory dataset ("Once performed this cannot be undone") and stores "download the updated data at the next prescribed interval" (Upload_Dataset_Satellite.htm) — one-way distribution with no merge, prompt, or conflict concept. In-store, workstations share a single store-local database over the LAN, and Networking_The_Workstations.htm is a cabling/router installation guide with no partition or reconnect behaviour. No topic in the complete help TOC addresses concurrent edits from two devices, so the documented behaviour the claim requires does not exist in the vendor's public corpus. https://help.microworks.com/webhelp/Storenet_Satellite.htm · retrieved 2026-08-04

reliability-offline-feature-matrix

The "no" cites sitemap.xml of the marketing host as proof of absence. That reasoning is now demonstrably unsafe — the vendor's actual product documentation lives on a different host (help.microworks.com/webhelp/) that the sitemap does not cover and the researcher never opened. Absence of an offline feature matrix was not established. adversarially verified

reliability-public-status-page

Same defect: inferred from the marketing-host sitemap only, and marked 'inferred' at that. A separate documentation/support host exists; no affirmative source states there is no status page. adversarially verified

reliability-contractual-uptime-sla differentiator

Consistent with commercial-autorenew-terms-published and commercial-soc2-attestation (both existing cells, no): no MSA, terms of service, or trust-centre page is publicly accessible anywhere on the site, and the complete documentation-host TOC has no SLA, uptime, or service-credit topic. There is no contractual document to carry an SLA. https://www.microworks.com/sitemap.xml · retrieved 2026-08-04

reliability-incident-postmortems

No blog, status page, or trust-centre section exists anywhere on the site (per the sitemap) or in the complete help TOC. No post-incident report or root-cause summary has ever been published for the hosted Storenet service or any other component. https://www.microworks.com/sitemap.xml · retrieved 2026-08-04

reliability-247-live-support

The manual's Support Policies topic states the hours: 'Technical support by telephone is available Monday through Thursday from 9 a.m. to 8 p.m. EST, Friday from 9 a.m. to 6 p.m. EST, and Saturday from 11 a.m. to 3 p.m. EST. After-hours and holiday support calls will be handled via pager until 11 p.m. EST, with a 30-minute or less target response time', limited to system-down problems. It is also not included in a base subscription: 'PrISM Users must have a current support contract to receive telephone support. All new turnkey systems ship with one (1) year free support', with contracts 'issued on a per-store basis' for 6, 12 or 24 months. https://help.microworks.com/webhelp/Support_Policies.htm · retrieved 2026-09-03 adversarially verified

reliability-onsite-install differentiator

On-site work is offered as a paid line item: 'Shipping, setup, travel, and installation charges are non-refundable' (Returned Equipment policy). Shortfall: no topic describes what the on-site installation or go-live service contains, who performs it, or when it applies; the FAQ's default posture is that systems 'ship pre-configured and thoroughly tested complete with diagrams and cables customized to the specifics of each location'. https://help.microworks.com/webhelp/Support_Policies.htm · retrieved 2026-09-03 adversarially verified

reliability-menu-build-service differentiator

Asserted in sales copy only: the bullet "Customized Menu and Database Setup" and the sentence "Our support staff will pre-configure your system to arrive with your menu, pricing, and inventory, setup and ready to go." Shortfall: no documented scope, turnaround, item ceiling, revision policy, or statement of whether it is included in the purchase or billed — and the 488-topic help TOC has no onboarding or menu-build chapter (only Installation Overview, Going Live, Support Policies and RMA Policies). Grade corrected to C: this is a marketing feature page, not documentation. https://www.microworks.com/products/pizza-pos.htm · retrieved 2026-08-02 adversarially verified

reliability-hardware-replacement-sla

Dell three-year on-site hardware warranty, two years on touchscreens, one year on other peripherals. No stated replacement turnaround time. https://www.microworks.com/home/faq.htm · retrieved 2026-08-01

reliability-backup-restore

No backup/restore topic exists among the Getting Started or Software Installation books (Setting Up Workstations, Networking, System Startup, Passwords, Going Live, System Administrator, Special Instructions, Installing PrISM for Windows), and no RPO/RTO figure is published anywhere. Because the database lives on operator-owned, on-premise hardware, some form of local backup practice plausibly exists, but the vendor documents none of it — genuinely unresolved rather than established absent.

reliability-pci-dss-4-attestation

No AoC, P2PE listing, or compliance page is published; the payments page makes only a general encryption/tokenization claim. https://www.microworks.com/products/payments.htm · retrieved 2026-08-01

reliability-mfa-role-based-access

The role-based half is fully documented and granular — Password Groups as permission tiers assigned to employees, built from individually selected system functions, with a Super User override, plus per-function Required flags, per-item Password Protect, and four routing-station password modes (Passwords on Router, Password on Entry, Password on Route, Password on Entry and Route). Shortfall: authentication is a single password entered at the terminal; multi-factor authentication is not documented anywhere in the help system for either the POS or the back office, and there is no back-office login separate from the Windows workstation. https://help.microworks.com/webhelp/Setup_Password_Groups.htm · retrieved 2026-08-02

reliability-self-serve-training

"Online Help" documentation is referenced from the support page. A free public video/LMS training library and an on-terminal training mode are not documented. https://www.microworks.com/home/supportform.htm · retrieved 2026-08-01

reliability-failover-terminal-role differentiator

The documented architecture assigns fixed roles to named machines — a MANAGER1 mini tower as the server and POS1/POS2 low-profile stations as clients — with no automatic promotion of a client terminal to the server role on failure. Networking_The_Workstations.htm is a cabling/router guide with no failover procedure documented. https://help.microworks.com/webhelp/Setting_Up_Workstations.htm · retrieved 2026-08-04

reliability-cellular-backup

The store's own network setup chapter documents wired LAN and router configuration only, with no cellular/LTE failover option. Only the RapidRun driver app and the handheld tablet reference wireless connectivity (Wi-Fi 6 on the handheld), and neither names a cellular failover for the store network itself. https://help.microworks.com/webhelp/Networking_The_Workstations.htm · retrieved 2026-08-04

commercial-month-to-month-contract differentiator

The payments page mentions month-to-month billing availability with some service providers, which concerns processing, not the POS license. Prism is sold as a capital purchase or a lease through third-party leasing companies; no subscription term is published.

commercial-no-early-termination-fee differentiator

Same basis as the already-established commercial-autorenew-terms-published (no): no MSA, terms of service, or subscription agreement is publicly accessible anywhere on the site or the documentation host's complete TOC — only Support Policies and RMA Policies exist, and neither addresses termination fees. With no published terms at all, none can state an ETF waiver. https://www.microworks.com/sitemap.xml · retrieved 2026-08-04

commercial-autorenew-terms-published

No MSA, terms of service, or subscription agreement is publicly accessible; the sitemap contains no legal/terms page beyond a privacy and SMS policy. Re-checked 2026-08-02 against the documentation host as well: the complete PrISM WebHelp table of contents (whxdata/whtdata0.xml) enumerates every topic in the system and contains no terms, contract or subscription-agreement page either — only Support Policies and RMA Policies, neither of which states renewal terms. https://www.microworks.com/sitemap.xml · retrieved 2026-08-02

commercial-processing-not-bundled differentiator

Same underlying fact as the already-established payments-processor-choice (partial): merchant processor choice exists — Microworks requires "information pertaining to your primary credit card processing company" — but the gateway is fixed and singular (PCCharge) and configured through Microworks Tech Support rather than self-service, so the operator's processor choice is brokered rather than a fully open bring-your-own-processor model. https://help.microworks.com/webhelp/Authorizer_Overview.htm · retrieved 2026-08-04

commercial-interchange-plus-published differentiator

No processing rate of any structure is published. https://www.microworks.com/products/payments.htm · retrieved 2026-08-01

commercial-rate-increase-clause differentiator

No processing agreement or rate card is published anywhere (payments-published-rates, no; commercial-interchange-plus-published, no), so there is no published document that could cap or prohibit a unilateral rate increase, or grant a penalty-free exit on one. https://www.microworks.com/quote.htm · retrieved 2026-08-04

commercial-pricing-published

Quote-only. The quote page: "We are experiencing technical difficulties with our online quote form, please call or email us for a quote!" No per-location or per-terminal figure exists on the site. https://www.microworks.com/quote.htm · retrieved 2026-08-01

commercial-module-unbundling differentiator

The catalog is structured as discrete purchasable modules — WebOrder, RapidRun, Kiosk/QR, Surveillance, Enterprise Management, Notification Service — implying à la carte purchase, but no terms or prices confirm independent cancellation. https://www.microworks.com/products.htm · retrieved 2026-08-01

commercial-hardware-purchase-outright

Turn-key outright purchase is available (Dell hardware, warranty included) with leasing as an alternative, not a requirement. No published prices. https://www.microworks.com/home/faq.htm · retrieved 2026-08-01

commercial-hardware-not-locked differentiator

The PC is commodity — turn-key systems ship on Dell and the evaluation runs on the buyer's own Windows machine — but the licence is bound to vendor-issued hardware. "The installation of a USB software license keylok is required to unlock the full operational abilities of the PrISM software," verified in Help | About by a four-digit key serial and a licensed user count, showing "N/A" if the driver fails. Shortfall: adding or replacing a terminal requires Microworks to issue a physical dongle carrying a seat count, so hardware freedom stops at the licence key. https://help.microworks.com/webhelp/USB_Software_License_Keylok.htm · retrieved 2026-08-02 adversarially verified

commercial-implementation-fee-published

No implementation, menu-build, onboarding, or training fee figure is published, nor is any stated as $0. https://www.microworks.com/quote.htm · retrieved 2026-08-01

commercial-data-export-self-serve

Storenet reports are described as delivered in spreadsheet format by store or across stores. Full transaction-level self-serve export of orders, line items, payments, and labor is not documented — though the on-premise database is physically in the operator's possession. https://www.microworks.com/products/enterprise-management.htm · retrieved 2026-08-01

commercial-export-customer-and-loyalty differentiator

Customer report family produces customer lists and mailing labels; reports are available in spreadsheet format. Machine-readable export of loyalty point ledgers and gift-card liability balances is not documented. https://www.microworks.com/products/reporting.htm · retrieved 2026-08-01

commercial-post-termination-export-window differentiator

Same basis as commercial-autorenew-terms-published (no): no MSA or terms of service is publicly accessible anywhere, so no post-termination data-retrieval window is stated. The only documented export mechanism at any time is Scheduled_Reports.htm's PDF/HTML report files, with no termination-specific provision. https://www.microworks.com/sitemap.xml · retrieved 2026-08-04

commercial-data-ownership-clause differentiator

No public MSA exists, so no ownership or vendor-use restriction clause can be verified. The on-premise deployment gives the operator de facto physical custody of the database, which is a structural rather than contractual protection.

commercial-source-available-selfhost

Proprietary commercial software. It is self-hosted on-premise, which satisfies the deployment half, but no source is published under any license. https://www.microworks.com/demo.htm · retrieved 2026-08-01

commercial-pci-p2pe-tokenization

P2PE and tokenization claimed with "keep cardholder data off the POS." No validated P2PE listing and no named SAQ type (A / P2PE-HW). https://www.microworks.com/products/payments.htm · retrieved 2026-08-01

commercial-pci-dss-4-controls

Authentication is documented as a single password entered at the terminal (reliability-mfa-role-based-access, existing cell: partial, no MFA documented anywhere in the help system for POS or back office), which forecloses the MFA-for-CDE-access control. The payments marketing page (re-read 2026-08-04) makes only a general tokenization/P2PE claim with no PCI DSS 4.0.1 AoC and no mention of payment-page script-integrity monitoring. https://help.microworks.com/webhelp/Setup_Password_Groups.htm · retrieved 2026-08-04

commercial-soc2-attestation

No SOC 2, ISO 27001, or trust center is mentioned anywhere on the site or in the sitemap. Re-checked 2026-08-02 against the documentation host as well: the complete PrISM WebHelp table of contents contains no trust-centre, audit or certification topic. https://www.microworks.com/sitemap.xml · retrieved 2026-08-02

commercial-privacy-dsar-tooling

Same basis as guest-loyalty-privacy-rights-tooling: the expected customer-record maintenance topic did not resolve to real content (redirected to the marketing homepage), so in-app deletion/export tooling for a data-subject request could not be confirmed present or absent. No DPA, privacy-rights, or DSAR topic is named anywhere else in the manual or on the site. Genuinely unresolved.

commercial-wcag-kiosk-accessibility differentiator

No VPAT/ACR or WCAG claim is published; the kiosk and QR ordering page is silent on accessibility. https://www.microworks.com/products/kiosk-qr-ordering.htm · retrieved 2026-08-01

commercial-dual-pricing-compliant differentiator

Follows directly from payments-dual-pricing and menu-pricing-dual-pricing (both no): the complete pricing engine has no tender-based price dimension at all, so there is no dual-pricing/surcharge feature to be card-network-compliant, exclude debit/prepaid cards, or carry a disclosure requirement. https://help.microworks.com/webhelp/Pricing.htm · retrieved 2026-08-04