• New – If enabled in settings and using the ‘WooCommerce style’ registration option, the username field will now appear for registering users. This field will not be displayed for most configurations.
• New – Add support for Coderockz Woo Delivery
• Improved – Refactored Klarna Payments integration to use available gateways filter instead of the weird templating tactic they use.
• Fix – Fix styling of Amazon Pay banner on order pay page
• Fix – Fix potential PHP warning/error with enabled fields setting not returning an array
• Fix – Fix bug with Chrome Autocomplete service making fields readonly on the PayPal for WooCommerce review order screen
• Fix – Fix potential issue where — (dash dash) was selected as country when no location was set or found.
• Fix – Fix bugs caused by our attempts to prevent select2 from loading. We can’t really go after select2 so aggressively because Local Pickup Plus and other plugins need it or they throw errors / don’t work properly
• Fix – Fix broken action that prevented woocommerce_checkout_before_customer_details and woocommerce_checkout_after_customer_details actions from firing. This allows ThemeHigh Checkout Field Editor’s conditional fields to work properly.
• Fix – Preserve alerts when going to payment tab on error (order review step)
• Dev – Differentiate validation promise logs so that we know if a promise failed during tab validation or order submission

The post CheckoutWC 7.4.0 Released appeared first on CheckoutWC.

The Problem With Local Pickup

Local Pickup is a feature we have wanted to tackle for a long time. Local Pickup has a fundamental problem in WooCommerce: it’s implemented as shipping method

This leads to bad user experiences.

For example, with CheckoutWC customers had to enter their shipping address to even see the Local Pickup option.

Introducing Local Pickup in CheckoutWC

7.3.0 brings a fully functional Local Pickup solution.

Customers have the option to choose how they want to receive their purchase. If they select ‘Pick up’ the shipping address and shipping step is hidden. All verbiage on the page updates to pickup verbiage.

Easy Setup

Setting up Local Pickup only takes a few minutes. Pick which shipping method is your local pickup option, decide whether to show the shipping step, and add some pickup locations. More about setup here.

Advanced Features

Are you using an advanced API for your local pickup shipping methods?

You can specify the name of your local pickup methods using RegEx. 

What else is new in CheckoutWC 7.3.0?

We’ve added a lot of new functionality, bug fixes, and developer quality of life improvements to 7.3.0.

CheckoutWC 7.3.0 Change Log

