Where Timma's features stand, and what shipped each week. Written for everyone, not just the development team. If you support customers or sell Timma, this page should answer "can my customer use this yet, and where?" without asking anyone.
Feature status
Feature | Status | Who can use it | Epic |
|---|
Tap to Pay on iPhone | 
| Any salon in Finland, since August 2026. | TIM-193 |
Kletta accounting integration |
| Any salon in Finland, since August 2026. 10 €/month per business ID, first month free. | TIM-51 |
Series cards |
| Any salon. Existing customers were migrated across in August 2026. | TIM-97 |
Refreshed marketing site |
| Public website, live in every market since August 2026. | TIM-758 |
Online booking, new version | 
| New salons get it automatically. Existing salons can switch it on themselves. | TIM-2 |
New gift card shop | 
| Will require Adyen. | TIM-897 |
Pay by link |
| Will cover Finland, Norway and Sweden, with MobilePay, Vipps and Swish. | TIM-53 |
Blocking clients |
| Will need the new online booking. | TIM-1237 |
PowerOffice GO accounting integration |
| Will be for Norway. | TIM-1031 |
Genie AI analyst for salons |
| — | TIM-1034 |
Online booking email improvements |
| — | TIM-1304 |
Rescheduling an online booking |
| — | TIM-1352 |
New marketing tool | 
| — | TIM-1384 |
Scheduled availability |
| — | TIM-1385 |
Scheduled pricing |
| — | TIM-1386 |
Hano transfer tool |
| — | TIM-312 |
A country named on a row that is not yet released is the intended market, not somewhere a salon can use the feature today. Only Released and Open beta rows can be offered to customers. |
|
These are long since live and stable. They are kept out of the table above so it only shows what is changing. Any salon in the listed countries can use them.
Feature | Released | Who can use it | Epic |
|---|
Prerequisite forms | February 2026 | Any salon. Forms customers fill in before their appointment. | TIM-4 |
Subscription billing in Estonia and Latvia | January 2026 | Any salon in Estonia and Latvia | TIM-108 |
Fiken accounting integration | January 2026 | Any salon in Norway | TIM-95 |
Tripletex accounting integration | December 2025 | Any salon in Norway | TIM-3 |
The Tripletex and Fiken integrations existed long before these dates. The 2025–2026 work rebuilt their settings screens; it did not launch the integrations. |
|
How to read the statuses
Status | What it means for a customer |
|---|
| Agreed and on the list, but work has not started. No date to promise. |
| Being built now. Do not offer it to customers yet. |
| A named list of salons is using it. Nobody else can be added without asking the product team. |
| Any salon can turn it on, and new salons usually get it by default. Safe to recommend, but say it is new. |
| 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. |
Weekly releases
Timma releases every Thursday. Each release gets its own page listing what changed, in plain language.
Each weekly page is split into three parts, because "we shipped it" and "a salon can tell" are not the same thing:
Section | What goes in it |
|---|
Highlights | Features that reached more customers than the week before, plus the two or three biggest items. Read this if you read nothing else. |
Changes your customers will notice | Changes to features salons are already using, so the difference is visible straight away. This is the section support and sales need. |
Everything else | Collapsed. Groundwork on features that have not launched, plus internal and commercial work. Nothing here changes anything for a salon this week. |
The split between the last two sections follows the feature's status above: work on something still In development cannot be customer-visible, because the feature is not out yet. That is why a week's biggest body of work sometimes sits in the collapsed section.
How this page is maintained
Every Thursday morning, before the Jira board's Done column is cleared:
Everything finished that week is stamped with the week's release version in Jira.
A new weekly page is written from that list and added under the current year.
The table above is regenerated.
The release is marked as released in Jira and the board is cleared.
Tickets worth mentioning at all are tagged SLIDES in Jira. That tag decides whether an item appears; the feature's status decides which of the three sections it lands in.
A feature's status cannot be read off a Jira workflow or off the code. Epics 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 epic carries an explicit label — STAGE_PLANNED, STAGE_DEV, STAGE_PILOT, STAGE_BETA or STAGE_GA — set by a person, and that label is what this page shows. Country labels (FI, SE, NO, EE, LV) record where it is released, or where it is intended if it is not out yet. 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 the page entirely. Any epic with no stage label is reported as missing rather than guessed at. |
Spotted something wrong? Tell the product team rather than editing the table — it is regenerated each week, so manual edits get overwritten. The fix belongs on the epic's labels.