To ensure seamless order management, APIs facilitate the exchange of order statuses between the POS system and Grubtech. This integration ensures that order updates flow smoothly between both platforms, keeping systems synchronized in real time. These APIs will be used to send status of an order from POS to Grubtech.

Order Accepted

This endpoint is used to notify the system when an order has been accepted on the Grubtech platform. Once a restaurant or store confirms that they can fulfill the order, the platform updates the order status to "Accepted" and triggers this notification. This ensures that all connected systems, such as delivery services or customer apps, are aware that the order is being processed.

How It Works

Order is placed by a customer through an ordering platform (e.g., food delivery app or website).
Restaurant/store reviews the order and decides whether to accept or reject it.
Order status is updated to "Accepted" on the Grubtech platform.
Grubtech triggers the API request to the Order Accepted endpoint.
Connected systems receive the update, including:
- Ordering platform (to update the customer’s order status)
- Kitchen system (to start food preparation)
- Delivery service (to prepare for dispatch if required)
Order moves to the next stage, typically preparation, then dispatch and delivery.

By integrating this endpoint, you can ensure seamless communication between the restaurant, ordering platform, and delivery services. By automatically updating the order status when an order is accepted, this integration provides real-time updates to customers, reducing uncertainty and improving their experience. It also streamlines kitchen operations by triggering food preparation without delays, leading to faster order fulfillment. Additionally, it enhances coordination with delivery services by notifying them that an order is confirmed and will be ready soon. Automating this process reduces manual work for restaurant staff, minimizes errors, and improves overall efficiency.

Refer our documentation on Order Accepted JSON payload and a detailed breakdown of its attributes for more details.

Order Rejected

This endpoint is used to notify relevant systems when an order is marked as rejected on the Grubtech platform. When an order's status is updated to "Rejected," this endpoint sends a notification to ensure that all connected platforms, such as restaurants, delivery services, or third-party integrations, are informed about the rejection. This helps maintain accurate order tracking and coordination across different systems.

How It Works

When an order is rejected on the Grubtech platform, its status is updated to "Rejected."
The platform triggers this API endpoint to send a rejection notification.
The notification contains details such as the order ID, rejection reason, timestamp, and any additional relevant information.
This data is sent to connected systems (e.g., restaurants, delivery partners, third-party apps) to keep them updated.
Once received, these systems can take necessary actions, such as updating their order records, notifying customers, or stopping any further processing.

By integrating this endpoint, businesses can automatically notify connected systems, such as restaurants, delivery partners, and third-party applications, ensuring seamless order management.

Refer our documentation on Order Rejected JSON payload and a detailed breakdown of its attributes for more details.

Order Started

This API sends a notification to other systems or apps when an order is marked as "Started" on the Grubtech platform. It helps keep connected systems updated in real time about the order's progress.

How It Works

When an order is marked as "Started" on the Grubtech platform, this API is triggered.
The API sends a notification to connected systems or apps.
This notification contains order details and its updated status.
External systems use this update to track order progress in real time.
Businesses can use this information to trigger actions, such as preparing the order or updating dashboards.
The API provides a response confirming whether the notification was successfully sent or if there was an error.

Integrating this endpoint keeps all connected systems updated in real time when an order is marked as "Started" on the Grubtech platform. This improves operational efficiency by automating workflows, reducing manual efforts, and enhancing visibility.

Refer our documentation on Order Started JSON payload and a detailed breakdown of its attributes for more details.

Order Prepared

This endpoint allows you to send a notification indicating that an order has been marked as "prepared" on the Grubtech platform. When an order reaches the "prepared" status, it means that the items in the order are ready for the next steps in the process, such as dispatch or delivery. By triggering this notification, the system informs relevant parties (such as customers, delivery teams, or the platform itself) that the order is ready, helping to keep everyone updated on its progress.

How It Works

The order status is updated to "prepared" on the Grubtech platform, indicating the items are ready.
The endpoint is triggered once the order reaches the "prepared" status.
A notification is sent to relevant parties (e.g., customers, delivery teams, platform).
The notification informs recipients that the order is now ready for the next step in the process, like dispatch or delivery.
This helps ensure seamless communication and keeps everyone updated on the order's status.

Integrating this endpoint ensures real-time notifications when an order is marked as "prepared," improving communication, streamlining operations, enhancing customer experience, and reducing manual effort, all while ensuring smoother order management and accountability.

Refer our documentation on Order Prepared JSON payload and a detailed breakdown of its attributes for more details.

Order Dispatched

This endpoint is used to send a notification to the relevant parties (such as the customer, delivery team, or other stakeholders) when the status of an order has been updated to "dispatched" in the Grubtech platform. This means that the order is now on its way to the delivery destination. The notification serves to inform all involved parties that the order has been handed over to the delivery team and is in transit.

How It Works

The order status is updated to "dispatched" on the Grubtech platform.
This change triggers the endpoint to send a notification.
The notification is sent to relevant parties (e.g., customer, delivery team, stakeholders).
The notification informs recipients that the order is now in transit and has been handed over to the delivery team.
This keeps everyone updated on the status of the order and ensures smooth communication.

Integrating this endpoint enables real-time notifications when an order is marked as dispatched on the Grubtech platform.

Refer our documentation on Order Dispatched JSON payload and a detailed breakdown of its attributes for more details.

Order Completed

This API endpoint is used to notify relevant systems or partners when an order has been successfully completed on the Grubtech platform. Once an order reaches the "Completed" status, this endpoint triggers a notification to confirm that the order has been fully processed and finalized.

How It Works

When an order is marked as "Completed" on Grubtech, the system automatically calls this endpoint.
The endpoint sends relevant order details, such as order ID, completion timestamp, and any additional necessary information.
External systems can use this notification to update their records, trigger automated workflows, or inform customers.

Integrating this endpoint ensures real-time updates when an order is completed, improving system synchronization and automation. It enhances customer experience by enabling automated notifications and post-order actions like invoicing or feedback requests.

Refer our documentation on Order Completed JSON payload and a detailed breakdown of its attributes for more details.

Order Cancelled

This API endpoint is used to notify relevant systems or users when an order is canceled on the Grubtech platform. Once an order's status is updated to "Cancelled," the endpoint triggers an automated notification. This ensures that all integrated services, such as delivery partners, restaurant management systems, and customer support teams, stay informed about the order's cancellation in real time.

How It Works

When an order is marked as "Cancelled" on the Grubtech platform, the system automatically triggers this endpoint.
A request is sent to the configured destination (e.g., restaurant system, delivery partner, or customer service tool) with order details.
The receiving system processes the notification and updates its records accordingly.

The Order Cancelled Notification Endpoint instantly notifies integrated systems when an order is canceled on the Grubtech platform. This ensures real-time updates for restaurants, delivery partners, and customer service teams, improving efficiency, reducing waste, and enhancing customer experience.

Refer our documentation on Order Cancelled JSON payload and a detailed breakdown of its attributes for more details.