Codewerk.
Get a quote
Home/Blog/How to choose a shop system without writing a 90-page spec

How to choose a shop system without writing a 90-page spec

Long requirement documents make everyone feel safe and tell you nothing. Three exercises that reveal more than any feature matrix.

Photo: free stock photography (Unsplash licence) — see imprint

Why feature matrices lie

Every vendor ticks every box, because every box can be ticked with enough effort. 'Supports customer-specific pricing' is true of nearly all of them and tells you nothing about whether it takes a checkbox or a three-week plugin. The matrix measures marketing, not effort.

Exercise one: the ugly three

Write down the three requirements your own people cannot fully explain — the pricing exception, the weird approval, the article that behaves differently. Make every vendor demo those in their system, live. Half the shortlist disappears in an afternoon.

Exercise two: the leaving test

Ask each vendor, in writing: if we leave in three years, what exactly do we take with us, and in what format? The answers will differ enormously and tell you more about your future negotiating position than any pricing page.

Exercise three: call two of their customers

Not the reference the vendor gives you. Find a shop running the system, find its e-commerce manager on LinkedIn, and ask what broke last year. Twenty minutes of that is worth more than the entire evaluation process you were about to run.

Key takeaways
  • Feature matrices measure marketing, not effort.
  • Demo the three requirements nobody can fully explain.
  • Ask in writing what you take with you when you leave.

We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.

Talk to an engineer

// Keep reading

Related articles