Retail OS connects checkout, stock, purchasing, finance, people and customer channels in one accountable operating layer.
One source of operational truth
The operating layer
A sale changes stock. Stock changes purchasing. Payments change finance. Every action keeps its actor, location and evidence—without hiding unfinished provider work behind a green toggle.
CapabilitiesPersonal · Pro · Enterprise
From sale to finance
Uzbek · Russian · English
System map
Purpose-built workspaces share permissions, business context and the same underlying records.
Barcode checkout, mixed tender, debts, sale discounts, receipt snapshots and offline queueing.
Variants, product galleries, barcode and QR labels, batches, expiry, serials and stock movement.
Suppliers, receiving, payables, receivables, expenses and account balances in UZS.
Owner, administrator and worker access with explicit capabilities and location scope.
A draggable Kanban board, accountable tasks, rewards, events and attendance context.
Website and bot configuration with provider connections kept separate from channel content.
Separate camera counts, CompreFace identity recognition and an interactive 3D warehouse model.
Exports, operational analytics, signed events and tenant-aware API access.
Built for daily pressure
The interface keeps context across locations, workers, products and money so teams act from the same record.
Built around the merchandise
The same accountable records adapt to the decisions that matter in each category.
Size and color variants, multi-image products, returns, store-level stock and sell-through visibility.
Serials, kits, supplier receiving, warranty context, barcode labels and location-aware availability.
Rich catalogs, dimensions, purchasing, transfers, customer debt and delivery-ready order context.
Bouquet composition, perishable stock, bookings, responsible tasks, gifts and customer notifications.
Provider truth
Every integration shows whether it is live or adapter-ready. BILLZ, Shopify, Odoo, BTS, Resend and international barcode adapters activate after valid provider credentials are verified.
Integration surface
Tenant-aware endpoints, explicit permissions, signed provider events and request IDs give internal teams a stable integration boundary.
DocsPlans
Plans control real permissions, team access, integration capacity and onboarding depth.
Core POS, catalog, inventory and focused operational capacity.
Open Retail OSWorkers, custom roles, projects, customer channels, API access, analytics and connected services.
Open Retail OSAdaptation, controlled rollout, advanced security, integration engineering and dedicated operating support.
Open Retail OSClear before rollout
No. Owners define roles, permissions and location scope. Navigation and protected actions follow those assignments.
The POS can queue checksummed sale commands offline and synchronize them when the terminal reconnects. Provider payments still depend on their network.
Yes. Company branding accepts sanitized SVG, PNG, JPEG and WebP logos. Products support multiple gallery images and the POS uses the primary image.
No. OCRO labels live connections, adapters and planned work separately so a credential form is never presented as a finished workflow.
Personal covers focused owner operations. Pro adds teams, roles, projects, API and channels. Enterprise adds adaptation, rollout engineering and advanced controls.
Next operation
Sign in to the operating console or review the API documentation before connecting your business.