Calisto Station

Turn any device you already own into a register, a stock lookup, or a daily operations portal.

Build the screen each role needs, then hand your employee a tablet. They sign in with their own account and the screen you built for them is what opens. The cashier gets a checkout. The floor associate gets a stock lookup. The manager gets the close. No dedicated POS hardware, and nothing to provision on the device.

Included in Nexus

Any device, any role

The cashier, the floor associate, and the manager each sign in to a different screen on the same device.

Build a station for each role your business needs. The cashier gets a checkout screen. The floor associate gets stock lookup and transfer requests. The manager gets end-of-day reconciliation and the close. The device does not decide which one opens; the account that signs in does. Invite someone by email and they join the same member list the rest of the platform reads, so there is no second directory to keep, and a station granted to someone turns up in their Agenda alongside the rest of their day.

Bring your own device

0

designers on one station: portal and terminal

0

steps from design to the counter

0

reports off one order of record

0

connected areas reading the same records

One

member list shared with every other app

Zero

permission tiers to administer

Who Works Here

Everyone who is not an admin is set up here.

Station is where the people who work for you are added, given a role you named yourself, and granted the stations their job needs. What each of them opens is what you composed for them.

Invite them by email

Add the people who work for you by address. They land on the same member list Workforce, Equipo and Purview already read, so there is no second staff directory to keep in step with the first.

Two Designers, One Station

The portal on the laptop and the screen on the counter are one station.

Build carries two modes of one station. Portal is the responsive employee view for anyone working from a desk or a phone, carrying the same portal capabilities Navigator gives your customers. Screens is the fixed canvas for a mounted terminal, opening at that device’s real dimensions. Both bind to one design, share one theme and use the same blocks.

The responsive employee view, for anyone working from a desk or a phone.

Laid out for a desk

The station laid out for a desk or a phone rather than a mounted terminal. Desktop-first, with a breakpoint for each width you arrange.

Navigator capabilities, pointed inward

The same portal capabilities Navigator gives your customers, pointed at your staff instead, so a block can bind to anything the rest of the platform holds.

One theme across both modes

Moving between the portal and the terminal never shows a different design.

Station · Portal Designer
Back to My StationsFront Desk — Coral BayActive
100%SavedSave
HomeTodayTasksDirectory+
Shift Header
Task List
Quick Actions
The Builder

A station is something you build, not something you switch on.

Compose the screens your staff actually open, connect them to your own catalog and locations, publish them to an address, and deploy them onto the devices in your rooms. One workspace carries all of it: four tabs across the top, the design settings behind the paintbrush, and no configuration hidden anywhere else.

My Stations

Every station you have built, with its status and when it last changed. Open one and you are in its workspace; there is no second place a station is configured.

Start From a Template

A gallery of starting points organised by what your business does, with the ones matching your active business first. Or start blank. Either way you land in the designer with a theme already applied.

Build It For Me

Describe the station you want to set up. Calisto reads what your business already has configured and assembles a first draft you then edit. It is a starting point, not a black box.

← StationsLobby BarLiveDesign
Build
Design the screens and the portal
Calisto
Scope which of your data flows in
Publish
Give it a public address
Deploy
Put it on your hardware
Team
Who configures it, who it belongs to
Monitor
How it is performing

Design is not a tab. It opens from the paintbrush in the header, in exactly the same place on every Calisto surface builder.

The Calisto Tab

Where the data on the screen comes from.

Every Calisto surface builder carries the same Calisto tab, and on a station it is the one place data is scoped. Pick the location, pick which parts of your business flow in, and add capabilities as blocks. Nothing is duplicated into the station: it reads the same catalog, the same reservations and the same members your other apps read.

Your own catalog, not a copy

A station sells from the one catalog your business already keeps. Change an item once and every station, kiosk, site and app that shows it changes with it. There is no station-local product list to keep in step.

Governed reads

What a station is allowed to show is decided by your business rules in Purview, applied on the server. A field that is redacted for this station is not sent to the device in the first place.

