SambaPOS

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-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

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

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

order-capture-bar-tab-preauth differentiator

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

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

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

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

order-capture-qr-same-check differentiator

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

order-capture-kiosk-first-party differentiator

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

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

order-capture-drive-thru-timers

Checked kb.sambapos.com in both languages (286 English and 327 Turkish posts, dumped in full and grepped) - zero occurrences of drive-thru or of any order/total/window timer metric; 9. Reports (14 English articles including the Custom Reporting Tags lists 9.1.3 and 9.1.4, which enumerate the report fields available from the database) exposes ticket dates but no speed-of-service segment; 2.3.18 'How to Run Product Timers' is time-based billing for rentable products such as pool tables, not service timing; KDS (8.9) and KDS V2 (8.19) time only ticket age for colour escalation. forum.sambapos.com /search.json for 'drive thru timer' returns zero posts. sambapos.com/drive-thru-pos/ is marketing and promises orders prepared 'in the time that is promised' without naming a captured metric. No affirmative evidence either way, so unknown rather than no.

order-capture-voice-ai differentiator

Checked the whole 6. Integrations section on kb.sambapos.com (19 English articles, enumerated: PaymentSense Pay-at-Counter and Pay-at-Table, International Bancard, Dojo, Global Payments, OpenEdge, Worldline TIM, Quest x2, Dejavoo x2, GloriaFood, Go Order GloriaFood, RestaJet, takeaway.com, Jetrik x2, Shipday, 7shifts, Nav Core) - no voice ordering of any kind, first-party or partner. Grepped all 613 dumped KB records in both languages: every 'voice' hit is the word 'invoice' or the KDS 'Notification Voice' chime setting. forum.sambapos.com /search.json for 'voice ordering AI' returns only community wishes (t/7559 2015 'Notify kitchen... by playing recorder voice message', t/13281 2016 'Siry and Silvia and Cortana Order') with no vendor product answer. sambapos.com site search for 'voice' returns only e-invoice pages. Absence across an integration list is not proof - integration directories are routinely incomplete - so unknown.

order-capture-throttling differentiator

Corrected reasoning; value unchanged. The earlier rationale rested on having checked 'all four inbound-order integrations', which was not the full set: GoOrder ships Uber Eats, DoorDash and Grubhub for the US (5.5.8, 2023-03-09), Yemeksepeti/Delivery Hero (5.5.6), Trendyol Yemek (5.5.8), and Getir and Migros Yemek, documented in Turkish only at KB 6.16-6.19. I read those articles: their settings are activation, 'Otomatik Onay' auto-accept, an order sound, discount type, menu and entity mapping, the ticket's initial state ('Durum ve Durum Degeri') and default category for unmatched products, plus printer tags - no per-channel capacity, no time slot and no promised- or quote-time field. The only volume controls documented anywhere remain item-level: KB 4.55 daily item sales limit (decremented on Order Added to Ticket, cancelling with 'Not currently available'), 4.50 zero-stock prevention, and GO Kiosk V2's Sold Out toggle and product time windows. Grepped the 68-topic, 1,451-post V5 Release and Beta dump through 5.7.28 for throttling, capacity, slot, prep time, busy and pause: nothing. Still absence rather than a vendor statement, so unknown. adversarially verified

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

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

order-capture-order-ready-signal differentiator

Corrected reasoning; value unchanged. The earlier rationale said 'the 19-article Integrations section contains no DoorDash, Uber Eats or Deliveroo connector', and the vendor's release series disproves it: 5.5.8 (2023-03-09) announces 'Go Order USA Integration added (Uber Eats, Doordash, Grubhub, Gloriafood)', with Jesse [STAFF] explaining it 'will allow you to integrate doordash grubhub Uber and gmoriafood directly into sambapos and remove tablets' and that 'it works with auto accept or without allowing you to accept orders directly through sambapos'. So a two-way channel to the marketplaces exists and SambaPOS does push at least one state back to them - the Go Order Getir article (KB 6.19) exposes an 'Otomatik Onay' (auto-approve) setting alongside the initial ticket state ('Durum ve Durum Degeri'), i.e. acceptance is returned to the platform. What remains unevidenced is the claim's actual subject: no GoOrder, GloriaFood or KDS article, and no post in the 68-topic release series through 5.7.28, documents an order-READY or prepared-state callback driven from POS or KDS state, and the GloriaFood custom integration (6.3/6.29) is still inbound-only ('Poll Accepted Orders v2' / 'Push Accepted Orders' into gf-producer.sambapos.com). Unknown. adversarially verified

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-pricing-nested-modifiers

Modifiers are Order Tag Groups with selection constraints; three-level nesting with independent min/max per level is not documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01

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

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. https://kb.sambapos.com/en/2-3-5-e-how-to-add-different-order-tag-according-to-portion/ · retrieved 2026-08-01 adversarially verified

menu-pricing-fractional-placement differentiator

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. https://kb.sambapos.com/en/4-60-half-and-half-pizza-configuration/ · retrieved 2026-08-01 adversarially verified

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

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. https://kb.sambapos.com/en/4-60-half-and-half-pizza-configuration/ · retrieved 2026-08-01 adversarially verified

menu-pricing-topping-quantity-tiers

KB 2.3.5.b gives each order tag a single fixed Price plus a max-quantity cap ('it can be selected as many as determined maximum value') — i.e. repeat-add pricing, exactly what the claim excludes. KB 2.3.5.d prefixes (Add/Eject) are documented as visual indicators with no per-prefix price effect, and the vendor-forum pattern for No/Extra variants is a duplicated tag per variant (e.g. No Spinach at price 0 — forum.sambapos.com/t/2585), not tiers with a configurable multiplier. https://kb.sambapos.com/en/2-3-5-b-how-to-add-price-and-quantity-for-order-tags/ · retrieved 2026-08-03

menu-pricing-size-style-matrix differentiator

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. https://kb.sambapos.com/en/2-3-5-e-how-to-add-different-order-tag-according-to-portion/ · retrieved 2026-08-04

menu-pricing-included-allowance differentiator

KB 2.3.5.a enumerates the Order Tag Group settings — Min Selected Items, Max Selected Items, and layout fields — with no included-allowance or charge-for-overage field. On the vendor forum the recommended pattern for included toppings is to auto-apply default order tags and price every tag individually (Jesse: configure the pizza with no toppings, set the default order tags to apply automatically — forum.sambapos.com/t/2585); substitution credits and overage-only charging do not exist. https://kb.sambapos.com/en/2-3-5-a-what-is-order-tag-how-to-create/ · retrieved 2026-08-03

menu-pricing-combos

Automatic a-la-carte-to-combo conversion is documented and buildable. KB 4.43 adds Product Tag Captions 'Combo,ComboPrice', marks each product as Main, Side or Drink in the Product Tag Editor and writes into ComboPrice 'the new prices that will be taken once those products included into combo menu'; a 'Promotion' order tag group is mapped to every Main category, and an 'Adjust Order Prices' action (Function Type 'X for Y$', Order Tag Name Promotion, Distribute Discounts True) is driven by a Find Combo rule that scans the ticket. Component choice is therefore any product carrying the matching Combo tag, at its own ComboPrice. Shortfall: there is no combo or meal-deal entity in the product - every combo is assembled by hand from product tag captions, an order tag group, five actions and rules, and the swap delta is an absolute per-product ComboPrice column rather than a modelled price difference; nothing surfaces a combo as a single sellable menu item. https://kb.sambapos.com/en/4-43-how-to-apply-auto-combo-implementation/ · retrieved 2026-08-08

menu-pricing-upsell-prompts differentiator

Corrected reasoning; value unchanged. The earlier rationale said no prompt configuration exists for the POS itself, which is wrong: KB 2.3.5.h 'How to Activate Auto Select Feature' (modified 2023-12-27) sets a per-product Auto Select flag on Menus > Edit Product Properties so that 'if you add these products to the ticket, sub feature or portion page will be opened automatically', and when a user asked on forum t/7569 for a pop-up that prompts the server after an item is rung, Emre Eren (SambaPOS founder, staff-flagged, 2015-10-10) answered 'Do you know Auto Select feature? When you enable Auto Select for menu items on Menus > Edit Product Properties, order tags will appear just after order added to ticket.' That is a forced modifier prompt, not a suggestive-sell offer: it presents the item's own order tags and portions, it is a single product-level flag with no per-channel variant for kiosk (8.6/8.14) or online (4.68 QR menu, 6.3 GloriaFood), and no attach-rate, prompt-shown or accept-rate measure appears in the 14 articles of section 9 or in the custom reporting tag lists 9.1.3/9.1.4. Grepped all 437 V5 Request/Tutorial topics for upsell, suggestive and attach rate: zero. Nearest mechanism found, claim not reached, and no vendor statement of absence - so unknown.

