Differences

This shows you the differences between two versions of the page.

--- ecommerce:shopping_for_ecommerce_solutions [2021/10/18 20:46] – [Conclusions] mithat
+++ ecommerce:shopping_for_ecommerce_solutions [2021/10/19 21:38] – [WordPress+WooCommerce] mithat
@@ Line 15: / Line 15: @@
 A couple years ago, I set up a trial [[https://woocommerce.com/|WordPress+WooCommerce]] shop  partially to learn its in and outs for client work and partially to see if it would eventually work as a solution for my own shop. This should come as little surprise to those who know what a supporter of FOSS I am.
-What I found is that while it’s possible to build a shop with WordPress+WooCommerce, to make it useful you’ll need to add some third-party plugins, some by WooCommerce, some not, FOSS, some not. This arguably turns the open-source platform into a distributed proprietary one. Apart form the compromise in computing ecology this represents, it introduces two additional issues of concern: (1) There’s no guarantee that a third-party plugin you’re relying on will be maintained in the future, and (2) there’s no guarantee that the pricing model for a third party plugin you’re relying on won’t change. It also introduces a couple usability issues for the shop maintainer: the management of features tends to get a little spidery, and updating plugins can be chaotic if done automatically; if done manually a lot of diligence is required. Not a deal-killer, but a bit of a papercut.
+What I found is that while it’s possible to build a shop with WordPress+WooCommerce, to make it useful you’ll need to add some third-party plugins, some by WooCommerce, some not, some FOSS, some not. This arguably turns the open-source platform into a distributed proprietary one. Apart form the compromise in computing ecology this represents, it introduces two additional issues of concern: (1) There’s no guarantee that a third-party plugin you’re relying on will be maintained in the future, and (2) there’s no guarantee that the pricing model for a third party plugin you’re relying on won’t change. It also introduces a couple usability issues for the shop maintainer: the management of features tends to get a little spidery, and updating plugins can be chaotic if done automatically; if done manually a lot of diligence is required. Not a deal-killer, but a bit of a papercut.
 As far as how well WordPress+WooCommerce lines up with my three desired features:
@@ Line 21: / Line 21: @@
   * It can be very low cost to run — free in fact if you don’t count webhosting that you already have. However, running it for “free” will limit the plugins you can use.
   * WooCommerce’s own tax calculation plugin promises to do what I need, and initial testing suggests that it works. Other options exist but get very costly very quickly.
-  * The [[https://woocommerce.com/products/woocommerce-amazon-fulfillment/|plugin for Fulfillment by Amazon]] is a bit costly. We aren’t talking about Amazon’s service fees here, we’re talking about having plunk down $129 a year on top of those. It looks other fulfillment integrations may be possible. This needs some research.
+  * The [[https://woocommerce.com/products/woocommerce-amazon-fulfillment/|plugin for Fulfillment by Amazon]] is a bit costly. We aren’t talking about Amazon’s service fees here, we’re talking about having plunk down $129 a year on top of those. However, other fulfillment integrations appear to be possible. This needs some research.
+Other pros and cons include:
+  * Because it's so popular, there are a //lot// of plugins. This means if you want to add something to your store (e.g., on-demand printing of swag) you'll probably have a decent range of service providers to pick from.
 ===== Shop 0.0.2 =====