Maintain your own items: which changes can you make?

Separate day-to-day changes from system settings

Yes — you can maintain items, prices and recipes in BonZumo with the permissions set up for those tasks. Whether you can also change further settings depends on your permissions and on how your business assigns responsibilities.

What matters is the distinction between an everyday change and a system change. A new lunch special, an updated price, or an adjusted recipe are typical maintenance tasks in a restaurant. More sensitive areas such as broader access rights, core organizational rules, or technical processes are not automatically something every authorized person should touch on the side. That separation protects you from unnecessary dependency, but also from accidental changes in places that can have wider consequences.

In practice, if you want to avoid needing outside help for every small change, set up self-management around real working situations. So do not ask in general whether you are allowed to change everything. Ask more specifically: can I create new items, adjust prices, maintain recipes, and manage the sales-related assignment myself? With that approach, it becomes clear quite quickly which tasks you can take over internally and where you should set deliberate limits.

Create a new item yourself in a clean operator workflow

A good test of real independence is a simple but typical case: you want to sell a new lunch plate tomorrow. You do not need an abstract feature list for that. You need a clean path from the idea to the sale. In BonZumo, items are maintained in a structured way. That helps you create a new entry properly instead of just typing something in somewhere.

In practical terms, you create the item with its name, assign the price, and place it where your team can find it sensibly during sales. The key question is not just whether the record can be saved, but whether it is logically easy to find for service staff or at the counter in daily work. If the new lunch plate exists but ends up in the wrong category or is visible at the wrong location, you create questions again. Self-management only works well when you think through the whole workflow.

Smaller businesses in particular benefit when this kind of maintenance does not get stuck with an external party. Seasonal items, daily specials, price changes, or a new drinks list often come up at short notice. If you can handle those changes internally, your digital offer stays much closer to your actual operation. It still makes sense to define clearly once who is allowed to create new items and who should only sell them. Otherwise you can end up with duplicate or inconsistent entries even though the software itself allows maintenance.

Name, price, and assignment decide whether an item is usable in sales

The most common mistake with self-maintained items is usually not the technology but an unclear structure. A name has to be understandable to your team at a glance. A price has to match what is actually being sold. And the assignment has to be chosen so that the item appears in the right sales context. If you work carefully here, you save much more time later than with any quick but unclear entry.

BonZumo keeps sales steps connected through the same shared records. That matters in day-to-day work because an item does not exist in isolation. It appears at the POS, gets ordered, may be prepared at a kitchen or bar station, and is later paid. So before saving, you should always check whether the new entry is named logically for your team and fits the menu or the relevant sales station. A bistro owner, for example, would assign a lunch plate differently from a cocktail at the evening bar. That operational assignment is exactly what decides whether self-management reduces workload or creates confusion.

If you have several locations or different sales areas, this decision becomes even more important. Then it is not enough that an item exists somewhere in the system. You need to decide where it should be visible and where it should not. That prevents a product from being sold by mistake in an area where it is not actually offered. Being able to change things yourself is helpful, but it only becomes really strong together with a clear internal structure.

Maintain recipes only where your underlying data is reliable

You can maintain not only items and prices but also recipes. That becomes useful when you want to look at your offer from a business point of view and keep ingredients and quantities in good order. In that case, costing supports your decision about whether a sales price matches your material usage. For operators who actively manage their menu, this is often the point where self-management becomes especially valuable.

Still, you should only maintain recipes yourself when the underlying data in your business is actually kept in order. A recipe with unclear quantities, changing units, or outdated purchase prices may look complete, but it will help very little with decisions. In that case the problem is not the software but the quality of your master data. So it makes sense to define first who is responsible for ingredients, quantities, and changes, and how often those details are reviewed.

A typical example would be a new pasta dish where you do not want to set the price by gut feeling alone. Then you can maintain the ingredients and quantities and include the recipe cost in your decision. But if the sauce is recorded internally sometimes in liters, sometimes in portions, and sometimes as an estimate, every calculation becomes unreliable. Being able to maintain it yourself does not just mean filling in fields. It means working with dependable operational data.

Set permissions before several people start changing things

Whether you can make changes yourself is always also a permissions question. BonZumo uses role-based viewing and action rights. That matters because not every person needs to see or edit everything. A shift lead needs different options from a service employee, and someone in the office needs different options again from someone at the bar. This keeps self-management possible without weakening protective boundaries.

