Permalink

Hitting all the e-commerce targets

8

Jane Wells, user experience lead for WordPress and Automattic employee, in response to The Morality of Forking:

And if Woo just wanted to fork something, they might have been better off forking Shopp — it has a more consistent UI, less complex code, and better reporting. Then again, Jigoshop creates fewer tables and uses custom post types. Hm, but WP e-Commerce also uses CPTs, has way better reporting, and creates fewer tables than Shopp. This is the problem — everyone is doing something better than the others, but no one is hitting all the targets yet.

8 thoughts on “Hitting all the e-commerce targets

  1. How right she is, there is no perfect WordPress eCommerce package, and when 1.0 comes out for WooCommerce I doubt it will be perfect, but it will give the competition a shakeup and say, “Hey, we need to get better”.

    • I’d go as far as saying “there’s no perfect solution, WordPress or otherwise”. There’s always something missing from the chosen solution. Self-hosted can be a nightmare if you’ve got to go in hacking the code; hosted is usually restrictive and pricey.

      Clients expect all features to be available when they ask for them. It’s hard to explain why when they’re not.

  2. No one has mentioned Cart66 in the recent e-commerce debate. I looked briefly at this a while ago and it looked pretty interesting.

    Has anyone tested it out properly, and how does it compare to the other offerings?

    • I own a copy, and have played with it a good bit, but not actually gone to production. The setback with Cart66 is that it integrates into posts and pages, and utilizes shortcodes to display products. It makes it work quite well when only a few products are involved, but not so much for sites with dozens of products, or thousands of products.

      h/t also to Patrick Daly for helping point me to this issue.

      • Thanks Brian, interesting to know.
        I would have thought the minimum requirement for a ‘serious’ e-commerce Plugin would be to utilise CPT’s. Just too much of a mess otherwise if you had a large product base.

    • I’ve used Cart66 on three separate sites. None of them are focused mainly on e-commerce however; Brian Krogsgard is right, it wouldn’t work well with a ton of products. Here’s how it does work well though:

      1. Gravity Forms integration. For gathering form data along with a purchase.
      2. Membership setups. It’s not intuitive work right out of the box, but I was able to set up a smooth-ish membership area, with recurring billing.

      The best way to set up a product site using Cart66 is to build your own CPT with custom taxonomies – along with custom meta boxes for the Cart66 code. Then build custom templates to display them. It ends up being a lot of work and you also have to manage your products in two places: in the Cart66 admin as well as your CPT product.

      I agree with Jane Wells though – Nobody’s nailed the WordPress/e-commerce thing yet.

  3. I am wondering, what is currently the best for a site with say, 10,000 items? Is it even possible to do this in WP? Thanks much, Dave

  4. WordPress is a moving target when it comes to developing an ecommerce solution for it. Cpts aren’t even a year old. The admin is constantly changing. It seems more stable now, but who knows what the future holds.

Comments are closed.