For exporters
Know which farm is in the pallet, before the buyer asks.
The exporter portal runs the packhouse — receipts, quality, packing, pallets, cold chain, orders and documents — on top of records that reach all the way back into your suppliers’ spray diaries. When a question arrives from Hamburg, the answer is a query, not a week.
xport.softfarm.co.ke · Separate tenant, same backbone as your producers.
Selector: LOT-2026-0001
Frozen 3 September · Chlorpyrifos exposure
Packhouse operations
Receipt to pallet to purchase order
Everything a packhouse does day to day, with the traceability thread carried through every step rather than bolted on at the end.
Suppliers
Linked producer farms plus external suppliers who are not on the platform, each with their own compliance history.
Incoming & goods receipts
Dispatches arriving from linked farms become goods receipts with their crop, spray history and residue results attached. Reject or quarantine at the gate.
Quality
Quality checks recorded against the receipt, so a decision to accept is evidenced rather than assumed.
Production plans & packing
Plan against demand, then run packing that consumes receipts and produces finished-goods lots.
Pallets & cold chain
Build pallets from lots, assign storage zones and keep the temperature record that the buyer’s specification requires.
Inventory & mass balance
Finished-goods stock with a mass balance that reconciles what came in against what was packed, shipped and written off.
Sales & export documents
Buyers, sales orders, export documentation and commercial invoicing, with the ledger posted behind them.
Procurement
Purchase orders and vendors for packaging, inputs and services.
Supply graph · standing views
Rendered in-app as node-link graphs. No database console required.
Trace & recall
A recall is an impact assessment, not a logistics exercise
SoftFarm is deliberate about what recall means here. Simulating a recall freezes a dossier — a numbered, dated snapshot of exactly what was affected and who holds it — and then routes each bucket to the feature that actually handles it.
- Select by lot, producer, crop or date range. The dossier resolves affected goods receipts, finished-goods lots, pallets and buyers.
- Split the cartons into packed, shipped and on-hand, so the response is proportionate to where the product actually is.
- On-hand stock is written off with a quality reason, removing it from inventory and posting the loss to the ledger.
- Shipped cartons come with the buyers and orders to notify — handled off-system, but never guessed at.
- Not yet packed goods are rejected or quarantined at the goods receipt.
There is no inbound “receive recalled goods” step and returned product is not re-inventoried. A closed loop — quarantine hold, returns receipt, disposition — is on the roadmap, not in the product.
Why it works
Your suppliers are tenants, not rows in a spreadsheet
A linked producer keeps their own account, their own data and their own login. What crosses the boundary is the dispatch — and with it, the provenance you would otherwise have to take on trust.
- No re-keying. A dispatch becomes a goods receipt with its crop, applications and residue results intact.
- No blind spots. If a supplier sprayed something Europe does not allow, you see it against the lot — not after the border does.
- External suppliers too. Farms not on the platform are still first-class in the packhouse; they just carry less provenance, and the system is honest about that.
- Separate tenancy. Exporter roles and permissions are distinct from producer ones, enforced server-side.
Traceability you only assemble after a complaint is not traceability. It is archaeology. Why the chain is recorded as work happens, not reconstructed afterwards.
Run the exposure query against your own chain.
Ask which of your buyers is holding produce from a supplier you have just found a problem with. On a normal system that is a week of paperwork. Here it is a screen.