What's New

With print bill on handed over or auto print for rider out on, picking an order from the Rider App handed it over and then showed a controller error — the bill was queued through a legacy path that needs the web login's controller, which the app never has.

🖨️ Now: • The handover bill and the rider slip queue through the same path the order editor uses • The pick answers cleanly and the rider's run opens as it should • The web Deliver button takes the same path

Result: A pick from the phone prints the bill and never errors.

The Set Recipe form gave no sign of what a save would do, so a second click on Save was refused as a duplicate, and a recipe just saved could not be picked up again without leaving the form.

🧭 Before you save: A status card says whether the recipe already exists and offers Edit that recipe when it does • For a group version, it says which branches will cook it and starts from the standard, with the ingredients filled in • Every existing version of the item is listed with its branches • An existing standard recipe can be moved onto a group after one confirmation • Duplicates and empty recipes are refused with a plain sentence before anything is saved

🔁 Keeps your place: After Save, the form keeps the recipe you just saved, and the button reads Update recipe • Edit that recipe loads its ingredients, group and units into this form • Changing the food or the variant starts the form afresh

Result: Each save changes the recipe you are looking at, and only that one.

Every branch cooked from the same recipe, so a branch that makes a dish differently had to share one recipe with the rest or keep a duplicate item.

📋 Now, under Inventory → Food Recipes → Recipe Groups: Create a group and pick its branches on one form • A branch belongs to one group at most • Give a group its own version of any recipe; the branches in that group cook that version • Every other branch keeps the standard recipe, and a group never narrows what a branch can cook

🍳 Where it shows: Sales take their ingredients from the version the branch cooks • The Recipe tab, the manufacturing recipes and the Food Recipes report name each group and its branches, and can be filtered by group • A recipe can be opened for editing from any branch

🧹 Clean-up: Duplicate items named with a suffix for one branch can be folded into a group in one step, and the old copies stay until they are retired

Result: One menu, with one recipe for each branch that needs its own.

The Edit button on a stock issuance demand was there but led nowhere useful, so a wrong quantity or department meant raising the demand again.

✏️ Now: Edit a demand while nothing has been issued against it • Its lines, quantities and departments can be changed, and the quantity box shows the amount you entered in the units you picked • The date stays as it was raised • Once anything has been issued against it, the demand is locked against editing

🏬 Who can edit: A demand can be edited only from the branch that raised it • Its own departments stay selectable even when your access to other departments is narrower

Result: A demand is corrected before any stock moves, not after.

After Clear Order Data the POS was empty but the rider app still listed hand-ins, runs and proofs of the cleared orders, and the owner app kept showing the old days, alerts and Z-reports.

🧹 Now: • Everything both apps keep about the cleared orders goes with them — hand-ins, runs, proofs and photos, returns, trips, tenders, problem reports • Riders come off duty and off the map • The owner app's daily figures, alerts and day-close logs of the window are removed and its cached blocks dropped • Pick one branch or every branch • Orders are selected by their own date as well

Result: A cleared window is cleared everywhere.

When no channel was set up, the delivery code was printed on the bill and shown on the grid — a code the rider could read himself, which proved nothing.

💬 Now: • The code goes to the customer over your WhatsApp gateway (AnySender, Meta or the legacy server, as set in System Settings) • The wording is the new Rider delivery code Notification Template — edit it like any other, Meta templates included • SMS and e-mail follow as set up under OTP & Recovery • The counter code is gone: without a channel the rider cannot ask for a code

Result: Only the customer holds the code the rider must hear at the door.

The rider screens were scattered: the hub under Options, tracking under App Settings, the points rates inside Business Settings, access on the superadmin menu.

🛵 Now: • One Rider App group in the Options menu: Rider Hub, Rider Points, Rider Tracking, and Rider App Access for superadmins • Points get their own tab on the Rider page: the four rates and the month's board • Business Settings keeps only the on/off switch • The group appears only where the rider app is switched on

Result: Settings switch things on and off; the Rider page is where riders are managed.

The superadmin's Rider App Access page switched to the tenant's database once per feature when a preset was applied — twenty-two times in one click — and every save redrew the whole list.

⚡ Now: • The restaurant list is read once and kept for an hour (↻ reloads it) • A preset writes everything and clears the caches once • A save repaints only its row, so the page keeps its place • "Default" removes the row properly, limits included • Pickers, presets and rows fit a phone screen

Result: Enable or disable a restaurant's features from anywhere, instantly.

The rider app is off for every restaurant until a superadmin switches it on, yet every cashier still saw a Rider App dropdown on the Delivery tab and managers an Options → Rider entry.

🛵 Now: • The dropdown, its four windows (hand-ins, proofs, runs, riders now) and Options → Rider appear only where the app is switched on • A restaurant that never asked for the app sees no trace of it • Switching a restaurant on brings everything back within a minute

Result: What you see on the POS matches what the centre has enabled.

Saving anything under Business Settings quietly reset the four rider point rates to 10, 5, 5 and 10, even when they had been set on the Points tab of the Rider page.

🏆 Now: The rates set under Options → Rider → Points are kept through every Business Settings save • The form carries the four rates along, so a save never drops them

Result: The points you set stay the points you set.

The rider app went live switched on for every restaurant: any rider with the right role could sign in, whether or not the restaurant had asked for the app.

🛵 Now: • Every restaurant starts with the rider app off • A superadmin turns it on per restaurant (or per tenant) in Rider App Access • Restaurants added later start off too • Nothing else changes for restaurants already switched on by hand

Result: The rider app is a product you enable, not a default every rider gets.

Updating an order that has already been cancelled is now refused for every order type. Until now a take-away was only locked once it was paid, so an Update pressed on the POS right after a cancel (the screen still held the cart) was accepted and quietly re-added the items as live lines on the cancelled order — the Items History showed a Plus (RECALL) two seconds after the void.

The same rule now protects the waiter app and the new order service: a cancelled or deleted order answers Order is not editable, whatever its type.