RoarPOS

Everything RoarPOS does

The parts a cafe touches every day, and the parts it should never have to think about.
The register app's first screen, Connect this tablet, asking for the enrollment code

The register

A native Android app for any tablet running Android 8 or newer. It is not in the Play Store; it is downloaded from this site or from the portal and connects with one code.
  • Staff sign in with a four-digit PIN, verified on the tablet even when offline
  • Cash, card and invoice tenders, tips, discounts and loyalty
  • Sells offline and drains the queue when the connection returns
  • Menu refreshes every minute; a price change lands before the next customer
  • Updates itself from Settings, never forced, with what's new before you say yes

Menu, sizes and modifiers

Categories are the headings. Channels are the places the menu appears: the register, online ordering, a menu board, the website. Modifier groups are the questions asked when something is ordered, milks and syrups and extra shots, written once and shared between items.
  • Per-channel price, name and serving hours, so breakfast can stop at 10:30 online and 11:00 at the counter
  • Seasonal specials that appear and disappear on their own dates
  • Remove a channel or category and move its items in the same step
An item in the back office: details, sizes, the options it asks, and the channels it appears on
The admin portal's home page with its setup checklist

The owner portal

A guided setup checklist gets a cafe from nothing to taking cards: the shop and its hours, Stripe onboarding into the cafe's own account, then readers and tills.
  • Tax profiles and rates per location
  • Employees, roles and PINs
  • Register layouts, schedules and discounts
  • Loyalty programmes with boost windows
  • Go live on your own domain from the portal

Loyalty, gift cards and wholesale

Points that earn and spend at the till, gift cards sold and topped up with an outstanding-balance report, and wholesale invoices raised against a customer record.
A loyalty programme configured in the admin portal
Sales reports in the admin portal

Reports that answer the question

Takings by hour, product mix, tenders, refunds and voids, and the one line that matters at cash-up: anything taken and not yet settled.

Online ordering and kitchen display

Online ordering reads the same menu with its own channel, collection slots come from the shop's opening hours, and payment goes through Stripe so the cafe never sees a card number. A kitchen display enrols with the same kind of code as a register.
Online ordering checkout on a cafe's website

Payments, done properly

Every cafe connects its own Stripe account from the portal. Card money goes to the cafe's bank, not through us. Card readers are Stripe WisePOS E smart readers, paired by a code shown on the reader, to a location or to one register. Online payments and in-person payments settle to the same account and show up in the same reports.

Questions cafes ask first

Do I need special hardware?

Any Android tablet running Android 8.0 or newer, used sideways. A Stripe WisePOS E for card payments. Anything with a browser for a kitchen display or menu board. A receipt printer on the network if you want paper.

What happens when the internet drops?

The register keeps selling from its cached menu and prices. Sales queue on the tablet and go out when the connection returns; the count of unsent sales stays on screen so a shift never ends with money still on the tablet.

Is the menu really shared?

Yes. There is one menu, in the back office. The register, the ordering page, the website and any menu board read it, each through its own channel. The register checks for changes every minute.

Who holds the card payments?

Stripe, in the cafe's own connected account. RoarPOS never sees a card number and the platform never holds the cafe's money.

RoarPOS

The point of sale built for coffee. Part of the HGCS ecosystem by Creativity Jungle.
Contact
Creativity Jungle
Canopy CMS
© 2026 Creativity Jungle