Overview

Here's how the Order Status Updates work from a POS (Point of Sale) system to Grubtech (GT):

Accept Order: When a new order is placed, the POS system sends a signal to Grubtech (GT) to confirm the order is received and accepted for processing.
Reject Order: If there's an issue with the order, such as a stock problem or incorrect details, the POS system sends a message to Grubtech to cancel or reject the order.
Cancel Order: If an order needs to be canceled after being accepted, the POS system informs Grubtech to cancel the order completely.
Order Started: This status update indicates that the restaurant or business has begun processing the order, such as starting food preparation or getting the items ready for fulfillment.
Order Prepared: When the order is ready for dispatch (e.g., food is cooked and packed), the POS system sends a notification to Grubtech to mark the order as "prepared."
Order Dispatched: When the order is handed over for delivery, the POS system updates Grubtech to let them know that the order has been dispatched.
Order Completed: Once the delivery is successfully made and the customer receives the order, the POS sends a completion notification to Grubtech.

Accept Order

The Order Accept API is used to confirm that an order has been received and will be processed. When an order is accepted, it means the service provider acknowledges it and is ready to move forward. This step updates the order status to show that it has been confirmed and will be fulfilled. It can be done manually or automatically, depending on the system.

How It Works

The system or service provider receives a new order.
A decision is made (manually or automatically) to accept the order.
The Accept Order API is called to update the order status.
The order status changes to Accepted, indicating it will be processed.
The system can then proceed with the next steps, such as preparing or dispatching the order.

The Accept Order API updates an order’s status to “Accepted,” confirming it will be processed. This helps automate order management, reduce errors, and improve fulfillment speed while ensuring real-time status updates for a seamless workflow.

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

Reject Order

The Reject Order endpoint is part of the Order Status Update API and lets users mark an order as rejected. It is used when an order cannot be completed for reasons like unavailable items, delivery restrictions, or other issues.

How It Works

The POS system sends a request to Grubtech to mark an order as rejected.
This is used when an order cannot be completed due to reasons like unavailable items, out-of-service areas, or other constraints.
Grubtech updates the order status to "rejected" in the system once it receives the request.
A notification is sent to relevant parties (e.g., delivery partner) about the rejection.
This ensures the rejected order is no longer processed, preventing any further actions from being taken.

Integrating the Reject Order endpoint from the POS system to Grubtech ensures real-time updates of rejected orders, streamlines communication, and improves operational efficiency. It prevents further processing of unfulfilled orders, enhances customer communication, and supports quicker issue resolution and refunds.

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

Cancel Order

The Cancel Order endpoint is used to mark an order as canceled in the system. This means the order is no longer active and will not continue in the process. It’s usually used when the customer, merchant, or platform cancels the order for reasons like out-of-stock items, customer requests, or other issues. Once the cancellation is successful, the order status is updated, and any further steps like preparation or delivery are stopped.

How It Works

The Cancel Order endpoint marks an order as canceled.
It indicates that the order is no longer active and should not proceed.
The cancellation is triggered by the customer, merchant, or platform.
Common reasons for cancellation include stock unavailability, customer requests, or other issues.
Once the cancellation is successful, the order status is updated to "canceled."
Any further actions (e.g., preparation or delivery) are halted.

The Cancel Order endpoint allows merchants and platforms to efficiently cancel orders, stopping further actions like preparation or delivery. It improves order management, enhances customer satisfaction, and prevents unnecessary resource usage, all while maintaining an accurate and transparent workflow.

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

Start Order

The "Order Started" endpoint in the Order Status Update API is used to mark an order as starting. When this is triggered, it means that the process of preparing or fulfilling the order for a specific service has begun. This update helps keep track of the order's progress and lets everyone involved know that work on the order has started.

How It Works

The "Order Started" endpoint is part of the Order Status Update API.
When triggered, it marks an order as starting.
The order is identified by its unique ID and associated with a specific service.
It indicates that the preparation or fulfillment process for the order has begun.
This status update helps track the order’s progress.
It notifies relevant stakeholders that the order is actively being worked on.

Integrating the "Order Started" endpoint allows real-time tracking of order progress, enhances communication with stakeholders, improves customer experience, streamlines workflows, and provides valuable operational insights for optimizing order fulfillment processes.

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

Prepare Order

The Order Prepared endpoint is used to update an order's status to "prepared," meaning the order is ready for the next step, like being picked up or sent out for delivery. To use it, you send a POST request, where (service-id) is the ID of the business (like a restaurant or vendor), and (id) is the specific order ID.

How It Works

The POS system sends a POST request to the Order Status Update API in Grubtech.
The request includes:

--(service-id): The ID of the business (e.g., restaurant or vendor) sending the update.

--(id): The specific order ID to mark as "prepared."

The Order Prepared status is updated in Grubtech, indicating the order is fully prepared and ready for the next step (pickup or delivery).
Grubtech processes the request and updates the order status in its system, which can trigger further actions (e.g., notifying the delivery team).

Integrating the Order Prepared endpoint automates real-time order status updates from the POS to Grubtech, improving workflow efficiency, reducing errors, and ensuring better communication between the business and delivery teams. This leads to faster order processing, enhanced customer experience, and more accurate reporting.

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

Dispatch Order

The Order Dispatched endpoint is used to update an order's status to "dispatched." This means the order has been prepared and is now on its way to the customer. It shows that the order has left the restaurant or store.

How It Works

The Order Dispatched endpoint is triggered when the order is ready for delivery.
It updates the order status to "dispatched."
This indicates that the order has left the restaurant or store.
The order is now on its way to the customer.

The Order Dispatched endpoint updates the order status to "dispatched" once the order has left the restaurant or store and is on its way to the customer. This improves tracking, communication, and operational efficiency while enhancing the customer experience.

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

Complete Order

The Order Completed endpoint in the Order Status Update API is used to mark an order as finished. It shows that the order has been fully processed, including being delivered or picked up. Once the order is marked as completed, no more updates (like "dispatched" or "prepared") will be made for that order.

How It Works

The Order Completed endpoint marks an order as finished.
It indicates that the order has been fully fulfilled, including delivery or pickup.
Once the order is marked as completed, no further updates (like "dispatched" or "prepared") are expected for that order.
This is the final status for the order in the process.

The Order Completed endpoint marks an order as fully fulfilled, indicating successful delivery or pickup. It prevents further status updates, streamlining order management and improving tracking and customer experience.

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