• NEW – Local Pickup. CheckoutWC now has a native understanding of pickup vs delivery and can selectively show / hide the shipping address and shipping options based on whether the customer selects shipping or pickup.
• NEW – You can now select which countries to highlight in country dropdown from settings (WP Admin > CheckoutWC > Checkout > Field Options)
• NEW – You can now selectively hide/disable billing address fields from settings. (WP Admin > CheckoutWC > Checkout > Address Options)
• NEW – Added option to disable \’Same as shipping address\’ option in settings. (WP Admin > CheckoutWC > Checkout > Address Options)
• Improved – Remove cart item link is now always shown at mobile screen sizes
• Improved – Updated Greek translations based on feedback from customers.
• Dev – Updated WC tested version to 6.6.0
• Dev – Added two new actions: cfw_before_payment_methods_block and cfw_after_payment_methods_block
• Dev – Added new cfw_order_updates_heading filter and new cfw_after_thank_you_order_updates_text action
• Dev – Extra billing fields are now output on an action hook like everything else.
• Dev – Implemented updated_cart_totals JS event from WooCommerce core.
• Dev – Added new action after side cart totals: cfw_after_side_cart_totals
• Dev – Moved before_woocommerce_pay call so that it fires within the template content
• Dev – Added cfw_side_cart_free_shipping_progress_bar_free_shipping_message and cfw_side_cart_free_shipping_progress_bar_amount_remaining_message_format filters
• Fix – Fix potential JS errors from undefined variables
• Fix – Fix issue with PayPal for WooCommerce and customer info sections appearing that should be hidden
• Fix – Fix bug that prevented overriding CheckoutWC image sizes
• Fix – Fix issues with PostNL and MyParcel
• Fix – Fix issue where colon appearing in shipping method name was errantly removed.
• Fix – Improved accessibility of side cart.
• Fix – Fix issue with FlyCart Woo Discount Rules and side cart.
• Fix – Fix issue that caused the review panes to show incorrect information when billing address is forced to be the shipping address.
• Fix – Fix bug that made it possible for post code validation error to be shown when correct post code was entered.
• Fix – Fix potential typing issues that could cause fatal errors in recent versions of PHP.
• Fix – Fix issue where Select2 could be loaded.
• Fix – Fix issue with caching and add to cart error messages. Now acts more like native AJAX add to cart functionality in WooCommerce core.
• Fix – Fix incorrect usage warning 
• Fix – Fix multiple issues with Amazon Pay 2.0 legacy API and order pay endpoint
• Fix – Fixes to how Malaysian addresses are handled with Google Address Autocomplete
• Fix – Google Address Autocomplete now supports named buildings in addition to normal street addresses
• Fix – Fix conflict with Woostify CSS and side cart table styling.
• Fix – Fix issues with Variation Swatches for WooCommerce and the side cart
• Fix – Fix potential issue with some finicky gateways by adding a slight delay to firing payment_method_selected event so that it runs after animations have completed.
• Fix – Fix bug that prevented woocommerce_before_thankyou from running
• Fix – Fix bug that prevented side cart free shipping progress data from being filtered.
• Fix – Fix bug with option to hide the floating side cart button when the cart is empty and situations where the cart transitions to a non-empty state. Now behaves correctly when emptying the cart and adding an item.
• Fix – Refactored cart updating code to fix bug with WooCommerce Product Bundles quantity syncing
• Fix – Prevent fatal errors when order bump cannot be added to the cart

The post CheckoutWC 7.3.0 Released appeared first on CheckoutWC.

• New – Password fields now have toggle button to show password in plain text so that customers can verify they have entered the correct input.
• New – Smart Variation Matching for Order Bumps. When setting up an order bump you can now set the search and offer products to be a variable product. Smart Matching attempts to match the offer product variation attributes to the search product variation attributes in the cart. Example: If you sell mattresses you could set it up so that a person who chooses a queen mattress and then adds a mattress protector as an order bump would also get the queen size protector.
• New – Added option to order bumps to set whether or not the order bump quantity can be adjusted in the cart.
• Improved – Improved how bundled products are displayed when using WooCommerce Product Bundles.
• Improved – If it is not possible to change the quantity of a cart item, show the cart item quantity bubble on that line item. 
• Improved – Order Notes are now excluded from field persistence caching (Garlic.js).
• Dev – Added cfw_enable_field_persistence filter to make it easy to turn off field persistence.
• Dev – Added cfw_welcome_back_text filter for welcome back text.
• Fix – Fix bug that caused shipping phone to not be saved with submitted order.
• Fix – Fix issue where address review didn’t have all of the correct info when using WooCommerce for Japan.
• Fix – Fix bug where address formatting strings that weren’t replaced would appear in review address area of checkout steps.
• Fix – Fix bug that caused multiple events to be bound where one was required during field validation.
• Fix – Fix bug that caused the state field to not be validated.
• Fix – Fix lack of sale price when using YITH by implementing proper filter
• Fix – Handle sale prices differently so that it works with YITH Dynamic Pricing.
• Fix – Fix issue with zooming into text fields on mobile safari
• Fix – Fix characters not being totally covered by shimmer.
• Fix – Fix side cart totals spacing
• Fix – Detect coupons with free shipping and render shipping progress bar correctly.
• Fix – Add some more styling to help the side cart display correctly with themes that like to add borders to tables.
• Fix – Fix potential fatal error with PHP 8.
• Fix – Fix incorrect city when using Google Address Autocomplete with Swedish addresses.

The post CheckoutWC 7.2.0 Released appeared first on CheckoutWC.

