Skip to main content

Push Notifications

Settings > Pro > Push Notifications

Written by Deira Alanis
Updated today

General

This section allows you to link your platform with OneSignal to manage the automated alerts sent to administrators, business owners, drivers, and customers.

1. OneSignal Credentials

To ensure notifications are delivered, you must input the specific API keys and IDs for each application environment.

Field

Description

OneSignal User Authentication Key

⚠️ This field is now obsolete and is no longer required for standard integration.

Customer App OneSignal ID

The specific OneSignal Project ID for the Customer mobile application.

One Signal Ordering App Rest Api Key

The REST API Key required to trigger notifications for the Customer App.

Business App OneSignal ID

The specific Project ID for the Business/Owner mobile application.

One Signal Business App Rest Api Key

The REST API Key used for merchant-related alerts.

Delivery App OneSignal ID

The specific Project ID for the Driver/Courier mobile application.

One Signal Delivery App Rest Api Key

The REST API Key used for delivery and logistics alerts.

Website OneSignal ID

ID used to enable web push notifications directly in the browser.

One Signal Ordering Web Rest Api Key

REST API Key for managing alerts on the web ordering platform.

Dashboard OneSignal ID

ID for notifications appearing within the web administration panel.

One Signal Dashboard Web Rest Api Key

REST API Key for administrative dashboard alerts.


2. Proximity and Frequency Settings

These settings control physical triggers and how often a user is alerted.

  • Notification Proximity Alert Settings: Defines the distance radius (in meters or kilometers) to trigger notifications when a driver is near a business or a customer.

  • Set Max Notification Repeats: Sets how many times a notification sound or alert will repeat if not acknowledged (up to 15 times).

  • Set Notification Repeat Interval: The duration (in seconds) to wait between each repeated notification.


3. Role-Based Repeat Controls

Toggle persistent alerts for specific user types when an order is pending acceptance:

  • Enable Admin Notification Repeats: Repeats alerts for administrators in the Business App.

  • Enable Business Owner Notification Repeats: Repeats alerts specifically for store owners.

  • Enable Driver Notification Repeats: Repeats alerts for drivers when an order is assigned and awaiting their response.


4. Interface and Alternative Channels

Visual behavior and external messaging options.

  • Enable In-App Notifications: If set to "Yes," notifications will pop up while the user is actively using the app.

  • Set In-App Notification Position: Determines where on the screen the alert appears (e.g., Notification position top right).

  • One Signal Default Enabled: Specifies if the platform's default credentials should be active.

    ⚠️ IMPORTANT: Set to "NO"

    You must set this to "NO" to use your own custom OneSignal configuration (App IDs and REST API Keys). If left at "Yes," your custom credentials will be ignored, and notifications may not be delivered.

  • Allow text messages WhatsApp: Enables sending order status updates or alerts via WhatsApp (requires additional external configuration).

  • Allow text messages SMS: Enables sending traditional SMS text message alerts.


💡 Pro Tip: Always keep your REST API Keys confidential. These keys grant permission to send messages to your entire user base.


Administrator

