Can the tablet and phone be used at the same time?

Yes. They share one catalogue and one order state, so both can be in use during service without the two views disagreeing.

Was this an off-the-shelf POS that was configured?

No. DI Solutions built the POS software for the client as a product build.

Built by DI Solutions

Basil POS

Basil POS is a restaurant point-of-sale product, built by DI Solutions, whose tablet till and phone app share a single catalogue and a single live order state.

#POS#Restaurant#Mobile#Product build

Talk to an expert Visit the live site

Basil POS tablet and phone showing an à la carte menu and open order total

What Basil POS does

Orders

Live running total
One shared order state
Start on one device, finish on another

Clients

Tablet counter till
Companion phone app for the floor

Engagement

Product built end to end for the client
Not an off-the-shelf POS configuration
Ongoing development

Basil POS in use

The Basil POS counter setup — a swivel-mounted touchscreen till above a cash drawer, with a card terminal alongside

The Basil POS Android tablet till showing an open order, its item list and running total ready to send for payment

The cash payment dialog open on the tablet till, with the same payment step mirrored on the companion phone app

Pending orders across the tablet and phone views, each tile showing its counter, table and order total

The branded Basil POS handheld terminal, used for taking orders and payments away from the counter

How we built it

Challenges

Service does not happen in one place. A counter till on its own forces re-entry whenever an order starts at the counter and finishes at the table, and re-entry during a busy service is where orders get lost.

Our Process

We built the product end to end for Basil rather than configuring an off-the-shelf POS, with a tablet till and a companion phone app reading the same catalogue and writing to the same order.

Solutions

Category-driven menus, live order totals, per-item pricing, and one shared order state across both clients.

Results

An order started on the tablet can be finished on the phone with no re-entry, and both screens stay in agreement throughout service.

At a glance

Product: Basil POS
Client: Basil
Engagement: Product build, ongoing
Sector: Restaurant and hospitality
Clients: Tablet till and companion phone app
Live site: posbasil.com

What is Basil POS?

Basil POS is a point-of-sale system for restaurants. It presents the menu by category — à la carte, alcohol, appetisers, drinks, sides — and keeps a running order with per-item pricing. DI Solutions built the product for the client end to end.

Why does it run on both a tablet and a phone?

Because service does not happen in one place. The tablet is the counter till; the phone is the same system in a server's hand. Both read the same catalogue and write to the same order, so an order started at the counter can be finished at the table without re-entry.

Did DI Solutions build the whole product?

Yes. This was a product build rather than a staffing engagement — we built the POS software for Basil rather than placing developers into an existing team, and the engagement is ongoing.

Support Center

Frequently Asked Questions

Find answers to common questions about our services, process, and how we deliver unparalleled digital solutions.

: Yes. They share one catalogue and one order state, so both can be in use during service without the two views disagreeing.
: No. DI Solutions built the POS software for the client as a product build.