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 Developer
The variant model is the real thing — self-referencing parent-child products with a configurator that assembles property groups and variants, hierarchical categories, unlimited property groups for filtering, and products addressable across multiple sales channels. Payment breadth is thin in the captures: PayPal is the only provider named, and I found no public information on bundles, promotions and vouchers with rules, guest checkout, or invoice and direct debit as payment methods. The checkout itself is documented as customisable without a rebuild via the Store API, payment handlers and the state machine, which is what lifts it above the standard tier. 5 6 1 12