jHoldroyd

6 ms·

1.
by jHoldroyd 12y ago
You can use our checkout and order system but simply drop out the payment processing. Stripe makes this very easy and while people may not want to do it, by charging them a percentage of each transaction we're almost incentivizing them
2.
by jHoldroyd 12y ago
Exactly, we went through four revisions of our pricing and I'm not sure we'll ever be certain it's the "right" one. We just knew we had to simplify it and after user feedback this is the one that stuck. And thanks f
3.
by jHoldroyd 12y ago
We also felt that it meant the people building the sites also had an incentive to be more careful about the way they did it - like sharing resources across a session and limiting the calls per page, or implementing caching. All of which act
4.
by jHoldroyd 12y ago
That's the reason why we added the little bit of information about page-views to try and guide the user a little in case they had a store already. We very quickly know when a store is under attack and we either (where possible) drop th
5.
by jHoldroyd 12y ago
We've had a few people doing that, and we'll be forking our JavaScript SDK to natively support Node in the next week or two.
6.
by jHoldroyd 12y ago
Commercetools is a good platform and one of our closest competitors. The key differences are that our pricing scales a lot better, we don’t lock you into a single gateway or charge transaction fees. We also don’t arbitrarily limit the numbe
7.
by jHoldroyd 12y ago
Yes we do, we support over 50 payment gateways with more on the way. You can see the complete list here - https://moltin.com/faq#gateways
8.
by jHoldroyd 12y ago
Great, if you need anything or have any feedback we're always available on livechat or support@moltin.com
9.
by jHoldroyd 12y ago
Again, on the list - but if someone were to do one we'd be happy promote it ;)
10.
by jHoldroyd 12y ago
The beauty of an API approach is the features we don’t quite fully support can be easily created by you within your application, and then work alongside our product. We don’t explicitly advertise support for digital products at the moment,
11.
by jHoldroyd 12y ago
We have support for modifiers (size, colour, etc.), singles (gift wrapping, etc), input (custom options or labels). We’re working hard to make sure our new docs platform has all of this in it, but you can find it in the API reference and us
12.
by jHoldroyd 12y ago
In short, Yes! But perhaps not soon. We have a really strong community ethos at Moltin, and we’re trying hard to open up as much of our platform as possible, both in open source and community modules. We know there is still work to be done
13.
by jHoldroyd 12y ago
Because we’re quicker and easier to implement. That gives the developer much more freedom to be creative with their application, especially if they’re working within a budget or short timeframe. Our API also allows you to pick and choose th
14.
by jHoldroyd 12y ago
We are yes, we started with what we knew and now are allowing the community to vote on what they want us to release next - https://moltin.com/getting-started#vote
15.
by jHoldroyd 12y ago
Because we’re an API, you can retrieve, remove, destroy your data at will. When you incorporate us into your app or site, you have a very loose relationship with our system. That means its very easy for you to stop using our product withou
16.
by jHoldroyd 12y ago
Sorry about that, I'll take a look at the issue now.
17.
by jHoldroyd 12y ago
Hi there, co-founder here. A few of them do have an API offering, but there's a few issues with them - Firstly they’re bolted on the side, and aren’t usually functional enough to actually power a full store - generally they’re designed
18.
by jHoldroyd 12y ago
Hey co-founder here. Thanks, we're built on PHP, nginx, Postgres and redis running on AWS.
19.
by jHoldroyd 12y ago
Fantastic library, we've tried a few like it before and none of them really worked quickly or reliably enough. We did a quick mashup of our API and this to create a basic (but functional) mobile PoS using the phone camera as a scanner.