POS Product Attributes: Best Practices for Using Attributes or Unique Product Buttons in POS

The purpose of this article is to help you establish best practices for configuring attributes (aka "modifiers") and unique product buttons/tiles in a POS system to optimize the operator experience, reduce visible button clutter and ensure efficient and accurate order processing.


Overview of Key Concepts

Attributes:

    • Also known as modifiers
    • Are used to condense product options and reduce the number of visible buttons on the POS interface.
    • They help prompt POS operators to ask relevant questions to a customer about an order (e.g., size, flavor, add-ons, or cooking preferences).
    • Ideal for attributes or variations commonly associated with a base product.
    • In Venue Sumo attributes can be setup for:
      • an individual POS product;
      • a whole POS category; or
      • a whole POS sub-category.
    • Irrelevant attributes setup for POS category or sub-category can be excluded from particular products (e.g. Size attribute could be included from Tea within a Hot Drinks category).


      Example - Latte with Attributes for Size, Milk and Add-ons

      Operator clicks "Latte".

      Operator is shown available Attributes for Latte.



Unique Product Buttons/Tiles:

    • Another way to add POS products with a common base product is by adding each attribute as its own POS product button/tile;
    • Attributes can still be applied across these products by using the sub-category (sub-category in the example below would be Clothing and if you required a further attribute to Size, like colour this could be added)
    • See example below for our multiple products with the same common base product display in the POS for the operator.


Decision-Making Steps for Setup

Step 1: Identify Base Products and Variants

  • Review the menu or product list and categorize items into base products (e.g., coffee, sandwich) and their variants (e.g., small/medium/large, toasted/not toasted).
  • If an item has several variations that share the same base name, it is likely suited for attributes.

Step 2: Evaluate Attributes Applicability

Ask the following questions to determine if attributes are appropriate:

  • Does the variation apply to multiple products (e.g., "Extra Cheese" for sandwiches and burgers)?
  • Are the differences between the variants simple (e.g., sizes, add-ons, or preparation style)?
  • Will using a attributes reduce the number of visible buttons without sacrificing clarity?

Examples:

  • Base product: "Latte"
    • Attributes: Size (Small, Medium, Large), Milk Type (Whole, Almond, Oat), Extras (Whipped Cream, Extra Shot).

      Base product: "Pizza"

    • Attributes: Size (Small, Medium, Large), Toppings (Pepperoni, Mushrooms, Extra Cheese).

Step 3: Decide on Unique Product Buttons

Use unique buttons for products that:

  • Have no common base product (e.g., "Smoothie" and "Latte").
  • Differ significantly in price, preparation, or category (e.g., "Bottle of Water" vs. "Fountain Soda").
  • Are standalone items with no logical attributes.

Examples:

  • Unique button: "Chicken Salad" (distinct from "Caesar Salad").

Step 4: Combine for Efficiency

  • For complex menus, mix attributes and unique buttons as needed.
    • Example: Use unique buttons for distinct product categories (e.g., "Burgers," "Pizzas," "Salads") and attributes for customization within those categories.

Step 5: Test User Flow

  • Conduct a test run of the setup with your POS operators.
  • Ensure attributes prompt the correct questions and that navigation is intuitive.
  • Check how kitchen dockets display, test if they make sense to kitchen staff.
  • Adjust any confusing groupings or misplaced attributes.


Conclusion

Using attributes and unique buttons, the POS ensures fast, intuitive operation, improving customer satisfaction with quick, accurate orders and clear kitchen dockets, all while maintaining a clean interface.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us