Make the software fit your work.
Change your branding, build your own screens or add integrations with the developer pack. Test your changes before using them during service.
Four ways to make a change
Settings
Adjust menus, prices, choices and extras, tables, staff roles and branding.
An AI app builder
Describe the software change you want. An AI app builder can help write the code. Review and test its work before using it during service.
Your developer
Give them the included source access, documentation and tests.
RestaKit
Tell us what you want to change. We’ll quote for the work.
Ideas for your software
Ideas for custom development. Plan the data and technical work needed with your developer or RestaKit.
A manager’s report
Review voids by staff member and location in one view.
A kitchen screen
Put preparation notes where cooks can find them during service.
A menu presentation
Show seasonal dishes alongside ordering, using content guests can access on their devices.
Ingredient costs
Show which dishes an ingredient price change affects, so your chef can review costs.
A seasonal menu launch
Create the content
Create seasonal images or promotional videos with external AI tools. Check that they match the food you serve.
Share them in social posts or promotional pages. Check which formats your RestaKit software can display and whether software changes are needed.
From your idea to a working change
Check existing settings before commissioning development.
Example custom report: voids by staff member
1. Define the question
Show voids by staff member, reason and location. Distinguish who recorded each void from who approved it.
2. Design the report
Sketch the report columns and filters, with an AI design tool if useful. Review them with your manager.
3. Build the change
Use the developer pack to build the report with the data you need. Your developer or RestaKit can help. Test it in a separate environment before using it during service.
4. Test with your team
Compare sample transactions with report totals. Check permissions, filters, exports and effects on existing workflows.
Follow the change guide. Test changes and recovery before using them during service.
5. Introduce it
Have RestaKit or your developer plan the installation, backups and recovery, and future maintenance. You can also handle these yourself. Check the report after installation.
Check whether the result answers your original question.
Review a design or clickable prototype before development starts.
Use the change guide, testing setup and upgrade instructions.
Inside the developer packFixes and services
Free fixes.
If something goes wrong in RestaKit's own code or in one of our updates, we fix it free. Problems caused by changes, installation or settings made outside RestaKit are not covered.
Our services.
Early access includes deployment, installation, human testing and setup of one shared menu across up to three locations. We use your supplied menu, photos and dish options. Different menus are quoted separately. Recipes, ingredient and stock mapping, new photography, data migration and custom development are quoted separately.
Before building
Do I need to code?
Settings need no code. Development skills depend on the change.
Which AI tools?
Replit Agent and Bolt are external options; check compatibility first.
Replit FAQ ›Bolt help ›Can I build any feature?
You can customize any part of your software. The data and development work needed depend on your idea.
Does a mockup build the feature?
No. Mockups need separate development, testing and release.
Who maintains changes?
Choose who will maintain the changes and check them after updates.
Tell us what you want to change
What happens today, and what should happen instead?