Feature Requests

It would be useful to be able to set a password and customer type when adding / editing users as a Customer Association admin, e.g., in the ADD USER screen accessed from the User Management link. We have a company that would like to add users themselves, but they would like to set a password for the new user rather than forcing the new user to request a password reset. Another company needs to be able to set a customer type.

This field is used in single sign-on integrations, yet the only way to modify it is via import or API. It would be more convenient to use the admin panel to edit or verify the username for an individual customer.

The only way to edit reward points is via import (or API). There should be a way to edit records directly in the admin panel. Mock-up below

testing

Our use case is store-level custom fields to manage the content of a shared theme (including HTML). It would be nice on the back-end to have a placeholder or default value for more data types for when we create more multi-stores.

For example, we want to show the actual inventory value on the front end if we have less than 6 units remaining: ##IF[##QUANTITYONHAND## <6 ]## Only ##QUANTITYONHAND## remaining! ##ELSE## 5+ Remaining ##ENDIF## Cheers

The issue is having to list the dates of holidays for the next 50-or-so years. Unnecessary maintenance work especially with adding multi-stores. I think this feature should work based on a series of rules like the rule engine so that it works indefinitely. Additionally it could include common holidays that can be enabled via checkbox for even more convenient setup.

In the Custom Field section it would be helpful if we can enter a description of the Custom Field. For example, if we created a custom field called ShipType we would like to enter a  description regarding the proper entries to make for this field such as: Enter the type of shipping service required for this item. The options are: Small Parcel, LTL, White Glove.

We often need to confirm when items are in stock and some items have 5 or 6 variants. When we view the item audit history, it often cuts off after 2 or 3 variants. Also, the PK ID needed in the View Audit History Report and this is hard to find. Running a variant report shows different ID numbers than the PK ID. It shouldn't be this hard to confirm the date and amount of items are in stock after our warehouse receives them.

Have merge code functionality contain ##ELSEIF##, ##AND##, or ##OR## conditions