Example client · 🍦 gelato shop

How “A Lot o Gelato” runs on one portal.

A small ice-cream shop was juggling a website builder, a spreadsheet for staff, a supplier catalogue, and sticky notes for bookings. Here's the same business on one The Ship portal.

Before & after

😵 Before

  • Website on one platform, edited by hand
  • Staff schedule in a spreadsheet nobody could see
  • Supplier prices buried in emails
  • Bookings on paper — double-bookings happened
  • No idea what the day actually looked like

✅ After — one portal

  • Menu & site edited in the Shop CMS
  • Staff see their own shifts in the staff portal
  • 957-item supplier catalogue, searchable
  • Bookings in one schedule — and each one becomes a lead
  • An owner dashboard showing the whole day

Their module stack

Five modules, one login, all connected. Try each — they're live.

How it all connects

Nothing is re-typed. One action flows to the next.

🌐 Website enquiry 📅 Booking 📇 Lead Book 📒 Owner dashboard

A visitor books a party on the website → it lands in the schedule → the client drops into the Lead Book → it all rolls up on the dashboard.

Build one like this.

Start from this exact stack — Shop CMS, Staff, Inventory, Website, and Bookings — pre-loaded in the Builder. Tweak it for your business.

Open this stack in the Builder →

Prefer a different trade? See the photography-studio, real-estate brokerage, service & trades or sports club examples, the starter-site example, or browse all starter stacks →