Understanding POS Wallet Settings for Modifier Pricing

Overview

POS Wallet Settings are the mechanism that allows modifier pricing to change dynamically based on how many selections a guest makes within a modifier group. This functionality is most commonly used for build-your-own menu items where a certain number of toppings or options are included in the base price before additional charges apply.

Rather than charging the same amount for every modifier, the POS can define pricing tiers. Bite then reads those tiers from the POS and applies them during the ordering experience. When everything is working correctly, the kiosk pricing should mirror the behavior seen in the POS and in any connected mobile ordering channels.

This configuration lives in the POS (such as Toast) and is not directly editable within Bite.

Why This Feature Exists

Many restaurant menus include bundled modifier logic. A common example is a build-your-own salad or bowl where the base price includes a limited number of toppings. After the included amount is exceeded, each additional topping carries an incremental charge.

For example, a restaurant might configure an item so that the first five simple toppings are included in the base price, while any additional toppings cost $0.50 each. Similarly, the first dressing may be free, with subsequent dressings incurring a charge.

Without POS Wallet logic, every modifier would be priced individually, which would not match the restaurant’s intended pricing model. Wallet Settings allow the POS to express these allowance rules in a structured way that downstream systems like Bite can honor.

How Bite Uses POS Wallet Data

It is important to understand that Bite does not independently calculate modifier allowance logic. Instead, Bite relies on the pricing tiers that are defined in the POS and synced through the integration.

When an order is built on the kiosk, Bite counts how many modifiers the guest selects within the group and then applies the corresponding tiered pricing received from the POS. If the wallet data is present and interpreted correctly, the guest should see pricing that matches the POS exactly.

Because Bite is dependent on this synced configuration, discrepancies typically arise from either a POS configuration issue or a mismatch in how the data is being interpreted after sync.

What Correct Behavior Should Look Like

When Wallet Settings are functioning properly, the guest experience is straightforward. The base item price remains unchanged while the guest selects modifiers within the included allowance. Only after the guest exceeds the free threshold does the item total begin to increase.

Summary

POS Wallet Settings are the underlying mechanism that enables bundled modifier pricing such as “first five toppings free.” The POS defines the allowance tiers, and Bite applies them during ordering. When discrepancies occur, they are typically caused by either a POS configuration mismatch or an issue with how the wallet data is being interpreted after sync.

Because this feature sits at the intersection of POS configuration and integration behavior, careful comparison between systems is the fastest path to resolution.