With the new offer management, customers can request individual offers when placing an order. When the customer’s shopping cart contains all desired items, they have the option of clicking a “Request offer” button, which opens a new window where they can propose a new price and leave a comment. The shop owner can then accept, edit or reject the new offer in the backend. Finally, the customer receives the new offer for re-confirmation.
Since the previous version, it has been possible to create and maintain user accounts and contacts. However, with version 2.0, we put the issue of user rights to the test and restructured it. Hierarchies were introduced, which greatly simplify handling in particular. The complete corporate or organisational structure can now be mapped using a tree structure. The added value of this representation is a much improved overview and simplified handling.
When a customer places an order in a shop that uses the B2B Suite, it will be possible to store individual product numbers for them. The advantage is that the customer can work with the product numbers they use in their own inventory management system. It’s possible to import these product numbers using a CSV file, Excel upload or by creating a definition in the customer’s account.
Shopware has integrated a so-called cache multiplexer into the Enterprise Edition, making it now easily possible to use multiple application servers in a cluster setup. In such cases, the cache multiplexer enables control over the individual caches for each server (useful for emptying/updating the template cache, for example). From one central point – the Shopware backend – all servers/caches can be controlled simultaneously.
By default, Shopware retailers use a single database. The more the online shop is frequented, the higher the load on the corresponding database. This is where Primary Replica steps in and divides between read and write operations. So while write operations continue to be sent to one single database, the read operations are sent to any number of databases. This load distribution brings another boost in performance to the online shop.
Redis is key value storage, so essentially another database. You save various types of data in Redis, including number ranges, product listings or even translations. Outsourcing regularly frequented areas to Redis offers yet another increase in performance. In addition, Shopware also uses Redis as a cache – the entire frontend cache can be outsourced to Redis and managed centrally even with multiple application servers. The clear advantages are simplified administration and improved scaling.
With the jMeter technology you can easily perform load tests for your own online shop. Shopware also provides a set of scripts that can be used to measure the shop’s performance, even before it has gone live. These scripts are easily customisable and can be used without detailed knowledge of jMeter. Among other things, the Shopware Performance Whitepaper is based on these scripts.
From now on it will be much easier for Shopware Enterprise customers to design a more flexible price allocation. This is done on the basis of customers, customer groups and customer streams and can also be determined on a time-dependent basis using conditions such as "country of delivery = Germany AND currency = dollar, then price = $100".
Another new feature is the definition of gross prices – such as "€89.90, regardless of VAT and currency" – and the possibility that graduated prices can be set everywhere. Additionally, you can easily maintain and configure the complete price handling via API.