060 279 5587 info@sitect.co.za 139 Davies Street, Doornfontein, Johannesburg, 2001 Gauteng, SA
E-Commerce · Bespoke Platform Engineering

When off-the-shelf isn't enough.

Some businesses run on commerce logic Shopify and WooCommerce simply cannot model — dynamic pricing engines, complex B2B procurement, multi-vendor marketplaces, configurable products with hundreds of variants, regulated industries, ERP-coupled inventory. For those, we engineer custom platforms from the database up.

From R48k · scoped per build 3–6 months typical engagement You own the source code
Commerce CoreBespoke domain engine
StorefrontNext / Nuxt
Admin PanelInternal ops
Mobile APIiOS · Android
PaymentsSA + intl.
InventoryERP sync
SearchAlgolia · OpenSearch
AnalyticsWarehouse + BI
B2B PortalQuotes · Net-terms
Internal API Event bus
Why brands outgrow SaaS commerce

The point where Shopify & WooCommerce stop helping

SaaS commerce platforms are brilliant — until your business logic doesn't fit the box they ship in. Here are the patterns we see when off-the-shelf has hit its ceiling.

Constraint 01

Your pricing logic can't be expressed in a single field.

Quantity-tier pricing, customer-group pricing, contract pricing, dynamic rules based on currency-of-record, volume rebates on monthly aggregates. The "Price" field on a Shopify variant can't hold this. You end up with thirty plugins fighting each other, or a R200k/year Shopify Plus retainer to maintain a Frankenstein.

What you need: a domain-modelled pricing engine. Not a price field.
Constraint 02

Your "products" aren't products in the SaaS sense.

Configurable industrial parts with 14 attribute axes. Insurance quotes generated by risk engines. Bookings of physical assets across time. Subscription bundles with mid-cycle upgrades and proration. SaaS commerce platforms model "things in a cart" — they don't model your domain.

What you need: domain-driven design over a generic product schema.
Constraint 03

You're coupled to systems SaaS can't talk to natively.

Sage, SAP B1, SYSPRO, Pastel, Microsoft NAV, custom warehouse management, SARS-integrated invoicing. The "Shopify connector" exists but loses data on edge cases, and a single sync gap puts your stock out by 40 units mid-Black-Friday.

What you need: first-class integration as a build-time concern, not a plugin.
Constraint 04

You're charging SaaS commerce as if you don't have leverage.

At R8M+ GMV, Shopify Plus is R30k+/mo plus 0.15% transaction fees. WooCommerce on top-tier hosting is cheaper but the engineering team to make it scale costs you elsewhere. At a certain scale, custom is actually cheaper — and you stop paying for features you don't use.

What you need: a TCO honest conversation, not a feature-checkbox war.
Is custom right for you?

Signals you're a fit for a bespoke platform

If 3 or more of these describe your business, custom is probably the right answer. If 1 or 0 do — Shopify or WooCommerce will serve you better, and we'll tell you so.

You're doing R10M+ GMV/year

Below R10M GMV, the SaaS rental fee is rounding error. Above it, the equation flips and a bespoke platform pays itself back inside 18 months.

Your pricing logic is a spreadsheet

If your sales team uses Excel to quote because the website can't, you have a domain mismatch the SaaS box can't fix without compromise.

You're a marketplace, not a store

Multi-vendor, vendor onboarding, commissions, payouts, vendor-specific catalogues and dashboards. SaaS marketplaces exist; they all model their idea of a marketplace, not yours.

ERP is the source of truth

If stock, pricing, and customer data really live in Sage / SAP / SYSPRO and the website is a viewer of that data, a custom build with native integration is dramatically cleaner than constant sync battles.

Regulated or compliance-heavy

Pharmaceuticals, financial services, alcohol, age-restricted, FICA / KYC at checkout, region-locked inventory. Compliance flows are the build, not a plugin you bolt on.

You need a moat

If your operations are part of your competitive advantage, you don't want to run them on the same platform every other player rents. Custom is a moat with code in it.

Architecture · How we build

The 6-layer architecture we ship

We build commerce platforms as a layered, service-oriented system. Each layer has a clear responsibility, can be deployed independently, and can be swapped without rebuilding the rest.

Presentation
Storefront, admin UI, mobile apps — each consuming the same internal API. Server-rendered, edge-cached, responsive.
Next.jsNuxtInertiaReact Native
API gateway
Versioned REST + GraphQL surface, auth, rate-limiting, request shaping. Single contract for every client surface.
Laravel APIGraphQLSanctumOpenAPI
Domain core
Pure business logic — pricing engine, cart, checkout, order lifecycle, fulfilment rules, vendor model. No HTTP concerns.
LaravelDDDEvent sourcing
Integration
First-class adapters to your ERP, WMS, accounting, courier, payment gateway, and CRM. Event-driven, idempotent, retry-safe.
SageSAP B1SYSPROYocoAramex
Data
Operational database (MySQL / PostgreSQL), Redis for cache & queues, OpenSearch for product search, S3 for media.
MySQLPostgresRedisOpenSearchS3
Infrastructure
Cloud infrastructure as code, automated CI/CD, observability, monitoring, backups, secrets management. SA region by default.
AWS af-south-1TerraformGitHub ActionsCloudflare
What we engineer into the platform

