Overview

Dashboard map

The admin backend is grouped by the work users are trying to complete. These sections match the Filament navigation so you can explain the product without forcing users to learn implementation names.

Quick start

1. Create a location. Add the venue details, opening hours and public menu URL.
2. Add recipes. Enter dish or drink names, prices, descriptions, images, ingredients and tags.
3. Create a menu. Set the menu overview, display settings, schedule and location assignment.
4. Build sections. Open Edit menu content, add sections such as Starters or Cocktails, then add recipes into each section.
5. Preview and publish. Use the menu preview, check allergens and nutrition, then share the QR code or embed snippet.

Menus

A menu is the published container customers see. It stores the overview, display style, schedule, location assignment and the ordered content sections.

Creating a menu

1. Open Menus in the admin sidebar.
2. Click New menu and complete Menu Overview.
3. Use Display Settings for layout and presentation choices.
4. Use Menu Scheduling when a menu should only be visible at certain times.
5. Assign the menu to one or more locations before previewing or sharing it.

Useful actions

The menu table includes quick actions for previewing a menu, editing content, duplicating a menu and reviewing saved versions.

Sections

Sections are created inside Edit menu content. They are the practical categories guests understand: Starters, Mains, Desserts, White Wine, Draught Beer, Specials and so on.

Building sections

1. From a menu, choose Edit content.
2. Click Add section.
3. Enter a Section Name and optional description.
4. Use the section actions to set grid columns or day availability.
5. Click Add recipe to place recipes into the section.
6. Save after large changes. Undo and redo are available while editing content.

Recommended section categories

• Food: Starters, Small Plates, Mains, Sides, Desserts, Specials.
• Drinks: Cocktails, Wine, Beer and Cider, Spirits, Soft Drinks, Coffee and Tea.
• Operations: Breakfast, Lunch, Dinner, Weekend, Seasonal, Hidden Drafts.

Recipes

Recipes are reusable menu items. A recipe can be a dish, drink, bundle or seasonal item, and can appear in more than one menu section.

What to complete first

• Recipe Overview: name, SKU and recipe status.
• Recipe Details: price, serves, description, beverage category, tags and image.
• Information tabs: ingredients, allergens, kitchen notes, profitability and carbon information.
• Availability: keep drafts, seasonal items and discontinued items out of live menus until ready.

Drinks

Choose a beverage category to unlock category-specific fields for wine, beer, cocktails, coffee, tea, water, soft drinks, juices or spirits.

Locations

A location is a venue or site. Locations own public URLs, QR codes, opening hours, reviews, analytics and menu assignments.

1. Create the location before publishing a customer menu.
2. Add public-facing contact details, address and opening hours.
3. Assign menus to the location from either the location form or the menu form.
4. Use the generated QR and embed tools when the menu is ready.

Publishing

Publishing is less about a single button and more about making sure the right menu is assigned to the right location, previewed and shared through the right channel.

• Preview: open the menu preview from the menu table before sharing it.
• Versions: review saved menu versions and restore a previous version when needed.
• Scheduling: use menu scheduling and section day availability for time-based menus.
• Sharing: use QR codes, hosted menu URLs, embeds, WordPress, signage or API access.

Allergens

Allergen data starts at recipe level. Add ingredients, mark contains and may-contain allergens, then let menus and labels reuse the same source data.

1. Open a recipe.
2. Complete the ingredient and allergen fields in the information tabs.
3. Review any AI-detected allergen suggestions before applying them.
4. Preview the public menu and PPDS label output before publishing.

Nutrition

Nutrition data can be stored with the recipe so it appears consistently across menus, public item views and exports. Complete values once, then reuse them anywhere the recipe appears.

PPDS labels

Use Labels under PPDS Compliance to create labels from recipe data, review compliance information and preview printable output before use.

1. Create or select the recipe first.
2. Create a label and link it to the recipe.
3. Review ingredients, allergens, packaging and storage fields.
4. Preview the label before printing or downloading.

Analytics

Menu Analytics shows how guests interact with published menus, including views, device breakdowns and menu engagement. Location records also include location-level analytics.

UTM campaigns

Use UTM campaigns to separate traffic from table cards, posters, social links or venue-specific promotions. Campaign QR links make reporting easier later.

Reviews

Reviews provide a lightweight moderation area for location feedback. Publish, unpublish or flag reviews from the Reviews resource.

QR and embeds

QR codes and embeds point to the same live menu data. Once printed or embedded, future menu changes update automatically.

<div data-quiteful-menu="LOCATION_ID"></div>
<script src="https://quiteful.com/menu.min.js"></script>

Public API

The public API is the best route for a custom app, Next.js site, WordPress integration or venue microsite that needs to render Quiteful menu data with its own front end. OpenAPI reference is available at /api/documentation.

Recommended app flow

1. Use API Tokens in the backend to create a token and copy the Vercel environment block.
2. Fetch /api/v1/locations/{location}/menus to get the menu list, default menu, venue details, theme settings, filters, legend and public URLs.
3. Use meta.default_menu_uuid or meta.default_menu_slug to open the correct menu by default when a venue has multiple menus.
4. Fetch /api/v1/menus/{menu}/items for the render-ready section structure and recipe payloads.
5. For an outage-resilient website, read the menu's public_urls.snapshot_manifest, fetch its immutable menu.json artifact, and retain the last checksum-valid payload whenever a refresh fails.
6. Fetch /api/v1/locations/{location}/allergens for the combined allergen and nutritional information page; nutrition is exposed as a view/tab there rather than a separate navigation item.

Menu sections and ordering

