ESTYL

The client's goal in the ESTYL project involved data migration and setting up a new version of the Shopware 6 store from the Magento 1.5 platform.

ESTYL on Magento 1.5 platform

• Established in 2011
• Managed by several software house agencies
• Numerous unique, dedicated functional modifications

Why Shopware? Key competitive advantages of the Shopware 6 platform

API First approach

The API consists of three Rest APIs: Admin API, Sync API, and Store API (formerly Sales Channel API), each with its own purpose.

• Admin API: Allows CRUD operations for all entities in the Shopware database, along with special endpoints for data search/filtering and document generation. It is stateless, using OAuth for authentication and supports JSON:API.
• Sync API: A specialized endpoint of Admin API for importing and exporting large amounts of data, allowing the import of 300 products per second, with long processes handled asynchronously.
• Store API: A headless interface for the frontend, enabling custom sales channels like mobile apps, POS, and standard online stores. Uses a custom header sw-access-key for authentication.

In summary, Shopware 6 greatly facilitates integration with external systems and the creation of custom interfaces without sacrificing performance.

Performance

Shopware 6 boasts high performance due to its advanced architecture and modern technological solutions.

Shopware solutions are optimized for speed and effortlessly adapt to growing business needs, ensuring lightning-fast responsiveness that guarantees customer satisfaction with online shopping.

Shopping Experience

Shopware Shopping Experiences is an integrated CMS that allows creating and managing content pages on the e-commerce platform. With its intuitive editor and "drag and drop" functionality, users can create attractive pages without advanced technical skills. The system supports various block types (text, images, video, products) and enables dynamic content addition. It also facilitates easy integration with external applications and offers content automation and personalization features.

Flow Builder

Flow Builder in Shopware enables the automation of business processes by defining sequences of actions triggered by specific events. Users can create complex workflows without the need for programming, which enhances operational efficiency. Examples of use include automatically sending notifications, managing orders, and executing marketing actions. Flow Builder helps businesses save time and resources by simplifying daily operations.

Rule Builder

Rule Builder in Shopware allows the creation of custom rules that automate various aspects of e-commerce operations. Users can define conditions and actions without programming, simplifying store management. Rules can cover scenarios such as dynamic pricing, customer segmentation, and marketing task automation. Rule Builder enhances flexibility and operational efficiency, adapting to specific business needs.

Tags

Tags allow for more precise categorization and filtering of products, customers, and orders. This helps sellers create dynamic product groups, personalize offers, and better manage marketing content. These updates aim to increase operational efficiency and tailor the store to specific business needs.

Strategic Requirements for the ESTYL.pl Project

Necessary Conditions for the Success of the ESTYL.pl Project

• Availability of the home platform team
• Decision-making authority on the client side
• Client's readiness for compromises
• Abandonment of old solution habits
• Utilization of design templates
• Non-negotiable scope of requirements
• Full transparency between the client and Crehler
• Timely delivery and closure of releases

ESTYL.pl Project Schedule

Schedule - Recommended Version

Schedule - Expected Version

Schedule - Final Version

Conclusions

Migration:

• Never assume the correctness of imported data.
• Do not judge the quality of all imported data based on a sampled product batch.
• Import data incrementally.
• Be prepared to adjust import assumptions during the process.
• Always communicate risks, problems, and possible solutions to the client at the start and during the data migration.
• Detail project requirements using the MoSCoW method.
• Set up a separate instance for data retrieval via API.
• Review and clean the original instance.
• Data migration to Shopware is an investment.

Shopware - minimize development work in favor of migration tasks:

• Shopware's default version offers many functionalities required in MVP.
• Shopware requires minimal time investment for performance optimization.