--- title: Introduction to Shopware | Shopware Community Hub description: >- Understand Shopware’s evolution from version 4 to 6, its market positioning, and the platform’s approach to customization and flexibility in meeting diverse… canonical_url: >- https://hub.shopware.com/learn/unit/solutions-architect-introduction-to-shopware --- # Introduction to Shopware - Understand the **historical reasons** for various design decisions in Shopware. - Recognize Shopware's **ideal customer profile (ICP)** and market positioning. - Have an appreciation for the approach of Shopware to **customization and flexibility**. # Introduction to Shopware Shopware has evolved significantly since its early versions, adapting to changing market needs and technological advancements. This unit will explore Shopware's journey, current market position, and flexible implementation and customization options. ## The Evolution of Shopware ### Shopware 4: Embracing Open Source With Shopware 4, the company took a significant step by making its source code readable, including licensed versions. This move encouraged community contributions, fostering a collaborative ecosystem around the platform. ### Shopware 5: Going International Shopware 5 marked a shift towards internationalization, expanding beyond the German market. However, over time, it became evident that the platform was becoming overly complex with accumulated features and functionalities. ### Shopware 6: A New Beginning Shopware 6 was developed to respond to the challenges faced with version 5. The key principles behind Shopware 6 include: 1. **Platform Approach**: Enabling agencies and extension builders to add functionality while keeping the core nimble and light. 2. **Abstraction**: Recent releases have seen core components like stock and tax management refactored to be more abstract and interchangeable. 3. **Scalability**: The new architecture allows for better performance and easier customization for larger, more complex projects. These principles make Shopware 6 a robust and adaptable ecommerce solution suitable for businesses looking to grow and expand their online presence. ## Market Positioning and Ideal Customer Profile (ICP) As Shopware has matured, it has moved upmarket, catering to larger and more complex ecommerce operations. This shift has implications for agencies working with Shopware: 1. **Higher Expectations**: Up-market clients expect more expertise from agencies. This includes a higher service level and engagement, both pre-sale and post-delivery. Clients often look for strategic partners rather than just implementers. 2. **Broader Knowledge**: Agencies need to bring a wider range of knowledge to projects, going beyond simply setting up and customizing Shopware. This includes understanding related solutions such as Product Information Management (PIM) systems, Warehouse Management Systems (WMS), as well as common business processes and use cases in ecommerce. 3. **Solutions Architecture**: The need for this type of documentation reflects the increasing complexity of Shopware implementations. ### Shopware's ICP includes **Sales Channels:** - Businesses that operate across multiple sales channels, including online shops, marketplaces, social media platforms, and physical shops. **Ecommerce Maturity:** - Clients typically have some experience in ecommerce operations. **Revenue Range:** - Generally, online revenue starts at 5m EUR/USD and goes up to 150m and beyond. **Customization Needs:** - Prospects usually require some level of bespoke customization. ## Operation Modes and Customization Options Shopware offers multiple operation modes to cater to diverse client needs: 1. SaaS (Software as a Service) 2. PaaS (Platform as a Service) 3. On-Premises It's important to note that while these methods differ in terms of management and responsibility, they all use the same underlying Shopware codebase. The main differences lie in access and responsibility: - SaaS: Shopware manages the software and handles upgrades. - PaaS: Shopware provides and ensures performant hosting, but the agency is responsible for upgrades. - On-Premises: Shopware delivers the software as-is, with the client or agency responsible for hosting, management, and upgrades. For a deeper look at deployments, check out the learning unit [Development Best Practices](/learn/unit/solutions-architect-development-best-practices), part of the course "Customizing Shopware" in the same learning path. While this variety might seem confusing initially, each option has its merits and aligns with Shopware's philosophy of catering to a wide range of clients and agencies by making customization accessible. ## Customization Approaches 1. **Plugin System**: Traditional method for extending functionality. More about plugins [here](https://developer.shopware.com/docs/guides/plugins/plugins/). 2. **App System**: Modern, API-first approach to adding features. This article describes apps in more detail [Apps](https://developer.shopware.com/docs/guides/plugins/apps/). 3. **Themes**: Allows businesses to customize and modify the appearance and design of their online store. More on themes in this article: [Themes](https://developer.shopware.com/docs/guides/plugins/themes/). 4. **API Customization**: Allows for headless and custom frontend implementations [Api Integrations](https://developer.shopware.com/docs/guides/development/integrations-api/). 5. **Low-Code and No-Code Tools**: - [Rule Builder](https://docs.shopware.com/en/shopware-6-en/settings/rules): Creating complex business logic without coding applicable to pricing, visibility, and much more. - [Flow Builder](https://docs.shopware.com/en/shopware-6-en/settings/Flow-Builder): A solution for automating processes based on events and actions. - [Shopping Experiences](https://docs.shopware.com/en/shopware-6-en/content/ShoppingExperiences): A page builder tool used to create custom layouts and content structures on pages. These tools empower technical and non-technical users to customize and extend Shopware's functionality, reflecting the platform's commitment to flexibility and ease of use. We'll explore this topic further in a [later unit](https://hub.shopware.com/learn/unit/solution-architect-plugin-vs-app-vs-api-vs-theme-vs-no-code). ## The Importance of the Shopware Ecosystem Shopware's success is deeply rooted in its extensive ecosystem of partners and integrations. This ecosystem continues to be paramount to the platform's growth and adaptability. Key aspects include: **Extension Builders**: - Shopware relies on a community of developers and companies to create extensions that add functionalities and integrations. These extensions cover many needs, from marketing suites to payment gateways and beyond. **Extension Store**: - A marketplace where these extensions are available, allowing businesses to find and implement additional features easily. **Integration Partners**: - Companies specializing in connecting Shopware with other business systems, creating seamless workflows across the ecommerce ecosystem. **Solution Partners**: - Agencies and consultancies specializing in Shopware implementations, bringing expertise and best practices to projects. For Solutions Architects, understanding this ecosystem is crucial: - **Extension Knowledge**: Familiarity with available extensions can help recommend off-the-shelf solutions when appropriate, saving time and resources. - **Build vs. Buy Decisions**: Solutions Architects must be able to evaluate when to recommend a bespoke feature development versus utilizing an existing extension from the store. - **Ecosystem Leverage**: Understanding how to leverage the ecosystem can lead to more robust and cost-effective solutions for clients. - **Future-Proofing**: Knowledge of the ecosystem helps design solutions that can easily adapt and expand as the client's needs grow. By embracing and utilizing Shopware's ecosystem, Solutions Architects can create more comprehensive, efficient, and scalable ecommerce solutions for their clients. ## Use Case: Fashion Retailer Migration A fashion retailer with €20 million in online revenue is looking to migrate from their legacy platform to a more flexible solution. As a Solutions Architect, you would: 1. Recommend Shopware based on the client's revenue and industry alignment with Shopware's ICP. 2. Suggest a PaaS deployment for the balance of control and managed infrastructure. 3. Plan to use plugins and apps for standard features and develop custom apps for unique requirements. 4. Utilize the Rule Builder for complex pricing and promotion scenarios. 5. Implement the Shopping Experiences (CMS) for the marketing team to create landing pages easily. The outcome? A tailored Shopware solution that meets the retailer's specific needs while providing flexibility for future growth.