Tabula

Our own product: one point of sale for three businesses

Tabula is a product we designed without a client: a point of sale for three very different businesses on one design system, a restaurant, a retail store and a salon. Each gets its registers, its checkout and its owner back office, and all three are built from the same components and tokens. We sell it as a Figma kit for teams building point of sale and commerce products.

A point of sale is used standing up, in a hurry, by someone with a customer in front of them. A missed allergy, a ticket nobody sees or a refund that cannot be found costs more than any screen is worth, so the hard states came first: late tickets, allergies, low stock, offline registers, split checks and refunds.

One system, switched by mode

The three businesses differ in their work, not in their parts, so the difference lives in variables. A vertical mode, gastronomy, retail or beauty, restyles the accent. A density mode, touch, desk or kitchen, resizes every control for the device and the hands using it. Colour comes in light and dark, which is how the kitchen display gets its dark screen from the same tokens as everything else.

From the register to the kitchen

The restaurant day starts with a staff PIN sign in and a register that leads with the open orders across dine in, takeout and delivery. Orders are built from a photo menu with modifiers and notes for the kitchen, and sent with one button.

The kitchen display is designed to be read from across the line. Tickets sit in station columns, oldest first, with allergies in red. A ticket turns to a warning at ten minutes and overdue at fifteen, the all day counts run along the top, and a bumped ticket can be recalled.

Pay at the table

Paying at the table is a flow, not a screen. The server splits the check by seat or evenly, picks card, cash, gift card or a split tender, and hands the tablet to the guest with the tip options already worked out. The guest taps, gets a thank you and a receipt, and the table resets on the floor plan.

Retail: cash, counted for you

The store register handles what a shop counter actually sees: variants, returns and exchanges in the same sale, loyalty points and member pricing. At the cash step it does the change math, with quick amounts for the notes people usually hand over, and the customer facing display shows the same numbers as the cashier.

Salon: from the chair to checkout

The salon is built around the appointment. A stylist works from her phone, sees allergy notes like latex for the client in the chair, and sends the client to checkout when the service is done. The front desk adds the product the stylist recommended, the tip goes to the stylist, the next visit is booked at the interval she suggests, and the colour formula is saved to the client’s profile. Clients can also book online in four steps.

The owner’s back office

Each business gets an owner back office for running several locations from one desk: sales by location with labour, sales by day with a forecast, top items and the payment mix, plus the menu or catalogue, inventory, customers, staff, and ten or eleven settings pages. A location that goes offline says how many orders have not synced yet, and a guest profile carries the allergy that gets flagged on every ticket.

Every device a POS runs on

The 90 screens cover the devices a point of sale really runs on: tablet registers at 1366, a kitchen display at 1920, the back office at 1440 and 1280, a phone at 430, a portrait tablet at 834 and a self order kiosk at 1080 by 1920.

They are built from 34 component sets with 151 variants plus 6 standalone components, documented on spec sheets, on 175 variables in six collections, with 19 text styles in Geist including a numeric scale for prices and totals. Twelve flows are wired as clickable prototypes, 94% of frames use auto layout, and the file includes the product architecture, a device map and an audit page. The kit is on our products page.