Catalogue & checkout
How this is scored
Products, variants, pricing rules and the path to payment — the part that either converts or does not.
0 — Flat product list with one price and no variants; checkout is a form and one payment method.
3 — Variants and categories with a standard checkout and two or three payment methods, but no bundles, no tiered pricing and no guest checkout worth the name.
5 — Full variant matrix, product bundles, tiered and customer-group pricing, guest checkout, and the payment methods a German shop needs including invoice and direct debit.
8 — Configurable products, per-channel pricing, promotions and vouchers with rules, a checkout that can be customised without a rebuild, and payment via the major providers plus 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
The variant machinery is real — parent-child inheritance, a configurator object, unlimited property groups for filtering — and the payment architecture with synchronous and asynchronous handlers and the redirect URL returned in the API response means checkout can be reshaped without a rebuild. But we found no public information on invoice or direct debit as payment methods, on promotions or voucher rules, on guest checkout or bundles, and customer-specific prices appear only in the top Beyond tier. 1 2 5 6