Operations systemSales AILive

One system for sales, stock and teams, built for BondBoss.

BondBoss sells waterproofing and repair products online, in three stores and on Takealot. ZidTech built Ops Core to run its sales, stock, couriers and teams, and CartWatch, an AI voice agent that phones customers who abandon their carts.

REF·01  Ops Core · system map 43 automations · as of 23 Oct 2026
In · 6 core integrations
  • ShopifyOnline orders
  • YocoCard payments in store
  • TakealotMarketplace orders
  • Bob GoCourier bookings & costs
  • BreazeWaybills & fulfilment
  • GmailInvoices & email
Ops Core 30 modules
11 roles
CartWatchAI voice calls & order matching
Out · what it runs
  • JohannesburgFlagship store + warehouse
  • Cape TownStore
  • DurbanStore
  • 11 team rolesEach sees only their modules
  • KPIs & dashboardsSales, stock, couriers
  • CommissionsFrom paid invoices
Client
BondBoss, South Africa
Sites
JHB · CPT · DBN
Status
Ops Core live, CartWatch: 5 call batches a day
A · Locations4Johannesburg store & warehouse, Cape Town and Durban, all on Ops Core
B · Modules30across 11 user roles: each role sees only the modules it needs
C · Automations43Switched on: 8 on a schedule, 35 triggered by events (27 of them activity logs)
D · Runs290K+Runs started since May 2026 across all 61 automations built, incl. ones now switched off

Locations, modules and roles: Ops Core’s settings and permissions. Automation figures: Ops Core’s workflow registry. All read on 23 Oct 2026.

Project overview

The brief.

BondBoss was growing fast: a proven product range, nationwide delivery, marketplace sales and walk-in stores. Growth like that breaks spreadsheets, scattered chats and manual follow-ups, and expanding into new cities would have multiplied the chaos.

We mapped how the business actually works, then built Ops Core module by module around it and wired every integration in. CartWatch sits beside it, set up to match each call Marius makes to any resulting Shopify order and label the sale CartWatch-attributed or organic.

IndustryHome repair & waterproofing: e-commerce, retail stores & marketplaces
Project typeOperations system + AI sales agent, built on Base44 with an ElevenLabs voice
ServicesSystems architecture, integrations, automation, dashboards, AI voice agent
Primary goalScale into new cities with control and visibility, and follow up abandoned checkouts automatically
Branch network

Three cities. One system.

New cities used to mean more manual coordination. Now Cape Town and Durban run on Ops Core beside the Johannesburg flagship store and warehouse, so every branch sale, transfer and stock count lands in one place.

3 stores + 1 warehouse · September 2026Flagship + warehouseNew branchStock transfers raised, Sep 2026
View data table
Branches, in-store sales and stock transfers raised from the Johannesburg warehouse, September 2026
BranchRoleIn-store sales, Sep 2026In-store salesTransfers raised from the JHB warehouse, Sep 2026Transfers raised
JohannesburgFlagship + warehouse10730
Cape TownNew branch741
DurbanNew branch804

September 2026. In-store sales: completed sales by payment date. Transfers raised: stock transfers from the Johannesburg warehouse to that store, counted by the date each was created.

Record counts · September 2026

Sales recorded by channel

September 2026 · count of records in Ops Core

Orders by order date; in-store sales by payment date, completed sales only. Read from Ops Core on 23 Oct 2026.

Every channel lands in Ops Core, so the team compares online, marketplace and in-store sales side by side.

553invoices issued in Sep 2026 (excl. drafts & cancelled)
35stock transfers raised from the JHB warehouse in Sep 2026
What we built

Inside the system.

One system, 30 modules, and every role sees only what it needs. Switch roles to see how the menu changes.

Ops Core
  • Overview
  • Store Ops
  • Warehouse
  • Marketplace
  • CRM
  • Finance
  • Insights (no access)
  • Audits (no access)
  • Admin (no access)
  • Locked: Insights · Audits · Admin
Signed in asWarehouse Manager
11 of 30 modules
  • DashboardOverview
  • Walk-In SalesStore Ops
  • PickupsStore Ops
  • Warehouse ManagerWarehouse
  • Stock LevelsWarehouse
  • Reorder IntelligenceWarehouse
  • TransfersWarehouse
  • StocktakesWarehouse
  • OrdersMarketplace
  • Ops DashboardMarketplace
  • ShipmentsMarketplace
  • ActivitiesCRM
  • Admin ExpensesFinance