• New – Added new Cart Summary Link color setting
• New – Added setting to display sale prices in cart and checkout cart summary.
• New – It is now possible to use a WooCommerce Product Bundle that contains variations as an order bump. The default variation values for each bundled product are used. 
• Improved – Improved how product bundles are styled in the side cart and checkout cart summary
• Fix – Fix setting that appeared erroneously when side cart is disabled.
• Fix – Change label of cart item quantity color settings to add clarity to what they style.
• Fix – Fix issue where quantity stepper wasn’t available in side cart unless cart editing at checkout was enabled.
• Fix – Fix issue where there were duplicate validators during checkout submission
• Fix – Attempt to fix race condition that caused the postal code validation to show an error message after correct postal code was entered
• Fix – Fix bug in admin where publishing an order bump triggered before unload alert
• Fix – Tweak our side cart coupon apply code to better match core

The post CheckoutWC 7.1.8 Released appeared first on CheckoutWC.

Here are the release notes:

• New – Added new option to place Trust Badges in the footer. Trust Badges now have a main level admin menu.
• Improved – The official Stripe gateway undeprecated an important filter that allows us to turn on payment request/express buttons on the checkout page. So we re-implemented it.
• Improved – The whole row is now clickable to select a payment method. Particularly helpful on the Glass theme due to the larger styling of items.
• Dev – Removed cfw_disable_admin_menus filter in favor of better methods.  Try: remove_menu_page( ‘cfw-settings’ )
• Dev – Added new action: cfw_order_item_after_data
• Fix – Fix issue where Full Name, House Number, and Street Name fields caused issues with express checkout (Apple Pay, Google Pay, etc)
• Fix – Corrected some Danish translations. Thanks, Julie!
• Fix – Fix how we style the footer on the Glass theme. No longer uses absolute positioning which I think we can all agree is better.
• Fix – Fix bug that caused countries that are excluded in WooCommerce settings to show up in international phone field dropdown.
• Fix – Revert changes to Netherlands zip autocomplete in favor of disabling zip autocomplete entirely for the Netherlands and Belgium due to our data source not having good city data.
• Fix – Fix edge case where if a shipping address field value was ‘null’ the billing address sync would still run.
• Tweak – Removed colon after shipping method names
• Tweak – Renamed pot file to checkout-wc.pot since this seems to be more standards complaint.

The post CheckoutWC 7.1.3 Released appeared first on CheckoutWC.

Here’s the release notes:

• New – You can now elect to display trust badges below the checkout form in a horizontal row.
• New – Added loading animation on continue buttons at the bottom of each step that runs while asynchronous field validation is running.
• Improved – Use native form-row class as parent styling class instead of cfw-input-wrap. Makes it easier to style fields without fulling controlling every aspect of the field output.
• Improved – Added list of common email address domains that short circuit domain check resulting in faster validation.
• Improved – Fields that are not visible on the active tab are no longer validated. Also added a lot more logging when using cfw-debug=true URL parameter to identify which field is causing validation failures.
• Fix – Fix bug that caused the footer text color option to not work.
• Fix – Fix bug that caused Order Bumps admin menu to show for non-admins.
• Fix – Fix bug that caused the Show Credit Card Logos on Mobile option to not work on the Order Pay page.
• Fix – Fix multiple bugs that prevented order submission when using PayPal for WooCommerce and our full name field as well as our discreet address 1 fields.
• Fix – Billing address sync was trying to sync non-address shipping fields such as shipping methods.
• Fix – Fix issue with autocompleting city from zip for Dutch addresses.
• Fix – Fix issue with (optional) not being translated in field placeholders and on Add Address Line 2 type links.
• Fix – Fix validation errors with Iconic Delivery Slots when their UI was not visible
• Fix – Fix bug where HTML was added to field placeholders from label
• Fix – Styling improvements for Order Delivery Date Pro
• Fix – Fix edge case bug where missing trust badges data caused a fatal error.

The post CheckoutWC 7.1.0 Released appeared first on CheckoutWC.

