Notifications

Notifications on the AgriERP mobile app are the way the system communicates with the people who need to act on something. A new work order has been assigned. A spray window is opening. A piece of equipment has a fault. A buyer has changed an order. A grower is overdue with a delivery. A supervisor’s approval is needed. Without a notification system that works, all of this information lives inside the system and waits for someone to discover it. With one, the right person is alerted at the right time, and the operation runs ahead of its problems instead of behind them.

This document describes how notifications work on the AgriERP mobile app: how they are triggered, how they reach the right person, how the user manages them, and how they integrate with the rest of the work.

1. Types of notifications

Operational notifications

Capability	What it means in practice
Work-order assigned	A new work order has been assigned to the worker, the crew, or the supervisor. Surfaces with full context: what, where, when.
Work-order reminder	Time-sensitive work approaching its window: “Spray work on Block 14 is scheduled in 30 minutes.”
Schedule change	An existing work order has been rescheduled, reassigned, or cancelled. Affected people are notified directly, not by accident discovery.
Spray window alert	Weather, wind, or other conditions opening a critical spray window, or closing one that was open. Time-sensitive for the agronomy team.
Harvest readiness	A block has reached harvest readiness per the agronomic indicators. The harvest manager and the relevant crews are notified.
Quality event	A quality issue captured at receiving, packing, or dispatch. Quality manager and the affected supervisors are alerted.
Equipment fault	An equipment fault reported in the field. Maintenance team is notified; the affected supervisor sees that their equipment is now out of service.
Inventory alert	Stock below threshold, expiry approaching, quality hold released. The right operations or warehouse person is alerted.

Approval and workflow notifications

Capability	What it means in practice
Approval request	A purchase order, an expense, a contract, a credit hold release needs the user’s approval. The notification opens directly into the approval screen.
Approval escalation	An approval has been pending beyond its expected response time and has escalated to the next level. The escalation target is notified.
Decision made on your request	The user submitted something for approval; the approver has decided. The user is notified of the outcome.
Workflow assignment	A workflow step has been assigned to the user: a verification to complete, a review to perform, an investigation to handle.
Workflow reminder	An assignment is overdue. The user is reminded; further escalation follows if it remains undone.

Communication notifications

Capability	What it means in practice
Direct messages	From a supervisor, a manager, the agronomist, the office. Short messages tied to operational context (a specific work order, block, or grower).
Broadcast announcements	From program management or the business to a defined audience: “Heavy rain forecast; spray work paused tomorrow,” “All crews report to the depot at 6am for the start of harvest.”
Grower communications	For grower programs: appointment reminders, payment confirmations, delivery confirmations, program updates.
Buyer-related communications	Buyer changes to orders, delivery confirmations, quality feedback, the right people in sales and operations are alerted.

2. How notifications reach the user

Delivery channels

• Push notifications: the primary channel for users with smartphones and active app sessions. Surfaces in the device’s notification tray; tap opens directly into the app at the relevant screen.
• In-app notification centre: every notification is also available in the in-app notification centre, accessible from the bottom navigation. Unread badge counter shows the new count.
• SMS: for users without smartphones or in areas with unreliable data, SMS delivery for critical notifications. Short, structured messages with the key facts.
• Voice call: for very critical alerts in workforces with low text literacy, automated voice calls in the user’s local language. Reserved for high-priority operational alerts.
• Email: for office-based users, managers, and external parties (buyers, vendors), email is often the right channel, especially for less time-sensitive communications and approvals.
• Web app notifications: users on the web app receive equivalent notifications in their browser session, so they do not miss something happening while they are at a desk.

Priority and urgency

Capability	What it means in practice
Critical	Immediate action required: safety event, equipment failure during work, critical schedule change. Push notification with high-priority sound, SMS backup, voice call if not acknowledged within minutes.
High	Action needed soon: spray window opening, approval blocking other work, urgent supervisor message. Push notification with standard sound; surfaces prominently in the in-app centre.
Normal	Standard operational notifications: work order assigned, schedule reminder, message received. Push notification with default behaviour.
Low	Informational: completed tasks, daily summaries, status changes that do not need an immediate action. Available in the notification centre; no push interruption.

