Lashiro's

Decisions

1. Stock doesn't ship in the build

   Each product page is frozen at build time because it rarely changes; stock is read separately, with short revalidation. If stock shipped in the build, the site would lie between deploys, and that was exactly the problem to solve.

2. No payment gateway

   In Venezuela people pay with Pago Móvil, cash dollars, Zelle or Binance, and no gateway integrates them easily or cheaply. The site builds a numbered order and sends it through WhatsApp: no gateway, no PCI, no reconciliation and no disputes.

3. BCV dollars and bolívares

   Each price is converted once on the server at the official rate and rounded to the cent, so what the store adds up matches what the customer sees. If the rate doesn't arrive, the base currency is shown; never a hand-typed rate.

4. Built for slow mobile data

   Customers arrive from Instagram, on their phones and on poor connections. That's why there is handwritten CSS instead of a component library, fonts served from the site's own domain, AVIF images and the heavy lifting on the server.

5. Every read counts

   The project lives on Firestore's free plan, with 50,000 reads a day shared by the store, the panel and the tests. A page load costs one read per product and the whole stock just one; saving in the panel costs nothing, and there are alerts before the limit is reached.

6. Security lives in the rules

   Firestore rules are the real boundary, not the login screen: writing to the catalog is authorized against the list of admins, never against simply being signed in. Server routes check the token before anything else, and the rules have their own tests.

7. Login never comes before the cart

   You always buy as a guest. Accounts are optional, nobody signs in with their phone number without a code, and when an account is deleted its orders become anonymous.