Commodity operations
Sustainability records, purchasing, warehouse movements, and source-to-stock traceability.
Made for commodity operators and sourcing teams.
Overview
This platform family is under active development. The scope below describes its intended design; deployment readiness and supported capabilities must be confirmed for each engagement.
Commodity businesses need to understand both the source of their supply and what happens after a purchase. Farmer records, farm boundaries, sustainability evidence, purchase entries, and warehouse movements often live in different tools. That separation makes it harder to investigate a transaction, follow a bag of produce, or assemble evidence for a buyer.
Baobab brought these activities into a coordinated platform. Sustainability teams manage the people, places, and evidence behind the supply chain. Purchasing teams use that foundation to record transactions and track stock. Shared records connect the two modules without duplicating the farmer registry or organisation structure.
What is included
Sustainability Management System
Understand the source
The Sustainability Management System supports configurable geographic hierarchies, buying stations, farmer enrolment, and farm management. Teams can bring existing records in through bulk import, manage farmer status, and investigate possible duplicates.
Farm and plot records include geometry capture and map overlays, making land information usable alongside registry details. Deforestation-risk assessments and EUDR-oriented reporting organise evidence around sourcing decisions. Surveys and sustainability programmes connect assessment to field activities, participant records, inputs, and remediation work.
An example workflow begins with an enrolled farmer and a mapped farm. A sustainability team gathers survey evidence, evaluates relevant risk information, and records programme activity. That context becomes available to downstream operations through the same underlying farmer and farm foundation.
Purchasing Management System
Follow the commodity
The Purchasing Management System handles individual and bulk purchase entry, seasonal configuration, pricing, and yield-rate settings. Teams record purchases against the relevant operational context and follow stock through evacuation and warehouse workflows.
Bag-level barcode scanning and traceability connect physical handling to digital records. Warehouse views expose capacity thresholds, while operational dashboards and yield comparisons help managers understand activity across the purchasing process.
For a buying operation, the journey moves from a purchase record to stock handling, evacuation, and warehouse receipt. Traceability gives teams a way to investigate the relationship between produce, its recorded source, and subsequent movements. It supports operational accountability without asking staff to reconstruct that history from unrelated spreadsheets.
Built with
Baobab built the platform as separate frontend and backend feature modules composed into a Next.js application and a Hono API on Cloudflare Workers. Shared validation and permission contracts connect the interface to the API, helping both sides use the same definitions for important operational records.
The architecture separates geographic, sustainability, purchasing, and warehouse concerns while preserving their business relationships. Map-based information is integrated into the same product as transactional workflows. This is a practical example of domain modelling across activities that require different interfaces but depend on the same source data.
Questions
Is this available for deployment?
Deployment readiness has not yet been verified for this catalogue entry. Contact us to discuss current scope, release gates, and your requirements.
Who owns this software?
This is owned engineering work from The Baobab, a brand of Fortezza Nuova Enterprise. Deployment and licensing terms are agreed for the relevant product.
Run Commodity operations in your organisation
Discuss the capabilities you need, deployment environment, and integration responsibilities. We will confirm current readiness and agree a scope before committing to a release.