Once the technical connection is established, you must define which specific events will trigger a push notification to your administrators and team members. This ensures that the right people react at the right time without being overwhelmed by unnecessary alerts.

  • Pending: New orders awaiting action.

  • Completed By Admin: When an administrator manually closes an order.

  • Rejected: General order rejections.

  • Driver Arrived To Business: Arrival for pickup.

  • Preparation Completed: Kitchen/Business has finished the order.

  • Rejected By Business: Specific rejection from the store.

  • Rejected By Driver: When a driver declines an assigned task.

  • Accepted By Business: The store has started the order.

  • Accepted By Driver: A driver has taken the delivery task.

  • Pick Up Completed By Driver: The order is now in transit.

  • Pick Up Failed By Driver: Issues during the collection phase.

  • Delivery Completed By Driver: Successful hand-off to the customer.

  • Delivery Failed By Driver: Issues during the final drop-off.

  • PreOrder: Notifications for scheduled future orders.

  • Order Not Ready: Business signal for delays.

  • Order Picked Up Completed By Customer: For "Curbside" or "Pickup" models.

  • Order Cancelled By Customer: Immediate alert to stop operations.

  • Order Not Picked Up By Customer: Alert for abandoned pickup orders.

  • Driver Almost Arrived To Business: Proximity alert for pickup.

  • Driver Almost Arrived To Customer: Proximity alert for delivery.

  • Customer Almost Arrived To Business: For pickup synchronization.

  • Customer Arrived To Business: The customer is outside waiting.

  • Driver Waiting For Order: When a driver is at the store but the order is delayed.

  • Driver Arrived To Customer: The driver is at the delivery location.

  • Driver Assigned: A driver has been linked to the order.

  • Driver Is Close: Proximity notification for logistics tracking.

  • New Business Owner Signup: Notification for platform growth.

  • New Driver Owner Signup: Notification for new fleet members.


Business

In this section, you define the push notifications that Business Owners (merchants) will receive in their specific Business App. Proper configuration here ensures that restaurants or stores stay informed without unnecessary noise, focusing on the lifecycle of their specific orders.

  • Pending: Critical. Alerts the business that a new order has arrived and needs to be accepted.

  • Completed By Admin: Notifies the business if an admin manually closed an order from the back-office.

  • Rejected: General rejection alerts.

  • Driver Arrived To Business: Very useful. Tells the kitchen/staff that the driver is at the door ready for pickup.

  • Preparation Completed: Confirmation that the order is ready for the driver.

  • Rejected By Business: Log of the business’s own rejections.

  • Rejected By Driver: Alerts the business if a driver drops the task so they can keep an eye on the new assignment.

  • Accepted By Business: Confirmation of order start.

  • Accepted By Driver: Notifies the store that a driver is officially on the way to pick up the order.

  • Pick Up Completed By Driver: Confirms the order has left the premises.

  • Pick Up Failed By Driver: High Priority. Alerts the business if the driver couldn't collect the order.

  • Delivery Completed By Driver: Final confirmation that the customer received the food/product.

  • Delivery Failed By Driver: Notifies the business of issues at the drop-off point.

  • PreOrder: Alerts for scheduled orders so the kitchen can plan ahead.

  • Order Not Ready: Signal to indicate internal delays.

  • Order Picked Up Completed By Customer: Specific for "Takeout" or "Curbside" orders.

  • Order Cancelled By Customer: Immediate Alert. Tells the kitchen to stop preparing the food to save costs.

  • Order Not Picked Up By Customer: For abandoned pickup orders at the store.

  • Driver Almost Arrived To Business: A "heads up" for the staff to start packing the order.

  • Driver Almost Arrived To Customer: Monitoring the final stage of the delivery.

  • Customer Almost Arrived To Business: Preparation for curbside/pickup customers.

  • Customer Arrived To Business: The customer is outside; staff should bring the order out.

  • Driver Waiting For Order: Alerts the business owner if a driver is being delayed in their shop.

  • Driver Arrived To Customer: Tracking for the store owner.

  • Driver Assigned: Confirms a driver has been found for their order.

  • Driver Is Close: Proximity alert (usually 5-10 minutes away).


Customer

