Email Alerts for Aptean
Get the right alert to the right people, by email, the moment it matters, so quality, expiry and compliance issues are dealt with before they cost you.
Aptean's Food and Beverage modules raise alerts when something needs attention. A lot is about to expire, an inspection status changes, a compliance certificate is running out. Out of the box, Aptean sends those alerts to an HTTP endpoint or an Azure Service Bus. To turn them into emails, someone has to design, build, secure and maintain Power Automate flows or Azure Logic Apps, often a separate one for each module. Until that work is done, alerts sit on a page in Business Central until someone remembers to look.
This app replaces all of that with one built-in email approach for every Aptean module. Alerts are emailed straight to the team responsible from your own Business Central email account, and everything is set up on familiar Business Central pages.
Why use it
No integration project
You don't need Power Automate flows, Logic Apps, a Service Bus or Azure subscriptions. That means no additional licences, no connections or credentials that can expire, and nothing outside Business Central to monitor. Switch on Send Email From BC on a module's setup page and its alerts start arriving by email.
One way of doing it, across every module
Expiration, inspection, status management, non-conformance and compliance alerts all work the same way. They share the same recipient lists, the same kind of routing rules, the same send history and the same retry behaviour. Your administrators learn one setup instead of five separate integrations, and so do your support partners.
Act before it becomes a problem
Expired stock, a rejected lot that keeps moving or a lapsed supplier certificate can lead to write-offs, recalls or a failed audit. Every alert is emailed as soon as it is raised, so your teams can act while there is still time to sell, rework, quarantine or renew.
The right people, not everyone
Emails don't go to one shared inbox that everybody learns to ignore. Simple rules send each alert to the team that owns it, based on location, item category or the type of alert. For example, the Auckland warehouse hears about Auckland stock, and the chilled team hears about chilled items.
Set up recipients once, use them everywhere
A Distribution Group is a named list of people, such as QA Team or Auckland Warehouse. It can include Business Central users and external email addresses. You maintain each list in one place and use it across all notification types. When someone joins or leaves a team, you update one list.
Never lose track of a supplier or customer certificate
Compliance documents for vendors, customers, items, lots and your own company are checked every day. The right people get a reminder ahead of the expiry date and keep getting one at an interval you choose until the document is renewed. If you want, the app can also create a Business Central task, so the follow-up doesn't depend on someone's inbox.
Proof that people were told
Every email sent, or failed, is recorded together with who received it and why. When an auditor or customer asks "were you notified?", you can show the answer on the alert itself.
Your branding, your wording
Emails are built from report layouts you can customise. You can attach a full PDF report too. For example, the included Non-Conformance Detail report gives the recipient everything they need without logging in.
Looks after itself
Emails are sent through your existing Business Central email account. Failed emails are retried automatically by a Business Central job, and old history is removed by the standard retention policies.
What it covers
| Aptean module | You are emailed when… | Who receives it |
|---|---|---|
| Expiration Management | An item or lot is approaching or past its expiration date, its expiration date changes, or a purchase falls short of minimum shelf life | The Distribution Group whose rule matches the alert type, location, item category and inventory posting group, otherwise a default address |
| Inspection Status | A lot's inspection status changes, for example to Released, Rejected or On Hold | Matched by rule in the same way as Expiration Management |
| Status Management | A tracked record, such as a non-conformance, moves to a new status | The person on the alert, plus an optional Distribution Group per status |
| Compliance Documents | A company, customer, vendor, item or lot compliance document is about to expire, or has expired | The Distribution Group on the matching Compliance Notification Rule |
| Non-Conformances | The person responsible for a non-conformance follow-up action changes | The new responsible person |
An expiration warning is only a warning. It doesn't change the lot's inspection status. If someone then puts the lot on hold or rejects it, that change raises its own inspection status email. A lot can trigger either alert, or both.
How it works
- An alert is raised by the Aptean module, exactly as it is today.
- The app works out who needs to know. It uses your notification rules and Distribution Groups, or the address already on the alert.
- An email is sent directly from Business Central, either immediately or by a background job every few minutes. No external flow or service is involved.
- The result is logged against the alert. Anything that failed is retried automatically.
Every alert page also has a send now action, so you can resend an alert or send it on demand.
Prerequisites
The following apps must be installed:
- Aptean Status Management for Food and Beverage
- Aptean Expiration Management for Food and Beverage
- Aptean Inspection Status for Food and Beverage
- Aptean Compliance Documents for Food and Beverage
- Aptean Non Conformances for Food and Beverage
- Aptean Quality Control for Food and Beverage (BC)
- Aptean Quality Enhancements (Theta Systems Limited)
- Aptean Integration Layer for Food and Beverage
- Aptean Foundation Layer for Food and Beverage
You also need a working email account set up in Business Central.
Next steps
Go to Setup for step-by-step instructions. Most customers start like this:
- Create a Distribution Group for each team.
- Turn on email for the modules you use.
- Add a few rules to route alerts to the right team.
You can switch modules on one at a time.