MARKETPLACE & API INTEGRATIONS — SOUTH AFRICA

Uber Eats and Mr D orders, straight into your system.

Orders from Uber Eats, Mr D Food and Deeliver land in one pipeline through signed webhooks and idempotent ingestion, and status flows back to each platform in its own language. Built and running daily inside live dark stores.

01 / WHAT WE BUILD

What a proper platform integration includes.

Getting orders in is the easy 20%. The rest is everything that happens after.

S/01

Order ingestion

Signed webhooks with per-platform validators, plus pollers and APIs where a platform needs them. Idempotent, so the same order never lands twice.

S/02

Auto-accept inside the SLA

Orders are accepted automatically within each platform's time limit, so you don't lose them to a missed tablet chime.

S/03

Status sync back to the platform

A protocol adapter per marketplace translates your order lifecycle into each platform's native calls, queued with retries and backoff.

S/04

Honest capability contracts

Every integration declares what the platform truly supports. If a platform has no cancel API, we skip that action explicitly instead of pretending.

S/05

Virtual SKUs & combos

Combos and bundles the platforms can't represent natively are mapped to virtual SKUs, so menus and stock still add up.

S/06

Promotions via native APIs

Discounts, such as expiry markdowns, pushed through each platform's own mechanism, from Uber's promotions API to price overrides.

02 / BEYOND DELIVERY APPS

If it has an API, we'll connect it, honestly.

Every other integration

Delivery platforms are where we've gone deepest, but the same engineering applies to everything your business plugs into:

  • payment gateways: Paystack, PayFast, Ozow, Flutterwave, Stripe
  • accounting: Xero, Sage, QuickBooks
  • commerce: Shopify, WooCommerce
  • messaging: WhatsApp, email, push notifications
  • courier and shipping APIs

Failures you can see

Integrations break: a platform times out, refuses an update or changes a field. Ours fail loudly instead of silently, with verified retries, escalating backoff and explicit desync alerts when a platform refuses, so a mismatch gets fixed before a customer notices it.

API access, upfront

Each platform grants its own API access, and what your account can do varies. Part of discovery is confirming exactly what your platforms allow, so the scope is built on what's actually possible.

03 / IN PRODUCTION

Proof, not a pitch deck.

Systems we've built that are running right now. Walk through the Mngr flagship →

CASE — channels

Uber Eats, Mr D Food & Deeliver

Signed webhooks, per-platform validators and protocol adapters with real capability contracts. Virtual SKUs for combos, auto-accept inside each platform's SLA, and expiry promotions pushed through Uber's promotions API.

signed webhooksidempotent ingestionpromotions API
CASE — marketplace

SUPA customer app

The Yango-Tech-backed quick-commerce marketplace runs on Mngr: first-party order API, customer push notifications, partner webhooks and live driver location streamed to in-app tracking.

first-party APIFCM pushlive tracking
04 / PRICING

Priced per integration, quoted upfront.

Scoped per integration

  • fixed quote after discovery
  • typically 1–8 weeks per platform
  • priced by depth of sync, not by order volume

Often part of a bigger build

Always included

  • documentation of every integration
  • launch support & monitoring
  • post-launch bug fixes (30 days)
05 / PROCESS

How we work.

01

Discovery

How your business runs, where the bottlenecks are, what outcomes you need. No jargon.

02

Design & plan

Architecture, UX and a clear scope with timelines and pricing, before any code is written.

03

Build & test

Working software demoed every 1–2 weeks. You steer before we move forward.

04

Launch & support

Production deploy, team training, 30 days of post-launch fixes included.

06 / FAQ

Questions we actually get.

Yes. Orders flow from Uber Eats into your system automatically, and status updates flow back. We've built and run this in production for Uber Eats, Mr D Food and Deeliver.

Yes. Mr D Food runs alongside Uber Eats and Deeliver in the same pipeline, each through its own platform adapter.

Integrations are scoped per project and typically take 1–8 weeks each, depending on the platform and how deep the sync goes. You get a fixed quote after discovery.

It's retried with escalating backoff, and if the platform keeps refusing, a desync alert is raised. Nothing fails silently.

Each platform grants API access itself, and capabilities vary per account. We confirm what yours allows during discovery, before any build starts.

Yes: Paystack, PayFast, Ozow, Flutterwave and Stripe, including payment-aware order handling and automatic refunds on cancellations.

08 / CONTACT

Let's talk about what you're building.

No forms, no funnels. Reach a human directly. We reply within one business day.

LOCATIONCape Town, South Africa
HOURSMon–Fri · 09:00–17:00 SAST
RESPONSEWithin one business day