An ops layer built for seasonal stock, rural delivery, and real traceability.
OpsUI gives NZ agriculture and horticulture operators an operations system that handles seasonal demand swings, batch traceability for compliance and recalls, and rural delivery via the carriers that actually serve those addresses. Built in NZ for ANZ farming and ag-supply.
The same three problems, every time.
- §01
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.
- §02
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.
- §03
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.
4 modules, à-la-carte, NZ$1,596 / month all-in.
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.
Inventory Management
Stock by SKU, bin, batch and location with full transaction history
FromNZ$399 / moOrder Management
Order capture, status, priorities and pick-task generation in one module
FromNZ$399 / moShipping/Outbound
Pack queue, label print, tracking and end-of-day manifest
FromNZ$299 / mo- Rollout
Procurement
PO workflow, vendor records, three-way match and spend analytics
FromNZ$499 / mo
These modules are recommended — not required. Mix in or drop out anything that does not fit your operation. Pricing scales linearly with the modules you keep.
The honest answers.
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?
Yes — batch and lot tracking is built into the Inventory Management module. Recall queries can pull every customer who received a given batch in seconds. Full audit trail of every inventory movement (receipt, transfer, pick, dispatch). Specific MPI compliance scope (record retention, audit log format) is confirmed during implementation against your operation's specific MPI category.
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.
Agriculture & Horticulture? Let's scope it.
Walk us through your current setup and we will show you which OpsUI modules fit, what the rollout looks like, and where the gaps are.