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.
- ShopifyOnline orders
- YocoCard payments in store
- TakealotMarketplace orders
- Bob GoCourier bookings & costs
- BreazeWaybills & fulfilment
- GmailInvoices & email
11 roles
- 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
Locations, modules and roles: Ops Core’s settings and permissions. Automation figures: Ops Core’s workflow registry. All read on 23 Oct 2026.
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.
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.
View data table
| Branch | Role | In-store sales, Sep 2026In-store sales | Transfers raised from the JHB warehouse, Sep 2026Transfers raised |
|---|---|---|---|
| Johannesburg | Flagship + warehouse | 107 | 30 |
| Cape Town | New branch | 74 | 1 |
| Durban | New branch | 80 | 4 |
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.
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.
Inside the system.
One system, 30 modules, and every role sees only what it needs. Switch roles to see how the menu changes.
- Overview
- Store Ops
- Warehouse
- Marketplace
- CRM
- Finance
- Insights (no access)
- Audits (no access)
- Admin (no access)
- Locked: Insights · Audits · Admin
- DashboardOverview
- Walk-In SalesStore Ops
- PickupsStore Ops
- Warehouse ManagerWarehouse
- Stock LevelsWarehouse
- Reorder IntelligenceWarehouse
- TransfersWarehouse
- StocktakesWarehouse
- OrdersMarketplace
- Ops DashboardMarketplace
- ShipmentsMarketplace
- ActivitiesCRM
- Admin ExpensesFinance
- Overview
- CRM
- Finance
- Insights
- Store Ops
- Warehouse (no access)
- Marketplace (no access)
- Audits (no access)
- Admin (no access)
- Locked: Warehouse · Marketplace · Audits · Admin
- DashboardOverview
- PA WorkspaceCRM
- LeadsCRM
- Lead PoolCRM
- My AI LeadsCRM
- DealsCRM
- ContactsCRM
- ActivitiesCRM
- InvoicesFinance
- RefundsFinance
- CommissionsFinance
- Admin ExpensesFinance
- Invoice AnalyticsInsights
- KPIs & TargetsInsights
- Loyalty ProgramStore Ops
- Overview
- Finance
- Insights
- CRM
- Store Ops
- Warehouse (no access)
- Marketplace (no access)
- Audits (no access)
- Admin (no access)
- Locked: Warehouse · Marketplace · Audits · Admin
- DashboardOverview
- InvoicesFinance
- RefundsFinance
- PaymentsFinance
- CommissionsFinance
- Admin ExpensesFinance
- Invoice AnalyticsInsights
- KPIs & TargetsInsights
- ReportsInsights
- ActivitiesCRM
- Loyalty ProgramStore Ops
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.
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.
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.
- 01
Detect
Around the clockAbandoned 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 - 02
Call
5 batches a dayMarius, an ElevenLabs voice agent, places calls in five daily batches.
10:0012:0014:0016:0017:00 - 03
Call once
One call per numberOnce 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.
- 04
Match to orders
Scheduled every 30 minSet 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
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.
CartWatch switches on
Its first abandoned checkouts are synced from Shopify.
Ops Core is set up
The Johannesburg flagship store and warehouse become its first two locations.
Cape Town added
The Cape Town store goes on Ops Core; Yoco payment and Bob Go courier syncs set up.
Marius moves to batches
Scheduled batch calling starts (today: five batches a day, 10:00 to 17:00).
Durban added
The Durban store goes on the same system as Johannesburg and Cape Town.
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.
- 30modules across 11 user rolesEach role sees only the modules it needs
- 43automations switched on8 on a schedule, 35 that run when a record changes
- 3 + 1stores + warehouseJohannesburg, Cape Town and Durban, plus the JHB warehouse
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.