I'm a developer looking to stand up an ecommerce site, but have become frustrated with the available options, all of which seem geared to marketers who are more than happy to pay $30/month for the privilege of never touching code.<p>I want the complete opposite. I want to build an ecommerce site where I have complete control over the front-end code, and it just hooks into some RESTful back-end server somewhere else to process payment, grab shipping info, etc.<p>Are there any solutions for this? Something that would allow me to abstract away a lot of the ecommerce back-end into APIs, without completely giving up front-end control?
Have a look at <a href="https://spreecommerce.com" rel="nofollow">https://spreecommerce.com</a> (<a href="https://github.com/spree/spree" rel="nofollow">https://github.com/spree/spree</a>). You'd still have to setup the backend though I think they offer hosting solutions now.<p>Shopify has an extensive API. You'd be able to create your own frontend with or without their shopping cart, with or without their checkout process and with or without third-party whitelabel shipping.
Theres molitn (<a href="https://moltin.com/" rel="nofollow">https://moltin.com/</a>) from the YC15 batch, I haven't tried maybe it's for you.
Hrm... A while ago, I worked on a project that is somewhat like what you described in that it's a cart where you have the full ability to use any CMS you want (or none at all) for product listing pages.<p>There wasn't an API, though—most of the cart-specific functionality was done in JS. It's just a different approach to solve your problem.<p>I never finished the project, but it's really close to being ready for launch. I'm interested in discussing it with you further! Shoot me an email (it's in my profile).
Would you be willing to pay for this if there was a product that suits your needs or are you looking for a completely free solution?
I was using <a href="https://en.wikipedia.org/wiki/Spree_Commerce" rel="nofollow">https://en.wikipedia.org/wiki/Spree_Commerce</a> when building something similar. The frontend was a custom JS SPA while the backend + API was handled by a rails app that was running spree.