This section controls the push notifications that your End Users (Customers) will receive on their mobile devices or browsers. These alerts are vital for keeping the customer informed about the progress of their order, which significantly reduces support inquiries.

  • Pending: Confirmation that the order has been placed and is waiting for the store's response.

  • Completed By Admin: Notifies the customer if their order was finalized by the system administrator.

  • Rejected: General notification if the order cannot be processed.

  • Driver Arrived To Business: (Usually disabled for customers to avoid over-notifying) Informing them the driver is at the pickup location.

  • Preparation Completed: A great engagement point; tells the customer their food is ready and being packed.

  • Rejected By Business: Specific alert if the merchant cancels the order.

  • Rejected By Driver: (Usually disabled for customers) This is an internal logistic change that doesn't usually require customer notification.

  • Accepted By Business: The "Success" moment; confirms the restaurant is working on their order.

  • Accepted By Driver: Lets the customer know a delivery person is now dedicated to their order.

  • Pick Up Completed By Driver: The order is officially "On its way."

  • Pick Up Failed By Driver: Critical alert if there’s a delay in the collection phase.

  • Delivery Completed By Driver: The final "Enjoy your meal!" notification.

  • Delivery Failed By Driver: High-priority alert if the driver cannot find the address or complete the drop-off.

  • PreOrder: Confirmation for scheduled orders.

  • Order Not Ready: Transparent update if the business is experiencing delays.

  • Order Picked Up Completed By Customer: Confirmation for "Takeaway" orders.

  • Order Cancelled By Customer: Confirmation of their own cancellation action.

  • Order Not Picked Up By Customer: A reminder alert if the customer forgot to collect their order.

  • Driver Almost Arrived To Business: (Usually internal) Tracking the driver's proximity to the store.

  • Driver Almost Arrived To Customer: High Value Alert. The "Get ready" notification when the driver is seconds away.

  • Customer Almost Arrived To Business: (For Pickup) Tracking the customer's proximity to the store.

  • Customer Arrived To Business: Confirmation that the system knows they are outside.

  • Driver Waiting For Order: (Internal) Usually not shown to the customer.

  • Driver Arrived To Customer: The "I am at your door" notification.

  • Driver Assigned: Notification that the delivery person has been found.

  • Driver Is Close: The 5-minute warning before the delivery arrives.


Driver

This final section controls the push notifications that Drivers receive. For a delivery person, these alerts are their main tool for work; they need to know exactly when a task is available, when an order is ready, and if there are changes to their current route.

  • Pending: Alerts the driver that a new order is available for pickup or assignment.

  • Completed By Admin: Notifies the driver if the order they were handling was closed by an administrator.

  • Rejected: General notification for order cancellations or rejections.

  • Driver Arrived To Business: Confirmation that the system has registered their arrival at the store.

  • Preparation Completed: High Value. Notifies the driver that they can now enter the business to pick up the order (minimizes waiting time).

  • Rejected By Business: Alerts the driver if the store cannot fulfill the order they were assigned to.

  • Rejected By Driver: Internal log of their own declined tasks.

  • Accepted By Business: Signals that the store has started working on the order.

  • Accepted By Driver: Confirmation of their own acceptance action.

  • Pick Up Completed By Driver: Confirmation that the order is officially in their possession.

  • Pick Up Failed By Driver: Record of unsuccessful collection.

  • Delivery Completed By Driver: Final confirmation of a successful drop-off.

  • Delivery Failed By Driver: Record of issues during the final delivery phase.

  • PreOrder: Information about scheduled future tasks.

  • Order Not Ready: Notification from the business requesting more time.

  • Order Picked Up Completed By Customer: Alerts the driver if a "Pickup" order was handled directly by the client.

  • Order Cancelled By Customer: Immediate Priority. Prevents the driver from traveling to a business or house for a cancelled order.

  • Order Not Picked Up By Customer: Log for abandoned orders.

  • Driver Almost Arrived To Business: Proximity confirmation for the pickup phase.

  • Driver Almost Arrived To Customer: Proximity confirmation for the delivery phase.

  • Customer Almost Arrived To Business: Contextual alert if the driver needs to coordinate with a customer pickup.

  • Customer Arrived To Business: Real-time sync for on-site handovers.

  • Driver Waiting For Order: (Optional) Useful for tracking idle time at the store.

  • Driver Arrived To Customer: Confirmation that they are at the destination.

  • Driver Assigned: The official notification that a new delivery task has been put in their queue.

  • Driver Is Close: Proximity alert for general tracking.

Did this answer your question?