re: How / What to choose for your next e-commerce web project VIEW POST

VIEW PARENT COMMENT VIEW FULL DISCUSSION
 

Ha, yeah I see what you mean. We've got a few different use cases and it's bendable enough to drop in another project (which several customers do - ie we're not rip and replace from the ground up).

The main advantage is the fact we're an API, so the frontend implementation is customisable to your own requirements - if you're wanting something along those lines, the JS SDK is a good option but you can use any language you like. We have some starter resources as well to get a handle on it (OSS is here - github.com/moltin?utf8=%E2%9C%93&q... ) and some time in the docs is well spent - moltin.com/docs/tutorials/

code of conduct - report abuse