View Source

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	Who can use it	When	Ticket
Tap to Pay on iPhone	Any salon in Finland.	Released Aug 2026	TIM-193
Kletta accounting integration	Any salon in Finland. 10 €/month per business ID, first month free.	Released Aug 2026	TIM-51
Series cards	Any salon. Existing customers were migrated across.	Released Aug 2026	TIM-97
Refreshed marketing site	Public website, live in every market.	Released Aug 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
Prepayment for specific services	Will let a salon require prepayment on chosen services only, rather than all of them.	—	TIM-796
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	—	Starting 09/2026	TIM-1384
Scheduled availability	—	Starting 09/2026	TIM-1385
Scheduled pricing	—	Starting 11/2026	TIM-1386
More payment methods in online booking	Will add Apple Pay, Swish, Vipps and MobilePay to online booking.	Starting 11/2026	TIM-1392
Danish accounting integrations	Will be for Denmark. Which integration comes first is still open.	Starting 12/2026	TIM-1394
Booking with a Marketplace account	Will let a customer use their Marketplace account to book on a salon's own booking page.	Unknown	TIM-1393
Hano transfer tool	—	Unknown	TIM-312

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.

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	Ticket
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. The When column is an estimate of when it will start, and estimates move.
	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.

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.