Warehouse AssistantStock, orders & fulfilment
Illustrative view, rebuilt from Ops Core’s real menu and role permissions. No customer data. 3 of its 11 roles shown.
  • Multi-location operations

    Johannesburg store and warehouse, Cape Town and Durban, each with location-aware access, stock and reporting.

  • Sales from every channel

    Shopify orders, in-store Yoco payments, invoices and Takealot orders in one ledger.

  • Stock, transfers & stocktakes

    Live stock by location, warehouse-to-store transfers, barcode/QR scanning and reorder intelligence.

  • Couriers & fulfilment

    Bob Go and Breaze shipments booked with waybills recorded, plus a daily shipment health check and a 6-hourly courier-cost sync.

  • Teams, roles & commissions

    11 user roles across 30 modules, sales-rep commissions, KPIs and seven built-in AI assistants.

  • CartWatch AI recovery

    Voice calls by Marius, call-to-order matching, recovery attribution and a called-numbers registry.

Automation

24 hours on Ops Core.

Eight schedules run around the clock. Another 35 automations are triggered the moment a record changes, like a paid invoice or a new order.

A day of scheduled automations

The eight schedules active on 23 Oct 2026, in South African time

SAST (UTC+2), converted from the UTC schedules in Ops Core’s workflow registry, read 23 Oct 2026. Event-triggered automations are not shown.

  • 46,978order-status syncsevery 5 min since 12 May 2026
  • 659courier-cost syncsevery 6 h since 11 May 2026
  • 147data-integrity auditsdaily since 18 May 2026

Run totals counted on 23 Oct 2026.

CartWatch

The recovery playbook.

Abandoned checkouts used to be simply lost. Now CartWatch is built to run the same steps on every eligible one: one call per number, retried only if it never connects.

  1. 01

    Detect

    Around the clock

    Abandoned Shopify checkouts sync into CartWatch, and every phone number is checked and normalised before anyone is called.

    Checkouts · every 5 minPhone check · every 30 min
  2. 02

    Call

    5 batches a day

    Marius, an ElevenLabs voice agent, places calls in five daily batches.

    10:0012:0014:0016:0017:00
  3. 03

    Call once

    One call per number

    Once a call goes through, the number goes on the called-numbers registry and is never dialled again. A call that never connects is retried on up to three days, then the cart is closed as lost.

  4. 04

    Match to orders

    Scheduled every 30 min

    Set up to match calls to Shopify orders by email or phone, with a price check, and to label each recovery CartWatch-attributed or organic.

  • Called-numbers registry stops repeat dialling
  • Only validated phone numbers are called
  • Do-not-contact flags and recovered carts are skipped
Rollout

How the system rolled out.

Dated from the systems themselves: each milestone is the day its record or workflow was created in Ops Core or CartWatch.

  1. CartWatch switches on

    Its first abandoned checkouts are synced from Shopify.

  2. Ops Core is set up

    The Johannesburg flagship store and warehouse become its first two locations.

  3. Cape Town added

    The Cape Town store goes on Ops Core; Yoco payment and Bob Go courier syncs set up.

  4. Marius moves to batches

    Scheduled batch calling starts (today: five batches a day, 10:00 to 17:00).

  5. Durban added

    The Durban store goes on the same system as Johannesburg and Cape Town.

Final outcome

BondBoss now runs on a system we built for its next stage of growth. Ops Core gives every team one source of truth across three stores, the warehouse and every sales channel, and CartWatch is built to work the abandoned-checkout funnel automatically, calling customers so lost carts get a second chance.

Checked in Ops Core · 23 Oct 2026
  • 30
    modules across 11 user rolesEach role sees only the modules it needs
  • 43
    automations switched on8 on a schedule, 35 that run when a record changes
  • 3 + 1
    stores + warehouseJohannesburg, Cape Town and Durban, plus the JHB warehouse
Let's build what's next

Want results like these?

Let’s talk about where your business is now, and build the system that gets it where you want to be.