A single-counter business rarely needs the widest POS feature set. It needs a register that the owner and occasional staff can operate, reconcile, and recover without becoming a second job. Square, PayPal Zettle, and Helcim offer different paths, so simplicity should be measured across the whole merchant workflow.

Buyer constraint: there is no backup operations team

Picture an owner-run shop with one checkout position, a short catalog, cash and card sales, returns, emailed receipts, and bookkeeping handled after closing. If the reader fails or the account needs attention, the person serving customers is also responsible for diagnosis and support.

Square fits the hypothesis of an integrated small-business ecosystem. PayPal Zettle deserves review for straightforward PayPal-connected selling. Helcim belongs where the owner wants to evaluate payment economics and POS operations together. None should be selected merely because initial setup looks short.

Decision criteria for a deliberately small stack

Inspect item setup, taxes as merchant-configured fields, discounts, returns, cash recording, employee access, receipt options, reader and printer ownership, network behavior, payment status, settlement reporting, exports, support, replacement steps, contract terms, and cancellation. Separate essential checkout from add-ons that create another workflow to maintain.

Payment features do not prove PCI DSS compliance. Use PCI Security Standards Council merchant guidance to identify responsibilities for the device, network, provider relationship, staff practices, and applicable validation.

Reproducible mini-check at opening and close

Using fictional items and an approved test environment, open the register, sell a mixed basket, apply a discount, correct an item, record cash, issue a partial refund, resend a receipt, and hand the device to a second role. Disconnect one peripheral and follow the documented recovery path.

At close, compare orders, payment states, cash activity, refunds, and the finance export. Then locate the support identifier and data-export path without relying on setup notes. POS Platform Guide has not performed this configured test.

Exception and verdict: the only device becomes unavailable

Suppose the registered device is lost or unusable before opening. The owner should know how access is revoked, whether a replacement can be activated, what records remain available, and what approved fallback keeps the business honest with customers.

Choose Square for ecosystem simplicity, PayPal Zettle for a lean PayPal-connected flow, or Helcim when its combined payment and POS model fits. Reject any option whose recovery requires knowledge held only by an installer or reseller.

Traceable evidence

Sources for this decision

4 sources
  1. vendorSquare official product siteSquare · checked Aug 5, 2026 · supports: Vendor-published product scope used to verify capabilities relevant to this buyer context: Small merchants evaluating an integrated POS, payment, hardware, and business-software ecosystem. It does not prove the guide's fit verdict, configured performance, current pricing or compliance.
    Open source ↗
  2. vendorPayPal Zettle official product sitePayPal Zettle · checked Aug 5, 2026 · supports: Vendor-published product scope used to verify capabilities relevant to this buyer context: Small and mobile sellers evaluating a straightforward PayPal-connected in-person checkout. It does not prove the guide's fit verdict, configured performance, current pricing or compliance.
    Open source ↗
  3. vendorHelcim official product siteHelcim · checked Aug 5, 2026 · supports: Vendor-published product scope used to verify capabilities relevant to this buyer context: US and Canadian merchants evaluating payments and POS economics together. It does not prove the guide's fit verdict, configured performance, current pricing or compliance.
    Open source ↗
  4. standardsPCI SSC Merchant ResourcesPCI Security Standards Council · checked Aug 5, 2026 · supports: PCI SSC merchant guidance for identifying validation responsibilities and SAQ starting points; it does not determine the validation path without the merchant's acquiring bank and actual environment.
    Open source ↗