A register can collect a payment correctly and still leave accounting with a puzzle. Stock falls in one workbook, a receipt appears in another system, and the bank deposit arrives days later after a fee. At close, someone reconstructs the sale. When evaluating a Costa Rican POS, start with that reconstruction: which records remain after checkout, and how do they connect to the Hacienda document?
Tario POS shares invoices, customers, inventory, and accounting with Tario. It is a paid add-on with its own /pos workspace. Cashiers can operate a register without browsing financial reports. The records remain connected: a settled sale affects stock and books and must retain its identity through a return or fiscal problem.
Define locations and staff access first
A location is the selling site; a terminal is a register or checkout device. Configure both and assign staff by POS role and permitted locations. A manager may supervise several branches while a cashier works at one. Test that distinction with actual user accounts before the first shift. An administrator account cannot show what a restricted cashier will experience.
POS-only staff do not consume seats in the accounting plan. People who also need the main Tario workspace require that access and its corresponding seat. This suits a business with many shifts and a small administration team. Kitchen staff should not need access to banking just to follow their orders.
Check products and stock during checkout
Select the products available in the POS and verify price, tax, code, and unit. Link the selling site to the right inventory location. Thirty units spread across warehouses do not mean every register can promise all thirty. Inspect pending payments too: a reservation protects availability while a payment is unresolved, without treating the goods as already delivered.
Include two people trying to sell the last unit in a pilot. What does the second register see after the first starts payment? An accurate closing balance is insufficient if both customers were promised the same item. Control needs to work during the transaction, especially when several terminals share stock.
Payment methods have their own controls
Depending on configuration, Tario POS supports cash, external card payments, SINPE or transfers, and hosted ONVO payment. One order can combine payments. ONVO requires the merchant's connection, separate from the card used to pay Tario's subscription. Test payment results and confirmation through the intended workflow before enabling the channel for staff.
A paid sale and an accepted Hacienda document describe separate states. If payment succeeded but the fiscal document needs correction, charging again creates a second problem. POS history preserves the sale and offers a specific correction action for a rejected document. Training should cover this case so staff recognize a fiscal exception without initiating another charge.
For restaurants, walk through a table order
POS configuration includes tables, kitchen stations, and modifier groups. Try a concrete order: two drinks, one modified dish, and a bill paid with cash and card. Follow what the server sees, what reaches the kitchen, and what ends at checkout. Permissions and handoffs matter as much as finding a product quickly.
Then test a partial return. The settled sale remains evidence; a manager records the refund, quantities, payment allocation, and whether items return to stock. A damaged return needs different handling from an item ready for resale. The system retains the trail while a responsible person determines what physically happened.
Budget and pilot
Pricing lists Tario POS from US$19 monthly plus IVA or US$180 annually plus IVA on any plan, including the free plan. It includes one location and up to three terminals; additional locations follow the published rate. POS documents have their own counter and fair-use conditions. Review current pricing before costing several branches.
Start with a known shift, a small catalog, and someone who can inspect outcomes. Compare sales, payments, stock, and fiscal documents at the end. Give each difference an owner before expanding. A useful demonstration finishes with a sale you can trace into accounting and an exception the team knows how to resolve.