battles / Platforms
OXID eSales vs Spree Commerce
OXID eSales ($400/mo/mo, vibe code 5/10) vs Spree Commerce ($500/mo/mo, vibe code 6/10). Spree Commerce 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
$500/mo/mo
- MVP
- 2 weeks
- Full replacement
- 8-14 months
easier to rebuild
get the build prompt →price gap / year
$1,200/mo
running both / year
$10,800/mo
our call
Start with Spree Commerce — 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
Spree Commerce
Spree is free code you already own. Rebuilding it in a modern stack is realistic; you inherit the maintenance and lose the Rails extension ecosystem.
you can rebuild
- Catalog, taxonomy and variant modelling
- Cart and multi-step checkout
- Order, shipment and return records
- Admin CRUD screens
- Multi-store and multi-currency basics
what you lose
- The Rails extension ecosystem (payments, subscriptions, analytics)
- Years of accumulated promotion and tax edge cases
- Upstream security releases
- Developers who already know the API surface
real moats
- Extension ecosystem and long-running community
- Accumulated commerce edge cases in tax, promotions and returns
open source escape hatches
Questions people ask
Which is easier to rebuild with AI, OXID eSales or Spree Commerce?
Spree Commerce. It scores 6/10 on vibe code with a moat of 3/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 Spree Commerce?
OXID eSales at $400/mo/mo for a typical mid-market store. The gap between the two is about $1,200/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 Spree Commerce?
The Rails extension ecosystem (payments, subscriptions, analytics) Years of accumulated promotion and tax edge cases Upstream security releases
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