Dishup FAQ
Every answer,in one place.
We collected the most frequent questions about the platform, service workflows, payments, pricing and setups for different venue types.
- Platform, orders and service
- Payments, pricing and hardware
- Solutions for different formats
- Starter is suitable if you want to organize menus, table ordering and payments. Grow is designed for venues that also need to coordinate the kitchen, takeaway or delivery, fiscal receipts and data. Pro suits larger teams that need unlimited users, advanced reporting and priority support.
- Yes. You can start with the plan that best suits your current needs and move to a different tier as users, sales channels, or service complexity increase.
- The monthly fee is invoiced month by month. The annual fee is billed in a single payment and costs €120 less than twelve monthly payments for all three plans.
- These are the staff accounts that can access the Dishup manager. Starter includes up to 3 users, Grow up to 6 and Pro does not have a user limit.
- The fee covers the use of the Dishup software. Payment fees, readers, devices, printers and setup tasks depend on the solution you choose and are listed separately.
- No. Software prices are posted here. The demo helps you understand which plan and configuration make sense for your operational flow.
- It depends on the setup. Dishup can work alongside existing tools or become the main workflow for orders, service, payments and data.
- No. You can start with QR menus and web flows. Stripe readers, SmartDock, printers, OrderUp or other devices come in when they are truly needed.
- Yes. The best starting point is the most visible bottleneck: queues at payment, messy orders, chaotic takeaway or poor service data.
- No. The web flow works from the browser, starting from the restaurant QR or link.
- Yes. The menu can include options, add-ons, notes, product information and availability.
- Yes. You can choose whether guest orders enter the workflow directly or require staff approval.
- Yes. The same catalog can support table, counter, takeaway and other channels when configured.
- Yes. Each table keeps orders, service progress, the bill and history connected.
- The flow can be configured to show the items and states useful for preparation.
- Not necessarily. Printers and DeviceHub come in when the restaurant needs physical tickets or hybrid flows.
- Yes. Pickup points and OrderUp help separate preparation, pickup and handoff.
- No. A kiosk is one option. The setup starts from the way counter, takeaway and pickup work in your venue.
- It is a view for showing orders ready for pickup, useful when guests wait at the counter or in a dedicated area.
- Yes. Pickup points help separate zones, counters or handoff areas.
- Yes. The bill remains connected to the session even in fast flows.
- It is the Dishup workflow for the bill: total, payments, methods, remaining balance, fiscal documents and closeout stay connected.
- Yes. Staff can manage multiple payments without rebuilding the total by hand.
- Yes. One bill can be settled with different methods while the remaining balance stays visible.
- The flow can connect receipts, invoices and archive when fiscal integrations are configured.
- No. Start from the flow that matters most: QR, card, cash, readers or dedicated hardware come in when they are truly useful.
- No. A reader accepts card payments. SmartDock also brings the bill, service status and supported Dishup actions onto the device.
- No. Dishup.pay can work with QR, cash, cards and readers. SmartDock is for venues that want a dedicated Dishup station.
- Yes. It is built for scenarios where staff, bill and payment need to stay close.
- Because they are more complete Stripe devices than simple readers and allow a richer operating experience.
- No. Credit remains tied to the venue that issued it, keeping balances, settlement and refunds clear.
- It is especially useful for events, beach clubs and peaks, but can fit any flow where a physical QR speeds up payment.
- Yes. Vouchers can assign controlled promotional credit.
- First of all they are operational: payment, receipt, ready order and useful updates.
- From orders, payments and the other Dishup workflows active in the venue. Reports organize this information without manual reconstruction.
- Yes. Completed services remain available in the operational archive when the feature is active.
- No. It helps read information and ask operational questions. Decisions remain with owners and staff.
- No. The level of insight depends on which flows are active and what data they produce.
- Yes. You can choose whether guest orders enter the workflow directly or require staff approval.
- No. Start from the most urgent flow, then evaluate fiscal setup, readers, SmartDock or integrations.
- Yes. Dishup keeps channel, state and pickup readable in the same flow.
- No. It is useful when you want to show ready orders and reduce spoken calls.
- Yes, across areas of the same venue included in the setup. Credit, use and liability remain tied to that venue.
- Yes. Areas can share flows or remain separate where control is needed.
- Yes. The setup can start from a contained use case and then expand.
- Yes. Setup can separate catalogs, channels and flows where needed.
- Yes. Pickup points make handoff readable even across multiple areas.
- Yes, when it fits the format. Credit remains tied to the venue that issues it.
- No. You can start from one counter or pilot flow and expand.
- Yes. Each venue can keep menus, modules, channels and settings suited to its service.
- Yes. A pilot lets you validate the workflow, staff adoption and results before rollout.
- It depends on active modules and configuration, but the goal is to make history and performance more readable.
- Yes. Readers, SmartDock, QR, wallet and fiscal flows can come in based on group setup.
An answer for your venue
Do you have a more specific question?
In a demo we start from your service and review the workflows, tools and setup that fit your venue.
Review of your serviceGradual configurationPractical answers