Shop Menu
Shop Menu browses stock, chooses quantities, pays Currency and sells items. Buy displays the Shop Inventory; Sell displays the bound player’s Inventory. The Shop owns transaction validation, prices and destinations.
Prepare prices and create the menu
- Create Currency such as Gold. Add a Currency Owner to the player’s Inventory and fund it for testing.
- Give offered Item Definitions
CurrencyAmountsAttributes namedBuyPriceand, for selling,SellPrice. Match the Shop’s Buy Attribute Name and Sell Attribute Name exactly, including case/type. Validate prices before enabling transactions. - Stock the Shop’s Inventory and configure the player’s destination Bag to accept the offered categories and full requested amounts.
- Open Tools > Opsive > Ultimate Inventory System > UI Designer > Shop > Create. Assign Parent Transform and choose Panel Option > Basic for standalone UI or Main Menu with the Main Menu’s main content transform.
- Create, then select the menu in Edit; use Find Available Targets in Scene if needed. Add a Shop through Shop; the tool also adds/assigns its Inventory. Create/select the Inventory Grid and Quantity Picker Panel.
- Under Currency Displays, use Create Total Price UI to open Currency Designer. Create a Multi Currency View, map Gold to a Currency View with Text assigned, and explicitly connect it to Shop Menu > Total Price.
UI Designer: Shop covers hierarchy editing. Configure prices, funds and stock independently of the generated UI.

Connect player, selection and feedback
| Menu field | Default | Effect |
|---|---|---|
| Inventory | None | Direct player/client binding; takes precedence. |
| Bind To Panel Owner Inventory / Bind To Inventory By Identifier | On / 0 |
Otherwise use Panel Owner, or disable owner binding and specify a nonzero identifier. |
| Shop / Inventory Grid | None | Current shop and shared Buy/Sell view. |
| Total Price / Quantity Picker Panel | None | Quantity-dependent transaction price and confirmation. |
| Limit Buy Quantity To Available Item Amount | Off | Caps offered quantity by stock; use with finite-stock enforcement below. |
| Select Only With Click | Off | Enable when navigation selection must not change the chosen transaction item. |
| Open Quantity Picker On Item Click | On | Click opens quantity confirmation. |
| Buy Title / Sell Title | SHOP - BUY / SHOP - SELL |
Mode titles. |
| On Buy Success / Failed, On Sell Success / Failed | Empty | Feedback after the transaction result. |
Connect Menu Title, Buy Button, Sell Button, Close Button, Buy Modifier Text and Sell Modifier Text after customizing a hierarchy; manually added components start with these references unassigned. Use a separate Currency Owner Monitor for the player’s balance: Total Price is the transaction cost.
Configure prices, capacity and stock
| Shop field | Default | Decision |
|---|---|---|
| Buy Attribute Name / Sell Attribute Name | BuyPrice / SellPrice |
Required CurrencyAmounts lookup names. |
| Buy Modifier / Sell Modifier | 0 / 0 |
Multiply stored price by 1 + modifier, then quantity. -0.2 means 80 percent. |
| Add Item With Callback / Remove Item With Callback | Off / Off | Keep off for standard synchronous transactions; custom callbacks must complete or restore earlier changes. |
| Inventory | None | Stock/catalog source. |
| Default Item Collection To Add On Buy | Main-purpose collection | Resolve to Bag for normal purchases. |
| Item Collection To Add On Buy By Category | Empty | Optional category-specific destinations. |
For an all-or-nothing purchase into a restricted/capacity-limited Bag, add a buy condition requiring the destination’s CanAddItem result to satisfy both allowed.HasValue and allowed.Value.Amount == requested.Amount. Validate before charging or enabling confirmation; use a project transaction with rollback when state can change during the operation. Test partial capacity in a disposable scene and verify both funds and item totals.
For unlimited catalog stock, leave Shop Add Remove Binding > Remove On Buy and the menu quantity limit off. Keep at least one entry in Shop Inventory so it appears in Buy.
For finite stock, add Shop Add Remove Binding beside the Shop and assign its Shop. Enable Remove On Buy to validate/decrease stock and Limit Buy Quantity To Available Item Amount on the menu to restrict offered quantities. Enable Add On Sell when sold items should enter Shop Inventory. Use both the finite-stock enforcement and menu limit.
Share a menu and choose its initial mode
Use Shop Menu Opener for multiple shopkeepers. Assign a valid Shop and target Menu on each opener. Pass Open(interactingInventory) or assign Client Inventory for parameterless opening with a directly assigned Menu. Identifier-only client lookup uses the opener’s panel-lookup route rather than a direct Menu reference.

