What is the Order Submission Flow Report?
What is the Order Submission Flow Report?
When a customer places an order through the YUMBI Platform, it is transmitted to the restaurant's integrated Point of Sale (POS) provider for acceptance. If the order cannot be received or successfully processed by the POS, it automatically fails over to a backup device linked to the restaurant on the YUMBI Platform, such as OrderUp or a YUMBI Printer.
The Order Submission Flow report is designed to help you monitor transaction health, identify bottlenecks across your POS, YUMBI Printer, or OrderUp devices, and track fulfilment success across your brands.
Where to Find the Report
The Order Submission Flow report is located under the Operations tab within YUMBI Reports. Once selected, it will automatically populate data based on the stores assigned to your YUMBI profile.(See Figure 1)
Figure 1
Filters
You can refine the report using the following filters:(See Figure 1)
Date Range
Select the period you want to analyse.
Brand
Filter data by a specific brand.
Linked POS
Filter by the Point of Sale provider your restaurant is integrated with.
Store
Drill down into data for a specific store.
Key Performance Indicators (KPIs)
The following KPIs provide a high-level view of your overall order processing health: (See Figure 1)
Total Orders
The total volume of orders processed.
Overall Success
The percentage of orders successfully placed and accepted at the restaurant.
POS Success Rate
How often orders are successfully processed through the POS integration.
Channel Failures
Order failures occurring at the channel level.
Failed Orders
The total number of orders that could not be fulfilled.
Dashboard Views
You can toggle the dashboard between two views: (See Figure 1)
By POS Integration
Analyses performance grouped by Point of Sale provider.
By Brand
Analyses performance grouped by restaurant brand.
Within each view, you can also adjust the display to show: (See Figure 1)
Daily
Displays data for a specific day or day-by-day view.
Trends
Displays patterns and changes in data over a period of time.
Both
Displays both the daily view and trend analysis together.
Order Status Colour Coding
These status colour codings represent the different statuses of the order volume (See Figure 2).
Figure 2
| Status | Colour | Description |
|---|---|---|
| Succeeded | Green | Order was processed and accepted normally. |
| Failover | Orange | The primary path failed, and the order/s were transmitted to a backup device for acceptance. |
| Failed | Red | Order did not complete successfully. |
| Skipped | Grey | Order channel was bypassed based on specific system logic. |
| Not Sent | Dark Blue | Order was never transmitted to the restaurant for acceptance. |
View: By POS Integration
This view breaks down performance by integrated Point of Sale provider (e.g., Aura, Micros, Munch) along with other order channel devices which are linked to the restaurant to receive online orders (e.g., OrderUp/YUMBI Printer).
Figure 3
Each POS provider/Order channel device has a dedicated visual module showing: (See Figure 3)
Volume & Success Rates
Displays the total number of orders processed, along with overall order and POS success rate performance for order acceptance.
Timeline Trend
Displays a line graph illustrating success rate stability and performance trends over the selected date range.
Order Status Bar
Displays a horizontal breakdown of the different order statuses experienced at the store, such as Succeeded, Failover, and Failed order counts by channel.
POS Integration Health Summary Table
This table provides a granular breakdown of technical performance across each provider:
Figure 4
| Column | Description |
|---|---|
| POS | Name of the Point of Sale provider. When you click on the POS name displayed here, you will be able to view the breakdown of orders per store. |
| Orders | Total number of orders placed at the restaurant. |
| Success% | Rate of orders successfully placed and accepted at the restaurant. |
| POS Success | Number and percentage of orders successfully processed through the POS. |
| POS Failover | Orders not processed by the POS that failed over to a backup device (e.g., YUMBI Printer or OrderUp). When you click on the number displayed here, you will be able to view the breakdown of the associated POS error failures. |
| POS Skipped | Orders that bypassed the POS and were sent directly to a backup device. |
| POS Failed | Orders that failed at the POS and were not transmitted to any backup device. When you click on the number displayed here, you will be able to view the breakdown of the associated POS error failures. |
| OU Success | Number and percentage of orders successfully processed through OrderUp. |
| OU Failover | Orders not processed by OrderUp that failed over to another backup device (e.g., YUMBI Printer). When you click on the number displayed here, you will be able to view the breakdown of the associated OrderUp error failures. |
| OU Skipped | Orders that bypassed OrderUp and were sent to another backup device. |
| OU Failed | Orders that failed on OrderUp and were not transmitted to any backup device. When you click on the number displayed here, you will be able to view the breakdown of the associated OrderUp error failures. |
| Prt Success | Number and percentage of orders successfully processed through the YUMBI Printer. |
| Prt Failed | Orders that failed on the YUMBI Printer. When you click on the number displayed here, you will be able to view the breakdown of the associated YUMBI Printer error failures. |
| Not Sent | Orders that failed to transmit entirely. |
View: By Brand
This view reorganises the data to show how each restaurant brand is performing, regardless of which POS system they use or Order channel device.
Figure 5
Each brand has a dedicated visual module showing: (See Figure 5)
Volume & Success Rates
Displays the total number of orders processed, along with overall order and POS success rate performance for order acceptance.
Timeline Trend
Displays a line graph illustrating success rate stability and performance trends over the selected date range.
Order Status Bar
Displays a horizontal breakdown of the different order statuses experienced at the store, such as Succeeded, Failover, and Failed order counts by channel.
Brand Details Table
This table provides a granular breakdown of technical performance across each restaurant’s brands:
Figure 6
| Column | Description |
|---|---|
| Brand | Name of the restaurant brand. When you click on the brand name displayed here, you will be able to view the breakdown of orders per store. |
| POS Mix | The POS provider(s) the brand uses to receive online orders. |
| Orders | Total number of orders placed at the restaurant. |
| Success% | Rate of orders successfully placed and accepted at the restaurant. |
| POS Success | Number and percentage of orders successfully processed through the POS. |
| POS Failover | Orders not processed by the POS that failed over to a backup device (e.g., YUMBI Printer or OrderUp). When you click on the number displayed here, you will be able to view the breakdown of the associated POS error failures. |
| POS Skipped | Orders that bypassed the POS and were sent directly to a backup device. |
| POS Failed | Orders that failed at the POS and were not transmitted to any backup device. When you click on the number displayed here, you will be able to view the breakdown of the associated POS error failures. |
| OU Success | Number and percentage of orders successfully processed through OrderUp. |
| OU Failover | Orders not processed by OrderUp that failed over to another backup device (e.g., YUMBI Printer). When you click on the number displayed here, you will be able to view the breakdown of the associated OrderUp error failures. |
| OU Skipped | Orders that bypassed OrderUp and were sent to another backup device. |
| OU Failed | Orders that failed on OrderUp and were not transmitted to any backup device. When you click on the number displayed here, you will be able to view the breakdown of the associated OrderUp error failures. |
| Prt Success | Number and percentage of orders successfully processed through the YUMBI Printer. |
| Prt Failed | Orders that failed on the YUMBI Printer. When you click on the number displayed here, you will be able to view the breakdown of the associated YUMBI Printer error failures. |
| Not Sent | Orders that failed to transmit entirely. |
Breakdown of Associated Failure Reasons
The Order Submission Flow report provides deeper analytics into associated failure reasons through specific hyperlinked columns, namely: POS Failover, POS Failed, OU Failover, OU Failed, and Prt Failed.
When you click on the blue hyperlinked number displayed in these columns, a pop-up window will appear displaying further details related to the associated failure reasons.
POS Failover and POS Failed
These columns provide further insight into the various failure reasons associated directly with the Point of Sale (POS) system.
Figure 7
POS Failover and Failed Breakdown
| Column | Description |
| POS | This displays the Point of Sale (POS) Provider Name. |
| Reason | The specific reason for the order failure occurred on the POS (e.g. timeout, connection error, etc.). |
| Failover | Number of orders that failed over to a backup device. |
| Failed | Number of transactions that ultimately failed and were not successfully processed. |
| Total | Total number of failover and failed orders recorded. |
| % Errors | Percentage of failed transactions out of total transactions. |
| Example | Order number examples of the associated failure reason. |
OU Failover and OU Failed
This column displays a detailed breakdown of the various failure reasons associated with OrderUp.
Figure 8
OU Failover and Failed Breakdown
| Column | Description |
| Reasons | The specific reason why the order failure occurred on OrderUp (e.g., Timeout, rejected, etc.). |
| Failures | The number of times an order failure occurred for each reason. |
| % of Total | The percentage that each failure reason contributes to the total number of failures. |
Prt Failed
This column displays a detailed breakdown of the various failure reasons associated with printer.
Figure 9
Prt Failed Breakdown
| Column | Description |
| Reasons | The specific reason why the order failure occurred on the YUMBI Printer (e.g., Too Busy, Unable To Deliver, etc.). |
| Failures | The number of times an order failure occurred for each reason. |
| % of Total | The percentage that each failure reason contributes to the total number of failures. |
To further understand the various failed order reasons, please click HERE to view them.
The Grid Information can be exported for data analysis and provides additional categories of information using the CSV Option.
Related Articles
How do I view my Failed Order Report?
The failed order report provides a summary of unsuccessful orders that were attempted to be placed by a customer at a restaurant. There are various reasons these orders fail, and this report will underline these reasons. Click here to understand the ...How do I view my Order Details Report?
Overview of the Order Details report This report gives you a detailed overview of all your restaurants’ order activity over a selected date range, helping you track store performance, delivery patterns, and individual transactions. The Order Details ...How do I view my Order Summary Report?
The Order Summary Report offers a detailed analysis including the Restaurant's Sales Breakdown, Transaction Types, Payment Methods, and Tender Types for orders placed at your store. Additionally, this report features a link labeled “View Failed Order ...What is the Delivery Order Status Report and where can I find it?
Watch this short video that shows you how to find the Delivery Order Status Report and what it's all about. Or you can read through the article below: Delivery Order Status Report Finding the Delivery Order Status Report on the Report Portal is easy. ...Store Management Dashboard Report
The Store Management Dashboard Report is designed to offer a high-level graphical overview of your restaurant's operational landscape. This dynamic report encompasses critical metrics such as turnover performance, uptime analysis, order breakdown, ...