Skip to content

Agriculture & Horticulture

Agriculture & Horticulture, from workflow to modules.

Coordinate seasonal purchasing, inventory and dispatch across your operation.

Fit comes first. MPI export certification and specialist seasonal or packhouse workflows require separate evaluation. Confirm rural delivery and traceability requirements during scoping.

A working starting point

Follow the work.

  1. 01Purchase
  2. 02Receive
  3. 03Track stock
  4. 04Dispatch

Seasonal stock breaks generic ERPs

Demand peaks twice a year, drops to a trickle in between. Standard reorder points say to hold safety stock year-round and tie up working capital, or to stock out at season start. Both wrong.

Rural delivery breaks international systems

Rural delivery numbers, farm gate names, paddock-level locations: global ERPs cannot validate these addresses. Orders sit in a "address verification failed" queue while the season passes.

Batch traceability for compliance is on paper

MPI audit asks for the batch trail on a product. The team spends three days assembling it from delivery dockets, spreadsheets, and supplier emails. Recall capability does not actually exist.

Conceptual illustration: Separated batches of stock, matching identity tabs and one designated review tote.
Inventory Management
Inventory Management: Inspect the product interface alongside the workflow. Confirm your own records and operating requirements during a review.
Product example using sample data

Inspect the product interface alongside the workflow. Confirm your own records and operating requirements during a review.

Modules and responsibilities

What each module contributes.

Keep the parts you need. These recommendations do not create a separate package or change the catalogue price.

Conceptual illustration: Order, stock and dispatch work cells fitted to a modular plan with one optional extension.
Agriculture & Horticulture: suggested modules and published monthly prices
ModuleJob it performsDelivery statusMonthly price
Inventory ManagementTrack stock across bins and sites.Catalogue moduleNZ$399
Order ManagementCapture orders and track progress.Catalogue moduleNZ$399
Shipping & outboundPack, label and dispatch orders.Catalogue moduleNZ$299
ProcurementManage purchases and supplier records.Built on rolloutNZ$499
Dashboards & ReportingSee live performance and build reports.Catalogue moduleNZ$399

NZ$1,995 / month module subtotal

Sum of the suggested module licences. User allowances, additional seats, connectors and rollout requirements must be considered separately. Existing starter-pack pricing may suit a different combination.

Check packages and configure pricing

Inventory Management owns batch / lot / expiry tracking; Procurement owns supplier replenishment and seasonal forecasting; Shipping owns NZ rural delivery via NZ Couriers and NZ Post. Bundle handles ag-specific patterns without a separate ag-vertical product.

Before you decide

Requirements to confirm.

Conceptual illustration: A tabletop warehouse plan and representative records with a magnifying lens at a handoff.
  • MPI export certification and specialist seasonal or packhouse workflows require separate evaluation. Confirm rural delivery and traceability requirements during scoping.

Questions about this workflow.

Can OpsUI handle seasonal demand forecasting?

Yes. The Analytics module surfaces seasonal patterns from historical sales data, and Procurement can drive supplier orders against forecast rather than against a static reorder point. The forecasting depth is honest mid-tier, not as deep as a dedicated S&OP platform, but well above static reorder-point logic.

Does OpsUI support rural delivery addresses?

Yes. NZ Couriers and NZ Post integrations handle rural delivery numbers, farm gate names, and the address conventions NZ rural addresses actually use. Address validation happens against the NZ Post / NZ Couriers address book, not against a global generic.

Can OpsUI handle MPI traceability requirements?

Bring your identification, handling and assurance requirements to the workflow review. We need to confirm the exact records, controls and reports with representative data before treating this as a fit. MPI export certification and specialist seasonal or packhouse workflows require separate evaluation. Confirm rural delivery and traceability requirements during scoping.

Do you integrate with supplier portals like Farmlands or RD1?

Supplier-portal integrations are scoped during rollout against your specific supplier relationships. The REST API and standard OpsUI integration patterns handle the common shapes; we will not pre-claim Farmlands / RD1 / PGG Wrightson on this page until they are wired against a specific customer.

Keep exploring.

Related operating models.

Agriculture & horticulture ERP requirements: neutral guide

Your next step

Make this specific to your operation.

Walk through your current process, confirm the fit and scope the modules around the work you need to run.

Review my workflowExplore the live demo

Pick a role, enter a work email or mobile, and explore sample workflows. No password or credit card.