battles / Platforms
OXID eSales vs Solidus
OXID eSales ($400/mo/mo, vibe code 5/10) vs Solidus (usage-based/mo, vibe code 6/10). Solidus is the easier one to rebuild yourself — here is what you lose either way.
Platforms
$400/mo/mo
- MVP
- 3 weeks
- Full replacement
- 10-16 months
Platforms
usage-based/mo
- MVP
- 2 weeks
- Full replacement
- 8-14 months
easier to rebuild
get the build prompt →price gap / year
$4,800/mo
running both / year
$4,800/mo
our call
Start with Solidus — highest vibe code, weakest moat.
OXID eSales
Rebuilding the storefront is straightforward. Reproducing DACH legal texts, price display rules, invoicing and GoBD-compliant archiving is the part that takes real work.
you can rebuild
- Catalog, variants and category management
- Cart, checkout and order administration
- Customer groups with net/gross pricing display
- Newsletter and basic CRM fields
what you lose
- German legal defaults: price display rules, cancellation policy, imprint requirements
- GoBD-compliant invoice archiving expectations
- DACH payment methods (Rechnungskauf, SEPA, Klarna) already wired
- The local agency and module ecosystem
real moats
- Deep DACH legal and tax defaults accumulated over two decades
- Local agency network and enterprise references
- B2B pricing and invoicing conventions expected by German buyers
Solidus
There is no licence to escape. Rebuilding makes sense only if you want to leave Ruby; otherwise you are trading a maintained core for a bespoke one.
you can rebuild
- Catalog, variants and option types
- Cart, checkout and order state machine
- Promotions with basic rules and actions
- Admin interface for orders and products
what you lose
- A maintained upgrade path with a security-conscious core team
- Rails extensions for payments, taxes and reporting
- Free bug fixes from other people's production incidents
real moats
- An active maintainer community absorbing edge cases you have not hit yet
open source escape hatches
- spree/spree BSD-3
- medusajs/medusa MIT
- saleor/saleor BSD-3
Questions people ask
Which is easier to rebuild with AI, OXID eSales or Solidus?
Solidus. It scores 6/10 on vibe code with a moat of 2/10, so an AI-assisted MVP takes about 2 weeks and a full replacement about 8-14 months.
Which one costs less, OXID eSales or Solidus?
Solidus at usage-based/mo for a typical mid-market store. The gap between the two is about $4,800/mo a year.
What do I lose if I replace OXID eSales?
German legal defaults: price display rules, cancellation policy, imprint requirements GoBD-compliant invoice archiving expectations DACH payment methods (Rechnungskauf, SEPA, Klarna) already wired
What do I lose if I replace Solidus?
A maintained upgrade path with a security-conscious core team Rails extensions for payments, taxes and reporting Free bug fixes from other people's production incidents
More battles
One e-commerce SaaS teardown every week.
Honest verdicts, build prompts and overlooked vertical SaaS opportunities. No tracking pixels, no drip sequence, unsubscribe in one click.
free forever · no third-party tracking · the prompts stay public