If you’re a merchant selling goods to customers in Colorado, SB 21-260 establishes a retail delivery fee that merchants are required to collect and remit to the state of Colorado. If you wish to continue to sell to customers in Colorado, you will need a solution to collect this fee. Until a proper solution exists, this code snippet will serve as a band-aid solution.

Not sure what to do with code snippets? See What Do I Do With These Code Snippets?

The post WooCommerce & Colorado Retail Delivery Fee appeared first on WooCommerce, Remote Work & Other Fancy Stuff.

WooCommerce Payments express checkout modal injects WooCommerce branding into the checkout experience of your shop. If you would like to remove that, this can be achieved via a filter named wcpay_payment_request_total_label_suffix and an example of that can be seen below:

Not sure what to do with code snippets? See What Do I Do With These Code Snippets?

The post Remove “via WooCommerce” From Express Checkout appeared first on WooCommerce, Remote Work & Other Fancy Stuff.

If you’re using WooCommerce Bookings and you are trying to add a cost adjustment to one particular person type based on dates, you will find that this is not possible as the only cost adjustments available via the product configuration options will apply to the bookable block as opposed to the person’s booking cost.

If your pricing model requires this type of granular adjustment, this can be achieved via some custom code. Bookings provides a filter named woocommerce_product_booking_person_type_get_block_cost which could be used in conjunction with posted data to dynamically adjust the person type block cost. You will need to glean the ID of the person type that you are trying to target. That is listed in the person type panel, e.g.:

With that, if you were trying to adjust the block cost for that person type by $10 during the month of July & August, something like this code snippet would do the trick:

Not sure what to do with code snippets? See What Do I Do With These Code Snippets?

The post Date Based Person Cost Adjustment appeared first on WooCommerce, Remote Work & Other Fancy Stuff.

It’s possible to conditionally remove shipping methods on the checkout page and there are several examples of how this can be done with code. Some of these examples can be seen here: https://docs.woocommerce.com/document/hide-other-shipping-methods-when-free-shipping-is-available/

However, what if we want to hide those shipping methods only if the purchase is done via a WooCommerce Stripe provided payment request button, Google Pay, Apple Pay, et. al.?

The WooCommerce Stripe payment gateway fires an AJAX action when it retrieves the available shipping methods. One can hook into this same action and on a callback to that, hook into an appropriate WooCommerce filter hook. The examples linked seem to favor filtering woocommerce_package_rates which is fine, but I’m lazy and that’s too much work. For my purposes, the woocommerce_shipping_methods filter is much more efficient.

Suppose I wanted to remove Free Shipping as an available shipping method if a customer is using the payment request button to pay. In code, that might look similar to:

Not sure what to do with code snippets? See What Do I Do With These Code Snippets?

The post Hide Shipping Methods – Payment Request appeared first on WooCommerce, Remote Work & Other Fancy Stuff.

WooCommerce Subscriptions provides a couple of coupon types that are specific to subscription type products. These are documented here Subscription Coupons – however, it is often desirable to be able to offer a promotional code that would apply a discount to both a sign-up fee and a recurring discount. The use case would be for listing specials on coupon code sites or specials on groupon, etc. Unfortunately, there is currently no way to combine two different types of discounts into one coupon. At least not out-of-the-box.

WooCommerce Subscriptions hooks into the WooCommerce provided woocommerce_coupon_get_discount_amount filter to do its magic. One can hook into that same filter but on a lower priority to also apply a different discount type.

Consider a scenario similar to:

1. A synced subscription so no payment would be collected at sign-up without a sign-up fee.
2. Offer a discount on both the sign-up fee that is used to cover the first installment of the subscription product and for some number of renewals in the future with one coupon code.

Given a coupon code of recurringandsignupdiscount which may be configured similarly to:

The woocommerce_coupon_get_discount_amount filter can be implemented similar to:

To achieve the desired effect of one coupon being used for two discount types.

Not sure what to do with code snippets? See What Do I Do With These Code Snippets?

The post One Coupon Code – Two Discounts appeared first on WooCommerce, Remote Work & Other Fancy Stuff.

A recent change in WooCommerce has resulted in some cases where customers may be unable to check out if their cart contains a subscription product. This happens if the “Allow customers to create an account during checkout” option is disabled in combination with WooCommerce Subscriptions requiring an account at checkout. Effectively, customers are locked out of the checkout page unless they log in. This also has an unfortunate side-effect of allowing folks who merchants would rather not have an account the opportunity to create that account.

The implementation of the WooCommerce provided filter named woocommerce_checkout_registration_enabled provides a way to take the behavior back to what may have been experienced with the earlier version of WooCommerce. See below:

