Shopify integrates directly with Facebook, Tumblr, Twitter and Pinterest with Buy It now buttons. It would be amazing to have these integrations for Woocommerce:
For selling directly on Facebook: https://www.shopify.com/facebook
For selling directly on Tumblr: https://www.shopify.com/buy-button/tumblr
For selling directly on Twitter: https://www.shopify.com/twitter
For selling directly on Pinterest: https://www.shopify.com/pinterest11 votes
The Xero plugin for Woo Commerce is great, but importing old sales is a slow and very time consuming process at the moment. It would be so useful to be able to import the sales in bulk as you can with the other systems I have integrated with Xero11 votes
Would be nice if WC fully supports qTranslate.
As of today qTranslate works fine with the products, but there is small bug when you try to add short description for the product. It does not allow you to make changes...11 votes
Have the ability to import all product data from Shopp (and the other WP e-comm systems).11 votes
After a lot of research, I have arrived to the conclusion that the best social plugins fro Wordpress are the ones provided by Addthis.
Would be nice to make this plugins fully compatible with Woocommerce.
They offer a social signin, works perfect in admin login page, but not with woocommerce.
Also, would be nice to use Addthis instead of ShareThis (product share).
Notice that this service provides analytics.
Thank you!!11 votes
Would love to see these two powerful applications merge...10 votes
The WooThemes API plugin to push invoices and customer data into XERO works well BUT it pushes invoices in as AUTHORISED immediately. From the perspective of testing and potentially for ongoing use, it would be good to have an option to choose DRAFT as the type in XERO. This would be much easier for testing and to allow site owners to ensure it's working properly before sending invoices in as AUTHORISED.10 votes
A two way sync on this would be like Christmas for us!10 votes
I noticed recently with the new update that the Publicize feature from Jetpack now shows up on the product editing page on all products, which is fantastic. However, it doesn't work when products are duplicated. We love the duplicate product feature and use it often as many of our products are similar to one another. But like with posts, Publicize will no longer work on duplicated products because it stores the fact that it's been published in the post_meta. When I duplicate a product, it's obviously duplicated the post_meta information as well, and therefore will no longer allow me to use Publicize.
I contact Jetpack about this issue and here is the full response they gave verbatim:
"When Jetpack Publicizes a post, it stores that fact in the post's post_meta. If the duplication copies over everything in ht epost_meta (which is likely does), then yes, Publicize will think that it has been Publicized already, and won't be available for that post unfortunately.
Please contct Woocommerce about this, and ask them to look into excluding the "_wpas_done_all" post_meta when cloning a post or product, then you should be able to Publicize it. Tell them to contact us if they need more details!"
We've had a huge increase in traffic since we began Publicizing our products as well as posts. It would be awesome if we could include this on duplicated products as well, as duplicating a product instead of creating a new one streamlines the process and saves a ton of time.
I noticed recently with the new update that the Publicize feature from Jetpack now shows up on the product editing page on all products, which is fantastic. However, it doesn't work when products are duplicated. We love the duplicate product feature and use it often as many of our products are similar to one another. But like with posts, Publicize will no longer work on duplicated products because it stores the fact that it's been published in the post_meta. When I duplicate a product, it's obviously duplicated the post_meta information as well, and therefore will no longer allow me to…9 votes
The WooCommerce extension for S3 is great but does not allow for Cloudfront integration. I would love to see Cloudfront supported with this plugin as this will allow me to offer streaming products as well as faster downloads for my digital products.9 votes
Other 3rd partys have managed this. Why cant this be a feature direct from you?9 votes
We use WooCommerce's Bookings plugin to book vacation rentals, but we also have it listed on VRBO. It would be amazing if the bookings calendar could sync automatically with VRBO so they talk to each other and we don't have to manually block out dates every times someone books a date.9 votes
I have an eCommerce website based on WooCommerce and I want to integrate the EDI for the below purpose:
-Accept orders via EDI
-Give order and shipment status via EDI
-Handle payment transactions via EDI
Can you please let me know if any Free OR Paid plugin available for this.
Prem Tiwari9 votes
Hi, I would like an extension exactly like Amazon S3 Storage, but works with Google Drive instead of Amazon S3 Storage, or better yet, lets the Wordpress site admin to choose what storage (Google Drive, Amazon Storage, Drop Box, etc.) they want to use.9 votes
This is required if you want to expand your customer base to mid to large enterprises and organizations.9 votes
Current billing system uses MaxMind Telephone verification which forces customers to verify phone before the purchase is moved from pending to active. Has worked wonders to prevent fraud.9 votes
When an invoice is exported to Xero from Woocommerce each invoice item line only shows the Product Title. Information about Product variations is not exported.
For example what I see now is ...
Product A $50
Product A $100
I would rather see...
Product A, Small Size $50
Product A, Large Size $1009 votes
What I am running into is not being able to sign clients who use IQ Retail system. A plugin that could integrate with with their system and the WooCommerce platform would make signing South Africa clients a breeze..
Would love to get some feedback on this...
Currently when a webhook fails it does so silently and then disables itself, so even if the problem is transient you no longer get any requests sent through on that webhook until it is re-enabled.
A failed request should be retried before it eventually fails and then only that request should be marked as failed, not the webhook itself.7 votes
- Don't see your idea?