Routing rules

• Role-based routing: a maintenance work order goes to the maintenance team. A spray window opens routes to the agronomy team. The system knows who should hear what.
• Assignment-based routing: for items already assigned to a specific person (a work order, an approval, a follow-up ticket), the notification goes to the assignee directly.
• Escalation routing: notifications that are unacknowledged or unactioned within a defined time escalate to the next level: supervisor, manager, director, depending on the urgency and the rule.
• Out-of-hours rules: non-critical notifications are held until the user’s working hours. Critical notifications break through. Each user has their working-hour profile.
• Do-not-disturb: users can put themselves on do-not-disturb for periods (off-duty, sleep, focus time). Critical notifications still break through; everything else is held.

3. Managing notifications

Acting on notifications

• Single-tap to action: tapping a notification opens the relevant screen: the work-order detail, the approval form, the message thread, the alert detail. The user can act immediately.
• Inline actions: for some notification types, the action can be taken inline without opening the full screen: approve or decline a request, acknowledge an alert, mark a task complete.
• Snooze: notifications can be snoozed for a defined period: “Remind me in an hour,” “Tomorrow morning.” The notification returns to the inbox at the chosen time.
• Dismiss: informational notifications can be dismissed once seen. Action-required notifications cannot be dismissed without action.
• Mark as read: the unread badge clears as the user reads notifications. The badge counter is the immediate signal of attention needed.

User preferences

• Per-category opt-in/opt-out: users can turn off notification categories they do not need (daily summaries, peer activity, broadcast announcements). Critical operational categories cannot be turned off.
• Channel preferences: users can choose their preferred channel for each notification type: push for work-order assignments, SMS for spray alerts, email for approval requests.
• Sound and vibration: users can adjust how attention-grabbing each priority level is. Some workers want every notification audible; others want their phone silent and rely on visual checks.
• Working-hour profile: the user’s working hours and time zone, used to time non-urgent notifications.
• Language: notifications are delivered in the user’s preferred language. The notification text is generated from templates in each supported language; not machine-translated at delivery.

Anti-noise principles

• Bundling: many small events of the same type are bundled into one notification. “5 work orders assigned for tomorrow” rather than 5 separate pings.
• Relevance filtering: users only see notifications relevant to their role and their assignments. A harvest worker does not receive maintenance notifications; a grower does not receive internal operational alerts.
• Throttling: the system avoids storms of notifications during high-activity periods. Repetitive triggers within a short window are throttled into summaries.
• Quiet hours and weekends: by default, low and normal priority notifications are held during quiet hours and weekends. Users who want continuous notifications can opt in.
• Auto-clear on action elsewhere: when the user handles something through another channel (the web app, in person), the corresponding mobile notification clears automatically. No phantom pings about already-resolved items.

4. Notifications and the rest of work

Notifications are not a separate workflow; they are the trigger layer that surfaces actions in the existing workflows. A work-order notification leads into Work Execution. An approval notification leads into the approval workflow. A spray-window alert leads into the agronomy planning view. A quality alert leads into the quality module.

• Deep linking: every notification carries the deep link to the relevant screen. The user is not dropped at a generic home screen; they land exactly where the action is.
• Context preserved: after the user handles the notification, they return to where they were. The notification is an interruption that the system manages, not a navigation rabbit hole.
• Audit trail: every notification, its delivery, its acknowledgement, and any action taken from it are captured. “Did you know about that?” has a structured answer.
• Cross-channel consistency: the same notification visible on the mobile app is visible on the web app and in email. The user can act from whichever channel suits the moment.

In summary

Notifications turn AgriERP from a system the user has to check into a system that tells the user what to do next. Operational, approval, and communication notifications cover the range of events that matter. Multiple channels, priority levels, and routing rules ensure the right people hear about the right things at the right urgency. User controls (preferences, snooze, do-not-disturb, working hours) prevent notification fatigue. Anti-noise principles, bundling, relevance filtering, throttling, quiet hours, keep the system useful for years, not just for the first week.

Used well, notifications are the difference between an agribusiness that runs ahead of its problems and one that is always reacting. The cost of building the system is low; the cost of not having it is much higher.