Restaurant-wide startup settings belong to 0r-restaurant/config/business.lua. Prices and the per-restaurant Accept new orders switch belong to Business > Orders > Products & pricing instead. Use Save sale settings for those panel changes; no recipe Publish is needed.
File changes require a main-resource restart during maintenance. Keep limits consistent with existing orders and inventory capacity; lowering a limit does not rewrite saved orders, packages or transactions.
Acceptance and maintenance#
| Exact key | Type / unit | Default | Example | When you see it |
|---|---|---|---|---|
Config.business.acceptanceSeconds | Positive number, seconds | 15 * 60 = 900 | 10 * 60 | New orders receive a 10-minute acceptance deadline after restart |
Config.business.maintenanceSeconds | Positive number, seconds | 30 | 45 | Background business checks run at the changed interval |
A deadline is saved when checkout creates the order. Changing acceptanceSeconds does not extend or shorten an existing deadline. Maintenance is not a guarantee that every external refund completes at that exact second. Compare a newly created order's deadline and inspect its payment/refund state after expiry.
Order and request bounds#
| Exact key | Type | Default | Example | Scope |
|---|---|---|---|---|
Config.business.maxLines | Positive whole number | 20 | 15 | Maximum distinct lines accepted in a checkout request |
Config.business.maxQuantity | Positive whole number | 100 | 80 | Bounds each checkout line and the total checkout quantity; also bounds fulfillment requests |
Config.business.maxAmount | Positive whole number | 100000000 | Keep the delivered value unless intentionally reducing supported amounts | Shared whole-number money bound, including sale-price validation |
Config.business.pageSize | Whole-number page size | 50 | 25 | Customer order-list default and some background batches |
Staff order/history pages have their own default of 10, with supported choices 10, 25, 50. pageSize does not change every table to the same size. It also does not cap the restaurant's total lifetime order count.
After changing a limit, check the cart quantity and total before checkout. Existing orders keep their saved product details and prices. If checkout fails, check the order and payment result before trying again.
New paid-order alerts#
Config.business.orderNotificationSound is a sound table with delivered value:
{ name = 'Event_Start_Text', set = 'GTAO_FM_Events_Soundset' }
Set that field to boolean false to silence the sound while keeping the notification. For example:
Config.business.orderNotificationSound = false
Restart main. Place one paid order with an active staff character online and verify the visible alert and intended sound. Alerts use the notification bridge and are not an offline notification queue. A custom provider must honor its sound options; see Custom Bridges.
Storage and delivery-bag capacity#
These settings are in config/packaging.lua, under Config.packaging:
| Exact key | Type / unit | Default | Example |
|---|---|---|---|
Config.packaging.slots | Positive whole number, provider storage slots | 50 | 60 |
Config.packaging.maxWeight | Positive whole number, selected inventory's weight units | 100000 | 120000 |
Config.packaging.maxLines | Positive whole number, distinct product lines per package | 20 | 15 |
Config.packaging.maxQuantity | Positive whole number, product quantity bound | 100 | 80 |
Automatic order packing splits products into bags within the configured limit. maxWeight uses your inventory's weight units. After restarting, check Storage and the displayed package capacity. Existing packages keep their saved contents.
For a complete order walkthrough, follow Business and Orders. For a payment or transfer needing review, use Business Recovery before any repeat action.