menu-pricing-86-propagation

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), and the article's scope is POS-local (that is our reading of it, NOT a quotation; an earlier pass printed a quoted sentence that appears nowhere in the 613-record KB dump). The GloriaFood leg of the earlier note is withdrawn - GloriaFood is discontinued and no longer accepting new signups (gloriafood.com, 2026-08-09) and KB 6.3 and 6.29 are headed 'This product is no longer supported' - and the cell does not need it. The only availability switch SambaPOS ships is the GO Kiosk V2 Sold Out control described in KB 8.14-a, which closes a product to sale without removing it from the menu; it is set in GO Office and scoped to the GO Kiosk and GO Tablet menus. Every live marketplace channel article (Yemek Sepeti 6.16, Trendyol 6.17, Migros 6.18, Getir 6.19) configures inbound intake only and offers no outbound availability call, and no propagation latency is stated for anything. https://kb.sambapos.com/en/4-50-how-to-prevent-zero-stocked-item-sales/ · retrieved 2026-08-09 adversarially verified

menu-pricing-countdown-auto-86 differentiator

Not a shipped countdown. The vendor-documented approach (KB 4.50) is a hand-assembled automation recipe — product tag, recipes, and two custom rules that warn below a threshold and cancel the order at zero inventory. Shortfalls: no staff-settable per-item par counts (a 2020 forum request for exactly that was answered 'This can be implemented now with current automation' — forum.sambapos.com/t/product-countdown/22149), no automatic 86 of the menu button (the sale is cancelled with a message instead), and no scheduled auto-restore. https://kb.sambapos.com/en/4-50-how-to-prevent-zero-stocked-item-sales/ · retrieved 2026-08-03

menu-pricing-dayparting

Time-based menus and prices are documented, as automation rather than as a schedule. KB 4.2.2 'Switching Between Menus Time Based' creates Breakfast/Lunch/Dinner screen menus and three Change Screen Menu actions fired by rules on the Ticket Opened event with constraints '{DATE:HHmm} Greater 0800 / Less 1129', etc.; KB 4.7 'How to Set Happy Hour' defines an HH price definition, fills the HH column of the Price List Editor and fires an Update Order action inside a time window; KB 4.63 shows day-of-week targeting via '{DATE:wd} Equals 3'. Times are the Windows clock of the on-premise server, which is the site's own timezone. Shortfall: there is no scheduling UI at all - every daypart is a hand-written automation rule per window, the menu swap is evaluated when a ticket is opened rather than continuously, and individual items are not scheduled: 4.42 'How to Close an Item for Sale' switches a product tag to Closed manually and 4.9 daily specials pick a product by day tag on a button press. https://kb.sambapos.com/en/4-2-2-switching-between-menus-time-based/ · retrieved 2026-08-08

menu-pricing-channel-price-books

Per-channel price books yes, markup rules no. KB 2.4.5.a: 'In a restaurant, it is possible to use different price lists, for example delivery service prices could be different than restaurant price list' - add a Price Definition per ticket type (name 'Delivery Service', price tag 'DLR'), fill its column in the Price List Editor, then fire an Update Order action with Price Tag [:Price List] from a rule constrained on '{TICKET TYPE} = Delivery Service'. KB 2.4.5 does the same keyed on a customer entity custom field. Shortfall: the claim's percentage-markup-on-a-base-price requirement is not met - the Price List Editor holds absolute per-item prices per tag and nothing derives one book from another; each channel needs its own hand-written rule; and there are no third-party marketplace connectors in the catalogue for a marketplace-specific book to attach to. https://kb.sambapos.com/en/2-4-5-a-how-to-add-price-list-for-different-ticket-types/ · retrieved 2026-08-08

menu-pricing-dual-pricing differentiator

Pricing switches on ticket type, never on tender. KB 2.4.5.a builds Price Definitions ('Price Definition Name: Ticket type that price list will be used. For example: Delivery Service', 'Price Tag: Shortcut for price list to be used on the screen'), prices them in the Price List Editor and applies them with an Update Order action carrying the '[:Price List]' formula, fired by a rule constrained on {TICKET TYPE}: the whole price list moves at ticket creation, so a card price cannot be shown as the item's base price with a cash alternative alongside it. Passing card cost on is hand-built on the vendor forum as a payment-time Update Ticket Calculation percentage on {REMAINING TOTAL} (Bob_be, 2020-01-29, forum.sambapos.com/t/21493) - a surcharge workaround, the alternative this claim excludes. Nothing stores or prints a cash and a card total together. The first-party channels the product does have - Jetrik ordering sites, GO Kiosk, GO Tablet and the GO Menu QR menu, all fed by a Send Menu function - receive one price per product and portion, and no dual-pricing, cash-discount or card-price item appears in any of the 68 release topics from 5.1.15 to 5.7.28. https://kb.sambapos.com/en/2-4-5-a-how-to-add-price-list-for-different-ticket-types/ · retrieved 2026-08-09

menu-pricing-allergen-nutrition

Jetrik supports dietary tags (spicy, vegan, vegetarian). No allergen matrix, no nutrition values, no recipe-derived nutrition. https://sambapos.com/jetrik-qr-menu/ · retrieved 2026-08-01

menu-pricing-recipe-linkage differentiator

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. https://kb.sambapos.com/en/2-3-15-c-what-is-inventory-recipe-how-to-create/ · retrieved 2026-08-01 adversarially verified

menu-pricing-3p-menu-push

SambaPOS does ship a menu push, but not to a marketplace. 'Send Menu' targets its own channels - Send Menu to GO Office for GO Kiosk and GO Tablet (8.6, 8.7, 8.14, 8.18), Send Menu to SambaPOS KDS (8.9, 8.19), Send Menu to Samba GO Menu for the QR menu (4.68) - and Jetrik, the operator's own branded ordering site, where 6.25 says the SambaPOS menu can be 'sent to Jetrik with a single click' (added in 5.7.0 as 'Jetrik Send Menu function added'). No Send Menu exists for any Go Order marketplace provider, including the GoOrder USA set (Uber Eats, DoorDash, Grubhub, added 5.5.8); there the menu is authored on the provider side and reconciled afterwards, which is what 6.25's Menu Pairing screen ('you need to match your products and portions in Jetrik with your products in SambaPOS'), 6.29's Alternative Mapping and 6.25's NOTE 1 - incoming products whose names differ are dropped into a Default Category - exist to do. Nothing surfaces per-item sync status or rejection errors to the operator; the only sync feedback documented anywhere is a 5.7.28 bug fix for the 'Send Menu to Go Office' freeze. https://kb.sambapos.com/en/6-25-how-to-integrate-sambapos-with-jetrik/ · retrieved 2026-08-08

menu-pricing-dynamic-pricing

Rule-based price switching yes, dynamic computation no. KB 4.7 defines a Happy Hour price definition (tag HH), fills the HH column of the Price List Editor and fires an Update Order action with Price Tag HH from a rule constrained on a '{DATE:HHmm}' window; KB 2.4.5.a swaps the price list on {TICKET TYPE} (channel); KB 4.63 applies a % discount to tagged items on a given weekday via '{DATE:wd}'. Shortfall: prices are pre-entered static columns chosen by a rule - nothing computes a price from demand, inventory or elasticity, there are no floor or ceiling guardrail fields anywhere in Price Definitions or the Update Order action, and every rule is hand-written per window. https://kb.sambapos.com/en/4-7-how-to-set-happy-hour/ · retrieved 2026-08-08

payments-processor-choice differentiator

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

payments-published-rates differentiator

Not an acquirer; publishes no card rates. Rates come from the merchant's chosen processor. https://sambapos.com/integrations/ · retrieved 2026-08-01

payments-dual-pricing differentiator

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

payments-surcharge-guardrails differentiator

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

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

payments-softpos-tap-to-pay differentiator

Checked all eight payment-processor articles on kb.sambapos.com: PaymentSense Pay at Counter (6.1) and Pay at Table (6.2, an Ingenico handheld driven by a Windows gateway exe), Dojo (6.14), OpenEdge (6.5), International Bancard (6.12), Global Payments (6.20, which addresses the reader by 'Credit Card DEVICEIP' plus port 8080), Worldline TIM (6.26), Quest (6.31, 'a transaction process which will be conducted by the PinPad') and Dejavoo (6.34/6.42) - all are dedicated card-reader integrations. 3.1 Hardware Requirements and Compatibilities lists supported peripheral classes (touchscreen PCs, ESC/POS printers, tablets, caller-ID boxes, scales, barcode readers, cash drawers) and no phone-based acceptance. sambapos.com site search for 'tap to pay' returns only the GO Kiosk product page; forum.sambapos.com /search.json for 'tap to pay iphone' returns zero posts. Unknown, not no.

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

payments-qr-guest-pay differentiator

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

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

payments-tip-pooling differentiator

Corrected reasoning; value unchanged. The earlier rationale concluded from the report-tag references (9.1.3/9.1.4) that SambaPOS exposes no tip-per-employee measure. That overstated a stale KB: 5.7.6 (2023-12-25) announces 'Time Clock declare cash tip option and declaration added', a per-employee cash-tip declaration that appears nowhere in KB 8.13, and 5.3.6 (2021-05-26) added a CanFinalizeTip permission. Per-employee tip data therefore does exist. What is still unevidenced is the claim itself: no vendor source - not the eight processor articles, each of which posts tips to a single Tip sales account through a Tip transaction type (4.70), not 4.6 Staff Salaries, not the 14 articles of section 9 - describes a pooling or distribution engine allocating by hours worked, sales, role percentage or points, or a payroll-ready per-employee allocation export. The 68-topic release series through 5.7.28 mentions tips only for adjust, split-payment calculation, the finalize permission and the cash declaration. An operator could build an allocation report on the SQL report engine (9.1.2), which is not a native distribution engine. Unknown. adversarially verified

