Development / Case study

From WooCommerce to the kitchen printer

Online ordering for Mario's Pizza, a 24-store franchise, delivered straight into the point of sale.

Mario's needed an online order to behave exactly like one taken at the counter: the correct menu, local payment, and no re-typing into the till.

Client

Mario's Pizza

Sector

Quick-service restaurant franchise, 24 stores, Trinidad & Tobago

Our role

Design and development: storefront, apps, back office, payments and POS integration

Engagement

Platform rebuild over about a year, in production and maintained

The challenge

Mario's online ordering had grown up on WordPress and WooCommerce. Staff re-typed every web order into the till, the menu could not model configurable pizzas and combo deals, and marketplace apps charged commission and kept the customer relationship. There was no app, no loyalty loop, and no visibility into who was buying. The brief was to own the whole channel: web, mobile, delivery and data, across two dozen kitchens.

What we built

1. 1

   A storefront built for pizza

   A configurator with live pricing, a deal builder with choice slots and automatic expiry, delivery or pickup across 24 geofenced stores, guest checkout and social sign-in.

2. 2

   Local payments and a subscription

   3-D Secure card payments through PowerTranz with tokenised cards, plus cash, Linx debit, card on delivery and pay at pickup. A monthly Pizza Pass bills a card on file automatically.

3. 3

   A customer app and a driver app

   An iPhone and Android app with push updates and live tracking, and a separate driver app with GPS streaming, proof of delivery and an offline queue.

4. 4

   Orders land in the POS

   A custom bridge to PixelPoint through the Call2Kitchen API maps products to roughly 1,600 SKUs, pushes each order once after checkout, and confirms receipt every five minutes with one-click re-push.

5. 5

   A back office managers can run

   About thirty admin sections: live orders, menu and availability controls, zones, drivers, loyalty, customer segments and campaigns, reports with CSV export, role-based access with two-factor sign-in, a register screen and receipt printing.

The decision

A custom platform with one backend for web, app, driver app and back office, over patching the WooCommerce store and adding a marketplace app.

Owning the platform made it possible for orders to land directly in the store's POS, with local payment methods, live delivery tracking, and a loyalty layer the brand owns. The trade-off was a much larger surface to build and test, including an older POS integration. That was managed with prices recalculated on the server, POS pushes that are sent once and confirmed on a schedule, and around 80 automated test files concentrated on pricing, deals, loyalty, SKU mapping and printing.

In production

24

Stores served

Per-store menus, hours and geofenced zones

~1,600

POS SKUs mapped

Automatic matching with admin aliases

0

Re-keyed orders

Orders push to the till; receipt confirmed every 5 minutes

These are delivery facts about the running system. Order volume, app downloads and average order value are held by the client and are not published here.

Built with

• Next.js
• React
• TypeScript
• React Native
• Firebase
• Vercel
• PowerTranz
• Call2Kitchen
• Resend