For your business, that is mainly an organizational topic. Do not only decide who has access in theory. Decide who should actually take care of which type of change. If three people can all change prices but nobody is responsible for keeping maintenance consistent, you can quickly end up with conflicting versions. If, on the other hand, one person creates items, a second checks prices, and the team then sells from that setup, the process becomes much more stable. The software helps you separate responsibilities, but it does not replace your own decision about how you want to work internally.

This distribution of permissions is especially helpful for new employees or temporary cover. You can limit access so someone can sell and take orders without also changing sensitive areas. That answers part of your original question as well. You do not have to be dependent on the provider, but internally you should distinguish between who maintains, who checks, and who only uses the system. That is exactly what makes self-management safer and more practical in daily work.

Always check changes in the actual sales workflow before release

A change is only good when it works later in the real sales process. That is why you should look at new or changed items not only in the admin area but always from the team's point of view. Can service staff find the item where they expect it? Is the price correct? Is the name clear enough that there will be no questions at the counter or at the table? This short practical check saves you from hectic corrections during service.

In hospitality, problems rarely start when an item is created. They usually show up when the team actually uses it. An item was created but appears in an illogical category. A price was changed but the affected team member did not know. Or a recipe was updated even though the kitchen prepares the dish differently in reality. If you take self-management seriously, every change needs a small operational finish: check it, communicate it, and only then use it in regular service.

For important changes, a second review is sensible even if you can handle the maintenance on your own technically. This does not need to be a complicated process. A short look by a second responsible person at the name, price, and assignment already prevents many mistakes. That is especially true when the change affects not only the office but also sales, the kitchen, or several shifts.

Limit sensitive settings deliberately instead of unlocking everything

That is why the honest answer to your question is not simply that you can change everything yourself. For items, prices and recipes, your ability to maintain them depends on your permissions. For other settings, clarify beforehand whether your account is allowed to edit them in your setup. For more sensitive settings, you should check deliberately whether you really need them regularly in-house or whether they change only rarely. Not every rare setting belongs in everyday access.

This is not a disadvantage. It is often a sign of good operational organization. For example, if an owner wants to maintain new items, prices, and recipes quickly, that should be possible. But that same owner may not want broader workflows, access rights, or basic configuration to be changed by accident at the same time. Self-management is strongest when it allows fast everyday changes while keeping critical areas limited.

So when your setup is discussed, ask specifically about the boundaries. Which settings are intended for operators? Which changes need special rights? Which areas should only be handled by one responsible person? With those questions, you avoid two extremes at once: complete dependency for small changes, and the risky release of everything to everyone.

Build your own working guide so changes do not depend on one person

If you want to maintain items and settings internally, you should document the workflows briefly. Not as a thick manual, but as your own operating guide for the most common cases. For example: create a new seasonal item, change a price, adjust a recipe, check the location assignment, communicate the change before the shift starts. This small documentation makes you more independent because the knowledge does not stay only in one person's head.

That matters especially during holidays, illness, or staff changes. Even if everything runs through you today, the better solution is usually a small, clear standard process. Then a replacement can understand what has to be checked when something is changed. In hospitality, it is not enough that a function exists. It has to work repeatably in a stressful daily routine. For exactly that reason, your own guide helps more than improvised verbal instructions.

It also makes sense to document typical mistakes at the same time. For example: never change prices without checking them in the sales view, only adjust recipes with current quantities, and always assign new items to the correct category and the right location. That way, self-management does not become an experimental area but a reliable part of your operational organization.

Have your real example demonstrated instead of asking in general terms

The best way to check your original question is not in theory but with a very specific example from your own business. Have someone show you how to create a new item, change an existing price, and maintain a recipe. Do not only watch whether the input itself is possible. Pay attention to who is allowed to do it, where the item appears later, and what internal check you need before or after the change. That is what shows you whether you can really work independently in daily practice.

Ask to see the roles and access rights for your own account. For other settings, use a real working case to check whether you are allowed to edit them yourself. Not: can I change all settings myself? But rather: as an operator, can I maintain the changes I need for daily work myself without accidentally opening sensitive areas? That gives you a clear answer that helps in the business. General statements often sound generous, but they do not solve the practical question of responsibility.

So overall, the answer is positive, but with deliberate limits. You can usually take care of typical maintenance tasks around items, prices, and recipes yourself if your access is set up for that. For broader or more sensitive settings, you should clarify permissions, responsibilities, and the exact process in advance. That way, you are not unnecessarily dependent on the provider and still keep control over the important parts of your system.