Overview
The Spendflo platform provides users with timely notifications for various tasks/ activities performed on the platform. The primary goal for Buying Hub notifications is to keep the users informed about the requests/ contracts being tracked by them on the platform. The users are notified based on their platform roles (Requestor, Approver, or Admin) or user roles (POC, Follower, or Contract Owner) via two different channels: Emails and Slack.
Note: To receive Slack notifications, the user must have installed the Spendflo App on Slack.
The images below provide sample notification for new procurement request submission.
Email Notification
Slack Notification
If you have opted for Spendflo to assist with negotiations in your Procurements, you will receive notifications based on your role below :-
| Event Description | Requestor | Approver/Pre-approver | Admin | POC | Followers |
| Request Submitted: User submits a new procurement request. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Pre-Approval Requested (if enabled): The request is sent to Approvers who would decide whether the request can proceed. | ✗ | ✓ | ✗ | ✗ | ✗ |
| Pre-Approved: One of the approvers has approved the request | ✓ | ✗ | ✗ | ✗ | ✓ |
| Pre-Approval Completed: All approvers have approved the request. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Pre-Approval Denied: The approver has denied the request | ✓ | ✗ | ✗ | ✗ | ✓ |
| Pre-Approval Overdue: The Approver has not yet approved/denied the request & is overdue. | ✗ | ✓ | ✗ | ✓ | ✗ |
| Negotiation Started: Negotiation process initiated. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Buyer Assigned : A buyer has been assigned to the request. | ✗ | ✗ | ✗ | ✗ | ✗ |
| Negotiation Completed: Negotiation has been completed. | ✓ | ✗ | ✗ | ✓ | ✓ |
| Approval Initiated: Approval of the final contract has started. | ✓ | ✗ | ✗ | ✗ | ✗ |
| Approval Received: One or more approvers have granted their approval. | ✓ | ✓ | ✗ | ✗ | ✗ |
| Approvals Completed: All approvers have approved the request. | ✓ | ✗ | ✗ | ✓ | ✓ |
| Approval Denied: One or more approvers have rejected the request. | ✓ | ✗ | ✗ | ✗ | ✗ |
| Approval Pending: At least one approval decision is still pending. | ✗ | ✓ | ✗ | ✗ | ✗ |
| Request Completed: All necessary steps finalized, request fulfilled. | ✓ | ✗ | ✗ | ✓ | ✓ |
| Marked as Customer to Buy: Requests which are to be taken up by the customer due to a low deal size. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Request Updated: User modifies details of an existing request. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Follower Added: Additional user added to receive updates on the request progress. | ✗ | ✗ | ✗ | ✗ | ✓ |
| Approval Document Uploaded: Document uploaded to support the approval process. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Requester Changed (Email now to new requestor): Request ownership transferred to a new user. | ✓ | ✗ | ✗ | ✗ | ✗ |
| Request Cancelled: User withdraws a submitted request. | ✓ | ✗ | ✗ | ✗ | ✓ |
If you have opted to use the Self-serve mode of the Spendflo Platform without any assistance from Spendflo on negotiations, following are the notifications you would receive based on your role:-
| Event Description | Requestor | Approver/Pre-approver | Admin | POC | Followers |
| Request Submitted: A new procurement request has been submitted. | ✓ | ✗ | ✓ | ✓ | ✓ |
| Request Cancelled: A submitted procurement request has been withdrawn. | ✓ | ✗ | ✗ | ✓ | ✓ |
| Pre-Approval Requested (if enabled) : The request is sent to the Pre-approvers in the organisation | ✗ | ✓ | ✗ | ✗ | ✗ |
| Pre-Approved: One of the Pre-approvers grants approval for the request. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Pre-Approval Completed: All pre-approvers have approved the request | ✓ | ✗ | ✗ | ✓ | ✓ |
| Pre-Approval Denied: One or more pre-approvers have denied the request. | ✓ | ✗ | ✗ | ✓ | ✓ |
| Pre-Approval Overdue: Pre-approval has not been received as per deadline. | ✗ | ✓ | ✗ | ✓ | ✗ |
| Negotiation Started: Negotiation process initiated with relevant stakeholders. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Buyer Assigned : Buyer assigned to manage the approved request. | ✓ | ✗ | ✓ | ✗ | ✓ |
| Negotiation Completed: Negotiation completed with the final commercials. | ✓ | ✗ | ✓ | ✓ | ✓ |
| Approval Initiated: Final approval workflow for the request starts - approval sent to the approvers. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Approval Received: One or more approvers have granted their approval. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Approvals Completed: All approvers have approved the request. | ✓ | ✗ | ✓ | ✓ | ✓ |
| Approval Denied: One or more approvers have rejected the request. | ✓ | ✗ | ✓ | ✓ | ✓ |
| Approval Pending: At least one approval decision is still outstanding. | ✗ | ✓ | ✗ | ✗ | ✗ |
| Request Completed: All necessary steps finalized, request fulfilled. | ✓ | ✗ | ✓ | ✓ | ✓ |
| Marked as Customer to Buy: Purchase responsibility shifted to the customer. | ✓ | ✗ | ✗ | ✓ | ✓ |
| Marked as Spendflo to Buy: Purchase responsibility assigned to Spendflo. | ✓ | ✗ | ✓ | ✓ | ✓ |
| Request Updated: Requestor modifies details of an existing request. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Follower Added: Additional user added to receive updates on the request progress. | ✗ | ✗ | ✗ | ✗ | ✓ |
| Approval Document Uploaded: Document uploaded to support the approval process. | ✓ | ✗ | ✗ | ✗ | ✓ |
| Requester Changed (Email to new requestor): Request ownership transferred to a new user. | ✓ | ✗ | ✗ | ✗ | ✗ |
Important note : Admins & POCs will receive some additional notifications if you have opted for self serve mode.