Exporting Tenders-SA Data: Excel, CSV, and Structured Formats Explained

Procurement data is most valuable when it can be analysed, shared, and integrated into your existing workflows. While browsing tenders and company profiles on the Tenders-SA website provides immediate insight, many business processes require data in structured file formats for offline analysis, reporting, database integration, or archival purposes.

Tenders-SA provides data export capabilities across five datasets and four structured formats. This guide explains the available formats, when to use each one, and how the export system works.

For a small business, exports are often the bridge between Tenders-SA and the rest of the tools the business already uses — an Excel-based bid tracker, an internal database, a supplier scorecard maintained by a procurement team, or a data warehouse used for market research. Rather than requiring every downstream system to integrate directly with an API, the export system gives you a file you can drop into whatever process already exists, which is often the fastest way to get value out of the data without any development effort.

Available Export Formats

Four structured formats are available for data export: Excel, CSV, JSON, and XML. Each has different characteristics that make it suitable for different use cases.

Excel (.xlsx)

The Excel format produces a standard .xlsx workbook file with a single worksheet. Column headers are human-readable (for example, Tender ID, Title, Reference Number, Source Organization) rather than raw database field names. Column widths are auto-sized to fit content, and numeric values such as award amounts are preserved as numbers rather than text strings.

Excel is the best choice when you need to share data with team members who will review, filter, or analyse it in spreadsheet software. The formatted headers and proper numeric types make it immediately usable without additional data cleaning.

The current implementation produces a single-sheet workbook. Multi-sheet exports (for example, one sheet per province or category) are not available.

CSV (.csv)

The CSV format follows the RFC 4180 standard with UTF-8 encoding. It uses comma separators and quoted fields where necessary. CSV files are compact and open in virtually all spreadsheet and database applications.

CSV is the recommended format when you need to import data into a database, CRM, or data analysis tool. Its simplicity and wide compatibility make it the most portable export format.

JSON (.json)

The JSON format exports data as a pretty-printed array of objects. Each object represents one record with key-value pairs matching the dataset fields. JSON preserves data types and nested structures naturally.

JSON is the best choice for developers integrating Tenders-SA data into applications, APIs, or data processing pipelines. The structured format makes it easy to parse programmatically without custom mapping logic.

XML (.xml)

The XML format wraps records in a standard <?xml> envelope with row elements. Field values are escaped for XML safety. This format is primarily useful for integration with legacy enterprise systems that expect XML input.

In practice, most Tenders-SA users default to Excel or CSV rather than JSON or XML, because their downstream workflow is usually spreadsheet-based rather than code-based. JSON and XML exist primarily to serve developers who are pulling exported data into a custom application, a data pipeline, or an internal reporting tool that expects structured input rather than a spreadsheet file. If you are unsure which format to choose, Excel is a safe default for a one-off review and CSV is the safer default if the file needs to be imported into another system afterward.

Available Datasets

Five datasets are available for export, each containing a specific set of fields relevant to different use cases:

• Active Tenders: Currently open tenders with fields including title, reference number, organisation, province, status, closing date, estimated value, type, and category.
• Closed Tenders: Tenders that have closed, with the same field structure as active tenders.
• Awarded Tenders: Tenders that have been awarded, including supplier name, award date, awarded amount, and award reference identifiers.
• Awarded Companies: Aggregated supplier intelligence with company names, total awards and value, last award date, provinces of operation, enterprise type, and B-BBEE level.
• Company Profiles: Detailed company profiles including registration number, B-BBEE level, CIDB grading, certifications, contact details, website, and public award history.

Filters and Record Limits

Exports can be filtered before generation to reduce the result set size and focus on relevant data. Available filters vary by dataset but include: date range, province, category, source organisation, award year, value range, and supplier name. Not all filters apply to every dataset.

The record limit can be set from 1 to 5,000 records per export. The default limit is 1,000. The 5,000 maximum is a hard cap designed to prevent memory issues during file generation. If your filtered dataset exceeds this limit, apply narrower filters and perform multiple exports.

A practical way to work within the 5,000-record cap is to filter by a meaningful business dimension before exporting, rather than trying to pull the entire dataset at once. A supplier interested only in construction opportunities in KwaZulu-Natal, for example, will get a far more useful export by applying both the category and province filters than by exporting all Active Tenders nationally and filtering afterward in a spreadsheet. Narrower exports are also faster to generate and easier to work with once downloaded, since the resulting file only contains rows that are actually relevant to the task at hand.

How the Export Process Works

When you request an export, the following process occurs:

1. Your request is validated server-side, including the Zod schema validation and feature gate check for your subscription plan.
2. The server queries the database with your filter parameters, retrieving up to 5,000 records.
3. The records are written to a file in your chosen format using the appropriate library: xlsx (SheetJS) for Excel, csv-writer for CSV, native JSON.stringify for JSON, or a custom XML generator for XML.
4. The file is saved to the exports directory and a download URL is generated.
5. The file is available for download for 24 hours before automatic deletion.

Data exports are available to users on the Starter subscription plan and above. Free-tier users do not have access to file exports.

Choosing the Right Format

The best format depends entirely on what you plan to do with the data:

• If you are building a dashboard, spreadsheet, or report for internal use, choose Excel for immediate usability.
• If you are importing data into a database, CRM, or analysis platform, choose CSV for maximum compatibility.
• If you are building a web application or API integration, choose JSON for easy programmatic parsing.
• If you are integrating with a legacy enterprise system that requires XML, choose XML.

Limitations

The export system has several limitations to be aware of. The 5,000-record cap means large-scale data dumps are not possible through this interface. All exports are single-sheet only for Excel. There is no custom column selection: you receive all fields in the dataset. There is no scheduled or recurring export capability: every export is generated on demand. Export files are stored for only 24 hours before automatic deletion, so downloads must be completed within that window.

Summary

Tenders-SA data exports provide flexibility for different workflows through four formats across five datasets. Excel for analysis, CSV for portability, JSON for development, and XML for legacy integration. Access the Export Configurator at /dashboard/exports to generate your first export.