Not sure what to do with code snippets? See What Do I Do With These Code Snippets?

The post Conditionally Allow Customer Registration appeared first on WooCommerce, Remote Work & Other Fancy Stuff.

If your WooCommerce site is having problems at checkout, but you’re not really sure what is behind it (i.e. steps to reproduce have not been identified) logging XHR requests (and JavaScript errors) from the checkout page can provide some insight into what is happening.

This technique would require that you had a listener setup somewhere to receive the data and process it. That is outside the scope of this article.

Injecting something like the following JavaScript perhaps using the conditional is_checkout would do the trick

The post Logging XHR Requests appeared first on WooCommerce, Remote Work & Other Fancy Stuff.

If we visit the wayback machine and look at the changelog for WooCommerce Bookings we can see that in November of 2015 a new coupon type was added to discount bookable persons. There is no equivalent coupon to discount by some number of blocks.

Fortunately, the WooCommerce Coupon class provides a filter that can be used to return a discount amount that is calculated dynamically based on the block cost of the bookable product.

The filter passes 6 parameters, the discount amount which is the value to be filtered and the amount that is being discounted, the cart item, a boolean to indicate whether or not this should apply to only one quantity or the entire line regardless of quantity, and an object representation of the coupon. We’ll need to use all of those in a callback function in order to be able to retrieve the coupon code.

The get_code method of the coupon class can be used to retrieve the coupon code of the current coupon. This can be used to conditionally target a specific coupon.

The cart item array contains an object representation of the bookable product with an array key of ‘data’. This object can be used to call the methods against the bookable product and get the block cost for this particular product.

Once all of that is put together, a new discount amount can be calculated based on the block cost and some arithmetic and assigned to the same variable name that the callback will return. All of that might look like this:

Not sure what to do with code snippets? See What Do I Do With These Code Snippets?

The post WooCommerce Bookings Block Number Discount appeared first on WooCommerce, Remote Work & Other Fancy Stuff.

Jetpack SSO provides many benefits for ease of use of the site as well as security. By default, the ‘Log in with WordPress.com’ button is only output on wp-admin. WooCommerce does not output that button on the my account login form. However, WooCommerce does provide an action hook (or two) that could be used to output the Jetpack SSO button. Here’s an example of how that might be done

The post Jetpack SSO & WooCommerce appeared first on WooCommerce, Remote Work & Other Fancy Stuff.

I’ve become interested in expanding my music appreciation lately and as a result, I’m listening to a lot of things that I haven’t had any exposure to previously. A great deal of my music listening happens while I’m working and that work can often require very intense focus. Task switching is a productivity killer. Moving completely out of the context of my workspace to “like” a song just isn’t going to happen. But if I don’t, it may be gone forever.

I wanted a way to quickly mark a groovy track for later exploration and more listening. I wasn’t able to find any out-of-the-box solution that met my needs. I should have stopped there.

I decided to try to hack something together. Spotify has a quite nice web API. The Spotify Web API equivalent of ‘liking’ a song is called Save Tracks for Current User. I also found a node wrapper for the Spotify API and so at first glance, it looked easy enough to just generate my access token on the Spotify developer ‘try it out’ page and hard code that into a few lines of JavaScript and be done with it. And that worked! For awhile

So it turns out, the access token is only valid for an hour. The access token can be refreshed so long as it is still valid. Refreshing the token requires that a refresh token is issued in addition to an access token. I definitely should have stopped there.

The access token needs to be refreshed before it expires and if I can’t be bothered to switch to an app to press a button, I certainly can’t be bothered to run a series of commands every 45 minutes or so, 24 hours a day.

The solution I finally cobbled together is a two part solution edit: I changed this up a bit. see comments. Part one is tasked with keeping the access token fresh:

1. Some JavaScript resides on a server somewhere. It’s on a cron schedule to run every 30 minutes.
2. That script refreshes the access token and writes the new access token to a file.
3. It also reads that same file for its own access token. The code looks something like this:

Part two does the actual job of ‘liking’ a song.

1. Takes some input in the form of a spotify song URI, e.g.: spotify:track:4675yUu8AUbE72T94BkLCD
2. strips the spotify:track: bit off of that
3. Uses scp (via node scp) to fetch token.txt from the remote server and writes that locally.
4. Reads the token file and sets that to the access token.
5. Does this: to a song.

That bit looks like this:

Just a side note, the Spotify track URI is fetched via shpotify.

And here’s how it all works

And, of course I have a voice command so now, all I need to do is say “heart song” and the magic happens in the background.

That’s where I stopped.

The post I’d Love To ❤️ You More appeared first on WooCommerce, Remote Work & Other Fancy Stuff.