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 Merchant
A native one-page checkout ships in the 9.2 bundle with developer documentation for modules and themes to adapt it, orders record payments by module name, and cart-rule discounts can be applied to orders — real conversion bones. But we found no public information on named payment providers, German payment methods such as invoice or direct debit, guest checkout, product variants or abandoned-cart recovery, so I cannot credit the level where payment breadth converts. 4 10