Point of sale, kitchen, online ordering, reservations, inventory, time clock and reporting share one catalog and sales lifecycle. Delivery, integrated payments and electronic invoicing are activated only after the required setup and validation.
These aren't prettier charts. They require recipes, stock, labor and sales to live in one system — which is precisely why a POS stitched together from integrations cannot produce them.
Real profit per item, computed from the recipe's plate cost — not a guessed markup. You learn which dishes make money and which quietly lose it.
The number a restaurant lives or dies by, live — because the time clock and the recipes are the same system. With labor %, sales per labor hour and profit per labor hour.
What your recipes say the sales should have consumed, against what the stock ledger actually removed. The gap is over-portioning, waste or theft — priced in colones.
Status labels show what is available today, what requires setup and what remains in pilot. Active modules share catalog, pricing, tax and operational history.
Fast counter selling with parked tickets, split & merged bills, tips, partial payments, refunds and a quick-menu.
Lay out your room — tables, bar, patio, stations. Every table shows the open bill sitting on it.
Tickets, prep timers, kitchen states and events tied to the same order lifecycle.
The payment, tip and CRC total session is implemented; each installation needs a cross-device test before service.
Web ordering for pickup or delivery, with a per-store link and public order-status tracking.
Job control, offers and delivery states are implemented. Background GPS, proof of delivery, offline driver commands and field release remain in validation.
A public page per store, table assignment, waitlist and configurable reminders.
Recipes, plate cost, stock, par levels, purchasing, suppliers and movement records connected to canonical sales.
Sales, product mix, payments, labor, prime cost, cash, shrinkage and accountability from canonical data. The custom builder remains beta.
CRC drawer count, expected versus counted and over/short. Printing the report requires validating the store's printer.
ESC/POS support through a compatible local bridge or network path. Logo, drawer, cut and connection must be tested on the target hardware.
PIN clock-in, consent-based identity photos, breaks, worked hours and manager timesheets.
Your PIN identifies you at the terminal. Voids and refunds require a manager PIN and an auditable reason.
The v4.4, CABYS, fiscal-data and signing foundation is implemented. Production issuance requires a certificate, complete fiscal catalog and activation validation.
Cash is available. Card, SINPE Móvil and crypto are shown only after provider credentials, confirmation and reconciliation are configured.
Role-based controls, plans with feature flags, a per-store Admin Console and an audit log. Platform plans are managed from Super Admin.
The unauthorized void and the buddy-punch are the two most common leaks in a restaurant. Both are closed by default.
Voiding or refunding requires a manager's PIN and a reason. Who approved it, who was on the terminal and why — all recorded. Refused attempts are logged too.
One low-res photo at PIN entry — in, out and both ends of every break, so nobody clocks in a colleague. With employee consent and automatic deletion after 60 days (Ley 8968).
If more product leaves than the recipes explain, it shows up on a report with a colón figure attached — before it becomes a habit.
We publish the operational state of each feature group so you can plan a realistic rollout.
| Capability | Status | Operational boundary |
|---|---|---|
| Cashier, tables & kitchen | available | Orders, tickets, approvals and kitchen events share the operational lifecycle. |
| Online orders, reservations & public tracking | available | Public tracking shows online-order status; it is not yet a live driver GPS map. |
| Catalog, inventory, reports & time clock | available | Canonical per-store data; consolidated multi-location reporting remains pending. |
| Customer Display & custom report builder | beta | Require workflow and store-device validation before service. |
| ESC/POS printing | setup required | Connection, logo, cut and drawer behavior must be validated on target hardware. |
| Factura Electrónica v4.4 | setup required | Requires a certificate, complete fiscal data and activation validation. |
| Card, SINPE Móvil & crypto | setup required | Each provider requires credentials, confirmation and reconciliation tests. |
| Field delivery operations | pilot | Background GPS, proof of delivery and offline commands remain pending field release. |
| Full offline selling | coming soon | Sync recovery and retry exist, but fully offline operation is not certified. |
| WhatsApp, AI import & multi-location roll-up | coming soon | Depend on external approvals or remaining product work. |
Pura Vida POS is CRC-first and models Costa Rican requirements. Regulated integrations are enabled only after each store is configured and validated.
v4.4, CABYS, fiscal-data and signing foundation; production issuance requires a certificate and activation validation.
Configure SINPE as a payment method; automated confirmation requires an activated and reconciled provider.
Work natively in CRC; offer optional USD conversion at the end of a customer's bill.
The public site and core operational flows support English and Spanish; administrative copy coverage continues to expand.
Plans and limits published from the same live configuration used by the platform.
Included in a plan means the module is entitled at that tier. Features marked beta, pilot or setup required keep those boundaries before operation.
Options that are available, in pilot or planned for a later stage. Activation depends on the plan and stated status.
The status page is available; live driver map and ETA remain in validation.
Branches, shared catalog and consolidated reporting remain in development.
Integrate approved tools after scope, credentials and validation are defined.
Canonical reports are available; the custom builder remains beta.
Enabled only after capture, confirmation and reconciliation are configured and tested.
WhatsApp ordering depends on provider approval and configuration.
Photo import with human review before publishing; not yet available.
Token-driven themes and per-screen branding assets.
Raise the plan quota; issuing documents first requires electronic-invoice activation.
Pick a plan and set up your store, currency and language.
Import your catalog, pricing, tax and recipes — once.
Test POS, kitchen, ordering and each device; enable integrations only after setup.
Sell with enabled methods, then add invoicing, payments or delivery after validation.
Something else? Write us and we answer the same day.
No — it is free forever. Perfect for trying the system with real sales: 1 owner, 1 PIN staff member, 1 device, 100 transactions and 25 electronic invoices a month. When the business grows you change plans and lose nothing: your data, menu and reports stay intact.
Not to use the cashier with enabled methods. Issuing electronic documents requires the .p12 certificate, complete fiscal data and activation validation.
The system works in colones as the base currency — the way Hacienda expects — and shows a USD conversion at the end of the bill if you turn it on, at the exchange rate you configure.
The platform supports compatible ESC/POS paths through a local bridge or network. Before service, we validate the model, connection, logo, cut and drawer behavior on your hardware.
Confirmed sales have sync recovery and retry. Fully offline operation is not yet certified; card, SINPE, crypto and electronic invoicing require connectivity.
Not yet as a production ordering channel. Activation depends on provider approval and configuration; customers can use the public online-ordering link in the meantime.
Your data travels encrypted and is backed up automatically every night, with every backup verified. Time-clock photos are deleted after 60 days per Ley 8968.
Any time, no contract, no penalty. You can export your reports before you go — your data is yours.
Or start free today — no card, no contract, no fine print.
Request a demo by email and we will review available modules, hardware requirements and integrations that need setup.