Capabilities SaaS commerce can't model cleanly

The features that prompted you to look for custom in the first place. We've shipped versions of each of these on bespoke SA platforms.

Domain pricing engine

Quantity tiers, contract pricing, customer-group rules, currency-of-record, dynamic discounts, channel-specific pricing, time-bound promos, volume rebates — all composable.

Configurable products

Variant matrices with 10+ attribute axes, dependent rules, sub-component selection, CAD-driven configurators, on-the-fly SKU generation.

Multi-vendor marketplaces

Vendor onboarding, KYC, vendor-specific catalogues + branding, commissions, payouts (Yoco Split / PayFast SplitPay / custom), vendor analytics.

B2B procurement

Quote-to-order, RFQ flows, net-30/60/90 invoicing, approval chains, requisition workflows, fleet pricing, contract repositories.

Subscription & bundling

Plan tiers, mid-cycle upgrades with proration, dunning, scheduled bundles, dynamic gift-with-purchase, "build-a-box" subscriptions.

Bookings & rentals

Calendar-based inventory, conflict detection, deposits, partial payments, rental return + condition workflows, calendar sync.

Inside-sales tooling

Sales-rep impersonation, telephonic-order entry, draft orders, internal-only promotions, opportunity → order flows tied to your CRM.

Search & merchandising

Algolia / Meilisearch / OpenSearch, faceted filters with custom attributes, merchandising rules, synonym tuning, query suggestions, "boost & bury" controls.

BI & analytics

Warehouse pipeline (BigQuery / Snowflake / Postgres BI), Metabase / Superset dashboards, customer-lifetime-value modelling, cohort analysis.

Our default stack

The technology choices behind every build

We make boring, well-understood tech choices — because at this price point, you're hiring engineering, not novelty.

Backend & core

Laravel 12PHP 8.2+ · domain core
Node.jsFor real-time + workers
PostgreSQLOr MySQL 8 if preferred
RedisCache · queues · sessions
OpenSearchProduct search · facets

Frontend & mobile

Next.js 15App Router · server components
Vue / NuxtWhen team prefers Vue
Inertia.jsFor tightly-coupled Laravel apps
React NativeMobile apps · iOS + Android
Tailwind CSSDesign system foundation

Infrastructure

AWS af-south-1Cape Town region default
CloudflareCDN · WAF · DNS
TerraformInfrastructure as code
GitHub ActionsCI/CD · automated deploys
Sentry + DatadogErrors · APM · uptime
What ships with the platform

Everything you walk away with at handover

Not just running software — the documentation, observability, and operability that make it actually maintainable by your team or any other competent agency.

Full source code

Every line of code MIT-licensed and pushed to your own repository. Branching strategy, PR conventions, and code-review playbook included.

Infrastructure as code

Terraform modules for every AWS resource, environment-specific configs, secrets in AWS Secrets Manager, full disaster-recovery runbook.

Living architecture docs

C4-model architecture diagrams, ADRs (architecture decision records) for every major choice, OpenAPI schemas, ERDs — all in the repo, versioned with the code.

Observability

Sentry error tracking, Datadog APM, CloudWatch dashboards, structured logs to a queryable store, SLO dashboards with alerts to your on-call.

Test suites

Domain unit tests, integration tests against real DB/Redis, end-to-end tests on Playwright, with CI gates that prevent shipping when tests fail.

3-month warranty + transition

Every defect we ship, we fix free for 3 months. We pair-program with your engineering team, run code reviews on their PRs, and exit only when you're confident running the platform alone.

How a custom build runs

The 6-phase engagement

Custom platforms are real engineering projects, not website builds. Here's how we run them — phased, with explicit go/no-go gates between each phase.

1

Discovery & domain modelling

Workshops with your business stakeholders, your existing systems audit, integration mapping, risk & compliance review. We produce a domain model, ADRs, and an architecture document before code is written.

Weeks 1–3
2

Foundation & spike

Repo scaffolding, CI/CD, AWS infrastructure provisioned via Terraform, auth, observability, the API gateway, and a "tracer bullet" feature end-to-end to de-risk the architecture.

Weeks 4–6
3

Core build

The domain core — catalog, pricing, cart, checkout, order lifecycle, payments, basic admin. 2-week sprints with reviewable demos every Friday.

Weeks 7–14
4

Integration build

ERP / WMS / accounting integrations. The riskiest phase — we treat external systems as untrusted, build idempotent connectors, run parallel-run tests against your real data.

Weeks 12–18
5

UAT & hardening

Your team runs UAT against staging. We instrument load tests, security review, penetration test, performance tune until SLOs are met. POPIA review & data-flow documentation.

Weeks 18–22
6

Launch + warranty

