Skip to main content
Most mid-size and enterprise merchants do not start from zero. They run an ERP that owns stock, a PIM that owns product data, a DAM that owns media, a warehouse system that ships boxes, and a payment provider with years of history. Replacing all of that to adopt a commerce platform is not a migration — it is a rebuild nobody asked for. Spree takes the opposite position: it is the system of record for what the shopper sees, and your existing systems stay the system of record for what is true. Content, prices and stock sync in and render from Spree’s own copy; live calls to your systems happen only at decision moments — pricing a line, adding to cart, taking a stock hold, completing an order.

​
The provider contracts

Every connection point is a documented contract with a default implementation that uses Spree’s own data — a store that connects nothing works exactly as before.

​
Credentials live in one place

Provider credentials are managed through Spree integrations — one admin surface for connecting external services, with secrets stored as masked preferences and connections verified before activation. Provider gems ship an integration class; there are no per-provider credential screens or environment-variable contracts for per-store services.