CheckoutWC 7.0 is a pivotal version for us. With the refactors in this release, we moved the project into a better trajectory – one in which we hope to do fewer substantial refactors and focus more on long term stability.

Now let’s dig into the release notes!

Better Optional Address Fields

Sometimes the most exciting things are the little things. Optional address fields will now be hidden behind a link by default. Research indicates that users are often confused by fields such as Address Line 2, which are infrequently filled out and often filled out incorrectly.

By hiding these fields behind a link such as “Add Address Line 2 (optional)” or “Add Company (optional)”, we can reduce customer confusion and improve our conversion rates.

A New Full Name Field

Another area of usability we are addressing is the number of form inputs which can be especially costly to fill out on mobile.

Namely we are providing a new optional feature to combine the first and last name fields as a single Full Name field.

We parse the full name into the respective first and last name fields so everything else will work the same. And our parsing library understands a large variety of names. 

Example 1:

Entered Full Name: Dr. David Livingston Jr.

First Name: David

Last Name: Livingston

Example 2:

Entered Full Name: Olivia de Havilland

First Name: Olivia

Last Name: de Havilland

We are excited to hear from customers like you on whether this boosts your conversion rates.

Field Rendering Jujumagumbo

7.0 also includes a big directional change regarding how we render fields. Since our first version, we used a separate function to render input field markup: cfw_form_field()

In 7.0, we are reversing course. We are using the raw input markup from woocommerce_form_field() and making minor adjustments to it. This should cleanup a lot of lingering edge cases where plugins expect fields to be rendered a certain way and then they are not rendered that way.

This should be completely invisible to the user.

Inline Postcode Validation

We have heard your feedback! The way we validate the shipping and billing post codes is not working.

Consequently, we’ve redesigned the whole process. This is how post code validation will work in 7.0:

Inline Email Domain Validation

How many times do you get an order where the customer entered the wrong email address, leaving you unable to reach out to them and leaving them frustrated, wondering where their receipt and updates are?

In 7.0 we’re going to help fix this by validating email addresses in real time. What we do is take the domain name from the email address and make a DNS request for the MX records associated with that domain. If no records come back, we display an error to the customer. It looks like this:

A New Login Flow

We are going back to the drawing board with logins. 

As CheckoutWC has become more complex, we have started to question the usability of our login system. The way it works now is that if a user either enters a known email address that matches an account OR they click on ‘Login’, a Password field and Login button was revealed underneath the email address field. 

This process worked pretty well, but it had some quirks. For example, when the login button was revealed, the email field functionally became a username OR email field. But it was still validated as an email field. This was confusing for some users.

On top of this, there were logistical issues with the other functionality that was co-located in that area of the form, such as creating an account and when to show a password field for that purpose.

The New Login Modal

Beneath the hood, there is more going on here. 

1. We’re still checking for existing accounts. If a user enters a known email address, we will open the login modal with their email address pre-filled. And we change the language: It looks like you already have an account. Please enter your login details below.
2. Clicking “Lost your password?” seamlessly opens the Lost Password modal.
3. We only prompt the user to login (by opening the modal automatically) once per 7 days.

New Admin Settings Design

Ok, I’m definitely biased but don’t these new admin screens look sexy?

But it’s more than just a new look. We took care to categorize settings into useful groups that pair similar types of settings together

It’s also clearer when a setting is dependent on another setting.

We have more to do here but we’re really happy with how it turned out.

House Number and Street Name

We’ve been asked a lot about how to better handle addresses in certain European countries. The pain point is that WooCommerce doesn’t offer discrete fields for Street Name and House Number.

This is problematic for certain jurisdictions where culturally people think of Address Line 1 as two components, and when they see ‘Street Address’ they instinctively write their street name, resulting in an incomplete address and sometimes a failed shipment.

We’ve solved that by allowing merchants to enable discreet Street Name and House Number fields. In additional to enabling the fields, you can also choose the order in which they appear.

