FAQ
The questions we get asked most often.
#Setup
#Why can't customers see my menu item?
Walk the availability checklist. It is almost always one of the first three: the item is unpublished, it is not listed at that branch, or it has no price at that branch.
#Why is a staff member's dashboard empty?
They probably have no branch assigned. Every role except owner, admin, marketing, and accountant is branch-scoped, and an unassigned user sees nothing. Staff → the person → Branches.
#Can I use my own domain?
Yes. Website → Domains, add the domain, create the DNS records Restro shows you, and it verifies and issues a certificate automatically. Your subdomain keeps working throughout.
#Do I need my own Apple and Google developer accounts?
Yes, for the mobile app. The app is published under your brand, and both stores require the business behind the app to hold the account.
#Orders
#What is the difference between voiding and refunding?
Void cancels an unpaid order. Refund returns money on a paid one. Restro will not let you void a paid order — it makes you refund it, so the money movement is recorded.
#Can I edit an order after it is placed?
While it is pending, confirmed, or preparing. Once it is ready the kitchen has committed and editing closes.
#Why is my order completed but unpaid?
Because those are separate things, deliberately. A cash-on-delivery order is unpaid until someone marks it paid. If this is a surprise, filter orders by payment status — it is usually a real gap, not a bug.
#An order was paid but never confirmed. Why?
Check the order for a payment mismatch flag. If the amount the provider reported does not match the order to the cent, Restro withholds the payment and flags it for review rather than confirming. This is the check that stops a tampered checkout.
#Stock
#Why did my stock not move when I sold something?
The menu item needs a recipe. Without one, Restro does not know what the dish consumes. Menu → Items → Recipe.
#Why was my stock adjustment rejected?
It would have taken the balance below zero. Restro will not hold negative stock. Recount, and record the true figure as an adjustment with a note.
#Should I record a movement for items sold?
No. Sales move stock automatically through recipes. Use manual movements for deliveries in, waste, transfers, and corrections after a count only — otherwise you double-count.
#Billing
#What happens when I hit a plan limit?
The action is refused with a message naming the limit. Nothing already created is removed and nothing is silently degraded.
#What happens if I downgrade?
The change takes effect at the end of the current period. Restro warns you up front if your current usage exceeds the target plan's limits, so you can decide what to remove.
#API
#Where do I get an API key?
Settings → Developers → Create key, with the restaurant:write permission. See Authentication.
#I lost my API key. Can you show it again?
No. Only a hash of the secret is stored, so it cannot be recovered by anyone including us. Create a new key and revoke the old one.
#Can I create orders through the API?
Not in v1. Orders can be read and advanced, but creating them requires pricing, availability, discount, and stock logic that belongs behind the checkout. Menu and stock are writable — see Menu and Inventory.
#Why am I getting 404 for an order I know exists?
Your key is probably branch-scoped and the order belongs to another branch. Scoped keys return 404 rather than 403, because confirming the order exists would itself leak information. Check branchIds on GET /v1/me.
#My webhook endpoint gets the same event twice. Is that a bug?
No. Delivery is at least once — a retry after a slow-but-successful response will duplicate. Deduplicate on the event id. See Webhooks.
#My signature check always fails.
Nearly always because the body was parsed and re-serialised before signing. Sign the raw bytes exactly as received. If your framework parses JSON automatically, configure it to keep the raw body for this route.
Did this page miss something? Tell us.
Back to top