Most POS comparisons expire when the first merchant asks for a workflow the vendor did not plan. A feature grid describes what exists today. The more durable question is who can decide what exists next: the merchant, an integration partner, a white-label vendor, the source owner, or a commissioned product team.
Tillo is an offline-capable point-of-sale and store-operations SaaS sold once as source code. You deploy it under your own brand and operate it for small physical merchants. Its verified scope joins barcode checkout with durable sales, cash shifts, stock ledgers, suppliers, purchasing, customers, promotions, reports, and multiple locations. This guide compares control paths across the retail POS category.
The category has two buyers
A physical merchant looking for a register is not making the same purchase as an operator looking for a platform business. The merchant needs software, payments, devices, support, and a reliable vendor now. The operator needs a product acquisition strategy: rent a white-label service, buy source code, commission a build, or accept that a merchant-focused platform's integration layer is enough.
This guide keeps those buyers separate. Square, Shopify POS, Lightspeed Retail, and Loyverse are credible answers for merchants running their own stores. Their public pricing proves that the category is active and shows how vendors package it. Rhombus offers a closer operator-level white-label route. Tillo offers source ownership. A custom build offers a blank sheet. The products should not be flattened into one “cheapest POS” ranking.
The ordering variable is who absorbs the next change. If a merchant needs a new tax rule, device, stock workflow, local payment method, supplier exchange, or reporting shape, one of five things happens: the vendor ships it, an integration covers it, a partner contract permits it, the source owner builds it, or a commissioned team delivers it. That ownership boundary matters longer than a feature count.
| Change owner | Products / route | What the operator controls | What remains outside the operator's control |
|---|---|---|---|
| Hosted vendor roadmap | Square, Shopify POS, Lightspeed Retail, Loyverse | Merchant setup, configuration, available extensions | Core product, release priority, commercial terms, service continuity |
| Integration layer | Shopify, Lightspeed, Square developer ecosystems | Connected workflows that published APIs permit | Core behavior and the platform boundaries around the integration |
| White-label vendor | Rhombus partner route | Brand and merchant relationship within the partner agreement | Underlying source, release channel, partner pricing, termination terms |
| Source owner | Tillo | Product code, brand, deployment, priorities, merchant offer | Work required for every unsubstantiated integration and operating surface |
| Commissioned team | Custom build | Product definition and implementation contract | Delivery capability, schedule, budget, maintenance continuity |
Vendor roadmap: the correct answer for many merchants
Hosted retail POS products are often the best answer for the store owner because the vendor has already assembled payments, devices, operations, and support. That does not make them platform acquisitions. It makes them services with a mature responsibility boundary. An operator evaluating a POS business should study them as market evidence and as standards merchants will expect, while avoiding the fiction that a subscription account transfers product ownership.
Square POS — the category reference
Square's public surface is broader than a register. It publishes point of sale, payments, inventory, staff tools, websites, hardware, APIs, an app marketplace, support, and adjacent services. Its official US pricing page shows $0–$149 per month per location as of 2026-09-01, plus card-present processing of 2.4%–2.6% + 15¢ depending on plan (Square POS pricing).
Square is a strong answer for a small merchant that wants to start with a vendor-run account, known payment acceptance, device options, and a support operation. It is also the clearest market anchor for an operator studying what small merchants already understand as “POS.”
The boundary is ownership. Square does not sell its source code through that pricing page, and the operator cannot turn a Square merchant account into an independently directed POS product. Square's APIs and marketplace create extension room, but the core remains Square's. Tillo's source-code route gives the operator product control; Tillo's current facts do not substantiate Square's payments, hardware, API ecosystem, website tools, app marketplace, or support. A buyer who needs those on day one should credit Square rather than imply parity.
Shopify POS — when online commerce owns the roadmap
Shopify POS is part of a larger commerce platform. The official page publishes online and in-person selling, multi-location operations, integrated payments, hardware, inventory, staff management, customer profiles, reporting, and omnichannel workflows. Its base plans run $39–$2,300 per month as of 2026-09-01, while POS Pro is published at an additional $89 per month per location on the standard plans (Shopify POS pricing).
Shopify POS is the honest choice for a merchant whose physical store and Shopify online store must share one commerce system. The vendor already owns the difficult seam between channels, and its app ecosystem provides extension paths. An operator can build around that ecosystem, but does not acquire Shopify's POS as a standalone codebase.
Tillo's verified scope includes small physical merchants, checkout, store operations, and multiple locations. It does not substantiate ecommerce, omnichannel orders, Shopify integration, integrated payments, hardware, apps, shipping, or the geographic availability of payment services. The source-code transaction gives Tillo's buyer control over future development, not evidence that the current product replaces Shopify's wider commerce surface.
Lightspeed Retail — when retail depth is vendor-managed
Lightspeed's X-Series pricing page publishes integrated payments, inventory management, ecommerce, loyalty, advanced reports, accounting and marketing integrations, mobile scanning, landed costs, forecasting, API access, workflows, roles, SSO, hardware, and support. Basic, Core, and Plus span $89–$289 per month as of 2026-09-01, with one register included; the company says extra locations, registers, and service fees can vary (Lightspeed Retail pricing).
Lightspeed is a credible answer for a retailer that wants a vendor to carry a deep inventory and commerce product, especially when the public integration and support surface matters. It gives an operator a useful benchmark for the operational expectations of inventory-heavy merchants.
The counterweight is the same boundary in a more specialized package. Lightspeed's API permits customization around the platform, but the buyer still rents the core product and accepts its commercial and release decisions. Tillo gives source control over its own store-operations product, while its current verified facts do not establish Lightspeed's payments, ecommerce, loyalty, forecasting, integrations, roles, SSO, hardware, or 24/7 support. Retail depth should be verified capability by capability, not inferred from the shared category label.
Loyverse — the free objection is legitimate
Loyverse publishes a free merchant POS with free sales analytics for the recent period, essential inventory, loyalty, customer display, kitchen display, multi-store management, and integrations. Optional software add-ons run $5–$25 per month per store, for a combined public software range of $0–$55 per month per store as of 2026-09-01. Its US page also publishes payments at 2.6% + 15¢ and optional hardware from $59–$269 (Loyverse pricing).
That is not a decoy free tier. It is a genuine merchant answer. A small store that wants a low-friction POS account should test Loyverse before considering the responsibility of source-code ownership. Its free and optional-add-on model also gives an operator real evidence of how hard it can be to charge merchants merely for basic checkout and inventory.
Loyverse's limitation for this buyer is not that Tillo is “cheaper.” The limitation is that a Loyverse account does not transfer the product roadmap or source code. Conversely, Tillo's verified facts do not substantiate Loyverse payments, displays, loyalty program, integrations, hardware, or managed support. Tillo is relevant only when operating and changing the product is the business, not when the buyer simply needs a register.
Integration control: powerful inside a vendor's boundary
Square, Shopify, and Lightspeed all publish developer or integration surfaces. That route can be the most efficient response to a merchant workflow: leave the vendor-owned checkout and payment system in place, then add the missing reporting, inventory, ecommerce, or operational connection around it.
An integration is not a failed form of ownership. It can avoid payment certification, device compatibility, release management, and support work that would otherwise move to the operator. It is especially attractive when the differentiator lives outside the transaction core and the platform already exposes the required data and events.
The boundary appears when the required change sits inside the core or outside the API contract. The operator cannot promise a workflow the vendor does not expose, cannot control when platform behavior changes, and cannot make the merchant relationship independent of the host product. Tillo reverses that boundary by making the product code the acquisition. The trade is that every vendor-carried obligation must be supplied, integrated, or consciously excluded by the Tillo operator.
White-label vendor: Rhombus
Rhombus publishes a partner path for payment companies, merchant service providers, POS resellers, and technology integrators. Its site describes branded POS deployment, processor and hardware choice, iOS/Android/Windows support, offline operation, retail and restaurant workflows, and 24/7 support. Merchant plans span $49–$289+ per month as of 2026-09-01, with optional add-ons from $5–$25 per month; Enterprise lists white-label options (Rhombus POS).
This is the closest live alternative in the set for an operator who wants a POS brand. Rhombus can carry device, processor, maintenance, support, and release work while the partner focuses on merchant acquisition and relationships. That vendor-carried responsibility is a real advantage over a source-code purchase.
The public page does not disclose the complete partner price schedule, minimum commitment, merchant-data terms, termination behavior, or source-code rights. Those are not minor details; they define whether the partner owns a durable business or rents a branded channel. Rhombus should win when those contract terms are acceptable and vendor operations are more valuable than code control.
Tillo wins a different argument. The buyer receives the product source and can direct changes without a partner roadmap. Tillo's facts do not establish Rhombus's device breadth, processor choice, restaurant support, partner tooling, or managed support. A Tillo buyer must value source control enough to carry those gaps.
Source owner: Tillo
Tillo is the option in this set where the product transaction is the source code. Its verified definition is specific: offline-capable POS and store operations for small physical merchants, with barcode checkout, durable sales, cash shifts, stock ledgers, suppliers, purchasing, customers, promotions, reports, and multiple locations. The operator deploys it under a separate brand and runs the SaaS for merchant customers.
That scope is more substantial than a blank SaaS starter and narrower than the ecosystems published by Square, Shopify, Lightspeed, Loyverse, or Rhombus. The useful comparison is not feature count. It is whether Tillo's connected retail loop is the correct base for the intended merchant offer, and whether the operator can supply every critical surface the current facts do not substantiate.
Those open surfaces include payment processing, hardware compatibility, receipts, ecommerce, APIs, apps, tax and fiscal compliance, integrations, deployment, native applications, support, security evidence, and the exact mechanics of offline operation. The absence of a fact does not prove the product can never support it. It means the page cannot sell it as present. The operator must verify, build, or exclude it.
Tillo's catalog price resolves from $149 and its checkout from https://saascode.ai/products/tillo. The demo is the appropriate diligence surface before either.
Commissioned team: the blank-sheet route
A custom build makes the operator the owner of the product definition from the first day. It fits when a distinctive payment arrangement, regulated workflow, device estate, fiscal regime, inventory model, or merchant segment is the business itself and adapting an existing product would preserve the wrong assumptions.
It also means the starting point has none of the retail loop. Checkout, sales durability, shifts, stock history, suppliers, purchasing, customers, promotions, reports, locations, offline behavior, integrations, security, deployment, and support all have to be specified and delivered. No scoped first-party quote was available in this research, so a cost range would be fabricated. The custom route should be evaluated through a real brief and real bids.
How an operator should choose
Start with the buyer level. If the business is a physical merchant needing software, the hosted vendors deserve the first evaluation. Square offers the strongest general category reference; Shopify POS deserves priority when online commerce is already central; Lightspeed deserves priority when published retail depth and vendor support are central; Loyverse deserves priority when a genuine free merchant product is sufficient. Tillo adds the wrong responsibility to that purchase.
If the business is becoming a POS operator, write down which forms of control are essential. Brand control may be enough. Merchant ownership and payment economics may be enough. An integration may protect the differentiated workflow without replacing the POS. Source control may be essential because the product itself must change. A custom build may be essential because no existing product shares the market assumptions.
Then price the responsibility, not only the invoice. A hosted vendor carries the product and narrows control. A white-label vendor carries more operations but introduces partner-contract dependency. Tillo transfers product control and product responsibility together. A custom build adds delivery risk before the product exists. Those are the durable differences an operator can use after every public price page changes.
Finally, make every missing Tillo fact a diligence item. Confirm the offline action set. Confirm payments and devices. Confirm fiscal requirements in the target geography. Confirm deployment, maintenance, support, and merchant onboarding. Confirm which merchant workflow makes the product worth owning. Source code is the beginning of that evaluation, not the end.
Questions about the retail POS landscape
What is the best POS for a small physical merchant in 2026?
The best merchant service depends on the store's operating shape. Square is the broad general reference; Shopify POS is strong when online and physical commerce must share a platform; Lightspeed publishes deeper retail operations; Loyverse offers a genuine free starting point. Tillo is not a merchant subscription recommendation. Tillo is source code for an operator building a POS SaaS business and carrying the associated product responsibility.
Which POS is strongest for online and in-store commerce?
Shopify POS publishes the clearest integrated online-commerce story in this set, with omnichannel workflows, payments, hardware, apps, and centralized operations. Tillo's verified facts establish physical-store POS and store operations but do not substantiate ecommerce or omnichannel selling. An operator should not claim Tillo replaces Shopify's commerce ecosystem unless those missing surfaces are independently verified and delivered.
Which option publishes the deepest retail inventory surface?
Lightspeed publicly describes inventory management, purchasing connections, landed costs, forecasting, mobile scanning, reports, integrations, and API access. Tillo publishes a grounded but narrower product scope: stock ledgers, suppliers, purchasing, sales, reports, and locations. Tillo gives its buyer source control; it does not inherit Lightspeed's broader published capabilities merely because both products serve retail.
What is the difference between white-label POS and Tillo?
A white-label POS such as Rhombus can let an operator present a branded service while the vendor continues to maintain the underlying platform, device support, and operations. Tillo transfers source control instead. The Tillo buyer can direct the product but must supply or verify payments, hardware, integrations, deployment, compliance, and support that a vendor-managed arrangement may include.
Is Tillo open-source POS software?
The verified catalog facts describe Tillo as a source-code SaaS product; they do not describe it as open source or name an open-source licence. Tillo should therefore be called commercial source code, not open source. Its relevance is that an operator acquires code to customize, deploy, and run a POS SaaS. Redistribution rights must not be inferred from source access.
Which path gives a POS operator the most control?
A commissioned build gives the operator the most control over the initial definition, with the greatest delivery burden. Tillo gives direct control over an existing source-code product whose retail scope is already defined. Rhombus gives brand and partner control within a vendor relationship. Square, Shopify, Lightspeed, and Loyverse give merchant configuration and integrations, not ownership of the core POS product.