Shopware

Start by creating products and assigning each to the sales channels where it should appear. Put products in one or more categories so shoppers can find them through the category tree. Visibility controls can expose an item in listings and search, search only, or through its direct URL.

Categories also organize the storefront navigation. A merchant can structure main, footer and service navigation separately, and select the sales channels where a category appears. This makes catalog organization and page navigation part of the setup work, not an automatic result of adding products.

Community Edition includes a visual page builder plus product and order management. The Commerce Platform ties the storefront and catalog to checkout and customer operations, so a buyer can trace a sample product from listing to order before deciding on extensions.

Rule Builder is a standard feature across Shopware plans. It can use conditions to vary shipping options or costs, displayed prices and promotions by factors such as location, customer status, order quantity or cart value. A buyer should test representative rules with fictional products to check how conditions interact.

Do not assume all rule-driven storefront content controls are in Community Edition: the vendor marks CMS content visibility by rule for Evolve and Beyond. This is a useful entitlement check if a store needs private B2B pages or group-specific content.

After an order is placed, staff can filter the order list by order, payment and delivery status. An order detail displays those three statuses separately, so fulfillment and payment follow-up should be checked as distinct steps.

Shopware documents a subtle cancellation boundary: setting an order status to Canceled resets stock, while changing only payment or delivery status to Canceled does not effectively cancel the order. A buyer should walk through that distinction with a fictional order before writing staff procedures.