Scoped to a branch

Pick the location this station belongs to and it serves that branch. Leave it unscoped and it serves everything, which is what a single-location business wants and never has to think about.

Add a capability as blocks

Choose a module and its blocks are written into the station design, then you land back in the designer to arrange them. You are never handed a configuration screen with no visible result.

Onto The Counter

Publish it, deploy it, hand it to the people who stand at it.

Three tabs that take a design and put it in front of staff. Being able to configure a station and being given it as your daily portal are two independent things.

Publish

Set a subdomain and the station goes live at its own address. You get the URL and a QR code, so a member of staff opens it on any device with a browser without installing anything. Take it off live and the address stops serving.

Deploy

Assign the design onto the devices that should run it. A device shows a running-this-station badge as soon as it is assigned, and unassigning returns it to the default screen. Assign one, or a room full.

Team

Two independent things on one screen. Who is allowed to configure this station, and whose daily work portal it is. Someone can be given the station as their portal without being able to edit it, and the other way round.

The Service Floor

Tables, tickets, the kitchen, and the check that ties them together.

Your rooms and tables with live open-check balances. Routing rules that send a fired ticket to the right prep station. An interactive kitchen board and an all-day view. One check that courses, splits, and settles to a card, a room or a house account.

The Service Floor

Tables, tickets, the kitchen, and the check that ties them together.

Service is not a checkout screen. It is an open check that lives across a table, a kitchen ticket that has to reach the right prep station, an item that ran out at seven, and a bill that splits three ways with one part going to a room. Station carries all of it against the same records your other apps read, so the floor plan in Orderflow and the table on the station are the same table.

T1
Open
4 seats
T2
Free
2 seats
T3
Open
6 seats
T4
Free
4 seats
Bar 1
Open
Bar 2
Free
Tables and open checks
Your rooms and tables with each occupied one carrying its live balance. Tap a table and the station opens or resumes that check. Seat counts show when you have recorded them and stay blank when you have not, rather than being invented.
Kitchen routing rules
Redirect or duplicate a fired ticket to a prep station when the dining option, service area or category matches. Rules sit on top of the prep station each item already carries, with a priority order and an active flag.
The kitchen board
Pending, preparing, ready. Tickets advance on the board itself, the board can be narrowed to one station, and an all-day view totals what still has to be produced across every open order.
Eighty-six an item
Take something off mid-shift and it disappears from every station serving that catalog. Restore it the same way. Each change is logged against the person who made it.
One check, however it splits
Courses, splitting a check, settling part of it, and settling the rest to a room or a house account. Tips only apply when the whole settlement succeeds, so a partly failed payment never books a tip.
Room and account charge
Look up an in-house guest and charge to their room, or charge to a member or corporate credit line. Remaining limits are shown when you have set them and left blank when there is no limit rather than guessed.
Devices, Printers, Registers

The hardware you already own, in one hub.

Station runs in a browser, so the hardware is whatever you have: tablets on the counter, phones in staff pockets, a dedicated terminal at the desk. The Devices hub is where they are registered, activated with a code, scoped to part of the catalog, and retired. Printers and registers sit alongside them, each with the honest amount of control the app actually gives you.

All12
Terminals4
Handhelds5
Sessions3
Front Desk iPad
TerminalOnline
Bar Station
TerminalOnline
Floor Handheld 1
HandheldOnline
Poolside iPhone
HandheldOffline
Devices
Every phone, tablet and desktop registered as a station, in four views: all of them, terminals, handhelds, and the sessions currently open. Register a device and it stays pending until its six-character code is entered on the device itself.
Device detail
Rename it, set where it is, and see its reader, printer and recent activity. Each device also carries its own catalog scope, so a poolside handheld can be limited to the part of the catalog it should sell.
Printers
Add a receipt or kitchen printer by name, model and protocol, send a test print, and watch its heartbeat. Adding is deliberate rather than automatic: you tell Calisto what is on the network.
Print jobs and routing
A read view of the print queue with what is waiting, what failed and how many retries it took, and a view of which routing tags each printer answers to. Item and ticket routing is set in the kitchen rules, not here.
Registers
Named selling stations with their own device and status. Open a register with a starting float, close it with a counted amount, and the difference is recorded. Currency follows what you entered and is never assumed.
Receipt templates
The receipt a station prints is one of your governed templates, authored once in Purview and used by every station, so a branding change lands everywhere at the same time.
The Drawer and the Close

