Before a vendor can configure your restaurant POS, prepare an approved menu, tax instructions, payment and business details, staff access rules, and a list of the hardware and service areas you need to support. The exact format and required fields depend on the vendor. Ask for its onboarding checklist and import templates before you sign, then have the people responsible for each part confirm what they can provide.
The buying decision is not just whether a system can ring up an order. It is whether your team can supply the necessary information, get it approved in time, and handle anything the vendor cannot import. A readiness sheet makes those dependencies visible while there is still time to compare options.
Gather the inputs and assign an owner
Start with the people who know the operation, not just the person collecting files. One manager might coordinate the project, but the kitchen lead, bookkeeper and shift supervisors may each hold a piece of the answer.
- Menu: Ask the menu owner or kitchen lead for the approved item list, prices, categories, sizes, modifiers and availability rules. Include instructions for choices that change the price and choices that must be made before an item can be ordered. Identify who can approve corrections.
- Tax: Ask the owner or bookkeeper to provide the restaurant's approved tax instructions and identify who can answer setup questions. A vendor may need those instructions organized by item or sales situation. Consult a qualified tax adviser when the correct treatment is unclear.
- Payments: Ask the business owner or authorized finance contact what business and banking information the payment provider requires, who may submit it, and when approval is expected. Also ask how refunds, tips and deposits should be configured. Do not put bank credentials or sensitive personal details in a shared menu spreadsheet.
- Staff: Have a manager list job roles and the actions each role needs, such as opening a check, applying a discount or issuing a refund. Ask how staff accounts are created and who approves access. Avoid collecting passwords in a general onboarding file.
- Hardware and floor: Have the operations lead inventory terminals, printers, cash drawers, network connections and any kitchen screens. Record model information where available. Provide the floor layout and explain which physical tables belong to each service area.
These inputs affect different people. A missing modifier can slow the kitchen; an unclear refund permission can hold up a manager; an unverified printer can change the equipment budget. Fleksa's restaurant POS system page describes menu and floor preparation with onboarding guidance. For any vendor, ask what your team must finish before that guidance can begin.
Sort requirements, approvals and unknowns
Give every input a status: ready, awaiting approval, unavailable or not yet requested. Add a named contact and the next action. A file can exist without being ready: a menu export with old prices still needs approval before anyone should use it to configure the new system.
Separate a vendor's required information from decisions your restaurant must make. For example, the vendor may request staff roles, but the owner still has to decide who may void an item. Payment setup may depend on an authorized person submitting information and on the provider's approval. Ask for the expected sequence and what work can proceed while approval is pending.
When an input is unavailable, do not silently leave it blank. Record the gap and ask what happens next. Can the vendor configure a limited version without it? Must someone enter it manually? Does it block training, payment activation or the planned opening date? A useful answer names the affected step and the person responsible for resolving it.
Keep the evidence beside the answer. A written template or setup guide is stronger evidence of a documented process than a verbal assumption. A vendor's written response to your sample is useful too, especially when it states any conditions. If a response says only “we can handle that,” ask for the configuration method and who performs it.
Protect sensitive information during this comparison. Use fictional names and sample menu data until you have agreed on a secure way to submit real business and payment details. Ask which people need access and how the vendor wants those details transferred.
Compare templates with one sample exception
Request the import template, field descriptions and an example of a completed file from each vendor. Ask which fields are mandatory, which values are accepted, and whether the vendor or your staff cleans and enters the data. Also ask what can be imported for each location and what must be configured separately.
Use the same small sample for every conversation. Hypothetical example: a restaurant sells a $12 rice bowl. A guest must choose one protein; chicken has no added charge and shrimp adds $3. The restaurant also needs staff to mark the shrimp choice as unavailable when it sells out. Its current spreadsheet includes the item, base price and modifier prices, but has no field for modifier availability.
Ask each vendor to explain how that missing availability setting would be supplied. One response might describe a separate field or configuration step; another might require staff to manage the choice manually. Do not assume either answer until the vendor documents it. Then ask the kitchen lead whether the described process is workable during a busy shift.
The exception can change the decision. If the restaurant frequently runs out of shrimp, a process that requires a manager to find and edit several menu entries may create more work than the team can accept. If the vendor can show a simpler documented process, ask who sets it up and whether it applies to every ordering channel the restaurant plans to use. If the process is still unclear, keep that requirement open rather than marking it supported.
Toast lists restaurant POS, hardware, online ordering, payments, kitchen display systems and integrations. Square offers restaurant point of sale and related payment and order tools. Fleksa offers restaurant POS connected with direct ordering, reservations and related tools. Those descriptions do not settle your import question. Give each vendor the same sample and compare its written answer, setup responsibilities and quoted work.
Keep costs separate from capability. Ask for a written onboarding quote that identifies fixed setup charges, variable charges such as per-location or per-item work, and exception costs such as manual cleanup or extra training. Ask what is excluded and how changes are approved. Processing fees are not the same as the total cost of operating the system. For a closer look at cost comparisons, read the guide to no-monthly-fee POS costs.
Build a readiness sheet before choosing
The following sheet shows how an owner could organize the work. Replace the sample contacts and statuses with your own. The dependency column matters: it shows what must happen before the next step, not merely whether a document exists.
| Input | Responsible contact | Status and dependency | Evidence or next action |
|---|---|---|---|
| Approved menu and modifiers | Kitchen lead | Awaiting owner approval; needed for menu configuration | Approve item prices and resolve the missing availability field with the vendor |
| Tax instructions | Bookkeeper | Awaiting confirmation; needed for tax setup | Provide approved instructions and contact an adviser if treatment is unclear |
| Payment setup | Business owner | Requirements requested; activation may depend on provider approval | Obtain the checklist, secure submission method and expected approval sequence |
| Staff permissions | General manager | Draft ready; owner must approve refund and discount access | Confirm roles and ask how accounts are created |
| Hardware and floor | Operations lead | Inventory in progress; compatibility and placement need vendor confirmation | Share model list and floor plan; obtain a written equipment quote |
Before selection, review the sheet with each vendor. Ask for the actual templates, a written answer to the sample exception, a list of work assigned to your team and a quote that covers the stated scope. Confirm the expected timing for each dependency, including what happens if an approval arrives later than planned.
Also ask about conditions that could affect the commitment: contract duration, cancellation charges, payment processor choices and the behavior of the system during an internet outage. Get the answers in writing rather than assuming they follow from a product demonstration. A qualified adviser can help interpret contract or tax questions when needed.
Once you have a configuration to review, use a simulated order to walk through the bowl, required protein choice and price change. Confirm in advance that the practice environment cannot create a real payment, guest message or courier dispatch. A live service pilot is a separate decision: plan its scope, staff coverage and fallback process with the vendor, without promising uninterrupted service. See these POS questions for more topics to raise during the discussion.
Next step: Request a demo of Fleksa's restaurant POS system with your sample menu and missing-field scenario. Ask the vendor to document the outcome, the information your team must provide and any unresolved setup work.
Frequently asked questions
Do I need a finished menu before requesting a POS demo?
No. A small, representative sample is enough to start comparing how vendors handle your requirements. You will still need an approved menu before the final configuration can reliably reflect what you sell.
Who should own POS onboarding at a restaurant?
Assign one coordinator to track deadlines and vendor responses. Keep the kitchen lead, finance contact, manager and operations lead responsible for approving the information they know best.
Can a vendor configure payments without my business details?
Ask the payment provider which details are required and who must submit them. Some configuration may proceed while approval is pending, but confirm the sequence and activation requirements in writing.
