Where Timma's features stand. If you support customers or sell Timma, this page should answer "can my customer use this yet, and where?" without asking anyone.
For what changed in a given week, see Release notes.
Feature status
Feature | Status | Who can use it | When | Ticket |
|---|---|---|---|---|
Tap to Pay on iPhone | RELEASED | Any salon in Finland. Closed beta in Norway and Sweden — we add the salons. | Released Aug 2026 | |
Kletta accounting integration | RELEASED | Any salon in Finland. 10 €/month per business ID, first month free. | Released Aug 2026 | |
Series cards | RELEASED | Any salon, in every market. Existing customers were migrated across. | Released Aug 2026 | |
Refreshed marketing site | RELEASED | Public website, live in every market. | Released Aug 2026 | |
Prepayment for specific services | RELEASED | Any salon, in every market. Needs Timma Pay prepayment switched on. | Released Sep 2026 | |
Blocking clients | RELEASED | Any salon, in every market. Needs the new online booking. | Released Sep 2026 | |
Online booking, new version | OPEN BETA | New salons get it automatically. Existing salons can switch it on themselves. | — | |
Pay by link | PILOT | A named list of salons in Finland, Norway and Sweden. Covers MobilePay, Vipps and Swish. | — | |
New gift card shop | PILOT | Will require Adyen. | — | |
PowerOffice GO accounting integration | IN DEVELOPMENT | Will be for Norway. | — | |
Genie AI analyst for salons | IN DEVELOPMENT | — | — | |
Online booking email improvements | IN DEVELOPMENT | — | — | |
Rescheduling an online booking | IN DEVELOPMENT | — | — | |
New marketing tool | PLANNED | — | Starting 09/2026 | |
Scheduled availability | PLANNED | — | Starting 09/2026 | |
Scheduled pricing | PLANNED | — | Starting 11/2026 | |
More payment methods in online booking | PLANNED | Will add Apple Pay, Swish, Vipps and MobilePay to online booking. | Starting 11/2026 | |
Booking with a Marketplace account | PLANNED | Will let a customer use their Marketplace account to book on a salon's own booking page. | Starting 11/2026 | |
Danish accounting integrations | PLANNED | Will be for Denmark. Which integration comes first is still open. | Starting 12/2026 | |
Hano transfer tool | PLANNED | — | Starting 01/2027 |
Dates in the When column for anything not yet released are estimates of when work starts, not when customers get it. A country named on a row that is not yet released is the intended market. Only Released and Open beta rows can be offered to customers.
How to read the statuses
Status | What it means for a customer |
|---|---|
PLANNED | Agreed and on the list, but work has not started. The When column is an estimate of when it will start, and estimates move. |
IN DEVELOPMENT | Being built now. Do not offer it to customers yet. |
PILOT | A named list of salons is using it, sometimes called a closed beta. Nobody else can be added without asking the product team. |
OPEN BETA | Any salon can turn it on, and new salons usually get it by default. Safe to recommend, but say it is new. |
RELEASED | Out and supported. Any salon in the listed countries can use it, though they may still need to switch it on. Sell it and support it freely. |
The status column is set by hand, on purpose
A feature's status cannot be read off a Jira workflow or off the code. Tickets sit in "In Progress" for months after a feature is live, and the step that switches a feature on for every existing salon is often run straight against the production database, leaving no trace anywhere. So each feature carries an explicit label on its Jira ticket — STAGE_PLANNED, STAGE_DEV, STAGE_PILOT, STAGE_BETA or STAGE_GA — set by a person, and that label is what this page shows.
That label is also what puts a row on this board, so a feature does not have to be an epic to appear here — a single story or task can. Country labels (FI, SE, NO, DK, EE, LV) record where it is released, or where it is intended if it is not out yet. The When estimate for a planned feature comes from the ticket's Target start date. ARCHIVED moves a row into the older-features list once it has been released for more than four months, and NOT_A_FEATURE keeps internal projects off this page entirely.
Want something added, removed or corrected here? Change the labels or Target start date on its Jira ticket, or ask the product team to. Editing this table directly will not last — it is rebuilt from Jira every Thursday, and a hand-added row disappears at the next rebuild.