Short Answer:

Use spree, it can do exactly what you want.

Long Answer:

1)  It will take less time to customize spree than build your own shopping 
cart.  You might think your own shopping cart is easy to build and w/ 
stripe today it makes it much easier.  But, if you start thinking about 
variations of products, adjustments, promotions, and coupons... you'll 
realize there is more logic than meets the eye to a shopping cart.

2)  Spree is superior to ror ecommerce.  The blog post was written about 
spree prior version .60 and prior to spree being essentially rewritten for 
rails 3 and rails supporting engines full force in rails 3.1.  I could go 
into a rebuttle issue by issue w/ the blog post but its not worth it.  If 
you read in the comments below I think there was enough discussion on that 
post in 2010 to cover those issues.

3)  Customizing spree is surprisingly easy.  Just look at a few examples of 
using deface to change things and you'll be up and running pretty 
quickly.  Spree has some amazing extensions and support that you will 
probably find an addition to spree via an extension someone else wrote 
rather than doing it yourself.

4)  Take a look at spreeworks.com and shopify.com if the volume of orders 
and customization is low these solutions might be a better fit.

What is my experience with spree?  I was a cofounder of www.stickermule.com and 
we really pushed the boundaries on using spree and couldn't be happier w/ 
the choice we made.

Drew

On Sunday, August 12, 2012 10:03:21 PM UTC-7, Scott Olmsted wrote:
>
> Anyone used Spree or ror_ecommerce for an e-commerce site? My client wants 
> to sell biological samples by credit card or purchase order, post a few 
> pdfs and other files on the page for each product, and perhaps export a 
> file to Quickbooks, including taxable status. Will customizing Spree take 
> longer than creating from scratch? What about using ror_ecommerce? Any 
> validity to the author's claims and criticisms of Spree? (
> http://ror-e.com/posts/1)
>
> Thanks, Scott
>

-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby

Reply via email to