Frequently asked questions

Does the POS need a restart after a layout change?

No. The tab fetches the current plan when opened; with the Table Plan Hub, central changes even appear immediately on every open screen. Only swapping the plugin jar itself (an update) needs a restart.

Do I need the Table Plan Hub?

No. Without a hub each POS maintains its own tableplan.json, which is entirely sufficient for a single POS. The hub pays off from two POS systems on, so the plans do not drift apart.

Who may edit the plan?

Users with the CCO permission SETTINGS_SCREEN, the same ones who may open the POS settings. Waitstaff do not see the "Plan bearbeiten" (edit plan) button. No new role is needed.

Does combining tables change the receipts?

No. Combined tables are pure table plan logic: a shared frame, shared selection, one tap target. The POS still keeps one receipt per table; receipts are merged as usual via the native action "Tische umziehen" (move tables).

How do I model floors?

With table areas on the CCO Manager: one area per floor, one plan per area in the layout file. The area dropdown at the bottom left switches the floor; it appears once two areas are visible.

What happens to occupied tables that do not appear in the plan?

They appear as clickable chips ("Nicht im Plan", not on the plan) below the plan; no table gets lost.

Does the plugin work on the Cloud Edition?

Yes, the jar also installs on Customer Checkout, cloud edition 3.x. The Cloud Edition, however, does not refresh its table data passively; there the plan is up to date when you open the tab and after your own actions. The primary target version is CCO 2.0 FP21, where the plan updates live.

What happens if the hub goes down?

Each POS keeps working with its local copy; the plan remains fully usable. Only central editing is unavailable, and the POS then deliberately does not save locally either, so no silent private version emerges.

Does the POS keep running when the license expires?

Yes. Maintenance-bound licenses are checked against the build date of the installed version, never against the clock, so a running installation never stops. Only versions released after the maintenance end require extended maintenance. Entirely without a valid license the plugin disables itself with a clear notice, but blocks neither the POS nor other plugins.

Can I recover an accidentally changed layout?

Yes. Every save creates backups next to the layout file (tableplan.json.1 … .5); the hub additionally keeps an unlimited history. See Operations.

I see no amount on other waiters' tables — a bug?

No. The plan shows other waiters' amounts only with the permission TABLE_SEE_AMOUNT_OF_OTHER_TABLES; without it, only the waiter's name is shown there.