Are You Often Waiting for a Response to Your Purchasing Orders? Here's How to Automate Procurement Notifications

How Can Purchasing Notifications Work Without Manual Follow-Up?

AI Automationcan help connect procurement systems with email and chat platforms to send notifications based on status, transaction value, deadline, or certain conditions.

• New requests can immediately notify the approver.

• Unprocessed approvals can be reminded after8, 24, or 48 hours.

• Updates on quotations, POs, or vendors can be forwarded to the relevant PIC.

• Messages can be differentiated based on the level of urgency.

• Each notification can be triggered automatically from a status change in the system.

The goal is not to create more notifications. On the contrary, the workflow should ensuremessages are only sent when there is an action that needs to be taken.

From Purchase Request to PO, When Should Notifications Be Sent?

In a procurement workflow, notifications should follow specific events, not be sent every time a small change occurs.

With AI Automation, the flow can be made like:

Purchase Request → Validation → Approval → RFQ → Vendor Response → Evaluation → PO → Delivery

Each event can have different recipients and channels.

1. Notification When Request Incoming

When a user submits a purchase request, the system can read the department, transaction value, and purchase type.

For example, a request worthRp. 150 millionrequires approval from Manager and Finance.

With AI Automation, notifications can be sent directly to approvers via email or chat.

The message should contain important information such as the request number, requester, purchase amount, category, and a link to the system.

2. Reminder of Unprocessed Approvals

Late approval often delays the entire procurement process.

Example workflow:

Request Created → Wait 24 Hours → Check Status → Pending? → Send Reminder

If there is still no action after48 hours, the system can escalate to superiors or procurement.

With AI Automation, procurement does not need to check each pending request one by one.

3. Connecting Email and Chat

Not everyone actively monitors email all day long. Chat, on the other hand, is usually more readily visible for operational purposes.

Therefore, channels can be distinguished.

For example:

Email → Detail Purchase Request

Chat → Urgent Approval Reminder

Email → Vendor Quotation Update

Chat → PO Issue atau Escalation

With AI Automation, one event can trigger different channels based on its level of importance.

4. Notifications Based on Transaction Value

Not all purchases have the same level of urgency and risk.

For example:

≤ Rp50 juta → Manager Notification

Rp50–250 million → Manager + Finance

>Rp250 million → Manager + Finance + Director

With AI Automation, the transaction value can be a condition for determining who receives the notification.

This makes messages more relevant and reduces the risk of procurement information being shared with unnecessary parties.

5. Notification When PO Has Problems

Workflow can also monitor the status after the PO is created.

For example:

PO Created → Vendor Confirmation → Delivery Tracking

If the vendor has not confirmed in2 working days, the system can create reminders.

If the SLA is exceeded, the notification can be forwarded to procurement.

With AI Automation, problems can be identified sooner before they impact delivery schedules.

How to Make Notifications Unobtrusive?

• Determine which events really require notification.

• Differentiate between informational notifications and required actions.

• Use email for detailed information.

• Use chat for more urgent needs.

• Set a reminder SLA, for example 24 hours.

• Create an escalation after a certain deadline.

• Avoid sending the same message to too many people.

• Include the request or PO number as an identifier.

• Keep a log of every notification.

• Make sure the recipient's permissions are correct.

• Use legal software for companies and officially licensed software.

Before fully implementing the workflow, test it with several scenarios. For example, a purchase request.Rp. 30 million, Rp. 100 million, and Rp. 300 million. Ensure each transaction results in the appropriate recipient and channel.

FAQ

1. Can procurement notifications be sent to email and chat?

Can. AI Automationcan connect events from the procurement system with available notification channels.

2. Can the approval reminder be automated?

Yes. The workflow can check the request status after a specified interval, such as 24 hours.

3. Can notification recipients differ based on the purchase value?

Yes. The transaction value can be used as a conditional rule to determine the recipient.

4. Can one request send multiple types of notifications?

Yes. For example, emails are sent for transaction details, while chats are used for reminders that require immediate action.

5. What if the approver doesn't respond?

Workflow can send reminders and then escalate after a certain SLA, for example 48 hours.

6. Can notifications be connected to ERP?

Yes, as long as the ERP provides an appropriate API, webhook, or integration mechanism.

7. Do all procurement changes need to be sent as notifications?

No. It is recommended that only events that require information or action be sent to the user to avoid notification fatigue.

8. Can notification history be tracked?

Yes. Workflow can keep a log of delivery times, recipients, events, statuses, and delivery results.