Quivi AI Assistant
Stop reading manuals. Talk to your POS.
Open the assistant. Say what you want. The merchant gets created, the menu gets imported, the tables get built. Eight minutes from signup to your first order — not eight days.
Hi — just signed up. Where do I start?
10:02
Welcome to Quivi! Let's open your business. In which country do you operate?
10:02
Portugal · NIF 515514454
10:03
Verified — Restaurante Alentejano, Lda · Évora. I'll pre-fill your fiscal name. What's your IBAN for settlement?
10:03
The 47-step form
Onboarding kills more merchants than churn ever will.
Every legacy POS makes you fill out a multi-day form. Business info. Fiscal config. Channels. Menu items, one row at a time. Employees. Integrations. Hidden fields. Jargon copy. Most signups never finish. Many finish and never go live. The form itself is the leakage.
Two days of data entry
For someone whose actual job is running a kitchen.
Multi-tab forms, hidden fields
One typo and the support ticket opens.
Migrations get stuck mid-setup
Toast / Lightspeed / Square exports don't import cleanly. They never do.
Most merchants give up before going live
Activation is where POS companies lose money. Quietly. Forever.
One prompt. Many actions.
It plans, calls, verifies. You watch.
Tell the assistant what you want. It breaks the request into tool calls — navigate, validate, POST, GET — runs them in sequence, and reports back when done. You don't fill forms. You supervise.
Create three tables called T1, T2, T3.
- 01 Navigate navigate_to_page
/setup/channels
- 02 Find profile call_api
GET api/channelprofiles
- 03 Create T1 call_api
POST api/channels { name: "T1" }
- 04 Create T2 call_api
POST api/channels { name: "T2" }
- 05 Create T3 call_api
POST api/channels { name: "T3" }
Done — T1, T2, T3 created under your On-Site profile. Opening the channels page now.
Three tools. Full backoffice.
- call_apiAuthenticated HTTP
Hits any backoffice endpoint — merchants, channels, menu, employees, reports — under your JWT.
- validate_vatvatcomply.com
Validates VAT/NIF and returns the registered fiscal name + address. Required before creating a merchant.
- navigate_to_pagereact-router
Takes you to the page where the change just happened. Every reply ends with a navigation.
What it does for you
Eight things the assistant does without asking.
It's not a chatbot answering FAQs. It's an agent with three tools, your JWT, and a complete map of the backoffice. Tell it what you want — it does the work.
Onboards your business
VAT validation, fiscal name pre-fill, IBAN entry, T&C acceptance. Five steps in five minutes.
Builds your channels
Tables, kiosks, online ordering, TPA. Pick a profile preset and ask for ten of them. Done.
Imports your menu
Drop a PDF. The importer reads categories, items, modifiers, prices. You confirm. It's live.
Creates your team
Employees, roles, PINs. One sentence: "Add Maria as a server with PIN 1234."
Configures pricing
Pricing profiles per channel, time-of-day pricing, modifier groups. It walks you through every concept.
Validates your VAT
Calls vatcomply.com, returns the registered fiscal name + address. No typing fiscal data twice.
Navigates the backoffice
Every reply ends with "opening the page now" — you see the change you just made, on the page that owns it.
Speaks your language
EN, PT, DA — same model, same capabilities. Switch language mid-conversation, the assistant follows.
Eight steps. One conversation.
From "I just signed up" to "taking my first order" — in one chat.
The assistant walks you through every step of activation. Each turn ends with a navigation: it takes you to the page where the change just happened, so you see the work being done.
≈ 8 minutes for a typical café · 15 for a 200-cover restaurant
- 01
Business information
validate_vat → POSTCountry, fiscal name (auto-filled from VAT), VAT, IBAN (length validated per country), postal code.
- 02
Accept Terms & Conditions
navigate + POSTThe assistant takes you to the form, double-confirms, and accepts on your behalf. Activation flips on.
- 03
Channel profile
POSTIt explains presets — On-Site, Kiosk, Online, TPA — and asks which one fits. No bitmask, no jargon.
- 04
Sales channels
POST × NTables, kiosks, takeaway counters. "Create ten tables" — done in ten POSTs, named T1 through T10.
- 05
Locations
POST · optionalPrep areas: bar, kitchen, pastry, expo. Skip if you don't need them — purely optional.
- 06
Menu items
menu importer / POSTDrop your PDF or build manually. AI extracts categories, items, modifiers, prices, allergens. You confirm. It's live.
- 07
Payment methods
POST · optionalCash, card, MB Way, voucher, account-on-file. Each merchant configures what they take.
- 08
Employees
POST · optionalServers, baristas, managers. PINs assigned. Roles auto-mapped. "Add Maria as a server." Done.
Drop a PDF
Get your full menu, live. In three minutes.
Most POS make you type every dish. Quivi imports your existing PDF — categories, items, modifiers, prices, allergens — and lets you confirm before publishing. The assistant calls the importer for you, polls the job, reports back.
Upload
Drop your menu.pdf into the chat. The assistant uploads it via api/Storage/pdf — one URL per page.
Parse
The importer reads each page — categories, items, modifiers, prices, allergens, photos. AI groups by section.
Review
The assistant shows you the extracted tree. Edit anything that doesn't look right — one sentence per change.
Publish
Live across every channel — POS, Guests, Backoffice. Same data. Same prices. Real-time.
Same importer powers our migrations from Toast, Lightspeed, Square, SumUp — anywhere you can export a menu PDF, we can import it.
EN · PT · DA
Three languages. One assistant.
The assistant detects your language and replies in kind. Switch mid-conversation — it follows. Same capabilities, same tools, in every language we ship.
Marketing site speaks four languages. Product UI ships in three (EN/PT/DA). Dutch is on the roadmap.
Honest limits
What it doesn't do (yet).
We're shipping the assistant in iterations. Here's what isn't supported today — so you know what to expect, and so we can ship the next thing without surprising anyone.
Splitting an invoice across payment methods
WorkaroundToday an invoice settles on one payment method. Workaround: issue two invoices, one per method.
Changing VAT on an issued invoice
WorkaroundOnce issued, an invoice's VAT is locked. Workaround: refund + reissue with the correct VAT.
History across sessions
RoadmapConversations live in your browser tab. Refresh and history clears. Server-side persistence is on the roadmap.
Attachments beyond PDF / PNG / JPG
RoadmapWe support menu PDFs and image proofs (logo, IBAN). Spreadsheets, .docx, CSV imports are next.
What this saves you
The math is brutal.
We measure activation, not signups. Every metric below is taken from real merchants opening on Quivi — not aspirational, not from a deck.
Sign up. Talk to the assistant.
Skip the wizard. Skip the spreadsheet. Skip the support ticket. Open the assistant, tell it about your business, and start taking orders today.