Vendors / Open source & self-hostable
SambaPOS
SambaPOS (Ozgu Yazilim)
dossier maintenance
- Claims in scope
- 278
- Scored
- 278
- Assessed
- 276
- Unknown
- 2
- Not applicable
- 36
- Values challenged
- 90
Identity
- Owner
- Ozgu Yazilim (Turkey). SourceForge's vendor listing gives the company location as Turkey; sambapos.com publishes no corporate/ownership page I could retrieve.
- Parent
- Ozgu Yazilim
- Founded
- unknown — the SambaPOS-3 GitHub repository was created 2011-11-06 (github.com/emreeren/SambaPOS-3), the earliest hard date I can source; no company founding date is published
- Scale
- unknown — no customer count, location count, or revenue figure is published anywhere. Only proxy signals: the abandoned open-source SambaPOS-3 repo has 542 stars / 429 forks, and forum.sambapos.com is active with threads dated June–July 2026.
- Who it is for
- Independent single-site and small-group restaurants, cafes, bars and takeaways running Windows PCs, who want to build their own workflows with the rules/actions/scripting engine. Reseller-led and heavily weighted to Turkey (Yemeksepeti, Getir, Trendyol Yemek, Migros Yemek, e-Invoice integrations) and the UK (UK Post Code Lookup, PaymentSense/Dojo). Neptune targets multi-branch chains but is quote-only.
- Site
- https://github.com/emreeren/SambaPOS-3
Pricing
transparency: published · unit: mixed · processor lock-in: no
- Software
- SambaPOS V5 Pro: $339 one-time payment, described as a 'Lifetime License', including multiple terminal usage, table service, delivery, custom reports and inventory/cost tracking (https://sambapos.com/product/sambapos-v5-pro/). Add-ons are separately priced annual SKUs: KDS $69 per device per year (https://sambapos.com/product/sambapos-kds/); Mobile Client $67 per device per year (https://sambapos.com/product/sambapos-mobile-client/); GO Tablet $67/year (https://sambapos.com/product/sambapos-go-tablet/); GO Kiosk $337/year (https://sambapos.com/product/sambapos-go-kiosk/); Jetrik QR Menu $99/year (https://sambapos.com/product/jetrik-qr-menu/). All add-ons require a valid V5 license. SambaPOS Neptune (cloud multi-branch management) is labelled an Enterprise Product and is quote-only. Note: SourceForge's third-party listing says 'starting price $500 one-time', contradicting the vendor's own $339 page — use the vendor figure.
- Card processing
- n/a — SambaPOS does not process payments and publishes no card rates.
- Contract
- Core POS is a perpetual one-time license, not a term subscription. Add-on modules bill annually, per device or per site. No published minimum term, auto-renewal term or cancellation notice window. NOTE: an earlier revision of this file said no public terms of service could be located; that was wrong and the record's own claims contradicted it — https://sambapos.com/terms-of-use/ is cited twelve times in claims.jsonl. It is published in two languages that name DIFFERENT legal entities: the English text is made by 'SambaPOS Inc.' and the Turkish https://sambapos.com/tr/satis-ve-kullanim-kosullari/ by 'SAMBAPOS YAZILIM A.Ş.'. Both are dated 2022 and no later revision is published. What the contract does NOT contain is a term, a renewal clause or a notice period — §3.14 only warns that licences are variously lifetime, monthly, annual or device-based and that expired licences 'may be temporarily disabled or permanently revoked'.
- Early termination
- None as a fee, but termination is not refundable. Terms of Use §3.18: once the user has decided to pay and licensing is complete, 'cancellation of the licence of their products and, if payment has been made, a refund of payment, is not possible' (Turkish text: 'ödeme iadesi mümkün değildir'). Trial periods before licensing are offered instead. There is therefore no early-termination charge on the perpetual core licence — the exposure is the forfeited prepayment on the annual add-on SKUs.
API posture
public API: none
- Cost to integrate
- unknown — no published partner program terms, certification cost, or revenue share.
- Webhooks
- No webhook SUBSCRIPTION API — there is no endpoint registration, no event catalogue, no signing secret and no delivery/retry dashboard. But the earlier reading that no outbound mechanism is documented at all was wrong. KB 4.35 configures a printer of type 'Custom Printer / URL Printer' whose fields are 'URL Format', 'Data Format', 'Token Char: @', 'Live Mode', 'Retry Count' and 'Retry Minutes' (https://kb.sambapos.com/en/4-35-how-to-apply-sms-sending-implementation-on-sambapos/). That is a general outbound HTTP call with templated tokens and a retry policy, fired from the Rules engine on any event the engine exposes — the vendor's documented pattern for pushing an SMS to a third party. So outbound integration is operator-built and event-triggered rather than absent; it is just not a managed webhook product. A 'Messaging Server' separately provides communication between SambaPOS products on the local network and is internal plumbing. The abandoned V3 source tree contains a Samba.ApiServer project (https://github.com/emreeren/SambaPOS-3) whose last master commit is 2014-02-08; it is not evidence of anything in V5.
- Data export on exit
- Structurally excellent, and the strongest thing about this vendor's data posture: SambaPOS V5 runs on a Microsoft SQL Server instance the operator owns and hosts (kb.sambapos.com documents database setup, multi-computer deployment, and backup/restore). The merchant has direct SQL access to every order, line, payment, customer and inventory record, with no vendor gatekeeper, no fee, and no post-termination cutoff. This is a consequence of the on-premise architecture, not a documented contractual right.
- Notes
- CORRECTION (209th): the earlier reading that there is 'no public REST or GraphQL reference' was wrong in substance. SambaPOS V5 ships a FIRST-PARTY GraphQL SERVER and the knowledgebase documents it as an installation prerequisite in both languages — 'GraphQL – make sure you can access to http://your_server_name_or_ip_or_localhost:9000' (https://kb.sambapos.com/en/4-19-how-to-select-portions-and-order-tags-by-popup/, also 4-100 and 8-7). It is authenticated: 2.2.10.b states that a user's Password field, which is DISTINCT from the POS PIN, exists solely for 'connections to be made to the SambaPOS program over GraphQL (for example Android Client users, handheld terminals)' (https://kb.sambapos.com/en/2-2-10-b-how-to-create-edit-user/), and the GO Tablet setup screen has a field literally labelled 'GraphQL'. There is also a third-party APPLICATION REGISTRY in front of it: KB 8.19 section 3.3 walks through registering an application with the fields 'Authentication Type: User Name & Password', 'Authorization Type: All Functions', 'Lifetime: 365', 'Allowed Origin: *' and a Permissions section, then notes 'After creating kds application you need to restart SambaPOS Messaging Server' (https://kb.sambapos.com/en/8-19-how-to-configure-sambapos-kds-v2/). A token lifetime, a CORS origin and per-application permissions are an authorization model, and SambaPOS's own KDS V2 is just one registered client of it. So the endpoint, its port, its transport, its auth model and its app-registration model are all published. What is NOT published is a SCHEMA REFERENCE: no type/query/mutation listing, no rate limits, no versioning or deprecation policy, no sandbox, and the forum threads 'graphql-api-v5-5' and 'what-happened-to-graphql-guide' record users asking where the guide went. It is also LAN-local by design, not an internet-facing platform API — which is why public_api stays 'none' rather than moving. Beyond it I found only integration-specific API-key articles (Google Maps and TomTom keys for the Nav Core module, GloriaFood 'Online Order API Activation', SMS gateway URL configuration, Worldline). There is no OAuth flow, no rate-limit table, no developer sandbox and no changelog/deprecation policy. Extensibility is otherwise delivered through the in-product automation engine — Actions, Rules, Automation Commands, Triggers and JScript Scripts (kb.sambapos.com Customization section, 69 articles) — plus direct SQL against the merchant's own database. That is real and deep, but it is local scripting against a LAN endpoint, not a platform API.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
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
Entity Screens in Layout view mode: place table entities over a JPG/PNG floor-plan background with widgets. Section/server assignment not documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Achievable but not shipped. Emre Eren (SambaPOS founder, staff-flagged, 2018-09-02) on the ticket-grouping mechanism: 'if you want to track seat numbers or customer name grouping on payment screen by seat number will be really useful. You can split payments by seat number for example.' The Display Payment Screen action takes a 'Grouping Order State' parameter, so items tagged with a seat-number order state group on the payment screen and each group can be settled separately without re-keying. Shortfall: there is no seat field anywhere in the product - the seat number must be built as an order state plus automation commands per seat (community V5 Tutorial 'Split bill, Take Order and Pay by Seat'), and no article in the 286-article English KB documents seat tagging. https://forum.sambapos.com/t/shivans-tutorial-2-order-courses-order-grouping/18157 · retrieved 2026-08-08
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
Coursing exists as grouping, not as hold-and-fire. A 'Course' order state can be set per item with a Change Course button, items regroup under Entree/Mains/Desserts on the ticket and on the kitchen print via '[ORDERS GROUP|ORDER STATE:Course:Entree,Mains,Desserts]', and the grouping display was shipped as the Update Ticket Grouping feature in SambaPOS V5 5.2.12 (thread confirmed in-line by Emre Eren, staff). KB 2.4.16 'Printing Kitchen Messages by Ticket Tag (Mains-Starters Away)' fires a printed away message by ticket tag. Shortfall: no hold state that withholds orders from the printer or KDS and no fire-next-course action that releases only one course - 2.4.16 prints a message, not the held items, and the whole arrangement is hand-built from actions and rules. A 2014 request thread (forum t/2774, 'Hold and Fire for Items') was answered with 'Anything is possible we just need to design it', i.e. build it yourself. https://forum.sambapos.com/t/shivans-tutorial-2-order-courses-order-grouping/18157 · retrieved 2026-08-08
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
Check splitting and merging are marketed; by-seat, even-N-way and post-partial-payment merge behaviour undocumented. https://sourceforge.net/software/product/SambaPOS/ · retrieved 2026-08-01
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
Asked directly whether the US card integration supports bar tabs with 'a $50 pre auth and then at end of tab it puts final amount and closes sale', Jesse Parker of SambaPOS (posting as the vendor, signs off 'email me jesse@sambapos.com') answered 2020-01-22: 'We do not not have that feature yet. However we may add it in the future. But we can do tabs with SambaPOS it just won't have a pre-authorization.' Next day: 'We use pre auth for tip adjust but tabs is a different thing. We would have to build something on Sambapos side for it... no we have not built it into Sambapos yet', and 'I will add this to the Redmine as a feature request... We have a tight roadmap so I wouldn't expect it to happen soon.' No incremental re-auth or stale-tab auto-close appears anywhere in the 286-article English KB or the 327-article Turkish KB, and the eight payment-processor integration articles (PaymentSense 6.1/6.2, Dojo 6.14, OpenEdge 6.5, International Bancard 6.12, Global Payments 6.20, Worldline 6.26, Quest 6.31, Dejavoo 6.34, latest revised 2024-11) document sale/refund/tip-adjust only. Evidence of absence is a 2020 vendor statement; nothing since contradicts it. https://forum.sambapos.com/t/us-credit-card-intergration-bar-tabs/21455 · retrieved 2026-08-08
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
Transfer between tables and devices yes, audit and server transfer no. KB 5.1.3.a: open the ticket, press Change Table, pick the destination table; 5.1.3.c merges tickets and tables the same way. All terminals share one MSSQL database through the Messaging Server (2.1.6, 2.2.2), so an open check is reachable from any terminal without a transfer step. Shortfall: no built-in transfer audit log naming both employees - KB 2.4.4 'How to Record Waiter that Prints Bill or Receives Payment into Logs' shows the operator building the log himself from an Add Ticket Log action (Category/Log text) plus a Display Ticket Log action and rules, which is what logging exists for at all; and no change-of-server / reassign-waiter action appears in the User Manual (54 English articles) or Customization (67). https://kb.sambapos.com/en/5-1-3-a-how-to-move-table/ · retrieved 2026-08-08
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
Partial stands, but the note understates the defect: the Mobile Client re-validates its licence over the internet every time an entity screen is opened (vendor developer's own words), so the handheld is the least offline-tolerant part of an architecture sold on offline resilience. $67/device/year verified on the product page; feature list is 'Take order with tags, Add order note, Track table status, Get payment' with no card-acceptance detail. https://forum.sambapos.com/t/major-issue-with-online-license-check-systems-offline/19437 · retrieved 2026-08-01 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
Vendor states the system 'doesn't rely on internet', backed by on-premise SQL Server. No published matrix of what degrades offline. https://sambapos.com/ · retrieved 2026-08-01
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
GO Tablet is table-based self-service ordering forwarding to kitchen screen/printer; whether items land on the same open server check is not documented. https://sambapos.com/sambapos-go-tablet/ · retrieved 2026-08-01
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
GO Kiosk is first-party ($337/yr) and syncs the SambaPOS menu; no ADA/WCAG conformance published. https://sambapos.com/sambapos-go-kiosk/ · 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
"Multiple lanes are dedicated to mobile orders and delivery, while at least one lane is dedicated to the regular drive thru" — lane differentiation is claimed, but order-point/pay-window/pickup-window separation, sequencing, and pull-forward/parking assignment are not described anywhere on the page or in the KB. https://sambapos.com/drive-thru-pos/ · retrieved 2026-08-04
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
order-capture-drive-thru-timers
English KB 9.1.3 Custom Reporting Tags (modified 2021-01-29) is the actual closed list - 'These are the supported DETAILS tags.' - and its ORDER DETAILS block exposes per-order, per-named-state timestamps: 'OSD.<state name> Order State Date', 'OST.<state name> Order State Time', alongside 'OSV.<state name> Order State Value' and 'OSU.<state name> Order State User'. The same article ships '{REPORT ENTITY STATE TOTAL DURATION:<expression>}' plus TOTAL HOURS/MINUTES/SECONDS tags, and arithmetic across fields: 'When you use fields in calculations you need to enclose them in square brackets.' English KB 4.3 lists Update Order State and Log Entity State among shipped Actions and Order State Updated among shipped Rule events. Segment timing tied to an individual order is therefore capturable and reportable from documented, shipped primitives. What does not exist anywhere in either language tree is any drive-thru concept: no lane, no window, no greet, no preconfigured speed-of-service report, and the only drive-thru documents in 958 corpus files are the English and Turkish marketing pages, which promise reduced waiting without naming a captured metric. Not shipped, but not foreclosed - partial with the mechanism named. https://kb.sambapos.com/en/9-1-3-custom-reporting-tags/ · retrieved 2026-09-05 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
The vendor English integrations index at sambapos.com/integrations/ (modified 2023-10-11) is the whole outward-facing partner story - 'SambaPOS assist to maximize the power of your POS with integration solutions' - and under a heading inviting the reader to discover what POS integration their restaurant needs it names exactly three: Global Payments Integrated, GloriaFood Integration and RestaJet Integration. No voice partner, no developer or partner programme, no way to apply to one. Corroborated by a corpus-wide zero across all 958 documents in BOTH languages for voice ordering, speech recognition, sesli siparis, yapay zeka, artificial intelligence, ChatGPT and machine learning; every English voice token is either the word invoice or the KDS Notification Voice chime. On the second limb of the claim I tested the analyst own corollary and it does not rescue anything: English KB 8.19 section 3.3 does document an Applications registry whose fields are an identifier, an authentication type of user name and password, an authorization type of all functions, a lifetime of 365 and an allowed origin of asterisk, sitting behind the port-9000 Message Server, but that is a local app-registration surface with no published schema and no partner onboarding - an API, not a documented API partner program addressed to voice AI. https://sambapos.com/integrations/ · retrieved 2026-09-05 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
Turkish KB 6.19 Go Order Getir Yemek Entegrasyonu section 6.1 walks the entire channel settings page field by field: 'Getir Aktif', 'Otomatik Onay', a play-sound box, discount type, menu, entity type, ticket type, default category, and an initial ticket state selector. Its siblings 6.16 Yemek Sepeti, 6.17 Trendyol and 6.18 Migros carry the identical list, and the ticket type it wires to is 'Adisyon Tipi: Paket Servis'. Neither limb of the claim appears on any of them: no per-channel capacity, no time slot, and no promised or quoted prep time that could be extended. Corpus-wide zero in both languages for throttl, capacity and time slot, and for kapasite and zaman dilimi - the single Turkish zaman dilimi hit is GO Kiosk V3 8.24, a scheduled product on/off window, not a capacity brake. The only shipped volume brakes are item-level: English 4.55 daily item sales limit and 4.50 zero-stock prevention. Disclosed against myself: the English GoOrder USA channels (DoorDash, Uber Eats, Grubhub) have no KB article at all, and English 6.29 describes its own settings loosely, as Auto Accept and Play Sound and so on, rather than exhaustively - so the closed enumeration I rely on is the Turkish aggregator one. All five are the same Go Order module, so I accept it. https://kb.sambapos.com/6-19-go-order-getir-yemek-entegrasyonu/ · retrieved 2026-09-05 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
The GloriaFood leg is withdrawn: gloriafood.com now states GloriaFood 'has been discontinued and is no longer accepting new signups' (retrieved 2026-08-09) and KB 6.3 and 6.29 are headed 'This product is no longer supported', so it is neither the only nor an available future-order channel. Jetrik, the Go Order channel SambaPOS staff recommend instead, does document scheduled ordering: KB 6.25 s3.3.5 'Scheduled Orders Screen - If you offer your customers the ability to place Planned Orders, you can make the relevant settings here.' Shortfall, and it is most of the claim: the setting sits on the Jetrik panel rather than in SambaPOS; 'Planned Orders' occurs exactly once in the 613-article KB dump, with no per-channel lead time and no computed fire time stated there or in the release notes through 5.7.28; and the only documented POS-side behaviour for a future-dated order is immediate print on acceptance (vendor forum t/22215, markjw and Farrukh_Shah, 2020-08-11). Orders fire on receipt, not at a computed fire time. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-09 adversarially verified
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
No catering-specific flow exists, but the mechanics the claim asks for ship in the Reservation module, which the KB does not document at all (its only mention of a 'Reservation Module' across 613 records is in passing in the RestaJet integration article). 5.2.14 (2018-10-02) lists 'Reservation added', and emre [STAFF], SambaPOS's founder, describes the mechanism in the 5.2.13 beta thread: a Reservation screen with check-ins and no-show formatting that is separate from the POS ticket queue; 'Creating Pre-Order Tickets ... These tickets used to keep a record of orders and deposit payments'; 'Adding Deposit to a Pre-Order Ticket ... %50 deposit calculates by default. We can change it'; and 'when we click on table number reservation ticket converts to real ticket, orders moves to new ticket and deposit amount added as a discount', which leaves the balance due on the real ticket. Shortfall: this is a table-booking module, not a catering flow - reservations bind to a table and a check-in, there is no event or off-premise delivery schedule, no quote document and no separate catering menu, and the deposit posts as cash with the payment type not selectable ('Payment type for deposit is Cash for now'). In the same thread SambaPOS's Jesse asks to 'build a version for catering reservations ... a way to schedule and plan catering gigs with custom catering menu', which has not shipped in any release through 5.7.28 (2026-07-02). https://forum.sambapos.com/t/sambapos-5-2-13-beta-release/18155/149 · retrieved 2026-08-09 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
CLAIM: Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash). VERDICT: unknown upheld, reason sharpened. NEW SURFACES: (1) forum.sambapos.com/t/26807 (5.5.8 release, 2023-03-09, staff VehbiEmiroglu): "Go Order USA Integration added (Uber Eats, Doordash, Grubhub, Gloriafood)"; Jesse 2023-03-11: "It will allow you to integrate doordash grubhub Uber and gmoriafood directly into sambapos and remove tablets. It works with auto accept or without allowing you to accept orders directly through sambapos." Nothing about outbound ready status. (2) The shipped 5.7.30 binary. Installer: https://sambapos.com/download/sambapos_setups/SambaSetup5730_09092.exe (linked anonymously from https://sambapos.com/download-sambapos/, 211,275,504 bytes, Authenticode-signed Advanced Installer; payload 49EB0A4\FILES.7z at offset 0x382200, first 0x200 bytes XOR 0xFF, 520 entries; 73 Samba*.dll/.exe extracted and scanned in raw bytes and as UTF-16LE). GoOrder USA is implemented in Samba.GoOrder.Kitchenhub.dll, i.e. through the KitchenHub aggregator. Its plaintext metadata names only inbound members (InitializeWebsocketConnection, SubscribeGraphQL, CreateSubscriptionStream, GetGoOrderDetail, CreateTicket, AddOrder, CloseTicket, SendQueryAsync); no update/status/ready member (only set_UseWebSocketForQueriesAndMutations, a GraphQL client option). In Samba.Presentation.ClientLibrary.dll the Getir, Jetrik, Migros and Trendyol explorers each carry <Provider>StatusCommand/<Provider>StatusLabel (Trendyol also updateIntegrationStatus), while GoOrderUSAExplorerViewModel carries only DoorDash/GrubHub/UberEats/GloriaFood filter buttons (DoorDashButtonCommand, IsDoorDashButtonEnabled) and no status command. BOUND: suggestive of no outbound status for US marketplaces, but NOT a census: the Kitchenhub assembly's user-string heap is encrypted (GetManifestResourceStream + BlockCopy decryptor, SuppressIldasm), so no no is published. Retrieved 2026-09-16. || 322nd: NEW SURFACES (322nd): crt.sh %.sambapos.com (2026-09-17) listed 53 names; live anonymous hosts probed: apidoc.sambapos.com (Wiki.js, 302 /login, /swagger 403 - gated), mcdemo.sambapos.com (GraphiQL shell; POST /api/graphql 401 - no introspection), md.sambapos.com (Nuxt app behind GitHub login), local.sambapos.com (Weblate 4.12.1, anonymous API lists 0 projects), admin.ticket.sambapos.com (helpdesk SPA), defter.sambapos.com (Cloudflare Access), getircloud.sambapos.com and metrik.sambapos.com (below); doc/koffice/b2b/usa-support/helpdesk/wl/v4/neptune do not answer. getircloud.sambapos.com ("SambaPOS Getir", CRA app; bundle Last-Modified 2021-09-24, so an OLD Getir-only panel, likely predating KB 6.19 GoOrder Getir): /asset-manifest.json lists main + vendor chunk 2 and their public source maps; main.3176f8f6.chunk.js.map holds all 17 app sources (screens/Order.js, OrderDetail.js, Menuchain.js, Settings.js, Login.js, components/*), chunk 2 map (485 sources) is library code only, no lazy chunks. Every outbound call in the app source: getirs2.sambapos.com /auth, /auth/login, /customers/state, /v1, /v1/manuelAdmit ("Sipariş Onaylandı"), /food-orders/<id>/cancel-options, /food-orders/<id>/cancel, /cancelReason, /restaurants/status/open|close, /restaurants/courier/enable|disable, /restaurants/autoConfirm/enable|disable, /sambaMenu, /matchMenu, /restaurants/menu. Order states are only DISPLAYED: 400 "Onay Bekliyor", 500 "Hazırlanıyor", 600 "Müşteriye Gidiyor", 700 "Teslim Edildi", 800 "Reddedildi"; no call moves an order to ready/handover (tokens prepare 3, all the CSS class label-prepare - POISON; ready/handover 0). So that Getir panel accepts/cancels and toggles the restaurant but pushes no ready signal. WHY STILL unknown: it is one old app for one Turkish marketplace, not the current GoOrder assemblies (Samba.GoOrder.Getir/Migros/Trendyol/Yemeksepeti.dll strings re-scanned: Migros carries a DeliverStatus member, Jetrik an "Update GoOrderOrders set ... Status" SQL and restaurants/status/open|close; string heaps otherwise obfuscated) nor the KitchenHub path for US marketplaces; not a census, so no 'no'. Retrieved 2026-09-17. || 330th: 330th, NEW SURFACE, still short of a verdict. The five GO Order integration documents are now held as a SETTINGS ENUMERATION, including the screenshots read as images at full resolution (strip the -1024xNNN suffix from the KB upload URL). GO Order module panel (SambaPOS 5.7.14, https://kb.sambapos.com/wp-content/uploads/2024/12/GloriaFood-Go-Order-61.jpg): Menu, Entity Type, Courier Entity Type, Ticket Type, Department, Default Category, Customer Mapping, Payment Methods, Default Portion, States, Delivery State Value, At Delivery State Value, Pending State Value, New Order Pop-Up, Use Default OTG; per-provider: Auto. Accept, Play Sound, Alternative Mapping, Order Method Tag Name, Tag for Pickup, Tag for Delivery, Default Delivery Time, DeliveryFee, Discount Type, Payment Type; Restaurant Information: Reference Id, Restaurant Key, Master Key, RestaurantName, Default Delivery Time. The Turkish twins (KB 6.16-6.19) list the same fields, and their "Durum ve Durum Degeri" is explicitly the LOCAL first state of the ticket ("Olusacak olan adisyon belgesinin ilk durumu burada belirlenir. Ornegin Paket: Bekliyor gibi"). The GO Order sale screen (https://kb.sambapos.com/wp-content/uploads/2024/12/GloriaFood-Go-Order-59.jpg) has two columns, New Orders and Orders In Courier, and the actions Delivery To Customer, Cancel, Display Ticket, Print, Close plus tenders - no ready/handover push. Forum full-text search is near-empty on the subject: search.json q=doordash returns ONE topic in the whole forum (/t/26807, the 5.5.8 release), q=kitchenhub two topics, both SQL Server threads. WHY STILL unknown: the claim is not US-only, and the Turkish explorers in the 5.7.30 binary do carry <Provider>StatusCommand members (Getir, Jetrik, Migros, Trendyol) that no document explains, with encrypted string heaps; a documentation census cannot tell whether that button pushes a marketplace status. crt.sh holds no goorder/kitchenhub host under sambapos.com, and kitchenhub.tech does not resolve, so the US aggregator's own surface is not reachable either. Retrieved 2026-09-18. adversarially verified
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
Role permissions can restrict specific operations; reason codes and a dedicated exception report are not documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01
Menu, modifiers & pricing engine
Payments & money movement
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
No in-house processing. Documented terminal/gateway integrations: Global Payments Integrated, PaymentSense, Dojo, Ingenico GMP3/TSM via OKC, Worldline TIM. https://sambapos.com/integrations/ · retrieved 2026-08-01
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
Not an acquirer; publishes no card rates. Rates come from the merchant's chosen processor. https://sambapos.com/integrations/ · retrieved 2026-08-01
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
No dual-pricing mode exists. Price Definitions (KB 2.4.5.a) switch whole price lists by ticket type through an automation rule — not by tender — and nothing stores or prints cash and card totals together. Passing card cost is hand-built on the vendor forum as an Update Ticket Calculation button applying a percentage to {REMAINING TOTAL} with a toggle (Bob_be, 2020-01-29): a surcharge workaround, not two-tier item pricing. https://forum.sambapos.com/t/credit-card-surcharge-does-not-surcharge-the-owing-amount-but-the-total-amount/21493 · retrieved 2026-08-03
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
Surcharging in SambaPOS is a user-built automation-command button applying an Update Ticket Calculation at a fixed percentage (Bob_be, 2020-01-29, with manual toggle and optional pop-up override). There is no surcharging engine: no BIN/product-code detection, no automatic debit/prepaid exclusion, no network-cap enforcement — the operator chooses the button and the rate by hand. SambaPOS itself processes no card payments, so tender-aware guardrails have nothing to hook into. https://forum.sambapos.com/t/credit-card-surcharge-does-not-surcharge-the-owing-amount-but-the-total-amount/21493 · retrieved 2026-08-03
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
payments-emv-nfc
Ships no first-party payment terminals; EMV/NFC depends entirely on the integrated third-party device. https://sambapos.com/integrations/ · retrieved 2026-08-01
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
SUBJECT: SambaPOS V5 Pro itself, not an acquirer. KB 3.1 Hardware Requirements and Compatibilities (English, MODIFIED 2025-02-18) enumerates the supported peripheral classes exhaustively under seven headings and nothing else: 'Computer Hardware Requirements', 'Printer Hardware' ('any type of thermal or dot-matrix ticket printer'), 'Tablet Hardware', 'Caller ID Device', 'Scales', 'Barcode Reader/Writer', 'Cash Drawer'. There is no card-acceptance class of any kind, phone-borne or otherwise. Corroborating zero-hit across all 958 documents in both languages: tap to pay, taptopay, softpos, soft pos, tap-to-phone, tap to phone, cep pos and mobil pos all return ZERO files; case-insensitive NFC returns exactly one file, the Turkish KB 11.9 Ingenico OKC meal-voucher article, where the phone is the GUEST's. Fabricated slugs 404 at a fixed 45,059 bytes so the zero-hit binds. The vendor's only device-borne acceptance runs the OPPOSITE way: sambapos.com/sambapos-odeal-integration/ (English, MODIFIED 2026-03-17, one of the ten genuinely current English documents) puts the SambaPOS order-taking app onto a PAX Android payment device at $165+KDV annually plus a V5 licence - a certified payment terminal, not a commodity phone. https://kb.sambapos.com/en/3-1-hardware-requirements-and-compatibilities/ · retrieved 2026-09-05 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
Mobile Client lists a 'Get payment' function on Android/iOS, but there is no vendor handheld and no documented EMV/NFC tableside capture. https://sambapos.com/sambapos-mobile-client/ · retrieved 2026-08-01
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
Stated by the vendor twice. Samba Go Menu shipped in 5.3.6 (2021-05-26) as 'ready-made websites that can be accessed with QR'; asked on that release topic 'could the customers place order after scanning QR Code?', VehbiEmiroglu of SambaPOS (staff-flagged, 2021-06-04) answered 'Not for now. Its only show your menu.' KB 4.68 documents the same product as menu display with no cart and no payment. Asked separately on forum t/24966 (2021-11-09) 'Does SambaPOS have an integrated Order & Pay App? Allowing customers to Order and Pay from their table', Jesse Parker of SambaPOS answered 'We have one coming soon but right now no', and when pressed in 2022-03 only 'Soon. We will announce a lot.' The 2020 pay-at-table thread t/23171 is the same promise ('We will be supporting this for USA very soon'). Scored on the second reading of a roadmap statement - not yet available - because nothing shipped since: no article in the 613-record KB in either language and no post in the 68-topic V5 Release series through 5.7.28 (2026-07) announces guest-phone check payment, and GO Kiosk (8.6/8.14) and GO Tablet (8.7/8.18) take payment on vendor-supplied hardware. Grade C: staff forum answers, not product documentation. https://forum.sambapos.com/t/sambapos-5-3-6-release/24268 · retrieved 2026-08-09
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
Both flows exist in pieces, the management surface does not. KB 6.34 (Dejavoo, 2024-11) configures the controller with 'Can Adjust Tip: Check this box to allow tip adjustments on the terminal' alongside 'Can Refund'; KB 6.20 (Global Payments) sets a 'Tip Calculation Type Name' inside the Payment Operations module; KB 4.70 builds the generic path - a Tip account, a Tip transaction type, a Fixed Amount Calculation Type and a Tip calculation selector button on the payment screen. The mechanism shipped in 5.2.20 (vendor release post, 2019-03-18, staff account): 'Payment Operations Module added (tip adjusment feature for coming credit card integrations)... Tip adjustment for tickets... Improvements made in Tip Adjusment', and SambaPOS staff state 'We use pre auth for tip adjust' (forum t/21455, 2020-01-23). Shortfall: no documented batch or adjust window, and no manager screen listing unadjusted tips; adjustment lives inside each processor's controller (and operators have reported it failing outright on OpenEdge, forum t/20733), while the vendor-neutral path is a manual tip button. https://kb.sambapos.com/en/6-34-how-to-assign-and-configure-dejavoo-license-in-sambapos/ · retrieved 2026-08-08
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
SUBJECT: SambaPOS V5 Pro. KB 4.70 How to Add Tip Calculation (ENGLISH, MODIFIED 2022-02-09; the Turkish twin 4-70-tip-bahsis-nasil-eklenir is content-identical) is the vendor's complete step-by-step for tips and it builds exactly four objects: one Sales Account ('Account Name: Tip Account'), one transaction type, one calculation type whose 'Calculation Method: Fixed Amount', and a step '4. Adding Tip Calculation Selector'. There is no employee dimension, no allocation basis, no hours/sales/role/points weighting and no distribution or payroll-export step. The same four-object build is repeated verbatim inside the processor articles (English 6.5 OpenEdge, 6.12 International Bancard, 6.20 Global Payments), so this IS the vendor's tip surface, not one stray article. Corpus-wide in both languages: tip pool, tipout, tip-out, gratuity, tip share and tip distribution return ZERO files, and the Turkish bahsis hits are one KB article plus eleven marketing pages, none of which distributes anything. The 7shifts payroll add-on (sambapos.com/7shifts/, $99 annual) is timesheets only and never mentions tips. The vendor states the position itself in its own blog, sambapos.com/the-importance-of-tipping-tracking/ (English, 2023-08-29; Turkish twin 2022-08-15), where merely SEEING per-employee tips is said to require applying the necessary customizations - i.e. attribution, let alone pooling, is the operator's build, not a product engine. https://kb.sambapos.com/en/4-70-how-to-add-tip-calculation/ · retrieved 2026-09-05 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
A store-and-forward mode exists but only inside one processor controller and only as a named setting. KB 6.20 step 8 configures the GPI Credit Card Controller under Program Settings > Module Settings with 'Credit Card SITENAME / SITEID / KEY / TERMINALID', 'Remove Calculation After Fail' and 'Store Forward Working Mode: Set this to Online'. Shortfall: the article documents no other value and never describes what the mode does when connectivity drops; there is no per-transaction floor limit and no cumulative offline ceiling anywhere in the settings enumerated; none of the other seven processor integrations (PaymentSense, Dojo, OpenEdge, International Bancard, Worldline, Quest, Dejavoo) exposes an equivalent, so this is a Global Payments Integrated feature reachable from SambaPOS rather than a SambaPOS capability. Consistent with this record's existing reliability-offline-card-auth finding. https://kb.sambapos.com/en/6-20-global-payments-integration/ · retrieved 2026-08-08
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
There is no offline stored-transaction capability for a liability statement to attach to. SambaPOS processes no card payments; its complete documented payment surface is six third-party terminal/gateway integrations (PaymentSense, Dojo, Global Payments Integrated, OKC for Ingenico GMP3/TSM, Worldline TIM), and neither the integrations page nor the KB documents store-and-forward, deferred authorization, or any offline card capture. With no vendor-side offline payment storage there is no decline-on-reconnect loss to allocate and no post-reconnect failed-payments report — offline card behaviour is whatever the merchant's third-party terminal does, outside SambaPOS. https://sambapos.com/integrations/ · retrieved 2026-08-04
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
Real balance-tracked gift certificates, but hand-built and single-site. KB 4.31 walks through the whole thing: a GC product, gift-certificate account types and accounts, a document type, a dedicated payment type, entity type/states/screens for the certificates themselves, a printing template carrying '<QR>{SOURCE ACCOUNT}' and '<BAR>{SOURCE ACCOUNT}' with 'NO CASH VALUE', and actions that create the entity, post purchase and redemption account transactions and update the balance - 'You can either scan the barcode via barcode reader or enter the number of Gift Certificate manually into numberpad.' Balance is the account balance, so it is real-time. Shortfall: this is a configuration recipe, not a shipped gift-card product (operators routinely stall on it - forum t/21773, t/21281); SambaPOS is a single on-premise SQL database per site, so 'redeemable across every location in the group' is not supported without a shared database; nothing exposes the balance to the online-ordering channel (GloriaFood/takeaway.com orders arrive already tendered); and where a processor gift card is used instead it is theirs, not SambaPOS's (KB 6.20 maps 'Gift Card Payment Type Name' to Global Payments' voucher). https://kb.sambapos.com/en/4-31-gift-certificates-sales-and-redemption-implementation/ · retrieved 2026-08-08
House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.
payments-house-accounts
An Accounts module provides customer accounts and running balances; credit limits and statement generation not documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Split checks and multiple tenders are marketed; no documented cap or split-by-seat detail. https://sourceforge.net/software/product/SambaPOS/ · retrieved 2026-08-01
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
Role-based permissions can gate these operations; an immutable approver-identified audit log is not documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
Not a payment facilitator; disputes are handled by the merchant's processor, not inside SambaPOS. https://sambapos.com/integrations/ · retrieved 2026-08-01
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
Vendor statement of absence, re-fetched and verified verbatim on 2026-08-09 via forum.sambapos.com/t/21455.json. Asked whether the US card integration could hold a card and charge it later, Jesse Parker of SambaPOS answered 2020-01-22 'We do not not have that feature yet... But we can do tabs with SambaPOS it just won't have a pre-authorization', and 2020-01-23 'We use pre auth for tip adjust but tabs is a different thing. We would have to build something on Sambapos side for it. Yes we can do it. But no we have not built it into Sambapos yet', adding 'I will add this to the Redmine as a feature request... We have a tight roadmap so I wouldn't expect it to happen soon.' So the only credential retention in the integration is the per-transaction preauth used for tip adjust; nothing holds a token against a guest. That matches the data model - a customer entity carries a receivable balance moved by account transactions (KB 5.4.8.c, 5.1.10.a-d) and free-text custom fields (2.4.5), with no credential field - and the eight processor articles, which document sale, refund and tip adjust only. Grepped all 437 V5 Request/Tutorial topics for card on file and token: zero. The record scores the sibling claim order-capture-bar-tab-preauth `no` on this same source. https://forum.sambapos.com/t/us-credit-card-intergration-bar-tabs/21455 · retrieved 2026-08-09
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
Holds no merchant funds and publishes no deposit schedule. https://sambapos.com/integrations/ · retrieved 2026-08-01
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
330th, MOVED OFF unknown: the missing piece was POSITIVE evidence of the architecture, not more absence. CLAIM: vendor provides P2PE and a current PCI DSS 4.x AoC / P2PE listing available to merchants on request. VERDICT: no. EVIDENCE: SambaPOS's own payment documentation shows the vendor supplies no encryption solution and never carries card data - the card leg is executed by a third party's PIN pad through a controller DLL the merchant copies into the SambaPOS folder. KB 6.31 (https://kb.sambapos.com/en/6-31-quest-payment-integration/): "clicking the Credit Card button on the right side will initiate a transaction process which will be conducted by the PinPad" and "If you wish to utilize Manual card entry wait until you establish a connection after which you can enter your card number on the PinPad." KB 6.34 (Dejavoo, modified 2025-10-21) is the same shape: move Samba.Modules.DejavooController.dll and Samba.Modules.PaymentOperations.dll into the root folder; "The Dejavoo license is free of charge." A P2PE solution listing is held by the entity that encrypts at the POI - here the terminal estate's provider - and SambaPOS is not that entity and claims nothing. BOUND: the publication conjunct was already measured on a bound surface (both hosts enumerated, 958 documents in both languages, WP REST registry + core sitemap incl. the glossary and faq types + the 17-file wpdmpro library, href fixpoint drained; fabricated slugs 404 at a fixed 45,059 bytes): PCI 0, P2PE 0, attestation 0, AoC 0, SAQ 0, point-to-point 0, and the complete legal shelf (Terms of Use, Privacy, Personal Data and Cookie Use, with Turkish twins) contains no security or compliance page - the same census on which reliability-pci-dss-4-attestation is already scored no. The 5.7.30 binary adds P2PE 0 / PCI 0 / 3DS 0 across 73 Samba assemblies, and the forum's only substantive PCI posts are the founder and staff saying the opposite of a vendor attestation (/t/18118, markjw, 2018: SambaPOS must "use third party card terminals as that also covers for PCI DSS compliance"). Retrieved 2026-09-18. https://kb.sambapos.com/en/6-31-quest-payment-integration/ · retrieved 2026-09-18 adversarially verified
Kitchen & production
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
Printer templates and printer mappings route tickets by product/department; KDS offers 'customizable screens'. Rule editing is operator-side by design. https://sambapos.com/sambapos-kds/ · retrieved 2026-08-01
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
No expo screen exists. The setup guides for both shipped KDS generations enumerate the entire configuration surface: KDS V2 (KB 8.19) offers per-device product-group filtering ('select the product groups you want to receive orders for on your KDS Tablet'), new-order position, and three time-based colour states; KDS V1 (KB 8.9) routes categories to devices with Kitchen/KReady ticket states. Neither documents an expo/pass screen type that consolidates items from multiple prep stations, and nothing gates order completion on every contributing station having bumped — completion is a per-device state change. The KDS product page claims no expo capability either, and the non-module alternative (KB 4.13 kitchen display) is a hand-built Task Printer recipe. https://kb.sambapos.com/en/8-19-how-to-configure-sambapos-kds-v2/ · retrieved 2026-08-04
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
Course assignment and course-grouped kitchen printing are documented; hold and on-demand fire are not. Items are assigned a 'Course' order state with a Change Course button and can be moved between courses on the fly; the kitchen printer template groups and orders them with '[ORDERS GROUP|ORDER STATE:Course:Entree,Mains,Desserts]', and the grouping display shipped as the Update Ticket Grouping feature in V5 5.2.12 (confirmed in-thread by SambaPOS founder Emre Eren, staff-flagged, 2018-08-31). KB 2.4.16 prints a 'Mains-Starters Away' kitchen message triggered from a ticket tag. Shortfall: the orders themselves are not held - there is no hold state that suppresses the kitchen print job or the KDS card, and no fire-course button that releases one course; the away message is text on a separate slip. SambaPOS KDS (8.9) and KDS V2 (8.19) have no course concept at all: their configurable surface is colour states, ticket tags, product groups per device and remove-finished. https://forum.sambapos.com/t/shivans-tutorial-2-order-courses-order-grouping/18157 · retrieved 2026-08-08
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
The vendor's own answer to 'how long will this take' is a hand-typed number. Jesse Parker of SambaPOS authored the V5 Tutorial 'Setting an ETA for Take Out orders' (2018-01-21): a Ticket Created rule fires an Ask Question prompt '[?Cook Time(min);;;NOC]' and the promised time is computed as [=FD(ADS('{TICKET TIME}',TN('[?Cook Time(min);;;NOC]')*60),'hh:mm')], then printed on the ticket and shown on the order-queue screen - one operator-entered duration for the whole ticket, entered per order. There is no per-item cook time to configure: the product record (KB 2.3.15.a-d, and 2.3.6 product tags) carries no duration field, and 2.3.18 Product Timers is time-based billing for rentable products such as pool tables. Nothing stages or staggers: both KDS apps colour cards by elapsed time since the order arrived (8.9 'Green for as soon as the order is placed, Yellow after 15th minutes and Red after 25th minutes'; 8.19 State 1/2/3 at 5/10/15 minutes) and the entity-screen kitchen display (4.13) shows '{CREATION MINUTES} min.'. Grepped all 437 V5 Request/Tutorial topics for cook time, prep time and quote time: the only hit is this tutorial. https://forum.sambapos.com/t/setting-an-eta-for-take-out-orders/16825 · retrieved 2026-08-09
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
330th, THE LAST BLOCKER IS REMOVED BY THE VENDOR'S OWN PAGE AND BY THE GO ORDER SETTINGS ENUMERATION. CLAIM: automatic pacing/delay of incoming digital orders or extension of quoted prep time past a volume or ticket-time threshold. VERDICT: no. EVIDENCE: (1) the "Dynamic Capacity Management" headline bullet on https://sambapos.com/sambapos-kds/ is elaborated on that same page, and the elaboration is manual: "Configuration Capabilities for Dynamic Needs ... With technological integration, your team members can handle any challenge that is thrown at them. Changes to stock, labour, orders, and more can be done almost instantaneously and from anywhere." Nothing automatic, no threshold. (2) Every place such a rule would be configured is enumerated by the vendor. The GO Order module settings, read from the vendor's own screenshots at full resolution (https://kb.sambapos.com/wp-content/uploads/2024/12/GloriaFood-Go-Order-61.jpg, SambaPOS 5.7.14): module panel = Menu, Entity Type, Courier Entity Type, Ticket Type, Department, Default Category, Customer Mapping, Payment Methods, Default Portion, States, Delivery State Value, At Delivery State Value, Pending State Value, New Order Pop-Up, Use Default OTG; provider panel = Auto. Accept, Play Sound, Alternative Mapping, Order Method Tag Name, Tag for Pickup, Tag for Delivery, Default Delivery Time, DeliveryFee, Discount Type, Payment Type; Restaurant Information dialog = Reference Id, Restaurant Key, Master Key, RestaurantName, Default Delivery Time (https://kb.sambapos.com/wp-content/uploads/2024/12/GloriaFood-Go-Order-53-1.jpg). The nearest miss is "Default Delivery Time: 30/40", a fixed promise, never extended by volume; "Auto. Accept" is the opposite of throttling. The four Turkish GO Order docs enumerate the same list (KB 6.17: Go Order Aktif, Menu, Varlik Tipi, Adisyon Tipi, Indirim Hesaplayici, Varsayilan Kategori, Durum ve Durum Degeri). KDS V2 (KB 8.19) has only colour thresholds (State 1/2/3 at 5/10/15 minutes) that change a card's colour. BOUND/CONTROLS: over those 9 GO Order + KDS articles (72,644 bytes), tokenised word-boundary case-insensitive: throttle 0, throttling 0, capacity 0, kapasite 0, threshold 0, pause 0, busy 0, limit 0, prep 0; positive control SambaPOS 259. This is on top of the 328th's 63-file, 19.8 MB re-grep (dynamic capacity 0 outside the one marketing bullet) and the 5.7.30 installer (throttl 2, both Rx Throttle/Debounce POISON). Retrieved 2026-09-18. https://kb.sambapos.com/en/6-29-go-order-gloriafood-integration/ · 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
Go Order is order intake only, and the finding no longer rests on GloriaFood, which is discontinued and closed to new signups (gloriafood.com, 2026-08-09) with both its KB articles headed 'This product is no longer supported'. The four live marketplace articles - Yemek Sepeti 6.16, Trendyol 6.17, Migros 6.18, Getir 6.19 - each enumerate the entire settings surface: the marketplace's own seller ID, API key and API secret, the SambaPOS menu to map against, a customer entity type, a Default Category for a marketplace product that does not exist in SambaPOS, account transaction and calculation templates, and an entity screen carrying the Go Order Explorer widget. None contains a pause, close-store or sold-out call outward. Jetrik is the same shape and puts the open/closed switch on the Jetrik panel dashboard rather than in SambaPOS (6.25). The GoOrder USA path (Uber Eats, DoorDash, Grubhub; release 5.5.8, undocumented in the KB in either language) is described by the vendor's own product page as order transfer, tracking, reporting, printing and a dashboard, with no pause, sold-out or menu feature. The only availability switch SambaPOS ships is the GO Office Sold Out control for GO Kiosk and GO Tablet (KB 8.14-a), which has no marketplace concept at all. https://kb.sambapos.com/6-17-go-order-trendyol-yemek-entegrasyonu/ · retrieved 2026-08-09 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
330th, THE KDS SIDE IS NOW A CENSUS FROM THE VENDOR'S OWN CONFIGURATION DOCS, SO THE CELL CLOSES. CLAIM: bumping an order ready on the KDS sends an order-ready event back to the third-party marketplace. VERDICT: no. EVIDENCE: SambaPOS publishes exactly two KDS configuration documents and both enumerate every setting screen. KB 8.9 (en, modified 2024-12-18, https://kb.sambapos.com/en/8-9-how-to-configure-sambapos-kds/) defines the bump itself: "4.3.4. Status Settings Wait Status: Kitchen Ready Status: KReady" and "When you click on an individual order, its status will turn to KReady and once all the orders of that ticket is completed, the ticket will disappear from Open Cards Tab and moved to Completed Cards Tab" - the bump writes a LOCAL SambaPOS order state and nothing else. KB 8.19 (en, https://kb.sambapos.com/en/8-19-how-to-configure-sambapos-kds-v2/, images dated 2025-02, the CURRENT V2 now that kdsadmin was retired) enumerates the whole configuration: Message Server port 9000+, a Kitchen order State, a kds user, a kds Application with Enable Default Functions, Send Menu to SambaPOS KDS, then "3.6. KDS Settings Screen" = Enable KDS, State 1/2/3 (colour after 5/10/15 minutes), Show Ticket Tag, Remove Finished Products, New Orders Position, and "3.7. KDS Devices Screen" = Select Groups. The tablet reaches only the local Message Server ("In the Manual Server Entry field, enter your Host PC's IP address ... and your SambaPOS Message Server Port number"), so the KDS has no path to a marketplace at all. The receiving end is enumerated too: all five GO Order integration documents (KB 6.16 Yemeksepeti, 6.17 Trendyol, 6.18 Migros, 6.19 Getir, 6.29 GloriaFood - the US/GoOrder path) list their complete settings and none has a status-out option; the GO Order sale screen, read from the vendor's own screenshots at full resolution (https://kb.sambapos.com/wp-content/uploads/2024/12/GloriaFood-Go-Order-59.jpg), offers only Delivery To Customer, Cancel, Display Ticket, Print, Close and the tender buttons. BOUND/CONTROLS: the 9 KDS+GO Order articles (72,644 bytes) tokenised, word-boundary, case-insensitive: callback 0, webhook 0, bump 0, courier 0, doordash 0, ubereats 0, grubhub 0, kitchenhub 0, ready 1 ("Ready Status: KReady", a local state - the POISON here is that every `status` hit, 21 of 21, is a LOCAL SambaPOS order state, a Windows service "Start status" or the "Go Order Working" status bar). Positive control SambaPOS 259. Retrieved 2026-09-18. https://kb.sambapos.com/en/8-9-how-to-configure-sambapos-kds/ · 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
KB 8.9 System Requirements point 3 is explicit: 'SambaPOS KDS works only Tablet Devices', Android 6.0+ with Google services or iOS 11+, downloaded from Play Store or App Store; the documented interaction is touch only - 'When you click on an individual order, its status will turn to KReady... You can also select the whole card by clicking twice on the Ticket Type Name.' KDS V2 (8.19) is the same. KB 3.1 Hardware Requirements and Compatibilities enumerates the peripheral classes SambaPOS supports - touchscreen/all-in-one PCs, ESC/POS thermal and dot-matrix printers, tablets, Hugin/Conexant caller-ID devices, CAS/TEM and custom COM-port scales, keyboard-emulating barcode readers, RJ11 cash drawers - and lists no bump bar or programmable keypad, and no supported models are published in either language KB. Community members do drive keypad-style workflows against a hand-built Ticket Lister display (forum t/29572, 2024, where the vendor-side answer was to edit your task printer template 'or use our android KDS app'), but that is a user workaround, not vendor bump-bar support with documented models. https://kb.sambapos.com/en/8-9-how-to-configure-sambapos-kds/ · retrieved 2026-08-08
An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.
kitchen-all-day-counts
Two halves. The KDS half is a real absence: English KB 8.9 (2024-12-18) walks the whole display model - the kdsadmin.sambapos.com Dashboard, General Settings (Color, Token, Server, Status, Ticket, Completed Tickets) and Device Settings (Device Name, Group Type, Notification Voice, Chosen Voice, Fixed Height) - and the tablet shows per-ticket cards only, an Open Cards Tab and a Completed Cards Tab, with 8.19 KDS V2 repeating the same model. No aggregated per-item view exists on the add-on, which is separately licensed per device at $69 annual. The V5 Pro half is not an absence: English KB 9.1.8 says 'You can add custom reports inside a Custom Entity Screen by using a Custom Report Viewer Widget.' and that 'Widget displays reports in current work period by default.', while 9.1.9 demonstrates order-line reports with a quantity column, a quantity summary and automatic grouping over menu item groups, and 9.1.3 exposes OS.<state name> so the same report can be restricted to orders still in an unfinished state. That is an all-day count on a station screen, assembled from documented shipped widgets rather than shipped as a named view. Table-stakes cell met by construction only: partial. https://kb.sambapos.com/en/9-1-8-custom-report-viewer-widget/ · retrieved 2026-09-05 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
Configurable colour escalation yes, per-station targets no. KDS V2 (KB 8.19, Manage > KDS > KDS Settings): 'State 1: This is the color of the ticket on the KDS screen will take until 5 minutes have passed since the order arrived. State 2... after 10 minutes... State 3... after 15 minutes. You can customize those periods accordingly.' KDS v1 (KB 8.9) puts the same on kdsadmin.sambapos.com General Settings > Color Settings - 'Green for as soon as the order is placed, Yellow after 15th minutes and Red after 25th minutes' - and Device Settings adds 'Notification Voice: You can Enable or Disable notification voice' with a choice of sound. Shortfall: the colour thresholds are a single global set - Device Settings scopes only which product groups and the display layout, not the target times, and there is no per-order-type target at all; the audible option is a new-order chime, not an alert fired when a ticket exceeds target. https://kb.sambapos.com/en/8-19-how-to-configure-sambapos-kds-v2/ · retrieved 2026-08-08
If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator
kitchen-printer-fallback
Automatic failover to a backup printer or screen has been an open feature request on the vendor forum since 2019-08-14 — the requester states he lost deals over it — and it never shipped: no staff reply, and the community answers are the excluded alternatives (rely on the Windows print spooler queuing jobs until the printer returns; printer pooling, which round-robins rather than fails over; and by 2022-04-30 the third-party tool Spool Queue Viewer++ to redirect jobs between printers). The KDS V1/V2 setup guides (KB 8.9, 8.19) likewise document no offline or failover behaviour for screens. https://forum.sambapos.com/t/new-feature-printer-backup-fail-over-option/20587 · retrieved 2026-08-04
KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator
kitchen-offline-operation
POS-to-KDS traffic runs over the LAN Messaging Server against a local SQL Server, so internet loss should not stop ticket display; not stated explicitly for KDS V2. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Full modifier and portion breakout yes, recipe/assembly detail no. KB 4.13 builds the kitchen screen as an entity screen carrying a Ticket Lister widget, and publishes its format: a header of '{CREATION MINUTES} min. - {ENTITY NAME:Tables}', product-group headings via '[ORDERS GROUP|PRODUCT GROUP]', then per line the quantity, product name and '{PORTION}' rendered in a distinct font/colour, followed by '{SORTED ORDER TAGS}' which prints each modifier as '[=('{ORDER TAG QUANTITY}'>1 ? {ORDER TAG QUANTITY} : ' ')] * {ORDER TAG NAME}' - i.e. every order tag with its multiple. Shortfall: there is no build or assembly view - inventory recipes (2.3.15.c) are a costing construct that never reaches a station screen, no recipe-step or preparation-instruction field exists on the product, and the packaged KDS app (8.9/8.19) shows only ticket type, ticket tags and the order lines, configured by product group per device. https://kb.sambapos.com/en/4-13-how-to-generate-kitchen-display/ · retrieved 2026-08-08
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
English KB 4.60 Half and Half Pizza Configuration (modified 2020-12-18) is the complete vendor model for a split pizza and it carries no position attribute. The product is a zero-priced Half and Half Pizza; the split is a per-size order tag group configured 'Name: 9 Inches 50/50 Pizza', 'Min Selected Items: 2', 'Max Selected Items: 2', 'Add Tag Price to Order Price: Must be selected', with three actions and one rule that do nothing but take the higher of the two tag prices. The two selections are an unordered set: no half, section, quadrant or position field exists on an order tag anywhere in the data model, so which variety sits on which half is never captured, and quarters are not modelled at all. Because it is never captured it cannot be rendered - the kitchen-display template in English 4.13 and the combo template in English 4.43 both emit order tag name and group as flat text, and English 8.9 and 8.19 describe no graphic element on the KDS. This answers the display question that the record's existing forum citation (t/10090) does not, that one being about price. The Turkish 4.60 twin carries the identical model. https://kb.sambapos.com/en/4-60-half-and-half-pizza-configuration/ · retrieved 2026-09-05 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
Recall ships, but only in the widget kitchen display the operator builds, and only for whole cards. KB 2.3.2.d enumerates the Task Editor Widget's settings and among them are 'Reccal size' [sic], 'Task Complete commands', 'Completed task visibility minutes' and 'Display completed items' - a configurable depth of completed tasks that can be returned to the active list. The mechanism is described by Emre Eren, SambaPOS's founder, in V5 Request t/9899 'Bump Bar for Kitchen display' (2016-04-29): 'Features added to Task Editor... Recalling last completed item... In the screen shot 123456 keys mapped to Toggle#{key} and Recall key mapped to backspace key', initially limited to one item ('you are limited to 1 recall only') and then extended after discussion into a stack - 'We set the maximum Recall Queue in the Task Editor Widget Settings' - shipped in 5.1.60 and drivable from a physical bump bar. Shortfalls: (1) this is the Task Editor kitchen display an operator assembles on an entity screen, not the packaged SambaPOS KDS or KDS V2 apps (KB 8.9, 8.19), which document only Open/Completed Cards tabs and a 'Remove Finished Products' toggle with no reverse action; (2) recall acts on a task card, not on one item within an order, and Emre notes it will not bring back an item that has aged off the screen; (3) there is no refire - reprinting a kitchen order is an operator-built Execute Print Job button that reprints the whole order to a chosen printer (community V5 Tutorial t/10453), not a per-item resend. https://kb.sambapos.com/en/2-3-2-d-how-to-add-layout-entity-screens/ · retrieved 2026-08-09
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
Removals are flagged, additions and changes are not. KB 4.13's kitchen-display Ticket Lister template carries distinct sections '[ORDERS:Gift]' and '[ORDERS:Void]' that re-render the same line in green with 'Gift' and in red with 'Void' respectively, so an item cancelled after the ticket is on screen is visually distinguished from the rest; the kitchen print templates do the same ('**VOID**' and '**FREE ITEM**' blocks, KB 4.43), and SambaPOS KDS carries a matching 'Void State: Void' setting on kdsadmin (KB 8.9 section 4.3.5.3). Shortfall: nothing highlights an item added to a live ticket - it simply appears as another order line - and there is no changed-item flag at all; the only other colour dimension documented on the KDS is ticket age (State 1/2/3). https://kb.sambapos.com/en/4-13-how-to-generate-kitchen-display/ · retrieved 2026-08-08
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
An order-status board exists as a build, SMS needs a third party. KB 4.13: 'By this document you can track preparation process of taken orders from kitchen screen. Prepared orders will be displayed on customer screen when they are confirmed' - the operator creates a Kitchen Track entity screen and a Customer Track entity screen, an 'Order Ready' and an 'Order Delivered' automation command and an Update Ticket Kitchen State action, with a rule 'Make State Ready When Ticket Selected From Kitchen Screen' that moves the ticket to the customer board. No extra licence is named: entity screens and widgets are base V5 Pro. Shortfall: it is assembled by hand from entity screens, widgets, actions and rules rather than shipped, and it is driven by that Order Ready command rather than by the SambaPOS KDS app's KReady bump (8.9), which documents no guest-facing output; the SMS route (KB 4.35) is a URL Printer posting to an operator-supplied SMS gateway - 'the URL that was provided by the Operator' - so text notification requires a separate third-party account, and no app push is documented anywhere. https://kb.sambapos.com/en/4-13-how-to-generate-kitchen-display/ · retrieved 2026-08-08
Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.
kitchen-waste-logging
Wastage logging with cost tracking exists in the inventory module; logging it from the KDS screen with reason codes is not documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
KDS markets 'kitchen efficiency calculation'; percentile/daypart/channel slicing and CSV/API export not documented. https://sambapos.com/sambapos-kds/ · retrieved 2026-08-01
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
English KB 9.1.3 Custom Reporting Tags (modified 2021-01-29) is the closed list - 'These are the supported DETAILS tags.' - covering TICKET DETAILS, ORDER DETAILS, PAYMENT DETAILS, CALCULATION DETAILS and ENTITY STATE DETAILS, and every field in all five is recorded history. No predicted, projected or forecast quantity exists in it. The only prediction-shaped fields anywhere in the reporting documentation are C.Prediction and C.CostPrediction in 9.1.4's consumption and cost blocks, and both are current inventory arithmetic, matching the Turkish 5.5.7.a definition of the projected stock level as the position after existing transactions. Corpus-wide zero across all 958 documents in both languages for forecast, prep list and hazirlik listesi. The second limb has no surface either: the Task module is documented (Add Task action in 4.3, Task Editor widget in Turkish 2.3.2.d, task start/end/duration report fields in 9.1.4) but no article in either tree generates tasks from sales history, and English 4.55 daily item limits asks the operator how many they have today rather than predicting it. Neither predicted quantities nor a surfaced daily prep list. https://kb.sambapos.com/en/9-1-3-custom-reporting-tags/ · retrieved 2026-09-05 adversarially verified
Delivery, dispatch & third-party channels
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
Deliverers are a first-class entity type: Manage > Settings > Configuration Tasks > 'Advanced Delivery Screen Setup' creates the Deliverers entity type, deliverer buttons and the rules that move a delivery ticket Waiting -> (deliverer selected) Delivering -> Delivered, with a 'DLVR-Update Delivery Service Deliverer State' action and a 'No Deliverer' command; the Delivery Service entity screen shows Waiting Orders and Delivered Orders columns. Shortfall: no deliverer clock-in/out (the Time Clock module, KB 8.13, clocks USERS by department/role and is never tied to deliverer entities), and no per-driver run-history report - section 9 Reports ships only custom SQL/report-tag templates and lists no deliverer report. https://kb.sambapos.com/en/4-12-advanced-delivery-service-implementation-v5-2-3/ · retrieved 2026-08-08
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
"Assign the couriers instantly via the SambaPOS dashboard. Real-time data lets you see who is available to deliver and who is not" describes courier assignment and availability, but multi-order run batching (assigning 2+ orders to one driver as a single run) is not mentioned on this page or documented in the KB. https://sambapos.com/delivery/ · retrieved 2026-08-04
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
A 'Nav Core' navigation module is documented, configured with Google Maps or TomTom API keys. Multi-stop sequencing on a dispatch board is not documented. https://kb.sambapos.com/en/ · 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
The page claims staff can "add addresses, helpful landmarks, and track the route on Google Maps," but does not describe a driver-facing mobile app capturing live GPS position, falling short of the claim; no KB article documents this mechanism further. https://sambapos.com/delivery/ · retrieved 2026-08-04
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
Delivery geography in SambaPOS is a postcode plus an operator-written script. The vendor's V5 Tutorial category answers distance-based delivery with JScript against Google's Distance Matrix API - "var u = 'http://maps.googleapis.com/maps/api/distancematrix/json?origins='+origin+'.&destinations='+destination+'.&mode=driving...'; var distance = json.rows[0].elements[0].distance.value/1000" - fed from a Customers custom field named PostCode and wired to an Update Ticket Calculation action; a later post in the same thread bands the fee in the script and returns -1 beyond 8.1 km to refuse the job. Jesse Parker of SambaPOS converted the original beta post into this tutorial ('I converted it to a tutorial to share with everyone') and answers configuration questions in it. The shipped surfaces are no wider: KB 2.2.6 defines serving areas as a Customers custom field of type String whose Values column holds neighbourhoods comma-separated ('Wandsworth, Southwark, Islington'), and KB 6.52 Nav Core (5.7.28) exposes AddressSearch and PostcodeLookup custom field types that geocode one address into Street, HouseNo, City, District, PostCode, Country plus hidden Lat, Lng and PlaceId. So an area is a postcode/neighbourhood list or a scripted point-to-point distance; there is no map on which to draw a polygon and no drive-time isochrone. Grepped all 437 V5 Request/Tutorial topics for polygon, isochrone and delivery zone: zero. Scoped to SambaPOS itself - KB 6.25 section 3.3.2 still does not enumerate the third-party Jetrik panel's Delivery screen. https://forum.sambapos.com/t/advanced-tutorial-automatic-delivery-charge-based-on-distance-via-google-maps/6918 · retrieved 2026-08-09
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
Zone-variable delivery charges are built by hand on the vendor forum: an Update Calculation action behind a prompt listing fixed amounts (Bob_be, 2020-08-09: replace the Amount field with a [?Delivery Charge;...] prompt offering 5/10/15) or custom automation commands (Francisco_Lopez). No reply points at a built-in zone table, and nothing derives fee, minimum or promise time from the validated address. KB 4.12, the advanced delivery implementation, contains no zones, fees, minimums or promise times. https://forum.sambapos.com/t/variable-delivery-charges-based-on-zones/22723 · retrieved 2026-08-03
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
A UK Post Code Lookup feature is documented for address entry; out-of-zone rejection is not. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
The deliverer record has no shipped fields at all, so it carries no compensation inputs. Emre Eren, SambaPOS's founder, builds the delivery workflow from scratch in the V5 Tutorial 'Custom Package Delivery for V5' (2015-11-24, requires 5.1.55): 'We'll start by creating a new Entity Type for Deliverers... We may want to track few more data for deliverers. Before saving Entity Type I'll switch to Custom Fields section and add two custom fields for Phone Number and Address.' The rest of the flow assigns a deliverer entity to a ticket through Ticket Lister command buttons, displays the ticket and opens a Google Maps route for the customer address; nothing measures a run, and settlement is per ticket. That matches KB 4.12, where the only per-deliverer data are operator-defined custom fields and the fast-payment buttons post against the ticket. Grepped all 437 V5 Request/Tutorial topics (6,390 posts) and all 613 KB records in both languages for mileage, odometer, kilometre and reimbursement: zero in every corpus. Where the vendor ships nothing the community substitutes: forum t/22739 'Deliverers Report' (2020) is a user-authored add-on 'to the Advance delivery Screen Setup - Configuration Task' whose stated purpose is 'to keep track of Deliverers/Drivers payments and totals'. No distance-per-run, no per-delivery flat reimbursement, no driver-retained tip line, and no payroll export separating reimbursement from wages. https://forum.sambapos.com/t/custom-package-delivery-for-v5/8263 · retrieved 2026-08-09
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
Turkish marketing page (grade C, MODIFIED 2023-10-11). Under the Yemeksepeti integration the vendor bullets a courier-account capability of SambaPOS itself, "Paketçi hesapları yönetimi", and the body says "Tüm ödeme süreçlerini SambaPOS & Yemeksepeti entegrasyonu ile takip edebilirsiniz." The GetirYemek block adds "Tüm teslimat ayrıntıları ve paketçi detayları en ince ayrıntısına kadar raporlanır." Underneath, the mechanism is operator-assembled but documented: KB 4.12 (English twin, 2023-02-13) creates Deliverers as an entity type and moves a ticket between the Waiting Orders and Delivered Orders columns once a deliverer is assigned; the Turkish 4.12 section 7 adds Hizli Odeme Al Nakit / Kredi Karti / Yemek Ceki buttons on the courier widget; KB 9.1.2 (English, 2018-07-05) lets an operator register arbitrary SQL in a custom report over that data. FRESHNESS CORRECTION: batch B's decisive citation was the Turkish 5.5.5.a stamped 2026-08-24, inside the 6m46s bulk re-save; its English twin is stamped 2018-04-06 and carries the same six-report statement, so that closed report list is an eight-year-old floor, not a current census. What is genuinely absent is a shipped per-deliverer settle-up with counted cash, over/short and tips owed. Partial, mechanism named. https://sambapos.com/tr/entegrasyonlar/ · retrieved 2026-09-05 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
Shipday integration is listed and documented, providing courier marketplace dispatch; quote/status write-back into the order record is not documented. https://sambapos.com/integrations/ · retrieved 2026-08-01
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
KB 6.44 Shipday Integration (English, MODIFIED 2026-03-12 - a dispersed date, not part of the 288-document 2026-08-24 event, so this one may honestly be called current). Shipday is the only DaaS courier anywhere in the 958-document corpus in either language. The push is a single unconditional path with no overflow logic: "8. Adding Send to Shipday Automation Command", then "9. Adding Send to Shipday Action", then "10. Adding Send to Shipday Rule" whose only gate is "Add Custom Constraint:" followed by "Automation Command Name|Equals|Send to Shipday". No condition on in-house deliverer availability, delivery zone or elapsed wait appears anywhere, and the trigger is a button the user presses ("Button Header: Send to Shipday"), so it is a manual hand-off rather than an automatic fallback - which also contradicts the Turkish marketing page's claim of a no-click transfer. Any hybrid-dispatch decision sits in dispatch.shipday.com. Shipday is a separately priced add-on (39 USD annual, requiring a SambaPOS V5 licence, per sambapos.com/tr/sambapos-shipday-entegrasyonu/), not a V5 Pro capability. https://kb.sambapos.com/en/6-44-shipday-integration/ · retrieved 2026-09-05 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
Two corrections to the earlier note, same verdict. First, 'the only GoOrder article is Go Order GloriaFood' is wrong: the KB documents Go Order integrations for Yemek Sepeti (6.16), Trendyol (6.17), Migros (6.18), Getir (6.19) and Jetrik (6.25), all Turkish-language except Jetrik, each configured directly against the marketplace's own seller ID, API key and API secret rather than through Otter, Deliverect, Chowly or ItsaCheckmate - so vendor-owned direct marketplace integrations do exist. Second, the GloriaFood article the note leaned on is dead ('This product is no longer supported') and GloriaFood itself is discontinued and no longer accepting new signups. Partial is held by the claim's own wording, which names DoorDash, Uber Eats and Grubhub: those three reach SambaPOS only via GoOrder USA, a US-only add-on priced at $49/month on top of an active V5 licence (release 5.5.8, 'Go Order USA Integration added (Uber Eats, Doordash, Grubhub, Gloriafood)'), with no KB article in either language, no certification statement anywhere, and no menu push, 86 sync or store-pause capability claimed. https://kb.sambapos.com/6-17-go-order-trendyol-yemek-entegrasyonu/ · retrieved 2026-08-09 adversarially verified
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
Re-grounded off the marketing page onto documentation. For the marketplaces SambaPOS actually documents, injection is automatic and ticket-native: 6.16, 6.17, 6.18 and 6.19 wire provider credentials, a customer entity type that the marketplace's customer details are written into automatically, an entity screen carrying the Go Order Explorer widget, and print jobs, while 4.79 (Yemek Sepeti), 4.80 (Trendyol), 4.85 (Migros) and 4.87 (Getir) define the printer tags those orders print with; Jetrik's settings add 'Auto Confirm: Select if you want to confirm the orders directly' and 'Popup In New Orders' (6.25). No tablet re-keying appears anywhere in that path. Shortfalls that keep this at partial: for the three US marketplaces named in the claim the only evidence is the GoOrder USA product page ('automatic order transfer to SambaPOS') plus a staff forum post saying it will 'remove tablets', with no KB article in either language; a marketplace product with no SambaPOS match is dropped into the operator-nominated Default Category and the articles warn it must be added to the relevant print jobs by hand or it will not reach a printer; and each channel is a separately purchased integration licence, the US one US-only at $49/month. https://kb.sambapos.com/6-17-go-order-trendyol-yemek-entegrasyonu/ · retrieved 2026-08-09 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
There is no POS-side 86 state to push. KB 4.50, read in full, is a do-it-yourself automation recipe rather than a feature: it tags products, evaluates {REPORT INVENTORY:{ITEM TAG:Alert}:Local Warehouse} on the Order Added to Ticket event and fires Show Message plus Cancel Orders ('{ITEM TAG:Alert} Out of Stock! Last order cancelled'). It never marks an item unavailable, so nothing exists to transmit; the article says nothing at all about online ordering, and the quotation to that effect in the earlier note does not appear in it. The only sold-out control SambaPOS ships is manual and first-party - the GO Kiosk V2 feature list describes 'Sold Out: you can close a product to sale within seconds without removing it from the menu', set in GO Office, whose product status vocabulary (soldOut, inStock, hidden) is scoped to GO Kiosk and GO Tablet menus. The third-party channels, including the GoOrder USA set (Uber Eats, DoorDash, Grubhub, GloriaFood, added in 5.5.8 and undocumented in the KB), are configured and marketed as order intake only, with no item-availability call in either direction. https://kb.sambapos.com/en/4-50-how-to-prevent-zero-stocked-item-sales/ · retrieved 2026-08-08
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
KB 6.25 (English, MODIFIED 2023-11-16). The Jetrik ordering panel carries an explicit manual store-status switch: "In here, you can set your restaurant as Open-Closed, change theme-language-password settings by clicking on your name which is located on the top right corner." Section "3.3.4. Opening Hours Screen" adds a schedule - "You can handle Opening Hours settings of your restaurant from here." - and the closed-hours section (mislabelled "3.3.5. Scheduled Orders Screen" twice in the English page, correctly titled Kapali Saat Secenekleri Ekrani in the Turkish twin, which does exist and was a diacritics false positive in the checker) states "You can adjust the settings here for how your restaurant will appear outside of business hours." So manual pause and scheduled closure both exist. What does not exist is timed auto-reactivation, and no marketplace channel module carries any store-status control: KB 6.19 Getir Yemek (Turkish) enumerates its in-POS settings field by field - Getir Aktif, Otomatik Onay, Ses Cal, Indirim Tipi, Menu, Varlik Tipi, Adisyon Tipi, Varsayilan Kategori, Durum ve Durum Degeri - and Getir Aktif is a module on/off flag, not a marketplace pause; KB 6.29 GloriaFood shows default settings described only as Auto Accept, Play Sound etc. The control lives in the Jetrik add-on's web panel, not the POS; the SambaPOS-side Jetrik integration is sold as free to Jetrik Standard members. Partial, add-on named. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-09-05 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
CLAIM: Third-party reconciliation report matching marketplace payouts to POS sales with commissions, fees, adjustments and missing orders. VERDICT: unknown upheld. NEW SURFACE: the shipped 5.7.30 binary (https://sambapos.com/download/sambapos_setups/SambaSetup5730_09092.exe; 73 Samba assemblies scanned raw + UTF-16LE): commission 0, payout 0 in every assembly; reconcil 14, all POISON (card-batch reconciliation in PaymentController/Samba.Modules.PayCellPaymentController.dll 13 and Samba.Modules.DejavooController.dll 1). GoOrder USA runs through Samba.GoOrder.Kitchenhub.dll (KitchenHub aggregator) whose visible members are order-ingest only; the GoOrder USA explorer in Samba.Presentation.ClientLibrary.dll is a ticket list with provider filter buttons. The priced "Detailed reporting" / "GoOrder dashboard" of sambapos.com/goorder-usa/ is a cloud surface not in the installer, and the Kitchenhub string heap is encrypted, so the scan is not a census. Retrieved 2026-09-16. || 322nd: NEW SURFACES (322nd): crt.sh %.sambapos.com (2026-09-17) listed 53 names; live anonymous hosts probed: apidoc.sambapos.com (Wiki.js, 302 /login, /swagger 403 - gated), mcdemo.sambapos.com (GraphiQL shell; POST /api/graphql 401 - no introspection), md.sambapos.com (Nuxt app behind GitHub login), local.sambapos.com (Weblate 4.12.1, anonymous API lists 0 projects), admin.ticket.sambapos.com (helpdesk SPA), defter.sambapos.com (Cloudflare Access), getircloud.sambapos.com and metrik.sambapos.com (below); doc/koffice/b2b/usa-support/helpdesk/wl/v4/neptune do not answer. (1) metrik.sambapos.com, SambaPOS Metrik cloud reporting (Flutter; main.dart.js 5,013,763 B, Last-Modified 2025-03-19, no main.dart.js_N.part.js deferred parts; AssetManifest lists lang ar/de/en/nl/tr). en.json holds 150 keys; its report enumeration is: Work Period Report, Item Sales Report, Cash Transactions Report, Inventory Transaction Report, Inventory Report, Cost Report, Product Group Report, End of day reports, Log report, User Based Sales, Sales By The Hour, Weekly Sales. Bundle controls (word-boundary, case-insensitive): commission 0, komisyon 0, payout 0, reconcil 0, mutabakat 0, getir 0, trendyol 0, yemeksepeti 0, migros 0, doordash 0, uber 0, goorder 0, delivery 0, paket 0. So Metrik has no marketplace reconciliation report. (2) getircloud.sambapos.com (2021 Getir-only panel, full public source map, 17 app sources): only totals (totalOrderPrice/todayOrderPrice) and order lists; commission/payout/hakediş/mutabakat/fee 0. WHY STILL unknown: Metrik bounds only that app; the priced GoOrder dashboard "Detailed reporting" (sambapos.com/goorder-usa/) is a separate cloud surface not reachable anonymously. Retrieved 2026-09-17. || 328th: 328th, PER-CELL RE-GREP over all 63 on-disk SambaPOS corpus files (19,786,797 bytes: kb article dump, the four forum dumps, the GoOrder page, the q322 Metrik and Getir bundles) using Turkish as well as English vocabulary: komisyon 0, hakediş 0, mutabakat 0, payout 16 and commission 26 - and every one of those 42 is POISON. The `payout` hits are SambaPOS's own cash-drawer 'Expenses and Payouts - Method Q' tutorial and inventory payouts from the drawer; the `commission` hits are forum members discussing marketplace commission RATES charged to them (e.g. /t/32171 on GloriaFood shutting down, and a member describing ten delivery companies with different promotions and commissions) - operator complaints about fees, never a SambaPOS report that reconciles them. No new surface exists to mine: the KB has no custom post type beyond the defaults, its 42 non-image media attachments are print templates and device manuals, and the sambapos GitHub org's 7 public repos hold no GoOrder or reporting code. Retrieved 2026-09-18. || 330th: 330th, NEW SURFACE, still short of a verdict. The GO Order module's own UI is now enumerated from the vendor's screenshots: it has exactly three tabs - Sale, Cancelled, Settings (https://kb.sambapos.com/wp-content/uploads/2024/12/GloriaFood-Go-Order-59.jpg) - i.e. no report or finance surface at all, and the only fee-shaped settings anywhere in it are DeliveryFee (a mapped SambaPOS service charge) and Discount Type (a mapped discount account); the Turkish GO Order docs build the same thing by hand as a local "TY/GY Indirim" discount account and calculation template (KB 6.17 s5, KB 6.19 s5), which records the marketplace's discount in the merchant's own books rather than reconciling a payout. Tokenised controls over the nine GO Order + KDS articles (72,644 bytes): commission 0, komisyon 0, payout 0, mutabakat 0, hakedis 0, reconcile 0, reconciliation 0, with positive control SambaPOS 259. WHY STILL unknown, unchanged in shape: the priced "Detailed reporting" of the $49/month GoOrder subscription (https://sambapos.com/goorder-usa/: "GoOrder Integration 49$ Monthly - Automatic order transfer to SambaPOS, Order tracking, Detailed reporting") lives in a cloud dashboard that is not one of the 53 crt.sh names under sambapos.com and is reached through the KitchenHub aggregator, so it is an unread paid add-on rather than a measured absence. 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
Connection status is exposed: after nominating the server terminal, 'the green Go Order Working text will also appear on the program status bar (lower left corner in SambaPOS)', and each integration article lists the causes of 'Go Order Not Working' - SambaPOS not licensed, that channel's integration licence not purchased, credentials not defined on cp.sambapos.com, no internet connection (KB 6.25 s1.0; identically in 6.16/6.17/6.19). Go Order Jetrik Settings also offers 'Popup In New Orders'. Shortfall: the indicator is one aggregate flag, not per-channel health; no failed or rejected injection is logged, listed or alerted on; and the documented failure mode for a mismatched item is silent - an order for a product that exists on the marketplace menu but not in SambaPOS is dropped into the operator-nominated Default Category, with a note warning that these products must be manually added to the relevant print jobs or they will not reach a printer. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-08
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
The page claims customers can "check the status of their orders, track the delivery, and know when to expect their food," and that the system sends "delivery notifications ... via SMS and email," but this is a marketing claim with no KB article describing a branded tracking page, its domain, or the order/driver state it is driven by. https://sambapos.com/delivery/ · retrieved 2026-08-04
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
KB 4.12 (English, MODIFIED 2023-02-13; the Turkish twin's 2026-08-24 stamp is part of the 288-document bulk re-save and carries no freshness). The Advanced Delivery Service is a two-column state machine with no duration anywhere: "Orders of selected customer will be seen in the Waiting Orders column, if you assign a deliverer for that order, it will be moved to Delivered Orders column." Its object list is closed by its own uninstall section, "8. Uninstalling Advanced Delivery Service Implementation from SambaPOS", enumerating 8.1 Actions, 8.2 Rules, 8.3 Entity Screens, 8.4 Entities, 8.5 Entity Types, 8.6 Ticket Types and 8.7 Automation Commands - no timer, duration field or load input among them. The other in-house guest-facing checkout, the Jetrik panel, is enumerated screen by screen in KB 6.25 with no promise-time surface, and Nav Core (KB 6.52) takes a Google or TomTom key to geocode and map an address while exposing no drive-time value to the ticket. I weighed the undocumented GoOrder USA dashboard, which the vendor says tracks prep times, and hold that it does not reopen this cell: that is after-the-fact analytics, and on marketplace channels the guest-facing promise belongs to the marketplace, not to SambaPOS. https://kb.sambapos.com/en/4-12-advanced-delivery-service-implementation-v5-2-3/ · retrieved 2026-09-05 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
Documented: 'Possible reasons for displaying the Go Order Working phrase as Go Order Not Working: ... There might not be a proper internet connection' (KB 6.25 s1.0, repeated in the Yemek Sepeti, Trendyol and Getir articles), so the vendor states plainly that online/marketplace delivery intake stops during an outage. Documented for a related module: the Android Mobile Client 'you need to have internet for setup; you don't need internet after setup' (KB 8.1). Shortfall: no document states what happens to in-house delivery during an outage - the phone/Caller ID order path (KB 3.6, 4.5), deliverer assignment and the Delivered Orders fast-payment settlement (KB 4.12) all run against the local SQL Server, but the KB never says so, and licence re-validation behaviour is contested elsewhere in this record. Cash delivery orders, driver assignment and driver settlement are each unaddressed. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-08
Digital ordering & guest-facing channels
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
The GloriaFood and Takeaway.com framing is withdrawn - GloriaFood is discontinued and no longer accepting new signups (gloriafood.com, 2026-08-09) and its KB articles are headed 'This product is no longer supported' - and the live answer is Jetrik. KB 6.25 documents it as a branded ordering channel: the restaurant settings screen sets 'how your restaurant's name and image will be displayed on the website and on the app', the menu is pushed from SambaPOS with a single click, and orders return into the POS through GO Order Jetrik with 'Auto Confirm' and 'Popup In New Orders'. It is licence-priced rather than commission-priced (Jetrik QR Menu, Starter and Growth packages bought in the cp.sambapos.com store under the V5 Pro licence; sambapos.com lists $99/yr), so there is no per-order marketplace commission. Shortfall: this is a separately licensed partner platform registered at reg.jetrik.com and administered at panel.jetrik.com, not a storefront SambaPOS itself ships; no custom-domain or own-URL support is documented; the home-page data flow is withheld from the QR Menu package; and payment types must be matched by hand between Jetrik and SambaPOS (6.25 s3.7.3). https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-09 adversarially verified
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
Announced by Tayfun (forum staff/admin badge, SambaPOS): 'Give your customers a fast ordering experience with iPhone and Android applications published under your name and logo... add online ordering features to your existing website, and if you do not have a website, start taking orders from your website with your own domain name.' RestaJet is a live, currently-listed SambaPOS integration (sambapos.com/en/integrations, retrieved 2026-08-08) with its own KB setup article (6.4). Shortfall: it is a third-party partner product, not SambaPOS software - it requires a RestaJet subscription plus a separately purchased SambaPOS-RestaJet Integration Licence on the same cp.sambapos.com account, the apps are built and published by RestaJet, and the source is a 2020 promotional post rather than product documentation. SambaPOS's own mobile apps (Mobile Client, GO Kiosk/GO Tablet, Android Caller ID) are all staff-facing. https://forum.sambapos.com/t/sambapos-restajet-online-ordering-system-campaign/21733 · retrieved 2026-08-08
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
Guest accounts exist on the vendor-sold direct ordering channel; card-on-file and reorder do not. KB 6.25 documents the Jetrik panel screen by screen: '3.9. Customers - You can view your registered customers on this screen', a Loyalty section ('3.5.1 ... activate the Reward option', '3.5.2 Points ... follow your customer's Points status') and Payment screens including Payment Methods and a Paynet online-payment account, with orders injected into SambaPOS as tickets via GO Order Jetrik. Jetrik is sold as a SambaPOS SKU (sambapos.com/products/, purchased in the cp.sambapos.com store and licensed under the V5 Pro main licence) and jetrik.com/features markets a Personalized URL, Custom Domain, Instant Payment and Integrated Loyalty. Shortfall: nothing documents a saved-address book, a tokenized card-on-file, or one-tap reorder of a previous order - neither KB 6.23/6.25 nor the Jetrik feature and pricing pages mention stored cards or reorder, and 'reorder', 'one-tap' and 'saved card' return zero hits across the KB dump. The SambaPOS-branded 'Jetrik QR Menu' tier is menu-only (KB 6.23: the panel data flow 'is not available in the Jetrik QR Menu package'), so ordering and payment require the higher Jetrik Standard/Pro tiers. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-09
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
KB 8.14 indexes and then walks the entire GO Office console that drives GO Kiosk and GO Tablet: device detail (name, greeting, delivery types, payment types, printer), Menu Edit, Menu List (open/close products), Menu Sorting, Payment Types, Settings (General, Kiosk - 'Category position and Order Tag Group visibility', Tablet, Kiosk Theme, Tablet Theme, Language), Advertising (Kiosk banners, Kiosk homepage ads, Tablet homepage ads) and Logs. There is no suggested-item, cross-sell, add-on prompt or recommendation setting anywhere in it; the only checkout-time prompt is Order Tag Group visibility, i.e. modifiers. KB 6.25 s3.1-3.10 enumerates the Jetrik panel the same way (Dashboard, Restaurant Setup, Services and Hours, Payment, Loyalty, Menu Setup, POS Pairing, Comments/Contacts, Customers, Orders) with no upsell section. Nothing in the 9. Reports section reports attach rate, and grepping the full 613-record en+tr KB dump for upsell/cross-sell/recommend/suggest returns no product feature. https://kb.sambapos.com/en/8-14-sambapos-go-kiosk-v2-configuration/ · retrieved 2026-08-08
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
KB 6.25 s3.3.5: 'Scheduled Orders Screen - If you offer your customers the ability to place Planned Orders, you can make the relevant settings here', sitting alongside Opening Hours and an out-of-hours appearance screen in the Jetrik panel that feeds orders into SambaPOS. Shortfall: future/scheduled ordering is confirmed but throttling is not - the article gives that screen one line without enumerating its settings, and no per-daypart or per-slot capacity limit, item cap, or automatic slot closure when the kitchen saturates is documented for Jetrik, GO Kiosk (KB 8.14 GO Office settings) or the Go Order GloriaFood module (KB 6.29). Scheduling is also channel-side: SambaPOS itself has no future-order queue in the delivery implementation (KB 4.12). https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-08
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
One flow, three of four modes. The Jetrik panel documented in KB 6.25 has a single Services and Hours section with '3.3.1. Pickup Screen', '3.3.2. Delivery Screen', '3.3.3. Dine In Screen' and Opening Hours, plus '3.2.4. Tables Screen - you can download the QR Codes for your tables', and the SambaPOS-side GO Order Jetrik Settings map each to its own Delivery/Pickup/Dine In Ticket Type and Department Type (1.3.1.a), so pickup, delivery and guest-facing QR dine-in run through one channel into one ticket stream. Shortfall: curbside is not a mode here - 'curbside' returns zero hits across the KB in both languages and survives only as a GO Kiosk marketing line ('Drive Thru, Curbside Pickup, and More' on sambapos.com/drive-thru-pos/), with no arrival check-in described anywhere; and mode-specific fees and prep timing are undocumented - the panel has one Taxes screen ('you can set Tax and Service Charges', 3.2.5) with no per-mode fee, and the GO Order Jetrik 'Calculation Settings' section is given one line ('Fill the related fields accordingly') without enumerating what it holds. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-09
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
Jetrik QR Menu plus GO Tablet cover scan-to-view and tablet self-order at table; scan-to-pay closing an existing POS check is not documented. https://sambapos.com/jetrik-qr-menu/ · retrieved 2026-08-01
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
GO Kiosk runs the SambaPOS menu with self-service payment; no published accessibility conformance. https://sambapos.com/sambapos-go-kiosk/ · 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
The vendor's only direct digital ordering channel is Jetrik, and its two setup documents enumerate it exhaustively: KB 6.23 and KB 6.25 walk every screen of the Jetrik panel (Restaurant Setup, Tables, Taxes, Pickup/Delivery/Dine In, Opening Hours, Scheduled Orders, Payments, Payment Methods, Paynet, Loyalty, Menu Setup, POS Pairing including the 'Payment Types Pairing Screen', Comments, Customers, Orders) and every SambaPOS-side GO Order Jetrik setting, and none of them is a shared or multi-participant cart. There is no shareable order link for several people to add their own items to, no per-person or total spend cap and no split payment on the digital channel; the only ordering identities the panel knows are one registered customer per order and one table. The marketplace paths (Getir, Yemeksepeti, Trendyol, Migros, GoOrder USA) inject single completed orders as tickets and offer nothing of the kind either. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-09
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
KB 6.25 (English, MODIFIED 2023-11-16) enumerates the whole "3.3. Services and Hours" section of the vendor's own ordering panel as a closed set of three service types: "3.3.1. Pickup Screen", "3.3.2. Delivery Screen", "3.3.3. Dine In Screen", followed by "3.3.4. Opening Hours Screen" and "3.3.5. Scheduled Orders Screen", where scheduled means a future-dated ordinary order - "If you offer your customers the ability to place Planned Orders, you can make the relevant settings here." - not a catering flow with minimums, lead-time rules, quotes, deposits or invoice terms. Absence is measurable on this host (fabricated slugs 404 at a fixed byte length), and the vendor markets thirteen dedicated verticals on sambapos.com - bars-and-nightclubs, cafe-bakery, casual-dining, drive-thru, fast-food, fine-dining, food-truck, full-service, ghost-kitchen, pizza, pool-aquapark, quick-service, table-service - with no catering vertical among them. Corpus-wide the string catering occurs in only two documents, neither a feature. A vendor that markets every vertical it serves is a would-mention-it surface for this. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-09-05 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
KB 4.5 (English, MODIFIED 2018-03-12). The entire inbound-telephony story is Caller ID popping a customer entity so a human can key the order: "After making connection and necessary configurations on SambaPOS, Caller Id becomes usable for delivery service." and, for an unrecognised number, the popup redirects the user to the entity screen to create the customer by hand. The same shape recurs in KB 8.5 and 8.23 (Android Caller ID), 3.6 device setup naming CIDShow, Hugin boxes and Conexant modems, and 4.56 and 4.92 call logging. Measured zero-hit across all 958 documents in both languages for yapay zeka, sesli siparis, artificial intelligence, machine learning and chatbot; every occurrence of the substring voice is inside invoice. No AI or voice partner appears on sambapos.com/integrations/ or sambapos.com/tr/entegrasyonlar/, and section 6 of the KB is payment terminals, fiscal devices, GloriaFood, RestaJet, takeaway.com, Shipday, 7shifts, Jetrik and Nav Core. An exhaustive configuration manual plus a per-partner integrations page is a would-mention-it surface, and absence is measurable on this host. https://kb.sambapos.com/en/4-5-how-to-use-caller-id-for-delivery-service/ · retrieved 2026-09-05 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
sambapos.com/drive-thru-pos/ (English, grade C, MODIFIED 2023-10-11). The vendor's own dedicated drive-thru page lists as a Traditional Drive Thru Limitation: "Customers can only order via speakers and receivers placed in the drive thru window." Its Drive Thru Transformation answer to that limitation is digital ordering by web and mobile plus the GO Kiosk for self-service - not AI voice in the lane. A vendor selling lane voice AI would sell it precisely here, and instead it sells kiosk. Corroborated by a measured zero across all 958 documents in both languages for yapay zeka, sesli siparis, artificial intelligence and machine learning, and by the absence of any lane or speaker-post article anywhere in the KB. GO Kiosk is itself a separately priced add-on (KB 8.6, 8.14, 8.24), not V5 Pro. https://sambapos.com/drive-thru-pos/ · retrieved 2026-09-05 adversarially verified
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
KB 4.35 (English, MODIFIED 2019-03-26; Turkish twin 4-35-sambaposda-sms-gonderme-uygulamasi-nasil-yapilir). This is the whole messaging surface and it is a URL Printer firing at a gateway the operator supplies: "http://api.center.com/v1/send-sms/get/?username=username&password=password&text=@message@&receipents=@number@&sender=Company Name". SambaPOS is an HTTP client using the operator's own credentials; there is no listener, no inbound message endpoint, no keyword or short-code handling and no chat channel of any kind. The only inbound telephony in the product is Caller ID (KB 4.5), which reads a calling number rather than a message. RULING ON THE COORDINATOR'S QUESTION: this cell is about inbound ordering specifically, so a bring-your-own outbound gateway does not part-satisfy it and does not lift the cell to partial. Across the corpus SMS occurs in only seven documents - KB 4.35 in each language plus five sambapos.com marketing pages - all promising notifications rather than order intake. https://kb.sambapos.com/en/4-35-how-to-apply-sms-sending-implementation-on-sambapos/ · retrieved 2026-09-05 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
KB 6.25 (English, MODIFIED 2023-11-16). Order with Google would have to be provisioned in the vendor's own ordering panel, and that panel is enumerated screen by screen with no such surface: Dashboard, Restaurant Setup (Main Information, Location, Cuisine Selection, Tables, Taxes), then "3.3. Services and Hours" comprising "3.3.1. Pickup Screen", "3.3.2. Delivery Screen", "3.3.3. Dine In Screen", "3.3.4. Opening Hours Screen" and "3.3.5. Scheduled Orders Screen", then Payment, Rewards and Comments. No Google Business Profile connection, no ordering-link provisioning step, no place-card surface. Measured zero-hit across all 958 documents in both languages for the phrases Order with Google and Google Business Profile; every occurrence of Google is a Maps or TomTom API key for Nav Core, Google DNS in a static-IP how-to, Google Drive as a backup target, Google Play Services as an Android prerequisite, or Google Pay inside a payment partner's method list. Neither sambapos.com/integrations/ nor sambapos.com/tr/entegrasyonlar/, which enumerate the online-ordering partners individually, carries a Google entry. Jetrik is in any case a separately licensed add-on. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-09-05 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
KB 6.25 (English, MODIFIED 2023-11-16). Same structural argument as the Google cell: an Apple Business Connect place card would need a listing-provisioning surface, and the vendor's own ordering panel is enumerated exhaustively - Dashboard, Restaurant Setup, then "3.3. Services and Hours" comprising "3.3.1. Pickup Screen", "3.3.2. Delivery Screen", "3.3.3. Dine In Screen", "3.3.4. Opening Hours Screen" and "3.3.5. Scheduled Orders Screen", then Payment, Rewards and Comments - and has none. Measured zero-hit across all 958 documents in both languages for Apple Business Connect. Apple occurs only as a tablet OS prerequisite for GO Tablet and GO Kiosk, as App Store download buttons for the Mobile Client, CDS, KDS and Metrik apps, and as Apple Pay inside payment-partner method lists, where the subject is the processor. SambaPOS's digital ordering is uniformly partner-hosted and separately licensed. Noted for the record: 61% of the other 44 records left this cell unknown; I keep no only because absence is measurable on this host and the partner list is enumerated per-partner on both marketing trees. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-09-05 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
KB 6.25 s3.5 gives the Jetrik ordering channel a Loyalty section - 'Settings Screen: You can activate the Reward option for your restaurant here', 'Points Screen: You can follow your customer's Points status here', 'Transactions Screen: You can follow the activity status by selecting a user here' - so accrual and redemption do exist inside the first-party-branded digital flow. Shortfall: it is not the same guest identity as in-store. Jetrik holds its own registered customers (s3.9) and its own points ledger, and the POS Pairing section (s3.7) pairs only Menu, Order Tags and Payment Types with SambaPOS - there is no customer or loyalty pairing screen. The POS-side loyalty story is a separate, operator-built implementation (KB 4.27 Basic Loyalty Points, a Loyalty Card entity type with a Points custom field driven by automation) or SambaCard (KB 2.4.9, an account-backed card entity), neither of which is documented as syncing with Jetrik. GO Kiosk/GO Tablet have no loyalty surface at all in the GO Office console (KB 8.14). https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-08
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
The published product catalogue is complete and enumerable — V5 Pro, Mobile Client, GO Kiosk, GO Tablet, Jetrik QR Menu, Metrik, KDS, Android CID, Neptune — and contains no guest subscription, membership or recurring-billing product; the integrations page lists none either. The platform additionally has no native payment processing and no guest-account infrastructure to bill a recurring entitlement against. https://sambapos.com/products/ · retrieved 2026-08-03
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
The documented mechanism is the opposite of define-once parity. To take Jetrik orders the operator must build a dedicated 'Jetrik Discount' account, 'Jetrik Discount Transaction' account transaction type, a 'Jetrik Discount' calculation type (Fixed Amount, Decrease Amount) and a calculation selector (KB 6.25 s1.2.1-1.2.4) purely to receive the discount Jetrik already computed; the Yemek Sepeti, Trendyol and Getir modules each require their own equivalent (Joker Iskonto, 'TY Indirim' account/transaction/calculation/selector, 'GY Indirim' likewise - KB 6.16 s7.1, 6.17 s5, 6.19 s5). POS-side discounts are separately authored objects again - percentage discount at the terminal (KB 5.4.6), ticket-tag and order-tag discounts (2.4.7.c, 2.3.5.i/j), automatic customer-group discounts (2.4.17) and the promotion recipes in section 4 (4.4, 4.10, 4.75) - each a calculation type or automation rule that exists only in SambaPOS. The GO Office console that drives GO Kiosk and GO Tablet has no discount, coupon or offer configuration anywhere in its enumerated screens (KB 8.14). There is no single offer object and consequently no channel-eligibility control. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-08
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
Guest records live in the operator's own on-premise Microsoft SQL Server database; bulk export needs no vendor approval or fee. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
330th, MOVED OFF unknown. CLAIM: digital checkout uses vendor-hosted fields or a hosted payment page, with the vendor publishing PCI DSS 4.0 compliance (incl. the March 2025 client-side script-integrity requirements) and supporting 3DS. VERDICT: no - the vendor operates no digital checkout of its own, and publishes neither the compliance statement nor 3DS. EVIDENCE: KB 6.29 Go Order GloriaFood Integration (en, the US marketplace path) settles digital orders INSIDE SambaPOS on the merchant's own tenders, not on any SambaPOS-hosted page: the vendor's own screenshot of the GO Order sale screen (https://kb.sambapos.com/wp-content/uploads/2024/12/GloriaFood-Go-Order-59.jpg) shows a GloriaFood PickUp order with "Order State: Unpaid" and the buttons Delivery To Customer, Cancel, Display Ticket, Print, Cash, Credit Card, Voucher, Customer Account; the module's Payment Methods setting is the same four local tenders (https://kb.sambapos.com/wp-content/uploads/2024/12/GloriaFood-Go-Order-61.jpg), and "Click on Delivery to Customer button to give the order to customer and get the payment accordingly." Where a card is taken it goes to a physical PIN pad (KB 6.31: the transaction "will be conducted by the PinPad"). Every hosted checkout in the record belongs to a partner - Jetrik (KB 6.25 s3.4 places Payments/Payment Methods and the Paynet activation inside the Jetrik panel), GloriaFood and RestaJet host their own. So no conjunct is met by SambaPOS: no vendor-hosted fields, no published PCI DSS 4.0 statement, no 3DS. BOUND/CONTROLS: the bound 958-document two-host census (see payments-p2pe-pci4 for how it is bound) returns PCI 0, DSS 0, 3D Secure 0, 3DS 0, SCA 0 in both languages, and the same controls over the 9 GO Order + KDS articles (72,644 bytes) return PCI 0, P2PE 0, 3DS 0, encrypt 0 with positive control SambaPOS 259. Retrieved 2026-09-18. https://kb.sambapos.com/en/6-29-go-order-gloriafood-integration/ · retrieved 2026-09-18 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
Fees reach the digital channel and post back into the POS, but none of this is surcharge compliance. The Jetrik panel has '3.2.5. Taxes Screen - On this screen you can set Tax and Service Charges', a Payment Methods screen and a 'Payment Types Pairing Screen' matching Jetrik payment types to SambaPOS ones, and KB 6.25 s1.2 has the integrator create a Jetrik Discount account, account transaction type, calculation type and calculation selector so the channel's own money movements land on the ticket through SambaPOS's calculation engine. Shortfall, and it is most of the claim: the digital fee is configured separately in the Jetrik panel rather than inheriting the POS configuration; there is no card-surcharge or dual-pricing feature on either side, only hand-built calculation types (the vendor forum's credit-card surcharge is a user-built Update Ticket Calculation button, Bob_be 2020-01-29, and it misapplies to the total rather than the owing amount); and no source describes guest-facing surcharge disclosure, jurisdictional surcharge prohibitions or card-brand rules at all. GO Kiosk documents no fee configuration. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-09
Guest data, loyalty & marketing
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
Customer Accounts holds transaction/debit-credit history, but the documentation covers "basic account management within a single location context," and there is no dedup/merge behavior documented across in-store, digital-ordering, and kiosk channels. https://kb.sambapos.com/en/5-4-8-c-customer-accounts-management/ · retrieved 2026-08-04
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
Marketplace orders arrive with usable guest identity but never become a guest profile. GoOrder lands the platform's customer data on the ticket as ticket-data tags, documented per provider: the Yemeksepeti tag list (KB 4.79) publishes {TICKET DATA:YSFirstName}, {TICKET DATA:YSLastName}, {TICKET DATA:YSMobilePhone} and eighteen delivery-address fields down to latitude and longitude, and the Trendyol list (KB 4.80) adds {TICKET DATA:TYCustomerId} alongside name and delivery phone; equivalents exist for Getir (4.87) and Migros (4.85). Shortfall: nothing creates or matches a Customers entity. The end-to-end GoOrder setup guide (KB 6.29, GloriaFood) builds Deliverer entities, a Delivery ticket type, delivery-fee accounts and print jobs and contains no customer-mapping step, and the Yemeksepeti guide's own customer section describes an operator pressing the New Customer button at the POS by hand. The identity is therefore print- and dispatch-time text, with no visit history, no loyalty accrual and no recognition on a later order unless the operator builds it with automation. The US providers named in the claim - DoorDash, Uber Eats and Grubhub - have no published tag list at all; sambapos.com/goorder-usa/ is a marketing page describing order transfer, tracking and reporting. https://kb.sambapos.com/4-79-go-order-yemek-sepeti-entegrasyonu-yazici-tagleri/ · retrieved 2026-08-09
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
Loyalty is typically built from customer entities, account balances and automation rules rather than shipped preconfigured; Extra360 is the named third-party loyalty integration. https://sambapos.com/integrations/ · retrieved 2026-08-01
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
KB 2.4.17 (English, MODIFIED 2018-12-19). Tiers exist only as an operator-assembled static construct: a String custom field on the Customers entity, "Custom Field Name: Discount Rate", with hand-typed values "Neighbour 5%,Regular 8%,Special 10%,Staff 15%", and four rules each gated by a Custom Constraint on that customer custom data ("Entity Type Name | Equals | Customers") applying the matching Calculation Type when the customer is selected. The band is set by hand at registration: no spend or visit threshold, no rolling window, no automatic promotion or demotion. The two shipped loyalty articles are flat (4.27 Basic Loyalty Points, 2.4.9 SambaCard) and the Jetrik add-on's Rewards section is a toggle plus Points and Transactions screens. The vendor does claim tiers in marketing - sambapos.com/delivery/ (grade C, 2022-12-08) invites the reader to organize a tiered-loyalty program, and the Turkish twin sambapos.com/tr/paket-servis/ carries the same sentence; both check out on their own pages, and the checker's flags on them were misattribution and diacritics artefacts. On 2026-07-28 the vendor also announced an unshipped first-party loyalty platform advertising membership tiers, marked Coming Soon (sambapos.com/sambapos-extra360-integration/); that is recorded as pending, not as evidence either way. Partial on the shipped manual mechanism. https://kb.sambapos.com/en/2-4-17-how-to-make-automatic-discount-for-customer-groups/ · retrieved 2026-09-05 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
sambapos.com/tr/ (Turkish, grade C, MODIFIED 2024-12-16). The product-level offline claim is first-party and explicit: "SambaPOS, çalışmak için internete ihtiyaç duymaz. İnternetiniz kesilse bile güvenle çalışmaya devam edersiniz." The English home page carries only the shorter half. Native loyalty sits inside that boundary by construction rather than by statement: KB 4.27's points are an entity custom field and 2.4.9 SambaCard is an account balance, both in the local MSSQL instance the terminals share (2.1.6), so nothing crosses the internet to earn or redeem. What is not documented in either language is loyalty-specific connectivity behaviour - no queue, retry or reconciliation statement anywhere, and nothing about the cloud-backed loyalty paths (Jetrik Rewards in 6.25, RestaJet Reward Point mapping in 6.4, the announced Extra360 platform) which do depend on a link. Partial: the product-level claim is first-party, the loyalty-level behaviour is inference. https://sambapos.com/tr/ · retrieved 2026-09-05 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
KB 2.3.10.b (English, MODIFIED 2018-04-09) gives the fullest published field list of the Calculation Type editor, the single object behind every discount, promotion, service charge and tip. Its fields are exactly "Template Name:", "Account Transaction Type:", "Calculation Method:", "Rate or Amount:", "Max Amount:", "Rounding:", "Tax Included:", "Decrease Amount:" and "Use Plain Sum:" - the last of which batch B's list omitted. There is no combinable-versus-exclusive flag, no priority or sequence field and no mutual-exclusion group, and 2.3.10.a, 2.4.7.c, 4.59, 4.63, 4.70, 4.78 and the Turkish 4-59 and 4-63 twins reproduce the same short set; KB 4.59 positively lands three separate Calculation Types on one ticket with nothing offered to rank or suppress them. But the engine that fires them is rule-driven with Custom Constraints - KB 2.4.17 gates each of four discount rules on a customer custom-data value so that only one fires - which means mutual exclusion and precedence are expressible as constraints an operator writes. That is the documented automation engine doing the job, which by the standing rule is partial with the mechanism named. Residue: the KB never states the order in which several calculations are applied to one ticket. https://kb.sambapos.com/en/2-3-10-b-how-to-set-bill-automatic-rounding/ · retrieved 2026-09-05 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
KB 2.4.17 (English, MODIFIED 2018-12-19). Targeting is operator-assembled and documented: audience membership is a hand-set custom field on the customer entity, "Custom Field Name: Discount Rate" with values "Neighbour 5%,Regular 8%,Special 10%,Staff 15%", and each offer is a rule gated on it ("Entity Type Name | Equals | Customers" plus a Custom Data constraint on the band) firing the matching Calculation Type when the customer is selected on the ticket; KB 4.15 builds a first-visit gift the same way. There is no list, no audience builder, no send job and no offer object, and the only outbound channel is KB 4.35, where the operator supplies their own SMS gateway URL and credentials. The vendor does claim an audience distinction in marketing (sambapos.com/delivery/, grade C, 2022-12-08, under Promotions and Campaigns), and the Turkish twin carries it, but that is a brochure sentence and the verdict does not rest on it. Partial: a real rule-and-custom-field mechanism over a manually maintained group, plus a bring-your-own gateway. https://kb.sambapos.com/en/2-4-17-how-to-make-automatic-discount-for-customer-groups/ · retrieved 2026-09-05 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
KB 9.1.2 (English, MODIFIED 2018-07-05). No packaged RFM or lifecycle report ships: the base install's six reports are Work Period, Item Sales, Cash Transactions, Inventory Transaction, Inventory and Cost (English 5.5.5.a, 2018-04-06), and section 9's additions are Item Sales by Product Tag, Void and Gift, Item Group Sales by Ticket Type, Open Tickets and Remaining Balanced Customers; none computes recency, frequency, monetary value or a lifecycle label, and RFM is a measured zero-hit across all 958 documents in both languages. What converts this from no to partial is that ticket, order, payment and customer data all sit in the merchant's own SQL Server and the vendor documents registering arbitrary SQL against it: "You can display result of an SQL Script in custom reports.", created under "Management > Automation > Scripts" and referenced from a report template by an @@Handler name. Customers can also be exported to Excel (4.94). RULING ON THE COMING-SOON QUESTION, applied across this batch: on 2026-07-28 - a genuine dispersed date, not the 2026-08-24 bulk re-save - the vendor announced Extra360, a first-party loyalty platform listing Customer Segmentation and marked Coming Soon (sambapos.com/sambapos-extra360-integration/). An announced-but-unshipped capability cannot carry yes or partial by itself, and it positively forbids no, because no asserts absence from the offering while an announcement is evidence of pendency. It is recorded here as pending, never as support. https://kb.sambapos.com/en/9-1-2-creating-custom-reports-with-sql/ · retrieved 2026-09-05 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
sambapos.com/delivery/ (English, grade C, MODIFIED 2022-12-08). The vendor makes the lifecycle claim itself: "Birthdays and Other Special Occasions Make your customers happy by sending congratulatory messages along with discount codes on birthdays, anniversaries, festivals, and other occasions." and "Prompt Notifications Send payment confirmations, delivery notifications, and order status via SMS and email." The Turkish twin sambapos.com/tr/paket-servis/ carries both and adds a phrase the English drops - the messages go to customers who have given permission. Underneath there is no campaign object and no scheduler over customer state: what exists is the generic Actions and Rules engine plus hand-built recipes (KB 4.15, a one-time promotional product for each new customer; 2.4.17, group discount on customer selection) and KB 4.35's operator-supplied SMS gateway as the only outbound path; the only time-driven jobs documented are work-period tasks such as 2.4.12.e emailing reports at end of day. Partial, with the qualifier that everything under the claim is a customer-built automation rather than a shipped lifecycle campaign product. https://sambapos.com/delivery/ · retrieved 2026-09-05 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
Both channels send from inside the product, but as event automation rather than campaigns. Email is a first-class action type: 2.4.12.e configures Action Type 'Send E-Mail' with SMTP Server, SMTP User, SMTP Password, SMTP Port, To E-mail Address, CC, Subject and an attachment, fired from a rule - so the earlier note's 'no native email campaign tool found' understated what exists. SMS has two paths: the URL Printer recipe of 4.35 against a gateway the operator supplies, and a native Twilio action added in 5.5.8 ('Twilio SMS Integration added (An action added for this)'), which the knowledge base never documents. The shortfall, and it is the whole shortfall, is that there is no campaign layer on either channel - no audience segmentation or list building, no scheduling, no template or campaign management, no delivery or open reporting, and no opt-out handling. Every send is one message triggered by a rule, addressed from a field such as {ENTITY DATA:Customer:Phone} or a typed address, over credentials and a sending account the operator owns. https://kb.sambapos.com/en/2-4-12-e-how-to-send-reports-as-email-at-end-of-work-period/ · retrieved 2026-08-08
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
sambapos.com/tr/paket-servis/ (Turkish, grade C, MODIFIED 2022-08-31). The vendor states the send is permission-scoped: "Doğum günleri, yıl dönümleri, festivaller ve diğer etkinliklerde indirim kodlarıyla birlikte izni olan müşterilere tebrik mesajları göndererek müşterilerinizi mutlu edin." The English twin drops the permission phrase entirely; the checker's NOWHERE flag on this string was a diacritics false positive. No consent object ships: the Customers entity's documented custom-field surface (2.2.6, 2.4.17, 4.48, 4.77, 6.52) has no consent flag, timestamp, source or per-channel state; KB 4.35 fires a print job at the operator's own gateway with no pre-send check and no suppression list; and there is no inbound path by which a STOP could reach SambaPOS, so revocation necessarily sits with the operator's gateway. Measured zero-hit in both languages for KVKK, GDPR, opt-in, opt-out and unsubscribe. What makes this partial rather than absent is the documented mechanism used everywhere else in the product: consent modelled as a Customers custom field and enforced as a rule Custom Constraint on the send, exactly the pattern KB 2.4.17 demonstrates for discount bands. sambapos.com/tr/kisisel-veriler/ is Ozgu Yazilim's own personal-data notice as controller of its business contacts, not a POS feature, and is not counted here. https://sambapos.com/tr/paket-servis/ · retrieved 2026-09-05 adversarially verified
Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.
guest-loyalty-10dlc-registration
KB 4.35 (English, MODIFIED 2019-03-26; Turkish twin 4-35-sambaposda-sms-gonderme-uygulamasi-nasil-yapilir). The architecture closes the question rather than merely failing to mention it: SambaPOS is an HTTP client against an endpoint the operator supplies with the operator's own credentials - "http://api.center.com/v1/send-sms/get/?username=username&password=password&text=@message@&receipents=@number@&sender=Company Name" - so the sending identity, the aggregator relationship and any A2P carrier registration are entirely the operator's, and the vendor holds nothing it could register. Measured zero-hit across all 958 documents in both languages for 10DLC, A2P and Twilio. Applicability is genuine rather than moot: the vendor sells into the US (GoOrder USA at 49 USD monthly, plus the Global Payments and Dejavoo integrations), so the subject is fair to score, and the answer is that the vendor provides nothing. Residue carried from the prior pass and not visible in this corpus: the 5.5.8 release note announcing a native Twilio SMS action has no KB article in either language, which if anything confirms that no registration guidance is published for it. https://kb.sambapos.com/en/4-35-how-to-apply-sms-sending-implementation-on-sambapos/ · retrieved 2026-09-05 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
KB 9.1.2 (English, MODIFIED 2018-07-05). No shipped attribution report exists: the base install's six reports (English 5.5.5.a, 2018-04-06) and section 9's additions include nothing that ties a redeemed offer to incremental spend, a control group or a send, and there is no campaign or offer object in the product - promotions are per-site Calculation Types and automation rules (2.4.7.a, 2.4.7.c, 4.4, 4.10, 4.15, 4.59, 4.63, 4.75 and the Turkish 4-59 and 4-63 twins). What is buildable is redemption reporting: discount amounts land in named accounts (Jetrik Discount, Loyalty Discount, TY Indirim) in the merchant's own SQL Server, and the vendor documents registering arbitrary SQL against it - "You can display result of an SQL Script in custom reports.", authored under "Management > Automation > Scripts". So redemption counts and discount value per offer are an operator build, while incrementality and control-group measurement remain impossible because no send or exposure is ever recorded: the only outbound path, KB 4.35, is a fire-and-forget print job. Partial with that split stated. The marketing side does claim campaigns exist (sambapos.com/delivery/), which is not relied on here. https://kb.sambapos.com/en/9-1-2-creating-custom-reports-with-sql/ · retrieved 2026-09-05 adversarially verified
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
Direct SQL access to the merchant-hosted database gives unrestricted self-serve export of guest and transaction history at no fee. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
sambapos.com/food-truck/ (English, grade C, MODIFIED 2023-10-11), under Customer Reporting: "Gather customer data like their name, phone, address, etc. Receive feedback from your customers during the check out process. Track their experience with colour-coded ratings to manage your performance." That is a first-party capture claim and it is the only one - I grepped the exact strings and they occur in exactly one document of 958, on one of a family of templated industry landing pages, and no KB article in either language configures it. Routing is absent entirely: measured zero-hit in both languages for anket, NPS, TripAdvisor and puanlama, nothing that routes by score, escalates a low rating or pushes to a public review site, and the only adjacent surface is passive - the Jetrik add-on's Comments screen in KB 6.25, which shows comments about the restaurant with no request trigger. Partial on capture; routing is not evidenced at all. https://sambapos.com/food-truck/ · retrieved 2026-09-05 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
Nothing in SambaPOS issues or redeems a referral. The vendor's position is that loyalty is not shipped as a product at all - 'This will not be a pre-made solution... The reason it's not pre-built is many people handle it differently' (JTRTech [STAFF], forum t/13833) - and what is published are three operator-assembled recipes: KB 4.27 Basic Loyalty Points (accrual at a configured points-per-currency rate, redemption as a discount), 2.4.9 SambaCard (a card entity backed by an account) and 4.31 Gift Certificates. None generates a per-guest code or link, none attributes a referred guest's first order, and none pays a two-sided reward; the data model is an entity custom field plus an account, with no referrer-referee link to hold. The nine-SKU product catalogue and the integrations page contain no referral or marketing-automation product for the mechanic to live in, and the staff release series 5.1.47-5.7.28 announces no referral or campaign feature. https://kb.sambapos.com/en/4-27-basic-loyalty-points-implementation/ · retrieved 2026-08-09
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
KB 2.4.9 (English, MODIFIED 2018-06-06; Turkish twin 2-4-9-sadakat-karti-sambakart-uygulamasi). The card model is a number-identified entity backed by an account: "It is necessary to create a different type of account for customer cards. So that it will be easier to track customer accounts and customer cards separately." The card is selected on the ticket by scanning or keying its number, and KB 4.27's Loyalty Card is likewise an entity with a Points custom field; delivery format is a printed barcode or QR from a slip or barcode printer (2.4.8.a, 2.4.8.b). There is no push-updatable balance object anywhere. Measured zero-hit across all 958 documents in both languages for pkpass, PassKit, Apple Wallet and Google Wallet. RULING ON THE COMING-SOON DOCTRINE FOR THIS CELL: it does not reach here. Extra360 (announced 2026-07-28, marked Coming Soon) advertises a stored-value digital wallet balance and a loyalty program, not a pkpass or Google Wallet object; the doctrine bars no only where the announcement's own words cover the cell's subject, and these do not. Global Payments' digital wallets phrase is Apple Pay and Google Pay as a card-present tender, subject the processor. The KB enumerates card creation and printing in full, so this is a would-mention-it surface and the zero converts. https://kb.sambapos.com/en/2-4-9-how-to-set-loyalty-card-sambacard/ · retrieved 2026-09-05 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
No guest DSAR tooling ships, and the vendor's own forum treats erasure as an operator problem. On t/28362 (2024) an operator handling a guest deletion request reports 'I Know we cant delete Entity attached to ticket', says the capability 'been requested earlier for future pos updates, not sure this happens', and is reduced to editing names and phone numbers by hand; the SambaPOS staff reply (markjw) argues the operator is entitled to retain the data and names no tool. On t/23357 the staff answer to the same need is to build one - JTRTech [STAFF]: 'Sure this could be done with automation, its only update entity data' - and a request that the vendor implement anonymisation 'in one of the future releases' produced no product. Overwriting an entity's fields does not propagate to loyalty cards (KB 4.27), SambaCard accounts (2.4.9), ticket history or the account ledger. The only shipped guest-data instrument is KB 4.94's bulk 'How to Export Customer List in Excel Format', which has no per-subject scoping, and the staff release series 5.1.47-5.7.28 announces no consent, erasure, GDPR or KVKK tooling. https://forum.sambapos.com/t/customer-personal-data/28362 · retrieved 2026-08-09
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
There is no loyalty engine to enforce controls in, and the vendor states that as a design position: 'This will not be a pre-made solution. SambaPOS is not trying to be a pre-made fixed setup like other software... The reason it's not pre-built is many people handle it differently. Point set on specific products, points based on price. Also how points are reclaimed.' (JTRTech [STAFF], forum t/13833). Every documented loyalty or stored-value build is accordingly an operator-assembled recipe over entity custom fields and account transactions - KB 4.27 Basic Loyalty Points, 2.4.9 SambaCard, 4.31 Gift Certificates - so a point balance is a plain account line that any user holding the button can move. None of the three carries a redemption velocity limit, a manager-approval step on manual point adjustment, an employee self-redemption flag or a loyalty audit log. The only gating in 4.27 is UI state ('Visible States: LoyaltyDiscountButton=Available'), which hides a button rather than validating a transaction, and the staff release series 5.1.47-5.7.28 announces no loyalty module and no loyalty controls. https://kb.sambapos.com/en/4-27-basic-loyalty-points-implementation/ · retrieved 2026-08-09
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
KB 4.27 (English, MODIFIED 2020-04-24). Measured zero-hit across all 958 documents of both hosts in both languages for yapay zeka, makine ogrenme, machine learning and artificial intelligence. There is also nothing for a recommender to attach to: the offer surface is Calculation Types pressed at the terminal and rules keyed on a hand-set customer group - 4.27 builds the card by hand ("Entity Type: Loyalty Card", "Card Number: LC00", "Points: Currently there is no points in the Loyalty Card.") and applies the discount through an automation command named LC-Apply Loyalty Discount - with no offer object, no audience and no issuance channel beyond the operator's own SMS gateway (4.35). RULING ON THE COMING-SOON DOCTRINE FOR THIS CELL: Extra360 (announced 2026-07-28, Coming Soon) advertises personalized offers but uses no AI or machine-learning language anywhere, and the doctrine bars no only where the announcement's own words cover the cell's subject. Personalized is not AI-recommended, so the zero stands against an exhaustive step-by-step configuration manual on a host where absence is measurable. https://kb.sambapos.com/en/4-27-basic-loyalty-points-implementation/ · retrieved 2026-09-05 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
Gift certificates are supported only as a DIY tutorial ("it will be explained how to apply Gift Certificate Implementation") requiring the operator to manually build accounts, entity types, and automation rules — not a native shipped balance system — and cross-location redemption across brand locations is not addressed in the documentation. https://kb.sambapos.com/en/4-31-gift-certificates-sales-and-redemption-implementation/ · retrieved 2026-08-04
Labor & workforce
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
Researcher missed a shipped module. KB 8.13 'How to Configure Time Clock Module?' states the Time Clock module 'comes along SambaPOS 5.7.0 version' — i.e. in the base product, not an add-on SKU — and covers clock in/out, paid vs unpaid breaks, departments and roles with hourly wage per role, and reporting on hours. A vendor product page markets it separately. Genuine yes. https://kb.sambapos.com/en/8-13-how-to-configure-time-clock-module/ · 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
The punch is PIN-only and stores no image. KB 8.13 documents the flow as entering the PIN, pressing Clock In-Out and then Clock In, and screenshots of the shipped module confirm it unchanged: a PIN pad, a 'Select Your Role' dialog, a clock-out confirmation showing the time and the user's name, and a Time Clock Users screen whose columns are User Name, Name, Surname, Last Clock In and Last Clock Out over a punch list of Clock In, Clock Out and Work duration - no photo thumbnail, no verification column (forum topics 27548, 2023-10-09, and 28024, 2024-03-05). The 5.7.8 settings screen carries four checkboxes (Enable Time Clock, Force Users for Clockin Before Login, Declare Cash Tips, Enable Breaks) plus Break Mode, Payroll Options and Overtime Options, with no capture or biometric option, and no release note from 5.7.0 through 5.7.28 mentions a camera, photo or facial feature. SambaPOS documents no camera anywhere in its peripheral coverage either. https://kb.sambapos.com/en/8-13-how-to-configure-time-clock-module/ · retrieved 2026-08-08
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
SambaPOS keeps no per-terminal database. 2.1.6 tells the installer to open 'TCP/IP 1433 Port' inbound and outbound so terminals can reach the server's MSSQL, and requires the network be 'configured on the exact same IP group'; 8.1 adds 'Mobile Client doesn't work without MSSQL database' and 'Android device and SambaPOS Server must be in the same network and IP group'. A terminal cut off from the server therefore records nothing to reconcile, and the Time Clock module settings (8.13: Enable Time Clock, Force User for Clock in Before Login, Enable Breaks, Departments, Roles, Assignments) expose no offline or resync option. Forum topic 13944 'Offline feature' (Feb 2017) is an open request for exactly this; moderator JTRTech replied there is 'no option for now for offline mobile tablet use'. Distinct from internet loss, which does not affect the product (8.1: 'You don't need internet after setup'). https://kb.sambapos.com/en/2-1-6-how-to-run-sambapos-on-multiple-computers/ · retrieved 2026-08-08
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
User Roles with a Permissions list, including partial management permissions, restricting individual operations and screens per role. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Positively determined absent on SambaPOS's own forum. Asked why an admin-authorised void reports under the cashier's name, Jesse answered (2019-10-11): "Admin verification does not change who did the void. It is just to allow it. The void is still executed by user that's logged in." Admin PIN authorisation therefore gates the action without attributing it, which is precisely what this claim requires. The workarounds offered in-thread confirm the gap rather than close it: JTRTech's options were to restrict voids by role so the manager must log in under their own account, or to rebuild the PIN prompt with scripting and store the authoriser as an order state — 'not a quick simple setup', and a custom build rather than a shipped audit trail. https://forum.sambapos.com/t/admin-void-report-issues/20930 · retrieved 2026-08-03
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
No scheduling product in the catalogue; 7shifts is the documented labour-management integration, implying scheduling is outsourced. https://sambapos.com/integrations/ · retrieved 2026-08-01
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
Shortfall: nothing in SambaPOS generates staffing levels or labor hours. The 7shifts integration (6.45, updated 2026-03) syncs users, departments and roles, sends clock in/out to '7shifts side under Time Clocking > Pay Periods > Review' and sends sales so that 'Sales data will reflect to the 7shifts side under Reports > Actuals' - so the sales history reaches a labor-scheduling system, but the recommendation, if any, is 7shifts' and requires a separately purchased 7shifts Integration licence (cp.sambapos.com) plus a 7shifts subscription. SambaPOS's own reporting (section 9, Work Period / Item Sales / Cost reports) is retrospective only; 'forecast' appears in no KB article in either language. https://kb.sambapos.com/en/6-45-7shifts-integration/ · retrieved 2026-08-08
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
Shortfall: no shipped manager view. 9.1.8 lets a custom report be embedded in a custom entity screen via the Custom Report Viewer Widget, and the 'Widget displays reports in current work period by default'; there is a Refresh Custom Report Widget automation action (4.3), custom reports may contain arbitrary SQL (9.1.2), and Time Clock Assignments carry an hourly wage per user (8.13), so labor cost against live sales can be assembled. But the operator must author the SQL and the screen themselves - the packaged reports (Work Period, Item Sales, Cash Transactions, Cost) are end-of-period and none expresses labor as a percentage of sales. https://kb.sambapos.com/en/9-1-8-custom-report-viewer-widget/ · retrieved 2026-08-08
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
The overtime capability 5.7.8 added is pay computation, not prevention. A screenshot of the Time Clock Settings screen running 5.7.8 (forum topic 28024, posted 2024-03-05) shows 'Overtime Options' split into Hours ('Daily Hours', 24) and Rates ('Daily Overtime Rate', 100), sitting directly under Payroll Options (Payroll Type, period Start Date, Length); a second screenshot in the same thread shows the Time Clock Roles editor carrying 'Overtime Options > Rates: Daily Overtime Rate, Double Overtime Rate, Weekly Overtime Rate' per role. Those are pay multipliers applied over a payroll period. Neither the settings screen nor the documented clock-in path (enter PIN, Clock In-Out, 'Select Your Role', Clock In) offers an approaching-overtime warning or a block, and no release note from 5.7.0 through 5.7.28 mentions one; 5.7.22's 'UserClockIn and UserClockOut rules' merely expose clock events to the automation engine so an operator could build a warning themselves. Graded C because the module's current settings surface is only visible in a community screenshot: KB 8.13 still documents 5.7.0 and never mentions overtime, and kb.sambapos.com's own search for 'overtime' returns only the 2018 do-it-yourself article 4.14. https://forum.sambapos.com/t/time-clock-not-working-on-the-new-update-578/28024 · retrieved 2026-08-08
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
Break handling is one module-wide paid/unpaid setting. KB 8.13 documents it as 'Enable Breaks... If you select this check box your users will be seeing the Break Option. They can take a Break or Clock Out... it can be displayed whether the breaks will be Paid or non Paid', and a screenshot of the same screen running 5.7.8 (forum topic 28024, 2024-03-05) - a version whose settings surface has otherwise grown to include Declare Cash Tips, Payroll Options and Overtime Options - still shows exactly 'Enable Breaks' plus a single 'Break Mode: Paid' dropdown, so break handling has gained no structure since 5.7.0. The vendor's own Time Clock page describes the module as Break Management, Department Assignment, Role Assignments, Multi Department-Roll Capabilities and Custom Report Building. There is no per-state or per-jurisdiction rule set, no break-attestation prompt and no missed-break premium flag anywhere in the module, the 613-record KB dump or any release note through 5.7.28; when an operator raised federal break-audit exposure on the 5.7.0 release thread, the SambaPOS-side answer was that the module supports multiple breaks, paid or unpaid. https://kb.sambapos.com/en/8-13-how-to-configure-time-clock-module/ · retrieved 2026-08-08
Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.
labor-minor-labor-rules
Neither half of the claim has anywhere to live. Scheduling is not a SambaPOS function: it is handed to 7shifts, where the roster and pay periods sit ('Clock In and Clock Out data will reflect to the 7shifts side under Time Clocking > Pay Periods > Review', 6.45), and 5.7.26 records '7Shifts integration finalized'. Clock-in enforcement has no attribute to enforce against: the Time Clock settings screen running 5.7.8 (forum topic 28024, 2024-03-05) is Enable Time Clock, Force Users for Clockin Before Login, Declare Cash Tips, Enable Breaks, Break Mode, Payroll Options and Overtime Options; Departments are a name and a default flag; Roles are name, department, colour and overtime rates; Assignments add an hourly wage (8.13); and the Time Clock Users grid is User Name, Name, Surname, Last Clock In, Last Clock Out. No birthdate or age field exists, and no maximum-hours cap, prohibited time window or school-day rule appears in the module, in the 613-record KB dump or in any release note from 5.7.0 through 5.7.28. https://kb.sambapos.com/en/8-13-how-to-configure-time-clock-module/ · retrieved 2026-08-08
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
English KB 4.70 How to Add Tip Calculation (modified 2022-02-09) builds tip CAPTURE and nothing else, in four objects: an 'Account Name: Tip Account' of type Sales Account, an 'Account Transaction Type Name: Tip Transaction' debiting Sales Accounts and crediting Receivable Accounts, a calculation type whose 'Calculation Method: Fixed Amount' posts to it, and a Calculation Selector button headed Tip. Its Turkish twin 4.70 is the same four objects, and English 6.14 PaymentSense Dojo and 6.31 Quest repeat them for card tips. Nothing anywhere divides that account. Corpus-wide zero in both languages for tip pool, tip-out, bahsis dagitimi and bahsis paylasimi - the havuz hits are an aquapark case study and a document-type article. There is also no basis to divide by: English 4.6 pays staff through manual account transactions with no tip input, and the Time Clock assignment in 4.14 carries only an hourly wage, so no hours, sales, points or role weighting exists in the model. The vendor concedes the point in its own Turkish post sambapos.com/tr/bahsis-takibinin-onemi/ (2022-08-15), which says that merely seeing how much tip was left for which member of staff requires the necessary customisations to be applied - so per-staff attribution, let alone automatic pooling per shift, is not shipped. Table-stakes cell, not met. https://kb.sambapos.com/en/4-70-how-to-add-tip-calculation/ · retrieved 2026-09-05 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
Even basic tip capture must be hand-built: 'Yes, you should set up a Tips Account' (Bob_be, 2021-07-01) plus a custom calculation with an over-tender prompt (JTRTech, same day). Nothing native retains a per-shift, per-employee record of tips received, amounts contributed to a pool, or amounts distributed from it — operators assemble accounts, calculations and custom reports themselves, and no pool-distribution record exists to export for audit. https://forum.sambapos.com/t/how-to-create-a-tip-reports/24409 · retrieved 2026-08-03
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
SambaPOS captures declared cash tips but exports no payroll file. The Time Clock Settings screen photographed running 5.7.8 (forum topic 28024, posted 2024-03-05) shows 'Declare Cash Tips' checked - the option 5.7.6 announced as 'Time Clock declare cash tip option and declaration added' - alongside Payroll Options (Payroll Type Continuous or Bi-Monthly, period Start Date and Length) and Overtime Options, so a declared-cash-tip figure and a pay period do exist in the product and the earlier note's claim that tips carry no cash-versus-charged split was wrong. What is absent is any payroll output. 6.45 enumerates the only labor payload that leaves the product: users (name, email, phone) synced to 7shifts, departments and roles synced, 'Clock In and Clock Out data will reflect to the 7shifts side under Time Clocking > Pay Periods > Review', and 'Sales data will reflect to the 7shifts side under Reports > Actuals'. Wages and tips are not in that payload, no other payroll destination appears in the 19-article Integrations section, and no W-2, Box 12 code TP or Box 14b tipped-occupation handling appears in the 613-record KB dump or in any release note from 5.5.0 through 5.7.28. The statutory modules SambaPOS does ship are Turkish e-Invoice, German TSE, Belgian Blackbox and Samoan TIMS. https://kb.sambapos.com/en/6-45-7shifts-integration/ · retrieved 2026-08-08
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 payroll product exists in the SambaPOS product catalogue. https://sambapos.com/products/ · retrieved 2026-08-01
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
Shortfall: one partner, timecards only. 6.45 documents a direct integration in which clock in/out data 'will reflect to the 7shifts side under Time Clocking > Pay Periods > Review' and sales appear under 'Reports > Actuals', after syncing users, departments and roles - a real timecard hand-off to a labor platform with a US payroll product. But it is the only such integration in the 19-article Integrations section, it requires a separately purchased 7shifts Integration licence on the same cp.sambapos.com account as the V5 Pro licence, and wages and tips are not part of the sync. No Gusto, ADP, Paychex or QuickBooks export or connector is documented in either the English or Turkish KB, and the generic Import/Export from File tool (2.4.2) exports configuration objects only. https://kb.sambapos.com/en/6-45-7shifts-integration/ · retrieved 2026-08-08
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
Shortfall: nothing native, and SambaPOS documents no swap workflow of its own. The Time Clock module's settings screen is the entire labor surface - 'Enable Time Clock', 'Force User for Clock in Before Login', 'Enable Breaks' (paid or non-paid), Departments, Roles and Assignments with an hourly wage - with no schedule, open shift, swap request or approval concept, and no employee-facing app (clock in/out happens at the terminal PIN screen). Scheduling is delegated wholesale to 7shifts (6.45), which receives synced users, departments, roles and punches; whatever self-service swap and approval behaviour exists is 7shifts', is not described by SambaPOS, and needs both a 7shifts Integration licence and a 7shifts subscription. https://kb.sambapos.com/en/8-13-how-to-configure-time-clock-module/ · retrieved 2026-08-08
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
The custom report engine can express per-user sales figures, but no packaged server scorecard is documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01
Inventory, purchasing & cost control
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
Recipes plus 'semi-finished products' give a sub-recipe layer; automatic plate-cost recalculation on ingredient price change is not explicitly documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Inventory items carry purchase and transaction units with multipliers; an explicit yield/waste percentage on raw-to-usable conversion is not documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
End-of-work-period counting compares recipe-driven consumption against physical count and reports cost; variance in both units and currency not confirmed. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Sales deplete recipe components including order-tag-driven components, but documentation frames stock status around work-period boundaries rather than continuous real time. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Both halves fail. Automatic: the only documented inventory-driven behaviour is the hand-built rule in 4.50 - a product tag, a constraint over {REPORT INVENTORY:...} on Order Added to Ticket, and Show Message plus Cancel Orders once the balance reaches zero. It blocks the sale in the cart; it does not mark the item unavailable on any menu, and it is a recipe the operator assembles rather than a shipped switch. Propagation: the one sold-out flag SambaPOS ships is manual and first-party, described in the GO Kiosk V2 feature list as 'Sold Out: you can close a product to sale within seconds without removing it from the menu' and set in GO Office, whose status vocabulary (soldOut, inStock, hidden) and route table (/menu, /kiosk, /tablet, /sync) cover only the GO kiosk and tablet menus - nothing ties it to a recipe, an ingredient balance or a threshold, and no marketplace appears in it. No release note from 5.5.0 to 5.7.28 adds an availability push. https://kb.sambapos.com/en/4-50-how-to-prevent-zero-stocked-item-sales/ · retrieved 2026-08-08
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
End-of-day physical counting is documented; scheduled recurring cycle counts and partial spot counts as distinct modes are not. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Counting is a Windows back-office procedure and the article states it as a requirement, not a preference: 'In order to count inventory, it is necessary to End Work Period', then 'go to Manage > Inventory > from here click on End of Day Records', open the latest End of Day document and 'write the product amounts into related item's line of Current Inventory column'. It runs after service against the server's management screens, has no scanning step, and produces no count document a device could hold and reconcile later. The mobile products SambaPOS documents - Mobile Client MC3 (8.10), GO Tablet V2 (8.18), GO Kiosk V2, KDS V2, Android Caller ID, metriK - each carry a published function set covering order entry, self-order, kitchen display, caller ID or report viewing, and none counts stock; MC3 and the Android client additionally require the device to sit in the server's IP group, so they are not offline-capable either. The one scanning improvement the staff release series makes to inventory is 'Barcode field added to Inventory Items' (5.2.22), which serves the desktop warehouse purchase screen; barcode support otherwise exists only for selling (5.1.11.b, 4.100). https://kb.sambapos.com/en/5-5-7-d-how-to-count-warehouse-inventory/ · retrieved 2026-08-09
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
Receiving is a hand-keyed document. KB 5.5.7.b: Warehouses > Purchase, with Ticket Number ('SambaPOS automatically uses the process date as ticket number'), Entity ('For inventory purchase you can select Supplier Entity selection'), Description, then 'Create a purchase line for inventory purchase by using Add button' with Name, Quantity, Unit, Price and Total typed in. The supplier is a label on the document; nothing transmits a purchase order and no PO object exists. 2.4.2 enumerates everything the Import/Export from File tool can move (Account Types, Accounts, Account Transaction Types and Document Types, Account Screens, Departments, Numerators, Document Types, Entity Types and Screens, Payment Types, States, Ticket and Order Tag Groups, Task Types, Printers, Printer Templates, Print Jobs, Calculation Types and Selectors, Automation Commands, Actions, Rules, Settings, Scripts, Custom Reports, Automatic Configuration Tasks): configuration objects only, no supplier catalog and no invoice. The vendor's 68-topic V5 Release series, 5.1.15 through 5.7.28 (forum categories 23 and 27, 1,451 posts), announces no purchasing, distributor or EDI work at all - the only inventory-side release items are warehouse defaults, inventory custom tags and barcode search. Sysco/US Foods/PFG are US broadliners and this is a Turkey- and UK-weighted vendor. https://kb.sambapos.com/en/5-5-7-b-how-to-purchase-item-into-inventory/ · retrieved 2026-08-09
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
5.5.7.b and 5.5.7.a describe the purchase document end to end: 'Create a purchase line for inventory purchase by using Add button', each line typed as Name, Quantity, Unit, Price, Total. No attachment, no capture, no parsing. 2.4.2 enumerates every object type the Import/Export from File tool handles and they are configuration objects (accounts, entity types, printers, print jobs, actions, rules, scripts, custom reports and so on) - no inventory purchase or supplier invoice among them. The automation action list (4.3) includes Data Export and Add Line to Text File but no import of transactional documents. Nothing in the 286 English or 327 Turkish KB posts mentions OCR or invoice scanning. https://kb.sambapos.com/en/5-5-7-b-how-to-purchase-item-into-inventory/ · retrieved 2026-08-08
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
Shortfall: history without alerting. Every purchase line stores a unit Price and Total against a supplier entity (5.5.7.a), 5.5.7.b points at the 'Product Purchase Report from the Reports menu' for purchases outside the current work period, and the Display Cost screen shows 'Average Price: Average price through purchasing prices after start work period' alongside Cost and Profit Rate - so per-item purchase price history is tracked and queryable, and custom SQL reports (9.1.2) can read it directly. But no contracted or expected price field exists on the inventory item card (2.3.15.a enumerates Name, Group, Warehouses, Base Unit and default cost, Transaction Unit, Multiplier, Additional Units), and no comparison threshold or notification is documented; nothing fires when a received price rises. https://kb.sambapos.com/en/5-5-7-a-general-features-of-warehouses/ · retrieved 2026-08-08
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
2.3.15.a is the Add Inventory Item screen in full: Inventory Item Name, Group Name, Warehouses, Base Unit and Base Unit Default Cost, Transaction Unit and its Default Cost, Multiplier, Additional Units. No par level, minimum, reorder point or forecast field, per item or per warehouse; the Neptune multi-branch equivalent (10.2) repeats the same field set. Purchasing is a manually keyed document (5.5.7.b) with no suggested-quantity function, and the documented way to watch stock is 4.28, which pastes a '{REPORT INVENTORY:Product Name:Warehouse Name}' tag into a menu button header and refreshes it with an automation action, or 4.50, which blocks sales of zero-stock items. The warehouse screen's 'Inventory' column is the amount remaining after transactions, not a target. https://kb.sambapos.com/en/2-3-15-a-how-to-add-inventory-item/ · retrieved 2026-08-08
Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.
inventory-waste-logging
Over-generous. KB 4.22 'How to Implement Wastage Stock?' is not a shipped waste-logging feature — it is a build-it-yourself recipe requiring the operator to create a Wastage entity, an Automation Command, an Account Type, an Account, a Transaction Type and a dedicated Ticket Type before any wastage can be recorded. The outcome (stock deducted, cost posted to a wastage account, reportable) is real, but 'documented configuration recipe' is partial, not native yes. Same caveat applies to the kitchen-waste-logging cell, which the researcher already scored partial. https://kb.sambapos.com/en/4-22-how-to-implement-wastage-stock/ · retrieved 2026-08-01 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
The Add Inventory Item screen (2.3.15.a) enumerates every field - Name, Group Name, Warehouses, Base Unit, Base Unit Default Cost, Transaction Unit, Transaction Unit Default Cost, Multiplier, Additional Units - with no expiry, use-by, batch or lot attribute, and the purchase line (5.5.7.a) is Name, Quantity, Unit, Price, Total, so a received date-coded lot cannot be entered either. Section 9's inventory reporting (Inventory Report, Inventory Transaction Report, Cost Report, 5.5.5.e-g) is quantity and cost by period. Wastage is handled after the fact by 4.22's Wastage Stock implementation, not by expiry prediction. No expiry/use-by/shelf-life term occurs in the 286 English or 327 Turkish KB posts. https://kb.sambapos.com/en/2-3-15-a-how-to-add-inventory-item/ · retrieved 2026-08-08
Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.
inventory-bar-partial-bottle
Every inventory item has a Base Unit used 'in recipes and all other processes' plus a Transaction Unit (the purchase unit) and a Multiplier converting between them - the KB's worked examples are 'Draft Beer / Cl' and tomato paste bought by the kg and consumed by the gram with multiplier 1000 (2.3.15.a, repeated in 10.2 for Neptune). Recipes deduct fractional base-unit quantities per pour (2.3.15.c), and counting is done by writing the measured amount into the 'Current Inventory' column of the End of Day record in that same base unit (5.5.7.d), so an open bottle counts as a fraction. The mechanism is generic fractional-unit inventory rather than a bar-specific feature: there is no weigh-the-bottle scale workflow - the documented scale integrations (CAS ER/PDN, Avery Berkel, Datalogic Magellan, Wintec, 8.4/8.8/8.12/8.16/8.20) price goods at the counter - and the count is manual. https://kb.sambapos.com/en/2-3-15-a-how-to-add-inventory-item/ · retrieved 2026-08-08
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
Shortfall: generic export, no named accounting target, no GL mapping. SambaPOS has a double-entry account system (5.4.8.a) and 9.1.5 documents building accounting reports from tags such as {ACCOUNT TOTAL:X}, {ACCOUNT TRANSACTION TOTAL:Type:Account} and {ACCOUNT TRANSACTION DETAILS:X} plus arbitrary SQL (9.1.2); the Cost Report (5.5.5.g) and Display Cost screen give period COGS, purchases are held as documents against supplier entities, reports export to file (4.58, 5.5.6.a) and there are Save Report to File and Data Export automation actions (4.3). What is missing is any QuickBooks, Sage Intacct, NetSuite or other named accounting import format, and any per-item-category GL account mapping - inventory Group Codes exist for reporting only. The only accounting-adjacent modules in the Integrations section are regional e-Invoice/fiscal ones. https://kb.sambapos.com/en/9-1-5-creating-accounting-reports-with-custom-reporting-tags/ · retrieved 2026-08-08
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
Knowledgebase 2.3.15.c: recipes are built in Manage > Inventory > Recipes; each recipe maps a Product and Portion to inventory items with quantity and unit, and the Fixed Cost field is calculated automatically as the raw material cost of the product. Order Tags can be mapped so a material is deducted only when that option is chosen. Depletion and costing are native modules of the V5 Pro application, not a contracted third party. https://kb.sambapos.com/en/2-3-15-c-what-is-inventory-recipe-how-to-create/ · retrieved 2026-08-06
Reporting, BI & data access
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
Metrik is marketed as tracking sales, employees, revenue and workflow 'instantly on all mobile devices'; latency and browser access unspecified, and the Metrik product page did not resolve. https://sambapos.com/products/ · retrieved 2026-08-01
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
Work-period reports cover sales and inventory close; a single document reconciling tax, tips, discounts, refunds, tenders and expected cash deposit is not explicitly documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
reporting-pmix-modifier-level
The custom report language can express item and order-tag sales; a packaged PMIX report with daypart/revenue-centre filters is not documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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 Void and Gift Report documents fields "No|User|Time|Status|Item|Quantity|Price" — employee and timestamp attribution are present — but there is no manager-approval attribution and no reason-code field documented. https://kb.sambapos.com/en/9-3-how-to-create-void-and-gift-report/ · retrieved 2026-08-04
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
MERGE-TIME CHANGE no -> partial: several shipped 5.7.30 DLLs are obfuscated (strings encrypted), so the assembly scan is not a census and cannot carry a no. SHORTFALL: over/short is NOT shipped as a report; the only route is an operator-built Entity Screen + custom report tags, per the vendor forum tutorial answer. CLAIM: Reports cash over/short per drawer, shift and employee, comparing counted cash to expected cash. VERDICT: no (proposed; see WEAKNESS). NEW SURFACE: the shipped SambaPOS V5 Pro 5.7.30 binary (file version 5.7.30.903; release post forum.sambapos.com/t/32282, 2026-09-07). Installer: https://sambapos.com/download/sambapos_setups/SambaSetup5730_09092.exe (linked anonymously from https://sambapos.com/download-sambapos/, 211,275,504 bytes, Authenticode-signed Advanced Installer; payload 49EB0A4\FILES.7z at offset 0x382200, first 0x200 bytes XOR 0xFF, 520 entries; 73 Samba*.dll/.exe extracted and scanned in raw bytes and as UTF-16LE). EVIDENCE: Samba.Localization.dll carries ONE resource table, Samba.Localization.Properties.Resources.resources, the central English UI string table. It also holds the default report templates (">Cash Transactions||", "Cash|{ACCOUNT TOTAL:Cash}", "Total||{ACCOUNT TRANSACTION TOTAL:Cash Expense:Cash}", "Work Period Report", "End of day Records") and the Time Clock label "Declare Cash Tips" (the 5.7.6 feature the 2026-08-09 audit said the KB never documented), which shows module UIs draw labels from this table. Its cash vocabulary is closed: "Cash", "Cash Drawer", "Cash Payment", "Cash Payment Type", "Cash Permissions", "Cash Status", "Cash Tip", "Cash Tip Amount", "Cash Transactions", "Cash Transactions Report", "Declare Cash Tips". BOUND/CONTROLS: case-insensitive word-boundary regex over the raw table: over 0, short 0, counted 0, variance 0, discrepanc* 0, blind 0, float 0; "expected" 1 (POISON: "The operation is taking longer than expected."); "drawer" 1 ("Cash Drawer"). Across all 73 Samba assemblies (raw + UTF-16LE): over/short|short/over|over or short 0, counted 0, cash count 0, blind close/drop/count 0, discrepanc 0; variance 1 (POISON: <Word>VARIANCE</Word> in the Oracle SQL keyword list of the Samba.Management.dll SQL editor highlighter). Forum corroboration: forum.sambapos.com/t/25732 "Cash Counter Feature" (2022-05-25) asks for counted cash vs sales; the only answer points to a community Entity Screen tutorial (/t/7105, 2016), and the 2025-05-28 follow-up "Did anything ever come of this?" is answered 2025-06-09 with the same DIY procedure; /t/23186 (2020-11-05) requests "cash declaration as a default feature". The precedent's objection (the KB is not a feature inventory) is answered by the string table, not the KB. WEAKNESS: some assemblies are obfuscated (Samba.GoOrder.Kitchenhub.dll has an encrypted user-string heap), so the census is the central resource table plus plaintext metadata, not every literal; and an operator CAN build an over/short screen with Entity Screens and custom {REPORT ...} tags, which a merger may prefer to score partial (shortfall: not shipped, operator-built). Retrieved 2026-09-16. https://forum.sambapos.com/t/cash-counter-feature/25732 · retrieved 2026-09-16 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
Shortfall: must be authored, nothing ships. 9.1.2 documents SQL scripts registered under an @@handler and rendered as report rows - the vendor's own worked example is a ticket-count-by-daypart report reading 'FROM Tickets' with DATEPART(HOUR,[DATE]) buckets - and 9.1.9 adds filtering, grouping and parameter lists. Time Clock stores clock in/out per user with a department, role and hourly wage set in Assignments (8.13), in the same database. So sales per labor hour and labor percent by hour, department or employee can be written. But the shipped reports are Work Period, Item Sales, Cash Transactions, Inventory, Inventory Transaction and Cost (5.5.5.a-g), none of which combines sales with clocked hours; the Time Clock module's own Reports tab is described only as a place where 'you can create new reports'. https://kb.sambapos.com/en/9-1-2-creating-custom-reports-with-sql/ · retrieved 2026-08-08
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
Achievable through the custom report engine; not shipped as a named report. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Shortfall: no commission netting. Departments exist precisely to separate 'Restaurant, Delivery Service, Take Away, Online Sale, Counter Sale' each with its own ticket type, menu, price list and warehouse (2.3.1.c), and 2.3.1.a states 'SambaPOS Basic Reports are Ticket Type Centric'; 9.4 builds item-group sales by ticket type, and the Cost Report / Display Cost screen give cost and Profit Rate per product, so revenue and margin per channel are reportable and each marketplace can be given its own ticket type. But no marketplace commission is captured anywhere: the GloriaFood, takeaway.com, Go Order and Shipday integration articles (6.3, 6.15, 6.29, 6.44) create tickets and never post a commission fee, and there is no commission field to net against - it would have to be modelled by hand as a calculation type or account transaction. https://kb.sambapos.com/en/2-3-1-c-how-to-create-department/ · retrieved 2026-08-08
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
2.4.12.e wires three actions into a rule: 'Save the Report to File' with parameters 'Report Name: Cash Report' and 'File Name: C:\Report\Cash Report.xps', and 'Send E-Mail' with SMTP Server/User/Password/Port, 'To E-mail Address: Addresses that e-mail will be sent', Subject, CC, message, the file to attach, Delete File, Bypass ssl Errors, Retry Count and Retry Minutes - multiple recipients separated by ';' - bound to the 'Work Period Ended' event. Cadence beyond that event comes from Triggers: 2.3.17.a documents Automation > Triggers with an Expression built from 'the minute, hour, day, week and month settings' ('It starts every day at 15:00 pm', 'only on Saturday / Sunday afternoon at 16:00') and 'Trigger activates the action of its assigned rule', and 'Trigger Executed' is a rule event in the enumerated event list (4.3). Any report can be named, since Report Name is a free parameter. Caveat for the reader: this is assembled from automation primitives, not a per-report Schedule button, and multiple reports need one Save/Send pair each. https://kb.sambapos.com/en/2-4-12-e-how-to-send-reports-as-email-at-end-of-work-period/ · retrieved 2026-08-08
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
CONVENTION NOTE: verdict tokens name the TARGET state, not the direction. This is an upgrade to partial. The claim 'no public REST or GraphQL reference exists' is true of the docs, but the dossier's conclusion that there is no API is wrong. SambaPOS V5 ships a GraphQL API on the Messaging Server: you activate it by appending '+' to the port in Samba.MessagingServerServiceTool.exe, authenticate integrators with access tokens against an 'Application' defined inside SambaPOS, and third parties demonstrably run mutations against it ('pushes sales through to samba, waits for a payment and then upda https://forum.sambapos.com/t/graphql-api-v5-5/25930 · retrieved 2026-08-01 adversarially verified
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
Consistent with the existing extensibility-webhooks-push finding: no webhook facility exists — the vendor-forum answer to calling an external HTTP service on ticket events is to hand-write JScript using the post helper inside automation rules, with no subscription management, retries, or signature verification. https://forum.sambapos.com/t/sambapos-script-for-self-hosted-http-service-and-post-data-in-url/21434 · retrieved 2026-08-04
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
Affirmative vendor-side statement found: 'GraphQL is a paid module. Any location that you wish to use Graphql will need to purchase a license' and 'The api is not an open free api, it is a product.' API access is upcharged per location, on top of the $339 base licence. Price is unpublished. https://forum.sambapos.com/t/what-happened-to-graphql-guide/25526 · retrieved 2026-08-01 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
Knowledgebase section 9 documents custom report templates, custom reports written in SQL, pivot and table views, filtering/grouping, an item sales report by product tag (PMIX) and a void-and-gift report, all authored in the in-application Reports screen of the one V5 Pro licence; Time Clock (8.13) records clock-in/out with an hourly wage rate per user role and is reportable there. Shortfall: there is no consolidated multi-location comparison in the base licence - cross-site and remote dashboards are the metriK product, and 8.11.1 requires a separately purchased Metrik licence per location in the same cp.sambapos.com account as V5 Pro. https://kb.sambapos.com/en/cat/reports/ · retrieved 2026-08-06
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
Retention is effectively unlimited because the merchant hosts the database, but the vendor publishes no retention commitment for the reporting UI or the cloud add-ons. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Shortfall: hand-built thresholds only, and no deviation detection. 4.3 enumerates the automation surface: events include Trigger Executed, Ticket Total Changed, Payment Processed, Order Cancelled and Work Period Ended, actions include Send E-mail, Broadcast Message, Show Message, Display Popup, Save Report to File and Execute Script. Rules take custom constraints on values - the vendor's own examples are 'Remaining Amount | Equals | 0' (2.4.4) and the daily item sale limit in 4.55 - and Triggers give scheduled evaluation (2.3.17.a), so an operator can raise an email when a configured figure crosses a line. What does not exist is any shipped alert or subscription screen, any void-spike or discount-anomaly detector, and any comparison against a historical baseline or forecast: the report engine has no forecast tag (9.1.3, 9.1.4) and metriK V2 is a pull-only report viewer (8.11.1), not a push channel. https://kb.sambapos.com/en/4-3-how-does-it-work-action-rule-structure/ · retrieved 2026-08-08
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
English KB 9.1.3 Custom Reporting Tags (modified 2021-01-29) states the only documented way to interrogate the data in this product: 'It is possible to prepare any type of reports with SQL and display results as a Custom Report. Alternatively you can use Custom Report Tags to prepare reports.' What follows is a closed list - 'These are the supported DETAILS tags.' - of bracketed tags over fixed field sets, filtered by an expression syntax the article itself compares to a SQL Where clause. 9.1.1 supplies template authoring, 9.1.2 the registered SQL script alternative, 9.1.8 the viewer widget and 8.11.1 the metriK V2 surface for reports flagged for it. Every one of those requires the operator to author the query in advance; none accepts a question. Corroborated by a corpus-wide zero across all 958 documents in both languages for natural language, dogal dil, yapay zeka, artificial intelligence, ChatGPT and machine learning - including the whole marketing tree, where this vendor gives dedicated landing pages to KDS, GoOrder, Jetrik, GO Kiosk and Neptune and would certainly give one to an AI assistant. https://kb.sambapos.com/en/9-1-3-custom-reporting-tags/ · retrieved 2026-09-05 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
Shortfall: no packaged cohort reporting. Guests are Customer entities with an account, and 9.1.4 exposes them to reports through REPORT ENTITY DETAILS with fields E.Id, E.EntityTypeId, E.Type, E.AccountId, E.Balance and EC.<custom field>, while 9.1.2 allows registered SQL scripts to be rendered as report rows against the live tables (the vendor's own example reads FROM Tickets and buckets by hour). Visit-driven logic is already used elsewhere - 4.15 gives a promotional product 'to each new customer for one time' and 4.102 gives a free coffee after five - and 4.17 prints a customer's previous transactions, 9.8.1 reports customers with remaining balances, 4.94 exports the customer list to Excel. But nothing shipped reports new versus returning counts, visit frequency or lifetime-spend cohorts; each would be an operator-written SQL report, and guest identity depends on a customer entity actually being selected on the ticket. https://kb.sambapos.com/en/9-1-4-custom-reporting-tags-for-v5/ · retrieved 2026-08-08
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
English KB 9.1.3 Custom Reporting Tags (modified 2021-01-29) is the closed report-tag list - 'These are the supported DETAILS tags.' - and its five blocks (TICKET, ORDER, PAYMENT, CALCULATION and ENTITY STATE DETAILS) expose nothing but recorded history: dates, times, users, terminals, quantities, prices, tags and state timestamps. No projected or forecast quantity appears, and the two prediction-named fields elsewhere in the reporting documentation, C.Prediction and C.CostPrediction in 9.1.4, are inventory arithmetic - Turkish 5.5.7.a defines the same idea as the stock quantity after existing transactions. The string forecast occurs in none of the 958 corpus documents and the Turkish side is the same; the only ongoru hits are generic marketing insight language on sambapos.com/tr/hizli-satis/ and /tr/hayalet-mutfak/. The viewer widget's date vocabulary in 9.1.8 is entirely historical apart from a forward selector that picks future-DATED records such as reservations rather than projecting anything. Nothing is consumable downstream either, because nothing is produced and this product ships no labour scheduling module at all. https://kb.sambapos.com/en/9-1-3-custom-reporting-tags/ · retrieved 2026-09-05 adversarially verified
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
No tip reporting ships at all — even tip capture is hand-built. On the vendor forum, the answer to 'how to create a tip report' is to assemble the plumbing yourself: 'Yes, you should set up a Tips Account' (Bob_be, 2021-07-01) plus 'a calculation for tips which has corresponding accounts etc setup' with an over-tender prompt (JTRTech, same day). With no native tip capture there is no declared-vs-charged distinction (SambaPOS also processes no cards, so charged tips are invisible to it), no tip-pool distribution detail, and no tax liability summary by jurisdiction; any report is the operator's own custom report against hand-built accounts. https://forum.sambapos.com/t/how-to-create-a-tip-reports/24409 · retrieved 2026-08-04
Multi-location, franchise & enterprise governance
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
Neptune supports branches and branch grouping — two levels plus HQ; not described as a first-class object permissions scope to. https://sambapos.com/sambapos-neptune/ · retrieved 2026-08-01
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
Neptune manages prices per branch; channel and daypart price tiers on one item record are not documented. https://sambapos.com/sambapos-neptune/ · retrieved 2026-08-01
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
Neptune provides cross-branch reports; the specific aggregation set (labour, discounts, voids, item mix) and variance flagging are not documented. https://sambapos.com/sambapos-neptune/ · retrieved 2026-08-01
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
KB 4.31 (English, MODIFIED 2019-09-27; Turkish twin 4-31-hediye-karti-uygulamasi). SambaPOS's own gift certificate is entirely operator-assembled inside one database: "In this document, it will be explained how to apply Gift Certificate Implementation." builds a "Product Name: Gift Certificate" under "Group Code: Gift Certificates", GC Accounts and GC Balances account types, and a Gift Certificate entity whose balance is written by "2.8. Adding Update Entity Data Action- Balance"; redemption is local - "You can either scan the barcode via barcode reader or enter the number of Gift Certificate manually into numberpad." Since SambaPOS is one installation per site with its own MSSQL (2.1.6), that balance cannot leave the site, and the eleven-article Neptune series documents no entity, account or balance sync (KB 10.8 scopes branches to products, menus, stock and recipes). What stops this being a flat no is that SambaPOS also passes gift cards through to processors whose balances live on their network: KB 6.20 Global Payments Integration (English, 2023-11-10) exposes a gift-card payment type setting, and the release series adds Valutec (5.3.2, US only) and Dejavoo gift card support (5.7.16). On those the subject is the processor, and SambaPOS documents nothing about multi-site redeemability, outstanding liability or inter-store settlement in either language. https://kb.sambapos.com/en/4-31-gift-certificates-sales-and-redemption-implementation/ · retrieved 2026-09-05 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
10.2 states what a branch receives - 'branches are defined for products, menu, stocks and recipes' - and the Neptune panel offers only Products, Inventory, Branches, Sync and inter-branch Orders. Customers are not synced. Loyalty in SambaPOS is assembled per installation from customer entities and account transactions: 4.27 Basic Loyalty Points, 4.9 the SambaCard loyalty card, 4.102 the free-coffee counter, 5.4.8.c Customer Accounts Management, with balances held in that database's accounts. Since each branch runs its own SQL Server (2.1.6), a guest's profile, point balance and order history do not follow them between branches; nothing in the KB describes a shared customer directory. https://kb.sambapos.com/en/10-2-how-to-use-sambapos-neptune/ · retrieved 2026-08-08
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
2.3.1.c: 'A restaurant could have different sections by sales, order, workflow structure process... Restaurant, Delivery Service, Take Away, Online Sale, Counter Sale, Game Saloon', and per department 'Each department can use a different product menu', 'Each department can use a different price list', 'Each department can follow different warehouse inventory actions', with its own Default Ticket Type and ticket creation method; the article's stated purpose is that 'each department should only see its own menu, price list, warehouse and screen view, print job, action-rule and automation commands'. Receipt branding follows: 2.3.1.a says 'Print jobs, Print Templates can be created and associated according to Ticket Types', and templates are freely editable HTML (2.3.14.b). Revenue separates because 'SambaPOS Basic Reports are Ticket Type Centric' (2.3.1.a), with 9.4 building item-group sales by ticket type. Departments switch on the same terminal at login and share the cash drawer and printers, so one machine and one drawer serve several brands. Note the vendor frames this as departments, not brands - there is no brand object and no per-brand marketplace routing beyond giving each channel its own ticket type. https://kb.sambapos.com/en/2-3-1-c-how-to-create-department/ · retrieved 2026-08-08
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
Tax templates are configurable per install and the vendor ships jurisdiction compliance modules (Turkish e-Invoice, German TSS, Samoan TIMS); per-location exemptions inside one account not documented. https://sambapos.com/integrations/ · retrieved 2026-08-01
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
KB 8.13 (English, MODIFIED 2023-10-11; the Turkish twin is content-identical and its 2026-08-24 stamp is part of the 288-document bulk re-save, carrying no freshness). Time Clock is a per-installation module and its whole settings surface is enumerated: "Enable Time Clock: Click on this box to activate the Time Clock Module.", "Enable Breaks: This is the choice which gives to select the Break Option." with a paid or non-paid choice, then "2.2. Departments Screen" where "You can set your departments and their related user roles from this section. Department: Restaurant Role: Waiter", and assignments where "you will be able to set the hourly wage as well.(this is not mandatory you can leave it as 0)". No overtime threshold, no schedule, no minor rule, and no scope beyond the local database. The only central layer is Neptune, and sambapos.com/sambapos-neptune/ (English, 2023-10-11) publishes a closed list of what HQ can push to branches - Products, Menus, Prices, Sales Screens, Users, Permissions, Reports, Inventory Items, Receipts, Accounts - with no time clock, wages, breaks or scheduling among them; central users and permissions genuinely exist, but those are not a labor policy. Residue: release 5.7.8 (2024-01-31) added Time Clock payroll overtime settings the KB still does not document, which affects how a setting behaves, not whether a central per-location-group labor policy is offered. https://kb.sambapos.com/en/8-13-how-to-configure-time-clock-module/ · retrieved 2026-09-05 adversarially verified
Hardware & physical footprint
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
Knowledgebase 1.4 states the requirement as any PC with at least an Intel i5 10th-gen CPU, minimum 8GB RAM, 100GB (SSD recommended) disk, 1024x768 monitor, Windows 10 or higher and .NET Framework 4.8; 3.1 additionally supports Intel-chipset Windows 8.1/10 tablets and Android 4.4+ devices with 2GB RAM as clients. The requirements are stated as commodity specifications and no proprietary SambaPOS terminal is documented. https://kb.sambapos.com/en/1-4-hardware-and-software-requirements/ · retrieved 2026-08-06
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
'Windows 10 or higher Operating System' stated for the POS; Mobile Client and KDS name Android and iOS; GO Tablet specifies 7-inch minimum tablets. Knowledge base has a system requirements article. https://sambapos.com/sambapos-v5-pro/ · retrieved 2026-08-01
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
No vendor handheld exists. The Mobile Client is an app licensed per device for the operator's own Android/iOS phones and tablets. https://sambapos.com/sambapos-mobile-client/ · 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
3.1 Hardware Requirements and Compatibilities (last modified 2025-02) is the vendor's supported-hardware statement and it is bring-your-own throughout: computers 'at least Intel i5 10th Gen', 'any type of touchscreen', 'Tablet Hardware: The most ideal tablet devices to use SambaPOS are the ones which has Intel Chipset and Windows 8.1 or 10 installed. On the versions above Android 4.4, it is possible to use terminals with the connection of SambaPOS Mobile Application', 'any type of thermal or dot-matrix ticket printer which ESC/POS compatible', 'all barcode readers... which has keyboard emulator', 'all cash drawers that were triggered by connecting with RJ11'. The mobile products SambaPOS sells are software licences per Android device (8.1 Mobile Client, 8.10 MC3, 8.18 GO Tablet). With no vendor handheld there is no vendor battery specification, hot-swappable or otherwise, and none appears in the KB. https://kb.sambapos.com/en/3-1-hardware-requirements-and-compatibilities/ · retrieved 2026-08-08
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
8.1 Android Mobile Client V2 Setup: 'Android device and SambaPOS Server must be in the same network and IP group', 'SambaPOS Server and Mobile Client must be in the same IP group' with a static server IP, Message Server addressed as 'http://your server pc name or http://your server pc ip', MSSQL TCP/IP enabled on port 1433, and the pda application defined with 'Authorization Type: All Functions in Local Network'. Internet is needed only once, for setup ('You need to have internet for setup. You don't need internet after setup'). The handheld therefore has to be on the store LAN; cellular is not an alternative path to the on-premise server, and no vendor-supplied failover, VPN or relay is documented anywhere in section 8 or in 2.1.6's multi-computer networking guide. https://kb.sambapos.com/en/8-1-android-mobile-client-v2-setup/ · retrieved 2026-08-08
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 a headline claim backed by on-premise SQL Server, but there is no explicit published list of which functions degrade. https://sambapos.com/ · retrieved 2026-08-01
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
SambaPOS KDS is a first-party product at $69 per device per year with customizable screens and kitchen efficiency calculation. https://sambapos.com/sambapos-kds/ · retrieved 2026-08-01
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
GO Kiosk supports horizontal and vertical orientation on operator-supplied hardware with self-service payment; no purpose-built freestanding enclosure SKU and no ADA documentation. https://sambapos.com/sambapos-go-kiosk/ · retrieved 2026-08-01
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
The page claims "multiple lanes are dedicated to mobile orders and delivery, while at least one lane is dedicated to the regular drive thru" and positions GO Kiosk for self-service at the window, but outdoor digital menu boards, order-confirmation displays, speaker/headset integration, and a documented timer/speed-of-service measurement are not described. https://sambapos.com/drive-thru-pos/ · retrieved 2026-08-04
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
Printing is a documented core module using printer templates over Windows and network printers, which in practice means broad ESC/POS support; no published compatibility list naming Epson/Star models. https://kb.sambapos.com/en/ · 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
Barcode entry, cash drawers via printer kick and Caller ID devices are documented under Hardware & Network; scales for by-weight items and customer-facing displays are unconfirmed, and no compatibility list exists. https://kb.sambapos.com/en/ · 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
Shortfall: no PCI statement of any kind. Card entry demonstrably happens on the payment device: 6.31 Quest - 'clicking the Credit Card button on the right side will initiate a transaction process which will be conducted by the PinPad. If you wish to utilize Manual card entry... you can enter your card number on the PinPad'; 6.2 PaymentSense Pay at Table - 'you will see the screen which is asking for you to Touch, Insert or Swipe the card', driven by the terminal's F1/F4 keys. The same semi-integrated pattern holds for Dojo (6.14), Global Payments (6.20), Worldline TIM (6.26), Dejavoo (6.34, 6.42), International Bancard (6.12) and OpenEdge (6.5). But none of these articles, and nothing else in the 613-record KB dump, names a PCI-listed PTS device, cites a validated P2PE solution listing, or tells the merchant which SAQ applies - the words PCI, P2PE and SAQ do not appear at all. Scope reduction is therefore a property of the processor the operator chooses, unstated by SambaPOS. https://kb.sambapos.com/en/6-31-quest-payment-integration/ · retrieved 2026-08-08
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
SUBJECT: the SambaPOS Mobile Client MC3 add-on (a priced add-on, $49 per sambapos.com/mobile-client-landing/) running on a commodity Android/iOS phone. KB 8.10 (English, MODIFIED 2023-10-02) is the complete setup document and its entire payment section 'Getting Payment on SambaPOS Mobile Client' is the single sentence 'Select desired table, click on Settle button.'. Its own troubleshooting checklist '6.1. Connection and Network Settings Part' is exclusively Wi-Fi, server IP group, Message Server and 'Is the Message Server Port 9000+ ?' - no reader, no NFC, no payment-device pairing, no card step anywhere in the article. MC3 is a Wi-Fi LAN client that writes a tender into the shared SQL database; the card leg stays on an external PIN pad in every documented processor integration (English 6.1, 6.2, 6.5, 6.12, 6.14, 6.20, 6.26, 6.31, 6.34, 6.42 plus about twenty Turkish yazarkasa/OKC articles). Zero corpus hits in either language for softpos, tap to pay or tap-to-phone. The only in-house device-borne acceptance is the Odeal PAX Android payment terminal, which is a reader, not a phone. https://kb.sambapos.com/en/8-10-sambapos-mobile-client-mc3-setup/ · retrieved 2026-09-05 adversarially verified
Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator
hardware-pricing-transparency
The vendor sells no hardware SKUs, so there are no hardware prices to publish. Software prices are published. https://sambapos.com/products/ · 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
Re-sourced from product documentation rather than the marketing products page. KB 3.1 'Hardware Requirements and Compatibilities' is a compatibility specification for equipment the operator supplies: a Windows PC (min Intel i5 10th Gen, 8GB RAM, 100GB disk), 'any type of thermal or dot-matrix ticket printer which ESC/POS compatible', barcode readers 'which has keyboard emulator', cash drawers triggered over RJ11 through the printer, and named third-party scales (Cas ER Junior, TEM EGE). The KB nowhere offers a device to buy or lease from the vendor, and the products page lists nine SKUs of which none is a physical device. There is no vendor lease because there is no vendor hardware; the merchant owns whatever it buys. https://kb.sambapos.com/en/3-1-hardware-requirements-and-compatibilities/ · retrieved 2026-08-02 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-sourced to product documentation. KB 1.4 specifies only generic, third-party equipment — Windows 10+ PC with .NET Framework 4.8, 1024x768+ monitor, ESC/POS-compatible thermal or dot-matrix printer, Android 4.4+ or Windows tablets for the Mobile Client. Nothing in the deployment is vendor-provisioned or vendor-serialised, so there is no device for SambaPOS to reclaim, remotely disable or brick when a licence lapses. The lock-in that does exist on churn is software-side (the V5 licence and the Mobile Client's online re-validation), not hardware-side; the PC, printer, drawer and tablet remain ordinary commodity kit. https://kb.sambapos.com/en/1-4-hardware-and-software-requirements/ · retrieved 2026-08-02 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
No vendor hardware means no vendor warranty term or advance-exchange programme. https://sambapos.com/products/ · retrieved 2026-08-01
Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.
hardware-byod
Mobile Client and GO Tablet are licensed per device on staff-owned or venue-owned Android/iOS devices, with multi-user support per device; no published BYOD security model. https://sambapos.com/sambapos-mobile-client/ · retrieved 2026-08-01
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
GO Office (gooffice.sambapos.com) is a live vendor-operated device console, but only for the GO device family. Its shipped application bundle (/assets/index-DDUi7_zw.js, retrieved 2026-08-08) declares routes /tablets, /tablet, /tablet-home, /tablet-theme, /kiosk, /kiosk-home, /kiosk-theme, /printer, /logs, /licenses, /sync, /remove-tablets and /remove-kiosks, and an English status dictionary reading online:'Online', offline:'Offline', error:'Error', kiosk:'Kiosk', tablet:'Tablet', status:'Status' - so each registered kiosk and tablet is shown online/offline. It also has per-device diagnostics ('Tablet Logs', 'Kiosk Logs' with columns Date, Device ID, Log Name, Message), bulk deregistration ('Remove Selected Devices'), licence sync ('Get Tablet Licences' / 'Get Kiosk Licences') and a remote push with a scope picker ('Choose Update Type' -> All, With Media Files, Device Settings, Language Options, Home Ads, Categories and Products, Payment Types) confirmed by 'Update request sent'. Shortfall: coverage stops at GO Kiosk and GO Tablet. The Windows POS terminals, the KDS clients and receipt printers are absent - the /printer route is kiosk printer configuration (Printer Type, Printer IP Address), not a monitored printer - and there is no remote reboot, no software-version column and no staged or ringed rollout; the push is content and settings to all devices at once, and KB 2.1.6 and 8.19 still have SambaPOS and KDS upgraded by running the installer on each machine. cp.sambapos.com (KB 5.5.9) is a licence and store panel, and one.sambapos.com's route table (/dashboard, /tickets, /products, /entities, /reports, /management, /users-management, /micro-integration, /edocuments, /malaysian-einvoice, /ticket-settings, /settings) has no device dimension at all. https://gooffice.sambapos.com/ · retrieved 2026-08-08
Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.
hardware-selfpour-scales
SUBJECT: SambaPOS V5 Pro peripheral support. KB 3.1 (English, MODIFIED 2025-02-18) enumerates the supported peripheral classes closed and complete - computer, ESC/POS printer, tablet, Caller ID device, scales, barcode reader, cash drawer - and no beverage-dispensing, flow-meter or tap-wall class appears. The scales entry is deliberately open-ended: 'Cas ER Junior model, runs directly with TEM EGE model scales. Also you can use all scales which is able to send data to computer through COM port, by adding them Custom Scale.' - but a generic COM-port weighing driver is weigh-to-price at the counter, not pour-to-tab, and the scale articles (8.4 CAS ER, 8.8 Avery Berkel, 8.12 CAS PDN, 8.16 Datalogic, 8.20 Wintec, Turkish 8.3 Desis and 8.21 Aclass) are all retail weighing. Across all 958 documents in both languages self pour, self-pour, tap wall, flow meter, flowmeter, akis olcer, pour spout, keg, musluk, PourMyBeer and iPourIt return ZERO files, and the two dispens hits are the English word indispensable. The only draft-beer mechanism in the corpus is inventory depletion by recipe (a Draft Beer / Cl inventory unit in KB 2.3.15.a and a Turkish Fici Bira / Cl twin), where stock is consumed when the item is SOLD - the reverse of a metered pour creating the sale. https://kb.sambapos.com/en/3-1-hardware-requirements-and-compatibilities/ · retrieved 2026-09-05 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
Caller ID setup is a documented Hardware & Network topic with widget creation on entity screens, and SambaPOS Android CID is a shipped first-party product. https://kb.sambapos.com/en/ · retrieved 2026-08-01
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
extensibility-public-api-docs
Upheld, and now affirmatively sourced rather than inferred from absence. Staff explicitly direct licence holders to 'email [SambaPOS support] and request it along with what you are wanting to build' rather than to any public reference; the GraphQL guide was removed and, as of the last posts in the thread, never restored. This is now a documented absence of public docs, not merely 'I couldn't find any' — but pair it with the correction above: the API itself exists. https://forum.sambapos.com/t/what-happened-to-graphql-guide/25526 · retrieved 2026-08-01 adversarially verified
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
No longer unknown that it costs money — a per-location GraphQL licence must be purchased, and it is not sold as a listed SKU on sambapos.com/products/ or visible in the Samba Market listing, so the amount remains unpublished. Scored 'no' on the free/included reading of the cell; the dollar figure itself stays unknown. https://forum.sambapos.com/t/pricing-and-documentation-for-sambapos-api/27174 · retrieved 2026-08-01 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
A free, fully-featured one-month trial download is available to anyone, which functions as a test environment; there is no seeded developer sandbox. https://sambapos.com/ · retrieved 2026-08-01
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
The local GraphQL API issues OAuth2-style tokens: POST to :9000/token with grant_type password or client_credentials against an Application the operator defines under Manage > Users > Applications (Identifier as client_id, optional client_secret, Lifetime, Allowed Origin, Active toggle, and a Permissions selection). Shortfalls: permission scoping is barely surfaced and undocumented (the 2018 walkthrough advice was 'don't select Permissions'), the API is a separately licensed paid module per location, and the integrator guide was withdrawn from public view — documentation is now provided by emailing support with the intended use case. https://forum.sambapos.com/t/server-9000-token-returns-400-response/17414 · retrieved 2026-08-03
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
No webhook facility exists. When an integrator needed SambaPOS to call an external HTTP service on ticket settlement, the vendor-forum answer was to hand-write JScript using the post helper inside automation rules ('You would call a sambapos script... use the post helper function' — JTRTech, 2020-02-23). Outbound push is therefore operator-authored scripting with no subscription management, delivery guarantees, retries or signing; the licensed GraphQL API is request/response, so third parties otherwise poll. https://forum.sambapos.com/t/sambapos-script-for-self-hosted-http-service-and-post-data-in-url/21434 · retrieved 2026-08-03
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
Per the existing extensibility-webhooks-push finding, no webhook facility exists at all in SambaPOS — outbound HTTP calls require hand-written JScript inside automation rules with no signing, retry/backoff, or replayable event log, so a signed-and-retried webhook cannot be present. https://forum.sambapos.com/t/sambapos-script-for-self-hosted-http-service-and-post-data-in-url/21434 · retrieved 2026-08-04
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
Partial stands but the reasoning was weak (it leaned on a GloriaFood 'API Activation' step and the abandoned V3 Samba.ApiServer tree). Better evidence: integrators push sales into SambaPOS through GraphQL mutations today. Still partial and not yes, because the write path is licence-gated, undocumented publicly, and demonstrably unstable across minor versions. https://forum.sambapos.com/t/graphql-api-v5-5/25930 · retrieved 2026-08-01 adversarially verified
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, Uber Eats and Grubhub appear on the integrations page alongside regional marketplaces, but the vendor does not state whether these are direct certified connections or middleware-mediated. https://sambapos.com/integrations/ · 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
KB 8.19 (English, MODIFIED 2025-01-24). SambaPOS ships a first-party application registry for third-party clients: "3.3. Creating Application" instructs "Main Menu > Manage > Users > Applications > Here, click on Add Application." with "Authorization Type: All Functions", "Lifetime: 365" and "Allowed Origin: *", plus a Permissions section - note that this one is All Functions, not the local-network-scoped variant batch B claimed was uniform across the KB. It sits behind the GraphQL message server on port 9000, and user accounts carry a password field distinct from the POS PIN whose only purpose is GraphQL authentication (KB 2.2.10.b states that the user password is used for connections made through GraphQL). Thirteen documented integrations register through this registry, including third parties that are not SambaPOS products - takeaway.com (KB 6.15), GloriaFood (6.3), RestaJet (6.4), PaymentSense (6.2) - so the endpoint an aggregation middleware would bind to is documented, public and already used by outside platforms. What is genuinely absent is named support: measured zero-hit across all 958 documents in both languages for Deliverect, Chowly, Otter, Checkmate and ItsaCheckmate, and the vendor built its own aggregation layer instead (GoOrder USA, 49 USD monthly, connecting DoorDash, Uber Eats, Grubhub and GloriaFood). Also absent is a published GraphQL schema reference. Partial with the mechanism named. https://kb.sambapos.com/en/8-19-how-to-configure-sambapos-kds-v2/ · retrieved 2026-09-05 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
One vendor-maintained GL connector exists, but not the one the claim names. SambaPOS ONE (one.sambapos.com; installer published at sambapos.com/download/sambapos-one/) ships a Mikro ERP integration - Mikro Yazilim is a Turkish ERP and accounting suite. Its shipped bundle (/assets/index-Bj_i1l9v.js, retrieved 2026-08-08) declares the routes /micro-integration/settings, /micro-integration/account-mapping, /micro-integration/payment-type-mapping, /micro-integration/stock-mapping, /micro-integration/transfer-records and /micro-integration/workperiods, and its English dictionary describes the module as 'Mikro ERP integration: settings, product and payment type mapping, accounts, and transfer records'. The mapping is to the ledger, not a CSV: fields include 'Mikro account code' with the placeholder '120.01.001' (a Turkish uniform chart-of-accounts receivable code), 'Mikro account name', 'Cash account' typed Cash/Bank/POS, 'Cost center', 'Project', 'Invoice serial no', 'Branch no', 'Working year' and 'Firma kodu', plus Mikro database and API host credentials; posting runs per work period with statuses Pending, Processing, Completed and Failed and a retry-count column, over a transfer-records log. Shortfall: no QuickBooks Online connector, and none for Xero, Sage or Zoho Books - grepping all 613 KB records in both languages returns zero hits for any of them, and QuickBooks appears on the forum only as unanswered user requests from 2015-2020 with an admin reply in 2016 asking 'What can we integrate with Quickbooks?'. So the claim's required QBO leg fails and the second-system leg is met by a single regional ERP that the knowledge base never documents. https://one.sambapos.com/ · retrieved 2026-08-08
Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.
extensibility-payroll-export
KB 6.45 documents a first-party, separately licensed 7shifts module (SambaPOS 5.7.26+, licence bought on cp.sambapos.com under the same account as the V5 Pro licence). It syncs users, departments and roles to 7shifts from the Time Clock module, and section 11 states 'Clock In and Clock Out data will reflect to the 7shifts side under Time Clocking > Pay Periods > Review', with section 12 adding 'Sales data will reflect to the 7shifts side under Reports > Actuals'. So hours reach a payroll-capable destination without re-keying. Shortfall: 7shifts is the ONLY such destination - no Gusto, ADP, Paychex, Paylocity or any other payroll connector appears in any of the 613 KB records in either language, so the claim's 'at least two named payroll providers' is not met, and the one that exists is a paid add-on rather than base functionality. https://kb.sambapos.com/en/6-45-7shifts-integration/ · retrieved 2026-08-08
The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.
extensibility-app-marketplace
A public integrations directory lists roughly two dozen named third-party integrations, but it is a marketing index with setup articles rather than a self-install marketplace. https://sambapos.com/integrations/ · retrieved 2026-08-01
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
Consistent with extensibility-order-injection-api: integrators demonstrably push sales through SambaPOS's GraphQL API and read back payment status, a form of driving the transaction engine from a third-party UI — but the API is a separately licensed paid module per location, its guide was withdrawn from public view, and it is demonstrably unstable across minor versions, so it falls short of a documented, supported headless mode. https://forum.sambapos.com/t/graphql-api-v5-5/25930 · retrieved 2026-08-04
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
A perpetual license plus a merchant-hosted SQL Server database means the complete historical record is already in the operator's hands in a documented machine-readable form at all times. https://kb.sambapos.com/en/ · retrieved 2026-08-01
Reliability, offline & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
reliability-offline-order-entry
A weighted differentiator scored yes off a marketing sentence. The only cited source is a segment blurb on the homepage ('SambaPOS doesn't rely on the internet to run'), which is claim-level. Counter-evidence from the vendor's own forum: a SambaPOS developer confirms 'Mobile Clients control licence over internet every time when you see an entity screen' because licensing is per-user, said 'we are developing a new licence control system for offline users' (Feb 2019), and the thread shows the problem persisting; the KB states the machine 'has to be connected to internet for Licensing and Activat https://forum.sambapos.com/t/major-issue-with-online-license-check-systems-offline/19437 · retrieved 2026-08-01 adversarially verified
Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator
reliability-offline-card-auth
SUBJECT AND SCOPE: a no about SambaPOS's delivered card path, NOT about any acquirer's terminal firmware or PCI posture. SambaPOS never authorises or stores a card; every integration is a DLL in the SambaPOS5 folder plus an Automation Command handing the transaction to an external PIN pad synchronously. KB 6.31 Quest Payment Integration (English, MODIFIED 2024-11-21) states the precondition directly: clicking the Credit Card button 'will initiate a transaction process which will be conducted by the PinPad', and 'If you wish to utilize Manual card entry wait until you establish a connection after which you can enter your card number on the PinPad.' - a live connection is required before card entry, with no queue. I then enumerated the whole integrations surface: all 20 English 6.x articles and all 34 Turkish 6.x yazarkasa/OKC articles (Ingenico GMP3/TSM, Beko 300TR and X30TR, Hugin, Pavo, InPos M530) contain not one reference to connection loss, queuing, a stored-transaction cap, a floor limit or a reconnect flush. Corpus-wide, offline appears in exactly ONE file (sambapos.com/full-service/) and cevrimdisi in exactly one (the Turkish twin), both as a marketing bullet listed beside Online Payment under Simple Payment Methods - a payment channel label, not store-and-forward. RESIDUAL, stated honestly: an acquirer terminal (Dojo, Global Payments, Dejavoo, PAX) may hold its own store-and-forward firmware; SambaPOS publishes nothing about it and ships none of its own. https://kb.sambapos.com/en/6-31-quest-payment-integration/ · retrieved 2026-09-05 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
SUBJECT: SambaPOS as publisher. Terms of Use (English, MODIFIED 2022-07-27; Turkish twin sambapos.com/tr/satis-ve-kullanim-kosullari/) allocates connectivity risk generically and nothing more - clause 3.13 'The user is responsible for preparing the necessary infrastructure for the operation of SambaPOS products.' followed by a sentence making the user responsible for problems caused by insufficient internet, operating system, network, cabling and electricity infrastructure; clause 3.17 disclaims interruption of third-party-integrated services and ends 'SambaPOS is not responsible for any damages incurred by this situation.' Neither is an allocation of loss on a declined stored transaction, and no per-transaction or cumulative offline cap appears in that document, in the Privacy Policy, in sambapos.com/personal-data/, or in any of the 958 corpus documents. There is also no mechanism for such a statement to attach to - see reliability-offline-card-auth, where all 54 integration articles were enumerated and SambaPOS ships no store-and-forward. CORRECTION TO THE SESSION BRIEF, confirmed by me: the brief says no contract is published on either host; a Terms of Use, a Privacy Policy, a Personal Data page and a Cookie Use Policy ARE published in both languages. What is genuinely absent is an MSA, SLA or DPA. https://sambapos.com/terms-of-use/ · retrieved 2026-09-05 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
Multi-computer deployment is documented: terminals share one local SQL Server database and communicate via the local Messaging Server, so shared check state survives internet loss entirely. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
The ordering path runs against an on-premise Microsoft SQL Server instance installed and administered by the operator; database setup is a documented installation step. https://kb.sambapos.com/en/ · retrieved 2026-08-01
Kitchen display and/or kitchen printer routing continues to function while offline.
reliability-offline-kds-printing
Kitchen printing is LAN-local and KDS traffic goes through the local Messaging Server, so both should survive internet loss, but the vendor does not state this for KDS V2 explicitly. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Feature request open since 2019-08-14, filed after the requester lost deals over the gap; replies confirm SambaPOS relies on the Windows print spooler ('Jobs are queued in windows' — JTRTech) and by 2022 the recommendation is a third-party tool ('you can do back up printer/fail over with Spool Queue Viewer++' — Lee_Midgley, 2022-04-30). No automatic failover to a backup printer or KDS, and no staff alert, ever shipped in core SambaPOS. https://forum.sambapos.com/t/new-feature-printer-backup-fail-over-option/20587 · retrieved 2026-08-03
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
A single shared SQL Server avoids multi-master conflicts by construction — but there is no partition tolerance: if the server PC is unreachable, terminals do not island, they stop. No documented conflict policy. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Offline capability is asserted as a marketing benefit with no published matrix of which features are unavailable offline. https://sambapos.com/ · retrieved 2026-08-01
A public, per-component status page exists showing current and historical incident state without a login.
reliability-public-status-page
sambapos.com/support/ is one screen in its entirety: 'Send us an email or visit the links below for support documents. Contact us: support@sambapos.com', with exactly two links, Forum and Documents. No status, uptime or trust page is offered there or in the site footer (which lists Copyright, Cookie Use Policy, Personal Data Privacy, Terms of Use). status.sambapos.com does not resolve at all (DNS failure, curl exit with no response), and the site's own wp-sitemap page index - 66 pages, retrieved in full - contains no status/uptime/incident page. The cloud-dependent components (licensing check, Metrik, Neptune, GO Kiosk) therefore have no public per-component incident history. https://sambapos.com/support/ · retrieved 2026-08-08
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
Terms of Use 3.3: 'SambaPOS offers license hosting services for its products. SambaPOS does not provide installation and support services for licensed products. Installation and support services are also regulated by contract.' 2.2 defines the Reseller - 'a fully independent company or person who provide support and installation service' - as the party that does. Consistent with that, sambapos.com/support/ offers only an email address (support@sambapos.com) plus links to the forum and the knowledge base; no telephone number, no hours and no support tiers are published anywhere on the site (66-page sitemap checked). The SourceForge third-party listing's '24/7 live support' line is contradicted by the vendor's own contract and should not be used. https://sambapos.com/terms-of-use/ · retrieved 2026-08-08
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
sambapos.com/resellers/ publishes a named directory - 'Our resellers are ready to assist you in many countries' - with per-reseller contact forms, covering US locations (Cloudsbite in TX, Vhizy LLC in DE, Everything But the Food in GA, A & V Business Solutions in IL, JP Solutions in Newark, Signature Hospitality Solutions in OH, Full Motion Technologies in PA, Transformative Network Technology in WA) and UK ones (SMEBIZNESS in Aberdeen, Orderable System in Bournemouth, JTR Solutions, Gofood.UK in Leeds, Link7, Pro Web Design and StoreSeen in London). Terms of Use 2.2 defines a Reseller as 'a fully independent company or person who provide support and installation service for SambaPOS licenses, products, services'. Shortfall: Terms 3.3 says 'SambaPOS does not provide installation and support services for licensed products. Installation and support services are also regulated by contract', and 3.8 that product configuration 'must be made by the user or reseller after licensing' - so go-live is a separate commercial contract with an independent third party, not a vendor service. No certification standard, coverage map, response time or in-person on-site commitment is published, and the free/self-download route (sambapos.com/download/) has no dealer attached at all. https://sambapos.com/resellers/ · retrieved 2026-08-08
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
reliability-hardware-replacement-sla
No vendor hardware, therefore no replacement programme. https://sambapos.com/products/ · retrieved 2026-08-01
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
The claim's verb is publishes, and publication is directly observable on a bound surface. Both hosts were enumerated for this session - 958 documents, the kb WordPress REST registry (329 tr and 286 en posts plus 6 pages), the WP core sitemap including the glossary and faq post types the REST registry does not expose, the www sitemap, and the 17-file wpdmpro download library - and an href fixpoint over the bodies drained to 8 recoverable strays, all held. Fabricated slugs 404 at a fixed 45,059 bytes (45,333 under /en/) while live articles are 50-136 KB, so a zero-hit binds on this vendor. Across that surface, in both languages, case-sensitive: PCI 0 files, P2PE 0, attestation 0, AoC 0, SAQ 0, point-to-point 0. I listed the www English and Turkish page inventories by hand: the vendor publishes a complete legal shelf in both languages - Terms of Use, Privacy Policy, Personal Data and Cookie Use Policy, with Turkish twins - and no security page, trust centre, compliance page or certification page exists beside them. It also publishes jurisdiction-regulatory pages when it has something to say, Regulation TSS for Germany and Regulation TIMS for Samoa, though those are integration marketing rather than attestations and I weight them lightly. No AoC, no validated-P2PE listing and no equivalent is published, which is exactly what this cell asks. Grade F because the finding is an enumeration of the whole surface rather than one carrying document. This says nothing about whether an AoC EXISTS: SambaPOS runs on the merchant's own Windows and SQL Server and never touches card data, so the entity that would hold one is the acquirer, and payments-p2pe-pci4 is deliberately and correctly left unknown for exactly that reason. adversarially verified
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
reliability-mfa-role-based-access
Role-based permissions are strong and documented; MFA on administrative logins is not documented anywhere. https://kb.sambapos.com/en/ · retrieved 2026-08-01
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
reliability-self-serve-training
A free public knowledge base of roughly 275 articles plus an active forum with a V5 Tutorial category and tutorial videos; a dedicated on-terminal training mode is not documented. https://kb.sambapos.com/en/ · 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
SUBJECT: SambaPOS V5 Pro on-premise topology. This is not an absence - the vendor states the restriction affirmatively. KB 2.2.2 What is SambaPOS Messaging Server? How to Install? (English, MODIFIED 2018-04-10): 'Message Server should work only on main computer. Other computers work communicating through Message Server.' The Turkish 2.2.2.a carries the identical sentence. KB 2.1.6 How to Run SambaPOS on Multiple Computers (English, 2023-02-08) repeats it in the technician workflow - the message server runs only on the server, terminals are configured solely as clients pointing at the server's static IP over TCP 1433 - and the licensing-tips article adds that licensing from the main machine automatically licenses the terminals connected to it. So the master role is a build-time property of one named machine holding SQL Server, the Message Server Windows service and the licence, while terminals carry a hardcoded connection string and no database of their own. Corpus-wide in both languages: failover, fail-over, yedek sunucu, cluster, always on and olaganustu durum return ZERO files; the single redundan hit is a GO Kiosk marketing line about redundant operating costs. The only published server-move procedures are manual and offline (2.1.3.b, 2.1.3.c). No promotion, election or automatic assumption of the role exists. https://kb.sambapos.com/en/2-2-2-what-is-sambapos-messaging-server-how-to-install/ · retrieved 2026-09-05 adversarially verified
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
SUBJECT SPLIT, which is why this is partial and not yes. MET: sambapos.com/dojo/ (English, MODIFIED 2023-10-11) under Features of Dojo Card Machines: 'Uninterrupted connection Switch between Wi-fi and mobile data in case of any interruptions in the service. Serve your customers at any time.' A second vendor page, sambapos.com/paymentsense/ (English, 2023-10-11), lists Mobile Data Usage when Wi-Fi is Down among its card-machine features. Turkish twins exist for both. SHORTFALLS, all three: (1) the device is the ACQUIRER's card machine, whereas a SambaPOS terminal is a Windows PC or Android GO client on a wired LAN against a local SQL Server; (2) the Turkish twin sambapos.com/tr/dojo/ renders the same sentence with the verb gecis yapabilir, can switch, which states a capability rather than an AUTOMATIC failover; (3) these are partner brochures, hence grade C, and no KB article supports them - KB 6.14 PaymentSense Dojo Integration is a DLL and automation-command walkthrough that never mentions connectivity. For SambaPOS's OWN terminals there is nothing: across 958 documents in both languages 4G, 5G, hotspot, sim kart, hucresel and mobil internet return ZERO files, case-sensitive LTE returns ZERO, and all three cellular hits are the CellularCallerId device in KB 8.5 and 8.23, an Android caller-ID source with no bearing on WAN failover. https://sambapos.com/dojo/ · retrieved 2026-09-05 adversarially verified
Commercial, compliance & data ownership
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
Core POS is a $339 one-time perpetual license rather than any subscription, which is stronger than month-to-month; but add-on modules bill annually per device with no monthly option. https://sambapos.com/sambapos-v5-pro/ · retrieved 2026-08-01
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
Evidence upgrade E->B: the prior note asserted that no public terms of service or MSA exists, which was wrong — the Terms of Use is cited twelve times elsewhere in this record. There is no early-termination FEE, because the core licence is perpetual, but the contract makes prepayment non-recoverable. Terms of Use 3.18: 'Trial versions of SambaPOS products are offered to users and vendors. Before licensing, products may be tested for a period determined by the user and the vendor. After the user and the seller make the decision to pay for and receive their license, no refunds will be given after the payment has been made.' 3.14 adds that expired licences 'may be temporarily disabled or permanently revoked to disable access to products'. So the exposure on exit is the forfeited annual prepayment on the add-on SKUs (KDS, Mobile Client, GO Tablet, GO Kiosk, Jetrik), not a termination charge. Document is dated 2022-07-27 and is the current published revision; no later one exists. Partial rather than yes because the no-refund rule cuts against the merchant. https://sambapos.com/terms-of-use/ · retrieved 2026-09-05 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
sambapos.com publishes exactly three contract documents (site footer and the full 66-page wp-sitemap: Terms of Use, Privacy, Cookie Use Policy); there is no MSA, EULA or subscription-terms page. The Terms of Use were read end to end. The only licensing/payment clauses are 3.14 - 'Some of the SambaPOS products may be licensed on a lifetime basis, some with monthly payments, some with annual payments, some with user and device-based licenses. Carefully read the description of the product you are buying... Products that have expired licenses may be temporarily disabled or permanently revoked' - and 3.18, 'no refunds will be given after the payment has been made'. Neither an auto-renewal term nor any cancellation notice window (30/60/90 day or otherwise) is stated anywhere in the document; the annual add-on SKUs (KDS, Mobile Client, GO Tablet, GO Kiosk, Jetrik) simply expire and disable. https://sambapos.com/terms-of-use/ · retrieved 2026-08-08
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
No in-house processing exists; the merchant chooses from documented gateway/terminal integrations (Global Payments Integrated, PaymentSense, Dojo, Ingenico, Worldline). https://sambapos.com/integrations/ · retrieved 2026-08-01
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
Not an acquirer, so no rate structure of any kind is published. https://sambapos.com/integrations/ · retrieved 2026-08-01
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
SambaPOS does not process card payments, so there is no processing agreement to cap; the applicable public terms are the Terms of Use, and they reserve the vendor's discretion rather than limiting it. 3.5: 'SambaPOS reserves the right to modify the prices, payment models and periods of its payments at the time of membership. The user and the vendor can use the product and the subscription that they have licensed until the end of the payment period.' 3.16: 'SambaPOS may make changes in the pricing of its products and memberships according to the characteristics of the countries and the laws of the countries... The user and the reseller accept the product offered to them as it is.' 3.18: 'no refunds will be given after the payment has been made.' The only protection an operator has is that the already-paid period runs to its end - there is no cap, no notice requirement, and no penalty-free exit on an increase. https://sambapos.com/terms-of-use/ · retrieved 2026-08-08
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
The base POS and the consumer-facing add-ons are genuinely published, which is creditable. But a buyer cannot price a real deployment from public pages: Neptune (multi-branch), Metrik (dashboards), the GraphQL API licence, and any reseller implementation/menu-build work are all quote-only, and the products index page shows no prices at all. Partial rather than yes. https://sambapos.com/products/ · retrieved 2026-08-01 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
Knowledgebase section 8 documents every module as an independently purchased licence attached to the same cp.sambapos.com account as the perpetual V5 Pro licence: KDS is licensed per device ('purchase SambaPOS KDS License as much as device counts to be used'), Mobile Client 'per Android device', GO Kiosk requires 'SambaPOS GO Kiosk license in the same account that you have SambaPOS V5 Pro License', and Metrik (8.11.1) and Jetrik QR Menu (6.25) are each bought from the cp.sambapos.com Store section. Buying or dropping a module changes only that module's licence; the base POS licence is perpetual and separately keyed, so it cannot be repriced by the module mix. https://kb.sambapos.com/en/cat/additional-modules/ · retrieved 2026-08-06
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
There is no vendor hardware and no lease programme; operators buy commodity Windows PCs, tablets, printers and drawers outright from third parties. https://sambapos.com/sambapos-v5-pro/ · retrieved 2026-08-01
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
Knowledgebase 3.1 states support for 'any type of thermal or dot-matrix ticket printer which ESC/POS compatible' and 'all cash drawers that were triggered by connecting with RJ11 interface through printer', with Android 4.4+ devices (2GB RAM) as clients via the mobile application and Intel-chipset Windows tablets as terminals. Third-party peripherals have their own setup articles (CAS ER Junior and CAS PDN scales, Avery Berkel, Wintec, Datalogic Magellan 93-9400). No SambaPOS-branded terminal is required. https://kb.sambapos.com/en/3-1-hardware-requirements-and-compatibilities/ · retrieved 2026-08-06
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
The full transactional history sits in a merchant-hosted Microsoft SQL Server database the operator installs and backs up; export requires no support ticket and no fee. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Customer entities, account balances and any loyalty ledger built on the accounts module are ordinary rows in the operator's own database. https://kb.sambapos.com/en/ · retrieved 2026-08-01
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
Structurally there is no cutoff — the license is perpetual and the data is local — but this is an architectural consequence, not a documented contractual window. https://sambapos.com/sambapos-v5-pro/ · retrieved 2026-08-01
Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator
commercial-data-ownership-clause
The Terms of Use and Privacy Policy were read in full and neither states that the merchant owns its transaction or customer data. The closest clause runs the other way: 3.12 says only that data 'is entered and saved by the user. For this reason, only the user is responsible for the content and accuracy of the information entered' - responsibility, not title. 4.4 then grants the opposite of a constraint: 'Because the user and resellers use SambaPOS products as a means of trade, any information used may be commercial information. Users and resellers give permission to SambaPOS for the use of this information in the development, marketing activities and the business development, processing and reporting' - with no aggregation or de-identification limit. 4.7 additionally has the merchant authorise Global Payments Integrated to give SambaPOS 'details of my payments transactions; fee and pricing details; underwriting and credit information', and Privacy 3.10 states recorded information 'has lost its confidentiality to SambaPOS'. Note the practical counterweight: V5 runs on the operator's own SQL Server, so the merchant physically holds the data - but that is architecture, not a published right. https://sambapos.com/terms-of-use/ · retrieved 2026-08-08
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
FOUND-AND-SHORT, not a zero-hit, and the two halves of this claim resolve differently. MET (a): sambapos.com/global-payments-integrated/ (English, MODIFIED 2023-10-11) states 'Help keep cardholder data safe and help prevent fraud with full encryption and tokenization'. The same tokenization sentence appears on sambapos.com/worldline-tim-integration-for-switzerland/ (2023-12-29), and end-to-end encryption is claimed in the vendor's own voice on sambapos.com/dojo/, sambapos.com/regulation-tss-for-germany/ and sambapos.com/regulation-tims-for-samoa/ (the last under its own End-to-End Encryption heading), with Turkish twins carrying uctan uca sifreleme. Hardware-encrypted card entry is also structurally real - every one of the 54 documented integrations runs the card on an external PIN pad and SambaPOS never touches it. NOT MET (b): the scope-reduction half is absent everywhere. Across all 958 documents in both languages, case-sensitive: SAQ ZERO files, P2PE ZERO, PCI ZERO, point-to-point ZERO, attestation ZERO. No applicable SAQ is named, no PCI SSC validated-P2PE listing is cited, and no scope-reduction claim is made anywhere. Grade C: these are acquirer capabilities recited on SambaPOS marketing pages, which is the weakest form of a real claim, not an absence. https://sambapos.com/global-payments-integrated/ · retrieved 2026-09-05 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
SUBJECT: SambaPOS as documenter - the claim's verb is documents, which an enumerated corpus can refute. Zero files in all 958 documents, both languages, case-sensitive, for PCI, MFA, multi-factor, two factor, two-factor, 2FA and script integrity; the only OTP hit is a custom reporting tag in KB 9.1.3. The authentication surface the vendor DOES document is the whole of it and it is single-factor: KB 2.2.10.b How to Create / Edit User? (ENGLISH, MODIFIED 2018-05-28; the Turkish twin is a literal translation stamped inside the 2026-08-24 bulk re-save and adds nothing) gives each user a Pin Code and a Password, where 'Pin and Passwords have to consist of minimum 4 character.', 'Pin Code is for entering from SambaPOS screen.' and 'Password is used for connections which will be making through GraphQL.' - a four-character PIN for the POS and a password for the GraphQL channel, with no second factor offered on either, and the back office is a local Windows window rather than a hosted console. For Req 6.4.3 and 11.6.1, SambaPOS hosts no payment page of its own. This scores the vendor's DOCUMENTATION only; it is NOT a finding about any acquirer's CDE posture and it does not describe or discharge the merchant's own compliance obligations. https://kb.sambapos.com/en/2-2-10-b-how-to-create-edit-user/ · retrieved 2026-09-05 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 published Privacy Policy operates under one regime - 3.11, 'SambaPOS shall act within the scope of Republic of Turkey Law No. 6698, and applies the law' - and mentions neither GDPR nor CCPA/CPRA. Its only data-subject mechanism is 3.9, 'The user and the reseller may request deletion of all registered information in SambaPOS due to termination of use', operationalised in Terms of Use 4.3 as an email 'from the users registered email' after which 'all user and reseller information related to the products will be deleted. The user and the seller's rights to use the product and license will be terminated.' That covers the licensee's own account record, not an individual guest's transaction and customer records, and it is coupled to losing the licence. No DPA is offered for execution anywhere on sambapos.com (full 66-page sitemap and 17-item download library checked - only Terms of Use, Privacy and a Cookie Use Policy exist), and no DSAR, right-to-erasure or data-export tooling for a guest appears in any of the 613 KB articles. Customer records live in the operator's own SQL Server, so deletion is reachable by hand-written SQL - which is not in-app tooling. https://sambapos.com/privacy/ · retrieved 2026-08-08
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
The GO Kiosk product page enumerates the product's selling points in full - 'Easy Integration with SambaPOS, Secure Payment Processing, Multi-language Support, Add Unlimited Products, Convenient Order Tracking, Both Horizontal and Vertical Set Up, Valid for EU Wamo QR Payment Ad, Countless Product Descriptions' - with no accessibility feature, no non-visual mode and no conformance statement; the accessibility-adjacent claims are multi-language and vertical/horizontal/countertop layout freedom. No VPAT or ACR is published anywhere SambaPOS publishes: the full wp-sitemap page index (66 pages) and download library (wp-sitemap-posts-wpdmpro-1.xml, 17 files) contain no accessibility, VPAT or conformance item, and the terms 'wcag', 'vpat', 'accessib', 'screen reader' and 'tactile' return zero hits across all 613 KB records in both languages, including the three GO Kiosk articles (8.6 setup, 8.6.1 FAQ, 8.14 V2 configuration). https://sambapos.com/sambapos-go-kiosk/ · retrieved 2026-08-08
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
The mechanism exists in generic form. KB 2.3.13: 'It is possible to add to tickets service charge automatically by percentage calculation or by adding a fixed amount', built as a Calculation Template with an Account Transaction Type, a Calculation Method ('rate from ticket amount') and a Rate/Amount field, surfaced by a Calculation Selector mapped to departments or ticket types; 2.3.13.a does the same from a button and 4.93 varies it by person count. Operators use the same Calculation Templates for a card fee - the forum has long-running threads on credit-card surcharge behaviour (t/21493, 2020). Shortfall, and it is the whole substance of the claim: no card-network compliance layer is documented anywhere. SambaPOS never sees the card, since authorisation belongs to the integrated terminal, so there is no BIN-level automatic exclusion of debit or prepaid cards; the words 'surcharge', 'dual pricing' and 'cash discount' return zero hits across all 613 KB records in both languages; and no required receipt or menu-board disclosure text is generated - receipt content is hand-built in the HTML printer templates. https://kb.sambapos.com/en/2-3-13-how-to-add-service-charge/ · retrieved 2026-08-08
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 90 values — 66 upheld, 18 downgraded, 6 upgraded. It separately resolved 179 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Pricing and identity
| Field | Verdict | What the verifier found |
|---|---|---|
| pricing.software | downgrade-to-partial | Figures I independently verified on the vendor's own product pages: $339 'One Time Payment / Lifetime License' with Windows 10+ requirement; KDS '$69 Annual / Per Device'; Mobile Client '$67' per device annually; GO Kiosk '$337 Annually' (V5 licence required); Jetrik '$99 Annual Fee'. GO Tablet $67 I did not verify. But the SKU list is incomplete in ways that change the cost picture: GoOrder (the only route to DoorDash/Uber Eats/Grubhub) is $49 PER MONTH — a recurring charge larger than every other add-on and nearly twice the base licence per year — and the GraphQL API requires a separately purchased per-location licence at an unpublished price. Metrik and Neptune are also unpriced. Note also that sambapos.com/products/ itself displays no prices; they appear only on individual product pages and cp.sambapos.com/market. source |
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| reporting-public-api | no (documented) | downgrade-to-partial | CONVENTION NOTE: verdict tokens name the TARGET state, not the direction. This is an upgrade to partial. The claim 'no public REST or GraphQL reference exists' is true of the docs, but the dossier's conclusion that there is no API is wrong. SambaPOS V5 ships a GraphQL API on the Messaging Server: you activate it by appending '+' to the port in Samba.MessagingServerServiceTool.exe, authenticate integrators with access tokens against an 'Application' defined inside SambaPOS, and third parties demonstrably run mutations against it ('pushes sales through to samba, waits for a payment and then updates the status'). It is NOT public in the meaningful sense — access requires a purchased licence, the Integrator's GraphQL API Guide was pulled from public view, and there is no versioning/deprecation policy (operators hit hard 404s on all GraphQL calls after the 5.5 upgrade with no notice and no docs). Partial, not no, and not yes. source |
| extensibility-public-api-docs | no (documented) | upheld | Upheld, and now affirmatively sourced rather than inferred from absence. Staff explicitly direct licence holders to 'email [SambaPOS support] and request it along with what you are wanting to build' rather than to any public reference; the GraphQL guide was removed and, as of the last posts in the thread, never restored. This is now a documented absence of public docs, not merely 'I couldn't find any' — but pair it with the correction above: the API itself exists. source |
| reporting-api-not-upcharged | unknown | resolve-to-no | Affirmative vendor-side statement found: 'GraphQL is a paid module. Any location that you wish to use Graphql will need to purchase a license' and 'The api is not an open free api, it is a product.' API access is upcharged per location, on top of the $339 base licence. Price is unpublished. source |
| extensibility-api-access-cost | unknown | resolve-to-no | No longer unknown that it costs money — a per-location GraphQL licence must be purchased, and it is not sold as a listed SKU on sambapos.com/products/ or visible in the Samba Market listing, so the amount remains unpublished. Scored 'no' on the free/included reading of the cell; the dollar figure itself stays unknown. source |
| extensibility-order-injection-api | partial (inferred) | upheld | Partial stands but the reasoning was weak (it leaned on a GloriaFood 'API Activation' step and the abandoned V3 Samba.ApiServer tree). Better evidence: integrators push sales into SambaPOS through GraphQL mutations today. Still partial and not yes, because the write path is licence-gated, undocumented publicly, and demonstrably unstable across minor versions. source |
| labor-clock-in-at-pos | unknown | resolve-to-yes | Researcher missed a shipped module. KB 8.13 'How to Configure Time Clock Module?' states the Time Clock module 'comes along SambaPOS 5.7.0 version' — i.e. in the base product, not an add-on SKU — and covers clock in/out, paid vs unpaid breaks, departments and roles with hourly wage per role, and reporting on hours. A vendor product page markets it separately. Genuine yes. source |
| menu-pricing-modifier-price-by-parent-size | unknown | resolve-to-yes | Researcher missed KB 2.3.5.e 'How to Add Different Order Tag According to Portion'. Order Tag Groups carry a Portion value in their mapping, so each portion (size) gets its own priced tag group, and the article states that after selecting tags, changing the portion changes the order tag prices accordingly. That is modifier pricing keyed to parent size, documented in product docs. source |
| menu-pricing-fractional-placement | unknown | resolve-to-partial | Target state partial (an upgrade). KB 4.60 'Half and Half Pizza Configuration' exists and the researcher missed it: it documents a 'Half and Half Pizza' product with per-half Order Tag Groups so each half carries its own flavour selection. Held to the high bar the brief demands, it is only partial: halves only (no quarters and no other fractions), it is a hand-built configuration of products + order tag groups + actions + rules rather than a fractional-placement primitive, and the article says nothing about printing or displaying which half a topping belongs to. source |
| menu-pricing-half-and-half-rule | unknown | resolve-to-partial | Target state partial (an upgrade). KB 4.60 does implement a pricing rule — max of the two halves, via the automation expression [=TN('[:OrderTagPrice]')] > [=TN('{PRICE}')] followed by an 'HP-Update Tag Price' action that zeroes the individual tag prices. But it is one hardcoded policy the operator wires up by hand, not a selectable max/average/proportional setting, and operators report it mispricing (charging for whichever half was selected first). Not a shipped, configurable half-and-half pricing rule. source |
| inventory-waste-logging | yes (documented) | downgrade-to-partial | Over-generous. KB 4.22 'How to Implement Wastage Stock?' is not a shipped waste-logging feature — it is a build-it-yourself recipe requiring the operator to create a Wastage entity, an Automation Command, an Account Type, an Account, a Transaction Type and a dedicated Ticket Type before any wastage can be recorded. The outcome (stock deducted, cost posted to a wastage account, reportable) is real, but 'documented configuration recipe' is partial, not native yes. Same caveat applies to the kitchen-waste-logging cell, which the researcher already scored partial. source |
| reliability-offline-order-entry | yes (documented) | downgrade-to-partial | A weighted differentiator scored yes off a marketing sentence. The only cited source is a segment blurb on the homepage ('SambaPOS doesn't rely on the internet to run'), which is claim-level. Counter-evidence from the vendor's own forum: a SambaPOS developer confirms 'Mobile Clients control licence over internet every time when you see an entity screen' because licensing is per-user, said 'we are developing a new licence control system for offline users' (Feb 2019), and the thread shows the problem persisting; the KB states the machine 'has to be connected to internet for Licensing and Activation'; and activation drops if the database is moved or renamed. Local SQL Server order entry on an already-activated terminal is architecturally sound, but 'offline order entry' is qualified by an online licensing dependency the vendor has not closed, and there is still no published offline feature matrix. source |
| order-capture-native-handheld | partial (documented) | upheld | Partial stands, but the note understates the defect: the Mobile Client re-validates its licence over the internet every time an entity screen is opened (vendor developer's own words), so the handheld is the least offline-tolerant part of an architecture sold on offline resilience. $67/device/year verified on the product page; feature list is 'Take order with tags, Add order note, Track table status, Get payment' with no card-acceptance detail. source |
| delivery-3p-direct-integration | partial (claimed) | upheld | Partial stands, with a material correction the dossier missed: DoorDash, Uber Eats and Grubhub are not standalone SambaPOS integrations at all — all three links on the integrations page resolve to GoOrder, a separate US-only add-on priced at $49/month on top of an active V5 licence. The KB integrations category contains no DoorDash, Uber Eats or Grubhub article; the only GoOrder article is 'Go Order GloriaFood'. Nothing states these are certified direct connections, and no menu push, 86 sync or store-pause capability is claimed anywhere. source |
| delivery-3p-injection | unknown | resolve-to-partial | Target state partial (an upgrade). The GoOrder page claims 'automatic order transfer to SambaPOS' with routing to kitchen printers and KDS — that is an injection claim. Kept at partial, not yes: it is a vendor marketing page, there is no KB article for the DoorDash/Uber Eats/Grubhub paths, no error-handling or injection-failure visibility is described, and it is a $49/month paid add-on limited to the USA. source |
| extensibility-doordash-preferred | no (documented) | downgrade-to-unknown | Rule violation: a 'no' asserting absence from DoorDash's 2026 Preferred Integration Partner cohort was scored 'documented' with no source URL at all, and I could not verify the cohort list myself. Downgrade to unknown. (Directionally it is probably right — SambaPOS reaches DoorDash through its own GoOrder add-on rather than a named partner listing — but a named-list absence needs the list.) |
| commercial-pricing-published | yes (documented) | downgrade-to-partial | The base POS and the consumer-facing add-ons are genuinely published, which is creditable. But a buyer cannot price a real deployment from public pages: Neptune (multi-branch), Metrik (dashboards), the GraphQL API licence, and any reseller implementation/menu-build work are all quote-only, and the products index page shows no prices at all. Partial rather than yes. source |
| menu-pricing-dayparting | partial (claimed) | downgrade-to-unknown | The cited source does not support the claim. I fetched the Jetrik QR Menu page and it advertises dietary tags, unlimited products, customizable templates and updating the menu 'based on the availability status of your food items' — there is no time-based / breakfast-lunch-dinner menu switching claim on it. No POS-side scheduled price activation found either. source |
| menu-pricing-recipe-linkage | yes (documented) | upheld | Upheld, and the generic kb.sambapos.com/en/ citation should be replaced with the actual article: KB 2.3.15.c documents Manage > Inventory > Recipes, binding a recipe to a product AND a specific portion with per-item quantities, auto-calculating raw product cost plus a Fix Cost field; KB 2.3.15.b adds semi-finished products. This is one of the few 'yes' cells here that is a genuinely shipped feature rather than an automation recipe. source |
| hardware-ownership-vs-lease | yes, grade E, cites sambapos.com/products/ | upheld | Challenged because a differentiator yes stood on grade E with a vendor marketing URL, which the rules do not allow. The value survives on better evidence: KB 3.1 Hardware Requirements and Compatibilities is written purely as a compatibility spec for equipment the operator already owns or buys elsewhere - min Intel i5 10th Gen / 8GB RAM / 100GB disk PC, and any ESC/POS-compatible thermal or dot-matrix printer, keyboard-emulator barcode readers, RJ11 cash drawers through the printer, Cas ER Junior and TEM EGE scales. I also re-read sambapos.com/products/: all nine SKUs (V5 Pro, Mobile Client, GO Kiosk, GO Tablet, Jetrik QR Menu, Metrik, KDS, Android CID, Neptune) are software licences, none a device, and the reseller programme sells licences via cp.sambapos.com rather than hardware. No lease instrument exists to find. Value unchanged, grade E to B. source |
| hardware-usable-after-churn | yes, grade E, cites sambapos.com/product/sambapos-v5-pro/ | upheld | Challenged on the same grounds - differentiator yes at grade E, and the original note was pure inference (nothing can be bricked) with a pricing page attached to it. I went to KB 1.4, which enumerates the whole deployment as third-party commodity kit: Windows 10 or later with .NET Framework 4.8, 1024x768 monitor, ESC/POS thermal or dot-matrix printer, Windows 8.1/10 or Android 4.4+ tablets. Because SambaPOS provisions no device and serialises none, there is no hardware for it to reclaim or disable at churn. I deliberately checked whether the licence mechanism reaches the hardware and it does not - the failure mode documented on the vendor forum (Mobile Client re-validating its licence online on every entity screen) disables the SambaPOS application, not the tablet. Value unchanged, grade E to B; the shortfall on exit is software-side and is scored elsewhere. source |
| order-capture-scheduled-orders | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell (never examined) resolved. Vendor forum documents that future-dated GloriaFood orders enter SambaPOS and print on acceptance, with no lead time and no computed fire time; KB delivery implementations contain no scheduled-order handling. Positive absence, not merely unfound. source |
| menu-pricing-topping-quantity-tiers | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. KB documents order tags as one fixed price plus a max-quantity cap (repeat-add), prefixes as visual-only, and the forum pattern is a duplicated tag per variant — the claim's excluded alternative — so tier multipliers are positively absent. source |
| menu-pricing-included-allowance | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. KB enumerates all Order Tag Group settings (min/max selected, layout) with no allowance/overage field, and staff on the vendor forum recommend auto-applied default tags priced individually as the way to do included toppings. source |
| menu-pricing-countdown-auto-86 | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-partial | Placeholder cell resolved to partial. A vendor-documented automation recipe (KB 4.50) blocks sales at zero inventory, which is a real slice of the capability, but there are no staff-settable par counts (feature request answered with 'implement with current automation'), no automatic 86 of the button, and no scheduled auto-restore. source |
| payments-dual-pricing | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. Price Definitions switch price lists by ticket type, not tender; no mechanism stores or prints cash and card totals together; and the vendor forum shows card-fee passing hand-built as a calculation button — dual-pricing mode positively absent. source |
| payments-surcharge-guardrails | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. The forum-documented surcharge is a manual Update Ticket Calculation button with a hand-picked percentage; no BIN detection, debit exclusion or cap enforcement exists, and SambaPOS processes no card payments for such guardrails to act on. source |
| delivery-zone-pricing | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. Vendor forum builds zone-variable delivery fees from prompts with fixed amounts and custom automation commands; no built-in zone table, and nothing applies fee/minimum/promise time automatically from the address. KB 4.12 contains none of it. source |
| digital-account-saved-payment | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. Enumerated the full nine-SKU product roster and integrations catalogue: no first-party consumer ordering platform exists — kiosk/tablet are in-store, Jetrik is a QR menu without accounts, remote ordering is third-party — so guest accounts with tokenized payment are positively absent from first-party channels. source |
| digital-subscriptions | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. Complete product catalogue contains no subscription/membership/recurring-billing product, and the platform has no payment processing or guest-account infrastructure to run one; scored on enumerated absence from the vendor's own roster. source |
| digital-surcharge-transparency | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. There is no POS-side surcharge/dual-pricing configuration to mirror (it is a hand-built calculation button per the vendor forum), and the first-party digital products document no fee or disclosure controls; parity with a nonexistent engine cannot be present. source |
| guest-loyalty-redemption-fraud-controls | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. The vendor's complete documented loyalty implementation (KB 4.27) is an automation recipe with zero enforcement controls — no velocity limits, no manager approval on adjustments, no self-redemption flagging; only UI state gating exists. source |
| labor-tip-distribution-audit-trail | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. Vendor forum confirms tip capture itself must be hand-built (Tips Account plus custom calculation), and nothing records pool contributions or distributions per employee per shift; custom reports are the operator's own work. source |
| extensibility-oauth-partner-apps | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-partial | Placeholder cell resolved to partial. OAuth2-style token issuance with per-application client credentials, lifetime and active toggle is documented on the vendor forum for the local GraphQL API; shortfalls are undocumented/barely-surfaced permission scoping, per-location paid licensing, and withdrawn public documentation. source |
| extensibility-webhooks-push | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. Vendor forum directs integrators to hand-write JScript post-helper calls inside automation rules to push events to external HTTP services; no webhook subsystem exists and the GraphQL API is request/response — the workaround recommendation establishes absence. source |
| reliability-printer-fallback | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. A printer backup/failover option has been an open feature request since 2019, with replies confirming reliance on the Windows spooler and, by 2022, a third-party tool recommendation; automatic failover with staff alert never shipped. source |
| menu-pricing-dual-pricing | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. KB 2.4.5.a documents multi-price-lists switched solely by ticket type, never by tender, and the vendor forum's card-cost pattern is a hand-built payment-time surcharge calculation on {REMAINING TOTAL} — the excluded alternative to item-level card-as-base dual pricing. No cash/card totals coexist anywhere, and no first-party online channel exists for cross-channel display parity. source |
| payments-offline-decline-liability | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. SambaPOS processes no payments — its whole payment surface is six third-party terminal/gateway integrations — and no store-and-forward or offline card capture is documented anywhere, so there is no vendor-stored offline transaction whose decline liability could be documented and no post-reconnect failure report. source |
| kitchen-expo-consolidation | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. The setup guides for both shipped KDS generations enumerate the full configuration surface — per-device product-group filtering, time-based colour states, per-device bump — with no expo/pass screen type and nothing that gates order completion on every station having bumped its items. source |
| kitchen-printer-fallback | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. Printer failover has been an open vendor-forum feature request since 2019 with no staff reply; community answers are the Windows print spooler, printer pooling, and a third-party redirect tool by 2022 — workaround recommendations that establish absence. KDS guides document no screen failover either. Consistent with the reliability-printer-fallback cell already resolved to no. source |
| digital-group-ordering | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. The enumerable nine-SKU catalogue contains no first-party consumer ordering channel of any kind — kiosk/tablet are in-store, Jetrik is a menu, remote ordering is third-party — so a shareable group-order link with spend caps and split payment is positively absent. source |
| digital-google-order | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. The capability presupposes a first-party direct ordering link, which SambaPOS does not sell; no Google Business Profile or Order with Google provisioning appears on the integrations page, in the KB, or on any product page. Third-party ordering partners' own Google listings are not a SambaPOS capability. source |
| guest-loyalty-thirdparty-identity-attach | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. There is no native guest profile to attach to — the complete documented guest/loyalty implementation is the KB 4.27 hand-built automation recipe — and the only marketplace injection path (GoOrder) documents order transfer and kitchen routing with no customer-identity mapping at all. source |
| guest-loyalty-referral-program | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. The vendor's complete loyalty documentation is a points accrual/redemption recipe with no referral codes or links, no referred-guest attribution and no two-sided rewards, and no referral product exists in the catalogue or integrations list. source |
| labor-break-compliance-by-state | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. The Time Clock module's enumerated settings reduce all break handling to one paid/unpaid toggle; no jurisdiction rule configuration, attestation prompt or missed-break premium flag exists anywhere in the module or KB. source |
| labor-minor-labor-rules | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. No scheduling module exists in the product catalogue for schedule-time enforcement, and the Time Clock module's enumerated settings carry no age field, hour caps, time windows or school-day limits for clock-in enforcement. source |
| reporting-tip-tax-compliance | unknown (placeholder: no public documentation located during the 2026-08-01 research pass) | resolve-to-no | Placeholder cell resolved. Vendor forum establishes that even tip capture must be hand-built (Tips Account plus custom calculation), so no declared-vs-charged report, tip-pool distribution detail or jurisdiction tax summary ships; SambaPOS also processes no cards, so charged tips are invisible to it. Consistent with labor-tip-distribution-audit-trail, already resolved to no. source |
| order-capture-drive-thru | unknown (placeholder — cell had not been examined) | resolve-to-partial | "Multiple lanes are dedicated to mobile orders and delivery, while at least one lane is dedicated to the regular drive thru" — lane differentiation is claimed, but order-point/pay-window/pickup-window separation, sequencing, and pull-forward/parking assignment are not described anywhere on the page or in the KB. source |
| menu-pricing-size-style-matrix | unknown (placeholder — cell had not been examined) | resolve-to-yes | Order tag groups are created per portion (e.g. 'Pizza Features – Normal Portion' vs '– Big Portion'), mapped via a portion column, and the article states "feature prices of product will be different according to portion selection" — a size x topping/style grid with a per-cell price override; the separate Half and Half Pizza Configuration article (4.60) adds a second style axis. source |
| menu-pricing-86-propagation | unknown (placeholder — cell had not been examined) | resolve-to-partial | 86'ing an item is not a native single action — it requires the operator to hand-build "Order Added to Ticket" automation rules with inventory-threshold constraints (KB 4.50). The article's own scope is POS-local — it covers automation rules inside the POS and says nothing about online ordering systems or third-party marketplaces (that is our reading of KB 4.50, NOT a quotation from it) — and the GloriaFood integration article separately confirms no availability sync back to that marketplace. source |
| menu-pricing-3p-menu-push | unknown (placeholder — cell had not been examined) | resolve-to-no | The documented menu-sync direction runs opposite to the claim: the GloriaFood integration "only supports pulling menus from GloriaFood into SambaPOS via a Fetch Menu function," with no push-from-POS path or per-item sync-status/rejection surfacing described; no other listed integration (RestaJet, Jetrik, takeaway.com) documents push-based menu sync either. source |
| kitchen-channel-pause-propagation | unknown (placeholder — cell had not been examined) | resolve-to-no | Availability changes made in SambaPOS are documented as POS-local only — KB 4.50 documents the automation-based 86 mechanism entirely within the POS and covers no sync to online ordering systems or third-party marketplaces (our reading of the article, NOT a quotation from it), and the GloriaFood integration article confirms no availability push in either direction beyond order receipt. source |
| delivery-dispatch-board | unknown (placeholder — cell had not been examined) | resolve-to-partial | "Assign the couriers instantly via the SambaPOS dashboard. Real-time data lets you see who is available to deliver and who is not" describes courier assignment and availability, but multi-order run batching (assigning 2+ orders to one driver as a single run) is not mentioned on this page or documented in the KB. source |
| delivery-driver-tracking | unknown (placeholder — cell had not been examined) | resolve-to-partial | The page claims staff can "add addresses, helpful landmarks, and track the route on Google Maps," but does not describe a driver-facing mobile app capturing live GPS position, falling short of the claim; no KB article documents this mechanism further. source |
| delivery-menu-push | unknown (placeholder — cell had not been examined) | resolve-to-partial | For GloriaFood the documented menu-sync mechanism runs POS-ward, not outward — a "Fetch Menu" pull from GloriaFood into SambaPOS — with no channel-specific markup or push-out-to-marketplace path described; menu-push behaviour for the other listed integrations (RestaJet, Jetrik, takeaway.com) is undocumented. source |
| delivery-86-sync | unknown (placeholder — cell had not been examined) | resolve-to-no | KB 4.50's own out-of-stock automation is documented as POS-local, and covers no sync to online ordering systems or third-party marketplaces; the GloriaFood integration article separately describes order receipt only, with no item-availability sync back to GloriaFood. Both characterisations are ours, NOT quotations from those articles. source |
| delivery-tracking-page | unknown (placeholder — cell had not been examined) | resolve-to-partial | The page claims customers can "check the status of their orders, track the delivery, and know when to expect their food," and that the system sends "delivery notifications ... via SMS and email," but this is a marketing claim with no KB article describing a branded tracking page, its domain, or the order/driver state it is driven by. source |
| digital-fulfillment-modes | unknown (placeholder — cell had not been examined) | resolve-to-partial | Pickup and delivery are documented via GloriaFood/RestaJet, dine-in via standard table service, and curbside pickup is claimed for GO Kiosk ("Drive Thru, Curbside Pickup, and More"), but these are separate add-on modules rather than one integrated flow, curbside arrival check-in is not described, and QR use in GO Tablet (KB 8.7/8.18) is staff scanning to assign a table, not guest-facing QR ordering. source |
| guest-loyalty-unified-profile | unknown (placeholder — cell had not been examined) | resolve-to-partial | Customer Accounts holds transaction/debit-credit history, but the documentation covers "basic account management within a single location context," and there is no dedup/merge behavior documented across in-store, digital-ordering, and kiosk channels. source |
| guest-loyalty-stored-value-gift | unknown (placeholder — cell had not been examined) | resolve-to-partial | Gift certificates are supported only as a DIY tutorial ("it will be explained how to apply Gift Certificate Implementation") requiring the operator to manually build accounts, entity types, and automation rules — not a native shipped balance system — and cross-location redemption across brand locations is not addressed in the documentation. source |
| labor-photo-punch-verification | unknown (placeholder — cell had not been examined) | resolve-to-no | The Time Clock module article documents only clock in/out, break management, department/role assignment, hourly wage settings, and reporting — the full set of configurable options shown — with no photo-capture or facial-verification option among them. source |
| labor-overtime-prevention | unknown (placeholder — cell had not been examined) | resolve-to-no | As with photo-punch verification, the Time Clock module's documented feature set (clock in/out, breaks, roles, wages, reporting) has no overtime warning or clock-in block among it. source |
| inventory-86-auto-sync | unknown (placeholder — cell had not been examined) | resolve-to-no | The documented out-of-stock mechanism is POS-local automation only; the article covers no sync to online ordering systems or third-party marketplaces (our reading, NOT a quotation from it), and the automation rules shown are confined to local POS operations. source |
| reporting-comps-voids-audit | unknown (placeholder — cell had not been examined) | resolve-to-partial | The Void and Gift Report documents fields "No|User|Time|Status|Item|Quantity|Price" — employee and timestamp attribution are present — but there is no manager-approval attribution and no reason-code field documented. source |
| reporting-cash-over-short | unknown (placeholder — cell had not been examined) | resolve-to-no | The Cash Transactions Report is documented as computing "Cash Status ... after subtracting expense total from income total" — a net cash position, not a counted-vs-expected variance; the article enumerates the report's components (income, expense, cash status) without any over/short concept, and no drawer/shift/employee-level reconciliation is described. source |
| reporting-webhooks | unknown (placeholder — cell had not been examined) | resolve-to-no | Consistent with the existing extensibility-webhooks-push finding: no webhook facility exists — the vendor-forum answer to calling an external HTTP service on ticket events is to hand-write JScript using the post helper inside automation rules, with no subscription management, retries, or signature verification. source |
| hardware-drive-thru | unknown (placeholder — cell had not been examined) | resolve-to-partial | The page claims "multiple lanes are dedicated to mobile orders and delivery, while at least one lane is dedicated to the regular drive thru" and positions GO Kiosk for self-service at the window, but outdoor digital menu boards, order-confirmation displays, speaker/headset integration, and a documented timer/speed-of-service measurement are not described. source |
| extensibility-webhook-reliability | unknown (placeholder — cell had not been examined) | resolve-to-no | Per the existing extensibility-webhooks-push finding, no webhook facility exists at all in SambaPOS — outbound HTTP calls require hand-written JScript inside automation rules with no signing, retry/backoff, or replayable event log, so a signed-and-retried webhook cannot be present. source |
| extensibility-headless-embedded | unknown (placeholder — cell had not been examined) | resolve-to-partial | Consistent with extensibility-order-injection-api: integrators demonstrably push sales through SambaPOS's GraphQL API and read back payment status, a form of driving the transaction engine from a third-party UI — but the API is a separately licensed paid module per location, its guide was withdrawn from public view, and it is demonstrably unstable across minor versions, so it falls short of a documented, supported headless mode. source |
| order-capture-kiosk-first-party | partial, grade B - GO Kiosk is first-party ($337/yr) and syncs the SambaPOS men | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| kitchen-station-routing | partial, grade B - Printer templates and printer mappings route tickets by prod | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| digital-qr-table | partial, grade B - Jetrik QR Menu plus GO Tablet cover scan-to-view and tablet | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| digital-kiosk | partial, grade B - GO Kiosk runs the SambaPOS menu with self-service payment; n | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| labor-native-payroll | no, grade B - No payroll product exists in the SambaPOS product catalogue. | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| hardware-os-platforms | yes, grade B - 'Windows 10 or higher Operating System' stated for the POS; | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| hardware-handheld-purpose-built | no, grade B - No vendor handheld exists. The Mobile Client is an app licen | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| hardware-kds | yes, grade B - SambaPOS KDS is a first-party product at $69 per device per | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| hardware-kiosk | partial, grade B - GO Kiosk supports horizontal and vertical orientation on ope | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| hardware-pricing-transparency | no, grade B - The vendor sells no hardware SKUs, so there are no hardware | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| hardware-byod | partial, grade B - Mobile Client and GO Tablet are licensed per device on staff | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| commercial-month-to-month-contract | partial, grade B - Core POS is a $339 one-time perpetual license rather than an | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| commercial-pricing-published | partial, grade B - The base POS and the consumer-facing add-ons are genuinely p | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| commercial-hardware-purchase-outright | yes, grade B - There is no vendor hardware and no lease programme; operator | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| inventory-native-not-partner | yes / B / Inventory, recipes and cost tracking are included in the $339 V5 Pro license, not a s | upheld | Original citation was the sambapos.com V5 Pro product page, a grade-C sales page, which cannot carry a yes on a differentiator. Re-cited to knowledgebase article 2.3.15.c, which describes the recipe editor, the inventory-item material lines and the automatically calculated Fixed Cost, plus 4.71 on defining inventory. The capability is documented first-party and native. source |
| reporting-tier-paywall | yes / B / There are no software tiers - the single $339 V5 Pro license includes custom reports, a | downgrade-to-partial | Original citation was the V5 Pro product page, a grade-C sales page. The knowledgebase does confirm the in-product report builder is ungated - no tier or analytics SKU appears anywhere in section 9, and licensing article 2.5 names only one product licence, V5 Pro. But the multi-location comparison limb of the claim fails: article 8.11.1 states a Metrik licence must be purchased per location alongside V5 Pro, so consolidated cross-site reporting is a paid add-on SKU. Named shortfall, value drops to partial. source |
| hardware-commodity-devices | yes / B / Runs on any Windows 10+ PC bought anywhere; clients run on commodity Android and iOS t | upheld | Original citation was the V5 Pro product page, a grade-C sales page. Re-cited to knowledgebase 1.4 and 3.1, which state the requirement as generic PC specifications plus Android 4.4+/Windows tablet clients. Note the original's iOS clause is not documented - the mobile client articles describe Android only - so the note was rewritten to Windows PC and Android. source |
| commercial-module-unbundling | yes / B / Every module - KDS, Mobile Client, GO Kiosk, GO Tablet, Jetrik, CID - is a separately p | upheld | Original citation was sambapos.com/products/, a first-party sales listing at grade C. Re-cited to the knowledgebase Additional Modules articles, which state per-module and per-device licence purchase requirements in the setup instructions themselves (KDS per device, Mobile Client per Android device, GO Kiosk, Metrik per location, Jetrik from the Store). That is documentation of a-la-carte licensing rather than a price list. source |
| commercial-hardware-not-locked | yes / B / Standard Windows 10+ PCs, Android/iOS tablets from 7 inches, and standard receipt/kitc | upheld | Original citation was the V5 Pro product page at grade C. Re-cited to knowledgebase 3.1, which names generic ESC/POS printers and RJ11-through-printer cash drawers as supported classes rather than a branded device list, and to the per-peripheral setup articles for third-party scales. The original note's 'iOS tablets from 7 inches' is not documented in the knowledgebase and was dropped. source |
| order-capture-seat-level | unknown | resolve-to-partial | Rationale was a bare assertion ('No seat-number tagging documented'). The KB is indeed silent across all 286 English and 327 Turkish articles, but forum.sambapos.com carries a first-party staff statement that payment-screen grouping by seat number works and permits split payment by seat, plus a V5 Tutorial implementing it. Present but hand-built, so partial, not unknown and not yes. source |
| order-capture-coursing-hold-fire | unknown | resolve-to-partial | The old rationale asserted no course/hold/fire feature exists. Course assignment and course-based grouping/printing are documented (forum V5 Tutorial with staff confirmation of the 5.2.12 Update Ticket Grouping feature; KB 2.4.16 for the away message). Hold and fire specifically are not, which is the named shortfall. source |
| order-capture-bar-tab-preauth | unknown | resolve-to-no | Moves off unknown on a first-party statement of absence, not on failure to find. The vendor said the feature is not built and filed it as a feature request; the KB's payment integrations, re-checked through the 2024 Dejavoo and Quest articles, still document no pre-auth. Graded C because the statement is a forum post by a vendor representative rather than documentation, and it is six years old. source |
| order-capture-transfer-audit | unknown | resolve-to-partial | The bare 'no documented ticket-transfer audit log' rationale understated the record: transfer itself is documented as a first-class Change Table action and a ticket-log mechanism exists, though it must be assembled by the operator and never names a transferring and receiving employee pair. source |
| menu-pricing-combos | unknown | resolve-to-partial | The old rationale said no combo construction or automatic conversion is documented; KB 4.43 is precisely that article and had not been read. It is a documented implementation recipe rather than a shipped feature, which is the named shortfall. source |
| menu-pricing-dayparting | unknown | resolve-to-partial | The previous pass correctly demolished a Jetrik QR-menu citation but concluded no POS-side scheduled activation exists. It does: KB 4.2.2 (time-based menu switching) and 4.7 (time-windowed price list) were not read. Partial because it is rule-building rather than scheduling and item-level activation is manual. source |
| menu-pricing-channel-price-books | unknown | resolve-to-partial | The old rationale claimed the only price mechanism was the single global Batch Price List (5.4.9). That is wrong: Price Definitions plus the Price List Editor give per-channel books selected by ticket type (2.4.5.a) or customer type (2.4.5). Partial because the markup-rule half of the claim is genuinely absent. source |
| menu-pricing-dynamic-pricing | unknown | resolve-to-partial | Previous rationale said only static per-portion pricing and manual Batch Price List updates were found; 4.7, 4.63 and 2.4.5.a document automatic rule-driven price variation by time, day and channel. Demand-driven pricing and floor/ceiling guardrails remain genuinely absent, which is the named shortfall. source |
| payments-tip-adjust | unknown | resolve-to-partial | The prior rationale saw only the generic Calculation Type in 4.70. A dedicated Payment Operations tip-adjustment module exists (5.2.20 release notes from the vendor's staff account) and the Dejavoo integration article exposes on-terminal tip adjustment; the batch window and manager screen halves of the claim are still unevidenced, hence partial. source |
| payments-offline-store-and-forward | unknown | resolve-to-partial | The prior rationale asserted SambaPOS documents no store-and-forward behaviour of its own. KB 6.20 does surface a 'Store Forward Working Mode' setting in the GPI Credit Card Controller module, which is positive evidence of a store-and-forward path on one processor; the configurable limits the claim asks for are absent, hence partial rather than yes. source |
| payments-gift-cards | unknown | resolve-to-partial | The prior rationale rested on a SourceForge third-party listing and said no vendor documentation was retrieved. KB 4.31 is vendor documentation for a first-party gift-certificate implementation with account-backed balances and barcode redemption; the multi-location and online-channel halves of the claim fail, so partial. source |
| kitchen-course-firing | unknown | resolve-to-partial | The prior rationale scoped the question to the two KDS articles and concluded nothing exists. Course assignment, on-the-fly course change and course-grouped kitchen printing are documented outside the KDS (staff-confirmed forum tutorial; KB 2.4.16); hold and fire remain absent, which is the named shortfall. source |
| kitchen-bump-bar-hardware | unknown | resolve-to-no | This is an enumeration argument with two legs that meet the bar: an explicit exclusivity statement in the vendor's own KDS requirements ('SambaPOS KDS works only Tablet Devices') and a hardware-compatibility page that enumerates supported peripheral classes with no bump bar among them. The claim also requires documented supported models, of which there are none on either host. source |
| kitchen-sla-alerts | unknown | resolve-to-partial | The prior rationale said no configurable target time or colour escalation is documented; both KDS articles document exactly that, with customisable minute thresholds. Partial because the thresholds are global rather than per station or order type and the audible signal is a new-order chime. source |
| kitchen-item-build-screens | unknown | resolve-to-partial | The prior rationale said the KDS shows ticket line text and ticket tags only, having read only the two KDS articles. KB 4.13 publishes the kitchen-display template and it renders portion plus a complete per-tag modifier breakout. Recipe-step/assembly display is genuinely absent, which is the named shortfall. source |
| kitchen-order-modification-alerts | unknown | resolve-to-partial | The prior rationale, based only on the two KDS articles, said only static ticket-age colour coding and tag display exist. KB 4.13's published template and the KDS Void State setting show voided/gifted lines are visually flagged on a displayed ticket; added and changed items are not, which is the named shortfall. source |
| kitchen-guest-ready-notification | unknown | resolve-to-partial | The prior rationale said no guest notification triggered by a kitchen bump is documented anywhere in the KB. KB 4.13 documents a customer-facing order-status screen fed by an Order Ready command, and KB 4.35 documents guest SMS from a rule; both are hand-built and the SMS depends on a third-party gateway, which are the named shortfalls. source |
| delivery-driver-roster | unknown / F / 'No driver entity, clock state, or per-driver run history documented. A knowledge base search for delivery driver returned only the Caller ID article.' | resolve-to-partial | The prior rationale was a search miss. The full kb.sambapos.com dump (613 records, en+tr) contains KB 4.12 'Advanced Delivery Service Implementation V5.2.3', which documents Deliverers as an entity type with assignment states created by a shipped configuration task. Clock-in/out and per-driver run history remain absent from the Time Clock module doc (8.13) and the whole 9. Reports section. source |
| delivery-store-pause | unknown / F / 'No in-POS control to pause/deactivate the store on a connected marketplace, with or without timed reactivation, is documented anywhere reviewed.' | resolve-to-no | Not a search miss this time: the five marketplace/ordering-channel integration articles each enumerate the complete Go Order settings screen for that channel, which is the entire in-POS configurable surface for the channel, and none carries a store-pause control. KB 6.25 s3.1 places the only open/closed switch in the partner's web panel. Turkish-language articles carry the marketplace evidence. source |
| delivery-injection-error-visibility | unknown / F / 'No integration-health dashboard (failed injections, per-channel connection status, failure alerts) is documented for GloriaFood, RestaJet, takeaway.com, Jetrik, or Shipday.' | resolve-to-partial | The Go Order Working / Not Working status-bar indicator and its documented cause list are integration health surfaced to the operator, and appear in KB 6.25 (en) and 6.16/6.17/6.19 (tr). The failed-injection and alerting halves are genuinely absent, and the Default Category fallback documents a silent failure path. source |
| delivery-offline-behavior | unknown / F / 'No explicit documentation states whether cash delivery orders, driver assignment, or driver settlement continue during an internet outage.' | resolve-to-partial | The claim asks whether the vendor documents offline behaviour for delivery. It documents one component explicitly and repeatedly - internet loss halts Go Order channel intake, with a named indicator and cause list - and is silent on the other three components. That is a documented-in-part answer, not an unexamined one. source |
| digital-native-app | unknown / F / 'No branded consumer ordering app product found. The Mobile Client is a staff app.' | resolve-to-partial | A branded consumer app offering does exist in SambaPOS's channel, via RestaJet - staff-announced on the vendor forum, documented as an integration module in KB 6.4, and still listed on sambapos.com/en/integrations in 2026. It is partner-supplied and separately licensed, which is the named shortfall; the evidence is vendor promotional copy, so grade C and not a yes. source |
| digital-upsell-engine | unknown / F / 'No configurable or algorithmic upsell/cross-sell prompt with attach-rate reporting is documented for GO Kiosk, GO Tablet, GloriaFood, or RestaJet.' | resolve-to-no | Both admin consoles for the vendor's own digital channels are documented as complete screen inventories, not overviews - KB 8.14 for GO Office and KB 6.25 s3 for the Jetrik panel - and neither exposes any suggestion or attach-rate surface. That is a settings-screen enumeration rather than a search miss. source |
| digital-scheduled-pacing | unknown / F / 'No future/scheduled order capacity throttling by daypart is documented in the GloriaFood/Go Order GloriaFood integration articles or elsewhere.' | resolve-to-partial | The prior pass looked only at the GloriaFood articles. KB 6.25 documents a Scheduled Orders screen in the Jetrik panel, so the scheduled-order half of the claim is confirmed; the pacing half is unevidenced and named as the shortfall. source |
| digital-loyalty-attach | unknown / F / 'No documentation ties loyalty accrual/redemption into the GloriaFood/RestaJet/GO Kiosk ordering flow using the in-store guest identity.' | resolve-to-partial | KB 6.25 documents a Loyalty section in the Jetrik ordering panel with Reward activation, a Points screen and a Transactions screen, so the digital channel does accrue and redeem. The shared-identity half fails on the same article's POS Pairing enumeration, which covers menu, order tags and payment types only. source |
| digital-promo-parity | unknown / F / 'No single discount/coupon/loyalty-offer definition is documented as honored identically across POS, kiosk, and digital ordering.' | resolve-to-no | This is positive mechanism evidence, not absence: five integration articles each instruct the operator to create a channel-specific discount account and calculation type so the channel's own promotion can be posted into the ticket, and the kiosk console enumerates no discount surface at all. Offers are authored per channel by construction. source |
| guest-loyalty-10dlc-registration | unknown / F / 'A2P 10DLC is a US requirement; SambaPOS's SMS story is bring-your-own-gateway and says nothing about it.' | resolve-to-no | Upgraded from an assertion to a documented mechanism: KB 4.35 shows SambaPOS is a URL-printer client of the operator's own SMS gateway, not a sending platform, so it cannot handle 10DLC registration; and the full corpus search establishes it does not document it either. Both halves of the claim fail on evidence rather than on silence alone. source |
| labor-offline-time-punch | unknown (grade F) - The Time Clock module documentation does not address offline behavior at all | resolve-to-no | Read the multi-computer setup guide and the Android client setup guide: both make a live MSSQL connection on the same LAN a hard requirement, and no local queue or reconciliation mechanism exists anywhere in the 286-article English KB. The Time Clock settings screen is the whole configurable surface and has no offline option; a still-open forum feature request confirms the gap. source |
| labor-demand-labor-forecast | unknown (grade F) - No staffing-level or labor-hour recommendation generated from POS sales history is documented; the vendor's own 7shifts KB article could not be retrieved | resolve-to-partial | The 7shifts KB article that the earlier pass could not retrieve is 6.45 and it is open; it documents a one-way push of punches and sales actuals into 7shifts. That places the operator's sales history in a labor platform but leaves SambaPOS with no native forecast, so the honest value is partial with the third-party dependency named. source |
| labor-realtime-labor-percent | unknown (grade F) - No live labor-cost-as-percent-of-sales manager view during service is documented | resolve-to-partial | Section 9 of the KB documents a widget that renders a custom report scoped to the current work period directly on a POS entity screen, and the Time Clock module stores hourly wages, so the live figure is constructible from documented primitives; nothing ships pre-built, which is the named shortfall. source |
| labor-qualified-tips-w2-reporting | unknown (grade F) - US 2026 W-2 Box 12 code TP / Box 14b tipped-occupation reporting is not addressed | resolve-to-no | This is not silence but an enumerated payload: the single documented labor-data export lists exactly what it transmits and wages and tips are not part of it, so there is no vehicle for a qualified-tips code. Confirmed against the full English and Turkish KB dumps, which contain no W-2, payroll-file or tipped-occupation content. source |
| labor-payroll-export-formats | unknown (grade F) - Only one labour partner (7shifts) is named; no Gusto/ADP/Paychex/QuickBooks payroll export documented | resolve-to-partial | Retrieved 6.45, which the earlier pass could not open, and it describes a working timecard sync rather than a mere partner listing - enough to move off unknown, but it is a single partner carrying hours and sales without wages or tips, so partial with the shortfall named. source |
| labor-shift-swap-workflow | unknown (grade F) - No self-service shift-swap/open-shift-claim workflow with manager approval is documented | resolve-to-partial | Read the Time Clock settings enumeration and the 7shifts article the earlier pass could not retrieve. SambaPOS holds no schedule, so nothing native can be swapped; the operator reaches the capability only through the third-party platform SambaPOS syncs staff and punches to, which is a limitation worth stating rather than an unknown. source |
| inventory-mobile-count-offline | unknown (grade F) - Android Mobile Client (8.1) is documented for order-taking; no dedicated barcode/QR mobile counting app is documented | resolve-to-no | The count procedure article is a complete workflow, not an overview, and it binds counting to a desktop End of Day document created by ending the work period; the shipped app set each carries a documented feature index and none includes stock counting. Together that is positive evidence rather than absence of evidence. source |
| inventory-vendor-catalogs-edi | unknown (grade F) - No broadline distributor EDI integrations named | resolve-to-no | Rather than rely on a missing integration listing, checked the two places electronic ordering would have to live: the purchase document (manual line entry, supplier is only an entity label) and the file import tool, whose importable-type list is exhaustive and contains no purchasing or invoice object. There is no mechanism for electronic PO transmission or invoice receipt. source |
| inventory-invoice-ocr | unknown (grade F) - No invoice photo/PDF/email ingestion with line-item extraction is documented | resolve-to-no | Two enumerations close this: the purchase document's field set, which is entirely manual, and the import tool's exhaustive list of importable object types, which has no place for a supplier invoice. There is no surface through which a document could be ingested. source |
| inventory-price-change-alerts | unknown (grade F) - No per-item purchase-price-history tracking with threshold alerting on price increases is documented; the Cost Report computes cost but no alerting mechanism is described | resolve-to-partial | The earlier pass understated the data side: purchase prices are held per line per supplier and exposed through the Product Purchase Report and the Display Cost average-price column, which is the tracking half of the claim. The alerting half has no field to key on - the inventory item card's enumerated fields include no contracted or par price - so partial with that shortfall named. source |
| inventory-par-auto-suggest | unknown (grade F) - No par-level-driven or forecast-driven suggested purchase-order quantity generation is documented | resolve-to-no | Checked the inventory item card, which is the entire configurable surface for an inventory item, and it holds no par or reorder field; there is consequently nothing for a suggestion engine to compare against, and no purchase-order object exists to suggest into. The word forecast appears in no KB article in either language. source |
| inventory-shelf-life-expiry | unknown (grade F) - No expiration/use-by date tracking or expiring-soon alerting is documented | resolve-to-no | This rests on two field-level enumerations rather than on search silence: the inventory item card and the purchase document line both list their fields exhaustively and neither has any date attribute, so there is no place to hold a use-by date in the data model. source |
| inventory-bar-partial-bottle | unknown (grade F) - scale integrations are documented for weight-priced products generally, not specifically for partial-bottle liquor inventory | resolve-to-yes | The claim is satisfied by either limb, and the bottle-fraction limb is documented: base unit in cl or ml with a multiplier from the purchase unit, recipes deducting fractions, and counts keyed in base units on the End of Day document. The earlier pass looked only at the scale limb, which is indeed about weight-priced retail items. source |
| inventory-cogs-gl-export | unknown (grade F) - No named QuickBooks/Sage/NetSuite connector | resolve-to-partial | Section 9 documents an account-tag reporting language and SQL over the live database, with file export actions, so period COGS and AP detail can be got out in a chosen layout; no vendor-published mapping to a named accounting system's import format exists, and GL mapping per category is absent, which is the stated shortfall. source |
| reporting-labor-productivity | unknown (grade F) - Item Sales Report and Time Clock reporting exist separately, but no combined report is documented | resolve-to-partial | The two data sets are not merely adjacent, they are in one SQL Server database that the documented custom-report engine queries directly with operator-written SQL, and wages are captured per user - so the capability is reachable, with the shortfall being that the operator builds it. source |
| reporting-channel-profitability | unknown (grade F) - No revenue/margin-by-channel report net of marketplace commission is documented | resolve-to-partial | Channel separation is a first-class construct here (department and ticket type) and the vendor states its basic reports are ticket-type-centric, with cost and profit rate available per product, so the revenue-and-margin-by-channel half is documented; the commission-netting half has no data to work from, which is the named shortfall. source |
| reporting-scheduled-delivery | unknown (grade F) - Custom Reports can be built with SQL and viewed via widgets/pivot tables, but no automatic recurring email/shared-destination delivery schedule for any report is documented | resolve-to-yes | The earlier pass looked only at section 9. The delivery mechanism is in section 2.4: a documented Save the Report to File action feeding a documented Send E-Mail action with a multi-recipient address list, and Triggers supply the recurring schedule through the Trigger Executed rule event. All three objects are vendor-documented with their parameters. source |
| reporting-anomaly-alerts | unknown (grade F) - No proactive threshold/deviation alerting is documented; the Automation Rules engine could in principle be hand-built to notify on a metric, but that is not a shipped reporting feature | resolve-to-partial | The earlier pass named the automation engine and then discounted it; the engine's constraint syntax, scheduled triggers and Send E-mail action are all vendor-documented with worked examples, which makes operator-configured threshold alerting reachable. Historical-pattern deviation has no supporting primitive at all, so partial rather than yes. source |
| reporting-guest-cohorts | unknown (grade F) - No new-vs-returning guest count, visit-frequency, or lifetime-spend cohort report tied to guest records is documented | resolve-to-partial | Guest records are first-class entities with accounts and custom fields, and the documented report engine reaches them both through a dedicated entity-details tag set and through operator SQL; the vendor also ships visit-count-driven promotions. The capability is therefore present but unpackaged, which is a partial with the shortfall named rather than an unknown. source |
| multi-location-cross-location-giftcard | unknown (grade F) - Neptune documents adding branches and assigning products/inventory/recipes to them, but does not describe cross-location gift-card redemption | resolve-to-no | The Neptune article states the sync scope as a closed list - products, menu, stocks, recipes - which is an enumeration rather than an overview, and the gift-certificate implementation is entirely local account and entity rows in a per-branch database. Cross-location redemption has no mechanism to run on. source |
| multi-location-cross-location-loyalty | unknown (grade F) - Neptune documentation does not describe a shared cross-branch loyalty profile/balance/order history | resolve-to-no | Neptune's article closes the list of what is defined per branch and customers are absent from it, while the loyalty implementations are local entity and account constructs in a per-branch database. That is positive evidence that a single profile is not shared, not merely undocumented. source |
| multi-location-multi-brand | unknown (grade F) - No single-terminal multi-brand/virtual-brand operation with separate menus/branding/reportable revenue is documented in Neptune or elsewhere | resolve-to-yes | The earlier pass searched Neptune, which is about branches. The capability is in the core setup documentation: departments give separate menus, price lists, warehouses and screens on one installation; print templates map per ticket type for separate receipt branding; and the vendor states its reports are ticket-type-centric, giving separately reportable revenue. All three limbs are grade-B documented. source |
| multi-location-central-labor-policy | unknown (grade F) - No per-location-group labor rule configuration enforced at the terminal is documented; the Time Clock module (8.13) is a single-location feature set | resolve-to-no | Checked the settings screen itself, which lists every option the module exposes, and no labor rule beyond break enable/paid exists to configure; separately, the multi-branch product's sync scope is a closed list that excludes users and labor settings. Both are enumerations rather than absence of search results. source |
| hardware-handheld-battery-swap | unknown (grade F) - No vendor handheld, therefore no vendor battery-life rating | resolve-to-no | Confirmed the premise against the vendor's own hardware compatibility page, which specifies operator-supplied Windows or Android tablets by minimum OS and chipset rather than any SambaPOS device, and against section 8, where every mobile product is a per-device software licence. The claim's subject does not exist. source |
| hardware-handheld-lte | unknown (grade F) - Android Mobile Client documentation covers device setup and order-taking over the local network; no cellular/LTE failover is documented | resolve-to-no | This is an affirmative architectural requirement, not silence: the vendor states the client must share an IP group with the server and authorizes it for local-network functions only, so an LTE fallback when store Wi-Fi drops is excluded rather than merely undocumented. source |
| hardware-p2pe-terminal | unknown (grade F) - Card entry happens on the integrated third party's PTS device; SambaPOS states no SAQ type for the merchant | resolve-to-partial | Verified the first half against two integration articles that describe the cardholder interacting with the PIN pad, including manual PAN entry on the pad, which keeps the Windows application out of the card path; the second half - a P2PE listing and a stated SAQ type - is absent from the entire KB, and that is the named shortfall. source |
| hardware-tap-to-phone | unknown (grade F) - No Tap to Pay on iPhone/Android acceptance on a commodity phone is documented | resolve-to-no | Rather than rest on absence, checked whether any SambaPOS-authored mobile app can take a payment at all: the Android client's documented function index stops at ordering and printing, and every card flow in the Integrations section is conducted on an external PIN pad. There is no application on the phone that could invoke a contactless kernel. source |
| hardware-remote-device-management | unknown (grade F) - No remote device-management console across terminals/printers/KDS is documented | resolve-to-no | Checked the two cloud consoles the vendor actually operates, each documented as a page-by-page index, and both are licence/commerce portals with no device dimension; the on-premise architecture updates by running the installer per machine. That is a positive account of the management surface, not a failed search. source |
| hardware-selfpour-scales | unknown (grade F) - No self-pour tap wall, flow-meter, or pour-spout integration is documented; the scale integrations found are for weight-priced retail/deli items | resolve-to-no | Checked the vendor's hardware compatibility page, which enumerates supported peripheral categories, and each scale module article, which describes weigh-to-price at the counter. Beverage dispense hardware is absent from the supported list and no article describes pours posting to a tab. Noted that a generic COM-port device can be added as a Custom Scale, which is why this is stated as no integration rather than technical impossibility. source |
| extensibility-menu-write-api | unknown | resolve-to-partial | Grepped all 613 KB records in both languages for graphql/mutation/addProduct: five English articles mention the endpoint, and 4.100 is the only one that writes menu data. It creates a product with group code, barcode and a named portion, but sets the price by direct SQL UPDATE against MenuItemPrices and never writes a modifier. source |
| extensibility-doordash-preferred | unknown | resolve-to-no | Retrieved DoorDash's 2026 DPIP announcement, which enumerates the cohort by name (ten partners). SambaPOS is absent. The developer.doordash.com DPIP overview page was also checked and carries the programme rules but no roster. source |
| extensibility-accounting-connectors | unknown | resolve-to-no | Full-corpus grep of the kb.sambapos.com dump (613 records, both languages) returns zero hits for quickbooks, xero, sage and zoho; the Integrations category index was retrieved and browsed directly and lists no accounting system. The forum's QuickBooks threads (t/13290, t/14960) are user requests with a staff question in reply, not a shipped connector. source |
| extensibility-payroll-export | unknown | resolve-to-partial | Read KB 6.45 in full from the corpus dump: clock-in/clock-out lands in 7shifts Pay Periods and sales in Reports > Actuals. Grepped all 613 records for payroll, gusto, adp, paychex and paylocity - the only hits are 7shifts (26 lines) and the Time Clock article, so there is no second provider. source |
| reliability-public-status-page | unknown | resolve-to-no | Retrieved sambapos.com/support/ in full (it is short enough to quote entirely), retrieved https://sambapos.com/wp-sitemap-posts-page-1.xml and read all 66 page URLs, and probed status.sambapos.com, which does not resolve. No status page exists on any of them. source |
| reliability-247-live-support | unknown | resolve-to-no | Read the full public Terms of Use, which expressly disclaims first-party support for licensed products, and the complete support page, which offers email plus community forum and documentation only. Neither the site nor the KB publishes a support phone number or any hours-of-cover commitment. source |
| reliability-onsite-install | unknown | resolve-to-partial | Retrieved the resellers directory, which names roughly fifteen firms across the US and UK with contact forms, and read the Terms of Use in full: 2.2 makes installation the reseller's defined role while 3.3 disclaims it as a vendor service. That is a real dealer channel but not a first-party or certified on-site offering. source |
| reliability-menu-build-service | unknown | resolve-to-no | The vendor's own contract assigns post-licence configuration to the user or the independent reseller and states SambaPOS will not perform it without a separate agreement; the KB documents menu building as a self-service task with a file-import helper. No onboarding or menu-build offer exists on any of the 66 pages in the site sitemap. source |
| commercial-autorenew-terms-published | unknown | resolve-to-no | Retrieved and read the entire public Terms of Use plus the Privacy Policy, and enumerated the site's 66 published pages from wp-sitemap-posts-page-1.xml to confirm no other contract document exists. The renewal/cancellation terms the claim asks for are simply not in the published text. source |
| commercial-rate-increase-clause | unknown | resolve-to-no | Read the full Terms of Use. Clauses 3.5 and 3.16 grant SambaPOS an unrestricted unilateral right to change prices and payment models, and 3.18 forecloses refunds; nothing in the document caps increases or grants an exit. source |
| commercial-data-ownership-clause | unknown | resolve-to-no | Read both published contract documents end to end. There is no ownership statement, and clause 4.4 expressly permits SambaPOS to use the merchant's commercial information for marketing and business development without an aggregated/de-identified limit - the inverse of the constraint the claim asks for. source |
| commercial-privacy-dsar-tooling | unknown | resolve-to-no | Read the full Privacy Policy and Terms of Use: the sole data-subject route is an email that deletes the account holder's registration data and terminates the licence, framed under Turkish Law 6698 only. Enumerated the site's published pages and download library - no DPA. Grepped the whole KB corpus - no DSAR/GDPR/erasure tooling. source |
| commercial-wcag-kiosk-accessibility | unknown | resolve-to-no | Retrieved the GO Kiosk product page and read its complete feature list; enumerated the vendor's entire published surface via wp-sitemap-posts-page-1.xml and wp-sitemap-posts-wpdmpro-1.xml; grepped the full KB corpus for accessibility terms. No conformance report exists to find and the kiosk documentation describes no non-visual access mode. source |
| commercial-dual-pricing-compliant | unknown | resolve-to-partial | Read KB 2.3.13, 2.3.13.a and 4.93 from the corpus dump: a percentage or fixed Calculation Template attached to a ticket via a Calculation Selector is the only fee mechanism SambaPOS documents, and it is card-blind. Grepped all 613 records for surcharge, dual pricing and cash discount - zero hits - so the compliance half of the claim (debit/prepaid exclusion, disclosure) is undocumented. source |
| delivery-store-pause | no / B / "SambaPOS's marketplace channels are Go Order Yemek Sepeti (KB 6.16), Trendyol Yeme" | downgrade-to-unknown | Checked whether the five-channel enumeration the no rests on is complete. It is not. The vendor's own release notes announce 'Go Order USA Integration added (Uber Eats, Doordash, Grubhub, Gloriafood)' in 5.5.8 and further GoOrder USA fixes in 5.6.0, 5.6.2 and 5.7.8, and sambapos.com/goorder-usa/ still sells it at $49/month; kb.sambapos.com documents it nowhere (zero hits for doordash, uber eats or grubhub in all 613 en+tr records). A sixth channel family whose in-POS settings screen nobody has seen defeats the enumeration. source |
| guest-loyalty-10dlc-registration | no / B / "KB 4.35 documents the whole of SambaPOS's SMS capability: the operator pastes the U" | downgrade-to-unknown | Tested the load-bearing premise that SambaPOS is only a client of the operator's own gateway. The vendor's 5.5.8 release notes add a native Twilio SMS integration as a rule action, which puts a US aggregator relationship inside the product and makes 10DLC registration a live question rather than a category error. kb.sambapos.com never mentions Twilio in either language, so the KB is demonstrably not a complete record of shipped features and the zero-hit search for 10DLC/A2P cannot carry an assertion of absence. source |
| multi-location-central-labor-policy | no / B / "8.13 enumerates the Time Clock module's whole settings surface: Settings ('Enable T" | downgrade-to-unknown | Tested whether KB 8.13 really is the Time Clock module's entire configurable surface. It is not: the article dates from 2023-10-11 and the vendor's own release notes add 'Time Clock payroll overtime settings' in 5.7.8 (2024-01-31) plus further Time Clock changes in 5.7.6, 5.7.10, 5.7.22 and 5.7.26, none of which the article reflects. The specific assertion that no overtime threshold exists is contradicted by the vendor. The single-site architecture still makes a per-location policy unlikely, but a stale settings list cannot carry a positive assertion of absence. source |
| hardware-tap-to-phone | no (grade B) - 5.1.12.a is the Android client's manual and its index is the app's whole function set: Entry | downgrade-to-unknown | Re-read the cited 5.1.12.a index and then the two mobile articles the first pass said it had not opened. KB 8.10 (MC3, 2023) documents an Android and iOS client with an explicit 'Getting Payment' step - 'Select desired table, click on Settle button' - which refutes the note's central assertion that no SambaPOS phone app has a payment or settle screen. KB 8.18 (GO Tablet V2, 2025) confirms the tablet product is order-taking only and states it 'won't work on mobile phones'. A web search for SambaPOS tap to pay / tap on phone returned only generic processor material, so there is no counter-evidence that the capability exists either. source |
| hardware-remote-device-management | no (grade B) - 5.5.9 indexes the customer portal at cp.sambapos.com in full - Login, Password Reminding | upgrade-to-partial | The enumeration covered one portal out of at least six. Grepping the KB dump for sambapos.com hosts surfaced cp, one, gooffice/toffice, koffice, kdsadmin, neptuneadmin and update; koffice and toffice no longer resolve, but gooffice.sambapos.com answers 200 and one.sambapos.com answers 200. I pulled both SPA bundles and read their route tables and i18n dictionaries. GO Office ships /tablets, /kiosk, /logs, /licenses, /remove-tablets and /remove-kiosks routes, an online/offline/error status vocabulary keyed to kiosk and tablet, per-device logs keyed by Device ID, and a scoped remote update push. That is device management, so the flat no is wrong; it is partial because nothing covers Windows terminals or KDS and there is no reboot, version or staged rollout. I also checked one.sambapos.com, whose declared routes contain no device page, which closes the first pass's own worry that it had never been opened. source |
| hardware-selfpour-scales | no (grade B) - 3.1 lists the supported peripheral classes: computer, monitor/touchscreen, printer, ta | downgrade-to-unknown | Re-read KB 3.1 in the dumped corpus. It is a requirements-and-compatibility page written class by class, with no sentence claiming the list is exhaustive, and its scales paragraph explicitly admits any COM-port device as a Custom Scale - which is the opposite of a closed supported-hardware table. I also ran forum.sambapos.com /search.json for flow meter, self pour, tap wall, beer dispense, PourMyBeer and iPourIt and got zero topics, so there is no counter-evidence that the capability exists; but a search returning nothing does not license a positive assertion of absence. source |
| extensibility-accounting-connectors | no (grade B) - Vendor-maintained integrations on SambaPOS are all delivered the same way - a separately | upgrade-to-partial | The enumeration premise - that every vendor-maintained module gets a numbered section-6 KB article and a cp.sambapos.com SKU - is false, and it was the load-bearing part of this cell. I opened one.sambapos.com (200, live SPA) and read its shipped bundle: it declares a six-route Mikro ERP module with account, payment-type and stock mapping, chart-of-accounts codes, cash/bank/POS account selection, cost-centre and project defaults, and per-work-period posting with retry state. Nothing about Mikro appears in the 613-record KB dump, so the KB is not a complete inventory of SambaPOS integrations. QuickBooks Online remains absent by the same grep, so the cell moves to partial rather than yes. source |
| labor-qualified-tips-w2-reporting | no (grade B) - SambaPOS produces no payroll file. 6.45 enumerates what leaves the product for labor purposes | upheld | The premise that the Time Clock has no cash-versus-charged tip concept is refuted: 5.7.6's release note adds a cash tip declaration and a 2024-03-05 screenshot of the live 5.7.8 settings screen shows 'Declare Cash Tips' plus a Payroll Options block with payroll-period type, start date and length. That changes the reasoning, not the value - the payroll block computes a period, it does not emit a file, and 6.45 remains an enumerated payload in which wages and tips do not appear. Re-grepped both KB languages and every release note 5.5.0-5.7.28 for W-2, Box 12, TP, Box 14b, tipped occupation and payroll export: nothing. source |
| labor-overtime-prevention | no (grade B) - As with photo-punch verification, the Time Clock module's documented feature set has no overtime warning | upheld | The cited enumeration is stale - KB 8.13 was last modified 2023-10-11 for 5.7.0 and 5.7.8 (2024-01-31) announced 'Time Clock payroll overtime settings added', so the note asserted the absence of a feature that shipped. I recovered the actual surface from screenshots of 5.7.8 in forum topic 28024: overtime is a Daily Hours threshold with Daily, Double and Weekly overtime RATES, per role, under Payroll Options. That is overtime pay, not overtime prevention, and no warning or clock-in block appears in the settings, the punch flow or any release note through 5.7.28. Value stands on new evidence; grade drops to C because the source is a user screenshot, not documentation. source |
| labor-break-compliance-by-state | no (grade B) - The Time Clock module's documented settings surface (KB 8.13) is fully enumerated, and its entire break capability is one toggle | upheld | KB 8.13 is not the complete settings surface it was treated as: it predates 5.7.6, 5.7.8 and 5.7.26, and 6.45 documents an 'Enable 7shifts Integration' option on the same screen that 8.13 never lists. I therefore re-derived the surface from a 2024-03-05 screenshot of 5.7.8, which shows Enable Time Clock, Force Users for Clockin Before Login, Declare Cash Tips, Enable Breaks, Break Mode, Payroll Options and Overtime Options - breaks still a single paid/unpaid selector, with no jurisdiction rules, attestation or premium flag - and cross-checked the vendor's Time Clock product page and every release note 5.7.0-5.7.28. source |
| labor-minor-labor-rules | no (grade B) - Both halves absent: no scheduling module exists in the nine-SKU catalogue, and 8.13's enumerated settings carry no age field | upheld | The clock-in leg rested on KB 8.13 being exhaustive, which the 5.7.6 and 5.7.8 additions disprove, so I re-read the module off screenshots of 5.7.8 and 5.7.0 (forum topics 28024 and 27548): settings, departments, roles, assignments, a users grid of User Name / Name / Surname / Last Clock In / Last Clock Out, and reports. Still no birthdate, hour cap or time window. The scheduling leg stands independently and is better evidenced by 6.45, which puts the roster and pay periods on the 7shifts side, than by a count of SKUs. source |
| labor-photo-punch-verification | no (grade B) - The Time Clock module article documents only clock in/out, break management, department/role assignment, hourly wage | upheld | The note's premise - that 8.13 shows 'the full set of configurable options' - is false for any version after 5.7.6, so I checked the module as shipped instead. Screenshots of 5.7.0 and 5.7.8 show the whole punch path (PIN, Select Your Role, Clock In, clock-out confirmation) and the Time Clock Users grid, which has no image or verification column, and the 5.7.8 settings screen has no capture option. No camera, photo or facial feature appears in any release note 5.7.0-5.7.28 or anywhere in the 613-record KB dump. source |
| kitchen-channel-pause-propagation | no (grade B) - KB 4.50 states the automation-based 86 mechanism 'provides no information about syncing to online ordering' | upheld | Two defects in the reasoning. KB 4.50 contains no such sentence - the quotation was the researcher's own summary set in quotation marks - and the documented channel set was incomplete, since GoOrder USA (DoorDash, Uber Eats, Grubhub) shipped in 5.5.8 and is absent from the KB. So I checked the outbound direction directly: 6.29's Go Order settings surface, the vendor's GoOrder USA feature page and the GO Office application bundle's route table are all order-intake or first-party-menu only, and Jetrik's open/closed switch sits on the Jetrik panel rather than in SambaPOS. source |
| delivery-86-sync | no (grade B) - KB 4.50's own out-of-stock automation is documented as POS-local, with 'no information about syncing to online ordering' | upheld | The quotation attributed to KB 4.50 is not in the article, and the same fabricated line was carrying three cells. Read 4.50 in the crawl: it is a rule that shows a message and cancels the last order, with no availability flag anywhere. Then checked whether any 86 state exists to push - the only one is a manual GO Office toggle for GO Kiosk and GO Tablet, whose bundle has no marketplace concept - and re-checked the channel side, where GoOrder USA's own product page lists order transfer, tracking, reporting, printing and a dashboard and nothing outbound. source |
| inventory-86-auto-sync | no (grade B) - The documented out-of-stock mechanism is POS-local automation only; the article 'provides no information about syncing' | upheld | The quoted sentence is absent from KB 4.50. Reading the article, the mechanism is a rule that shows a message and cancels the last order at zero stock - it does not 86 anything. Separately searched for a real availability flag: GO Office does carry a manual Sold Out state for GO Kiosk and GO Tablet products, which the first pass missed, but it is operator-set with no inventory linkage, and its bundle declares no marketplace or online-ordering route. Neither the automatic trigger nor the third-party reach the claim describes exists. source |
| menu-pricing-3p-menu-push | no (grade B) - The GloriaFood integration 'only supports pulling menus from GloriaFood into SambaPOS via a Fetch Menu function' | upheld | The cited article is the deprecated one - 6.3 opens 'This product is no longer supported' and points to the Go Order replacement - and the note also missed that a Send Menu function exists, so the reasoning was wrong twice. I traced every Send Menu target in the crawl: GO Office (kiosk, tablet), SambaPOS KDS, GO Menu and Jetrik, all first-party or own-brand channels. No marketplace provider has one, marketplace menus are paired by hand, and no per-item status or rejection reporting is documented for any channel. source |
| guest-loyalty-native-email-sms | partial (grade B) - SMS sending is documented via operator-configured third-party gateway API URLs; no native email campaign tool found | upheld | Both stated grounds are wrong. A native 'Send E-Mail' action with full SMTP parameters is documented in 2.4.12.e, and 5.5.8 added a native Twilio SMS action, so this is not a bring-your-own-gateway-only, email-less product. Partial survives on a different shortfall that I checked for directly: nothing in either KB language or in any release note 5.5.0-5.7.28 provides segmentation, scheduling, campaign or template management, send reporting or opt-out handling - both channels are per-event automation actions. The cell also cited the knowledge-base root rather than a page; replaced with the article that shows the action. source |
| digital-sms-ordering | unknown (grade F) - SMS is implemented as a URL Printer; the operator pastes their own gateway's URL, strictly outbound | upheld | The rationale's premise that SMS is only an operator-supplied gateway URL is refuted by 5.5.8, which added a native Twilio SMS action that the knowledge base never documents. It does not move the cell: the Twilio action is a send, like the URL Printer, and I found no inbound SMS or chat endpoint in either KB language or in any release note through 5.7.28, while the automation engine and GraphQL API still make a bridge buildable. Reasoning corrected, unknown at F retained. source |
| extensibility-middleware-compatibility | unknown / F / 'Grepped the full kb.sambapos.com dump (613 records, English and Turkish) for Delive' | upheld | Re-tested after the KB was shown not to be a complete feature inventory. Two independent legs replace the grep: the vendor's own staff release series (68 topics, 5.1.47-5.7.28) announces no aggregation-middleware integration in eleven years while announcing every other integration the product shipped, including the KB-undocumented GoOrder USA; and Otter's and ItsaCheckmate's published POS partner directories, 21 and 28 named systems, both omit SambaPOS. Not moved to no because the claim requires two endpoints and Deliverect's POS list renders client-side (only Micros Simphony and Flooid resolve to a fetch) while chowly.com/integrations 404s. Value and grade unchanged; the reasoning is withdrawn and replaced. source |
| guest-loyalty-privacy-rights-tooling | unknown (grade F) - Searched all 613 en+tr kb.sambapos.com records for GDPR, KVKK, kisisel veri, data | resolve-to-no | Re-opened this after the KB-is-the-feature-set premise fell. Two forum threads four years apart show the same thing from the vendor side: in t/23357 (2020) a staff member answers a request for built-in anonymisation with 'Sure this could be done with automation, its only update entity data', and in t/28362 (2024) an operator states outright that an entity attached to a ticket cannot be deleted and that the feature has been requested for future releases, while the staff reply argues against deleting rather than pointing at a tool. That is a vendor-recommended workaround plus a stated limitation, which is positive evidence of absence; the bulk Excel export in KB 4.94 is not per-subject and nothing propagates a deletion to the loyalty or account records. Graded C because the evidence is vendor forum statements rather than documentation. source |
| guest-loyalty-redemption-fraud-controls | no (grade B) - KB 4.27, the vendor's complete documented loyalty implementation, is an automation recipe | upheld | Value upheld, reasoning withdrawn and replaced. Calling KB 4.27 the vendor's complete documented loyalty implementation rests on the KB being a complete feature inventory, which this vendor's release stream disproves. What actually carries the cell is the vendor's own statement that loyalty is deliberately not a pre-made module (JTRTech [STAFF], t/13833) together with the three loyalty and stored-value recipes the KB does publish (4.27, 2.4.9, 4.31), all of which move points as ordinary account transactions with no approval, velocity or self-redemption control. I also read the whole 68-topic staff release series 5.1.47-5.7.28: loyalty occurs in it only as a print-template calculation name, and no loyalty module is ever announced. source |
| guest-loyalty-referral-program | no (grade B) - The vendor's complete documented loyalty capability (KB 4.27) is a hand-assembled points | upheld | Value upheld, reasoning corrected. 'Complete documented loyalty capability' was an appeal to KB completeness and had to go. In its place: the vendor states on its own forum that loyalty is intentionally not a pre-made module, and the KB's loyalty and stored-value material is three build-it-yourself recipes (4.27, 2.4.9, 4.31) whose data model is an entity custom field plus an account - there is no code object, no referrer-referee link and no attribution surface for a referral to use. I read the full 68-topic staff release series through 5.7.28 and searched the forum for referral and refer-a-friend: no referral feature exists in either. source |
| guest-loyalty-thirdparty-identity-attach | no (grade B) - There is no native guest profile for a marketplace order to attach to... GoOrder documents | upgrade-to-partial | The original note said GoOrder documents 'no customer-identity mapping of any kind', which was drawn from the GoOrder marketing page because GoOrder is one of the products missing from the KB dump the record was scored against. GoOrder is in fact documented: KB 4.79, 4.80, 4.85 and 4.87 publish per-provider printer tag lists in which the marketplace guest's first name, last name, mobile phone and full structured delivery address are available on the ticket. So the tickets are not anonymous and half the claim is met. The other half is not: I read the complete GoOrder setup walkthrough (KB 6.29) and it creates Deliverer entities, a delivery ticket type and print jobs with no customer entity mapping anywhere, and the Yemeksepeti integration guide handles customers by having the operator create them manually at the POS. Partial, with the shortfall named. source |
| inventory-mobile-count-offline | no (grade B) - 5.5.7.d is the whole counting procedure... SambaPOS's companion apps are enumerated in | upheld | Value upheld, one leg withdrawn. The claim that section 8 enumerates the companion app set is exactly the premise this vendor's release stream refutes - GoOrder is a shipped product that appears in no section-8 index. What carries the cell is KB 5.5.7.d itself, a complete procedure that binds counting to a desktop End of Day document created by ending the work period, so there is no count session for a handheld to hold offline. I re-read KB 8.10 (MC3), which requires the device to share the server's IP group, and searched both the 68-topic staff release series 5.1.47-5.7.28 and the forum for a stocktake or inventory-count app: neither exists. The only inventory scanning ever added is a barcode field on inventory items for the desktop purchase screen. source |
| inventory-vendor-catalogs-edi | no (grade B) - 'Nothing sends a purchase order anywhere - no PO object exists in the product - and 2.4.2 enumerat' | upheld | Re-evidenced after the KB-completeness premise was refuted. Re-read 5.5.7.b in full (hand-keyed purchase lines, supplier as an entity label) and 2.4.2's importable-object list; both are mechanism and enumeration arguments that do not need the KB to be exhaustive. Dropped the 'the 19-article Integrations section contains no distributor' leg, which did need it, and substituted a search of the 5.1.15-5.7.28 release series: no purchase order, supplier catalog, distributor or EDI item appears in any of the 68 topics. Value unchanged. source |
| kitchen-order-ready-callback | unknown (grade F) - 'No DoorDash/Uber Eats/Deliveroo connector exists in the 19-article Integrations sect' | upheld | Re-evidencing, not a value change. The rationale's premise that no marketplace connector exists is refuted by the 5.5.8 release note announcing Go Order USA for Uber Eats, DoorDash, Grubhub and GloriaFood. I re-read KB 8.9 and 8.19 (bump is a local Kitchen->KReady state change and card move) and searched the whole 5.1.15-5.7.28 release series for any outbound order-status or callback item: none. That leaves the outbound direction undocumented rather than documented-absent, so unknown stands with the false leg removed. source |
| kitchen-order-throttling | unknown (grade F) - 'The four inbound online-order integrations (GloriaFood 6.3, Go Order GloriaFood 6' | upheld | Re-evidencing, not a value change. The rationale counted the online-order channels off the KB and got four; the release series names at least eight providers, several of which the KB never mentions. I corrected the enumeration and then checked the thing that actually matters - whether any channel or the KDS carries a pacing control - across all 68 release topics through 5.7.28. No delay, hold, throttle or quoted-prep-time item exists, but neither does a statement of absence, so the cell remains unknown. source |
| labor-tip-pooling-rules | unknown (grade F) - 'Checked every occurrence of tip in the 613-record kb.sambapos.com dump (286 Engli' | upheld | Re-evidencing, not a value change. The rationale's method was a grep of the KB dump, and the KB is now known not to be the feature set - 5.7.6 added a Time Clock cash-tip declaration that appears nowhere in it. I re-ran the question against the release series instead: every tip item from 5.1.15 to 5.7.28 is capture or card-tip adjustment (5.7.6 declare cash tips, 5.7.24 Dejavoo tip adjust, 5.7.28 tip and split-payment calculation), with no pooling, share or tip-out feature and no staff statement that pooling is unsupported. Unknown stands. source |
| menu-pricing-dual-pricing | no (grade B) - 'never on tender... and there is no first-party online-ordering channel for the claimed' | upheld | Re-evidenced after the KB-completeness premise was refuted, and one factual leg withdrawn. Re-read 2.4.5.a: Price Definitions are selected by an Update Order rule constrained on {TICKET TYPE}, which is the mechanism the value rests on and needs no assumption that the KB is exhaustive. The claim that no first-party online channel exists is wrong - Jetrik, GO Kiosk, GO Tablet and GO Menu all take a Send Menu push - so I checked those instead and each receives a single price per product and portion. No dual-pricing or cash-discount item appears in the release series through 5.7.28. source |
| multi-location-cross-location-giftcard | no / B / "Neptune is the multi-branch product and 10.2 states its scope explicitly: 'After the b" | downgrade-to-unknown | Re-read the two staff release posts that the KB never reflects. 5.3.2 adds a Valutec gift-card integration (US only) and 5.7.16 adds gift-card support to the Dejavoo integration, so gift cards on this product are not necessarily local database rows and Neptune's product/menu/stock/recipe sync scope no longer implies anything about them. Neither release, nor any KB article, says whether those network-hosted cards redeem across a brand's locations or produce a consolidated liability figure, so the positive evidence of absence is gone and nothing replaces it. source |
| order-capture-catering | unknown (grade F) - "'catering' occurs once across all 613 dumped records, in passing inside 2.2.1" | resolve-to-partial | The KB search that produced the unknown could not see the Reservation module, which is undocumented there. Read the 5.2.14 release post ('Reservation added') and post 149 of the 5.2.13 beta thread, where emre (staff/admin, verified via the topic JSON) walks through pre-order tickets that record orders and deposit payments, a configurable 50%-by-default deposit, a dated reservation list with check-in and no-show, and conversion to a real ticket with the deposit applied as a discount. Deposits, balance-due tracking and a schedule separate from the order queue are therefore real; a catering-specific flow, quote document and event/delivery schedule are not, which is the named shortfall. source |
| order-capture-order-ready-signal | unknown / F / "Checked kb.sambapos.com 6.3 (GloriaFood) and 6.29 (Go Order GloriaFood) in full ... no" | upheld | Value upheld, reasoning withdrawn and replaced. The claim that SambaPOS has no marketplace connectors is false - GoOrder USA (Uber Eats, DoorDash, Grubhub) shipped in 5.5.8 and the Turkish GoOrder connectors add Yemeksepeti, Trendyol, Getir and Migros - and the Getir article's 'Otomatik Onay' shows an acceptance state being pushed back to the platform. I still found no documentation of a ready-state or prepared callback from POS or KDS in either the KB or the release series, so unknown is correct on the evidence that actually exists rather than on a false enumeration. source |
| order-capture-throttling | unknown / F / "the volume controls documented are 4.55 'How to Determine Daily Limit for Item Sales'" | upheld | Value upheld on a corrected basis. The prior note's enumeration of the inbound-order surface was wrong by more than half; I read the Turkish GoOrder articles (6.16 Yemeksepeti, 6.17 Trendyol, 6.18 Migros, 6.19 Getir) and the GoOrder USA release, and none carries a capacity, time-slot or quote-time setting - only auto-accept, initial ticket state and mapping. The release series adds no throttling feature through 5.7.28. Absence, not a stated limitation, so unknown stands. source |
| payments-tip-pooling | unknown / F / "4.70 (tips post to one Tip sales account through a Tip transaction type - no employee" | upheld | Value upheld, one supporting statement withdrawn. The 5.7.6 release post adds a Time Clock cash-tip declaration per employee, which the KB's Time Clock article does not carry, so the claim that no tip-per-employee measure exists was wrong. It does not reach the claim: declaring tips is not pooling them, and no vendor source in the KB or in the 68-topic release series describes allocation by hours, sales, role percentage or points, nor a payroll export of allocations. source |
| reporting-cash-over-short | no / B / "The Cash Transactions Report is documented as computing 'Cash Status ... after subtract" | downgrade-to-unknown | Re-read the cited article: it enumerates the blocks of one report, not the reporting surface, so it can only establish that the Cash Transactions Report has no over/short block - the product-level conclusion needed the KB to be exhaustive. Searched both KB languages and the full release series for a counted-cash or variance feature and found none, but also found 5.7.6 shipping an undocumented Time Clock cash-tip declaration, which is exactly the class of counted-cash feature the KB would not have shown. The assertion of absence cannot be sustained and nothing supports a yes or partial either. source |
| reporting-nl-query | unknown / F / "No natural-language or assistant surface appears in the 286 English or 327 Turkish KB p" | upheld | Value upheld and the note's own stated gap closed. I searched the complete V5 Release and V5 Beta Release dump (68 topics, 1,451 posts, through 5.7.28 of 2026-07-02) for AI, artificial, assistant, natural language and chat: the only assistant reference is a 2017 community joke, and the only chat feature is Team Chat between staff in the mobile client. No natural-language reporting surface is announced. Still an argument from silence across two corpora, so unknown rather than no. source |
| menu-pricing-upsell-prompts | unknown / F / "No prompt configuration appears in 4. Customization (67 articles) for the POS itself" | upheld | Value upheld, one supporting statement withdrawn. The rationale asserted that no per-item prompt configuration exists for the POS; KB 2.3.5.h documents the Auto Select flag, and Emre Eren recommends it by name in V5 Request t/7569 as the way to make modifiers pop up the moment an item is rung. It does not reach this claim - Auto Select shows the item's own order tags, is a single product-level flag with no per-channel behaviour, and nothing in section 9's report tags measures prompt display or attach rate - so the cell stays unknown on corrected evidence. source |
| payments-qr-guest-pay | unknown / F / "Roadmap statements are not evidence of a shipped capability, and nothing states it is un" | resolve-to-no | The rationale's stated blocker was that nothing said the flow is unsupported. Two vendor answers do. On the 5.3.6 release topic VehbiEmiroglu answered the direct question about ordering from the QR menu with 'Not for now. Its only show your menu', and on t/24966 Jesse Parker answered a request for an integrated order-and-pay app with 'We have one coming soon but right now no'. I checked both the KB and the whole release series through 5.7.28 for a shipped guest-device payment surface since and found none, so the not-yet reading is the current one. source |
| payments-card-on-file | unknown / F / "Nothing states tokenised card-on-file is unsupported as a matter of design, so unknown" | resolve-to-no | Re-fetched t/21455 as JSON and confirmed the quotations are real, because this record has had a fabricated quotation before. Jesse Parker states the vendor position directly: preauth exists only for tip adjust, and holding a card for later use is something 'we have not built it into Sambapos yet', logged as a Redmine feature request. Combined with the customer entity model, which has no credential field, and eight processor articles documenting sale/refund/tip-adjust only, that is a stated limitation rather than silence. The record already resolved order-capture-bar-tab-preauth to `no` on this same page. source |
| kitchen-prep-time-pacing | unknown / F / "No per-item cook-time field exists on the product record ... No statement of absence, so" | resolve-to-no | The rationale had the facts right and lacked only an affirmative vendor account of the mechanism. The V5 Tutorial category supplies one: Jesse Parker's ETA tutorial obtains the quoted time by asking the cashier for a cook-time in minutes per ticket and adding it to {TICKET TIME}. That is the product's answer to per-item cook timing, and it is manual, whole-ticket and unstaggered; the product record carries no duration field and both KDS apps escalate on elapsed time only. Positive evidence of absence rather than silence. source |
| kitchen-order-throttling | unknown / F / "Nothing documents load throttling and nothing states it is absent. Unknown." | upheld | Re-evidencing, not a value change. The prior pass established the channel enumeration and the absence of any pacing item through 5.7.28. I added the missing affirmative account of the quoted-time limb: Jesse Parker's V5 Tutorial obtains an ETA by prompting the cashier for a cook time in minutes and adding it to the ticket time, so there is no threshold-driven quote extension. The release-pacing limb is still silence in all three corpora - 437 request/tutorial topics return zero hits for throttl, capacity and time slot - so unknown stands. source |
| kitchen-recall-refire | unknown / F / "nothing documents it and nothing denies it. Unknown." | resolve-to-partial | Something does document it. KB 2.3.2.d's Task Editor Widget settings list includes a recall-size setting, and V5 Request t/9899 records Emre Eren adding the Recall command to the Task Editor and then raising it from a single item to a configurable Recall Queue in 5.1.60, operable from a bump bar. That is a genuine unbump in the widget-based kitchen display. Partial rather than yes because it is not in the packaged KDS apps, it recalls a whole card rather than an item, and reprinting is a whole-order print job with no per-item refire. source |
| delivery-zones-polygon | unknown / F / "Left unresolved because KB 6.25 section 3.3.2 describes the Jetrik panel's Delivery scre" | resolve-to-no | The prior pass had the shipped mechanisms right and withheld a verdict for want of a positive account. The V5 Tutorial corpus gives one: the vendor's canonical answer to distance-based delivery is an operator-written Google Distance Matrix script keyed on a customer postcode, published as a tutorial by Jesse Parker and maintained in-thread for a decade. With serving areas defined as a comma-separated string field (2.2.6) and Nav Core geocoding a single address (6.52), there is no surface on which a polygon or isochrone could be defined. The Jetrik caveat is retained in the note and does not bear on SambaPOS's own capability. source |
| delivery-driver-comp | unknown / F / "no document enumerates the deliverer entity's shipped fields or the payroll export's col" | resolve-to-no | The rationale withheld a verdict because nothing enumerated the deliverer entity's fields. Emre Eren's V5 Tutorial does, in the strongest possible form: there are no shipped deliverer fields - the entity type is created by the operator and the founder's own example adds Phone Number and Address - and his end-to-end delivery flow measures nothing about a run. Mileage, odometer, kilometre and reimbursement return zero across all 437 forum topics and all 613 KB records in both languages, and a community member had to author a deliverer payments-and-totals report as an add-on. That is absence with a vendor account behind it, not silence. source |
| delivery-cash-reconcile | unknown / F / "Left unknown because SambaPOS's reporting is a user-authored SQL/report-tag builder, so a" | upheld | Re-evidencing, not a value change. The V5 Tutorial corpus adds the vendor's own delivery implementation - Emre Eren's t/8263, where settlement is a ticket closing and the deliverer is merely an entity assigned to it - and two community add-ons that exist because nothing ships: a Deliverers Report for driver payments and totals, and a hand-built work-period cash-up screen. That is a much better account of what the product does than the prior rationale carried. I stopped short of `no` for consistency with this record's own reporting-cash-over-short downgrade of 2026-08-09, which established that counted-cash features here have shipped without appearing in the KB. source |
| reporting-nl-query | unknown / F / "Corrected reasoning; value unchanged. The earlier rationale ended by conceding that 'foru" | upheld | Propagation check after the forum-requests premise was refuted. This cell never relied on that premise - but it did print a gap that the same dump has since closed, so the reasoning was inadequate rather than wrong. I searched the 437-topic, 6,390-post dump of categories 21, 22 and 30 for natural language, machine learning, ChatGPT, AI and assistant: zero relevant hits, the only 'artificial intelligence' occurrence being a 2017 community joke. Value and grade unchanged; the stale closing sentence is withdrawn and replaced with the completed search. source |
| extensibility-middleware-compatibility | unknown / F / "Grepped the full kb.sambapos.com dump (613 records, English and Turkish) for Deliverect, C" | upheld | Propagation check after the forum-requests premise was refuted, and this cell did depend on it. The note attributed a roadmap quote in t/23808 to 'a staff reply from Jesse Parker'; the dumped topic is 6 posts with 0 by staff, the author is 'Jesse' - never flagged [STAFF] in either the 437-topic requests dump or the 68-topic release dump - and 'Parker' is not in the source. That leg is withdrawn. The two load-bearing legs survive and were re-retrieved on 2026-08-09: tryotter.com/integrations and itsacheckmate.com/integrations both still enumerate POS partners with SambaPOS absent, and the release series still announces no middleware integration in eleven years. Not moved to no because deliverect.com's POS list still renders client-side and chowly.com/integrations still 404s, so only two of five directories are enumerable. Value and grade unchanged. source |
| order-capture-scheduled-orders | no (grade B) - 'Vendor forum on the only documented future-order channel (GloriaFood): future orders come th' | upgrade-to-partial | The no rested entirely on GloriaFood being the only documented future-order channel. GloriaFood is discontinued and closed to new signups per its own homepage banner, both of its KB articles are marked no longer supported, and the premise was wrong on its own terms: KB 6.25 s3.3.5 documents a Scheduled Orders screen for Planned Orders on the Jetrik channel. I re-searched both KB languages and the release stream for lead time, planned, scheduled and the Turkish ileri tarih and found that one line only, so the intake half is documented and the lead-time and fire-time halves are not. source |
| menu-pricing-86-propagation | partial (grade B) - '86'ing an item is not a native single action - it requires the operator to hand-build' | upheld | Re-read KB 4.50 in the local crawl: still a do-it-yourself Order Added to Ticket rule, still POS-local, so the head of the note stands without GloriaFood. Replaced the dead GloriaFood clause by checking the live channels directly - the GO Kiosk V2 Sold Out toggle (KB 8.14-a) is the only shipped availability control and lives in GO Office for GO Kiosk and GO Tablet, while 6.16, 6.17, 6.18 and 6.19 enumerate settings surfaces that are inbound-only. Propagation reaches the vendor's own kiosk and tablet menus and nothing further: partial, re-evidenced rather than re-valued. source |
| kitchen-channel-pause-propagation | no (grade B) - 'Go Order is order intake only, and the channel list is wider than the knowledge base admit' | upheld | The value survives the GloriaFood refutation but the citation did not: it pointed at 6.29, an article for a discontinued product. I re-derived the absence from the channels a buyer can license today - 6.16, 6.17, 6.18 and 6.19 list their whole settings surface and it is credentials, menu mapping, a Default Category and printing, with nothing published outward - and re-checked that Jetrik's open/closed control sits on the Jetrik panel and that the GO Office Sold Out toggle is scoped to GO Kiosk and GO Tablet. Positive absence, re-evidenced. source |
| delivery-3p-direct-integration | partial (grade B) - 'DoorDash, Uber Eats and Grubhub are not standalone SambaPOS integrations at all - all three' | upheld | Partial survives, on corrected facts. Enumerating the KB article titles shows five Go Order integrations besides GloriaFood - Yemek Sepeti, Trendyol, Migros, Getir and Jetrik - so the note's claim that the GloriaFood article was the only one is false and the record was understating the vendor's direct-integration position. The three marketplaces this claim names remain add-on-only and undocumented, and the GloriaFood evidence is withdrawn as discontinued, so the value does not move. source |
| delivery-3p-injection | partial (grade B) - 'The GoOrder page claims automatic order transfer to SambaPOS with routing to kitchen printe' | upheld | The value is right and the evidence was not: a grade-B cell was resting on sambapos.com marketing for a path that has no documentation at all. Reading the documented channels instead, 6.16, 6.17, 6.18 and 6.19 plus the 4.79, 4.80, 4.85 and 4.87 printer-tag articles describe orders landing as tickets with customer entities and print jobs, and 6.25 documents Auto Confirm, which is the no-manual-accept behaviour the claim asks for. The undocumented US trio and the silent Default Category fallback hold it below yes. source |
| delivery-menu-push | partial (grade B) - 'For GloriaFood the documented menu-sync mechanism runs POS-ward, not outward - a Fetch Menu' | downgrade-to-no | The cell depended entirely on the refuted premise; its cited article is for a discontinued product and Fetch Menu exists nowhere else in the corpus. Rather than drop to unknown I enumerated every Send Menu occurrence in the whole KB dump: GO Office (kiosk, tablet), SambaPOS KDS, Samba GO Menu and Jetrik, all first-party or own-brand, and none of the four live marketplace integrations has one - they document the opposite, an inbound match with a Default Category catching products SambaPOS does not have. That is positive absence, and it matches the sibling cell menu-pricing-3p-menu-push, already at no on the same enumeration. source |
| digital-first-party-web | partial (grade B) - 'Jetrik ($99/yr) and GO Tablet/Kiosk are first-party and commission-free, but a branded firs' | upheld | Partial is right but the printed reason was stale and self-contradictory: it credited Jetrik and then said web ordering is delegated to GloriaFood, which is discontinued. Reading KB 6.25 in full shows Jetrik is a real branded web-and-app ordering channel with restaurant name and image settings, a one-click menu push from SambaPOS and Auto Confirm order return into the POS - more documented than the note admitted - but it is a separately licensed platform on jetrik.com with no documented custom domain, which is exactly the shortfall that keeps it off yes. source |
| digital-account-saved-payment | no (grade C) - 'The complete published product roster (nine SKUs) contains no consumer ordering platform with accounts' | upgrade-to-partial | The roster enumeration was misread. Jetrik QR Menu is on the roster and KB 6.25 documents the Jetrik panel in full: registered Customers, Loyalty/Points, Payment Methods and Paynet online payment, Pickup/Delivery/Dine In and Scheduled Orders, with orders landing in SambaPOS through GO Order Jetrik. Guest accounts on a vendor-sold direct channel are therefore documented and the 'no first-party channel offers guest accounts' claim cannot stand. I then hunted for the other two halves and found nothing: no saved-address book, no tokenized card-on-file and no one-tap reorder anywhere in the KB dump, on jetrik.com/features or on jetrik.com/pricing. Partial, with that shortfall named. source |
| digital-fulfillment-modes | partial (grade C) - 'Pickup and delivery are documented via GloriaFood/RestaJet ... separate add-on modules rather than one' | upheld | Value upheld, evidence replaced. The cell was grounded on GloriaFood/RestaJet plus a drive-thru marketing page; GloriaFood is discontinued to new signups and, separately, the 'separate add-on modules rather than one integrated flow' reading is wrong. KB 6.25 documents a single Jetrik channel with Pickup, Delivery and Dine In screens side by side and table QR codes, each mapped to its own ticket type and department in SambaPOS. I re-checked the two shortfalls against the KB dump: 'curbside' has zero hits in either language, and per-mode fees and prep timing are absent, with the Calculation Settings section left unenumerated. Partial stands, at grade B rather than C. source |
| digital-group-ordering | no (grade C) - 'contains no first-party consumer ordering channel at all: kiosk and tablet are in-store devices' | upheld | Value upheld, reasoning withdrawn and replaced. The original rested on there being no first-party consumer ordering channel at all, which is wrong - Jetrik is sold as a SambaPOS SKU and KB 6.25 documents it taking pickup, delivery, dine-in and scheduled orders into SambaPOS. I rebuilt the absence from the primary docs instead: the KB 6.23 and 6.25 walkthroughs enumerate every Jetrik panel screen and every SambaPOS-side setting, including the payment and payment-pairing screens, and there is no shared cart, participant link or spend cap among them, nor any hit for group ordering in the KB or forum dumps. No stands, now at grade B off documentation rather than a product page. source |
| digital-google-order | no (grade C) - 'The claim presupposes a restaurant direct-ordering link the vendor can provision to the Google Bus' | downgrade-to-unknown | The cell's sole argument was that no first-party direct ordering link exists. It does: jetrik.com/features advertises a Personalized URL and jetrik.com/pricing a custom domain with private SSL on the Pro tier, and Jetrik is a SambaPOS-sold, SambaPOS-documented channel (KB 6.23/6.25). With the impossibility argument gone I looked for direct evidence either way and found only silence - zero KB hits for Google Business Profile or Order with Google in either language, no Google entry on the integrations list, and no Jetrik integrations page. Silence on feature and integration pages is not positive absence, particularly for a differentiator-weight cell, so the honest value is unknown at F. source |
| digital-surcharge-transparency | no (grade B) - 'There is no POS-side surcharge or dual-pricing configuration for digital channels to mirror' | upgrade-to-partial | Two of the three supporting legs do not survive. The GloriaFood leg is stale, and the claim that the first-party digital touchpoints document no fee configuration is contradicted by KB 6.25, which gives the Jetrik panel a Taxes screen setting Tax and Service Charges, a payment-type pairing screen, and a full Jetrik Discount calculation type and selector chain wiring channel-side amounts into SambaPOS accounts. Fee configuration on the digital channel is real and does map into the POS engine, which makes a flat no too strong. It is only partial: the configuration is separate rather than shared, no card-surcharge or dual-pricing feature exists on either side (the forum's surcharge is a hand-built calculation button that applies to the wrong amount), and guest-facing disclosure and jurisdiction or card-brand handling are absent from every source I read. source |
| order-capture-drive-thru-timers | unknown / F - Checked kb.sambapos.com in both languages (286 English and 327 Turkish posts, dumped in full and gre | resolve-to-partial | English KB 9.1.3 Custom Reporting Tags (modified 2021-01-29) is the actual closed list - 'These are the supported DETAILS tags.' - and its ORDER DETAILS block exposes per-order, per-named-state timestamps: 'OSD.<state name> Order State Date', 'OST.<state name> Order State Time', alongside 'OSV.<state name> Order State Value' and 'OSU.<state name> Order State User'. The same article ships '{REPORT ENTITY STATE TOTAL DURATION:<expression>}' plus TOTAL HOURS/MINUTES/SECONDS tags, and arithmetic across fields: 'When you use fields in calculations you need to enclose them in square brackets.' English KB 4.3 lists Update Order State and Log Entity State among shipped Actions and Order State Updated among shipped Rule events. Segment timing tied to an individual order is therefore capturable and reportable from documented, shipped primitives. What does not exist anywhere in either language tree is any drive-thru concept: no lane, no window, no greet, no preconfigured speed-of-service report, and the only drive-thru documents in 958 corpus files are the English and Turkish marketing pages, which promise reduced waiting without naming a captured metric. Not shipped, but not foreclosed - partial with the mechanism named. source |
| order-capture-voice-ai | unknown / F - Checked the whole 6. Integrations section on kb.sambapos.com (19 English articles, enumerated: Payme | resolve-to-no | The vendor English integrations index at sambapos.com/integrations/ (modified 2023-10-11) is the whole outward-facing partner story - 'SambaPOS assist to maximize the power of your POS with integration solutions' - and under a heading inviting the reader to discover what POS integration their restaurant needs it names exactly three: Global Payments Integrated, GloriaFood Integration and RestaJet Integration. No voice partner, no developer or partner programme, no way to apply to one. Corroborated by a corpus-wide zero across all 958 documents in BOTH languages for voice ordering, speech recognition, sesli siparis, yapay zeka, artificial intelligence, ChatGPT and machine learning; every English voice token is either the word invoice or the KDS Notification Voice chime. On the second limb of the claim I tested the analyst own corollary and it does not rescue anything: English KB 8.19 section 3.3 does document an Applications registry whose fields are an identifier, an authentication type of user name and password, an authorization type of all functions, a lifetime of 365 and an allowed origin of asterisk, sitting behind the port-9000 Message Server, but that is a local app-registration surface with no published schema and no partner onboarding - an API, not a documented API partner program addressed to voice AI. source |
| order-capture-throttling | unknown / F - Corrected reasoning; value unchanged. The earlier rationale rested on having checked 'all four inbou | resolve-to-no | Turkish KB 6.19 Go Order Getir Yemek Entegrasyonu section 6.1 walks the entire channel settings page field by field: 'Getir Aktif', 'Otomatik Onay', a play-sound box, discount type, menu, entity type, ticket type, default category, and an initial ticket state selector. Its siblings 6.16 Yemek Sepeti, 6.17 Trendyol and 6.18 Migros carry the identical list, and the ticket type it wires to is 'Adisyon Tipi: Paket Servis'. Neither limb of the claim appears on any of them: no per-channel capacity, no time slot, and no promised or quoted prep time that could be extended. Corpus-wide zero in both languages for throttl, capacity and time slot, and for kapasite and zaman dilimi - the single Turkish zaman dilimi hit is GO Kiosk V3 8.24, a scheduled product on/off window, not a capacity brake. The only shipped volume brakes are item-level: English 4.55 daily item sales limit and 4.50 zero-stock prevention. Disclosed against myself: the English GoOrder USA channels (DoorDash, Uber Eats, Grubhub) have no KB article at all, and English 6.29 describes its own settings loosely, as Auto Accept and Play Sound and so on, rather than exhaustively - so the closed enumeration I rely on is the Turkish aggregator one. All five are the same Go Order module, so I accept it. source |
| order-capture-order-ready-signal | unknown / F - Corrected reasoning; value unchanged. The earlier rationale said 'the 19-article Integrations sectio | upheld | The claim names a push back to third-party marketplaces such as DoorDash. The only SambaPOS surface touching those marketplaces is GoOrder USA, and it has NO knowledge-base article in either language - the corpus holds only its marketing page (sambapos.com/goorder-usa/, 2024-04-16, $49/month on top of a V5 Pro licence), which is silent on outbound events in either direction. The channels that ARE enumerated are the Turkish aggregators 6.16-6.19 and English 6.29 GloriaFood, and 6.29 describes its own settings loosely rather than exhaustively, so it is not a census of its own screen. Against that, English KB 4.3 lists Order State Updated and Ticket State Updated among shipped Rule events and Send E-mail, Execute Print Job, Execute Script, Start Process and Broadcast Message among shipped Actions, and English KB 4.35 documents a URL Printer that fires an arbitrary outbound HTTP request from a rule, with a worked customer-notification template. An outbound state push is therefore a documented primitive, not something the product forecloses. Neither presence nor a closed absence can be shown for the marketplace endpoint the claim actually names. |
| menu-pricing-upsell-prompts | unknown / F - Corrected reasoning; value unchanged. The earlier rationale said no prompt configuration exists for | resolve-to-partial | English KB 4.65 Giving Free Item If Ticket Total Reaches Certain Amount (modified 2021-04-08) is a shipped configuration for a conditional on-screen offer: 'In this document, it will be explained how to give a free item when ticket total reaches certain amount.' It builds an action of 'Action Type: Ask Question' offering Milk or Juice and fires it from a rule whose 'Event Name: Ticket Total Changed'. English KB 4.3 confirms Ask Question, Display Popup and Show Message are shipped Actions and Order Added to Ticket, Order Tagged and Ticket Total Changed are shipped Rule events, while Automation Command mappings are per ticket type, department and terminal, which is how per-channel targeting is expressed in this product. A per-item, per-terminal suggestive-sell prompt is therefore configurable from documented primitives, and the vendor's marketing says the product is meant to be used that way, its quick-service landing page offering to add upselling and festive offers to a menu. The second limb is genuinely unmet: English 9.1.3, the real closed tag list, has no prompt-shown, offer, attach-rate or accept-rate field in any of its five DETAILS blocks, and there is no corpus-wide hit for attach rate in either language. First limb met by construction, second limb absent: partial. source |
| kitchen-order-throttling | unknown / F - Corrected reasoning; value unchanged. As before: KB 8.9 and 8.19 document the KDS configuration item | upheld | English KB 8.19 (2026-06-29; KDS V2 is a per-device add-on at $69 annual from the cp.sambapos.com Store, minimum SambaPOS 5.7.26) does enumerate its screens closed: KDS Settings is Enable KDS, State 1/2/3 colour thresholds in minutes, Show Ticket Tag, Remove Finished Products and New Orders Position; KDS Devices is Select Groups. Nothing there paces or delays release. But sambapos.com/sambapos-kds/ (2023-11-16) lists Dynamic Capacity Management among its headline bullets with no elaboration there or anywhere else, and both 8.9 and 8.19 push part of the KDS configuration surface out to kdsadmin.sambapos.com, a console that is not in this corpus at all. Add the automation engine documented in 4.3 - Trigger Executed and Order Added to Ticket rule events, constraint expressions, and the {TICKET ORDER COUNT EXP} tag from 9.1.3 - and a volume-triggered hold on print release is buildable, so the enumeration boundary is porous by design. Neither presence nor a closed absence. |
| kitchen-order-ready-callback | unknown / F - Marketplace connectors do exist - 5.5.8 (2023-03-09) announced 'Go Order USA Integration added (Uber | upheld | Two things are true at once. English KB 8.9 confirms the bump is a local state change - 'When you click on an individual order, its status will turn to KReady and once all the orders of that ticket is completed, the ticket will disappear from Open Cards Tab and moved to Completed Cards Tab' - wired as Wait Status Kitchen and Ready Status KReady on kdsadmin.sambapos.com, and English 8.19 requires tablet and host to be in the same IP group with manual host-IP entry. But English KB 4.3 lists Order State Updated among shipped Rule events and Send E-mail, Execute Print Job, Execute Script, Start Process and Broadcast Message among shipped Actions, and English KB 4.35 documents a URL Printer that turns any rule into an outbound HTTP request. Meanwhile the endpoint the claim actually names, a third-party marketplace, is reachable only through GoOrder USA, which has no knowledge-base article in either language. The outbound half is undocumented rather than absent and the marketplace half is undocumented entirely. Unknown. |
| kitchen-all-day-counts | unknown / F - Checked kb.sambapos.com 8.9 and 8.19: the KDS shows one card per ticket, filtered to the product gro | resolve-to-partial | Two halves. The KDS half is a real absence: English KB 8.9 (2024-12-18) walks the whole display model - the kdsadmin.sambapos.com Dashboard, General Settings (Color, Token, Server, Status, Ticket, Completed Tickets) and Device Settings (Device Name, Group Type, Notification Voice, Chosen Voice, Fixed Height) - and the tablet shows per-ticket cards only, an Open Cards Tab and a Completed Cards Tab, with 8.19 KDS V2 repeating the same model. No aggregated per-item view exists on the add-on, which is separately licensed per device at $69 annual. The V5 Pro half is not an absence: English KB 9.1.8 says 'You can add custom reports inside a Custom Entity Screen by using a Custom Report Viewer Widget.' and that 'Widget displays reports in current work period by default.', while 9.1.9 demonstrates order-line reports with a quantity column, a quantity summary and automatic grouping over menu item groups, and 9.1.3 exposes OS.<state name> so the same report can be restricted to orders still in an unfinished state. That is an all-day count on a station screen, assembled from documented shipped widgets rather than shipped as a named view. Table-stakes cell met by construction only: partial. source |
| kitchen-pizza-fractional-display | unknown / F - Checked kb.sambapos.com 4.60 'Half and Half Pizza Configuration': a Half and Half Pizza product pric | resolve-to-no | English KB 4.60 Half and Half Pizza Configuration (modified 2020-12-18) is the complete vendor model for a split pizza and it carries no position attribute. The product is a zero-priced Half and Half Pizza; the split is a per-size order tag group configured 'Name: 9 Inches 50/50 Pizza', 'Min Selected Items: 2', 'Max Selected Items: 2', 'Add Tag Price to Order Price: Must be selected', with three actions and one rule that do nothing but take the higher of the two tag prices. The two selections are an unordered set: no half, section, quadrant or position field exists on an order tag anywhere in the data model, so which variety sits on which half is never captured, and quarters are not modelled at all. Because it is never captured it cannot be rendered - the kitchen-display template in English 4.13 and the combo template in English 4.43 both emit order tag name and group as flat text, and English 8.9 and 8.19 describe no graphic element on the KDS. This answers the display question that the record's existing forum citation (t/10090) does not, that one being about price. The Turkish 4.60 twin carries the identical model. source |
| kitchen-prep-forecasting | unknown / F - Checked all 14 English articles of kb.sambapos.com 9. Reports, including 9.1.3 and 9.1.4 Custom Repo | resolve-to-no | English KB 9.1.3 Custom Reporting Tags (modified 2021-01-29) is the closed list - 'These are the supported DETAILS tags.' - covering TICKET DETAILS, ORDER DETAILS, PAYMENT DETAILS, CALCULATION DETAILS and ENTITY STATE DETAILS, and every field in all five is recorded history. No predicted, projected or forecast quantity exists in it. The only prediction-shaped fields anywhere in the reporting documentation are C.Prediction and C.CostPrediction in 9.1.4's consumption and cost blocks, and both are current inventory arithmetic, matching the Turkish 5.5.7.a definition of the projected stock level as the position after existing transactions. Corpus-wide zero across all 958 documents in both languages for forecast, prep list and hazirlik listesi. The second limb has no surface either: the Task module is documented (Add Task action in 4.3, Task Editor widget in Turkish 2.3.2.d, task start/end/duration report fields in 9.1.4) but no article in either tree generates tasks from sales history, and English 4.55 daily item limits asks the operator how many they have today rather than predicting it. Neither predicted quantities nor a surfaced daily prep list. source |
| reporting-cash-over-short | unknown / F - Withdrawn. The earlier no read the Cash Transactions Report article (last modified 2018-03-29), whic | upheld | Restoring the 2026-08-09 verdict unchanged. That audit downgraded a prior no on the ground that the Cash Transactions Report article enumerates the blocks of ONE report rather than the reporting surface, and that the product-level conclusion required the KB to be an exhaustive feature inventory - which this record has established it is not, because SambaPOS 5.7.6 (2023-12-25) shipped a Time Clock cash-tip declaration the KB never documents, exactly the class of counted-cash surface that would settle this cell. Everything the analyst adds is corroboration of silence rather than positive evidence: a Turkish twin of the 2018 article, the two-click Turkish day-end article, and operator-built Open Cash Drawer and Close Cash Drawer document types in English 2.3.4.b that move a manually keyed amount between a Main Vault account and a Cash account. The corpus-wide zero in both languages for kasa sayim, nakit sayim, kasa fark, cash count, counted cash, drawer count and over/short is real and I reproduced it, but by this record's own standing ruling it cannot carry the no on its own. Unknown. |
| reporting-nl-query | unknown / F - Corrected reasoning; value unchanged, and the note's own last remaining gap is now closed. No natura | resolve-to-no | English KB 9.1.3 Custom Reporting Tags (modified 2021-01-29) states the only documented way to interrogate the data in this product: 'It is possible to prepare any type of reports with SQL and display results as a Custom Report. Alternatively you can use Custom Report Tags to prepare reports.' What follows is a closed list - 'These are the supported DETAILS tags.' - of bracketed tags over fixed field sets, filtered by an expression syntax the article itself compares to a SQL Where clause. 9.1.1 supplies template authoring, 9.1.2 the registered SQL script alternative, 9.1.8 the viewer widget and 8.11.1 the metriK V2 surface for reports flagged for it. Every one of those requires the operator to author the query in advance; none accepts a question. Corroborated by a corpus-wide zero across all 958 documents in both languages for natural language, dogal dil, yapay zeka, artificial intelligence, ChatGPT and machine learning - including the whole marketing tree, where this vendor gives dedicated landing pages to KDS, GoOrder, Jetrik, GO Kiosk and Neptune and would certainly give one to an AI assistant. source |
| reporting-sales-forecast | unknown / F - Checked all of kb.sambapos.com section 9 Reports, the report tag references 9.1.3 and 9.1.4 (whose d | resolve-to-no | English KB 9.1.3 Custom Reporting Tags (modified 2021-01-29) is the closed report-tag list - 'These are the supported DETAILS tags.' - and its five blocks (TICKET, ORDER, PAYMENT, CALCULATION and ENTITY STATE DETAILS) expose nothing but recorded history: dates, times, users, terminals, quantities, prices, tags and state timestamps. No projected or forecast quantity appears, and the two prediction-named fields elsewhere in the reporting documentation, C.Prediction and C.CostPrediction in 9.1.4, are inventory arithmetic - Turkish 5.5.7.a defines the same idea as the stock quantity after existing transactions. The string forecast occurs in none of the 958 corpus documents and the Turkish side is the same; the only ongoru hits are generic marketing insight language on sambapos.com/tr/hizli-satis/ and /tr/hayalet-mutfak/. The viewer widget's date vocabulary in 9.1.8 is entirely historical apart from a forward selector that picks future-DATED records such as reservations rather than projecting anything. Nothing is consumable downstream either, because nothing is produced and this product ships no labour scheduling module at all. source |
| labor-tip-pooling-rules | unknown / F - Tip capture is documented; distribution is not, in either direction. KB 4.70 How to Add Tip Calculat | resolve-to-no | English KB 4.70 How to Add Tip Calculation (modified 2022-02-09) builds tip CAPTURE and nothing else, in four objects: an 'Account Name: Tip Account' of type Sales Account, an 'Account Transaction Type Name: Tip Transaction' debiting Sales Accounts and crediting Receivable Accounts, a calculation type whose 'Calculation Method: Fixed Amount' posts to it, and a Calculation Selector button headed Tip. Its Turkish twin 4.70 is the same four objects, and English 6.14 PaymentSense Dojo and 6.31 Quest repeat them for card tips. Nothing anywhere divides that account. Corpus-wide zero in both languages for tip pool, tip-out, bahsis dagitimi and bahsis paylasimi - the havuz hits are an aquapark case study and a document-type article. There is also no basis to divide by: English 4.6 pays staff through manual account transactions with no tip input, and the Time Clock assignment in 4.14 carries only an hourly wage, so no hours, sales, points or role weighting exists in the model. The vendor concedes the point in its own Turkish post sambapos.com/tr/bahsis-takibinin-onemi/ (2022-08-15), which says that merely seeing how much tip was left for which member of staff requires the necessary customisations to be applied - so per-staff attribution, let alone automatic pooling per shift, is not shipped. Table-stakes cell, not met. source |
| delivery-cash-reconcile | unknown / F - Corrected reasoning; value unchanged. As before, KB 4.12 settles the Advanced Delivery Service per t | resolve-to-partial | Turkish marketing page (grade C, MODIFIED 2023-10-11). Under the Yemeksepeti integration the vendor bullets a courier-account capability of SambaPOS itself, "Paketçi hesapları yönetimi", and the body says "Tüm ödeme süreçlerini SambaPOS & Yemeksepeti entegrasyonu ile takip edebilirsiniz." The GetirYemek block adds "Tüm teslimat ayrıntıları ve paketçi detayları en ince ayrıntısına kadar raporlanır." Underneath, the mechanism is operator-assembled but documented: KB 4.12 (English twin, 2023-02-13) creates Deliverers as an entity type and moves a ticket between the Waiting Orders and Delivered Orders columns once a deliverer is assigned; the Turkish 4.12 section 7 adds Hizli Odeme Al Nakit / Kredi Karti / Yemek Ceki buttons on the courier widget; KB 9.1.2 (English, 2018-07-05) lets an operator register arbitrary SQL in a custom report over that data. FRESHNESS CORRECTION: batch B's decisive citation was the Turkish 5.5.5.a stamped 2026-08-24, inside the 6m46s bulk re-save; its English twin is stamped 2018-04-06 and carries the same six-report statement, so that closed report list is an eight-year-old floor, not a current census. What is genuinely absent is a shipped per-deliverer settle-up with counted cash, over/short and tips owed. Partial, mechanism named. source |
| delivery-daas-fallback | unknown / F - Read KB 6.44 Shipday Integration (updated 2026-03-12) in full: the integration is a licensed module | resolve-to-no | KB 6.44 Shipday Integration (English, MODIFIED 2026-03-12 - a dispersed date, not part of the 288-document 2026-08-24 event, so this one may honestly be called current). Shipday is the only DaaS courier anywhere in the 958-document corpus in either language. The push is a single unconditional path with no overflow logic: "8. Adding Send to Shipday Automation Command", then "9. Adding Send to Shipday Action", then "10. Adding Send to Shipday Rule" whose only gate is "Add Custom Constraint:" followed by "Automation Command Name|Equals|Send to Shipday". No condition on in-house deliverer availability, delivery zone or elapsed wait appears anywhere, and the trigger is a button the user presses ("Button Header: Send to Shipday"), so it is a manual hand-off rather than an automatic fallback - which also contradicts the Turkish marketing page's claim of a no-click transfer. Any hybrid-dispatch decision sits in dispatch.shipday.com. Shipday is a separately priced add-on (39 USD annual, requiring a SambaPOS V5 licence, per sambapos.com/tr/sambapos-shipday-entegrasyonu/), not a V5 Pro capability. source |
| delivery-store-pause | unknown / F - The five documented Go Order channels (Yemek Sepeti 6.16, Trendyol 6.17, Migros 6.18, Getir 6.19, Je | resolve-to-partial | KB 6.25 (English, MODIFIED 2023-11-16). The Jetrik ordering panel carries an explicit manual store-status switch: "In here, you can set your restaurant as Open-Closed, change theme-language-password settings by clicking on your name which is located on the top right corner." Section "3.3.4. Opening Hours Screen" adds a schedule - "You can handle Opening Hours settings of your restaurant from here." - and the closed-hours section (mislabelled "3.3.5. Scheduled Orders Screen" twice in the English page, correctly titled Kapali Saat Secenekleri Ekrani in the Turkish twin, which does exist and was a diacritics false positive in the checker) states "You can adjust the settings here for how your restaurant will appear outside of business hours." So manual pause and scheduled closure both exist. What does not exist is timed auto-reactivation, and no marketplace channel module carries any store-status control: KB 6.19 Getir Yemek (Turkish) enumerates its in-POS settings field by field - Getir Aktif, Otomatik Onay, Ses Cal, Indirim Tipi, Menu, Varlik Tipi, Adisyon Tipi, Varsayilan Kategori, Durum ve Durum Degeri - and Getir Aktif is a module on/off flag, not a marketplace pause; KB 6.29 GloriaFood shows default settings described only as Auto Accept, Play Sound etc. The control lives in the Jetrik add-on's web panel, not the POS; the SambaPOS-side Jetrik integration is sold as free to Jetrik Standard members. Partial, add-on named. source |
| delivery-3p-reconciliation | unknown / F - Read the four Go Order marketplace articles (KB 6.16 Yemek Sepeti, 6.17 Trendyol, 6.18 Migros, 6.19 | upheld | UNKNOWN UPHELD, with the reason sharpened. sambapos.com/goorder-usa/ (English, grade C, MODIFIED 2023-10-11) sells "GoOrder Integration 49$ Monthly Automatic order transfer to SambaPOS Order tracking Detailed reporting Requires SambaPOS V5 License." and states "GoOrder dashboard shows real-time order info, metrics, and analytics." Section 6 of the KB documents only the GloriaFood member of that quartet (6.29); there is no article for the DoorDash, Uber Eats or Grubhub connectors in either language, and section 6 carries visible numbering gaps (6.5-6.10, 6.13, 6.21, 6.35, 6.48-6.49) across both trees. A priced, vendor-run dashboard that the KB never documents is exactly the shape that forbids a no under the unmined-product-library precedent. FRESHNESS CORRECTION: batch B's closed enumeration was the Turkish 5.5.5.a stamped 2026-08-24 (bulk re-save); its English twin, 2018-04-06, states that the default SambaPOS setup ships six basic reports. That closes what the base POS shipped in 2018 and says nothing about a 2023 cloud dashboard. Nothing in the corpus mentions marketplace payout deposits, commissions, adjustments or missing orders - but the corpus cannot be shown to be the place that would. [Source consulted: https://sambapos.com/goorder-usa/] |
| delivery-promise-time | unknown / F - Grepped the full 613-record en+tr kb.sambapos.com dump for promise time, preparation time, estimated | resolve-to-no | KB 4.12 (English, MODIFIED 2023-02-13; the Turkish twin's 2026-08-24 stamp is part of the 288-document bulk re-save and carries no freshness). The Advanced Delivery Service is a two-column state machine with no duration anywhere: "Orders of selected customer will be seen in the Waiting Orders column, if you assign a deliverer for that order, it will be moved to Delivered Orders column." Its object list is closed by its own uninstall section, "8. Uninstalling Advanced Delivery Service Implementation from SambaPOS", enumerating 8.1 Actions, 8.2 Rules, 8.3 Entity Screens, 8.4 Entities, 8.5 Entity Types, 8.6 Ticket Types and 8.7 Automation Commands - no timer, duration field or load input among them. The other in-house guest-facing checkout, the Jetrik panel, is enumerated screen by screen in KB 6.25 with no promise-time surface, and Nav Core (KB 6.52) takes a Google or TomTom key to geocode and map an address while exposing no drive-time value to the ticket. I weighed the undocumented GoOrder USA dashboard, which the vendor says tracks prep times, and hold that it does not reopen this cell: that is after-the-fact analytics, and on marketplace channels the guest-facing promise belongs to the marketplace, not to SambaPOS. source |
| digital-catering-portal | unknown / F - KB 6.25 s3.3 enumerates the Jetrik panel's Services and Hours screens as Pickup, Delivery, Dine In, | resolve-to-no | KB 6.25 (English, MODIFIED 2023-11-16) enumerates the whole "3.3. Services and Hours" section of the vendor's own ordering panel as a closed set of three service types: "3.3.1. Pickup Screen", "3.3.2. Delivery Screen", "3.3.3. Dine In Screen", followed by "3.3.4. Opening Hours Screen" and "3.3.5. Scheduled Orders Screen", where scheduled means a future-dated ordinary order - "If you offer your customers the ability to place Planned Orders, you can make the relevant settings here." - not a catering flow with minimums, lead-time rules, quotes, deposits or invoice terms. Absence is measurable on this host (fabricated slugs 404 at a fixed byte length), and the vendor markets thirteen dedicated verticals on sambapos.com - bars-and-nightclubs, cafe-bakery, casual-dining, drive-thru, fast-food, fine-dining, food-truck, full-service, ghost-kitchen, pizza, pool-aquapark, quick-service, table-service - with no catering vertical among them. Corpus-wide the string catering occurs in only two documents, neither a feature. A vendor that markets every vertical it serves is a would-mention-it surface for this. source |
| digital-voice-ai-phone | unknown / F - Grepped all 613 en+tr kb.sambapos.com records for AI, artificial intelligence, machine learning, yap | resolve-to-no | KB 4.5 (English, MODIFIED 2018-03-12). The entire inbound-telephony story is Caller ID popping a customer entity so a human can key the order: "After making connection and necessary configurations on SambaPOS, Caller Id becomes usable for delivery service." and, for an unrecognised number, the popup redirects the user to the entity screen to create the customer by hand. The same shape recurs in KB 8.5 and 8.23 (Android Caller ID), 3.6 device setup naming CIDShow, Hugin boxes and Conexant modems, and 4.56 and 4.92 call logging. Measured zero-hit across all 958 documents in both languages for yapay zeka, sesli siparis, artificial intelligence, machine learning and chatbot; every occurrence of the substring voice is inside invoice. No AI or voice partner appears on sambapos.com/integrations/ or sambapos.com/tr/entegrasyonlar/, and section 6 of the KB is payment terminals, fiscal devices, GloriaFood, RestaJet, takeaway.com, Shipday, 7shifts, Jetrik and Nav Core. An exhaustive configuration manual plus a per-partner integrations page is a would-mention-it surface, and absence is measurable on this host. source |
| digital-drivethru-ai | unknown / F - The kb.sambapos.com dump (286 en + 327 tr posts, every body searched) has no drive-thru or lane arti | resolve-to-no | sambapos.com/drive-thru-pos/ (English, grade C, MODIFIED 2023-10-11). The vendor's own dedicated drive-thru page lists as a Traditional Drive Thru Limitation: "Customers can only order via speakers and receivers placed in the drive thru window." Its Drive Thru Transformation answer to that limitation is digital ordering by web and mobile plus the GO Kiosk for self-service - not AI voice in the lane. A vendor selling lane voice AI would sell it precisely here, and instead it sells kiosk. Corroborated by a measured zero across all 958 documents in both languages for yapay zeka, sesli siparis, artificial intelligence and machine learning, and by the absence of any lane or speaker-post article anywhere in the KB. GO Kiosk is itself a separately priced add-on (KB 8.6, 8.14, 8.24), not V5 Pro. source |
| digital-sms-ordering | unknown / F - SMS out of SambaPOS has two implementations and both are outbound. 4.35 is a URL Printer against a g | resolve-to-no | KB 4.35 (English, MODIFIED 2019-03-26; Turkish twin 4-35-sambaposda-sms-gonderme-uygulamasi-nasil-yapilir). This is the whole messaging surface and it is a URL Printer firing at a gateway the operator supplies: "http://api.center.com/v1/send-sms/get/?username=username&password=password&text=@message@&receipents=@number@&sender=Company Name". SambaPOS is an HTTP client using the operator's own credentials; there is no listener, no inbound message endpoint, no keyword or short-code handling and no chat channel of any kind. The only inbound telephony in the product is Caller ID (KB 4.5), which reads a calling number rather than a message. RULING ON THE COORDINATOR'S QUESTION: this cell is about inbound ordering specifically, so a bring-your-own outbound gateway does not part-satisfy it and does not lift the cell to partial. Across the corpus SMS occurs in only seven documents - KB 4.35 in each language plus five sambapos.com marketing pages - all promising notifications rather than order intake. source |
| digital-google-order | unknown / F - Undetermined. The prior no rested on SambaPOS having no direct ordering link to provision, and that | resolve-to-no | KB 6.25 (English, MODIFIED 2023-11-16). Order with Google would have to be provisioned in the vendor's own ordering panel, and that panel is enumerated screen by screen with no such surface: Dashboard, Restaurant Setup (Main Information, Location, Cuisine Selection, Tables, Taxes), then "3.3. Services and Hours" comprising "3.3.1. Pickup Screen", "3.3.2. Delivery Screen", "3.3.3. Dine In Screen", "3.3.4. Opening Hours Screen" and "3.3.5. Scheduled Orders Screen", then Payment, Rewards and Comments. No Google Business Profile connection, no ordering-link provisioning step, no place-card surface. Measured zero-hit across all 958 documents in both languages for the phrases Order with Google and Google Business Profile; every occurrence of Google is a Maps or TomTom API key for Nav Core, Google DNS in a static-IP how-to, Google Drive as a backup target, Google Play Services as an Android prerequisite, or Google Pay inside a payment partner's method list. Neither sambapos.com/integrations/ nor sambapos.com/tr/entegrasyonlar/, which enumerate the online-ordering partners individually, carries a Google entry. Jetrik is in any case a separately licensed add-on. source |
| digital-apple-business-connect | unknown / F - Checked sambapos.com/en/integrations (retrieved 2026-08-08; payment, marketplace and online-ordering | resolve-to-no | KB 6.25 (English, MODIFIED 2023-11-16). Same structural argument as the Google cell: an Apple Business Connect place card would need a listing-provisioning surface, and the vendor's own ordering panel is enumerated exhaustively - Dashboard, Restaurant Setup, then "3.3. Services and Hours" comprising "3.3.1. Pickup Screen", "3.3.2. Delivery Screen", "3.3.3. Dine In Screen", "3.3.4. Opening Hours Screen" and "3.3.5. Scheduled Orders Screen", then Payment, Rewards and Comments - and has none. Measured zero-hit across all 958 documents in both languages for Apple Business Connect. Apple occurs only as a tablet OS prerequisite for GO Tablet and GO Kiosk, as App Store download buttons for the Mobile Client, CDS, KDS and Metrik apps, and as Apple Pay inside payment-partner method lists, where the subject is the processor. SambaPOS's digital ordering is uniformly partner-hosted and separately licensed. Noted for the record: 61% of the other 44 records left this cell unknown; I keep no only because absence is measurable on this host and the partner list is enumerated per-partner on both marketing trees. source |
| extensibility-middleware-compatibility | unknown / F - Grepped the full kb.sambapos.com dump (613 records, English and Turkish) for Deliverect, Chowly, Ott | resolve-to-partial | KB 8.19 (English, MODIFIED 2025-01-24). SambaPOS ships a first-party application registry for third-party clients: "3.3. Creating Application" instructs "Main Menu > Manage > Users > Applications > Here, click on Add Application." with "Authorization Type: All Functions", "Lifetime: 365" and "Allowed Origin: *", plus a Permissions section - note that this one is All Functions, not the local-network-scoped variant batch B claimed was uniform across the KB. It sits behind the GraphQL message server on port 9000, and user accounts carry a password field distinct from the POS PIN whose only purpose is GraphQL authentication (KB 2.2.10.b states that the user password is used for connections made through GraphQL). Thirteen documented integrations register through this registry, including third parties that are not SambaPOS products - takeaway.com (KB 6.15), GloriaFood (6.3), RestaJet (6.4), PaymentSense (6.2) - so the endpoint an aggregation middleware would bind to is documented, public and already used by outside platforms. What is genuinely absent is named support: measured zero-hit across all 958 documents in both languages for Deliverect, Chowly, Otter, Checkmate and ItsaCheckmate, and the vendor built its own aggregation layer instead (GoOrder USA, 49 USD monthly, connecting DoorDash, Uber Eats, Grubhub and GloriaFood). Also absent is a published GraphQL schema reference. Partial with the mechanism named. source |
| guest-loyalty-tiers | unknown / F - SambaPOS's shipped loyalty material is KB 4.27 (Basic Loyalty Points Implementation - a Loyalty Card | resolve-to-partial | KB 2.4.17 (English, MODIFIED 2018-12-19). Tiers exist only as an operator-assembled static construct: a String custom field on the Customers entity, "Custom Field Name: Discount Rate", with hand-typed values "Neighbour 5%,Regular 8%,Special 10%,Staff 15%", and four rules each gated by a Custom Constraint on that customer custom data ("Entity Type Name | Equals | Customers") applying the matching Calculation Type when the customer is selected. The band is set by hand at registration: no spend or visit threshold, no rolling window, no automatic promotion or demotion. The two shipped loyalty articles are flat (4.27 Basic Loyalty Points, 2.4.9 SambaCard) and the Jetrik add-on's Rewards section is a toggle plus Points and Transactions screens. The vendor does claim tiers in marketing - sambapos.com/delivery/ (grade C, 2022-12-08) invites the reader to organize a tiered-loyalty program, and the Turkish twin sambapos.com/tr/paket-servis/ carries the same sentence; both check out on their own pages, and the checker's flags on them were misattribution and diacritics artefacts. On 2026-07-28 the vendor also announced an unshipped first-party loyalty platform advertising membership tiers, marked Coming Soon (sambapos.com/sambapos-extra360-integration/); that is recorded as pending, not as evidence either way. Partial on the shipped manual mechanism. source |
| guest-loyalty-offline-behavior | unknown / F - Read the two loyalty articles end to end (KB 4.27 Basic Loyalty Points, KB 2.4.9 SambaCard): both st | resolve-to-partial | sambapos.com/tr/ (Turkish, grade C, MODIFIED 2024-12-16). The product-level offline claim is first-party and explicit: "SambaPOS, çalışmak için internete ihtiyaç duymaz. İnternetiniz kesilse bile güvenle çalışmaya devam edersiniz." The English home page carries only the shorter half. Native loyalty sits inside that boundary by construction rather than by statement: KB 4.27's points are an entity custom field and 2.4.9 SambaCard is an account balance, both in the local MSSQL instance the terminals share (2.1.6), so nothing crosses the internet to earn or redeem. What is not documented in either language is loyalty-specific connectivity behaviour - no queue, retry or reconciliation statement anywhere, and nothing about the cloud-backed loyalty paths (Jetrik Rewards in 6.25, RestaJet Reward Point mapping in 6.4, the announced Extra360 platform) which do depend on a link. Partial: the product-level claim is first-party, the loyalty-level behaviour is inference. source |
| guest-loyalty-offer-stacking-rules | unknown / F - Discounts and surcharges in SambaPOS are Calculation Types surfaced through Calculation Selectors. A | resolve-to-partial | KB 2.3.10.b (English, MODIFIED 2018-04-09) gives the fullest published field list of the Calculation Type editor, the single object behind every discount, promotion, service charge and tip. Its fields are exactly "Template Name:", "Account Transaction Type:", "Calculation Method:", "Rate or Amount:", "Max Amount:", "Rounding:", "Tax Included:", "Decrease Amount:" and "Use Plain Sum:" - the last of which batch B's list omitted. There is no combinable-versus-exclusive flag, no priority or sequence field and no mutual-exclusion group, and 2.3.10.a, 2.4.7.c, 4.59, 4.63, 4.70, 4.78 and the Turkish 4-59 and 4-63 twins reproduce the same short set; KB 4.59 positively lands three separate Calculation Types on one ticket with nothing offered to rank or suppress them. But the engine that fires them is rule-driven with Custom Constraints - KB 2.4.17 gates each of four discount rules on a customer custom-data value so that only one fires - which means mutual exclusion and precedence are expressible as constraints an operator writes. That is the documented automation engine doing the job, which by the standing rule is partial with the mechanism named. Residue: the KB never states the order in which several calculations are applied to one ticket. source |
| guest-loyalty-targeted-offers | unknown / F - In SambaPOS itself there is no offer-issuance channel to target: discounts are calculation selectors | resolve-to-partial | KB 2.4.17 (English, MODIFIED 2018-12-19). Targeting is operator-assembled and documented: audience membership is a hand-set custom field on the customer entity, "Custom Field Name: Discount Rate" with values "Neighbour 5%,Regular 8%,Special 10%,Staff 15%", and each offer is a rule gated on it ("Entity Type Name | Equals | Customers" plus a Custom Data constraint on the band) firing the matching Calculation Type when the customer is selected on the ticket; KB 4.15 builds a first-visit gift the same way. There is no list, no audience builder, no send job and no offer object, and the only outbound channel is KB 4.35, where the operator supplies their own SMS gateway URL and credentials. The vendor does claim an audience distinction in marketing (sambapos.com/delivery/, grade C, 2022-12-08, under Promotions and Campaigns), and the Turkish twin carries it, but that is a brochure sentence and the verdict does not rest on it. Partial: a real rule-and-custom-field mechanism over a manually maintained group, plus a bring-your-own gateway. source |
| guest-loyalty-rfm-segmentation | unknown / F - Walked the whole 9. Reports section (14 English articles): 9.1.1-9.1.9 are the custom-report toolkit | resolve-to-partial | KB 9.1.2 (English, MODIFIED 2018-07-05). No packaged RFM or lifecycle report ships: the base install's six reports are Work Period, Item Sales, Cash Transactions, Inventory Transaction, Inventory and Cost (English 5.5.5.a, 2018-04-06), and section 9's additions are Item Sales by Product Tag, Void and Gift, Item Group Sales by Ticket Type, Open Tickets and Remaining Balanced Customers; none computes recency, frequency, monetary value or a lifecycle label, and RFM is a measured zero-hit across all 958 documents in both languages. What converts this from no to partial is that ticket, order, payment and customer data all sit in the merchant's own SQL Server and the vendor documents registering arbitrary SQL against it: "You can display result of an SQL Script in custom reports.", created under "Management > Automation > Scripts" and referenced from a report template by an @@Handler name. Customers can also be exported to Excel (4.94). RULING ON THE COMING-SOON QUESTION, applied across this batch: on 2026-07-28 - a genuine dispersed date, not the 2026-08-24 bulk re-save - the vendor announced Extra360, a first-party loyalty platform listing Customer Segmentation and marked Coming Soon (sambapos.com/sambapos-extra360-integration/). An announced-but-unshipped capability cannot carry yes or partial by itself, and it positively forbids no, because no asserts absence from the offering while an announcement is evidence of pendency. It is recorded here as pending, never as support. source |
| guest-loyalty-lifecycle-automation | unknown / F - Searched the full en+tr KB for birthday/dogum gunu, win-back, lapsed and campaign: no shipped campai | resolve-to-partial | sambapos.com/delivery/ (English, grade C, MODIFIED 2022-12-08). The vendor makes the lifecycle claim itself: "Birthdays and Other Special Occasions Make your customers happy by sending congratulatory messages along with discount codes on birthdays, anniversaries, festivals, and other occasions." and "Prompt Notifications Send payment confirmations, delivery notifications, and order status via SMS and email." The Turkish twin sambapos.com/tr/paket-servis/ carries both and adds a phrase the English drops - the messages go to customers who have given permission. Underneath there is no campaign object and no scheduler over customer state: what exists is the generic Actions and Rules engine plus hand-built recipes (KB 4.15, a one-time promotional product for each new customer; 2.4.17, group discount on customer selection) and KB 4.35's operator-supplied SMS gateway as the only outbound path; the only time-driven jobs documented are work-period tasks such as 2.4.12.e emailing reports at end of day. Partial, with the qualifier that everything under the claim is a customer-built automation rather than a shipped lifecycle campaign product. source |
| guest-loyalty-consent-management | unknown / F - Searched all 613 kb.sambapos.com records (286 en + 327 tr bodies) for consent, opt-in/opt-out, unsub | resolve-to-partial | sambapos.com/tr/paket-servis/ (Turkish, grade C, MODIFIED 2022-08-31). The vendor states the send is permission-scoped: "Doğum günleri, yıl dönümleri, festivaller ve diğer etkinliklerde indirim kodlarıyla birlikte izni olan müşterilere tebrik mesajları göndererek müşterilerinizi mutlu edin." The English twin drops the permission phrase entirely; the checker's NOWHERE flag on this string was a diacritics false positive. No consent object ships: the Customers entity's documented custom-field surface (2.2.6, 2.4.17, 4.48, 4.77, 6.52) has no consent flag, timestamp, source or per-channel state; KB 4.35 fires a print job at the operator's own gateway with no pre-send check and no suppression list; and there is no inbound path by which a STOP could reach SambaPOS, so revocation necessarily sits with the operator's gateway. Measured zero-hit in both languages for KVKK, GDPR, opt-in, opt-out and unsubscribe. What makes this partial rather than absent is the documented mechanism used everywhere else in the product: consent modelled as a Customers custom field and enforced as a rule Custom Constraint on the send, exactly the pattern KB 2.4.17 demonstrates for discount bands. sambapos.com/tr/kisisel-veriler/ is Ozgu Yazilim's own personal-data notice as controller of its business contacts, not a POS feature, and is not counted here. source |
| guest-loyalty-10dlc-registration | unknown / F - KB 4.35 (2019) documents SMS as a bring-your-own-gateway URL Printer - the operator pastes their own | resolve-to-no | KB 4.35 (English, MODIFIED 2019-03-26; Turkish twin 4-35-sambaposda-sms-gonderme-uygulamasi-nasil-yapilir). The architecture closes the question rather than merely failing to mention it: SambaPOS is an HTTP client against an endpoint the operator supplies with the operator's own credentials - "http://api.center.com/v1/send-sms/get/?username=username&password=password&text=@message@&receipents=@number@&sender=Company Name" - so the sending identity, the aggregator relationship and any A2P carrier registration are entirely the operator's, and the vendor holds nothing it could register. Measured zero-hit across all 958 documents in both languages for 10DLC, A2P and Twilio. Applicability is genuine rather than moot: the vendor sells into the US (GoOrder USA at 49 USD monthly, plus the Global Payments and Dejavoo integrations), so the subject is fair to score, and the answer is that the vendor provides nothing. Residue carried from the prior pass and not visible in this corpus: the 5.5.8 release note announcing a native Twilio SMS action has no KB article in either language, which if anything confirms that no registration guidance is published for it. source |
| guest-loyalty-campaign-attribution | unknown / F - There is no campaign or offer object in SambaPOS to attribute sales to - promotions are calculation | resolve-to-partial | KB 9.1.2 (English, MODIFIED 2018-07-05). No shipped attribution report exists: the base install's six reports (English 5.5.5.a, 2018-04-06) and section 9's additions include nothing that ties a redeemed offer to incremental spend, a control group or a send, and there is no campaign or offer object in the product - promotions are per-site Calculation Types and automation rules (2.4.7.a, 2.4.7.c, 4.4, 4.10, 4.15, 4.59, 4.63, 4.75 and the Turkish 4-59 and 4-63 twins). What is buildable is redemption reporting: discount amounts land in named accounts (Jetrik Discount, Loyalty Discount, TY Indirim) in the merchant's own SQL Server, and the vendor documents registering arbitrary SQL against it - "You can display result of an SQL Script in custom reports.", authored under "Management > Automation > Scripts". So redemption counts and discount value per offer are an operator build, while incrementality and control-group measurement remain impossible because no send or exposure is ever recorded: the only outbound path, KB 4.35, is a fire-and-forget print job. Partial with that split stated. The marketing side does claim campaigns exist (sambapos.com/delivery/), which is not relied on here. source |
| guest-loyalty-review-capture-routing | unknown / F - Grepped all 613 en+tr kb.sambapos.com records for survey, feedback, anket, review, rating, NPS, Goog | resolve-to-partial | sambapos.com/food-truck/ (English, grade C, MODIFIED 2023-10-11), under Customer Reporting: "Gather customer data like their name, phone, address, etc. Receive feedback from your customers during the check out process. Track their experience with colour-coded ratings to manage your performance." That is a first-party capture claim and it is the only one - I grepped the exact strings and they occur in exactly one document of 958, on one of a family of templated industry landing pages, and no KB article in either language configures it. Routing is absent entirely: measured zero-hit in both languages for anket, NPS, TripAdvisor and puanlama, nothing that routes by score, escalates a low rating or pushes to a public review site, and the only adjacent surface is passive - the Jetrik add-on's Comments screen in KB 6.25, which shows comments about the restaurant with no request trigger. Partial on capture; routing is not evidenced at all. source |
| guest-loyalty-wallet-pass | unknown / F - Zero hits for wallet, Apple Wallet, Google Wallet, PassKit, .pkpass or cuzdan across all 613 en+tr k | resolve-to-no | KB 2.4.9 (English, MODIFIED 2018-06-06; Turkish twin 2-4-9-sadakat-karti-sambakart-uygulamasi). The card model is a number-identified entity backed by an account: "It is necessary to create a different type of account for customer cards. So that it will be easier to track customer accounts and customer cards separately." The card is selected on the ticket by scanning or keying its number, and KB 4.27's Loyalty Card is likewise an entity with a Points custom field; delivery format is a printed barcode or QR from a slip or barcode printer (2.4.8.a, 2.4.8.b). There is no push-updatable balance object anywhere. Measured zero-hit across all 958 documents in both languages for pkpass, PassKit, Apple Wallet and Google Wallet. RULING ON THE COMING-SOON DOCTRINE FOR THIS CELL: it does not reach here. Extra360 (announced 2026-07-28, marked Coming Soon) advertises a stored-value digital wallet balance and a loyalty program, not a pkpass or Google Wallet object; the doctrine bars no only where the announcement's own words cover the cell's subject, and these do not. Global Payments' digital wallets phrase is Apple Pay and Google Pay as a card-present tender, subject the processor. The KB enumerates card creation and printing in full, so this is a would-mention-it surface and the zero converts. source |
| guest-loyalty-ai-offer-recommendation | unknown / F - Grepped every one of the 613 kb.sambapos.com post bodies (286 en + 327 tr) for AI, artificial intell | resolve-to-no | KB 4.27 (English, MODIFIED 2020-04-24). Measured zero-hit across all 958 documents of both hosts in both languages for yapay zeka, makine ogrenme, machine learning and artificial intelligence. There is also nothing for a recommender to attach to: the offer surface is Calculation Types pressed at the terminal and rules keyed on a hand-set customer group - 4.27 builds the card by hand ("Entity Type: Loyalty Card", "Card Number: LC00", "Points: Currently there is no points in the Loyalty Card.") and applies the discount through an automation command named LC-Apply Loyalty Discount - with no offer object, no audience and no issuance channel beyond the operator's own SMS gateway (4.35). RULING ON THE COMING-SOON DOCTRINE FOR THIS CELL: Extra360 (announced 2026-07-28, Coming Soon) advertises personalized offers but uses no AI or machine-learning language anywhere, and the doctrine bars no only where the announcement's own words cover the cell's subject. Personalized is not AI-recommended, so the zero stands against an exhaustive step-by-step configuration manual on a host where absence is measurable. source |
| multi-location-cross-location-giftcard | unknown / F - Withdrawn. The earlier no argued from Neptune's sync scope ('branches are defined for products, menu | resolve-to-partial | KB 4.31 (English, MODIFIED 2019-09-27; Turkish twin 4-31-hediye-karti-uygulamasi). SambaPOS's own gift certificate is entirely operator-assembled inside one database: "In this document, it will be explained how to apply Gift Certificate Implementation." builds a "Product Name: Gift Certificate" under "Group Code: Gift Certificates", GC Accounts and GC Balances account types, and a Gift Certificate entity whose balance is written by "2.8. Adding Update Entity Data Action- Balance"; redemption is local - "You can either scan the barcode via barcode reader or enter the number of Gift Certificate manually into numberpad." Since SambaPOS is one installation per site with its own MSSQL (2.1.6), that balance cannot leave the site, and the eleven-article Neptune series documents no entity, account or balance sync (KB 10.8 scopes branches to products, menus, stock and recipes). What stops this being a flat no is that SambaPOS also passes gift cards through to processors whose balances live on their network: KB 6.20 Global Payments Integration (English, 2023-11-10) exposes a gift-card payment type setting, and the release series adds Valutec (5.3.2, US only) and Dejavoo gift card support (5.7.16). On those the subject is the processor, and SambaPOS documents nothing about multi-site redeemability, outstanding liability or inter-store settlement in either language. source |
| multi-location-central-labor-policy | unknown / F - SambaPOS is one installation per site (2.1.6) and Neptune, the multi-branch layer, defines branches | resolve-to-no | KB 8.13 (English, MODIFIED 2023-10-11; the Turkish twin is content-identical and its 2026-08-24 stamp is part of the 288-document bulk re-save, carrying no freshness). Time Clock is a per-installation module and its whole settings surface is enumerated: "Enable Time Clock: Click on this box to activate the Time Clock Module.", "Enable Breaks: This is the choice which gives to select the Break Option." with a paid or non-paid choice, then "2.2. Departments Screen" where "You can set your departments and their related user roles from this section. Department: Restaurant Role: Waiter", and assignments where "you will be able to set the hourly wage as well.(this is not mandatory you can leave it as 0)". No overtime threshold, no schedule, no minor rule, and no scope beyond the local database. The only central layer is Neptune, and sambapos.com/sambapos-neptune/ (English, 2023-10-11) publishes a closed list of what HQ can push to branches - Products, Menus, Prices, Sales Screens, Users, Permissions, Reports, Inventory Items, Receipts, Accounts - with no time clock, wages, breaks or scheduling among them; central users and permissions genuinely exist, but those are not a labor policy. Residue: release 5.7.8 (2024-01-31) added Time Clock payroll overtime settings the KB still does not document, which affects how a setting behaves, not whether a central per-location-group labor policy is offered. source |
| payments-softpos-tap-to-pay | unknown / F - Checked all eight payment-processor articles on kb.sambapos.com: PaymentSense Pay at Counter (6.1) a | resolve-to-no | SUBJECT: SambaPOS V5 Pro itself, not an acquirer. KB 3.1 Hardware Requirements and Compatibilities (English, MODIFIED 2025-02-18) enumerates the supported peripheral classes exhaustively under seven headings and nothing else: 'Computer Hardware Requirements', 'Printer Hardware' ('any type of thermal or dot-matrix ticket printer'), 'Tablet Hardware', 'Caller ID Device', 'Scales', 'Barcode Reader/Writer', 'Cash Drawer'. There is no card-acceptance class of any kind, phone-borne or otherwise. Corroborating zero-hit across all 958 documents in both languages: tap to pay, taptopay, softpos, soft pos, tap-to-phone, tap to phone, cep pos and mobil pos all return ZERO files; case-insensitive NFC returns exactly one file, the Turkish KB 11.9 Ingenico OKC meal-voucher article, where the phone is the GUEST's. Fabricated slugs 404 at a fixed 45,059 bytes so the zero-hit binds. The vendor's only device-borne acceptance runs the OPPOSITE way: sambapos.com/sambapos-odeal-integration/ (English, MODIFIED 2026-03-17, one of the ten genuinely current English documents) puts the SambaPOS order-taking app onto a PAX Android payment device at $165+KDV annually plus a V5 licence - a certified payment terminal, not a commodity phone. source |
| hardware-tap-to-phone | unknown / F - No documented Tap to Pay on iPhone / Tap to Pay on Android acceptance, but no exhaustive enumeration | resolve-to-no | SUBJECT: the SambaPOS Mobile Client MC3 add-on (a priced add-on, $49 per sambapos.com/mobile-client-landing/) running on a commodity Android/iOS phone. KB 8.10 (English, MODIFIED 2023-10-02) is the complete setup document and its entire payment section 'Getting Payment on SambaPOS Mobile Client' is the single sentence 'Select desired table, click on Settle button.'. Its own troubleshooting checklist '6.1. Connection and Network Settings Part' is exclusively Wi-Fi, server IP group, Message Server and 'Is the Message Server Port 9000+ ?' - no reader, no NFC, no payment-device pairing, no card step anywhere in the article. MC3 is a Wi-Fi LAN client that writes a tender into the shared SQL database; the card leg stays on an external PIN pad in every documented processor integration (English 6.1, 6.2, 6.5, 6.12, 6.14, 6.20, 6.26, 6.31, 6.34, 6.42 plus about twenty Turkish yazarkasa/OKC articles). Zero corpus hits in either language for softpos, tap to pay or tap-to-phone. The only in-house device-borne acceptance is the Odeal PAX Android payment terminal, which is a reader, not a phone. source |
| payments-tip-pooling | unknown / F - Corrected reasoning; value unchanged. The earlier rationale concluded from the report-tag references | resolve-to-no | SUBJECT: SambaPOS V5 Pro. KB 4.70 How to Add Tip Calculation (ENGLISH, MODIFIED 2022-02-09; the Turkish twin 4-70-tip-bahsis-nasil-eklenir is content-identical) is the vendor's complete step-by-step for tips and it builds exactly four objects: one Sales Account ('Account Name: Tip Account'), one transaction type, one calculation type whose 'Calculation Method: Fixed Amount', and a step '4. Adding Tip Calculation Selector'. There is no employee dimension, no allocation basis, no hours/sales/role/points weighting and no distribution or payroll-export step. The same four-object build is repeated verbatim inside the processor articles (English 6.5 OpenEdge, 6.12 International Bancard, 6.20 Global Payments), so this IS the vendor's tip surface, not one stray article. Corpus-wide in both languages: tip pool, tipout, tip-out, gratuity, tip share and tip distribution return ZERO files, and the Turkish bahsis hits are one KB article plus eleven marketing pages, none of which distributes anything. The 7shifts payroll add-on (sambapos.com/7shifts/, $99 annual) is timesheets only and never mentions tips. The vendor states the position itself in its own blog, sambapos.com/the-importance-of-tipping-tracking/ (English, 2023-08-29; Turkish twin 2022-08-15), where merely SEEING per-employee tips is said to require applying the necessary customizations - i.e. attribution, let alone pooling, is the operator's build, not a product engine. source |
| hardware-selfpour-scales | unknown / F - No self-pour tap wall, flow meter, pour spout or dispense-controller integration is documented anywh | resolve-to-no | SUBJECT: SambaPOS V5 Pro peripheral support. KB 3.1 (English, MODIFIED 2025-02-18) enumerates the supported peripheral classes closed and complete - computer, ESC/POS printer, tablet, Caller ID device, scales, barcode reader, cash drawer - and no beverage-dispensing, flow-meter or tap-wall class appears. The scales entry is deliberately open-ended: 'Cas ER Junior model, runs directly with TEM EGE model scales. Also you can use all scales which is able to send data to computer through COM port, by adding them Custom Scale.' - but a generic COM-port weighing driver is weigh-to-price at the counter, not pour-to-tab, and the scale articles (8.4 CAS ER, 8.8 Avery Berkel, 8.12 CAS PDN, 8.16 Datalogic, 8.20 Wintec, Turkish 8.3 Desis and 8.21 Aclass) are all retail weighing. Across all 958 documents in both languages self pour, self-pour, tap wall, flow meter, flowmeter, akis olcer, pour spout, keg, musluk, PourMyBeer and iPourIt return ZERO files, and the two dispens hits are the English word indispensable. The only draft-beer mechanism in the corpus is inventory depletion by recipe (a Draft Beer / Cl inventory unit in KB 2.3.15.a and a Turkish Fici Bira / Cl twin), where stock is consumed when the item is SOLD - the reverse of a metered pour creating the sale. source |
| reliability-offline-card-auth | unknown / F - The words 'offline' (English) and 'cevrimdisi/cevrim disi' (Turkish) return zero hits across all 613 | resolve-to-no | SUBJECT AND SCOPE: a no about SambaPOS's delivered card path, NOT about any acquirer's terminal firmware or PCI posture. SambaPOS never authorises or stores a card; every integration is a DLL in the SambaPOS5 folder plus an Automation Command handing the transaction to an external PIN pad synchronously. KB 6.31 Quest Payment Integration (English, MODIFIED 2024-11-21) states the precondition directly: clicking the Credit Card button 'will initiate a transaction process which will be conducted by the PinPad', and 'If you wish to utilize Manual card entry wait until you establish a connection after which you can enter your card number on the PinPad.' - a live connection is required before card entry, with no queue. I then enumerated the whole integrations surface: all 20 English 6.x articles and all 34 Turkish 6.x yazarkasa/OKC articles (Ingenico GMP3/TSM, Beko 300TR and X30TR, Hugin, Pavo, InPos M530) contain not one reference to connection loss, queuing, a stored-transaction cap, a floor limit or a reconnect flush. Corpus-wide, offline appears in exactly ONE file (sambapos.com/full-service/) and cevrimdisi in exactly one (the Turkish twin), both as a marketing bullet listed beside Online Payment under Simple Payment Methods - a payment channel label, not store-and-forward. RESIDUAL, stated honestly: an acquirer terminal (Dojo, Global Payments, Dejavoo, PAX) may hold its own store-and-forward firmware; SambaPOS publishes nothing about it and ships none of its own. source |
| reliability-offline-decline-liability | unknown / F - Checked the same two hosts as reliability-offline-card-auth: kb.sambapos.com has no offline/store-an | resolve-to-no | SUBJECT: SambaPOS as publisher. Terms of Use (English, MODIFIED 2022-07-27; Turkish twin sambapos.com/tr/satis-ve-kullanim-kosullari/) allocates connectivity risk generically and nothing more - clause 3.13 'The user is responsible for preparing the necessary infrastructure for the operation of SambaPOS products.' followed by a sentence making the user responsible for problems caused by insufficient internet, operating system, network, cabling and electricity infrastructure; clause 3.17 disclaims interruption of third-party-integrated services and ends 'SambaPOS is not responsible for any damages incurred by this situation.' Neither is an allocation of loss on a declined stored transaction, and no per-transaction or cumulative offline cap appears in that document, in the Privacy Policy, in sambapos.com/personal-data/, or in any of the 958 corpus documents. There is also no mechanism for such a statement to attach to - see reliability-offline-card-auth, where all 54 integration articles were enumerated and SambaPOS ships no store-and-forward. CORRECTION TO THE SESSION BRIEF, confirmed by me: the brief says no contract is published on either host; a Terms of Use, a Privacy Policy, a Personal Data page and a Cookie Use Policy ARE published in both languages. What is genuinely absent is an MSA, SLA or DPA. source |
| reliability-failover-terminal-role | unknown / F - Read the deployment articles in the kb.sambapos.com dump: 2.1.1/2.1.3 set up one machine as the SQL | resolve-to-no | SUBJECT: SambaPOS V5 Pro on-premise topology. This is not an absence - the vendor states the restriction affirmatively. KB 2.2.2 What is SambaPOS Messaging Server? How to Install? (English, MODIFIED 2018-04-10): 'Message Server should work only on main computer. Other computers work communicating through Message Server.' The Turkish 2.2.2.a carries the identical sentence. KB 2.1.6 How to Run SambaPOS on Multiple Computers (English, 2023-02-08) repeats it in the technician workflow - the message server runs only on the server, terminals are configured solely as clients pointing at the server's static IP over TCP 1433 - and the licensing-tips article adds that licensing from the main machine automatically licenses the terminals connected to it. So the master role is a build-time property of one named machine holding SQL Server, the Message Server Windows service and the licence, while terminals carry a hardcoded connection string and no database of their own. Corpus-wide in both languages: failover, fail-over, yedek sunucu, cluster, always on and olaganustu durum return ZERO files; the single redundan hit is a GO Kiosk marketing line about redundant operating costs. The only published server-move procedures are manual and offline (2.1.3.b, 2.1.3.c). No promotion, election or automatic assumption of the role exists. source |
| reliability-cellular-backup | unknown / F - KB section 3 (Hardware & Network) contains only five English articles - 3.1 Hardware Requirements an | resolve-to-partial | SUBJECT SPLIT, which is why this is partial and not yes. MET: sambapos.com/dojo/ (English, MODIFIED 2023-10-11) under Features of Dojo Card Machines: 'Uninterrupted connection Switch between Wi-fi and mobile data in case of any interruptions in the service. Serve your customers at any time.' A second vendor page, sambapos.com/paymentsense/ (English, 2023-10-11), lists Mobile Data Usage when Wi-Fi is Down among its card-machine features. Turkish twins exist for both. SHORTFALLS, all three: (1) the device is the ACQUIRER's card machine, whereas a SambaPOS terminal is a Windows PC or Android GO client on a wired LAN against a local SQL Server; (2) the Turkish twin sambapos.com/tr/dojo/ renders the same sentence with the verb gecis yapabilir, can switch, which states a capability rather than an AUTOMATIC failover; (3) these are partner brochures, hence grade C, and no KB article supports them - KB 6.14 PaymentSense Dojo Integration is a DLL and automation-command walkthrough that never mentions connectivity. For SambaPOS's OWN terminals there is nothing: across 958 documents in both languages 4G, 5G, hotspot, sim kart, hucresel and mobil internet return ZERO files, case-sensitive LTE returns ZERO, and all three cellular hits are the CellularCallerId device in KB 8.5 and 8.23, an Android caller-ID source with no bearing on WAN failover. source |
| commercial-pci-p2pe-tokenization | unknown / F - Grepped the full kb.sambapos.com dump (613 records, both languages) for pci, p2pe, saq, tokeniz and | resolve-to-partial | FOUND-AND-SHORT, not a zero-hit, and the two halves of this claim resolve differently. MET (a): sambapos.com/global-payments-integrated/ (English, MODIFIED 2023-10-11) states 'Help keep cardholder data safe and help prevent fraud with full encryption and tokenization'. The same tokenization sentence appears on sambapos.com/worldline-tim-integration-for-switzerland/ (2023-12-29), and end-to-end encryption is claimed in the vendor's own voice on sambapos.com/dojo/, sambapos.com/regulation-tss-for-germany/ and sambapos.com/regulation-tims-for-samoa/ (the last under its own End-to-End Encryption heading), with Turkish twins carrying uctan uca sifreleme. Hardware-encrypted card entry is also structurally real - every one of the 54 documented integrations runs the card on an external PIN pad and SambaPOS never touches it. NOT MET (b): the scope-reduction half is absent everywhere. Across all 958 documents in both languages, case-sensitive: SAQ ZERO files, P2PE ZERO, PCI ZERO, point-to-point ZERO, attestation ZERO. No applicable SAQ is named, no PCI SSC validated-P2PE listing is cited, and no scope-reduction claim is made anywhere. Grade C: these are acquirer capabilities recited on SambaPOS marketing pages, which is the weakest form of a real claim, not an absence. source |
| commercial-pci-dss-4-controls | unknown / F - Grepped all 613 kb.sambapos.com records in both languages for pci, mfa, 'two factor', 2fa, otp and ' | resolve-to-no | SUBJECT: SambaPOS as documenter - the claim's verb is documents, which an enumerated corpus can refute. Zero files in all 958 documents, both languages, case-sensitive, for PCI, MFA, multi-factor, two factor, two-factor, 2FA and script integrity; the only OTP hit is a custom reporting tag in KB 9.1.3. The authentication surface the vendor DOES document is the whole of it and it is single-factor: KB 2.2.10.b How to Create / Edit User? (ENGLISH, MODIFIED 2018-05-28; the Turkish twin is a literal translation stamped inside the 2026-08-24 bulk re-save and adds nothing) gives each user a Pin Code and a Password, where 'Pin and Passwords have to consist of minimum 4 character.', 'Pin Code is for entering from SambaPOS screen.' and 'Password is used for connections which will be making through GraphQL.' - a four-character PIN for the POS and a password for the GraphQL channel, with no second factor offered on either, and the back office is a local Windows window rather than a hosted console. For Req 6.4.3 and 11.6.1, SambaPOS hosts no payment page of its own. This scores the vendor's DOCUMENTATION only; it is NOT a finding about any acquirer's CDE posture and it does not describe or discharge the merchant's own compliance obligations. source |
| reliability-pci-dss-4-attestation | unknown / F - Grepped the complete kb.sambapos.com dump (613 records, English and Turkish) for pci, p2pe, attestat | resolve-to-no | The claim's verb is publishes, and publication is directly observable on a bound surface. Both hosts were enumerated for this session - 958 documents, the kb WordPress REST registry (329 tr and 286 en posts plus 6 pages), the WP core sitemap including the glossary and faq post types the REST registry does not expose, the www sitemap, and the 17-file wpdmpro download library - and an href fixpoint over the bodies drained to 8 recoverable strays, all held. Fabricated slugs 404 at a fixed 45,059 bytes (45,333 under /en/) while live articles are 50-136 KB, so a zero-hit binds on this vendor. Across that surface, in both languages, case-sensitive: PCI 0 files, P2PE 0, attestation 0, AoC 0, SAQ 0, point-to-point 0. I listed the www English and Turkish page inventories by hand: the vendor publishes a complete legal shelf in both languages - Terms of Use, Privacy Policy, Personal Data and Cookie Use Policy, with Turkish twins - and no security page, trust centre, compliance page or certification page exists beside them. It also publishes jurisdiction-regulatory pages when it has something to say, Regulation TSS for Germany and Regulation TIMS for Samoa, though those are integration marketing rather than attestations and I weight them lightly. No AoC, no validated-P2PE listing and no equivalent is published, which is exactly what this cell asks. Grade F because the finding is an enumeration of the whole surface rather than one carrying document. This says nothing about whether an AoC EXISTS: SambaPOS runs on the merchant's own Windows and SQL Server and never touches card data, so the entity that would hold one is the acquirer, and payments-p2pe-pci4 is deliberately and correctly left unknown for exactly that reason. |
| commercial-no-early-termination-fee | partial / E - A perpetual license leaves nothing to terminate early, but no public terms of service or MSA states | downgrade-to-partial | Evidence upgrade E->B: the prior note asserted that no public terms of service or MSA exists, which was wrong — the Terms of Use is cited twelve times elsewhere in this record. There is no early-termination FEE, because the core licence is perpetual, but the contract makes prepayment non-recoverable. Terms of Use 3.18: 'Trial versions of SambaPOS products are offered to users and vendors. Before licensing, products may be tested for a period determined by the user and the vendor. After the user and the seller make the decision to pay for and receive their license, no refunds will be given after the payment has been made.' 3.14 adds that expired licences 'may be temporarily disabled or permanently revoked to disable access to products'. So the exposure on exit is the forfeited annual prepayment on the add-on SKUs (KDS, Mobile Client, GO Tablet, GO Kiosk, Jetrik), not a termination charge. Document is dated 2022-07-27 and is the current published revision; no later one exists. Partial rather than yes because the no-refund rule cuts against the merchant. source |
Sources
Every URL this record cites. 170 in total.
- https://kb.sambapos.com/en/
- https://sourceforge.net/software/product/SambaPOS/
- https://forum.sambapos.com/t/major-issue-with-online-license-check-systems-offline/19437
- https://sambapos.com/
- https://sambapos.com/sambapos-go-tablet/
- https://sambapos.com/sambapos-go-kiosk/
- https://kb.sambapos.com/en/2-3-5-e-how-to-add-different-order-tag-according-to-portion/
- https://kb.sambapos.com/en/4-60-half-and-half-pizza-configuration/
- https://sambapos.com/jetrik-qr-menu/
- https://kb.sambapos.com/en/2-3-15-c-what-is-inventory-recipe-how-to-create/
- https://sambapos.com/integrations/
- https://sambapos.com/sambapos-mobile-client/
- https://sambapos.com/sambapos-kds/
- https://sambapos.com/goorder-usa/
- https://kb.sambapos.com/en/8-13-how-to-configure-time-clock-module/
- https://sambapos.com/products/
- https://kb.sambapos.com/en/4-22-how-to-implement-wastage-stock/
- https://sambapos.com/sambapos-v5-pro/
- https://forum.sambapos.com/t/graphql-api-v5-5/25930
- https://forum.sambapos.com/t/what-happened-to-graphql-guide/25526
- https://sambapos.com/sambapos-neptune/
- https://forum.sambapos.com/t/pricing-and-documentation-for-sambapos-api/27174
- https://forum.sambapos.com/t/pricing-of-pizza-half-and-half/10090
- https://kb.sambapos.com/en/cat/integrations/
- https://sambapos.com/sambapos-time-clock/
- https://kb.sambapos.com/en/5-5-8-a-how-to-activate-license-unregistered-trial/
- https://kb.sambapos.com/en/3-1-hardware-requirements-and-compatibilities/
- https://kb.sambapos.com/en/1-4-hardware-and-software-requirements/
- https://forum.sambapos.com/t/gloria-food-future-order/22215
- https://kb.sambapos.com/en/2-3-5-b-how-to-add-price-and-quantity-for-order-tags/
- https://kb.sambapos.com/en/2-3-5-a-what-is-order-tag-how-to-create/
- https://kb.sambapos.com/en/2-3-5-d-how-to-add-prefix-for-order-tags/
- https://forum.sambapos.com/t/with-and-without-buttons-for-toppings/2585
- https://kb.sambapos.com/en/4-50-how-to-prevent-zero-stocked-item-sales/
- https://forum.sambapos.com/t/product-countdown/22149
- https://forum.sambapos.com/t/credit-card-surcharge-does-not-surcharge-the-owing-amount-but-the-total-amount/21493
- https://kb.sambapos.com/en/2-4-5-a-how-to-add-price-list-for-different-ticket-types/
- https://forum.sambapos.com/t/variable-delivery-charges-based-on-zones/22723
- https://kb.sambapos.com/en/4-12-advanced-delivery-service-implementation-v5-2-3/
- https://sambapos.com/delivery/
- https://kb.sambapos.com/en/4-27-basic-loyalty-points-implementation/
- https://forum.sambapos.com/t/how-to-create-a-tip-reports/24409
- https://forum.sambapos.com/t/server-9000-token-returns-400-response/17414
- https://forum.sambapos.com/t/sambapos-script-for-self-hosted-http-service-and-post-data-in-url/21434
- https://forum.sambapos.com/t/new-feature-printer-backup-fail-over-option/20587
- https://kb.sambapos.com/en/8-19-how-to-configure-sambapos-kds-v2/
- https://kb.sambapos.com/en/8-9-how-to-configure-sambapos-kds/
- https://kb.sambapos.com/en/4-31-gift-certificates-sales-and-redemption-implementation/
- https://kb.sambapos.com/en/5-4-8-c-customer-accounts-management/
- https://kb.sambapos.com/en/5-5-5-d-what-is-cash-transactions-report-how-to-analyze/
- https://kb.sambapos.com/en/6-3-how-to-setup-gloriafood-online-ordering-integration-module/
- https://kb.sambapos.com/en/9-3-how-to-create-void-and-gift-report/
- https://sambapos.com/drive-thru-pos/
- https://kb.sambapos.com/en/4-71-how-to-define-inventory-on-sambapos/
- https://kb.sambapos.com/en/cat/reports/
- https://kb.sambapos.com/en/8-11-1-how-to-setup-metrik-v2-for-sambapos/
- https://kb.sambapos.com/en/2-5-how-to-handle-licensing-on-sambapos-5-5-and-higher-versions/
- https://kb.sambapos.com/en/cat/additional-modules/
- https://kb.sambapos.com/en/8-1-android-mobile-client-v2-setup/
- https://forum.sambapos.com/t/shivans-tutorial-2-order-courses-order-grouping/18157
- https://kb.sambapos.com/en/2-4-16-printing-kitchen-messages-by-ticket-tag-mains-starters-away/
- https://forum.sambapos.com/t/hold-and-fire-for-items/2774
- https://forum.sambapos.com/t/us-credit-card-intergration-bar-tabs/21455
- https://kb.sambapos.com/en/5-1-3-a-how-to-move-table/
- https://kb.sambapos.com/en/2-4-4-how-to-record-waiter-that-prints-bill-or-receives-payment-into-logs/
- https://kb.sambapos.com/en/4-43-how-to-apply-auto-combo-implementation/
- https://kb.sambapos.com/en/4-2-2-switching-between-menus-time-based/
- https://kb.sambapos.com/en/4-7-how-to-set-happy-hour/
- https://kb.sambapos.com/en/4-63-how-to-apply-discount-for-desired-items-on-desired-days-of-the-week/
- https://kb.sambapos.com/en/2-4-5-how-to-sell-with-different-prices-to-different-customer-types/
- https://kb.sambapos.com/en/6-34-how-to-assign-and-configure-dejavoo-license-in-sambapos/
- https://forum.sambapos.com/t/sambapos-5-2-20-release/19620
- https://kb.sambapos.com/en/6-20-global-payments-integration/
- https://forum.sambapos.com/t/bump-bar-kitchen-display/29572
- https://kb.sambapos.com/en/4-13-how-to-generate-kitchen-display/
- https://kb.sambapos.com/en/4-35-how-to-apply-sms-sending-implementation-on-sambapos/
- https://kb.sambapos.com/en/2-2-6-how-to-create-delivery-department/
- https://kb.sambapos.com/en/6-52-how-to-configure-nav-core-on-sambapos/
- https://forum.sambapos.com/t/limit-delivery-addresses/19309
- https://kb.sambapos.com/en/6-45-7shifts-integration/
- https://kb.sambapos.com/en/6-44-shipday-integration/
- https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/
- https://kb.sambapos.com/6-16-go-order-yemek-sepeti-entegrasyonu/
- https://kb.sambapos.com/6-17-go-order-trendyol-yemek-entegrasyonu/
- https://kb.sambapos.com/6-19-go-order-getir-yemek-entegrasyonu/
- https://kb.sambapos.com/en/6-4-how-to-setup-restajet-integration-module/
- https://forum.sambapos.com/t/sambapos-restajet-online-ordering-system-campaign/21733
- https://sambapos.com/en/integrations/
- https://kb.sambapos.com/en/8-14-sambapos-go-kiosk-v2-configuration/
- https://kb.sambapos.com/en/6-29-go-order-gloriafood-integration/
- https://kb.sambapos.com/en/2-4-9-how-to-set-loyalty-card-sambacard/
- https://kb.sambapos.com/en/4-94-how-to-export-customer-list-in-excel-format/
- https://kb.sambapos.com/en/2-1-6-how-to-run-sambapos-on-multiple-computers/
- https://forum.sambapos.com/t/offline-feature/13944
- https://kb.sambapos.com/en/9-1-8-custom-report-viewer-widget/
- https://kb.sambapos.com/en/4-70-how-to-add-tip-calculation/
- https://kb.sambapos.com/en/5-5-7-d-how-to-count-warehouse-inventory/
- https://kb.sambapos.com/en/5-1-12-a-how-to-use-sambapos-android-client/
- https://kb.sambapos.com/en/5-5-7-b-how-to-purchase-item-into-inventory/
- https://kb.sambapos.com/en/2-4-2-what-is-import-export-from-file-how-to-perform/
- https://kb.sambapos.com/en/5-5-7-a-general-features-of-warehouses/
- https://kb.sambapos.com/en/2-3-15-a-how-to-add-inventory-item/
- https://kb.sambapos.com/en/5-5-5-g-what-is-cost-report-how-to-analyze/
- https://kb.sambapos.com/en/9-1-5-creating-accounting-reports-with-custom-reporting-tags/
- https://kb.sambapos.com/en/9-1-2-creating-custom-reports-with-sql/
- https://kb.sambapos.com/en/2-3-1-c-how-to-create-department/
- https://kb.sambapos.com/en/2-4-12-e-how-to-send-reports-as-email-at-end-of-work-period/
- https://kb.sambapos.com/en/2-3-17-a-trigger-features-and-usage/
- https://kb.sambapos.com/en/4-3-how-does-it-work-action-rule-structure/
- https://kb.sambapos.com/en/9-1-4-custom-reporting-tags-for-v5/
- https://kb.sambapos.com/en/10-2-how-to-use-sambapos-neptune/
- https://kb.sambapos.com/en/2-3-1-a-what-is-ticket-type/
- https://kb.sambapos.com/en/6-31-quest-payment-integration/
- https://kb.sambapos.com/en/6-2-how-to-configure-payment-sense-pay-at-table-settings/
- https://kb.sambapos.com/en/5-5-9-usage-of-user-control-panel-cp-sambapos-com/
- https://kb.sambapos.com/en/2-2-11-reseller-control-panel-how-to-use-cp-sambapos-com/
- https://kb.sambapos.com/en/4-100-how-to-add-new-product-by-scanning-unknown-barcode/
- https://kb.sambapos.com/en/4-19-how-to-select-portions-and-order-tags-by-popup/
- https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026
- https://developer.doordash.com/en-US/docs/marketplace/overview/getting_started/preferred_integrations_new/
- https://forum.sambapos.com/t/quickbooks-integration/13290
- https://sambapos.com/support/
- https://sambapos.com/wp-sitemap-posts-page-1.xml
- https://sambapos.com/terms-of-use/
- https://sambapos.com/resellers/
- https://sambapos.com/privacy/
- https://sambapos.com/sambapos-go-kiosk/
- https://sambapos.com/wp-sitemap-posts-wpdmpro-1.xml
- https://kb.sambapos.com/en/2-3-13-how-to-add-service-charge/
- https://forum.sambapos.com/t/sambapos-5-5-8-release/26807
- https://forum.sambapos.com/t/sambapos-5-7-8-release/27931
- https://kb.sambapos.com/en/8-10-sambapos-mobile-client-mc3-setup/
- https://kb.sambapos.com/en/8-18-sambapos-go-tablet-v2-setup/
- https://gooffice.sambapos.com/
- https://one.sambapos.com/
- https://sambapos.com/download/sambapos-one/
- https://forum.sambapos.com/t/time-clock-not-working-on-the-new-update-578/28024
- https://forum.sambapos.com/t/sambapos-5-7-6-release/27804
- https://forum.sambapos.com/t/sambapos-5-7-0-release/27548
- https://www.tryotter.com/integrations
- https://itsacheckmate.com/integrations/
- https://forum.sambapos.com/t/deliverect-api-integration/23808
- https://forum.sambapos.com/t/customer-personal-data/28362
- https://forum.sambapos.com/t/gdpr-gloria-food/23357
- https://forum.sambapos.com/t/customer-loyalty-points-module/13833
- https://kb.sambapos.com/4-79-go-order-yemek-sepeti-entegrasyonu-yazici-tagleri/
- https://kb.sambapos.com/4-80-go-order-trendyol-entegrasyonu-yazici-tagleri/
- https://forum.sambapos.com/t/sambapos-5-7-28-release/32105
- https://forum.sambapos.com/t/sambapos-5-7-10-release/28240
- https://forum.sambapos.com/t/sambapos-5-3-2-release/23647
- https://forum.sambapos.com/t/sambapos-5-7-16-release/30202
- https://forum.sambapos.com/t/sambapos-5-2-13-beta-release/18155/149
- https://forum.sambapos.com/t/sambapos-5-2-14-release/18392
- https://kb.sambapos.com/en/2-3-5-h-how-to-activate-auto-select-feature/
- https://forum.sambapos.com/t/pop-up-modifier/7569
- https://forum.sambapos.com/t/sambapos-5-3-6-release/24268
- https://forum.sambapos.com/t/order-pay-app/24966
- https://forum.sambapos.com/t/setting-an-eta-for-take-out-orders/16825
- https://kb.sambapos.com/en/2-3-2-d-how-to-add-layout-entity-screens/
- https://forum.sambapos.com/t/bump-bar-for-kitchen-display/9899
- https://forum.sambapos.com/t/set-up-button-to-reprint-kitchen-orders-to-different-printers/10453
- https://forum.sambapos.com/t/advanced-tutorial-automatic-delivery-charge-based-on-distance-via-google-maps/6918
- https://forum.sambapos.com/t/custom-package-delivery-for-v5/8263
- https://forum.sambapos.com/t/deliverers-report/22739
- https://forum.sambapos.com/t/cash-management-end-of-work-period-cash-up/19160
- https://www.gloriafood.com/
- https://kb.sambapos.com/8-14-a-sambapos-go-kiosk-v2-yeni-eklenen-ozellikler/
- https://kb.sambapos.com/en/6-23-how-to-setup-jetrik-qr-menu-integration/
- https://www.jetrik.com/features
- https://www.jetrik.com/pricing