The Olmira changelog
Olmira ships in small, dated releases, and this page is the record: what you can newly do, month by month, described the way it works today. It is also the fastest way to gauge how quickly the product is growing.
August 2026 — Editing where the page actually is
The canvas stopped being read-only for anything that repeats. Click a card, gallery image, review, pricing row or table row and a toolbar adds, duplicates, moves or deletes it right there — no hunting for the matching row in a settings panel. Repeatable blocks that insert empty now seed a first item from the template's own example copy instead of leaving a blank box to decode. Also fixed: preview opened a host that didn't exist, and section backgrounds were dropped on save.
August 2026 — Subscriptions handled by a merchant of record
Billing moved to Dodo Payments as our merchant of record: Dodo sells you the subscription, charges your payment method, issues your invoice and accounts for the VAT or sales tax due on it, while Olmira supplies the service and stays the party every billing question starts with. Sales through your own storefront are separate — there you are the seller of record, on your own payment account, and Olmira never touches the money. The 30-day free trial needs no card, and the refund policy is written in plain language.
August 2026 — The companion app
The Android companion app went into real device testing: notifications, orders, chat, analytics, bookings and settings, on actual phones. iOS is in development and not available yet. Where the app stands.
Late July 2026 — Jobs & Integrations
API tokens for your own scripts, CSV import for products, services, bookable resources and customer lists, scheduled pulls from systems you already run, and signed outbound webhooks across roughly twenty commerce and booking events. One field-mapping engine with a dedupe key sits behind every inbound connector, so re-running the same file updates records instead of duplicating them. See Integrations and importing your existing data.
Late July 2026 — The back office
Management shipped: expenses with a receipt-and-approval flow, a Balance view that computes profit as revenue minus cost of goods minus expenses, multi-location inventory with purchase orders, and invoices with EU e-invoice (EN 16931 / UBL 2.1) export next to a real payments ledger. The part most small businesses still run in a spreadsheet, now in the same product as the storefront that feeds it.
Mid-July 2026 — Selling, six ways
One catalogue learned to sell products, services, subscriptions, appointments, reservations and custom orders. Bookings gained real resources — staff, rooms, equipment with their own capacity, so the engine knows when Tuesday is actually full — and payment at the moment of booking, settled through your connected Stripe account, the one gateway booking payments run on.
Mid-July 2026 — Bringing customers back
Every checkout, booking or newsletter signup now lands in the same customer record. Segments filter on real activity; live chat answers routine questions from your own knowledge base before handing over to a human; review feeds from Google, Trustpilot, TripAdvisor and Facebook pull your real rating onto your own pages. Marketing & CRM.
July 2026 — Eight languages
English, Spanish, Latin-American Spanish, French, German, Portuguese, Russian and Ukrainian — the platform, published sites and AI translation, all of them. Your plan sets how many site languages you can switch on (every plan gets at least two), and switching one on makes the whole site — pages, menus, forms — editable in it.
June 2026 — The builder grows up
The foundations landed: a full section library, theme presets built on shared design tokens, and an in-app media editor for crop, rotate and text. Most of what you see on this site was built with that toolset; the canvas editing above came later, on top of it.
What's next
We publish shipped work, not dated promises: when a capability lands, it appears here — including the parts that are still partial, labelled as such. Want something specific? Tell us — every request is read by the people who build the product.
See it, not just read about it
Every feature, one page
Pricing
In small, dated releases rather than one big annual launch. Not everything that ships is changelog-worthy — this page tracks the milestones that change what you can actually do, not every internal fix.
A small, independent team — the same people who build the product run it and answer support. About Olmira covers how it is made and run.
No. When something is retired, it is announced on this page rather than quietly disappearing.
Contact us directly. There's no public voting board today; every request reaches a real person on the team.
No — it's for capability changes: what you can newly do, not every fix along the way. That keeps it readable instead of a raw commit log.