Opening binds the player, assigns that shopkeeper and smart-opens the panel. Verify every opener has a non-null Shop before opening shared UI. Choose Menu Open Options > Open Buy Sub Menu (default), Open Sell Sub Menu, or Open No Sub Menu to leave the grid closed on the Buy/Sell choice.
The quantity picker starts at 1. Buy is limited by affordability and optional stock; Sell is limited by the selected player stack. With no affordable unit, confirmation is disabled even when the displayed maximum is 1. Quantity changes redraw Total Price. A successful transaction invokes feedback and redraws the grid.
Inspect a native purchase
In this example, the customer starts with 45 Gold and no Health Potions. Shop stock starts at 5, and one potion costs 3 Silver and 55 Bronze. Confirming Buy for quantity 1 adds one potion to the player and reduces stock to 4 through Remove On Buy. The matching editor setup shows the direct player binding and generated references.

The customer balance becomes 44 Gold, 96 Silver and 45 Bronze. The second crop shows the quantity picker reopened for one potion after that purchase; Total Cost is the next quoted transaction, and the header monitor is the remaining wallet balance. In Inventory × 4 in the Shop details refers to Shop stock. Both crops come from the same native frame.

This purchase example exercises the native selection, quantity-confirmation and transaction path. Continue with the checks below for insufficient funds, selling, stock exhaustion and other shopkeepers.
Verify buying and selling
Give the player 60 Gold, price potions at 10 Gold and a sword at 50. Buy two potions: Bag should gain two and Gold fall to 40. Selecting a sword should show 50 with confirmation unavailable and no data changes. Add 20 Gold and verify the sword purchase delivers one to Bag for exactly 50.
Test finite stock with one sword and both required settings; after buying it, the entry should be unavailable. Sell a potion priced at 5 Gold and verify one leaves Bag while Gold increases by five. With Add On Sell enabled, it should enter stock. Open from a second shopkeeper and confirm the source changes while the player remains correct.
| Symptom | Check | Fix |
|---|---|---|
| Buy displays player items | Shop and source Inventory. | Assign the correct Shop; Sell uses the player source. |
| Blank price | Attribute name/type and currency view mapping. | Supply CurrencyAmounts and map Gold/Text. |
| Quantity does not update Total Price | Total Price and picker references. | Explicitly connect the Multi Currency View and generated picker. |
| Purchase unavailable | Client funds, destination and buy conditions. | Bind the intended owner and require a valid full-amount destination. |
| Stock never decreases | Shop Add Remove Binding. | Enable Remove On Buy; the menu cap controls only offered quantity. |
Developer, save and network boundaries
ShopMenu.SetShop changes the source. Shop.BuyItem and SellItem receive the client Inventory, Currency Owner and ItemInfo. The standard menu price display expects the built-in Shop using CurrencyCollection; use a compatible custom menu/pricing path for another ShopBase currency implementation.
Save player Inventory and Currency with their savers; persist finite stock with its own Inventory Saver. Mode, selection and pending quantity are transient. Run multiplayer validation and ownership changes on the server/host, replicate accepted results and define conflict/rollback handling for shared stock. Custom callbacks must restore earlier currency/item changes when a later stage fails.