Agrena Florena

Automated file transfer for the documents and data trading partners expect — shipment files out, confirmations in, on a schedule.

Backups, data housekeeping, master maintenance and the operational tasks that keep the platform healthy.

Stock on hand, consumption by block, ageing and valuation — the inventory view finance and agronomy both read.

Counts are entered against system balances, variances are explained and adjustments are posted with an approval behind them.

Transfers leave the source store, sit in transit and land on the destination balance only when received.

Every movement — receipt, issue to block or packhouse, return and write-off — posts against the store so the balance stays live.

Where stock lives and what may live there: stores, item masters, categories and units of measure.

Requisitions from the farm and packhouse are approved, ordered against a vendor, received into store and matched to the invoice.

Purchase items, specifications, vendors and agreed rates — the reference the purchase cycle draws on.

Standing orders and spot sales are matched to available grade and volume, so allocation follows commitment rather than guesswork.

Harvest against plan, grade mix, shipment performance and revenue per stem, drawn from the same transactions the floor entered.

Day-to-day worksheets that put the plan in the hands of the team — harvest sheets, grading sheets and dispatch sheets, printed or on screen.

Invoices are generated from shipped quantities and agreed prices, in the customer currency, with credit notes for rejections and claims.

The vehicles that move flowers from farm to packhouse to airport, with trip records, driver and temperature handling.

Packed boxes are consolidated into a consignment with its airway bill, phytosanitary paperwork and customer allocation, then dispatched and tracked.

Harvested stems are graded by length and quality, bunched, sleeved and packed to the customer specification, with output and waste captured per grader and per batch.

Chemical and fertiliser applications, irrigation and cultural operations are logged per block with their date, dose and operator — both an agronomy record and a residue-compliance record.

Harvest records stems cut per block, per variety, per picker and per day — the number every downstream grade, pack and invoice is derived from.

Production plans the crop: which variety in which block, planted when, expected to yield what — the baseline that harvest is later measured against.

Company, financial-year, numbering series, tax and integration settings — the switches that shape how every module behaves.

Varieties, grades, farms, blocks, customers, agents, currencies and units — defined once and referenced everywhere, which is what keeps harvest, grading and invoicing speaking the same language.

A full trail of inserts, updates and deletions with the user and timestamp behind each — the record that settles a stock or grading dispute.

Requests raised anywhere in Agrena — purchase, transfer, write-off — are routed to the right approver and tracked to a decision.

Roles bundle screen and action privileges so a grader, a packhouse supervisor and a finance user each see only their own working surface.

Employee records underpin harvest capture, grading-hall output and payroll — every quantity recorded on the farm traces back to the person who recorded it.

Administrators create and maintain the people who can log into Agrena. Each user is linked to a role, and Menu Management decides exactly which of the 26 modules and their screens that role can reach — so access is granted by menu, not by memo.