Enable, Disable and Delete a Restaurant

Activation changes the restaurant's live availability. Deletion removes the restaurant and its persistent business records. Use the action that matches the operational need.

Enable a completed restaurant#

1. Select the restaurant and open Edit.
2. Set its enabled state as intended.
3. Review required recipes, active staff and locations.
4. Apply any open forms, Save draft and Publish.
5. Approach a published interaction as the appropriate user and verify it.

The local enabled switch does not immediately activate the world. An enabled restaurant¹ uses the published state. Sales also have their own accept new orders control and per-product enabled states.

Close new sales without closing fulfillment#

To end a shift, turn off new orders in Business > Orders > Products & pricing. Staff can still prepare and deliver existing orders. Disabling the whole restaurant also closes its kitchen and can be blocked by unfinished customer orders.

See Sales and Prices. A disabled product and an unavailable kitchen station are also different conditions; inspect the right setting before changing activation.

Disable the restaurant#

Review paid orders and unresolved customer payments/refunds first. The server prevents changes that would strand required customer obligations, including removal of necessary locations or saleable fulfillment paths.

When deactivation is accepted and published, its temporary production and device work are cleaned up without ingredient refunds. Existing finished inventory products remain governed by their own metadata and usage rules. Finish parked food before shutting down or restarting.

A disabled restaurant can retain saved configuration for later use. Its map reservation is not released merely by disabling it.

Delete only after reviewing the records#

Hard deletion requires a global administrator². It is blocked when charged customer orders remain undelivered/unrefunded or customer payment/refund outcomes are unresolved.

Deleting removes the restaurant configuration, business history, stored stock and account balance. Move stock and withdraw funds you need to keep before confirming. Deletion does not return the balance to an owner, remove items from players or transfer an old inventory stash. Stored stock, completed-order history or a remaining balance alone may not block deletion.

Before confirming, settle the intended customer obligations, move any stock and funds you need to preserve, and take an appropriate database/config backup. Check the restaurant name and the actual confirmation text. This is the destructive action in the management workflow.

Verify the result#

After activation changes, verify published world interactions and the current order controls. After deletion, the restaurant should no longer appear as a live configured business. Items already held by players remain in their inventories.

For safe maintenance order, use Updates and Backups. For a blocked action involving orders or money, use Order, Payment and Stock Recovery and preserve the blocking error.