If your menu went live on your delivery platforms even though nobody pressed Publish, check whether a modifier was marked out of stock, or back in stock, around that time. In klikit, a modifier availability change republishes the whole branch menu. An item availability change does not.
Items and modifiers are updated differently
Marking an item out of stock (or back in stock) sends a small availability update for that one item to each of your delivery platforms. Nothing else on your menu changes, and your menu is not republished.
Marking a modifier out of stock (or back in stock) works differently. One modifier can sit in several modifier groups, those groups can be attached to many items, and those items can appear in several categories. To make sure every affected item is shown correctly on every platform, klikit republishes the entire branch menu. This is the same as pressing Publish for that branch.
This happens whether the modifier change is made on klikit Cloud (web) or on the klikit app, and it happens for any user who is allowed to manage out of stock, including Branch Managers. It also applies when you mark an item out of stock and confirm the pop-up asking whether to mark its modifier version out of stock as well.
What this means for changes you have synced but not published
Your branch menu holds everything you have Saved and Synced to that branch, including edits you have not yet published. When a modifier availability change republishes the branch menu, all of those pending edits go live at the same time.
A common example: you edit prices, press Save and Sync to the branch, and plan to press Publish later. Before you do, a team member at the branch marks a modifier out of stock. The republish that follows carries your new prices live straight away.
This is why the change can look like it came from nowhere. Your activity log will not show a Publish entry, because nobody pressed Publish. Look for a modifier out of stock or back in stock change at that time instead.
How to avoid publishing changes before you are ready
- Treat Sync as the final step before going live. Only sync a change to a branch when you are ready for it to be published. Anything you sync can be published by the next modifier availability change on that branch.
- Publish as soon as you sync. If a change is ready, press Publish straight after Sync rather than leaving it pending.
- Hold modifier changes while edits are pending. If a brand edit is synced but must not go live yet, ask branch staff to avoid marking modifiers out of stock or back in stock until it has been published. Item out of stock changes are safe, as they do not republish the menu.
- Prefer item out of stock when it does the job. If the thing you are running out of is sold as its own item as well as a modifier, and only the standalone item is affected, mark the item out of stock rather than the modifier.
Checking what was published
To confirm which version of your menu is live, open the branch menu on klikit Cloud and compare it with what customers see on your delivery platforms. Menu changes usually take a few minutes to reflect on the consumer apps.
If your menu was published with changes you did not want live, correct the items on klikit Cloud, then Save, Sync and Publish again so the corrected menu reaches your delivery platforms.
For the full steps on marking items and modifiers out of stock, see How do I Manage Out of Stock (OOS) on the web-app? and How do I Manage Out of Stock (OOS) on the app?.
Need Help? Contact us on Live Chat
Tap "Live Chat" button on the right bottom corner your screen