Supply Points and Material Purchases

A supply point¹ sells configured packets to authorized staff. It is an independent point with offers, not a production recipe or an unlimited provider stash.

1. Create the materials first#

Add the ingredient definitions with their correct units. For example, Red Pepper in Gram and Water in Milliliter. The material's name does not determine how much stock a purchase gives; each Supply offer sets that separately.

See Add a Material. Finished-product-role materials cannot be reused as Supply ingredients under the restaurant's output-role rules.

2. Add a Supply point#

Open Kitchen > Operation Points in a manual restaurant and add a Supply point. Give it a location-based name, such as Dry ingredient shelf. Choose Point or Object and place it where staff should buy inputs.

Supply uses the ordinary point/object picker. It has no separate work-tool pose because it does not process a device batch. The generic point form screenshot illustrates the location controls; Supply's offers are configured in its own form section.

3. Configure one packet offer#

Use the trailing + in the offers collection. Select a material, its quantity per packet and its price per packet.

The example is 20 for the whole packet, not 20 per gram. A price of zero is a free offer. Negative prices are invalid. Each purchase buys one configured packet; there is no bulk quantity input, bank choice or finite shop-stock counter in this flow.

Selecting an existing offer pill opens its quantity/price dialog. Save or delete there, then save the parent point form. Nested changes are still local until the parent form is applied. Cancelling a nested dialog returns to the parent without discarding unrelated parent fields.

4. Save and publish the point#

Accept the point form, Save draft and Publish. Check that the Supply material definitions, offers and position are in the same published setup. Saving alone leaves the live offers unchanged.

5. Buy as active staff#

Approach the published point with cash and inventory space. Open the Supply selection, choose the offer and complete the purchase. The default interface is the Restaurant NUI selection. The server validates staff, point, publication, cash and capacity before issuing the packet.

Supply uses cash only. Ox uses its configured inventory money currency; other adapters use their supported cash path. A shortage should produce the account-specific error. The resource does not silently switch to the bank when cash is insufficient.

Native Ox shop option#

The operator can opt into native Supply shops in config/operation_points.lua. This requires compatible Ox completion hooks, fixed prices and non-stacking restaurant_material. Provider forks without the required completion semantics use the supported fallback path or fail the required capability checks. Do not enable it merely because a generic Ox shop opens.

The native option never authorizes replaying a purchase after an uncertain outcome². If money/items do not match after a failed transfer, keep the operation error and follow Inventory Recovery.

Confirm the packet#

Read its material name, quantity and unit in inventory. Buying one 250 g packet should not create 250 physical items. Run a recipe consuming a known amount, then inspect the remainder. See Materials and Quantities before changing a correct packet to fix a misunderstood count.

Try the complete custom example#

Use Your First Custom Production to apply these rules to one Supply point, a Cutting recipe, a Cooking recipe and their exact ingredient quantities.