Cape Town florist pilot

What the Cape Town florist pilot covered

This project ran with a Sea Point florist cluster handling same-day cut-offs most weeks. Independent shops needed their bouquets, potted orchids and soft gift bundles moving on time in Cape Town’s traffic, without the chaos of chasing one driver or courier. We focused on clear daily ownership: each team kept a lane card up to date, logged exceptions on paper, and managed handovers with a visible checklist. Electronic plans failed too often during power cuts or when the Wi-Fi dropped, so paper stayed on the wall for every shift. This pilot suited owner-managed shops, compact teams and delivery routes where every hour counted, especially with local Highveld-style storms closing in.

Who benefits from this pilot, who does not

Florists, bakeries, small gift shops and any Cape suburban team with an urgent route each day will recognise these pressures. You get the most value if your team cares about on-time handover, hates losing track of parcels, and cannot spare a manager for every handoff. If you run a big distribution centre, national depot chain or a shop with dozens of bays, this pilot is probably too narrow. Teams already running full route planning software (and trusting it every morning) may find our pen-and-paper approach too simple.

• Best for shops with 3 to 10 people on the floor.
• Works for teams dispatching time-sensitive or fragile goods, flowers, cakes, parcels.
• Suited to owner-managed or small ops teams, not national depots.
• Does not replace warehouse management systems for inventory or bulk sorting.
• Avoid if you need full batch tracking or automated SMS alerts.

How the florist pilot worked on the floor

Every morning, operators held a fifteen-minute standup. The top priority was assigning one owner per lane card and writing down that day’s special deliveries or known hazards. A checklist stayed visible (even during load-shedding) and every box, bouquet and carton got ticked as it left the workbench. Regional handoff notes went to the next hub if there was a transfer, with paper copies in every van. Most days ended with a short update about missing items or returns. Lane cards and checklists avoided double-handling, and most florists found fewer frantic calls to dispatch by Friday. Borrowing direct routines from Moves and Lanes, the pilot forced focus on real moves, not wishful routing.

A worked example: Friday before Mother’s Day

On peak days, like the Friday before Mother’s Day, three florists in the pilot shared the same cut-off for Sea Point, Green Point and Camps Bay. Each assigned an operator to own a lane card. In the morning, they flagged two high-value bouquets needing early delivery. The checklist pinned to the wall listed all eleven local stops. At 14:00, the regional van collected the parcels. One fragile box was marked for a handoff in Salt River, a note went with both the driver and the hub. By late afternoon, each florist checked the card against their own dispatch note, quickly spotted a missing return, and followed up with Updates to close the loop. Delays were logged; exceptions followed up the next week.

What to have ready before you contact Hello Logistics

Before you drop us a line about running a similar programme, have these basics ready. This helps us match you to the right lane moves and avoids wasted back-and-forth. Attach any routing notes or example checklists you already use if you have them. If your team is new to paper records, let us know so we can supply ready-made cards. Send your next city or suburb focus so we know where you want the pilot.

• A short list of your week’s regular delivery zones or suburbs.
• Your current daily cut-off times and any known pain points.
• The number and type of parcels you move each week.
• How many people handle dispatch or delivery each shift.
• Notes about load-shedding or other local disruptions.
• Any existing handover routine or checklist, attach if possible.

Pitfalls and lessons for South African teams

The biggest pitfall was trying to widen the scope too fast, adding event kits or treating returns as a ‘Saturday job’ always broke the system. Protect the main checklist and delay any extra decoration or one-off requests until your daily routine is steady. Most projects fail locally not from lack of tech, but from vague ownership and no paper trail. Setting one owner per lane each shift prevented lost parcels and cut frantic WhatsApps by the weekend. If your power fails, or municipal paperwork delays a driver, having something simple and visible keeps the team calm. For more trials like this, see Projects or how we manage fragile returns with the Midrand returns calm pilot.