• custom_class is available on sections and menu item/group entries. It is sanitised and intended for stable styling hooks such as a branded hot drinks section.
• availability.windows[].start_source and end_source can use location_open or location_close. A breakfast section can therefore start from the venue opening time and end at 12:00.
• availability.unavailable_behavior=disabled means keep the section visible and keep item modals openable for allergens, ingredients and nutrition.
• ordering_enabled=false is the field apps should use to disable order buttons after a cutoff. Do not hide allergen or nutrition details just because ordering is disabled.
• The optional at query parameter on menu endpoints resolves availability for a specific date/time, which is useful for previews and automated tests.

Recipes, modifiers and compliance

• Recipes include allergens, nutrition, dietary_info, beverage metadata and modifier_groups when loaded.
• Modifier options linked to add-on recipes expose the linked recipe's allergens, dietary flags and nutrition. Missing nutrition is returned empty and should be treated as incomplete, not estimated by the app.
• Modifier presentation controls are global, not Sutton-specific. Use dietary_pill_display as inline, tooltip or hidden; use dietary_pill_label_style as code or full; use dietary_tooltip_label_style as full or code. These fields can be set on a modifier group and overridden per option.
• Custom allergens from team settings and recipe data appear in filter_schema.custom_allergens for menu, allergen and nutrition endpoints.
• Beer, wine and spirits are distinct drink recipes. Use beverage metadata such as type, ABV and volume to group or format them on the front end.
• Menu terms and conditions appear in endpoint metadata as menu_terms_conditions and has_menu_terms_conditions. Show a link or modal when the flag is true.

Venue links

Location payloads include public contact fields and map data. Front ends should render email as mailto:, phone as tel:, and address using google_maps_link when present.

QUITEFUL_API_TOKEN=your_token_here
QUITEFUL_API_BASE_URL=https://quiteful.com/api/v1
QUITEFUL_TENANT_SLUG=your-tenant
QUITEFUL_MAIN_MENU_UUID=menu-uuid
NEXT_PUBLIC_SITE_URL=https://your-site.vercel.app
NEXT_PUBLIC_QUITEFUL_MENU_URL=https://quiteful.com/your-tenant/your-location/menu

Digital signage

Digital signage has two parts: Slide Builder creates playlists, and Devices pairs physical screens to those playlists.

1. Create a playlist with menus, announcements, images or videos.
2. Create or pair a device.
3. Assign the playlist and location.
4. Use the preview and fullscreen links for checks before placing it on a live display.

Access Collins

Connect Access Collins to link each Quiteful location to a Collins venue, show a Book a table button on your menu hero, and sync bookings into the dashboard.

Before you start

• An Access Collins customer account.
• A bearer token from your Access Collins account manager.
• Quiteful locations created for each physical site.

Quick start (booking button only)

1. Open Locations → choose a location → Menu appearance.
2. Enable Show Book a table button and paste your Collins booking URL.
3. Publish your menu and test the QR code or embed.

Full connection

1. Open the team menu → Access Collins.
2. Enable Access Collins integration for your workspace.
3. Paste your bearer token, choose production or playpen, and connect.
4. Link each Quiteful location to a Collins venue (or use Suggest mappings).
5. Use Apply to menu hero on a venue link to enable the booking button automatically.
6. Optional: configure the inbound webhook URL in Collins or your middleware for real-time booking updates.

Multi-site groups

One Collins account can cover multiple venues. Use one connection per Quiteful team workspace, then link each location separately. Group and Scale plans support multiple locations under one team.

Personalised booking menus

1. Set the location’s Website menu page URL and enable External menu supports personalised links.
2. On the Collins venue link, open Personalised menus and enable automatic sending.
3. Map exact Collins custom-field values, labels, or explicit note phrases to Quiteful filters. Unmapped free text is never interpreted.
4. Confirmed bookings with an email and a recognised preference receive their link seven days before dining. Links expire 24 hours after the booking.

Owners can also create 7–10 day links from Guest preference links, optionally tag a recipient and send the transactional email immediately.

API menu token contract

Compatible API menus read the opaque guest query parameter, resolve it through GET /api/v1/guest-preferences/{token}, validate location_uuid, and hydrate their existing filter state. Preserve the same token on allergen and nutrition links. Expired, scheduled, revoked, or mismatched tokens must show an unavailable state rather than silently loading an unfiltered menu.

API and webhooks

• Quiteful can send menu.published, location.updated and collins.venue.linked events to your webhook endpoints.
• Issue an API token with locations:read and menus:read if Collins or middleware needs to read Quiteful menu data.
• Collins API reference: docs.collinsbookings.com.

Troubleshooting

• 401 from Collins — check the bearer token and environment (production vs playpen).
• 403 — token may not have access to that venue.
• 429 — rate limit reached; sync will retry on the next scheduled run.
• Missing book button — enable Show Book a table button and confirm the URL is set.

API and webhooks

Use API Tokens for authenticated API access and Webhooks to notify external systems when menus or recipes change.

• Open the API documentation.
• Create tokens from the team menu, then store them outside the dashboard.
• Create webhook endpoints with HTTPS URLs and rotate signing secrets when needed.
• Each webhook is a JSON POST signed with X-Quiteful-Signature using HMAC-SHA256 and the endpoint secret.
• Use Send Test on an endpoint to queue a webhook.test payload through the same delivery path as live menu and recipe events.

Team members

Use Team Members to invite colleagues, change roles and remove access. Billing, API tokens and webhooks live in the team menu because they apply to the whole workspace.

Billing

Billing is available from the team menu for users with billing access. It shows the active plan, trial state and links to the Stripe billing portal where payment methods and invoices are managed.

Security

Every admin action is scoped to the active team. API tokens, webhooks and team membership should be reviewed whenever staff or agency access changes.