Since our last minor release in May, we’ve been working on a variety of improvements to WooCommerce:
- REST API v3
- Improved copy for transactional emails
To ensure this update is stable, we’ve been doing plenty of testing and QA on our side including a public beta period, unit and integration testing, compatibility testing with our extensions and popular premium themes, running the latest version on Woo.com, and working with customers to do managed updates.
WooCommerce 3.5 is a minor release, meaning it should be fully backwards compatible with all WooCommerce releases since 3.0. However, it’s still considered best practice, and recommended, to backup before updating.
Here are some more details about what’s new in 3.5:
REST API v3
The latest version of the WooCommerce REST API is ready, and it features new endpoints as well as improvements to existing endpoints. Some of the features include:
- A reviews endpoint to list, get, create, and update product reviews.
- Date fields are now editable on the products endpoint, and the endpoint has been updated to work with the “on backorder” stock status introduced in WC 3.3.
- A series of new reports endpoints to get total counts of orders, products, customers, coupons and reviews.
- New orderby options for the products endpoint to allow listing products by price, popularity, or rating.
- Automatic total calculations when applying/removing coupons in the orders endpoint.
- New data endpoints to fetch Continents, Countries and Currencies.
- Refund line items through the API.
- Ability to batch update settings.
You can look through the full documentation for the API v3 here, and see details for all of the endpoints and their query parameters.
Note: API v2 and other legacy APIs are still included in WooCommerce 3.5 for backwards compatibility.
Improved copy for transactional emails
The wording of the WooCommerce transactional emails has remained largely unchanged for years. We have improved the default wording of the emails to be friendlier and more human. Improving the default content will improve the customer experience and reduce the need for store owners to do template overrides of the transactional emails.
This is the first phase of a larger initiative to improve WooCommerce’s emails and email content editing experience. Stay tuned in 2019 for more improvements.
But wait, there’s more!
- You can now export products by category in the CSV exporter.
- You can now set a low-stock threshold for individual products.
- The payment method settings page has been slightly redesigned for improved accessibility.
Features for developers
- The Action Scheduler library used by the WooCommerce Subscriptions plugin and other WooCommerce plugins is now included in WooCommerce core. It provides a robust, scalable background processing solution for developers. In 3.5 webhooks are delivered using this library.
- Support for the Custom Product Tables feature plugin. We’re working on custom database tables to store product data and improve the performance and scalability of WooCommerce. This release adds the hooks and filters required by the feature plugin. Read more about this here.
- Support for the wc-admin feature plugin. We’re working on a modernization of the WooCommerce admin experience. This release adds the API required by the feature plugin. Read more about this here.
- Many new filters and actions to increase the customizability of WooCommerce.
For a more complete list of new features, enhancements, tweaks, and fixes, see the changelog.
You should also read the development blog to see what templates and functions have changed in WooCommerce 3.5.
Ready to update?
We’re here if you need us:
- Think you’ve found a bug with WooCommerce 3.5 or a conflict with another plugin? Report it via our GitHub issue tracker.
- Need help with the upgrade? Visit our Support page.
- Want to chat about the release, or have a great idea for the next version? Start a discussion on the public WooCommerce forums at WordPress.org.
Please note that we are not able to diagnose or solve potential issues via blog comments. The fastest way to get in touch with us is one of the methods listed above.
If you’re craving more technical details about this update, you can read our post on the developer blog.
What do you think of our latest release? Let us know in the comments!