Answers.Body: <p>I just finished <a href="http://lighthouseroasters.com/">my first Snipcart project</a> and I'm in the process of making a plugin for browsing orders and customers from the Craft control panel. Lindsey D's got the landscape covered with his answer so I can at least share my experience with <a href="https://snipcart.com/">Snipcart</a>:</p>
  
  <h2>Snipcart</h2>
  
  <p>For those who somehow skipped other answers or haven't <em>looked at</em> Snipcart, it's a JavaScript cart service that's focused on being quick and easy to implement. You define product links with some <code>data</code> markup, include their cart JavaScript, and get a modal (guest+member) cart and checkout flow that you can style as needed. It can work with physical products, downloads, somewhat configurable products, and it comes with support for flexible promotional code options. There's a somewhat limited (but useful) control panel, integration with a handful of payment gateways, and the option of using live shipping rates from different (selectable) carriers.</p>
  
  <p>Snipcart is not as full-featured as something like Shopify—the reporting is fairly basic and we're hoping for gift certificate support, for example. My client asked to customize the specific shipping speeds/services offered by carriers, but at the time of this answer it's not possible; you can only toggle one <em>carrier</em> or another, not the individual services from that carrier. These limitations are the tradeoffs you get with Snipcart since it's young: it's astonishingly easy to get working right now, but if a particular feature doesn't exist there's not much you can do other than ask and wait.</p>
  
  <h2>Team Snipcart</h2>
  
  <p>Snipcart's team is small but dedicated and incredibly responsive. It's abundantly clear that they're working hard on building and refining their product. Charles responded quickly and thoughtfully to every question I had, even the annoying didn't-RTFM ones. He was willing to take feature requests, help troubleshoot when I had issues, and he's a nice guy to boot.</p>
  
  <p>Sometimes merely asking about <em>how to do something</em> would result in a feature magically appearing or a problem being fixed.</p>
  
  <h2>Integration</h2>
  
  <p>If you can <a href="http://docs.snipcart.com/configuration/product-definition">define your products</a> in a way that works, you're basically done. There are JavaScript and REST APIs and webhook support for limited extensibility. The Snipcart folks are aware of Craft, to the point of <a href="https://snipcart.com/blog/managing-your-craft-inventory-using-snipcart-webhooks">suggesting Craft-specific inventory management on their blog</a>.</p>
  
  <p>Snipcart was easy to drop in and immediately get a working cart. (And we're using Stripe, which is always dreamy in my experience.) Overriding/customizing cart styles was painless, even though Snipcart could change the base cart markup at any time and require some adjustment.</p>
  
  <p>Integration with Stripe was perfectly smooth, in test mode and in live mode—not a single issue or hiccup. Snipcart was available and fast 100% of the time, and every order has been captured and charged flawlessly as you'd expect. (We had some initial configuration issues on our end that we quickly worked out, but those weren't Snipcart's fault.)</p>
  
  <p>We had an awkward account-juggling process since there's only one set of administrative credentials per Snipcart account. We ended up creating a new client-owned account and reconfiguring it for launch. Not a big deal, but it'd be nice to see multiple account users as an option. You can have multiple private API keys, hence the Craft plugin I'm working on for browsing orders/customers.</p>
  
  <h2>Conclusion</h2>
  
  <p>Snipcart's definitely the scrappy new kid on the block, this simple integration has gone pretty well, and I would look to use Snipcart again for the right project. For a store with more intense/complicated needs, Shopify, Commerce, or Sprout Commerce might give you more control at the expense of more development time.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T19:53:34.340Z
Answers.Text: Any chance it's possible to hide shipping methods/services you don't want with CSS?
Answers.UserDisplayName: Anna_MediaGirl
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T20:05:44.807Z
Answers.Text: @Anna_MediaGirl I considered that, it just made me nervous because it'd be unreliable at best. The services aren't uniquely classed or identified, so I'd have to hide the *nth* element which could change depending on the services available for a customer's geographic location. So it might be possible, I'm just reluctant to live with on such a workaround.
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T22:28:20.357Z
Answers.Text: I couldn't agree more. Maybe they will class them for us. I'll ask. If not, I can't use them for the project I'm about to start. Will send an email.
Answers.UserDisplayName: Anna_MediaGirl
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T22:31:22.993Z
Answers.Text: Cool, thanks @Anna_MediaGirl. Regardless I hope the project goes well and look forward to your answer here about whatever you end up using!
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T23:05:07.430Z
Answers.Text: From their team... "we plan to allow selecting methods from the dashboard, but adding a css class is a good/fast idea, we will try to do it soon". The CSS class does the trick for me.
Answers.UserDisplayName: Anna_MediaGirl
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T04:42:13.613Z
Answers.Text: They added the CSS class to the <tr> tag. Kudos for quick!
Answers.UserDisplayName: Anna_MediaGirl
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T16:42:00.677Z
Answers.LastActivityDate: 2014-06-19T19:11:10.427Z
Answers.LastEditDate: 2014-06-19T19:11:10.427Z
Answers.UserDisplayName: Matt Stein
Answers.Body: <p>I've yet to try it but <a href="https://snipcart.com">Snipcart</a> seems to be on of the most viable options right now. Essentially it works though HTML/JavaScript and integrates with fields you define in your Craft setup, see their post explaining <a href="https://snipcart.com/blog/integrating-snipcart-with-craft-cms-a-child-s-play-">here</a>. You can even update your inventory using their webhooks, again they explain how to <a href="https://snipcart.com/blog/managing-your-craft-inventory-using-snipcart-webhooks">here</a>.</p>
  
  <p>The only others that you haven't mentioned but are in the Straight Up Craft directory are a <a href="https://github.com/davist11/craft-shopify/">Shopify plugin</a> by Trevor Davis and <a href="http://squarebit.co.uk/plugins/charge">Charge</a> by Joel Bradbury - I'm not sure if you have already seen these.</p>
  
  <p>For an upcoming site I plan to try the Snipcart method, failing that I'll fall back to implementing <a href="https://stripe.com">Stripe.js</a> manually and writing a plugin to handle the inventory side of things with <a href="https://stripe.com/docs/webhooks">Stripe webhooks</a>.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T11:09:28.820Z
Answers.Text: You're right, I'd forgotten about Snipcart. I had seen that blog post. I'm wary of a purely JS solution only because I'm an old school progressive enhancement type of guy.
Answers.UserDisplayName: Mike Pierce
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T11:11:21.520Z
Answers.Text: Shopify unfortunately isn't an option for my client in this case.
  
  Charge looks great for simple payments, but as far as I can tell there's no concept of a cart or shopping session, right?
Answers.UserDisplayName: Mike Pierce
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T11:37:43.257Z
Answers.Text: Yep charge simply lets you buy individual things, not collect them in a cart.
Answers.UserDisplayName: Josh Angell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T11:40:32.377Z
Answers.Text: Another method I've been thinking over is writing my own cookie-based cart, using PayPal as the only gateway (you can just POST them a form with stuff in it) and then somehow getting back inventory data on the return from PayPal - I know all this is possible but I've not actually tried any of it!
Answers.UserDisplayName: Josh Angell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T08:41:13.870Z
Answers.LastActivityDate: 2014-06-19T08:41:13.870Z
Answers.UserDisplayName: Josh Angell
Answers.Body: <p>Foxycart indicates they are jumping in  <a href="https://twitter.com/foxycart/status/478952251239567361">https://twitter.com/foxycart/status/478952251239567361</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T16:15:49.783Z
Answers.Text: So Foxycart is turning on the lights as we inquire http://bit.ly/SXFIr2
Answers.UserDisplayName: cmcjane
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T18:51:57.557Z
Answers.Text: I think they sensed that they were being talked about somewhere.
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T20:43:19.843Z
Answers.Text: Indeed, but I think they were already on it, or they have an amazing ability to learn quickly!
Answers.UserDisplayName: cmcjane
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T02:17:38.460Z
Answers.LastActivityDate: 2014-06-20T02:17:38.460Z
Answers.UserDisplayName: cmcjane
Answers.Body: <h3>E-commerce Master List</h3>
  
  <p><strong>This is a compilation of all publicly available solutions.</strong> Other answers here describe each plugin in greater detail... This is simply a complete list of every known option.</p>
  
  <p>Listed in alphabetical order (not by popularity or preference)</p>
  
  <p><strong>1st party plugin</strong></p>
  
  <ul>
  <li><a href="https://craftcommerce.com/">Craft Commerce</a> (<em>see more info below</em>)*</li>
  </ul>
  
  <p><strong>3rd party plugins (built exclusively for Craft)</strong></p>
  
  <ul>
  <li><a href="http://squarebit.co.uk/software/craft/charge">Charge</a></li>
  <li><a href="http://sprout.barrelstrengthdesign.com/craft-plugins/commerce">Sprout Commerce</a> (in private beta)</li>
  </ul>
  
  <p><strong>3rd party services with official Craft plugins</strong></p>
  
  <ul>
  <li><a href="https://github.com/FoxyCart/foxycart-craft">FoxyCart</a> (<a href="https://wiki.foxycart.com/integration/craftcms">integration notes</a>)</li>
  <li><a href="https://github.com/snipcart/snipcart-craft-webhooks-plugin">Snipcart</a></li>
  </ul>
  
  <p><strong>3rd party services with unofficial Craft plugins</strong></p>
  
  <ul>
  <li><a href="https://github.com/lindseydiloreto/craft-moltin">Moltin</a></li>
  <li><a href="https://github.com/davist11/craft-shopify/">Shopify</a></li>
  <li><a href="https://github.com/mattstein/snipcart-craft-plugin">Snipcart</a></li>
  </ul>
  
  <p><strong>DIY custom solutions (via an API)</strong></p>
  
  <ul>
  <li><a href="https://moltin.com/">Moltin</a></li>
  <li><a href="https://developer.paypal.com/docs/api/">PayPal</a></li>
  <li><a href="https://stripe.com/docs">Stripe</a></li>
  </ul>
  
  <blockquote>
    <p>&#42; Craft Commerce was formerly known as "Market Commerce" (aka "Cellar Commerce"). The name was changed after the plugin (and its developer, <a href="https://twitter.com/lukeholder">Luke Holder</a>) were <a href="http://pixelandtonic.com/blog/craft-commerce">acquired by Pixel &amp; Tonic</a>.</p>
  </blockquote>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T11:12:52.987Z
Answers.Text: Thanks @lindsey-d, looking forward to seeing what others think when it comes to this question. I can't have been the first one to wish for the simplicity of Craft CP extended to managing a store.
Answers.UserDisplayName: Mike Pierce
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T17:28:15.737Z
Answers.Text: @MikePierce I doubt I'm the first one either, but you're not alone.
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T15:02:35.063Z
Answers.Text: @LindseyD FoxyCart has been around for a while (used it on another project ~3 years ago), so it probably belongs in "Adapted for Craft" since you could start using it right now if you wanted to.
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T16:06:00.403Z
Answers.Text: Hmm, good point @MattStein... I put it in the "Coming Soon" category because it looks like they're working on an official Craft adaptation (like Snipcart did). What you describe would fall more into the DIY category (though not via API). Thoughts?
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T18:50:25.517Z
Answers.Text: @LindseyD They [just posted notes on integrating with Craft](https://wiki.foxycart.com/integration/craftcms), as though they sensed they were being mentioned somewhere. FoxyCart's platform is similar Snipcart just more full-featured, with very flexible checkout pages instead of modals. I don't know what "Adapted for Craft" is supposed to mean, honestly, I just imagine that Snipcart and FoxyCart should appear in the same category.
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T19:05:31.633Z
Answers.Text: @MattStein They are mind-readers! Perhaps they do belong in a different category. "Adapted for Craft" means that a plugin has been written which makes it easier to integrate that 3rd party service... which hasn't yet happened for FoxyCart (though may be in the works). I'm certainly open to re-organizing the list or re-naming categories, let me know what you think it should be called!
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T19:09:42.490Z
Answers.Text: @LindseyD Oh I'm just here to complain, not offer productive suggestions. But if you *insist*, I'd consider Snipcart and FoxyCart "Drop-In Services" since they're super quick to implement and the entire cart+checkout flow is handled by a third party. As opposed to Stripe/PayPal where you'd have to make a cart, figure out shipping, etc. or Charge/Commerce/Sprout that'd run on the server with Craft.
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T19:12:39.210Z
Answers.Text: @MattStein I like it! I might wait a few more days to make that adjustment, just in case FoxyCart is truly about to release a plugin. I'm trying not to over-edit this post. :)
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:06:32.243Z
Answers.Text: @MattStein LindseyD ooops some how I didn't see the last three comments before I edited it.  Should I unedit it?
Answers.UserDisplayName: cmcjane
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:08:07.703Z
Answers.Text: @cmcjane I think so, yes. FoxyCart's definitely not an API-only thing, so your edit's in an entirely different direction altogether.
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:09:20.933Z
Answers.Text: @MattStein that's why the kids shouldn't play after dark.
Answers.UserDisplayName: cmcjane
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:10:44.257Z
Answers.Text: @cmcjane Actually, I got to "review" that edit and approve it... Based on this conversation, I let it get moved into API. Sounds like FoxyCart exists outside of our classification system!
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:11:59.323Z
Answers.Text: In the Catholic Church there is this concept of "in limbo"
Answers.UserDisplayName: cmcjane
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:14:42.893Z
Answers.Text: Regardless of who classifies it (cmcjane, Lindsey D, the Pope), FoxyCart is more like Snipcart than PayPal or Stripe.
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:14:43.630Z
Answers.Text: @cmcjane Lol, it's definitely in limbo. I'm debating whether to reject your un-edit (nothing personal). Based on what Matt suggested, FoxyCart should just go into a new category called "Drop-In Services". And based on FoxyCart's recent activity, it wouldn't surprise me if a true plugin were just days away. What are your thoughts?
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:15:49.957Z
Answers.Text: @MattStein Ah, except that a plugin has been written for Snipcart (by Snipcart)! Should that get moved to the "Built specifically for Craft" category?
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:18:46.093Z
Answers.Text: @LindseyD I would still put it in "Drop-In Services" and note "(plugin available)" next to it. The plugin is a post-receive hook for modifying order quantity. FoxyCart could technically write a plugin to put their logo in the Craft dashboard and get moved to "Built specifically for Craft" by your presence-of-first-party-plugin criteria. Unless it's a plugin for comprehensive Craft integration, I don't think that criteria's all that significant.
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:22:25.460Z
Answers.Text: @MattStein The thought behind "Built specifically for Craft" was definitely for 100% native Craft integration. "Adapted for Craft" was supposed to represent 3rd party services that had plugins built to integrate with Craft... By your logic, Shopify would also be a "Drop-In Service" (plugin available).
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:28:03.503Z
Answers.Text: @LindseyD Dammit you're right, and I guess I finally see how FoxyCart can be in DIY instead of adapted. I surrender for now, this entire q/a is a real challenge!
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-20T21:28:52.503Z
Answers.Text: @MattStein Ok, I've got a new plan... Cross your fingers! :)
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-21T05:37:23.797Z
Answers.Text: Sorry had to hop on a ferry for Marthas Vineyard, out of loop for a few.  I think the solution is to remove the (via an API) from the DIY and open up that category to be like purgatory, where the taste of heaven is on your lips and entirely possible, as opposed to Built Exclusively for Craft where you are in the land of milk and honey.
Answers.UserDisplayName: cmcjane
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-21T05:43:49.367Z
Answers.Text: Lol @cmcjane, that may be the greatest comment I've read all day. I've already given FoxyCart their own category of "3rd party services (no plugins)" as well as had a little [Twitter chat with them today](https://twitter.com/LindseyDiLoreto/status/480078864975011840). You make a valid point though, I'll definitely keep that suggestion in mind for a future edit (I get the feeling this list will continue to evolve). Thanks for the contributions!
Answers.UserDisplayName: Lindsey D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-23T18:40:30.197Z
Answers.Text: @LindseyD Unfortunately I just caught up on this thread, and I don't have any complaints about the current list. But I'll be watching [with unnecessary skepticism](http://i1.ytimg.com/vi/OGAu_DeKckI/hqdefault.jpg)...
Answers.UserDisplayName: Matt Stein
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-19T09:22:45.257Z
Answers.LastActivityDate: 2015-12-02T00:31:49.680Z
Answers.LastEditDate: 2015-12-02T00:31:49.680Z
Answers.UserDisplayName: Lindsey D
Body: <p>I'm developing an online store. The store needs to be seamlessly integrated with all of the editorial content on both the front and back-end. Craft is obviously a perfect candidate for the editorial content, but at this moment the options for e-commerce plugins are limited.</p>
  
  <p><strong>What e-commerce options are currently available for Craft?</strong></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-08-14T18:31:30.237Z
Comments.Text: Due to the nature of this question, it's been converted into a community wiki. _"Questions should be manually converted to community wiki when they are marginal fits or 'list of X' questions that contain enough value to avoid deletion."_
Comments.UserDisplayName: Lindsey D
Tags: <plugins><ecommerce>
Title: What is the current landscape regarding e-commerce plugins for Craft?
ThreadText: # What is the current landscape regarding e-commerce plugins for Craft?
  
  (Asked by: username_0 on 2014-06-19)
  
  I'm developing an online store. The store needs to be seamlessly integrated with all of the editorial content on both the front and back-end. Craft is obviously a perfect candidate for the editorial content, but at this moment the options for e-commerce plugins are limited.
  
  **What e-commerce options are currently available for Craft?**
  
  **Tags:** plugins, ecommerce
  
  > **Comments:**
  > **username_1**: Due to the nature of this question, it's been converted into a community wiki. _"Questions should be manually converted to community wiki when they are marginal fits or 'list of X' questions that contain enough value to avoid deletion."_  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_1 on 2014-06-19. Score: 40 | Accepted answer
  
  ### E-commerce Master List
  
  **This is a compilation of all publicly available solutions.** Other answers here describe each plugin in greater detail... This is simply a complete list of every known option.
  
  Listed in alphabetical order (not by popularity or preference)
  
  **1st party plugin**
  
  * [Craft Commerce](https://craftcommerce.com/) (*see more info below*)\*
  
  **3rd party plugins (built exclusively for Craft)**
  
  * [Charge](http://squarebit.co.uk/software/craft/charge)
  * [Sprout Commerce](http://sprout.barrelstrengthdesign.com/craft-plugins/commerce) (in private beta)
  
  **3rd party services with official Craft plugins**
  
  * [FoxyCart](https://github.com/FoxyCart/foxycart-craft) ([integration notes](https://wiki.foxycart.com/integration/craftcms))
  * [Snipcart](https://github.com/snipcart/snipcart-craft-webhooks-plugin)
  
  **3rd party services with unofficial Craft plugins**
  
  * [Moltin](https://github.com/lindseydiloreto/craft-moltin)
  * [Shopify](https://github.com/davist11/craft-shopify/)
  * [Snipcart](https://github.com/username_2/snipcart-craft-plugin)
  
  **DIY custom solutions (via an API)**
  
  * [Moltin](https://moltin.com/)
  * [PayPal](https://developer.paypal.com/docs/api/)
  * [Stripe](https://stripe.com/docs)
  
  > \* Craft Commerce was formerly known as "Market Commerce" (aka "Cellar Commerce"). The name was changed after the plugin (and its developer, [Luke Holder](https://twitter.com/lukeholder)) were [acquired by Pixel & Tonic](http://pixelandtonic.com/blog/craft-commerce).
  
  > **Comments:**
  > **username_0**: Thanks @username_1-d, looking forward to seeing what others think when it comes to this question. I can't have been the first one to wish for the simplicity of Craft CP extended to managing a store.  
  > **username_2**: @username_0 I doubt I'm the first one either, but you're not alone.  
  > **username_2**: @username_1 FoxyCart has been around for a while (used it on another project ~3 years ago), so it probably belongs in "Adapted for Craft" since you could start using it right now if you wanted to.  
  > **username_1**: Hmm, good point @username_2... I put it in the "Coming Soon" category because it looks like they're working on an official Craft adaptation (like Snipcart did). What you describe would fall more into the DIY category (though not via API). Thoughts?  
  > **username_2**: @username_1 They [just posted notes on integrating with Craft](https://wiki.foxycart.com/integration/craftcms), as though they sensed they were being mentioned somewhere. FoxyCart's platform is similar Snipcart just more full-featured, with very flexible checkout pages instead of modals. I don't know what "Adapted for Craft" is supposed to mean, honestly, I just imagine that Snipcart and FoxyCart should appear in the same category.  
  > **username_1**: @username_2 They are mind-readers! Perhaps they do belong in a different category. "Adapted for Craft" means that a plugin has been written which makes it easier to integrate that 3rd party service... which hasn't yet happened for FoxyCart (though may be in the works). I'm certainly open to re-organizing the list or re-naming categories, let me know what you think it should be called!  
  > **username_2**: @username_1 Oh I'm just here to complain, not offer productive suggestions. But if you *insist*, I'd consider Snipcart and FoxyCart "Drop-In Services" since they're super quick to implement and the entire cart+checkout flow is handled by a third party. As opposed to Stripe/PayPal where you'd have to make a cart, figure out shipping, etc. or Charge/Commerce/Sprout that'd run on the server with Craft.  
  > **username_1**: @username_2 I like it! I might wait a few more days to make that adjustment, just in case FoxyCart is truly about to release a plugin. I'm trying not to over-edit this post. :)  
  > **username_5**: @username_2 username_1 ooops some how I didn't see the last three comments before I edited it.  Should I unedit it?  
  > **username_2**: @username_5 I think so, yes. FoxyCart's definitely not an API-only thing, so your edit's in an entirely different direction altogether.  
  > **username_5**: @username_2 that's why the kids shouldn't play after dark.  
  > **username_1**: @username_5 Actually, I got to "review" that edit and approve it... Based on this conversation, I let it get moved into API. Sounds like FoxyCart exists outside of our classification system!  
  > **username_5**: In the Catholic Church there is this concept of "in limbo"  
  > **username_2**: Regardless of who classifies it (username_5, username_1, the Pope), FoxyCart is more like Snipcart than PayPal or Stripe.  
  > **username_1**: @username_5 Lol, it's definitely in limbo. I'm debating whether to reject your un-edit (nothing personal). Based on what username_2 suggested, FoxyCart should just go into a new category called "Drop-In Services". And based on FoxyCart's recent activity, it wouldn't surprise me if a true plugin were just days away. What are your thoughts?  
  > **username_1**: @username_2 Ah, except that a plugin has been written for Snipcart (by Snipcart)! Should that get moved to the "Built specifically for Craft" category?  
  > **username_2**: @username_1 I would still put it in "Drop-In Services" and note "(plugin available)" next to it. The plugin is a post-receive hook for modifying order quantity. FoxyCart could technically write a plugin to put their logo in the Craft dashboard and get moved to "Built specifically for Craft" by your presence-of-first-party-plugin criteria. Unless it's a plugin for comprehensive Craft integration, I don't think that criteria's all that significant.  
  > **username_1**: @username_2 The thought behind "Built specifically for Craft" was definitely for 100% native Craft integration. "Adapted for Craft" was supposed to represent 3rd party services that had plugins built to integrate with Craft... By your logic, Shopify would also be a "Drop-In Service" (plugin available).  
  > **username_2**: @username_1 Dammit you're right, and I guess I finally see how FoxyCart can be in DIY instead of adapted. I surrender for now, this entire q/a is a real challenge!  
  > **username_1**: @username_2 Ok, I've got a new plan... Cross your fingers! :)  
  > **username_5**: Sorry had to hop on a ferry for Marthas Vineyard, out of loop for a few.  I think the solution is to remove the (via an API) from the DIY and open up that category to be like purgatory, where the taste of heaven is on your lips and entirely possible, as opposed to Built Exclusively for Craft where you are in the land of milk and honey.  
  > **username_1**: Lol @username_5, that may be the greatest comment I've read all day. I've already given FoxyCart their own category of "3rd party services (no plugins)" as well as had a little [Twitter chat with them today](https://twitter.com/LindseyDiLoreto/status/480078864975011840). You make a valid point though, I'll definitely keep that suggestion in mind for a future edit (I get the feeling this list will continue to evolve). Thanks for the contributions!  
  > **username_2**: @username_1 Unfortunately I just caught up on this thread, and I don't have any complaints about the current list. But I'll be watching [with unnecessary skepticism](http://i1.ytimg.com/vi/OGAu_DeKckI/hqdefault.jpg)...  
  
  ---
  
  ### Answer by username_2 on 2014-06-19. Score: 15
  
  I just finished [my first Snipcart project](http://lighthouseroasters.com/) and I'm in the process of making a plugin for browsing orders and customers from the Craft control panel. username_1's got the landscape covered with his answer so I can at least share my experience with [Snipcart](https://snipcart.com/):
  
  ## Snipcart
  
  For those who somehow skipped other answers or haven't *looked at* Snipcart, it's a JavaScript cart service that's focused on being quick and easy to implement. You define product links with some `data` markup, include their cart JavaScript, and get a modal (guest+member) cart and checkout flow that you can style as needed. It can work with physical products, downloads, somewhat configurable products, and it comes with support for flexible promotional code options. There's a somewhat limited (but useful) control panel, integration with a handful of payment gateways, and the option of using live shipping rates from different (selectable) carriers.
  
  Snipcart is not as full-featured as something like Shopify—the reporting is fairly basic and we're hoping for gift certificate support, for example. My client asked to customize the specific shipping speeds/services offered by carriers, but at the time of this answer it's not possible; you can only toggle one *carrier* or another, not the individual services from that carrier. These limitations are the tradeoffs you get with Snipcart since it's young: it's astonishingly easy to get working right now, but if a particular feature doesn't exist there's not much you can do other than ask and wait.
  
  ## Team Snipcart
  
  Snipcart's team is small but dedicated and incredibly responsive. It's abundantly clear that they're working hard on building and refining their product. Charles responded quickly and thoughtfully to every question I had, even the annoying didn't-RTFM ones. He was willing to take feature requests, help troubleshoot when I had issues, and he's a nice guy to boot.
  
  Sometimes merely asking about *how to do something* would result in a feature magically appearing or a problem being fixed.
  
  ## Integration
  
  If you can [define your products](http://docs.snipcart.com/configuration/product-definition) in a way that works, you're basically done. There are JavaScript and REST APIs and webhook support for limited extensibility. The Snipcart folks are aware of Craft, to the point of [suggesting Craft-specific inventory management on their blog](https://snipcart.com/blog/managing-your-craft-inventory-using-snipcart-webhooks).
  
  Snipcart was easy to drop in and immediately get a working cart. (And we're using Stripe, which is always dreamy in my experience.) Overriding/customizing cart styles was painless, even though Snipcart could change the base cart markup at any time and require some adjustment.
  
  Integration with Stripe was perfectly smooth, in test mode and in live mode—not a single issue or hiccup. Snipcart was available and fast 100% of the time, and every order has been captured and charged flawlessly as you'd expect. (We had some initial configuration issues on our end that we quickly worked out, but those weren't Snipcart's fault.)
  
  We had an awkward account-juggling process since there's only one set of administrative credentials per Snipcart account. We ended up creating a new client-owned account and reconfiguring it for launch. Not a big deal, but it'd be nice to see multiple account users as an option. You can have multiple private API keys, hence the Craft plugin I'm working on for browsing orders/customers.
  
  ## Conclusion
  
  Snipcart's definitely the scrappy new kid on the block, this simple integration has gone pretty well, and I would look to use Snipcart again for the right project. For a store with more intense/complicated needs, Shopify, Commerce, or Sprout Commerce might give you more control at the expense of more development time.
  
  > **Comments:**
  > **username_3**: Any chance it's possible to hide shipping methods/services you don't want with CSS?  
  > **username_2**: @username_3 I considered that, it just made me nervous because it'd be unreliable at best. The services aren't uniquely classed or identified, so I'd have to hide the *nth* element which could change depending on the services available for a customer's geographic location. So it might be possible, I'm just reluctant to live with on such a workaround.  
  > **username_3**: I couldn't agree more. Maybe they will class them for us. I'll ask. If not, I can't use them for the project I'm about to start. Will send an email.  
  > **username_2**: Cool, thanks @username_3. Regardless I hope the project goes well and look forward to your answer here about whatever you end up using!  
  > **username_3**: From their team... "we plan to allow selecting methods from the dashboard, but adding a css class is a good/fast idea, we will try to do it soon". The CSS class does the trick for me.  
  > **username_3**: They added the CSS class to the <tr> tag. Kudos for quick!  
  
  ---
  
  ### Answer by username_4 on 2014-06-19. Score: 12
  
  I've yet to try it but [Snipcart](https://snipcart.com) seems to be on of the most viable options right now. Essentially it works though HTML/JavaScript and integrates with fields you define in your Craft setup, see their post explaining [here](https://snipcart.com/blog/integrating-snipcart-with-craft-cms-a-child-s-play-). You can even update your inventory using their webhooks, again they explain how to [here](https://snipcart.com/blog/managing-your-craft-inventory-using-snipcart-webhooks).
  
  The only others that you haven't mentioned but are in the Straight Up Craft directory are a [Shopify plugin](https://github.com/davist11/craft-shopify/) by Trevor Davis and [Charge](http://squarebit.co.uk/plugins/charge) by Joel Bradbury - I'm not sure if you have already seen these.
  
  For an upcoming site I plan to try the Snipcart method, failing that I'll fall back to implementing [Stripe.js](https://stripe.com) manually and writing a plugin to handle the inventory side of things with [Stripe webhooks](https://stripe.com/docs/webhooks).
  
  > **Comments:**
  > **username_0**: You're right, I'd forgotten about Snipcart. I had seen that blog post. I'm wary of a purely JS solution only because I'm an old school progressive enhancement type of guy.  
  > **username_0**: Shopify unfortunately isn't an option for my client in this case.  Charge looks great for simple payments, but as far as I can tell there's no concept of a cart or shopping session, right?  
  > **username_4**: Yep charge simply lets you buy individual things, not collect them in a cart.  
  > **username_4**: Another method I've been thinking over is writing my own cookie-based cart, using PayPal as the only gateway (you can just POST them a form with stuff in it) and then somehow getting back inventory data on the return from PayPal - I know all this is possible but I've not actually tried any of it!  
  
  ---
  
  ### Answer by username_5 on 2014-06-20. Score: 9
  
  Foxycart indicates they are jumping in <https://twitter.com/foxycart/status/478952251239567361>
  
  > **Comments:**
  > **username_5**: So Foxycart is turning on the lights as we inquire http://bit.ly/SXFIr2  
  > **username_2**: I think they sensed that they were being talked about somewhere.  
  > **username_5**: Indeed, but I think they were already on it, or they have an amazing ability to learn quickly!  
  
  ---
  
  