PDQ POS

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

order-capture-floor-plan-editor

No product documentation published. Casino/table-service deployments imply table management but nothing is documented. || 325th: NEW SURFACE, does not settle the cell. The 2016 Feature Overview does affirm table service exists - 'Enhanced table management interface' and 'Hostess module' under Point-of-Sale Capabilities (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf) - but none of the claim's conjuncts (a graphical EDITOR, drawing sections, placing tables of varying shape/capacity, multiple saved layouts per location, assigning sections to servers) appears in the document, and 'Transfers (items, tables, tabs, servers, cashiers)' is a transfer function, not a layout editor. Shortfalling every conjunct is not a partial. Held unknown. Retrieved 2026-09-17. || 326th: NEW SURFACE for this cell, and it cuts against the claim's 'editor' verb. PDQ's retired ProTable and Solutions pages establish that table LAYOUTS exist and are colour-coded by status - 'This module comes with TABLE LAYOUTS AND COLOR CODED FOR THE TABLE'S STATUS' - but attribute their creation to the vendor, not the operator: 'As with all PDQ modules, THEY ARE CUSTOMIZED TO YOUR SPECIFIC NEEDS. MENUS, TABLE LAYOUTS, RECIPES, STAFF AND MORE ARE PERSONALIZED TO YOUR OPERATION.' (https://web.archive.org/web/20041016013929/http://www.pdqpos.com/solutions.htm). ProTable itself adds only monitoring: 'Table Status - ProTable allows servers and managers to monitor open tables, time since last order, and current balance' (https://web.archive.org/web/20041208124200/http://www.pdqpos.com/table.htm). PDQ's current posture is the same - its Podcasts index sells configuration as a service, 'Our expert in-house Menu Team will happily make your menu changes' (https://web.archive.org/web/20220627142629/https://www.pdqpos.com/podcasts/). Still no graphical editor, no shape/capacity placement, no multiple saved layouts and no section-to-server assignment; held unknown. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE, the vendor's own video catalogue, fetched to 100%. PDQ's YouTube uploads playlist (channel UCjfIRXazn4Ut8ploYMeO9RA) reports '45 videos', and all 45 titles are on disk (.cache/q332/pdq-pos/a/uploads.txt). None is a table-service, floor-plan or bar demo. The titles are testimonials, trade shows, kiosks, the Delivery Toolkit, the VDU, menu boards, rear displays, 'Quest Tablet POS', 'PDQ POS Demo' and overviews. I read the watch-page descriptions of 25 of the videos, and the full-resolution auto-frames (maxres 1-3) of the demo and overview videos. 'PDQ POS Demo' (2016, 369 s) shows the order screen with 'Phone (Hold For Call History)', DEL/PU check tiles, 'Dispatch (2)', 'Recall', 'Manager' and 'Time Clock', and no table map. The 2026 bar/restaurant testimonial (Gino's Pizza, 'Ristorante - Bar') frames show only people and the room. Nothing adds an operator floor-plan editor, table shapes or section-to-server assignment. Retrieved 2026-09-18. || 333rd: 333rd: NEW CHECKS, do not settle. (1) The table-service order screen in PDQ POS Overview (CAtnMz-w59k, frames at 12 s and 20 s, read for kitchen cells in the 332nd but not for this one) is headed 'Section: The Garden / Dennis Hamburg / [partly illegible] Guests: 3 11:14 AM', and a 'Number Of Guests' keypad precedes it: sections, server attribution and guest counts exist at order entry. (2) PDQ's retired business-models page lists for Table Service 'Separate Checks | Automatic Price Changes | TABLE STATUS | Clocking Out' (https://web.archive.org/web/20160617213823/http://www.pdqpos.com/all-business-models/). (3) 14 further vendor uploads were downloaded at up to 1080p: 7 were read as scene-change contact sheets (YUUejVp2lhY, xvVu3cVQl8I, PWqryUhZN4E, zX9EUPItKsE, I1htVJv8xk4, UxsD4LSD2hY, and part of the 6-min demo EoHF88VZ9aA whose full caption track was read) and 5 by caption track only (CRtZ5kwzjcQ, 90Mb91fTkKU, fJePiriHNNg, WJl-rwtWvTw, hMgf61pAV7U; kS_2EDgDGUw and 4-73vNrBqZM have no captions and were not read): none shows a table map, let alone an editor. No drawing, table-shape placement, saved layouts or section-to-server assignment screen anywhere; a section NAME on an order header is adjacent. Retrieved 2026-09-18. || 334th: 334th: NEW SURFACE, unread. PDQ runs a second video channel, https://vimeo.com/pdqpos (19 uploads 2016-02-15 to 2018-02-28, listed via oEmbed). 13 duplicate YouTube uploads; the 6 not on YouTube are short promos or hardware clips: 'PDQ POS-Video' (237398208, 242 s, 2017), 'Welcome to Old Antlers Inn' (155405145, 30 s, a Wellsboro PA restaurant), 'Welcome to PDQ Signature Systems' (60 s), 'Camera with Text Overlay', 'Fingerprint Reader', 'Digital signage'. Vimeo refuses anonymous playback: yt-dlp says the web client needs a login, and player.vimeo.com/video/<id>/config returns 403 to curl with a browser UA. So the frames could not be read, and no login was attempted. A 30 s restaurant welcome and a 242 s promo are unlikely to show a floor-plan editor. Also read today: the silent 2018 slide video P1NW60Uw3Gw (366 s, 1080p, every slide). It has no table-service or floor-plan slide. Retrieved 2026-09-18. adversarially verified

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

order-capture-seat-level

CLAIM: order lines tagged to a seat number at entry, and the check split by seat afterward without re-keying. VERDICT: partial. EVIDENCE: the PDQ POS Feature Overview sheet lists, under Point-of-Sale Capabilities, 'Combine and split orders' with the indented sub-bullet 'Split guest, check and item' - three split axes named, GUEST being one of them, so per-guest apportionment of an existing check exists without re-keying (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). SHORTFALL (named): nothing states that lines are TAGGED TO A SEAT NUMBER AT ENTRY, nothing describes a seat map or per-seat printing, and the sheet is a 2016 sales feature overview, not an admin guide. Absence of the first conjunct is why this is partial and not yes. Retrieved 2026-09-17. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-17 adversarially verified

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

order-capture-coursing-hold-fire

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For order capture the two sites establish the SURFACES and nothing about their behaviour: first-party 8-inch and 10-inch tablets, a counter station, a three-in-one POS/customer-display/kiosk unit, four kiosk models, and an order-entry screen (visible in the 2019 overview flyer) whose keys are categories, sizes, toppings, "1/2 with", "NO'S", Smart Coupon, Gift Card, Phone/Call History, Send, Pay, Charge Card and OOPS. Nothing in either site describes a seat, a course, a tab pre-authorisation, a transfer, an order throttle, a scheduled fire time or a drive-thru timer, and no configuration or settings screen is published anywhere. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: NEW CHECK, does not settle. The only table-service order screen in PDQ's video catalogue (CAtnMz-w59k at 12 s and 20 s: 'Section: The Garden', guest count 3) carries top-row keys Cancel, Print Order, Bar Menu, Smart Coupon, Gift Card, 'Next (Mods)', a side-choice key, Special Instructions, Send and Pay (zoomed from the 720p frames), and no course, hold or fire key; the further uploads read this session (contact sheets or captions) are pizzeria/QSR/delivery/kiosk flows. A tokenised re-grep of 4,473 on-disk PDQ files gives 'hold and fire', 'fire next/course/now', 'hold item(s)' and 'delayed send' = 0; 'coursing' hits are atlas claim text only. The one hold-like control is 'Delay Order', which delays a WHOLE order (already noted by the 332nd). A montage screen is not a census of the table-service module, so no `no`. Retrieved 2026-09-18. adversarially verified

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

order-capture-split-merge

PDQ's own feature sheet lists 'Combine and split orders' with the sub-bullet 'Split guest, check and item' (both byte-contiguous, both under the Point-of-Sale Capabilities column). Affirmatively established: split BY ITEM and MERGE. SHORTFALLS: even N-way split, split by arbitrary dollar or percentage amount, and whether either is possible AFTER a partial payment. NOTE ON READING: an earlier pass glossed the document's 'guest' as seat-equivalent; that equivalence is the reader's, not the document's, and on a pizzeria-first product 'guest' may mean payer rather than seat - so the claim's BY SEAT conjunct is NOT claimed as established. SOURCE DATE: a 2016 first-party sell sheet (uploads/2016/12) recovered from the Internet Archive because pdqpos.com left WordPress and it 404s live. Evidence about the 2016 product. Verified that the live 2025 catalogue restates none of it - the tokens split, gift, transfer, email, security role, happy hour and permission each occur zero times there - so carry-forward rests on PDQ POS being a continuously-sold product line, not on any current document. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-12 adversarially verified

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

order-capture-bar-tab-preauth

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For order capture the two sites establish the SURFACES and nothing about their behaviour: first-party 8-inch and 10-inch tablets, a counter station, a three-in-one POS/customer-display/kiosk unit, four kiosk models, and an order-entry screen (visible in the 2019 overview flyer) whose keys are categories, sizes, toppings, "1/2 with", "NO'S", Smart Coupon, Gift Card, Phone/Call History, Send, Pay, Charge Card and OOPS. Nothing in either site describes a seat, a course, a tab pre-authorisation, a transfer, an order throttle, a scheduled fire time or a drive-thru timer, and no configuration or settings screen is published anywhere. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 324th: NEW 2026-09-17: PDQ does publish a tab feature set -- the PDQ POS Feature Overview PDF (https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf) lists 'Tab sharing', 'Search tabs by name', 'Transfers (items, tables, tabs, servers, cashiers)' and 'Recall invoice'. None of the three conjuncts of this claim is touched: no card PRE-AUTHORIZATION on tab open, no configurable auth amount, no incremental re-auth, no stale-tab auto-close at end of day. The tokens 'pre-auth', 'preauth', 'authorization hold' and 'incremental' are zero across every PDQ document read this session. Tabs exist; tab card pre-auth is undocumented, which is absence of evidence, not evidence of absence. Retrieved 2026-09-17. || 326th: NEW SURFACE for this cell: PDQ's retired ProBar module page, absent from every prior corpus. It documents the tab feature directly - 'RUN TABS - ProBar can RUN TABS BY THE CUSTOMER'S NAME OR SEAT LOCATION. Recalling the Tabs takes seconds with just a couple of taps.' - and the stale-tab control it does ship is a clock-out block, not an auto-close: 'ProBar has a feature that PREVENTS THE BARTENDERS FROM CLOCKING OUT WITHOUT FIRST CLOSING THEIR CHECKS. This feature reduces the number of walk-outs and eases the close out process.' (https://web.archive.org/web/20041208105701/http://www.pdqpos.com/bar.htm; the same clock-out rule appears on ProTable, https://web.archive.org/web/20041208124200/http://www.pdqpos.com/table.htm). So the tab identity key is a NAME OR SEAT, explicitly not a card - which is evidence against the pre-auth conjunct rather than for it - and the walk-out remedy is procedural. No card pre-authorization, configurable auth amount, incremental re-auth or end-of-day auto-close on any surface. Held unknown. Retrieved 2026-09-18. adversarially verified

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

order-capture-transfer-audit

The feature sheet lists transfers of items, tables, tabs, servers and cashiers, affirmatively establishing that open checks move between servers, tables and cashiers. TWO SHORTFALLS: (1) the claim's second half - that the transfer is written to an AUDIT LOG NAMING BOTH EMPLOYEES - is not stated anywhere; the reports list carries 'Void order history' and 'Detailed comp, void reasons' but no transfer log, so the audit limb is unevidenced rather than contradicted. (2) The claim covers transfer between servers, tables and DEVICES; the source says cashiers, not devices, so the device limb is unaddressed. EXTRACTION NOTE: the bullet wraps mid-phrase in both pdftotext modes, so it must not be presented as a byte-contiguous quotation even though it is a single bullet in the rendered PDF. SOURCE DATE: a 2016 first-party sell sheet (uploads/2016/12) recovered from the Internet Archive because pdqpos.com left WordPress and it 404s live. Evidence about the 2016 product. Verified that the live 2025 catalogue restates none of it - the tokens split, gift, transfer, email, security role, happy hour and permission each occur zero times there - so carry-forward rests on PDQ POS being a continuously-sold product line, not on any current document. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-12 adversarially verified

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

order-capture-native-handheld

First-party 8-inch and 10-inch PDQ tablets are catalogued as mobile order-taking devices ('take orders from anywhere'), and the Multi-Revenue Center release (software revision 3.5.383) states staff 'take orders from a wireless POS tablet' and that the update 'gives operators ... the ability to place orders and accept payment for any of those operations wirelessly'. Two shortfalls: the vendor never states whether the tablet runs a native application or a remote session on a back-office terminal, and no document ties a card reader to the tablets - the catalog's EMV reader is an option on the COUNTER STATION, not on the tablets. Evidence is a vendor press release and a marketing product catalog; no product documentation exists for this vendor. https://www.globenewswire.com/news-release/2025/02/26/3033019/0/en/Signature-Systems-Inc-Announces-Slate-Of-New-Features-For-Casino-POS.html · retrieved 2026-08-09 adversarially verified

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

order-capture-offline-order-entry

333rd: this cell was never individually checked against the evidence that moved its two siblings (reliability-local-transaction-engine partial/C and reliability-offline-order-entry partial/C, both merged). Its only note is 95 characters of 2026-08 boilerplate. CLAIM: with the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen and tender cash, AND the vendor publishes what does and does not work offline. VERDICT: partial, grade C. CAPABILITY LIMB, satisfied in part: PDQ's own abstract for its 'Cloud vs. Traditional POS' episode, re-fetched today from the Wayback capture (200, 123,628 bytes), says '...Learn the real difference between cloud and traditional POS and how a hybrid approach will allow you to embrace the cloud WITHOUT BEING DEPENDENT ON IT!', and the companion abstract recommends 'a secure, scalable, powerful, and highly configurable server-based system' (https://web.archive.org/web/20220627142629/https://www.pdqpos.com/podcasts/). The 2016 Feature Overview flags only 'Inventory reporting (w/cloud service)' as cloud-dependent and keeps 'Back Office (POS)' in a separate column from the 'Cloud-Reporting Service' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). The 2021 pricing workbook sells an on-premise 'SSI Virtual Server Appliance'. PUBLICATION LIMB, fails: this record's reliability-offline-feature-matrix is already no/C on a bounded publication census (no offline or degradation matrix in any PDQ document), and the 333rd read 13 more vendor videos (contact sheets or captions) without finding one. SHORTFALL (named): no PDQ sentence says that order entry, modifiers, kitchen send or cash tender keep working when the WAN drops; the strongest statement is an abstract on a RETIRED page (positives capped at partial) and the live homepage now calls itself 'cloud-based technology'. The 2015 dial-backup sheet and the 2021 Wildwood SIM-card quote are second ONLINE paths for card processing, not an offline mode, and are not used. Same shape and grade as the merged sibling reliability-offline-order-entry. Retrieved 2026-09-18. https://web.archive.org/web/20220627142629/https://www.pdqpos.com/podcasts/ · retrieved 2026-09-18 adversarially verified

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

order-capture-qr-same-check

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For order capture the two sites establish the SURFACES and nothing about their behaviour: first-party 8-inch and 10-inch tablets, a counter station, a three-in-one POS/customer-display/kiosk unit, four kiosk models, and an order-entry screen (visible in the 2019 overview flyer) whose keys are categories, sizes, toppings, "1/2 with", "NO'S", Smart Coupon, Gift Card, Phone/Call History, Send, Pay, Charge Card and OOPS. Nothing in either site describes a seat, a course, a tab pre-authorisation, a transfer, an order throttle, a scheduled fire time or a drive-thru timer, and no configuration or settings screen is published anywhere. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: NEW SURFACE, does not settle the cell. PDQ ships a guest-facing in-venue ordering product it had not previously been credited with: its 2024-2025 corporate boilerplate lists 'a natively integrated "IN-PLACE DINING" MOBILE APP' beside the enterprise reporting app and online ordering (https://pdqpos.com/newsarticles?rid=PR_82724_sycuan), and the Live! Casino Louisiana release records the first deployment: 'SSI has also installed THEIR BRAND-NEW MOBILE ORDERING SUITE in the property, a first for the POS provider... "This mobile ordering experience will be the first of its kind in the nation, with more PDQ POS properties adding it soon"' (https://pdqpos.com/newsarticles?rid=PR_000_live_louisiana, 2025-03-17). The Jake's 58 study adds 'MOBILE ORDERING CAPABILITIES: Guests now enjoy the convenience of ordering directly from their devices' (https://pdqpos.com/ProjectDetail?pk=j58ch). SHORTFALL: nothing states the entry route is a QR code, and - the operative conjunct - nothing states the guest's items land on the SAME OPEN CHECK as server-entered items rather than as a separate ticket. Held unknown; this is the surface a future pass should push on. Retrieved 2026-09-18. || 331st: MERGE HOLD (proposed no/B, held unknown): 331st merge: the V2 client creating a fresh OrderUID per scan shows the CLIENT does not look up a check, but a table/seat-tagged web order can still be merged onto the open check SERVER-side at the store POS, which no client census can see (the agent says so). A differentiator `no` needs that bounded. PROPOSAL AS WRITTEN: CLAIM: guest QR at-table ordering writes items onto the SAME open check as server-entered items rather than a separate ticket. VERDICT: no. NEW SURFACE (331st): PDQ's NEW guest ordering client, a Next.js/Turbopack app served anonymously at https://marylandlive.pdqonlineordering.com/ (the same build fronts bossierlive/philadelphialive/pittsburghlive, i.e. the Live! casino 'brand-new mobile ordering suite' of the 2025-03-17 release, and it is a different app from the legacy 13-page WebForms pdqonlineordering.com client the 327th censused). Its chunk set was taken to a FIXPOINT: 49 static chunk/css files referenced from the seed HTML and from each other, 49 held, 0 missing (re-derived this session by re-running the reference regex over every held file), all GET, no session opened and nothing POSTed. The client calls exactly 33 '/api/online/*' endpoints and reads 56 dotted upper-case store-config keys; those two lists are the app's whole server surface. EVIDENCE: it IS a scan-at-seat app - the URL scan key is read by 'getScanKeyFromUrl ... r.get("key")||r.get("DataKey")' (https://marylandlive.pdqonlineordering.com/_next/static/chunks/1swpukh0yk8ef.js), the store config carries 'LOCATION.ISTABLE', 'LOCATION.PROMPTTABLE', 'LOCATION.PROMPTSEAT' and 'LOCATION.PROMPTROOM', and checkout validates 'Table number is required' / 'Seat number is required' into Customer.TableNumber / Customer.SeatNumber (https://marylandlive.pdqonlineordering.com/_next/static/chunks/1swpukh0yk8ef.js; https://marylandlive.pdqonlineordering.com/_next/static/chunks/17-c9ky7ir9it.js). But every order is a NEW order object minted in the browser - 'OrderUID:crypto.randomUUID(),OrderWebID:"",OrderSource:"PDQV2"' - then priced by /api/online/orders/calculate, charged by /api/online/orders/charge and sent by /api/online/orders/submit, which returns a fresh 'OrderWebID' (https://marylandlive.pdqonlineordering.com/_next/static/chunks/1wv3xur2ou__5.js; https://marylandlive.pdqonlineordering.com/_next/static/chunks/3-pqppw_7-kgz.js). The table/seat is a delivery label on that new web order. BOUND: none of the 33 endpoints reads, looks up or appends to an existing check (the order endpoints are calculate/charge/submit/details, and 'details' takes the client's own OrderUID). CONTROLS (tokenised, case-insensitive, over all 49 files, 2.76 MB): OrderUID 138 and OrderWebID 35 (known positives); CheckID 0, TicketNumber 0, TicketID 0, TabID 0, 'open check' 0, 'existing order' 0, 'pay check' 0, 'view check' 0. POISON named: 'CheckNumber' 3 hits are all zod's '$ZodCheckNumberFormat'; 'add to order' 3 hits are the add-to-CART button; 'split' 130 hits are String.prototype.split. RESIDUAL (stated, not hidden): a server-side merge of a table-tagged web order into a server's open check is not observable from any public surface; nothing PDQ publishes says it happens. Retrieved 2026-09-18. || 333rd: 333rd: NEW SURFACES, do not lift the 331st merge hold (server-side merge unseen). PDQ's 2025-11-20 video 'PDQ POS Mobile Ordering Now Available' (zX9EUPItKsE, 1080p, frame-read) shows the QR use case the vendor markets: an 'ORDER HERE / SCAN ME' tent on a COUNTER opening show.pdqonlineordering.com ('Quick Eats', Delivery/Pickup tabs, footer '(c) 2024 - V 3.0.1'), the Ocean Casino food-truck pickup flow with ASAP/time slots, and captions 'Accurate Order Locations', 'Text Confirmation & Notifications', 'In-Room Ordering', 'Player Points & Comps Compatible', 'Full POS Integration'. No at-table add-to-open-check flow is shown. 333rd V2 TENANT CENSUS (GET only, no session): all 209 tenant subdomains in the 331st tenant list were fetched with curl + browser UA (208 x 200, admin 403). The Next.js V2 client now fronts 7 of them, not 4: the 4 Live! casinos plus 3 PIZZERIAS (mygiaspizza 'Gia's Pizza', slicespizzapa 'Slice's Pizza Ridge Ave', trianospizza 'Triano's Pizza'), and an 8th unlisted tenant, oceancasino.pdqonlineordering.com ('Ocean Casino', found in PDQ's 2025-11-20 video). Every V2 tenant serves the IDENTICAL build: the same 25 /_next/static chunk references as marylandlive, 0 differences, and every one already held in the 331st fixpoint census (.cache/q331/pdq-pos/c/chunks). So the V2 client census the 331st/332nd ran already covers the pizzeria tenants: a newer client on more tenants, no new code. Retrieved 2026-09-18. adversarially verified

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

order-capture-kiosk-first-party

Four first-party kiosk SKUs shipped. Shared menu tree with POS implied not stated; no ADA/accessibility conformance published. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-01

Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.

order-capture-drive-thru

Outdoor kiosk markets 'self-ordering from the car'; digital menu boards integrated. No order-point/window separation or lane sequencing documented. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-01

Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.

order-capture-drive-thru-timers

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For order capture the two sites establish the SURFACES and nothing about their behaviour: first-party 8-inch and 10-inch tablets, a counter station, a three-in-one POS/customer-display/kiosk unit, four kiosk models, and an order-entry screen (visible in the 2019 overview flyer) whose keys are categories, sizes, toppings, "1/2 with", "NO'S", Smart Coupon, Gift Card, Phone/Call History, Send, Pay, Charge Card and OOPS. Nothing in either site describes a seat, a course, a tab pre-authorisation, a transfer, an order throttle, a scheduled fire time or a drive-thru timer, and no configuration or settings screen is published anywhere. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: NEW SURFACE, does not settle the cell. PDQ ran a dedicated drive-thru partner page, /hme-hd-audio-2/, absent from every prior pass's corpus. Its headline is 'We Proudly Use HD Audio from HME, THE INDUSTRY LEADER IN DRIVE-THRU SOUND TECHNOLOGY AND TIMING SYSTEMS', but the entire body is about the EOS|HD headset's audio - wideband speech, '44% improvement' inbound noise reduction, '17 times the echo cancellation', '88% improvement in outbound noise reduction' - and no timer, segment, or time-capture function is described (https://web.archive.org/web/20160125162246/http://www.pdqpos.com/hme-hd-audio-2/). Supporting context that also fails the claim: 'Drive-thru equipment' is a listed peripheral and 'QSR reporting' a listed report in the 2016 Feature Overview (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf), and the Jimmy John's case study says only 'PDQ POS also enables the drive-thru experience for Jimmy John's integrating hardware and software to keep driver lines moving as quickly as possible' (https://pdqpos.com/ProjectDetail?pk=jjsw). No order/total/window segment times tied to individual orders anywhere; the tokens 'timer', 'speed of service' and 'SOS' are zero across the corpus. Held unknown. Retrieved 2026-09-18. || 333rd: MERGE HOLD (proposed partial/C, held unknown): The only evidence is a retired (2015-2019) business-models line 'Drive-Thru Timers' beside PDQ's own HME page titled 'Zoom Drive-Thru Timer System': the timer is most likely HME's product integrated with the POS, and a third party's product is not the vendor's feature (328th rule); nothing ties segments to individual orders. PROPOSAL AS WRITTEN: 333rd: CORRECTION and NEW EVIDENCE. The 326th note says 'the tokens timer, speed of service and SOS are zero across the corpus'. That is FALSE for 'timer': a tokenised word-boundary re-grep of every PDQ corpus on disk (4,473 files after excluding notes/prop copies) finds 'Drive-Thru Timers' on PDQ's own retired business-models page, in q261-pdq/routeB since the 261st and never cited. CLAIM: captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders. VERDICT: partial, grade C. EVIDENCE: PDQ's 'Whatever Your Business Model' page lists, under Drive Thru: 'Drive-Thrus are already the fastest way to serve your customers. Let PDQ POS make it even faster! Speed & Accuracy | DRIVE-THRU TIMERS | Line Busters | PERFORMANCE REPORTS' (re-fetched today: https://web.archive.org/web/20160617213823/http://www.pdqpos.com/all-business-models/ ; captured 2015-06-27 to 2019-12-18). The same site's HME partner page carries a slider titled 'ZOOM DRIVE-THRU TIMER SYSTEM' beside 'Digital Drive-Thru Headset System w/HD Audio' (http://pdqpos.com/hme-hd-audio-2/, Wayback 2015-07-31), and the 2016 Feature Overview lists 'Drive-thru equipment' as a peripheral and 'QSR reporting' as a report. So PDQ marketed drive-thru timers plus performance reports as a PDQ POS drive-thru capability. SHORTFALL (named, and why this is only partial): a feature NOUN on a retired marketing page (grade C; retired, so positives cap at partial); no segment (order/total/window) and no per-order tie is described; and the HME slide suggests the timer itself is HME's ZOOM system integrated with the POS rather than PDQ-built. If the merge treats the timer as a third party's product, hold unknown with this correction kept. Controls: 'speed of service' and 'SOS report' still 0 in PDQ-authored documents (the 4 'speed of service' hits are atlas claim text and a 331st regex file). Retrieved 2026-09-18. adversarially verified

Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator

order-capture-voice-ai

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For order capture the two sites establish the SURFACES and nothing about their behaviour: first-party 8-inch and 10-inch tablets, a counter station, a three-in-one POS/customer-display/kiosk unit, four kiosk models, and an order-entry screen (visible in the 2019 overview flyer) whose keys are categories, sizes, toppings, "1/2 with", "NO'S", Smart Coupon, Gift Card, Phone/Call History, Send, Pay, Charge Card and OOPS. Nothing in either site describes a seat, a course, a tab pre-authorisation, a transfer, an order throttle, a scheduled fire time or a drive-thru timer, and no configuration or settings screen is published anywhere. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd: NEW SURFACE, a third party's partner list, and PDQ has since been removed from it. For about two years the voice-AI vendor ConverseNow listed PDQ among its POS integrations. Its Technology page says 'Our partnerships include many of the restaurant industry's leading POS systems, drive-thru providers and other technology suppliers', and the logo wall below that line includes '/wp-content/uploads/2022/04/PDQ-Logo-grey-v2.png', beside PAR, Olo, NCR Aloha, Qu, ItsaCheckmate, Fiserv, Brink, Focus and Xpient. Captures: 2022-05-19 (.cache/q325/conversenow) and 2024-04-23 (https://web.archive.org/web/20240423142510/https://conversenow.ai/technology/). I read the image at full size (https://web.archive.org/web/20240423142638id_/https://conversenow.ai/wp-content/uploads/2022/04/PDQ-Logo-grey-v2.png). It is Signature Systems' own 'PDQ / SIGNATURE SYSTEMS, INC / TECHNOLOGY SERVICES' seal, so it is not the PDQ chicken chain. The LIVE conversenow.ai 'Integration Partners' list, fetched today, has 9 logos: Brink POS, Fiserv, Focus, ItsaCheckmate, NCR Aloha, Olo, PAR, Qu, Xpient. PDQ is gone, and the old image URL now 404s. WHY STILL UNKNOWN: the claim needs a FIRST-PARTY voice agent, or a voice-AI partner program that PDQ ITSELF documents. This is a third party's retired partner card (grade D; a retired third-party partner card is not evidence, per the 329th). No PDQ surface on disk names ConverseNow or any voice-AI vendor: 0 hits for 'conversenow' across 3,449 files. PDQ's own phone channel is a human call centre ('PDQ HQ & Call Center' videos). Retrieved 2026-09-18. adversarially verified

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

order-capture-throttling

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For order capture the two sites establish the SURFACES and nothing about their behaviour: first-party 8-inch and 10-inch tablets, a counter station, a three-in-one POS/customer-display/kiosk unit, four kiosk models, and an order-entry screen (visible in the 2019 overview flyer) whose keys are categories, sizes, toppings, "1/2 with", "NO'S", Smart Coupon, Gift Card, Phone/Call History, Send, Pay, Charge Card and OOPS. Nothing in either site describes a seat, a course, a tab pre-authorisation, a transfer, an order throttle, a scheduled fire time or a drive-thru timer, and no configuration or settings screen is published anywhere. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 331st: NEW SURFACE (331st): PDQ's NEW guest ordering client, a Next.js/Turbopack app served anonymously at https://marylandlive.pdqonlineordering.com/ (the same build fronts bossierlive/philadelphialive/pittsburghlive, i.e. the Live! casino 'brand-new mobile ordering suite' of the 2025-03-17 release, and it is a different app from the legacy 13-page WebForms pdqonlineordering.com client the 327th censused). Its chunk set was taken to a FIXPOINT: 49 static chunk/css files referenced from the seed HTML and from each other, 49 held, 0 missing (re-derived this session by re-running the reference regex over every held file), all GET, no session opened and nothing POSTed. The client calls exactly 33 '/api/online/*' endpoints and reads 56 dotted upper-case store-config keys; those two lists are the app's whole server surface. WHAT IT HOLDS FOR THIS CELL (does not settle it): the new client offers scheduled time slots from the server (/api/online/stores/timeslot-detail; eligibility reasons 'timeslotsNotEligible', 'orderingWindowClosed') and its quoted ready time is a STATIC store setting - 'pickupTime:A(t,"PAGE.ORDERCOMPLETE.PICKUPTIME","20")', 'deliveryTime:...DELIVERYTIME","40"', rendered as 'Your order will be ready in {ReadyTime} minutes.' (https://marylandlive.pdqonlineordering.com/_next/static/chunks/1wv3xur2ou__5.js). No kitchen-load or capacity input reaches the client, so the auto-extension conjunct is not evidenced; whether the server withholds slots on capacity is not observable. Held unknown. Retrieved 2026-09-18. || 331st: 331st (slice g): NEW SURFACE, a LIVE RENDER of the legacy storefront's order-time step, the first since the guest-session POST was refused in the 327th. Under a specific owner authorisation of 2026-09-18, ONE anonymous guest session was run on each of 3 public tenants (slicespizza, passariellos, hgchesterbrookpizza .pdqonlineordering.com; 8 requests each, 5-7 s apart, 20:51-20:59 UTC = Friday 16:51-16:59 EDT): GET /, the title page's 'Order Now' guest postback, the 'Pickup' postback, the city dropdown postback, 'Start Order' (Menu.aspx), then the cart's 'Order Time: Change' postback that renders the 'Change Order Time' popup. Nothing was carted, no field was typed into, no account was made, no order was placed. Saved under .cache/q331/pdq-pos/g/pages/. This is a live observation of the vendor's own shipped product (grade B for what it renders), not documentation. WHAT IT SHOWS: the time picker (ddlTime) is 'As Soon As Possible' plus a contiguous list of 15-minute slots. slicespizza: 21 slots, 5:15 PM to 10:15 PM (slot ids 37..57, i.e. quarter-hours counted from the 8:00 AM opening, no gap). passariellos: 17 slots, 5:15 PM to 9:15 PM (ids 33..49, no gap). hgchesterbrookpizza: 21 slots, 5:15 PM to 10:15 PM (ids 29..49, no gap). The first slot was 5:15 PM on all three, even though their order-type labels quote different pickup times (35, 30 and 30 minutes), so the earliest slot is not taken from the store's own quote. At the start of Friday dinner, no slot was withheld and no capacity or 'slot full' message rendered. Two stores also show 'This location is not accepting delay orders for today. All orders will be processed now.' (lblNoDelay), which is a per-store switch for future orders, not a capacity limit. The 7 first-party client scripts (.cache/q312/pdq-pos/assets) contain no capacity, slot or throttle vocabulary, because the slot list is built on the server. WHY STILL UNKNOWN: one moment's render cannot show whether the server removes slots once a per-slot capacity is reached, or pushes out the quote under kitchen load. A contiguous list at 5 PM on a Friday does not bound that, so no 'no' is proposed. Retrieved 2026-09-18. || 333rd: 333rd: NEW SURFACE, does not settle. The POS order-type chooser in the 2017 PDQ POS Overview video (YUUejVp2lhY, 1080p frames 87-93 s) shows a per-order-type READY-IN quote: 'Delivery ... Ready in 35 Minutes', 'Pickup ... Ready in 20 Minutes'. That is a per-channel quote time, but nothing shows capacity per time slot or an automatic extension under load. 333rd V2 TENANT CENSUS (GET only, no session): all 209 tenant subdomains in the 331st tenant list were fetched with curl + browser UA (208 x 200, admin 403). The Next.js V2 client now fronts 7 of them, not 4: the 4 Live! casinos plus 3 PIZZERIAS (mygiaspizza 'Gia's Pizza', slicespizzapa 'Slice's Pizza Ridge Ave', trianospizza 'Triano's Pizza'), and an 8th unlisted tenant, oceancasino.pdqonlineordering.com ('Ocean Casino', found in PDQ's 2025-11-20 video). Every V2 tenant serves the IDENTICAL build: the same 25 /_next/static chunk references as marylandlive, 0 differences, and every one already held in the 331st fixpoint census (.cache/q331/pdq-pos/c/chunks). So the V2 client census the 331st/332nd ran already covers the pizzeria tenants: a newer client on more tenants, no new code. Retrieved 2026-09-18. adversarially verified

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

order-capture-scheduled-orders

CORRECTED after verification: citation moved to /OrderDetails.aspx, which is where the evidence actually lives - the landing page does not contain it, and the step is reachable only by POST from the sign-in page. PDQ's own ordering platform accepts future-dated orders: the Order Details step renders a RadDatePicker calendar and a time dropdown, and the tenant publishes an ordering horizon, 'If you need to place an order greater than 6 days out, please call store.' The platform also ships a delay-order control whose template string reads 'This location is not accepting delay orders for today. All orders will be processed now.' HONESTY CORRECTION: that string sits in a container carrying style='display: none;' and was NOT displayed in the session observed, so it evidences a platform capability and its per-store toggle, NOT an observed store notice; and the time dropdown rendered with zero options in the state reached. SHORTFALL, the half the claim turns on: nothing establishes that a scheduled order is injected into the make queue at a computed FIRE TIME rather than on receipt, and no per-channel lead time is documented. The control ids are platform-level ASP.NET names rather than tenant copy, which limits but does not remove the one-tenant risk. https://passariellos.pdqonlineordering.com/OrderDetails.aspx · retrieved 2026-09-12

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

order-capture-catering

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For order capture the two sites establish the SURFACES and nothing about their behaviour: first-party 8-inch and 10-inch tablets, a counter station, a three-in-one POS/customer-display/kiosk unit, four kiosk models, and an order-entry screen (visible in the 2019 overview flyer) whose keys are categories, sizes, toppings, "1/2 with", "NO'S", Smart Coupon, Gift Card, Phone/Call History, Send, Pay, Charge Card and OOPS. Nothing in either site describes a seat, a course, a tab pre-authorisation, a transfer, an order throttle, a scheduled fire time or a drive-thru timer, and no configuration or settings screen is published anywhere. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: NEW SURFACE, does not settle the cell. Catering is a first-class, separately-detectable order class in PDQ: the Mobile Reporting alert list fires on it specifically - 'Configurable Text/Email Alerts when large orders are voided, AM/PM deposits are made, LARGE CATERING ORDERS ARE PLACED and details of over/under' (https://web.archive.org/web/20150731053525/http://pdqpos.com/mobile-reporting/). That is the only occurrence of the word in the whole corpus assembled this session. None of the claim's conjuncts is touched: no quote, no deposit, no balance-due tracking and no separate event schedule is described on any PDQ surface, and 'Automated event scheduling' in the Feature Overview refers to specials and happy hours, not catering events (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Shortfalling every conjunct is not a partial; held unknown. Retrieved 2026-09-18. || 327th: 327th (APPS/HOSTS SLICE): NEW SURFACE, bounding the ONLINE ORDERING app only (it does not bound the store-level POS, where a catering flow would live). The live tenant TitlePage offers exactly two fulfilment types - the stylesheet's only order-type labels are '.lblOrderTypeText_Delivery' and '.lblOrderTypeText_Pickup' (https://passariellos.pdqonlineordering.com/Styles/Pages/OnlineOrdering.css) - and the page caps forward ordering with the verbatim line 'If you need to place an order greater than 6 days out, please call store.' A 6-day ceiling and a call-the-store fallback is the opposite of a catering flow with quotes, deposits and balance-due tracking, and no page in the 13-page set is a quote, deposit or event-schedule page. Held unknown because the POS product's own catering behaviour is still undocumented and the ordering app cannot speak for it. Retrieved 2026-09-18. || 333rd: 333rd: NEW SURFACE, vendor videos frame-read (PDQ POS Overview YUUejVp2lhY, 1080p, 2017; PDQ POS Demo EoHF88VZ9aA, 2016). The order-completion screen of the running POS shows every financial piece a catering flow uses, but as the GENERIC order flow, not a distinct catering flow: 'Delay Order' with a date picker ('Delay Order For 3/21/2017 5:00:00 PM', quick delays 15/30/45/60/90 min), 'Prepay Cash', 'House Account', 'Tax Exempt', 'Sponsorship', and a footer 'To Pay Balance Later - Press Send Order - Balance Due: $35.25'. The demo also takes a multi-person party order as named sub-orders ('type in Agnes's name, save ... we can go back and forth between the orders ... recap the order on the side with totals for each person'). 'Catering' appears only as a MENU CATEGORY key on the order screen. No quote, no deposit schedule, no event calendar separate from the order queue. Adjacent features, not a partial of a distinct catering flow; held. Retrieved 2026-09-18. adversarially verified

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

order-capture-order-ready-signal

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For order capture the two sites establish the SURFACES and nothing about their behaviour: first-party 8-inch and 10-inch tablets, a counter station, a three-in-one POS/customer-display/kiosk unit, four kiosk models, and an order-entry screen (visible in the 2019 overview flyer) whose keys are categories, sizes, toppings, "1/2 with", "NO'S", Smart Coupon, Gift Card, Phone/Call History, Send, Pay, Charge Card and OOPS. Nothing in either site describes a seat, a course, a tab pre-authorisation, a transfer, an order throttle, a scheduled fire time or a drive-thru timer, and no configuration or settings screen is published anywhere. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

order-capture-void-comp-controls

The only first-party evidence is a peripheral blurb: the FINGERPRINT READER entry says 'save precious seconds at every login and manager override', which establishes manager override as a routine, per-user-authenticated flow in the product. Reason codes on voids/comps/discounts and an exception report are not documented - and they could not have been, because the catalog is a 20-page hardware marketing piece with no settings screens, field tables or configuration procedures anywhere in it, and PDQ publishes no manual, help centre or admin guide. Treat the gap as unpublished, not as absent. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

menu-pricing-nested-modifiers

CLAIM: modifier groups nested at least THREE levels deep, each level with independent min/max selection counts and a forced-selection flag. VERDICT: partial -- multi-level choice nesting is stated by the vendor and corroborated by the shipped online-ordering app's own data shape, but neither the depth nor the min/max/required flags are documented. EVIDENCE 1, verbatim from the PDQ POS Feature Overview PDF (https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf): 'Combos & Choice items / can build multiple levels of choice items to combo'; 'Modifier building'; 'highly advanced menu design system'; and on the POS side 'Pizza setup matrix / Choice setup (topping, size, crust, sauce)'. EVIDENCE 2 (live, vendor's shipped app): the item configurator on the pdqonlineordering.com tenant sites keys its choice rows on a four-part composite captured in an earlier pass as SectionType / SectionID / SecItemID / StepID, i.e. a section -> section-item -> step chain, which is a nesting of at least three addressable levels. SHORTFALL NAMED: 'multiple levels' is not 'at least three', and no min-selection, max-selection or forced/required attribute is published anywhere; the online-ordering assets already held (Scripts/Menu.js 10,049 b, Misc.js 8,648 b, OnlineMaster.js 7,058 b, Validation.js 1,974 b) contain zero occurrences of MinQty, MaxQty, IsRequired, MinSelect or MaxSelect. Grade C. Retrieved 2026-09-17. https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-17 adversarially verified

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

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

332nd: CLAIM: one modifier carries different prices depending on the parent item AND the selected size, set up as a matrix rather than by duplicating the modifier. VERDICT: partial. This adds the PRICE the 325th hold said was missing ('a named Pizza setup matrix shows a configuration shape but no price is attached to it'). The evidence is captures already on disk that no pass had indexed across parents. SURFACE: PDQ's own online-ordering item-builder popups, as served by the vendor's shipped product at https://bigdaddypizza.pdqonlineordering.com/Menu.aspx. There are 29 builder captures on disk: .cache/q290-pdq/b5s-item.html, b5l-item.html, v-bplain1-item.html and v-bplain6-item.html (2026-09-14), plus .cache/q312/pdq-pos/pages/bigdaddypizza-item.html. No new session was opened this pass. I indexed every topping row by its persistent record GUID and its modifier-group id (script .cache/q332/pdq-pos/a/topmatrix.mjs, output topmatrix.out). EVIDENCE: FIVE parent items across THREE item families all render the SAME topping group, 'Modifiers_c8833b3d-4a7e-47ff-a30a-d3c0d491a8c5'. The parents are 'Small Tomato Pie', 'Party Tomato Pie', 'Small Pizza', 'Party Pizza' and 'Small Upside Down Pizza'. They share the same 25 topping record GUIDs, e.g. Pepperoni 3ecc0271-4d57-4102-b2ce-9a0dc5b1c156, Sausage 3ff30b8d-2dea-4514-9ca7-571415d51f73 and Bacon fb4c3663-c759-46... Each record's hidden price cells, named by the vendor's own Topping.js as 'varHalfPrice = gridrow.cells[2]' and 'varFullPrice = gridrow.cells[3]', change with the parent's SIZE: every Small parent shows '1.0000' half / '1.5000' whole, and every Party parent shows '3.5000' / '6.5000'. That holds for 25 of the 25 shared records. So ONE modifier record carries a different price per selected size. It is keyed off the parent, not duplicated per size, which is the matrix shape the 2016 Feature Overview names: 'Pizza setup matrix / Choice setup (topping, size, crust, sauce)' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). SHORTFALL (named): no variation by parent ITEM was observed. At equal size the three families price every shared record identically, e.g. Small Tomato Pie = Small Pizza = Small Upside Down Pizza = 1.0000/1.5000 (parent-item variations found: 0 of 61 multi-parent records). Other tenants duplicate groups per size instead (the 290th found wallyspizza's 14" and 16" Round use separate groups with 0 of 20 GUIDs shared), so the matrix is a configuration choice, not forced. On the 290th rejection ('a partial whose only shortfall is not established is rejected'): the size conjunct is part of the claim itself and is MET on the vendor's product. Only the parent-item conjunct is unestablished, which is the partial the current rules describe. Grade B: a render of the vendor's own shipped ordering product (the 331st graded its live renders B). Retrieved 2026-09-18. https://bigdaddypizza.pdqonlineordering.com/Menu.aspx · retrieved 2026-09-18 adversarially verified

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

menu-pricing-fractional-placement

MOVED OFF `unknown` ON NEW FIRST-PARTY EVIDENCE, and the earlier verifier's reasoning was sound on the evidence it had -- it searched competitor pizza-POS pages and third-party writeups, none of which name PDQ. The evidence is the vendor's own order screen. The check pane of the order-entry screenshot on the Signature Systems overview flyer reads, line by line: MED 14" $7.50 / 1/2 with $0.00 / ANCHOVIES $1.50 / 1/2 with $0.00 / FRESH GARLIC $1.50 -- and a "1/2 with" key sits at the end of the topping grid beside PEPPERONI, MUSHROOMS, SAUSAGE and the rest. So a placement modifier is applied twice on one pie, each time carrying its own separately-priced topping. That is sectioned placement at halves with independent per-section pricing. The "1/2 with" string is read twice independently on the same screen -- once as a key in the topping grid, where it is large and unambiguous, and twice as an indented child line under the bold MED 14" parent -- which is why it is reported despite the small italic type of the check pane; the indentation of the four child rows under the parent is clear at every magnification. Shortfalls: HALVES ONLY -- no quarter or third key is present, and the claim asks for quarters ideally -- and the placement RULE is undocumented, so nothing establishes how the price is derived or whether the behaviour is configurable. See `menu-pricing-half-and-half-rule`, which stays `unknown` for exactly that reason. The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-SSI-flyer-lower-res.jpg · retrieved 2026-08-30

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

menu-pricing-half-and-half-rule

PDQ's own multi-tenant online-ordering platform (*.pdqonlineordering.com, 'Powered by PDQ Signature Systems' on every captured page). Retrieval: live guest item-builder captures, read-only, 2026-09-14; nothing carted, Checkout never touched. The shared client script Scripts/Topping.js was fetched from bigdaddypizza and passariellos and is byte-identical (14,276 bytes, md5 870d4b39...). MET (one pricing lever for a topping on half a pizza): AnimateTopping() reads 'varHalfPrice = gridrow.cells[2].textContent;', 'varFullPrice = gridrow.cells[3].textContent;' and 'varQuarterPrice = gridrow.cells[7].textContent;', then case 'left' and case 'right' set 'varPrice = varHalfPrice;', the four quarter cases set varPrice = varQuarterPrice, and 'full'/'fullquarter' set varPrice = varFullPrice. Each topping row stores its own half price per size. bigdaddypizza Party Tomato Pie (group Modifiers_c8833b3d): Pepperoni 3ecc0271 half 3.5000 / full 6.5000, Shrimp 60bb1f45 half 3.5000 / full 10.0000. The lever is an ABSOLUTE PRICE the operator types in, NOT a fraction-of-full rule: wallyspizza 16" Round, Veggie 78542c1a, half 3.7500 / full 3.0000, so the half costs MORE than the full; italiandelight has half 0 / full 2.0000 on 21 of 21 rows while still offering Topping_Left and Topping_Right. An operator can make a half cost any fraction of full by typing that price topping by topping, so the fraction-of-full outcome is reachable, but only by hand. SHORTFALL (observed, online-ordering client): (a) there is only one lever and nothing to choose between. The grid has exactly nine hidden cells (index, GUID, Half, Full, HalfDbl, FullDbl, Show, Quarter, QuarterDbl), and the shared Topping.js has only three price branches (half, quarter, full), with no maximum, averaging or other-half comparison anywhere. So the storefront cannot charge the higher-priced half or average the halves, whatever a tenant has set. (b) half-and-half here means placing a topping on one half of one base item. Across 69 cached menu files (.cache/q291-pdq/menus), 'half and half' appears in only 5: drinks at claudios-pizzeria, italian-touch, casadamico and gzepps, and one ready-made pizza at pudgiesofwilliamsport ('Half N Half', 'Double Pepperoni on one side, plain cheese on the other side'). NOT ESTABLISHED: the PDQ POS terminal's own half rule (the 2019 SSI flyer shows '1/2 with' at $1.50 per topping, with no whole-pie price on screen); the office-only admin console; whether the server reprices an order when it is submitted (no order was submitted). VARIANCE CONTROL (ratio census, .cache/q293-pdq/ratio.mjs, cell by cell): half/full is 0.538 on 24 rows and 0.350 on 1 at bigdaddypizza Party, 0.667 x24 and 0.250 x1 at bigdaddypizza Small, 0.570 x27, 0.545 x3, 0.427, 0.499 and 1.000 at passariellos MED, 0.333 x15, 0.462 x4 and 0.300 at wallyspizza 14" Round, 0.250 x11, 0.500 x3, 0.375 x2, 0.208, 0.288, 0.417 and 1.250 at wallyspizza 16" Round, and 0.000 on every row at italiandelight (21) and vizzinispizza (17). Quarter price equals half price on every row with a full price. The ratios differ by topping, size and tenant, which is what hand-typed prices look like; no single configured fraction explains them. POISON EXCLUDED: 'Half and Half Tea' and the other drink hits are beverages; 'Half N Half' at pudgies is a ready-made menu item, not a pricing rule; 'Half Loaf' is a bread size; the HalfDbl/FullDbl cells and the X2 icon are the quantity tier (scored in topping-quantity-tiers); the Left/Right/Quarter controls themselves are placement (scored in fractional-placement); the Show cell is a display flag, not a price. https://bigdaddypizza.pdqonlineordering.com/ · retrieved 2026-09-14 adversarially verified

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

menu-pricing-topping-quantity-tiers

PDQ's own multi-tenant online-ordering platform (*.pdqonlineordering.com, 'Powered by PDQ Signature Systems' present on every captured page as a positive control). Retrieval: live guest session, read-only, 2026-09-14, opening the item-builder popup; nothing was added to the cart. The shared client script Scripts/Topping.js was fetched from two tenants and is byte-identical (14,276 bytes). MET: a per-topping Double tier that is distinct from adding the topping twice. Each topping row renders a checkbox with value="Topping_Double" under a column image <img id="imgDouble" alt="Double" class="imgDouble" src="../Images/Site/Icons/Toppings/X2.png" title="Double" />. Its price is stored separately per topping: Topping.js reads 'varHalfDblPrice = gridrow.cells[4].textContent;' and 'varFullDblPrice = gridrow.cells[5].textContent;' and charges formatCurrency(varDblPrice) when the Double box is checked. passariellos 'MED PIZZA' $17.99: Pepperoni half 1.9900, full 3.4900, double half 3.98, double full 6.98. SHORTFALL (observed): (a) there is no light or extra tier per topping. Topping.js recognises only None, Full, FullQuarter, Left, Right, the four quarters and Double, and the builders render only Topping_None, Topping_Left, Topping_Full, Topping_Right and Topping_Double. On passariellos and wallyspizza, light and extra appear only as separate whole-item option labels (raw >Light Sauce<, >Lite Cheese<, >Extra Cheese ($2.00)<), not as per-topping tiers. (b) the Double tier carries an absolute stored price, not a price multiplier. NOT ESTABLISHED: whether the PDQ POS terminal or the office-only admin console offers more tiers. VARIANCE CONTROL: Double is enabled on 33 of 36 rows at passariellos and 19 of 20 at wallyspizza (wallyspizza 16" Round Pepperoni 0.7500/3.0000/1.5/6), and disabled on 25 of 25 rows at bigdaddypizza, where the double cells are 0 0. Enabling Double is tenant configuration, so its absence on one tenant is not scored as 'no'. POISON EXCLUDED: 'Double Cut' is a slicing instruction; 'Light Sauce', 'Lite Cheese' and 'Extra Cheese ($2.00)' are standalone mod options, not topping tiers; 'Extra Bread' is a menu item; 'light egg batter' is a dish description; 'Half Loaf' is a bread size; the '2 Extra Large Plain Pizzas' coupon is a size name; the Left/Right/Quarter values are placement, not quantity. https://passariellos.pdqonlineordering.com/ · retrieved 2026-09-14 adversarially verified

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

menu-pricing-size-style-matrix

The order-entry screenshot on the Signature Systems overview flyer shows a size row and a style row crossed with each other: Small 10", MED 14", Large 16" for the regular crust, and SM Sicilian, LARGE SICILIAN, SM VEGGIE SICILIAN, LG VEGGIE SICILIAN beside them, with a matching specials row (10"/14"/16" PIZZA SPECIAL, SM SICILIAN SPECIAL, LG SICILIAN SPECIAL). The check pane prices the selected cell independently -- MED 14" rings at $7.50 -- so distinct size x style cells carry distinct prices. Shortfall, and it is the claim's actual subject: this is the ORDERING surface, not the configuration surface. Nothing shows a two-axis grid with a per-cell override; seven flat items each with its own price would produce exactly this screen, and PDQ publishes no menu-setup documentation that could tell the two apart. The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-SSI-flyer-lower-res.jpg · retrieved 2026-08-30

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

menu-pricing-included-allowance

PDQ's own multi-tenant online-ordering platform (*.pdqonlineordering.com; 'Powered by PDQ Signature Systems' on 69 of 69 captured Menu.aspx pages as a positive control). Retrieval: live guest sessions, read-only, 2026-09-14, opening the item-builder popup; nothing was added to the cart and Checkout was never touched. Leads came from a tokenised term census over the 69 menus ('included' 2 tenants, 'free topping' 2, 'each additional'/'additional topping' 5). Six builders were opened on six unrelated operators. MET: an item can define an included allowance of N modifiers at no charge, with a configured count bound, and premium options inside the allowance can carry their own upcharge. claudios-pizzeria 'Create Your Own Flat Bread' $9.99, copy '(Up to 3 toppings included)', group 'Choose One:' with instruction 'You MUST select between One and Three': 21 options, 18 at ItemPrice="0.0000" and Meatballs/Steak/Eggplant at 1.0000. jjspizzashack 6" 'Crispy French Bread Pizza' $6.50, copy 'With your choice of three pizza toppings. Additional topping 50¢', group 'Toppings:' 'You may choose up to Three', 18 options at 0. italiandelight 'Sm Calzone' $8.99, copy 'one free topping (must select topping or it will be just cheese)', group 'Select Free Topping:' 'Choose One', 18 at 0 and Ricotta Cheese 2.0000. denirospizza 'Kids Pita Pizza' $7.99 'With one topping included.', 'Choose 1 Topping:' 'Choose One', 18 at 0. vizzinispizza '5) 1-Pizza Deal' $8.45, 'Choose 1st Topping:' 'Choose One', 16 at 0. freshworksofholmecircle 'Create Your Own Fries' $8.00 'Any 3 Toppings', 'Choose 3 Toppings:' 'You may choose up to Three', 10 at 0. SHORTFALL (observed): (a) overage is not charged automatically on this surface. The allowance group is capped at N, and any topping beyond N must be picked from a second, duplicated modifier group with its own per-topping price: claudios 'Additional Toppings:' 18 at 1.6000 (15 names shared, e.g. Pepperoni 0 / 1.60); jjspizzashack 'Additional Toppings:' 21 at 0.5000 (15 shared); denirospizza 'Additional Toppings:' 15 at 1.99; italiandelight 'Extra Toppings:' and vizzinispizza 'Additional Toppings:' as Topping.js grids (italiandelight first row 0 half / 2.0000 full; vizzinispizza Pepperoni 0 / 0.7500). freshworks has no overage path at all. No builder renders a single list whose (N+1)th selection is priced. The modifier markup carries only per-option ItemName/ItemPrice and a free-text instruction, with no free-count attribute, and the shared scripts (OnlineMaster.js toggleCheckState, Misc.js, and Topping.js, byte-identical on two tenants) contain no count-to-price logic. (b) There is no substitution credit: 0 negative ItemPrice values, and no credit or substitution text in any builder. NOT ESTABLISHED: whether the server reprices overage on submit (no order was ever submitted); whether the PDQ POS terminal or the office-only admin console supports a free-count modifier; and whether substitutions are forbidden. The count bound forbids overage only inside the allowance group. VARIANCE CONTROL: 6 of 6 builders on 6 unrelated operators show no automatic overage. 5 use the duplicated-group construction, and 1 (freshworks) caps the allowance with no overage path. No PDQ tenant was found modelling it differently, so the shortfall is not attributed to one operator's configuration. POISON EXCLUDED: 'Choose One:' is claudios' group TITLE while its instruction says between One and Three; 'Prices listed are per half pound' (freshworks) is deli weight; 'Meatball (4-cut Halves)' (pizzabella) is a cut; '10 Items minimum' (denirospizza) is catering; 'Includes 2 Traditional Toppings. ($2.00 ea. additional topping per 10 pieces)' (italiandelight, italiantouchmtjackson; $1.00 at italian-touch) is a platter section header, not verified in a builder; '(No substitutions) Additional toppings extra' (levantespizza) is a section banner, not verified in a builder; 'Free 2 Liter...', 'Free Delivery' and 'Free Small Plain' are coupon names; Misc.js 'Free to use if this text is included' is a licence comment; 'Topping_Double' is a quantity tier, not an allowance. https://claudios-pizzeria.pdqonlineordering.com/ · retrieved 2026-09-14 adversarially verified

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

menu-pricing-combos

CLAIM: combo/meal construction where components can be swapped with a price delta, AND the system auto-detects and converts eligible a-la-carte cart items into the combo price. VERDICT: partial -- combos with multi-level component choice are a named back-office build feature; neither the price-delta swap nor auto-combo detection is documented. SURFACE: the PDQ POS Feature Overview PDF via Wayback (https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf, 217,190 bytes, 6,924 chars extracted), section 'Back Office (POS)'. EVIDENCE, verbatim: 'Combos & Choice items' with the sub-bullet 'can build multiple levels of choice items to combo', beside 'highly advanced menu design system' and 'Modifier building'. SHORTFALL NAMED: no upcharge or price-delta field on a swapped component is described, and no cart-side auto-combo recognition ('combo detected', 'meal upgrade') appears on any PDQ surface including the live pdqonlineordering.com tenant sites. Grade C (vendor feature summary, retired copy). Retrieved 2026-09-17. https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-17 adversarially verified

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

menu-pricing-upsell-prompts

The POS Solutions flyer leads with selling "more food via programatic up-sell", and two of its three panels attach up-sell to a named surface: DIGITAL MENU BOARDS are "GREAT FOR UP-SELL/PROMOTIONS" with "INSTANT MENU/PRICE UPDATES", and GUEST DISPLAY MONITORS "SHOWCASE PROMOS; UP-SELL PRODUCT". Two shortfalls, both load-bearing. The channels evidenced are customer-facing DISPLAYS, not the POS, kiosk or online-ordering flows the claim names, and nothing describes a prompt configured per item or per channel. And the claim's second half -- that the vendor reports attach-rate on those prompts -- has no evidence at all; no attach-rate metric appears on the reporting dashboard or anywhere else. The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-solutions-flyer-lower-res.jpg · retrieved 2026-08-30

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

menu-pricing-86-propagation

Score upheld, but the supporting note is materially wrong and should be corrected before it propagates into the narrative. The Yellow Dog page actually says PDQ 'gets item data from Yellow Dog's API every 15 minutes', that terminal refresh 'can be done manually but it is also done automatically nightly', and that 'new/updated barcodes will be scannable at the POS WITHOUT a refresh'. The dossier compressed this into 'manual terminal refresh, not push propagation', which overstates the counter-signal. || 332nd: 332nd: NEW CHECK against the 331st's V2 ordering-client census, 49 chunks plus rendered pages (3.57 MB), which no pass had checked for this cell. PDQ's own new online-ordering client has NO per-item availability STATE. The item schema's only availability fields are time windows and gates: AvalStartTime/AvalEndTime, AvalPickup/AvalDelivery, AvalLoyalty/AvalNoLoyalty/AvalLoyaltyTiers, AvalDataKeyGroups and AvalSSI (https://marylandlive.pdqonlineordering.com/_next/static/chunks/1wv3xur2ou__5.js). CONTROLS (case-insensitive, all 72 files): stock 0, 'sold out' 0, 'out of stock' 0, inventory 0. 'unavailable' has 21 hits, all store, time-slot, channel or geolocation states ('Ordering unavailable', 'Pickup Unavailable', 'POSITION_UNAVAILABLE'), none at item level. POISON NAMED: all 11 '86' hits are noise, from CSS lab() colour values, charCode case labels and a base64 length regex. WHY STILL UNKNOWN: a client with no 86 flag can still receive a menu payload the server has already stripped of 86'd items. So this neither shows nor bounds propagation, and the claim's KDS, kiosk, marketplace and latency conjuncts are untouched. Retrieved 2026-09-18. || 333rd: 333rd: NEW SURFACE, adjacent only. PDQ's 'Integrated Digital Menu Boards' video (fJePiriHNNg, 2017, captions + frames) documents POS-to-board PROPAGATION for PRICES with a stated latency: 'our menu boards are fully integrated with our point of sale for pricing ... we'll change the price of cheeseburgers from 6.99 to 7.99 we simply make the change on the point of sale and save WITHIN A FEW SECONDS the price updates on the screens'. It says nothing about item availability / 86 status, and names no online-ordering, kiosk or marketplace target. Price propagation to one surface is not an 86 propagating to all surfaces. Retrieved 2026-09-18. || 334th: 334th: NEW SURFACE, adjacent only. PDQ's own silent slide video '5 Profit Generating Essentials for POS Systems' (https://www.youtube.com/watch?v=P1NW60Uw3Gw, 366 s, uploaded 2018-04-24, presenter Larry Fiel, VP of Marketing; the audio track is digitally silent, max amplitude 0.0, so every prior caption/ASR pass got nothing from it; downloaded at 1080p, 376 scene-change frames extracted and read as contact sheets). Its menu-board slide (frames 322-324 s) reads 'Integrated Digital Menu Boards: Real-time price changes by store/region/all'. That is PRICE propagation to boards, scoped by store/region/chain, the same shape as the 333rd's menu-board video; no slide mentions item availability, 86, sold-out or propagation to online ordering, kiosk or marketplaces. Retrieved 2026-09-18. adversarially verified

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

menu-pricing-countdown-auto-86

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For menu and pricing the only substantive artefact is the order-entry screenshot on the 2019 overview flyer, which is an ORDERING surface: it shows sizes, styles, a topping grid, a "1/2 with" placement key, a "NO'S" key and priced check lines. It shows no setup surface at all. Every claim in this category is about how the menu is CONFIGURED -- nesting depth, min/max counts, quantity tiers, effective dates, price books per channel, allowances, franchise inheritance, allergen fields -- and PDQ publishes no menu-setup documentation of any kind on either host. The one third-party document that touches menu data is Yellow Dog's integration page, and it describes item data flowing INTO PDQ from Yellow Dog every 15 minutes, not PDQ's own menu model. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

menu-pricing-dayparting

'Automated event scheduling (specials, promotions, happy hour, etc.)' establishes automatic time-based activation and deactivation of promotional pricing - happy hour is a daypart by definition - which is the claim's PRICES conjunct. TWO SHORTFALLS: the claim also covers scheduling whole MENUS and individual ITEMS, neither stated; and nothing addresses whether scheduling resolves in the LOCATION'S OWN TIMEZONE, which is the failure mode for multi-site operators. EXTRACTION NOTE: this bullet wraps a line and is recoverable only whitespace-normalised, not byte-contiguous. SOURCE DATE: a 2016 first-party sell sheet (uploads/2016/12) recovered from the Internet Archive because pdqpos.com left WordPress and it 404s live. Evidence about the 2016 product. Verified that the live 2025 catalogue restates none of it - the tokens split, gift, transfer, email, security role, happy hour and permission each occur zero times there - so carry-forward rests on PDQ POS being a continuously-sold product line, not on any current document. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-12 adversarially verified

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

menu-pricing-channel-price-books

CLAIM: distinct price books per channel (dine-in, pickup, delivery, kiosk, each marketplace) INCLUDING percentage-markup rules applied to a base price rather than per-item entry. VERDICT: partial. NEW SURFACE (331st): PDQ's NEW guest ordering client, a Next.js/Turbopack app served anonymously at https://marylandlive.pdqonlineordering.com/ (the same build fronts bossierlive/philadelphialive/pittsburghlive, i.e. the Live! casino 'brand-new mobile ordering suite' of the 2025-03-17 release, and it is a different app from the legacy 13-page WebForms pdqonlineordering.com client the 327th censused). Its chunk set was taken to a FIXPOINT: 49 static chunk/css files referenced from the seed HTML and from each other, 49 held, 0 missing (re-derived this session by re-running the reference regex over every held file), all GET, no session opened and nothing POSTed. The client calls exactly 33 '/api/online/*' endpoints and reads 56 dotted upper-case store-config keys; those two lists are the app's whole server surface. EVIDENCE: PDQ's menu model carries MULTIPLE PRICE LEVELS per item and maps each ordering channel to one of them per store. Every item, option and topping in the typed menu schema has a base price plus a price-level array - 'BasePrice ... ExtendPrice:s.z.array(...)' - and the topping renderer also prices full/half/double placement through the same mechanism ('BasePriceFull'->'ExtendPriceFull', 'BasePriceHalf'->'ExtendPriceHalf', 'BasePriceDouble', 'BasePriceDoubleHalf') (https://marylandlive.pdqonlineordering.com/_next/static/chunks/1wv3xur2ou__5.js). The store's price setup (/api/online/stores/price-setup) returns 'BaseSettings:[{Type,PriceIndex}]', and the client selects the level by channel: 'let e={9:"Delivery",8:"Pickup"} ... return A.BaseSettings?.find(r=>r.Type===e[t])?.PriceIndex??1' (https://marylandlive.pdqonlineordering.com/_next/static/chunks/1zs8y20hmsmmo.js), then prices with 'getItemPrice=(t,r,i)=> ... a=t[ExtendPrice...]; if(1===r)return n??a[0]; if(r<=a.length)return a[r-1]' (https://marylandlive.pdqonlineordering.com/_next/static/chunks/3-pqppw_7-kgz.js). So delivery and pickup can carry different prices from store-configured price levels - the per-channel price book conjunct, for the vendor's own online channels. SHORTFALLS (named): the levels are explicit per-item price columns, i.e. manual per-item entry; no percentage-markup rule applied to a base price appears anywhere in the schema or code; dine-in/kiosk mapping is not visible in this client; and PDQ is absent from DoorDash's 64-provider registry, so no per-marketplace price book is evidenced. Retrieved 2026-09-18. https://marylandlive.pdqonlineordering.com/_next/static/chunks/1zs8y20hmsmmo.js · retrieved 2026-09-18 adversarially verified

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

menu-pricing-dual-pricing

Pizzeria copy claims PDQ 'lowers those costly credit-card fees', which hints at cash discount, but no dual-pricing feature is described. || 332nd: 332nd: NEW CHECK against the 331st's V2 ordering-client census (72 files, 3.57 MB). It found a POISON a future pass should not mistake for a cash/card price pair. Every menu node carries 'BasePrice2' and 'ExtendPrice2', but the code uses them as the price of a PAIRED SECOND POS ITEM. When 'mainSectionItem.POSItemName2' is set, the builder pushes an extra line '{POSItemCode: POSItemNum2, ItemName: POSItemName2, ItemPrice: getItemPrice(..., "BasePrice2"), ModID: 1}', and the menu shows BasePrice + BasePrice2 SUMMED (https://marylandlive.pdqonlineordering.com/_next/static/chunks/3-pqppw_7-kgz.js; .../3axfp_7o0vorh.js). The price index that selects among ExtendPrice[] is a CHANNEL index, 'BaseSettings.find(Type==="Delivery"/"Pickup").PriceIndex', not a tender. The only card-cost vector in checkout is an order-level fee line, 'totalPIF', labelled by store config 'PIF.DISPLAYNAME' (default 'Fee'). That is a surcharge shape, which the claim treats as the backwards structure. CONTROLS (all 72 files): 'dual' 0, 'surcharge' 0, 'CashDiscount'/'cash discount' 0, 'card price' 0. The 'Cash*' hits are payment options (CashOption, CashOnFirstOrder, CashFromGuests). WHY STILL UNKNOWN: this bounds only PDQ's online-ordering client. Whether the store POS can run an item-level cash/card price is unseen, and a client-side absence does not bound it (331st rule). Retrieved 2026-09-18. adversarially verified

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

menu-pricing-versioning-effective-dates

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For menu and pricing the only substantive artefact is the order-entry screenshot on the 2019 overview flyer, which is an ORDERING surface: it shows sizes, styles, a topping grid, a "1/2 with" placement key, a "NO'S" key and priced check lines. It shows no setup surface at all. Every claim in this category is about how the menu is CONFIGURED -- nesting depth, min/max counts, quantity tiers, effective dates, price books per channel, allowances, franchise inheritance, allergen fields -- and PDQ publishes no menu-setup documentation of any kind on either host. The one third-party document that touches menu data is Yellow Dog's integration page, and it describes item data flowing INTO PDQ from Yellow Dog every 15 minutes, not PDQ's own menu model. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: MERGE HOLD (proposed partial/C, held unknown): recurring happy-hour / event price scheduling is an adjacent feature; none of staging a version, preview or rollback is described. PROPOSAL AS WRITTEN: CLAIM: menu changes staged as an effective-dated version, previewed before publish, and rolled back to a prior version after publish. VERDICT: partial. EVIDENCE: the 2016 Feature Overview lists 'Automated event scheduling (specials, promotions, happy hour, etc.)' among Point-of-Sale Capabilities, and the 2004 ProBar/ProTable pages implement it as prices that change on a stored calendar of events and dayparts (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf; https://web.archive.org/web/20041208105701/http://www.pdqpos.com/bar.htm). Menu/price changes can therefore be entered in advance and activate on a schedule, which is the effective-dating conjunct. SHORTFALLS (named): nothing describes a VERSION - no staged draft, no preview-before-publish step, and no rollback to a prior version after publish; an event calendar of dayparts is not a menu version history. Retrieved 2026-09-18. adversarially verified

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

menu-pricing-franchise-hierarchy

CLAIM: central corporate menu template pushed to locations with FIELD-LEVEL GOVERNANCE controlling which attributes a location may override. VERDICT: partial. EVIDENCE: the 2016 Feature Overview's 'Back Office (POS)' column opens with a three-level control hierarchy, in this order: 'Master control / Store level control / Station control', alongside 'Categories', 'Modifier building', 'Combos & Choice items' and 'highly advanced menu design system' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). PDQ's Jimmy John's case study shows the master level in use across a chain: 'Jimmy John's also routinely offers limited time offers, working with Signature Systems, Inc. to LAUNCH EACH OFFER ACROSS THE COUNTRY SIMULTANEOUSLY AND WITHOUT ERROR so that customers in Maine can have the same experience as those in California' (https://pdqpos.com/ProjectDetail?pk=jjsw). A master-to-store menu push therefore exists. SHORTFALLS (named): 'Store level control' establishes that a store tier exists but says nothing about WHICH FIELDS it may override or that governance is field-level; and the Jimmy John's launch is described as work PDQ performs with the customer, not as a self-serve corporate template screen. Retrieved 2026-09-18. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-18 adversarially verified

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

menu-pricing-allergen-nutrition

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For menu and pricing the only substantive artefact is the order-entry screenshot on the 2019 overview flyer, which is an ORDERING surface: it shows sizes, styles, a topping grid, a "1/2 with" placement key, a "NO'S" key and priced check lines. It shows no setup surface at all. Every claim in this category is about how the menu is CONFIGURED -- nesting depth, min/max counts, quantity tiers, effective dates, price books per channel, allowances, franchise inheritance, allergen fields -- and PDQ publishes no menu-setup documentation of any kind on either host. The one third-party document that touches menu data is Yellow Dog's integration page, and it describes item data flowing INTO PDQ from Yellow Dog every 15 minutes, not PDQ's own menu model. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 331st: MERGE HOLD (proposed no/B, held unknown): 331st merge: the claim's publish-to-online-ordering conjunct fails on both ordering clients, but whether the store POS STORES allergen/nutrition per item is unseen; if it does, the verdict is partial, not no. A back-office/ordering-client census does not bound the store-level POS. PROPOSAL AS WRITTEN: CLAIM: stores allergen flags and nutrition values per item AND publishes them to online ordering and third-party menus, AND can derive nutrition from linked recipe components. VERDICT: no. NEW SURFACE (331st): PDQ's NEW guest ordering client, a Next.js/Turbopack app served anonymously at https://marylandlive.pdqonlineordering.com/ (the same build fronts bossierlive/philadelphialive/pittsburghlive, i.e. the Live! casino 'brand-new mobile ordering suite' of the 2025-03-17 release, and it is a different app from the legacy 13-page WebForms pdqonlineordering.com client the 327th censused). Its chunk set was taken to a FIXPOINT: 49 static chunk/css files referenced from the seed HTML and from each other, 49 held, 0 missing (re-derived this session by re-running the reference regex over every held file), all GET, no session opened and nothing POSTed. The client calls exactly 33 '/api/online/*' endpoints and reads 56 dotted upper-case store-config keys; those two lists are the app's whole server surface. EVIDENCE/BOUND: the new client declares its menu data model as typed zod schemas (Menu -> MainGroups -> MainSections -> MainSectionItems/Window -> WindowSections -> SectionItem / SectionToppingItem), and the per-item fields are enumerated there: DisplayName, ItemDescription, ImagePath/ImageName, SortOrder, AvalPickup, AvalDelivery, AvalLoyalty/AvalNoLoyalty/AvalLoyaltyTiers, AvalDataKeyGroups, BasePrice/ExtendPrice, BasePrice2/ExtendPrice2, POSItemNum/POSItemName(2), IsTaxable/IsTaxable2, IsAlcohol, and per section MinForce/MaxForce and IsTopping (https://marylandlive.pdqonlineordering.com/_next/static/chunks/1wv3xur2ou__5.js). There is no allergen, nutrition or calorie field. The schemas are not exhaustive (the topping renderer also reads BasePriceFull/AllowHalf/AllowDouble, which the schema omits), so the bound rests on the CODE: any field the app displays must be referenced by name somewhere in the 49 files, and none of the allergen/nutrition vocabulary is. CONTROLS (tokenised, word/camelCase boundary, case-insensitive) over all 49 files + the 19 rendered route pages, 3.46 MB: known positives IsAlcohol 29, Gratuity 57, TableNumber 26; allergen 0, allergens 0, allergy 0, calorie 0, calories 0, nutrition 0, nutritional 0, kcal 0, gluten 0, dairy 0, vegan 0, vegetarian 0, dietary 0 (poison: 'contains' 110 = DOM Node.contains). The LEGACY WebForms client (39 files incl. its Menu.js and two tenant Topping scripts, 0.75 MB on disk from the 290th-327th; known positive Topping 176) is also zero on allergen/calorie/nutrition/gluten, and on its live tenant menus allergen information exists only as operator-typed item NAMES and a typed disclaimer - 'Gluten Free 12" 6 Slices', 'Passariello's pizza & pasta made with gluten free flour is prepared in a common kitchen with the risk of gluten exposure' (https://passariellos.pdqonlineordering.com/). So neither of PDQ's first-party online-ordering clients can receive or display a structured allergen/nutrition value, and the 'publishes to online ordering' conjunct fails on the vendor's own channel; PDQ is absent from DoorDash's provider registry, and no recipe-derived nutrition is described on any PDQ surface. Whether the store POS keeps a private allergen flag is not observable, but it could not satisfy the claim without the publishing conjunct. Retrieved 2026-09-18. adversarially verified

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

menu-pricing-recipe-linkage

Counter-signal: recipe/on-hand costing is handled by partners (Yellow Dog, Restaurant365) in documented integrations.

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

menu-pricing-3p-menu-push

CLAIM: menus pushed to third-party marketplaces via a certified DIRECT integration (not scraping or a menu-management middleman), with per-item sync status and rejection errors surfaced. VERDICT: partial. NEW SURFACE: PDQ's own DoorDash press release PDF (December 16, 2020), recovered from the Wayback CDX index of pdqpos.com and not linked from the current site. It states the integration keeps the menu in sync: 'the integration allows Jimmy John's ... to add more than 2,400 DoorDash service locations, while significantly minimizing changes to its in-store operations and ENSURING ITS EXISTING MENUS AND STORE HOURS STAY SYNCED WITH THE DOORDASH PLATFORM', and that it is direct and first-of-kind: 'To date, PDQ Signature Systems is the only POS provider to accomplish a seamless, value-added integration to DoorDash's new Self-Delivery platform' (https://web.archive.org/web/20250121221212/https://www.pdqpos.com/wp-content/uploads/2020/12/PR_JJ-DoorDash3.pdf). DoorDash, Uber Eats and Grubhub are each named as direct integrations on the Integrations page (https://web.archive.org/web/20220627152844/https://www.pdqpos.com/integrations/). SHORTFALLS (named): nothing states that MODIFIERS, PHOTOS or channel-specific price markups are part of the push, and nothing describes per-item sync status or rejection errors being surfaced to the operator - so the claim's second conjunct is entirely unmet. Retrieved 2026-09-18. https://web.archive.org/web/20250121221212/https://www.pdqpos.com/wp-content/uploads/2020/12/PR_JJ-DoorDash3.pdf · retrieved 2026-09-18 adversarially verified

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

menu-pricing-dynamic-pricing

CLAIM: rule-based dynamic pricing where item price varies automatically by time, demand or channel, with configurable floor/ceiling guardrails. VERDICT: partial. NEW SURFACE - the retired per-module pages of pdqpos.com (2004), recovered from the CDX index and not present in any prior pass's corpus. ProTable: 'Automatic Price Changes - ProTable can AUTOMATICALLY CHANGE THE PRICE OF ITEMS BASED ON TIME OF DAY OR DAY OF WEEK. UP TO FOUR DIFFERENT PRICES FOR AN ITEM can be used based on the establishments requirements.' (https://web.archive.org/web/20041208124200/http://www.pdqpos.com/table.htm). ProBar: 'Automatic Price Change - ProBar can be customized so PRODUCT PRICES CHANGE BASED ON EVENTS SUCH AS LUNCH, DINNER, HAPPY HOUR, LADIES NIGHT, etc' (https://web.archive.org/web/20041208105701/http://www.pdqpos.com/bar.htm). The capability survives into the current line: the 2016 Feature Overview lists 'Automated event scheduling (specials, promotions, happy hour, etc.)' under Point-of-Sale Capabilities (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). So the TIME axis of the claim is met by a rule the operator configures. SHORTFALLS (named): price never varies by DEMAND (no load, no inventory, no surge language anywhere) and the four-price ceiling is a slot count, not a floor/ceiling guardrail on a computed price; per merge policy positives from the retired 2004 module pages carry at most partial. Retrieved 2026-09-18. MERGE NOTE (326th): cited to the 2016 Feature Overview (Automated event scheduling: specials, promotions, happy hour); the 2004 module pages are corroboration only, being too old to carry the verdict alone. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-18 adversarially verified

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

payments-processor-choice

CLAIM: The POS operates with third-party payment processors the merchant chooses (a documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. VERDICT partial/C. MET (not tied to one in-house processor): (1) PDQ's own 'PDQ POS Feature Overview' (Product-Feature-Summary.pdf, uploaded 2016-12, Wayback capture 2019-12-18, text extracted 2026-09-16) lists under payments "Integrated to multiple payment gateways and payment processors for credit cards", next to "Fully PCI compliant" and "EMV capable". Anyone can open this URL without logging in. (2) The live product agrees. PDQ's multi-tenant online ordering (*.pdqonlineordering.com) takes cards through more than one third-party gateway, and the gateway varies by tenant. The shared CheckOut.aspx script routes card results with ProcessPaymentData('DC'), ProcessPaymentData('MPS') and ProcessPaymentData('FP'). After the 'Credit Card' payment-method postback, 21 of 45 tenants load Datacap hosted tokenisation (script token.dcap.com/v1/client/hosted with a live DCActivate call) and 10 of 45 load Mercury's hosted iframe (hc.mercurypay.com/CheckoutIFrame.aspx). No tenant loads both. 14 are unresolved: 5 credit-card-only tenants stop at 'Invalid Contact Name' before the frame loads, 4 credit-card-only tenants render no frame, and 3 have no payment dropdown. FreedomPay is a code path only, loaded by 0 tenants. Denominators: 69 tenants were probed, 49 reached Menu.aspx in a guest Pickup session (20 stopped at OrderDetails.aspx), and 45 reached CheckOut.aspx (4 had no item that could be carted without a required choice). Guest sessions ran 2026-09-16 with .cache/q312/pdq-pos/seam.mjs. The verifier re-drove hgchesterbrookpizza (Datacap), passariellos (Datacap) and slicespizza (Mercury), and the counts reproduce from the saved pages (verify/count.mjs). One item was carted in session only. No details were typed and nothing was submitted. The checkout evidence appears only after session postbacks: CheckOut.aspx sends an anonymous visitor to MessagePage.aspx?SessionEnded=True with a 302. That is why the cited URL is the feature summary. SHORT: (a) no list of supported processors is published. The feature summary names neither gateways nor processors, and a gateway is not a processor. Datacap and Mercury hosted checkout could each front PDQ's own PDQ Pay, so the split across tenants alone does not prove the merchant chooses. The 'multiple ... processors' limb rests on a 2016 first-party feature summary, and the currently promoted PDQ Pay page says nothing either way. (b) grade floor: this is a differentiator claim, and a feature summary plus live-product observation is grade C, so yes is not available. (c) the live evidence covers the online-ordering card path only, not the in-store terminal. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-16 adversarially verified

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

payments-published-rates

PDQ operates a dedicated first-party payments product page for PDQ Pay. Its entire commercial copy is qualitative — 'Simplify payment acceptance and improve your bottom line', 'defend your revenue with leading fraud intelligence' — and it contains no rate, no percentage, no per-transaction figure and no interchange-plus markup. The live homepage likewise carries the claim that PDQ 'lowers those costly credit-card fees' with no number attached. A vendor payments page that markets on price and states no price is positive evidence that rates are quote-only. https://web.archive.org/web/20251209110121/https://www.pdqpos.com/payments/ · retrieved 2026-08-02 adversarially verified

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

payments-dual-pricing

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For payments both sites market PDQ Pay in purely qualitative terms -- "a robust payment engine", "defend your revenue with leading fraud intelligence", "lowers those costly credit-card fees" -- with no rate, no tender rules and no flow description. The hardware evidence is a counter station with an optional EMV reader, a card-swipe pinpad, a pin-pad mount and "MOBILE EMV PAYMENT" on the tablet POS; the order screen shows Gift Card, Smart Coupon, Pay and Charge Card keys and a Delivery Fee line. None of that reaches surcharging rules, dual pricing, tap-to-phone, tip adjustment or pooling, offline store-and-forward and its decline liability, house accounts, split tender, chargeback tooling, card-on-file, payout timing or multi-entity routing, none of which is mentioned anywhere on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: per-cell check (this cell carried only category boilerplate). NEW: PDQ's own 'PDQ POS Demo' video (https://www.youtube.com/watch?v=EoHF88VZ9aA, 370 s, vendor channel @PDQPOS; downloaded at 720p60, 191 scene-change frames extracted and read as images; the Manager screen footer reads 'Version: 3.5.190' and '1/27/2016', so this is a 2016-generation build): the pay screen (frames f0162-f0169) shows ONE total ('Subtotal / Del Fee / Tax / Balance $7.95'), tender keys $1/$5/$10/$20/$40, Exact Change, Check, Charge Card, Sponsor, Other and Pay Types, and a change-due screen; there is no cash-price/card-price pair. That is a 2016 build (a retired generation carries no `no`). CONTROLS over 3,997 on-disk files: 'cash discount|dual pric*|cash price|card price|non-cash adjustment' - 0 PDQ statements; POISON NAMED: G'zepps storefront notice 'Credit Card Fees Apply' (a store notice, not dual pricing), a third-party POS's App Store copy ('cash discount programs offered free'), and DoorDash's integration flag MENU_CONTAINS_ITEM_LEVEL_BASE_PRICE labelled 'Dual Pricing' (a homonym, closed in the 260th). The V2 web-ordering bundle has no cash/card price field. Retrieved 2026-09-18. adversarially verified

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

payments-surcharge-guardrails

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For payments both sites market PDQ Pay in purely qualitative terms -- "a robust payment engine", "defend your revenue with leading fraud intelligence", "lowers those costly credit-card fees" -- with no rate, no tender rules and no flow description. The hardware evidence is a counter station with an optional EMV reader, a card-swipe pinpad, a pin-pad mount and "MOBILE EMV PAYMENT" on the tablet POS; the order screen shows Gift Card, Smart Coupon, Pay and Charge Card keys and a Delivery Fee line. None of that reaches surcharging rules, dual pricing, tap-to-phone, tip adjustment or pooling, offline store-and-forward and its decline liability, house accounts, split tender, chargeback tooling, card-on-file, payout timing or multi-entity routing, none of which is mentioned anywhere on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: per-cell check (this cell carried only category boilerplate and was never checked against the leaflet that moved digital-surcharge-transparency and commercial-dual-pricing-compliant to partial/C). The 2020 PDQ DELIVERY TOOLKIT leaflet confirms a card surcharge exists: 'we also support the ability to add a credit card surcharge to the order ... We can also add a surcharge fee to the POS system, if you want to offset some of those costs as well.' But this claim is the three GUARDRAILS - automatic debit/prepaid exclusion by BIN, network-cap enforcement, per-location enable/disable - and the leaflet states none of them, so a partial would shortfall every conjunct (held shape). Also checked today: the V2 web-ordering client bundle (.cache/q331/pdq-pos/c, app.js + 52 chunks) has one store-configured fee, 'TotalPIF' with a display name from store config key 'PIF.DISPLAYNAME' defaulting to 'Fee' - a generic per-store fee, not card-conditional, with no BIN/debit/cap logic; 'surcharge', 'debit' and 'prepaid' occur 0 times in it and 'bin' only as image names (closed-bin.png/open-bin.png - POISON). On the legacy storefronts (69 tenant menus in .cache/q291-pdq/menus plus the q312 checkouts) exactly one store, G'zepps (Old Bridge NJ), prints 'Credit Card Fees Apply', and Blue Bell Pizza's cart shows 'Convenience Fee: $1.00' - store-level fee settings, but a per-store notice is not shown to be a per-location surcharge toggle. Retrieved 2026-09-18. adversarially verified

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

payments-emv-nfc

The COUNTER STATION is 'Available with an optional slim MSR, 2D barcode reader, EMV reader, and pin pad mounts', so EMV exists but as an option on one SKU rather than across all first-party terminals; the CARD SWIPE PINPAD is described only as 'Taking a variety of payment options' and the PIN PAD MOUNT as accepting 'all forms of card-based payment'. CORRECTION 2026-08-30: the shortfall recorded here -- that EMV was tied only to the counter station -- no longer holds. The vendor's POS Hardware flyer at https://ssipos.com/wp-content/uploads/2019/09/SSI-hardware-flyer-lower-res.jpg lists "MOBILE EMV PAYMENT" as a bullet of TABLET POS, and its photograph pairs the tablet with a separate handheld card device, so EMV on the handheld is a stated capability delivered by a PAIRED READER rather than by the tablet itself. Contactless, Apple Pay and Google Pay are still named nowhere on either vendor site or in the catalog - but the catalog states no device specifications at all (no model numbers, no OS, no radios), so its silence is a publication gap and is not evidence that the terminals lack NFC. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

payments-softpos-tap-to-pay

328th (APPS SLICE): BOUNDED BY AN APP-STORE PUBLISHER CENSUS. Tap to Pay on iPhone and Tap to Pay on Android can only be delivered through an app the vendor publishes to the respective store, so the vendor's complete published-app set bounds this claim. That set was enumerated three ways today: (1) Apple's lookup API on the developer id behind both PDQ apps - https://itunes.apple.com/lookup?id=1218876301&entity=software - returns the artist 'Signature System Inc' plus exactly TWO software rows, com.pdqpos.pdqposenterprise ('MY PDQ', 1.3.0) and com.pdqpos.pdqdelivery ('PDQ DT', 2.0 (74)); (2) the Google Play developer page for 'Signature Systems, Inc' lists exactly TWO packages, com.pdqpos.pdqdelivery and com.pdqpos.mypdqpos; (3) iTunes Search for 'pdq pos', 'pdqpos' and 'signature systems pdq' and Play search for 'pdqpos' return no further app by this publisher (the only other 'PDQ' results are com.paytronix.eatpdq, an unrelated chicken chain). DENOMINATOR: 2 iOS apps + 2 Android apps = the vendor's entire mobile publication. Neither is a payment-accepting app: MY PDQ is described by the vendor as '100% cloud-based reporting' and its screens are Store Totals / Voids and Promos; PDQ DT is a driver toolkit whose screens are Current Run / Previous Run(s) / Settings with an 'On Way' and 'Delivered' status pair. CONTROLS run tokenised (split on non-alphanumerics, so no substring poison) and case-insensitive over the joined 12,715-byte corpus of all three listing texts plus release notes: 'tap to pay' 0, 'tap' 0, 'contactless' 0, 'nfc' 0, 'softpos' 0, 'card reader' 0, 'reader' 0, 'chip' 0, 'emv' 0, 'pay' 0, 'tip' 0; known-positive controls on the same corpus with the same regex returned 'delivery' 26 and 'driver' 6, so the matcher works. Grade C because the corpus is store listings. Retrieved 2026-09-18. https://apps.apple.com/us/developer/signature-system-inc/id1218876301 · retrieved 2026-09-18 adversarially verified

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

payments-pay-at-table

The Multi-Revenue Center release (software revision 3.5.383) states the update 'gives operators ... the ability to place orders and accept payment for any of those operations wirelessly' and that 'Guests can place, pay for and receive orders for any restaurant on premises without the need to leave their seat', with staff taking orders 'from a wireless POS tablet'. It also adds virtual tables and tab transfer between locations. Shortfalls: CORRECTION 2026-08-30: the vendor's POS Hardware flyer at https://ssipos.com/wp-content/uploads/2019/09/SSI-hardware-flyer-lower-res.jpg lists TABLET POS as "COUNTER/WALL-MOUNT & HAND-HELD", "GREAT FOR TABLESIDE ORDERING" and "MOBILE EMV PAYMENT", so EMV at the table is stated after all -- via a paired handheld reader shown beside the tablet, not on the tablet. What remains unstated is contactless acceptance, and, and no tip prompt or check-splitting flow is documented anywhere - PDQ publishes no manual or help centre in which one could appear. https://www.globenewswire.com/news-release/2025/02/26/3033019/0/en/Signature-Systems-Inc-Announces-Slate-Of-New-Features-For-Casino-POS.html · retrieved 2026-08-09 adversarially verified

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

payments-qr-guest-pay

CLAIM: guest scans a QR on the printed check or table tent to VIEW AND PAY THE CHECK from their phone, and the payment closes the check in the POS. VERDICT: no. NEW SURFACE (331st): PDQ's NEW guest ordering client, a Next.js/Turbopack app served anonymously at https://marylandlive.pdqonlineordering.com/ (the same build fronts bossierlive/philadelphialive/pittsburghlive, i.e. the Live! casino 'brand-new mobile ordering suite' of the 2025-03-17 release, and it is a different app from the legacy 13-page WebForms pdqonlineordering.com client the 327th censused). Its chunk set was taken to a FIXPOINT: 49 static chunk/css files referenced from the seed HTML and from each other, 49 held, 0 missing (re-derived this session by re-running the reference regex over every held file), all GET, no session opened and nothing POSTed. The client calls exactly 33 '/api/online/*' endpoints and reads 56 dotted upper-case store-config keys; those two lists are the app's whole server surface. EVIDENCE: PDQ's only guest QR surface is scan-to-ORDER-and-pay: the scan key selects the store/location ('getScanKeyFromUrl', 'resolveScanTransType'), the guest builds a new order ('OrderUID:crypto.randomUUID()...OrderSource:"PDQV2"'), pays it through /api/online/orders/charge or the hosted payframe (/api/online/payments/host/prepare, /host/result, /host/mobile/prepare, /host/mobile/result), and submits it (https://marylandlive.pdqonlineordering.com/_next/static/chunks/1wv3xur2ou__5.js; https://marylandlive.pdqonlineordering.com/_next/static/chunks/17-c9ky7ir9it.js). Tenders are config-gated: 'PAGE.CHECKOUT.ACCEPTCHARGECARD', 'ACCEPTGIFTCARD', 'ACCEPTROOMCHARGE' (with /api/online/loyalty/pms/charge), 'ACCEPTCASH', 'CHARGE.MOBILEPAY.ACTIVE'. BOUND: of the 33 endpoints none retrieves a check the guest did not create - there is no check-number or QR-on-receipt lookup, and 'orders/details' takes the client's own OrderUID. So a server-rung check cannot be viewed or paid from the phone; paying for one's own new order is an ADJACENT feature (order-and-pay), not the claim. CONTROLS over all 49 files: 'pay check' 0, 'view check' 0, 'pay bill' 0, CheckID 0, TicketID 0 (poison: 'CheckNumber' = zod '$ZodCheckNumberFormat'); the prior corpora hold no pay-at-table product either (the only contactless line is the staff-held Tablet POS, 'Secure, contactless pay at curbside'). Retrieved 2026-09-18. || 334th DISCLOSED COUNTER-EVIDENCE, weighed and not decisive: a 2018 PDQ marketing slide video (YouTube P1NW60Uw3Gw, silent audio, slides read at 1080p, frames 219-223 s) lists "QR code & barcode scan-to-pay" under Integrated Payments. Grade C, seven years older than the V2 client census, and it names neither a guest viewing the check on their own phone nor the payment closing the check in the POS (scan-to-pay at the terminal of a wallet code fits the wording equally). The no stands. Retrieved 2026-09-18. https://marylandlive.pdqonlineordering.com/_next/static/chunks/1wv3xur2ou__5.js · retrieved 2026-09-18 adversarially verified

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

payments-tip-adjust

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For payments both sites market PDQ Pay in purely qualitative terms -- "a robust payment engine", "defend your revenue with leading fraud intelligence", "lowers those costly credit-card fees" -- with no rate, no tender rules and no flow description. The hardware evidence is a counter station with an optional EMV reader, a card-swipe pinpad, a pin-pad mount and "MOBILE EMV PAYMENT" on the tablet POS; the order screen shows Gift Card, Smart Coupon, Pay and Charge Card keys and a Delivery Fee line. None of that reaches surcharging rules, dual pricing, tap-to-phone, tip adjustment or pooling, offline store-and-forward and its decline liability, house accounts, split tender, chargeback tooling, card-on-file, payout timing or multi-entity routing, none of which is mentioned anywhere on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 328th: 328th (WEB/DOCUMENT SLICE): NEW SURFACE, does not settle the cell, and I am deliberately NOT proposing a partial. The recovered 2020 'PDQ DELIVERY TOOLKIT(R)' leaflet enumerates the driver-facing feature list as exactly three bullets -- 'Driver Mapping', 'Driver Order Reminders', 'Driver Receipt/Tip Reconciliation' -- and says the Toolkit spares drivers 'waiting in line at the store to enter tips'. That is a post-delivery driver tip-entry flow on a mobile app, but no mechanism, no batch/adjust window, no manager screen for unadjusted tips and no pre-auth flow is described, so on the 326th/327th holds it is an adjacent feature, not a conjunct. Corroborating third-party surface, grade D, recorded so it is not re-mined: branchapp.com's partner announcement of 1 Mar 2021 ('Branch + PDQ: Instant, Digital Tips & Mileage for Restaurant Franchises') says PDQ 'will leverage the tips and reimbursements module of the Branch EPP, allowing its customers to instantly pay their employees tips, mileage, and wages after each shift... This process is automated, so there's no additional hassle for restaurants or changes to their payroll systems needed', and quotes PDQ EVP/CTO John White. Tip PAYOUT via an external Employer Payments Platform is not tip ADJUSTMENT at the terminal, and it also means PDQ is not the payroll system of record. Retrieved 2026-09-18. || 331st: NEW SURFACE (331st): PDQ's NEW guest ordering client, a Next.js/Turbopack app served anonymously at https://marylandlive.pdqonlineordering.com/ (the same build fronts bossierlive/philadelphialive/pittsburghlive, i.e. the Live! casino 'brand-new mobile ordering suite' of the 2025-03-17 release, and it is a different app from the legacy 13-page WebForms pdqonlineordering.com client the 327th censused). Its chunk set was taken to a FIXPOINT: 49 static chunk/css files referenced from the seed HTML and from each other, 49 held, 0 missing (re-derived this session by re-running the reference regex over every held file), all GET, no session opened and nothing POSTed. The client calls exactly 33 '/api/online/*' endpoints and reads 56 dotted upper-case store-config keys; those two lists are the app's whole server surface. WHAT IT HOLDS FOR THIS CELL (does not settle it): a guest-device tip prompt exists for ONLINE orders - checkout renders 'Gratuity' presets plus 'Enter custom gratuity', gated by 'PAGE.CHECKOUT.ALLOWTIPPING_DELIVERY' / 'ALLOWTIPPING_PICKUP' (https://marylandlive.pdqonlineordering.com/_next/static/chunks/17-c9ky7ir9it.js; https://marylandlive.pdqonlineordering.com/_next/static/chunks/1wv3xur2ou__5.js). That is a pre-payment tip on the guest's own phone, not the card-present pre-auth-then-adjust flow, and no batch/adjust window or unadjusted-tips manager screen is described. Held unknown. Retrieved 2026-09-18. || 331st: 331st (slice g): the legacy storefront's rendered checkouts ALREADY ON DISK (.cache/q312/pdq-pos/pages/*-cc.txt, guest Pickup sessions of 2026-09-16, taken after the 'Credit Card' payment-method postback) were re-grepped for this cell, which nobody had done. 19 of 42 credit-card renders show a guest-entered tip field (ctl00$MasterPopups$ucNewPayment$txtTipAmount) labelled 'Tip Amount' with the sentence 'Tip for your order, you will have the option to leave tip when you pickup.' The card number goes into a hosted Datacap or Mercury frame. So the legacy online checkout has a pre-payment tip on the guest's own device, and its wording points to a second chance to tip at pickup. It does NOT show a pre-auth then tip-adjust flow on the POS, a batch or adjust window, or a manager screen for unadjusted tips, so the cell stays unknown. The storefront is not the POS terminal. Retrieved 2026-09-18. || 333rd: 333rd: NEW SURFACE, does not settle the cell. PDQ's own 'PDQ POS Demo' video (https://www.youtube.com/watch?v=EoHF88VZ9aA, 370 s, vendor channel @PDQPOS; downloaded at 720p60, 191 scene-change frames extracted and read as images; the Manager screen footer reads 'Version: 3.5.190' and '1/27/2016', so this is a 2016-generation build). Two tip-related screens appear. (1) The driver cash-out grid ('Click on driver's name to select'; frames f0332-f0355) has columns 'ID# / Name / Qty / Total / -Drops / +Banks / -DMR / -Paid Del / -Chg Tips / Balance', i.e. CARD ('Chg') tips are netted out of each driver's cash owed at cash-out, so tip amounts are attached to closed card checks before settlement. (2) The recall/order-list screen's bottom bar has a 'Tip Out' button beside Pickup/Delivery/For Here/InShop/All Open/Web/Table/Search/More (frame f0148); it is never pressed in the video, so what it opens is unseen. Neither shows a pre-auth then adjust flow, an adjust/batch window or a manager list of unadjusted tips, so the cell stays unknown. The 'PDQ POS Manager' function screen of the same build (frame f0329: Register/Driver/Server Functions, Register Payouts, Driver/Server Bank-Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, AM Deposit, Quick X, Z Report) has a 'Charge Card' function whose contents are not shown. Retrieved 2026-09-18. || 334th: 334th: NEW SURFACES, do not settle. (1) 'PDQ Delivery Tool Kit Explainer Video' (https://www.youtube.com/watch?v=LCeKw8MiRQQ, 133 s, Rebel Hill Productions for PDQ; no caption track, so transcribed locally with faster-whisper base.en) says only 'Drivers: detailed route mapping, facilitate contactless delivery, item reminders for order accuracy, easy receipt, tip reconciliation'. That is the same driver-side reconciliation the 328th held as adjacent. (2) PDQ's own silent slide video '5 Profit Generating Essentials for POS Systems' (https://www.youtube.com/watch?v=P1NW60Uw3Gw, 366 s, uploaded 2018-04-24, presenter Larry Fiel, VP of Marketing; the audio track is digitally silent, max amplitude 0.0, so every prior caption/ASR pass got nothing from it; downloaded at 1080p, 376 scene-change frames extracted and read as contact sheets). Its payments slide lists 'Integrated Payments: Credit cards; Gift cards; e-Wallet payments (Apple/Android/Samsung Pay); QR code & barcode scan-to-pay'. No slide covers tip adjust, pre-auth, an adjust window or unadjusted tips. Retrieved 2026-09-18. adversarially verified

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

payments-tip-pooling

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For payments both sites market PDQ Pay in purely qualitative terms -- "a robust payment engine", "defend your revenue with leading fraud intelligence", "lowers those costly credit-card fees" -- with no rate, no tender rules and no flow description. The hardware evidence is a counter station with an optional EMV reader, a card-swipe pinpad, a pin-pad mount and "MOBILE EMV PAYMENT" on the tablet POS; the order screen shows Gift Card, Smart Coupon, Pay and Charge Card keys and a Delivery Fee line. None of that reaches surcharging rules, dual pricing, tap-to-phone, tip adjustment or pooling, offline store-and-forward and its decline liability, house accounts, split tender, chargeback tooling, card-on-file, payout timing or multi-entity routing, none of which is mentioned anywhere on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: per-cell check (this cell carried only category boilerplate). NEW: PDQ's own 'PDQ POS Demo' video (https://www.youtube.com/watch?v=EoHF88VZ9aA, 370 s, vendor channel @PDQPOS; downloaded at 720p60, 191 scene-change frames extracted and read as images; the Manager screen footer reads 'Version: 3.5.190' and '1/27/2016', so this is a 2016-generation build) shows a 'Tip Out' button on the recall/order-list screen (frame f0148) that is never pressed, and a driver cash-out grid netting '-Chg Tips' per driver (frames f0332-f0355). PDQ's 2016 Product Feature Summary PDF (Wayback, already on disk at .cache/q324/pdq-pos/pdf/featuresummary.txt) lists 'Sales & gratuity by employee' and 'Tip reporting' under reports. That is per-employee tip REPORTING and a possible tip-out function; nothing states pooling or distribution rules (hours, sales, role %, points) or a payroll export of allocations, and 'tip pool|tip share|tip-out|gratuity distribution' are 0 PDQ documents across 3,997 on-disk files (the 8 hits are Branch's site navigation 'Tip Pooling' - a third party's product - and agent scratch). Held unknown: a 2016 build's unlabelled button is not a pooling engine. Retrieved 2026-09-18. adversarially verified

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

payments-offline-store-and-forward

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For payments both sites market PDQ Pay in purely qualitative terms -- "a robust payment engine", "defend your revenue with leading fraud intelligence", "lowers those costly credit-card fees" -- with no rate, no tender rules and no flow description. The hardware evidence is a counter station with an optional EMV reader, a card-swipe pinpad, a pin-pad mount and "MOBILE EMV PAYMENT" on the tablet POS; the order screen shows Gift Card, Smart Coupon, Pay and Charge Card keys and a Delivery Fee line. None of that reaches surcharging rules, dual pricing, tap-to-phone, tip adjustment or pooling, offline store-and-forward and its decline liability, house accounts, split tender, chargeback tooling, card-on-file, payout timing or multi-entity routing, none of which is mentioned anywhere on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: MERGE HOLD (proposed partial/C, held unknown): same evidence as reliability-offline-card-auth: dial-backup authorises online over a phone line; no store-and-forward and no offline limits, so no conjunct is met. PROPOSAL AS WRITTEN: CLAIM: card payments captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. VERDICT: partial. EVIDENCE: the unlinked pci.pdqpos.com installer PDF set (recovered via the Wayback CDX index of pci.pdqpos.com, not linked from any live page) requires every store to run a dedicated analog line so that 'you will not lose sales if the internet goes down and will not need to write down credit card numbers' (https://web.archive.org/web/20150714004622/http://pci.pdqpos.com/Downloads/PDQ%20POS-Preparing%20For%20Your%20Security%20Package.pdf). Card acceptance therefore survives a WAN outage. SHORTFALLS (named): this is dial-backup live authorisation, NOT store-and-forward; and neither document - nor any other PDQ surface read this session - mentions a per-transaction offline ceiling, a cumulative offline ceiling, or any operator-configurable offline limit. The tokens 'store and forward', 'store-and-forward', 'floor limit' and 'offline limit' are zero across the 81-document PDQ corpus. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE, does not settle the cell. Card authorisation in PDQ runs through Datacap NETePay, not PDQ code: Datacap's 2016 post says PDQ 'has thousands of EMV-enabled merchants utilizing Datacap's NETePay software' and quotes PDQ: 'By harnessing the POS-isolating power of NETePay, our acclaimed PDQ POS is insulated from all exposure to card data' (https://datacapsystems.com/blog/2016/03/01/2016-3-1-pdq-signature-systems-and-datacap-partner-for-us-emv-transition, grade D). Any store-and-forward would therefore be a NETePay/processor setting, which PDQ does not publish; the retired PDQ PAY pages (Wayback /payments/ 2025-12-09 and /pdq-pay/ 2024-07-16, never read before) say nothing about offline cards. 'store-and-forward', 'SAF', 'floor limit' and 'offline limit/transaction/mode/payment' are 0 PDQ documents across 3,459 on-disk documents. Retrieved 2026-09-18. adversarially verified

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

payments-offline-decline-liability

333rd: CLAIM (documentation-shaped, conjunctive): the vendor PUBLICLY documents who bears the loss when a stored offline transaction declines on reconnect, AND surfaces a post-reconnect report of failed offline payments. VERDICT: no, grade C - the first conjunct is a publication test and it fails on a bounded census. This is the same census shape already merged on this record for the sibling reliability-offline-decline-liability (no/C, 331st), labor-offline-time-punch (no/C, 332nd, owner ruling: documentation-shaped claims take a `no` from a publication census) and payments-payout-timing (no/C, 332nd); this cell carried only the 2026-08-30 category boilerplate and had never been checked against that census. PUBLICATION CENSUS (333rd, re-derived today with curl + browser UA, not inherited): www.pdqpos.com homepage 200, 110,961 bytes decompressed (same as the 326th/331st/332nd copies); legal set exactly termsofuse.aspx (-> /termsofuse, 81,365 B), privacypolicy.aspx (59,266 B), smsprivacypolicy.aspx (52,924 B); /termsofsale, /support and a nonsense control /zzz-nope-333 all return the same 1,923-1,928-byte not-found page; /payments now redirects to the homepage anchor /#pdqpay; pdqpay.com still redirects to a domain-for-sale page (domains.atom.com/lpd/name/PdqPay.com); ssipos.com WP REST X-WP-Total pages 8, posts 5, media 216 (unchanged). PDQ publishes no KB, manual, help centre or developer portal (certspotter host set of the 332nd: help = BeyondTrust remote-support portal, pci = login, ftp = Cerberus login; none a documentation host). NEW SURFACE ALSO CHECKED: PDQ's YouTube channel, 43 uploads (flat-playlist census; 0 shorts, 0 streams), captions now held for 24 (4 new today; the rest are captions-disabled or were 429-throttled), and PDQ's own 'PDQ POS Demo' video (https://www.youtube.com/watch?v=EoHF88VZ9aA, 370 s, vendor channel @PDQPOS; downloaded at 720p60, 191 scene-change frames extracted and read as images; the Manager screen footer reads 'Version: 3.5.190' and '1/27/2016', so this is a 2016-generation build): the pay screen offers $1/$5/$10/$20/$40, Exact Change, Check, Charge Card, Sponsor, Other and Pay Types, and no frame shows an offline-card state or report. CONTROLS (tokenised, word-boundary, case-insensitive, over 3,997 files in 20 on-disk pdq corpora: .cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, every q331 and q332 pdq-pos slug, and today's fetches incl. the new transcripts; KNOWN POSITIVES 'surcharg*' 25 docs and 'time clock' 22 docs fire, so the regexes work): 'declined offline|offline declin*|declin* after|on reconnect' 0 documents; 'store-and-forward|SAF' 11 files, 0 PDQ statements - POISON NAMED: 'SAF' matches compressed byte streams inside PDFs (SSI 5-Technology-Mistakes, the RSPA award PDF), a base64 SHA1 digest in an APK MANIFEST.MF ('saf/AL47...'), and our own agent scratch (term lists, prior notes); 'floor limit|offline limit/cap' 3 files, all agent scratch; 'offline (card|credit|payment|transaction|mode|approval)' 2 files, both other publishers' App Store listings; 'declin(e|ed|es|ing)' 6 files, none PDQ ('decline in cash transactions' on Branch's blog, a BoldSign listing, a campus 'declining balance'); 'failed payment/transaction report|offline report' 1 file - the V2 web-ordering client's online error string 'Payment authorization failed' (an ONLINE card-not-present error, not an offline report). No PDQ document names who bears an offline-decline loss or any offline report. Retrieved 2026-09-18. https://www.pdqpos.com/ · retrieved 2026-09-18 adversarially verified

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

payments-gift-cards

First-party evidence the original pass missed: PDQ's own 'PDQ POS Feature Overview' enumerates 'Built-in gift card processing' under POS capabilities, 'Check gift card balance' as a named POS-screen function, and 'Multiple payment options (cash, credit, gift, coupons, etc.)' under Payment. That establishes first-party gift cards with at-POS balance lookup. Shortfall: the claim also requires redemption across every location in the group and through the online-ordering channel, and neither is stated anywhere — the same document lists multi-store functions only for inventory transfer and reporting. Further caveat: this PDF now 404s on pdqpos.com and was retrieved from a 2019 Internet Archive capture of a 2016 upload, so it is dated vendor collateral, not current documentation. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-08-02 adversarially verified

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

payments-house-accounts

328th (APPS SLICE): NEW SURFACE that falsifies the shared category note's sentence 'house accounts ... none of which is mentioned anywhere on either host'. The vendor's own App Store SCREENSHOTS of MY PDQ (the myPDQPOS enterprise reporting client) were downloaded at full resolution and read. The iPad 'Store Totals' screen carries a 'Misc Summary' block whose closed line list is, verbatim and in order: 'Paid Orders (0): $0.00 / Open Orders (0): $0.00 / Charges (0): $0.00 / House Accounts (0): $0.00 / Gift Cards (0): $0.00 / Emp Meals (0): $0.00 / Mgr Meals (0): $0.00 / Discounts (0): $0.00 / Promos (0): $0.00 / Voids (0): $0.00' (https://is1-ssl.mzstatic.com/image/thumb/Purple113/v4/53/31/ff/5331ffc1-6186-a98e-da75-6e807dabfd40/pr_source.png/1000x0w.png). So PDQ POS does carry House Accounts as a first-class settlement category, counted and totalled separately from Charges and Gift Cards in the enterprise day-part report. PARTIAL, not yes: the claim's other conjuncts - per-account credit limits, a running per-account balance, and periodic statement or invoice generation - are not shown by a count-and-total report line, and an app-store screenshot is grade C. Retrieved 2026-09-18. https://apps.apple.com/us/app/my-pdq/id1218876302 · retrieved 2026-09-18 adversarially verified

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

payments-split-tender

CLAIM: one check settled with MULTIPLE TENDERS and split by seat, item, even shares or arbitrary amount, with no hard cap below eight ways. VERDICT: partial. EVIDENCE: the 2016 Feature Overview lists 'Combine and split orders' with the indented sub-bullet 'SPLIT GUEST, CHECK AND ITEM', plus 'Multiple payment options' and 'Custom tender options' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). The retired ProTable module page adds the timing and the per-party rendering: 'ProTable allows the wait staff to SPLIT TICKETS AT ANYTIME BEFORE, DURING, OR AFTER TAKING THE ORDER. Simply choose a seat at the table and start entering the order. When the customers are ready to pay, EACH CHECK WILL BE DISPLAYED ON THE PROTABLE SCREEN.' (https://web.archive.org/web/20041208124200/http://www.pdqpos.com/table.htm). Splitting by guest and by item is therefore established, as is a multi-tender palette. SHORTFALLS (named): nothing states that a SINGLE check can be settled with more than one tender (the multi-tender bullets enumerate the tender TYPES available, which is a different thing); even-share and arbitrary-amount splits are not named; and no split-way cap is published. Retrieved 2026-09-18. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-18 adversarially verified

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

payments-refund-void-controls

Manager override is a named, routine flow in the product: the catalog's FINGERPRINT READER entry says 'save precious seconds at every login and manager override', and the homepage lists 'secure fingerprint POS log-in' among the system's essentials, so approvals are authenticated per individual. What the claim additionally requires - an immutable audit log identifying the approver, and role gating spelled out for voids, refunds, discounts and no-sales specifically - is published nowhere; the catalog is a hardware marketing piece with no software content, and PDQ operates no documentation site, so this is a publication gap rather than a demonstrated absence. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

payments-chargeback-tooling

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For payments both sites market PDQ Pay in purely qualitative terms -- "a robust payment engine", "defend your revenue with leading fraud intelligence", "lowers those costly credit-card fees" -- with no rate, no tender rules and no flow description. The hardware evidence is a counter station with an optional EMV reader, a card-swipe pinpad, a pin-pad mount and "MOBILE EMV PAYMENT" on the tablet POS; the order screen shows Gift Card, Smart Coupon, Pay and Charge Card keys and a Delivery Fee line. None of that reaches surcharging rules, dual pricing, tap-to-phone, tip adjustment or pooling, offline store-and-forward and its decline liability, house accounts, split tender, chargeback tooling, card-on-file, payout timing or multi-entity routing, none of which is mentioned anywhere on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: NEW SURFACE, does not settle the cell. The only chargeback sentence PDQ publishes is a prevention claim, not a tooling one: its one-stop-shop article says the platform 'has also incorporated secure and compliant digital modes of payments, INCLUDING MOBILE EMV FOR CHARGEBACK ELIMINATION' (https://web.archive.org/web/20220627152647/https://www.pdqpos.com/a-one-stop-shop-for-restaurant-technology/); the PDQ Pay page offers only 'Reduce risks, protect payment information and defend your revenue with leading fraud intelligence' (https://pdqpos.com/). EMV liability shift is not a dispute dashboard: no list of open disputes, no evidence-submission flow, and no assembly of the POS transaction record for representment appears anywhere. 'Chargeback' occurs exactly twice in the 81-document corpus, in two snapshots of that same article, and never in any other sense. Held unknown. Retrieved 2026-09-18. adversarially verified

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

payments-card-on-file

CLAIM: Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders and in-store, with no PAN stored by the merchant. VERDICT partial/C. MET (online ordering, entered through a hosted gateway): the checkout payment popup of PDQ's shared multi-tenant online ordering (*.pdqonlineordering.com, CheckOut.aspx) renders div ctl00_MasterPopups_ucNewPayment_divSaveCard with checkbox chkCreditSave, ticked by default, labelled "Save card on file for future purchases." The checkout also carries a stored-card panel (pnlStoredCC / lblStoredCardsMain, on 43 of 45 checkouts), which for a guest shows only the header 'Payment Options'. The card number is entered inside a third-party hosted frame, not a PDQ form field: Datacap hosted web token (token.dcap.com) on 21 of 45 tenants, Mercury HostedCheckout (hc.mercurypay.com) on 10 of 45. The PDQ page has no PAN input of its own. The label appears on 33 of 45 tenants that reached CheckOut.aspx (69 probed, 49 reached Menu.aspx, 45 reached checkout). The other 12: 5 credit-card-only tenants stop at 'Invalid Contact Name' before the panel renders, 4 credit-card-only tenants render no panel, and 3 have no payment dropdown. HOW REACHED: guest Pickup session on 2026-09-16 (.cache/q312/pdq-pos/seam.mjs): Order Now, Pickup, Start Order, cart one item, 'Proceed to Checkout >', then the 'Credit Card' option postback on the payment-method dropdown. Nothing was typed in and nothing was submitted. The label is NOT in the anonymous title page, the menu or the first checkout HTML. It appears only after the Credit Card postback. Without a session, CheckOut.aspx redirects (302) to MessagePage.aspx?SessionEnded=True, so the cited tenant root is only the entry point. The verifier re-drove hgchesterbrookpizza, passariellos and slicespizza, and the label and gateway were present on all three. This overturns the earlier note saying there was 'no save-card option': that pass read only the registration form. SHORT: (1) reuse across phone and in-store orders, the claim's cross-channel limb, is not shown by any page. (2) Tokenisation is inferred from the hosted-gateway architecture. No page documents where the saved credential lives or that the merchant never holds the PAN, and a saved card was never observed being reused, because no account was created and nothing was submitted. (3) Differentiator grade floor: observing the live product is grade C, so yes is not available. https://hgchesterbrookpizza.pdqonlineordering.com/ · retrieved 2026-09-16 adversarially verified

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

payments-payout-timing

332nd: CLAIM (conjunctive): the vendor PUBLISHES its deposit schedule AND offers a next-day or same-day/instant funding option. VERDICT: no, grade C - the first conjunct is a publication test and it fails on a bounded census (the same shape as microworks-prism's merged no/C and agilysys's no/B on this cell). PUBLICATION CENSUS (332nd, re-derived today with curl + browser UA, not inherited): www.pdqpos.com homepage 200 / 110,961 bytes (same byte count as the 326th and 331st copies); its legal set is exactly termsofuse.aspx (200, 81,365 B), privacypolicy.aspx (200, 59,266 B) and smsprivacypolicy.aspx (200, 52,924 B); /termsofsale 404 (1,927 B) against a nonsense-path control /zzz-nope-332 404 (1,928 B), so the merchant 'Terms of Sale' the Terms of Use incorporates by reference is not published; pdqpay.com redirects to a domain-for-sale page (domains.atom.com/lpd/name/PdqPay.com); ssipos.com WP REST pages X-WP-Total 8, posts 5 (unchanged). The retired WordPress pdqpos.com's own payments pages, which no prior pass had opened, were read from Wayback: /payments/ (12 captures 2024-10-14..2025-12-09, latest https://web.archive.org/web/20251209110121id_/https://www.pdqpos.com/payments/) and /pdq-pay/ (2024-07-16): each is ~830 words of qualitative 'PDQ PAY' copy ('Secure, innovative payment processing', 'leading fraud intelligence', 'accepting both traditional and alternative payment types') with no rate, no schedule and no agreement. CONTROLS (tokenised, word-boundary, case-insensitive, over 3,459 text documents in 18 on-disk pdq corpora: .cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, q331/pdq-pos/f and this session's fetches; KNOWN-POSITIVE controls 'surcharg*' 19 docs and 'terminat*' 94 docs fire, so the regexes work): 'deposit/funding/settlement schedule|timing' 0 documents; 'next-day/same-day/instant/rapid/fast funding|deposit|payout|settlement' 0 documents; 'funding|funded|payout(s)' 46 documents and 'deposit(s)' 25, every one resolving to another sense - POISON NAMED: 'Monitor Payouts From Each Location' and 'AM/PM deposits are made' are CASH-DRAWER payouts and bank-bag deposits in PDQ's mobile-reporting page, 'easy to payout' is a separate-checks line, and the rest are Branch/DailyPay (third-party wage and tip payout) pages. The only PDQ sentence on merchant funding (2020 Delivery Toolkit leaflet, already in the record) says 'we do not hold any of your money and funds are released quickly by our credit card processor' - it delegates funding to the processor and names no schedule and no next-day option. NEW CONTEXT (third party, grade D, corroboration only): Datacap's 2016 partnership post says PDQ 'now supports US EMV through virtually all US processors via Datacap's ... NETePay' and its payments integration 'supports all processors in the US' (https://datacapsystems.com/blog/2016/03/01/2016-3-1-pdq-signature-systems-and-datacap-partner-for-us-emv-transition, WP post 944), i.e. PDQ is processor-agnostic and funding timing sits with whichever processor the merchant contracts. Nothing PDQ publishes offers a funding speed. Retrieved 2026-09-18. https://www.pdqpos.com/ · retrieved 2026-09-18 adversarially verified

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

payments-multi-entity-routing

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For payments both sites market PDQ Pay in purely qualitative terms -- "a robust payment engine", "defend your revenue with leading fraud intelligence", "lowers those costly credit-card fees" -- with no rate, no tender rules and no flow description. The hardware evidence is a counter station with an optional EMV reader, a card-swipe pinpad, a pin-pad mount and "MOBILE EMV PAYMENT" on the tablet POS; the order screen shows Gift Card, Smart Coupon, Pay and Charge Card keys and a Delivery Fee line. None of that reaches surcharging rules, dual pricing, tap-to-phone, tip adjustment or pooling, offline store-and-forward and its decline liability, house accounts, split tender, chargeback tooling, card-on-file, payout timing or multi-entity routing, none of which is mentioned anywhere on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd: NEW SURFACE, does not settle the cell. Datacap's 2016 partnership post (WP post 944, quoting PDQ marketing director Larry Fiel) establishes PDQ's payment layer: PDQ 'supports US EMV through virtually all US processors via Datacap's ... NETePay' and 'By harnessing the POS-isolating power of NETePay, our acclaimed PDQ POS is insulated from all exposure to card data'. So settlement is per the merchant's own processor account, and per-store merchant accounts are the natural shape - but nothing says one PDQ account routes funds to different bank accounts per location/entity under unified reporting, and 'split settlement', 'merchant ID(s)', 'MID(s)', 'separate bank account(s)' and 'multiple merchant accounts' are 0 PDQ documents across 3,459 on-disk documents (the 'MID' hits are YouTube 'NO MID-ROLL ADS' titles and a WP mime list 'mid,midi' - POISON). Third-party host, grade D. Retrieved 2026-09-18. adversarially verified

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

payments-p2pe-pci4

CLAIM: the vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance or P2PE listing available to merchants on request. The availability-on-request half of the second conjunct is not testable from outside and is not asserted on here; what is testable is whether any current 4.x attestation or validated P2PE listing exists, and it does not. A search of the PCI SSC validated P2PE solutions listing surfaced no Signature Systems entry, which is recorded as a search result and not as a census of that registry. On the estate, Attestation of Compliance 0, AOC 0, stem attest 0, ROC 0, QSA 0, report on compliance 0, 4.0 0, 4.0.1 0, v4 0, version 4 0, 4.x 0. Disclosure that narrows an earlier absolute: on the estate the controls read P2PE 0, point-to-point 0, point 2 point 0, Point-2-Point 0, stem encrypt 0, stem tokeni 0, vault 0, PA-DSS 0, SSF 0, hosted payment 0 and hosted field 0, while SAQ returns 12 and no SAQ level is ever named, and EMV 16, pinpad 2 and swipe 4 show the corpus does carry payment-hardware vocabulary where it applies. Off the estate, however, a 2010-11-16 PRNewswire release with Payment Processing Inc describes PPI's Point-2-Point Cardholder Data Security Program and a Managed Payer Data facility that stores card data on PPI's servers, and calls PDQ POS a validated Payment Application Data Security Standard (PA-DSS) application. A prior note saying tokenization is never mentioned in any PDQ material was therefore too absolute, and the vendor's own spelling is Point-2-Point, which a P2PE control does not match. That artefact does not carry this cell: PA-DSS was retired 2022-10-28, it is not a validated P2PE listing, it names no SAQ, and it is sixteen years old. Scope, stated so the company and the product are not conflated: the vendor itself makes the certification company-scoped. The ssipos.com home page says PCI DSS Level 1 Compliant Service Provider, and Signature Systems' own 2022-12 article advises buyers to select a provider that is PCI DSS compliant as a company. A service-provider compliance status is not a product attestation, and it is not used here to settle any product-scoped conjunct. Estate bounding, re-probed independently rather than inherited: pdqsecurity.com, pdqtek.com and pdqoo.com all 301 to the pdqpos.com marketing home page (pdqsecurity.com and pdqoo.com direct to https://pdqpos.com on both http and https; pdqtek.com via an http://pdqpos.com hop), and a deep path on pdqsecurity.com and on pdqtek.com returns a zero-length 404, so none of the three serves any content of its own; the www. host of each does not resolve, as does a deliberately fabricated control host, so a DNS failure is distinguishable from a redirect. The pdqpos.com Terms of Use names those four pdq domains but does not name ssipos.com, so the Terms are not the estate enumeration. The reachable published estate is two hosts: pdqpos.com, which is one marketing home page, two ProjectDetail pages, four newsarticles pages, three legal pages and the 2025 Product Catalog PDF, with no robots.txt and no sitemap.xml and no /security, /pdqsecurity, /trust or /compliance path; and ssipos.com, a WordPress site whose REST manifest is strictly larger than its sitemap. A fabricated path 404s hard on both hosts, but pdqpos.com also has a soft-200 shape -- https://www.pdqpos.com/newsarticles returns HTTP 200 carrying a Page Not Found body -- so path probes on that host must be read from the body and not the status. Vintage, and the newer-surface hunt that tests it: the brochure is dated 2022-05-19, PCI DSS v4.0.1 was published June 2024 and its future-dated requirements became enforceable 31 March 2025, so this document cannot carry a 4.x statement as a matter of chronology. That argument is only as good as the search for a newer surface, and that search corrects an earlier assertion that the newest security-bearing artefact is the 2025 Product Catalog: Signature Systems publishes press releases through GlobeNewswire and pdqpos.com links only four of them. The newest, 2026-08-19, together with the 2026-03-30 and 2025-02-26 releases, carries the same corporate boilerplate whose only security clause is the versionless phrase full PCI DSS compliance, with no SOC 2, no ISO 27001, no version number, no attestation, no P2PE and no tokenization. ssipos.com has no /trust/, /compliance/ or /security/ page, all three 404, and its media library ends at 2023-11-13. As of 2026-09-15 no 2024-2026 compliance surface exists anywhere on or off the estate. Controls were run tokenised with both word boundaries, and as a left-boundary stem where morphology matters, over 76 document-instruments -- 13 PDFs in two extractions each, the brochure in three, 24 HTML documents held both raw and tag-stripped after HTML-comment removal, and the media census -- which is 37 distinct documents. Positive controls on the same run: the 1937, SSI 845, POS 683, security 260, PCI 136, DSS 51. Poison published: whitespace-squashed substring matching is unusable on its own -- SCA 161 (a substring of casino, Cordish and landscape), ROC 116, RTO 113, RPO 98, v4 91, SLA 53, QSA 20, AOC 11, MFA 6, every one of which tokenises to 0. Two traps tokenisation does not cure: break returns 146 word-boundary hits of which 144 are CSS line-break and word-break declarations in inline styles on the ssipos.com podcasts page, which also carries 144 of the 148 iframe hits; and the bare word token returns 80 hits, every one an ASP.NET __RequestVerificationToken or cookie-consent token in raw pdqpos.com markup and none of them payment tokenization, so only the stem tokeni, which reads 0, is a usable instrument for this vendor. Extraction instrument: the brochure was re-extracted three ways and the invariance reproduced -- pdftotext -layout, pdftotext plain and pdftotext -raw yield an identical token vocabulary with an empty symmetric difference in all six pairwise directions, an identical single-letter-token count of 15 in all three, and five phrase controls present in all three, so on this multi-column document neither the intra-word-space fault nor the adjacent-column-interleave fault fired. The vocabulary size is a reader artefact and is deliberately not published as a figure: one reader counts 322 tokens and another 312 over the same three files; the invariance is the control. Media census and declared residue: ssipos.com wp-json media X-WP-Total is 216, and the per_page=100 HTTP 500 sits on a record and moves with the sort key, so 212 records were recovered by unioning eight orderings. The residue of 4 was then closed by mime filtering rather than by inference: X-WP-Total is 201 for media_type=image (115 png plus 86 jpeg), 2 for video, 13 for media_type=application and 12 for mime_type=application/pdf, and 201+2+13 is exactly 216, so the type census is closed; mime_type=application/pdf&per_page=100 returns all twelve PDFs in a single page with no 500, which makes the twelve-PDF corpus a census rather than a floor. The four unreachable records are therefore two png, one jpeg and one non-PDF application/* file of unknown type, and that single non-PDF file is the declared hole. X-WP-Total for after=2023-12-01 is 0, which bounds the whole library, residue included, to on or before 2023-11-13. https://ssipos.com/wp-content/uploads/2022/05/SSI-Security.pdf · retrieved 2026-09-15 adversarially verified

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

kitchen-station-routing

CLAIM: items route to specific KDS stations by item, category, order type or revenue center, rules configurable per location without vendor involvement. VERDICT: partial. EVIDENCE: PDQ's Quick Service Module sheet (quick_svc.pdf, Signature Systems, 66 Richboro Rd Newtown PA - a retired 2004 document, archived 2004-12-08) states under 'Routing Tickets': 'PDQ can route tickets to 10 different make areas. PDQ tickets use whole words in legible type minimizing errors at the make table' (https://web.archive.org/web/20041208204758/http://www.pdqpos.com/quick_svc.pdf). The 2016 Feature Overview independently lists 'Kitchen printers' and 'Kitchen video systems' among supported peripherals and 'Sales by destinations' among reports (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). So multi-station routing with a bounded fan-out of 10 make areas is established. SHORTFALLS (named): the ROUTING KEY is not stated (no mention of routing by item, category, order type or revenue center); nothing says the rules are operator-editable per location rather than set by PDQ at install; and the only document that quantifies it is a retired 2004 module sheet, which per policy can carry a positive no higher than partial. Retrieved 2026-09-17. https://web.archive.org/web/20041208204758/http://www.pdqpos.com/quick_svc.pdf · retrieved 2026-09-17 adversarially verified

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

kitchen-expo-consolidation

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice c): NEW SURFACE - the full 1080p video stream of PDQ's own 'PDQ VDU (KDS)' demo (youtube.com/watch?v=J8n_rhS4QFk, vendor channel @PDQPOS, uploaded 2020-05-18, 101 s, 1920x1080), downloaded anonymously and decoded frame by frame (62 distinct frames at 1 s steps, plus 0.5 s crops of the setup screens), read as images. Prior passes held only YouTube's three auto-thumbnails and a 160x90 storyboard. Vendor-authored product demo = grade C. WHAT IT HOLDS FOR THIS CELL: the VDU is multi-display with an explicit chain: each display has a 'Route Position' and a 'Stage Setup' tab, the setup header has 'Manage Stages', and a per-display toggle reads 'Combine Transactions By Order'. Three displays are configured in the demo, but only one is ever shown, and no frame shows an expo view, a consolidated multi-station order, or a rule that the order completes only when every station has bumped. Stages and route positions are the plumbing such a feature would use, not the feature. Held unknown. Retrieved 2026-09-18. adversarially verified

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

kitchen-course-firing

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice c): NEW SURFACE, does not settle the cell. Full-resolution frames of PDQ's own videos 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 1080p; 190 distinct frames extracted, a sample read) and 'PDQ POS Overview (no audio)' (CAtnMz-w59k, 720p, 59 frames, all read), downloaded anonymously and read as images. A table-service order screen (WOb74p-EcYI at 92 s) reads 'Section: MAIN / Angela Dipaolo / Tbl:4 Guests:2 3:20 PM / Order # 13 / In At 3:20 PM' with controls 'Sep Seats', 'Cancel', 'Print Order', 'Smart Coupon', 'Gift Card', 'Special Instructions', 'Send', 'Pay': seat separation and send, but no course, hold or fire control. The order-completion screen (CAtnMz-w59k at 27 s) has a 'Delay Order' button, which delays a WHOLE order and is not coursing. Held unknown: a screen without a course button in a marketing montage is not a census of the FSR module. Retrieved 2026-09-18. adversarially verified

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

kitchen-prep-time-pacing

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice c): NEW SURFACE - the full 1080p video stream of PDQ's own 'PDQ VDU (KDS)' demo (youtube.com/watch?v=J8n_rhS4QFk, vendor channel @PDQPOS, uploaded 2020-05-18, 101 s, 1920x1080), downloaded anonymously and decoded frame by frame (62 distinct frames at 1 s steps, plus 0.5 s crops of the setup screens), read as images. Prior passes held only YouTube's three auto-thumbnails and a 160x90 storyboard. Vendor-authored product demo = grade C. WHAT IT HOLDS FOR THIS CELL: the per-display VDU editor has toggles 'Show Prep Time' and 'Quick Bump Prep Time' and numeric 'Pre-Prep Warning' / 'Post-Prep Warning' fields, so the KDS carries a prep time. It does not show whether prep time is set PER ITEM, and no frame shows items being held back or staggered so an order finishes together (every item of a new ticket appears at once in the demo). Held unknown: a prep-time display is adjacent to, not part of, cook-time staggering. Retrieved 2026-09-18. adversarially verified

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

kitchen-order-throttling

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice c): NEW SURFACES, none settles the cell. Read as images (frames at 0.5 s steps, distinct frames kept): PDQ's own 'PDQ POS Demo' (youtube.com/watch?v=EoHF88VZ9aA, 2016, 369 s, 191 frames, plus its English caption track), 'PDQ POS Overview' (YUUejVp2lhY), 'Learn More About PDQ POS' (PWqryUhZN4E), 'PDQ POS' (xvVu3cVQl8I), the current www.pdqpos.com hero video (https://www.pdqpos.com/assets/video/PDQ.mp4, live 200, 60 s), the 'PDQ POS Slide Show' (T2hV0YmVBjE, second vendor channel @pdqpos1959), the SOFO Expo talk (z5vXjbqGtMo, talking head, captions 429-refused), 'The Chef's Kitchen' TV segment (hMgf61pAV7U), and two 2023 SSI-commissioned promos by Rebel Hill Productions for the Parx Casino rollout ('PDQ POS Training' 5P5jYoKlOLw, 'PDQ POS Installation' J1GdSoIMGC4, both ending 'Learn more at ssipos.com'). Also found: an unlinked Vimeo account (vimeo.com/pdqpos) embedded 8 videos on the 2022 /images-videos/ page (Wayback 20220627145426); 3 are public (Self-service Drive-thru, Integrated Digital Menu Boards, About PDQ Signature Systems - YouTube duplicates) and 5 answer 'Sorry' (private/removed) even with the pdqpos.com referer. A third channel, @signaturesystems1, holds 8 testimonials of 16-37 s. Not one frame across these shows a KDS/VDU software screen; the only kitchen-display frames are hardware (Installation promo 43-50 s: monitors mounted over the Parx line showing a Windows desktop, with a bump bar beneath). WHAT IT ADDS FOR THIS CELL (first per-cell check; the prior note is the 2026-08-30 category boilerplate): the 2016 POS demo's order-type screen quotes FIXED times ('Delivery ... Ready In 35 Minutes', 'Pickup ... Ready In 20 Minutes', EoHF88VZ9aA at 139 s), and its 'Delay Order' screen offers a clock time and quick delays of 15/30/45/60/90 minutes (YUUejVp2lhY at 45-48 s and 93-96 s; 'Delay Order For 3/21/2017 5:00:00 PM'), which is a MANUAL future-time hold, not load-based pacing. Re-grep of the V2 Next.js ordering client already on disk (.cache/q331/pdq-pos/c/chunks, 52 files + app.js): the quoted time is a store-config string - keys 'PAGE.ORDERCOMPLETE.PICKUPTIME' (default "20") and 'PAGE.ORDERCOMPLETE.DELIVERYTIMEMESSAGE' ('Your order will be delivered within the next {ReadyTime} minutes.'). Tokenised, word-boundary controls over those chunks: throttl*, capacity, busy*, maxOrders*, leadTime*, prepTime* - zero product hits. POISON NAMED: 'pacing' matches Tailwind 'spacing' hundreds of times, 'Throttled' is a React scheduler label and Leaflet's throttle util, 'pause'/'paused' is TanStack Query fetchStatus. So neither client shows load-based throttling, but one ordering client plus two demos is not a census of the POS/online-ordering back office (throttling would be a server-side setting). Held unknown. Retrieved 2026-09-18. adversarially verified

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

kitchen-channel-pause-propagation

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice c): NEW SURFACE, does not settle the cell. The auto-caption track of PDQ's hour-long PMQ webinar 'Making Dollars & Sense Out of Delivery' (CUqcUlcds3A; the 331st's caption files were empty, today's yt-dlp pull returned the English ASR track) has PDQ's VP of Marketing confirm marketplace integration into the POS: 'integration to doordash integration to ubereats integration to the third parties combined with your native integration by your pos provider ... you have integration to pdq pos but that's not all there's integration to pdq online ordering ... and ... pdq rewards'. PDQ's sales director adds that operators keep 'a pos menu that has their normal prices and then ... a doordash menu that everything's 20 percent higher ... you just hit the button and now all of a sudden you're on new pricing'. Tokenised controls over all 20 caption tracks of the vendor channel (141 KB): 'pause' 0, '86' 0, 'throttl*' 0, 'busy' 4 (all 'we've been busy' chatter, none a store status); known-positive control 'doordash' 5, 'delivery' 72. So a marketplace link exists; nothing says a pause or an 86 at the POS/KDS propagates to it. Retrieved 2026-09-18. adversarially verified

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

kitchen-order-ready-callback

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice c): NEW SURFACE, does not settle the cell. The PMQ webinar's caption track (CUqcUlcds3A) confirms a DoorDash/Uber Eats integration into PDQ POS (quoted on kitchen-channel-pause-propagation), and the only 'ready' events it describes go to the GUEST: 'real time text notifications so your customer knows when it left' (the Delivery Toolkit). The full-resolution 'PDQ VDU (KDS)' demo (J8n_rhS4QFk) shows bump as the only ticket action and no marketplace or courier option anywhere in the per-display setup ('Display Information / Display Setup / Transaction Types / Stage Setup / Bump Bar Setup'). Nothing says a KDS bump sends a ready event to a marketplace. Held unknown: the 327th rule applies (an unpublished partner integration is not bounded by a public census). Retrieved 2026-09-18. adversarially verified

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

kitchen-bump-bar-hardware

The 2025 product catalog is now retrievable and extractable (it was not on 2026-08-01, which is why this sat at partial). Page 8 heads a section 'VDUs/KDS' and lists a '15 IN. MONITOR & BUMP BAR' SKU: 'Controlled by the bump bar, the 15 in. monitor & bump bar combo unit is a perfect replacement for the ticket system commonly used in kitchens, lowering paper-use and increasing efficiency in expediting customer orders.' A named, first-party bump-bar model, so the documented-supported-model test is met. Key legends and programmability are not described. The former citation, /pdq-pos-hardware-catalog/, now 301s to the pdqpos.com homepage and has been withdrawn. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

kitchen-all-day-counts

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice c): NEW SURFACE - the full 1080p video stream of PDQ's own 'PDQ VDU (KDS)' demo (youtube.com/watch?v=J8n_rhS4QFk, vendor channel @PDQPOS, uploaded 2020-05-18, 101 s, 1920x1080), downloaded anonymously and decoded frame by frame (62 distinct frames at 1 s steps, plus 0.5 s crops of the setup screens), read as images. Prior passes held only YouTube's three auto-thumbnails and a 160x90 storyboard. Vendor-authored product demo = grade C. WHAT IT HOLDS FOR THIS CELL: the VDU main screen's whole control column is visible (frame 85 s): 'Time Clock', 'Message', 'Display Setup', 'Display History', two unlabelled scroll buttons and 'Page 1 of 1'. There is no all-day/summary/consolidated-count button, and none of the per-display toggles seen reads as an all-day count. Not a `no`: one 2020 demo of one display style is not a census of the VDU's views or styles ('Manage Styles' exists). Retrieved 2026-09-18. adversarially verified

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

kitchen-sla-alerts

332nd (slice c): NEW SURFACE - the full 1080p video stream of PDQ's own 'PDQ VDU (KDS)' demo (youtube.com/watch?v=J8n_rhS4QFk, vendor channel @PDQPOS, uploaded 2020-05-18, 101 s, 1920x1080), downloaded anonymously and decoded frame by frame (62 distinct frames at 1 s steps, plus 0.5 s crops of the setup screens), read as images. Prior passes held only YouTube's three auto-thumbnails and a 160x90 storyboard. Vendor-authored product demo = grade C. CLAIM: configurable target cook times per station or order type, with visual colour escalation and/or audible alert when a ticket exceeds target. VERDICT: partial/C. EVIDENCE (frames 78-83 s): the VDU's own setup is per DISPLAY (i.e. per station): 'VDU Setup' lists three displays with columns 'Display Name / Station / Style / Route Position / Active' ('Demo' on 'Current PC', 'Test2' on DEMO_2, 'Test' on DEMO_3), with 'Add Display / Modify Display / Delete Display' and 'Manage Stages / Manage Styles'. The per-display editor has tabs 'Display Information / Display Setup / Transaction Types / Stage Setup / Bump Bar Setup' and numeric fields 'Rows 2 / Columns 4 / Route Position 1 / Bump Increment 1 / Pre-Prep Warning 0 / Post-Prep Warning 0', plus on/off toggles including 'Show Prep Time', 'Show Alerts' and 'Quick Bump Prep Time'. So a per-station, operator-set warning threshold relative to prep time and an alerts switch exist. Each live ticket header carries a running elapsed timer ('Chk 14 ... 0:36 PU', 'Chk 12 ... 1:04 DEL', 'Chk 15 ... 0:21', frame 85 s). SHORTFALL (named): the demo's thresholds are all 0 and no frame shows what happens when a ticket crosses one - the header colours seen follow ORDER TYPE (PU red, DEL blue, in-store tan), not age - so the escalation conjunct is unseen; the labels are read from a 1080p video frame, legible but soft. Table-stakes weight, so partial/C is permissible. Retrieved 2026-09-18. https://www.youtube.com/watch?v=J8n_rhS4QFk · retrieved 2026-09-18 adversarially verified

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

kitchen-printer-fallback

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 334th: 334th (slice c): first per-cell check; NEW SURFACES, none settles the cell. (1) PMQ Think Tank (thinktank.pmq.com, now NXDOMAIN): Wayback CDX lists 7 archived 200 thread pages whose URL names PDQ (pdq-pos.10282, pdq-signature-system.11690, pos-systems-diamond-touch-vs-pdq.1635 pages 1-4, .208 page 3); 23 posts mention PDQ, 2006-2010, all about price, support and Windows 98/XP - zero on printers, KDS or failover. (2) Vimeo's public v2 listing of PDQ's account (https://vimeo.com/api/v2/user/pdqpos/videos.json) holds 19 public videos, 2016-2018; the four no prior pass read ('PDQ POS-Video' 237398208, 'Fingerprint Reader', 'Camera with Text Overlay', 'Welcome to Old Antlers Inn') answer 401 to the anonymous player, so they are unread and not absent. (3) GlobeNewswire releases (Fancy Dance Casino 2026-08-19; Slate of New Features 3.5.383, 2025-02-26): no printer, KDS or offline sentence. Per-cell re-grep of on-disk text (1.04 MB: all 45 @PDQPOS caption/ASR tracks, the q324/q325 Wayback site pages, the 2016 Feature Overview, the catalog PDF texts): 'back-up printer|fail over|re-route|redirect' 0 hits; the 20 distinct 'printer' contexts are hardware catalogue lines and one routing testimonial ('each group is sent to a specified printers', PDQ Touchscreen POS Testimonial 0ow2fea_MCA) - routing, not fallback. Retrieved 2026-09-18. adversarially verified

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

kitchen-offline-operation

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice c): NEW SURFACE - the full 1080p video stream of PDQ's own 'PDQ VDU (KDS)' demo (youtube.com/watch?v=J8n_rhS4QFk, vendor channel @PDQPOS, uploaded 2020-05-18, 101 s, 1920x1080), downloaded anonymously and decoded frame by frame (62 distinct frames at 1 s steps, plus 0.5 s crops of the setup screens), read as images. Prior passes held only YouTube's three auto-thumbnails and a 160x90 storyboard. Vendor-authored product demo = grade C. WHAT IT HOLDS FOR THIS CELL: every VDU display is bound to a local station computer - the setup list's 'Station' column reads 'Current PC', 'DEMO_2', 'DEMO_3', and the editor shows 'Station Name KODLIX / My Computer: KODLIX' - so the KDS is a program on in-store PCs fed by the in-store POS, consistent with the vendor's 'hybrid ... without being dependent on [the cloud]' abstract already cited on reliability-offline-order-entry. No frame or sentence says the VDU keeps receiving tickets when the internet is down; an architecture inference is not the claim, so held unknown. Retrieved 2026-09-18. || 333rd: 333rd (slice c): NEW SURFACES, none settles the cell. Read as images (frames at 0.5 s steps, distinct frames kept): PDQ's own 'PDQ POS Demo' (youtube.com/watch?v=EoHF88VZ9aA, 2016, 369 s, 191 frames, plus its English caption track), 'PDQ POS Overview' (YUUejVp2lhY), 'Learn More About PDQ POS' (PWqryUhZN4E), 'PDQ POS' (xvVu3cVQl8I), the current www.pdqpos.com hero video (https://www.pdqpos.com/assets/video/PDQ.mp4, live 200, 60 s), the 'PDQ POS Slide Show' (T2hV0YmVBjE, second vendor channel @pdqpos1959), the SOFO Expo talk (z5vXjbqGtMo, talking head, captions 429-refused), 'The Chef's Kitchen' TV segment (hMgf61pAV7U), and two 2023 SSI-commissioned promos by Rebel Hill Productions for the Parx Casino rollout ('PDQ POS Training' 5P5jYoKlOLw, 'PDQ POS Installation' J1GdSoIMGC4, both ending 'Learn more at ssipos.com'). Also found: an unlinked Vimeo account (vimeo.com/pdqpos) embedded 8 videos on the 2022 /images-videos/ page (Wayback 20220627145426); 3 are public (Self-service Drive-thru, Integrated Digital Menu Boards, About PDQ Signature Systems - YouTube duplicates) and 5 answer 'Sorry' (private/removed) even with the pdqpos.com referer. A third channel, @signaturesystems1, holds 8 testimonials of 16-37 s. Not one frame across these shows a KDS/VDU software screen; the only kitchen-display frames are hardware (Installation promo 43-50 s: monitors mounted over the Parx line showing a Windows desktop, with a bump bar beneath). WHAT IT ADDS FOR THIS CELL: the Installation promo (J1GdSoIMGC4 at 49.5 s) shows a kitchen display at Parx Casino mid-install as a Windows PC desktop on a line-mounted monitor with a bump bar and local PC cabling beneath, which corroborates the 332nd's reading that the VDU is a local Windows station program. It is still an architecture inference: no frame or sentence says tickets keep flowing when the internet is down. Held unknown. Retrieved 2026-09-18. adversarially verified

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

kitchen-item-build-screens

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice c): NEW SURFACE - the full 1080p video stream of PDQ's own 'PDQ VDU (KDS)' demo (youtube.com/watch?v=J8n_rhS4QFk, vendor channel @PDQPOS, uploaded 2020-05-18, 101 s, 1920x1080), downloaded anonymously and decoded frame by frame (62 distinct frames at 1 s steps, plus 0.5 s crops of the setup screens), read as images. Prior passes held only YouTube's three auto-thumbnails and a 160x90 storyboard. Vendor-authored product demo = grade C. WHAT IT HOLDS FOR THIS CELL: tickets show each item with its modifiers as indented lines beneath it ('Small Old Italian' / 'Lettuce' / 'Tomato' / 'Onion' / 'No Oil'), both on the ticket and in the item-status panel. That is ticket line text with modifiers, which the claim excludes; no recipe step, portion or build/assembly view appears. Held unknown. Retrieved 2026-09-18. adversarially verified

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

kitchen-pizza-fractional-display

No make-line screen documentation published despite pizza positioning. || 326th: NEW READING for this cell, recorded because PDQ is a pizza-first vendor and this is the nearest evidence. The configuration object exists and its axes are named: the 2016 Feature Overview lists 'PIZZA SETUP MATRIX' with the indented sub-bullet 'Choice setup (TOPPING, SIZE, CRUST, SAUCE)' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf), and PDQ's Podcasts index argues pizza modifier complexity is its core competence: 'the nuances of ordering and fulfilling pizzas, INCLUDING AN ARRAY OF MODIFIERS, is perhaps the most difficult restaurant concept to master' (https://web.archive.org/web/20220627142629/https://www.pdqpos.com/podcasts/). What the make-line actually shows is described only as text: 'PDQ TICKETS USE WHOLE WORDS IN LEGIBLE TYPE minimizing errors at the make table' (https://web.archive.org/web/20041208204758/http://www.pdqpos.com/quick_svc.pdf). The claim needs SECTIONED/FRACTIONAL placement (halves, quarters) rendered visually and unambiguously; 'half', 'quarter', 'fraction' and 'section' are zero as topping-placement terms across the corpus, and the named matrix axes (topping, size, crust, sauce) contain no placement axis. Held unknown. Retrieved 2026-09-18. || 331st: 331st: NEW SURFACE, does not settle the cell: PDQ's own POS order-entry demo 'POS Ordering: FAST and EASY!' (youtube.com/watch?v=4-73vNrBqZM; auto-thumbnail i.ytimg.com/vi/4-73vNrBqZM/maxres2.jpg, read as an image). The pizza screen has a '1/2 with' button beside the topping grid (PEPPERONI ... TOMATOES), so half-pie placement is ENTERED at the POS. What reaches the make line is not shown. The order list renders toppings as indented text under the size ('Personal 10" / PEPPERONI', 'MED 14" / MUSHROOMS'), and the VDU demo frames (J8n_rhS4QFk) show only text lines. The claim needs the placement RENDERED visually on the make-line screen or ticket, so an entry button is adjacent and not a partial. Held unknown. Retrieved 2026-09-18. adversarially verified

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

kitchen-recall-refire

332nd (slice c): NEW SURFACE - the full 1080p video stream of PDQ's own 'PDQ VDU (KDS)' demo (youtube.com/watch?v=J8n_rhS4QFk, vendor channel @PDQPOS, uploaded 2020-05-18, 101 s, 1920x1080), downloaded anonymously and decoded frame by frame (62 distinct frames at 1 s steps, plus 0.5 s crops of the setup screens), read as images. Prior passes held only YouTube's three auto-thumbnails and a 160x90 storyboard. Vendor-authored product demo = grade C. CLAIM: a bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order. VERDICT: partial/C. EVIDENCE (frames 88-94 s): touching a ticket on the VDU opens an item-level panel with columns '# Qty Description Status'; each item line has its own 'Bump' button, and once bumped the button turns red and reads 'Un Bump' (all three items of Chk 12 - 'Small Abruzzi', 'Small Chicken Diablo', 'Small Old Italian' - shown in the 'Un Bump' state at 94 s), with 'BUMP All Items' and 'RESET All Items' buttons at the foot and an 'OK (Save Status)' button. The VDU's main-screen side column reads 'Time Clock / Message / Display Setup / Display History' plus 'Page 1 of 1' (frame 85 s). So bumped ITEMS can be un-bumped individually and a ticket's item statuses can be reset, and bumped tickets have a history view. SHORTFALL (named): no frame shows a ticket that has left the screen being recalled from 'Display History' back to the live queue, and no frame shows an item being refired or a ticket reprinted. Item-level un-bump is the claim's own unbump operation at item grain, so partial, not yes. Retrieved 2026-09-18. https://www.youtube.com/watch?v=J8n_rhS4QFk · retrieved 2026-09-18 adversarially verified

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

kitchen-order-modification-alerts

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice c): NEW SURFACES, none settles the cell. Read as images (frames at 0.5 s steps, distinct frames kept): PDQ's own 'PDQ POS Demo' (youtube.com/watch?v=EoHF88VZ9aA, 2016, 369 s, 191 frames, plus its English caption track), 'PDQ POS Overview' (YUUejVp2lhY), 'Learn More About PDQ POS' (PWqryUhZN4E), 'PDQ POS' (xvVu3cVQl8I), the current www.pdqpos.com hero video (https://www.pdqpos.com/assets/video/PDQ.mp4, live 200, 60 s), the 'PDQ POS Slide Show' (T2hV0YmVBjE, second vendor channel @pdqpos1959), the SOFO Expo talk (z5vXjbqGtMo, talking head, captions 429-refused), 'The Chef's Kitchen' TV segment (hMgf61pAV7U), and two 2023 SSI-commissioned promos by Rebel Hill Productions for the Parx Casino rollout ('PDQ POS Training' 5P5jYoKlOLw, 'PDQ POS Installation' J1GdSoIMGC4, both ending 'Learn more at ssipos.com'). Also found: an unlinked Vimeo account (vimeo.com/pdqpos) embedded 8 videos on the 2022 /images-videos/ page (Wayback 20220627145426); 3 are public (Self-service Drive-thru, Integrated Digital Menu Boards, About PDQ Signature Systems - YouTube duplicates) and 5 answer 'Sorry' (private/removed) even with the pdqpos.com referer. A third channel, @signaturesystems1, holds 8 testimonials of 16-37 s. Not one frame across these shows a KDS/VDU software screen; the only kitchen-display frames are hardware (Installation promo 43-50 s: monitors mounted over the Parx line showing a Windows desktop, with a bump bar beneath). WHAT IT ADDS FOR THIS CELL (first per-cell check; the prior note is the 2026-08-30 category boilerplate): the 2016 demo narrates an edit to an order already sent - 'we touched the check number next to Artie's name ... add some wings ... 24 wings with hot sauce will resend it for delivery' (EoHF88VZ9aA captions at 121-139 s) - so re-opening and re-sending a sent check exists. The frames show only the POS side, where the added '24 PC WINGS / HOT' line is listed plainly with no add/changed marker (f0139); no kitchen ticket or VDU view of the resent order appears in any video. Held unknown: the claim is about how the KITCHEN display flags the edit. Retrieved 2026-09-18. adversarially verified

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

kitchen-guest-ready-notification

'SMS customer notifications' shipped in the PDQ Delivery Toolkit; trigger source (KDS bump vs dispatch) not documented. https://www.pdqpos.com/ · retrieved 2026-08-01

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

kitchen-waste-logging

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 334th: 334th (slice c): first per-cell check; does not settle the cell. The same new surfaces as kitchen-printer-fallback this session (7 archived PMQ Think Tank PDQ threads, PDQ's 19-video public Vimeo listing, GlobeNewswire releases) hold no waste statement. Per-cell re-grep over 1.04 MB of on-disk PDQ text (45 channel caption/ASR tracks, Wayback site pages, Feature Overview, catalogs): 'waste|spoilage|remake|comp' 18 hits, none a logging feature - PDQ talks at the 2018 Pizza Expo (Fl7_sGpSmnU) and the Atlantic City Pizza & Pasta show (rCQdXNVCBrk) ('eliminate food waste is huge', 'I have to remake the food because they wanted no onions') credits order accuracy of integrated ordering, and 'waste too much time' is the PMQ delivery webinar host's aside (CUqcUlcds3A) (POISON NAMED). No KDS waste/remake reason entry is shown or described anywhere. Retrieved 2026-09-18. adversarially verified

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

kitchen-speed-of-service-reporting

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice c): NEW SURFACE, does not settle the cell. The on-screen slides of PDQ's own '5 Profit Generating Essentials for POS Systems' (P1NW60Uw3Gw, 2018, 366 s, 1080p, 100 distinct frames read as images) include '3. Insightful "Business Health" Reporting - Enterprise-level, Secure Cloud-based Reporting' and 'Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchise... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. The list names late DELIVERIES but no kitchen ticket time, station time or speed-of-service report; the VDU demo (J8n_rhS4QFk) shows per-ticket elapsed timers and a 'Display History' button but no report. Held unknown: a marketing slide list is not a report catalogue. Retrieved 2026-09-18. adversarially verified

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

kitchen-prep-forecasting

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. For the kitchen, hardware is established and software is not. The 2025 catalog has a VDUs/KDS section -- a 15-inch monitor and bump-bar combo "controlled by the bump bar", a 22-inch waterproof all-in-one and a DigiVue signage PC -- and ssipos.com lists "integrated kitchen display systems" among the hardware. That settles that a first-party KDS exists with physical bump bars. It settles nothing about routing rules, expo consolidation, course firing, prep pacing, throttling, channel pause propagation, ready callbacks, all-day counts, SLA alerts, printer fallback, offline operation, build screens, recall/refire, modification alerts, waste logging, speed-of-service reporting or prep forecasting -- none of which appears in any published PDQ material, and none of which a hardware catalog could carry. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice c): NEW SURFACE, does not settle the cell. PDQ's '5 Profit Generating Essentials' slides (P1NW60Uw3Gw) have a 'Predict' section: 'Analytics - Gathers info from multiple channels; performance tracking' and 'Predictive Analytics - Determine best offers; increase marketing efficiency'. POISON NAMED: this 'Predict'/'Predictive' is guest-offer targeting under the loyalty heading 'Power to Leverage Big Data', not demand or prep forecasting; no prep list or forecast quantity appears in any frame or in the 20 caption tracks of the vendor's channel ('prep' 0 hits, 'forecast' 0). Retrieved 2026-09-18. adversarially verified

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

delivery-driver-roster

'PDQ Delivery Toolkit app' is a native module with driver mapping/tracking and enhanced reporting. Clock-in/out and assignment-state modelling not documented. https://www.pdqpos.com/ · retrieved 2026-08-01

Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).

delivery-dispatch-board

A dispatch surface is implied by the Delivery Toolkit but no dispatch screen, undispatched queue, or run batching is documented. https://www.pdqpos.com/ · retrieved 2026-08-01

Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator

delivery-route-map

'driver mapping and tracking' is claimed; multi-stop route sequencing/optimization is not. https://www.pdqpos.com/ · retrieved 2026-08-01

Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator

delivery-driver-tracking

Native delivery dispatch/tracking is explicitly one of the conclusion-flipping cells and must clear the highest bar. The only evidence is the homepage phrase 'Delivery toolkit app that integrates driver mapping and tracking' — one clause of marketing copy. No product doc, no screenshot, no help article, no description of what is tracked (GPS breadcrumb vs. status flag), no dispatch screen. The dossier itself scores the adjacent dispatch-board and route-map cells partial off the same sentence; scoring tracking 'yes' off that same sentence is inconsistent. https://www.pdqpos.com/ · retrieved 2026-08-01 adversarially verified

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

delivery-zones-polygon

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Delivery is the best-marketed and least-documented part of this product. www.pdqpos.com names "PDQ Delivery Toolkit" and describes "a full-featured delivery toolkit app that integrates driver mapping and tracking, SMS customer notifications, enhanced reporting, and DoorDash/Uber Eats integration", plus "PDQ Third Party Fulfillment (3PF)". The 2019 reporting screenshot corroborates that delivery is a first-class dimension: Delivery and Web Delivery are separate transaction types, the Store Totals grid carries a "Late Del" column, and the Labor Summary pays Driver, Driver Bike and Driver In-Shop as distinct job classes. What is missing is every mechanism the claims ask about -- zone geometry, zone pricing, address validation, per-run compensation inputs, a driver cash settle-up producing an over/short, DaaS fallback, menu push and 86 sync to marketplaces, store pause, marketplace reconciliation, injection-error visibility, how a promise time is computed, and offline behaviour. None of it is described on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 324th: 324th: Wayback-recovered retired pdqpos.com marketing copy (2015 /online-ordering/) says operators can "carve out bad areas" of a delivery area and that "Multiple delivery zones and fees available". REJECTED as evidence for this cell at merge: the claim requires arbitrary map POLYGONS or drive-time ISOCHRONES, and "carve out bad areas" is equally consistent with excluding ZIP codes from a radius, which the claim explicitly excludes. No geometry primitive is named anywhere in the recovered corpus. Held unknown. Retrieved 2026-09-17. || 332nd: 332nd (slice d): NEW, per-cell read of the V2 Next.js ordering client (the 331st's 49-chunk fixpoint, .cache/q331/pdq-pos/c/chunks) for the ZONE model, which no prior note did. The client carries a store-level DeliveryZoneDetails object with exactly ZoneID, DelCharge and MinOrderOverride ('DeliveryZoneID:9===D&&S?.DeliveryZoneDetails?.ZoneID', 'let e=l?.DeliveryZoneDetails?.MinOrderOverride??-1'), i.e. zones carry their own fee and minimum (zone-pricing evidence, not geometry). Zone assignment is SERVER-side: the client POSTs /api/online/franchise/storelist with franchiseID, transTypeID, zipCode, latitude and longitude and receives the store with its zone. The Leaflet map in the client draws only store markers and the delivery-address marker; the 'Polygon'/'MultiPolygon' tokens are inside Leaflet's bundled GeoJSON parser, and no zone shape, radius or boundary is fetched or rendered. So coordinates reach the server (consistent with polygon OR radius lookup) but the geometry primitive is not visible in any client. Held unknown. Retrieved 2026-09-18. || 333rd: 333rd (slice d): NEW, does not settle the cell. TENANT CENSUS (new this session): GET / on all 209 tenant slugs in the Wayback-derived list (.cache/q331/pdq-pos/c/tenants.txt): 200 legacy WebForms, 7 V2 Next.js (bossierlive, marylandlive, philadelphialive, pittsburghlive, plus three PIZZA tenants no prior pass saw on V2: mygiaspizza, slicespizzapa, trianospizza), 1 redirect off-domain (domspizza), 1 403 (admin). Two more V2 tenants absent from the Wayback list were found by name probe (oceancasino, sycuan; *.pdqonlineordering.com is a wildcard cert, so certspotter cannot enumerate tenants). All 9 V2 tenants serve the IDENTICAL chunk set (same md5 over the sorted chunk list), and every chunk is inside the 331st 49-chunk fixpoint (.cache/q331/pdq-pos/c/chunks): there is one V2 build, not a newer one on other tenants. Each V2 page embeds the franchise config in its RSC payload (36 keys, same schema on all 9; .cache/q333/pdq-pos/d/v2-config.json). The config has a server-side geometry switch that no prior note records: 'MAPPING.HERE.ENABLEMICROSOFTGEOMETRY' is 'false' on all 9 tenants. It sits beside 'MAPPING.HERE.ACTIVE' 'True' (HERE geocoding) and 'UseMapping'/'SaveGeoCodes'. The key does not occur in any V2 client chunk, so whatever it gates is server-side, and its name does not say polygon. It is off everywhere it is visible. POS demo 'PDQ POS Demo' (youtube EoHF88VZ9aA, 2016, v3.5.199), 161 frames read at 1080p: the customer record carries 'Map 0.10 Miles' / 'Map 6.70 Miles' and a 'Sub Division' field. The Driver Mapping screen ('Full Map', 'Order List', 'Directions') draws delivery pins and a route ('Total Driving Distance: 81.3 Miles') with NO zone overlay. So the observed zone model is distance and subdivision based, and no polygon is ever drawn. Not a no: no zone-setup screen appears in any source, and the geometry switch leaves a server polygon mode possible. Retrieved 2026-09-18. || 334th: 334th (slice d): NEW SURFACE, does not settle the cell. PDQ's own driver app, PDQ DT ('PDQ Delivery Toolkit', Android package com.pdqpos.pdqdelivery, listed at https://play.google.com/store/apps/details?id=com.pdqpos.pdqdelivery; APK v1.3.4, 47,158,626 bytes, sha256 52ee11e8b22d1d3f..., fetched anonymously from the APKPure mirror because Play serves no APK; never installed or run). It is a Xamarin.Forms app: its logic ships as .NET assemblies inside assemblies.blob (116 entries, LZ4/XALZ). PDQDT.dll (332,800 bytes) and PDQDT.Android.dll (451,584 bytes) were unpacked and 8,011 distinct strings read out, incl. the XAML page set and the embedded EULA (PDQDT.Content.AppTerms.txt). No prior session opened this app's code (the 327th/328th read its store listings only). The order model the store sends the driver carries a delivery zone only as a LABEL on the customer record: CustomerInfo fields are Phone, CustPhoneFull, PhoneExt, Name, Address, Address1, City, State, Zip, SecName, RoomNumber, DelZone, DelInstructions, Dept, Floor, SubDivision, EmailAddress; order fields add DelCharge beside SubTotal/Taxes/OrderTotal. No coordinates, radius, polygon, boundary or isochrone field exists in the app; directions are handed off to the device map app ('triggerMapping', 'Mapping is not supported by your device.'), and the only geometry the app produces is the driver's own GPS trail (Latitude, Longitude, Speed, Bearing) sent to wapi-dtdata-s1.mypdqpos.com. With the 332nd's V2-client finding (DeliveryZoneDetails = ZoneID, DelCharge, MinOrderOverride; zone assigned server-side from zip/lat/long) this is the second PDQ client that shows zones as named, priced records, and neither shows how a zone's area is defined. Held unknown: the zone editor is in the store POS/back office, which is unseen. Retrieved 2026-09-18. adversarially verified

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

delivery-zone-pricing

CLAIM: each delivery zone carries its own independently configurable delivery fee, order minimum and quoted promise time, applied automatically from the validated address. VERDICT: partial -- per-zone FEES are published; minimums and promise times are not. NEW SURFACE: PDQ's own Online Ordering feature page, archived snapshot https://web.archive.org/web/20151223080810/http://www.pdqpos.com/online-ordering-2/ (3,440 chars stripped), section headed 'The NUTS & BOLTS of ONLINE ORDERING'. EVIDENCE, verbatim: 'Multiple delivery zones and fees available' and 'Custom delivery zone available so you carve out "bad" areas'. SHORTFALL NAMED: fee-per-zone only; no per-zone order minimum, no per-zone promise time, and nothing states the fee is selected automatically from a validated address rather than by store pick. Grade C (vendor feature page); retired copy, so partial is the ceiling. Retrieved 2026-09-17. https://web.archive.org/web/20151223080810/http://www.pdqpos.com/online-ordering-2/ · retrieved 2026-09-17 adversarially verified

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

delivery-address-validation

CLAIM: address entry validated/geocoded against a mapping service at order time, rejecting or flagging out-of-zone addresses before acceptance. VERDICT: partial. NEW SURFACE (production code, not marketing): PDQ Online Ordering is an ASP.NET WebForms app served per-tenant at <store>.pdqonlineordering.com; its shipped script https://passariellos.pdqonlineordering.com/Scripts/mapping.js (200, 824 bytes; a nonsense sibling /Scripts/zzz-nope.js returns 404, so this is not a soft-200) geocodes the typed address at order time and hands the result to the server: 'function getCoordinates(address, ajaxControlIDToUse, divMapID) { ... map = new VEMap(divMapID); map.LoadMap(); ... find(address); }' calling 'map.Find(...)' against Microsoft Virtual Earth, and in FindCallback: 'if (places == null) { //Could not find address $find(ajaxControlID).ajaxRequest("3|Could Not Find Address|"); }' else '//Send back to code behind....bestPlace.LatLong.Latitude,bestPlace.LatLong.Longitude'. So the address IS geocoded against a mapping service during ordering and an unresolvable address is rejected with a named error. There is also a 'getCoordinatesAndNextAddress' variant. SHORTFALL (named): the OUT-OF-ZONE half is not visible in client code - the lat/long is posted to server code-behind and the zone test happens there; PDQ's own copy says only 'Multiple delivery zones and fees available' and 'Custom delivery zone available so you carve out "bad" areas' (https://web.archive.org/web/20151223080810/http://www.pdqpos.com/online-ordering-2/), which does not state that an out-of-zone address is refused before the order is accepted. Grade B (vendor's own shipped production JS, not published documentation). Retrieved 2026-09-18. https://passariellos.pdqonlineordering.com/Scripts/mapping.js · retrieved 2026-09-18 adversarially verified

Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator

delivery-driver-comp

CLAIM: tracks per-delivery driver comp inputs - mileage/distance per run, per-delivery flat reimbursement, driver-retained tips - and exports them to payroll as separate reimbursement vs wage lines. VERDICT: partial. EVIDENCE: PDQ's own Off-Premise Solutions page describes the PDQ Delivery Toolkit app: it provides drivers with 'Driver Mapping and essential tools that save in-store tip/receipt reconciliation time', and 'assists store owners by providing a Driver Tracking map, back-end reporting to ensure driver integrity and metrics to accurately determine both miles driven and time-on-road vs. time-in-store FOR WAGE PURPOSES' (https://web.archive.org/web/20200924180900/https://www.pdqpos.com/2020/06/22/off-premise-solutions/, archived 2020-09-24). Mileage capture and driver tip handling explicitly for wage computation are therefore first-party features, not spreadsheets. SHORTFALLS (named): no per-delivery flat reimbursement rate is described; and there is NO payroll export, let alone one separating reimbursement from wage lines - the page stops at 'metrics ... for wage purposes'. Source is a retired vendor solutions/blog page (grade D), so the differentiator grade floor bars any yes here regardless. Retrieved 2026-09-17. https://web.archive.org/web/20200924180900/https://www.pdqpos.com/2020/06/22/off-premise-solutions/ · retrieved 2026-09-17 adversarially verified

Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.

delivery-cash-reconcile

NEW EVIDENCE answering the exact gap the previous pass was held on ('no driver bank, settle-up or over/short output is described'). PDQ's own 'Easy to Learn & Operate' page, under the heading 'Delivery is a snap', enumerates the driver round-trip and ends with a settle-up line: 'Driver takes order, touches ticket, touches name and gets directions if necessary. / Upon return, driver touches his/her name and is ready to pickup new orders. / DETERMINE HOW MUCH EACH DRIVER OWES IN SECONDS.' (https://web.archive.org/web/20150731053400/http://pdqpos.com/easy-to-learn/). The Driver Dispatch module sheet adds the cash half: 'The driver locator allows one to look-up every driver on route and check their locations, driver times, and IMPORTANT CASH DROPS' (https://web.archive.org/web/20041016083946/http://www.pdqpos.com/driver.htm, a retired 2004 module page). An amount-owed-per-driver figure plus per-driver cash drops is a settle-up output, not merely reconciliation time saved. SHORTFALL (named): the amount owed is not stated to net tips owed to the driver, nothing is called a driver bank, and no over/short variance figure is named; and the settle-up sentence sits on a 2015 marketing page, the cash-drop sentence on a 2004 retired module page. Retrieved 2026-09-18. https://web.archive.org/web/20150731053400/http://pdqpos.com/easy-to-learn/ · retrieved 2026-09-18 adversarially verified

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

delivery-daas-dispatch

CORRECTED after verification; the earlier note over-claimed and the grade was too high. Affirmatively established, and only this: NATIVE COURIER HANDOFF - PDQ Third Party Fulfillment offers 'automatic overflow to Uber Eats and DoorDash delivery platforms'. SHORTFALLS: (1) the claim requires the courier QUOTE to return into the order record; the page claims lowest delivery rates and order stacking at a single fee for multiple orders but never states a per-order quote is surfaced. (2) An earlier pass also claimed courier STATUS return was established. IT IS NOT: the real-time driver location/ETA bullet is a SEPARATE list item about instantly assigning drivers or using 'driver autopilot' for self-assignment, which are first-party-fleet actions, and the same page separately advertises a natively integrated 'PDQ Delivery Toolkit' with its own mobile app - so that tracking bullet more naturally describes PDQ's own-driver product than courier-order status. Attaching it to the overflow bullet was an inference across two independent bullets. Grade D: this is a press-release landing page ('Signature Systems Announces "PDQ Third Party Fulfillment"'), not documentation, and it 404s live so it is cited to its 2025-12-09 archive capture. The quoted strings cross a </strong> boundary in raw bytes - sense preserved, but they are not byte-contiguous. Nash and Relay occur zero times. https://web.archive.org/web/20251209100255/https://www.pdqpos.com/3pf/ · retrieved 2026-09-12 adversarially verified

Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator

delivery-daas-fallback

CLAIM: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. VERDICT: partial -- the overflow product exists and is named, the triggering RULES are not published. NEW SURFACE: the PDQ Third Party Fulfillment (3PF) product page as archived 2023-10-02 (https://web.archive.org/web/20231002202204/https://www.pdqpos.com/3pf/, 5,257 chars stripped); 3PF is still a current product, named in the About Us block of the LIVE https://www.pdqpos.com/ home page ('PDQ Third Party Fulfillment (3PF)'). EVIDENCE, verbatim: 'ORDER OVERFLOW: Easily expand your delivery areas and volume with automatic overflow to Uber Eats and DoorDash delivery platforms'; 'ORDER STACKING: Reap significant savings with a single fee for multiple orders'; 'REAL-TIME TRACKING: Track driver locations, ETAs, and progress in real-time. Instantly assign drivers or use driver autopilot for self-assignment.'; headline 'Automate Delivery Dispatch' over 'optimum automated delivery management'. SHORTFALL NAMED: the word 'automatic' is asserted but no condition is published -- no in-house-driver-unavailable rule, no out-of-zone rule, no wait threshold, no fee ceiling; and 'driver autopilot' is described as driver SELF-assignment, not courier handoff. Grade D: vendor marketing page, retired copy, so partial is the ceiling regardless. Retrieved 2026-09-17. https://web.archive.org/web/20231002202204/https://www.pdqpos.com/3pf/ · retrieved 2026-09-17 adversarially verified

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

delivery-3p-direct-integration

DoorDash and Uber Eats named as direct integrations via PDQ Third Party Fulfillment (3PF). Grubhub is never named. Not a DoorDash Preferred Integration Partner. https://www.pdqpos.com/ · retrieved 2026-08-01

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

delivery-3p-injection

'PDQ Third Party Fulfillment (3PF)' is a named product implying injection; ticket-level behavior and tablet-free operation not documented. https://www.pdqpos.com/ · retrieved 2026-08-01

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

delivery-menu-push

CLAIM: menu, pricing, modifiers and photos publish from the POS master menu to connected marketplaces, including channel-specific markups, without maintaining a separate menu per portal. VERDICT: partial. EVIDENCE: PDQ's DoorDash press release states the integration works by keeping the operator's existing menu synced rather than by a second menu in the DoorDash portal - 'significantly minimizing changes to its in-store operations and ENSURING ITS EXISTING MENUS AND STORE HOURS STAY SYNCED WITH THE DOORDASH PLATFORM' (https://web.archive.org/web/20250121221212/https://www.pdqpos.com/wp-content/uploads/2020/12/PR_JJ-DoorDash3.pdf). PDQ also sells this as its 'Third Party Fulfillment (3PF)' platform and separately offers 'integration to ItsaCheckmate, a 3rd party aggregator that integrates to over forty 3rd party platforms, thus eliminating the need to have a tablet for each provider' (https://web.archive.org/web/20200924180900/https://www.pdqpos.com/2020/06/22/off-premise-solutions/). SHORTFALLS (named): modifiers, item photos and channel-specific price markups are nowhere mentioned; the only synced objects PDQ names are 'menus and store hours'. Retrieved 2026-09-18. https://web.archive.org/web/20250121221212/https://www.pdqpos.com/wp-content/uploads/2020/12/PR_JJ-DoorDash3.pdf · retrieved 2026-09-18 adversarially verified

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

delivery-86-sync

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Delivery is the best-marketed and least-documented part of this product. www.pdqpos.com names "PDQ Delivery Toolkit" and describes "a full-featured delivery toolkit app that integrates driver mapping and tracking, SMS customer notifications, enhanced reporting, and DoorDash/Uber Eats integration", plus "PDQ Third Party Fulfillment (3PF)". The 2019 reporting screenshot corroborates that delivery is a first-class dimension: Delivery and Web Delivery are separate transaction types, the Store Totals grid carries a "Late Del" column, and the Labor Summary pays Driver, Driver Bike and Driver In-Shop as distinct job classes. What is missing is every mechanism the claims ask about -- zone geometry, zone pricing, address validation, per-run compensation inputs, a driver cash settle-up producing an over/short, DaaS fallback, menu push and 86 sync to marketplaces, store pause, marketplace reconciliation, injection-error visibility, how a promise time is computed, and offline behaviour. None of it is described on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice d): NEW SURFACE checked for this cell: the DoorDash partner registry (https://merchants.doordash.com/api/partner-integrations), re-fetched live today, lists 64 providers and PDQ is not one of them (tokens 'pdq' 0 and 'signature' 0 in the payload; same 64 as the frozen 2026-09-11 copy .cache/q258/pi.json). PDQ's only DoorDash statement is the 2020 Jimmy John's press release (Self-Delivery listing, 'menus and store hours stay synced'), so PDQ holds no DoorDash-certified integration today whose per-feature flags could evidence this cell either way. Absence from the registry is NOT a capability no: an order-aggregation middleware could carry the feature, and PDQ publishes no marketplace documentation. A per-cell vocabulary grep over 4,380 text files in 18 on-disk pdq corpora (incl. 84 re-extracted PDFs) found '86'/'out of stock'/'sold out' only as POS/online-menu item availability, never as a push to a marketplace. Retrieved 2026-09-18. adversarially verified

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

delivery-store-pause

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Delivery is the best-marketed and least-documented part of this product. www.pdqpos.com names "PDQ Delivery Toolkit" and describes "a full-featured delivery toolkit app that integrates driver mapping and tracking, SMS customer notifications, enhanced reporting, and DoorDash/Uber Eats integration", plus "PDQ Third Party Fulfillment (3PF)". The 2019 reporting screenshot corroborates that delivery is a first-class dimension: Delivery and Web Delivery are separate transaction types, the Store Totals grid carries a "Late Del" column, and the Labor Summary pays Driver, Driver Bike and Driver In-Shop as distinct job classes. What is missing is every mechanism the claims ask about -- zone geometry, zone pricing, address validation, per-run compensation inputs, a driver cash settle-up producing an over/short, DaaS fallback, menu push and 86 sync to marketplaces, store pause, marketplace reconciliation, injection-error visibility, how a promise time is computed, and offline behaviour. None of it is described on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: NEW SURFACE, does not settle the cell, and it is the closest PDQ comes. The DoorDash press release states that store availability data flows from PDQ to the marketplace: the integration ensures 'its existing menus and STORE HOURS STAY SYNCED WITH THE DOORDASH PLATFORM' (https://web.archive.org/web/20250121221212/https://www.pdqpos.com/wp-content/uploads/2020/12/PR_JJ-DoorDash3.pdf). Scheduled hours are not a pause: the claim needs an operator-initiated deactivation from inside the POS with a TIMED AUTO-REACTIVATION, and no PDQ surface describes pausing, 86ing a store, or a busy/closed toggle - 'pause' is zero across the corpus. PDQ's 3PF page instead solves overflow in the other direction ('automatic overflow to Uber Eats and DoorDash delivery platforms'). Shortfalling the operative conjunct, held unknown. Retrieved 2026-09-18. || 332nd: 332nd (slice d): NEW SURFACE checked for this cell: the DoorDash partner registry (https://merchants.doordash.com/api/partner-integrations), re-fetched live today, lists 64 providers and PDQ is not one of them (tokens 'pdq' 0 and 'signature' 0 in the payload; same 64 as the frozen 2026-09-11 copy .cache/q258/pi.json). PDQ's only DoorDash statement is the 2020 Jimmy John's press release (Self-Delivery listing, 'menus and store hours stay synced'), so PDQ holds no DoorDash-certified integration today whose per-feature flags could evidence this cell either way. Absence from the registry is NOT a capability no: an order-aggregation middleware could carry the feature, and PDQ publishes no marketplace documentation. So DoorDash's STORE_AVAILABILITY_WEBHOOKS ('Integrated close/pause store') flag does not exist for PDQ at all. Retrieved 2026-09-18. adversarially verified

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

delivery-3p-reconciliation

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Delivery is the best-marketed and least-documented part of this product. www.pdqpos.com names "PDQ Delivery Toolkit" and describes "a full-featured delivery toolkit app that integrates driver mapping and tracking, SMS customer notifications, enhanced reporting, and DoorDash/Uber Eats integration", plus "PDQ Third Party Fulfillment (3PF)". The 2019 reporting screenshot corroborates that delivery is a first-class dimension: Delivery and Web Delivery are separate transaction types, the Store Totals grid carries a "Late Del" column, and the Labor Summary pays Driver, Driver Bike and Driver In-Shop as distinct job classes. What is missing is every mechanism the claims ask about -- zone geometry, zone pricing, address validation, per-run compensation inputs, a driver cash settle-up producing an over/short, DaaS fallback, menu push and 86 sync to marketplaces, store pause, marketplace reconciliation, injection-error visibility, how a promise time is computed, and offline behaviour. None of it is described on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: NEW SURFACE, does not settle the cell. PDQ's Third Party Fulfillment (3PF) page is the vendor's most detailed third-party-delivery document and its feature list is closed: 'ORDER OVERFLOW: Easily expand your delivery areas and volume with automatic overflow to Uber Eats and DoorDash delivery platforms / ORDER STACKING: Reap significant savings with a single fee for multiple orders / REAL-TIME TRACKING: Track driver locations, ETAs, and progress in real-time. Instantly assign drivers or use DRIVER AUTOPILOT for self-assignment. / PLUS... Brand app integration, ENHANCED REPORTING & ANALYTICS, and more!' (https://web.archive.org/web/20231002202204/https://www.pdqpos.com/3pf/). 'Enhanced reporting & analytics' is the nearest thing to this claim and it is unqualified: no payout matching, no commission or marketing-fee itemisation, no refund/adjustment line, no missing-order detection. The tokens 'reconcile', 'reconciliation', 'payout', 'commission' and 'deposit' return only the unrelated cash-drawer and driver-tip senses elsewhere in the corpus. Held unknown. Retrieved 2026-09-18. || 333rd: 333rd (slice d): NEW SURFACE, with POISON recorded. PDQ's 58-minute delivery webinar 'Making Dollars & Sense Out of Delivery' (youtube CUqcUlcds3A; captions held at .cache/q332/pdq-pos/c/subs) is the vendor's longest statement on third-party delivery. Every 'reconciliation' in it (24:21, 24:32, 27:23, 33:16) is DRIVER TIP/RECEIPT reconciliation in the Delivery Toolkit app ('we want to simplify driver tip and uh receipt reconciliation ... they can do it from their phone'). None concerns marketplace payouts. On marketplaces it states only an integration ('integration to doordash integration to ubereats integration to the third parties combined with your native integration') and a pricing practice ('they'll have a pos menu that has their normal prices and then they'll have a doordash menu that everything's 20 percent higher'). No payout, commission, deposit or missing-order matching is described. Held unknown. Retrieved 2026-09-18. adversarially verified

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

delivery-injection-error-visibility

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Delivery is the best-marketed and least-documented part of this product. www.pdqpos.com names "PDQ Delivery Toolkit" and describes "a full-featured delivery toolkit app that integrates driver mapping and tracking, SMS customer notifications, enhanced reporting, and DoorDash/Uber Eats integration", plus "PDQ Third Party Fulfillment (3PF)". The 2019 reporting screenshot corroborates that delivery is a first-class dimension: Delivery and Web Delivery are separate transaction types, the Store Totals grid carries a "Late Del" column, and the Labor Summary pays Driver, Driver Bike and Driver In-Shop as distinct job classes. What is missing is every mechanism the claims ask about -- zone geometry, zone pricing, address validation, per-run compensation inputs, a driver cash settle-up producing an over/short, DaaS fallback, menu push and 86 sync to marketplaces, store pause, marketplace reconciliation, injection-error visibility, how a promise time is computed, and offline behaviour. None of it is described on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice d): NEW SURFACE checked for this cell: the DoorDash partner registry (https://merchants.doordash.com/api/partner-integrations), re-fetched live today, lists 64 providers and PDQ is not one of them (tokens 'pdq' 0 and 'signature' 0 in the payload; same 64 as the frozen 2026-09-11 copy .cache/q258/pi.json). PDQ's only DoorDash statement is the 2020 Jimmy John's press release (Self-Delivery listing, 'menus and store hours stay synced'), so PDQ holds no DoorDash-certified integration today whose per-feature flags could evidence this cell either way. Absence from the registry is NOT a capability no: an order-aggregation middleware could carry the feature, and PDQ publishes no marketplace documentation. Vocabulary grep (4,380 files, 18 pdq corpora): 'failed order(s)', 'order rejected/error', 'integration status/health', 'connection status', 'injection' return no PDQ statement about marketplace order failures. Retrieved 2026-09-18. adversarially verified

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

delivery-tracking-page

'SMS customer notifications' shipped in the Delivery Toolkit; a branded tracking page on the restaurant's own domain is not documented. https://www.pdqpos.com/ · retrieved 2026-08-01

Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator

delivery-promise-time

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Delivery is the best-marketed and least-documented part of this product. www.pdqpos.com names "PDQ Delivery Toolkit" and describes "a full-featured delivery toolkit app that integrates driver mapping and tracking, SMS customer notifications, enhanced reporting, and DoorDash/Uber Eats integration", plus "PDQ Third Party Fulfillment (3PF)". The 2019 reporting screenshot corroborates that delivery is a first-class dimension: Delivery and Web Delivery are separate transaction types, the Store Totals grid carries a "Late Del" column, and the Labor Summary pays Driver, Driver Bike and Driver In-Shop as distinct job classes. What is missing is every mechanism the claims ask about -- zone geometry, zone pricing, address validation, per-run compensation inputs, a driver cash settle-up producing an over/short, DaaS fallback, menu push and 86 sync to marketplaces, store pause, marketplace reconciliation, injection-error visibility, how a promise time is computed, and offline behaviour. None of it is described on either host. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: NEW SURFACE, does not settle the cell: pdqdt.com, the Delivery Toolkit's own former website, which now 302s to pdqpos.com and was recovered from the Wayback CDX index (its Yoast page-sitemap enumerates exactly five pages: /, /contact/, /terms/, /404/, /privacy/). Its customer-notification copy quotes an ETA to the guest - customers 'will get up-to-date notifications, (order is on-the-way; DRIVER WILL BE THERE IN "X" AMOUNT OF TIME; order has been left at the door for contactless service)' - and its cost section names routing: 'Whether MAPPING OUT THE FASTEST ROUTE, enhancing your driver dispatch/routing abilities...' (https://web.archive.org/web/20210304053234/https://pdqdt.com/). PDQ's 3PF page adds 'REAL-TIME TRACKING: Track driver locations, ETAS, and progress in real-time'. All of these are POST-DISPATCH ETAs to a guest whose order is already placed. The claim is about the QUOTED PROMISE TIME AT ORDER, adjusting from kitchen load, driver availability and zone drive time; nothing describes how that quote is computed, and 'quote time', 'promise time' and 'prep time' are zero across the corpus. Held unknown. Retrieved 2026-09-18. || 327th: 327th (APPS/HOSTS SLICE): NEW SURFACE, does not settle the cell. The driver app listing is the vendor's fullest published account of delivery mechanics and it is entirely about routing and visibility, never about quoting: 'The features of PDQ DT focus on providing delivery drivers with the resources they need to most efficiently reach their customer with fresh food quickly without having to manually find routes to their destinations', plus driver performance monitoring 'especially when it comes to unauthorized routes and stops' and 'reduced per-mileage payments'. Nothing addresses a quoted promise time or its adjustment from kitchen load, driver availability or zone drive time. The ordering app that would DISPLAY such a quote (Menu.aspx/CheckOut.aspx) could not be rendered without a server session, so the quote surface is unobserved. Retrieved 2026-09-18. || 328th: 328th (APPS SLICE): the driver app's ACTUALS are now observed and they are still not a quote. PDQ DT's order card (vendor's own App Store screenshot) stamps three times per order - 'In: 11:02:49 AM / On Way: 11:03:04 AM / Delivered: 11:03:04 AM' - alongside 'Balance Due: $8.88' and a 'Remember Me' forgotten-item list, with 'On Way' and 'Delivered' as the two driver status buttons and a 'Previous Run(s)' history tab. That is elapsed-time measurement after the fact, per order; no quoted promise time and no adjustment input (kitchen load, driver availability, zone drive time) appears anywhere in the app. Retrieved 2026-09-18. || 328th: 328th (WEB/DOCUMENT SLICE): NEW SURFACE, does not settle the cell. The recovered 2020 'PDQ DELIVERY TOOLKIT(R)' FAQ leaflet ((c)Signature Systems, Inc.; 404 on live pdqdt.com, Wayback only; absent from every q324-q327 corpus) is PDQ's fullest published account of its delivery ETA behaviour, and what it describes is a LIVE DRIVER ETA, not a quoted promise time: customers 'will get up-to-date notifications, (order is on-the-way; driver will be there in "x" amount of time; order has been left at the door for contactless service)', and the Dedicated Driver Map, 'shown on a station (Win 10) or TV (Mini PC)... displayed in near real time', lets the operator 'see the orders that a driver delivered, how many orders the driver has remaining, and how long it will be until the driver arrives back at the store', with 'any previous delivery run with the GPS route drawn on map'. None of the claim's three inputs -- current kitchen load, driver availability, zone drive time -- is named as feeding a QUOTED promise time at order entry, so the cell stays unknown rather than partial. Retrieved 2026-09-18. || 331st: 331st: NEW SURFACE, and the first observation of a QUOTE AT ORDER ENTRY that prior passes could not render. The order-type screen of PDQ's own POS demo 'POS Ordering: FAST and EASY!' (auto-thumbnail i.ytimg.com/vi/4-73vNrBqZM/maxres3.jpg, read as an image) shows each channel tile with a quoted time: 'Delivery ... Ready In 35 Minutes $38.16' and 'Pickup ... Ready In 20 Minutes $30.48'. 'For Here' and 'InShop' show no time. So the POS quotes a promise time per channel at order entry. One frame cannot show whether the quote moves with kitchen load, driver availability or zone drive time or is a fixed per-store constant, and that is the claim's only operative conjunct. A partial would shortfall it, so the cell is held unknown. Retrieved 2026-09-18. || 331st: 331st (slice g): NEW SURFACE, a LIVE RENDER of the legacy storefront's order-time step, the first since the guest-session POST was refused in the 327th. Under a specific owner authorisation of 2026-09-18, ONE anonymous guest session was run on each of 3 public tenants (slicespizza, passariellos, hgchesterbrookpizza .pdqonlineordering.com; 8 requests each, 5-7 s apart, 20:51-20:59 UTC = Friday 16:51-16:59 EDT): GET /, the title page's 'Order Now' guest postback, the 'Pickup' postback, the city dropdown postback, 'Start Order' (Menu.aspx), then the cart's 'Order Time: Change' postback that renders the 'Change Order Time' popup. Nothing was carted, no field was typed into, no account was made, no order was placed. Saved under .cache/q331/pdq-pos/g/pages/. This is a live observation of the vendor's own shipped product (grade B for what it renders), not documentation. WHAT THE STOREFRONT QUOTES: the order-type step's delivery and pickup quote is a label (lblDelivery / lblPickup). Across 26 tenant renders (23 captured 2026-09-16 in .cache/q312/pdq-pos/pages, plus today's 3; enumerated in .cache/q331/pdq-pos/g/quotes.tsv), it is written prose from the tenant, not a computed value. Evidence: ranges such as 'Usually within 40-60 minutes' (anthonys7) and 'delivered within approximately 35-45 minutes' (antonellis-pizza), which no single computed figure produces. The number is repeated inside the tenant's own sentence: passariellos today reads 'Usually within 60 minutes, peak hours can surpass 60 minutes' and 'usually ready within 30 minutes, peak hours can surpass 30 minutes'. Two tenants write their own peak disclaimers: pizzabella, 'Friday - Sunday evening Delivery Times may be longer than 60 minutes'; pizzapub, '(Please allow additional time on Fri, Sat, & Sun)'. Across the 26 renders there are 0 hits for live-wait wording ('currently', 'estimated', 'wait time is'). None of the 45 checkouts on disk (from 2026-09-16) shows a computed promise time. 44 of 45 carry 'Order Time: As Soon As Possible'. The other, littleangelospizza, carries a chosen slot, 'Order Time: 9/16/2026 11:15 AM'. Today's time pickers start at 5:15 PM on all 3 tenants whatever their quote (see order-capture-throttling). So in PDQ's legacy guest ordering, the promise shown to guests is a fixed per-store figure, and tenants hand-write disclaimers that peak times exceed it. WHY STILL UNKNOWN (not proposed as 'no'): this bounds the online storefront only. The POS itself quotes a per-channel 'Ready In N Minutes' at order entry (slice b's video frame this session). Nothing here shows whether that POS figure moves with kitchen load, driver availability or zone drive time. Retrieved 2026-09-18. || 333rd: MERGE HOLD (proposed no/B, held unknown): The V2 client renders the promise through a {ReadyTime} placeholder that the server may compute; the fixed PAGE.ORDERCOMPLETE.DELIVERYTIME setting is a default, and a client census cannot see server-side logic (331st rule). The POS-side evidence is a 2016 demo (v3.5.199) from a retired generation, which may not carry a `no` (owner ruling 2). PROPOSAL AS WRITTEN: 333rd (slice d): CLAIM: quoted delivery promise times adjust dynamically from kitchen load, driver availability and zone drive time, rather than a fixed per-store constant. VERDICT: no, grade B. The 331st held this cell because the POS's own 'Ready In N Minutes' quote had been seen in one frame only, so whether it moves was unseen. Two new observations settle what the vendor's own product does. (1) CURRENT ORDERING CLIENT, ALL 9 TENANTS: in PDQ's second-generation Next.js ordering client the guest's delivery promise is a STORE CONFIG CONSTANT. The config reader reads 'deliveryTime:A(t,"PAGE.ORDERCOMPLETE.DELIVERYTIME","40"),deliveryTimeMessage:A(t,"PAGE.ORDERCOMPLETE.DELIVERYTIMEMESSAGE","Your order will be delivered within the next {ReadyTime} minutes."),pickupTime:A(t,"PAGE.ORDERCOMPLETE.PICKUPTIME","20")' (chunk 1wv3xur2ou__5.js, live today on trianospizza, 200, 107,156 B, byte-identical to the 331st copy; nonsense sibling /_next/static/chunks/zzznope333.js 404). The order-complete page renders 'Estimated Delivery Time' from exactly that value: 'ed=et?w:T,ec=et?P:L,eu=ec?.replace("{ReadyTime}",ed)' (chunk 1q8iz79oo15a3.js, live, 57,933 B), or the guest's own TimeScheduled if the order was scheduled. No order-response field, kitchen-load input, driver count or zone time feeds it. The store-level DeliveryZoneDetails object carries only ZoneID, DelCharge and MinOrderOverride, with no time (332nd). The 331st recorded this constant on order-capture-throttling, never on this cell. TENANT CENSUS (new this session): GET / on all 209 tenant slugs in the Wayback-derived list (.cache/q331/pdq-pos/c/tenants.txt): 200 legacy WebForms, 7 V2 Next.js (bossierlive, marylandlive, philadelphialive, pittsburghlive, plus three PIZZA tenants no prior pass saw on V2: mygiaspizza, slicespizzapa, trianospizza), 1 redirect off-domain (domspizza), 1 403 (admin). Two more V2 tenants absent from the Wayback list were found by name probe (oceancasino, sycuan; *.pdqonlineordering.com is a wildcard cert, so certspotter cannot enumerate tenants). All 9 V2 tenants serve the IDENTICAL chunk set (same md5 over the sorted chunk list), and every chunk is inside the 331st 49-chunk fixpoint (.cache/q331/pdq-pos/c/chunks): there is one V2 build, not a newer one on other tenants. Each V2 page embeds the franchise config in its RSC payload (36 keys, same schema on all 9; .cache/q333/pdq-pos/d/v2-config.json). The delivery wording tenants type into config is itself fixed prose: 'Usually within 60 minutes' (bossierlive, philadelphialive, pittsburghlive, slicespizzapa), and Triano's 'Check confirmation email for expected times. Average times can vary from 60 minutes'. (2) THE POS ITSELF: PDQ's own 6-minute 'PDQ POS Demo' (youtube.com/watch?v=EoHF88VZ9aA, uploaded 2016-10-14; the POS Manager screen reads 'Version: 3.5.199' dated 1/27/2016) was read frame by frame at 1080p, 161 scene frames (.cache/q333/pdq-pos/d/fr-EoHF88VZ9aA). The order-type screen quotes 'Delivery ... Ready In 35 Minutes' for three delivery orders to three different addresses: Artie Powell, 15 Penns Trail, whose customer record reads 'Map 0.10 Miles'; Agnes Simpson, 905 Steamboat Station, 'Map 6.70 Miles'; and Benjamin Bouvie, 87 South Nester Ave. Pickup reads 'Ready In 20 Minutes' every time. A 67-fold difference in the POS's own computed distance leaves the quote unchanged, so in the POS the quote has no drive-time input: it is a per-store constant per channel. (The Driver Dispatch queue does grow from 2 pending deliveries at 2:24 PM to 6 at 2:33 PM, but the frames do not fix which quotes were taken after that growth, so kitchen load is NOT claimed from this video.) These are the same 35/20 figures as the 331st's 'POS Ordering: FAST and EASY!' frame. CONTROLS: in the V2 client, 'readytime|preptime|waittime|leadtime|estimatedtime|promisetime|quotetime' occur only as the {ReadyTime} placeholder and the 'Estimated ... Time' label; 'minutes' elsewhere is date-fns (getMinutes/setMinutes: POISON). WEAKEST POINT: the POS evidence is a 2016 demo build. The current-generation evidence (live client, 9 tenants) is decisive for the guest-facing quote, the in-store POS quote is only observed in 2016, and the demo ran on demo data. Retrieved 2026-09-18. || 334th: 334th (slice d): NEW SURFACE, does not settle the cell and does not re-propose the held 333rd shape. PDQ's own driver app, PDQ DT ('PDQ Delivery Toolkit', Android package com.pdqpos.pdqdelivery, listed at https://play.google.com/store/apps/details?id=com.pdqpos.pdqdelivery; APK v1.3.4, 47,158,626 bytes, sha256 52ee11e8b22d1d3f..., fetched anonymously from the APKPure mirror because Play serves no APK; never installed or run). It is a Xamarin.Forms app: its logic ships as .NET assemblies inside assemblies.blob (116 entries, LZ4/XALZ). PDQDT.dll (332,800 bytes) and PDQDT.Android.dll (451,584 bytes) were unpacked and 8,011 distinct strings read out, incl. the XAML page set and the embedded EULA (PDQDT.Content.AppTerms.txt). No prior session opened this app's code (the 327th/328th read its store listings only). The driver app computes no ETA or promise: its only time fields are stamps - order 'In: {0:T}' (TimeIn), 'On Way: {0:T}' (TimeOut), 'Delivered: {0:T}', and per previous run 'Time Left: {0:G}' (TimeLeft, a date-time the run left the store, beside 'Order Count:' NumOrders). Its location service reports raw fixes (Latitude, Longitude, Speed, Timestamp, Accuracy, Bearing) to wapi-dtdata-s1.mypdqpos.com, so any drive-time estimate PDQ sends customers ('Text Notifications With Order Status Times' in the 2021 Delivery Tool Kit explainer, youtube LCeKw8MiRQQ; 'driver will be there in "x" amount of time' in the retired 2020 Delivery Toolkit leaflet) would be computed SERVER-side, which no client census can see (331st rule). Held unknown. Retrieved 2026-09-18. adversarially verified

Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.

delivery-offline-behavior

334th (slice d): CLAIM: the vendor DOCUMENTS explicit offline behaviour for delivery: whether cash delivery orders, driver assignment and driver settlement continue during an internet outage. VERDICT: no/C. This is documentation-shaped ('Vendor documents'), the same shape as this record's merged guest-loyalty-offline-behavior no/C and labor-offline-time-punch no/C (owner ruling 2026-09-18: a publication census carries `no`), and it is answered on the same census, re-derived today and WIDENED to every vendor publication the 333rd/334th found since. CURRENT PUBLICATION CENSUS (334th, GET only): (1) www.pdqpos.com homepage 200, 110,961 bytes, byte-identical to the 326th/331st/332nd copies (pdqdt.com serves the same page; pdqdt.com/terms/ 404); its legal set /termsofuse 81,365 B, /privacypolicy 59,266 B, /smsprivacypolicy 52,924 B; a nonsense path /zzz-nope-334 404s (1,928 B). (2) ssipos.com WordPress: /wp-json/wp/v2/types core types only; pages X-WP-Total 8, posts X-WP-Total 5 (all 13 read); media X-WP-Total 216 (its PDFs read in the 331st/332nd). (3) the Online Ordering Terms every legacy tenant serves (https://passariellos.pdqonlineordering.com/SSIPolicies.html, 200). (4) 84 vendor PDF texts (2025 Product Catalog, 2021-2023 SSI press releases, SSI Security brochure, articles; plus retired 2004-2020 copies, used for positives only). (5) PDQ's own app-store listings (iTunes lookup rows for MY PDQ and PDQ DT, 6 files). (6) NEW: the PDQ DT end-user licence agreement embedded in the driver app (see below). (7) NEW: EVERY PDQ video transcript on disk, 57 in all - 20 YouTube caption tracks (332nd) plus 36 local faster-whisper transcripts (333rd) plus 'PDQ Delivery Tool Kit Explainer Video' (youtube LCeKw8MiRQQ, 2021-02-04, 132 s, on the production house's channel, never transcribed before: downloaded today, transcribed locally, 179 scene frames read). That is PDQ's only video about its delivery product; its whole feature list, spoken and on screen, is 'Detailed Route Mapping', 'Facilitate Contact-less Delivery', 'Item Reminders, For Order Accuracy', 'Easy Receipt/Tip Reconciliation', 'Text Notifications With Order Status Times', 'Dedicated Driver Map Capable Of Being Displayed On A Station/Monitor (Always know where your drivers are)', 'Full Back End Reporting So You Can Easily Assess Driver Performance' and 'Complete Native integration to PDQ POS, PDQ ONLINE ORDERING, and PDQ REWARDS' - no outage behaviour. TOTAL: 166 documents, 795,976 chars (134 of them current). CONTROLS (tokenised, word-boundary, case-insensitive; positives first): 'delivery/deliveries' 51 docs / 291 hits, 'driver(s)' 22 / 141, 'dispatch*/assign*' 17 / 37, 'cash' 33 / 125 (the instrument works on the vendor's delivery vocabulary); 'offline/off-line' 0 / 0; 'redundan*' 0; 'outage(s)' 3 hits, all the SSI article line 'a system with more down time, cloud-based outages ...' (POISON: a sales argument against cloud competitors, no delivery behaviour); '(goes|went|is) down' 2, both in the RETIRED 2015 'Preparing For Your Security Package' PDF: 'a dedicated analog phone line for dial-backup This way you will not lose sales if the internet goes down' (POISON: card authorisation, not delivery; retired, so it can carry nothing here either way); 'connectivity' hits are the catalog's 'wifi/bluetooth connectivity' and the Wildwood release's SIM-card failover 'for uninterrupted processing whenever our Wi-Fi connectivity falters' (POISON: card processing). PROXIMITY: an outage/offline/internet-down/connectivity/dial-backup token within 300 chars of delivery/driver/dispatch/run occurs in ONE document only, the retired 2015 PCI PDF above ('Dedicated Dispatch screen ... you do not need a VeriFone unit ... dial-backup'), which is about card processing. The 57 transcripts carry 'internet' 0, 'offline' 0, 'outage' 0. WHAT THE PRODUCT DOES IS NOT DOCUMENTATION, recorded so a reviewer need not re-derive it: PDQ's own driver app, PDQ DT ('PDQ Delivery Toolkit', Android package com.pdqpos.pdqdelivery, listed at https://play.google.com/store/apps/details?id=com.pdqpos.pdqdelivery; APK v1.3.4, 47,158,626 bytes, sha256 52ee11e8b22d1d3f..., fetched anonymously from the APKPure mirror because Play serves no APK; never installed or run). It is a Xamarin.Forms app: its logic ships as .NET assemblies inside assemblies.blob (116 entries, LZ4/XALZ). PDQDT.dll (332,800 bytes) and PDQDT.Android.dll (451,584 bytes) were unpacked and 8,011 distinct strings read out, incl. the XAML page set and the embedded EULA (PDQDT.Content.AppTerms.txt). No prior session opened this app's code (the 327th/328th read its store listings only). It ships an 'Offline Mode!' banner (Views/OffLineMessage.xaml, bound to IsApiOffline) and status icons cloudConnected/cloudDisconnected and internetConnected/internetDisconnected; GPS fixes are written to a local SQLite queue (toolkitSQLite.db3; ProcessLocationQueue, FlagLocationItemProcessedAsync, CleanupLocationQueue) and replayed to https://wapi-dtdata-s1.mypdqpos.com/api/mobile/; but order status changes ('On Way', 'Delivered', setOrderStatusOnItsWayAsync / DeliveredAsync / AutoDeliveredAsync / CanceledAsync) are direct API calls with no local queue ('Device is not connected to the internet.'). That is shipped code, unpublished, and it covers the phone app only, not the store POS where cash, assignment and settlement happen; it does not make the vendor's documentation say anything. Grade C: marketing, legal pages and vendor videos; PDQ publishes no product documentation that could be silent. Retrieved 2026-09-18. https://www.pdqpos.com/ · retrieved 2026-09-18 adversarially verified

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

digital-first-party-web

Sole evidence is homepage marketing copy — I confirmed the verbatim strings 'built-in custom online ordering' and 'integrated online ordering' exist, so the module is real, but there is no product documentation and no statement that it is included rather than a priced add-on. Third-party listings indicate online ordering and loyalty are extra-fee modules on top of base pricing, and the 'commission-free' half of this sub-feature is nowhere stated by the vendor. A named marketing module with unknown packaging and unverified commission terms is partial, not yes. A denylisted source was also cited https://www.pdqpos.com/ · retrieved 2026-08-01 adversarially verified

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

digital-menu-single-source

Marketed as 'built-in' and 'integrated' online ordering, implying a shared menu; single-source propagation is not documented. https://www.pdqpos.com/ · retrieved 2026-08-01

Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator

digital-native-app

Verified in the cited press release: 'their brand-new mobile ordering suite' and a 'natively integrated In-Place Dining mobile app' at Live! Casino Louisiana. Partial is right — this is a property-specific casino deployment, and I found no branded per-restaurant apps in the App Store or Play Store. https://www.pdqpos.com/newsarticles.aspx?rid=PR_000_live_louisiana&nb=true · retrieved 2026-08-01 adversarially verified

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

digital-account-saved-payment

CLAIM: Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels. VERDICT partial/C. The evidence is PDQ's shared multi-tenant online ordering (*.pdqonlineordering.com), from guest sessions on 2026-09-16 (.cache/q312/pdq-pos/seam.mjs, re-driven by the verifier on passariellos, hgchesterbrookpizza and slicespizza). Nothing was registered or submitted. MET: (a) ACCOUNT. The anonymous title page reads "Not a member? Click Below to Register." on 69 of 69 tenants. The Register postback renders a form with First Name, Last Name, Phone, Cell, Email, Confirm Email, Create Password and Confirm Password on 69 of 69, and title pages carry a ForgotPassword panel on 69 of 69. (b) SAVED CARD. After the 'Credit Card' payment-method postback in a carted session, the checkout payment popup shows checkbox chkCreditSave, "Save card on file for future purchases.", with card entry in a Datacap (token.dcap.com) or Mercury (hc.mercurypay.com) hosted frame. This appears on 33 of 45 tenants that reached CheckOut.aspx (69 probed, 49 reached Menu.aspx, 45 reached checkout). (c) SAVED ORDER. CheckOut.aspx shows "Save Order As Favorite? Favorite Name:" on 43 of 45 checkouts, and Menu.aspx includes the UserFavorites control on 49 of 49 menus reached. The first pass's figure of 69 of 69 was wrong: 20 tenants stopped at OrderDetails.aspx and never reached a menu. Only the title and register text is visible to an anonymous visitor. (b) and (c) appear only inside a session with an item in the cart, and CheckOut.aspx sends a sessionless visitor to MessagePage.aspx?SessionEnded=True with a 302. SHORT: (1) SAVED ADDRESSES are not evidenced. The register form collects no address on 0 of 69 tenants, and the only address control, 'Add New Address' on OrderDetails.aspx, is the guest path. (2) ONE-TAP REORDER is not demonstrated. Saving a favourite was seen, but reordering from a favourite or from past orders could not be observed without logging in. The menu's Favorites/PastOrder switch was earlier shown to be only a CSS toggle, and tokenised 'reorder', 'past order' and 'order history' have 0 text hits. (3) 'Across first-party channels' is unshown: this is web online ordering only. (4) Evidence is the live product at grade C, with no documentation. https://passariellos.pdqonlineordering.com/ · retrieved 2026-09-16 adversarially verified

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

digital-upsell-engine

CLAIM: digital checkout presents configurable or algorithmic upsell/cross-sell suggestions, WITH attach-rate reporting on those suggestions. VERDICT: partial -- suggestive selling in the online-ordering flow is claimed by the vendor; the reporting conjunct is absent. EVIDENCE, verbatim from https://web.archive.org/web/20151223080810/http://www.pdqpos.com/online-ordering-2/, section 'BOOST THE AVERAGE CHECK': 'Implement suggestive selling to promote high margin items. The result: higher check averages and increased profits--typically 15% - 20% higher than typical phone-in orders!' SHORTFALL NAMED: (a) nothing says whether suggestions are rule-configured or personalised from order history; (b) no attach-rate or suggestion-performance report is documented on any PDQ reporting surface -- the 2016 Product Feature Summary's report column names 33 reports and none of them is an upsell, suggestion or attach report. Grade C, retired copy. Retrieved 2026-09-17. https://web.archive.org/web/20151223080810/http://www.pdqpos.com/online-ordering-2/ · retrieved 2026-09-17 adversarially verified

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

digital-scheduled-pacing

CLAIM: future/scheduled orders WITH per-daypart throttling - capacity limits per time slot that automatically close slots when the kitchen is saturated. VERDICT: partial. EVIDENCE: PDQ's own Online Ordering page states the future-order half directly - 'INCREASE REVENUE: ALLOW CUSTOMERS TO PLACE ADVANCE ORDERS 24/7/365' - and the confirmation carries a time: 'Confirmation emails to customers detailing times, order details and credit card specifics' (https://web.archive.org/web/20151223080810/http://www.pdqpos.com/online-ordering-2/). SHORTFALL (named, and it is the differentiating half): NO throttling of any kind is described. Tokenised, case-insensitive controls over the full 81-document PDQ corpus assembled this session (vendor site 2004/2015/2016/2020/2022/2026 generations, the 2016 Feature Overview, the 2024 and 2025 catalogues, the 2004 module sheets, the pci.pdqpos.com installer PDFs, both app-store listings and the pdqdt.com site) return ZERO for 'throttl', 'capacity', 'time slot', 'timeslot', 'quote time' and 'pacing'. That corpus is a marketing corpus, not a census of the product, so this is a floor, not a `no`. Retrieved 2026-09-18. https://web.archive.org/web/20151223080810/http://www.pdqpos.com/online-ordering-2/ · retrieved 2026-09-18 adversarially verified

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

digital-fulfillment-modes

Delivery, takeout, online ordering and 'contactless services' referenced; curbside arrival check-in and per-mode fee/prep config not documented. https://www.pdqpos.com/ · retrieved 2026-08-01

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

digital-qr-table

331st (slice c): NEW SURFACE - PDQ's SECOND-GENERATION guest ordering app, never read by any prior pass. The four Live! Casino & Hotel tenants (marylandlive, philadelphialive, pittsburghlive, bossierlive .pdqonlineordering.com - bossierlive is the Louisiana property the 2025 press release calls 'a mobile ordering experience ... the first of its kind') no longer run the legacy ASP.NET WebForms app: they serve a Next.js/Turbopack app footed 'Powered by PDQ Signature Systems, Inc. (c) 2026 - V 3.11'. Census: every /_next/static chunk referenced from the HTML of /, /menu, /checkout, /confirmation and a nonsense path, taken to a fixpoint (3 rounds, 49 JS chunks, 2.65 MB, 0 misses, no source maps - .js.map 404s like a nonsense sibling). Route census from the bundle's own router calls: '/', '/menu', '/checkout', '/confirmation' only; /account, /rewards, /loyalty, /orders, /profile, /signup, /login all 404 exactly like /zzz-nope (45,0xx-byte not-found page). The client's API table is a closed Object.freeze enum of ~40 endpoints (online/franchise/*, online/store/*, online/menu/*, online/order/{detail,validate,submit}, online/charge/{hostprepare,hostresult,Auth}, online/user/*, online/loyalty/{lookup,redeem,charge}, online/franchise/datakeylookup). Production JS the vendor does not publish as documentation = grade B. CLAIM: guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the POS check, including splitting and tipping. VERDICT: partial. EVIDENCE (verbatim from the shipped client): a 'KeyInputDialog' titled 'Enter Key' tells the guest 'You can scan the QR code with your device's camera or simply enter the key below.' (desktop: 'On desktop, please enter the key manually. To scan a QR code, try opening this on your mobile device.'); the scanned DataKey is resolved through online/franchise/datakeylookup and its per-location config is read as 'LOCATION.ISTABLE', 'LOCATION.PROMPTTABLE', 'LOCATION.PROMPTSEAT', 'LOCATION.ISROOM', 'LOCATION.PROMPTROOM', 'LOCATION.STOREID'; the checkout schema then requires 'Table number is required' / 'Seat number is required' / 'Room number is required' for such locations, the scanned key also scopes the menu ('AvalDataKeyGroups' / 'NotAvalDataKeyGroups', 'F_OrderDataKey' sent with the order), and checkout carries a gratuity selector ('selectedGratuity', 'selectedGratuityOption', a 'Gratuity' line on the order summary). So a guest scans a table/seat QR, orders, tips and pays, and the order is submitted to the POS tagged with that table/seat. SHORTFALLS (named): it OPENS A NEW online order (online/order/submit) - nothing attaches to an existing open POS check (tokens 'check id' 0, no open-check lookup endpoint in the closed API enum), and there is no bill splitting (tokenised 'split bill' 0, 'split check' 0; the only non-method 'split' identifiers are Next.js 'splitPathnameIntoParts' and a storage helper). Deployed on the casino tenants; the legacy pizza-tenant app has no table surface (327th CSS census). Retrieved 2026-09-18. https://marylandlive.pdqonlineordering.com/ · retrieved 2026-09-18 adversarially verified

Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator

digital-kiosk

Four kiosk SKUs plus a three-in-one POS/customer-display/kiosk unit with multiple tenders including cash. Shared menu engine implied; accessibility conformance not published. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-01

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

digital-group-ordering

331st (slice c): NEW SURFACE - PDQ's SECOND-GENERATION guest ordering app, never read by any prior pass. The four Live! Casino & Hotel tenants (marylandlive, philadelphialive, pittsburghlive, bossierlive .pdqonlineordering.com - bossierlive is the Louisiana property the 2025 press release calls 'a mobile ordering experience ... the first of its kind') no longer run the legacy ASP.NET WebForms app: they serve a Next.js/Turbopack app footed 'Powered by PDQ Signature Systems, Inc. (c) 2026 - V 3.11'. Census: every /_next/static chunk referenced from the HTML of /, /menu, /checkout, /confirmation and a nonsense path, taken to a fixpoint (3 rounds, 49 JS chunks, 2.65 MB, 0 misses, no source maps - .js.map 404s like a nonsense sibling). Route census from the bundle's own router calls: '/', '/menu', '/checkout', '/confirmation' only; /account, /rewards, /loyalty, /orders, /profile, /signup, /login all 404 exactly like /zzz-nope (45,0xx-byte not-found page). The client's API table is a closed Object.freeze enum of ~40 endpoints (online/franchise/*, online/store/*, online/menu/*, online/order/{detail,validate,submit}, online/charge/{hostprepare,hostresult,Auth}, online/user/*, online/loyalty/{lookup,redeem,charge}, online/franchise/datakeylookup). Production JS the vendor does not publish as documentation = grade B. CLAIM: group ordering - a shareable link where multiple participants add their own items to one order under a spend cap, with split or single payment. VERDICT: no. BOUND: PDQ's guest ordering is now censused in BOTH of its first-party clients: (1) the legacy WebForms app (327th: 13 pages across all 210 Wayback tenant hosts, 7 first-party scripts, no bundler/loader, no share/join/participant route), and (2) this second-generation Next.js app, whose whole client is held (49 chunks at a fixpoint, 0 misses) and whose router knows only /, /menu, /checkout, /confirmation. A group order is intrinsically a client feature (a share link, a join route, per-participant carts); neither client has one. The publisher's app-store census (iTunes artistId 1218876301 and Google Play 'Signature Systems, Inc': MY PDQ reporting + PDQ DT driver app only; 327th/328th) shows no separate consumer ordering app where it could live. CONTROLS (tokenised on camelCase/underscore/punctuation, case-insensitive, over the 2.65 MB bundle, 541,617 tokens): 'group order' 0, 'order together' 0, 'invite' 0, 'participant' 0, 'split bill' 0, 'split check' 0. KNOWN-POSITIVE controls on the same corpus: 'loyalty' 344, 'gratuity' 59, 'seat' 75, 'room' 271 - the reader works. POISON FOUND AND EXCLUDED: 'group' 199 is menu 'MainGroups'/'GroupID', Radix 'RovingFocusGroup' and Tailwind 'group' classes; 'join' 155 is Array.join plus the constant JOIN_GO:'online/loyalty/lookup' (a loyalty lookup, not a group join); 'share' 8 is React's ViewTransition 'share'/'onShare' internals and a JSON-schema error string. WEAKEST POINT: a server-side feature cannot be excluded by a client census, but a group order has no server-only form; if the OWNER reads a two-client census as short of the product, hold unknown with this note. Retrieved 2026-09-18. https://marylandlive.pdqonlineordering.com/ · retrieved 2026-09-18 adversarially verified

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

digital-catering-portal

Scope: PDQ Signature Systems' own multi-tenant online-ordering platform (*.pdqonlineordering.com, 'Powered by PDQ Signature Systems' on 69 of 69 captured Menu.aspx pages) ONLY. This is not a finding about the PDQ POS terminal, whose catering handling is scored separately under order-capture-catering and remains unknown. Retrieval: read-only guest sessions 2026-09-14; nothing was carted and Checkout was never opened. FINDING, per conjunct. (1) No distinct catering flow: the order-type step (OrderDetails.aspx) offers no catering order type on any of 5 tenants enumerated, including three whose menus sell catering (lavillaromapizza, bluebellpizza and hgchesterbrookpizza offer only Delivery and Pickup; passariellos and wallyspizza offer 'Delivery', 'Pickup' and 'Curbside Pickup'). The set is tenant-configured, since Curbside appears on some tenants only. (2) Catering menus and minimums are operator prose, not rules: 25 of 69 captured menus contain the word catering (or a variant), always as a section name or item copy in the ordinary menu, cart and checkout (passariellos: 'Catering Appetizers', 'Catering Sandwich Platters', 'Catering Entree's'). Minimums appear only as text such as '10 Items minimum' (denirospizza) and '15 Personal Minimal For Packages' (littleangelospizza). (3) Lead time is also text only: 'While every attempt will be made to prepare short notice catering orders, we recommend 24-48 hours notice to assure that we can accommodate you.' (lavillaromapizza). (4) No quote or proposal step was found on the storefront, and several operators send catering off the platform: 'CATERING (MUST CALL TO PLACE ORDER)' with 'COPY AND PASTE URL BELOW FOR CATERING MENU:' (anthonys7); 'Please contact the store and ask for a manager to place a catering order.' (originaldominickspizza). (5, 6) Deposits and invoice, house-account or ACH terms are excluded by PDQ's platform-wide On-Line Ordering Terms & Conditions (SSIPolicies.html, byte-identical on five tenants; agreement between the guest and 'Signature Systems, Inc. and the restaurant'). s.4(d): 'Payment for the Online Ordering Services may only be made using Visa, MasterCard, Discover, and American Express credit cards, Apple Pay and Google Pay.' s.6(a): 'Your credit card will be charged one hundred percent (100%) of the price of the total order amount' ... 'once the online order is submitted.' The document never mentions deposits, invoices, ACH or house accounts. Not a catering flow: steakandhoagiefactory's coupon '10% Off your next catering order of $100.00 or more' is a discount; pdqpos.com's mobile-reporting page lists alerts when 'large catering orders are placed', which is POS alerting; 'Caterease' appears only on a third party's (Yellow Dog Software) integration help pages. PDQ's 2025 Product Catalog contains no catering entry. NOT ESTABLISHED / RISKS: Checkout.aspx was not inspected; the order-type step was enumerated on 5 of 69 tenants, and because order types are tenant-configured, an unseen tenant could differ; PDQ could sell an unpublished catering module or take catering on the POS. Grade C: live storefront behaviour, with vendor legal terms supporting the payment conjuncts. https://passariellos.pdqonlineordering.com/ · retrieved 2026-09-14 adversarially verified

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

digital-voice-ai-phone

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Digital ordering is claimed, never shown. Both sites market "custom Online Ordering" / "natively integrated online ordering" as a first-party module, and the 2025 press releases add a "natively integrated 'In-Place Dining' mobile app" and, for Live! Casino & Hotel Louisiana, "a mobile ordering experience ... the first of its kind in the nation". No ordering site, demo, screenshot or documentation of that module is published anywhere, so guest accounts and saved payment, upsell engines, scheduled-order pacing, QR table ordering, group ordering, catering portals, AI voice or drive-thru ordering, Google Order and Apple Business Connect listings, subscriptions, promo parity across channels, checkout PCI/SCA handling and surcharge transparency all rest on nothing. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice d): NEW, third-party check. Web searches for PDQ with ConverseNow, Kea, Loman, VOICEplug, Certus, SoundHound returned no voice-AI vendor naming PDQ as an integrated POS. Flipdish (which now sells an 'AI Phone Agent') once had a PDQ POS integration page (Wayback captures 2022-10-03..2024-01-31); today it 301s to flipdish.com/us/integrations, whose POS list no longer names PDQ - a retired third-party partner card, not evidence either way. Vendor corpus: 'voice' hits are 'Voice Over IP (VoIP) line' (PCI checklist) and 'the voice of' (an award article) - POISON; no AI phone ordering in any PDQ document. Retrieved 2026-09-18. || 333rd: 333rd (slice d): NEW, the vendor's video corpus checked per cell. PDQ's channel has 45 uploads (yt-dlp flat listing of @PDQPOS videos+shorts today). Caption tracks for 20 of them, including the 58-minute webinar 'Making Dollars & Sense Out of Delivery' (CUqcUlcds3A), the Pizza Expo, Pizza & Pasta Show and TribalNet talks, and the Sycuan interview, were grepped for voice/phone/AI vocabulary. The phone content is staff taking call-in orders ('phone in', 'call center' ads 3n8ne1qF3aY/obMeKMtdc7A), the 'Call Center' product, and a customer calling support. 'AI' occurs only in yz3p_Ibnu9c, where Sycuan's VP speaks generally ('everyone's looking at AI'). No AI voice agent, answering service or named voice partner occurs. 25 uploads have no captions (transcripts disabled or blocked). Held unknown. Retrieved 2026-09-18. adversarially verified

Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.

digital-drivethru-ai

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Digital ordering is claimed, never shown. Both sites market "custom Online Ordering" / "natively integrated online ordering" as a first-party module, and the 2025 press releases add a "natively integrated 'In-Place Dining' mobile app" and, for Live! Casino & Hotel Louisiana, "a mobile ordering experience ... the first of its kind in the nation". No ordering site, demo, screenshot or documentation of that module is published anywhere, so guest accounts and saved payment, upsell engines, scheduled-order pacing, QR table ordering, group ordering, catering portals, AI voice or drive-thru ordering, Google Order and Apple Business Connect listings, subscriptions, promo parity across channels, checkout PCI/SCA handling and surcharge transparency all rest on nothing. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice d): NEW, per-cell grep of 84 PDFs re-extracted with pdftotext. Every PDQ drive-thru reference is HARDWARE/KIOSK and from 2015-2018 documents ('Self-Serve, Drive-Thru Kiosks', 'Drive-thru equipment', 'Count the number of screens you have for the drive-thru'); the current 2025 catalogue has 0 drive-thru hits, and 'voice' never occurs beside drive-thru in any PDQ document. No drive-thru voice AI is described. Held unknown (capability not bounded by a marketing census). Retrieved 2026-09-18. || 333rd: 333rd (slice d): NEW SURFACE, the vendor's only drive-thru product video. 'Self-service Drive-Thru Kiosk' (youtube WJl-rwtWvTw, uploaded 2016-10-14, 'New from PDQ POS: Self-service, drive-thru kiosks!') was read at 1080p, 83 scene frames. It is a TOUCH kiosk on a lane pedestal (Jimmy John's menu). The driver taps items, modifier grid ('Add Extras', 'Modify', 'Light'/'None'), 'How Many Of This Item Would You Like?', 'Would You Like To Order Another Item?', then 'Finish & Pay' with Gift Card or Credit Card. There is no microphone, voice prompt or speech UI, and no hand-off to staff. It has no captions track (transcripts disabled). Of PDQ's 45 channel uploads (@PDQPOS videos+shorts listed with yt-dlp today), 20 caption tracks were grepped (.cache/q333/pdq-pos/d/tx). None mentions voice ordering at a drive-thru. AI is mentioned only by a casino VP describing his own industry (yz3p_Ibnu9c). An adjacent touch-kiosk feature is not a partial. Held unknown: a video census does not bound a capability. Retrieved 2026-09-18. adversarially verified

Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.

digital-sms-ordering

SMS is used for outbound customer notifications only; no text-to-order capability is described. || 328th: MERGE HOLD (proposed no/C, held unknown): The bound is a 3-page 2020 leaflet recovered from Wayback (retired host) plus a corpus the 327th itself called thin; a retired document may not carry a `no` (320th rule) and PDQ's back-office docs are unpublished. The closed three-notification SMS enumeration is kept as the bound. PROPOSAL AS WRITTEN: 328th (WEB/DOCUMENT SLICE): NEW SURFACE and a proposed move to no. CLAIM: supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS. VERDICT: no, grade C. THE SURFACE: the vendor's only dedicated document about its SMS feature, the 3-page 'PDQ DELIVERY TOOLKIT(R)' FAQ leaflet, (c)2020 SIGNATURE SYSTEMS, INC. (pdqdt.com/wp-content/uploads/2020/04/Delivery-Toolkit-LF.pdf, now 404 on the live host, recovered from Wayback; not present in any q324-q327 corpus). It contains a section headed 'What functions does the SMS (texting) feature have?' whose enumeration of the feature is CLOSED: 'If the customer selects to receive SMS messages, there are numerous options:' followed by exactly three bullets -- 'Send a text when the driver leaves the store'; 'Automatically send a text when the driver selects "On Way" in the app (in the case of multiple deliveries from the same driver)'; 'Automatically send a text when the driver selects "delivered" and it is a CONTACTLESS DELIVERY...' -- all three OUTBOUND notifications. The same section then says 'SMS is seamlessly integrated across the entire PDQ POS platform, so it also works for Call-In Orders and Online Orders!', i.e. SMS is applied to orders captured by phone or web, never a channel an order arrives on. BOUND/CONTROLS: tokenised, case-insensitive, word-boundary controls over every PDQ corpus on disk (701 files, 90.3 MB, .cache/q324|q325|q326|q327|q328/pdq-pos*: the pdqpos.com and ssipos.com WordPress censuses taken to 100% of wp/v2/types, the pdqdt.com pages, the PCI subdomain, the live pdqonlineordering.com ordering app and its scripts, the PDF library, the app-store listings, and my new additions -- this leaflet, the 2018 'About PDQ Signature Systems' capability statement, the 20-page 2025 product catalogue and 30 PDQ YouTube video titles+descriptions): 'text[- ]to[- ]order' 0, 'text[- ]a[- ]link' 0, 'order(ing)? (by|via|through) (text|SMS)' 0, 'chat ?bot' 0, 'text (us )?your order' 0, 'two-way (text|SMS|messag)' 1, 'conversational' 0. POISON FOUND AND EXCLUDED: every apparent hit for 'text to order', 'text-a-link' and 'conversational' was inside THE ATLAS'S OWN FILES (q326/q327 claimtext.txt, claims-short.txt, unknowns.json, and corpus.tsv which ingests them) -- i.e. my own control vocabulary, not the vendor's; the single 'two-way text' and 'reply <KEYWORD>' hits are inside a Google Play / iTunes SEARCH RESULT page for OTHER publishers' apps, not PDQ's. Denominator on a known-positive control: 'SMS' 318 hits in 58 files, 'surcharge' 182 in 10, 'delivery' 7,053 in 315 -- the corpus is demonstrably rich in PDQ's own SMS and ordering-channel vocabulary, which is what makes the zero meaningful. WEAKEST POINT, stated honestly: the corpus is a census of PDQ's PUBLICATION surface, not of the product, and the SMS enumeration is six years old; if the OWNER holds this to the 327th's rule that a capability no needs a census of the product's own docs, hold it as unknown with this note. Retrieved 2026-09-18. || 333rd: 333rd (slice d): NEW SURFACE, a CURRENT vendor source (the 328th's bound was a retired 2020 leaflet). PDQ's 'PDQ POS Mobile Ordering Now Available' (youtube zX9EUPItKsE, uploaded 2025-11-20, 1080p, 64 scene frames read) is the vendor's feature montage for its current mobile ordering. Its title cards are 'Mobile Ordering', 'Safe & Secure', 'Player Points & Comps Compatible', 'Full POS Integration', 'Order From Anywhere', 'Accurate Order Locations', 'Text Confirmation & Notifications', 'In-Room Ordering', 'Mobile Ordering Only From SSI'. The only SMS feature is OUTBOUND: the phone on screen shows a received text 'Your Ocean Food Truck Order #1190 is Ready For Pickup ...'. Orders are started by scanning a QR code into the web client (Ocean Casino Resort food truck and in-app), never by texting. V2 client (all 9 tenants, one build): the only 'sms' token is the URI-scheme whitelist of the bundled sanitiser '(?:f|ht)tps?|mailto|tel|callto|sms|cid|xmpp|matrix' (POISON), and 'optin' is Zod's schema flag (POISON). Held unknown: a marketing montage is not an enumeration of the SMS feature, and PDQ's back-office docs are unpublished (the 328th hold stands). Retrieved 2026-09-18. adversarially verified

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

digital-google-order

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Digital ordering is claimed, never shown. Both sites market "custom Online Ordering" / "natively integrated online ordering" as a first-party module, and the 2025 press releases add a "natively integrated 'In-Place Dining' mobile app" and, for Live! Casino & Hotel Louisiana, "a mobile ordering experience ... the first of its kind in the nation". No ordering site, demo, screenshot or documentation of that module is published anywhere, so guest accounts and saved payment, upsell engines, scheduled-order pacing, QR table ordering, group ordering, catering portals, AI voice or drive-thru ordering, Google Order and Apple Business Connect listings, subscriptions, promo parity across channels, checkout PCI/SCA handling and surcharge transparency all rest on nothing. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice d): NEW, per-cell check of both PDQ ordering clients. Google's ordering-redirect partners must carry the rwg_token conversion parameter through the ordering flow; 'rwg_token' is 0 across the V2 Next.js client (49 chunks, fixpoint), the legacy WebForms storefront renders (q312, 26 tenants) and every other pdq corpus on disk; 'order with google', 'reserve with google', 'google business' are 0 vendor hits. The only Google surface in the client is an outbound directions link (GOOGLE_MAP_LINK 'https://www.google.com/maps/dir/?api=1&destination'). Google's public partner page (google.com/maps/reserve/partners, 428 names) is a RESERVATIONS list and cannot bound food ordering. Not a no: a merchant can paste its PDQ ordering URL into Google Business Profile by hand, and whether PDQ provisions it is unpublished. Retrieved 2026-09-18. adversarially verified

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

digital-apple-business-connect

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Digital ordering is claimed, never shown. Both sites market "custom Online Ordering" / "natively integrated online ordering" as a first-party module, and the 2025 press releases add a "natively integrated 'In-Place Dining' mobile app" and, for Live! Casino & Hotel Louisiana, "a mobile ordering experience ... the first of its kind in the nation". No ordering site, demo, screenshot or documentation of that module is published anywhere, so guest accounts and saved payment, upsell engines, scheduled-order pacing, QR table ordering, group ordering, catering portals, AI voice or drive-thru ordering, Google Order and Apple Business Connect listings, subscriptions, promo parity across channels, checkout PCI/SCA handling and surcharge transparency all rest on nothing. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd (slice d): NEW, per-cell check. The only Apple Maps reference in PDQ's V2 ordering client is an outbound directions link (APPLE_MAP_LINK 'https://maps.apple.com/?q'); 'business connect' and 'apple maps' otherwise 0 across 4,380 text files in 18 pdq corpora. No PDQ document mentions an 'Order Food' action. Held unknown (an operator can configure an Apple action link without the vendor). Retrieved 2026-09-18. adversarially verified

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

digital-loyalty-attach

'PDQ Rewards' built-in loyalty plus built-in online ordering implies shared identity; not documented. https://www.pdqpos.com/ · retrieved 2026-08-01

Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.

digital-subscriptions

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Digital ordering is claimed, never shown. Both sites market "custom Online Ordering" / "natively integrated online ordering" as a first-party module, and the 2025 press releases add a "natively integrated 'In-Place Dining' mobile app" and, for Live! Casino & Hotel Louisiana, "a mobile ordering experience ... the first of its kind in the nation". No ordering site, demo, screenshot or documentation of that module is published anywhere, so guest accounts and saved payment, upsell engines, scheduled-order pacing, QR table ordering, group ordering, catering portals, AI voice or drive-thru ordering, Google Order and Apple Business Connect listings, subscriptions, promo parity across channels, checkout PCI/SCA handling and surcharge transparency all rest on nothing. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 331st: 331st (slice c): NEW SURFACE - PDQ's SECOND-GENERATION guest ordering app, never read by any prior pass. The four Live! Casino & Hotel tenants (marylandlive, philadelphialive, pittsburghlive, bossierlive .pdqonlineordering.com - bossierlive is the Louisiana property the 2025 press release calls 'a mobile ordering experience ... the first of its kind') no longer run the legacy ASP.NET WebForms app: they serve a Next.js/Turbopack app footed 'Powered by PDQ Signature Systems, Inc. (c) 2026 - V 3.11'. Census: every /_next/static chunk referenced from the HTML of /, /menu, /checkout, /confirmation and a nonsense path, taken to a fixpoint (3 rounds, 49 JS chunks, 2.65 MB, 0 misses, no source maps - .js.map 404s like a nonsense sibling). Route census from the bundle's own router calls: '/', '/menu', '/checkout', '/confirmation' only; /account, /rewards, /loyalty, /orders, /profile, /signup, /login all 404 exactly like /zzz-nope (45,0xx-byte not-found page). The client's API table is a closed Object.freeze enum of ~40 endpoints (online/franchise/*, online/store/*, online/menu/*, online/order/{detail,validate,submit}, online/charge/{hostprepare,hostresult,Auth}, online/user/*, online/loyalty/{lookup,redeem,charge}, online/franchise/datakeylookup). Production JS the vendor does not publish as documentation = grade B. WHAT IT HOLDS FOR THIS CELL: zero subscription surface in the guest client - tokenised 'subscription' 0, 'membership' 0, 'recurring' 0 (the 32 'subscribe' tokens are state-store/React-Query onSubscribe internals); no plan or entitlement endpoint in the closed API enum. Not scored no: a membership 'managed in the platform' could be sold at the POS or back office, which no guest-client census bounds. Retrieved 2026-09-18. || 333rd: 333rd (slice d): NEW, extends the 331st's four-casino read to every V2 tenant. TENANT CENSUS (new this session): GET / on all 209 tenant slugs in the Wayback-derived list (.cache/q331/pdq-pos/c/tenants.txt): 200 legacy WebForms, 7 V2 Next.js (bossierlive, marylandlive, philadelphialive, pittsburghlive, plus three PIZZA tenants no prior pass saw on V2: mygiaspizza, slicespizzapa, trianospizza), 1 redirect off-domain (domspizza), 1 403 (admin). Two more V2 tenants absent from the Wayback list were found by name probe (oceancasino, sycuan; *.pdqonlineordering.com is a wildcard cert, so certspotter cannot enumerate tenants). All 9 V2 tenants serve the IDENTICAL chunk set (same md5 over the sorted chunk list), and every chunk is inside the 331st 49-chunk fixpoint (.cache/q331/pdq-pos/c/chunks): there is one V2 build, not a newer one on other tenants. Each V2 page embeds the franchise config in its RSC payload (36 keys, same schema on all 9; .cache/q333/pdq-pos/d/v2-config.json). The only membership-shaped keys in the 36-key franchise config are 'API.ALLOWREWARDSENROLL' (True on trianospizza and oceancasino only) and 'GLOBAL.ALLOWUSERENROLL' (account creation). There is no subscription, membership, recurring-billing or plan key, and the one client build has no such route (331st). The 2025 mobile-ordering video's feature cards (youtube zX9EUPItKsE) name 'Player Points & Comps Compatible' and no subscription. Held unknown: a storefront census does not bound the back office. Retrieved 2026-09-18. adversarially verified

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

digital-promo-parity

CLAIM: discounts, coupon codes and loyalty offers defined once and honoured identically across POS, kiosk and first-party digital, with channel eligibility controls. VERDICT: partial. EVIDENCE: PDQ's Online Ordering page says promotions are managed inside the same product as the POS menu - 'INCREASE EFFICIENCY: EASILY MAINTAIN MENUS AND TRACK RESULTS THROUGH ONE INTERFACE. There's no new software to learn and you'll have ONE point of contact for both your POS and Online Ordering' - and, in its Nuts & Bolts list, 'COUPONS AND DAILY SPECIALS ARE ALL MANAGED' (https://web.archive.org/web/20151223080810/http://www.pdqpos.com/online-ordering-2/). The definition surface is the POS back office: 'Coupons by items, departments and condition', 'Offers and discounts', 'Coupon manager', 'Coupon sales summary' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf), and the vendor repeatedly stresses that online ordering, rewards and kiosks are NATIVE rather than bolt-ons: 'native online ordering, native rewards/loyalty' (https://web.archive.org/web/20250121221212/https://www.pdqpos.com/wp-content/uploads/2020/12/PR_JJ-DoorDash3.pdf). SHORTFALLS (named): 'honoured identically' is inferred from shared management rather than stated, and CHANNEL ELIGIBILITY CONTROLS - restricting an offer to one channel - appear nowhere; the only coupon conditioning named is 'by items, departments and condition'. Retrieved 2026-09-18. https://web.archive.org/web/20151223080810/http://www.pdqpos.com/online-ordering-2/ · retrieved 2026-09-18 adversarially verified

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

digital-guest-data-ownership

332nd (slice d): CLAIM: vendor DOCUMENTS that the operator owns and can export first-party guest records (email, phone, consent status, order history) in bulk, without a fee or vendor approval. This is a documentation claim, so it is settled by a publication census (the same instrument that carried this record's merged commercial-post-termination-export-window no/B and commercial-no-early-termination-fee no/B). VERDICT: no, grade B (vendor legal documents). NEW SURFACE: the guest-facing legal document that actually governs PDQ's online-ordering guest data, which no prior note on this cell cites: the 'On-Line Ordering Terms & Conditions' served on every legacy tenant at /SSIPolicies.html (live today: passariellos.pdqonlineordering.com/SSIPolicies.html 200, 5,666 B; nonsense sibling /zzz-nope-332.html 404, 103 B; same text as the q261 copy). It does NOT allocate guest data to the operator; it makes the vendor and the restaurant ONE joint party: 'The Online Ordering Terms are between you and Signature Systems, Inc. and the restaurant utilizing the Online Ordering Services (hereinafter "we" or "us")', and 'As you are checking out as a guest, you can opt in to receive communications from Us ... We may use the information you provide', 'The only third parties with whom We will share your information are ... Third-Party Service Providers', 'We will never sell your information.' The V2 (Next.js) client on the Live! casino tenants carries only an inline summary: 'We collect your name, email, phone number, and order data to process your order and improve our services ... We do not sell your information.' Neither says the operator owns the records, and neither mentions export. PUBLICATION CENSUS (re-derived by the 331st/332nd, not inherited): www.pdqpos.com is one page (110,961 B, 29 hrefs) whose legal set is exactly termsofuse.aspx (governs the WEBSITE), privacypolicy.aspx (site visitors) and smsprivacypolicy.aspx; /termsofsale 404 against a nonsense control, so the merchant Terms of Sale the Terms of Use incorporates is unpublished; ssipos.com WP REST pages 8 / posts 5 / media 216 with core types only; pdqdt.com serves the pdqpos page; no sitemap, docs, KB or developer host (crt.sh set). CONTROLS (tokenised, word-boundary, case-insensitive, over 4,380 text files / 406 MB in 18 on-disk pdq corpora incl. 84 PDFs re-extracted with pdftotext this session; KNOWN-POSITIVE 'terminat*' 267 hits in 146 files): '(you|operator|merchant|restaurant|owner) (own|retain|keep) (the|your|their) (customer|guest|data)' 0; 'data ownership|ownership of (the|your) data|owner of the data|belongs to you' 0 vendor documents (the only hit is our own control file); 'export (your|the|all|customer|guest) (data|customers|list|records)|data export|bulk export' 0 vendor documents (hits are the PCI SSC listing's 'Export List' button and our own pipeline files - POISON); 'portab*' 0 vendor statements. 'hostage' 18 files: 17 are the SSI Security brochure ('hold infrastructures hostage'), and 1 is PDQ's podcast page describing a COMPETITOR episode ('Holding your data hostage', audio-only on SoundCloud, not transcribable here) - spoken competitor marketing, not a documented PDQ term. WEAKEST POINT: the merchant Terms of Sale is private (incorporated by reference, 404); if the owner treats an unpublished incorporated contract as blocking a documentation no, hold unknown with this note. 'Customer Data Management (CDM) reporting suite' (2025 press releases) is a reporting product, not an ownership/export term. Retrieved 2026-09-18. https://passariellos.pdqonlineordering.com/SSIPolicies.html · retrieved 2026-09-18 adversarially verified

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

digital-checkout-pci-sca

CLAIM: digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance including the client-side script-integrity requirements effective March 2025, and supporting 3DS. This is a conjunction and its publication conjunct is stated explicitly in the claim, so a demonstrated publication failure makes the conjunction false. 3DS 0, 3-D Secure 0, 3D Secure 0, SCA 0, strong customer authentication 0, script integrity 0, 6.4.3 0, 11.6.1 0, hosted payment 0, hosted field 0, 4.0 0, 4.0.1 0. The citation is disclosed for what it is: the brochure is the vendor's maximal security disclosure and says nothing whatever about e-commerce payment pages, and the checkout surface itself is unpublished -- Signature Systems owns a dedicated online-ordering domain, pdqoo.com, and it 301s to the POS marketing home page. This verdict is about the claim, not about whether PDQ's checkout is secure. Scope, stated so the company and the product are not conflated: the vendor itself makes the certification company-scoped. The ssipos.com home page says PCI DSS Level 1 Compliant Service Provider, and Signature Systems' own 2022-12 article advises buyers to select a provider that is PCI DSS compliant as a company. A service-provider compliance status is not a product attestation, and it is not used here to settle any product-scoped conjunct. Estate bounding, re-probed independently rather than inherited: pdqsecurity.com, pdqtek.com and pdqoo.com all 301 to the pdqpos.com marketing home page (pdqsecurity.com and pdqoo.com direct to https://pdqpos.com on both http and https; pdqtek.com via an http://pdqpos.com hop), and a deep path on pdqsecurity.com and on pdqtek.com returns a zero-length 404, so none of the three serves any content of its own; the www. host of each does not resolve, as does a deliberately fabricated control host, so a DNS failure is distinguishable from a redirect. The pdqpos.com Terms of Use names those four pdq domains but does not name ssipos.com, so the Terms are not the estate enumeration. The reachable published estate is two hosts: pdqpos.com, which is one marketing home page, two ProjectDetail pages, four newsarticles pages, three legal pages and the 2025 Product Catalog PDF, with no robots.txt and no sitemap.xml and no /security, /pdqsecurity, /trust or /compliance path; and ssipos.com, a WordPress site whose REST manifest is strictly larger than its sitemap. A fabricated path 404s hard on both hosts, but pdqpos.com also has a soft-200 shape -- https://www.pdqpos.com/newsarticles returns HTTP 200 carrying a Page Not Found body -- so path probes on that host must be read from the body and not the status. Vintage, and the newer-surface hunt that tests it: the brochure is dated 2022-05-19, PCI DSS v4.0.1 was published June 2024 and its future-dated requirements became enforceable 31 March 2025, so this document cannot carry a 4.x statement as a matter of chronology. That argument is only as good as the search for a newer surface, and that search corrects an earlier assertion that the newest security-bearing artefact is the 2025 Product Catalog: Signature Systems publishes press releases through GlobeNewswire and pdqpos.com links only four of them. The newest, 2026-08-19, together with the 2026-03-30 and 2025-02-26 releases, carries the same corporate boilerplate whose only security clause is the versionless phrase full PCI DSS compliance, with no SOC 2, no ISO 27001, no version number, no attestation, no P2PE and no tokenization. ssipos.com has no /trust/, /compliance/ or /security/ page, all three 404, and its media library ends at 2023-11-13. As of 2026-09-15 no 2024-2026 compliance surface exists anywhere on or off the estate. Controls were run tokenised with both word boundaries, and as a left-boundary stem where morphology matters, over 76 document-instruments -- 13 PDFs in two extractions each, the brochure in three, 24 HTML documents held both raw and tag-stripped after HTML-comment removal, and the media census -- which is 37 distinct documents. Positive controls on the same run: the 1937, SSI 845, POS 683, security 260, PCI 136, DSS 51. Poison published: whitespace-squashed substring matching is unusable on its own -- SCA 161 (a substring of casino, Cordish and landscape), ROC 116, RTO 113, RPO 98, v4 91, SLA 53, QSA 20, AOC 11, MFA 6, every one of which tokenises to 0. Two traps tokenisation does not cure: break returns 146 word-boundary hits of which 144 are CSS line-break and word-break declarations in inline styles on the ssipos.com podcasts page, which also carries 144 of the 148 iframe hits; and the bare word token returns 80 hits, every one an ASP.NET __RequestVerificationToken or cookie-consent token in raw pdqpos.com markup and none of them payment tokenization, so only the stem tokeni, which reads 0, is a usable instrument for this vendor. Extraction instrument: the brochure was re-extracted three ways and the invariance reproduced -- pdftotext -layout, pdftotext plain and pdftotext -raw yield an identical token vocabulary with an empty symmetric difference in all six pairwise directions, an identical single-letter-token count of 15 in all three, and five phrase controls present in all three, so on this multi-column document neither the intra-word-space fault nor the adjacent-column-interleave fault fired. The vocabulary size is a reader artefact and is deliberately not published as a figure: one reader counts 322 tokens and another 312 over the same three files; the invariance is the control. Media census and declared residue: ssipos.com wp-json media X-WP-Total is 216, and the per_page=100 HTTP 500 sits on a record and moves with the sort key, so 212 records were recovered by unioning eight orderings. The residue of 4 was then closed by mime filtering rather than by inference: X-WP-Total is 201 for media_type=image (115 png plus 86 jpeg), 2 for video, 13 for media_type=application and 12 for mime_type=application/pdf, and 201+2+13 is exactly 216, so the type census is closed; mime_type=application/pdf&per_page=100 returns all twelve PDFs in a single page with no 500, which makes the twelve-PDF corpus a census rather than a floor. The four unreachable records are therefore two png, one jpeg and one non-PDF application/* file of unknown type, and that single non-PDF file is the declared hole. X-WP-Total for after=2023-12-01 is 0, which bounds the whole library, residue included, to on or before 2023-11-13. https://ssipos.com/wp-content/uploads/2022/05/SSI-Security.pdf · retrieved 2026-09-15 adversarially verified

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

digital-surcharge-transparency

328th (WEB/DOCUMENT SLICE): NEW SURFACE, and it moves the cell off unknown. The surface is a vendor-authored 3-page product FAQ leaflet, 'PDQ DELIVERY TOOLKIT(R) - Essential Resources to Enhance Your Delivery Operations', (c)2020 SIGNATURE SYSTEMS, INC., which was published on pdqdt.com (/wp-content/uploads/2020/04/Delivery-Toolkit-LF.pdf), is GONE from the live pdqdt.com (that host no longer runs WordPress: /wp-json/wp/v2/types, /sitemap_index.xml and the uploads path all 404 today), and survives only in Wayback. It is not in any q324-q327 corpus (grep for 'Dedicated Driver Map' over .cache/q32*/pdq-pos*/ returns only my own copy). CLAIM: digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. VERDICT: partial, grade C. EVIDENCE, verbatim from the leaflet's 'ADDITIONAL INFORMATION / Convenience Fee/CC Surcharge' section: 'We support a convenience fee that can be added to every online order. While the fee structure is up to the owner/operator, it's typically a small amount that covers any additional fees that are incurred (e.g., cell provider imposed SMS fees, delivery toolkit services, etc.).' and 'Since so much credit card traffic is now driven to online rather than to call-in orders, we also support the ability to add a credit card surcharge to the order. This would help cover additional processing fees occurred when running ecommerce transactions vs MOTO (mail order/telephone order). We can also add a surcharge fee to the POS system, if you want to offset some of those costs as well.' WHY PARTIAL, NOT YES: that last sentence is the claim's FIRST conjunct stated by the vendor in its own words -- the same card-surcharge configuration exists in the digital channel and in the POS, and per-order convenience fees are configurable online -- but the leaflet says nothing about a guest-facing disclosure, nothing about card-brand or debit/prepaid exclusion, and nothing about jurisdictions where surcharging is prohibited; the fee structure is explicitly left 'up to the owner/operator'. Grade C: a product leaflet is marketing-grade, and it is from 2020. Retrieved 2026-09-18. https://web.archive.org/web/20230127020820id_/https://pdqdt.com/wp-content/uploads/2020/04/Delivery-Toolkit-LF.pdf · retrieved 2026-09-18 adversarially verified

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

guest-loyalty-unified-profile

'PDQ Rewards' plus a cloud 'Customer Data Management (CDM) reporting suite' implies a unified guest record; merge/dedup behavior undocumented. https://www.pdqpos.com/ · retrieved 2026-08-01

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

guest-loyalty-thirdparty-identity-attach

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Loyalty exists as a named module and is otherwise undescribed. Both sites market "PDQ Rewards" / "built-in loyalty/rewards", "Rewards" is a top-level item on the back-office nav bar in the 2019 reporting screenshot, and the 2025 catalog says the MSR card reader "can be integrated with virtually any loyalty option". Third-party loyalty vendors -- Paytronix, JOINGO, GiveX -- appear in ssipos.com's integration list. That is the whole of it. Accrual models, tiers, offline behaviour, stacking rules, targeting, RFM segmentation, lifecycle automation, campaign attribution, member-data export, review routing, referrals, wallet passes, redemption-fraud controls and AI offer recommendation are described nowhere, and the presence of third-party loyalty partners in the integration list cuts against reading the native module as deep. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 331st: 331st (slice c): NEW SURFACE - PDQ's SECOND-GENERATION guest ordering app, never read by any prior pass. The four Live! Casino & Hotel tenants (marylandlive, philadelphialive, pittsburghlive, bossierlive .pdqonlineordering.com - bossierlive is the Louisiana property the 2025 press release calls 'a mobile ordering experience ... the first of its kind') no longer run the legacy ASP.NET WebForms app: they serve a Next.js/Turbopack app footed 'Powered by PDQ Signature Systems, Inc. (c) 2026 - V 3.11'. Census: every /_next/static chunk referenced from the HTML of /, /menu, /checkout, /confirmation and a nonsense path, taken to a fixpoint (3 rounds, 49 JS chunks, 2.65 MB, 0 misses, no source maps - .js.map 404s like a nonsense sibling). Route census from the bundle's own router calls: '/', '/menu', '/checkout', '/confirmation' only; /account, /rewards, /loyalty, /orders, /profile, /signup, /login all 404 exactly like /zzz-nope (45,0xx-byte not-found page). The client's API table is a closed Object.freeze enum of ~40 endpoints (online/franchise/*, online/store/*, online/menu/*, online/order/{detail,validate,submit}, online/charge/{hostprepare,hostresult,Auth}, online/user/*, online/loyalty/{lookup,redeem,charge}, online/franchise/datakeylookup). Production JS the vendor does not publish as documentation = grade B. WHAT IT HOLDS FOR THIS CELL: only a menu-availability flag - the store-menu query sends 'F_SystemSSI:false, F_SystemThirdParty:false', i.e. menus can be scoped by originating system (PDQ's own vs a third-party channel). Nothing about attaching marketplace orders to a guest profile; that is server-side and outside any guest client. Retrieved 2026-09-18. adversarially verified

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

guest-loyalty-accrual-models

CLAIM: at least TWO of points-per-dollar, visit/punch-count and spend-tier accrual, as configuration, without a bolt-on loyalty vendor. VERDICT: partial. EVIDENCE: loyalty is first-party and points-based. The 2016 Feature Overview lists 'Guest loyalty & rewards' under Point-of-Sale Capabilities and 'CUSTOMER MEMBER POINTS' under Payment (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf); PDQ describes the programme as its own product, 'PDQ Rewards - custom branded and customizable, the easy-to-use PDQ Rewards program, with a low, flat monthly fee' (https://web.archive.org/web/20200924180900/https://www.pdqpos.com/2020/06/22/off-premise-solutions/), and its 2020 boilerplate calls it 'NATIVE REWARDS/LOYALTY' (https://web.archive.org/web/20250121221212/https://www.pdqpos.com/wp-content/uploads/2020/12/PR_JJ-DoorDash3.pdf). So the no-bolt-on conjunct is met and ONE accrual model (points) is named. SHORTFALL (named): only one of the three models is evidenced - no punch/visit count and no spend tier is described anywhere - so the claim's 'at least two' threshold is not reached. Retrieved 2026-09-18. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-18 adversarially verified

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

guest-loyalty-tiers

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Loyalty exists as a named module and is otherwise undescribed. Both sites market "PDQ Rewards" / "built-in loyalty/rewards", "Rewards" is a top-level item on the back-office nav bar in the 2019 reporting screenshot, and the 2025 catalog says the MSR card reader "can be integrated with virtually any loyalty option". Third-party loyalty vendors -- Paytronix, JOINGO, GiveX -- appear in ssipos.com's integration list. That is the whole of it. Accrual models, tiers, offline behaviour, stacking rules, targeting, RFM segmentation, lifecycle automation, campaign attribution, member-data export, review routing, referrals, wallet passes, redemption-fraud controls and AI offer recommendation are described nowhere, and the presence of third-party loyalty partners in the integration list cuts against reading the native module as deep. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 331st: 331st (slice c): NEW SURFACE - PDQ's SECOND-GENERATION guest ordering app, never read by any prior pass. The four Live! Casino & Hotel tenants (marylandlive, philadelphialive, pittsburghlive, bossierlive .pdqonlineordering.com - bossierlive is the Louisiana property the 2025 press release calls 'a mobile ordering experience ... the first of its kind') no longer run the legacy ASP.NET WebForms app: they serve a Next.js/Turbopack app footed 'Powered by PDQ Signature Systems, Inc. (c) 2026 - V 3.11'. Census: every /_next/static chunk referenced from the HTML of /, /menu, /checkout, /confirmation and a nonsense path, taken to a fixpoint (3 rounds, 49 JS chunks, 2.65 MB, 0 misses, no source maps - .js.map 404s like a nonsense sibling). Route census from the bundle's own router calls: '/', '/menu', '/checkout', '/confirmation' only; /account, /rewards, /loyalty, /orders, /profile, /signup, /login all 404 exactly like /zzz-nope (45,0xx-byte not-found page). The client's API table is a closed Object.freeze enum of ~40 endpoints (online/franchise/*, online/store/*, online/menu/*, online/order/{detail,validate,submit}, online/charge/{hostprepare,hostresult,Auth}, online/user/*, online/loyalty/{lookup,redeem,charge}, online/franchise/datakeylookup). Production JS the vendor does not publish as documentation = grade B. WHAT IT HOLDS FOR THIS CELL: tiers are CONSUMED, not computed. The loyalty lookup (online/loyalty/lookup, keyed by 'accountNumber' + 'accountPin' + captcha) returns 'Customer.Tier' / 'Tier' / 'Customer.LoyaltyTier'; menu groups, sections and items carry 'AvalLoyaltyTiers' / 'NotAvalLoyaltyTiers' and are filtered by the guest's tier ('filterMenuByLoyaltyAndDataKey'), with tier badges ('aria-label Tier: ${tier}') coloured from a palette of generic tier names (gold, silver, bronze, platinum, diamond, vip, elite, legend, ambassador, tier1-tier5 ...). So tier-gated menu benefits exist in the digital flow. NOT A PARTIAL: nothing shows PDQ assigning, promoting or demoting a tier - the tier arrives in the lookup response, and on these casino tenants the account is a player-club card ('PLAYER_REWARDS' tender type 11, 'Failed to redeem points or comps'), i.e. very likely the casino management system's tier, a third party's product. Retrieved 2026-09-18. adversarially verified

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

guest-loyalty-offline-behavior

332nd: CLAIM: the vendor DOCUMENTS explicitly what loyalty lookup, accrual and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). VERDICT: no - a documentation-shaped claim (same shape as labor-offline-time-punch, which the owner ruled on 2026-09-18: a publication census carries `no`), answered by a bounded publication census. CURRENT PUBLICATION CENSUS (re-derived today, 332nd): (1) www.pdqpos.com - homepage 110,961 bytes, byte-identical to the 326th/331st copies; legal set exactly three pages, now served extensionless (termsofuse.aspx, privacypolicy.aspx and smsprivacypolicy.aspx 301 to /termsofuse, /privacypolicy, /smsprivacypolicy; stripped text identical to the 328th copies: 39,336 / 17,292 / 11,510 chars); robots.txt and sitemap.xml 404; a nonsense path 404s. pdqdt.com, pdqtek.com, pdqsecurity.com, pdqoo.com serve or redirect to the same page (331st). (2) ssipos.com - /wp-json/wp/v2/types core types only; pages X-WP-Total 8, posts X-WP-Total 5 (both re-fetched today, 1 page each); its 12 media-library PDFs (press releases, awards, SSI Security brochure) read in the 331st. (3) the 4 newsarticles press releases and 2 project pages linked from the homepage, and the 20-page 2025 Product Catalog PDF. (4) the Online Ordering Terms every legacy tenant serves (https://passariellos.pdqonlineordering.com/SSIPolicies.html, 200, Last-Modified 12 Aug 2026). 35 documents, 187,953 stripped chars. The 2016-2022 WordPress site (blog, /pf/ product pages) is RETIRED - /2020/06/17/ai-powered-self-serve-kiosks/ and /pf/kiosks/ both 404 live today - so per the owner's ruling it carries no `no` and positives from it are capped at partial. No docs, help, developer or status host exists in the crt.sh name set (324th/327th). CONTROLS over those 35 documents (tokenised, word-boundary, case-insensitive; known positives first): 'loyalty' 7 docs / 9 hits and 'reward(s)' 3 / 5 (the regex works); 'offline'/'off-line' 0; 'internet down'/'outage(s)' 0; 'queue(d)' 0, 'reconcil*' 1 (a Casino Cash Trac press release: 'automate all revenue audit reconciliation needs' - POISON, revenue audit, not loyalty); 'connectivity' 2 (the catalog's tablet 'wifi connectivity, bluetooth connectivity' and a Wildwood release's SIM-card failover for card processing - neither mentions loyalty). Wider controls over 3,604 text documents in 17 on-disk corpora (every .cache pdq dir, incl. retired Wayback copies): no document places loyalty/rewards/points within 200 chars of offline/connectivity/queue/reconcile except atlas notes and a classifier tsv; the 'offline' hits are the retired AI-kiosk blog ('see their customers in the offline world' - POISON, marketing idiom) and TanStack Query listeners in the V2 ordering client. The only observed loyalty failure behaviour is in that guest web client ('Network error during loyalty lookup', recorded in the 331st), which is not the POS losing connectivity and is not documentation. Grade C: marketing plus legal pages, no product documentation exists to be silent. Retrieved 2026-09-18. https://www.pdqpos.com/ · retrieved 2026-09-18 adversarially verified

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

guest-loyalty-offer-stacking-rules

PDQ's own multi-tenant online ordering enforces a per-coupon exclusive-vs-combinable rule server-side, from both directions. There is no evidence of an order-of-application or precedence rule. Retrieval: live read-only guest sessions (Pickup) on *.pdqonlineordering.com, 2026-09-14, coupon Add postbacks only, then a plain GET of Menu.aspx for the settled cart. No items carted, no coupon wizard completed, Checkout never touched. MET (exclusive vs combinable, per coupon): on slicespizza, Add 7d513099 ('1 large Cheese Pizza 10 wings') then 3dd02b96 ('2 LG Cheese for 26.99') gives no error, and the settled cart lists both ('Lrg 1Top 10Wings 24.99', '2 LG Cheese for 26.99'). On the same tenant, an incoming exclusive coupon is refused: f3b1c0c7 then 13ae3b50, and 3dd02b96 then 13ae3b50, each return 'Coupon Validation Error Sorry, this coupon failed to meet the coupon's requirements. This coupon is not allowed with any other offers. Please remove any other coupons before applying this one.' An exclusive coupon already in the cart blocks a combinable one with a distinct message: f3b1c0c7 then 3dd02b96 returns 'There is currently a coupon ordered that is not allowed with other offers. Please remove that coupon before adding the selected one.' In every case only the first coupon remains in the cart. The same exclusivity refusal reproduces on belairpizzeria (ecfb7671 and 1b3c4b9b, refused in both orders) and on steakandhoagiefactory (4f07a428 then e159da57). It is distinct from the other coupon rules the engine enforces, e.g. steakandhoagiefactory e159da57 'The minimum balance requirements (subtotal before tax) for this coupon has not been reached. $40.00'. Ruled out: a one-combo-per-order rule, since two combo coupons co-exist. SHORTFALL: no order-of-application or precedence rule observed, and no discount amount was ever computed (subtotal $0.00 throughout, nothing carted). NOT ESTABLISHED: the admin screen that sets the flag (office-only), whether the flag is a documented configuration setting or its exact name, and behaviour on the PDQ POS terminal or kiosk. POISON EXCLUDED: 'Not valid with other offers' is coupon description copy (steakandhoagiefactory 4f07a428) and is not evidence; only the server validation popups are. 13ae3b50 then 7d513099 was inconclusive, because 13ae's solo Add opens a wizard rather than carting it. https://slicespizza.pdqonlineordering.com/ · retrieved 2026-09-14 adversarially verified

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

guest-loyalty-targeted-offers

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Loyalty exists as a named module and is otherwise undescribed. Both sites market "PDQ Rewards" / "built-in loyalty/rewards", "Rewards" is a top-level item on the back-office nav bar in the 2019 reporting screenshot, and the 2025 catalog says the MSR card reader "can be integrated with virtually any loyalty option". Third-party loyalty vendors -- Paytronix, JOINGO, GiveX -- appear in ssipos.com's integration list. That is the whole of it. Accrual models, tiers, offline behaviour, stacking rules, targeting, RFM segmentation, lifecycle automation, campaign attribution, member-data export, review routing, referrals, wallet passes, redemption-fraud controls and AI offer recommendation are described nowhere, and the presence of third-party loyalty partners in the integration list cuts against reading the native module as deep. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 325th: MERGE HOLD (proposed partial/C, held unknown): a 2004 retired sheet describing postal mailings tailored by order history; no audience rules, and too old to describe the current product. PROPOSAL AS WRITTEN: CLAIM: offers issued to a DYNAMICALLY DEFINED audience (rules over recency, frequency, spend or items purchased) rather than only broadcast to the whole list. VERDICT: partial (weak). EVIDENCE: PDQ's Quick Service Module sheet, under 'Direct Marketing': 'Customer marketing features give you the power to track customer ordering tendencies. You can create mailings tailored to your customer increasing repeat business.' (https://web.archive.org/web/20041208204758/http://www.pdqpos.com/quick_svc.pdf, a retired 2004 document). Offers are therefore differentiated by the guest's own order history rather than broadcast to all. The 2016 Feature Overview adds 'Coupons by items, departments and condition', 'Coupon sales summary', 'Offers and discounts' and 'Customer member points' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf) - a coupon CONDITION axis, but conditions on the basket, not on the audience. SHORTFALLS (named): no audience or segment builder, no recency/frequency/spend rules, and no statement that any rule re-evaluates dynamically; the channel described is postal mailings. The retired 2004 source caps this at partial by policy. Retrieved 2026-09-17. || 333rd: 333rd: NEW SURFACES, do not settle the cell. (1) PDQ's 'PDQ POS Demo' (youtube.com/watch?v=EoHF88VZ9aA, uploaded 2016-10-14, 369 s, 720p; 191 distinct frames, all read) shows the register's 'Returning Customer' screen with side buttons 'Rewards (Not Active)', 'History (72 Orders)', 'House Acc', 'Credit $0.00', and, once items are rung in, a 'Smart Coupon' button on the order screen; the Manager screen (PDQ POS Manager 3.5.190, 1/27/2016) has a 'Marketing' tab that is never opened. 'Smart Coupon' is basket-triggered at the register, not an audience rule. (2) 'PDQ POS Overview' (YUUejVp2lhY, 2017) shows the MyPOS 'Edit Campaign Manager' with a single 'Campaign: Birthday' (see guest-loyalty-lifecycle-automation) and no audience/segment builder on the screen. V2 CLIENT TENANT CENSUS (333rd, GET only): all 207 tenant roots in the 331st's list fetched with curl (207 x 200); 7 run the Next.js V2 client (the 4 Live! casinos plus three PIZZERIAS: mygiaspizza, slicespizzapa, trianospizza), and two tenants not in that list were found from PDQ's own 2025 'Mobile Ordering Now Available' video and probing (oceancasino, sycuan; a nonsense subdomain 302s to /Error.aspx). Every V2 tenant ships the SAME build as the 331st's 49-chunk fixpoint (0 new JS chunks; only 2 font files differ), so no tenant adds client code. Each V2 page embeds a 42-key tenant settings dictionary; its loyalty/marketing keys are 'API.ALLOWREWARDSENROLL' (True on trianospizza only, False on the other six) and 'API.ALLOWSPECIALSEMAIL' (False on all seven); neither key is read anywhere in the shipped bundle (0 hits), i.e. both are consumed server-side. Retrieved 2026-09-18. adversarially verified

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

guest-loyalty-rfm-segmentation

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Loyalty exists as a named module and is otherwise undescribed. Both sites market "PDQ Rewards" / "built-in loyalty/rewards", "Rewards" is a top-level item on the back-office nav bar in the 2019 reporting screenshot, and the 2025 catalog says the MSR card reader "can be integrated with virtually any loyalty option". Third-party loyalty vendors -- Paytronix, JOINGO, GiveX -- appear in ssipos.com's integration list. That is the whole of it. Accrual models, tiers, offline behaviour, stacking rules, targeting, RFM segmentation, lifecycle automation, campaign attribution, member-data export, review routing, referrals, wallet passes, redemption-fraud controls and AI offer recommendation are described nowhere, and the presence of third-party loyalty partners in the integration list cuts against reading the native module as deep. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: MERGE HOLD (proposed partial/C, held unknown): a single 2015 marketing sentence about one-time versus repeat customers for direct mail; no computed lifecycle segments. The agent flagged it as weak. PROPOSAL AS WRITTEN: CLAIM: automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator writing queries. VERDICT: partial (weak). EVIDENCE: PDQ's 'Easy to Learn & Operate' page states the system does the identifying, under the heading 'Customer loyalty is effortless': 'IDENTIFY ONE-TIME CUSTOMERS and send them direct mail pieces to come back. FIND REPEAT CUSTOMERS and send them a promotion to thank them.' (https://web.archive.org/web/20150731053400/http://pdqpos.com/easy-to-learn/). One-time versus repeat is a frequency-based lifecycle split (new vs regular) presented as a built-in lookup, not an operator-built query, and the AI-kiosk page adds returning-guest habit tracking feeding the 'Customer Data Management (CDM) reporting suite' where 'you'll instantly know key essentials, such as who's ordering what' (https://web.archive.org/web/20200815161803/https://www.pdqpos.com/pf/kiosks/). SHORTFALLS (named): only the FREQUENCY axis appears - no recency window, no monetary band, and no named at-risk/lapsed/VIP segment; and the sentence is 2015 marketing, with no screen, field or segment list behind it. Retrieved 2026-09-18. adversarially verified

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

guest-loyalty-lifecycle-automation

333rd: NEW SURFACE, a vendor video read frame by frame. CLAIM: ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns, not one-off manual sends. VERDICT: partial/C. EVIDENCE: PDQ's own upload 'PDQ POS Overview' (youtube.com/watch?v=YUUejVp2lhY, channel @PDQPOS, uploaded 2017-05-16, 198 s, 608x1080; downloaded anonymously, 120 distinct frames extracted at 1 s steps, all contact sheets read, the relevant frame cropped and upscaled from the 1611 kbps stream) shows, under the caption 'Cloud-based Reporting / Rewards/Loyalty / Online Ordering' (138-144 s), a screenshot of the PDQ MyPOS back office (nav: Home, Enterprise, Inventory, Rewards, Reporting, Settings) open on a screen titled 'Edit Campaign Manager' with the header 'Campaign: Birthday' and 'Reward: 25 Babe's Points', buttons 'Save', 'Cancel', 'Test Email', 'Exit', a template bar (Template 'Clean Head Pic and Default', Theme, Background Style, Points Style, Email Font, Link Style), an image list with a 'Months' selector and Active/Inactive status per image (Birthday02 Active; holiday images such as 4thOfJuly01, AprilFoolsDay01, CincoDeMayo01, Easter01, FathersDay01, Halloween01 Inactive), and the rendered email: 'You're receiving this E-mail because you signed up with the Babe's Rewards Loyalty Program ... Happy Birthday! ... you signed up for our Babe's Rewards and that has given you 25 Babe's Points!' beside an 'ACCOUNT BALANCE' panel (points balance, money balance, points earned, money saved). A named, saved, templated Birthday campaign that attaches a points reward to a loyalty member's birthday is the birthday automation, configured in the operator's back office. The same slide reappears in 'Learn More About PDQ POS' (PWqryUhZN4E) and 'PDQ POS' (xvVu3cVQl8I). SHORTFALLS (named): only the BIRTHDAY campaign is shown; no first-visit thank-you or lapsed win-back campaign is legible (two image names in the list may read '30Days01'/'30Days02' but are not legible enough to cite); the screen does not state the send is always-on rather than scheduled; the back-office screenshot is dated by its own dashboard ('Last Log In 2/25/2013'), so it corroborates an older generation of MyPOS and caps this at partial; marketing video = grade C. Corroboration that the rewards module is live today: the 2026 V2 ordering client embeds 'API.ALLOWREWARDSENROLL' = True on trianospizza.pdqonlineordering.com. Retrieved 2026-09-18. https://www.youtube.com/watch?v=YUUejVp2lhY · retrieved 2026-09-18 adversarially verified

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

guest-loyalty-native-email-sms

PDQ operates its own SMS messaging service (dedicated SMS Privacy Policy) and sends customer notifications. Native email campaign capability is not documented. https://www.pdqpos.com/smsprivacypolicy.aspx · retrieved 2026-08-01

Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.

guest-loyalty-consent-management

Consent is addressed ('Consent to receive automated marketing text messages is not a condition of any purchase') but revocation is documented only via keywords: STOP, END, CANCEL, UNSUBSCRIBE, QUIT. https://www.pdqpos.com/smsprivacypolicy.aspx · retrieved 2026-08-01

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

guest-loyalty-10dlc-registration

332nd: PROPOSED partial/C on the claim's 'HANDLES' branch, the same shape as the microworks-prism row landed in the 331st (vendor-run messaging service + the vendor's own SMS programme policy). CLAIM: handles OR explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform. WHAT IS NEW: (1) the guest SMS is the VENDOR's messaging programme, not the operator's. PDQ's Online Ordering Terms, served on every legacy tenant (https://passariellos.pdqonlineordering.com/SSIPolicies.html, 200 today, Last-Modified 12 Aug 2026), are 'between you and Signature Systems, Inc. and the restaurant utilizing the Online Ordering Services', and say 'By providing a mobile number, you agree to receive SMS (text) messages for promotional and/or order update purposes' and that the only third parties who get the data are service providers 'and, if applicable, to provide communications as described in Section 2.(c)'. The SMS Privacy Policy (https://www.pdqpos.com/smsprivacypolicy, 'Updated January, 2025', stripped text identical to the 328th copy) governs 'SSI text message programs or services (the "Messaging Service")', opt-out 'by responding to any of our text messages' with STOP/END/CANCEL/UNSUBSCRIBE/QUIT, and 'By signing up to receive text messages from SSI' - SSI is the named sender. (2) The vendor's main Privacy Policy (https://www.pdqpos.com/privacypolicy, live today) carries, verbatim, the clause carrier campaign vetting asks every registered sender to publish: 'No mobile information will be shared with third parties/affiliates for marketing/promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.' That is the fingerprint of a registered A2P programme held by SSI itself, i.e. the operator is not asked to register a brand or campaign. SHORTFALLS (named): '10DLC' 0, 'A2P' 0, 'campaign registration'/'brand registration'/'TCR' 0 over the 35-document current publication census (homepage, 3 legal pages, SSIPolicies, 6 press/project pages, 2025 catalog, ssipos.com 8 pages + 5 posts + 12 PDFs); the registration is inferred from the compliance wording, not stated; which number type (10DLC, toll-free, short code) sends guest texts is unpublished; and nothing says the policy covers the restaurant's own marketing sends rather than order-update texts. Grade C: legal pages with the link between them inferred. Retrieved 2026-09-18. https://www.pdqpos.com/smsprivacypolicy · retrieved 2026-09-18 adversarially verified

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

guest-loyalty-campaign-attribution

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Loyalty exists as a named module and is otherwise undescribed. Both sites market "PDQ Rewards" / "built-in loyalty/rewards", "Rewards" is a top-level item on the back-office nav bar in the 2019 reporting screenshot, and the 2025 catalog says the MSR card reader "can be integrated with virtually any loyalty option". Third-party loyalty vendors -- Paytronix, JOINGO, GiveX -- appear in ssipos.com's integration list. That is the whole of it. Accrual models, tiers, offline behaviour, stacking rules, targeting, RFM segmentation, lifecycle automation, campaign attribution, member-data export, review routing, referrals, wallet passes, redemption-fraud controls and AI offer recommendation are described nowhere, and the presence of third-party loyalty partners in the integration list cuts against reading the native module as deep. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

guest-loyalty-data-export-portability

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Loyalty exists as a named module and is otherwise undescribed. Both sites market "PDQ Rewards" / "built-in loyalty/rewards", "Rewards" is a top-level item on the back-office nav bar in the 2019 reporting screenshot, and the 2025 catalog says the MSR card reader "can be integrated with virtually any loyalty option". Third-party loyalty vendors -- Paytronix, JOINGO, GiveX -- appear in ssipos.com's integration list. That is the whole of it. Accrual models, tiers, offline behaviour, stacking rules, targeting, RFM segmentation, lifecycle automation, campaign attribution, member-data export, review routing, referrals, wallet passes, redemption-fraud controls and AI offer recommendation are described nowhere, and the presence of third-party loyalty partners in the integration list cuts against reading the native module as deep. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

guest-loyalty-cdp-event-api

No public API or webhook stream of any kind exists.

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

guest-loyalty-review-capture-routing

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Loyalty exists as a named module and is otherwise undescribed. Both sites market "PDQ Rewards" / "built-in loyalty/rewards", "Rewards" is a top-level item on the back-office nav bar in the 2019 reporting screenshot, and the 2025 catalog says the MSR card reader "can be integrated with virtually any loyalty option". Third-party loyalty vendors -- Paytronix, JOINGO, GiveX -- appear in ssipos.com's integration list. That is the whole of it. Accrual models, tiers, offline behaviour, stacking rules, targeting, RFM segmentation, lifecycle automation, campaign attribution, member-data export, review routing, referrals, wallet passes, redemption-fraud controls and AI offer recommendation are described nowhere, and the presence of third-party loyalty partners in the integration list cuts against reading the native module as deep. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: NEW SURFACE, does not settle the cell. PDQ Online Ordering ships a guest feedback page on every tenant: a Wayback CDX census of pdqonlineordering.com (9,077 captures across ~60 store subdomains plus admin.pdqonlineordering.com) yields a small, closed page set for the guest app - titlepage.aspx, menu.aspx, checkout.aspx, ordercomplete.aspx, orderdetails.aspx, orderreceipt.aspx, FEEDBACK.ASPX, storeclosed.aspx, messagepage.aspx, error.aspx, upgradenotice.aspx - and feedback.aspx answers 200 live today (https://passariellos.pdqonlineordering.com/feedback.aspx). A post-order feedback surface therefore exists. SHORTFALL: nothing indicates the request is TRIGGERED after a transaction rather than being a standing link, and no score-based routing exists in the page set - there is no admin screen for it (admin.pdqonlineordering.com exposes only managerlogin.aspx, managerorders.aspx, managersettings.aspx and messagepage.aspx) and no mention of public review sites anywhere in the PDQ corpus. Held unknown. Retrieved 2026-09-18. adversarially verified

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

guest-loyalty-referral-program

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Loyalty exists as a named module and is otherwise undescribed. Both sites market "PDQ Rewards" / "built-in loyalty/rewards", "Rewards" is a top-level item on the back-office nav bar in the 2019 reporting screenshot, and the 2025 catalog says the MSR card reader "can be integrated with virtually any loyalty option". Third-party loyalty vendors -- Paytronix, JOINGO, GiveX -- appear in ssipos.com's integration list. That is the whole of it. Accrual models, tiers, offline behaviour, stacking rules, targeting, RFM segmentation, lifecycle automation, campaign attribution, member-data export, review routing, referrals, wallet passes, redemption-fraud controls and AI offer recommendation are described nowhere, and the presence of third-party loyalty partners in the integration list cuts against reading the native module as deep. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 331st: 331st (slice c): NEW SURFACE - PDQ's SECOND-GENERATION guest ordering app, never read by any prior pass. The four Live! Casino & Hotel tenants (marylandlive, philadelphialive, pittsburghlive, bossierlive .pdqonlineordering.com - bossierlive is the Louisiana property the 2025 press release calls 'a mobile ordering experience ... the first of its kind') no longer run the legacy ASP.NET WebForms app: they serve a Next.js/Turbopack app footed 'Powered by PDQ Signature Systems, Inc. (c) 2026 - V 3.11'. Census: every /_next/static chunk referenced from the HTML of /, /menu, /checkout, /confirmation and a nonsense path, taken to a fixpoint (3 rounds, 49 JS chunks, 2.65 MB, 0 misses, no source maps - .js.map 404s like a nonsense sibling). Route census from the bundle's own router calls: '/', '/menu', '/checkout', '/confirmation' only; /account, /rewards, /loyalty, /orders, /profile, /signup, /login all 404 exactly like /zzz-nope (45,0xx-byte not-found page). The client's API table is a closed Object.freeze enum of ~40 endpoints (online/franchise/*, online/store/*, online/menu/*, online/order/{detail,validate,submit}, online/charge/{hostprepare,hostresult,Auth}, online/user/*, online/loyalty/{lookup,redeem,charge}, online/franchise/datakeylookup). Production JS the vendor does not publish as documentation = grade B. WHAT IT HOLDS FOR THIS CELL: no referral surface - tokenised 'referral' 0, 'refer' 0, 'invite' 0; the signup schema (online/user/signup) asks name, email, phone and password only. Held unknown (the native loyalty programme's back office is unpublished). Retrieved 2026-09-18. || 333rd: 333rd: extends the 331st's V2-client zero to every V2 tenant. V2 CLIENT TENANT CENSUS (333rd, GET only): all 207 tenant roots in the 331st's list fetched with curl (207 x 200); 7 run the Next.js V2 client (the 4 Live! casinos plus three PIZZERIAS: mygiaspizza, slicespizzapa, trianospizza), and two tenants not in that list were found from PDQ's own 2025 'Mobile Ordering Now Available' video and probing (oceancasino, sycuan; a nonsense subdomain 302s to /Error.aspx). Every V2 tenant ships the SAME build as the 331st's 49-chunk fixpoint (0 new JS chunks; only 2 font files differ), so no tenant adds client code. Each V2 page embeds a 42-key tenant settings dictionary; its loyalty/marketing keys are 'API.ALLOWREWARDSENROLL' (True on trianospizza only, False on the other six) and 'API.ALLOWSPECIALSEMAIL' (False on all seven); neither key is read anywhere in the shipped bundle (0 hits), i.e. both are consumed server-side. The embedded settings dictionary has 0 keys matching refer/referral/invite. Held unknown. Retrieved 2026-09-18. adversarially verified

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

guest-loyalty-wallet-pass

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Loyalty exists as a named module and is otherwise undescribed. Both sites market "PDQ Rewards" / "built-in loyalty/rewards", "Rewards" is a top-level item on the back-office nav bar in the 2019 reporting screenshot, and the 2025 catalog says the MSR card reader "can be integrated with virtually any loyalty option". Third-party loyalty vendors -- Paytronix, JOINGO, GiveX -- appear in ssipos.com's integration list. That is the whole of it. Accrual models, tiers, offline behaviour, stacking rules, targeting, RFM segmentation, lifecycle automation, campaign attribution, member-data export, review routing, referrals, wallet passes, redemption-fraud controls and AI offer recommendation are described nowhere, and the presence of third-party loyalty partners in the integration list cuts against reading the native module as deep. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 331st: 331st (slice c): NEW SURFACE - PDQ's SECOND-GENERATION guest ordering app, never read by any prior pass. The four Live! Casino & Hotel tenants (marylandlive, philadelphialive, pittsburghlive, bossierlive .pdqonlineordering.com - bossierlive is the Louisiana property the 2025 press release calls 'a mobile ordering experience ... the first of its kind') no longer run the legacy ASP.NET WebForms app: they serve a Next.js/Turbopack app footed 'Powered by PDQ Signature Systems, Inc. (c) 2026 - V 3.11'. Census: every /_next/static chunk referenced from the HTML of /, /menu, /checkout, /confirmation and a nonsense path, taken to a fixpoint (3 rounds, 49 JS chunks, 2.65 MB, 0 misses, no source maps - .js.map 404s like a nonsense sibling). Route census from the bundle's own router calls: '/', '/menu', '/checkout', '/confirmation' only; /account, /rewards, /loyalty, /orders, /profile, /signup, /login all 404 exactly like /zzz-nope (45,0xx-byte not-found page). The client's API table is a closed Object.freeze enum of ~40 endpoints (online/franchise/*, online/store/*, online/menu/*, online/order/{detail,validate,submit}, online/charge/{hostprepare,hostresult,Auth}, online/user/*, online/loyalty/{lookup,redeem,charge}, online/franchise/datakeylookup). Production JS the vendor does not publish as documentation = grade B. WHAT IT HOLDS FOR THIS CELL: no wallet surface in the guest client - tokenised 'wallet' 0, 'pkpass' 0, 'passkit' 0; the only Apple/Google identifiers are 'ApplePay'/'GooglePay' tender constants and crawler UA strings. Not scored no: a pass is issued server-side (email/SMS link), which a client census does not bound, and loyalty on these tenants is the casino's player club. Retrieved 2026-09-18. || 334th: 334th (slice e): NEW SURFACE, does not settle the cell. PDQ publishes no guest app (the 328th publisher census: Apple developer id 1218876301 = MY PDQ + PDQ DT; Google Play 'Signature Systems, Inc' = com.pdqpos.mypdqpos + com.pdqpos.pdqdelivery). Both of those apps' CODE is now read: MY PDQ v1.3.0 (332nd, 6,690 strings) and, new today, PDQ DT v1.3.4 (APK 47,158,626 bytes from the APKPure mirror, Xamarin assemblies.blob unpacked, PDQDT.dll + PDQDT.Android.dll, 8,011 strings). 'wallet', 'pkpass', 'passkit', 'walletobjects' are 0 in both, and PDQ DT carries 0 'reward'/'loyalty' tokens although PDQ's 2021 Delivery Tool Kit explainer (youtube LCeKw8MiRQQ) sells it as natively integrated with 'PDQ REWARDS'. A wallet pass needs no native app (it can be issued from the web or by email), so this bounds nothing: held unknown. Retrieved 2026-09-18. adversarially verified

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

guest-loyalty-privacy-rights-tooling

Privacy Policy offers only a postal-mail California 'Shine the Light' request to the Legal Department; no in-product DSAR tooling described. || 332nd: 332nd: NEW, does not settle the cell. The vendor privacy policy (now served at https://www.pdqpos.com/privacypolicy; privacypolicy.aspx 301s there; 'Effective date: January 15, 2019') offers more than the postal 'Shine the Light' request: 'if you wish to change, access, or remove your Personal Data, please contact us as indicated below. We will attempt, where practical, to respond to your requests' - a request channel to SSI for SSI's own data, handled by the vendor, which is neither operator admin tooling nor deletion propagation to loyalty/marketing records. The guest-facing Online Ordering Terms (https://passariellos.pdqonlineordering.com/SSIPolicies.html) add only 'details on how to opt-out of location collection' and have 0 'delete'/'deletion'. The operator back office (myPDQPOS) is login-only, so whether an in-app locate/export/delete tool exists is unseen - the same reason the 331st merge held commercial-privacy-dsar-tooling. Held unknown. Retrieved 2026-09-18. adversarially verified

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

guest-loyalty-redemption-fraud-controls

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Loyalty exists as a named module and is otherwise undescribed. Both sites market "PDQ Rewards" / "built-in loyalty/rewards", "Rewards" is a top-level item on the back-office nav bar in the 2019 reporting screenshot, and the 2025 catalog says the MSR card reader "can be integrated with virtually any loyalty option". Third-party loyalty vendors -- Paytronix, JOINGO, GiveX -- appear in ssipos.com's integration list. That is the whole of it. Accrual models, tiers, offline behaviour, stacking rules, targeting, RFM segmentation, lifecycle automation, campaign attribution, member-data export, review routing, referrals, wallet passes, redemption-fraud controls and AI offer recommendation are described nowhere, and the presence of third-party loyalty partners in the integration list cuts against reading the native module as deep. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 331st: 331st (slice c): NEW SURFACE - PDQ's SECOND-GENERATION guest ordering app, never read by any prior pass. The four Live! Casino & Hotel tenants (marylandlive, philadelphialive, pittsburghlive, bossierlive .pdqonlineordering.com - bossierlive is the Louisiana property the 2025 press release calls 'a mobile ordering experience ... the first of its kind') no longer run the legacy ASP.NET WebForms app: they serve a Next.js/Turbopack app footed 'Powered by PDQ Signature Systems, Inc. (c) 2026 - V 3.11'. Census: every /_next/static chunk referenced from the HTML of /, /menu, /checkout, /confirmation and a nonsense path, taken to a fixpoint (3 rounds, 49 JS chunks, 2.65 MB, 0 misses, no source maps - .js.map 404s like a nonsense sibling). Route census from the bundle's own router calls: '/', '/menu', '/checkout', '/confirmation' only; /account, /rewards, /loyalty, /orders, /profile, /signup, /login all 404 exactly like /zzz-nope (45,0xx-byte not-found page). The client's API table is a closed Object.freeze enum of ~40 endpoints (online/franchise/*, online/store/*, online/menu/*, online/order/{detail,validate,submit}, online/charge/{hostprepare,hostresult,Auth}, online/user/*, online/loyalty/{lookup,redeem,charge}, online/franchise/datakeylookup). Production JS the vendor does not publish as documentation = grade B. WHAT IT HOLDS FOR THIS CELL: two client-side guards only - loyalty account lookup requires 'PIN is required' plus a captcha ('Please complete the captcha'), and a reward token already applied to the order is refused with 'Already Redeemed' / 'This reward has already been redeemed for this order.' (a check of the token against the order's redeemed-token list in the browser), plus a 300 ms debounce on the redeem button. None of the claim's controls (redemption velocity limits, manager approval on manual point adjustments, employee self-redemption flagging, audit log) is visible; these are back-office/server controls a guest client cannot show, and PIN authentication is adjacent, not a redemption control. Held unknown. Retrieved 2026-09-18. adversarially verified

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

guest-loyalty-ai-offer-recommendation

332nd: CLAIM: the vendor DOCUMENTS AI/ML-generated recommendations for offer content, target audience or send timing, as a SHIPPED feature not a roadmap statement. VERDICT: no - a documentation claim against a bounded CURRENT publication census; the 326th hold (kiosk up-sell is adjacent) is respected, not re-proposed as partial. CURRENT PUBLICATION CENSUS (re-derived today, 332nd): (1) www.pdqpos.com - homepage 110,961 bytes, byte-identical to the 326th/331st copies; legal set exactly three pages, now served extensionless (termsofuse.aspx, privacypolicy.aspx and smsprivacypolicy.aspx 301 to /termsofuse, /privacypolicy, /smsprivacypolicy; stripped text identical to the 328th copies: 39,336 / 17,292 / 11,510 chars); robots.txt and sitemap.xml 404; a nonsense path 404s. pdqdt.com, pdqtek.com, pdqsecurity.com, pdqoo.com serve or redirect to the same page (331st). (2) ssipos.com - /wp-json/wp/v2/types core types only; pages X-WP-Total 8, posts X-WP-Total 5 (both re-fetched today, 1 page each); its 12 media-library PDFs (press releases, awards, SSI Security brochure) read in the 331st. (3) the 4 newsarticles press releases and 2 project pages linked from the homepage, and the 20-page 2025 Product Catalog PDF. (4) the Online Ordering Terms every legacy tenant serves (https://passariellos.pdqonlineordering.com/SSIPolicies.html, 200, Last-Modified 12 Aug 2026). 35 documents, 187,953 stripped chars. The 2016-2022 WordPress site (blog, /pf/ product pages) is RETIRED - /2020/06/17/ai-powered-self-serve-kiosks/ and /pf/kiosks/ both 404 live today - so per the owner's ruling it carries no `no` and positives from it are capped at partial. No docs, help, developer or status host exists in the crt.sh name set (324th/327th). CONTROLS over those 35 documents (tokenised, word-boundary, case-insensitive; known positive 'loyalty' 7 docs / 9 hits): 'AI' 0, 'artificial intelligence' 0, 'machine learning'/'ML' 0, 'predictive'/'algorithm*' 0, 'facial/face recognition' 0, 'recommend*' 1 (privacy policy: 'we recommend that you review the privacy statements of these other linked sites' - POISON), 'personaliz*' 4 hits in 2 docs (privacy policy 'Personalize and improve the usability of the Sites'; SMS policy 'Cookies enable personalization ... personalized text messages such as reminders' - cookie boilerplate, not a model). The homepage's only near-miss is 'fraud intelligence' in the payments block (the token 'intelligence', no AI claim). NEAREST MISS, RETIRED AND NEW TO THE RECORD: the 2020 blog post 'AI-Powered Self-Service Kiosks Offer Benefits to the Customer and Operator. Tailored experiences. Targeted loyalty. Tangible data.' (https://web.archive.org/web/20220127023724/https://www.pdqpos.com/2020/06/17/ai-powered-self-serve-kiosks/, 404 live) quotes PDQ's marketing director on 'tailored suggestions and specials based on ordering history' via facial recognition, but in so many words as ROADMAP: 'PDQ POS, which is developing AI for kiosks to roll out in the second half of 2020'. With the Aug 2020 /pf/kiosks/ 'OPTION' page already held as an adjacent kiosk up-sell, the retired material shows per-guest item suggestions on a kiosk, never generated offer content, a generated audience or send timing, and nothing on any live vendor surface mentions AI at all. Grade C (marketing + legal census). Retrieved 2026-09-18. https://www.pdqpos.com/ · retrieved 2026-09-18 adversarially verified

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

guest-loyalty-stored-value-gift

The strongest cell in this set. 'Built-in gift card processing' (Point-of-Sale Capabilities) and 'Check gift card balance' (Point-of-Sale Screen) are both byte-contiguous and affirmatively establish the claim's head noun - native first-party stored value rather than a third-party gateway. TWO SHORTFALLS, both qualifiers rather than the head: nothing ties the gift balance to the same GUEST PROFILE used by loyalty (which appears separately as 'Guest loyalty & rewards'), and cross-location redeemability across all locations of a brand is nowhere stated. SOURCE DATE: a 2016 first-party sell sheet (uploads/2016/12) recovered from the Internet Archive because pdqpos.com left WordPress and it 404s live. Evidence about the 2016 product. Verified that the live 2025 catalogue restates none of it - the tokens split, gift, transfer, email, security role, happy hour and permission each occur zero times there - so carry-forward rests on PDQ POS being a continuously-sold product line, not on any current document. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-12 adversarially verified

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

labor-clock-in-at-pos

The dossier's note asserts 'Partner documentation confirms clock-in/clock-out data originates in PDQ POS and flows to HotSchedules.' I fetched the page and it does not say that. It says 'Enforce clock-in times with ease, reducing early clock-ins and late clock-outs' and lists sales/schedule data flow — it never states that punch data originates in PDQ or flows from PDQ to Fourth. The fingerprint reader is documented for login and manager override, which is authentication, not timekeeping. Likely true of any POS of this age, but the cited source does not establish it. https://www.fourth.com/partner/integrations/point-of-sale/pdq-pos · retrieved 2026-08-01 adversarially verified

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

labor-photo-punch-verification

A fingerprint reader exists for login/override, which is biometric authentication rather than photo punch verification. || 326th: NEW SURFACE, does not settle the cell, and it identifies the wrong modality. PDQ's punch-identity hardware is a FINGERPRINT reader, not a camera: the 2025 Product Catalog's peripherals section reads 'FINGERPRINT READER - Make logging in for yourself, your managers and your other staff a breeze. Simply configure the fingerprint reader and save precious seconds at every login and MANAGER OVERRIDE.' (https://pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf), and the live site lists 'secure fingerprint POS log-in' among the system's essentials (https://pdqpos.com/). The claim asks for a photo at punch or facial verification WITH a photo-only, no-template mode; a fingerprint reader is a biometric template and is the opposite of that mode. PDQ's only camera products are the ProCam/DVR text-overlay systems, which record the transaction, not the punch: 'PDQ ProCam can insert the customer's receipt on the video as the customer is cashing out' (https://web.archive.org/web/20041016082914/http://www.pdqpos.com/cam.htm). Held unknown: the corpus is marketing, not a census of the time-clock module. Retrieved 2026-09-18. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). It corroborates the fingerprint modality already in this note: PDQ's implementation manager lists the station peripherals he installs as 'a Lane 3000 credit card terminal, a printer, a cash drawer ... more peripheral devices such as a fingerprint biometrics reader, a side-pipe [swipe] reader, a credit card terminal' (J1GdSoIMGC4, 54-75 s). No upload shows a camera at the time clock or a photo on a timecard; the 2016 demo's home screen shows a 'Time Clock' button (EoHF88VZ9aA, 7 s) but the clock screen itself is never opened. Retrieved 2026-09-18. || 334th: 334th: NEW SURFACE, does not settle the cell. SURFACE NO PASS OPENED: the Android binaries of BOTH apps in PDQ's complete published-app set (the 328th enumerated it three ways: Apple developer lookup id1218876301 returns exactly MY PDQ + PDQ DT; the Google Play developer page lists exactly com.pdqpos.pdqdelivery + com.pdqpos.mypdqpos). (a) PDQ DT, com.pdqpos.pdqdelivery, APK v1.3.4 (47,158,626 bytes, sha256 52ee11e8b22d1d3f..., build files dated 2023-04-21, fetched anonymously from the APKPure mirror because Play serves no APK; Play's current listing is 2.0, updated 2026-05-01, iOS 2.0 (74) 2026-05-06, so the binary is one generation behind the listing): a Xamarin app whose assemblies.blob (XABA, 116 assemblies, XALZ/LZ4) was unpacked, never executed; PDQDT.dll (332,800 bytes, sha256 5263fdd4692e5e60...) #US and #Strings heaps read. (b) MY PDQ, com.pdqpos.mypdqpos v1.3.0, myPdqPos.dll already unpacked by the 332nd (.cache/q332/pdq-pos/h/apk) but never read for labour; its #US heap was read today. Neither app captures a punch photo: MY PDQ's Time Clock page (myPdqPos.Pages.Misc.TimeClockPage.xaml) is an unbuilt stub whose only content is <Label Text="TODO">, and its manifest requests no CAMERA permission (INTERNET, WRITE_EXTERNAL_STORAGE only); PDQ DT does request CAMERA, but its only camera code is the QR sign-in scanner ('validateCameraPermissionsAsync', ZXing 'Scan QR code from timeclock screen'). Tokenised controls over the #US+#Strings heaps of PDQDT.dll, PDQDT.Android.dll, myPdqPos.dll and myPdqPos.Droid.dll: punch 0, geofenc*/fence 0, schedul* 0, swap 0, overtime 0, payroll 0, wage 0, photo 0, selfie 0 in all four; 'clock' = only 'timeclock' (DT sign-in text x2, MY PDQ page/icon), DT 'clockIcon' (order-time icon beside 'In: {0:T}' / 'On Way' / 'Delivered') and Android Material time-picker resources; POISON NAMED: MY PDQ 'Shift' (x20) is AM/PM SHIFT SALES ('StoreSalesByShift', 'AM Shift:', 'PM Shift:', 'Show Shift Sales'), 'break' is 'Transaction Breakdown'/'HourlySalesBreakdown'/'LineBreakMode', 'tip' is 'tooltip'/'MultiPage', 'radius' is CornerRadius. The punch is taken at the terminal (fingerprint reader, per the existing note), whose time-clock screen no public surface shows; held unknown. Retrieved 2026-09-18. adversarially verified

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

labor-geofenced-mobile-punch

334th: CLAIM: mobile clock-in restricted by geofence/location validation for staff who do not punch at a fixed terminal. VERDICT: no, grade A (vendor application binaries). SURFACE NO PASS OPENED: the Android binaries of BOTH apps in PDQ's complete published-app set (the 328th enumerated it three ways: Apple developer lookup id1218876301 returns exactly MY PDQ + PDQ DT; the Google Play developer page lists exactly com.pdqpos.pdqdelivery + com.pdqpos.mypdqpos). (a) PDQ DT, com.pdqpos.pdqdelivery, APK v1.3.4 (47,158,626 bytes, sha256 52ee11e8b22d1d3f..., build files dated 2023-04-21, fetched anonymously from the APKPure mirror because Play serves no APK; Play's current listing is 2.0, updated 2026-05-01, iOS 2.0 (74) 2026-05-06, so the binary is one generation behind the listing): a Xamarin app whose assemblies.blob (XABA, 116 assemblies, XALZ/LZ4) was unpacked, never executed; PDQDT.dll (332,800 bytes, sha256 5263fdd4692e5e60...) #US and #Strings heaps read. (b) MY PDQ, com.pdqpos.mypdqpos v1.3.0, myPdqPos.dll already unpacked by the 332nd (.cache/q332/pdq-pos/h/apk) but never read for labour; its #US heap was read today. EVIDENCE: (1) PDQ's app for exactly the staff this claim is about - delivery drivers - does not take a punch; it signs the driver in with a code issued by the TERMINAL's time clock: XAML strings 'Scan QR code from timeclock screen' (Pages/SignIn.xaml, ZXing scanner) and 'Enter code from timeclock screen' (Pages/ManualSignIn.xaml), and its only TimeIn/TimeOut fields are ORDER times ('In: {0:T}', 'On Way: {0:T}', 'Delivered: {0:T}' in Pages/Secure/OrderItem.xaml). (2) Its location use is declared, in the app's own disclosure string, as delivery tracking bound to the terminal pairing, not punch validation: 'PDQDT collects location data to enable delivery progress tracking and notification of orders even when the app is in the background but NOT when the app is closed. PDQDT will only access device location when the delivery driver is paired to the store PDQPOS terminal.' (locationService.cs: StartLocationUpdates / ProcessLocationQueue / empLocationAsync send Latitude/Longitude/Speed/Bearing; 'Location listener disabled for this store, exiting without starting.'); the current Play listing (2.0) says the same: 'updating the driver location to the store via PDQPOS through background services', Data safety 'Location'. (3) The other published app's Time Clock page was never built: myPdqPos.Pages.Misc.TimeClockPage.xaml (Title='Time Clock', icon timeclock.png) contains a single <Label Text="TODO">; the app's whole mobile API (api/Mobile) is twelve calls - ValidateLogin, StoreSales, StoreSalesByShift, ReportQuickX, ReportVoidPromo, ReportHourlySales, StoreCountItems, UserDetailsByUserID, UserAccessLoadDefaults, UserAccessGetStores, UserAccessGetUsers, UserSettingsUpdate - with no clock call; and its AndroidManifest requests only INTERNET and WRITE_EXTERNAL_STORAGE (no location). Tokenised controls over the #US+#Strings heaps of PDQDT.dll, PDQDT.Android.dll, myPdqPos.dll and myPdqPos.Droid.dll: punch 0, geofenc*/fence 0, schedul* 0, swap 0, overtime 0, payroll 0, wage 0, photo 0, selfie 0 in all four; 'clock' = only 'timeclock' (DT sign-in text x2, MY PDQ page/icon), DT 'clockIcon' (order-time icon beside 'In: {0:T}' / 'On Way' / 'Delivered') and Android Material time-picker resources; POISON NAMED: MY PDQ 'Shift' (x20) is AM/PM SHIFT SALES ('StoreSalesByShift', 'AM Shift:', 'PM Shift:', 'Show Shift Sales'), 'break' is 'Transaction Breakdown'/'HourlySalesBreakdown'/'LineBreakMode', 'tip' is 'tooltip'/'MultiPage', 'radius' is CornerRadius. BOUND (named): the census is the vendor's published MOBILE apps; the DT binary is 1.3.4 while the listing is 2.0 (the 328th read the 2.0 App Store screenshots, which still show 'Scan QR code from timeclock screen'); the login-gated myPDQPOS web back office is unseen, so a browser punch there is not bounded by this census - the merge should weigh that. The existing cell text (fingerprint reader at the terminal) is consistent: PDQ's punch is a terminal punch. Retrieved 2026-09-18. MERGE REGRADE A -> B: an unpacked production binary the vendor does not publish as documentation is grade B (324th precedent); the no is bounded by the complete published-app set (2 apps), and PDQ DT signs drivers in with a code issued by the terminal time clock rather than punching. https://play.google.com/store/apps/details?id=com.pdqpos.pdqdelivery · retrieved 2026-09-18 adversarially verified

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

labor-offline-time-punch

332nd: CLAIM: records time punches while the POS is offline and reconciles them on reconnect without loss or duplicates, WITH THE BEHAVIOUR DOCUMENTED. VERDICT: no. Per the owner ruling of 2026-09-18, this claim is documentation-shaped and a publication census carries a `no` (square and spoton landed this way). This record already carries the same census shape on reliability-offline-decline-liability, reliability-incident-postmortems and reliability-offline-feature-matrix. PUBLICATION CENSUS (332nd, re-derived today with curl + browser UA, not inherited): (1) www.pdqpos.com - homepage 200, 110,961 bytes, 29 distinct hrefs (same size as the 326th and 331st copies); the legal set is still exactly three live documents (termsofuse.aspx 81,365 B, privacypolicy.aspx 59,266 B, smsprivacypolicy.aspx 52,924 B); /termsofsale, /sitemap.xml and a nonsense path all return the same 1,927-1,928-byte ASP.NET not-found page, so there is no hidden legal or doc page behind those names. (2) ssipos.com WordPress REST: X-WP-Total pages 8, posts 5, media 216 (newest page edit is the homepage, 2026-08-19; the newest post is 2015). (3) Hosts: certspotter was run today (it was rate-limited in the 331st) on pdqpos.com, ssipos.com and mypdqpos.com: 18 names. Two are not in the 324th crt.sh set: session.pdqpos.com (resolves to 50.227.231.99, refuses connections on 443 and 80) and ftp.pdqpos.com (302 to /login, a 'Cerberus Web Client' file-transfer login). Neither is a documentation host; the rest are the known help (BeyondTrust remote-support portal), pci (login), support/ssi-jira (NXDOMAIN) and casino incident-report hosts. PDQ has no KB, manual, help centre or developer portal. (4) Tokenised, word-boundary, case-insensitive controls over 3,674 text documents in 24 on-disk corpora (.cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, all seven q331 pdq-pos slugs, and today's fetches). Agent notes, greps and scripts are excluded. CONTROLS: first a known positive: 'time clock' 10 docs, so the regex works. 'timecard' 0 docs. 'offline' 94 docs / 74 snippets, and none is about punches. POISON: PDQ's AI-kiosk essay says 'see their customers in the offline world'; YouTube player UI strings ('You are offline') and the 'Better Offline' podcast channel sit in the saved watch pages; the V2 ordering bundle has a react-query window online/offline listener; and the rest are other publishers' App Store/Play listings ('Offline Restaurant Club', Otter 'online and offline orders'). 'punch' 110 docs / 36 distinct snippets, and all are POISON: 'Fruit Punch' / 'Hawaiian Punch' menu items on the ordering tenants, 'punch above our weight' in a loyalty case study, and the PDQ Rewards app's 'digital card punch'. 'clock in/out' 40 docs / 23 snippets. The PDQ ones are about who may clock out: 'Servers cannot clock out before closing their checks' (ProTable, a 2000s Wayback page), 'Safeguard the POS against fraudulent clock-ins/clock-outs' (fingerprint reader) and the kiosk 'when they've clocked out'. The rest are third parties: Fourth's HotSchedules partner page and other publishers' App Store/Play listings. 'reconcil*' 41 docs / 15 snippets: casino revenue-audit reconciliation and driver tip/receipt reconciliation, never punches. 'internet down / without internet / lose connection' 8 docs: only the 2015 dial-backup sheet, which is about the card path, plus other publishers. No PDQ document describes the time clock's behaviour with the network down. Retrieved 2026-09-18. https://pdqpos.com/ · retrieved 2026-09-18 adversarially verified

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

labor-granular-rbac

CORRECTED after verification - an earlier pass carried a FABRICATED QUOTATION here and it has been struck. The string 'Master control / Store level control / Station control' does not exist in the source: those are three separate bullets and the slashes were the reader's own. They also sit in the Back Office (POS) column describing back-office administration scope, whereas 'User defined security roles' sits in Employee Management - a different section - so welding them to infer that ROLES are scoped per store and station is a cross-section inference the document never makes. ('Master control' also appears twice, under Back Office and under Cloud-Reporting Service, so the composite was ambiguous as to origin.) What survives, on one conjunct only: 'User defined security roles' and 'Employee roles' establish that roles are OPERATOR-DEFINED rather than fixed cashier/manager/admin tiers. SHORTFALLS: the claim requires permissions grantable per DISCRETE ACTION - void, comp, discount, refund, drawer open, price change, report access - and no document enumerates the permission set or shows per-action granularity; and nothing anywhere states roles are scoped per location. SOURCE DATE: a 2016 first-party sell sheet (uploads/2016/12) recovered from the Internet Archive because pdqpos.com left WordPress and it 404s live. Evidence about the 2016 product. Verified that the live 2025 catalogue restates none of it - the tokens split, gift, transfer, email, security role, happy hour and permission each occur zero times there - so carry-forward rests on PDQ POS being a continuously-sold product line, not on any current document. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-12 adversarially verified

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

labor-manager-override-audit

The catalog's FINGERPRINT READER entry - 'Simply configure the fingerprint reader and save precious seconds at every login and manager override' - establishes that overrides are a distinct flow gated by a biometric login, and the homepage confirms 'secure fingerprint POS log-in' as a system essential, so approvals are attributable to an individual approver. The second half of the claim, an immutable trail queryable after the fact, is not documented: PDQ publishes no manual, help centre or admin guide, and the catalog is hardware marketing with no software content. Unpublished, not shown absent. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

labor-native-scheduling

Downgrading in the other direction: a 'no' here rests on a 2015 reviewer comment ('They don't offer a lot of extras like... scheduling, online ordering, etc') that is demonstrably stale on its other half, since online ordering has since shipped. Third-party profiles describe PDQ managing 'back office operations such as payroll, inventory reporting, station control and coupon management', and the Enterprise Reporting mobile app is described as surfacing labor data. Partner scheduling relationships do not prove native absence. Per the standing rule, absence of documentation is 'unknown' unless a source affirmatively states the absence in the present tense. A denylisted source was also cited for this cell and has been dropped. || 325th: NEW SURFACE, does not settle the cell. PDQ's own 2020 labor article 'Labor: Measure, Understand & React' positions shift scheduling as someone else's product: its cost-containment section is headed 'Best-of-Breed Integrations ...Seamlessly, w/Top Tier Scheduling Providers' and reads 'Seamless integration with the POS / With the POS becoming the "hub" & the POS provider doing the "heavy lifting"' (https://web.archive.org/web/20200924180536/https://www.pdqpos.com/2020/06/22/an-overview-on-labor/). The 2022 Why PDQ software list enumerates what is 'Natively integrated' - custom Online Ordering, Enterprise reporting, Enterprise mobile app, PDQ Rewards/Loyalty, PDQ Delivery Toolkit - and scheduling is not among them, only 'Seamless integration with most 3rd parties' (https://web.archive.org/web/20220627153113/https://www.pdqpos.com/why-pdq/). Both are RETIRED Wayback snapshots of pages the rebuilt pdqpos.com no longer serves, so per merge policy they cannot carry a no; and the 2025 catalogue's module list is introduced by 'including', an open enumeration. Held unknown deliberately: the evidence points to third-party scheduling but no current, first-party, closed enumeration says so. Retrieved 2026-09-17. || 326th: ADDITIONAL CORROBORATION on a new surface, still not a census. PDQ's Integrations page names the scheduling products by brand - 'HOT SCHEDULES', 'KRONOS', 'Macromatix', 'Workday' - under the heading 'Our value-added, Seamless 3rd Party Integrations Include...' (https://web.archive.org/web/20220627152844/https://www.pdqpos.com/integrations/), and the Podcasts index states the division of labour in PDQ's own abstract for its Labor episode: 'A great POS system should amass labor data, provide all-inclusive labor reporting, offer holistic labor cost monitoring and labor forecasting (via sales forecasting), SEAMLESSLY INTEGRATE TO TOP TIER SCHEDULING PROVIDERS & have the latest cost-containing innovations in hardware, software and services' (https://web.archive.org/web/20220627142629/https://www.pdqpos.com/podcasts/). The Employee Management enumeration in the 2016 Feature Overview is a closed five-line list containing no scheduling item. The page ends 'and more!' and no back-office census exists, so this remains a floor, not a publishable `no`. Retrieved 2026-09-18. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. Retrieved 2026-09-18. || 334th: 334th: NEW SURFACES, do not settle the cell. (1) A partner page no pass cited: Crunchtime's live 'PDQ + Crunchtime' integration page (https://www.crunchtime.com/pdq, linked from crunchtime.com/integrations) says 'Automatically sync your key operational data from PDQ into Crunchtime for more accurate forecasting', 'Manage Labor Spend - Optimize your staff schedules by using real-time sales data from your POS', and 'we automatically sync key operational data, including sales and labor' - i.e. a third scheduling product (after Fourth/HotSchedules and Workday/Kronos) consumes PDQ labour data; Fourth's HotSchedules PDQ page (https://www.fourth.com/partner/integrations/point-of-sale/pdq-pos) is still live today and attributes 'schedules, time-off requests, and shift swaps' to HotSchedules. Third-party, grade E, and partner schedulers do not prove native absence. (2) SURFACE NO PASS OPENED: the Android binaries of BOTH apps in PDQ's complete published-app set (the 328th enumerated it three ways: Apple developer lookup id1218876301 returns exactly MY PDQ + PDQ DT; the Google Play developer page lists exactly com.pdqpos.pdqdelivery + com.pdqpos.mypdqpos). (a) PDQ DT, com.pdqpos.pdqdelivery, APK v1.3.4 (47,158,626 bytes, sha256 52ee11e8b22d1d3f..., build files dated 2023-04-21, fetched anonymously from the APKPure mirror because Play serves no APK; Play's current listing is 2.0, updated 2026-05-01, iOS 2.0 (74) 2026-05-06, so the binary is one generation behind the listing): a Xamarin app whose assemblies.blob (XABA, 116 assemblies, XALZ/LZ4) was unpacked, never executed; PDQDT.dll (332,800 bytes, sha256 5263fdd4692e5e60...) #US and #Strings heaps read. (b) MY PDQ, com.pdqpos.mypdqpos v1.3.0, myPdqPos.dll already unpacked by the 332nd (.cache/q332/pdq-pos/h/apk) but never read for labour; its #US heap was read today. Tokenised controls over the #US+#Strings heaps of PDQDT.dll, PDQDT.Android.dll, myPdqPos.dll and myPdqPos.Droid.dll: punch 0, geofenc*/fence 0, schedul* 0, swap 0, overtime 0, payroll 0, wage 0, photo 0, selfie 0 in all four; 'clock' = only 'timeclock' (DT sign-in text x2, MY PDQ page/icon), DT 'clockIcon' (order-time icon beside 'In: {0:T}' / 'On Way' / 'Delivered') and Android Material time-picker resources; POISON NAMED: MY PDQ 'Shift' (x20) is AM/PM SHIFT SALES ('StoreSalesByShift', 'AM Shift:', 'PM Shift:', 'Show Shift Sales'), 'break' is 'Transaction Breakdown'/'HourlySalesBreakdown'/'LineBreakMode', 'tip' is 'tooltip'/'MultiPage', 'radius' is CornerRadius. So neither published app builds or shows a schedule. Held unknown: the store POS and the login-gated back office are unseen, and PDQ's own statements that scheduling is integrated are on retired pages (owner ruling: a retired doc carries no `no`). Retrieved 2026-09-18. adversarially verified

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

labor-demand-labor-forecast

HotSchedules consumes PDQ sales history to forecast — the forecasting lives in the partner, not PDQ. || 325th: NEW SURFACE, does not settle the cell. PDQ's 2020 labor article carries a section headed 'Labor Forecasting... Via Sales Forecasting!' whose entire body is 'Historical, comparative smart sales data via on-demand, secure cloud-based POS reporting CAN GREATLY ASSIST WITH labor forecasting' (https://web.archive.org/web/20200924180536/https://www.pdqpos.com/2020/06/22/an-overview-on-labor/). That is a claim about reporting being an input to a human's forecast, not about the platform generating recommended staffing levels or labor hours by daypart, so it shortfalls the claim's operative verb and cannot support a partial. Held unknown. Retrieved 2026-09-17. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. Retrieved 2026-09-18. || 334th: 334th: NEW SURFACE, does not settle the cell. Crunchtime's live PDQ integration page (https://www.crunchtime.com/pdq) places the forecast in Crunchtime, fed by PDQ: 'Automatically sync your key operational data from PDQ into Crunchtime for more accurate forecasting and business planning' and 'we automatically sync key operational data, including sales and labor ... helping you make proactive decisions on staffing'. A partner's forecast is not the vendor's (third-party product rule). SURFACE NO PASS OPENED: the Android binaries of BOTH apps in PDQ's complete published-app set (the 328th enumerated it three ways: Apple developer lookup id1218876301 returns exactly MY PDQ + PDQ DT; the Google Play developer page lists exactly com.pdqpos.pdqdelivery + com.pdqpos.mypdqpos). (a) PDQ DT, com.pdqpos.pdqdelivery, APK v1.3.4 (47,158,626 bytes, sha256 52ee11e8b22d1d3f..., build files dated 2023-04-21, fetched anonymously from the APKPure mirror because Play serves no APK; Play's current listing is 2.0, updated 2026-05-01, iOS 2.0 (74) 2026-05-06, so the binary is one generation behind the listing): a Xamarin app whose assemblies.blob (XABA, 116 assemblies, XALZ/LZ4) was unpacked, never executed; PDQDT.dll (332,800 bytes, sha256 5263fdd4692e5e60...) #US and #Strings heaps read. (b) MY PDQ, com.pdqpos.mypdqpos v1.3.0, myPdqPos.dll already unpacked by the 332nd (.cache/q332/pdq-pos/h/apk) but never read for labour; its #US heap was read today. Neither app has a forecast: MY PDQ's labour content is reporting only ('Labor %', 'LaborPercentByHour', 'DailyLaborPercent', 'TotalLaborPercentage' beside 'Hourly Sales Breakdown'); forecast/schedul* tokens 0 in all four assemblies. Held unknown. Retrieved 2026-09-18. adversarially verified

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

labor-realtime-labor-percent

Labour cost as a percentage of sales is a first-class figure on the manager-facing dashboard: a "Labor By Store" panel of percentage bars, and a "Labor %" column on every Store Totals row. The date range in the screenshot is Start 4/2/2019 / End 4/2/2019 -- a single current day -- so a same-day reading is evidenced rather than only a next-morning one. Shortfall: "real time during service" is not established. No refresh cadence is stated, the surface is a back-office web dashboard rather than a POS-side or in-service manager view, and nothing indicates the figure updates without re-running the range. The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-software-flyer-lower-res.jpg · retrieved 2026-08-30

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

labor-overtime-prevention

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Labour is evidenced only through reporting. The 2019 Sales Dashboard shows a Labor Summary by job class and a Labor % per store, and the flyer names "Labor Costs" and "Time Clock Reporting" as reporting subject areas, so a POS time clock exists and feeds the reports. Nothing describes the clock's own behaviour or any rules engine on top of it: geofenced or mobile punch, offline punch, overtime prevention, state break compliance, fair-workweek and minor-labour rules, tip-pool computation and its audit trail, qualified-tips W-2 reporting, digital onboarding and I-9. PDQ is also not a scheduling product -- its partners Fourth/HotSchedules and Workday are, and the Fourth partner page describes schedule, sales and forecast data flowing between the two -- so several of these may be intentionally out of scope for the product rather than merely undocumented. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. Retrieved 2026-09-18. adversarially verified

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

labor-break-compliance-by-state

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Labour is evidenced only through reporting. The 2019 Sales Dashboard shows a Labor Summary by job class and a Labor % per store, and the flyer names "Labor Costs" and "Time Clock Reporting" as reporting subject areas, so a POS time clock exists and feeds the reports. Nothing describes the clock's own behaviour or any rules engine on top of it: geofenced or mobile punch, offline punch, overtime prevention, state break compliance, fair-workweek and minor-labour rules, tip-pool computation and its audit trail, qualified-tips W-2 reporting, digital onboarding and I-9. PDQ is also not a scheduling product -- its partners Fourth/HotSchedules and Workday are, and the Fourth partner page describes schedule, sales and forecast data flowing between the two -- so several of these may be intentionally out of scope for the product rather than merely undocumented. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: NEW READING of the Employee Management enumeration for this cell. The 2016 Feature Overview's Employee Management column is a five-line closed list - 'Comprehensive time clock management / User defined security roles / BREAK CALCULATIONS / Employee performance / Payroll' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). 'Break calculations' confirms breaks are tracked and arithmetically handled, but none of the claim's three conjuncts is touched: no per-state or per-jurisdiction rule configuration, no break attestation prompt, and no missed-break/premium-pay flag. PDQ's own 2020 labour article discusses jurisdictional variation only as a cost driver the operator must reason about - 'State minimum wage differentials and differences in tip credit allowances (toward minimum wage) affect the labor cost percentage' (https://web.archive.org/web/20200924180536/https://www.pdqpos.com/2020/06/22/an-overview-on-labor/) - not as a rule the system enforces. Shortfalling every conjunct is not a partial; held unknown. Retrieved 2026-09-18. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. Retrieved 2026-09-18. adversarially verified

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

labor-fair-workweek-support

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Labour is evidenced only through reporting. The 2019 Sales Dashboard shows a Labor Summary by job class and a Labor % per store, and the flyer names "Labor Costs" and "Time Clock Reporting" as reporting subject areas, so a POS time clock exists and feeds the reports. Nothing describes the clock's own behaviour or any rules engine on top of it: geofenced or mobile punch, offline punch, overtime prevention, state break compliance, fair-workweek and minor-labour rules, tip-pool computation and its audit trail, qualified-tips W-2 reporting, digital onboarding and I-9. PDQ is also not a scheduling product -- its partners Fourth/HotSchedules and Workday are, and the Fourth partner page describes schedule, sales and forecast data flowing between the two -- so several of these may be intentionally out of scope for the product rather than merely undocumented. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. Retrieved 2026-09-18. adversarially verified

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

labor-minor-labor-rules

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Labour is evidenced only through reporting. The 2019 Sales Dashboard shows a Labor Summary by job class and a Labor % per store, and the flyer names "Labor Costs" and "Time Clock Reporting" as reporting subject areas, so a POS time clock exists and feeds the reports. Nothing describes the clock's own behaviour or any rules engine on top of it: geofenced or mobile punch, offline punch, overtime prevention, state break compliance, fair-workweek and minor-labour rules, tip-pool computation and its audit trail, qualified-tips W-2 reporting, digital onboarding and I-9. PDQ is also not a scheduling product -- its partners Fourth/HotSchedules and Workday are, and the Fourth partner page describes schedule, sales and forecast data flowing between the two -- so several of these may be intentionally out of scope for the product rather than merely undocumented. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. Retrieved 2026-09-18. adversarially verified

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

labor-tip-pooling-rules

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Labour is evidenced only through reporting. The 2019 Sales Dashboard shows a Labor Summary by job class and a Labor % per store, and the flyer names "Labor Costs" and "Time Clock Reporting" as reporting subject areas, so a POS time clock exists and feeds the reports. Nothing describes the clock's own behaviour or any rules engine on top of it: geofenced or mobile punch, offline punch, overtime prevention, state break compliance, fair-workweek and minor-labour rules, tip-pool computation and its audit trail, qualified-tips W-2 reporting, digital onboarding and I-9. PDQ is also not a scheduling product -- its partners Fourth/HotSchedules and Workday are, and the Fourth partner page describes schedule, sales and forecast data flowing between the two -- so several of these may be intentionally out of scope for the product rather than merely undocumented. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. The only tip mechanics shown are the driver check-out's '-Chg Tips' column and the Delivery Toolkit's 'easy receipt tip reconciliation' (kS_2EDgDGUw, 45 s), which settle a single driver's charged tips, not a pool. Retrieved 2026-09-18. adversarially verified

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

labor-tip-distribution-audit-trail

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Labour is evidenced only through reporting. The 2019 Sales Dashboard shows a Labor Summary by job class and a Labor % per store, and the flyer names "Labor Costs" and "Time Clock Reporting" as reporting subject areas, so a POS time clock exists and feeds the reports. Nothing describes the clock's own behaviour or any rules engine on top of it: geofenced or mobile punch, offline punch, overtime prevention, state break compliance, fair-workweek and minor-labour rules, tip-pool computation and its audit trail, qualified-tips W-2 reporting, digital onboarding and I-9. PDQ is also not a scheduling product -- its partners Fourth/HotSchedules and Workday are, and the Fourth partner page describes schedule, sales and forecast data flowing between the two -- so several of these may be intentionally out of scope for the product rather than merely undocumented. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. The only tip record shown is the per-driver '-Chg Tips' column on the check-out grid (EoHF88VZ9aA, 332-355 s): tips received per driver, with no pool contribution or distribution column. Retrieved 2026-09-18. adversarially verified

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

labor-qualified-tips-w2-reporting

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Labour is evidenced only through reporting. The 2019 Sales Dashboard shows a Labor Summary by job class and a Labor % per store, and the flyer names "Labor Costs" and "Time Clock Reporting" as reporting subject areas, so a POS time clock exists and feeds the reports. Nothing describes the clock's own behaviour or any rules engine on top of it: geofenced or mobile punch, offline punch, overtime prevention, state break compliance, fair-workweek and minor-labour rules, tip-pool computation and its audit trail, qualified-tips W-2 reporting, digital onboarding and I-9. PDQ is also not a scheduling product -- its partners Fourth/HotSchedules and Workday are, and the Fourth partner page describes schedule, sales and forecast data flowing between the two -- so several of these may be intentionally out of scope for the product rather than merely undocumented. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. Retrieved 2026-09-18. adversarially verified

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

labor-native-payroll

No first-party payroll product is marketed; Restaurant365 is the named payroll/HR partner. || 324th: NEW 2026-09-17: the word 'Payroll' IS published by PDQ, as a bullet under 'Employee Management' in the PDQ POS Feature Overview PDF (https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf), beside 'Comprehensive time clock management', 'User defined security roles', 'Break calculations' and 'Employee performance'; the report column adds 'Hours and wages' and 'Hourly labor'. That single word does NOT establish the claim, which requires PDQ to PROCESS payroll first-party (tax filing and direct deposit) rather than export to a provider: (a) nothing anywhere names a filing agent, a direct-deposit funding flow, a W-2/941 obligation or a payroll price; (b) the only published PDQ price list, the Sky River workbook, carries no payroll line among its software SKUs; (c) PDQ's documented labour posture is integration -- Fourth/HotSchedules and Restaurant365 are the named partners. Read 'Payroll' here as a labour reporting/export bullet unless a first-party payroll product is found. Held unknown deliberately. Retrieved 2026-09-17. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. Retrieved 2026-09-18. adversarially verified

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

labor-payroll-export-formats

CLAIM: exports timecards, wages and tips in documented formats or via direct integration for at least two major payroll providers. VERDICT: partial. EVIDENCE: the underlying data exists and is enumerated - 'Comprehensive time clock management', 'Break calculations', 'Payroll', 'Employee performance' under Employee Management, and 'Hours and wages', 'Hourly labor', 'Tip reporting', 'Export to Excel / PDF' under Reports (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf) - and PDQ names 'Kronos' and 'Workday' (plus 'Macromatix', 'DailyPay', 'Branch') as seamless third-party integrations (https://web.archive.org/web/20220627152844/https://www.pdqpos.com/integrations/). SHORTFALL (named): no export FORMAT is documented anywhere (no file layout, no named payroll interface file), and it is not stated that TIPS travel with the timecard export; only an integration partner list and a generic Excel/PDF report export are published. Retrieved 2026-09-18. https://web.archive.org/web/20220627152844/https://www.pdqpos.com/integrations/ · retrieved 2026-09-18 adversarially verified

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

labor-shift-swap-workflow

Shift swap is a HotSchedules capability in the partner integration, not documented as native to PDQ. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. Retrieved 2026-09-18. || 334th: 334th: NEW SURFACE, does not settle the cell. SURFACE NO PASS OPENED: the Android binaries of BOTH apps in PDQ's complete published-app set (the 328th enumerated it three ways: Apple developer lookup id1218876301 returns exactly MY PDQ + PDQ DT; the Google Play developer page lists exactly com.pdqpos.pdqdelivery + com.pdqpos.mypdqpos). (a) PDQ DT, com.pdqpos.pdqdelivery, APK v1.3.4 (47,158,626 bytes, sha256 52ee11e8b22d1d3f..., build files dated 2023-04-21, fetched anonymously from the APKPure mirror because Play serves no APK; Play's current listing is 2.0, updated 2026-05-01, iOS 2.0 (74) 2026-05-06, so the binary is one generation behind the listing): a Xamarin app whose assemblies.blob (XABA, 116 assemblies, XALZ/LZ4) was unpacked, never executed; PDQDT.dll (332,800 bytes, sha256 5263fdd4692e5e60...) #US and #Strings heaps read. (b) MY PDQ, com.pdqpos.mypdqpos v1.3.0, myPdqPos.dll already unpacked by the 332nd (.cache/q332/pdq-pos/h/apk) but never read for labour; its #US heap was read today. Neither of PDQ's two published apps is an employee self-service app: PDQ DT is the delivery-driver app (sign-in by 'Scan QR code from timeclock screen', orders, payment, location) and MY PDQ is the manager reporting client (twelve api/Mobile calls, none about schedules). Tokenised controls over the #US+#Strings heaps of PDQDT.dll, PDQDT.Android.dll, myPdqPos.dll and myPdqPos.Droid.dll: punch 0, geofenc*/fence 0, schedul* 0, swap 0, overtime 0, payroll 0, wage 0, photo 0, selfie 0 in all four; 'clock' = only 'timeclock' (DT sign-in text x2, MY PDQ page/icon), DT 'clockIcon' (order-time icon beside 'In: {0:T}' / 'On Way' / 'Delivered') and Android Material time-picker resources; POISON NAMED: MY PDQ 'Shift' (x20) is AM/PM SHIFT SALES ('StoreSalesByShift', 'AM Shift:', 'PM Shift:', 'Show Shift Sales'), 'break' is 'Transaction Breakdown'/'HourlySalesBreakdown'/'LineBreakMode', 'tip' is 'tooltip'/'MultiPage', 'radius' is CornerRadius. The only swap workflow on any surface is the partner's: Fourth's live HotSchedules PDQ page says 'Employees benefit from streamlined access to schedules, time-off requests, and shift swaps through a unified platform' (https://www.fourth.com/partner/integrations/point-of-sale/pdq-pos) - HotSchedules' feature, not PDQ's (third-party product rule). Held unknown: the claim's 'self-service app' could be web, and the back office is login-gated. Retrieved 2026-09-18. adversarially verified

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

labor-digital-onboarding-i9

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Labour is evidenced only through reporting. The 2019 Sales Dashboard shows a Labor Summary by job class and a Labor % per store, and the flyer names "Labor Costs" and "Time Clock Reporting" as reporting subject areas, so a POS time clock exists and feeds the reports. Nothing describes the clock's own behaviour or any rules engine on top of it: geofenced or mobile punch, offline punch, overtime prevention, state break compliance, fair-workweek and minor-labour rules, tip-pool computation and its audit trail, qualified-tips W-2 reporting, digital onboarding and I-9. PDQ is also not a scheduling product -- its partners Fourth/HotSchedules and Workday are, and the Fourth partner page describes schedule, sales and forecast data flowing between the two -- so several of these may be intentionally out of scope for the product rather than merely undocumented. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). Labour content across all 57 videos is limited to: a 'Time Clock' button on the order-entry home screen and on the Driver Dispatch toolbar (EoHF88VZ9aA, 2016, frames 7 s and 265-306 s; the clock screen is never opened); a 'PDQ POS Manager' screen whose Daily tab offers Register/Driver/Server Functions, Register Payouts, Driver and Server Bank/Drop, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders/Z Report, Quick X, AM Deposit, Z Report, with Reports/Marketing/Settings/Service tabs unopened (EoHF88VZ9aA, 329 s); a driver check-out grid with columns Qty, Total, -Drops, +Banks, -DMR, -Paid Del, -Chg Tips, Balance (EoHF88VZ9aA, 332-355 s: 'on the far right is the balance owed, so in seconds you can check out drivers'); a brochure bullet 'Track waitstaff, orders, tips, banks, timekeeping & more' (PWqryUhZN4E, 48 s); and marketing that kiosks 'reduce labor costs' (KoAg2vwYJ9c, WJl-rwtWvTw). Tokenised, word-boundary, case-insensitive controls over all 43 PDQ speech transcripts (20 caption tracks + 23 ASR): overtime 0, tip pool/tip out 0, onboard* 0, I-9 0, W-4 0, geofenc* 0, punch 0, 'time clock'/timeclock 0 (the only clock-in speech is 'clocked into the pos', CUqcUlcds3A); schedul* 2, payroll 1, break* 4, swap 1 - POISON NAMED: both 'schedule' hits are 'schedule a ... consultation', the one 'payroll' is a Sycuan casino VP saying his tribe 'kept people on payroll' during COVID (yz3p_Ibnu9c), the four 'break' hits are 'breaking the seal', 'ipads break', 'my server break' and 'break it down', and 'swap' is a 'hot-swap warranty'. Frames are not tokenised; the frame reads are listed above. Retrieved 2026-09-18. adversarially verified

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

labor-server-performance-metrics

CLAIM: per-employee sales performance metrics (average check, item/category attachment rate, void and comp rate) by server or cashier. VERDICT: partial. EVIDENCE: 'Employee performance' is a named line item under Employee Management, and the Reports column carries 'Sales & gratuity by employee' and 'Employee reporting' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Per-employee sales attribution is therefore established. SHORTFALL (named): none of the three specific metrics the claim enumerates (average check, attachment rate, void/comp rate per employee) is named; 'Detailed comp, void reasons' and 'Void order history' are reports over the whole store, not per server. The feature sheet gives the axis but not the measures. Retrieved 2026-09-17. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-17 adversarially verified

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

inventory-recipe-bom-costing

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-unit-conversion-yields

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-theoretical-vs-actual

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd: per-cell re-check against surfaces that later passes built. MY PDQ, the mobile client for the myPDQPOS enterprise back office, has a closed report picker, 'Select Available Report', with two entries: 'Store Totals' and 'Void And Promo Report' (App Store screenshots, read in the 328th). So the MOBILE client has no variance report. The web back office is login-gated and its report catalogue is unseen, so no `no`. PDQ's podcast page lists an 'Enterprise reporting' episode about 'the true health of your enterprise as it relates to sales, labor, inventory, and more' (SoundCloud track 1246899784, 2:39). It is audio-only and was not transcribed: there is no speech-to-text tool on this box, and the stream needs a SoundCloud client_id. It would be grade C marketing in any case. Retrieved 2026-09-18. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. CELL-SPECIFIC: 'food costs' and 'full inventory' appear as report subjects on the slide; no theoretical-vs-actual or variance report is named. adversarially verified

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

inventory-realtime-depletion

Counter-signal: in the documented Yellow Dog integration PDQ transmits sales once daily at 9am and Yellow Dog's ProcessSales adjusts on-hands — a batch, partner-owned path. || 332nd: 332nd: NEW SURFACES, do not settle the cell. (1) The PDQ V2 Next.js ordering client (2.65 MB app.js + 52 chunks, on disk from the 331st) tokenised for stock vocabulary: inventory 0, stock 0 (the only hit is androidStock, a browser-detection symbol), onhand/on_hand 0, soldout/outofstock 0, countdown 0. Every availability token is about the STORE or the TIME (isPickupAvailable, availableTimes, isMainGroupAvailable, ensureStoreAvailableOrFailover). So no ingredient on-hand figure reaches the ordering client; the store POS and the login-gated myPDQPOS back office stay unseen. (2) Wayback CDX over the whole mypdqpos.com domain (216 rows) holds the root, jquery, 404 well-known probes and the jjportal/jjsignup/pushapi-3/rewardsimages hosts only; no back-office page was ever archived. (3) certspotter + crt.sh on pdqpos.com: the only unprobed hosts are ftp.pdqpos.com (CerberusFTPServer/11.0, 302 to /login) and session.pdqpos.com (timeout); no documentation host. Retrieved 2026-09-18. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. For THIS cell: 'Fully integrated inventory' is the nearest PDQ words to sale-driven depletion. They do not say that sales deplete ingredients or when, so no partial. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-86-auto-sync

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd: NEW SURFACE, does not settle the cell. The PDQ V2 ordering client (app.js + 52 chunks) carries no ingredient-count or threshold field: inventory 0, stock 0 (excluding androidStock), onhand 0, soldout/outofstock 0. Its availability tokens cover the store, the time and the menu group only. So an 86 driven by ingredient counts would have to be pushed from the server, and the client cannot show whether that happens. The partner Yellow Dog is still the only inventory depletion described anywhere, and it is described on the partner's side. Retrieved 2026-09-18. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. For THIS cell: the demo's order-entry screens (pizza, subs, wings, drinks and beer grids) show no 86/out-of-stock marker or count badge on any button (read at contact-sheet resolution). Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-count-modes

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-mobile-count-offline

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. For THIS cell: the only mobile surfaces in the videos are the tablet POS and the handheld EMV payment device; neither shows a count screen. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-vendor-catalogs-edi

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: NEW READING of the inventory enumeration for this cell. PDQ's inventory module lives in the cloud service, and the 2016 Feature Overview's 'Cloud-Reporting Service' column is a closed six-line list: 'Master control / DETAILED INVENTORY MANAGEMENT / Employee management / VENDORS / Transfer inventory for multi-store units / Comprehensive reporting, with web-based access from any smart device or computer' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). A vendor record therefore exists as a first-class object. None of the claim's substance does: no supplier catalogue import, no EDI, no order guide, no price file, no punch-out. The corpus also shows PDQ routing BOH inventory work to partners - 'Crunchtime' and 'Restaurant 365' are named on the Integrations page (https://web.archive.org/web/20220627152844/https://www.pdqpos.com/integrations/). A bare 'Vendors' line satisfies no conjunct, so this is held unknown rather than made a partial. Retrieved 2026-09-18. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-invoice-ocr

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-price-change-alerts

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-par-auto-suggest

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-waste-logging

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-transfers

CLAIM: inter-location inventory transfers as a two-sided transaction crediting the sender and debiting the receiver, with an in-transit or approval state. VERDICT: partial -- the capability is named for multi-store operators; the two-sided mechanics and any in-transit or approval state are not. EVIDENCE, verbatim from the PDQ POS Feature Overview PDF (https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf), under the heading 'Cloud-Reporting Service': 'Transfer inventory for multi-store units', listed beside 'Detailed inventory management', 'Vendors' and 'Master control'. SHORTFALL NAMED: nothing states that a transfer posts as a paired credit/debit, and no in-transit, pending or approval state is described anywhere. Note also that PDQ's most detailed public inventory evidence remains a PARTNER's doc (Yellow Dog's Fetch API), in which PDQ is the API consumer, so native inventory depth stays largely undocumented. Grade C, retired copy. Retrieved 2026-09-17. https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-17 adversarially verified

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

inventory-commissary

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 325th: MERGE HOLD (proposed partial/C, held unknown): inter-store inventory transfer is an adjacent feature; no production step and no transfer cost, which are the claim. PROPOSAL AS WRITTEN: CLAIM: a commissary/central-kitchen model where one location produces prep items and issues or sells them to other locations at a COMPUTED TRANSFER COST. VERDICT: partial. EVIDENCE: the Feature Overview's Cloud-Reporting Service column enumerates 'Detailed inventory management', 'Vendors' and, explicitly, 'Transfer inventory for multi-store units' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Inter-location inventory transfer within one group is therefore a shipped capability. SHORTFALLS (named): no production or assembly of prep items at one store is described (no build or yield step), and above all NO TRANSFER COST is computed or mentioned - the line records movement, not valuation. Nothing distinguishes a producing commissary from any peer store. Retrieved 2026-09-17. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. CELL-SPECIFIC: 'Transfer inventory for multi-store units' covers only the issue half of the claim. No production of prep items and no computed transfer cost are named, and the merge rule of the 331st says an adjacent back-office module is not a partial, so this stays unknown. adversarially verified

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

inventory-lot-traceability

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-shelf-life-expiry

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-bar-partial-bottle

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. adversarially verified

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

inventory-cogs-gl-export

Upheld on the better source (Restaurant365's own PDQ partner page) rather than the SEO directory. Remains partial: the GL export is a property of R365, not of PDQ, and no PDQ-side mapping or file format is documented. https://www.restaurant365.com/partners/pdq-pos/ · retrieved 2026-08-01 adversarially verified

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

inventory-native-not-partner

Some native inventory exists (listed as a PDQ feature), but deep costing and on-hand management are documented as living in partners — Yellow Dog for casino/resort inventory, Restaurant365 for accounting and inventory. https://help.yellowdogsoftware.com/signaturesystemsinc · retrieved 2026-08-01

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

inventory-menu-margin-linkage

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. A back-office Inventory module demonstrably exists -- "Inventory" is a top-level item on the nav bar in the 2019 back-office screenshot, and "Inventory" is named as a reporting subject area on the same flyer -- and that is the entire first-party evidence for this category. Not one of its features is described anywhere: recipe and BOM costing, unit conversions and yields, theoretical-versus-actual variance, 86 sync, count modes, offline mobile counts, vendor catalogs and EDI, invoice OCR, price-change alerts, par suggestions, waste logging, transfers, commissary, lot traceability, shelf life, partial-bottle pours and menu-margin linkage. The one document that describes inventory behaviour around PDQ is Yellow Dog's integration page, and it documents YELLOW DOG doing the work -- its ProcessSales application matching sales to items and adjusting on-hands -- which is evidence about the partner, not about PDQ's own module. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd (slice g): NEW SURFACE, does not settle the cell. PDQ's own YouTube uploads that no pass had read were downloaded and decoded frame by frame (distinct-frame extraction, frames read as images): 'PDQ POS Demo' (EoHF88VZ9aA, 2016, 369 s, 720p, 209 distinct frames), 'PDQ POS Overview' (YUUejVp2lhY, 2017, 1080p portrait, 120 frames), 'Learn More About PDQ POS' (PWqryUhZN4E, 2017, 1080p, 46 frames), 'PDQ POS' (xvVu3cVQl8I, 2016, 44 frames), plus a re-read of the 332nd's frames of 'PDQ POS Overview (no audio)' (CAtnMz-w59k). What they hold on inventory: (1) the STORE-LEVEL 'PDQ POS Manager' screen (demo at 5:29, Version 3.5.190, dated 1/27/2016) has exactly five bottom tabs, 'Daily', 'Reports', 'Marketing', 'Settings', 'Service', and its Daily tab holds Register/Driver/Server functions, bank/drop, payouts, Service Times, House Accounts, Customer Search, Delay Orders, Charge Card, Calculator, Prev Day Orders, Prev Day Z Report, Quick X, AM Deposit and Z Report; no inventory entry is on the terminal. (2) The myPDQPOS cloud back office's nav bar reads 'Home, Enterprise, Inventory, Rewards, Reporting, Settings' (YUUejVp2lhY at 2:20), and PDQ's brochure panel 'Multi-Store Cloud Reporting' says only 'Live dashboard of all stores' and 'Fully integrated inventory' (PWqryUhZN4E at 0:47). So inventory lives in the login-gated cloud back office, and no frame shows any inventory screen, field or workflow. None of the 20 caption tracks pulled in the 332nd mentions inventory, recipes, food cost or ingredients. Caption tracks for these uploads could not be pulled today (YouTube 429 / IpBlocked; three have captions disabled). The 2025 Product Catalog (1,438 words, on disk from the 332nd) has zero tokens for inventor*, recipe*, ingredient*, 'food cost', waste*, vendor* and stock*. The screens date from 2016-2017 and the back office is gated, so none of this can carry a `no`; 'Fully integrated inventory' is a slogan that names no conjunct of this claim. For THIS cell: PDQ's marketing slide list ('Labor costs ... full inventory ... food costs', read in the 332nd from P1NW60Uw3Gw) names food costs as a reporting topic but does not link them to menu items or margins. Retrieved 2026-09-18. || 334th: 334th (slice g): NEW SURFACES, do not settle the cell. (1) PDQ's own 2017-era slideshow '5 Profit Generating Essentials for POS Systems' (YouTube P1NW60Uw3Gw, 367 s, 1080p; no speech track: faster-whisper returned zero segments, so it was decoded into 182 distinct frames and read as images). Its only inventory content is one slide under '3. Insightful "Business Health" Reporting' (at about 3:20): 'Enterprise-level, Secure Cloud-based Reporting ... Insights: A deep dive into analytical data across the chain, region-to-region, franchisee-to-franchisee... Labor costs, late deliveries, discounts, voids, promos, full inventory, deposit reports, time clock reporting, food costs...'. That is a list of report subjects in marketing copy; it names no recipe, count, vendor, variance, par, waste, lot, expiry or margin mechanism. (2) Inventory partner lists were probed for PDQ: CrunchTime lists PDQ ('we sync your key operational data, helping you track menu popularity and labor spend', https://www.crunchtime.com/integrations); Restaurant365's PDQ page is marketing only; Craftable, WISK, BevSpot, Yellow Dog's public integrations page, meez, Apicbase, Ottimate and Parsley carry zero PDQ/Signature Systems tokens; MarginEdge and xtraCHEF integration URLs 404. Partner capability is the partner's, not PDQ's, as this record already holds. (3) Two further Wayback-only PDQ PDFs were recovered: 'PDQ-SSI-Product-Catalog_Updated.pdf' (2025-08, capture truncated at 5 MiB, 654 words recovered) is a hardware catalogue with zero inventory tokens; 'Catalog2024_Version-1.pdf' and 'PDQ-Technology-Guide-.pdf' (2020) are truncated at 1 MiB in the archive and no text could be recovered. The 2016 'Product Feature Summary' (already cited on inventory-transfers) lists under 'Cloud-Reporting Service' only 'Detailed inventory management', 'Vendors' and 'Transfer inventory for multi-store units'. (4) 16 more PDQ uploads were downloaded for local transcription. Of the 5 short ones that finished, none mentions inventory. A 2019-era customer testimonial (pnlJJvKSEQ8, transcribed in the 333rd) says 'I use the PDQ Management Boards, it helps on my inventory ... it tells me how much dough I did each day'. That is a grade-E-shaped customer anecdote about usage reporting, not a mechanism. 'About PDQ Signature Systems (4 minutes)' (WOb74p-EcYI, 2017, 1080p) was decoded into 358 distinct frames; the 30 read are staff interviews and order-entry screens, with no inventory screen. The inventory UI stays in the login-gated myPDQPOS back office, so nothing here carries a `no`. Retrieved 2026-09-18. CELL-SPECIFIC: 'food costs' as a report subject is not recipe cost joined to item sales mix, and no margin threshold flag is named. adversarially verified

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

reporting-realtime-dashboard

I fetched the cited press release. It says 'a natively integrated enterprise reporting mobile app' and the homepage says 'enterprise reporting suite, among the most complete and easiest to use in the industry'. Neither source contains the word real-time, states a refresh interval, or describes a dashboard. Counter-signal from the one piece of real integration documentation: PDQ posts sales to Yellow Dog once daily at 09:00, which is not a real-time posture. 'A reporting product exists' is partial; 'real-time dashboard' is unevidenced. https://www.pdqpos.com/newsarticles.aspx?rid=PR_000_live_louisiana&nb=true · retrieved 2026-08-01 adversarially verified

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

reporting-eod-closeout

The components exist and are visibly grouped for a close-out: the Store Totals grid gives sales, average ticket and a per-channel split per store; sibling tabs give "Discount Info" and "Credit Card Info" (tender detail); the Miscellaneous Summary carries voids, promos, pay-ins and vouchers; and the flyer's subject line names "Deposits". Shortfall: the claim wants ONE document reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types and expected cash deposit. Nothing shown is that document -- tax, tips and refunds appear nowhere on the dashboard, the pieces sit on four separate tabs, and no EOD or close-out report is named anywhere in PDQ's public material. The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-software-flyer-lower-res.jpg · retrieved 2026-08-30

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

reporting-pmix-modifier-level

Verified: the Yellow Dog page confirms PDQ's sales payload transmits 'Modifiers' and maps by 'Yellow Dog SKU and PDQ ItemNum', so modifier-level data demonstrably exists in the export. Partial is correct because no PMIX report itself is documented. https://help.yellowdogsoftware.com/signaturesystemsinc · retrieved 2026-08-01 adversarially verified

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

reporting-comps-voids-audit

The Sales Dashboard screenshot carries a "Miscellaneous Summary" panel whose rows are Emp Meals, Mgr Meals, Promos, Voided Items, Voids and Voucher, each with a quantity and a dollar total (a sixth row reads as PayIns and is at the limit of the image, so nothing here rests on it); the lower grid has a dedicated "Discount Info" tab beside "Store Totals", "Misc. Info" and "Credit Card Info"; and the flyer's subject line names "Discounts/Voids/Promos". Shortfall, and it is the whole substance of the claim: everything visible is an AGGREGATE. There is no employee attribution, no approving-manager column, no reason code and no timestamp anywhere in the screenshot, and no document describes an exception report. The record's separate finding that manager override is a per-user authenticated action (the catalog's fingerprint reader "at every login and manager override") establishes that an approver exists, not that the report names one. The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-software-flyer-lower-res.jpg · retrieved 2026-08-30

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

reporting-cash-over-short

CLAIM: reports cash over/short per drawer, per shift AND per employee, comparing counted cash to expected cash from tendered transactions and paid-outs. VERDICT: partial -- PDQ publishes a named cash-control report set covering the paid-out and drawer-event halves of the claim; the over/short variance figure itself and its per-employee breakdown are not named. EVIDENCE, verbatim from the PDQ POS Feature Overview PDF (https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Under 'Reports': 'Daily cash in/ out' and 'Cash drawer open history'. Under 'Point-of-Sale Capabilities': 'Cash payout reconciliation', 'Safe drop (pre-determined cash amount in drawer notification)' and 'Dual cash drawer capabilities'. Under 'Point-of-Sale Screen': 'Shift start / end'. SHORTFALL NAMED: the tokens 'over/short', 'over short', 'variance' and 'blind count' are ZERO in the document; no report is named that compares a counted drawer against an expected drawer, and no per-employee cash-accountability report is listed (the employee-axis reports are 'Sales & gratuity by employee', 'Employee reporting' and 'Tip reporting'). Grade C, retired copy. Retrieved 2026-09-17. https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-17 adversarially verified

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

reporting-labor-productivity

The Sales Dashboard screenshot shows a "Labor By Store" bar panel with a labour percentage against each store, a "Labor %" column on every row of the Store Totals grid, and a "Labor Summary" panel breaking labour cost down by job class, each with a headcount and a dollar total: 2nd Assistant Manager, Assistant Manager, Associate, Catering Manager, Driver, Driver Bike, Driver In-Shop and Extra are legible, the panel carries a scrollbar so the list is not complete, and two further rows are cut or too small to read and are not reported here. The flyer's subject line names "Labor Costs" and "Time Clock Reporting", so the figures come from the POS clock. Shortfall: the claim asks for sales per labour hour and labour percentage BY HOUR, BY DEPARTMENT and BY EMPLOYEE. What is evidenced is by STORE and by JOB CLASS. No hourly breakdown, no per-employee row and no SPLH figure appears anywhere. The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-software-flyer-lower-res.jpg · retrieved 2026-08-30

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

reporting-server-scorecards

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Reporting is the one category where a screenshot of the running product exists, and the cells it could reach have been moved. What it cannot reach stays here. The 2019 POS Software flyer shows a Sales Dashboard with store-group and store pickers, a date range, a View button and a Reports button, and names the subject areas as "Labor Costs | Inventory | Sales | Sales Forecast | Deposits | Time Clock Reporting | Discounts/Voids/Promos", closing with "Hundreds of on-demand reports. Custom on-request reports." Nothing in it, or anywhere else on either host, addresses cash over/short per drawer, per-server scorecards, scheduled report delivery, bulk raw export to a customer-controlled destination, outbound webhooks, whether API and raw-data access are upcharged, which plan tier reporting sits behind, the retention window, anomaly alerting, natural-language query, or payroll-ready tip and tip-tax output. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 325th: MERGE HOLD (proposed partial/C, held unknown): the sheet gives sales and gratuity per employee, which are inputs; none of the four metrics the claim names is listed or computed, so the partial shortfalls every conjunct. PROPOSAL AS WRITTEN: CLAIM: per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. VERDICT: partial. EVIDENCE: the Feature Overview's Reports column lists 'Sales & gratuity by employee', 'Employee reporting', 'Tip reporting' and 'Detailed comp, void reasons', and its Employee Management column lists 'Employee performance' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Sales and gratuity are therefore attributed per employee, which is the input the claim's tips-as-a-percentage-of-sales half needs. SHORTFALLS (named): average check, items per check and category attachment rate are NOT among the roughly thirty enumerated reports; the tip percentage is not stated to be computed; and 'Detailed comp, void reasons' is listed as a store report, not as a per-employee rate. Four conjuncts unmet, one met, hence partial. Retrieved 2026-09-17. adversarially verified

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

reporting-channel-profitability

The dashboard's "Sales by Transaction Type" table splits revenue seven ways -- InShop, Web Delivery, Delivery, Drive Thru, Pickup, Web Pick Up, For Here -- with quantity, total, average ticket, share of sales and the same-period figure for Last Year, and the Store Totals grid repeats those channels as per-store columns. So revenue by fulfilment channel is real and is a first-class dimension. Shortfall, and it is what the claim is actually about: these are FULFILMENT MODES, not marketplaces. There is no per-marketplace row -- DoorDash and Uber Eats, which PDQ names as integrations, would both land inside a single "Web Delivery" bucket -- no commission field, and therefore no margin net of marketplace fees anywhere. The report answers "where did the order come from", not "what did it earn". The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-software-flyer-lower-res.jpg · retrieved 2026-08-30

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

reporting-multiloc-drilldown

'PDQ Enterprise Reporting' is marketed for multi-unit operators; side-by-side comparison and transaction drill-down not documented. https://www.pdqpos.com/ · retrieved 2026-08-01

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

reporting-custom-report-builder

Assessed, unresolved -- REGRADED FROM `no` (grade D) ON 2026-08-31. The prior cell called itself "an affirmative absence, not a failure to find", resting on a two-item enumeration in the POS Software flyer on ssipos.com (2019): "Hundreds of on-demand reports. Custom on-request reports." The evidence rules license a `no` when the DOCS enumerate the alternatives and this is not among them, and a marketing flyer is not the docs -- a sales enumeration is the vendor choosing what to advertise on one page, not a statement of what the product does and does not do. It is also seven years old, and a builder could have shipped since without PDQ publishing anything. The evidence itself is unchanged and still points the same way, which is why it is recorded here rather than discarded: "Custom on-request reports" describes a report obtained by REQUESTING it from the vendor, and the flyer's dashboard screenshot of the running product shows only a Store Groups picker, a Stores picker, a date range, View and a Reports button, with no dimension, measure, filter or save surface. That corroborates the shape of a canned library with parameters, but store-and-date parameters over fixed reports are what this claim contrasts ITSELF against, so they do not satisfy a weaker half either and `partial` is not available. PDQ publishes no manual, admin guide or reporting documentation on either of its two sites (www.pdqpos.com and ssipos.com, both enumerated 2026-08-30), so nothing of documentation grade addresses the question in either direction. Source read: https://ssipos.com/wp-content/uploads/2019/09/SSI-software-flyer-lower-res.jpg || 326th: NEW SURFACE, does not settle the cell - and it points the other way, so record it. PDQ's live press-release route (pdqpos.com/newsarticles?rid=..., real content versus a 48.7 KB nonsense-rid shell) describes report customisation as work PDQ'S OWN STAFF perform for the customer, not as a self-service builder: 'In addition to converting the hardware, THE PDQ POS DEVELOPMENT TEAM ALSO CUSTOMIZED DOZENS OF FUNCTIONS AND REPORTS to maintain continuity for servers and managers following the conversion' (https://pdqpos.com/newsarticles?rid=PR_82724_sycuan, Sycuan Casino Resort, 2024-08-27). The same posture governs menus: PDQ's Podcasts index, 'Menu Management - ... Our expert IN-HOUSE MENU TEAM will happily make your menu changes, promptly and effectively' (https://web.archive.org/web/20220627142629/https://www.pdqpos.com/podcasts/). Against that, the Feature Overview's Reports column is a fixed list of about thirty named canned reports with no builder, no dimension/measure picker and no saved-view concept (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). This is suggestive of a `no` but the corpus is marketing, not a census of the back office, so it is held unknown rather than published. Retrieved 2026-09-18. || 327th: 327th: NEW SURFACE, does not settle the cell, but it answers the age objection the existing note raises against itself. The existing note discounts the 2019 flyer's 'Custom on-request reports' partly because it 'is also seven years old, and a builder could have shipped since without PDQ publishing anything.' SSI's 2022 whitepaper, recovered in full this session, restates the same operating model three years later and sells it as the differentiator: what the buyer should want is 'the development team's willingness to provide customization, all required integrations, and timely new feature releases (again without cost)' (https://ssipos.com/wp-content/uploads/2022/06/SSI-3-Vital-Things-to-Consider.-article.pdf). The live ssipos.com casino product page, modified 2026-08-19 and fetched from the publisher's own WordPress REST manifest this session, says the same thing in the present tense - 'Custom, agile, fast-cycle, in-house development' and 'extensive cloud-based analytical reporting built into the POS' - with no mention of an operator-facing builder (https://ssipos.com/signature-systems-casino-pos-system/). So the 2019 flyer's shape is corroborated at 2022 and again at 2026 by two independent vendor documents: report customisation is work PDQ's own staff perform on request. This remains marketing prose rather than documentation, so it still cannot carry a `no`, and store-and-date parameters over canned reports are what the claim contrasts itself against, so `partial` is still not available. Held unknown, with the age objection now retired. Retrieved 2026-09-18. || 328th: 328th (APPS SLICE): NEW SURFACE, deliberately NOT scored. MY PDQ's 'Reports' screen is a closed picker headed 'Select Available Report' listing exactly two entries, 'Store Totals' and 'Void And Promo Report', and the vendor's own 1.3.0 release note ships a report as a version feature ('Added new report for Hourly Sales'), which is the signature of a fixed catalogue. Held unknown rather than no because this enumeration bounds the MOBILE CLIENT of the back-office only: the myPDQPOS web portal it reads from is login-gated and its report catalogue is server-side, which no app screenshot can see. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE, does not settle the cell. It shows the SHAPE of the portal's report catalogue from the vendor's own data model, which the 328th said no app screenshot could see. the MY PDQ Android app (package com.pdqpos.mypdqpos, v1.3.0, the enterprise-reporting companion listed at https://play.google.com/store/apps/details?id=com.pdqpos.mypdqpos; APK 22,026,521 bytes, sha256 ff00754cb51bb668..., fetched anonymously from the APKPure mirror because Play serves no APK). It is a Xamarin.Forms app, so its logic ships as .NET assemblies compressed with XALZ/LZ4. Unpacked, never executed: myPdqPos.dll decompressed to 516,608 bytes (sha256 fecfd249d00c113e...), with 6,690 UTF-16 and ASCII strings read out. A report is a server-side catalogue RECORD, not a user-built query: 'ReportId', 'ReportShortId', 'ReportName', 'ReportTitle', 'ReportDescription', 'ReportCategoryName', 'ReportType', 'ReportSort', 'ReportPermissionId', 'ReportButtonText', 'ReportButtonColor', plus a boolean 'IsCustomReport'. A flag that marks some catalogue entries as custom fits the vendor's 'Custom on-request reports' model already in this note: custom reports are rows PDQ adds to a catalogue. No dimension, measure, filter-definition or saved-view field exists anywhere in the model. Held unknown, not `no`: the DTOs are a client's view of the portal, and the portal UI itself (mypdqpos.com) is login-gated. Retrieved 2026-09-18. adversarially verified

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

reporting-scheduled-delivery

CLAIM: ANY report can be scheduled for automatic recurring delivery by email or to a shared destination, on a defined cadence and recipient list. VERDICT: partial -- automatic emailing to a multi-recipient list exists but is documented for ONE report only, and no cadence control is described. EVIDENCE, verbatim from the PDQ POS Feature Overview PDF (https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf), 'Reports' column: 'Credit card settlement', 'CC settlement auto email', 'Email to multiple emails', 'Export to Excel / PDF', 'Web-based access from any smart device or computer'. So a recipient LIST is supported and at least one report is auto-emailed. SHORTFALL NAMED: the auto-email is bound to credit-card settlement, an end-of-day event, not to an arbitrary report; no schedule or cadence control, no daily/weekly/monthly language and no SFTP or shared-destination option appears on any PDQ surface. Grade C, retired copy. Retrieved 2026-09-17. https://web.archive.org/web/2016id_/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-17 adversarially verified

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

reporting-raw-warehouse-export

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Reporting is the one category where a screenshot of the running product exists, and the cells it could reach have been moved. What it cannot reach stays here. The 2019 POS Software flyer shows a Sales Dashboard with store-group and store pickers, a date range, a View button and a Reports button, and names the subject areas as "Labor Costs | Inventory | Sales | Sales Forecast | Deposits | Time Clock Reporting | Discounts/Voids/Promos", closing with "Hundreds of on-demand reports. Custom on-request reports." Nothing in it, or anywhere else on either host, addresses cash over/short per drawer, per-server scorecards, scheduled report delivery, bulk raw export to a customer-controlled destination, outbound webhooks, whether API and raw-data access are upcharged, which plan tier reporting sits behind, the retention window, anomaly alerting, natural-language query, or payroll-ready tip and tip-tax output. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

reporting-public-api

Upheld and now cited, but the old rationale's premise was wrong in one half. It said there is no API reference and no self-serve credentials anywhere; the first part of that is right and the second overstates. PDQ does assert an API on its live site: the About-SSI boilerplate of this press release, served today from the vendor's own host, lists 'value-added integrations via RESTful APIs' among its products and services, and it does so in 6 documents of the corpus. Five Signature Systems press releases go further and say 'RESTful APIs with full documentation' -- so documentation exists; it is not published. The claim asks for a documented public REST or GraphQL API over orders, payments, menu and labor WITH credentials obtainable without a signed partner agreement, and neither half is reachable. Probed 2026-09-09: developer.pdqpos.com, docs.pdqpos.com, api.pdqpos.com, support.pdqpos.com and status.pdqpos.com all fail DNS resolution; www.pdqpos.com serves no robots.txt (404) and answers a hard ASP.NET 'The resource cannot be found' for /api, /developers and /pricing that is the same shape as a fabricated control, so no soft-200 is hiding a portal. Across a 151-document corpus assembled 2026-09-09 (102 archived pdqpos.com pages, the 6 live pages, the 6 live rid/pk detail pages, 13 ssipos.com WordPress documents and 24 vendor PDFs; 733,737 characters, every PDF extracted twice, in layout and in reading order) -- and every zero below held unchanged as the corpus grew from 145 to 176 extractions, `swagger`, `openapi`, `oauth`, `webhook`, `webhooks`, `sdk` and `api key` occur zero times, tokenised and as bare substrings alike, while the present-controls read restful in 14 documents and integration in 42. https://www.pdqpos.com/newsarticles.aspx?rid=PR_924_bonanza&nb=true · retrieved 2026-09-09

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

reporting-webhooks

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Reporting is the one category where a screenshot of the running product exists, and the cells it could reach have been moved. What it cannot reach stays here. The 2019 POS Software flyer shows a Sales Dashboard with store-group and store pickers, a date range, a View button and a Reports button, and names the subject areas as "Labor Costs | Inventory | Sales | Sales Forecast | Deposits | Time Clock Reporting | Discounts/Voids/Promos", closing with "Hundreds of on-demand reports. Custom on-request reports." Nothing in it, or anywhere else on either host, addresses cash over/short per drawer, per-server scorecards, scheduled report delivery, bulk raw export to a customer-controlled destination, outbound webhooks, whether API and raw-data access are upcharged, which plan tier reporting sits behind, the retention window, anomaly alerting, natural-language query, or payroll-ready tip and tip-tax output. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

reporting-api-not-upcharged

CORRECTED after verification; same defect and same cell as extensibility-api-access-cost. The workbook prices API and reporting access as two separate annual per-device lines on top of the base licence: 'API Reporting Interface - Annual' at SUM(B35+B48+B49)*115 (115 per device per year) and 'SSI POS Enterprise Reporting - Annual' at SUM(B35+B48+B49+B52+B53+B54+B55)*228 (228 per device per year). Both render 0 purely because the device quantities are unfilled. API and raw-data access are therefore NOT included in the standard subscription. No revenue share and no enterprise-only contract requirement is stated, but the claim fails on the per-location/per-device fee limb alone. PROVENANCE LIMIT: this is one workbook, dated serial 44319 = 2021-05-03, published on https://ssipos.com/sky-river/ as a landing page addressed 'for WILTON RANCHERIA SKY RIVER', carrying a buyer-specific 'Boyd Discount' line which applies only to the base-licence row. It is the vendor's only published pricing artefact; treat it as evidence about PDQ's 2021 commercial model, not a current restaurant-segment price list. https://ssipos.com/wp-content/uploads/2021/04/Sky-River-Casino-Quote-05-3-21.xlsx · retrieved 2026-09-12 adversarially verified

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

reporting-tier-paywall

331st: THE CELL WAS NEVER CHECKED against the vendor's published pricing workbook, which already carries three other cells (reporting-api-not-upcharged, extensibility-api-access-cost, commercial-module-unbundling). CLAIM: core reporting beyond basic sales summaries (labor vs sales, PMIX, comps/voids audit, multi-location comparison) is on the entry-level paid plan, not behind a higher tier or an add-on analytics SKU. VERDICT: partial. EVIDENCE: the workbook is linked from ssipos.com's own 'Sky River' page as an 'Interactive Excel-Based Pricing List' (https://ssipos.com/wp-content/uploads/2021/04/Sky-River-Casino-Quote-05-3-21.xlsx, 200, 116,626 bytes; sheet1 read cell by cell, formulas included). Its only software licence row is 'SSI POS Pro Site License, Unlimited Users, Perpetual'; there is no Basic/Pro/Enterprise tier ladder. Reporting appears in two places only, both as separate annual subscriptions under 'Subscriptions': row 20 'SSI POS Enterprise Reporting - Annual', unit price =SUM(B35+B48+B49+B52+B53+B54+B55)*228 (228 dollars per year for each terminal, tablet, kiosk and menu-board device), and row 21 'API Reporting Interface - Annual' at *115. The enterprise product is the cloud, multi-store layer: SSI's own brand list calls it 'SSI Enterprise natively integrated cloud-based enterprise-level reporting/analytics' (https://ssipos.com/wp-content/uploads/2022/05/SSI-Security.pdf). The 2016 Feature Overview puts multi-store functions in a separate 'Cloud-Reporting Service' column ('Transfer inventory for multi-store units', 'Comprehensive reporting, with web-based access'). The MY PDQ enterprise app's Store Totals is the report that rolls up 'All Locations' / 'All Assigned Stores' (vendor App Store screenshots, id1218876302). WHAT IS INCLUDED: the store-level reports the claim names are listed as PDQ POS features in the Feature Overview's Reports column: 'Hourly labor', 'Hours and wages', 'PLU / Item reporting', 'Top sales items', 'Void order history', 'Detailed comp, void reasons', 'Employee reporting'. None of them has a SKU of its own in the price list. SHORTFALL (named): multi-location comparison, one of the claim's four examples, needs the separately priced annual Enterprise Reporting add-on. Also flagged: the Feature Overview marks 'Inventory reporting (w/cloud service)'. CAVEATS: the workbook is a 2021 casino proposal with a prospect-specific discount row ('Boyd Discount'), so it is grade C. The link between Enterprise Reporting and the multi-store roll-up is drawn from SSI's own product descriptions; the workbook does not say it in one sentence. Retrieved 2026-09-18. https://ssipos.com/wp-content/uploads/2021/04/Sky-River-Casino-Quote-05-3-21.xlsx · retrieved 2026-09-18 adversarially verified

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

reporting-history-retention

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Reporting is the one category where a screenshot of the running product exists, and the cells it could reach have been moved. What it cannot reach stays here. The 2019 POS Software flyer shows a Sales Dashboard with store-group and store pickers, a date range, a View button and a Reports button, and names the subject areas as "Labor Costs | Inventory | Sales | Sales Forecast | Deposits | Time Clock Reporting | Discounts/Voids/Promos", closing with "Hundreds of on-demand reports. Custom on-request reports." Nothing in it, or anywhere else on either host, addresses cash over/short per drawer, per-server scorecards, scheduled report delivery, bulk raw export to a customer-controlled destination, outbound webhooks, whether API and raw-data access are upcharged, which plan tier reporting sits behind, the retention window, anomaly alerting, natural-language query, or payroll-ready tip and tip-tax output. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

reporting-anomaly-alerts

CLAIM: proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern. VERDICT: partial. NEW SURFACE: PDQ's Mobile Reporting page, never read in a prior pass, closes its feature list with: 'Plus: Configurable Text/Email Alerts when large orders are voided, AM/PM deposits are made, large catering orders are placed and details of over/under' (https://web.archive.org/web/20150731053525/http://pdqpos.com/mobile-reporting/). That is a configurable, push-delivered (text/email) alert set whose triggers are threshold-shaped ('large' voids, 'large' catering orders, cash over/under) - the threshold branch of the claim, on the operator's own device. SHORTFALLS (named): the page does not say the THRESHOLD ITSELF is operator-set (only that the alerts are 'configurable'), lists a fixed set of four trigger types rather than an arbitrary metric, and nothing anywhere describes deviation-from-historical-pattern detection (no forecast, no anomaly language). Differentiator weight on a grade-C marketing page, so partial rather than yes. Retrieved 2026-09-18. https://web.archive.org/web/20150731053525/http://pdqpos.com/mobile-reporting/ · retrieved 2026-09-18 adversarially verified

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

reporting-nl-query

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Reporting is the one category where a screenshot of the running product exists, and the cells it could reach have been moved. What it cannot reach stays here. The 2019 POS Software flyer shows a Sales Dashboard with store-group and store pickers, a date range, a View button and a Reports button, and names the subject areas as "Labor Costs | Inventory | Sales | Sales Forecast | Deposits | Time Clock Reporting | Discounts/Voids/Promos", closing with "Hundreds of on-demand reports. Custom on-request reports." Nothing in it, or anywhere else on either host, addresses cash over/short per drawer, per-server scorecards, scheduled report delivery, bulk raw export to a customer-controlled destination, outbound webhooks, whether API and raw-data access are upcharged, which plan tier reporting sits behind, the retention window, anomaly alerting, natural-language query, or payroll-ready tip and tip-tax output. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 327th: 327th (APPS/HOSTS SLICE): NEW SURFACE, does not settle the cell. The MY PDQ app is PDQ's own description of the enterprise reporting product on mobile and it is an entirely canned-report product: 'MY PDQ is 100% cloud-based reporting specially formatted for use on your mobile device', 'gain access to your POS sales data specifically tailored for use on your mobile device', and its release notes for 1.3.0 read 'Added new menu option to manage preferences / Added new report for Hourly Sales'. Adding a fixed 'Hourly Sales' report as a version feature is the signature of a fixed report catalogue, not an ad-hoc query engine. Held unknown, not scored no: this is the MOBILE client of the back-office, and the myPDQPOS web portal it reports on is login-gated (mypdqpos.com serves only an ASP.NET/Telerik 2019 login page; its subdomains are a wildcard catch-all - rewardsimages.mypdqpos.com returns byte-identical 21,489-byte login HTML), so the reporting UI's full feature set is unobserved. Retrieved 2026-09-18. adversarially verified

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

reporting-guest-cohorts

The reporting suite is described as a 'Customer Data Management (CDM)' platform, implying guest-level analytics; no cohort or new-vs-returning reporting is documented. https://www.pdqpos.com/ · retrieved 2026-08-01

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

reporting-sales-forecast

The POS Software flyer names the reporting platform's subject areas in a single line -- "Labor Costs | Inventory | Sales | Sales Forecast | Deposits | Time Clock Reporting | Discounts/Voids/Promos" -- so a sales forecast is a named, shipped area of the Enterprise Reporting product rather than something inferred. Shortfall: that line is the whole of the evidence. No granularity is stated (the claim wants daypart or hourly), the forecast is not visible on the dashboard screenshot, and nothing shows it being consumed by a scheduling or ordering workflow. The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-software-flyer-lower-res.jpg · retrieved 2026-08-30

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

reporting-tip-tax-compliance

CLAIM: payroll- and tax-ready tip reporting - declared versus charged tips per employee, tip-pool distribution detail, and a tax liability summary by jurisdiction. VERDICT: partial. EVIDENCE: the 2016 Feature Overview's roughly thirty-line Reports enumeration contains 'TIP REPORTING', 'SALES & GRATUITY BY EMPLOYEE', 'Hours and wages', 'Tax reporting' and 'Export to Excel / PDF' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Per-employee gratuity attribution and a tip report therefore exist and can leave the system. SHORTFALLS (named): DECLARED versus CHARGED tips are not distinguished; no tip-pool distribution detail appears (no pooling feature is documented at all); and 'Tax reporting' is a sales-tax report line with no tip tax-liability or per-jurisdiction dimension. Retrieved 2026-09-18. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-18 adversarially verified

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

multi-location-org-hierarchy

The Sales Dashboard's two leftmost controls are "Store Groups:" and "Stores:", both multi-select and both defaulting to "*** (All Groups Selected) ***" / "*** (All Stores Selected) ***", and the grid beneath rolls up stores from two visibly different brands at once (GAB Terminal B/C/D alongside JJ #90048, #90031, #90015). "Enterprise" is also a top-level item on the back-office nav bar. So an enterprise > store-group > store grouping exists as a real object that reporting is scoped to. Two shortfalls. First, reporting is the only scope shown -- nothing evidences permissions being scoped to a group, which is half the claim. Second, and it cuts against the reading: Yellow Dog's integration documentation says that in PDQ "normally each Property ... would be considered a separate instance", and that multiple Yellow Dog stores can be mapped to a single PDQ store -- an instance-per-property topology sits awkwardly beside a single enterprise tree, and no PDQ document reconciles them. The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-software-flyer-lower-res.jpg · retrieved 2026-08-30

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

multi-location-central-menu-publish

CLAIM: a corporate menu authored once and published to a CHOSEN SET of locations in a single action, with a publish/version history showing what was pushed, when and by whom. VERDICT: partial. EVIDENCE: a surface new to this record - the Corporate America (March 2017) cover-interview PDF hosted on pdqpos.com, quoting John White, EVP/CTO of PDQ Signature Systems, verbatim: 'With POS integration, menu changes can almost instantly occur franchise-wide, to select stores by region, or to a single location... whatever's necessary!' (https://web.archive.org/web/20191218141745/https://www.pdqpos.com/wp-content/uploads/2017/03/Corp-America-March-2017-POS-TheNeedForSpeed-with-cover.pdf). That is the claim's targeting half stated by the vendor's CTO: franchise-wide, a regional subset, or one store. The same interview calls PDQ's 'cloud-based franchise management platform' a distinct product. Corroborating first-party config hierarchy: the Feature Overview's Back Office (POS) column enumerates 'Master control', 'Store level control' and 'Station control' as three levels (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). SHORTFALLS (named): there is NO publish/version history - nothing records what was pushed, when, or by whom, and no rollback is described; and PDQ performs 'Custom menu creation at no extra cost' with 'Unlimited menu updates at no extra cost' as a SERVICE (https://web.archive.org/web/20220627153113/https://www.pdqpos.com/why-pdq/), which leaves open how much of the publish is operator-driven. Grade D (vendor-hosted advertorial quoting its own CTO). Retrieved 2026-09-17. https://web.archive.org/web/20191218141745/https://www.pdqpos.com/wp-content/uploads/2017/03/Corp-America-March-2017-POS-TheNeedForSpeed-with-cover.pdf · retrieved 2026-09-17 adversarially verified

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

multi-location-local-override-policy

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Multi-unit operation is real and its mechanics are unpublished. The 2019 dashboard proves cross-store rollup with a "Store Groups" picker above a "Stores" picker, and both sites market PDQ Enterprise Reporting to multi-unit operators; the catalog's About page says the product is "designed for independents, franchises and chains of all sizes". Against that, Yellow Dog's integration page states that in PDQ "normally each Property ... would be considered a separate instance", which is an instance-per-property topology rather than one tenant with many stores. Nothing published resolves that, and nothing describes central menu publishing, local override policy, price zones, scheduled publish, new-store templating, corporate-versus-franchisee roles, royalty calculation or collection, normalised item rollup, cross-location gift cards or loyalty, multi-jurisdiction tax, a config audit log or central labour policy. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: MERGE HOLD (proposed partial/C, held unknown): three headings ('Master control / Store level control / Station control') name tiers but describe no lock/permit mechanism and no override policy; the same words already carry menu-pricing-franchise-hierarchy. PROPOSAL AS WRITTEN: CLAIM: corporate can lock or permit specific settings per location, with a documented override policy. VERDICT: partial. EVIDENCE: PDQ publishes a named three-tier configuration hierarchy - the 2016 Feature Overview's Back Office column begins 'Master control / Store level control / Station control' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf), and the Enterprise page frames the same product as 'Full-featured, Web-based Management Solution for Your Multi-location Enterprise! From 2 To 2000+' (https://web.archive.org/web/20150731053407/http://pdqpos.com/enterprise/). Tiered scope therefore exists and a store tier is distinguishable from the master tier. SHORTFALL (named): no document states which settings the store tier may change, whether the master tier can LOCK a setting, or that any override policy is published. Retrieved 2026-09-18. adversarially verified

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

multi-location-price-zones

332nd: THIS CELL WAS NEVER CHECKED on its own. Its note is the category boilerplate, but evidence already in the record for two sibling cells meets two of this claim's three axes. CLAIM: one menu item carries different prices per location group, per order channel and per daypart, without duplicating the item record. VERDICT: partial. EVIDENCE (channel axis, current vendor code, grade B): PDQ's V2 ordering client types each menu item as ONE record with a base price plus a price-level array: 'BasePrice:s.z.number().optional().nullable(),ExtendPrice:s.z.array(s.z.any()).optional().nullable()' (https://marylandlive.pdqonlineordering.com/_next/static/chunks/1wv3xur2ou__5.js). The store's price setup returns 'BaseSettings:s.z.array(s.z.object({Type:s.z.string(),PriceIndex:s.z.number()}))' (same chunk), and the client picks the level by channel: 'let e={9:"Delivery",8:"Pickup"},t=y??8;return I.priceSetup.BaseSettings?.find(r=>r.Type===e[t])?.PriceIndex??1' (same chunk; the menu-pricing-channel-price-books cell already cites the getItemPrice lookup in 3-pqppw_7-kgz.js). So one item record carries a separate price for each channel, with no copy of the item. EVIDENCE (daypart axis, retired pages, corroboration only): ProTable 'can AUTOMATICALLY CHANGE THE PRICE OF ITEMS BASED ON TIME OF DAY OR DAY OF WEEK. UP TO FOUR DIFFERENT PRICES FOR AN ITEM can be used' (https://web.archive.org/web/20041208124200/http://www.pdqpos.com/table.htm). The 2016 Feature Overview carries the same primitive forward as 'Automated event scheduling (specials, promotions, happy hour, etc.)' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Again that is several prices on one item. A HOMONYM CHECKED AND EXCLUDED: the same schema has 'BasePrice2/ExtendPrice2/POSItemNum2/POSItemName2', but the cart code pushes it as a SECOND POS line ('POSItemCode:r?.mainSectionItem.POSItemNum2 ... ModID:1'). That is a linked add-on item, not a price level, so it is neither evidence for this claim nor evidence of item duplication. SHORTFALL (named): the LOCATION-GROUP axis is unshown. No price zone or price group appears in the V2 schema, in the 33 /api/online endpoints, or in the MY PDQ app's data model, which carries StoreGroupId/StoreGroupName and MasterMenuId but no price attached to a group. Retrieved 2026-09-18. https://marylandlive.pdqonlineordering.com/_next/static/chunks/1wv3xur2ou__5.js · retrieved 2026-09-18 adversarially verified

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

multi-location-scheduled-publish

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Multi-unit operation is real and its mechanics are unpublished. The 2019 dashboard proves cross-store rollup with a "Store Groups" picker above a "Stores" picker, and both sites market PDQ Enterprise Reporting to multi-unit operators; the catalog's About page says the product is "designed for independents, franchises and chains of all sizes". Against that, Yellow Dog's integration page states that in PDQ "normally each Property ... would be considered a separate instance", which is an instance-per-property topology rather than one tenant with many stores. Nothing published resolves that, and nothing describes central menu publishing, local override policy, price zones, scheduled publish, new-store templating, corporate-versus-franchisee roles, royalty calculation or collection, normalised item rollup, cross-location gift cards or loyalty, multi-jurisdiction tax, a config audit log or central labour policy. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: MERGE HOLD (proposed partial/C, held unknown): a case-study sentence about simultaneous national LTO launches says nothing about operator-scheduled future activation, per-location timezones or rollback. PROPOSAL AS WRITTEN: CLAIM: menu/price/promo changes scheduled to activate at a future date-time in each target location's own timezone, and rollable back after activation. VERDICT: partial. NEW SURFACE: pdqpos.com's live case-study pages (ProjectDetail?pk=..., reached through the ASP.NET route /ProjectDetail, which a nonsense pk returns a 47.8 KB shell for versus 50.8 KB with content - so this is real content, not a soft-200). The Jimmy John's study states: 'Jimmy John's also routinely offers limited time offers, working with Signature Systems, Inc. to launch each offer ACROSS THE COUNTRY SIMULTANEOUSLY AND WITHOUT ERROR so that customers in Maine can have the same experience as those in California' (https://pdqpos.com/ProjectDetail?pk=jjsw). The scheduling primitive is published separately as 'Automated event scheduling (specials, promotions, happy hour, etc.)' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). SHORTFALLS (named): 'simultaneously' is the OPPOSITE of the claim's per-location-timezone interpretation, and no rollback-after-activation is described anywhere. Retrieved 2026-09-18. adversarially verified

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

multi-location-new-store-template

332nd: THIS CELL WAS NEVER CHECKED on its own. Its note is the category boilerplate. CLAIM: a new location is provisioned by cloning a documented configuration template rather than configured from scratch, AND the vendor publishes the expected time-to-open. VERDICT: partial, on the second conjunct only. EVIDENCE: PDQ's own Service & Support page (https://web.archive.org/web/20160617020618/http://www.pdqpos.com/service-support/, re-fetched today; WordPress post dated 2016-04-18; retired, so it can carry a positive only up to partial) publishes the opening timeline: 'Most installations take just one to two days. After your installation and training are complete, we will "go live" in real time to ensure you have a smooth transition.' The same page says 'All new equipment is staged in our state-of-the-art facility', which is vendor-side pre-configuration before the store opens. SHORTFALL (named, and it points AWAY from the template conjunct): nothing describes cloning a store configuration. PDQ's own pricing workbook prices setup as vendor labour PER PROFIT CENTRE: 'Configuration of profit center and menu development (per profit center)', 'Hardware Installation (per profit center)' and '"Go Live" support (per day)' (https://ssipos.com/wp-content/uploads/2021/04/Sky-River-Casino-Quote-05-3-21.xlsx, sharedStrings). That reads as per-site configuration work the vendor does, not an operator cloning a template. The MY PDQ app's data model has a 'UserTemplateID', but that is a template for USER access, not for a store. Retrieved 2026-09-18. https://web.archive.org/web/20160617020618/http://www.pdqpos.com/service-support/ · retrieved 2026-09-18 adversarially verified

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

multi-location-corp-vs-franchisee-roles

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Multi-unit operation is real and its mechanics are unpublished. The 2019 dashboard proves cross-store rollup with a "Store Groups" picker above a "Stores" picker, and both sites market PDQ Enterprise Reporting to multi-unit operators; the catalog's About page says the product is "designed for independents, franchises and chains of all sizes". Against that, Yellow Dog's integration page states that in PDQ "normally each Property ... would be considered a separate instance", which is an instance-per-property topology rather than one tenant with many stores. Nothing published resolves that, and nothing describes central menu publishing, local override policy, price zones, scheduled publish, new-store templating, corporate-versus-franchisee roles, royalty calculation or collection, normalised item rollup, cross-location gift cards or loyalty, multi-jurisdiction tax, a config audit log or central labour policy. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 327th: 327th (APPS/HOSTS SLICE): NEW SURFACE, does not settle the cell, but it proves the enterprise/franchise product is live and current. PDQ runs a per-brand enterprise portal: jjportal.mypdqpos.com serves a live login page titled 'Jimmy John's Enterprise' footed 'Copyright (c) Signature Systems 2026 - V144', and jjsignup.mypdqpos.com serves a second live page, 'Welcome to Jimmy John's Portal! ... powered by Signature Systems, Inc'. The ordering product is franchise-aware too: the Wayback index for pdqonlineordering.com contains '/?FranchiseID=d518a417-bce9-4553-8cdc-055e95de6638', and each tenant carries its own store-level Manager pages (ManagerLogin.aspx, Manager/ManagerOrders.aspx, Manager/ManagerSettings.aspx) distinct from the corporate host admin.pdqonlineordering.com. That is a two-tier corporate/store structure, but every one of these pages is a login form - no role, scope or permission is visible - and admin.pdqonlineordering.com returns 403 to every path INCLUDING a nonsense control, i.e. a blanket refusal, never an absence. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE, does not settle the cell: the MY PDQ Android app (package com.pdqpos.mypdqpos, v1.3.0, the enterprise-reporting companion listed at https://play.google.com/store/apps/details?id=com.pdqpos.mypdqpos; APK 22,026,521 bytes, sha256 ff00754cb51bb668..., fetched anonymously from the APKPure mirror because Play serves no APK). It is a Xamarin.Forms app, so its logic ships as .NET assemblies compressed with XALZ/LZ4. Unpacked, never executed: myPdqPos.dll decompressed to 516,608 bytes (sha256 fecfd249d00c113e...), with 6,690 UTF-16 and ASCII strings read out. It shows the ENTERPRISE PERMISSION MODEL the myPDQPOS portal serves to its clients. The tenant key is the franchise ('FranchiseID', 'FranchiseUrl', 'MasterMenuId'), with stores and store groups beneath it ('StoreGroupId', 'StoreGroupName', 'AllStoreIdList', and the picker strings '*** All Groups ***' and '*** (Select Store) ***'). Users are scoped PER STORE and PER PAGE/REPORT: 'UserStorePermissions', 'UserStorePermissionId', 'UserPagePermissions', 'ReportPermissions', 'RequiredPermissionId', and a permission tree ('UserPermissionId', 'UserPermissionShortId', 'UserPermissionParentShortId', 'UserPermissionCategoryName'). They are provisioned from a 'UserTemplateID', and 'IsPDQUser' marks PDQ's own staff. The app ships a User Access screen ('Add New User', 'Search Users...', 'All Assigned Stores'; API methods UserAccessGetUsers, UserAccessGetStores, UserAccessLoadDefaults). So corporate can see every store and a user can be confined to assigned stores. But this is ONE tenant with store-scoped users. Nothing distinguishes a franchisor tenant from an independently owned franchisee tenant, or gives the franchisee ownership of its employees, banking or labour data, which is the claim. Adjacent, not a partial. Retrieved 2026-09-18. adversarially verified

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

multi-location-royalty-calculation

328th (APPS SLICE): NEW SURFACE. The MY PDQ app's own App Store screenshots show that the myPDQPOS enterprise 'Store Totals' report opens with a dedicated section headed 'Royalty Sales' carrying a single line 'Sales: $0.00', placed ABOVE and separately from the ordinary 'Sales Totals' block (Non Tax SubTotal / Taxable SubTotal / Total Tax / SubTotal / Grand Total) - i.e. PDQ computes and reports a distinct royalty-basis sales figure from POS sales, per store and for 'All Assigned Stores' (https://is1-ssl.mzstatic.com/image/thumb/Purple123/v4/6e/ab/8b/6eab8bec-5575-9b77-2726-262014a93108/pr_source.png/1000x0w.png). That royalty sales is a separate number from grand-total sales is itself evidence of a configurable basis net of something. PARTIAL, not yes: the screenshot shows the BASIS only - no royalty/ad-fund/marketing-fee AMOUNT, no defined schedule, and no visible configuration of gross-vs-net; and an app-store screenshot is grade C, below the A/B a differentiator yes needs. Retrieved 2026-09-18. https://apps.apple.com/us/app/my-pdq/id1218876302 · retrieved 2026-09-18 adversarially verified

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

multi-location-royalty-collection

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Multi-unit operation is real and its mechanics are unpublished. The 2019 dashboard proves cross-store rollup with a "Store Groups" picker above a "Stores" picker, and both sites market PDQ Enterprise Reporting to multi-unit operators; the catalog's About page says the product is "designed for independents, franchises and chains of all sizes". Against that, Yellow Dog's integration page states that in PDQ "normally each Property ... would be considered a separate instance", which is an instance-per-property topology rather than one tenant with many stores. Nothing published resolves that, and nothing describes central menu publishing, local override policy, price zones, scheduled publish, new-store templating, corporate-versus-franchisee roles, royalty calculation or collection, normalised item rollup, cross-location gift cards or loyalty, multi-jurisdiction tax, a config audit log or central labour policy. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 328th: 328th (APPS SLICE): NEW SURFACE, does not settle the cell. The myPDQPOS enterprise report does compute a royalty BASIS ('Royalty Sales / Sales:' as its own section of Store Totals, above the ordinary Sales Totals block), which is the input this claim's ACH sweep would draw on, but nothing in either PDQ app shows a fee amount, a franchisee statement, or a collection event; MY PDQ is read-only reporting and its whole report picker is two entries. Retrieved 2026-09-18. adversarially verified

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

multi-location-consolidated-reporting

PDQ Enterprise Reporting is positioned for multi-unit above-store reporting; the specific aggregations, ranking and variance flags are not documented. https://www.pdqpos.com/ · retrieved 2026-08-01

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

multi-location-normalized-item-rollup

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Multi-unit operation is real and its mechanics are unpublished. The 2019 dashboard proves cross-store rollup with a "Store Groups" picker above a "Stores" picker, and both sites market PDQ Enterprise Reporting to multi-unit operators; the catalog's About page says the product is "designed for independents, franchises and chains of all sizes". Against that, Yellow Dog's integration page states that in PDQ "normally each Property ... would be considered a separate instance", which is an instance-per-property topology rather than one tenant with many stores. Nothing published resolves that, and nothing describes central menu publishing, local override policy, price zones, scheduled publish, new-store templating, corporate-versus-franchisee roles, royalty calculation or collection, normalised item rollup, cross-location gift cards or loyalty, multi-jurisdiction tax, a config audit log or central labour policy. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: MERGE HOLD (proposed partial/C, held unknown): multi-store reporting and PLU reports are listed, but nothing addresses a shared corporate item id surviving local renames or prices, which is the claim. The agent flagged it as weakest. PROPOSAL AS WRITTEN: CLAIM: item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. VERDICT: partial. EVIDENCE: PDQ's Mobile Reporting page lists as separate report lines 'Menu Sales Report | MULTIPLE STORE REPORTING | COMPARE STORES | View Top Selling Items | Monitor Payouts From Each Location' (https://web.archive.org/web/20150731053525/http://pdqpos.com/mobile-reporting/); the Feature Overview's Cloud-Reporting Service column adds 'Master control' and 'Comprehensive reporting, with web-based access from any smart device or computer', and the report list includes 'PLU / Item reporting' and 'Top sales items' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Cross-store item reporting under a master tier therefore exists. SHORTFALL (named): nothing states that a corporate item ID survives a LOCAL RENAME or local price - the hard half of this claim - and no mapping or alias screen is described. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE, does not settle the cell. the MY PDQ Android app (package com.pdqpos.mypdqpos, v1.3.0, the enterprise-reporting companion listed at https://play.google.com/store/apps/details?id=com.pdqpos.mypdqpos; APK 22,026,521 bytes, sha256 ff00754cb51bb668..., fetched anonymously from the APKPure mirror because Play serves no APK). It is a Xamarin.Forms app, so its logic ships as .NET assemblies compressed with XALZ/LZ4. Unpacked, never executed: myPdqPos.dll decompressed to 516,608 bytes (sha256 fecfd249d00c113e...), with 6,690 UTF-16 and ASCII strings read out. In the enterprise data model each store record carries a 'MasterMenuId', so stores are bound to a master menu, and inventory lines carry 'ItemId'/'ItemCode'. That is the precondition for a shared corporate item ID. Nothing shows that the ID survives a local RENAME or a local PRICE, which is the claim. The app's only item-level views are store counts and void/promo lists; it has no cross-store item rollup at all. Retrieved 2026-09-18. adversarially verified

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

multi-location-cross-location-giftcard

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Multi-unit operation is real and its mechanics are unpublished. The 2019 dashboard proves cross-store rollup with a "Store Groups" picker above a "Stores" picker, and both sites market PDQ Enterprise Reporting to multi-unit operators; the catalog's About page says the product is "designed for independents, franchises and chains of all sizes". Against that, Yellow Dog's integration page states that in PDQ "normally each Property ... would be considered a separate instance", which is an instance-per-property topology rather than one tenant with many stores. Nothing published resolves that, and nothing describes central menu publishing, local override policy, price zones, scheduled publish, new-store templating, corporate-versus-franchisee roles, royalty calculation or collection, normalised item rollup, cross-location gift cards or loyalty, multi-jurisdiction tax, a config audit log or central labour policy. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd: NEW SURFACE, does not settle the cell. the MY PDQ Android app (package com.pdqpos.mypdqpos, v1.3.0, the enterprise-reporting companion listed at https://play.google.com/store/apps/details?id=com.pdqpos.mypdqpos; APK 22,026,521 bytes, sha256 ff00754cb51bb668..., fetched anonymously from the APKPure mirror because Play serves no APK). It is a Xamarin.Forms app, so its logic ships as .NET assemblies compressed with XALZ/LZ4. Unpacked, never executed: myPdqPos.dll decompressed to 516,608 bytes (sha256 fecfd249d00c113e...), with 6,690 UTF-16 and ASCII strings read out. The enterprise Store Totals model reports gift cards SOLD and gift cards TAKEN AS TENDER as separate per-store lines: 'amtGiftSold'/'qtyGiftSold' versus 'amtGiftCards'/'qtyGiftCards' (label 'giftCardsAmountLabel'). Those are the inputs an inter-store reconciliation would need. But no cross-store redemption, outstanding-liability balance or settlement between owners appears anywhere in the model or the app. Retrieved 2026-09-18. adversarially verified

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

multi-location-cross-location-loyalty

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Multi-unit operation is real and its mechanics are unpublished. The 2019 dashboard proves cross-store rollup with a "Store Groups" picker above a "Stores" picker, and both sites market PDQ Enterprise Reporting to multi-unit operators; the catalog's About page says the product is "designed for independents, franchises and chains of all sizes". Against that, Yellow Dog's integration page states that in PDQ "normally each Property ... would be considered a separate instance", which is an instance-per-property topology rather than one tenant with many stores. Nothing published resolves that, and nothing describes central menu publishing, local override policy, price zones, scheduled publish, new-store templating, corporate-versus-franchisee roles, royalty calculation or collection, normalised item rollup, cross-location gift cards or loyalty, multi-jurisdiction tax, a config audit log or central labour policy. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 331st: 331st (slice g): NEW SURFACE, a re-grep of the legacy storefront renders on disk (.cache/q312/pdq-pos/pages, guest sessions of 2026-09-16). The shared app ships a rewards panel (control RewardsAccountInfo, on Menu.aspx and CheckOut.aspx) with the same default text on 4 tenants: bluebellpizza, claudios-pizzeria, gzepps and mypizzavillage. The text reads 'Rewards Account Information ... Sign up today and you will be able to join any of our participating locations to receive special Promotional Offers and Discounts.' with a 'Sign Me Up' checkbox, chkRewardsSignUp. That checkbox has no autopostback, so a guest session renders nothing further. On mypizzavillage the tenant's own line adds 'Earn points for every dollar. Use points to pay for your order !' The panel also has a 'divPopupRewardSearch' popup, which is empty for a guest. This is PDQ's own wording that a rewards account can span 'participating locations'. It does not say whether one profile, points balance and order history are shared across the brand or kept per location. 'Join any of our participating locations' can be read either way, so it is not a partial. Retrieved 2026-09-18. adversarially verified

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

multi-location-multi-brand

Casino deployments span 'all profit centers', which is revenue centers rather than distinct brands with separate receipts and branding. || 326th: MERGE HOLD (proposed partial/C, held unknown): casino outlets each running PDQ are separate profit centres, not two brands on one terminal and drawer. The agent flagged it. PROPOSAL AS WRITTEN: CLAIM: one location/terminal operates two or more distinct brands with separate menus, receipts/branding and separately reportable revenue on the same hardware and drawer. VERDICT: partial. NEW SURFACE - the live case-study and press-release routes on pdqpos.com. Jake's 58: 'SSI's POS offers an intuitive interface that enables SEAMLESS MENU UPDATES ACROSS BISTRO58 AND OTHER F&B OUTLETS AT JAKE'S 58' (https://pdqpos.com/ProjectDetail?pk=j58ch). Live! Casino & Hotel Louisiana: 'has installed PDQ POS ACROSS ALL PROFIT CENTERS and online... Live! Casino & Hotel Louisiana contains 10 food and beverage outlets' (https://pdqpos.com/newsarticles?rid=PR_000_live_louisiana). The Feature Overview supplies the reporting primitive, 'Sales by destinations' and 'Sales volume by item type' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Multiple separately-branded F&B outlets with distinct menus on one PDQ installation is therefore established. SHORTFALLS (named): these are distinct OUTLETS at one property, not two brands on ONE TERMINAL AND DRAWER, and nothing describes per-brand receipt branding or virtual brands. Retrieved 2026-09-18. adversarially verified

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

multi-location-multi-tax-jurisdiction

CLAIM: per-location tax configuration with multiple simultaneous rates, jurisdiction-specific rules (prepared-food vs grocery, inclusive vs exclusive) and per-location exemptions. VERDICT: partial. EVIDENCE: the 2016 Feature Overview lists under Point-of-Sale Capabilities 'MULTIPLE TAX INCLUSIVE AND TAX FEATURES AVAILABLE', and under Reports 'Tax reporting'; the Back Office column carries 'Store level control' beneath 'Master control' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Multiple simultaneous tax treatments including tax-inclusive pricing are therefore shipped, and a per-store configuration tier exists. SHORTFALLS (named): no jurisdiction-specific rule category (prepared-food vs grocery) and no per-location tax exemption is named; 'Store level control' is generic and is not stated to cover tax. Retrieved 2026-09-18. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-18 adversarially verified

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

multi-location-config-audit-log

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Multi-unit operation is real and its mechanics are unpublished. The 2019 dashboard proves cross-store rollup with a "Store Groups" picker above a "Stores" picker, and both sites market PDQ Enterprise Reporting to multi-unit operators; the catalog's About page says the product is "designed for independents, franchises and chains of all sizes". Against that, Yellow Dog's integration page states that in PDQ "normally each Property ... would be considered a separate instance", which is an instance-per-property topology rather than one tenant with many stores. Nothing published resolves that, and nothing describes central menu publishing, local override policy, price zones, scheduled publish, new-store templating, corporate-versus-franchisee roles, royalty calculation or collection, normalised item rollup, cross-location gift cards or loyalty, multi-jurisdiction tax, a config audit log or central labour policy. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

multi-location-enterprise-api

No public API of any kind is documented. || 326th: NEW SURFACE, does not settle the cell. PDQ asserts an API exists, in its own 2024-2025 corporate boilerplate carried identically by four live press releases: 'Products & services include a natively integrated enterprise reporting mobile app, natively integrated "In-Place Dining" mobile app, natively integrated online ordering, ... comprehensive menu management, VALUE-ADDED INTEGRATIONS VIA RESTFUL APIS, expert project management...' (https://pdqpos.com/newsarticles?rid=PR_000_live_louisiana, and the same paragraph at ?rid=PR_82724_sycuan, ?rid=PR_924_bonanza, ?rid=PR_000_prairie_flower); the 2020 DoorDash release says the same ('RESTful APIs and more'). The claim's operative verb is PUBLISHES A DOCUMENTED API, and nothing is published: certificate-transparency listing of pdqpos.com returns 20 names, of which only help.pdqpos.com (a BeyondTrust remote-support session portal) and pci.pdqpos.com (redirects to /login) resolve and answer; support.pdqpos.com and ssi-jira.pdqpos.com are NXDOMAIN; www.pdqpos.com serves no robots.txt and no sitemap.xml; and the live site's only non-marketing routes are /newsarticles, /ProjectDetail, /termsofuse, /privacypolicy, /smsprivacypolicy. An asserted-but-unpublished API satisfies no conjunct, so this is held unknown rather than made a partial. Retrieved 2026-09-18. || 327th: 327th (APPS/HOSTS SLICE): NEW SURFACE, does not settle the cell. PDQ does operate a named enterprise web service. The Wayback copy of the vendor-served DISCO document at pushapi-3.mypdqpos.com is verbatim: '<contractRef ref="http://pushapi-3.mypdqpos.com/PDQEnterpriseAPI.asmx?wsdl" docRef="http://pushapi-3.mypdqpos.com/PDQEnterpriseAPI.asmx" />' with '<soap address="http://pushapi-3.mypdqpos.com/PDQEnterpriseAPI.asmx" xmlns:q1="http://www.mypdqpos.com/services/PDQEnterpriseAPI" binding="q1:PDQEnterpriseAPISoap" />' and a second binding 'PDQEnterpriseAPISoap12'. So the integration surface is an ASMX SOAP 1.1/1.2 service under the myPDQPOS enterprise platform, named 'PDQEnterpriseAPI'. NOT SETTLED because the WSDL itself is unobtainable: pushapi-3, pushapi-1/2/4 and pushapi.mypdqpos.com all fail to connect on 443 AND on 80 (curl exit 28, ~21 s, from this network today), and Wayback holds the ?disco capture but no ?wsdl capture. Without the WSDL there is no operation list, so none of the claim's conjuncts (documented; transaction-level data across ALL locations in one call; no per-location credentials) is shown. A discovery stub is not documentation. Retrieved 2026-09-18. || 331st: 331st: NEW SURFACE, does not settle the cell. Ten press-release PDFs in the ssipos.com WordPress media library (216 items, paged in full via /wp-json/wp/v2/media) were never opened by name before. Their 2021-2022 boilerplate goes further than the 'via RESTful APIs' wording the 326th recorded: 'RESTful APIs WITH FULL DOCUMENTATION' (SSI-Parx-Press-Release.pdf, 13 Jul 2022; SSI-Cordish-Gaming-Press-Release.pdf, 1 Apr 2022; PR_Wildwood.pdf, 15 Jul 2021). The 2023 releases (SSI-_Cordish-Gaming-goes-live-Press-Release.pdf, SSI-Press-Release-Osage-Casino-1-1.pdf) drop the API sentence altogether. So the vendor says documentation exists, but none is published on any host we hold (ssipos.com has no custom WP types: /wp-json/wp/v2/types lists only core types). The pricing workbook sells access as 'API Reporting Interface - Annual' at 115 dollars per device per year. Nothing shows a cross-location single call or credential model. The claim's verb, PUBLISHES a documented API, is still unmet. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE, does not settle the cell. A SECOND enterprise API, a REST one, beside the SOAP 'PDQEnterpriseAPI' recorded by the 327th. the MY PDQ Android app (package com.pdqpos.mypdqpos, v1.3.0, the enterprise-reporting companion listed at https://play.google.com/store/apps/details?id=com.pdqpos.mypdqpos; APK 22,026,521 bytes, sha256 ff00754cb51bb668..., fetched anonymously from the APKPure mirror because Play serves no APK). It is a Xamarin.Forms app, so its logic ships as .NET assemblies compressed with XALZ/LZ4. Unpacked, never executed: myPdqPos.dll decompressed to 516,608 bytes (sha256 fecfd249d00c113e...), with 6,690 UTF-16 and ASCII strings read out. The app calls an ASP.NET Web API at 'https://wapi-data.mypdqpos.com' + 'api/Mobile' (older builds pointed at 'http://pdqenterprisewapi-s1.azurewebsites.net' and 'https://wapi-1-beta.mypdqpos.com'). It authenticates by OAuth2 password grant ('grant_type=password&username={0}&password={1}&passKey={2}&client_id={3}', then 'Bearer' plus a refresh_token). Its whole method set, from the DataWebAPI async state machines, is 14 calls: ValidateLogin, StoreSales, StoreSalesByShift, ReportQuickX, VoidPromo, UserDetails, UserAccessDefaults, PasswordResetRequest, UserAccessStores, UserAccessUsers, StoreCounts, StoreCountItems, UserSettingsUpdate and ReportHourlySales. The request and response models (BaseRequestModel, DashboardRequestModel) carry 'FranchiseID' and a 'StoreIds' list, so the data model lets one bearer token read several stores. That is the shape the claim describes, but for store TOTALS, not transaction-level data. NOT PUBLISHED, which is the claim's verb. GET probes today (GET only, no token used, nothing sent to any endpoint): wapi-data.mypdqpos.com '/' 403 (58 bytes); '/Help', '/help', '/swagger', '/swagger/ui/index' and '/swagger/docs/v1' all 404 at 103 bytes, identical to the '/zzz-nope' nonsense control; '/api/Mobile' answers the framework's own JSON 404 ('No action was found on the controller 'Mobile''). pdqenterprisewapi-s1.azurewebsites.net behaves the same. wapi-1-beta.mypdqpos.com and wapi-data.pdqbeta.com do not connect on 443 or 80. There is no Web API Help page and no Swagger. Retrieved 2026-09-18. adversarially verified

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

multi-location-central-labor-policy

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Multi-unit operation is real and its mechanics are unpublished. The 2019 dashboard proves cross-store rollup with a "Store Groups" picker above a "Stores" picker, and both sites market PDQ Enterprise Reporting to multi-unit operators; the catalog's About page says the product is "designed for independents, franchises and chains of all sizes". Against that, Yellow Dog's integration page states that in PDQ "normally each Property ... would be considered a separate instance", which is an instance-per-property topology rather than one tenant with many stores. Nothing published resolves that, and nothing describes central menu publishing, local override policy, price zones, scheduled publish, new-store templating, corporate-versus-franchisee roles, royalty calculation or collection, normalised item rollup, cross-location gift cards or loyalty, multi-jurisdiction tax, a config audit log or central labour policy. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

hardware-commodity-devices

CORRECTED: the previous note said "nothing indicates the software runs on operator-purchased iPads or generic Android tablets", which was true of www.pdqpos.com and the 2025 catalog but false of the vendor's other site. ssipos.com states it plainly under ALL-ENCOMPASSING HARDWARE: "We're also hardware agnostic, so our software can run on your existing hardware!" Shortfall, and it is most of the claim: that single sentence is the entire evidence. No supported-device list, no client OS or minimum specification, and no named third-party terminal appears anywhere -- while the 2025 Product Catalog markets roughly 25 first-party SKUs and the same ssipos.com paragraph sells a first-party all-in-one, tablet and kiosk line. "Your existing hardware" most naturally reads as the operator's incumbent terminals at migration, which is not the same as buying commodity iPads or Android tablets from a third party today. https://ssipos.com/ · retrieved 2026-08-30

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

hardware-os-platforms

327th: NEW SURFACE, and it moves the cell off unknown. CLAIM: vendor documentation names the specific client operating systems supported and states minimum OS versions and device specs. VERDICT: partial, grade D. The PCI Security Standards Council's List of Validated Payment Applications is a registry nobody had queried for this vendor (it is JS-driven; the rows come from a POST to /includes/ajax/solution_listings.php with program=PADSS and search='Signature Systems, Inc.'). It holds TWO entries under Signature Systems, Inc., both for the product 'PDQPOS', and both carry a 'Tested Platforms/Operating Systems' field with a service-pack level. EVIDENCE, verbatim from the listing: PDQPOS Version # 3.5.x, Reference # 14-08.00296.002, App Type 'POS Face-to-Face/POI', Target Market 'Quick service restaurants (QSR), fine dining restaurants and bars', 'Tested Platforms/Operating Systems: Windows POSReady 2009', 'Service Pack/Build/Version: Windows Embedded for Point of Service (WEPOS) SP3, Windows POSReady 2009 SP3', Other Dependencies 'Datacap DSIClient 2.5 / Microsoft .NET Framework 3.5 / Microsoft SQL Server 2008 / Kaspersky Endpoint Security 10', validated to PA-DSS v3.0 by Sikich LLP, expiry 28 Oct 2019. The older entry: PDQPOS Version # 2.0.0.0, Reference # 11-08.00296.001, 'Tested Platforms/Operating Systems: Windows XP, Windows Server 2003, Windows Server 2008', 'Service Pack/Build/Version: Windows XP SP3, WEPOS SP3, POS Ready 2009 SP3, Windows Server 2003 SP2, Windows Server 2008 SP2', PA-DSS v1.2, expiry 28 Oct 2013. Both are now flagged 'Acceptable only for Pre-Existing Deployments' because PA-DSS was retired in October 2022. Independently corroborated in SSI's own 2022 whitepaper, recovered in full this session from ssipos.com: 'The best architecture to support this seismic shift is one that is inherently flexible, scalable, reliable, secure, and dependable (think: Microsoft Windows OS and .NET framework)' (https://ssipos.com/wp-content/uploads/2022/06/SSI-3-Vital-Things-to-Consider.-article.pdf). WHY PARTIAL AND NOT YES: the client OS family is named (Windows) with an explicit minimum service-pack level, which is two of the claim's three conjuncts, but the source is a third-party registry entry whose validation expired in 2019, not current vendor documentation; no device specs are stated; and nothing anywhere names an OS for the 8-inch/10-inch tablets, the three-in-one unit or the four kiosk bodies in the live 2025 catalogue. Grade D because a registry is a third-party source. Weakest point: currency. ALSO RECORDED HERE because it qualifies the 2026-08-30 category note that enumerates PDQ's 'FULL public surface': ssipos.com's own WordPress manifest was fetched to 100% this session (wp-json/wp/v2/types = 12 types; pages returns exactly 8, posts 5 theme-demo items, blocks 0, media 400) so the Yoast sitemap was NOT a subset and that half of the enumeration holds; but www.pdqpos.com's retired /blogs/ index (https://web.archive.org/web/20230605172829/https://www.pdqpos.com/blogs/) names a TWELVE-item closed library of vendor whitepapers and 'slicks', four of which are held by nothing: 'Is Best of Breed the Best Approach?', 'PDQ vs. THE Competition (Infographic)', 'Online Ordering: 5 Ways' and 'Cloud vs. Traditional POS'. They were served from j8e434.p3cdn1.secureserver.net, which is now NXDOMAIN; the paths 404 on both pdqpos.com roots and the Wayback CDX for that CDN host and for pdqpos.com/wp-content/uploads/2023* is empty. That is a shaped corpus hole, not an absence: a vendor-authored competitive feature comparison existed and cannot be read. Retrieved 2026-09-18. https://listings.pcisecuritystandards.org/assessors_and_solutions/payment_applications?agree=true&reference=Signature+Systems%2C+Inc. · retrieved 2026-09-18 adversarially verified

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

hardware-handheld-purpose-built

8-inch and 10-inch purpose-built tablets with gorilla glass, IP65 rating, weather-resistant build, WiFi and Bluetooth. IP rating published; no drop rating; integrated card reader not confirmed on the tablets. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-01

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

hardware-handheld-battery-swap

Multi-tablet docking stations (5 tablets) and printer dock chargers are catalogued, but no battery life figure or swap capability is published. || 331st: 331st: NEW SURFACES checked, nothing on batteries, and one HOMONYM recorded so it is not mis-read later. The vendor pricing workbook has a row 'Tablet Extended 3yr Hot Swap' at 600 per tablet (quantity =SUM(B48:B49), i.e. one per 7-inch/10-inch tablet). That is a unit-replacement warranty; the catalogue's REPAIRS page uses the same phrase, 'Hot-swap available for most products'. It is NOT a hot-swappable battery. The 2025 catalogue's tablet page, rendered and read as an image (8-inch: 'gorilla glass', 'IP65', '4G or 5G Models Available'; 10-inch Touch Dynamic in a card-reader base), gives no battery life figure and shows no battery door. Its page 10 enumerates only charging accessories ('MULTI-TABLET DOCK ... Charge up to five tablets', 'PRINTER DOCK CHARGER'). Retrieved 2026-09-18. || 332nd: 332nd: attempted model identification, NEGATIVE, recorded so it is not retried. The catalogue's 10-inch tablet sits in a TOUCH DYNAMIC-branded base, so Touch Dynamic's own catalogue (touchdynamic.com product JSON and pages, 41 products) was checked for the 8-inch unit. Its only 8-inch rugged tablet, the Quest VIII Ultra, matches 'Gorilla Glass' and 'IP65' and its spec reads 'BATTERY & POWER Dual Battery Standard, Hot Swappable' (https://www.touchdynamic.com/products/quest-viii-ultra) - but it is NOT the device PDQ pictures: PDQ's 8-inch has side buttons, no front home button and a different corner-bumper profile (both images read at full size), and the Quest VIII Ultra spec lists no 4G/5G while PDQ says '4G or 5G Models Available'. Touch Dynamic's docked tablets are the 10.1-inch Quest Rugged (LTE, no battery spec) and the 11.6-inch Fusion Hybrid ('Built-in Battery (Tablet)', 3.8 V 7000mAh, no swap). PDQ names no model, so no manufacturer spec can be attributed to its handheld. Held unknown. Retrieved 2026-09-18. || 333rd: NEW SURFACE READ (333rd), nothing on batteries. PDQ's own "Quest Tablet POS" video (https://www.youtube.com/watch?v=CRtZ5kwzjcQ, 2017-05-16, 76 s, downloaded at 1080p and read as a 5-second contact sheet) shows a Touch Dynamic Quest tablet running PDQ POS in the hand and then docked in a TOUCH-branded base beside a separate pinpad; the tablet runs Windows (taskbar visible at 55 s). No frame shows a battery door, a battery swap, a charge indicator or a stated battery life, and the video carries no on-screen text about power. It is also the 2017 generation, not the 2025 catalogue's 8-inch unit. Held unknown. Retrieved 2026-09-18. adversarially verified

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

hardware-handheld-lte

The catalog is now retrievable and extracts cleanly, and the '4G or 5G Models Available' string is real: it appears twice, once under the 8-INCH TABLET (also 'gorilla glass touch screen, IP65 rating, wifi connectivity, bluetooth connectivity') and once under the 10-INCH TABLET. So cellular-capable handhelds exist as ordered variants. The shortfall is what the claim actually asks for: nothing states the cellular radio acts as a fallback when store Wi-Fi drops, no failover behaviour, carrier, or data plan is described, and it is a purchase-time model choice rather than a documented redundancy feature. Partial, with the shortfall named. The former citation, /pdq-pos-hardware-catalog/, now 301s to the homepage and has been withdrawn. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

hardware-offline-mode

Offline operation is never mentioned in the catalog or on the site, and no degradation matrix is published. || 325th: NEW SURFACE, does not settle the cell. The claim's second half requires the VENDOR to document which functions degrade offline. PDQ's 2022 Why PDQ hardware list opens with 'Server/Hybrid solutions' (https://web.archive.org/web/20220627153113/https://www.pdqpos.com/why-pdq/) and the 2016 Feature Overview enumerates the 'Cloud-Reporting Service' as a column SEPARATE from 'Back Office (POS)', flagging inventory reporting '(w/cloud service)' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf) - i.e. the transaction engine is on-premise and only reporting is cloud. That is architectural inference, not a published offline scope: no PDQ document (live site, 2025 catalogue, 2016 feature sheet, 2004 module sheet) states what does and does not work with the WAN down. Held unknown rather than partial because the documentation conjunct is the one being tested. Retrieved 2026-09-17. || 331st: 331st: NEW SURFACES, adjacent only. (1) The vendor pricing workbook sells an on-premise server: 'SSI Virtual Server Appliance', 2 units at 12,500. That supports the 'Server/Hybrid' architecture already noted, but it states no offline behaviour. (2) PR_Wildwood.pdf (https://ssipos.com/wp-content/uploads/2021/07/PR_Wildwood.pdf, 15 Jul 2021) quotes the customer: 'by adding a SIM card with cellular service, we can ensure uninterrupted processing whenever our Wi-Fi connectivity falters'. That is a second ONLINE path, the same shape the 326th held for dial-backup, not an offline mode. Neither document lists which functions degrade offline. Retrieved 2026-09-18. adversarially verified

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

hardware-kds

Same unverifiable-PDF problem, and worse: I found no independent corroboration of a first-party PDQ KDS/bump-bar SKU. Trade coverage of PDQ hardware enumerates 'all-in-one, tablet and self-serve kiosk POS... customer-facing video display units, integrated digital menu boards and camera systems' — VDU there means customer-facing display, not kitchen display. A first-party KDS is plausible but unconfirmed outside a document I could not read. https://www.fbtechreview.com/pdq-signature-systems · retrieved 2026-08-01 · not refetchable · site policy · graded B when read adversarially verified

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

hardware-kiosk

Re-evidenced on 2026-08-09 after the previously cited /pdq-pos-hardware-catalog/ page was deleted. The 2025 catalog now extracts and devotes four consecutive pages, each headed 'KIOSKS', to named models: FREESTANDING KIOSK ('Take payments in any environment... anti-theft screws'), OUTDOOR KIOSK ('Self-ordering from the car or on foot... built to withstand rain, heat and freezing temperatures'), CASH KIOSK ('Receive and disburse payments via cash... operate completely unattended') and DESKTOP KIOSK ('the same great user experience of a freestanding kiosk in a more compact model'). That covers both freestanding and countertop form factors with integrated payment, including cash. A separate catalog entry describes a THREE-IN-ONE DISPLAY serving as 'a POS, customer display and self-order kiosk'. The Live! Casino Louisiana release (still live) independently names 'self-serve kiosks with multiple tenders'. ADA/WCAG conformance remains unpublished - no VPAT or ACR anywhere - and no kiosk runs a documented shared menu engine statement, so that leg is inferred from it being the same POS product. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

hardware-drive-thru

Outdoor kiosk supports 'self-ordering from the car'; integrated digital menu boards and a DigiVue signage PC driving up to four displays at 300ft. No speaker/headset integration or speed-of-service timers documented. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-01

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

hardware-printer-compatibility

Epson label printer named; thermal receipt printer 'can be connected via serial, USB or ethernet to integrate with any system'; impact printer and mobile hip printer offered. Multi-manufacturer ESC/POS support is implied, not stated, and no compatibility list is published. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-01

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

hardware-peripherals

Cash drawer and mini cash drawer, barcode scanner with charge base, pole display, video pole display, 8-inch touch rear display, pin pad mount, fingerprint reader. No scales for by-weight items and no published compatibility list. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-01

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

hardware-p2pe-terminal

331st: NEW EVIDENCE from an IMAGE, read at full resolution. It settles the PTS-device conjunct and leaves the other two open. CLAIM: card entry happens on a PCI-listed PTS device using validated P2PE, so the POS app and tablet stay out of PCI scope, and the vendor states the merchant's SAQ type. VERDICT: partial. EVIDENCE: page 7 ('PERIPHERALS') of the live 2025 Product Catalog (https://pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf, 200, 11,853,518 bytes, 20 pages) catalogues one card terminal under the heading 'CARD SWIPE PINPAD'. The text calls it only 'among the most secure in the industry', which is the phrase the existing note rests on. But the PRODUCT PHOTO above that text, rendered from the PDF at 110 dpi and read as an image, shows the device face printed 'Lane/3000' and 'ingenico', with the contactless (NFC) symbol at the top and an EMV/PIN keypad. The PCI SSC PIN Transaction Security listing (listings.pcisecuritystandards.org/assessors_and_solutions/pin_transaction_devices, public listing search for 'Lane') lists Ingenico 'Lane/3000' as an approved PED twice: Approval Number 4-30414, version 6.x, expiring 30 Apr 2032, and 4-30310, version 5.x (Lane/3000 and Desk/1500), expiring 30 Apr 2027, with SRED and On-Guard SDE/FPE firmware among the listed applications. So the terminal PDQ sells for card entry is a current PCI-listed PTS device. This also corrects the existing note's counter-signal that 'NFC ... is never named anywhere': the catalogued pinpad carries the contactless mark. SHORTFALLS, both named: (1) nothing states that a VALIDATED P2PE solution runs on it. The 327th registry query found no P2PE listing naming Signature Systems, and PDQ's own PA-DSS entry names 'Datacap DSIClient 2.5' semi-integration, which is not a P2PE listing. The On-Guard firmware on the PTS listing is Ingenico's encryption capability, not a validated P2PE solution. (2) No merchant SAQ type is stated anywhere: SSI-Security.pdf (https://ssipos.com/wp-content/uploads/2022/05/SSI-Security.pdf, 14 pages) offers only 'PCI Self-Awareness Questionnaire (SAQ) Simplification' and 'PCI SAQ Assistance', and names no SAQ type. The model is identified from a catalogue photograph (grade C, vendor sales document), not from a spec sheet. Retrieved 2026-09-18. https://pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-09-18 adversarially verified

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

hardware-tap-to-phone

328th (APPS SLICE): SAME BOUND AS payments-softpos-tap-to-pay, stated for the hardware axis. Contactless acceptance on a commodity phone or tablet requires a vendor-published store app carrying the Tap to Pay entitlement. The publisher census run today - Apple lookup on developer id 1218876301 (2 apps: MY PDQ, PDQ DT) and the Google Play developer page for 'Signature Systems, Inc' (2 packages: com.pdqpos.pdqdelivery, com.pdqpos.mypdqpos), with iTunes and Play searches finding no other app by this publisher - is the complete set, and neither app takes a payment. PDQ's own reading of the tablet form factor is the opposite of reader-less: its marketing hardware line is 'MOBILE EMV PAYMENT' on the tablet POS, i.e. an attached EMV reader. Grade C (store listings). Retrieved 2026-09-18. https://play.google.com/store/apps/developer?id=Signature+Systems,+Inc · retrieved 2026-09-18 adversarially verified

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

hardware-pricing-transparency

The 2025 Product Catalog enumerates roughly 25 hardware SKUs with descriptive copy and zero prices; no price appears on any SKU or anywhere on the site. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-01

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

hardware-ownership-vs-lease

DOWNGRADED from yes after verification. The claim has two limbs and explicitly requires the second: hardware can be purchased outright AS AN ALTERNATIVE to a lease, and the vendor states which. Limb 1 is well evidenced - hardware appears as outright unit-priced line items with literal prices. Limb 2 FAILS: the workbook contains no ownership, purchase, lease or rental language at all (all three tokens occur zero times), so the vendor states nothing about the model. Reading published purchase prices as an implicit statement of the model is an inference, and the claim asks for a statement. PROVENANCE LIMIT: this is one workbook, dated serial 44319 = 2021-05-03, published on https://ssipos.com/sky-river/ as a landing page addressed 'for WILTON RANCHERIA SKY RIVER', carrying a buyer-specific 'Boyd Discount' line which applies only to the base-licence row. It is the vendor's only published pricing artefact; treat it as evidence about PDQ's 2021 commercial model, not a current restaurant-segment price list. https://ssipos.com/wp-content/uploads/2021/04/Sky-River-Casino-Quote-05-3-21.xlsx · retrieved 2026-09-12 adversarially verified

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

hardware-usable-after-churn

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. The 2025 Product Catalog is the strongest artefact this record has for hardware -- it enumerates roughly 25 SKUs across tablets, counter stations, displays, peripherals, VDUs/KDS, printers, QSR add-ons and four kiosk models -- and the cells it can settle have been settled elsewhere in this record. It enumerates PRODUCTS, never SPECIFICATIONS or COMMERCIAL TERMS: no model number, no OS, no radio, no price, no lease-versus-purchase statement, no post-cancellation usage term, and no statement about running the software on a member of staff's own phone. ssipos.com adds one sentence in the other direction -- "We're also hardware agnostic, so our software can run on your existing hardware!" -- which is recorded on `hardware-commodity-devices` and is too thin to carry a device-level or contractual claim. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: NEW SURFACE, does not settle the cell, but it is the closest evidence that exists and is worth recording. PDQ's business model is converting OTHER vendors' installed hardware to run PDQ POS, which it states twice in live press releases: 'SSI worked with Sycuan Casino Resort to RE-UTILIZE NEARLY ALL EXISTING HARDWARE on location to run PDQ POS, including more than 160 point-of-sale stations and tablets... The majority of the SIX DIFFERENT GENERATIONS OF WORKSTATIONS AND TABLETS that had been deployed over the previous eight years were converted to run the PDQ POS platform' (https://pdqpos.com/newsarticles?rid=PR_82724_sycuan); 'Bonanza Casino will be taking advantage of SSI'S ABILITY TO CONVERT ANY PRE-EXISTING POS HARDWARE' (https://pdqpos.com/newsarticles?rid=PR_924_bonanza). That establishes PDQ's software is not hardware-locked - the reverse direction of the claim. The claim asks whether HARDWARE BOUGHT FROM PDQ stays usable after cancellation, and no PDQ document addresses it: the 2025 Product Catalog covers the device range and a 'REPAIRS' page but says nothing about ownership or post-termination use (https://pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf), and the governing Terms of Sale is unpublished. Held unknown. Retrieved 2026-09-18. || 331st: 331st: NEW SURFACE, same direction as the Sycuan evidence, does not settle the cell. SSI's 8 May 2023 Cordish go-live release positions PDQ against hardware lock-in in so many words: 'SSI was also willing and able to run its multi-award-winning software on Cordish's existing hardware, which resulted in a significant cost-savings vs. other providers that AUTOMATICALLY REQUIRE A HARDWARE LOCK-IN' (https://ssipos.com/wp-content/uploads/2023/05/SSI-_Cordish-Gaming-goes-live-Press-Release.pdf). The 2025 catalogue's own terminals are third-party commodity devices: a Touch Dynamic-branded 10-inch tablet base (page 4 photo) and an Ingenico Lane/3000 pinpad (page 7 photo). Both statements concern OTHER vendors' hardware running PDQ, or generic sourcing. Neither states that hardware bought from PDQ stays usable with other software after cancellation, which is the claim. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE located, UNREADABLE by policy. PDQ published a podcast titled exactly 'No Hardware Lock-In Podcast', listed on its own Podcasts page (ssipos.com WordPress page 29402, linking https://soundcloud.com/user-39287521/no-hardware-lock-in-podcast). It is audio on soundcloud.com, whose robots.txt NAMES ClaudeBot/anthropic-ai and disallows '/' for them apart from platform pages, so it was not fetched by any means (no UA swap, no mirror); the Podcasts page carries no text abstract. On its title it belongs with the Cordish release's anti-lock-in positioning already noted (PDQ running on OTHER vendors' hardware), not with the claim's direction (PDQ-sold hardware staying usable after cancellation). Held unknown. Retrieved 2026-09-18. adversarially verified

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

hardware-rma-sla

The catalog's REPAIRS page is four marketing bullets in full: 'Hardware can be repaired by PDQ technicians / Turn-around times in days, not weeks / Hot-swap available for most products / Some repairs can be performed remotely'. The homepage adds that PDQ POS is 'backed by an industry-leading warranty' with no term stated. So there is a posture and a hot-swap offer but no warranty length, no advance-exchange guarantee and no numeric turnaround; PDQ publishes no terms document covering hardware service, and the terms-of-use page does not address it. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

hardware-byod

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. The 2025 Product Catalog is the strongest artefact this record has for hardware -- it enumerates roughly 25 SKUs across tablets, counter stations, displays, peripherals, VDUs/KDS, printers, QSR add-ons and four kiosk models -- and the cells it can settle have been settled elsewhere in this record. It enumerates PRODUCTS, never SPECIFICATIONS or COMMERCIAL TERMS: no model number, no OS, no radio, no price, no lease-versus-purchase statement, no post-cancellation usage term, and no statement about running the software on a member of staff's own phone. ssipos.com adds one sentence in the other direction -- "We're also hardware agnostic, so our software can run on your existing hardware!" -- which is recorded on `hardware-commodity-devices` and is too thin to carry a device-level or contractual claim. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 327th: 327th (APPS/HOSTS SLICE): NEW SURFACE, does not settle the cell. PDQ publishes two staff-facing mobile apps to the consumer app stores, i.e. onto staff-owned devices: 'PDQ DT' (com.pdqpos.pdqdelivery, Signature Systems, Inc., iOS 2.0 build 74 updated 2026-05-06, and live on Google Play with 100+ downloads) and 'MY PDQ' (com.pdqpos.pdqposenterprise, iOS 1.3.0, 2022-05-05). The DT listing is explicit that it runs on the driver's own handset: 'The app allows the user to navigate, call or to use the phone while still updating the driver location to the store via PDQPOS through background services' and 'Continued use of GPS running in the background can dramatically decrease battery life.' NOT SCORED: the claim is about the ORDERING or PAYMENT app on a personal phone with a documented permission and security model - DT is a delivery toolkit, MY PDQ is read-only reporting, neither takes an order or a payment, and no permission or security model is published for either. Shortfalling every conjunct is not a partial. Retrieved 2026-09-18. || 328th: 328th (APPS SLICE): NEW EVIDENCE on the permission-and-security-model conjunct, still not enough to score. PDQ DT's Google Play Data safety declaration is the vendor's own published model for the staff app on a personal handset and it is minimal but explicit: 'No data shared with third parties', 'This app may collect these data types: Location', 'Data is encrypted in transit', 'You can request that data be deleted'. Its sign-in model is also now visible from the vendor's App Store screenshots: the driver pairs the personal phone to the store by 'Scan QR code from timeclock screen' with a 'Manual' fallback reading 'Enter code from timeclock screen' - a store-issued, timeclock-bound pairing code rather than a shared password. MY PDQ's Play Data safety by contrast declares 'No data collected'. Still unknown because the claim's SUBJECT is the ordering or payment app on a personal phone, and PDQ publishes neither: its two store apps are a driver toolkit and a read-only reporting client. Retrieved 2026-09-18. adversarially verified

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

hardware-remote-device-management

Only signal is 'some repairs can be performed remotely'; no device-management console is documented. || 326th: NEW SURFACE, does not settle the cell. The 2025 Product Catalog's 'REPAIRS' page is a four-line closed list: 'Hardware can be repaired by PDQ technicians / Turn-around times in days, not weeks / Hot-swap available for most products / SOME REPAIRS CAN BE PERFORMED REMOTELY' (https://pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf). The remote-access mechanism is a support tool, not an operator console: help.pdqpos.com is a BeyondTrust Remote Support session-key portal titled 'Signature Systems Support Portal' (4,788 bytes, robots meta 'noindex, nofollow'), i.e. a technician joins a session the store initiates. None of the claim's conjuncts appears anywhere: no console listing terminals/printers/KDS as online-offline, no remote reboot, no software-version visibility, no staged rollout. Held unknown. Retrieved 2026-09-18. || 328th: 328th (WEB/DOCUMENT SLICE): NEW SURFACE, identified, does not settle the cell. help.pdqpos.com is live (200, 4,788 bytes) and is titled 'Signature Systems Support Portal', but it is a hosted BEYONDTRUST REMOTE SUPPORT customer portal, not a device console: its only interactive element is a session-key box (form action '/check_access_key', scripts '/api/start_session.js', '/content/access_key_input.js', '/content/portal.js', link to beyondtrust.com, 'help?show_help=help_session_keys'). Probed for a public knowledge base and there is none -- /kb, /kb/1, /kb/search, /portal, /news, /rss, /sitemap.xml, /Main/frmKnowledgeBase.aspx all return an 18-byte 404 identical to the /zzz-nope nonsense control, and /robots.txt is 108 bytes; the page itself carries meta robots 'noindex, nofollow'. So PDQ's technicians get attended remote access to a terminal, which is not the claim's fleet console with per-device online/offline state, remote reboot, software-version visibility or staged rollout. Also probed and NXDOMAIN (no such host, so no hidden doc site): support.pdqpos.com, kb.pdqpos.com, docs.pdqpos.com, training.pdqpos.com, university.pdqpos.com, learn.pdqpos.com; and 404 on www.pdqpos.com/support/, /dealers/, /resources/, /sitemap_index.xml. support.pdqpos.com existed historically but Wayback holds only its robots.txt. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE, adjacent only. Signature Systems' 2018 capabilities statement 'Scope of Products and Services' (https://web.archive.org/web/20190920203102/https://www.pdqtek.com/wp-content/uploads/2018/01/About-PDQ-Signature-Systems.pdf) sells MANAGED IT alongside the POS: 'We will monitor, maintain, and support every aspect of your technology infrastructure', 'Receive peace of mind knowing that your network is being monitored 24/7/365', with PDQ Tek listing 'Business Continuity', 'Onsite Support', 'Virtual CIO' and PDQ Security 'Managed Endpoint'. That is vendor staff monitoring the network as a service (the same shape as the BeyondTrust technician portal), not an operator-facing console showing each terminal, printer and KDS online/offline with remote reboot, software-version visibility or staged rollout; none of those four conjuncts appears. Held unknown. Retrieved 2026-09-18. || 333rd: NEW SURFACE (333rd, certspotter on ssipos.com named osage.ssipos.com, sycuan.ssipos.com, sycuantest.ssipos.com, which no prior pass had probed), adjacent only. osage.ssipos.com and sycuan.ssipos.com are one-line framesets titled "Osage IT Incident Report" and "Sycuan Incident Report" that load Cognito Forms (https://www.cognitoforms.com/SignatureSystemsInc/SycuanIncidentReport); sycuantest 301s to https://ssipos.com/sycuan/ ("Sycuan Incident Report - Signature Systems Casino POS System", WordPress page dated 2024-06-07). That is a per-casino web form for the customer to REPORT an incident to SSI, the opposite of a console showing terminal/printer/KDS online-offline status with remote reboot, software-version visibility or staged rollout. certspotter on pdqpos.com also named pci.pdqpos.com (a MAXpci PCI-compliance portal, same site as maxpci.com and pci.hubwallet.com) and session/support/ssi-jira.pdqpos.com (no answer on 443). None is a device console. Held unknown. Retrieved 2026-09-18. adversarially verified

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

hardware-callerid-integration

CORRECTED: the previous note called caller ID a "notable gap ... never mentioned in the catalog or on the site", which held for the artefacts then in hand and does not hold now. The order-entry screenshot on the Signature Systems overview flyer puts a red "Phone" key in the top-left corner of the order screen, the most prominent position on it, captioned "(Hold For Call History)". So a telephony/call-history function is a first-class POS control, which fits the pizza-and-delivery positioning. Shortfalls: the claim wants the customer record and order history to POP on an INCOMING call, and what is evidenced is an operator-initiated key held to open history -- the opposite interaction. No caller-ID hardware, telephony provider or integration is named anywhere, and no documentation describes the flow. The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-SSI-flyer-lower-res.jpg · retrieved 2026-08-30

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

extensibility-public-api-docs

Upheld, and this is now the sharpest evidence for it rather than an inference. Five Signature Systems press releases -- RedHawk, The Lodge, Wildwood, Cordish Gaming and Parx -- carry the same About-SSI boilerplate crediting the product with 'RESTful APIs with full documentation'. The vendor therefore states that API documentation EXISTS. This claim asks whether that documentation is readable without a signed partner agreement, NDA or sales call, and it is not: no developer, docs, api or support subdomain resolves; the live pdqpos.com surface is six pages plus six parameterised detail pages, none of them a reference; ssipos.com is a 13-document WordPress site whose own type census (wp/v2/types) declares only posts, pages and media, with no documentation project; and neither host's whole published output contains `swagger`, `openapi`, `oauth`, `sdk`, `api key` or `developer portal` even once. The word endpoint reads 10 times in 5 documents and is a trap -- every occurrence is the security product's sense (Managed Endpoint, next-gen endpoint software, Endpoint Detection & Response), never an API route. https://ssipos.com/wp-content/uploads/2021/07/PR_RedHawk.pdf · retrieved 2026-09-09

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

extensibility-api-access-cost

CORRECTED after verification - an earlier pass read this line as costing nothing, which was wrong. In the published pricing workbook the 'API Reporting Interface - Annual' row is a separate annual subscription line whose unit-price cell is not a literal but the formula SUM(B35+B48+B49)*115, i.e. 115 US dollars per year for each POS terminal, 7-inch tablet and 10-inch tablet in the estate. It displays 0 only because this prospect's device quantities were left unfilled. The list price IS published, and API access is a recurring PER-DEVICE charge levied on top of the base licence - precisely what the claim (included in the base subscription at no additional per-location fee, surcharge or upgraded-plan requirement) denies. Scored no on presence of evidence, not on absence. PROVENANCE LIMIT: this is one workbook, dated serial 44319 = 2021-05-03, published on https://ssipos.com/sky-river/ as a landing page addressed 'for WILTON RANCHERIA SKY RIVER', carrying a buyer-specific 'Boyd Discount' line which applies only to the base-licence row. It is the vendor's only published pricing artefact; treat it as evidence about PDQ's 2021 commercial model, not a current restaurant-segment price list. https://ssipos.com/wp-content/uploads/2021/04/Sky-River-Casino-Quote-05-3-21.xlsx · retrieved 2026-09-12 adversarially verified

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

extensibility-partner-revshare

331st: CLAIM: the vendor publishes its partner/marketplace commercial terms (referral fee, revenue-share percentage, or per-location partner fee) in public documentation. VERDICT: no - a publication claim against a bounded publication census. PUBLICATION CENSUS (331st, re-derived today, not inherited): (1) www.pdqpos.com - homepage 110,961 bytes and 29 distinct hrefs, byte-identical to the 326th copy; its legal set is exactly three documents (termsofuse.aspx, privacypolicy.aspx, smsprivacypolicy.aspx), whose stripped text is identical to the 328th copies; no robots.txt and no sitemap (both 404); pdqtek.com, pdqsecurity.com and pdqoo.com redirect to pdqpos.com and pdqdt.com serves the same 110,961-byte page. (2) ssipos.com - /wp-json/wp/v2/types lists only core types (post, page, attachment, menu/FSE internals, wpb_gutenberg_param), so there is no custom legal/kb type to page; pages X-WP-Total 8, posts 5, media 216 (213 paged by offset; the non-image files are 12 PDFs - press releases, awards, two whitepapers, the SSI Security brochure - one 2021 price-quote .xlsx and two stock mp4s). (3) Hosts: the crt.sh name set (324th/327th) has no status, docs, developer or partner host; status.pdqpos.com, status.ssipos.com and status.mypdqpos.com do not resolve; certspotter was rate-limited today (not run). (4) Controls were run tokenised, word-boundary, over 3,429 text documents in 17 on-disk corpora (.cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, and this session's fetches). CONTROLS: 'partner program' 0, 'revenue share/sharing' 0, 'referral fee(s)' 0, 'reseller/dealer/VAR program' 0 documents. 'commission(s)' 32 documents are all PDQ marketing about THIRD-PARTY delivery commissions ('20-30% in fees and commissions') or PDQ Online Ordering being 'Commission-free' - a merchant price, not partner terms. ssipos.com's WP search for 'partner' returns 2 pages, whose only hits are 'SSI & Branch, our new partner!' (a podcast title) and 'Platinum Partner: Sophos' (a supplier badge). The only historical dealer surface is the 2000s pdqpos.com/dealers.htm, an application form asking the applicant's 'Gross Annual Sales' - it states no terms. PDQ's API is unpublished (PDQEnterpriseAPI SOAP, 327th), and no partner portal host exists. Retrieved 2026-09-18. https://pdqpos.com/ · retrieved 2026-09-18 adversarially verified

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

extensibility-free-sandbox

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. The finding here has changed shape and is worth stating precisely. It is no longer right to say PDQ has no APIs: the About-SSI boilerplate in all four 2025 press releases claims "value-added integrations via RESTful APIs", ssipos.com's software panel says "RESTful APIs", and Yellow Dog documents a working two-way integration in which PDQ is issued an API user and credentials, posts sales daily at 9am, corrects them by PUT, and pulls item data every 15 minutes. What is absent is PUBLIC access: developer.pdqpos.com, developers.pdqpos.com, api.pdqpos.com and portal.pdqpos.com do not resolve, ssipos.com has no developer route, and no reference, sandbox, OAuth flow, webhook contract, rate limit, versioning policy or partner programme terms are published anywhere. `product.yaml` now records this as partner-gated rather than none. So these cells are unknown because access is behind a sales conversation, which is a different fact from the capability being absent. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd: per-cell control, does not settle the cell. Vocabulary 'sandbox|test environment|test store|demo store|demo account|developer account|developer portal|developer program|dev environment' over 3,387 on-disk PDQ files (both vendor sites, the 2016-2025 PDFs, the Wayback WordPress corpus, the V2 ordering client's 52 chunks, the app-store listings): ZERO PDQ-authored hits. The only hits are POISON: Datacap's own 'Developer Portal' navigation (a payment partner's site), Next.js's image CSP string 'sandbox;' and React's 'non-minified dev environment' error text inside the ordering-client bundle. The one live API host (servicesapi.mypdqpos.com) publishes no doc or signup path (20 paths = 0-byte 404 like the /zzz-nope control). Held unknown, not 'no': PDQ runs an unpublished partner API (the quote workbook prices an 'API Reporting Interface') and a capability 'no' is not bounded by a public census in that case. Retrieved 2026-09-18. || 333rd: NEW SURFACES (333rd), none a developer sandbox. (1) dev.pdqonlineordering.com answers 200 (65,819 bytes) titled "Dev V2 Testing": it is a STORE TENANT of the ordering site (the same store-picker page as live tenants) that PDQ uses for testing, with no developer signup, keys, seeded-data statement or API. (2) admin.pdqonlineordering.com answers 403 "This site is only accessible from within the office network. No external access is allowed." (3) The live online-ordering service https://api.pdqonlineordering.com/PDQOnlineAPI.asmx (WSDL, 11 POS_* operations, each taking PassKey + StoreID) has no test/sandbox endpoint and no signup; 40 sibling .asmx names 404. (4) SwaggerHub: org "pdq" exists (https://api.swaggerhub.com/apis/pdq, 1 API, "Keyshare API" 1.93, 2026-04-28), but its paths are /keyshare/doorbells and /keyshare/access-users/.../assign-credential/{lock_mac}: a door-lock product, a HOMONYM, not PDQ POS; org "SSI" holds only 2017 Petstore/EatBacon IoT samples (homonym); pdqpos, PDQ-POS, SignatureSystems, ssipos, mypdqpos and 7 other slugs 404. Held unknown: PDQ runs unpublished partner APIs, so a capability no is not bounded. Retrieved 2026-09-18. adversarially verified

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

extensibility-oauth-partner-apps

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. The finding here has changed shape and is worth stating precisely. It is no longer right to say PDQ has no APIs: the About-SSI boilerplate in all four 2025 press releases claims "value-added integrations via RESTful APIs", ssipos.com's software panel says "RESTful APIs", and Yellow Dog documents a working two-way integration in which PDQ is issued an API user and credentials, posts sales daily at 9am, corrects them by PUT, and pulls item data every 15 minutes. What is absent is PUBLIC access: developer.pdqpos.com, developers.pdqpos.com, api.pdqpos.com and portal.pdqpos.com do not resolve, ssipos.com has no developer route, and no reference, sandbox, OAuth flow, webhook contract, rate limit, versioning policy or partner programme terms are published anywhere. `product.yaml` now records this as partner-gated rather than none. So these cells are unknown because access is behind a sales conversation, which is a different fact from the capability being absent. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 327th: 327th (APPS/HOSTS SLICE): NEW SURFACE, does not settle the cell, but it cuts against the claim's mechanism. The only PDQ integration endpoint anyone has now located is an ASP.NET ASMX service bound as 'PDQEnterpriseAPISoap' and 'PDQEnterpriseAPISoap12' (SOAP 1.1 and 1.2) in the vendor's own DISCO document; SOAP/ASMX of that generation carries WS-Security or a static credential, not OAuth 2.0 scopes. Held unknown rather than scored because (a) the WSDL is unreachable (all pushapi-* hosts time out on 443 and 80) so the auth scheme is inferred from the binding, not read, and (b) one service is not a census of all of PDQ's APIs - the 324th merge already rejected that shape. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE, does not settle the cell. The ASMX service help page of the 'push' API host, archived 2 Jun 2017 (https://web.archive.org/web/20170602001953/http://pushapi-3.mypdqpos.com/, 4,483 bytes, the standard .NET page 'PDQEnterpriseAPI Web Service ... The following operations are supported'), enumerates the service's COMPLETE operation list: 'ADMIN_CleanSales', 'APIOnline', 'StoreIsValid', 'SubmitOrderTotals', 'SubmitTransactionData', 'SyncAllData', 'SyncCompleted', 'UploadMiscData' - eight operations, all of them the store uploading its own data to the myPDQPOS enterprise cloud (Submit/Sync/Upload) plus two health/identity checks. The auth shape it shows is a per-STORE identity check ('StoreIsValid') and no token, authorize, grant, scope or revoke operation - consistent with the 327th's inference of a static store credential rather than OAuth 2.0, but it is a store-to-vendor service, not a third-party-app surface. The live successor host servicesapi.mypdqpos.com answers '/' with the 14-byte text 'API is running' and publishes nothing: /swagger, /swagger/ui/index, /swagger/docs/v1, /swagger/v1/swagger.json, /Help, /help/api, /api, /api/help, /docs, /openapi.json, /$metadata, /odata, /api/v1, /v1, /robots.txt, /health, /status, /version and the PDQEnterpriseAPI.asmx path all return the same 0-byte 404 as the /zzz-nope control; pushapi-1/-3 and pushapi.mypdqpos.com time out on 80 and 443 today. Held unknown: one retired internal service is not a census of PDQ's APIs. Retrieved 2026-09-18. || 333rd: NEW SURFACE (333rd, host probing led by certspotter/crt.sh): a LIVE, anonymous ASMX service at https://api.pdqonlineordering.com/PDQOnlineAPI.asmx (IIS 10 / ASP.NET 4.0.30319 on Azure App Service; root 200, 7,245 bytes, titled "PDQOnlineAPI Web Service"; ?WSDL 200, 23,780 bytes; not a wildcard soft-200: a nonsense tenant host returns 302/128 bytes and /zzz-nope-333 on the API host returns 404/103). Its WSDL enumerates the COMPLETE operation list of the online-ordering<->POS service, 11 operations: POS_PendingOrderList(PassKey, StoreID), POS_OrderDetail(PassKey, StoreID, OrdUID), POS_ConfirmOrder, POS_VoidOrder, POS_GetOrdUID(PassKey, StoreID, OrdWebID), POS_ApplyTip, POS_AdjustTip(..., PmtUID, decTipAmount), POS_VoidCharge, POS_AdjustPayment(..., decDifferance), POS_CloseBatch(PassKey, StoreID), POS_UploadStoreInfo(PassKey, StoreID); every result is an untyped <s:any/> XML blob and the WSDL carries no <wsdl:documentation>. 40 sibling .asmx names (PartnerAPI, ThirdPartyAPI, OloAPI, ChowlyAPI, MenuAPI, IntegrationAPI, PDQEnterpriseAPI, ...) and /api, /swagger*, /help, /webhooks on the same host all 404; Wayback CDX holds no capture of the host. Only GETs of the help page and WSDL were made; no operation was invoked. AUTH SHAPE: every one of the 11 operations takes the same two plain string parameters, PassKey and StoreID, i.e. a static per-store shared secret sent in the SOAP body. There is no token, authorize, grant, scope or revoke operation. That is the store POS authenticating to PDQ's own cloud, not a third-party app being granted scoped access by an operator. Held unknown under the owner ruling of 2026-09-18 (Q6): a complete manifest of ONE internal service is not a route manifest of the vendor's app - the Zonal posture (static-credential services plus an unpublished gateway): PDQ also runs servicesapi.mypdqpos.com (every doc path 404) and partner integrations (Yellow Dog, Olo, Chowly, 3PF) whose interfaces are unseen. Retrieved 2026-09-18. adversarially verified

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

extensibility-webhooks-push

The one documented integration pattern is PDQ polling and posting to a partner's API on a schedule, not PDQ pushing events. || 327th: 327th (APPS/HOSTS SLICE): NEW SURFACE, does not settle the cell. crt.sh/Wayback on mypdqpos.com surfaced a host family literally named 'push': pushapi-3.mypdqpos.com serving PDQEnterpriseAPI.asmx. On the evidence this is the STORE-to-PLATFORM push (a POS pushing its data up to the myPDQPOS enterprise cloud), which is the opposite direction from the claim's platform-to-customer-endpoint webhook, and neither event names, retry behaviour nor signature verification is visible. The hosts do not answer today (443 and 80 both time out) and Wayback has only the ?disco stub, so nothing can be enumerated. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE, does not settle the cell. The ASMX service help page of the 'push' API host, archived 2 Jun 2017 (https://web.archive.org/web/20170602001953/http://pushapi-3.mypdqpos.com/, 4,483 bytes, the standard .NET page 'PDQEnterpriseAPI Web Service ... The following operations are supported'), enumerates the service's COMPLETE operation list: 'ADMIN_CleanSales', 'APIOnline', 'StoreIsValid', 'SubmitOrderTotals', 'SubmitTransactionData', 'SyncAllData', 'SyncCompleted', 'UploadMiscData' - eight operations, all of them the store uploading its own data to the myPDQPOS enterprise cloud (Submit/Sync/Upload) plus two health/identity checks. Not one operation is outbound: no Subscribe/Register/Callback/Notify operation and no endpoint-URL parameter surface, so the 'push' in the host name is the POS pushing TO PDQ's cloud, confirming the 327th's reading of direction. The live successor host servicesapi.mypdqpos.com answers '/' with the 14-byte text 'API is running' and publishes nothing: /swagger, /swagger/ui/index, /swagger/docs/v1, /swagger/v1/swagger.json, /Help, /help/api, /api, /api/help, /docs, /openapi.json, /$metadata, /odata, /api/v1, /v1, /robots.txt, /health, /status, /version and the PDQEnterpriseAPI.asmx path all return the same 0-byte 404 as the /zzz-nope control; pushapi-1/-3 and pushapi.mypdqpos.com time out on 80 and 443 today. Held unknown under the 327th merge rule: this is one retired (2017) internal service, not a census of PDQ's unpublished partner APIs, and a retired-generation doc may not carry a 'no'. Retrieved 2026-09-18. || 333rd: NEW SURFACE (333rd, host probing led by certspotter/crt.sh): a LIVE, anonymous ASMX service at https://api.pdqonlineordering.com/PDQOnlineAPI.asmx (IIS 10 / ASP.NET 4.0.30319 on Azure App Service; root 200, 7,245 bytes, titled "PDQOnlineAPI Web Service"; ?WSDL 200, 23,780 bytes; not a wildcard soft-200: a nonsense tenant host returns 302/128 bytes and /zzz-nope-333 on the API host returns 404/103). Its WSDL enumerates the COMPLETE operation list of the online-ordering<->POS service, 11 operations: POS_PendingOrderList(PassKey, StoreID), POS_OrderDetail(PassKey, StoreID, OrdUID), POS_ConfirmOrder, POS_VoidOrder, POS_GetOrdUID(PassKey, StoreID, OrdWebID), POS_ApplyTip, POS_AdjustTip(..., PmtUID, decTipAmount), POS_VoidCharge, POS_AdjustPayment(..., decDifferance), POS_CloseBatch(PassKey, StoreID), POS_UploadStoreInfo(PassKey, StoreID); every result is an untyped <s:any/> XML blob and the WSDL carries no <wsdl:documentation>. 40 sibling .asmx names (PartnerAPI, ThirdPartyAPI, OloAPI, ChowlyAPI, MenuAPI, IntegrationAPI, PDQEnterpriseAPI, ...) and /api, /swagger*, /help, /webhooks on the same host all 404; Wayback CDX holds no capture of the host. Only GETs of the help page and WSDL were made; no operation was invoked. DIRECTION: the service is POLL-based. The store POS asks the cloud for work (POS_PendingOrderList), fetches each order (POS_OrderDetail) and acknowledges it (POS_ConfirmOrder); nothing is pushed, and no subscribe/register/callback/endpoint-URL operation exists. Even PDQ's own online ordering reaches its own POS by polling, the same direction as the 2017 PDQEnterpriseAPI upload service and the Yellow Dog pull. Held unknown under the owner ruling of 2026-09-18 (Q6): a complete manifest of ONE internal service is not a route manifest of the vendor's app - the Zonal posture (static-credential services plus an unpublished gateway): PDQ also runs servicesapi.mypdqpos.com (every doc path 404) and partner integrations (Yellow Dog, Olo, Chowly, 3PF) whose interfaces are unseen. Retrieved 2026-09-18. adversarially verified

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

extensibility-webhook-reliability

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. The finding here has changed shape and is worth stating precisely. It is no longer right to say PDQ has no APIs: the About-SSI boilerplate in all four 2025 press releases claims "value-added integrations via RESTful APIs", ssipos.com's software panel says "RESTful APIs", and Yellow Dog documents a working two-way integration in which PDQ is issued an API user and credentials, posts sales daily at 9am, corrects them by PUT, and pulls item data every 15 minutes. What is absent is PUBLIC access: developer.pdqpos.com, developers.pdqpos.com, api.pdqpos.com and portal.pdqpos.com do not resolve, ssipos.com has no developer route, and no reference, sandbox, OAuth flow, webhook contract, rate limit, versioning policy or partner programme terms are published anywhere. `product.yaml` now records this as partner-gated rather than none. So these cells are unknown because access is behind a sales conversation, which is a different fact from the capability being absent. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd: NEW SURFACE, does not settle the cell. The ASMX service help page of the 'push' API host, archived 2 Jun 2017 (https://web.archive.org/web/20170602001953/http://pushapi-3.mypdqpos.com/, 4,483 bytes, the standard .NET page 'PDQEnterpriseAPI Web Service ... The following operations are supported'), enumerates the service's COMPLETE operation list: 'ADMIN_CleanSales', 'APIOnline', 'StoreIsValid', 'SubmitOrderTotals', 'SubmitTransactionData', 'SyncAllData', 'SyncCompleted', 'UploadMiscData' - eight operations, all of them the store uploading its own data to the myPDQPOS enterprise cloud (Submit/Sync/Upload) plus two health/identity checks. It has no outbound delivery operation at all, so there is no webhook surface on which signing, retry/backoff or a replayable event log could be documented. The live successor host servicesapi.mypdqpos.com answers '/' with the 14-byte text 'API is running' and publishes nothing: /swagger, /swagger/ui/index, /swagger/docs/v1, /swagger/v1/swagger.json, /Help, /help/api, /api, /api/help, /docs, /openapi.json, /$metadata, /odata, /api/v1, /v1, /robots.txt, /health, /status, /version and the PDQEnterpriseAPI.asmx path all return the same 0-byte 404 as the /zzz-nope control; pushapi-1/-3 and pushapi.mypdqpos.com time out on 80 and 443 today. Held unknown: one retired internal service is not a census of PDQ's partner APIs. Retrieved 2026-09-18. || 333rd: NEW SURFACE (333rd, host probing led by certspotter/crt.sh): a LIVE, anonymous ASMX service at https://api.pdqonlineordering.com/PDQOnlineAPI.asmx (IIS 10 / ASP.NET 4.0.30319 on Azure App Service; root 200, 7,245 bytes, titled "PDQOnlineAPI Web Service"; ?WSDL 200, 23,780 bytes; not a wildcard soft-200: a nonsense tenant host returns 302/128 bytes and /zzz-nope-333 on the API host returns 404/103). Its WSDL enumerates the COMPLETE operation list of the online-ordering<->POS service, 11 operations: POS_PendingOrderList(PassKey, StoreID), POS_OrderDetail(PassKey, StoreID, OrdUID), POS_ConfirmOrder, POS_VoidOrder, POS_GetOrdUID(PassKey, StoreID, OrdWebID), POS_ApplyTip, POS_AdjustTip(..., PmtUID, decTipAmount), POS_VoidCharge, POS_AdjustPayment(..., decDifferance), POS_CloseBatch(PassKey, StoreID), POS_UploadStoreInfo(PassKey, StoreID); every result is an untyped <s:any/> XML blob and the WSDL carries no <wsdl:documentation>. 40 sibling .asmx names (PartnerAPI, ThirdPartyAPI, OloAPI, ChowlyAPI, MenuAPI, IntegrationAPI, PDQEnterpriseAPI, ...) and /api, /swagger*, /help, /webhooks on the same host all 404; Wayback CDX holds no capture of the host. Only GETs of the help page and WSDL were made; no operation was invoked. The service has no outbound delivery at all: the POS polls and acknowledges (POS_PendingOrderList -> POS_OrderDetail -> POS_ConfirmOrder), so there is no webhook on which signing, retry/backoff or a replayable event log could exist. The acknowledge step is a pull-queue confirm, not a documented delivery guarantee. Held unknown under the owner ruling of 2026-09-18 (Q6): a complete manifest of ONE internal service is not a route manifest of the vendor's app - the Zonal posture (static-credential services plus an unpublished gateway): PDQ also runs servicesapi.mypdqpos.com (every doc path 404) and partner integrations (Yellow Dog, Olo, Chowly, 3PF) whose interfaces are unseen. Retrieved 2026-09-18. adversarially verified

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

extensibility-order-injection-api

Upheld but on different evidence than cited. The topbusinesssoftware directory should be discarded; the homepage independently names 'PDQ Third Party Fulfillment (3PF)' alongside 'DoorDash/Uber Eats integration', which establishes that an inbound order path exists. The partial is correct precisely because it is a private partner path, not a public write API — no endpoint, auth model, or payload is documented anywhere. https://www.pdqpos.com/ · retrieved 2026-08-01 adversarially verified

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

extensibility-menu-write-api

Upheld, same correction as above: the pull cadence is 15 minutes with automatic nightly refresh, not a manual-only refresh. The conclusion (a pull-and-cache model, no documented live menu write API) survives, but the vs_reference line characterising PDQ's integration path as 'a once-daily 9am batch sales push with manual terminal refresh for menu changes' is half wrong — the 9am daily figure applies to outbound sales only. || 332nd: 332nd: NEW SURFACE, does not settle the cell. The ASMX service help page of the 'push' API host, archived 2 Jun 2017 (https://web.archive.org/web/20170602001953/http://pushapi-3.mypdqpos.com/, 4,483 bytes, the standard .NET page 'PDQEnterpriseAPI Web Service ... The following operations are supported'), enumerates the service's COMPLETE operation list: 'ADMIN_CleanSales', 'APIOnline', 'StoreIsValid', 'SubmitOrderTotals', 'SubmitTransactionData', 'SyncAllData', 'SyncCompleted', 'UploadMiscData' - eight operations, all of them the store uploading its own data to the myPDQPOS enterprise cloud (Submit/Sync/Upload) plus two health/identity checks. None of the eight writes menu items, modifiers or prices; the direction is POS data up to the enterprise cloud, not menu data down. The live successor host servicesapi.mypdqpos.com answers '/' with the 14-byte text 'API is running' and publishes nothing: /swagger, /swagger/ui/index, /swagger/docs/v1, /swagger/v1/swagger.json, /Help, /help/api, /api, /api/help, /docs, /openapi.json, /$metadata, /odata, /api/v1, /v1, /robots.txt, /health, /status, /version and the PDQEnterpriseAPI.asmx path all return the same 0-byte 404 as the /zzz-nope control; pushapi-1/-3 and pushapi.mypdqpos.com time out on 80 and 443 today. Held unknown: the only documented menu path remains PDQ pulling item data and retail prices from a partner (Yellow Dog), and a retired internal service is not a census of PDQ's partner APIs. Retrieved 2026-09-18. || 333rd: NEW SURFACE (333rd, host probing led by certspotter/crt.sh): a LIVE, anonymous ASMX service at https://api.pdqonlineordering.com/PDQOnlineAPI.asmx (IIS 10 / ASP.NET 4.0.30319 on Azure App Service; root 200, 7,245 bytes, titled "PDQOnlineAPI Web Service"; ?WSDL 200, 23,780 bytes; not a wildcard soft-200: a nonsense tenant host returns 302/128 bytes and /zzz-nope-333 on the API host returns 404/103). Its WSDL enumerates the COMPLETE operation list of the online-ordering<->POS service, 11 operations: POS_PendingOrderList(PassKey, StoreID), POS_OrderDetail(PassKey, StoreID, OrdUID), POS_ConfirmOrder, POS_VoidOrder, POS_GetOrdUID(PassKey, StoreID, OrdWebID), POS_ApplyTip, POS_AdjustTip(..., PmtUID, decTipAmount), POS_VoidCharge, POS_AdjustPayment(..., decDifferance), POS_CloseBatch(PassKey, StoreID), POS_UploadStoreInfo(PassKey, StoreID); every result is an untyped <s:any/> XML blob and the WSDL carries no <wsdl:documentation>. 40 sibling .asmx names (PartnerAPI, ThirdPartyAPI, OloAPI, ChowlyAPI, MenuAPI, IntegrationAPI, PDQEnterpriseAPI, ...) and /api, /swagger*, /help, /webhooks on the same host all 404; Wayback CDX holds no capture of the host. Only GETs of the help page and WSDL were made; no operation was invoked. The only store-data operation is POS_UploadStoreInfo(PassKey, StoreID): the POS uploads its store data UP to the online-ordering cloud. No operation writes items, modifiers or prices DOWN to the POS; the direction matches the 2017 PDQEnterpriseAPI upload service. The only documented menu inflow remains PDQ pulling item data from a partner (Yellow Dog). Held unknown under the owner ruling of 2026-09-18 (Q6): a complete manifest of ONE internal service is not a route manifest of the vendor's app - the Zonal posture (static-credential services plus an unpublished gateway): PDQ also runs servicesapi.mypdqpos.com (every doc path 404) and partner integrations (Yellow Dog, Olo, Chowly, 3PF) whose interfaces are unseen. Retrieved 2026-09-18. adversarially verified

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

extensibility-data-symmetry

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. The finding here has changed shape and is worth stating precisely. It is no longer right to say PDQ has no APIs: the About-SSI boilerplate in all four 2025 press releases claims "value-added integrations via RESTful APIs", ssipos.com's software panel says "RESTful APIs", and Yellow Dog documents a working two-way integration in which PDQ is issued an API user and credentials, posts sales daily at 9am, corrects them by PUT, and pulls item data every 15 minutes. What is absent is PUBLIC access: developer.pdqpos.com, developers.pdqpos.com, api.pdqpos.com and portal.pdqpos.com do not resolve, ssipos.com has no developer route, and no reference, sandbox, OAuth flow, webhook contract, rate limit, versioning policy or partner programme terms are published anywhere. `product.yaml` now records this as partner-gated rather than none. So these cells are unknown because access is behind a sales conversation, which is a different fact from the capability being absent. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd: NEW SURFACE, does not settle the cell. The ASMX service help page of the 'push' API host, archived 2 Jun 2017 (https://web.archive.org/web/20170602001953/http://pushapi-3.mypdqpos.com/, 4,483 bytes, the standard .NET page 'PDQEnterpriseAPI Web Service ... The following operations are supported'), enumerates the service's COMPLETE operation list: 'ADMIN_CleanSales', 'APIOnline', 'StoreIsValid', 'SubmitOrderTotals', 'SubmitTransactionData', 'SyncAllData', 'SyncCompleted', 'UploadMiscData' - eight operations, all of them the store uploading its own data to the myPDQPOS enterprise cloud (Submit/Sync/Upload) plus two health/identity checks. It is WRITE-ONLY in the store-to-cloud direction (no Get/Read/Query operation), the mirror image of the Yellow Dog integration where PDQ is the client that posts sales and GETs item data. Neither is an API exposing the same objects for read and write to a third party. The live successor host servicesapi.mypdqpos.com answers '/' with the 14-byte text 'API is running' and publishes nothing: /swagger, /swagger/ui/index, /swagger/docs/v1, /swagger/v1/swagger.json, /Help, /help/api, /api, /api/help, /docs, /openapi.json, /$metadata, /odata, /api/v1, /v1, /robots.txt, /health, /status, /version and the PDQEnterpriseAPI.asmx path all return the same 0-byte 404 as the /zzz-nope control; pushapi-1/-3 and pushapi.mypdqpos.com time out on 80 and 443 today. Held unknown. Retrieved 2026-09-18. || 333rd: NEW SURFACE (333rd, host probing led by certspotter/crt.sh): a LIVE, anonymous ASMX service at https://api.pdqonlineordering.com/PDQOnlineAPI.asmx (IIS 10 / ASP.NET 4.0.30319 on Azure App Service; root 200, 7,245 bytes, titled "PDQOnlineAPI Web Service"; ?WSDL 200, 23,780 bytes; not a wildcard soft-200: a nonsense tenant host returns 302/128 bytes and /zzz-nope-333 on the API host returns 404/103). Its WSDL enumerates the COMPLETE operation list of the online-ordering<->POS service, 11 operations: POS_PendingOrderList(PassKey, StoreID), POS_OrderDetail(PassKey, StoreID, OrdUID), POS_ConfirmOrder, POS_VoidOrder, POS_GetOrdUID(PassKey, StoreID, OrdWebID), POS_ApplyTip, POS_AdjustTip(..., PmtUID, decTipAmount), POS_VoidCharge, POS_AdjustPayment(..., decDifferance), POS_CloseBatch(PassKey, StoreID), POS_UploadStoreInfo(PassKey, StoreID); every result is an untyped <s:any/> XML blob and the WSDL carries no <wsdl:documentation>. 40 sibling .asmx names (PartnerAPI, ThirdPartyAPI, OloAPI, ChowlyAPI, MenuAPI, IntegrationAPI, PDQEnterpriseAPI, ...) and /api, /swagger*, /help, /webhooks on the same host all 404; Wayback CDX holds no capture of the host. Only GETs of the help page and WSDL were made; no operation was invoked. Of the 11 operations, the reads (PendingOrderList, OrderDetail, GetOrdUID) cover online ORDERS only, and the writes are order state (Confirm/Void), payment adjustments and one store-info upload. No customer, employee, menu or inventory object is read or written. It is a narrow internal order queue, not a general API whose read and write sets could be compared. Held unknown under the owner ruling of 2026-09-18 (Q6): a complete manifest of ONE internal service is not a route manifest of the vendor's app - the Zonal posture (static-credential services plus an unpublished gateway): PDQ also runs servicesapi.mypdqpos.com (every doc path 404) and partner integrations (Yellow Dog, Olo, Chowly, 3PF) whose interfaces are unseen. Retrieved 2026-09-18. adversarially verified

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

extensibility-published-rate-limits

Upheld, and now measured directly rather than derived from the API-docs cell. The old rationale reasoned that because no public API documentation exists there can be no published rate limits; that inference is sound but it was never checked, and the vendor does assert APIs exist. Checked 2026-09-09 against a 151-document corpus assembled 2026-09-09 (102 archived pdqpos.com pages, the 6 live pages, the 6 live rid/pk detail pages, 13 ssipos.com WordPress documents and 24 vendor PDFs; 733,737 characters, every PDF extracted twice, in layout and in reading order) -- and every zero below held unchanged as the corpus grew from 145 to 176 extractions: `rate limit`, `rate limits`, `throttle`, `throttling`, `requests per second`, `quota` and `calls per` occur zero times, tokenised and as bare substrings. The claim wants specific numeric quotas with documented throttling behaviour and headers; not one number, header name or 429 reference is published on either vendor host. This citation is the live home page because it is the whole of the current public surface -- six pages, whose footer offers Terms of Use, Privacy Policy and SMS Privacy Policy and nothing developer-facing. https://www.pdqpos.com/ · retrieved 2026-09-09

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

extensibility-doordash-preferred

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

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

extensibility-first-party-delivery-integrations

DoorDash and Uber Eats claimed as direct integrations in the PDQ Delivery Toolkit / 3PF. Grubhub is never named, and no certification is evidenced. https://www.pdqpos.com/ · retrieved 2026-08-01

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

extensibility-middleware-compatibility

CLAIM: the POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate). VERDICT: yes (table-stakes claim, so grade C marketing suffices). EVIDENCE: PDQ's own Integrations page, headed 'Our value-added, Seamless 3rd Party Integrations Include...', names among others 'DoorDash / Uber Eats / Grubhub / Chowly / ... / Olo' (https://web.archive.org/web/20220627152844/https://www.pdqpos.com/integrations/). Independently, PDQ's Off-Premise Solutions page states: 'PDQ also offers integration to ItsaCheckmate, a 3rd party aggregator that integrates to over forty 3rd party platforms, thus eliminating the need to have a tablet for each provider' (https://web.archive.org/web/20200924180900/https://www.pdqpos.com/2020/06/22/off-premise-solutions/). Chowly and ItsaCheckmate are two of the five platforms the claim names, and the vendor asserts both as shipped integrations; Olo is a third aggregation endpoint. BOUND: this is the vendor's own partner list and it ends 'and more!', so it is a floor, not a census - it cannot carry a `no` about any middleware it omits. Retrieved 2026-09-18. https://web.archive.org/web/20220627152844/https://www.pdqpos.com/integrations/ · retrieved 2026-09-18 adversarially verified

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

extensibility-accounting-connectors

Upheld, and the evidence is stronger than the dossier claimed. Restaurant365 maintains a dedicated PDQ POS partner page, which is materially better than the SEO directory cited. Still partial: QuickBooks Online is unconfirmed and no journal-entry or GL mapping is documented on either side. https://www.restaurant365.com/partners/pdq-pos/ · retrieved 2026-08-01 adversarially verified

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

extensibility-payroll-export

CLAIM: labor hours export natively to at least two NAMED payroll providers without manual re-keying. VERDICT: partial. EVIDENCE: PDQ's Integrations page, 'Our value-added, Seamless 3rd Party Integrations Include...', names among its partners 'Kronos', 'Workday', 'Macromatix', 'DailyPay' and 'Branch' (https://web.archive.org/web/20220627152844/https://www.pdqpos.com/integrations/); the labour data those consume is published in the 2016 Feature Overview as 'Comprehensive time clock management', 'Break calculations', 'Payroll' and the reports 'Hours and wages' and 'Hourly labor' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Two named workforce/payroll platforms (Kronos, Workday) plus two earned-wage-access platforms (DailyPay, Branch) are therefore supported endpoints. SHORTFALLS (named): none of the claim's example providers (Gusto, ADP, Paychex, Paylocity) is named; no export FORMAT or file spec is published; and the page ends 'and more!', so the list is a floor rather than a census. Retrieved 2026-09-18. https://web.archive.org/web/20220627152844/https://www.pdqpos.com/integrations/ · retrieved 2026-09-18 adversarially verified

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

extensibility-bi-data-warehouse

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. The finding here has changed shape and is worth stating precisely. It is no longer right to say PDQ has no APIs: the About-SSI boilerplate in all four 2025 press releases claims "value-added integrations via RESTful APIs", ssipos.com's software panel says "RESTful APIs", and Yellow Dog documents a working two-way integration in which PDQ is issued an API user and credentials, posts sales daily at 9am, corrects them by PUT, and pulls item data every 15 minutes. What is absent is PUBLIC access: developer.pdqpos.com, developers.pdqpos.com, api.pdqpos.com and portal.pdqpos.com do not resolve, ssipos.com has no developer route, and no reference, sandbox, OAuth flow, webhook contract, rate limit, versioning policy or partner programme terms are published anywhere. `product.yaml` now records this as partner-gated rather than none. So these cells are unknown because access is behind a sales conversation, which is a different fact from the capability being absent. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd: NEW SURFACE, does not settle the cell. PDQ runs its own file-transfer server: ftp.pdqpos.com (50.227.231.25; crt.sh shows certificates continuously since 2023, the current one issued 2026-08-16) answers https with 'Server: CerberusFTPServer/11.0' and a 302 to /login for every path, the /zzz-nope control included; port 80 times out. Cerberus serves FTP/FTPS/SFTP, so a vendor-hosted SFTP drop exists, but it is login-gated and nothing states its purpose. Per-cell control over 3,387 on-disk PDQ files for 'data warehouse|snowflake|sftp|ftp|s3 bucket|bigquery|redshift|power bi|tableau|scheduled export|nightly export|data feed|raw data|csv export': the only PDQ-authored hits are the 2016 feature sheet's 'Export to Excel / PDF' and this host's certificates; the rest are third-party pages (Mirus, Otter). A vendor-hosted server is also not the claim's customer-controlled destination. Retrieved 2026-09-18. adversarially verified

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

extensibility-app-marketplace

PDQ publishes no marketplace. SCOPE CORRECTION 2026-08-30: this note previously said "PDQ's entire public web surface was enumerated on 2026-08-09", which was wrong -- that enumeration covered www.pdqpos.com only, and the vendor runs a second site, ssipos.com, named in its own press releases. ssipos.com has been enumerated now (robots.txt is "User-Agent: * / Disallow:", a Yoast sitemap index listing eight pages, no marketplace route) and the verdict is unchanged: what it publishes is a static logo-and-name list of integration partners under "Our Integrations", not a browsable, self-serve marketplace with listings. www.pdqpos.com is one page of 110,963 bytes whose every navigation anchor is a #fragment into itself; the only other real paths are /privacypolicy.aspx, /smsprivacypolicy.aspx, /termsofuse.aspx, /newsarticles.aspx and /ProjectDetail.aspx plus the catalog PDF, and fabricated control paths return genuine 404s so status is informative. No support., docs., api., developer. or portal. subdomain resolves. The homepage advertises 'More than one hundred software integrations' and the catalog's OUR INTEGRATIONS page is an unlabelled logo wall ending 'AND MANY MORE!' - so integrations exist but no named, browsable, self-install directory is published anywhere. https://www.pdqpos.com/ · retrieved 2026-08-09 adversarially verified

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

extensibility-custom-fields-scripting

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. The finding here has changed shape and is worth stating precisely. It is no longer right to say PDQ has no APIs: the About-SSI boilerplate in all four 2025 press releases claims "value-added integrations via RESTful APIs", ssipos.com's software panel says "RESTful APIs", and Yellow Dog documents a working two-way integration in which PDQ is issued an API user and credentials, posts sales daily at 9am, corrects them by PUT, and pulls item data every 15 minutes. What is absent is PUBLIC access: developer.pdqpos.com, developers.pdqpos.com, api.pdqpos.com and portal.pdqpos.com do not resolve, ssipos.com has no developer route, and no reference, sandbox, OAuth flow, webhook contract, rate limit, versioning policy or partner programme terms are published anywhere. `product.yaml` now records this as partner-gated rather than none. So these cells are unknown because access is behind a sales conversation, which is a different fact from the capability being absent. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

extensibility-headless-embedded

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. The finding here has changed shape and is worth stating precisely. It is no longer right to say PDQ has no APIs: the About-SSI boilerplate in all four 2025 press releases claims "value-added integrations via RESTful APIs", ssipos.com's software panel says "RESTful APIs", and Yellow Dog documents a working two-way integration in which PDQ is issued an API user and credentials, posts sales daily at 9am, corrects them by PUT, and pulls item data every 15 minutes. What is absent is PUBLIC access: developer.pdqpos.com, developers.pdqpos.com, api.pdqpos.com and portal.pdqpos.com do not resolve, ssipos.com has no developer route, and no reference, sandbox, OAuth flow, webhook contract, rate limit, versioning policy or partner programme terms are published anywhere. `product.yaml` now records this as partner-gated rather than none. So these cells are unknown because access is behind a sales conversation, which is a different fact from the capability being absent. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd: NEW SURFACE, does not settle the cell. The only live PDQ API host located is servicesapi.mypdqpos.com (crt.sh), which answers '/' with 'API is running' and publishes nothing else: 20 doc/spec paths (/swagger, /swagger/docs/v1, /swagger/v1/swagger.json, /Help, /api/help, /openapi.json, /$metadata, /docs, ...) return the same 0-byte 404 as the /zzz-nope control. The archived 2017 'push' ASMX service on the same domain (https://web.archive.org/web/20170602001953/http://pushapi-3.mypdqpos.com/) lists only store-to-cloud upload operations ('ADMIN_CleanSales', 'APIOnline', 'StoreIsValid', 'SubmitOrderTotals', 'SubmitTransactionData', 'SyncAllData', 'SyncCompleted', 'UploadMiscData'): no order-creation, pricing or tender operation a third-party UI could drive. PDQ's own V2 Next.js ordering client renders server-side, so its engine calls are not visible in the shipped bundle. Held unknown: third-party order paths exist (3PF, Olo, Chowly on the vendor's integrations page) but nothing shows a third-party UI driving the transaction engine via a supported API, and an unpublished partner API cannot bound a 'no'. Retrieved 2026-09-18. || 333rd: NEW SURFACE (333rd, host probing led by certspotter/crt.sh): a LIVE, anonymous ASMX service at https://api.pdqonlineordering.com/PDQOnlineAPI.asmx (IIS 10 / ASP.NET 4.0.30319 on Azure App Service; root 200, 7,245 bytes, titled "PDQOnlineAPI Web Service"; ?WSDL 200, 23,780 bytes; not a wildcard soft-200: a nonsense tenant host returns 302/128 bytes and /zzz-nope-333 on the API host returns 404/103). Its WSDL enumerates the COMPLETE operation list of the online-ordering<->POS service, 11 operations: POS_PendingOrderList(PassKey, StoreID), POS_OrderDetail(PassKey, StoreID, OrdUID), POS_ConfirmOrder, POS_VoidOrder, POS_GetOrdUID(PassKey, StoreID, OrdWebID), POS_ApplyTip, POS_AdjustTip(..., PmtUID, decTipAmount), POS_VoidCharge, POS_AdjustPayment(..., decDifferance), POS_CloseBatch(PassKey, StoreID), POS_UploadStoreInfo(PassKey, StoreID); every result is an untyped <s:any/> XML blob and the WSDL carries no <wsdl:documentation>. 40 sibling .asmx names (PartnerAPI, ThirdPartyAPI, OloAPI, ChowlyAPI, MenuAPI, IntegrationAPI, PDQEnterpriseAPI, ...) and /api, /swagger*, /help, /webhooks on the same host all 404; Wayback CDX holds no capture of the host. Only GETs of the help page and WSDL were made; no operation was invoked. The service joins PDQ's OWN web-ordering UI to the store POS: the POS pulls web orders (POS_PendingOrderList/POS_OrderDetail; POS_GetOrdUID maps the web order id OrdWebID to the POS id) and settles their payments (ApplyTip/AdjustTip/AdjustPayment/VoidCharge/CloseBatch). No operation lets a caller price a cart, create an order or tender against the POS engine, and every call is made BY the POS, so it is not an API a third-party UI could drive. Held unknown under the owner ruling of 2026-09-18 (Q6): a complete manifest of ONE internal service is not a route manifest of the vendor's app - the Zonal posture (static-credential services plus an unpublished gateway): PDQ also runs servicesapi.mypdqpos.com (every doc path 404) and partner integrations (Yellow Dog, Olo, Chowly, 3PF) whose interfaces are unseen. Retrieved 2026-09-18. adversarially verified

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

extensibility-api-versioning-deprecation

Upheld, and now measured rather than derived. Checked 2026-09-09 across a 151-document corpus assembled 2026-09-09 (102 archived pdqpos.com pages, the 6 live pages, the 6 live rid/pk detail pages, 13 ssipos.com WordPress documents and 24 vendor PDFs; 733,737 characters, every PDF extracted twice, in layout and in reading order) -- and every zero below held unchanged as the corpus grew from 145 to 176 extractions: `changelog`, `release notes`, `deprecation`, `deprecated`, `api version`, `versioning`, `sunset` and `breaking change` occur zero times, tokenised and as bare substrings. The vendor does publish a release CADENCE -- the home page advertises 'Releasing new features and updates regularly throughout the year' -- but a cadence is not a changelog and says nothing about breaking changes or notice periods. There is no developer host on which such a policy could live: developer, docs and api subdomains all fail DNS resolution. https://www.pdqpos.com/ · retrieved 2026-09-09

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

extensibility-data-portability-exit

Neither the Terms of Use nor the Privacy Policy addresses export at contract end.

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

reliability-offline-order-entry

332nd: this cell was never checked against the corpus behind its sibling reliability-local-transaction-engine (merged partial/C). CLAIM: order entry, ticket routing and check printing continue on-terminal when the internet connection is lost. VERDICT: partial, grade C. EVIDENCE: PDQ's own abstract for its 'Cloud vs. Traditional POS' episode says the product is built NOT to depend on the internet: 'Learn the real difference between cloud and traditional POS and how a hybrid approach will allow you to embrace the cloud WITHOUT BEING DEPENDENT ON IT!' (https://web.archive.org/web/20220627142629/https://www.pdqpos.com/podcasts/). The companion abstract recommends 'a secure, scalable, powerful, and highly configurable server-based system'. The live SSI site still sells 'Secure, Scalable Server/Hybrid/Cloud Platforms' and 'Cloud/Server/Hybrid solutions' (https://ssipos.com/, fetched today). The 2016 Feature Overview flags only 'Inventory reporting (w/cloud service)' as cloud-dependent and keeps 'Back Office (POS)' in a separate column from the 'Cloud-Reporting Service'. SHORTFALL (named): no PDQ sentence says that order entry, KITCHEN ROUTING or CHECK PRINTING keep working when the WAN drops. The strongest statement is an audio-episode abstract on a RETIRED page (positives capped at partial), the audio tracks are gone (SoundCloud oEmbed 404 for track 858577591 today), and the live pdqpos.com homepage now calls itself 'secure, scalable cloud-based technology'. The 2015 dial-backup sheet ('you will not lose sales if the internet goes down') is about CARD authorisation and is held on reliability-offline-card-auth, so it is not used here. Table-stakes weight, so partial/C is permissible. Retrieved 2026-09-18. https://web.archive.org/web/20220627142629/https://www.pdqpos.com/podcasts/ · retrieved 2026-09-18 adversarially verified

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

reliability-offline-card-auth

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Two things are well established here and neither is what these cells ask. Support is documented in unusual detail for this vendor -- "24x7x365", "100% US-based", and a 2019 flyer claiming an 11-second average time to answer, 95% resolution on the initial call, tiered support on every shift and on-site support as needed -- and security is asserted at length ("PCI DSS Level 1 Compliant Service Provider", "PCI QIR Certified", vulnerability and penetration testing, SAQ simplification). What is documented nowhere is the system's behaviour when things break: offline card authorisation and who carries the decline liability, degraded LAN operation across multiple terminals, offline KDS and printing, printer fallback, sync conflict handling, incident postmortems, backup and restore, and failover of the terminal role. ssipos.com markets "Secure Cloud/Server/Hybrid Platforms", which implies on-premise capability and is not a degradation matrix. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 326th: MERGE HOLD (proposed partial/C, held unknown): a 2015 analog dial-backup line is a second ONLINE authorisation path, not store-and-forward, and an installer sheet that old does not describe the current product's offline behaviour. PROPOSAL AS WRITTEN: CLAIM: card payments can be accepted while offline via store-and-forward, not just cash-only fallback. VERDICT: partial. NEW SURFACE: pci.pdqpos.com/Downloads/ - an installer-facing PDF set nothing on the current site links to, recovered from the Wayback CDX index of pci.pdqpos.com. 'Preparing for Your Security Package' (Signature Systems, July 2015) STEP 3 reads: 'To ensure you have an analog (non-VoIP) phone line - Contact your phone company to make sure you have a DEDICATED ANALOG PHONE LINE FOR DIAL-BACKUP. THIS WAY YOU WILL NOT LOSE SALES IF THE INTERNET GOES DOWN AND WILL NOT NEED TO WRITE DOWN CREDIT CARD NUMBERS.' (https://web.archive.org/web/20150714004622/http://pci.pdqpos.com/Downloads/PDQ%20POS-Preparing%20For%20Your%20Security%20Package.pdf); the companion 'Signature Systems Security Checklist' repeats it as a required install step: 'Ensure that a dedicated phone line has been run to the network cabinet (Note: This line cannot be a Voice Over IP (VoIP) line' (https://web.archive.org/web/20150714201921/http://pci.pdqpos.com/Downloads/Signature%20Systems%20Security%20Checklist.pdf). So a card payment CAN be authorised with the internet down, and the vendor says so in its own words. SHORTFALL (named): the mechanism is DIAL BACKUP - a live authorisation over PSTN - not store-and-forward; no queued-transaction behaviour, no offline floor limit and no post-reconnect settlement report is described, and the documents are 2015 installer collateral for a product line that has since moved to EMV terminals. Retrieved 2026-09-18. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). The card path shown: PDQ's installer names the current station terminal as 'a Lane 3000 credit card terminal' (J1GdSoIMGC4, 57 s), and the Quest tablet video pairs 'a Bluetooth EMV credit card reader' and shows only an online 'Authorize ... Wait for the approval' flow (CRtZ5kwzjcQ, 39-71 s). No upload says store-and-forward, offline, deferred authorisation or floor limit, so the 326th hold (dial-backup is online authorisation) and the 332nd note (Datacap NETePay owns the card path) stand. Retrieved 2026-09-18. adversarially verified

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

reliability-offline-decline-liability

331st: CLAIM: the vendor PUBLICLY documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. VERDICT: no - a publication claim against a bounded publication census. PUBLICATION CENSUS (331st, re-derived today, not inherited): (1) www.pdqpos.com - homepage 110,961 bytes and 29 distinct hrefs, byte-identical to the 326th copy; its legal set is exactly three documents (termsofuse.aspx, privacypolicy.aspx, smsprivacypolicy.aspx), whose stripped text is identical to the 328th copies; no robots.txt and no sitemap (both 404); pdqtek.com, pdqsecurity.com and pdqoo.com redirect to pdqpos.com and pdqdt.com serves the same 110,961-byte page. (2) ssipos.com - /wp-json/wp/v2/types lists only core types (post, page, attachment, menu/FSE internals, wpb_gutenberg_param), so there is no custom legal/kb type to page; pages X-WP-Total 8, posts 5, media 216 (213 paged by offset; the non-image files are 12 PDFs - press releases, awards, two whitepapers, the SSI Security brochure - one 2021 price-quote .xlsx and two stock mp4s). (3) Hosts: the crt.sh name set (324th/327th) has no status, docs, developer or partner host; status.pdqpos.com, status.ssipos.com and status.mypdqpos.com do not resolve; certspotter was rate-limited today (not run). (4) Controls were run tokenised, word-boundary, over 3,429 text documents in 17 on-disk corpora (.cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, and this session's fetches). CONTROLS: 'store-and-forward' 0, 'floor limit(s)' 0 documents. 'offline' 20 documents, none about payments: PDQ's AI-kiosk article ('see their customers in the offline world') and third-party pages (Otter 'online and offline orders', an App Store bundle id) - POISON named. 'declin(e|ed|es)' 4 documents, all a Branch blog line about a 'decline in cash transactions'. The only PDQ document about paying with the internet down is the 2015 installer sheet's DIAL-BACKUP line (already held as not store-and-forward on reliability-offline-card-auth) and it names no liability and no cap. No merchant processing agreement is published: pdqpay.com is a PARKED for-sale domain (redirects to domains.atom.com; Wayback holds only a 2002 GoDaddy park page), so no payments host exists that could carry it. Retrieved 2026-09-18. https://pdqpos.com/ · retrieved 2026-09-18 adversarially verified

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

reliability-lan-degraded-multi-terminal

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Two things are well established here and neither is what these cells ask. Support is documented in unusual detail for this vendor -- "24x7x365", "100% US-based", and a 2019 flyer claiming an 11-second average time to answer, 95% resolution on the initial call, tiered support on every shift and on-site support as needed -- and security is asserted at length ("PCI DSS Level 1 Compliant Service Provider", "PCI QIR Certified", vulnerability and penetration testing, SAQ simplification). What is documented nowhere is the system's behaviour when things break: offline card authorisation and who carries the decline liability, degraded LAN operation across multiple terminals, offline KDS and printing, printer fallback, sync conflict handling, incident postmortems, backup and restore, and failover of the terminal role. ssipos.com markets "Secure Cloud/Server/Hybrid Platforms", which implies on-premise capability and is not a degradation matrix. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

reliability-local-transaction-engine

CLAIM: vendor documents a local/on-premise transaction engine or edge server (not purely cloud request/response) for the ordering path. VERDICT: partial. NEW SURFACE - PDQ's Podcasts & Blogs index carries ~70 vendor-authored abstracts, three of which are about exactly this architecture: 'Cloud vs. Traditional POS - Pure cloud-based POS sure gets a lot of attention these days. But is it really the best platform for your stores? Learn the real difference between cloud and traditional POS and how a HYBRID APPROACH WILL ALLOW YOU TO EMBRACE THE CLOUD WITHOUT BEING DEPENDENT ON IT!'; 'Server vs. Cloud-based POS Systems - Learn the difference...and why a secure, scalable, powerful, and highly configurable SERVER-BASED system could be the best choice for your growing enterprise.'; 'Architectural Framework - The technological platform your POS is running on has a direct effect on reliability...' (https://web.archive.org/web/20220627142629/https://www.pdqpos.com/podcasts/). This is corroborated structurally by the 2016 Feature Overview, which puts 'Back Office (POS)' and the 'Cloud-Reporting Service' in SEPARATE columns and flags only 'Inventory reporting (w/cloud service)' as cloud-dependent (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf), and by the 2015 store-prep guide, which builds the store around an on-premise Sophos firewall at 192.168.1.1 with wall/counter stations behind it (https://web.archive.org/web/20150714004622/http://pci.pdqpos.com/Downloads/PDQ%20POS-Preparing%20For%20Your%20Security%20Package.pdf). SHORTFALL (named): every one of these is marketing or an audio-episode abstract; PDQ publishes no architecture document naming an edge server, its failure modes, or what the ordering path does when the WAN drops. Differentiator weight at grade C, so partial. Retrieved 2026-09-18. https://web.archive.org/web/20220627142629/https://www.pdqpos.com/podcasts/ · retrieved 2026-09-18 adversarially verified

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

reliability-offline-kds-printing

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Two things are well established here and neither is what these cells ask. Support is documented in unusual detail for this vendor -- "24x7x365", "100% US-based", and a 2019 flyer claiming an 11-second average time to answer, 95% resolution on the initial call, tiered support on every shift and on-site support as needed -- and security is asserted at length ("PCI DSS Level 1 Compliant Service Provider", "PCI QIR Certified", vulnerability and penetration testing, SAQ simplification). What is documented nowhere is the system's behaviour when things break: offline card authorisation and who carries the decline liability, degraded LAN operation across multiple terminals, offline KDS and printing, printer fallback, sync conflict handling, incident postmortems, backup and restore, and failover of the terminal role. ssipos.com markets "Secure Cloud/Server/Hybrid Platforms", which implies on-premise capability and is not a degradation matrix. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). What the videos do say about the kitchen path: kitchen routing is by category group to named printers ('The categories are broken down into groups and each group is sent to a specified printers ... go straight to the cook station ... salad station ... bar station', a customer in the 2010 @signaturesystems1 testimonial 'PDQ Touchscreen POS Testimonial', 0ow2fea_MCA, 0-26 s), and PDQ's implementation manager describes installing 'our KDS display systems, which is our kitchen display system management software ... going into different screens all around your line kitchen within your different revenue centers' (J1GdSoIMGC4, 37-84 s). None of the 56 videos says what the kitchen path does when the internet or the store server is down; the tokens offline / internet down / without internet are zero across all transcripts. Retrieved 2026-09-18. adversarially verified

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

reliability-printer-fallback

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Two things are well established here and neither is what these cells ask. Support is documented in unusual detail for this vendor -- "24x7x365", "100% US-based", and a 2019 flyer claiming an 11-second average time to answer, 95% resolution on the initial call, tiered support on every shift and on-site support as needed -- and security is asserted at length ("PCI DSS Level 1 Compliant Service Provider", "PCI QIR Certified", vulnerability and penetration testing, SAQ simplification). What is documented nowhere is the system's behaviour when things break: offline card authorisation and who carries the decline liability, degraded LAN operation across multiple terminals, offline KDS and printing, printer fallback, sync conflict handling, incident postmortems, backup and restore, and failover of the terminal role. ssipos.com markets "Secure Cloud/Server/Hybrid Platforms", which implies on-premise capability and is not a degradation matrix. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have.

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

reliability-sync-conflict-handling

332nd: CLAIM: the vendor DOCUMENTS its conflict-resolution behaviour for edits made on two devices during a network partition (last-write-wins, merge or operator prompt). VERDICT: no. The claim is documentation-shaped, the same shape as this record's merged reliability-offline-feature-matrix, reliability-incident-postmortems and reliability-offline-decline-liability `no`s. PUBLICATION CENSUS (332nd, re-derived today with curl + browser UA, not inherited): (1) www.pdqpos.com - homepage 200, 110,961 bytes, 29 distinct hrefs (same size as the 326th and 331st copies); the legal set is still exactly three live documents (termsofuse.aspx 81,365 B, privacypolicy.aspx 59,266 B, smsprivacypolicy.aspx 52,924 B); /termsofsale, /sitemap.xml and a nonsense path all return the same 1,927-1,928-byte ASP.NET not-found page, so there is no hidden legal or doc page behind those names. (2) ssipos.com WordPress REST: X-WP-Total pages 8, posts 5, media 216 (newest page edit is the homepage, 2026-08-19; the newest post is 2015). (3) Hosts: certspotter was run today (it was rate-limited in the 331st) on pdqpos.com, ssipos.com and mypdqpos.com: 18 names. Two are not in the 324th crt.sh set: session.pdqpos.com (resolves to 50.227.231.99, refuses connections on 443 and 80) and ftp.pdqpos.com (302 to /login, a 'Cerberus Web Client' file-transfer login). Neither is a documentation host; the rest are the known help (BeyondTrust remote-support portal), pci (login), support/ssi-jira (NXDOMAIN) and casino incident-report hosts. PDQ has no KB, manual, help centre or developer portal. (4) Tokenised, word-boundary, case-insensitive controls over 3,674 text documents in 24 on-disk corpora (.cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, all seven q331 pdq-pos slugs, and today's fetches). Agent notes, greps and scripts are excluded. CONTROLS: first a known positive: 'rewards?' 284 docs, so the regex works. 'last-write' 0. 'combine/transfer checks|tables|tabs' 0. 'two/multiple/both/several devices|terminals|stations|tablets' 1 doc, an unrelated publisher's Play listing. 'conflict(s)' 51 docs / 11 snippets, all POISON: conflict-of-law and terms-precedence clauses in PDQ's Terms of Use and Online Ordering Terms, plus a WP Rocket JS string. 'partition*' 3 docs, POISON: 'Partitioned HSM' in the PCI PTS listing and the cookie attribute 'Partitioned' in the V2 ordering bundle. 'merg(e|ed|es|ing)' 48 docs / 21 snippets, POISON: the privacy policy's corporate 'sold, assigned, transferred, or merged', plus zod/zustand/tailwind-merge code in the V2 ordering bundle. 'wins' is casino-slot app copy. 'sync*' 102 docs. The PDQ-authored uses are menus/store hours 'synced' to DoorDash (Jimmy John's release), PDQ Rewards 'automatically syncs your data', and SSI Security's 'Synchronized w/Firewall'. None concerns two devices editing through a partition. The rest are third parties (Fourth/HotSchedules 'Real-Time Syncing', Crunchtime, Otter, Yellow Dog 'Sync Approach', the DoorDash registry). PDQ publishes no conflict-resolution statement on any surface. Retrieved 2026-09-18. https://pdqpos.com/ · retrieved 2026-09-18 adversarially verified

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

reliability-offline-feature-matrix

Upheld, but the old rationale's second half was false and is withdrawn: it said offline operation is not discussed anywhere in the vendor's public materials. The word does appear -- three times, in the phrase 'the offline world', which in all three is the AI-kiosk essay's term for guests physically in the restaurant as opposed to online shoppers. That is not a discussion of offline operation, but it is not silence either, and a later pass searching for it would have found the hits and mistrusted the cell. The verdict stands on unambiguous vocabulary instead: across a 151-document corpus assembled 2026-09-09 (102 archived pdqpos.com pages, the 6 live pages, the 6 live rid/pk detail pages, 13 ssipos.com WordPress documents and 24 vendor PDFs; 733,737 characters, every PDF extracted twice, in layout and in reading order) -- and every zero below held unchanged as the corpus grew from 145 to 176 extractions, `store and forward`, `store-and-forward`, `failover`, `redundancy`, `redundant`, `local database` and `offline mode` occur zero times, tokenised and as bare substrings. The one near-miss is 'cloud-based outages', in an SSI marketing article naming outages as a reason to prefer SSI -- a competitor jab, not a feature matrix. This cited Feature Overview is the vendor's own fullest capability enumeration, four columns covering point-of-sale, reports, payment, employee management, back office, cloud reporting and supported peripherals, and it carries no resilience row of any kind. It is a floor rather than a ceiling -- it is titled an overview and closes by inviting the reader to learn more -- but the claim asks for an EXPLICIT published list of what stops working offline, and no such list exists on any surface. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-09

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

reliability-public-status-page

Upheld and re-probed on 2026-09-09 rather than inherited. status.pdqpos.com still fails DNS resolution, and so do developer, docs, api and support on the same domain, so this is a real NODATA/NXDOMAIN answer and not a refusal that might decay. The cited home page is the entire current public surface: its footer links Terms of Use, Privacy Policy and SMS Privacy Policy only, and the crawl of every href on the host reaches six pages plus six parameterised detail pages, none of them a status surface. Across a 151-document corpus assembled 2026-09-09 (102 archived pdqpos.com pages, the 6 live pages, the 6 live rid/pk detail pages, 13 ssipos.com WordPress documents and 24 vendor PDFs; 733,737 characters, every PDF extracted twice, in layout and in reading order) -- and every zero below held unchanged as the corpus grew from 145 to 176 extractions, `status page`, `statuspage`, `system status` and `service status` occur zero times, tokenised and as bare substrings; `uptime` reads once, in an SSI marketing article about how to evaluate a POS vendor, not about SSI's own availability. The claim wants a public per-component page with current and historical incident state and no login; there is none. https://www.pdqpos.com/ · retrieved 2026-09-09

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

reliability-contractual-uptime-sla

No public MSA. Consistent with the broader finding that no restaurant POS vendor was found publishing a customer-facing uptime SLA with credits. || 326th: NEW SURFACE, does not settle the cell. The only public PDQ statement about contractual commitments is a customer quote in the live Bonanza Casino release: 'One thing that immediately struck us was that SSI DIDN'T JUST PUT OUR NEEDS ON A ROADMAP, THEY WROTE THEIR COMMITMENTS TO US INTO OUR CONTRACT.' (https://pdqpos.com/newsarticles?rid=PR_924_bonanza, 2024-11-06). That says commitments are contractual but names no uptime percentage, no measurement window and no credit schedule, and it is a customer's words, not a published SLA. PDQ publishes a support commitment instead of an availability one - '24x7x365 live in-house team', 'Our domestic, in-house Help Desk is open 24/7/365' (https://pdqpos.com/) - and the product is on-premise/hybrid, so an availability SLA may not apply in the usual form. The live legal set is exactly three documents (termsofuse.aspx, privacypolicy.aspx, smsprivacypolicy.aspx); the Terms of Sale they incorporate by reference is not published, and /sla returned the ASP.NET not-found page. Held unknown. Retrieved 2026-09-18. || 327th: 327th: NEW SURFACE, does not settle the cell, and it is the first PDQ document to put a number on availability. SSI's 2022 whitepaper '3 Vital Things to Consider Before Buying a POS System for F&B', recovered in full this session (3.06 MB live from ssipos.com; the Wayback copy is truncated at 1 MiB), frames uptime as an ASPIRATION and not as a term: 'Combine that with predictable uptime (six nines-99.9999% is the goal); enhanced 24x7x365 live domestic support with menu management at no additional cost with a one-size-fits-all service agreement...' The sentence is advice to the BUYER about what to look for in any vendor, the figure is introduced as 'the goal', there is no measurement window, no exclusions and no service-credit remedy, and the document is an unsigned marketing whitepaper, not the agreement. 'A one-size-fits-all service agreement' is the nearest thing to a contract statement PDQ publishes and it describes support, not availability. Per the standing rule that a stated aspiration is not a commitment, this cannot carry a partial: the claim's operative conjunct is a contractual percentage WITH a credit remedy and neither is present. Held unknown. Retrieved 2026-09-18. adversarially verified

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

reliability-incident-postmortems

331st: CLAIM: the vendor publishes written post-incident reports or root-cause summaries for major outages. VERDICT: no - a publication claim against a bounded publication census. PUBLICATION CENSUS (331st, re-derived today, not inherited): (1) www.pdqpos.com - homepage 110,961 bytes and 29 distinct hrefs, byte-identical to the 326th copy; its legal set is exactly three documents (termsofuse.aspx, privacypolicy.aspx, smsprivacypolicy.aspx), whose stripped text is identical to the 328th copies; no robots.txt and no sitemap (both 404); pdqtek.com, pdqsecurity.com and pdqoo.com redirect to pdqpos.com and pdqdt.com serves the same 110,961-byte page. (2) ssipos.com - /wp-json/wp/v2/types lists only core types (post, page, attachment, menu/FSE internals, wpb_gutenberg_param), so there is no custom legal/kb type to page; pages X-WP-Total 8, posts 5, media 216 (213 paged by offset; the non-image files are 12 PDFs - press releases, awards, two whitepapers, the SSI Security brochure - one 2021 price-quote .xlsx and two stock mp4s). (3) Hosts: the crt.sh name set (324th/327th) has no status, docs, developer or partner host; status.pdqpos.com, status.ssipos.com and status.mypdqpos.com do not resolve; certspotter was rate-limited today (not run). (4) Controls were run tokenised, word-boundary, over 3,429 text documents in 17 on-disk corpora (.cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, and this session's fetches). CONTROLS: 'post-mortem/postmortem' 0, 'root cause' 0, 'status page' 0 PDQ documents. 'outage(s)' 7 documents, all copies of ONE sentence in SSI's 2022 whitepaper warning buyers about competitors' 'cloud-based outages' - not a report of a PDQ outage. 'RCA' 7 hits are binary-stream collisions inside the catalogue PDF. POISON NAMED: 'incident report(s)' 12 documents / 33 hits are the per-casino 'Sycuan Incident Report' and 'Osage IT Incident Report' pages (ssipos.com/sycuan, osage.ssipos.com, sycuan.ssipos.com) - forms for a casino property to FILE an incident with SSI, the opposite direction, and none carries an outage narrative. No status host exists in CT logs or DNS. Retrieved 2026-09-18. https://pdqpos.com/ · retrieved 2026-09-18 adversarially verified

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

reliability-247-live-support

I verified the homepage verbatim: '24x7x365, live in-house team', '100% US-based'. This is a first-party claim about the vendor's own service delivery, presented as standard rather than a premium tier, which is the appropriate evidence class for a support-hours cell. The 2015 contradicting review is a data point about execution, not about the offering. https://www.pdqpos.com/ · retrieved 2026-08-01 adversarially verified

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

reliability-onsite-install

I verified the quote exists — 'The installer who came on-site was professional, knew the system thoroughly and stayed until everything was fully up and running' — but the sole evidence is one anonymous review on a lead-generation directory. The vendor itself does not document on-site installation as a standard included service, and no statement of scope or cost exists. One review is not a vendor commitment. https://softwarefinder.com/retail/pdq-pos/reviews · retrieved 2026-08-01 adversarially verified

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

reliability-menu-build-service

The POS Hardware flyer lists "CUSTOM MENU (with updates at no added cost!)" as an attribute of the ALL-IN-ONE POS, which puts the menu build on the vendor's side of the line and prices ongoing changes at zero. Corroborating, from the vendor's press-release boilerplate: "expert project management, onsite training and education", and Sycuan Casino Resort's VP of IT saying Signature Systems "was able to work with us to re-create all of the functionality, customizations, and integrations that had been built over that 8-year span ... over the course of just a few months". Shortfall: no document states that the INITIAL menu build is included in onboarding, or at what price -- PDQ publishes no implementation, menu-build or onboarding fee at all (see `commercial-implementation-fee-published`), so "at no added cost" is an unpriced marketing phrase against an unpublished base. The artefact is a marketing flyer dated 2019 on ssipos.com (a second vendor site that the 2026-08-01 and 2026-08-09 passes never reached, because both enumerated www.pdqpos.com only); the screenshot inside it is of the running product, with a 4/2/2019 date range on screen. A screenshot is stronger than the prose around it but it is still a sales artefact, it is seven years old, and PDQ publishes no manual in which any of this is specified. Graded D on both counts. HOW IT WAS READ, because that is part of the evidence: the file is named "-lower-res" and is a 2MB JPEG of a print flyer, so the screenshot inside it was cropped and enlarged to be read at all. Panel headings, column headers and button captions come out cleanly at that magnification; small italic body rows are at the limit of the source resolution and are reported here only where a second, independent reading of the same string exists elsewhere on the page. https://ssipos.com/wp-content/uploads/2019/09/SSI-hardware-flyer-lower-res.jpg · retrieved 2026-08-30

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

reliability-hardware-replacement-sla

The catalog's REPAIRS page offers 'Hot-swap available for most products' and 'Turn-around times in days, not weeks', repairs performed by PDQ technicians and 'Some repairs can be performed remotely'; the homepage says the product is 'backed by an industry-leading warranty'. A hot-swap programme therefore exists, but no stated turnaround time, no advance-exchange commitment and no purchasable service tier is published - these are marketing bullets, not a service agreement, and PDQ publishes no terms covering hardware service. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

reliability-backup-restore

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Two things are well established here and neither is what these cells ask. Support is documented in unusual detail for this vendor -- "24x7x365", "100% US-based", and a 2019 flyer claiming an 11-second average time to answer, 95% resolution on the initial call, tiered support on every shift and on-site support as needed -- and security is asserted at length ("PCI DSS Level 1 Compliant Service Provider", "PCI QIR Certified", vulnerability and penetration testing, SAQ simplification). What is documented nowhere is the system's behaviour when things break: offline card authorisation and who carries the decline liability, degraded LAN operation across multiple terminals, offline KDS and printing, printer fallback, sync conflict handling, incident postmortems, backup and restore, and failover of the terminal role. ssipos.com markets "Secure Cloud/Server/Hybrid Platforms", which implies on-premise capability and is not a degradation matrix. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 324th: NEW 2026-09-17 -- SURFACE CENSUS, recorded so it is not re-run. Certificate-transparency listing (https://crt.sh/?q=%25.pdqpos.com&output=json, and the same for ssipos.com) returns 20 and 6 distinct names. Every non-mail host was probed live with curl and a browser UA: help.pdqpos.com = 200, a BeyondTrust Remote Support session-key portal titled 'Signature Systems Support Portal', no knowledge base (4,788 bytes, robots meta 'noindex, nofollow'); support.pdqpos.com and ssi-jira.pdqpos.com do NOT resolve (NXDOMAIN); pci.pdqpos.com = 200 but redirects to /login; osage.ssipos.com and sycuan.ssipos.com are per-casino 'Incident Report' framesets of about 410 bytes. www.pdqpos.com serves NO robots.txt and NO sitemap.xml (both return the ASP.NET 'The resource cannot be found' page); ssipos.com's robots.txt is 'User-Agent: * / Disallow:' and both /sitemap.xml and /wp-sitemap.xml 301. There is therefore no PDQ documentation host that could carry this cell. On the substance: the SSI Security brochure's 'Services' line is a closed vendor-authored list -- 'Managed Firewall, Managed SIEM, Managed Endpoint, Network Security, Wireless Protection, Server Protection, PCI Compliance, Vulnerability Remediation' -- with no backup, restore, disaster-recovery, RPO or RTO entry; that bounds the SECURITY product only, not the POS, so it cannot carry a no. Retrieved 2026-09-17. || 332nd: 332nd: NEW SURFACE, does not settle the cell. Today's certspotter run (the 331st was rate-limited) found two names the 324th crt.sh census lacked. ftp.pdqpos.com returns 302 to /login, a 'Cerberus Web Client' file-transfer portal behind a login: it is a file-exchange host, not an operator backup/restore feature, and it publishes nothing. session.pdqpos.com resolves (50.227.231.99) but refuses connections on 443 and 80. Neither publishes RPO/RTO. The disjunct 'operators can trigger their own backup/restore' is a store-level capability, and no census of PDQ's back office or POS exists, so this stays unknown. Retrieved 2026-09-18. || 333rd: MERGE HOLD (proposed partial/C, held unknown): A customer testimonial of a SUPPORT-guided recovery after a replacement server was couriered ('walked me through it ... got the backup to work') is neither operator self-serve backup/restore nor published RPO/RTO, and 'backup' may mean a spare machine: it shortfalls both limbs of the claim. PROPOSAL AS WRITTEN: 333rd: CLAIM: operators can trigger and retrieve their own data backup/restore, OR the vendor publishes RPO/RTO figures. VERDICT: partial, grade C. EVIDENCE: PDQ's own channel (@PDQPOS, 'CD Pizza Uses PDQ POS', RP7OckoUUho, uploaded 2026-05-15, 44 s, vendor description 'CD pizza is proud to use PDQ POS') publishes an operator's account of a store-server restore: 'I've had a PDQ for roughly 20 years ... I had a my server break on a Thursday. They overnighted it to me and walked me through it and and got the backup to work see almost seamlessly. It was up within 45 minutes.' (YouTube caption track, en-orig, 2-17 s). So a store-level data backup exists, survives the loss of the store server, and was restored onto the replacement BY THE OPERATOR with support on the phone, in under an hour. SHORTFALL (named): the restore was vendor-guided, not shown as a self-serve operator function; nothing says the operator can TRIGGER or RETRIEVE a backup unaided, where backups live, or how often they run; no RPO or RTO is published (a customer's '45 minutes' is an anecdote, not a stated RTO); ASR/caption wording 'got the backup to work' could also be read as a backup MACHINE. It is a customer testimonial in vendor marketing, so grade C, and the cell is niche weight. This cell's certspotter note (ftp.pdqpos.com Cerberus portal, session.pdqpos.com) stands. CENSUS BEHIND IT: Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). No other upload mentions backup, restore, recovery, RPO or RTO. Retrieved 2026-09-18. adversarially verified

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

reliability-pci-dss-4-attestation

CLAIM: the vendor publishes a current PCI DSS v4.0 or v4.0.1 Attestation of Compliance or equivalent covering the post-March-2025 future-dated requirements. The verb is publishes, which is precisely what a bounded estate can settle. What the vendor publishes are claims of status -- PCI DSS Level 1 Certified, PCI QIR Certified, Certified PCI Provider Visa and MasterCard, and the sentence For cardholder data protection, SSI Security also provides PCI DSS compliance, with in-house domestic remediation services from a certified PCI team -- and never a document, a version number, a QSA, or a listing. Attestation of Compliance 0, AOC 0, stem attest 0, ROC 0, QSA 0, 4.0 0, 4.0.1 0, version 4 0. The Our Certifications enumeration, audited rather than accepted: it has no introducing sentence at all. It is a bare heading followed by five bullets -- PCI DSS Level 1 Certified; PCI QIR (Qualified Integrator & Reseller) Certified; Certified PCI Provider: Visa; Certified PCI Provider: MasterCard; Certified Information Systems Security Professional (CISSP) -- and so carries none of the sample markers (including, such as, our certifications include, and more) that would disqualify it as a census. It is nevertheless the stronger of two renderings, not three: the 2025 Product Catalog carries no certification list at all, and the brochure's own front page and the ssipos.com home page both list Sophos Platinum Partner, which Our Certifications omits, while the home-page list closes with the open-ended sentence We are also proud to be a long-standing TRIBAL HUB associate member. The list is therefore not a superset of every credential-shaped claim the vendor makes elsewhere, and it is treated here as strong but not sole evidence. The operative zero is corpus-wide, not list-local: SOC, SOC 2, SOC2, ISO, ISO 27001, 27001, trust center, trust centre, NDA, non-disclosure and the stem attest all return 0 across all 76 document-instruments. Scope, stated so the company and the product are not conflated: the vendor itself makes the certification company-scoped. The ssipos.com home page says PCI DSS Level 1 Compliant Service Provider, and Signature Systems' own 2022-12 article advises buyers to select a provider that is PCI DSS compliant as a company. A service-provider compliance status is not a product attestation, and it is not used here to settle any product-scoped conjunct. Estate bounding, re-probed independently rather than inherited: pdqsecurity.com, pdqtek.com and pdqoo.com all 301 to the pdqpos.com marketing home page (pdqsecurity.com and pdqoo.com direct to https://pdqpos.com on both http and https; pdqtek.com via an http://pdqpos.com hop), and a deep path on pdqsecurity.com and on pdqtek.com returns a zero-length 404, so none of the three serves any content of its own; the www. host of each does not resolve, as does a deliberately fabricated control host, so a DNS failure is distinguishable from a redirect. The pdqpos.com Terms of Use names those four pdq domains but does not name ssipos.com, so the Terms are not the estate enumeration. The reachable published estate is two hosts: pdqpos.com, which is one marketing home page, two ProjectDetail pages, four newsarticles pages, three legal pages and the 2025 Product Catalog PDF, with no robots.txt and no sitemap.xml and no /security, /pdqsecurity, /trust or /compliance path; and ssipos.com, a WordPress site whose REST manifest is strictly larger than its sitemap. A fabricated path 404s hard on both hosts, but pdqpos.com also has a soft-200 shape -- https://www.pdqpos.com/newsarticles returns HTTP 200 carrying a Page Not Found body -- so path probes on that host must be read from the body and not the status. Vintage, and the newer-surface hunt that tests it: the brochure is dated 2022-05-19, PCI DSS v4.0.1 was published June 2024 and its future-dated requirements became enforceable 31 March 2025, so this document cannot carry a 4.x statement as a matter of chronology. That argument is only as good as the search for a newer surface, and that search corrects an earlier assertion that the newest security-bearing artefact is the 2025 Product Catalog: Signature Systems publishes press releases through GlobeNewswire and pdqpos.com links only four of them. The newest, 2026-08-19, together with the 2026-03-30 and 2025-02-26 releases, carries the same corporate boilerplate whose only security clause is the versionless phrase full PCI DSS compliance, with no SOC 2, no ISO 27001, no version number, no attestation, no P2PE and no tokenization. ssipos.com has no /trust/, /compliance/ or /security/ page, all three 404, and its media library ends at 2023-11-13. As of 2026-09-15 no 2024-2026 compliance surface exists anywhere on or off the estate. Controls were run tokenised with both word boundaries, and as a left-boundary stem where morphology matters, over 76 document-instruments -- 13 PDFs in two extractions each, the brochure in three, 24 HTML documents held both raw and tag-stripped after HTML-comment removal, and the media census -- which is 37 distinct documents. Positive controls on the same run: the 1937, SSI 845, POS 683, security 260, PCI 136, DSS 51. Poison published: whitespace-squashed substring matching is unusable on its own -- SCA 161 (a substring of casino, Cordish and landscape), ROC 116, RTO 113, RPO 98, v4 91, SLA 53, QSA 20, AOC 11, MFA 6, every one of which tokenises to 0. Two traps tokenisation does not cure: break returns 146 word-boundary hits of which 144 are CSS line-break and word-break declarations in inline styles on the ssipos.com podcasts page, which also carries 144 of the 148 iframe hits; and the bare word token returns 80 hits, every one an ASP.NET __RequestVerificationToken or cookie-consent token in raw pdqpos.com markup and none of them payment tokenization, so only the stem tokeni, which reads 0, is a usable instrument for this vendor. Extraction instrument: the brochure was re-extracted three ways and the invariance reproduced -- pdftotext -layout, pdftotext plain and pdftotext -raw yield an identical token vocabulary with an empty symmetric difference in all six pairwise directions, an identical single-letter-token count of 15 in all three, and five phrase controls present in all three, so on this multi-column document neither the intra-word-space fault nor the adjacent-column-interleave fault fired. The vocabulary size is a reader artefact and is deliberately not published as a figure: one reader counts 322 tokens and another 312 over the same three files; the invariance is the control. Media census and declared residue: ssipos.com wp-json media X-WP-Total is 216, and the per_page=100 HTTP 500 sits on a record and moves with the sort key, so 212 records were recovered by unioning eight orderings. The residue of 4 was then closed by mime filtering rather than by inference: X-WP-Total is 201 for media_type=image (115 png plus 86 jpeg), 2 for video, 13 for media_type=application and 12 for mime_type=application/pdf, and 201+2+13 is exactly 216, so the type census is closed; mime_type=application/pdf&per_page=100 returns all twelve PDFs in a single page with no 500, which makes the twelve-PDF corpus a census rather than a floor. The four unreachable records are therefore two png, one jpeg and one non-PDF application/* file of unknown type, and that single non-PDF file is the declared hole. X-WP-Total for after=2023-12-01 is 0, which bounds the whole library, residue included, to on or before 2023-11-13. https://ssipos.com/wp-content/uploads/2022/05/SSI-Security.pdf · retrieved 2026-09-15 adversarially verified

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

reliability-mfa-role-based-access

Terminal-level access control is evidenced: the catalog's FINGERPRINT READER entry covers 'every login and manager override', the homepage lists 'secure fingerprint POS log-in' as a system essential, and a manager-override step implies at least a staff/manager permission split. Nothing beyond that is published - no permissions matrix, no role list, and no statement that multi-factor authentication is available or enforceable on back-office or administrative logins. PDQ markets 'PDQ Security (our acclaimed PCI DSS data and cybersecurity platform)' but publishes no security documentation, trust centre or resolving trust. subdomain in which an MFA control could be described. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

reliability-self-serve-training

A public YouTube channel (youtube.com/c/PDQPOS) exists as free video content; no structured LMS/training library and no terminal training mode are documented. https://www.youtube.com/c/PDQPOS · retrieved 2026-08-01

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

reliability-failover-terminal-role

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Two things are well established here and neither is what these cells ask. Support is documented in unusual detail for this vendor -- "24x7x365", "100% US-based", and a 2019 flyer claiming an 11-second average time to answer, 95% resolution on the initial call, tiered support on every shift and on-site support as needed -- and security is asserted at length ("PCI DSS Level 1 Compliant Service Provider", "PCI QIR Certified", vulnerability and penetration testing, SAQ simplification). What is documented nowhere is the system's behaviour when things break: offline card authorisation and who carries the decline liability, degraded LAN operation across multiple terminals, offline KDS and printing, printer fallback, sync conflict handling, incident postmortems, backup and restore, and failover of the terminal role. ssipos.com markets "Secure Cloud/Server/Hybrid Platforms", which implies on-premise capability and is not a degradation matrix. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 333rd: 333rd: NEW SURFACE, a whole-video census, does not settle the cell. Every PDQ-related YouTube upload was read, not just the 20 whose caption tracks the 332nd pulled: the vendor channel @PDQPOS (43 uploads, listed today with yt-dlp), plus two vendor channels no pass had found - @signaturesystems1 (8 customer testimonials, 2010) and @pdqpos1959 (1 slide show) - plus three of the four PDQ videos on its production house's channel @rebelhillproductions (PDQ staff on camera; the fourth, 'PDQ Delivery Tool Kit Explainer Video' LCeKw8MiRQQ, was not transcribed: 'PDQ Point Of Sale {Explainer Video}' l9PNVjny2ck, 'Promotional Video (PDQ POS Training)' 5P5jYoKlOLw, 'Promotional Video (PDQ POS Installation)' J1GdSoIMGC4) and a 2016 reseller demo (pb-WDCf7FnA). YouTube's caption endpoint returned 429 today, so the 35 uncaptioned PDQ audio tracks were downloaded anonymously and transcribed locally (faster-whisper base.en; 23 carry speech, 12 are music-only; '5 Profit Generating Essentials' P1NW60Uw3Gw is slides-only and its frames were read in the 332nd), 56 PDQ videos in all, and the four product demos with no speech in their titles ('PDQ POS Demo' EoHF88VZ9aA 2016 1280x720, 161 distinct frames; 'PDQ POS Overview' YUUejVp2lhY; 'Learn More About PDQ POS' PWqryUhZN4E 1080p; 'PDQ POS' xvVu3cVQl8I) were decoded frame by frame and read as images. Grade C at best (vendor marketing). The only video that touches a server failure is the CD Pizza testimonial (RP7OckoUUho, 2026-05-15): 'I had a my server break on a Thursday. They overnighted it to me and walked me through it and ... got the backup to work ... It was up within 45 minutes.' That shows the store runs on a designated local server that the vendor REPLACES by courier, which is consistent with no automatic terminal takeover, but it does not say what the terminals did between the failure and the replacement, so it cannot carry a `no`; the owner's cloud-POS ruling does not apply because PDQ is server-based (the 2016 demo's 'PDQ POS Manager' screen shows 'IP: 127.0.0.1', 'Version: 3.5.190', EoHF88VZ9aA at 329 s). Tokenised controls over all 43 PDQ speech transcripts: failover 0, redundan* 0, 'backup server' 0, restore 0, recover* 0, offline 0, internet 0; POISON NAMED: 'fail' (2) is 'you fail PCI' and a misheard 'feel free', 'master' occurs only as 'masters in physics', and the one 'backup' is this testimonial. Retrieved 2026-09-18. adversarially verified

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

reliability-cellular-backup

'4G or 5G Models Available' appears twice in the 2025 catalog, once under the 8-INCH TABLET and once under the 10-INCH TABLET, so a cellular data path exists on first-party handhelds as an ordered model variant. Nothing describes it as a fallback: no automatic failover behaviour, no carrier, no data plan, no statement of what happens when store Wi-Fi drops, and no cellular option is offered on the counter station or any fixed display. A model choice at purchase time, not a documented redundancy feature. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

commercial-month-to-month-contract

331st: NEW SURFACE plus a publication census. CLAIM: vendor publicly offers a month-to-month subscription with no minimum multi-year term for its core POS software tier. VERDICT: no, grade C. (a) The census: PUBLICATION CENSUS (331st, re-derived today, not inherited): (1) www.pdqpos.com - homepage 110,961 bytes and 29 distinct hrefs, byte-identical to the 326th copy; its legal set is exactly three documents (termsofuse.aspx, privacypolicy.aspx, smsprivacypolicy.aspx), whose stripped text is identical to the 328th copies; no robots.txt and no sitemap (both 404); pdqtek.com, pdqsecurity.com and pdqoo.com redirect to pdqpos.com and pdqdt.com serves the same 110,961-byte page. (2) ssipos.com - /wp-json/wp/v2/types lists only core types (post, page, attachment, menu/FSE internals, wpb_gutenberg_param), so there is no custom legal/kb type to page; pages X-WP-Total 8, posts 5, media 216 (213 paged by offset; the non-image files are 12 PDFs - press releases, awards, two whitepapers, the SSI Security brochure - one 2021 price-quote .xlsx and two stock mp4s). (3) Hosts: the crt.sh name set (324th/327th) has no status, docs, developer or partner host; status.pdqpos.com, status.ssipos.com and status.mypdqpos.com do not resolve; certspotter was rate-limited today (not run). (4) Controls were run tokenised, word-boundary, over 3,429 text documents in 17 on-disk corpora (.cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, and this session's fetches). 'month-to-month' 0 PDQ documents - POISON NAMED: the single hit ('easy month-to-month terms. No ETF') is the App Store description of 'Pymt - Point of Sale', Pymt, LLC, a third-party app returned by a search. 'no contract(s)' and 'cancel anytime' 0 PDQ documents. 'monthly' appears only as the price basis of the ONLINE ORDERING add-on ('Low Monthly Cost - $79.99 for UNLIMITED orders', 'one low flat monthly fee') and a 'low cost monthly maintenance structure' - billing frequency for an add-on and support, not a no-minimum-term offer for the core POS. (b) The one vendor-published price document for the core POS: a live 'Signature Systems, Inc. POS Proposal for: Sky River Casino' spreadsheet on ssipos.com (WP media id 29184, uploaded 2021-04-29, proposal dated serial 44319 = 2021-05-03, linked from the ssipos.com/sky-river page), unread by every prior pass because it is an .xlsx. It prices the software as 'SSI POS Pro Site License, Unlimited Users, Perpetual' and EVERY recurring line as annual: 'SSI POS Enterprise Reporting - Annual', 'API Reporting Interface - Annual', 'SSI Online Ordering (per Restaurant) - Annual', 'SSI POS Software Support - Annual', 'SSI Integrations Support - Annual', totalled as 'Annual Subscription Total' and 'Software Total Annual Recurring'; it closes 'This sales quote is good for 90 days'. Nothing in it is monthly. Grade C: a vendor-authored price quote for one enterprise account, and the restaurant (pizza/QSR) line may be sold differently - which is why the verdict rests on the absence of any PUBLIC month-to-month offer, with the quote as the only published counter-evidence. Retrieved 2026-09-18. https://ssipos.com/wp-content/uploads/2021/04/Sky-River-Casino-Quote-05-3-21.xlsx · retrieved 2026-09-18 adversarially verified

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

commercial-no-early-termination-fee

331st: CLAIM: the vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. VERDICT: no, the same shape as this record's merged commercial-autorenew-terms-published no/B: the published terms verifiably do not say it. The live Terms of Use (re-fetched today; stripped text identical to the 328th copy, 5,628 words) governs the WEBSITES only and incorporates a merchant 'Terms of Sale' by reference ('All purchases through our site or other transactions for the sale of goods or services ... are governed by our Terms of Sale, which are hereby incorporated into these Terms of Use'), and that document is not published: /termsofsale is 404 again today and the 325th's twelve candidate paths 404 against a nonsense control. Tokenised controls over the Terms of Use: 'early termination' 0, 'termination fee' 0, 'liquidated damages' 0, 'renew' 0, 'subscription' 0, 'month' 0. 'terminat' 3 hits, all about the WEBSITE: 'Monitoring and Enforcement; Termination', 'Terminate or suspend your access to all or part of the Website', and 'terminate the user accounts of repeat infringers'. 'fee' 6 hits, all attorneys' fees/AAA arbitration fees. PUBLICATION CENSUS (331st, re-derived today, not inherited): (1) www.pdqpos.com - homepage 110,961 bytes and 29 distinct hrefs, byte-identical to the 326th copy; its legal set is exactly three documents (termsofuse.aspx, privacypolicy.aspx, smsprivacypolicy.aspx), whose stripped text is identical to the 328th copies; no robots.txt and no sitemap (both 404); pdqtek.com, pdqsecurity.com and pdqoo.com redirect to pdqpos.com and pdqdt.com serves the same 110,961-byte page. (2) ssipos.com - /wp-json/wp/v2/types lists only core types (post, page, attachment, menu/FSE internals, wpb_gutenberg_param), so there is no custom legal/kb type to page; pages X-WP-Total 8, posts 5, media 216 (213 paged by offset; the non-image files are 12 PDFs - press releases, awards, two whitepapers, the SSI Security brochure - one 2021 price-quote .xlsx and two stock mp4s). (3) Hosts: the crt.sh name set (324th/327th) has no status, docs, developer or partner host; status.pdqpos.com, status.ssipos.com and status.mypdqpos.com do not resolve; certspotter was rate-limited today (not run). (4) Controls were run tokenised, word-boundary, over 3,429 text documents in 17 on-disk corpora (.cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, and this session's fetches). No MSA, subscription agreement or order form is published on any vendor host. This is not a finding that an ETF exists - exit economics sit in the unpublished Terms of Sale - only that no published term promises there is none. Retrieved 2026-09-18. https://www.pdqpos.com/termsofuse.aspx · retrieved 2026-09-18 adversarially verified

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

commercial-autorenew-terms-published

The published Terms of Use governs website use only and contains no auto-renewal term or cancellation notice window; no subscription agreement is publicly accessible. https://www.pdqpos.com/termsofuse.aspx · retrieved 2026-08-01

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

commercial-processing-not-bundled

CLAIM: the POS can be purchased and operated with a third-party payment processor of the operator's choice, with no mandatory in-house processing lock. VERDICT: partial. EVIDENCE: PDQ states processor plurality as a product property - the 2016 Feature Overview's Payment column reads 'INTEGRATED TO MULTIPLE PAYMENT GATEWAYS AND PAYMENT PROCESSORS FOR CREDIT CARDS' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf) - and names the processors and gateways individually on its Integrations page: 'Vantiv/Worldpay', 'Cayan/Tsys', 'Freedom Pay', 'Datacap', 'TRUIST' (https://web.archive.org/web/20220627152844/https://www.pdqpos.com/integrations/); the 2015-era site carried dedicated /mercury/, /vantiv/ and /payments/ pages. PDQ's own processing brand, PDQ Pay, is presented as an additional offering ('Signature Systems, Inc. is proud to OFFER PDQ Pay', https://pdqpos.com/), not as a condition of buying the POS. SHORTFALLS (named): no contract language is public - PDQ's live Terms of Use incorporates a separate, unpublished 'Terms of Sale' - so nothing rules out a commercial requirement to use PDQ Pay; and no page states in words that the operator may choose their own processor. Differentiator weight at grade C, so partial. Retrieved 2026-09-18. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-18 adversarially verified

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

commercial-interchange-plus-published

Upheld and now measured. The vendor markets a payments position without ever pricing it -- the cited home page says PDQ POS 'lowers those costly credit-card fees' for pizzerias, and the archived Feature Overview lists 'Integrated to multiple payment gateways and payment processors for credit cards' -- so this is a deliberate quote-only posture, not an oversight. Across a 151-document corpus assembled 2026-09-09 (102 archived pdqpos.com pages, the 6 live pages, the 6 live rid/pk detail pages, 13 ssipos.com WordPress documents and 24 vendor PDFs; 733,737 characters, every PDF extracted twice, in layout and in reading order) -- and every zero below held unchanged as the corpus grew from 145 to 176 extractions, `interchange`, `basis point`, `bps`, `flat rate`, `processing rate`, `discount rate`, `surcharge`, `cash discount` and `dual pricing` occur zero times, tokenised and as bare substrings. No bps figure, no per-transaction figure, no blended rate and no markup of any kind is published, so the claim -- which requires an interchange-plus option with the markup stated as bps plus per-transaction -- fails at the first step. The 20-page 2025 product catalogue is a hardware and peripheral catalogue and carries no price on any page either. https://www.pdqpos.com/ · retrieved 2026-09-09

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

commercial-rate-increase-clause

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Commercially PDQ publishes nothing that binds it. The only contract-shaped documents on either host are a website Terms of Use and a Privacy Policy, both of which govern use of the website and neither of which is a subscription agreement: there is no minimum term, no auto-renewal clause, no cancellation notice period, no early-termination fee, no rate-increase clause, no module unbundling statement, and no merchant-data export or ownership term. Pricing is quote-only across the board -- roughly 25 hardware SKUs are catalogued with zero prices, and no software, processing or implementation figure appears anywhere. So these cells are unknown because the operative agreement is private, which is the ordinary posture for a quote-only enterprise vendor and is itself the finding. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: MERGE HOLD (proposed no/B, held unknown): PDQ is processor-agnostic (Datacap NETePay, any US processor), so the processing agreement is the third-party processor's; absence of that agreement from PDQ's own sites does not bound its terms, and an unpublished contract is not a stated absence of a cap. PROPOSAL AS WRITTEN: 332nd: CLAIM: the processing agreement caps or prohibits unilateral vendor-initiated rate increases outside pass-through interchange/network changes, or grants penalty-free exit on any increase. VERDICT: no, grade B - no processing agreement or rate card is published on any vendor host, so no published term caps an increase or grants an exit (the shape merged for microworks-prism no/B and, on this record, commercial-no-early-termination-fee no/B and commercial-autorenew-terms-published no/B). PUBLICATION CENSUS (332nd, re-derived today with curl + browser UA, not inherited): www.pdqpos.com homepage 200 / 110,961 bytes (same byte count as the 326th and 331st copies); its legal set is exactly termsofuse.aspx (200, 81,365 B), privacypolicy.aspx (200, 59,266 B) and smsprivacypolicy.aspx (200, 52,924 B); /termsofsale 404 (1,927 B) against a nonsense-path control /zzz-nope-332 404 (1,928 B), so the merchant 'Terms of Sale' the Terms of Use incorporates by reference is not published; pdqpay.com redirects to a domain-for-sale page (domains.atom.com/lpd/name/PdqPay.com); ssipos.com WP REST pages X-WP-Total 8, posts 5 (unchanged). The retired WordPress pdqpos.com's own payments pages, which no prior pass had opened, were read from Wayback: /payments/ (12 captures 2024-10-14..2025-12-09, latest https://web.archive.org/web/20251209110121id_/https://www.pdqpos.com/payments/) and /pdq-pay/ (2024-07-16): each is ~830 words of qualitative 'PDQ PAY' copy ('Secure, innovative payment processing', 'leading fraud intelligence', 'accepting both traditional and alternative payment types') with no rate, no schedule and no agreement. CONTROLS (tokenised, word-boundary, case-insensitive, over 3,459 text documents in 18 on-disk pdq corpora: .cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, q331/pdq-pos/f and this session's fetches; KNOWN-POSITIVE controls 'surcharg*' 19 docs and 'terminat*' 94 docs fire, so the regexes work): 'processing|merchant|processor agreement(s)|application(s)|contract(s)' 0 documents; 'interchange' 0; 'pass-through' 0; 'rate|price|pricing|fee increase(s)|change(s)|adjustment(s)' 19 documents, all POISON - 'Automatic Price Changes' is ProBar/ProTable time-of-day MENU pricing ('Up to four different prices for an item'), not a processing rate. The live Terms of Use governs the WEBSITES and its only change clause is 'Signature may, at its sole discretion, modify the Terms of Use ... at any time' - about the website terms, not rates; all purchases are pushed to the unpublished 'Terms of Sale'. The PDQ PAY pages (live homepage section; retired /payments/ and /pdq-pay/ via Wayback) publish no rate and no agreement, and pdqpay.com is a for-sale domain. PDQ is processor-agnostic via Datacap NETePay ('supports all processors in the US', Datacap 2016 post, grade D), so the merchant's processing agreement is with a third-party processor PDQ does not publish. This is a finding about PUBLISHED terms: a private agreement may still carry a cap. Retrieved 2026-09-18. adversarially verified

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

commercial-pricing-published

Re-verified without the denylisted directories. I fetched the live site (single page, 110KB of HTML) and it contains no instance of 'pricing', 'price', or any dollar figure; the only commercial CTA is a contact form. I then enumerated every pdqpos.com URL ever captured by the Internet Archive (CDX, 165 non-asset paths spanning the 2002 HTML site through the 2026 rebuild) and no /pricing, /cost or /plans route has ever existed. Positive evidence of absence on the vendor's own commercial surface, not merely a failure to find one. https://www.pdqpos.com/ · retrieved 2026-08-02 adversarially verified

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

commercial-module-unbundling

Modules are billed as separate, independently-quantified annual lines distinct from the base SSI POS Pro Site License: Online Ordering (per Restaurant) at a static 1550, plus Enterprise Reporting, API Reporting Interface, SIEM, Endpoint Anti-Virus and Integrations Support. A-la-carte PURCHASE is therefore established. THREE SHORTFALLS: (1) independent CANCELLATION without repricing the base licence is nowhere addressed; (2) loyalty, inventory, payroll and marketing - four of the six modules the claim names - have no SKU in the list at all; and (3) these are not freely-standing SKUs, because four of the six annual lines are priced by FORMULA over the hardware estate (Enterprise Reporting = devices*228, Software Support = devices*276, SIEM = devices*180, Endpoint AV = devices*24), so their price is coupled to the base configuration rather than independent of it. PROVENANCE LIMIT: this is one workbook, dated serial 44319 = 2021-05-03, published on https://ssipos.com/sky-river/ as a landing page addressed 'for WILTON RANCHERIA SKY RIVER', carrying a buyer-specific 'Boyd Discount' line which applies only to the base-licence row. It is the vendor's only published pricing artefact; treat it as evidence about PDQ's 2021 commercial model, not a current restaurant-segment price list. https://ssipos.com/wp-content/uploads/2021/04/Sky-River-Casino-Quote-05-3-21.xlsx · retrieved 2026-09-12 adversarially verified

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

commercial-hardware-purchase-outright

DOWNGRADED from yes after verification. Conjunct 1 IS established: the workbook carries static literal unit prices for all three hardware categories the claim names - POS terminal with fingerprint reader and MSR 1700, Kitchen Video Display Bundle 1500, Receipt Printer 400, Kitchen Printer 400 - plus EMV pin pads 450, tablets 1350/1800, kiosk 5995 and cash drawers 300. Unlike the software rows, these hardware cells are literals rather than formulas, so they do function as a rate card, and the buyer-specific discount provably touches only the base-licence row. SHORTFALL: conjunct 2, no mandatory multi-year hardware lease or rental, rests only on no lease line appearing in this one document. The tokens lease, rental and purchase each occur ZERO times in the workbook, so it is silent both ways - a document-internal absence, not a vendor statement. PROVENANCE LIMIT: this is one workbook, dated serial 44319 = 2021-05-03, published on https://ssipos.com/sky-river/ as a landing page addressed 'for WILTON RANCHERIA SKY RIVER', carrying a buyer-specific 'Boyd Discount' line which applies only to the base-licence row. It is the vendor's only published pricing artefact; treat it as evidence about PDQ's 2021 commercial model, not a current restaurant-segment price list. https://ssipos.com/wp-content/uploads/2021/04/Sky-River-Casino-Quote-05-3-21.xlsx · retrieved 2026-09-12 adversarially verified

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

commercial-hardware-not-locked

One named third-party device appears in the first-party catalog: the QSR ADD-ONS label printer, 'This Epson label printer is quick and easy to use'. That is the whole of the evidence. The catalog's other 35-odd SKUs are PDQ-branded, no compatibility list or supported-device matrix is published, and nothing states that a generic ESC/POS printer, a standard cash drawer or a third-party tablet can be attached. Note that the receipt printer's 'can be connected via serial, USB or ethernet to integrate with any system' points the other way - it describes PDQ hardware working with foreign systems, not PDQ POS accepting foreign hardware - and is not evidence for this claim. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-08-09 adversarially verified

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

commercial-implementation-fee-published

Upheld, but the old rationale contained a factual error that had to be corrected: it asserted that no implementation, menu-build, onboarding or training fee is published NOR STATED AS $0. The second clause is false. A promotional banner on 11 archived pdqpos.com pages, including this one, reads 'UNLIMITED ORDERS ONE LOW FLAT MONTHLY FEE NOW: NO SETUP FEES', under a headline offering online ordering with no POS required -- an explicit statement of a zero setup fee. The verdict survives anyway, on three grounds. The offer is for the STANDALONE online-ordering product, sold explicitly to operators running someone else's POS, not for a PDQ POS implementation. It is a dated 2020 promotion ('NOW:') that no longer appears anywhere on the live six-page site. And the claim is a conjunction -- implementation, menu-build, onboarding AND training fees, each published as an amount or as $0 -- of which a setup-fee waiver on one add-on satisfies at most a fraction; the accompanying 'ONE LOW FLAT MONTHLY FEE' states no figure, and `implementation fee`, `menu build`, `onboarding fee`, `training fee`, `installation fee` and `activation fee` all occur zero times across a 151-document corpus assembled 2026-09-09 (102 archived pdqpos.com pages, the 6 live pages, the 6 live rid/pk detail pages, 13 ssipos.com WordPress documents and 24 vendor PDFs; 733,737 characters, every PDF extracted twice, in layout and in reading order) -- and every zero below held unchanged as the corpus grew from 145 to 176 extractions. The vendor's own catalogue does confirm that onboarding labour is real and priced by quote: it advertises 'onsite training and education' and the home page promises multi-unit operators they will not have to 'lift a finger for installation and testing'. https://web.archive.org/web/20200924181727/https://www.pdqpos.com/2020/06/17/how-to-win-at-online-ordering-delivery/ · retrieved 2026-09-09

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

commercial-data-export-self-serve

CLAIM: operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee. VERDICT: partial. EVIDENCE: the 2016 Feature Overview's Reports column ends with the export primitives 'EXPORT TO EXCEL / PDF', 'Email to multiple emails', 'CC settlement auto email' and 'Web-based access from any smart device or computer', over a report set that includes 'PLU / Item reporting', 'Sales by card type', 'Hours and wages' and 'End-of-day reporting' (https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf). Self-serve export of report output therefore exists and is not gated behind support. SHORTFALLS (named): what exports is a REPORT, not the transactional history - no line-item or payment-level extract, no documented API endpoint, and no statement about fees; PDQ's only public API statement is the boilerplate 'value-added integrations via RESTful APIs' (https://pdqpos.com/newsarticles?rid=PR_82724_sycuan), with no published specification. Retrieved 2026-09-18. https://web.archive.org/web/20191218142437/https://www.pdqpos.com/wp-content/uploads/2016/12/Product-Feature-Summary.pdf · retrieved 2026-09-18 adversarially verified

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

commercial-export-customer-and-loyalty

Re-searched 2026-08-30 against what is now known to be the vendor's FULL public surface, which is TWO sites, not one. www.pdqpos.com is a single marketing page plus three legal pages, six press-release and project pages, and the 20-page 2025 Product Catalog PDF. ssipos.com -- a second vendor site, named as "Learn more at SSIpos.com" in PDQ's own 2025 press releases, missed by both the 2026-08-01 and the 2026-08-09 passes because each enumerated www.pdqpos.com only -- is a WordPress marketing page (robots.txt reads "User-Agent: * / Disallow:", i.e. nothing restricted; its Yoast sitemap index lists eight pages) plus seven 2019 flyer images, two of which carry legible screenshots of the running product. There is still no manual, help centre, admin guide, knowledge base or developer portal on either host. Commercially PDQ publishes nothing that binds it. The only contract-shaped documents on either host are a website Terms of Use and a Privacy Policy, both of which govern use of the website and neither of which is a subscription agreement: there is no minimum term, no auto-renewal clause, no cancellation notice period, no early-termination fee, no rate-increase clause, no module unbundling statement, and no merchant-data export or ownership term. Pricing is quote-only across the board -- roughly 25 hardware SKUs are catalogued with zero prices, and no software, processing or implementation figure appears anywhere. So these cells are unknown because the operative agreement is private, which is the ordinary posture for a quote-only enterprise vendor and is itself the finding. This is a determination about PDQ's PUBLICATION, not about the product: the capability may well exist and be undocumented. Recorded at category level rather than per cell, because the gap is the same gap for every cell in the category and pretending otherwise would manufacture specificity the evidence does not have. || 332nd: 332nd: LEAD LOCATED, UNREAD. PDQ's own podcast page (https://www.pdqpos.com/podcasts/, captured in q261 routeB) lists an episode 'The thing about [insert name for heated bread] pos...' described as 'Hidden fees. Surcharges. Exorbitant payment processing rates. Added costs. Holding your data hostage. Not 'enterprise ready'... (7:12 minutes)' - a competitor-comparison episode that may state PDQ's own data-portability position. It is AUDIO ONLY on SoundCloud (api.soundcloud.com/tracks/1492630582); this box has no speech-to-text tool, and fetching the stream needs a SoundCloud client_id taken from its bundle, which the brief bars, so it was not transcribed. Even if transcribed it would be spoken marketing (grade C) and would not show that loyalty balances and gift-card liability are exportable. The V2 ordering client names Paytronix (33 references) and Punchh as the loyalty providers, so loyalty ledgers sit in a third party's system. Retrieved 2026-09-18. || 334th: 334th: NEW SURFACES, do not settle. (1) The 332nd lead (the podcast episode on 'Holding your data hostage') is still unread. PDQ's SoundCloud account user-39287521 resolves to soundcloud:users:238922273, and its public podcast RSS (https://feeds.soundcloud.com/users/soundcloud:users:238922273/sounds.rss) returns 200 but has ZERO <item> entries, so there are no direct audio enclosures. The show is not on Apple Podcasts either: iTunes podcast search for 'PDQ Signature Systems', 'SSI POS' and 'PDQ POS' returns only WIP radio shows and unrelated podcasts. Getting the audio would mean taking a client_id from SoundCloud's JS bundle, which the brief bars, so it was not transcribed. (2) PDQ's own silent slide video '5 Profit Generating Essentials for POS Systems' (https://www.youtube.com/watch?v=P1NW60Uw3Gw, 366 s, uploaded 2018-04-24, presenter Larry Fiel, VP of Marketing; the audio track is digitally silent, max amplitude 0.0, so every prior caption/ASR pass got nothing from it; downloaded at 1080p, 376 scene-change frames extracted and read as contact sheets). Its loyalty slides say only 'Integrated Loyalty Program: Custom branding/theming; Flexibility: tailor to guests/segments; Instant & milestone redemption; Seamless integration with POS' and 'Segmentation: Define, score and dynamically track guests ... real-time dashboard with administration/management/reporting'. There is no export, portability, data-ownership or gift-liability statement. Retrieved 2026-09-18. adversarially verified

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

commercial-post-termination-export-window

332nd: CLAIM: contract or documentation specifies a post-termination data retrieval window (a defined number of days in which the operator can still export) rather than immediate cutoff. VERDICT: no, grade B - no published PDQ contract or document specifies one (the shape merged for microworks-prism no/B, hungerrush no/B, and on this record commercial-no-early-termination-fee no/B). PUBLICATION CENSUS (332nd, re-derived today with curl + browser UA, not inherited): www.pdqpos.com homepage 200 / 110,961 bytes (same byte count as the 326th and 331st copies); its legal set is exactly termsofuse.aspx (200, 81,365 B), privacypolicy.aspx (200, 59,266 B) and smsprivacypolicy.aspx (200, 52,924 B); /termsofsale 404 (1,927 B) against a nonsense-path control /zzz-nope-332 404 (1,928 B), so the merchant 'Terms of Sale' the Terms of Use incorporates by reference is not published; pdqpay.com redirects to a domain-for-sale page (domains.atom.com/lpd/name/PdqPay.com); ssipos.com WP REST pages X-WP-Total 8, posts 5 (unchanged). The retired WordPress pdqpos.com's own payments pages, which no prior pass had opened, were read from Wayback: /payments/ (12 captures 2024-10-14..2025-12-09, latest https://web.archive.org/web/20251209110121id_/https://www.pdqpos.com/payments/) and /pdq-pay/ (2024-07-16): each is ~830 words of qualitative 'PDQ PAY' copy ('Secure, innovative payment processing', 'leading fraud intelligence', 'accepting both traditional and alternative payment types') with no rate, no schedule and no agreement. CONTROLS (tokenised, word-boundary, case-insensitive, over 3,459 text documents in 18 on-disk pdq corpora: .cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, q331/pdq-pos/f and this session's fetches; KNOWN-POSITIVE controls 'surcharg*' 19 docs and 'terminat*' 94 docs fire, so the regexes work): 'post-termination|upon termination|upon expiration|upon cancellation|after termination|after cancellation' 3 documents, all one retired document (below); '<n> days after|following|of termination|cancellation|expiration' 0; 'export your|its|their|all data|data export|return of data' 0 ; 'retriev*' 18 documents, none a PDQ statement - WP REST schema text ('The url to retrieve'), a third-party 404 page, a third-party signature app's App Store copy, and our own pipeline logs/verdict files (POISON). 'terminat*' 94 documents: the live Terms of Use's are website-only ('Monitoring and Enforcement; Termination', 'Terminate or suspend your access to all or part of the Website'); the consumer Online Ordering Terms say 'We may suspend or terminate the Online Ordering Services ... at any time, for any reason' (q261 oo/policies); the privacy policy's is staff discipline; the PCI pages' is 'termination of the right to accept payment cards'. CORROBORATION ONLY (retired document, may not carry the no by itself): the PDQ Delivery Toolkit mobile EULA (Signature Systems, effective 2019-02-25, formerly pdqdt.com/terms, now replaced by the pdqpos homepage) says 'Upon termination: all rights granted to you under this Agreement will also terminate; and you must cease all use of the Application and delete all copies' - immediate cutoff, no window. The merchant Terms of Sale is unpublished (404 vs nonsense control). Retrieved 2026-09-18. https://www.pdqpos.com/termsofuse.aspx · retrieved 2026-09-18 adversarially verified

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

commercial-data-ownership-clause

Neither the Terms of Use nor the Privacy Policy states that the merchant owns its transaction and customer data or constrains vendor use of it. The Privacy Policy only describes sharing data with third parties for hosting, mailing, and support functions. https://www.pdqpos.com/privacypolicy.aspx · retrieved 2026-08-01

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

commercial-source-available-selfhost

Upheld and now cited, with the reasoning re-based. The old rationale called the product fully proprietary commercial software from a privately held vendor; that conclusion is right but the only document on either host that uses the word proprietary is the WEBSITE Terms of Use, which governs the marketing site's own copy and images and settles nothing about the POS. The evidence is instead the vendor's own description of what it sells: this catalogue closes by describing Signature Systems as 'privately held, debt-free, and profitable' whose 'signature product, PDQ POS' is deployed in tens of thousands of operations -- a single-vendor product sold with first-party hardware, on-site installation and in-house repair. Across a 151-document corpus assembled 2026-09-09 (102 archived pdqpos.com pages, the 6 live pages, the 6 live rid/pk detail pages, 13 ssipos.com WordPress documents and 24 vendor PDFs; 733,737 characters, every PDF extracted twice, in layout and in reading order) -- and every zero below held unchanged as the corpus grew from 145 to 176 extractions, `open source`, `source code`, `self-host`, `self hosted`, `github`, `gitlab`, `gpl`, `mit license` and `perpetual license` occur zero times, tokenised and as bare substrings; the two hits for on-premise are about staff working on the premises of a restaurant, not about deployment. The GitHub code search API returns 0 repositories for pdqpos and 0 for ssipos, and none of the 11 results for signature systems pos belongs to this vendor. The claim requires source published under an OSI or source-available licence with a documented self-hosting option; there is no source, no licence and no repository. https://www.pdqpos.com/assets/PDQ_SSI_Product_Catalog_2025.pdf · retrieved 2026-09-09

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

commercial-pci-p2pe-tokenization

CLAIM: the vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A or SAQ P2PE-HW, and names the applicable SAQ. Every conjunct fails on the published estate: no P2PE or encryption vocabulary of any kind, no tokenization, and although SAQ appears twelve times it is always as a consulting service (PCI Self-Awareness Questionnaire (SAQ) Simplification, PCI SAQ Assistance) and never as a named scope level. The brochure's entire cardholder-data content is one bullet, Protection of guest payment cards: in-use, in-transit and at-rest, which is not a statement about P2PE or tokenization. Disclosure that narrows an earlier absolute: on the estate the controls read P2PE 0, point-to-point 0, point 2 point 0, Point-2-Point 0, stem encrypt 0, stem tokeni 0, vault 0, PA-DSS 0, SSF 0, hosted payment 0 and hosted field 0, while SAQ returns 12 and no SAQ level is ever named, and EMV 16, pinpad 2 and swipe 4 show the corpus does carry payment-hardware vocabulary where it applies. Off the estate, however, a 2010-11-16 PRNewswire release with Payment Processing Inc describes PPI's Point-2-Point Cardholder Data Security Program and a Managed Payer Data facility that stores card data on PPI's servers, and calls PDQ POS a validated Payment Application Data Security Standard (PA-DSS) application. A prior note saying tokenization is never mentioned in any PDQ material was therefore too absolute, and the vendor's own spelling is Point-2-Point, which a P2PE control does not match. That artefact does not carry this cell: PA-DSS was retired 2022-10-28, it is not a validated P2PE listing, it names no SAQ, and it is sixteen years old. Scope, stated so the company and the product are not conflated: the vendor itself makes the certification company-scoped. The ssipos.com home page says PCI DSS Level 1 Compliant Service Provider, and Signature Systems' own 2022-12 article advises buyers to select a provider that is PCI DSS compliant as a company. A service-provider compliance status is not a product attestation, and it is not used here to settle any product-scoped conjunct. Estate bounding, re-probed independently rather than inherited: pdqsecurity.com, pdqtek.com and pdqoo.com all 301 to the pdqpos.com marketing home page (pdqsecurity.com and pdqoo.com direct to https://pdqpos.com on both http and https; pdqtek.com via an http://pdqpos.com hop), and a deep path on pdqsecurity.com and on pdqtek.com returns a zero-length 404, so none of the three serves any content of its own; the www. host of each does not resolve, as does a deliberately fabricated control host, so a DNS failure is distinguishable from a redirect. The pdqpos.com Terms of Use names those four pdq domains but does not name ssipos.com, so the Terms are not the estate enumeration. The reachable published estate is two hosts: pdqpos.com, which is one marketing home page, two ProjectDetail pages, four newsarticles pages, three legal pages and the 2025 Product Catalog PDF, with no robots.txt and no sitemap.xml and no /security, /pdqsecurity, /trust or /compliance path; and ssipos.com, a WordPress site whose REST manifest is strictly larger than its sitemap. A fabricated path 404s hard on both hosts, but pdqpos.com also has a soft-200 shape -- https://www.pdqpos.com/newsarticles returns HTTP 200 carrying a Page Not Found body -- so path probes on that host must be read from the body and not the status. Vintage, and the newer-surface hunt that tests it: the brochure is dated 2022-05-19, PCI DSS v4.0.1 was published June 2024 and its future-dated requirements became enforceable 31 March 2025, so this document cannot carry a 4.x statement as a matter of chronology. That argument is only as good as the search for a newer surface, and that search corrects an earlier assertion that the newest security-bearing artefact is the 2025 Product Catalog: Signature Systems publishes press releases through GlobeNewswire and pdqpos.com links only four of them. The newest, 2026-08-19, together with the 2026-03-30 and 2025-02-26 releases, carries the same corporate boilerplate whose only security clause is the versionless phrase full PCI DSS compliance, with no SOC 2, no ISO 27001, no version number, no attestation, no P2PE and no tokenization. ssipos.com has no /trust/, /compliance/ or /security/ page, all three 404, and its media library ends at 2023-11-13. As of 2026-09-15 no 2024-2026 compliance surface exists anywhere on or off the estate. Controls were run tokenised with both word boundaries, and as a left-boundary stem where morphology matters, over 76 document-instruments -- 13 PDFs in two extractions each, the brochure in three, 24 HTML documents held both raw and tag-stripped after HTML-comment removal, and the media census -- which is 37 distinct documents. Positive controls on the same run: the 1937, SSI 845, POS 683, security 260, PCI 136, DSS 51. Poison published: whitespace-squashed substring matching is unusable on its own -- SCA 161 (a substring of casino, Cordish and landscape), ROC 116, RTO 113, RPO 98, v4 91, SLA 53, QSA 20, AOC 11, MFA 6, every one of which tokenises to 0. Two traps tokenisation does not cure: break returns 146 word-boundary hits of which 144 are CSS line-break and word-break declarations in inline styles on the ssipos.com podcasts page, which also carries 144 of the 148 iframe hits; and the bare word token returns 80 hits, every one an ASP.NET __RequestVerificationToken or cookie-consent token in raw pdqpos.com markup and none of them payment tokenization, so only the stem tokeni, which reads 0, is a usable instrument for this vendor. Extraction instrument: the brochure was re-extracted three ways and the invariance reproduced -- pdftotext -layout, pdftotext plain and pdftotext -raw yield an identical token vocabulary with an empty symmetric difference in all six pairwise directions, an identical single-letter-token count of 15 in all three, and five phrase controls present in all three, so on this multi-column document neither the intra-word-space fault nor the adjacent-column-interleave fault fired. The vocabulary size is a reader artefact and is deliberately not published as a figure: one reader counts 322 tokens and another 312 over the same three files; the invariance is the control. Media census and declared residue: ssipos.com wp-json media X-WP-Total is 216, and the per_page=100 HTTP 500 sits on a record and moves with the sort key, so 212 records were recovered by unioning eight orderings. The residue of 4 was then closed by mime filtering rather than by inference: X-WP-Total is 201 for media_type=image (115 png plus 86 jpeg), 2 for video, 13 for media_type=application and 12 for mime_type=application/pdf, and 201+2+13 is exactly 216, so the type census is closed; mime_type=application/pdf&per_page=100 returns all twelve PDFs in a single page with no 500, which makes the twelve-PDF corpus a census rather than a floor. The four unreachable records are therefore two png, one jpeg and one non-PDF application/* file of unknown type, and that single non-PDF file is the declared hole. X-WP-Total for after=2023-12-01 is 0, which bounds the whole library, residue included, to on or before 2023-11-13. https://ssipos.com/wp-content/uploads/2022/05/SSI-Security.pdf · retrieved 2026-09-15 adversarially verified

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

commercial-pci-dss-4-controls

CLAIM: the vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 March 2025, notably MFA for all access to the cardholder data environment including POS and back-office logins, and payment-page script integrity monitoring per Req 6.4.3 and 11.6.1. The brochure's PCI Compliance section is introduced by the sentence We ensure and maintain your PCI DSS compliance: and then lists seven items -- PCI Audit and Gap Analysis; PCI Self-Awareness Questionnaire (SAQ) Simplification; PCI SAQ Assistance; Internal/External Vulnerability Scanning and Assessment; Internal/External Penetration Scanning and Assessment; Policies and Procedures; Training and Education -- which is the vendor's own complete account of what it does for a merchant's PCI compliance, and neither control is in it. MFA 0, multi-factor 0, multifactor 0, two-factor 0, 2FA 0, script integrity 0, 6.4.3 0, 11.6.1 0. The only authentication mechanism named anywhere on the estate is a convenience fingerprint login in the 2025 catalog, which is not MFA for the cardholder data environment. The Our Certifications enumeration, audited rather than accepted: it has no introducing sentence at all. It is a bare heading followed by five bullets -- PCI DSS Level 1 Certified; PCI QIR (Qualified Integrator & Reseller) Certified; Certified PCI Provider: Visa; Certified PCI Provider: MasterCard; Certified Information Systems Security Professional (CISSP) -- and so carries none of the sample markers (including, such as, our certifications include, and more) that would disqualify it as a census. It is nevertheless the stronger of two renderings, not three: the 2025 Product Catalog carries no certification list at all, and the brochure's own front page and the ssipos.com home page both list Sophos Platinum Partner, which Our Certifications omits, while the home-page list closes with the open-ended sentence We are also proud to be a long-standing TRIBAL HUB associate member. The list is therefore not a superset of every credential-shaped claim the vendor makes elsewhere, and it is treated here as strong but not sole evidence. The operative zero is corpus-wide, not list-local: SOC, SOC 2, SOC2, ISO, ISO 27001, 27001, trust center, trust centre, NDA, non-disclosure and the stem attest all return 0 across all 76 document-instruments. Scope, stated so the company and the product are not conflated: the vendor itself makes the certification company-scoped. The ssipos.com home page says PCI DSS Level 1 Compliant Service Provider, and Signature Systems' own 2022-12 article advises buyers to select a provider that is PCI DSS compliant as a company. A service-provider compliance status is not a product attestation, and it is not used here to settle any product-scoped conjunct. Estate bounding, re-probed independently rather than inherited: pdqsecurity.com, pdqtek.com and pdqoo.com all 301 to the pdqpos.com marketing home page (pdqsecurity.com and pdqoo.com direct to https://pdqpos.com on both http and https; pdqtek.com via an http://pdqpos.com hop), and a deep path on pdqsecurity.com and on pdqtek.com returns a zero-length 404, so none of the three serves any content of its own; the www. host of each does not resolve, as does a deliberately fabricated control host, so a DNS failure is distinguishable from a redirect. The pdqpos.com Terms of Use names those four pdq domains but does not name ssipos.com, so the Terms are not the estate enumeration. The reachable published estate is two hosts: pdqpos.com, which is one marketing home page, two ProjectDetail pages, four newsarticles pages, three legal pages and the 2025 Product Catalog PDF, with no robots.txt and no sitemap.xml and no /security, /pdqsecurity, /trust or /compliance path; and ssipos.com, a WordPress site whose REST manifest is strictly larger than its sitemap. A fabricated path 404s hard on both hosts, but pdqpos.com also has a soft-200 shape -- https://www.pdqpos.com/newsarticles returns HTTP 200 carrying a Page Not Found body -- so path probes on that host must be read from the body and not the status. Vintage, and the newer-surface hunt that tests it: the brochure is dated 2022-05-19, PCI DSS v4.0.1 was published June 2024 and its future-dated requirements became enforceable 31 March 2025, so this document cannot carry a 4.x statement as a matter of chronology. That argument is only as good as the search for a newer surface, and that search corrects an earlier assertion that the newest security-bearing artefact is the 2025 Product Catalog: Signature Systems publishes press releases through GlobeNewswire and pdqpos.com links only four of them. The newest, 2026-08-19, together with the 2026-03-30 and 2025-02-26 releases, carries the same corporate boilerplate whose only security clause is the versionless phrase full PCI DSS compliance, with no SOC 2, no ISO 27001, no version number, no attestation, no P2PE and no tokenization. ssipos.com has no /trust/, /compliance/ or /security/ page, all three 404, and its media library ends at 2023-11-13. As of 2026-09-15 no 2024-2026 compliance surface exists anywhere on or off the estate. Controls were run tokenised with both word boundaries, and as a left-boundary stem where morphology matters, over 76 document-instruments -- 13 PDFs in two extractions each, the brochure in three, 24 HTML documents held both raw and tag-stripped after HTML-comment removal, and the media census -- which is 37 distinct documents. Positive controls on the same run: the 1937, SSI 845, POS 683, security 260, PCI 136, DSS 51. Poison published: whitespace-squashed substring matching is unusable on its own -- SCA 161 (a substring of casino, Cordish and landscape), ROC 116, RTO 113, RPO 98, v4 91, SLA 53, QSA 20, AOC 11, MFA 6, every one of which tokenises to 0. Two traps tokenisation does not cure: break returns 146 word-boundary hits of which 144 are CSS line-break and word-break declarations in inline styles on the ssipos.com podcasts page, which also carries 144 of the 148 iframe hits; and the bare word token returns 80 hits, every one an ASP.NET __RequestVerificationToken or cookie-consent token in raw pdqpos.com markup and none of them payment tokenization, so only the stem tokeni, which reads 0, is a usable instrument for this vendor. Extraction instrument: the brochure was re-extracted three ways and the invariance reproduced -- pdftotext -layout, pdftotext plain and pdftotext -raw yield an identical token vocabulary with an empty symmetric difference in all six pairwise directions, an identical single-letter-token count of 15 in all three, and five phrase controls present in all three, so on this multi-column document neither the intra-word-space fault nor the adjacent-column-interleave fault fired. The vocabulary size is a reader artefact and is deliberately not published as a figure: one reader counts 322 tokens and another 312 over the same three files; the invariance is the control. Media census and declared residue: ssipos.com wp-json media X-WP-Total is 216, and the per_page=100 HTTP 500 sits on a record and moves with the sort key, so 212 records were recovered by unioning eight orderings. The residue of 4 was then closed by mime filtering rather than by inference: X-WP-Total is 201 for media_type=image (115 png plus 86 jpeg), 2 for video, 13 for media_type=application and 12 for mime_type=application/pdf, and 201+2+13 is exactly 216, so the type census is closed; mime_type=application/pdf&per_page=100 returns all twelve PDFs in a single page with no 500, which makes the twelve-PDF corpus a census rather than a floor. The four unreachable records are therefore two png, one jpeg and one non-PDF application/* file of unknown type, and that single non-PDF file is the declared hole. X-WP-Total for after=2023-12-01 is 0, which bounds the whole library, residue included, to on or before 2023-11-13. https://ssipos.com/wp-content/uploads/2022/05/SSI-Security.pdf · retrieved 2026-09-15 adversarially verified

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

commercial-soc2-attestation

CLAIM: the vendor states it holds a current SOC 2 Type II or ISO 27001 attestation and will provide the report under NDA via a trust center or on request. The claim's verb is a statement the vendor makes, so a bounded estate can settle it, and it is settled negatively: the vendor makes no such statement anywhere it publishes, and it operates no trust center. The Our Certifications enumeration, audited rather than accepted: it has no introducing sentence at all. It is a bare heading followed by five bullets -- PCI DSS Level 1 Certified; PCI QIR (Qualified Integrator & Reseller) Certified; Certified PCI Provider: Visa; Certified PCI Provider: MasterCard; Certified Information Systems Security Professional (CISSP) -- and so carries none of the sample markers (including, such as, our certifications include, and more) that would disqualify it as a census. It is nevertheless the stronger of two renderings, not three: the 2025 Product Catalog carries no certification list at all, and the brochure's own front page and the ssipos.com home page both list Sophos Platinum Partner, which Our Certifications omits, while the home-page list closes with the open-ended sentence We are also proud to be a long-standing TRIBAL HUB associate member. The list is therefore not a superset of every credential-shaped claim the vendor makes elsewhere, and it is treated here as strong but not sole evidence. The operative zero is corpus-wide, not list-local: SOC, SOC 2, SOC2, ISO, ISO 27001, 27001, trust center, trust centre, NDA, non-disclosure and the stem attest all return 0 across all 76 document-instruments. Scope, stated so the company and the product are not conflated: the vendor itself makes the certification company-scoped. The ssipos.com home page says PCI DSS Level 1 Compliant Service Provider, and Signature Systems' own 2022-12 article advises buyers to select a provider that is PCI DSS compliant as a company. A service-provider compliance status is not a product attestation, and it is not used here to settle any product-scoped conjunct. Estate bounding, re-probed independently rather than inherited: pdqsecurity.com, pdqtek.com and pdqoo.com all 301 to the pdqpos.com marketing home page (pdqsecurity.com and pdqoo.com direct to https://pdqpos.com on both http and https; pdqtek.com via an http://pdqpos.com hop), and a deep path on pdqsecurity.com and on pdqtek.com returns a zero-length 404, so none of the three serves any content of its own; the www. host of each does not resolve, as does a deliberately fabricated control host, so a DNS failure is distinguishable from a redirect. The pdqpos.com Terms of Use names those four pdq domains but does not name ssipos.com, so the Terms are not the estate enumeration. The reachable published estate is two hosts: pdqpos.com, which is one marketing home page, two ProjectDetail pages, four newsarticles pages, three legal pages and the 2025 Product Catalog PDF, with no robots.txt and no sitemap.xml and no /security, /pdqsecurity, /trust or /compliance path; and ssipos.com, a WordPress site whose REST manifest is strictly larger than its sitemap. A fabricated path 404s hard on both hosts, but pdqpos.com also has a soft-200 shape -- https://www.pdqpos.com/newsarticles returns HTTP 200 carrying a Page Not Found body -- so path probes on that host must be read from the body and not the status. Vintage, and the newer-surface hunt that tests it: the brochure is dated 2022-05-19, PCI DSS v4.0.1 was published June 2024 and its future-dated requirements became enforceable 31 March 2025, so this document cannot carry a 4.x statement as a matter of chronology. That argument is only as good as the search for a newer surface, and that search corrects an earlier assertion that the newest security-bearing artefact is the 2025 Product Catalog: Signature Systems publishes press releases through GlobeNewswire and pdqpos.com links only four of them. The newest, 2026-08-19, together with the 2026-03-30 and 2025-02-26 releases, carries the same corporate boilerplate whose only security clause is the versionless phrase full PCI DSS compliance, with no SOC 2, no ISO 27001, no version number, no attestation, no P2PE and no tokenization. ssipos.com has no /trust/, /compliance/ or /security/ page, all three 404, and its media library ends at 2023-11-13. As of 2026-09-15 no 2024-2026 compliance surface exists anywhere on or off the estate. Controls were run tokenised with both word boundaries, and as a left-boundary stem where morphology matters, over 76 document-instruments -- 13 PDFs in two extractions each, the brochure in three, 24 HTML documents held both raw and tag-stripped after HTML-comment removal, and the media census -- which is 37 distinct documents. Positive controls on the same run: the 1937, SSI 845, POS 683, security 260, PCI 136, DSS 51. Poison published: whitespace-squashed substring matching is unusable on its own -- SCA 161 (a substring of casino, Cordish and landscape), ROC 116, RTO 113, RPO 98, v4 91, SLA 53, QSA 20, AOC 11, MFA 6, every one of which tokenises to 0. Two traps tokenisation does not cure: break returns 146 word-boundary hits of which 144 are CSS line-break and word-break declarations in inline styles on the ssipos.com podcasts page, which also carries 144 of the 148 iframe hits; and the bare word token returns 80 hits, every one an ASP.NET __RequestVerificationToken or cookie-consent token in raw pdqpos.com markup and none of them payment tokenization, so only the stem tokeni, which reads 0, is a usable instrument for this vendor. Extraction instrument: the brochure was re-extracted three ways and the invariance reproduced -- pdftotext -layout, pdftotext plain and pdftotext -raw yield an identical token vocabulary with an empty symmetric difference in all six pairwise directions, an identical single-letter-token count of 15 in all three, and five phrase controls present in all three, so on this multi-column document neither the intra-word-space fault nor the adjacent-column-interleave fault fired. The vocabulary size is a reader artefact and is deliberately not published as a figure: one reader counts 322 tokens and another 312 over the same three files; the invariance is the control. Media census and declared residue: ssipos.com wp-json media X-WP-Total is 216, and the per_page=100 HTTP 500 sits on a record and moves with the sort key, so 212 records were recovered by unioning eight orderings. The residue of 4 was then closed by mime filtering rather than by inference: X-WP-Total is 201 for media_type=image (115 png plus 86 jpeg), 2 for video, 13 for media_type=application and 12 for mime_type=application/pdf, and 201+2+13 is exactly 216, so the type census is closed; mime_type=application/pdf&per_page=100 returns all twelve PDFs in a single page with no 500, which makes the twelve-PDF corpus a census rather than a floor. The four unreachable records are therefore two png, one jpeg and one non-PDF application/* file of unknown type, and that single non-PDF file is the declared hole. X-WP-Total for after=2023-12-01 is 0, which bounds the whole library, residue included, to on or before 2023-11-13. https://ssipos.com/wp-content/uploads/2022/05/SSI-Security.pdf · retrieved 2026-09-15 adversarially verified

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

commercial-privacy-dsar-tooling

The Privacy Policy provides only a postal-mail California 'Shine the Light' request channel to the Legal Department, once per calendar year. No in-app DSAR tooling, no GDPR procedure, and no published DPA. || 331st: MERGE HOLD (proposed no/B, held unknown): 331st merge: the published-DPA conjunct fails on a publication census, but the claim's first conjunct is IN-APP tooling (locate/export/delete a guest's records) in PDQ's back office, which is unpublished and unseen; if it exists the verdict is partial, not no. Same shape as the pdq allergen hold. PROPOSAL AS WRITTEN: 331st: CLAIM (conjunctive): in-app tooling for CCPA/CPRA and GDPR data-subject requests - locating, exporting and deleting one guest's records - PLUS a published DPA the operator can execute. VERDICT: no, because the second conjunct is a publication test and it fails on a bounded census; the in-app half is not assessed and the verdict does not rest on it. PUBLICATION CENSUS (331st, re-derived today, not inherited): (1) www.pdqpos.com - homepage 110,961 bytes and 29 distinct hrefs, byte-identical to the 326th copy; its legal set is exactly three documents (termsofuse.aspx, privacypolicy.aspx, smsprivacypolicy.aspx), whose stripped text is identical to the 328th copies; no robots.txt and no sitemap (both 404); pdqtek.com, pdqsecurity.com and pdqoo.com redirect to pdqpos.com and pdqdt.com serves the same 110,961-byte page. (2) ssipos.com - /wp-json/wp/v2/types lists only core types (post, page, attachment, menu/FSE internals, wpb_gutenberg_param), so there is no custom legal/kb type to page; pages X-WP-Total 8, posts 5, media 216 (213 paged by offset; the non-image files are 12 PDFs - press releases, awards, two whitepapers, the SSI Security brochure - one 2021 price-quote .xlsx and two stock mp4s). (3) Hosts: the crt.sh name set (324th/327th) has no status, docs, developer or partner host; status.pdqpos.com, status.ssipos.com and status.mypdqpos.com do not resolve; certspotter was rate-limited today (not run). (4) Controls were run tokenised, word-boundary, over 3,429 text documents in 17 on-disk corpora (.cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, and this session's fetches). CONTROLS: 'data processing agreement/addendum' 0 documents; 'DPA' 6 hits, all binary-stream collisions inside one PDF's compressed bytes (POISON); 'data subject' 0; 'GDPR' 232 documents, every one the cookie banner string 'This cookie is set by GDPR Cookie Consent plugin' on the old WordPress pdqpos.com (POISON - a website plugin, not a privacy programme); 'CCPA/CPRA' 11 documents, all third-party (Chowly footers). The live Privacy Policy (1,945 words, identical to the 328th copy) has 0 'CCPA', 0 'GDPR', 0 'delete/deletion', 0 'access request' and 0 'processor', and offers only the California 'Shine the Light' postal request to the Legal Department once per calendar year. The consumer ordering surface's Online Ordering Terms (q261 oo/policies, 1,688 words) have 0 'delete', 0 'request', 0 'California', 0 'GDPR'. No DPA is published on any vendor host. Retrieved 2026-09-18. || 333rd: 333rd: NEW (consumer side only; does not reach the held in-app operator conjunct). The V2 guest web-ordering client (Next.js bundle on disk at .cache/q331/pdq-pos/c: app.js + 52 chunks, 0 loader misses) has no account-deletion, data-download or privacy-request flow; its only privacy text is an in-app blurb: 'We collect your name, email, phone number, and order data to process your order and improve our services. Your payment details are handled securely by third-party processors. We do not sell your information.' Its only 'delete' strings are cart-item confirmations ('Are you sure you want to delete this item?'). This is the GUEST app, not PDQ's operator back office, so it does not bound the claim's operator tooling; the live Privacy Policy is unchanged today (59,266 B). Retrieved 2026-09-18. adversarially verified

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

commercial-wcag-kiosk-accessibility

331st: CLAIM: vendor publishes a VPAT/ACR claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual kiosk mode. VERDICT: no - this is a publication claim and the publication census is bounded. PUBLICATION CENSUS (331st, re-derived today, not inherited): (1) www.pdqpos.com - homepage 110,961 bytes and 29 distinct hrefs, byte-identical to the 326th copy; its legal set is exactly three documents (termsofuse.aspx, privacypolicy.aspx, smsprivacypolicy.aspx), whose stripped text is identical to the 328th copies; no robots.txt and no sitemap (both 404); pdqtek.com, pdqsecurity.com and pdqoo.com redirect to pdqpos.com and pdqdt.com serves the same 110,961-byte page. (2) ssipos.com - /wp-json/wp/v2/types lists only core types (post, page, attachment, menu/FSE internals, wpb_gutenberg_param), so there is no custom legal/kb type to page; pages X-WP-Total 8, posts 5, media 216 (213 paged by offset; the non-image files are 12 PDFs - press releases, awards, two whitepapers, the SSI Security brochure - one 2021 price-quote .xlsx and two stock mp4s). (3) Hosts: the crt.sh name set (324th/327th) has no status, docs, developer or partner host; status.pdqpos.com, status.ssipos.com and status.mypdqpos.com do not resolve; certspotter was rate-limited today (not run). (4) Controls were run tokenised, word-boundary, over 3,429 text documents in 17 on-disk corpora (.cache/pdq-pos, q261-q312 pdq dirs, q324-q328 pdq-pos and pdq-pos-apps, and this session's fetches). CONTROLS: 'VPAT' 0, 'WCAG' 0, 'Section 508' 0, 'conformance report' 0, 'screen reader(s)' 0 documents (the only hits were my own control file). 'ADA' 9 documents: 8 are binary-stream collisions inside the 2025 catalogue PDF bytes and 1 is a DATACAP page (third party) - POISON, none is a PDQ statement. 'accessibility' 62 documents, and every PDQ-authored one is the privacy policy's 'disability data ... for diversity or accessibility purposes' (an HR data category) or the App Store's own line on PDQ's app, 'The developer has not yet indicated which accessibility features this app supports'; the rest are footers of third parties (DoorDash, Olo, Menufy, Checkmate). ssipos.com's WP search returns 0 results for 'accessibility', 'vpat' and 'wcag', and /accessibility is 404 on both vendor hosts. The consumer web-ordering surface's own Online Ordering Terms (q261 oo/policies, 1,688 words, the same text served on bigdaddypizza/passariellos/wallyspizza ordering sites) has 0 'accessib', 0 'ADA', 0 'WCAG'. The kiosk surface is real (four kiosk models in the 2025 catalogue), so the claim applies and is unmet. Retrieved 2026-09-18. https://pdqpos.com/ · retrieved 2026-09-18 adversarially verified

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

commercial-dual-pricing-compliant

331st: the cell's rationale said only that pizzeria marketing 'hints at' a surcharge program; the vendor says it outright in a document the 328th found for a DIFFERENT cell (digital-surcharge-transparency, merged partial/C) and nobody checked against this one. CLAIM: POS supports card-network-compliant dual pricing / cash discount or surcharging, with automatic exclusion of debit and prepaid cards from any surcharge, and the required receipt and menu-board disclosure. VERDICT: partial, grade C. EVIDENCE, verbatim from the vendor's 3-page 'PDQ DELIVERY TOOLKIT' leaflet ((c)2020 Signature Systems, Inc.), section 'Convenience Fee/CC Surcharge': 'Since so much credit card traffic is now driven to online rather than to call-in orders, we also support the ability to add a credit card surcharge to the order. ... We can also add a surcharge fee to the POS system, if you want to offset some of those costs as well.' (https://web.archive.org/web/20230127020820id_/https://pdqdt.com/wp-content/uploads/2020/04/Delivery-Toolkit-LF.pdf). So a card SURCHARGE exists at the POS in the vendor's own words - the claim's first conjunct. SHORTFALL (named): nothing on debit/prepaid exclusion, nothing on receipt or menu-board disclosure, nothing on cash-discount/dual-price display; 'cash discount', 'dual pricing' and 'non-cash adjustment' are 0 vendor documents across 3,429 on-disk documents (the 2 hits are third-party pages), and 'debit' never appears beside 'surcharge' in a PDQ document. Grade C: a product leaflet, 2020, on a host that no longer serves it (retired document: positive at most partial, which is what is proposed). POISON NAMED: 'Surcharge: $2.00' on parmapizzaandgrill checkout pages (q312) is an ITEM surcharge on a stuffed-crust burger line, not a card surcharge, and was not used. Retrieved 2026-09-18. https://web.archive.org/web/20230127020820id_/https://pdqdt.com/wp-content/uploads/2020/04/Delivery-Toolkit-LF.pdf · retrieved 2026-09-18 adversarially verified