Article management - flexible and location-specific

Depending on the scope and requirements of your project, articles in Hypersoft can either apply centrally to all areas or must be customised individually for each area or location.

A few typical examples:

Article A is only available in the restaurant.
Article B is available everywhere, but has different formulations and prices.
Article C is only available at 5 out of 8 locations.

Only the relevant items should be displayed on the respective POS and mPOS systems - with the appropriate queries, correct recipes and correct prices.

Managing this diversity efficiently and keeping track of changes can be challenging.

That's why the Hypersoft system offers you powerful tools and clever structures to implement your article organisation clearly, flexibly and controllably. We will be happy to show you the most important basics.

Clients and points of sale

Each location should be a client in Hypersoft. If you work with a single location, this is not relevant for you. One location can treat all areas equally, in which case all items are in one sales outlet. If you have different requirements for items at the location depending on the point of sale, you can assign them accordingly. If you do not need both, you can skip these links Location Management in the item master and Connecting locations

Assortments are available to separate the options for booking items between the POS systems of your operators and your guests, the users. Assortments are so versatile if you use different channels (sales channels or systems) with eSolutions (webshop, self-order terminal or in-house ordering).

Item assortments

Assortments are switches that can be used to mark items for specific programmes or areas.

Use assortments...

Assortments - targeted article control for different channels

Assortments allow you to specifically control which items should be available in which areas - e.g. delivery service, self-order terminals (SOT) or 3rd party integrations. You work with a common article master from which you can compile a customised offer for each area.

Items can be assigned to one or more assortments. Programmes that work with assortments use this assignment like a filter to display only the relevant articles. This gives you full control over your product range structure - flexible and differentiated.

Examples of the use of assortments

An article is displayed or queried differently in the SOT than at the checkout.

The same article is listed in different assortments with different queries or prices.

Items can also be created in duplicate if required, if they are to be handled differently (e.g. booking processes).

Targeted planning and use of product ranges

Define the required assortments for your articles (e.g. A to H) and create a well thought-out concept for your article data - especially if you also want to use it for other connections or areas. You can find helpful information on this in the documentation under Best practice for article master data for eSolutions.

Assortments in connection with queries (POS)

A special function is the use of assortments within queries at the checkout: depending on the active assortment of a channel, an article can behave differently. This allows you to control your articles in a context-sensitive manner - depending on the sales channel or usage situation: t: Assortments in connection with queries

Price control

There are different tools for controlling the prices of items, depending on requirements. Price levels are available as the top category everywhere in the POS area. They operate at the level of losses that can be used for free levies and their control. One price level for regular guests, one price level for dinner and lunch, one price level for events or seasons. : Use prices and price levels

If you work with several locations, this can quickly become too many price levels, so you may prefer to use the price groups, where you can link logical calculations per product group as required. This option for larger systems increases the possibilities and creates structure while keeping everything clear: Price groups and price maintenance

We don't want to list all the possibilities here, but we would like to offer the options for some items:

Further documentation: Processing during operation

Back to the parent page: Basic knowledge 1: Basics