payments-offline-store-and-forward differentiator

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

payments-offline-decline-liability differentiator

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

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

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

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

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

payments-chargeback-tooling differentiator

Not a payment facilitator; disputes are handled by the merchant's processor, not inside SambaPOS. https://sambapos.com/integrations/ · retrieved 2026-08-01

payments-card-on-file differentiator

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

payments-payout-timing differentiator

Holds no merchant funds and publishes no deposit schedule. https://sambapos.com/integrations/ · retrieved 2026-08-01

payments-p2pe-pci4

Searched sambapos.com's own WordPress search (https://sambapos.com/?s=PCI and ?s=P2PE): both return no matching posts or pages. Grepped all 613 dumped kb.sambapos.com records (286 English, 327 Turkish): zero occurrences of PCI, P2PE, or encryption of any kind; the compliance material the vendor does publish is fiscal (e-invoice/e-archive for Turkey, TSS for Germany, TIMS for Samoa), not card-security. Architecturally the card never touches SambaPOS - every integration hands the transaction to a processor-supplied pinpad (Ingenico, Dejavoo, Quest PinPad, GPI device over IP) - and forum discussion from 2015-2018 treats PCI as the processor's burden and a reason for semi-integration. No AoC, P2PE listing or 'available on request' statement was found on either host, and no vendor statement disclaims one, so unknown rather than no.

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

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

kitchen-course-firing differentiator

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

kitchen-prep-time-pacing differentiator

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-order-throttling differentiator

Corrected reasoning; value unchanged. As before: KB 8.9 and 8.19 document the KDS configuration item by item (Enable KDS, three colour states with minute thresholds, Show Ticket Tag, Remove Finished Products, New Orders Position, per-device product groups, notification voice, fixed height) and none is load-sensitive; 4.13/4.32 build a kitchen display from entity screens and states with no pacing; the inbound channel set is at least eight providers wide (GloriaFood 6.3, Go Order GloriaFood 6.29, takeaway.com 6.15, RestaJet 6.4, plus Go Order USA for Uber Eats/DoorDash/Grubhub in 5.5.8, Trendyol Yemek 5.5.8, Getir and Migros 5.7.0, Jetrik 5.7.10) and no delay, hold, pacing or promised-time item appears in any of the 68 release topics from 5.1.15 to 5.7.28; the only volume brakes are per-item daily count limiting (4.55) and zero-stock blocking (4.50). Added on 2026-08-09: the claim's second limb, extending a quoted prep time, now has a positive account rather than silence - Jesse Parker of SambaPOS documents the vendor's quoted-time mechanism in V5 Tutorial t/16825, where a Ticket Created rule asks the cashier '[?Cook Time(min);;;NOC]' and adds that manually entered figure to {TICKET TIME} to print an ETA. It is per ticket, hand-entered and unconditioned by order volume or ticket time, so no automatic extension exists. The first limb - pacing or delaying release of incoming digital orders - remains undocumented in either direction across the KB, the release series and all 437 V5 Request/Tutorial topics (zero hits for throttl, capacity or time slot), so the cell stays unknown.

kitchen-channel-pause-propagation differentiator

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

kitchen-order-ready-callback differentiator

