YITH WooCommerce Gift Cards 4.36.0

I dropped YITH WooCommerce Gift Cards into a client’s WooCommerce site that sells spa appointments and “panic gifts” for people who forgot birthdays. Simple brief: let customers buy a digital gift card, send it by email, and let staff redeem it without turning checkout into a crime scene.

Of course, nothing in WooCommerce land is ever “just install the plugin”. YITH WooCommerce Gift Cards did the job, but I had to stare at Query Monitor longer than I wanted.

Database footprint: not horrible, not clean either

First thing I checked: does YITH WooCommerce Gift Cards create its own custom tables? On my setup, no separate monster tables appeared. Most gift card data lived where you’d expect WordPress plugins to dump everything: wp_posts, wp_postmeta, WooCommerce order meta, and options.

That’s better than some plugins that build their own little database empire.

Still, YITH WooCommerce Gift Cards does leave a decent trail in wp_options. I saw plugin settings, email template flags, and a few transient-style entries. The annoying part was not the size, but the autoload behavior. A couple of options were loaded globally when they absolutely did not need to be. Classic WordPress plugin behavior: “Sure, let’s load gift card settings on every blog post, what could go wrong?”

Frontend behavior and DevTools checks

In Chrome DevTools, the gift card product page was mostly sane. No giant JS framework nonsense, thank God. But YITH WooCommerce Gift Cards still injects its own scripts and styles even when I wish it were more selective.

On a clean product page, I checked Query Monitor and saw extra WooCommerce-related queries tied to gift card validation and balance handling. Not catastrophic. Not elegant either.

The stupid bit was AJAX. On one checkout build with a custom mini-cart drawer, YITH WooCommerce Gift Cards triggered extra admin-ajax.php requests when the cart fragments refreshed. Not 50 requests or anything insane, but enough to make me mutter at the screen. I ended up dequeuing one frontend script on non-gift-card pages because, honestly, why should the About page care about gift card logic?

The conflict that ate my afternoon

The worst conflict was with a custom checkout based on WooCommerce Blocks plus a theme override that already smelled bad. YITH WooCommerce Gift Cards expected the classic checkout flow in a few places, especially around coupon-style redemption and validation messages.

Result: the gift card field appeared, submitted, then silently failed on refresh. No useful error. Just vibes.

My ugly little fix was hooking into WooCommerce validation and forcing the gift card message back into the right notice stack:

add_filter('woocommerce_add_error', function ($message) {
    if (strpos($message, 'gift card') !== false) {
        wc_add_notice($message, 'error');
    }
    return $message;
});

Is it beautiful? No. Did it stop the client from calling me every ten minutes? Yes.

Hooks and template overrides

This is where YITH WooCommerce Gift Cards half-redeems itself. The plugin is reasonably developer-friendly. Not perfect, but there are enough actions and filters to avoid editing plugin files like a caveman.

Template overrides also work in the usual WordPress way. I could copy output templates into the theme and adjust the gift card form markup without touching core plugin files. That saved me when the designer insisted the recipient email field had to sit inside a weird two-column layout for “brand consistency”. Sure, Linda.

Documentation for hooks exists, but it is not what I’d call joyful reading. You still end up grepping through plugin files because some filters are named like someone lost a bet.

Caching, Redis, and dynamic content

With page caching enabled, YITH needs care. Gift card balances, recipient fields, and cart redemption blocks are dynamic. If your cache plugin is too aggressive, customers may see stale form states or missing validation messages.

Redis object cache worked fine after I excluded cart and checkout fragments from full-page cache. The issue was not Redis itself; it was cached HTML pretending checkout is static. I also had to exclude gift card product URLs from one optimization plugin’s JS delay feature, because delayed validation scripts broke the recipient email field.

Core Web Vitals impact? Small but real. The plugin added extra CSS and JS, but not enough to tank LCP on its own. The bigger problem was WooCommerce plus theme bloat. YITH WooCommerce Gift Cards was just another brick in the wall.

GPL and practical update workflow

For colleagues asking about licensing: the product is distributed under the GNU GPL, so the PHP code follows GPL rules. In practical terms, if you have a proper Pro package from a legitimate source, the included Pro features are available in that package and can be used across your own sites without domain-count drama from the code itself.

Do not confuse that with vendor services. Automatic updates and support are tied to the vendor’s account system. If you are not using their updater, you update manually.

My routine is boring but safe: export the database first, then zip the current plugin folder, then upload the new package through Plugins -> Add New -> Upload Plugin. If that fails because WordPress is being WordPress, I overwrite the plugin folder by FTP/SFTP. After that I clear object cache, page cache, and re-save WooCommerce permalinks if anything smells weird.

What I actually like

YITH handles the boring business logic better than I expected: generated codes, email delivery, balances, order integration, and gift card redemption are all usable without building half a payment system yourself.

The admin UI is not gorgeous, but it is understandable. Store managers can issue cards, check status, and resend emails without needing me to babysit them. That alone is worth something.

What I absolutely hate

I hate that YITH WooCommerce Gift Cards assumes too much about checkout structure. If you run a normal WooCommerce theme, fine. If you have a custom checkout, headless bits, Blocks, page builders, or a heavily optimized frontend, prepare coffee.

I also dislike the option sprawl. It is not the dirtiest plugin I’ve seen, but uninstall cleanup could be better. After removing it on staging, I still found leftover post meta and settings. Not fatal, just messy. WordPress plugin developers apparently believe databases are compost bins.

Developer pain notes

Does it fight Elementor or other builders?

Sometimes. Product templates built in Elementor can hide or duplicate the gift card fields. Use the native WooCommerce product form widget or manually place the expected hooks.

Can I cache gift card product pages?

Carefully. Exclude cart, checkout, account pages, and any dynamic balance/redemption endpoints. Also test recipient fields after JS optimization.

Does it clean the database after uninstall?

Not completely in my test. Expect leftover metadata and options. I would run a staging cleanup query, not blindly nuke production.

Will it destroy Core Web Vitals?

No, not by itself. But it adds assets. Dequeue YITH WooCommerce Gift Cards scripts where gift card logic is not needed