Skip to content
Roadmap

What we do, and what we don’t

Every feature page on this site describes something that actually ships. This is the other half of that promise: the things Sofia does not do yet, written down.

Roadmap

Shipped18

Not built3

Under consideration0

Shipped

  • Call Sofia — conversation engine

    Per-store number on the live phone path, coverage matcher, Tanda and Firestore adapters, kill switch. Each store has its own number after you subscribe. This site does not publish a line to call.

    Learn more
  • Platform maintenance mode

    Ops toggle. Public site 503s onto a brief page. The phone webhook says the message and hangs up.

  • Explainable Auto-Fill with run history

    Hard constraints then weighted scoring, per-assignment reasoning, and one-click undo of a whole run.

    Learn more
  • Fair-workweek ledger

    Append-only premium tracking across ten jurisdiction presets, set per location, with an audit-ready export.

    Learn more
  • More jurisdictions

    Philadelphia, Emeryville, Berkeley, Evanston, and unincorporated Los Angeles County join the five already shipping. A city that is not listed is still a custom pack.

    Learn more
  • Offline-first time clock

    Deterministic punch ids, a device hold until sync succeeds, a break answer that does not insert a break, optional grace or rounding, an optional still, declared tips when the till is on, and one exception inbox on Timesheets.

    Learn more
  • Demand forecasting

    Recency-weighted expected staffed hours by weekday, position, and daypart. A manager can leave a holiday week out of the average. Included on every plan.

    Learn more
  • Worker self-service

    Open-shift claiming, worker-to-worker swaps, availability, time off for a day or a portion of a day, and earned-so-far pay.

    Learn more
  • Skills inferred from shift history

    Open a person on Team. A position they were assigned at least twice in the last eight weeks, and are not tagged for, is offered as a chip. Adding it is a click in the editor — nothing is written until you save — and Auto-Fill can then schedule them there.

  • Ask Sofia

    Checkable answers for the store and week open on Schedule. Chips open that screen. Fill Saturday explains the ranking and does not apply it. A product that is off is named as off.

    Learn more
  • Notification deep links

    A notification opens the right week, location, and shift — Schedule for managers, My shifts for workers.

  • Tanda OAuth

    Connect Tanda from Sofia settings. Tokens stay on the server. The adapter fails closed if Tanda is disconnected.

    Learn more
  • Store billing

    A$200 per store per month via Stripe. Subscribe from Settings, cancel in one click, unused days refunded, card detached. Unpaid workspaces keep working.

  • Pay runs

    An admin turns Payroll on. A manager builds a draft from approved hours, paid leave, and recorded tips when those products are on, and can type hours when Time is off. My pay lists the rows that add up to the gross. The CSV is the clerk's to import. Sofia does not sync to Xero, KeyPay, Gusto, or ADP. There is no tax filing and no bank file.

  • Till

    An admin turns POS on. Staff record items, tax, a tip, and a tender of cash, card, or other. Card means the payment was taken somewhere else. Paid items split by daypart. A minute weight can suggest empty shifts, and they stay drafts until a manager accepts them. Sofia does not charge a card and does not read an external till.

  • Staff messages

    An admin turns Messages on. Everyone, a channel per location, a channel per position at that store, and direct messages. A new message rings the bell without the message text. A qualified yes in the channel can take an offered shift. It is not customer SMS.

    Learn more
  • Reports

    An admin turns Analytics on. The report is one store and one week. The scorecard names scheduled hours, approved hours when Time is on, labor against the typed plan and against till sales when the till is on, and premiums booked in the ledger. A closed week can show forecast accuracy from shift history. Voice fills and the median come from the call log. A store that did not save a report is absent. Sofia does not invent award rates, tax, or message volume.

    Learn more
  • Tanda drift

    On a Tanda roster, a manager compares the open week. Opening the report changes nothing. One row can be written to Tanda or reloaded into Sofia. An in-app claim, swap, or leave approval uses the same adapter. A cost Tanda returns is labelled from Tanda and is not stored as a wage. Pay items, punches, and till sales are not pushed. Deputy and 7shifts are not connected.

    Learn more

Not built

Things you may be looking for that Sofia does not have. If one of these is a dealbreaker, better to find out here than three weeks into a rollout.

  • Payroll and POS integrations

    Sofia does not send pay items to Xero or MYOB, lodge tax, or produce a bank file. It does not read an external till or charge a card. Pay runs and the in-app till are separate products an admin turns on. Projected sales stay a number a manager types.

  • Native mobile apps

    The worker and manager surfaces are mobile-first web, and web push is available if a worker opts in. There is no app-store native app.

  • SSO and advanced roles

    Role-based access is enforced in the database rules today, but SSO is a Scale conversation rather than a self-serve feature.

Information pack

Request a free information pack

A practical overview of Sofia, activation, and A$200-per-store pricing for your operation — sent straight to your work inbox.

  • Call-offs by call or by text, from the roster rules you set
  • How the first store is activated
  • A$200 per store per month

Optional. The site or company this pack is for.

We use these details to send your pack and follow up on your request. Privacy