Marketplace connectors do exist - 5.5.8 (2023-03-09) announced 'Go Order USA Integration added (Uber Eats, Doordash, Grubhub, Gloriafood)', which kb.sambapos.com never documents - so the earlier reasoning that there was nothing to call back to was wrong. What I still cannot establish is the outbound direction. Bumping is documented as a purely local state change (KB 8.9: '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 / Ready Status KReady); KDS V2 (8.19, modified 2026-06-29, minimum 5.7.26) is the same model with the admin panel moved in-app. The GloriaFood-side templates in 6.3 and 6.29 are inbound polls or pushes into gf-producer.sambapos.com, and 6.44 Shipday dispatches a courier rather than notifying a marketplace. No KB article, and no post in the 68-topic V5 Release series through 5.7.28, describes a ready or status event travelling from SambaPOS out to a marketplace - but nothing states it does not, and the GoOrder USA connector is undocumented enough that its callback behaviour cannot be read off the record either way. Unknown.

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

kitchen-all-day-counts

Checked kb.sambapos.com 8.9 and 8.19: the KDS shows one card per ticket, filtered to the product groups selected for that device, with Open Cards and Completed Cards tabs - no aggregate quantity view; 4.13 'How to Generate Kitchen Display' builds an entity screen with a Ticket Lister widget whose template groups orders by product group within each ticket, again per ticket. 9. Reports (14 articles) covers historical sales; 9.5 'How to Create Open Tickets Report for SambaPOS Metrik V2' reports open tickets to the manager dashboard rather than an aggregated item count to a station, and 9.1.2 shows custom reports can run arbitrary SQL, so an operator could build one. Nothing documents an all-day view and nothing says it is absent. Unknown.

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

kitchen-printer-fallback differentiator

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

kitchen-offline-operation differentiator

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

kitchen-item-build-screens differentiator

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

kitchen-pizza-fractional-display differentiator

Checked kb.sambapos.com 4.60 'Half and Half Pizza Configuration': a Half and Half Pizza product priced 0, an order tag group per size ('9 Inches 50/50 Pizza') with Min and Max Selected Items both 2 and 'Add Tag Price to Order Price', and rules (HP-Update Portion, HP-Change Order Price, HP-Update Tag Price) that take the higher of the two tag prices - the split is expressed purely as two selections in one tag group, with no half or section identifier in the data model shown. Checked how that reaches the line: the kitchen-display template in 4.13 renders modifiers as '[=('{ORDER TAG QUANTITY}'>1 ? ... )] * {ORDER TAG NAME}', and the kitchen print template in 4.43 renders them as '{ORDER TAG GROUP}: {ORDER TAG NAME}' - flat text lines in both cases, with no section rendering documented; the KDS app articles (8.9/8.19) describe no graphic element at all. What I cannot establish from the docs is whether operators name the tags to carry the half (the screenshots the articles rely on are not in the text dump), so I will not assert either that placement is rendered unambiguously or that it cannot be. Unknown; the record already cites forum t/10090 on half-and-half pricing, which addresses price, not display.

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

kitchen-order-modification-alerts differentiator

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

kitchen-guest-ready-notification differentiator

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

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

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

kitchen-prep-forecasting

Checked all 14 English articles of kb.sambapos.com 9. Reports, including 9.1.3 and 9.1.4 Custom Reporting Tags (which enumerate the available report tags and database fields - all historical transaction data) and 9.1.2 Creating Custom Reports with SQL; also 5.5.5.a-g (the basic report set: work period, item sales, cash transactions, inventory, inventory transaction, cost), 5.5.7.a-d (warehouses, purchasing, cost check, counting), 4.28 stock level tracking, 4.22 wastage and 4.55 daily item limits, which asks the operator how many of each item they have today rather than predicting it. Nothing forecasts demand and nothing produces a prep task list. forum.sambapos.com /search.json for 'prep list forecast' returns zero posts. Unknown.

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

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

delivery-route-map differentiator

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

delivery-driver-tracking differentiator

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-zones-polygon differentiator

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

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

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

delivery-driver-comp differentiator

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

delivery-cash-reconcile

Corrected reasoning; value unchanged. As before, KB 4.12 settles the Advanced Delivery Service per ticket - 'Get Fast Payment Cash / Credit Card / Voucher' actions and buttons on the Delivered Orders widget window - with no driver bank, no assignment-versus-collected tally and no over/short figure, and the 14 English articles of section 9 list no per-deliverer cash report. Added on 2026-08-09 from the V5 Tutorial corpus: the vendor's own end-to-end delivery implementation settles the same way. Emre Eren's 'Custom Package Delivery for V5' (t/8263, 2015-11-24) builds the whole workflow from an operator-created Deliverers entity type, two Ticket Lister widgets and rules, and ends 'Removing Tickets - We already implemented it. Settling a ticket should remove ticket from Delivered Orders list'; a deliverer is an entity assigned to a ticket, with no float, no cash bank and no variance. Community members supply the missing pieces: t/22739 'Deliverers Report' (2020) is an add-on to the shipped Advanced Delivery configuration task 'useful to keep track of Deliverers/Drivers payments and totals', and even till-level cash-up is a hand-built screen (t/19160, RickH 2019, computing a Final Closing Cash Figure from a manually entered float against counted cash). Still unknown rather than no: this record's 2026-08-09 audit downgraded reporting-cash-over-short to unknown on the finding that counted-cash features here have shipped without KB coverage (the 5.7.6 Time Clock cash-tip declaration), so the same class of absence argument cannot carry a driver-level no either.

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

delivery-daas-fallback differentiator

Read KB 6.44 Shipday Integration (updated 2026-03-12) in full: the integration is a licensed module whose documented wiring is an automation command 'Send to Shipday' + an action of type 'Send Ticket to Shipday' + a rule whose Event Name is 'Automation Command Executed' with constraint 'Automation Command Name Equals Send to Shipday' - i.e. a staff button press pushes one ticket to Shipday. No condition on deliverer availability, delivery zone or elapsed wait appears anywhere in the article, and no other DaaS courier is documented (sambapos.com/en/integrations lists Shipday as the only courier network alongside the Turkish marketplaces). Unresolved because SambaPOS's rule engine is general-purpose - the same action can be bound to other events by the operator - so the KB's silence does not establish that no overflow rule can exist, only that none is shipped or documented.

delivery-3p-direct-integration differentiator

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

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

delivery-menu-push

The GloriaFood evidence is gone: 'Fetch Menu' appears in the 613-article KB dump only inside 6.3, which is headed 'This product is no longer supported', and GloriaFood is discontinued and no longer accepting new signups (gloriafood.com, 2026-08-09). Re-derived from the live channels, nothing publishes a menu outward to a marketplace. SambaPOS does ship a Send Menu and its complete target list is first-party or own-brand: Send Menu to GO Office for GO Kiosk and GO Tablet (8.6, 8.7), Send Menu to SambaPOS KDS, Send Menu to Samba GO Menu, and Jetrik, the operator's own branded ordering site, where the SambaPOS menu can be 'sent to Jetrik with a single click' (6.23, 6.25; release 5.7.0 'Jetrik Send Menu function added'). No marketplace channel has one: in 6.16 (Yemek Sepeti), 6.17 (Trendyol), 6.18 (Migros) and 6.19 (Getir) the menu is authored on the marketplace side and reconciled inbound, each article defining a Default Category for a marketplace product that has no SambaPOS equivalent. No channel-specific price markup field and no photo publishing exist anywhere in the KB in either language or in the release notes through 5.7.28. https://kb.sambapos.com/6-17-go-order-trendyol-yemek-entegrasyonu/ · retrieved 2026-08-09 adversarially verified

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

delivery-store-pause

The five documented Go Order channels (Yemek Sepeti 6.16, Trendyol 6.17, Migros 6.18, Getir 6.19, Jetrik 6.25) each enumerate an in-POS settings screen with no store-pause or timed-reactivation control, and Jetrik's open/closed switch sits in the partner panel at panel.jetrik.com (6.25 s3.1). But those five are not the whole channel set: SambaPOS also ships GoOrder USA carrying Uber Eats, DoorDash, Grubhub and GloriaFood (5.5.8 release notes, 2023-03-09; sold at sambapos.com/goorder-usa/ for $49/month; bug-fixed again in 5.7.8), and it is documented nowhere on kb.sambapos.com - grepping all 613 English and Turkish records for doordash, uber eats and grubhub returns zero. Its in-POS settings surface is unexamined, and store pause is a standard control on those US marketplaces, so absence cannot be asserted. adversarially verified

delivery-3p-reconciliation differentiator

Read the four Go Order marketplace articles (KB 6.16 Yemek Sepeti, 6.17 Trendyol, 6.18 Migros, 6.19 Getir - Turkish only) and KB 6.25 Jetrik. What each one does build is an accounting hook, not a reconciliation: a per-channel discount account, account transaction type, calculation type and calculation selector (e.g. 'TY Indirim Hesabi', 'Jetrik Discount', Yemek Sepeti's 'Joker Iskonto') so the marketplace-funded discount lands on the ticket. No article mentions payout deposits, commission, service or marketing fees, refunds/adjustments, or unpaid/missing orders, and grepping both languages for komisyon/hakedis/payout/commission/reconcil returns nothing. The 9. Reports section ships no such report. Unresolved rather than no because reports in SambaPOS are user-authored SQL (KB 9.1.2) and the KB nowhere states what the marketplace modules do or do not import beyond order and discount data.

delivery-injection-error-visibility differentiator

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

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

delivery-promise-time differentiator

Grepped the full 613-record en+tr kb.sambapos.com dump for promise time, preparation time, estimated/ETA, teslimat suresi and hazirlanma suresi: no article computes or quotes a delivery time, dynamically or statically. The POS-side delivery model (KB 4.12) is a state machine - Waiting, Delivering, Delivered - with no timer input, and Nav Core (KB 6.52) geocodes an address without exposing drive time. The quote a customer actually sees would come from the ordering channel: KB 6.25 s3.3.2 gives the Jetrik panel a Delivery screen and s3.3.4 an Opening Hours screen but describes neither's fields, and GloriaFood/RestaJet host their own checkouts. Unresolved because that partner-side surface was never enumerated by SambaPOS.

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-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

digital-menu-single-source

GO Tablet advertises 'real-time menu synchronization' with the POS; Jetrik is managed separately. https://sambapos.com/sambapos-go-tablet/ · retrieved 2026-08-01

digital-native-app differentiator

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

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-upsell-engine differentiator

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

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

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

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

digital-kiosk differentiator

GO Kiosk runs the SambaPOS menu with self-service payment; no published accessibility conformance. https://sambapos.com/sambapos-go-kiosk/ · retrieved 2026-08-01

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

digital-catering-portal differentiator

KB 6.25 s3.3 enumerates the Jetrik panel's Services and Hours screens as Pickup, Delivery, Dine In, Opening Hours and Scheduled Orders - no catering service type - and KB 8.14's GO Office device settings expose only delivery types and payment types. Grepped the full 613-record en+tr KB dump for catering: the only hit is an unrelated use of the word in a Turkish/English gift-and-void reporting article. No minimums, lead-time rules, quotes/proposals, deposits or invoice/ACH terms appear anywhere in the KB. Unresolved rather than no because SambaPOS does ship the adjacent primitives - Customer Accounts with debiting/charging and account limits (KB 5.1.10.b-d, 5.4.8.c, 4.82), price tags per department and per customer type (2.4.5), and a general automation engine - so a catering flow is constructible, and the vendor has never stated whether a catering product exists.

digital-voice-ai-phone differentiator

Grepped all 613 en+tr kb.sambapos.com records for AI, artificial intelligence, machine learning, yapay zeka and sesli siparis: zero hits of any kind. The telephony surface is Caller ID only - KB 3.6 (device setup; the hardware doc names CIDShow and Hugin Caller ID boxes and Conexant fax modems), 4.5 (using Caller ID for delivery service), 4.56/4.92 (call logging) and 8.5/8.23 (Android Caller ID app) - all of which pop the matching customer entity so a human takes the order. sambapos.com/en/integrations (retrieved 2026-08-08) lists no voice or AI partner. Unresolved rather than no because an integrations page is a directory and a grep is a search: SambaPOS publishes no supported/unsupported statement about voice ordering, and its GraphQL API would let a third party inject orders without appearing in any SambaPOS document.

digital-drivethru-ai

The kb.sambapos.com dump (286 en + 327 tr posts, every body searched) has no drive-thru or lane article at all, and zero hits for AI, artificial intelligence, machine learning, yapay zeka or sesli siparis. The vendor's drive-thru material is a marketing page (sambapos.com/drive-thru-pos/, grade D) describing lane hardware and GO Kiosk self-service; GO Kiosk's own configuration doc (KB 8.14) enumerates the whole GO Office console with no voice or speech feature. Left unknown because nothing on either host asserts that lane voice ordering is unsupported - the evidence is a comprehensive search returning nothing, which is not a finding of absence.

digital-sms-ordering

SMS out of SambaPOS has two implementations and both are outbound. 4.35 is a URL Printer against a gateway the operator supplies - the operator pastes their own URL ('http://api.center.com/v1/send-sms/get/?username=...&text=@message@&receipents=@number@'), builds a printer template filling {ENTITY DATA:Customer:Phone} and a message body, and fires it from an automation command. 5.5.8 additionally added a native action ('Twilio SMS Integration added (An action added for this)'), which the knowledge base never documents, so the earlier reading that SMS is only a bring-your-own-gateway URL Printer was incomplete. Neither path is a listener. Nothing in the English or Turkish knowledge base, and no release note from 5.5.0 through 5.7.28, documents an inbound SMS or chat endpoint; the only inbound telephony is Caller ID (3.6, 4.5, 8.23), which reads the calling number rather than a message. Unresolved rather than no because SambaPOS exposes a GraphQL API and a general rule engine, so a text-to-order bridge is buildable, and no vendor page states whether conversational ordering is or is not supported.

digital-google-order differentiator

Undetermined. The prior no rested on SambaPOS having no direct ordering link to provision, and that is refuted: Jetrik - sold as a SambaPOS SKU and documented in KB 6.23/6.25 - gives the restaurant a 'Personalized URL' and, on the Pro tier, its own 'Custom Domain' with a private SSL certificate (jetrik.com/features and jetrik.com/pricing, retrieved 2026-08-09), which is exactly the kind of link Order with Google provisions. Whether that link is or can be provisioned to a Google Business Profile is not addressed by any source I can reach: 'Google Business' and 'Order with Google' return zero hits across the 2.4MB KB dump in both languages (the only Google references are to the Google Maps API), sambapos.com/integrations/ lists no Google integration, and jetrik.com has no integrations page - its footer link 404s. Absence of mention on feature and integration pages is not positive evidence of absence, so this is unknown rather than no.

digital-apple-business-connect

Checked sambapos.com/en/integrations (retrieved 2026-08-08; payment, marketplace and online-ordering partners enumerated - GloriaFood, RestaJet, Jetrik, Shipday, Yemek Sepeti, Getir, Trendyol, Migros, no Apple entry), and searched the complete kb.sambapos.com corpus offline (286 en + 327 tr post bodies): 'Apple' occurs exactly twice, both in GO Tablet/GO Kiosk hardware requirements ('for Apple tablets, iOS version must be 10 or above'). No Apple Business Connect, Apple Maps or place-card material on kb.sambapos.com, sambapos.com or forum.sambapos.com. SambaPOS also has no first-party hosted ordering flow for an Order Food action to point at - its digital channels are the partner-hosted Jetrik, GloriaFood and RestaJet - which makes support unlikely, but no vendor statement establishes absence, so this stays unresolved.

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

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

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

digital-guest-data-ownership differentiator

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-pci-sca

Grepped all 613 en+tr kb.sambapos.com records for PCI, DSS, 3D Secure, 3DS and SCA: zero hits in either language. The digital checkout is not SambaPOS's: KB 6.25 s3.4 places Payments, Payment Methods and the Paynet payment activation inside the Jetrik panel, GloriaFood and RestaJet host their own checkouts (KB 6.3, 6.4, 6.29), and the GO Kiosk console only maps payment type names for a device standing in the restaurant (KB 8.14 s4.6). SambaPOS's own card handling is terminal-side integrations to physical PIN pads (Worldline TIM, Ingenico/Beko/Pavo/Hugin fiscal devices, KB 6.22-6.51). Unresolved because the claim asks what the vendor publishes: SambaPOS makes no compliance statement to read, and the compliance obligation for the hosted page sits with the partner, which is a structural argument rather than evidence of the vendor's position.

digital-surcharge-transparency differentiator

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-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

guest-loyalty-thirdparty-identity-attach differentiator

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

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

guest-loyalty-tiers differentiator

SambaPOS's shipped loyalty material is KB 4.27 (Basic Loyalty Points Implementation - a Loyalty Card entity type with Holder Name and a hidden Points custom field, an Apply Loyalty Discount command whose button caption computes points x 0.01, and a Claim Unused Points command; entirely operator-assembled and flat) and KB 2.4.9 SambaCard (a card entity backed by an account, used as stored value). Neither has tiers, thresholds, promotion or demotion. Also read KB 2.4.5 (different prices by customer type) and 2.4.17 (automatic discount for customer groups) - these are static operator-assigned groups, with no rolling-window spend or visit rule and no automatic movement between groups. The closest tier language is partner promotional copy on the vendor forum: 'You can create customer classes according to the spending limits you set' (Tayfun, staff, t/21733, 2020) describing RestaJet's system - no rolling window, no demotion, and not SambaPOS. Unresolved on that basis.

guest-loyalty-offline-behavior differentiator

Read the two loyalty articles end to end (KB 4.27 Basic Loyalty Points, KB 2.4.9 SambaCard): both store points and balances as entity custom fields and account transactions in the same local Microsoft SQL Server instance the POS runs on, so by architecture they are LAN-local - but neither article, and no article in 2.4, 4 or 5, ever discusses connectivity loss, queueing or reconciliation for loyalty. Grepped both languages for offline/cevrimdisi alongside loyalty/puan: no hit joins them. The only connectivity documentation in this area is community discussion of multi-branch customer sync on the forum (t/13351, t/5047), which is grade D and speculative. Unresolved: the claim asks whether the vendor documents the behaviour explicitly, and it does not - inferring it from the single-database architecture would be analyst inference, not documentation.

guest-loyalty-offer-stacking-rules differentiator

Discounts and surcharges in SambaPOS are Calculation Types surfaced through Calculation Selectors. Across every article that builds one (KB 2.3.10.c, 2.4.7.a/c, 4.27 s3.3, 4.41, 4.78, 4.95, 6.25 s1.2.3, 6.16-6.19) the documented fields are the same short set - Template Name, Account Transaction Type, Calculation Method (Rate / Fixed Amount / Fixed Amount from Ticket Total), a Decrease Amount checkbox, and mappings by role/department/ticket type - with no combinable-vs-exclusive flag, no priority or order-of-application field and no mutual-exclusion group. KB 2.3.10.c ('How to Limit Discount and Rounding') limits WHO may discount and by how much via role permissions, not how offers interact. Left unknown rather than no because no article enumerates the Calculation Type editor in full (several say 'other templates can also be selected according to working style'), and calculation types do carry an ordering when several are applied to one ticket that the KB never documents.

guest-loyalty-targeted-offers differentiator

In SambaPOS itself there is no offer-issuance channel to target: discounts are calculation selectors pressed at the terminal (KB 5.4.6, 4.41, 4.78, 4.95), automatic rules keyed on a customer group or product (2.4.17, 4.59, 4.63, 4.15 'give a promotional product to each new customer for one time'), and the only outbound message path is an operator-supplied SMS gateway fired per ticket by a print job (KB 4.35) - there is no list, no send and therefore no audience definition. Grepped both languages for campaign/segment/audience/kampanya/segment: no product feature. The one on-point statement is partner promotional copy from SambaPOS staff on the forum - 'With the automatic communication rules you set, you can celebrate your customers' birthdays, and send special discount codes to those who have not ordered for 30 days' (Tayfun, staff, t/21733, 2020) - which describes RestaJet's marketing automation, not SambaPOS, and is marketing rather than documentation. Unresolved on that basis; if RestaJet is treated as in scope this cell should be re-examined against RestaJet's own documentation.

guest-loyalty-rfm-segmentation differentiator

Walked the whole 9. Reports section (14 English articles): 9.1.1-9.1.9 are the custom-report toolkit (report templates, 'Creating Custom Reports with SQL', custom reporting tags, pivot and table views, the report viewer widget, filtering and grouping), and the shipped named reports are Item Sales by Product Tag (9.2.2), Void and Gift (9.3), Item Group Sales by Ticket Type (9.4), Open Tickets for Metrik V2 (9.5) and Remaining Balanced Customers (9.8.1). None computes recency, frequency, monetary value or any lifecycle label, and grepping both languages for RFM/segment/at-risk/lapsed/VIP finds no feature. Customer data can be exported to Excel (KB 4.94) for outside analysis. Unresolved rather than no because the reporting surface is explicitly user-authored SQL over the POS database, so what a given site 'has' is not fixed by the documentation, and the vendor never states that no lifecycle segmentation ships.

guest-loyalty-lifecycle-automation

Searched the full en+tr KB for birthday/dogum gunu, win-back, lapsed and campaign: no shipped campaign product. What exists is the general Automation (Actions/Rules/Automation Commands) engine plus hand-built recipes such as KB 4.15 'How to Give Promotional Product to Each New Customer for One Time' - a first-visit gift assembled from a rule, not a configurable always-on campaign - and KB 4.35's operator-supplied SMS gateway as the only outbound channel. No scheduler over customer state is documented; SambaPOS's only time-driven jobs in the KB are end-of-work-period tasks (e.g. 2.4.12.e emailing reports). The birthday and 30-day win-back language in this record's neighbourhood comes from SambaPOS staff promoting the RestaJet partner product (forum t/21733, 2020), which is marketing for a third party's system. Left unknown because the vendor makes no statement either way about shipping lifecycle campaigns.

guest-loyalty-native-email-sms differentiator

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

guest-loyalty-consent-management

Searched all 613 kb.sambapos.com records (286 en + 327 tr bodies) for consent, opt-in/opt-out, unsubscribe, STOP, GDPR, KVKK and kisisel veri: zero hits in either language. The Customers entity type's documented custom-field surface (KB 2.2.6, 4.48 multiple addresses, 4.77 image, 6.52 Nav Core address sub-fields) contains no consent flag, timestamp or source, and consent is not among the locked sub-fields Nav Core creates. The only messaging path is KB 4.35, where the operator supplies their own SMS gateway URL and credentials and SambaPOS merely POSTs to it from a print job - so revocation handling would sit with the gateway, and there is no inbound path for SambaPOS to receive a STOP in the first place. sambapos.com/en/integrations lists no email or SMS marketing platform. Unresolved because none of this is a vendor statement that consent capture is unsupported; per-channel consent could be modelled as operator-built custom fields.

guest-loyalty-10dlc-registration

KB 4.35 (2019) documents SMS as a bring-your-own-gateway URL Printer - the operator pastes their own operator's send-sms URL and credentials into a custom printer - which would put 10DLC registration entirely on the operator's side. But that is no longer the whole of SambaPOS's SMS capability: the 5.5.8 release notes (2023-03-09) state 'Twilio SMS Integration added (An action added for this)', a native action against a US aggregator for which A2P 10DLC brand and campaign registration is a live requirement. The Twilio action has no KB article (zero hits for twilio across all 613 English and Turkish records), so whether SambaPOS handles, passes through or documents registration for it cannot be determined, and the zero-hit corpus search that supported the 'does not document it' half is unreliable for a feature the KB never covers. adversarially verified

guest-loyalty-campaign-attribution differentiator

There is no campaign or offer object in SambaPOS to attribute sales to - promotions are calculation types and automation rules created per site (KB 4.4, 4.10, 4.15, 4.59, 4.63, 4.75, 2.4.7.a/c) - so attribution would mean reporting on a discount account. Walked the entire 9. Reports section: the shipped named reports are Item Sales by Product Tag, Void and Gift, Item Group Sales by Ticket Type, Open Tickets and Remaining Balanced Customers; everything else is the custom SQL/report-tag builder (9.1.1-9.1.9). Nothing ties a redeemed offer to incremental check totals, and grepping both languages for attribution/incremental/redemption report finds no such feature. Discount amounts do land in dedicated discount accounts (e.g. Jetrik Discount, Loyalty Discount, TY Indirim), which is the raw material for a hand-built report but not a shipped one. Unresolved because a user-authored report layer means the documentation cannot establish absence.

guest-loyalty-data-export-portability differentiator

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

guest-loyalty-review-capture-routing differentiator

Grepped all 613 en+tr kb.sambapos.com records for survey, feedback, anket, review, rating, NPS, Google review and TripAdvisor: the only hits are 'Preview' buttons in printer-template articles and a 'Help and Feedback' menu item in a Turkish module article - no post-transaction feedback request anywhere. The nearest surface is passive: KB 6.25 s3.8 gives the Jetrik panel a Comments/Contacts screen where 'you can view comments and communication messages about your restaurant', with no request trigger, no score and no routing. The only outbound channel SambaPOS itself has is the operator-supplied SMS gateway (KB 4.35), which could carry a survey link if the operator built one. Left unknown because nothing on kb.sambapos.com, sambapos.com or forum.sambapos.com states that feedback capture or score-based routing is unsupported.

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

guest-loyalty-wallet-pass differentiator

Zero hits for wallet, Apple Wallet, Google Wallet, PassKit, .pkpass or cuzdan across all 613 en+tr kb.sambapos.com records; the only two 'Apple' occurrences in the corpus are iOS version requirements for GO Tablet hardware. SambaPOS's card model is a physical or virtual card entity identified by a card number - SambaCard (KB 2.4.9, card entity plus account, selected on the ticket via an entity search screen) and the Loyalty Card entity of KB 4.27 - with barcode/QR printing available from slip or barcode printers (KB 2.4.8.a/b) for the card itself. No push-updatable balance mechanism of any kind is documented. Unresolved rather than no because the vendor publishes no statement on wallet passes and no enumeration of loyalty-card delivery formats.

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

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

guest-loyalty-ai-offer-recommendation differentiator

Grepped every one of the 613 kb.sambapos.com post bodies (286 en + 327 tr) for AI, artificial intelligence, machine learning, yapay zeka, ML, predictive and recommendation: zero hits of any kind, in either language, including the 2026-dated articles (Nav Core 6.52, Shipday 6.44, SQL setup). sambapos.com/en/integrations (retrieved 2026-08-08) names payment/fiscal devices, marketplaces and ordering partners only, with no AI vendor. There is likewise no offer-issuance product for a recommendation to attach to - see guest-loyalty-targeted-offers. Unresolved rather than no because the evidence is an exhaustive search returning nothing plus a directory page, neither of which is a first-party statement that no such feature exists or is planned.

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-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

labor-photo-punch-verification differentiator

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

labor-offline-time-punch differentiator

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

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

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

labor-native-scheduling differentiator

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

labor-demand-labor-forecast differentiator

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

labor-realtime-labor-percent differentiator

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

labor-overtime-prevention differentiator

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

labor-break-compliance-by-state differentiator

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

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

labor-tip-pooling-rules

Tip capture is documented; distribution is not, in either direction. KB 4.70 How to Add Tip Calculation and its Turkish twin build a Tip account, a Tip account transaction type and a Calculation Type with 'Calculation Method: Fixed Amount' behind a Calculation Selector button, which adds a tip to a ticket and posts it to a Sales/Receivable account; the PaymentSense Dojo and Quest articles (6.14, 6.31) repeat the same three objects for card tips. The KB is not the whole product, so I also read the 68-topic V5 Release series through 5.7.28: it adds tip capture and adjustment only - 5.7.6 'Time Clock declare cash tip option and declaration added' (a declared cash-tip figure the KB never documents), Dejavoo tip adjust across multiple terminals (5.7.24) and tip and split-payment calculation improvements (5.7.28) - and never a pool, a share or a tip-out. Nothing splits a pool by hours, sales, points or role; 4.6 How to Manage Staff Salaries pays staff by manual account transactions with no tip input, and the Time Clock assignment carries only an hourly wage. But no vendor statement rules it out and the account system plus custom SQL reports could plausibly be configured to do it, so this is unresolved rather than absent. Unknown.

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

labor-qualified-tips-w2-reporting differentiator

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

labor-native-payroll differentiator

No payroll product exists in the SambaPOS product catalogue. https://sambapos.com/products/ · retrieved 2026-08-01

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

labor-shift-swap-workflow differentiator

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

labor-server-performance-metrics differentiator

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-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

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

inventory-theoretical-vs-actual differentiator

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

inventory-realtime-depletion differentiator

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

inventory-86-auto-sync differentiator

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

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

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

inventory-vendor-catalogs-edi differentiator

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

inventory-invoice-ocr differentiator

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

inventory-price-change-alerts differentiator

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

inventory-par-auto-suggest differentiator

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

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

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

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

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-native-not-partner differentiator

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

inventory-menu-margin-linkage differentiator

Cost reports show product cost against price; automatic margin-threshold flagging on ingredient cost change is not documented. https://kb.sambapos.com/en/ · retrieved 2026-08-01

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

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

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

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

reporting-cash-over-short

Withdrawn. The earlier no read the Cash Transactions Report article (last modified 2018-03-29), which describes that one report's blocks - Sales Incomes, Out of Sales Incomes and Customer Account Incomes, Income Totals, Expenses, Expense Totals, and Cash Status, 'the clarified situation of cash after subtracting expense total from income total' - and generalised from a single report's block list to the absence of any counted-versus-expected variance in the product. That step requires the KB to be a complete feature inventory, which this record has now established it is not: the Reservation module, GoOrder USA and the Time Clock cash-tip declaration all ship undocumented. Re-checked in both directions and found nothing to replace it. Neither the 286 English nor the 327 Turkish KB records contains a cash-count, till-declaration or variance article (zero hits for cash count, counted cash, over/short, variance, kasa sayim, nakit sayim, kasa fark), there is no drawer-session or drawer-assignment concept in the documented model, and the 68-topic, 1,451-post V5 Release and Beta series through 5.7.28 announces no drawer count or over/short feature - but 5.7.6 (2023-12-25) does announce 'Time Clock declare cash tip option and declaration added', proof that counted-cash declaration surfaces reach this product without documentation. No positive evidence of absence, and none of presence. Unknown. adversarially verified

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

reporting-server-scorecards differentiator

Achievable through the custom report engine; not shipped as a named report. https://kb.sambapos.com/en/ · retrieved 2026-08-01

reporting-channel-profitability differentiator

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

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

reporting-public-api differentiator

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

reporting-webhooks differentiator

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

reporting-api-not-upcharged differentiator

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

reporting-tier-paywall differentiator

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

reporting-history-retention differentiator

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

reporting-anomaly-alerts differentiator

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

reporting-nl-query

Corrected reasoning; value unchanged, and the note's own last remaining gap is now closed. No natural-language or AI assistant surface appears in the 286 English or 327 Turkish kb.sambapos.com records, nor in the full V5 Release and V5 Beta Release dump (68 topics, 1,451 posts, 5.1.15 through 5.7.28 of 2026-07-02): 'Push notification added to Metrik' and generic 'Metrik Improvements' are the only metriK entries, and the only 'assistant' hit is a 2017 community joke asking for 'a siri like assistant that can configure any feature by voice'. The earlier note conceded that the forum's Request and Tutorial categories had not been dumped; they have since been dumped in full - forum.sambapos.com categories 21 (V5 Request, 258 topics), 22 (V5 Tutorial, 177) and 30 (V5 Features, 2), 437 topics and 6,390 posts - and they return zero occurrences of 'natural language', 'machine learning' or ChatGPT, with the sole 'artificial intelligence' occurrence again a community joke. Every documented way to ask SambaPOS a question remains a custom report: a bracketed template with report tags (9.1.3/9.1.4), optionally backed by a registered SQL script (9.1.2), viewed in the report viewer or in metriK V2 for reports flagged 'Display In Metrik'. Three corpora are now silent rather than one, but silence is still not a vendor statement of absence and none of the three is an enumeration of the reporting surface. Unknown. adversarially verified

reporting-guest-cohorts differentiator

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

reporting-sales-forecast differentiator

Checked all of kb.sambapos.com section 9 Reports, the report tag references 9.1.3 and 9.1.4 (whose documented fields are ticket, order, order-tag, menu-item and entity attributes - all recorded history), the packaged reports in 5.5.5.a-g (Work Period, Item Sales, Cash Transactions, Inventory, Inventory Transaction, Cost), the Custom Report Viewer Widget's date-range vocabulary in 9.1.8 (This/Past Month, This/Past Week, Today, Yesterday, Workperiod, 'Last 10 days', explicit ranges - and a 'Next 10 days' option that selects future-dated records such as reservations, not a projection), and section 8's metriK V2 report viewer. The string 'forecast' occurs in none of the 286 English or 327 Turkish KB posts; the nearest Turkish term, 'Tahmini Seviye' in 5.5.7.a, is the projected stock level after current transactions, not a sales projection. So no forward sales figure is exposed in the reporting UI and none is consumed by scheduling or purchasing. What stops this being a `no` is that the only evidence is absence: no enumeration asserts the report set is complete, and 9.1.2 lets an operator register arbitrary SQL that could compute a naive projection. Unresolved.

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-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

multi-location-central-menu-publish

Neptune centrally controls products, menus and prices across branches; publish/version history is not documented. https://sambapos.com/sambapos-neptune/ · retrieved 2026-08-01

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

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

multi-location-cross-location-giftcard

Withdrawn. The earlier no argued from Neptune's sync scope ('branches are defined for products, menu, stocks and recipes') plus the premise that gift certificates in SambaPOS are only local rows - a GC product, GC Accounts and GC Balances account types and a Gift Certificate entity type (4.31) - in each branch's own MSSQL database. The vendor's V5 Release series disproves that premise: 5.3.2 (2021-01-20) announces 'Valutec Gift Card Integration Added (US Only)' and 5.7.16 (2025-03-11) 'Gift Card Support Added to Dejavoo Integration'. Both are processor-hosted gift-card programmes whose balances live on the acquirer's network rather than in the branch database, and neither appears anywhere in the 613-record KB dump (zero hits for Valutec; the two Dejavoo articles, 6.34 and 6.42, never mention gift cards). Neptune's scope therefore does not settle the question. Searched both directions for a replacement and found nothing: no vendor page states whether a Valutec or Dejavoo card sold at one site is redeemable at another, and no outstanding-liability or inter-store settlement report is documented. Unknown. adversarially verified

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

multi-location-multi-brand differentiator

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

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

multi-location-central-labor-policy

SambaPOS is one installation per site (2.1.6) and Neptune, the multi-branch layer, defines branches only for 'products, menu, stocks and recipes' (10.2) with no user, role or labor configuration, so a per-location-group labor policy has no obvious home. But the settings enumeration the assertion rested on is out of date: KB 8.13 was last modified 2023-10-11 and lists only Enable Time Clock, Force User for Clock in Before Login and Enable Breaks (paid/non-paid), while the vendor's release notes add Time Clock payroll overtime settings in 5.7.8 (2024-01-31), a cash-tip declaration in 5.7.6, a clock-out-all-users action in 5.7.10, UserClockIn/UserClockOut automation rules in 5.7.22 and a reworked Assignment screen in 5.7.26. Overtime settings demonstrably exist and are undocumented, so neither their scope nor their enforcement point can be assessed from the published surface. adversarially verified

hardware-commodity-devices differentiator

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

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

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

hardware-handheld-battery-swap differentiator

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

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

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

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

hardware-kiosk differentiator

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

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

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

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

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

hardware-tap-to-phone differentiator

No documented Tap to Pay on iPhone / Tap to Pay on Android acceptance, but no exhaustive enumeration establishes its absence either. KB 8.10 (SambaPOS Mobile Client MC3, modified 2023-10-02) ships a first-party app on both Google Play and the iOS App Store whose documented function list includes '5.3.4. Getting Payment on SambaPOS Mobile Client - Select desired table, click on Settle button', so a payment screen does exist on a commodity phone; the article never enumerates which payment types that screen offers. The older 5.1.12.a Android client index (no settle screen) is superseded and cannot stand as the mobile function set. Card acceptance in every documented processor integration (6.2 PaymentSense, 6.14 Dojo, 6.20 Global Payments, 6.26 Worldline TIM, 6.31 Quest, 6.34/6.42 Dejavoo) runs on an external PIN pad and no SoftPOS or NFC-acceptance content appears in the 613-record KB dump or in a forum search for 'tap to pay' - but an integration list is a directory, not a completeness assertion, and a search returning nothing is not evidence of absence. Unknown.

hardware-pricing-transparency differentiator

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-ownership-vs-lease differentiator

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

hardware-usable-after-churn differentiator

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

hardware-rma-sla differentiator

No vendor hardware means no vendor warranty term or advance-exchange programme. https://sambapos.com/products/ · retrieved 2026-08-01

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

hardware-remote-device-management differentiator

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

hardware-selfpour-scales

No self-pour tap wall, flow meter, pour spout or dispense-controller integration is documented anywhere SambaPOS publishes, but nothing positively establishes its absence. KB 3.1 'Hardware Requirements and Compatibilities' walks through computer, printer, tablet, Caller ID, scales, barcode reader and cash drawer without ever claiming to be the complete supported-peripheral list, and its scales entry deliberately generalises - '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.' The five scale modules (8.4 CAS ER, 8.8 Avery Berkel, 8.12 CAS PDN, 8.16 Datalogic Magellan, 8.20 Wintec) and 4.66 / 5.1.11.a all describe weigh-to-price at the counter, not a metered pour posting to an open tab, and forum.sambapos.com /search.json returns zero topics for 'flow meter', 'self pour', 'tap wall', 'beer dispense', 'PourMyBeer' and 'iPourIt'. That is absence of evidence across a hardware compatibility page and a help-centre search, which is unknown rather than no.

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

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

extensibility-api-access-cost differentiator

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

extensibility-free-sandbox differentiator

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

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

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

extensibility-webhook-reliability differentiator

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

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

extensibility-menu-write-api differentiator

KB 4.100 (Customization) documents a menu WRITE against the local GraphQL endpoint that KB 4.19 puts on port 9000 of the SambaPOS server: gql.Exec('mutation m {addProduct(name: "...", groupCode: "...", barcode: "...", portions: [{name: "...", price: "..."}]) { id name groupCode }}'), followed by postResetProductCacheMessage to flush the product cache, and a getProduct read. Shortfall: in SambaPOS's own worked example the price does not stick from the mutation - the script immediately runs sql.ExecSql("UPDATE MenuItemPrices SET Price = ... WHERE MenuItemPortionId = ...") to set it; no mutation for modifiers/order tags or for updating an existing product is documented; and no GraphQL schema reference is published, so the mutation surface is only visible through scattered scripting examples. https://kb.sambapos.com/en/4-100-how-to-add-new-product-by-scanning-unknown-barcode/ · retrieved 2026-08-08

extensibility-doordash-preferred differentiator

DoorDash's newsroom post announcing the 2026 integration standards (published 2026-05-18) names the complete 2026 Preferred Integration Partner cohort: Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast and UrbanPiper. SambaPOS appears nowhere on the page. This is the named list the prior researcher lacked; sambapos.com does market a 'Doordash Integration' page, but that is its own GoOrder/aggregator path, not DPIP membership. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-08

extensibility-first-party-delivery-integrations differentiator

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

extensibility-middleware-compatibility

Grepped the full kb.sambapos.com dump (613 records, English and Turkish) for Deliverect, Chowly, Otter, Checkmate and ItsaCheckmate: zero hits, and the KB Integrations index covers payment terminals, GloriaFood, RestaJet, takeaway.com, Shipday, 7shifts, Jetrik and Nav Core with no aggregation middleware. That corpus cannot be treated as complete, so the finding rests on two sources that do not depend on it. First, the vendor's own release series on forum.sambapos.com (68 topics, 5.1.47 through 5.7.28, 2015-2026) announces no aggregation-middleware integration of any kind - zero occurrences of Deliverect, Chowly, Otter, Checkmate or ItsaCheckmate in any release note - while it does announce every other integration the product shipped, including the KB-undocumented GoOrder USA. Second, the endpoint list lives on the middleware side, and two of the five publish enumerated POS partner directories: tryotter.com/integrations (Squirrel Systems, Micros, Maitre'D, Lightspeed, XPIENT, Brink, Revel, Lavu, Yammii, Loyverse, Focus, Veloce, Toast, Clover, 4Soft, GoTab, Square, POSitouch, Epos Now, InTouch, Shift4) and itsacheckmate.com/integrations (Par Brink, Revel, Toast, SpotOn, Genius, Clover, Upserve, Square, Ovvi, HungerRush, Union, Cake, Salido, NCR, NCR Silver, Maitre D, SpeedLine, Focus, Micros, Micros Res, PixelPoint, Rezku, Prism, Order Counter, 4Soft, UperMenu, Xenial, Dinerware) - SambaPOS is on neither, and both pages were re-retrieved on 2026-08-09 with SambaPOS still absent. WITHDRAWN: an earlier version of this note cited the V5 Request topic 'Deliverect API Integration' (t/23808, 2021-02-15) as carrying 'a staff reply from Jesse Parker'. The dumped topic records 6 posts, none by staff; the author is 'Jesse', a community member never flagged as staff in any forum dump, and the surname is not in the source. His 'We will be integrating with all of them but it takes time for those partnerships' and 'I think we have plans for something better. Stay tuned' are therefore community speculation, not a vendor roadmap statement, and carry no weight here. Left unresolved rather than no because the claim's bar is two supported endpoints and only two of the five directories are enumerable: deliverect.com/en-us/integrations/pos-systems renders its POS list client-side (no POS names resolve to a fetch) and chowly.com/integrations 404s, both re-checked 2026-08-09. SambaPOS also exposes a GraphQL endpoint that would let a middleware build a connector without any SambaPOS-side announcement. adversarially verified

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

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

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

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

extensibility-data-portability-exit differentiator

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-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

reliability-offline-card-auth differentiator

The words 'offline' (English) and 'cevrimdisi/cevrim disi' (Turkish) return zero hits across all 613 kb.sambapos.com records in both languages. Every documented card path hands the card leg to a third-party terminal or gateway - PaymentSense Pay At Counter 6.1 and Pay At Table 6.2, Dojo 6.14, OpenEdge 6.5, International Bancard 6.12, Global Payments 6.20, Quest 6.31, Worldline TIM 6.26, Dejavoo 6.34/6.42, plus the Turkish fiscal-device set - and none of those articles describes queued authorisation, a stored-transaction cap or a reconnect flush. On forum.sambapos.com the V5 Request 'Offline feature' (t/13944, 2017-02-03) asks for offline operation against a remote database and drew only community replies, no vendor commitment. Left unresolved rather than 'no' because store-and-forward, where it exists, is a capability of the acquirer's terminal (Dojo, Global Payments, Dejavoo) rather than of SambaPOS, and I did not retrieve those vendors' terminal specifications in this pass.

reliability-offline-decline-liability differentiator

Checked the same two hosts as reliability-offline-card-auth: kb.sambapos.com has no offline/store-and-forward article in either language (zero hits over 613 records), so there is no documented mechanism for a decline-liability or offline-cap statement to attach to. The public contract was read in full at sambapos.com/terms-of-use/: the closest clause is 3.17, 'products offered through providers, services, and servers can sometimes be interrupted for certain or unspecified reasons that are not connected to SambaPOS. SambaPOS is not responsible for any damages incurred by this situation' - a general third-party-outage disclaimer, not an allocation of loss on a declined stored transaction, and it states no per-transaction or cumulative cap. Unresolved because the party that would publish such a statement is the acquirer whose terminal holds the card leg, and those documents were not retrieved.

reliability-lan-degraded-multi-terminal differentiator

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

reliability-local-transaction-engine differentiator

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

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

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

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

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

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

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

reliability-onsite-install differentiator

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

reliability-menu-build-service differentiator

Terms of Use 3.8: 'Some of the SambaPOS products have a high level of configurability. These configurations must be made by the user or reseller after licensing. If there is no agreement between the user and SambaPOS to make these configurations, SambaPOS will not provide these configurations according to the client's requests and workflow. SambaPOS is not a part of the contractual arrangements, installation and support contracts and trade arranged between the user and the reseller.' 3.3 adds that SambaPOS 'does not provide installation and support services for licensed products'. Menu construction is exactly such a configuration and the KB presents it as operator work (2.3.8 detailed menu design, plus the Import/Export from File utility 2.4.2 for bulk entry). There is no onboarding package, menu-build service or data-entry SKU on sambapos.com's pricing or product pages. https://sambapos.com/terms-of-use/ · retrieved 2026-08-08

reliability-hardware-replacement-sla

No vendor hardware, therefore no replacement programme. https://sambapos.com/products/ · retrieved 2026-08-01

reliability-pci-dss-4-attestation

Grepped the complete kb.sambapos.com dump (613 records, English and Turkish) for pci, p2pe, attestation, aoc and compliance: no PCI DSS material of any kind. Retrieved the full wp-sitemap page index for sambapos.com (66 pages) and the download library (wp-sitemap-posts-wpdmpro-1.xml, 17 items): there is no security, trust, compliance or certification page - the only regulatory pages are 'Regulation TSS for Germany' and 'Regulation TIMS for Samoa', both fiscal-recording rules, not card security. The Terms of Use and Privacy Policy were read in full and name no card-data standard; Privacy 3.11 invokes only Republic of Turkey Law No. 6698. Left unresolved rather than 'no' because SambaPOS runs on the merchant's own Windows/SQL Server and never touches card data, so the entity that would hold a v4.0.1 AoC is the acquirer, and any AoC covering SambaPOS's own hosted services (licensing check, Metrik, Neptune) would plausibly be issued under NDA rather than published.

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

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

reliability-failover-terminal-role differentiator

Read the deployment articles in the kb.sambapos.com dump: 2.1.1/2.1.3 set up one machine as the SQL Server Express host, 2.2.1 Quick Setup connects terminals to it, and the licensing article states 'After licensing from the main machine, the Message Server will work and automatically license all terminals connected to it' - a single designated primary by construction. Grepped all 613 records in both languages for failover, fail-over, redundancy, cluster, 'yedek sunucu' and 'always on': zero hits, and there is no HA, clustering or mirroring article. forum.sambapos.com searches for server redundancy and disaster recovery return only community troubleshooting threads (e.g. t/4608 Disaster Recovery, 2015) with no staff statement either way. Unresolved because the absence of a documented promotion mechanism is not the vendor asserting that no terminal can assume the role - the record needs a staff statement or a settings surface showing the server role is fixed, and neither was found.

reliability-cellular-backup

KB section 3 (Hardware & Network) contains only five English articles - 3.1 Hardware Requirements and Compatibilities, 3.4 printers, 3.6 Caller ID, 3.7 pole/customer display, 3.8 cash drawer - none of which discusses WAN links, routers or connectivity failover. Grepped all 613 records in both languages for cellular, LTE, 4G, 5G, SIM and hotspot: no article documents an automatic mobile-data failover for terminals. Architecturally the transaction path is Windows terminals on a LAN against a local SQL Server, so a WAN outage does not stop order capture, and the internet dependency is confined to the licence check, cloud add-ons and delivery-aggregator polling. Unresolved rather than 'no' because the vendor has published no statement about terminal connectivity failover at all, and the Android/GO clients could in principle run over a device's own mobile data without a documented failover feature.

commercial-month-to-month-contract differentiator

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

commercial-no-early-termination-fee differentiator

A perpetual license leaves nothing to terminate early, but no public terms of service or MSA states this, and annual add-on cancellation terms are unpublished. https://sambapos.com/sambapos-v5-pro/ · retrieved 2026-08-01

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

commercial-processing-not-bundled differentiator

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

commercial-interchange-plus-published differentiator

Not an acquirer, so no rate structure of any kind is published. https://sambapos.com/integrations/ · retrieved 2026-08-01

commercial-rate-increase-clause differentiator

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

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

commercial-module-unbundling differentiator

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

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

commercial-hardware-not-locked differentiator

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

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

commercial-export-customer-and-loyalty differentiator

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

commercial-post-termination-export-window differentiator

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

commercial-data-ownership-clause differentiator

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

commercial-pci-p2pe-tokenization

Grepped the full kb.sambapos.com dump (613 records, both languages) for pci, p2pe, saq, tokeniz and 'card data': zero hits. The payment-terminal articles - PaymentSense Pay At Counter 6.1 and Pay At Table 6.2, Dojo 6.14, OpenEdge 6.5, International Bancard 6.12, Global Payments 6.20, Quest 6.31, Worldline TIM 6.26, Dejavoo 6.34/6.42 - are firewall/DLL/gateway configuration walkthroughs that never name an SAQ type, a P2PE solution listing or a tokenisation scheme. The Terms of Use and Privacy Policy contain no card-security language, and the site's 66-page sitemap has no security or compliance page. Unresolved rather than 'no' because the semi-integrated architecture means scope reduction is determined by the acquirer's validated terminal (Dojo, Global Payments, Dejavoo, Worldline), and I did not retrieve the PCI SSC validated-P2PE listings for those devices in this pass.

commercial-pci-dss-4-controls

Grepped all 613 kb.sambapos.com records in both languages for pci, mfa, 'two factor', 2fa, otp and 'script integrity': nothing addresses the post-March-2025 future-dated requirements. The documented authentication surface is KB 2.2.10.b, where a user gets a minimum four-character PIN Code for the SambaPOS screen plus a Password used only 'for connections which will be making through GraphQL (Example; Android Client Users, Handy Terminals)' - no second factor is offered on either POS or back-office login, and the back office is a local Windows application rather than a hosted console. For Req 6.4.3/11.6.1, SambaPOS does not host a payment page for its own account; GO Kiosk and Jetrik payments are handed to an integrated terminal or QR wallet. Left unresolved because the claim is about the vendor documenting these controls and I found no vendor statement in either direction - the PIN/password finding is evidence about the product, not a compliance statement, and Neptune/Metrik cloud components publish no security documentation at all.

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

commercial-wcag-kiosk-accessibility differentiator

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

commercial-dual-pricing-compliant differentiator

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