Cash you can actually account for.

Expected cash decomposed rather than asserted. Paid-in, paid-out, drops and no-sales during the shift. A blind close where the cashier never sees the expected figure, a manager reconciliation stamped to a person, and a Z-report that posts a balanced entry to the books.

The Drawer and the Close

Cash you can actually account for.

The drawer is where trust in a service business is won or lost. Station decomposes the expected figure rather than storing a total, keeps every mid-shift movement as its own line, hides the expected amount from the person counting, and stamps the reconciliation with the manager who signed it off. Closing the shift posts a balanced entry to the books in the same step.

Expected cash is a calculation
Opening float
+Cash sales
+Paid in
Paid out
Drops
Expected

Counted minus expected is the variance. Under a blind close the cashier never sees this panel.

Open the till
A starting float, optionally a note and the device it belongs to. From that moment the expected figure is a live calculation, not a number someone typed at the end of the night.
Movements during the shift
Paid in, paid out, a drop to the safe, a no-sale. Each one is a line in the drawer ledger with who made it, and each one moves the expected figure immediately.
Blind close
The cashier counting the drawer sees no expected figure at all. The whole breakdown is suppressed until a manager reconciles it, and the variance is stamped with that manager. Counting against a number you can already see is not a count.
X-report and Z-report
Pull an X-report mid-shift for the same figures without closing anything. The Z-report closes the shift: gross, net, tax, tips, refunds and comps, an item breakdown, tenders by method, and drawer expected against counted.
It posts to the books
Closing posts a balanced journal entry through the same folio and ledger spine the rest of Calisto uses, and reconciles the drawer in the same action. There is no export step and nothing to key in twice.
Daily reconciliation
What the stations reported, what actually posted to the ledger, the difference, and how many sessions it covers. If they disagree you find out the next morning, not at the end of the month.
Taking Money

Your gateway, your money, and a sale that survives the network.

A charge runs through the payment connector your account owns. Rails that settle later open a pending tender and wait for the callback. Sales taken during an outage replay as a batch that cannot double-post. No currency is ever assumed.

Your gateway, your money

A charge runs through the payment connector your account owns, resolved per account at the moment of the sale. Calisto never holds a platform key in the middle, and a station with no connector configured says so instead of failing quietly.

Your own connector
Resolved per account
Says so when unset

Rails that answer later

Pix and M-Pesa do not settle while the customer stands there. The station opens a pending tender, mints the QR or the request, and the callback captures it.

Pending tender
Callback captures it
Expired tenders recorded

Sells through an outage

Sales taken while the connection is down are replayed as a batch when it returns, matched on their own key so a replay can never double-post.

Batch replay
Idempotent by key
Flagged for review

More than one currency, honestly

Add the currencies a station accepts and refresh their rates. Every rate carries where it came from and when, the base rate is pinned, and a missing currency stays empty rather than being filled in with a guess.

Rate provenance
Base rate pinned
Never fabricated

One order of record

Lines are written to the order before any payment is attempted, and prices are resolved again on the server rather than trusted from the device. The same order carries through settlement, refunds and the books.

Server-resolved prices
One order end to end
Performance

Five reports off one order of record.

Every report reads the same order spine the checks were written to, so the transaction list, the margin report and the reconciliation cannot disagree with each other. Nothing is filled in where data is missing: a null cost renders blank, and an amount with no currency renders as a plain localised number rather than acquiring a symbol it never had.

Analytics

Today at a glance: revenue, orders, open sessions, refunds waiting, items taken off, online orders pending, and the last seven days of revenue. Amounts render in whatever currency was actually reported, and a plain number where there is none.

