Umporta

We chose the room over the product grid, and the visit over the cart.

We built the site the way the showroom actually works. The idea comes first, then the houses it is built from, then rooms assembled around one chosen piece, and only then an invitation to come in.

1. 01

   Structure discovery around finished rooms, not a conventional product grid.

2. 02

   Make showroom visits and measurement calls the primary paths instead of forcing a cart.

3. 03

   Build the consultant tool as an iPad app that keeps working without a network.

4. 04

   Keep private prices out of public code, so they cannot reach the site.

We closed the places where a sale could quietly break.

One product serves two opposite environments: a public brand site and a private, offline-first showroom system for consultants.

Surfaces

Public website and private consultant iPad PWA

Core

Next.js, strict TypeScript, Supabase and one validated catalogue model

Resilience

Custom service worker, local visit state and a reconnecting outbox

• The showroom keeps working offline

  The catalogue is cached, an active client visit survives a reload, and outgoing actions wait locally until the connection returns.

• The server owns every sale

  The server recalculates totals, an administrator confirms the order, stock follows the confirmed state, and repeated submissions cannot create a second sale.

• Prices cross an explicit firewall

  Public code does not import private pricing. A consultant controls whether a client artefact includes prices, and the server validates that choice again.

• Catalogue data stays canonical

  The source catalogue remains read-only. Idempotent sync steps create application assets, mirror imagery and validate the resulting model before it ships.

1. 01

   An order does not drift with the exchange rate

   Every sale stores its amount in dollars and in sum. The rate is written into the order when it is drawn up. The total in soʻm (UZS) is computed from that rate alone, at confirmation and at every later change to the order. Each payment carries its own recorded rate and is converted to dollars at that rate.

   Tomorrow’s rate cannot change yesterday’s order.

2. 02

   The soʻm rate comes from three sources

   The system takes the official rate of the Central Bank of Uzbekistan; if that fails, a free exchange-rate service; after that, the rate set in the system’s settings. An administrator’s manual rate outranks all three. A rate outside 8,000–25,000 sum per dollar is discarded as a fault.

   A rate of 1 sum to the dollar from a failing service never reaches a client.

3. 03

   The storage changed while the showroom kept working

   The new database was installed alongside the old files but kept switched off, so the showroom’s work did not change.

   The storage changed; every sale kept its number.

4. 04

   A catalogue from unreadable PDFs

   The catalogue was assembled from supplier PDFs whose text could not be read, so the pages were parsed from the image. When it was assembled it held 234 records; 144 had their names checked against the Orix and Yılka websites. Doubtful records are marked and go for review. The first rule is to invent nothing. An empty, marked field is better than a guess.

   Where the source is silent, the catalogue shows a marked empty field, not a guess.

5. 05

   A new field cannot go missing

   An automated check reads the code and requires each of the 24 fields that one database update added to a sale to be named in all five places: write, update, read, export and format validation. A second check creates a separate empty database for the run, fills it with records in the old format, applies the change and confirms nothing was lost.

   A field added to a sale cannot vanish silently on write or export, and old records survive the move.

7 database migrations · 10 tables · 34 pages · 13 server routes · 158 commits. Counted by us from the repository on 26 September 2026.