POS · Portsmouth

Your harbour ferry and visitor-attraction tills run on Square, and none of them know the tide times

The short answer

A custom POS system for Portsmouth waterfront, ferry, or visitor-attraction operators runs £35,000 to £95,000 over 3 to 6 months. Square, Toast, and Clover sell a coffee fine. They don't understand a ferry crossing with timed capacity, a dockyard attraction with timetabled entry, or a harbour business whose selling is governed by tides and sailings.

Your tills sell tickets, food, and retail across the waterfront, but the thing that actually governs the sale, the next sailing, the timed-entry slot, the capacity left on a crossing, lives outside Square in a separate booking sheet. So a staff member sells a ferry ticket without knowing the crossing is full, or a visitor attraction oversells a timed slot, and the till and the timetable never reconcile.

Square, Toast, and Clover are built for a counter where you ring up whatever the customer wants. They have no concept of timed capacity, multi-venue waterfront operations, or selling tied to sailings and tide-dependent schedules. For a Portsmouth harbour operator, the POS isn't just a till; it's the point where the timetable, capacity, and money have to meet.

Where the off-the-shelf tools fall short

  • Ferry and timed-entry capacity lives outside Square, so staff sell slots that are already full
  • Multi-venue waterfront operations (ferry, attraction, retail, food) run on disconnected tills
  • Tide and sailing schedules govern selling but the POS has no idea they exist
  • Reconciling till takings against bookings and capacity is a manual end-of-day chore
£95k
top-end custom POS
3 to 6 mo
timeline
0
oversold crossings
one
source for online and on-site

Custom pos: what Portsmouth teams actually get

A custom POS ties selling to your real operation: it knows the next sailing, the capacity left, the timed-entry slots, and the tide-dependent schedule, so staff can't oversell a full crossing or a booked slot. Ferry, attraction, retail, and food run as one connected system, and takings reconcile against capacity automatically instead of at the end of a long day.

Build custom when
  • Selling is governed by timed capacity, sailings, or tide-dependent schedules
  • You run multiple waterfront venues on disconnected tills
  • Overselling full crossings or slots is a recurring problem
Buy or configure when
  • You run a single counter with no timed capacity
  • Square or Toast covers your selling without a separate booking sheet
  • Budget is tight and standard retail POS is genuinely enough
The benefits
  • Sales are capped by real capacity, so a full crossing or timed slot can't be oversold
  • Ferry, attraction, retail, and food operate as one connected multi-venue system
  • Tide and sailing schedules drive what's sellable, reflecting how the harbour actually works
  • Takings reconcile against bookings and capacity automatically
  • Customer-facing booking and on-site sales share one source of truth
The trade-offs
  • Custom POS hardware and resilience requirements add cost over a Square setup
  • Waterfront connectivity can be patchy, so offline-capable selling has to be built
  • You take on payment-processing integration and its compliance obligations
  • A single-venue operation with no timed capacity doesn't need this and Square is fine

Feature priorities for Portsmouth teams

What to build in
+Capacity-aware ticketing tied to sailings and timed-entry slots
+Multi-venue operation across ferry, attraction, retail, and food
+Tide and timetable awareness governing what's sellable when
+Offline-capable selling for patchy waterfront connectivity
+Automatic reconciliation of takings against bookings and capacity
+Integration with online booking so on-site and online share capacity

What we build under POS in Portsmouth

The engagements Portsmouth teams bring us most often: payment processing integration, custom POS system, point of sale software, retail POS, restaurant POS and Square alternative.

The honest cost picture for Portsmouth

Project scopeTypical costTimeline
Capacity-aware POS, single venue£35k to £55k3 to 4 months
Plus multi-venue and timetable logic£55k to £75k4 to 5 months
Plus offline mode and online booking integration£75k to £95k5 to 6 months
Cost by project scopeCost by project scopeCapacity-aware POS, single venue$35k to $55kPlus multi-venue and timetable logic$55k to $75kPlus offline mode and online booking integration$75k to $95k
Typical project cost bands. Source: Digital Heroes 2026 delivery benchmarks.
Want a fixed quote instead of estimates?
One scoping call, then a named senior team and a fixed price within 48 hours.
Talk to Digital Heroes

Timeline: what happens, and when

Delivery timeline by phaseDelivery timeline by phaseDiscovery2 wkDesign3 wkBuild7 wkTest2 wk1 wk
Indicative delivery timeline by phase.
What drives the price up mostWhat drives the price up mostCapacity and timetable engineMulti-venue operationOffline-capable sellingPayment integration
What pushes the price up most, relative impact.

Exactly what you get

A POS that understands the waterfront: it knows the next sailing, the capacity remaining, the timed-entry slots, and the tide-dependent schedule, so staff can't oversell. Ferry, attraction, retail, and food run as one connected system, selling works even when harbour connectivity drops, and takings reconcile against bookings and capacity automatically. On-site and online booking share one source of truth so capacity is never double-counted.

How to choose a developer in Portsmouth

Choose a developer who has built capacity-aware ticketing or hospitality POS, not just retail tills. Ask how they'd tie selling to sailings and timed slots, how they'd keep selling working offline on the waterfront, and how on-site and online share capacity. A partner who asks about your tides, timetables, and multi-venue setup gets it. One that proposes a standard Square configuration hasn't understood what governs your sales.

Red flags when hiring (and what to ask instead)
  • !They treat it as a retail till. Ask how it handles timed ferry capacity
  • !No offline plan. Ask what happens when waterfront connectivity drops mid-sale
  • !No booking integration. Ask how online and on-site share the same capacity
  • !No payment-compliance experience. Ask how they handle card processing securely
  • !They ignore multi-venue. Ask how ferry, attraction, and retail connect

Teams investing in pos in Portsmouth usually scope it next to supply chain, business intelligence dashboards, booking & scheduling, since these systems share data and budgets.

Rohan Malhotra · Enterprise Software Consultant

Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.

Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.

FAQ

Frequently asked questions

Why isn't Square enough for a ferry or attraction?

Square rings up sales but has no concept of timed capacity, sailings, or tide-dependent schedules. So staff can oversell a full crossing or slot because the till doesn't know the limit. A custom POS makes capacity govern the sale.

What happens if connectivity drops on the harbour?

A well-built custom POS sells offline and reconciles when the connection returns, so a patchy waterfront signal doesn't stop you taking money. Offline capability is a core requirement, not an extra.

Can online bookings and on-site tills share capacity?

Yes, and they should. Integration means a slot sold online instantly reduces what's sellable on-site and vice versa, so you never double-sell a timed crossing or entry.

Does it handle multiple venues?

Yes. Ferry, attraction, retail, and food can run as one connected system with shared reporting, instead of disconnected Square tills that you reconcile by hand at close.

Keep reading