Catalogue & checkout
How this is scored
Products, variants, pricing rules and the path to payment — the part that either converts or does not.
0 — Not a shop: no product catalogue and no checkout of its own.
3 — A product catalogue with categories and a checkout that takes payment through at least one provider.
5 — Products with variants, discounts or vouchers, guest checkout, and several payment methods including those German buyers expect (PayPal, invoice or direct debit) through named providers.
8 — Tiered and customer-group pricing, bundles or configurable products, rule-based promotions, per-channel or per-market pricing, abandoned-cart recovery, a checkout customisable without a rebuild, and buy-now-pay-later where offered.
10 — Merchandising and checkout are the product: rule-driven pricing and promotions, A/B-testable checkout, multi-currency and multi-language as standard, and conversion features (abandoned cart, one-page checkout) shipped rather than bolted on.
The Developer
Variants are modelled properly — a parent-child product with a configurator object assembled for Store API requests, hierarchical categories and property groups for filtering — and payments run through documented synchronous and asynchronous handlers with PayPal named and Shopware Payments in the paid plans. Customer-specific prices sit on the top Beyond plan. We found no public information on discounts or vouchers, guest checkout, abandoned-cart recovery or rule-based promotions, so this sits at the variants-plus-named-payment level. 5 6 1 2