Restaurants, cafés, food trucks and bakeries

From the table to the kitchen to the register.

A point of sale for places that serve food. Tables and seats, courses and modifiers, split bills, and a menu you edit from any browser.

Coming soon. Amyn is in development.

A white point-of-sale screen and card reader concept on a marble café counter
Concept render. Amyn hardware is in development.

Tables, sections and seats.

Draw your room once: tables grouped into sections, each with its seats and a place on the map. The register shows which are open, and each table order carries a guest count.

Every item carries a seat and a course number. Starters go out before mains, and each plate reaches the right person.

Counter orders skip all of this.

Orders the kitchen can read.

Modifiers are the “no onions” and “extra sauce” choices on an item. Each group sets its rule: pick one, pick up to three, required or optional. A modifier can change the price or cost nothing. A free-text note covers the rest.

Course, seat, modifiers and note travel with every item. That is what a kitchen ticket needs. The kitchen screen that shows it is being built.

Split bills, partial payments and tips.

One bill can be paid in two or more payments. Each payment records its own tender, cash or card, and its own tip. The order shows what is still owed until it reaches zero.

Seat numbers on every item give a by-seat split what it needs.

See payments and rates

Hours that follow your year.

Each location keeps its usual hours and its Ramadan hours. Set them once for the location, not on every register. A pause for Friday prayer has its own setting.

The customer screen is planned to follow those hours, so an iftar special shows only when it should.

See the customer screen

Shifts and the time clock.

A shift opens with a cash float and closes with a count, which shows whether the drawer is over or short. Staff clock in and out, breaks included. The dashboard will show the day by location, from any device.

See the dashboard

One register is enough.

A food truck runs on one register. Card payments taken without a signal wait in a queue until the signal returns. A bakery sells by the piece and by the box; items carry their own sizes and prices.

What is built, and what is planned.

Where these features stand, as of October 2026. Built means the tables and rules exist in our cloud backend; the screens that use them are still being made. You cannot use them yet: no merchant accounts and no live registers until launch.

FeatureStatus
Orders, items, sizes and per-location pricesBuilt
Modifiers and item notesBuilt
Tables, sections, seat and course numbersBuilt
Split and partial payments, tipsBuilt
Shifts and the time clockBuilt
Business and Ramadan hours, Friday prayer pauseBuilt
Kitchen screenBeing built (the order data it shows is built)
Browser menu editor and publishingBeing built
Online orderingPlanned
ReservationsPlanned

The same promises for every business.

  • One simple card rate, published before launch. See payments and rates
  • No monthly software fee. No statement fees. No PCI fees (a charge named after the card industry’s security standard).
  • No hardware subscription or lease. Built for spills, grease, heat, drops and long shifts. See the hardware
  • We don’t sell your data. No ad trackers, no analytics scripts from other companies, no training AI on your data. Read our privacy promise
  • Interest-free by design, with transparent terms. The tools are in development, and nothing on this site is an offer of financing. Read about interest-free payments

Our planned direction. Amyn is in development.