Your store, inventory, and customers. One system.

From storefront to back office, orders, inventory, customers and support share the same records.

Sample merchant workspace

Almacén Rambla

Sample data

Orders

Recent orders at Almacén Rambla. Sample data.
OrderCustomerDateStatusTotal

Pick an order with a click, with Enter or with the arrow keys.

Almacén Rambla is a fictional merchant and all of its data is sample data. Its catalog and its customers’ messages are in Spanish, the store’s language.

One order, from storefront to finance

A sample order: RU-10482 from Lucía Fernández at Almacén Rambla, a fictional store, step by step. Every stage works on the same record, so nobody re-enters it in another app or reconciles spreadsheets.

Hover, focus or tap a marked value to see which other steps it appears in.

  1. Storefront

    Lucía buys from Almacén Rambla’s online store.

    Product
    Yerba mate orgánica 1 kg
    Price
    $ 389

    Implemented and verified (RUNI UY)

  2. Order

    The order arrives with payment already approved and lands in the admin’s order list.

    Order
    Customer
    Payment
    Mercado Pago, approved

    Implemented and verified (RUNI UY)

  3. Inventory

    Stock drops at the shipping warehouse at the same moment.

    SKU
    Depósito Central
    12 11

    Implemented and verified (data model)

  4. Customer

    Lucía’s record adds the order, and her support question stays attached to that same order.

    Customer
    Case S-2201
    ¿Puedo cambiar la dirección de entrega?

    Implemented and verified (RUNI UY)

  5. Fulfillment

    It is packed and shipped. The new status shows on the order and on the customer’s record.

    Order
    Status
    Packing, then Shipped

    Implemented and verified (RUNI UY), no carrier integration

  6. Finance

    Order margin and payment reconciliation, read per merchant.

    Order
    Margin
    Not yet

    Planned

Designed for more than one language and currency

Today RUNI UY sells in Uruguay, in Spanish and in Uruguayan pesos. Underneath, the foundation already stores exact amounts in any currency and already handles right-to-left text on test stores.

Pick a market and watch the language, price, delivery date and address format change on the same product page.

  • Exact amounts: Implemented and verified
  • Semantic localization: In development
  • Selling in other markets: Planned
Choose a market for the preview
Almacén Ramblaes-UY · UYUSample data
1 kg

AlmacénYerba y mate

Yerba mate orgánica 1 kg

$ 389 IVA incluido

Agregar al carrito

Llega el

Enviar a

Lucía FernándezRambla República de México 5500, apto. 30211400 MontevideoUruguay
Several stores per merchant: Planned
Preview of a product page from Almacén Rambla, a fictional merchant with sample data.

How each amount is stored

Every amount is stored as an integer in its currency’s minor unit and read with the ISO 4217 exponent. The same integer means different things in different currencies, and the engine never rounds by guesswork.

Technical example: the integer 12500 read in three currencies.
CurrencyExponentEqualsShown (es-UY)
CLP Chilean peso012,500 pesos, no decimalsCLP 12.500
UYU Uruguayan peso2125.00 pesos; RUNI UY shows them without decimals$ 125
KWD Kuwaiti dinar312 dinars and 500 filsKWD 12,500
How each text is translated

Each store speaks the way its market does: text adapts to what the shopper wants to do instead of copying the Spanish sentence. A missing translation stays visible and is never silently filled with another variant.

Store texts in three variants. Sample data.
Intentes-UYpt-BRen-US
Shipping costCosto de envíoFreteLiteral rejected: Custo de envioShipping
Track the orderSeguir mi pedidoRastrear pedidoLiteral rejected: Seguir meu pedidoTrack order
In-store pickupRetirar en el localMissing pt-BR translation. It is not filled with es-UY.Pick up in store

What works today

Every claim on this page uses one of these five statuses, taken from the release ledger as of 25 October 2026. When something is verified only with RUNI UY, the row says so.

Implemented and verified
In production, with its verification recorded.
Approved but not released
Integrated and accepted; waiting for its release approval.
In development
Being built now.
Planned
On the roadmap, not built.
Open decision
A product decision is still pending.
Status of each RUNI OS capability, grouped by status
CapabilityScope and limits
Implemented and verified 11
Multi-merchant foundation: merchants, memberships and rolesVerified with one merchant in production, RUNI UY. A second merchant was tested only in a test environment.
Online store, catalog and checkoutRUNI UY. The theme engine has one design family; others are planned.
Orders, payments, returns and shipmentsRUNI UY, with Mercado Pago and PayPal. No carrier integration. Per-merchant payment accounts: planned.
Inventory: warehouses and stock ledgerVerified in the data model. The locations screen and transfers are planned.
Customer support casesRUNI UY. Membership-based support is planned.
Purchasing and stock costRUNI UY. Purchase orders and cost basis; per merchant: planned.
Subscriptions and recurring ordersRUNI UY. The per-merchant version is planned.
Pages, navigation and SEORUNI UY. Generic blocks, templates and articles: planned.
Transactional email; campaigns in test modeRUNI UY. Transactional email is live; marketing email runs only in test mode.
Exact amounts for every ISO 4217 exponentShowing and selling in currencies other than the Uruguayan peso is still planned.
Arabic and right-to-left textTest stores only. Not a market launch.
Approved but not released 0
Nothing in this status as of the ledger date.
In development 1
Semantic localization workflowTranslation by intent, with missing translations kept visible.
Planned 6
Several stores per merchant and custom domainsEach store with its own currency and language. It needs its own approval before work starts.
Invitations and teams in the adminRoles owned by each merchant.
Finance, analytics and BI per merchantRUNI UY has partial readers that do not separate merchants yet.
B2B: company accounts, price lists and quotesOptional module. Not started.
AI-assisted operationsSpecified, not built. There are no AI agents in production.
RUNI’s internal operations consoleMerchant onboarding, support access and audit.
Open decision 2
Distribution centres as a location typeNot modelled. It would be decided alongside the multi-location work.
Branches within a company accountTo be defined within the B2B module.

A real store already runs on it

RUNI UY (runiuy.com), a Uruguayan pet supplies store, is the first to operate on RUNI OS in production. Catalog, payments, orders, shipments and support live in the same system.

The multi-merchant foundation is verified with that single merchant. A second merchant was tested in a test environment, and there is no other one in production yet.

That is why every pilot will start with someone from RUNI beside you.

Implemented and verified at RUNI UY

  • Online store, catalog and checkout
  • Payments with Mercado Pago and PayPal
  • Orders, returns and shipments no carrier integration
  • Customer support cases
  • Subscriptions and recurring orders
  • Pages, navigation and SEO
  • Transactional email marketing email runs in test mode only

Source: the capability ledger on this page.

Assisted pilot, not open yet

Once it opens, someone from RUNI will set up the store with you and stay with you from day one.

Pilot terms are not defined yet; we discuss them with each merchant. RUNI OS operates in Uruguay today, and if your business is in another country we still want to hear about it.

What you sell, where, and what you use today. At least 20 characters.

This form does not send data yet.