Food & beverage · Western Cape

WhatsApp ordering, bake planning and dispatch for a Cape Town bakery group

Handle more orders with the same team, plan the bake from real orders, and get every load and invoice right the first time.

Industry
Food manufacturing (bakery)
Location
Western Cape, South Africa
Stages
Order → Plan → Deliver → Reconcile
Setup
Core system, connected to Sage Pastel
Timeline
Live in weeks

A Cape Town food manufacturer with more than 500 employees bakes over 200,000 loaves a day. Orders came in on WhatsApp and by phone, and were re-typed into spreadsheet after spreadsheet before a truck left the yard. Hubble built one system for ordering, bake planning, dispatch and reconciliation, designed around how the bakery already works. It runs as their core operations system and connects to Sage Pastel.

By Thijan Dippenaar, General Manager · Published

The problem

Orders came in through WhatsApp groups and phone calls, often only after staff had chased customers for them.

Each order was re-typed several times in different spreadsheets as it moved through the operation. Retail-chain orders were printed and keyed in by hand.

The bake plan was built by hand from those sheets.

Wrong loads went out and trucks came back. Invoicing errors meant finance spent its time issuing credit notes to fix them.

What we built

One order inbox combining orders from WhatsApp, the customer portal and retailer files
One inbox for every order channel
Overnight bake plan by oven and line, generated from live orders, with ingredients needed
The day's bake plan builds itself from orders as they come in
Dispatch screen flagging a load that does not match its order
Dispatch flags any load that doesn't match its order
  • For customers: WhatsApp ordering by text, voice note or screenshot, plus a simple web portal. Customers get automatic reminders before the cut-off.
  • For the order desk, bakery and dispatch: one inbox for every order channel. Retail-chain files are uploaded instead of re-typed. Cut-offs and recurring orders are set per customer. The day's bake plan builds itself from orders as they come in. Orders flow straight to dispatch, which flags any load that doesn't match its order.
  • For finance: ordered, dispatched and invoiced are matched daily, with a list of cash to collect, and exported to Sage Pastel. Only exceptions are surfaced.

What improved

  • No re-typing from order to dispatch.
  • The bake plan is ready from live orders, not compiled by hand.
  • Fewer wrong loads, returned trucks and credit notes.
Before After
Orders re-typed across spreadsheets Captured once
Bake plan by hand Builds itself from orders
Wrong loads out Flagged before dispatch
Credit notes Daily ordered vs dispatched vs invoiced

Questions

Can bakery customers order on WhatsApp without an app?

Yes. They send a message, voice note or screenshot, or use a simple web portal. Every order lands in one place, already checked against the customer's products and cut-off.

Do we have to replace Sage Pastel?

No. Finance stays in Sage Pastel. Hubble runs ordering, planning, dispatch and reconciliation, and sends invoice-ready data to your accounting package.

A straight 30-minute conversation about your operation.

A straight 30-minute conversation about your operation.

Start a conversation