Ideas

Change the way history is presented. Today the History tab is useless: It holds so much data that the site just loads for a long time to in the end is not able to present it. When the history in the beginning did load (because it didn't have that ...

The possibility of adding restrictions on what a back office admin is allowed to edit. For example a “EnglishAdmin” user can edit the english values of Website fields, but not the swedish values.

It would be useful to be able to add custom fields to addresses in Customers. This could be used for receiver company name, address-id, delivery information etc.

It should be possible to get the Litium ID of the role using customerRoles in Storefront API. Currently there is only the translated name and ID of GraphQL cache. We need something like this: query GetContent { customerRoles { id roleId name }}

It should be possible to get the Litium ID of the address type using customerAddressTypes in Storefront API. Currently there is only the translated name and ID of GraphQL cache. The ID is useful to filter addresses by type, eg. in a creation where...

As it is today its not possible to delete orders in our Litium backend.

Its currently possible to add pointer of entity type Website. Would be very vauable to be able to point to a channel as well.

It would be useful if a field template could inherit fields from another template by marking it as parent. That would allow creating a single base template with fields common to all products and new templates would just need to define its unique f...

Add support for displaying price, unit of measurement and stock balance as columns in PIM views.

A button in Backoffice to force a purge of the Redis cache.