Explore Jooule
From the first order to your food costs and team schedule. Explore each workflow, then see how it fits into service.
Browse products →105 features
Features depend on your selected products and restaurant setup. Items marked “Check availability” need an enabled provider, device or service. Their details explain the conditions.
No matching features. Try a different phrase or clear the filters.
Capture relevant guest allergy notes and keep the warning with the table and the kitchen’s preparation information.
The system communicates recorded warnings; staff still need to verify ingredients and preparation. It does not certify a dish as allergy-safe.
Show the live order, a supported payment QR and thanks, with a branded photo or video playlist while the till is idle.
Requires a compatible configured guest display; payment QR availability follows the connected payment provider.
Find scheduled orders by date, adjust their time, start preparation early or follow the cancellation and refund workflow.
Preparation release follows the order’s timing. Refunds depend on the original payment provider; this is separate from day closing.
Keep removal and comp reasons with the staff member and any required manager approval.
Return to an unsent order draft saved on the same device within its retention window.
Drafts remain on the same device for up to 12 hours; they are not synchronized unsent orders across devices.
Arrange rooms and tables in the floor editor and use the service view to see each table’s current state.
Authorized staff can add supported custom-price items for counter requests that do not fit a fixed menu price.
Start dine-in, pickup or delivery orders at one register and follow them in the active-order list.
Use the register on supported Windows and Android devices, with browser access to supported staff screens.
Device compatibility and installation are checked during setup. New orders require an internet connection.
Join available tables, move a party, release joined tables and merge checks that meet the supported rules.
Table joining and check merging are different actions. Paid or otherwise ineligible checks cannot be merged.
Servers use a phone or tablet to take orders by seat, send rounds and keep the table’s check together.
Receive ready-food and guest-call alerts, with background alerts on supported configured Android devices.
Background behavior depends on device permissions and app setup; a browser tab does not provide every Android alert behavior.
Choose manual firing, supported ready-triggered progression or expediter control, with configured delays between courses.
Automatic progression requires supported kitchen-screen operation. Paper-only kitchens use manual pacing.
Assign dishes to courses and choose which courses reach the kitchen when sending the order.
Move a ticket ahead of another, return it to automatic priority or undo your own move in the shared kitchen queue.
Changing priority does not change the promised ready time or release held work.
Keep a round on hold until staff send it, or set a timed release where supported.
Holding a service round is separate from a guest placing a prepaid order for a future date.
Group separately packed sides at the end of the ticket, with quantities, dish context and a reminder under the dish.
Set a restaurant default and station overrides for supported dish, category and section ordering, then preview and test-print the result.
These are structured organization controls, not a free-form font, column or page-layout designer.
See station work in a shared queue, with changed and late tickets drawing attention where action is needed.
Mark a dish or station ready, see station totals and follow orders waiting for pickup with a timer.
Station completion has a short undo window; this is not a historical ticket-recall feature.
Show the kitchen queue or ready order codes on a read-only wall display.
Keep named portions identifiable with separate packing labels where the order uses that meal structure.
See printer warnings, spaced retry attempts and staff resend controls for tickets already accepted by the server.
Requires an internet connection for new orders. Retrying an accepted print job is not offline POS operation.
Route image-based tickets to the right station and optionally print a whole-order slip at the register.
Requires a compatible 80 or 58 mm ESC/POS printer and the supported network or USB connection.
Guests can choose a supported future pickup or delivery date and time, then pay online to confirm the scheduled order.
Requires online prepayment. Offered dates and times follow service hours, preparation time, delivery-zone rules and any configured advance-order limit.
Assign orders, follow pickup and delivery states, open navigation and record supported payment on delivery.
For the restaurant’s own drivers. This does not include live GPS tracking or automatic dispatch optimization.
Set named delivery zones with their fee, minimum order and timing so guests see the applicable terms.
Use required choices, extras, preparation notes and supported multi-portion meals across the shared ordering flow.
Give guests a locked menu with dish photos, previously loaded content and an automatic return after inactivity.
A browsing menu, not a guest ordering or payment app. Only previously loaded content can remain visible without a connection.
Let guests choose an order type, customize dishes and review their order on a kiosk that resets between guests.
Offer enlarged controls, tap sounds and supported-language speech on compatible kiosk devices.
Speech depends on language and device support. Interface options do not establish accessibility certification.
Take direct pickup and delivery orders from the restaurant’s site using the menu managed in Jooule.
Successful supported online payment accepts the order; pay-on-collection orders wait for staff approval.
Online payment requires an enabled supported provider; pay-on-collection availability follows the restaurant’s settings.
Use kitchen preparation settings for quoted times, add a rush delay or pause new ordering for a chosen period.
Quoted times use configured preparation settings, not a promise of demand forecasting or exact completion.
Give guests an order-status page with the promised ready time and the progress recorded by the system and staff.
The page shows recorded progress; an automatic ready SMS is not included in this feature.
Choose whether orders guests place from the table need waiter approval before they reach the kitchen.
Guests can call a server, request the check and choose a tip through the table’s phone flow.
Guests scan a table QR, browse and order without installing an app, adding rounds to the table’s shared check.
A sold-out change is shared across ordering screens so staff and guests see the same availability.
Offer configured pairings and suggestions informed by the restaurant’s own sales, including top sellers.
The restaurant’s website uses its own domain and the menu, prices and availability managed in Jooule.
Publish supported terms, consent controls and accessibility information using the restaurant’s configured details.
Available content differs by country and the information supplied by the restaurant. It is not a legal compliance guarantee.
Choose from five structured templates, adjust colors and type, add photos and follow the setup completion guide.
Structured restaurant templates, not an unrestricted website builder.
Regular and holiday hours feed the website, supported ordering and reservation times, and search-engine information.
Choose a guest segment, preview the reachable audience and message cost, then send and follow the campaign’s status.
Requires a connected SMS service. Only eligible consenting recipients are included, and sending incurs messaging charges. This is not an email campaign product.
Find guests, review their order history and club details, and manage consent and customer groups.
Sell or reload a card at the register, check its balance and use it for all or part of a payment.
Enable gift cards for the restaurant. Cards are scoped to the issuing location; this does not include online gifting or delivery by email.
Website inquiries reach an inbox where managers can assign an owner, keep notes and track follow-ups.
An inquiry does not enroll a guest in the loyalty club or grant marketing consent.
Schedule supported club and benefit changes, and make attributed adjustments to a member’s balance.
Offer monetary rewards, welcome and birthday benefits, coupons and punch cards connected to the guest’s check.
Guests choose party size and time, confirm within the temporary hold and receive a link to view or cancel the reservation.
Online booking does not include a deposit or card hold in this workflow.
Use table and joined-table capacity, protected walk-in space and arrival limits when offering reservation times.
Online guests choose a reservation time and party size, not a specific physical table.
Confirm arrivals, seat parties, correct seating and mark no-shows while carrying relevant guest details into service.
Send supported reservation updates and morning reminders through the restaurant’s connected SMS account.
Requires a connected SMS service. Message delivery and charges depend on that service.
Compare the schedule with recorded work by day and job, including labor cost as a share of sales.
Requires the Labor module. Cost visibility follows permissions; missing rates remain unknown rather than zero.
Keep dated hourly, monthly and job-specific rates, with employer costs included in supported labor calculations.
Supported country rules and configured inputs determine estimates. This is not payroll payment, filing or a payslip service.
Follow labor as a share of today’s sales, sales per labor hour and an estimate for the rest of the scheduled day.
The remaining-day estimate uses the schedule and comparable weekday history. Missing data and stale open shifts can limit the estimate.
Compare scheduled staff with role rules, past weekday demand and booked orders, then act on uncovered periods.
Requires the Labor module and role rules. History and booked orders inform coverage; this is not seasonal or weather-based AI forecasting.
Read supported translations alongside original messages and control off-shift notifications.
Translation requires an enabled AI service; the original remains available if a translation is delayed or unavailable.
Employees can offer a shift or volunteer for an opening; managers approve the change before the schedule is updated.
Use branch groups and private messages, share photos and ask staff to acknowledge important announcements.
Managers can moderate permitted branch spaces, not read everyone’s private conversations.
Invite staff to their workplace, give them their schedule and hours on their phone, and manage connected devices.
Access and installation options are confirmed during setup. This listing does not promise availability in any app store.
Employees request time off or corrections to recorded hours; managers review and decide in the same workflow.
Review recorded hours, close the monthly record and export supported attendance information for payroll preparation.
Country-specific rules and export scope vary. The export supports payroll preparation, not payment or filing of payroll.
Build the week by role, see availability and conflicts, and publish the schedule when it is ready.
Record work and breaks with server timestamps, then let employees review their monthly hours.
Phone clock-ins must be enabled; the restaurant may require its own network. This feature does not use GPS or fingerprints.
Split tips by hours, equally or by tables, with each person’s cash and payroll portions shown.
See recipe cost, its share of the selling price before tax and dishes above your food-cost target.
Requires the Food cost module and sufficient approved recipe and price data. These figures do not measure the restaurant’s net profit.
Compare purchases and recipe-based usage with actual food cost between two full stock counts. Review the gap and see food and labor figures together when both modules are enabled.
Actual cost needs full counts bounding the reporting period and usable cost data. Missing counts, prices or recipes remain visible; combined food and labor figures require both modules and appropriate access.
Count ingredients by storage area, track confirmed receipts and recipe use when dishes reach the kitchen, and review estimated balances and items that may run short during service.
Requires Food Cost, appropriate access, a counted baseline and mapped units and recipes. Shortage estimates use recorded usage from comparable weekdays; missing history or unrecorded waste limits accuracy. An estimate does not automatically mark dishes sold out.
Log discarded ingredients, dishes or preparations with quantity, reason and an optional photo. The supported recipe mapping records the related stock movements, and authorized staff can correct a log.
Requires Food Cost and appropriate access. Dish and preparation movements depend on their recipe mapping; waste must be recorded by staff.
Choose which preparations are counted as stock, define their containers and record batches made. A recorded batch adds the preparation and deducts the ingredients defined by its recipe.
Requires Food Cost, appropriate access and an approved preparation recipe with a defined yield. A batch suggested from a count discrepancy needs a person’s confirmation.
Upload document photos or PDFs, review the extracted items and quantities, and confirm what was received.
Requires the Food cost module and an enabled document-reading service. A manager reviews the extraction and confirms receipt; an uploaded invoice alone does not confirm delivery.
Review possible duplicates and match delivery notes, consolidated invoices and credits without counting the same purchase twice.
Trace ingredient price changes to affected dishes and see suggested prices for your food-cost target before deciding what to change.
Impact uses approved recipe coverage and recorded sales. Suggested prices require review before the menu is changed.
Set a target for food cost as a share of the selling price before tax and review dish-level pricing suggestions.
The supported target is food-cost percentage. Complete overhead, contribution-margin and business net-profit target management is not available here.
Request a suggested recipe draft, then correct quantities and approve it before it contributes to approved recipe figures.
Requires an enabled AI service. A suggested recipe does not know your actual preparation method or portion size until you review it.
Include mapped modifiers, reusable preparations and order-specific packaging in dish cost calculations.
Unmapped choices and incomplete recipes remain visible as gaps; they are not silently treated as fully costed.
Build dishes from ingredients and preparations, set yield assumptions and keep approved recipe versions.
Yield assumptions support recipe costing; they are separate from recording actual spoilage or a physical stock count.
Match supplier item names to kitchen ingredients and convert packs into the units used in recipes.
Set price lists by order type or channel, apply shared adjustments and review branch overrides before repricing.
Record checks and temperatures, follow corrective actions and sign off the day, with an inspection view and PDF export.
Checks depend on the restaurant’s configured jurisdiction and templates. Recordkeeping does not guarantee compliance or replace staff measurements.
Organize opening, closing and recurring tasks, assign responsibility and see what still needs attention in the restaurant’s business day.
Basic schedules and supported required starter checks are included; additional recurring workflows and reminders require the Labor module.
See takings, sales by hour, dish or staff member, current activity and the month’s payment-method totals.
Count notes and coins, enter the opening float and compare the count with expected cash and a recorded variance.
This is a branch/day count, not independent drawer sessions or a full business-day closing workflow.
Request a file export of restaurant data for review or transfer to your accountant.
Export is available on request. Formats and scope are agreed for the restaurant; direct synchronization with general accounting software is not implied.
Use the configured tax rate and supported tax-inclusive or tax-exclusive pricing for the restaurant’s country.
Rates and supported country behavior must be configured correctly. This is not tax filing or a guarantee of compliance in every jurisdiction.
Set remaining sellable portions and temporary sold-out periods from the restaurant’s availability controls.
Counts refer to sellable dish portions, not ingredient weights or physical kitchen inventory.
Start from the original payment and record the amount and reason; supported connected providers can process eligible refunds.
Refund handling depends on the original provider. Recording a cash or external-terminal refund does not return the money; some providers require handling outside Jooule.
Supported US pilot configurations connect online card payments and compatible Stripe readers to Jooule.
US Stripe paths require supported equipment, an enabled restaurant account and an approved branch pilot where applicable. Confirm availability before choosing a payment setup.
Signed-in members can choose to save a card through a supported provider and use it again on eligible checkouts.
Requires member consent, an enabled saved-card setting and a supported provider and payment configuration.
Take cash or record an external terminal payment, split evenly, by amount or by seat, and keep one tip for the check.
Ask about sales, payments, labor, dish costs and other supported reports, with answers limited to your access.
Requires the assistant module and an enabled AI service. Answers cover supported reports and the signed-in person’s permissions; confirm language availability during setup.
Employees can ask Danny about their own shifts, recorded hours and tips.
Requires an enabled assistant service. Employees receive their own records, not coworkers’ personal reports.
The phone agent uses the restaurant’s menu to build orders, check earlier orders and offer supported payment or staff handoff options.
Requires telephone and AI setup. Ordering, delivery, payment links and staff transfer depend on the restaurant’s enabled services; availability is confirmed per restaurant.
Choose a greeting and tone, allow a requested switch to a supported language and control whether the agent offers one extra suggestion.
Only configured, supported languages are offered. The restaurant’s menu, permissions and payment policy stay the same when the caller changes language.
Configured Telegram and MCP connections can access Danny’s supported reports within their assigned permissions.
Each connection requires setup and a permitted identity. It does not expand the reports or permissions the assistant may use.
Connected US restaurants can receive Uber Eats orders in Jooule and return acceptance, readiness and cancellation updates.
US restaurants only. Availability depends on partner access, restaurant connection and enabled capabilities; confirm eligibility during setup.
Review connected tills, printers, kiosks and phones, inspect reported status and open the relevant device settings.
Status reflects the latest report from a device. Printer discovery and testing require an available restaurant-side connection.
Control staff access, manager approvals and who may see sensitive wage or food-cost amounts.
Connected US restaurants receive DoorDash orders in the register and kitchen and send kitchen-ready updates back.
US restaurants only. Requires an eligible connected merchant account and enabled partner capabilities.
Sensitive changes keep the actor and action, with database protections against editing or deleting audit entries.
Run the till on supported Windows or Android devices and print through compatible network or USB thermal printers.
Compatibility is confirmed for the proposed setup; supported hardware does not mean every printer or device will work.
Share organization-level catalog data and link staff to their workplaces while keeping branch operations scoped.
Reports remain scoped to the selected location; a consolidated cross-location comparison dashboard is not included.
Keep marketing consent, support customer data requests and let managers revoke staff device access.
Improve today’s operation, plan an opening or prepare for another location. Tell us what you need, and explore how our service and technology can help.