South African government procurement data is technically public.
But if you’ve ever tried to work with it, you already know the reality:
fragmented portals,
inconsistent award records,
unstructured PDFs,
broken search experiences,
and almost no tooling for publishers or developers.
Most procurement reporting still looks like screenshots pasted into articles or manually maintained spreadsheets that go stale within days.
We wanted to solve that properly.
So we built a free publisher platform that lets blogs, media sites, and developers embed live procurement intelligence widgets directly into their websites.
No API keys.
No backend integration.
No database maintenance.
Just copy, paste, and publish.
The Problem With South African Procurement Data
South Africa publishes thousands of tender opportunities and contract awards every month through multiple government procurement systems.
The raw data exists, but using it at scale is painful.
Even basic editorial questions are difficult to answer:
Which companies are winning contracts?
Which provinces are spending the most?
Which sectors are seeing procurement growth?
Which suppliers dominate specific industries?
Most publishers do not have:
data engineering teams,
procurement analysts,
ETL pipelines,
or infrastructure to continuously process OCDS-style datasets.
That means procurement journalism often becomes static and reactive instead of live and data-driven.
We thought procurement intelligence should behave more like embeddable web infrastructure.
The Publisher Platform
We built the Tenders SA Publishers Hub to expose live procurement data through embeddable widgets and public APIs.
The widgets update automatically from our procurement aggregation pipeline and can be embedded into:
WordPress,
Ghost,
Webflow,
Shopify,
Next.js,
React,
or plain HTML websites.
The system currently exposes:
Winners Feed Widget
Sector Trends Widget
Top Companies Leaderboard
Provincial Heatmap
The widgets are powered by the same OCDS-aligned procurement database used internally across the Tenders SA platform.
- Winners Feed Widget
This became the most requested widget almost immediately.
It renders a live stream of recently awarded government contracts including:
supplier names,
award values,
provinces,
sectors,
and awarding entities.
Instead of manually updating procurement tables, publishers can embed a real-time award feed directly into articles or sidebars.
The data refreshes automatically every hour.
Example use cases:
investigative journalism,
procurement monitoring,
regional business news,
industry-specific contract tracking.
A construction publication can filter for construction awards only.
A provincial portal can track local government spending.
An ICT publication can surface software and cybersecurity contracts.
- Sector Trends Widget
The Sector Trends Widget is designed more like a lightweight procurement analytics layer.
It visualises:
sector-level procurement activity,
rolling award values,
and market movement across industries.
For editorial teams, this solves a major problem:
most procurement reporting talks about “increased spending” without actual data visualisation.
Now an article discussing infrastructure growth can embed live procurement trend charts directly beside the analysis.
The widget supports filtering by:
province,
category,
and sector.
The data updates continuously from the underlying procurement aggregation pipeline.
- Top Companies Leaderboard
This widget surfaces which suppliers are capturing the most government procurement value.
It ranks companies by:
total award value,
contract activity,
province,
and category.
This became surprisingly useful for:
economic development portals,
local business publications,
procurement consultants,
and supplier intelligence tracking.
Instead of manually building leaderboards from spreadsheets, publishers can embed live rankings directly into their sites.
The API Layer
The widgets themselves are powered by a public REST API.
Endpoints currently include:
/api/widgets/winners-feed
/api/widgets/top-companies
/api/widgets/sector-trends
The API is intentionally simple:
JSON responses,
no OAuth,
no API keys for basic usage,
and lightweight enough for direct frontend integration.
Example:
fetch('https://www.tenders-sa.org/api/widgets/top-companies?province=gauteng&limit=5')
.then(res => res.json())
.then(data => console.log(data))
We wanted publishers and developers to integrate procurement intelligence without building an entire procurement platform themselves.
Why We Avoided “Enterprise Procurement Software” Complexity
A lot of procurement tooling collapses under its own complexity.
Heavy dashboards.
Complex onboarding.
Locked APIs.
Enterprise sales cycles.
Mandatory integrations.
That approach excludes:
independent publishers,
small media teams,
niche industry blogs,
and local developer communities.
Our goal was different:
make procurement data as embeddable as a YouTube video.
That heavily influenced the architecture:
iframe embeds,
lightweight JS widgets,
edge caching,
CDN delivery,
zero-auth public endpoints,
and no-code configuration.
OCDS Matters More Than Most People Realise
One of the hardest parts was not the frontend widgets.
It was standardising procurement data.
Government procurement records are messy:
supplier names vary,
categories are inconsistent,
notices arrive in different formats,
and award structures differ between entities.
The platform normalises this data into a structured model aligned with OCDS principles before it reaches the widget layer.
Without that normalisation layer, live procurement widgets would become unreliable very quickly.
The Unexpected Outcome: Procurement Syndication
The original idea was just embeddable widgets.
What emerged instead was a procurement syndication network.
Publishers started embedding live procurement intelligence into:
local business portals,
sector-specific blogs,
procurement newsletters,
municipal information sites,
and trade publications.
Instead of procurement data living only inside government portals, it now flows through the broader South African web ecosystem.
That distribution effect matters more than the widgets themselves.
Developer Experience Was a Core Requirement
Most government-adjacent tooling has terrible developer experience.
We wanted:
simple embeds,
predictable APIs,
lightweight integration,
and framework compatibility.
The widgets work with:
React,
Next.js,
Vue,
WordPress,
Ghost,
Shopify,
Webflow,
and static HTML.
No vendor lock-in.
No proprietary CMS requirements.
Repositories & Developer Resources
Main platform:
https://www.tenders-sa.org
Publishers Hub:
https://www.tenders-sa.org/publishers
Developer API docs:
https://www.tenders-sa.org/publishers/developers
Example widget integrations and SDK snippets are available throughout the developer portal.
Final Thoughts
South African procurement data should not require a data engineering team to understand.
Publishers should be able to:
embed it,
analyse it,
visualise it,
and distribute it easily.
That was the core idea behind the publisher platform.
The widgets are not the product.
The real product is turning fragmented public procurement data into infrastructure developers and publishers can actually build on top of.