On submit, we stitch them back together into one Address Line 1, following the country based formatting rules we apply for Google Address Autocomplete.  

New Free Features

7.0 also makes some common features free for everyone:

• User Matching
• Order Review Step
• One Page Checkout
• Php Snippets

Now that we have thoroughly vetted these features and no they don’t increase our support load, we’re comfortable making them available to all license holders.

New Order Bump Feature

In 7.0.9 we added a quick new feature: You can now choose what happens when an Order Bump becomes invalid.

Example, say someone adds a T-Shirt to the cart and they get offered a second T-Shirt at 50% off. They accept the offer and then they decide to remove the original T-Shirt from the cart.

Previously the second T-Shirt would revert to the normal price and they would no longer get the discount. However now you can configure this on each Order Bump. You can elect to remove the Order Bump from the cart if it no longer meets the conditions required to show it.

This is helpful for stores that offer unpublished products as Order Bumps and don’t want people to be able to purchase them at any price without the requisite conditions being met.

That’s It For Now

We have more coming in 2022. If you would like to be notified about updates, subscribe to our e-mail list by signing up in the box below.

The post CheckoutWC 7.0 Released appeared first on CheckoutWC.

We have a lot of stuff in the works, but today we’re releasing a tasty patch release that fixes some bugs and generally makes CheckoutWC better for everyone.

Here are the details:

• New – Add support for YITH Points and Rewards 3.x
• Improved – Automatically exclude our JS files from WP Rocket transformations that break things.
• Improved – Added action before upsells are added to the cart: cfw_before_order_bump_add_to_cart
• Improved – When rendering a remove item link, we now pass it through the WooCommerce filter so that it picks up changes from other code.
• Improved – Refactored Google Address Autocomplete service. It’s cleaner! It’s faster! (maybe) And it’s much easier to handle country by country edge cases.
• Fix – Fix multiple bugs with Checkout Field Editor (official WooCommerce extension)
• Fix – Clean up jQuery migrate warnings.
• Fix – Fixes for PayPal for WooCommerce Complete Payments gateway.
• Fix – Fix bug where error messages were not properly displayed if the error was not output in the form tag.
• Fix – Fix bugs with Thrive theme.
• Fix – Aborted AJAX calls are no longer logged as errors.
• Fix – Eliminated deprecated function call.
• Fix – Fix bug with Metro theme.
• Fix – Fixed bug where upsells were not discounted properly after being added to the cart.
• Fix – Fix bug where the city field was not validated if it was rendered off screen.

The post CheckoutWC 6.2.3 Released appeared first on CheckoutWC.

CheckoutWC 5.0 is here and it’s our biggest release since version 1.0. In addition to adding a lot of highly requested features from our backlog, we took the time to fix some technical debt. CheckoutWC 5.0 is leaner, faster, and more extensible than ever.

Order Bumps and Upsells

We’ve finally added native support for Order Bumps and Upsells.

Order Bumps are designed to increase your Average Order Value (AOV). This is done by offering your customers special discounts that are only available when making a purchase. Here’s what it looks like:

Order Bumps can also be used as Upsells. When an Order Bump is configured as an Upsell, it will replace a specific product in the cart.

Trust Badges

In 5.0 we made it easy to add Trust Badges from Settings. Here’s an example of what you can setup, right from the admin dashboard:

SmartyStreets Address Validation

Do your customers struggle to enter their addresses correctly leading to incorrect orders and lost revenue?

Our SmartyStreets Address Validation feature helps catch incorrect addresses before orders are submitted. Here’s what it looks like in action:

Re-designed Admin Settings Pages

We went back to the drawing board with 5.0 and re-designed our admin settings pages from scratch. Our new pages are better organized and more aesthetically pleasing:

Up Next

We are really proud of how 5.0 came together.

We have a lot of new features in the hopper for 2021 including a cart page replacement.

Have a question? Drop a comment below or use the Help widget at the bottom right to reach out to Customer Support!

The post CheckoutWC 5.0 Released appeared first on CheckoutWC.