Skip to content
OneZera

Work

What we have built

We do not publish client names, logos or screenshots. What we can describe is the problem, what we built and what changed afterwards. The screens shown here are mock-ups of the kind of interface each system uses, not client work.

Transport. Customer app, driver app, dispatch admin.

Taxi and private-hire booking platform

The problem

Bookings came in by phone and went out over the radio. Nobody could tell a caller where their car was, and driver pay was worked out from handwritten sheets at the end of the week.

What we built

  • Customer app for booking, fare estimates and live status
  • Driver app with job offers, navigation handover and shift tracking
  • Dispatch screen showing every live job
  • Automatic assignment, with the controller able to override it

What changed

Bookings, dispatch and driver pay now come off one system.

Wholesale. Android and iOS, Laravel API.

Trade ordering system for a wholesaler

The problem

Trade customers ordered by phone and message. Staff typed those orders in again, and the mistakes turned up at delivery, when they were expensive.

What we built

  • Customer app for the trade catalogue, pricing tiers and repeat orders
  • Staff app for accepting, picking and dispatching
  • Push alerts with their own sound, and a count of new orders
  • Invoice and delivery note printing to the office printer

What changed

Orders get typed once, by the customer. The counter runs off a tablet.

Retail. Tablet POS, central back office.

Point of sale for a multi-branch retailer

The problem

Each branch had its own tills and its own figures. Stock and takings were reconciled once a week, when there was time.

What we built

  • Tablet point of sale that keeps working when the internet doesn't
  • Central product, pricing and stock control across branches
  • Receipt and label printing to counter hardware
  • Daily takings and stock movement per branch

What changed

Head office sees every branch on the same day, in the same format.

Hospitality. Customer app, kitchen screen, driver app.

Food ordering and delivery for restaurants

The problem

Delivery platforms took a cut of every order and kept the customer details that came with it.

What we built

  • Ordering app and web storefront on the restaurant's own domain
  • Kitchen screen that accepts, times and closes orders
  • Driver app for assignment and delivery confirmation
  • Payments into the restaurant's own account

What changed

Orders come in on the restaurant's own app, and the customer list belongs to the restaurant.

E-commerce. Laravel, PostgreSQL, Next.js.

Moving a shop off WooCommerce

The problem

Every new feature meant another plugin, and every plugin was another thing that could take the checkout down.

What we built

  • A Laravel and PostgreSQL API holding products, orders and customers
  • A Next.js storefront on the shop's own domain
  • A web admin for staff, with the same API serving the mobile apps
  • Both systems running side by side until the new one had proved itself

What changed

The website, the apps and the back office now run off one codebase.

Our own product. Laravel, SMS and email.

Reorder prompts for repeat-purchase businesses

The problem

Businesses know roughly when a customer is due to reorder. Nobody has time to chase every account by hand.

What we built

  • Reorder messages by SMS and email, timed per customer
  • A link that rebuilds the customer's usual basket in one tap
  • An admin for scheduling, templates and results

What changed

We built it, we run it, and we are on call for it ourselves.

If any of this sounds like your situation, tell us about it. We can go through comparable work on a call in more detail than we can publish here.