Fast on proper hardware
A native Android till for SUNMI counter terminals. Scans register without selecting a field first, and the printer, cash drawer and second screen are all driven directly.
Early access · Built in the UK
The till built on a real shop floor.
ForwardPOS is a retail till, customer display and stock system in one. It runs on proper counter hardware, keeps taking cash when the internet drops, and holds a stock ledger that matches the shelf. It is being built and proven behind a real counter at Tower Cards, with WooCommerce sync in testing.
£1 excluding VAT covers your whole first month — every shop, every extra till, whichever plan you choose. Your normal price, from £59 a month, starts on the second invoice.
5060123456781SCAN OR TYPE
2×Card sleeves, matte blackSLV-100-BLK£17.98
1×Deck box, forestDBX-FOR£12.50
1×Playmat, tidalMAT-TDL£24.99
3×Booster pack, sealedBST-S01£13.47
Items7
Net£57.45
VAT 20%£11.49
TOTAL£68.94
CUSTOMERDISCOUNTHOLDREMOVE
PAY£68.94
K
Kestrel GamesFriday league from 6pm
2 × Card sleeves£17.98
Deck box, forest£12.50
Playmat, tidal£24.99
3 × Booster pack£13.47
TOTAL£68.94
KESTREL GAMES
TILL01-000418
2 Sleeves17.98
1 Deck box12.50
1 Playmat24.99
3 Booster13.47
TOTAL68.94
Cash70.00
Change1.06
- 01ScanBarcode in, product found, no field to tap first.
- 02BasketPriced from your catalogue, VAT worked out per rate.
- 03DisplayYour customer sees it, in your branding.
- 04PayCash, card or test card, confirmed by the provider.
- 05StockEvery unit moved through a ledger.
- 06ReceiptPrinted on the 80 mm printer, or looked up later.
- 07SyncYour web shop sees the same stock count.
Why ForwardPOS
Everything a counter needs, and nothing that gets in its way.
Most tills are a website squeezed into an app. ForwardPOS is written for the counter itself: the hardware under your hands, the queue in front of you, the stock in the back room.
A customer display that's yours
Your logo, colours and messages on the customer screen, with a live basket while you serve and your promotions and events when the counter is quiet.
Keeps taking cash offline
When the connection drops, cash sales are saved on the till and uploaded exactly once when it's back. Nothing is guessed, doubled or quietly thrown away.
One stock count, everywhere
ForwardPOS holds the stock figure for your shop and your website. Every sale, return and correction goes through a ledger, so you can always see why a number changed.
Money you can trust
Prices are held in whole pennies, never floating-point numbers. VAT is worked out per rate, and net plus VAT always equals the total. The server re-checks every basket the till sends.
Modules for your trade
Turn on ForwardTCG, Cinema, Hospitality, Eat or Hotel for the workflows that trade needs — each on the same till, back office and stock ledger. All five are in early access and not charged yet. See modules.
When the Wi-Fi drops
The queue doesn't wait for your router.
A prepared till carries on taking cash when it loses the connection. It shows you plainly that it's offline and how many sales it's holding, and uploads each one exactly once when it's back.
- Each offline sale keeps its original ID, so a retry can never create a second sale.
- The cash given, change, VAT and total are stored exactly as the customer saw them.
- If the server disagrees on a price or tax rate, the sale waits for a manager. It is never quietly rewritten.
- Card payments never pretend to work offline. Only the payment provider can confirm a card payment.
Cash received. Saved on this till; will sync when connected.
1×Playmat, tidalMAT-TDL£24.99
2×Card sleeves, matte blackSLV-100-BLK£17.98
Total£42.97
Cash given£50.00
CHANGE£7.03
NEXT CUSTOMER→
Customer zero
“Tower Cards is where we prove it works. ForwardPOS is the product.”
ForwardPOS is being developed alongside Tower Cards, a UK trading-card shop, on the same SUNMI hardware a customer would use. There is no bespoke build for them: their logo, prices and promotions are settings, exactly as yours would be.
15.6″ + 10″operator and customer screens on the D3 Pro
80 mmthermal receipts, with lookup and reprint
1psmallest unit of money anywhere in the system
1×per sale, however many times the till retries
Help shape the till you'll use every day.
Early access is open to a small number of independent UK shops. You get hands-on setup, a direct line to the people building it, and a real say in what gets built next.
Platform
One system from the scanner to the stockroom.
ForwardPOS is five parts that share one set of data: the till your staff use, the screen your customers see, the back office you manage from, the integrations that link it all up, and the core that keeps everything consistent.
Every feature below is marked honestly. Built works and is covered by automated tests. In testing is written and being proven on real hardware or with a real provider, and Early access means shops can use it today while it is still being proven. Planned is on the roadmap.
The parts of ForwardPOS
The till
A native Android app for counter terminals. Big targets, one-tap actions, and scanning that works without selecting a field first.
| Barcode scanning, EAN-13, EAN-8, UPC, Code 128 | In testing |
| Basket, VAT per rate, line and order discounts | Built |
| Cash with change and cash drawer | Built |
| Refunds: whole sale, single lines, part quantities | Built |
| Till sessions: float, paid in and out, cash-up | Built |
| Offline cash with exactly-once upload | In testing |
| Receipt printing, lookup and reprint | In testing |
| Inventory browse by category and name (no barcode required) | Built |
| Separate till screens when a module is enabled for that till | In testing |
| Saved servers, e.g. a live shop and a training server | Built |
The customer screen
Your shop's face at the counter. It follows the basket as you scan, confirms the payment, thanks the customer by name of shop, then goes back to your own promotions.
| Live basket, total and payment status | Built |
| Logo, colours and thank-you message from the back office | Built |
| Idle slides for promotions and events | Built |
| Idle video | In testing |
| Browser or tablet displays for other hardware | Planned |
Payments and web shops
Integrations plug in behind a fixed boundary, so you choose your card provider and web platform, and switching one never means changing the till.
| Cash, and a test card for training | Built |
| Mollie card payments and card refunds | In testing |
| WooCommerce stock and order sync | In testing |
| Shopify | Planned |
| Stripe Terminal and Revolut | Planned |
| Accounting exports | Planned |
Where you run the shop
A web app for managers and owners. Nothing to install, and every action is limited by what that person is allowed to do.
| Products, barcodes and prices | Built |
| Product categories for catalogue browse | Built |
| Stock levels, adjustments and a full movement history | Built |
| Settings → Modules to enable vertical modules per business, location or till | Built |
| Sales, voids and receipts | Built |
| Review of offline sales, with price and tax approvals | Built |
| Customers, loyalty fobs, events and attendance | Built |
| Several shops: locations, tills and central pricing | Built |
| Staff roles and an audit log of sensitive actions | Built |
| A virtual till in the browser, for online orders and counter work without a terminal | Built |
| Receipts carrying your shop's name, address, VAT number and your own footer | Built |
| Cash position at a glance: opening float, cash sales, refunds, paid-outs and the expected drawer | In testing |
| Staying signed in through a page refresh, with idle and absolute limits | In testing |
| Suppliers, purchase orders and goods-in | Planned |
| Margin and category reporting | Planned |
Forward Core
The part you never see, and the reason the numbers add up.
Forward Core is the central service every till and screen talks to. It re-prices every basket from your own catalogue, owns the stock figure, and records who did what.
- A till's arithmetic is checked, never trusted. If the till and the server disagree on a total, the sale is refused rather than quietly corrected.
- Each shop's data is walled off from every other shop's, and automated tests actively try to break that wall.
- Staff permissions are specific actions such as void, refund or price override, not just job titles.
- Past sales keep the prices, names and VAT rates they were sold at, even after you edit a product.
backoffice · Kestrel Games
FWDDashboardProductsStockSalesTillsCustomersSettings
Today£1,28442 sales
7 days£8,905301 sales
Offline0all synced
Low stock6lines
SaleTillStatusTotal
TILL01-000418Till 01Completed£68.94
TILL02-000207Till 02Completed£12.50
TILL01-000417Till 01Refunded£24.99
See it running on a real counter.
Book a demo on a D3 Pro, with your own products loaded if you'd like.
Hardware
Built for the counter, starting with the SUNMI D3 Pro.
ForwardPOS runs natively on commercial Android counter terminals. It drives the printer, cash drawer, scanner and customer screen directly instead of working around them. The first supported terminal is the SUNMI D3 Pro.
What the terminal gives you
The operator screen
15.6″ Full HD touch. The layout runs basket on the left, totals and a large PAY button on the right, with the connection state always in view.
The customer display
The 10″ rear screen shows your branding, the live basket and the total, then your promotions between customers.
KESTREL GAMES
12 Market Row · VAT 123 4567 89
TILL01-000418 · Sam
21/09/2026 14:32
2 x Card sleeves17.98
1 x Deck box, forest12.50
1 x Playmat, tidal24.99
3 x Booster pack13.47
Net57.45
VAT 20%11.49
TOTAL£68.94
Cash70.00
Change1.06
Thanks for shopping with us!
80 mm receipts
Your shop name, address and VAT number, the sale number, operator, a VAT breakdown and your own footer. Any receipt can be looked up and reprinted later.
The back office, anywhere
Runs in any modern browser, on a laptop in the back room or a tablet on the shop floor.
SUNMI D3 Pro
The first certified terminal.
Specifications from SUNMI's product page. Configurations vary by reseller, so check the exact model before you buy.
- Operator screen
- 15.6″ Full HD touchscreen
- Customer screen
- 10″ rear display, with an optional NFC tap-on-glass version
- Platform
- Qualcomm, 4 GB RAM, 64 GB storage, SUNMI OS (Android)
- Receipts
- 80 mm thermal printing
- Cash drawer
- RJ12 drawer port, opened by the till with every open logged
- Scanning
- USB barcode scanners that type like a keyboard
- Network
- Ethernet and Wi-Fi. Ethernet is recommended for the counter.
Not locked in
Your hardware choice stays yours.
The till talks to hardware through a small, fixed set of abilities: print, open the drawer, read a barcode, drive a second screen. SUNMI is the first implementation of that, not the only one.
- Generic ESC/POS receipt printers are supported alongside SUNMI's own.
- The till checks what a device can actually do before offering it, so it never pretends a drawer or screen is there.
- More Android terminals, and browser or tablet customer displays, are on the roadmap.
- We can source and set up hardware for you, or you can use a compatible terminal you already own. Hardware is quoted separately from the software.
Want the hardware set up for you?
We can source a D3 Pro, scanner and cash drawer and set them up with your shop, or get a SUNMI you already own running.
Modules · ForwardTCG
For shops that sell cards one at a time.
Trading-card and hobby shops don't just sell boxes. They sell singles in a given condition, buy collections over the counter, and run league nights. ForwardTCG adds all of that to the same till, without changing how the rest of the shop works. Singles, buying, store credit, graded cards and pre-orders are all in early access today.
What it covers
Built with a card shop, for card shops.
ForwardTCG is developed alongside Tower Cards. It's an optional module: shops that don't need it never see it, and it never changes how the core till behaves. Early access means it is in real use while parts of it are still being proven, mostly on the Android till. The table below says which is which.
Two rates, set by you. The cash rate and the trade-credit rate are configured separately for your shop, within limits your business sets. Neither is worked out from the other, and nobody at the till can override them.
Flat fee, never a cut. ForwardTCG is a fixed monthly add-on. It never takes a percentage of your card sales. See pricing.
TRADE-IN
Offer · 21/09/2026 15:10
Holo rare #041NM
Market ref.12.00
Full art #188LP
Market ref.30.00
Market reference42.00
Cash at 60%25.20
Trade credit at 75%31.50
Cash or credit, not both
Stock added on acceptance
Where it stands
What works today, and what we are still proving.
| Sell singles by game, set, number, rarity, condition, language and finish | Built |
| Each card is ordinary stock, so pricing, stock counts and returns work like the rest of the shop | Built |
| Receipts record the exact card sold, so they still describe it years later | Built |
| Buy cards for cash or trade them for store credit, in the browser till | Built |
| Market prices entered by hand or pulled from JustTCG or PulseTCG with your own API key, with the source kept on each offer | Built |
| A queue for collections still waiting to be priced | Built |
| Cost tracked per purchase, so the margin on each single is real | Built |
| Undo a completed buy or trade, with a reason recorded | Built |
| Graded cards, reserved at the till so they can never be sold twice | Built |
| Pre-orders with deposits | Built |
| League nights and events, with attendance on loyalty fobs | Built |
| Selling and returning the exact card on the SUNMI D3 till | In testing |
| Buying, trading and spending store credit on the Android till | In testing |
| Buying and trading on the Android till with no connection, settled when it comes back | In testing |
| Printed receipts for buys and trades on the Android till | In testing |
| Tournament registration | Planned |
Run a card shop? Try it at your counter.
ForwardTCG switches on from your back office, and it is not charged while it is in early access.
Modules
One platform, shaped to your trade.
Modules add the screens, records and workflows a particular kind of business needs, on top of the same till, back office, payments and reporting. All five are in early access: you can switch them on from your back office today, they are not charged yet, and each one keeps growing on the same core.
The modules
TCGEarly access
ForwardTCG
Card and hobby shops
- Sell singles by game, set, condition, language and finish
- Buy collections for cash or store credit, at your own rates
- Graded cards, reservations and pre-orders with deposits
- Market prices entered by hand or pulled from JustTCG or PulseTCG
- Coming: tournament registration
£39 / shop / month, not charged yetExplore ForwardTCG
CINEarly access
ForwardCinema
Independent cinemas
- Screens and showtimes, with ticket sales capped at capacity
- Concessions, ticket bundles and complimentary tickets
- Scan tickets at the door, reprint them or refund and release seats
- Stop sales on a showing and block off seats
- Coming: a visual seat map and the Android till screens
Priced at launchAsk about it
HOSEarly access
ForwardHospitality
Pubs, bars and cafés
- A floor plan of tables with covers, guest names and notes
- Open tabs, courses and orders sent to the right kitchen or bar station
- Split the bill evenly or by item, and merge tables
- A waitlist, simple reservations and service or cover charges
- Coming: happy hours and time-based pricing
Priced at launchAsk about it
EATEarly access
ForwardEat
Restaurants and takeaways
- Options and add-ons, meal deals and priced extras
- A kitchen screen with courses, holds and rush orders
- Allergen flags, sold-out items, prep notes and tips
- Eat-in, collection and delivery orders with ready times
- Coming: online ordering and courier dispatch
Priced at launchAsk about it
HTLEarly access
ForwardHotel
Hotels and guest houses
- Rooms and housekeeping status, check-in and check-out
- Guest bills with charges, deposits, transfers and splits
- Do-not-disturb, wake-up calls and rooms out of order
- See which rooms are free on a date, and who is arriving
- Coming: a full reservations diary and a front-desk till
Priced at launchAsk about it
Running something else?
Modules are how ForwardPOS grows into new trades. If your business needs something the core doesn't do, tell us. It may be the next one we build.
Talk to us
How modules work
Specialist where it matters, shared everywhere else.
The same core underneath
Stock, payments, VAT, staff permissions, audit and reporting are shared by every module, so a cinema's popcorn and a card shop's booster packs are counted the same careful way.
Switched on where you need it
Turn a module on for the business, then narrow it to locations or tills. A hotel can run ForwardHotel at reception and ForwardHospitality in the bar, with one set of reports.
Never a separate product
Modules add their own records alongside the core rather than changing it, so every business gets the same updates, the same security and the same till. Disabling a module never deletes history.
Roadmap
What's built, what's next, and what we haven't promised.
Every capability on this site appears here with the same status it carries everywhere else, and we keep the two in step: if a status changes here, it changes there too. Nothing below has a delivery date: the order is our current intention, and intentions move.
Working today
In use by shops now, covered by automated tests. Where a capability depends on particular hardware or a payment provider, it is listed further down instead.
| Basket, VAT per rate, line and order discounts | Forward Register | Built |
| Cash with change and cash drawer | Forward Register | Built |
| Refunds: whole sale, single lines, part quantities | Forward Register | Built |
| Till sessions: float, paid in and out, cash-up | Forward Register | Built |
| Saved servers, e.g. a live shop and a training server | Forward Register | Built |
| Live basket, total and payment status | Forward Display | Built |
| Logo, colours and thank-you message from the back office | Forward Display | Built |
| Idle slides for promotions and events | Forward Display | Built |
| Products, barcodes and prices | Forward Backoffice | Built |
| Product categories for catalogue browse | Forward Backoffice | Built |
| Stock levels, adjustments and a full movement history | Forward Backoffice | Built |
| Settings → Modules: enable vertical modules per business, location or till | Forward Backoffice | Built |
| Sales, voids and receipts | Forward Backoffice | Built |
| Review of offline sales, with price and tax approvals | Forward Backoffice | Built |
| Customers, loyalty fobs, events and attendance | Forward Backoffice | Built |
| Several shops: locations, tills and central pricing | Forward Backoffice | Built |
| Staff roles and an audit log of sensitive actions | Forward Backoffice | Built |
| A virtual till in the browser, for online orders and counter work without a terminal | Forward Backoffice | Built |
| Receipts carrying your shop's name, address, VAT number and your own footer | Forward Backoffice | Built |
| Cash, and a test card for training | Forward Connect | Built |
| Sell singles by game, set, number, rarity, condition, language and finish | ForwardTCG | Built |
| Each card is ordinary stock, so pricing, stock counts and returns work like the rest of the shop | ForwardTCG | Built |
| Receipts record the exact card sold, so they still describe it years later | ForwardTCG | Built |
| Buy cards for cash or trade them for store credit, in the browser till | ForwardTCG | Built |
| Market prices entered by hand or pulled from JustTCG or PulseTCG with your own API key, with the source kept on each offer | ForwardTCG | Built |
| A queue for collections still waiting to be priced | ForwardTCG | Built |
| Cost tracked per purchase, so the margin on each single is real | ForwardTCG | Built |
| Undo a completed buy or trade, with a reason recorded | ForwardTCG | Built |
| Graded cards, reserved at the till so they can never be sold twice | ForwardTCG | Built |
| Pre-orders with deposits | ForwardTCG | Built |
| League nights and events, with attendance on loyalty fobs | ForwardTCG | Built |
| HTTPS everywhere, private no-store API responses | Hosting and operations | In place |
| Per-shop data isolation, tested by automated cross-shop attacks | Hosting and operations | In place |
| Rate limits, with a much tighter limit on PIN sign-in | Hosting and operations | In place |
| Health and readiness endpoints | Hosting and operations | In place |
| Backups of the server that runs ForwardPOS | Hosting and operations | In place |
Being proven
Written and deployed, and now being tested on real hardware, with a real provider, or in a hosted build that has not yet been promoted. Usable, but we are not calling it finished.
| Barcode scanning, EAN-13, EAN-8, UPC, Code 128 | Forward Register | In testing |
| Inventory browse by category and name on the till | Forward Register | Built |
| Separate till screens when a module is enabled for that till | Forward Register | In testing |
| Offline cash with exactly-once upload | Forward Register | In testing |
| Receipt printing, lookup and reprint | Forward Register | In testing |
| Idle video | Forward Display | In testing |
| Cash position at a glance: opening float, cash sales, refunds, paid-outs and the expected drawer | Forward Backoffice | In testing |
| Staying signed in through a page refresh, with idle and absolute limits | Forward Backoffice | In testing |
| Mollie card payments and card refunds | Forward Connect | In testing |
| WooCommerce stock and order sync | Forward Connect | In testing |
| Selling and returning the exact card on the SUNMI D3 till | ForwardTCG | In testing |
| Buying, trading and spending store credit on the Android till | ForwardTCG | In testing |
| Buying and trading on the Android till with no connection, settled when it comes back | ForwardTCG | In testing |
| Printed receipts for buys and trades on the Android till | ForwardTCG | In testing |
| ForwardEat: kitchen screen, options and add-ons, courses and order types | ForwardEat | Early access |
| ForwardHospitality: table plan, tabs, waitlist, reservations and bill splitting | ForwardHospitality | Early access |
| ForwardCinema: showtimes, ticket sales, door scanning and seat holds | ForwardCinema | Early access |
| ForwardHotel: rooms, housekeeping, guest bills and arrivals | ForwardHotel | Early access |
Next up
What we intend to build next. No dates, and the order can change if a shop tells us something else matters more.
| Tournament registration | ForwardTCG | Planned |
| A visual seat map, a film catalogue and Android till screens | ForwardCinema | Planned |
| A full reservations diary and a front-desk till | ForwardHotel | Planned |
| Online ordering and courier dispatch | ForwardEat | Planned |
| Happy hours and time-based pricing | ForwardHospitality | Planned |
| Independent database backups held off the server | Hosting and operations | Planned |
| A restore procedure that is actually tested, not just written down | Hosting and operations | Planned |
| Central monitoring and alerting | Hosting and operations | Planned |
After that
Wanted, understood, and behind the work above. Ask if one of these is the thing standing between you and a decision.
| Suppliers, purchase orders and goods-in | Forward Backoffice | Planned |
| Margin and category reporting | Forward Backoffice | Planned |
| Shopify | Forward Connect | Planned |
| Accounting exports | Forward Connect | Planned |
| Published uptime and support hours | Hosting and operations | Planned |
| Outbound webhooks for sales, refunds and stock changes | Developer API | Planned |
| Stock levels and adjustments for integrations | Developer API | Planned |
| Customers and loyalty for integrations | Developer API | Planned |
| API keys scoped to a single integration | Developer API | Planned |
Exploring
Under consideration. Nothing has been designed and nothing is committed.
| Browser or tablet displays for other hardware | Forward Display | Planned |
| Stripe Terminal and Revolut | Forward Connect | Planned |
Modules
Specialist trades are served by optional modules on the same core. All five can be switched on today in early access, and none is charged yet. See the modules page for what each one can do today.
| ForwardTCG — Trading cards and hobby shops | Early access |
| ForwardCinema — Tickets, seats and concessions | Early access |
| ForwardHospitality — Pubs, bars and cafés | Early access |
| ForwardEat — Restaurants and takeaways | Early access |
| ForwardHotel — Front desk and guest charges | Early access |
Pricing
At least 20% under the till it's most like.
Plans are monthly, with no contract and no cut of your card takings. Each plan sits at least 20% below the nearest like-for-like plan from Lightspeed Retail, the closest match for stock control, web-shop sync, several shops and an API.
First month £1 with the code NEW1POUND, for new customers. Your whole first month costs £1 excluding VAT (£1.20 with VAT), whichever plan, shops and tills you choose. From the second month your normal plan price applies, monthly with no contract, and you can cancel before then in the billing portal.
Prices exclude VAT. Early access shops are onboarded individually, so talk to us before you plan a switchover.
Essentials
One shop, one till
£59/ month
vs Lightspeed Basic £75 · 21% less
- Till, customer display and back office
- Products, barcodes and a stock ledger
- Cash, card via your provider, refunds
- Offline cash with exactly-once upload
- Your branding on screen and receipt
- Receipt lookup and reprint
- Email support
SUBTOTAL59.00
VAT 20%11.80
TOTAL70.80
Get started
MOST SHOPS
Retail
A busy shop, up to three tills
£119/ month
vs Lightspeed Core £149 · 20% less
- Everything in Essentials
- Up to 3 tills
- Till sessions, paid in and out, cash-up
- Customers, loyalty fobs and events
- Offline sale review and approvals
- Staff roles and an audit log
- WooCommerce stock sync (in testing)
- Phone and email support
SUBTOTAL119.00
VAT 20%23.80
TOTAL142.80
Get started
Multi-store
Per shop, for two or more
£149/ shop / month
vs Lightspeed Plus £189 · 21% less
- Everything in Retail, in every shop
- Up to 3 tills per shop
- Central pricing across shops
- Shop and till management in one place
- API access for your own integrations
- Shopify sync (planned)
- A named contact
SUBTOTAL149.00
VAT 20%29.80
TOTAL178.80
Get started
+ available now · ~ in testing or planned, included in the plan when it ships
Add-ons
Only pay for what your shop uses.
Extra till
£19 / till / month
Add tills beyond your plan's limit, at the same shop.
Modules
£39 / shop / month for ForwardTCG
A flat fee, never a percentage of sales. Every module is in early access and not charged yet; we will agree a start date with you in writing first. The others are priced at launch. See modules.
Hardware
Quoted or bring your own
D3 Pro terminals, scanners and drawers sourced and set up for you, or use a compatible SUNMI you own.
Card payments: you sign up with a supported provider and pay their rate directly. ForwardPOS adds nothing on top of it, on any plan.
How we compare
Where our prices come from.
We price against the closest like-for-like product rather than the cheapest headline. Some tills cost less on paper, and here's what's different about them.
| Product | Plan | Per month | What to know |
|---|---|---|---|
| ForwardPOS | Essentials / Retail / Multi-store | £59 / £119 / £149 | No contract. No cut of card takings. Offline cash included on every plan. |
| Lightspeed Retail | Basic / Core / Plus | £75 / £149 / £189 | The closest match on inventory, web-shop sync, several shops and an API. Extra registers cost more. Card rates are quoted individually. |
| Square for Retail | Free / Plus | £0 / £49 | Plus mainly lowers the in-person card rate, from 1.75% to 1.6%. Tied to Square's own payments. |
| Epos Now | Standard / Premium | ~£25 / ~£39 | Lower monthly fee, but contracts typically run 24 to 36 months, with app add-ons charged extra. |
| TCG Sync | Storefront Pro | 2% of TCG sales | A specialist card-shop platform, with a US$1,000 setup fee. Compare with ForwardTCG's flat £39. |
Competitor prices were checked in September 2026 from published reviews and vendor pages, and may exclude VAT or change without notice. Check with each provider before deciding. Sources: Lightspeed, Square, Epos Now, TCG Sync.
How does the £1 first month work?
Enter the code NEW1POUND when you sign up and your whole first monthly invoice is £1 excluding VAT — £1.20 on a UK invoice at 20% — whichever plan you pick, however many shops and extra tills you have. It is a paid first month, not a free trial, so you have a working account from day one. Your normal plan price then applies from the second invoice. Checkout shows you that price and the renewal date before you confirm, and you can cancel before it through the billing portal. The offer is for new customers and cannot be added to an existing subscription.
Do the prices include VAT?
No. All prices exclude VAT. Each plan's receipt shows the total with UK VAT at 20% added.
Is there a contract?
No. Plans are billed monthly and you can cancel whenever you like. Your products, customers and sales history belong to you.
Can I use ForwardPOS today?
ForwardPOS is in early access. It is running on real hardware at our first shop, and some features are still being proven, each one marked on the platform page. Choose a plan to create your account, verify your email and subscribe with Stripe. Your back office is created after payment is confirmed.
What do card payments cost?
Whatever your payment provider charges you. You hold the account and the relationship with them, and ForwardPOS adds no fee on top.
What happens if my internet goes down?
A prepared till keeps taking cash and saves each sale on the device, then uploads it exactly once when the connection returns. Card payments need a connection, because only the provider can confirm them.
Can I run it on my own server?
Not yet. ForwardPOS is hosted by us today. A self-hosted option for larger and multi-site retailers is planned; see hosting.
Hosting
We run it for you, and your tills keep trading if we can't be reached.
ForwardPOS is a hosted service: we run the servers, the database and the updates. Because each till keeps what it needs to take cash locally, a dropped connection slows your reporting down, not your queue.
Where ForwardPOS runs
ForwardPOS Cloud
Available in early accessThe standard way to run ForwardPOS. Included in every plan.
- Run by Network Heroes on infrastructure we operate: the servers, the PostgreSQL databases and every update.
- Cloudflare carries public traffic to the service and helps protect it against attacks.
- Production and staging run separately, each with its own private database.
- HTTPS only. Tills refuse to talk to a hosted ForwardPOS address over plain HTTP.
- Every response is marked private and never cached, so no shared cache can hand one shop's data to another.
- A separate training server your staff can switch to from the till's sign-in screen.
- Health and readiness endpoints, so uptime checks see the database as well as the web server.
Self-hosted
PlannedFor larger and multi-site retailers who need the platform on their own infrastructure. Not priced yet, so talk to us if it matters to you.
- The same Forward Core, shipped as containers, with a Docker Compose setup for smaller installs.
- Runs on your own PostgreSQL, behind your own HTTPS certificate.
- Tills connect through the saved-servers list, so a device can move between your server and ours.
- Needs outbound internet for card providers and web-shop sync.
Public HTTPS traffic from tills and browsers reaches Forward Core through Cloudflare.
Before general availability
What we're committing to, and where it stands.
These are the operating standards ForwardPOS Cloud must meet before it leaves early access. We'll publish status here as each one is met.
| Standard | Status |
|---|---|
| HTTPS everywhere, private no-store API responses | In place |
| Backups of the server that runs ForwardPOS | In place |
| Per-shop data isolation, tested by automated cross-shop attacks | In place |
| Rate limits, with a much tighter limit on PIN sign-in | In place |
| Health and readiness endpoints | In place |
| Independent database backups held off the server | Planned |
| A restore procedure that is actually tested, not just written down | Planned |
| Central monitoring and alerting | Planned |
| Published uptime and support hours | Planned |
Technical specification
How ForwardPOS is built, and why.
For IT leads, auditors and anyone who'd rather read the design than the brochure. This describes the system as it's built today. Where something is planned rather than built, we say so.
Architecture
ForwardPOS is multi-tenant software as a service. One platform serves every retailer, and each retailer's data is isolated from every other's. Data belongs to a hierarchy of tenant → organisation → location → register, and stock belongs to a location.
There are five parts. Forward Core is the central API and the single source of truth for products, prices, stock, sales and payments. Forward Register is the native Android till. Forward Display is the customer screen, driven by the till. Forward Backoffice is the browser-based management app. Forward Connect is the integration layer for payment providers and web shops, each behind a fixed interface so it can be swapped.
Specialist trades are served by optional vertical modules: ForwardTCG, ForwardCinema, ForwardHospitality, ForwardEat and ForwardHotel. Each is switched on in Settings → Modules. Modules carry their own data on sale lines or domain records and never add trade-specific rules to the core.
Technology
- Till
- Kotlin, Jetpack Compose and Hilt on Android. Tested first on SUNMI OS.
- Customer display
- Android's Presentation API on the terminal's second screen, with system bars hidden.
- Core API
- NestJS 10 on Node.js, in strict TypeScript. Request validation rejects unknown fields rather than ignoring them.
- Database
- PostgreSQL 18 through Prisma 6, with versioned migrations. Production and staging each have their own private database.
- Back office
- React with Vite.
- Shared domain
- One TypeScript package for pricing, VAT, stock and permission rules, used by the core and the back office.
- API
- REST and JSON, versioned in the path (
/v1), with an OpenAPI description. - Packaging
- A pnpm monorepo. The backend can run in containers, with Docker Compose for local development.
- Hosting
- The website, the production service and the staging service run as separate container applications, deployed with Coolify on infrastructure Network Heroes operates. Public traffic reaches them through Cloudflare Tunnel.
Money and VAT
- All money is held as whole minor units (pence), never as floating-point numbers. Every amount is stored alongside its currency.
- VAT is worked out per rate and rounded once per rate, so net plus VAT always equals the total exactly. VAT-inclusive and VAT-exclusive pricing are both supported.
- The till sends what it scanned and the total it expects. Core re-prices the basket from its own catalogue and rejects the sale if the totals differ. It never silently corrects the till's figure.
- Each sale line keeps the name, SKU, price and VAT rate it was sold at, so historical receipts never change when a product does.
- A receipt taken in one currency is never committed in another, even if the shop's settings change later.
Tenancy and security
- The tenant comes from the verified access token, never from a value the client sends. Database access is scoped automatically and fails closed: a query with no tenant context is refused.
- Automated tests actively attempt to read and write across shops, and must fail to.
- Permissions are specific actions, such as
sale:void,sale:refund,sale:price-overrideandinventory:adjust, grouped into default roles: cashier, supervisor, manager and administrator. - Passwords and PINs are hashed with Argon2. PINs are 4 to 8 digits, and PIN sign-in is limited to 10 attempts a minute.
- Refresh tokens rotate on every use. Presenting one that has already been used is treated as theft and signs that user out everywhere.
- Security headers are set by Helmet, cross-origin access uses an explicit allow-list, request bodies are capped, and no response is ever shared between users through a cache.
- No payment card data is stored. Only provider references are.
Offline and sync
Every sale is given a globally unique ID by the till, and that ID doubles as its idempotency key. Replaying a sale returns the original result. Replaying the same ID with different content is refused as a conflict. Sales and payments commit in serialisable database transactions, and two identical retries racing each other still produce one sale and one stock movement.
A till that has been prepared for offline use can accept cash without a connection. Each offline receipt is written to durable storage before the till reports success, and keeps its original sale and payment keys for its eventual upload. If the server rejects a receipt, for a changed price, a changed VAT rate or a stock shortage, the receipt stays on the till and is reported to the back office for a manager to review. It is never rewritten to make it fit.
Card payments are never taken offline. Only the payment provider can confirm a card payment, so the till won't pretend otherwise.
Inventory
Stock is a ledger. Every change is a movement recording the shop, product, quantity, type, reference, the person or system responsible, and the time. The current quantity is a cached total of those movements, so a number can always be explained. Movement types include sale, refund, void, adjustment, offline review corrections and stock allocated to web orders. Each shop decides whether its tills may sell into negative stock.
ForwardPOS is the stock master. Web shops are sales channels that receive its figure, and inbound web orders reduce it through the same ledger. Sync is idempotent to prevent loops.
Payments
Payment providers implement one interface: create a payment, check its status, cancel, refund, and verify webhooks. A sale is marked paid only when the provider confirms it, never because the till asked. Payment requests need a stable retry key, and the balance is reserved before a provider is contacted, so two taps can't take two payments.
A payment in an uncertain state is never voided or restocked just because it is old. The provider is asked first. Webhooks are verified against the exact bytes the provider sent.
- Cash
- Built: tender, change, drawer and cash-up
- Test card
- Built: a simulated card for training and demos
- Mollie
- In testing: payments and card refunds
- Stripe, Revolut
- Planned
Hardware
The till reaches hardware through a HardwareProvider abstraction with a small set of abilities: print a receipt, open the drawer, read barcodes, drive a customer display and report device information. The SUNMI implementation is the first. Capabilities are detected on the device rather than assumed. USB HID scanners are read at the activity level, so a scan registers without a focused text field and typed input is never swallowed.
Audit and logging
Sensitive actions are written to a protected audit log with the shop, user, till, action, affected record, time and relevant before and after values. That covers sign-in, refunds, discounts, price overrides, stock adjustments, drawer opens, voids and changes to staff, permissions, integrations and settings. Application logs are structured and carry request IDs. Passwords, payment secrets and card data are never logged.
Testing
- Unit tests for money, VAT, discounts, refunds, change and stock rules.
- Database integration tests against an isolated test database, covering idempotency, concurrency, offline replay, approvals and cross-shop isolation.
- Android unit tests for checkout, offline queue retention, sign-in and scanner input.
- Written acceptance procedures for anything that needs a physical device, such as the printer, drawer, customer display and offline operation.
Developers · API v1 preview
The same API the till uses.
Forward Register, Forward Backoffice and your own integrations all call one versioned REST API. If the till can do something, it goes through a documented endpoint with the same permission checks.
Preview v1 is in early access and may still change before general availability. API access is included in the Multi-store plan. This page covers the core integration surface: catalogue, sales, payments and refunds.
Base URL and versioning
Your base URL is given to you when your account is set up. The version is part of every path, so /v1 keeps working after /v2 exists. A till estate can't all be upgraded at the same moment, and the API is designed around that.
# every request
https://{your-forwardpos-server}/v1/...
Authorization: Bearer {accessToken}
Content-Type: application/json
An OpenAPI description is available for development and training servers. It isn't exposed on live servers by default, because a complete map of a retail API helps attackers more than it helps integrators. Ask us if you need it.
Authentication
Sign in to get a short-lived access token and a refresh token. Staff and integration users sign in with an email and password. A till signs in with its register code and an operator's PIN, and its session is bound to that register.
Your shop is identified by the token itself. Any shop or tenant ID you send is ignored, and a token can never read another shop's data.
Refresh tokens rotate: each refresh returns a new pair and retires the old refresh token. Presenting a retired refresh token is treated as theft and signs that user out everywhere, so store the newest one and never replay an old one.
Conventions
- Money
- Integers in minor units:
4999is £49.99. Field names end inMinor. There are no decimals anywhere. - IDs
- UUIDs. For sales, the client creates the ID, which lets a till work offline.
- Idempotency
- A sale's ID is its idempotency key. Payments and stock adjustments need an
Idempotency-Keyheader. A retry with the same key and body returns the first result. The same key with a different body gets409. - Validation
- Unknown fields are rejected, not ignored, so a typo can't silently do nothing.
- Server authority
- Totals, VAT and payment state are always calculated by the server. The client says what it expects so a mismatch can be caught, never adopted.
- Modules
- Module details sit under
moduleData.<moduleId>or in the module's own records. Enabling a module never grants permissions; disabling never deletes history. - Time
- ISO 8601 timestamps.
transactedAtis when the sale happened, which for an offline sale can be long before it uploaded. - Caching
- Every response is
Cache-Control: private, no-store. Don't cache responses in shared proxies.
Errors and limits
Errors are JSON with a statusCode and a human-readable message written to be shown to staff.
| Status | Meaning |
|---|---|
| 400 | The request failed validation, for example an unknown field or a non-integer amount. |
| 401 | No token, or an expired one. Refresh and retry. |
| 403 | Signed in but not allowed. The message names the missing permission. |
| 404 | Not found in your shop. Other shops' records are indistinguishable from missing ones. |
| 409 | A conflict, such as an ID reused with different content or a payment whose outcome isn't known yet. |
| 422 | Understood but refused, such as a total that doesn't match the server's calculation or stock the shop won't sell below zero. |
| 429 | Rate limited. Wait for the Retry-After interval. |
Limits: 300 requests a minute by default, 30 a minute for token refresh, and 10 a minute for each sign-in endpoint.
Auth
POST
/v1/auth/passwordpublic · 10/minSign in with an email and password.
| tenantSlug | string | Your account's short name. |
| string | The user's email address. | |
| password | string | 8 to 256 characters. |
// 200 { "accessToken": "eyJhbGciOi...", "refreshToken": "r1_9f2c...", ... }
POST
/v1/auth/pinpublic · 10/minA till signs in an operator with the register code and a 4 to 8 digit PIN. The session is bound to that register, and sales can only be committed for it.
POST
/v1/auth/refreshpublic · 30/minSwap a refresh token for a new access and refresh pair. The old refresh token stops working.
POST
/v1/auth/logoutpublicRevoke a refresh token. Returns 204.
Registers
Register-bound sessions (PIN sign-in) call these with me resolved from the token, never from a path parameter.
GET
/v1/registers/me/configregister sessionConfiguration and branding for this till, including enabledModules / modulesVersion after a safe refresh boundary (empty basket, no pending payment).
POST
/v1/registers/me/heartbeatregister sessionReport that the register is alive. Optional x-forwardpos-app-version and x-forwardpos-device headers.
POST
/v1/registers/me/offline-reportregister sessionSubmit an offline trading report for review in the back office.
Catalogue
Shared inventory foundation: products, barcodes, categories and till browse. Modules extend products via moduleData rather than parallel catalogues.
GET
/v1/products/barcode/{barcode}product:readLook up a product by barcode. This is the scan path, matched exactly on the barcode string, so a retailer's own labels work as well as EAN codes.
GET
/v1/products/categoriesproduct:readList catalogue categories for till inventory browse.
GET
/v1/products?q={text}&categoryId={id}&limit={n}product:readBrowse or search the catalogue. Optional categoryId filters by category. Responses include stock and, where relevant, module variant hints (e.g. hospitality bottle pour quantity).
GET
/v1/products/sync?since={timestamp}&cursor={cursor}product:readPull the catalogue in pages, or only what changed since a time. Tills use this to fill their offline cache. Follow the returned cursor until there are no more pages.
POST
/v1/products/{productId}/barcodesproduct:barcode:associateAttach another barcode to an existing product, for example when a supplier changes packaging.
Sales
A sale is committed first, which moves stock, and paid second. It is only complete when a payment provider has confirmed payment.
POST
/v1/salessale:createCommit a basket. Send what was scanned and the total you expect. The server prices it from your catalogue and refuses it with 422 if the totals differ. Discounts need sale:discount:line or sale:discount:order, and a unit price different from the catalogue needs sale:price-override.
Request
{
"id": "6f1c2a4e-8b1d-4c1e-9d7a-2a3b4c5d6e7f", // your UUID, also the idempotency key
"registerId": "b3e0...",
"transactedAt": "2026-09-21T14:32:05Z",
"lines": [
{ "id": "c9a1...", "productId": "2d7f...", "quantity": 2 },
{ "id": "e04b...", "productId": "91ac...", "quantity": 1 }
],
"expectedTotalMinor": 3048
}
Response 201
{
"id": "6f1c2a4e-8b1d-4c1e-9d7a-2a3b4c5d6e7f",
"saleNumber": "TILL01-000419",
"status": "PENDING",
"subtotalMinor": 3048, "discountMinor": 0,
"netMinor": 2540, "taxMinor": 508, "totalMinor": 3048
}
| lines | 1–500 | Each has id, productId, quantity (1–10,000), and optionally discountMinor, discountBasisPoints, discountReason and unitPriceMinor. |
| orderDiscountMinor | integer | Optional. Or orderDiscountBasisPoints. |
| customerId | uuid | Optional. Attaches a customer. |
| tillSessionId | uuid | Optional. Must be an open session on this register. |
| wasOffline | boolean | Set by tills replaying an offline sale. |
GET
/v1/sales/{saleId}sale:createThe sale's current status and totals. Use this to settle an uncertain outcome instead of guessing.
POST
/v1/sales/{saleId}/voidsale:voidAbandon an unpaid sale and return its stock, with a reason. Voiding twice returns the same voided sale without restocking again. Returns 422 if a payment has settled (refund it instead) and 409 if a payment's outcome isn't known yet.
Payments
POST
/v1/sales/{saleId}/paymentssale:create · Idempotency-KeyTake a payment against a committed sale. The amount is reserved before the provider is contacted, so two identical taps can't take two payments. For cash, send tenderedMinor and the change is worked out for you.
// Idempotency-Key: 0e5b7c1a-... { "provider": "cash", "amountMinor": 3048, "tenderedMinor": 5000 } // 201 { "id": "a41f...", "provider": "cash", "state": "PAID", "amountMinor": 3048, "changeMinor": 1952 }
state is one of PENDING, PAID, FAILED, EXPIRED or CANCELLED. A card payment starts as PENDING and is only PAID once the provider confirms it.
POST
/v1/sales/{saleId}/payments/{paymentId}/confirmsale:createAsk the server to check a pending payment with its provider. The answer comes from the provider, never from the client.
Payment providers notify ForwardPOS through signed webhooks, which are verified against the exact bytes sent. These endpoints are for providers, not integrators.
Refunds
Refunds are prepared, then confirmed, so a refund is never half-done. Card refunds go back through the original provider. Every refund needs sale:refund.
GET
/v1/refunds/lookup?receipt={saleNumber}sale:refundFind the original sale from its receipt number to start a refund.
POST
/v1/refundssale:refundPrepare a refund of whole or part lines. Nothing moves until it's confirmed.
POST
/v1/refunds/{id}/confirmsale:refundComplete a prepared refund. Stock returns through the ledger.
POST
/v1/refunds/{id}/cancelsale:refundAbandon a prepared refund.
Health
GET
/healthpublicIs the process alive? Doesn't touch the database, so a brief database blip can't cause a restart storm.
GET
/readypublicCan it serve traffic? Checks the database, and returns 503 if it can't reach it.
Modules
ForwardTCG, ForwardCinema, ForwardHospitality, ForwardEat and ForwardHotel are in early access, and their endpoints are still settling. Rather than publish routes that may change, we share the module reference directly with integrators who need it. Ask us for it.
What you can rely on now: where a module adds details to a sale line, they sit under moduleData.<moduleId> rather than in new core fields. Switching a module on never grants a staff permission, and switching it off never deletes a record.
Coming next
| Outbound webhooks for sales, refunds and stock changes | Planned |
| Stock levels and adjustments for integrations | Planned |
| Customers and loyalty for integrations | Planned |
| API keys scoped to a single integration | Planned |
Back-office routes, such as fleet settings, owner exports, billing, signup and module set-up, are not part of the public reference.
Get started
Your shop. Your ForwardPOS.
Choose your plan, verify your email and set up your business. Subscribe securely with Stripe, then head straight into your own back office.
First month £1 with the code NEW1POUND, for new customers. Your whole first month costs £1 excluding VAT (£1.20 with VAT), whichever plan, shops and tills you choose. From the second month your normal plan price applies, monthly with no contract, and you can cancel before then in the billing portal.
Online signup is not open yet. Tell us the plan and the size of your shop and we will set you up by hand, usually the same working day. The buttons below write the email for you.
Choose where to start.
Monthly, with no contract and no cut of your card takings. Multi-store is priced per shop. You can change plan later by asking us.
Essentials
£59/ month
One shop and one till, with the core tools for your counter: checkout, customer display, products, stock and offline cash.
Retail
£119/ month
One busy shop with up to three tills, adding customers, shop management and the reporting a busy counter needs.
Multi-store
£149/ shop / month
For two or more shops, with up to three tills each and one place to run stock, pricing and staff across them.
Size it up
Tell us how many shops and tills you need. Your answers travel with you into signup, and nothing here is final — ask us and we will move you.
£59 per month, excluding VAT
Continue to signup
Prices exclude VAT. Add extra tills for £19 each per month. Stripe shows tax and the final recurring total before you subscribe. Hardware and shop payment-provider fees are separate. Compare the plans in full.
From signup to your first sale.
- Verify your emailA short code confirms your account belongs to you.
- Make it yoursSet your business name, choose your plan and tell us how many shops and tills you need.
- Subscribe securelyPay through Stripe. Your card details stay with Stripe.
- Open your back officeReview VAT settings, add products, configure shop payments and pair your till.
Modules are in early access.
ForwardTCG, ForwardCinema, ForwardHospitality, ForwardEat and ForwardHotel can be switched on from your back office today. None of them is on your bill yet, and we will agree any start date with you in writing first. See the modules.
Already trading with us?
Sign in to pick up where you left off. Open your back office
Something not right, or not sure which plan fits? Email [email protected] and a person will answer.
ForwardPOS is in early access. Hardware and provider acceptance testing is ongoing; see the platform details for current availability.
Legal
Privacy notice
How Network Heroes Ltd uses information about visitors to this site, businesses with a ForwardPOS account, and people who contact us.
ForwardPOS is provided by Network Heroes Ltd, registered in England and Wales with company number 15467032 (VAT registration GB475910664). Registered office: Blackpool Enterprise Centre, Lytham Road, Blackpool, Lancashire, England, FY4 1EW. For support and privacy enquiries, email [email protected].
Who this notice covers
This notice explains our use of information about website visitors, business account holders and people who contact us. A shop using ForwardPOS is responsible for explaining its own use of customer, staff, loyalty and event-attendance information. Where we host that information on its instructions, we do so under a separate data-processing agreement with that shop.
Information we use
Account setup includes your email address, name, business details, VAT status, selected plan and shop/till allowances. We store password hashes, verification records, subscription references and account activity. Support messages and technical records may include contact details, IP addresses, timestamps and error information. Only provide information needed for your request.
Why we use it
We use account and subscription details to set up and administer the service you request. Where you contract personally, this supports that contract; where you act for a company, our basis is our legitimate interest in administering that business relationship. Security and operational records support our legitimate interests in protecting accounts, investigating faults and preventing misuse. Statutory financial records are retained to meet applicable legal obligations. Signup is not consent to marketing. You can ask support to review an account restriction or billing error.
Service providers
Stripe handles ForwardPOS subscription checkout and billing. Card entry takes place in Stripe's hosted checkout; ForwardPOS receives billing references and payment/subscription status. Maileroo sends the emails that verify your address at signup, so it receives your email address and the content of those emails.
This website and the ForwardPOS service run on server infrastructure operated by Network Heroes Ltd, and their databases are held there. Cloudflare sits in front of them: requests to this website and to the ForwardPOS service pass through Cloudflare's network, which delivers them to our servers and helps protect the service against attacks and misuse. To do this, Cloudflare handles connection details such as your IP address, the details of each request, and the information passing between your browser or till and our servers.
Until 13 October 2026, the ForwardPOS service and this website were hosted by SiteGround. Public traffic now goes to our infrastructure. The earlier SiteGround deployment and its data are temporarily retained so that we can reverse the move if we need to.
Storage and retention
Verification codes expire after ten minutes and signup credentials expire after 24 hours. Expiry does not mean the underlying signup record has been deleted. We assess retention against the purpose of each record, legal obligations and unresolved disputes. Incomplete signup records are needed only to complete or investigate signup and prevent abuse; support records are needed to resolve enquiries and relevant disputes; operational logs are needed to investigate faults and security incidents. Information no longer needed for those purposes will be deleted or anonymised.
Merchant data is scheduled for deletion 60 days after the paid subscription ends following cancellation, or 60 days after the seven-day payment grace period ends following non-payment. The verified account owner may request an export during that period. A timely export request pauses deletion of the requested data until it has been supplied and there have been at least seven days to retrieve it. Earlier deletion may be requested subject to legal requirements. Our own billing records and evidence needed for legal obligations or a dispute may be retained separately. Restricted backup copies expire through rotation; deletion instructions are reapplied after a restore.
Cookies and browser storage
This website remembers your light/dark theme in browser storage. It sets no cookies of its own, carries no analytics or advertising, and serves its own fonts. Opening a page here involves Cloudflare, which carries the request to us as described above, and our own server, which keeps standard request logs (IP address, time, page requested and browser details) to run and secure the site. No other company is contacted. The signup application uses browser session storage for its signup credential. Stripe and other services may use their own storage when you visit their pages.
Your choices and rights
Depending on the circumstances, you may request access, correction, erasure, restriction or portability of your information, or object to its use. Where processing relies on consent, you may withdraw it. Some information is needed to create and bill an account; without it we cannot complete signup. For a shop's records, contact that shop first. For information controlled by Network Heroes Ltd, email [email protected] using the contact link above.
You can also raise concerns with the Information Commissioner's Office.
Changes
This notice is version 1.2 and takes effect on 13 October 2026. It records that ForwardPOS and this website moved from SiteGround to infrastructure operated by Network Heroes Ltd, with Cloudflare carrying and protecting traffic, and that Maileroo now sends verification emails. Version 1.1 took effect on 24 September 2026 and recorded that the site no longer loads fonts from Google; version 1.0, of the same date, said it did. Earlier versions are available from support. We will explain material changes to how information is used before they take effect, and the version and date above will change with them.
Legal
Subscription terms
The terms of a ForwardPOS subscription bought for business use: what your plan includes, how billing and cancellation work, and where responsibility sits.
ForwardPOS is provided by Network Heroes Ltd, registered in England and Wales with company number 15467032 (VAT registration GB475910664). Registered office: Blackpool Enterprise Centre, Lytham Road, Blackpool, Lancashire, England, FY4 1EW. For support and privacy enquiries, email [email protected].
Business use and your order
These terms cover ForwardPOS subscriptions bought for business use. The person ordering must have authority to act for that business. Review the selected plan, locations, extra tills, monthly price and tax before confirming payment. A successful checkout is followed by business-account provisioning; contact support if payment succeeds but access is not supplied.
What your subscription includes
Your order identifies the plan and shop/till allowances. Upcoming modules and features marked planned or coming soon are not included as delivered functionality. Hardware purchases and the payment provider you use to accept your own customers' payments are separate unless expressly included in your order.
Charges and renewal
Subscriptions renew monthly through Stripe. Prices are in pounds sterling, with applicable VAT shown separately at checkout. Essentials is £59 per shop per month with one till; Retail is £119 per shop per month with up to three tills; Multi-store is £149 per shop per month with a minimum of two shops and up to three tills per shop. Extra tills are £19 per till per month. Your checkout confirmation records the amount ordered.
We sometimes offer an introductory price to new customers, such as a discounted first month under a published code. An introductory price applies only to the invoice or period stated when you order, and covers the plan, locations and extra tills on that order. It is a paid introduction rather than a free trial, and VAT is added to the discounted amount at checkout. Your normal plan price resumes automatically on the next invoice. That return to your normal price is not a price increase, so the 30 days' notice below does not apply to it; the discounted amount, the normal recurring price and the renewal date are all shown at checkout before you confirm, and you can cancel before that renewal through the billing portal. An introductory offer applies to a new subscription only and cannot be added to an existing one.
We will notify you by email at least 30 days before increasing your subscription price. The increase will apply from a renewal date after that notice period. You can cancel before that renewal using the billing portal if you do not wish to continue at the new price.
Contact support to request changes to plans, locations or till allowances. Any change requires written confirmation of its price, allowances and effective date before it takes effect.
Cancellation and refunds
You can request cancellation through the account owner's billing portal. Cancellation is scheduled for the end of the current billing period. The portal shows the cancellation date. You can continue using your paid subscription until then. Cancellation does not itself erase business or accounting records.
We do not normally refund unused time when you cancel a monthly subscription. We will correct duplicate or incorrect charges and provide refunds required by law. If we permanently discontinue a paid service before the end of your paid period, we will refund the unused portion. Contact support about billing problems; this policy does not remove remedies for our breach of contract.
Your responsibilities
Keep account access secure and allocate staff permissions appropriately. You are responsible for the accuracy of product, stock, tax and customer records you enter, your sales and returns policies, and notices or permissions needed for your staff and customers. Do not use the service unlawfully, attempt unauthorised access or interfere with other businesses' accounts.
Connectivity, hardware and payments
Offline trading depends on a previously synced and supported terminal. Some actions need connectivity or provider confirmation. Check that queued sales have synchronised and investigate uncertain payment results before collecting payment again. We will confirm the supported devices and payment methods for your setup. ForwardPOS subscription billing does not itself enable card acceptance on your tills.
Service and support
ForwardPOS is currently in early access. Office support hours are Monday to Friday, 09:00–17:00 UK time. Submit support tickets to [email protected]. Tickets receive an initial response by the next working day; a response is not a promise of resolution within that time. Do not rely on roadmap items as commitments to a delivery date.
Maintenance
Advance notice is not required for planned maintenance expected to cause no more than 15 minutes of downtime. For planned downtime longer than 15 minutes, we will provide at least 24 hours of notice for urgent maintenance and at least seven days of notice for non-urgent maintenance.
If an immediate security threat or unplanned incident makes advance notice impracticable, we may act immediately to protect the service and data. We will notify affected account owners as soon as reasonably practicable and provide updates on material disruption.
Availability, backups and recovery
ForwardPOS is an early-access service. Uptime is not guaranteed. Any availability commitment made to us by an infrastructure or network provider, such as Cloudflare, does not constitute a ForwardPOS uptime guarantee. We operate the infrastructure that runs ForwardPOS, keep backups of it, and will use reasonable care when maintaining and recovering hosted data. We do not promise a fixed recovery time or that every change since the last usable backup can be recovered.
Customers may also keep their own backups using the export or backup features included in their ForwardPOS plan. Keep independent copies of business records you need to retain. This does not remove our own data-protection or contractual responsibilities.
Failed payments and suspension
A failed subscription payment has a seven-day grace period from the first failed collection of that payment to allow it to be corrected. Further retries do not restart this period. We will notify the account owner of the failure. If payment remains unpaid when the grace period ends, we may suspend trading access. Contact support or update the payment method in the billing portal to resolve the balance. We will restore access once payment and any separate security issue are resolved, provided the data has not been deleted.
We may also restrict access where reasonably necessary to address unlawful use, a serious breach of these terms or a material security threat. Where safe and lawful, we will explain the reason and allow a reasonable opportunity to remedy it. Restrictions will be proportionate. You may ask support to review a suspension.
Data access and deletion after closure
Merchant data is scheduled for deletion 60 days after the paid subscription ends following cancellation, or 60 days after the seven-day payment grace period ends following non-payment. During that period, the verified account owner may request a standard export through support without renewing the trading subscription or purchasing an additional backup feature. Trading access and export access are separate. We will send a reminder at least seven days before scheduled deletion. If you request an export before the deadline, we will not delete the requested data until it has been supplied and you have had at least seven days to retrieve it.
You may instruct us to delete merchant personal data sooner, subject to applicable law and identity checks. Once deletion is complete, recovery is not promised. Restricted backup copies will expire through the backup rotation and will not be used for ordinary operations; if a backup is restored, applicable deletion instructions will be reapplied. We may retain our own billing records or limited evidence required by law or an unresolved dispute, separately from merchant operational data.
Your data and our software
Your business retains its rights in data it supplies. Network Heroes Ltd retains its rights in ForwardPOS software and branding. Where we process merchant personal data, we do so under an agreed data-processing agreement covering our instructions, confidentiality, security, subprocessors, incident assistance and the return or deletion of data.
Early access, warranties and liability
ForwardPOS is supplied as an early-access product. We offer no voluntary warranty that the service will be uninterrupted, error-free or suitable for every business requirement. We do not guarantee uptime. This does not remove our express commitments elsewhere in these terms or any rights or liabilities that cannot lawfully be excluded or restricted. In particular, nothing in these terms excludes or limits liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation. These terms do not impose an additional financial cap on liability; responsibility for loss is determined under applicable law.
Ending the service, disputes and changes
We may end the service for a material breach that is not remedied within 14 days of written notice, or immediately where continued provision would be unlawful or present a serious security risk. We may discontinue the service for other reasons with at least 30 days of notice. The refund and data-export provisions above continue to apply as appropriate.
Contact [email protected] first about a complaint so we can investigate and seek a resolution. These terms are governed by the law of England and Wales, whose courts have jurisdiction. Nothing prevents either party seeking urgent relief or exercising rights that cannot lawfully be restricted.
We send contractual notices to the account owner's registered email address; keep it current. We will give at least 30 days of notice of material changes to these terms, with the opportunity to cancel before they apply. Changes required sooner by law or to address an immediate security risk will be explained as soon as reasonably practicable. Changes will not retrospectively remove accrued rights.
This version
These terms are version 1.2 and take effect on 13 October 2026. Version 1.2 replaces the reference to SiteGround's backup facilities, now that we operate the infrastructure that runs ForwardPOS ourselves. It does not change your rights, your price or our other commitments. Version 1.1 took effect on 25 September 2026, and earlier versions are available from support.