Public Profile
  • Add functionality to accept an order fulfilment in HQ on behalf of a store

    In some areas of the world, where the internet is not very stable, the stores depend on the help of coworkers in the HQ to do operations which are relying on RTS calls on POS. Accepting an order fulfillment is one of them, but unfortunately, there is no way to accept an order fulfillment on behalf of the sotre within HQ. Hence this feature request is to add in HQ a new operation "Accept oder fulfillment" to the sales line menu -> "Update line" --> "STATUS".
  • Override "Must not key in price" when price override permissions are granted

    Currently, when an item is blocked for manual price entry using the "Must not key in price"-setup, there is no way to manually enter a price anymore at all. Even when the "override Price" permission is granted to e.g. a store Manager. This is a problem when the item does not have zero price allowed but also doesn't have an active sales price. In such a scenario, even the store manager cannot sell the item successfully. This idea does request to honour the "Override price"-permission in a way, that users with that permission are still able to enter a price. Best would probably be to add a new option e.g. "Must not key in price without permission" that will enable this feature.
  • Implement a sorting option for filter attributes to have alphabetical/numerical sorting

    Currently, when you use attributes as filter refiners, the attributes are always re-sorted based on the amount of items returned. e.g. if you have brands like "Apple", "Bell" and "HP", if "HP" has more items that is using this attribute, it will get listed before the two other brands. This can cause confusion if you expect an alphabetical , or numerical ordering, e.g. if you use shoesizes as an attribute. It would be good to have a toggle to set an attribute specific default value to turn a quantity-based sorting on/off, which can then be overridden by the front-end-user within the CMS to still benefit from the existing logic.
  • Implement a validation for income/expense

    When using data entities to import transactional data from 3rd party systems which include income/expense transactions, it might occur that there income/expense transactions existing which are missing the related payments. This might be due to the fact, that they are imported at a later stage than the transactions or because the import is still running. The problem now is, that since there is no validation existing for income/expense transactions, this might lead to partially posted statements that are in status -> "Discounts posted" , where no rollback or corrective actions are available anymore. Hence it is important to have this validation in place since there is no possibility for the users to correct this statement without opening a ticket with support.
  • Enable extended warranty feature for call center sales orders as well as e-commerce

    It is now possible to sell extended warranties through POS, but unfortunately, it is not integrated into call center or e-commerce. Please do close this gap, as from an omni-channel perspective, it should not matter through which channel the sales order is placed. Hence, it should also be possible to sell extended warranties in all other channels as well.

  • Enable split store hours

    Currently, in the store's detail form --> STORE --> STORE HOURS -> STORE HOURS we can define only one set of opening hours for each day, e.g. "from 8:00 until 16:00", and if it is closed or not.


    In order to enable customers who have split store hours, e.g., "from 10:00 to 14:00 and 19:00 to 22:00", which is very common in Europe or common for restaurants in general, it would be good if the opening hours could be defined and handled to support this scenario. .

  • Enable "invoice comment"-handling on POS generated sales orders

    Since ancient EPOS-times, the operation 122 - invoice comment was not supported in the context of a sales order creation.

    This is still valid up until today and is throwing a specific error "Invoice comments are not allowed on customer orders".


    Please enable the invoice comment handling for sales orders in POS to provide a consistent comment experience in the multi-channel world.