Skip to main content
Help CenterRestaurant
English (US)
Browse help topics
Getting started

First-day launch checklist

Last updated 2026-08-074 min read

A practical checklist before you open with Ellich: menu, staff, devices, and tests.

On this page

Use this operational checklist before serving customers with Ellich. Account creation, starter data, a green summary, or one successful page load is not proof that every enabled workflow is live.

Confirm identity, store, and staff access

  • Sign in as the owner and confirm the active company and store.
  • Create each real employee, assign the correct location, department, job and permissions, activate the employee invitation, and issue a unique POS PIN when needed.
  • Test one owner, manager, employee, and protected manager action. Do not share an owner login or POS PIN.
  • For multiple stores, switch locations and prove each user sees only the permitted stores.

Use Create and complete your store account, Sign in and choose your store, and Add employees, assign access, and manage POS PINs for the detailed steps.

Prove menu, price, tax, and inventory behavior

  • Replace or remove starter records before relying on the catalog.
  • Confirm products, categories, prices, required modifiers, availability, and the intended POS, kiosk, online, and signage channels.
  • Verify tax, tip, service-charge, receipt, and locale settings with a controlled calculation.
  • Map inventory-tracked POS products and recipes, then prove that a paid test sale deducts the expected stock once.

Import preview success is not publication. Review rejected rows and commit only the intended menu records.

Install and verify service devices

  • Install POS / Store Edge first and prove Main POS is open before linking KDS, Kiosk, Customer Display, Operations Board, Table Order Kiosk, or Sub POS.
  • Confirm every installed Station shows the intended store, role, device name, current version, and healthy heartbeat.
  • Send one controlled POS order and prove the correct KDS stations receive the correct items once.
  • Queue a printer test and verify paper output from the intended printer. A queued job alone is not a successful print.

Do not reset or uninstall a paired Station as the first response to a temporary connection failure.

Activate and reconcile payments

  • Complete Ellich Payments onboarding and confirm the account, store assignment, reader, charges, and required provider state are ready.
  • Run one permitted small live card transaction and verify terminal approval, POS captured or settled state, receipt, and provider record.
  • Test a refund or cancellation according to store policy and verify its recorded state.
  • Train staff not to retry an unresolved or pending terminal request or collect another tender until payment is reconciled.

Creating an Ellich account does not activate card processing, terminals, or payouts.

Prove every optional customer channel separately

  • Kiosk: complete one order from a fresh session through payment, POS, KDS, confirmation, and session reset.
  • Online ordering: prove the public store, customer account routes, product visibility, ordering hours, secure payment, one linked POS order, and KDS handoff.
  • Reservations: place a signed-out booking for the real location, date, party size, consent, and deposit policy.
  • Website: verify the exact public URL in a fresh session; an editor success message is not proof that every live update step succeeded.
  • Digital signage: verify the assigned screen, published revision, heartbeat, and current playback.

Skip channels the business will not use. A ready POS does not make an optional channel ready automatically.

Run a controlled soft opening

Use a limited menu, staff group, time window, and clearly identified test records. Complete the full path from sign-in through order, production, payment, receipt, reporting, and cleanup. Confirm that reports, drawer or shift closeout, payment totals, KDS state, and inventory agree.

Record who can pause ordering, take a device out of service, reconcile a payment, correct a missing KDS route, and contact support. Capture the store, device, time and timezone, exact message, safe record IDs, and redacted screenshots. Never send passwords, PINs, MFA codes, tokens, cookies, or card data.

Open for normal service only after the in-scope workflows have direct evidence. A checklist is a review aid; it does not override a failed test, unresolved payment, offline device, warning, or missing integration.