African public procurement
Tender, award and party records built directly on the Open Contracting Data Standard (OCDS) — with supplier, buyer and monthly roll-ups, and natural-person parties stripped from every published table.
What's inside
Tenders
One row per ocid — title, status, category, value and buyer, sourced from the official OCDS release feed.
Awards & parties
Award values and the organizations behind them. Party records are classified; natural persons are excluded from publication.
Analytics
Pre-built supplier, buyer and monthly roll-ups so you can rank counterparties and track spend over time without rebuilding the joins.
Data dictionary (core tender table)
| Field | Type | Description |
|---|---|---|
ocid | string | Open Contracting ID — the globally unique process identifier. |
country | string | ISO country code of the procuring jurisdiction. |
title | string | Tender title as published. |
status | enum | Tender status from the OCDS release. |
category | string | Procurement category (goods / works / services). |
value_amount | number | Tender value where disclosed. |
value_currency | string | ISO currency of the value. |
release_date | date | OCDS release date. |
buyer_name | string | Procuring entity (organization only). |
source_ref | string | Reference back to the OCDS release package. |
license_class | string | License Register code (OCDS feed is openly licensed — see Trust). |
Party tables carry a party_type classification (organization / natural_person / unknown). Only organization parties reach the published product — enforced in the model layer, not by convention.
Try before you buy
Like every dataco SKU, AF-TENDER ships with its dictionary, a provenance annex and a measured metrics file. The free sample lets you validate the OCDS lineage and the natural-person exclusion for yourself.