Transactions

Every line off the order of record, filterable by date range and property.

Daily reconciliation

Station totals against what posted to the ledger, with the variance and the session count.

Product margins

What each item makes. A missing cost renders as blank rather than as zero margin.

ABC ranking

Which items carry the revenue and which are carrying nothing.

Staff sales

Sales by the person who rang them, resolved through the operator on the terminal.

Approvals

Voids and comps that need a second pair of eyes, banded by risk, with the reason and who asked. Approve or reject in the queue.

Settings

Business identity, locale and brand shared with every other Calisto app; your catalog structure edited inline rather than sent elsewhere; which design each station serves; which space each device belongs to; and a getting-started checklist that resolves against real signals rather than ticking itself.

Connections

What your staff touch is the same record the rest of the business reads.

The catalog, the prices, the orders and the payments are shared with every other surface, so a station is a view onto them rather than a second system.

Station
Workforce
Commerce
Connected to Core
Operations
Work
Nexus

Workforce

Station → Workforce · Equipo · Agenda

Someone you invite here joins the same member list Workforce and Equipo already read, so a person is added once rather than once per system. A station you grant them appears inside their Agenda work view beside the rest of their day.

Commerce

Station → Catalog · Pulse · Orderflow · Payments

The terminal sells from the Catalog your website already shows, at the prices Pulse set. An order rung up on the counter joins the same queue in Orderflow as the website and the app, and payment takes on your own processor rather than a rented one.

Connected to Core

Station → Bookings · Registry · Tickets

A booking taken at the desk and one taken online are the same record, so the table held on the phone is the table the host sees. A member tapping in resolves against Registry, and admissions resolve against Tickets.

Operations

Station → Orderflow · Dispatch

Fire a ticket and the routing rules you set send it to the prep station that makes it, so the pass shows the queue rather than a stack of paper. What is running late is visible while it still matters.

Work

Station → Ledger · Depot

The close leaves a paper trail rather than a memory: a blind count, a manager reconciliation stamped to a person, and a Z-report that posts a balanced entry into the books instead of a note someone types up later.

Nexus

Station → Sites · Apps · Navigator · Kiosks · Display

The portal and the terminal are composed from the same block palette as your website, your app and the lobby screen, so a counter is one more place you place blocks rather than a separate product to learn.

Companion apps

Where Station touches everything else.

6 of these 14 connections are in your plan today. The rest stay visible so you know the instrument is there before you need it.

Orderflow
Calisto OpsNot in this plan
Orderflow

The Tables surface links across to the Orderflow floor plan, and tapping a table hands off to the published station with the space and property carried through.

Catalog
Calisto CommerceNot in this plan
Catalog

The menu builder mounted in Station edits the one shared catalog spine that Catalog owns; item prep-station assignments are set there, never in Station.

Purview
Calisto CoreIn your plan
Purview

Station surfaces, the station template library, receipt templates and who may configure a station are all owned by Purview, and its data rules redact station and device reads.

Pulse
Calisto CommerceNot in this plan
Pulse

Station reads the prices Pulse sets on the shared catalog structure; it never stores its own price book.

Ledger
Calisto OpsNot in this plan
Ledger

Closing a shift posts a balanced journal entry through the shared folio to ledger spine, and the daily reconciliation report compares station totals against what posted.

Workforce
Calisto CoreNot in this plan
Workforce

Clock in and clock out from a station write workforce clock events stamped with the active operator user id.

Display
Calisto NexusIn your plan
Display

Firing a kitchen order writes the order Display reads for kitchen and expediting screens.

Inventory
Calisto CoreIn your plan
Inventory

Stock, waste and prep are Inventory concepts; a station reaches them as blocks rather than holding its own stock records.

Bookings
Calisto CoreIn your plan
Bookings

In-house guest lookup for room charge reads the one shared reservations model, checked-in guests only.

Agenda
Calisto WorkNot in this plan
Agenda

A station assigned to a person as their portal renders inside Agenda under Work, My View, alongside its own published URL.

