Shopware & Pickware ERP The modular Onlineshop-System

Shopware is a modular online shop software developed in Germany which is available as open source software as well as in commercial editions.

Shopware is not just a pure shop system, Shopware offers besides the general basic functions of an innovative shop solution also CMS functionalities and with Pickware also functions of a well thought-out merchandise management out of the box, as well as through several thousand extensions similar to WordPress the possibility to adapt the system to the needs of the user. With Version 6, which was introduced in May and follows an API first approach, not only was a completely new technological basis based on Symfony and Vue created, but also the headless approach can now be effectively implemented with the software.

Community Edition
The Community Edition was introduced at the end of 2010 and is a free, open source version of the software on the same technical basis as the paid editions. While the source code was disclosed in 2010, with the release of version 4 on August 28, 2012, the software was placed under the AGPL3 license.

For the free software, the manufacturer offers no warranty and no support or maintenance, but a Wiki and a forum are available. The Community Edition is not limited in its functionality and can manage any number of categories, articles and customers. An upgrade to the paid editions is possible. The Community Edition can be extended with free and paid plugins from the Community Store.

Professional Edition
The Professional Edition is a commercial license. In addition to the basic functionalities of the Community Edition, it contains additional features such as storytelling, digital publishing and a separate ERP system. In addition, this edition entitles customers to a warranty and to manufacturer support and maintenance.

Extensions
There are about 3,500 plug-ins for shopware, including administration, evaluations, languages, advertising and marketing as well as template and design. Furthermore, there are interfaces to almost all known payment service providers and various merchandise management systems. Shopware offers the possibility to create invoices and delivery notes yourself; however, functions such as purchasing or financial accounting are not integrated. Therefore interfaces to various ERP and merchandise management systems are offered. So there is nothing to stand in the way of all requirements. If a functionality is not yet available, I as a web developer can also develop an individual plugin for your shopware shop, tailored to your requirements.

Technology
Shopware was developed in the programming language PHP. Up to version 5, the basis was the framework "enlight", a producer-specific modification of the Zend Framework. From version 6 on, the base of Shopware is based on the Symfony Framework. A relational MySQL database is required. The software follows the MVC design pattern as well as the template design. Smarty is used as the framework for the templates, for the development of JavaScript components since version 6 the library Vue.js is used.

Advantages of Shopware

High flexibility, scalability and individual design for different target groups from SMEs to large companies, Shopware offers different versions for different needs and price ranges
Extensive support is granted (from Professional Edition upwards)
Uncomplicated creation not only of landing pages, but of entire worlds of experience and themes
No programming knowledge is required to set up and operate the system
Backend can be operated easily and intuitively
The shop system is browser-based
A wide range of functions and templates

Disadvantages of Shopware

Some important functions only available in paid plugins
Special server or web hosting required
Partially high costs due to premium plugins
Special technical knowledge required for the installation of shopware

Pickware ERP

Pickware is a powerful complete merchandise management solution especially for your shopware online shop. Pickware is integrated directly into the Shopware and is free of charge in the basic version.

Do you need support for your next web project?

Niels Langlotz
Web-Developer

Tel: +49 176 45 606 488
E-Mail: info(at)typoniels.de

I would like to use my project experience as a developer for your next project, just contact me.

Frequently asked questions & answers

The answer to the following questions may also interest you

Shopware version 6 was released in March 2021 and so you may ask yourself as a current or future store owner whether you should continue to rely on version 5, which will still be supplied with bug fixes and security until 2024, or whether the step to switch to version 6 now is the right one.

To make it short: It depends. For example, if you have a good running Shopware 5 online store with many customers, many purchased plug-ins, individually developed extensions and connections to various third-party systems. Leave yourself some more time. Your version is still somewhat directly supported by Shopware. An upgrade does not have to be completed in the next few months.

If, on the other hand, it is a new store project, you should definitely go directly to the new Shopware version. In the future, there will be a lot of new extensions and services that can be used for your business model. Here, the path with version 6 is worthwhile.

I would be happy to upgrade your existing Shopware store
Request a quote now via email to shopware-upgrade(at)typoniels.de.

Ingredient	Bakingtime	Bakery	Baking instructions
Cookie secret ingredient	1 year	TYPONiels HTML	Saves your consent to using cookies.
TYPO3 Users (Login)	session	TYPONiels HTTP	Assigns your browser to a session on the server.

Ingredient	Bakingtime	Bakery	Baking instructions
User ID	13 months	Matomo HTML	Used to store a few details about the user such as the unique visitor ID.
Referrer	6 months	Matomo HTML	Used to store the attribution information, the referrer initially used to visit the website.
Session of the user	30 minutes	Matomo HTML	Short lived cookie used to temporarily store data for the visit.
Data of the session	30 minutes	Matomo HTML	Short lived cookie used to temporarily store data for the visit.
Temporary Data Object	30 minutes	Matomo HTML	Short lived cookie used to temporarily store data for the visit.
AdSense Audit	3 months	Google HTML	Used by Google AdSense to experiment with advertisement efficiency.
AMP Token	1 year	Google HTML	Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, request in progress or an error retrieving a Client ID from AMP Client ID service.
DoubleClick identifier	2 years	Google HTML	Used by DoubleClick (Google Tag Manager) to help identify the visitors by either age, gender or interests.
Survey Invitation	365 days	Hotjar HTML	Hotjar cookie that is set once a visitor interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.
Survey completed	365 days	Hotjar HTML	Hotjar cookie that is set once a visitor completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.
Survey (FeedbackMessage)	365 days	Hotjar HTML	Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.
Feedback form minimized	365 days	Hotjar HTML	Hotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show.
User identifier	365 days	Hotjar HTML	Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Letzte Aktivität	session	Hotjar HTML	This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).
TLD test	session	Hotjar HTML	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
Feedback User Attributes	session	Hotjar HTML	User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
User attributes (Cached)	session	Hotjar HTML	This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.
LocalStorage test	365 days	Hotjar HTML	This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
Page limit	30 minutes	Hotjar HTML	This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit.
Session limit	30 minutes	Hotjar HTML	This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit.
Session Process Flag	30 minutes	Hotjar HTML	This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.

Do you need support for your next web project?

Frequently asked questions & answers

Shopware Version 5 or 6?