Phased cutover (often by region, customer-segment, or shadow-mode), 90-day defect warranty, weekly check-ins with your engineering team, deliberate hand-off.

Month 6+
Why brands invest at this level

What custom earns back

Indicative figures from recent SA bespoke commerce builds, measured 6–12 months after launch. Custom isn't always cheaper than SaaS — but where the fit is right, the ROI is unambiguous.

−54%
Platform TCO
vs prior Shopify Plus stack
2.8×
Quote-to-order
B2B flow rebuilt around domain
11→1
Tools consolidated
Plugins / SaaS retired
99.97%
Uptime · 12 months
Across 4 active platforms
Indicative pricing — ZAR, ex VAT

How bespoke engagements are scoped

Custom builds are always estimated bottom-up after discovery, but here are the bands we typically see. 30% on signature, 30% on phase-3 demo, 30% on UAT, 10% on launch.

Foundation

Defined scope, single domain, single integration
From R48 000 · ex VAT
3–4 months · 1 integration
  • Domain model + core catalog/cart/checkout
  • Custom admin panel
  • 1 SA payment gateway + 1 courier
  • 1 first-class integration (ERP / WMS / accounting)
  • AWS Cape Town · Terraform · CI/CD
  • 90-day defect warranty
Scope a Foundation build

Enterprise Platform

Multi-region, regulated, omnichannel
POA
From R180 000 · 6–9 months
  • Multi-region · multi-currency · multi-tax
  • Mobile apps (iOS + Android)
  • Compliance workflows (FICA / KYC / FSP / FAIS)
  • 4+ integrations · event-driven core
  • BI warehouse + dashboards
  • Retained engineering pod post-launch
Talk to us about Enterprise
FAQ

The questions we get asked most

Honest answers about cost, ownership, risk, and how to know if custom is genuinely the right call.

How do I know if we genuinely need custom or if Shopify Plus would do it?
Book a 45-minute architecture call. If we can model your business on Shopify Plus or WooCommerce in under an hour without ugly hacks, we'll tell you — and we'll quote that build instead. Custom is what we recommend when off-the-shelf can't model your domain without compromise, when the SaaS fee passes the cost of engineering, or when ownership/compliance forces your hand.
Custom seems risky compared to a known SaaS platform — what could go wrong?
The risks are real: scope creep, key-person dependency, the "we built our own commerce platform" graveyard. We mitigate by (1) phased contracts with go/no-go gates, (2) ADRs documenting every architectural choice for future maintainers, (3) test coverage that protects domain logic, (4) deliberate hand-off including pair-programming with your engineering team, (5) we deliberately use boring well-understood tech so any competent agency could take over. Custom isn't safe by default; it's safe when engineered with the long term in mind.
What if we don't have an internal engineering team?
You need one — or a long-term retainer with us. A custom platform without a maintaining team becomes legacy software fast. We'll help you hire (we've helped 3 clients hire their first SA-based engineer) or run a retained ops pod (from R22k/mo) until you have your own team in place.
Can we run the SaaS store alongside the custom platform during transition?
Yes — and we usually recommend a shadow / phased rollout for any platform serving meaningful GMV. Common strategies: (1) shadow-mode (both run, custom only writes), (2) region or customer-segment cutover, (3) read-only first, then writes. We design the cutover plan during discovery.
What's the total cost of ownership 3 years out?
A worked example. A mid-size SA brand on Shopify Plus + 10 paid apps + a fractional Plus partner: ~R720k/year all-in. The same brand on a custom platform: build cost amortised over 3 years (~R40k/year), AWS hosting (~R140k/year), Sentry/Datadog + tooling (~R45k/year), retainer (~R140k/year) = ~R365k/year. After year 3 the gap widens because SaaS fees rise and a custom platform doesn't. The "cheaper" answer depends on growth rate.
What if we lose you mid-build?
Every project ships its ADRs, OpenAPI specs, architecture diagrams, README runbooks, and a deliberate weekly recording of design decisions into your repo. We deliberately use mainstream technology (Laravel, Next.js, PostgreSQL, AWS) that any competent SA agency can pick up. We've twice handed off projects mid-build to client teams; both shipped on time.
Is everything POPIA-compliant out of the box?
Yes — POPIA isn't an add-on at this tier, it's a build-time concern. Every platform we ship has consented data-processing baked in, customer data export & delete endpoints, breach-notification procedures, retention policies, role-based access on PII, and a data-flow document for your information officer.
Can you migrate from our existing platform without losing data?
Yes. We script migrations idempotently with reconciliation reports — you get a delta between source and destination after every dry-run. Customer accounts, order history, product catalog, content, tax records, all preserved. SEO-critical URLs get 301s. We've migrated stores from Shopify Plus, BigCommerce, Magento 2, Salesforce Commerce Cloud, and bespoke PHP without losing data.

Tell us where SaaS commerce broke for you — we'll tell you honestly if custom is the answer.

Send us a paragraph on your business model, current platform, the friction you're hitting. We'll come back with a 45-minute architecture call, a recommended tier, and an indicative budget — no obligation, no pitch deck.