Deployment, data isolation, statutory payroll, the cold chain and what an auditor will find. If your procurement committee has a question that is not here, ask it in the enquiry and we will answer in writing before the demo.
It replaces the spreadsheets, notebooks and WhatsApp threads that each department keeps separately. Production, pack house, cold room, inventory, logistics, sales, procurement, stores, financials, HR, payroll and compliance all write to one database, so a graded stem, its cold room hours, its invoice and its spray history are the same record seen from different desks.
Seventeen modules grouped into five domains — Grow, Measure, Move, Sell & Buy and Run — sharing a single database. They are not separate products that sync overnight; a change in the pack house is immediately the same record finance invoices and compliance audits.
No. Every record is scoped to a single farm tenant. There are no shared tables of farm data and no cross-farm queries, so yields, buyers, costs and payroll stay inside your own tenant. Flori-Core is sold to the farm and deployed per farm.
No. Flori-Core is software that helps farms maintain and evidence their own certifications. It does not issue, grant or guarantee any certification, and is not affiliated with, partnered with or endorsed by any certification body. Schemes such as GlobalG.A.P, Rainforest Alliance, MPS and KEPHIS requirements are referenced only as certifications a farm may track inside the system.
Certificates, spray logs and chemical usage are captured at the point of work by the person doing it, rather than reconstructed the week before an inspection. The certificate registry raises alerts ahead of expiry, spray logs record product, rate, operator, block, date and re-entry interval at application, and stores movements reconcile against what was actually applied in the field.
Yes. The audit trail is append-only across every module: nothing can be edited or deleted after the fact, and corrections are written as new entries. Each row expands to the field-level diff — the old value, the new value, the named user or the system rule that fired, the timestamp in EAT, and the source address and client.
Yes. Permanent and casual workers sit in one workforce register with contracts, training records, handler certification tracking and appraisals. Monthly payroll runs cover salaried and daily-rate casual workers, apply NSSF, NHIF and PAYE deductions, support bulk approval, and deliver payslips by email and SMS.
KES, USD and EUR are held in one ledger, so costs in shillings and sales in euros or dollars reconcile without a parallel spreadsheet. Financials cover P&L, balance sheet, cash flow and budget versus actuals.
Automation rules fire on thresholds in real time — for example alerting when a cold room exceeds its ceiling, or triggering irrigation below a soil moisture set point. Alerts reach supervisors by SMS and WhatsApp rather than waiting for someone to be at a desk, and every rule run is logged and attributable.
Yes. Logistics covers shipment planning, route mapping from the farm to JKIA, the dispatch queue, the fleet register and driver assignment. Cold room check-in and check-out, FIFO inventory and cold chain handover from the pack house sit on the same record.
Pricing is quoted against hectares under production, headcount and the modules you deploy. Ask on the demo call and we will put it in writing for your procurement committee.
A walkthrough against your own operation rather than a slide deck. Tell us the shape of the farm and we run the demo on the departments that matter to you — pack house and cold chain, payroll and casual labour, or the compliance registry. If you are reviewing with a committee, we send written answers on hosting, data isolation, roles and the audit trail ahead of the call.
We walk the modules that matter to your farm and answer procurement's questions in writing. The compliance and security detail is the page committees usually read first.