Who Is This For?
Merchants who need the full Beep Delivery picture from the customer's first tap through payment, rider or pickup, printed tickets, and when an order ends or is cancelled.
Overview
This article explains Beep Delivery from start to finish. It tells you what customers do on the Beep app or website, how orders show on your POS and in BackOffice, how statuses change for StoreHub riders, for your own delivery team, and for customer pickup, auto-cancel and customer cancel, and how receipts and kitchen tickets fit in.
Radius, fees, pause mode, and alert settings sit in other articles so those topics are easy to find. This article keeps the order flow in one place.
Note:
Details can change by country. For example rider hours or SMS wording may differ. Examples that mention StoreHub Automated Logistics (SHALP) apply only where that rider program runs.
Before You Begin
Beep Delivery is on for your account. Your store is set up to take Beep orders.
Your store can go online for Beep when you want to take orders (see here).
Your team knows where to find online orders on the POS (for example open 'Transactions', then the online orders area) and in BackOffice.
If you use auto-print, your team knows how kitchen and receipt printers work when statuses change (see the status tables below).
Introduction
What Beep Delivery is
Beep Delivery lets customers find your store in the Beep app or on the web. They build a cart, pay online, and get food by delivery or pickup based on what you turned on. On your side, orders show on the alert paths you picked. They also show in StoreHub tools like the POS and BackOffice. Your team can then cook, hand off, and close orders in a steady routine.
Ways customers can receive orders
Delivery with StoreHub riders (SHALP) | A StoreHub rider picks up from your store and brings food to the customer. You may see statuses like 'Finding Rider' and 'Rider Found'. |
Delivery with your own riders (self-delivery) | Your team runs dispatch. You update statuses like 'Picked Up' and 'Delivered' on the POS when your process uses those labels. |
Self-pickup | The customer collects at your store. Statuses follow the pickup steps shown later in this article. |
Customers see delivery or pickup based on what you offer and what their address or path in the app allows.
Step-by-Step Guide
How Customers Order on the Beep App (Delivery With Riders)
These steps are the usual path when a customer orders delivery and your store uses StoreHub riders. The app screen may look slightly different by version.
1. Customers download the Beep app from the Apple App Store or Google Play.
2. They sign up with a phone number, enter the code, then enter an address so the app can show nearby restaurants.
3. They pick a store, pick Delivery, then pick date and time where those choices appear.
Notes:
Sometimes customers pick which store serves them. Ask them to pick a store near their address. Food usually arrives faster.
StoreHub rider delivery (SHALP) uses different order hours in different countries. Read your team's rider guide for the times that apply to your store.
To change booking slots or store hours for orders in BackOffice, read here.
4. They browse your menu, add items to the cart, then move toward checkout.
5. Before payment they check delivery address, delivery notes, and contact details.
6. They pick how to pay and pay. After payment, if delivery uses SHALP, the system looks for a rider.
7. After a rider is assigned, start cooking based on your store rules (see here).
8. Customers can track the rider in the app and get updates.
9. After delivery, they may see rewards or cashback based on program rules. They can check order history in the app.
Ordering on the Beep Website
Customers who do not want the app can open your Beep menu in the phone browser. Your brand gets a URL when the store goes live.
1. Open the menu link on the phone browser.
2. Browse, add to cart, and check out the same way your web menu allows.
Note:
Your exact URL is tied to your account. If staff cannot find it, use BackOffice store preview or share actions while you troubleshoot.
Delivery Purchase Flow (Address and Menu Checks)
App or web, the customer should confirm the delivery address before the kitchen cooks.
1. On the home screen, the customer checks the delivery address shown. They can search or pick a saved address if it looks wrong.
2. In the menu, they check the delivery strip above the menu before adding items.
3. If details look right, they tap Continue to keep browsing in delivery mode.
Self-Pickup Purchase Flow
1. From the start screen, the customer opens Self Pickup (wording may vary by market) and picks your store from stores that offer pickup.
2. In the menu, they check pickup details before adding items. When correct, they tap Continue and keep browsing in self-pickup mode.
How Restaurant Receives Beep Delivery Orders
Orders should show where your team already looks during service:
1. POS register
New Beep orders appear in your online orders area (exact taps depend on device). Many stores see a badge or queue for Beep.
2. Notifications
Based on your settings, your team may also get WhatsApp, email, or StoreHub Manager alerts. Full setup is in this article.
Note:
If nothing alerts your team after the customer pays, fix alerts first. Do not assume the problem is order volume.
Receipts and Kitchen Dockets
Receipts and kitchen tickets print with the order number so front of house, kitchen, and riders use the same ID. If printing fails, check the printer connection first. Then reprint from the POS using Resend to Kitchen or your usual action.
Managing Orders From BackOffice
You can open orders in BackOffice, read details, and change status if your role allows. You may see which customer account placed the order when the system links it.
Critical Timing Before Kitchen Starts Heavy Prep
When you use StoreHub riders for delivery, do not start heavy cooking before a rider is assigned in the normal flow. If no rider is found in time, the order may auto-cancel (see Auto-cancellation when no rider is found). StoreHub does not pay you back for food you cooked too early in that case.
That is why alerts matter. Your shift needs to see rider assignment, not only that a new order arrived.
Order Status Definitions
StoreHub Riders, On-Demand Delivery
Status | Meaning |
Pending Acceptance | Orders are accepted automatically in normal flows. The flow moves to Finding Rider. |
Finding Rider | The system looks for a rider through the logistics network. |
Rider Found | You may start preparing once a rider is found. If you use a kitchen printer, the ticket can print here. If nothing printed, check the printer connection, then tap 'Resend to Kitchen' on the register. |
Pending Pick Up | When the rider arrives, manually move the order to Picked Up if your flow needs it. That triggers the customer notification. |
Picked Up | The order is on the way to the customer. |
Delivered | The rider taps Job Completed in the rider app. This status shows in BackOffice and on the register (iOS behaviour may differ by build; trust ticket ID if labels lag). |
Self-Delivery, On-Demand
Status | Meaning |
Pending Acceptance | Orders are accepted automatically. The flow moves to Finding Rider on the label, even when you assign your own driver. |
Finding Rider | Some builds show this while you arrange your own rider. Treat it as dispatch in progress. |
Rider Found | Start preparing when your policy says dispatch is far enough along. Kitchen tickets can print; if not, check the printer and use Resend to Kitchen. |
Pending Pick Up | When your rider arrives, move to Picked Up so the customer gets the alert. |
Picked Up | The order is on the way with your rider. |
Note:
If your screen skips Finding Rider and jumps straight to Rider Found, follow your internal dispatch checklist and the printed ticket time.
Customer Self-Pickup
Status | Meaning |
Pending Acceptance | Orders are accepted automatically. The flow moves to Pending Pick Up. A kitchen receipt can print and you may start preparing. |
Pending Pick Up | When the customer has collected the food, change the status to Picked Up. |
Picked Up | The customer successfully collected the order. |
Auto-Cancellation When No Rider is Found
A normal Beep on-demand flow can take up to about 30 minutes to find a rider.
If more than 30 minutes pass and no rider is found, the order auto-cancels.
The customer receives an SMS and a full refund.
Example SMS wording (currency and amount vary by region):
Sorry! We can't find a rider for your order now due to the high volume. RM #{amount} has been fully refunded to you.
Note:
If a rider was already assigned and then cancels the job, the order usually does not cancel on its own. Contact StoreHub Support via live chat with the order ID so the team can search for a new rider.
StoreHub only steps in to find a replacement rider if a previously assigned rider was cancelled. That is separate from the first 30 minute search.
If You Use SHALP and Need to Switch an Order to Self-Delivery
For the full steps and rules, see here.
Notes:
Pre-orders are not cancelled by this 30 minute rider search rule.
Customers can cancel on-demand orders themselves before a rider is found. They get SMS and a full refund for that path too.
When Customers Ask to Change a Paid Pre-Order Delivery Time
In the older workflow, delivery time cannot change after payment. Practical options:
Offer self-pickup instead of delivery if your store allows it and the customer agrees.
Cancel and place a new order for the new slot when policy allows. Refund speed depends on how they paid.
Payment, Refunds, and What Staff Should Verify at the Counter
How payment posts and how fast refunds return depends on payment type and when the order was cancelled.
Staff should not hand out food if the Beep order does not show as a normal active order with a clear status in your tools.
For payouts and checking money in the bank, see here.
Troubleshooting
Issue | What to do |
Customer paid but no order on POS or BackOffice within a few minutes. | Check that the store is online and filters are right. Refresh. Check the customer picked the right store and account. Then escalate if needed. |
Kitchen cooked early but no rider came and the order cancelled. | Train the shift using Critical timing before kitchen starts heavy prep. Make rider status easy to see in alerts. |
Status stays Finding Rider too long. | This may lead to auto-cancel. Follow your logistics article. Switch to self-delivery only if your policy allows it. |
Customer says they paid but you see no order. | Ask for a screenshot or receipt if they have one. Check store and time. Escalate with order details if you have them. |
Printed ticket has no order number or is hard to read. | Reprint from the POS. Check printer pairing before rush hour. |
FAQs
1. Where do we set WhatsApp, email, Manager app, or POS alerts for new orders?
Step-by-step setup is in this article. This article only explains why those alerts matter for cooking at the right time.
2. A rider accepted the job, then cancelled. What should we do?
The order often stays open. Contact StoreHub Support via live chat with the order ID and a short note so the team can arrange a new rider.
3. Where is full self-delivery setup and POS button detail?
Use this guide for radius, fees, dispatch, and switching rules.
4. Why do some statuses say "rider" when we self-deliver?
Older Beep used the same status names for more than one mode. Agree inside your team what each label means for your drivers so everyone updates the POS the same way.
Need Help?
Contact StoreHub Support via live chat in your StoreHub app or email [email protected].
Was this article helpful?
Let us know below or contact support for further assistance.