Kiosks
Calisto NexusIn your plan
Kiosks

The universal self-service kiosk template mounts the same station terminal shell on an unattended device.

Payments
Calisto CommerceNot in this plan
Payments

Charges run through the subscriber’s own payment connector resolved per account; Station never holds a platform key.

Registry
Calisto CoreIn your plan
Registry

Member and house-account credit lines resolve against the shared membership records.

Signal
Calisto OpsNot in this plan
Signal

Registered POS devices and their online state live in the shared device registry, and station signal thresholds set the targets alerts fire against.

Built for these industries

9 customer types run Station today.

See every sector
Pricing

No setup cost. Pay when you start using.

Employee portals for everyone on your team.

Calisto Station

Employee portal builder.

€30/station/mo

One station, and everyone you assign to it. Your team signs up and gets Depot storage and a calistomail.com address at no additional cost.

Everything. One Price.

Everything included in Calisto Station.

Your People
  • Invite an employee by email onto the same member list Workforce, Equipo and Purview already read. Acceptance needs a session on the invited address plus a one-time code, and only that code’s hash is ever stored.
Roles and Team Access
  • Name a role for how you organise people, then grant stations against it. Roles are labels, not permission tiers: there are no access levels to administer, because every member is a full operator.
Their Daily View
  • A station granted to someone opens at its own address and also appears inside their Agenda work view, so nobody has a second place to remember.
The Builder
  • My Stations, a template gallery organised by what your business does, build-it-for-me, and one workspace with four tabs across the top.
Dual Designer
  • The fixed device canvas for the terminal and the responsive portal for a desk or a phone, on one station, one theme, one set of blocks.
The Calisto Tab
  • Scope the station to a branch and to the parts of your business it should serve. Your catalog, never a copy of it.
Publish
  • A public address on calistostation.com with a QR code, opening in any browser with nothing to install.
Deploy and Devices
  • Assign a design onto terminals and handhelds. Register, activate with a code, scope a device to part of the catalog, retire it.
Tables and Checks
  • Your rooms and tables with live open-check balances, tap to open or resume, and a hand-off from the floor plan that carries the table through.
Kitchen
  • Routing rules that redirect or duplicate a fired ticket, an interactive kitchen board, an all-day production view, and eighty-six with an audit trail.
The Check
  • Courses, splits, partial settlement, settle to a room or to a house account, and tips that only apply when the whole settlement succeeds.
Drawer and Close
  • Decomposed expected cash, mid-shift movements, blind close, manager reconciliation stamped to a person, X-report and Z-report posting to the ledger.
Payments
  • Your own gateway, asynchronous rails with idempotent capture, offline replay that cannot double-post, and multi-currency carrying rate provenance.
Printers and Registers
  • Receipt and kitchen printers with test print and heartbeat, a print-queue monitor, and named registers with open, close and recorded variance.
Performance
  • Live analytics, five reports off one order of record, and a void and comp approval queue banded by risk.
Settings
  • Shared business identity and locale, catalog structure edited inline, per-station design assignment, device spaces, and notification preferences.
Honest answers

Questions about Calisto Station

No. Station is the builder. You design the screen a role needs, and when that person signs in on a tablet, a phone, or a mounted terminal, that screen is what opens, which is what makes the device a register. It is also where every employee who is not an admin gets set up, so granting floor staff access to the terminals is part of setting them up.

One is the responsive employee portal, desktop-first with full portal capabilities. The other is the fixed terminal screens on the device. Same builder, two surfaces, because a person and a till need different screens.

No. It is an organising label for granting stations. Calisto has no intra-account permission tiers, so a role groups people for setup rather than restricting what they may see.

No. They are the shared member model that Workforce, Equipo and Purview all read. Adding somebody once means their schedule, training and pay follow.

The pricing section on this page reads the live catalogue and is the authority. There are no per-employee seat fees, and Station works without the rest of the Nexus suite.

The published surfaces stop serving and the member records, transactions and schedules export in standard formats.