KATLA FOR WOOCOMMERCE
Consent that never touches the cart.
The same WordPress plugin, with a list of things it refuses to do. Cart, session and checkout cookies bypass the guard, store-critical scripts cannot be blocked by accident, and the marketing pixels wait their turn.
WooCommerce 7.0+HPOS compatibleCart & checkout blocks
wp-content/plugins/katla-consentCheckout-safe by default
Store-critical cookies bypass the cookie guard:
woocommerce_cart_hash wc_cart_hash_*
woocommerce_items_in_cart wc_fragments_*
wp_woocommerce_session_* store_notice*
Store-critical handles are stripped from the blocked
list, so a stray rule can't take checkout down:
wc-cart-fragments wc-checkout wc-blocks-checkout
// Order attribution is marketing, not necessary —
// so it is deliberately not allowlisted:
add_action( 'wp_enqueue_scripts', function () {
katla_block_script( 'wc-order-attribution', 'marketing' );
}, 20 );Or gate it from the Blocking tab, with no code at allFull guide →
WHY WOOCOMMERCE SITES STRUGGLE WITH CONSENT
A consent plugin on a store has a second job: don't break the store.
THE PROBLEMA cookie guard that blocks indiscriminately empties carts and loses sessions, and the symptom looks nothing like the cause.
WITH KATLAWooCommerce cart, session, fragment and store-notice cookies are allowlisted by name and by prefix. The guard never touches them.
THE PROBLEMOne over-eager blocking rule can take checkout down, and you hear about it from customers rather than from a test.
WITH KATLAwc-cart-fragments, wc-checkout and wc-blocks-checkout are removed from the blocked list whatever the rule says, so the mistake cannot reach checkout.
THE PROBLEMOrder attribution cookies look necessary, get allowlisted, and quietly turn into a compliance gap.
WITH KATLAsbjs_* is deliberately left out of the allowlist, because it is marketing. Gate the wc-order-attribution handle and those cookies are never set at all.
SETUP
Four steps, and checkout keeps working.
- Install the pluginThe same katla-consent plugin. WooCommerce support is built in, not a separate add-on.
- Connect your storePaste the Site ID, then run a scan so the plugin has real cookie data to work from.
- Check the classificationsCart and session cookies come back as functional, pixels as marketing. Override anything that looks wrong.
- PublishAdd [katla_policy] to your privacy page, and optionally a preferences link to checkout and My Account.
BUILT FOR WOOCOMMERCE
Made for stores.
Checkout-safe by defaultThe store cookies WooCommerce needs bypass the guard, and the script handles checkout depends on are unblockable.
HPOS and block checkoutThe plugin declares compatibility with high-performance order storage and with the cart and checkout blocks.
Server-side blockingPixels are neutralised while WordPress is still building the page, so they never load and then get told off afterwards.
Preferences where shoppers areA cookie settings link can be appended to the checkout and registration privacy notice, and to the My Account dashboard.
A policy from your real cookiesThe generated cookie policy lists what the scan found on your store — including whatever the last app you installed added — in 13 languages.
Consent Mode v2 and GTMGA4 and Google Ads get all four signals, denied by default. Your existing GTM triggers read the same decision from window.dataLayer.
CORE WEB VITALS
That's how the cookie crumbles. Except your SEO shouldn't.
Store speed is revenue, and the consent banner is the first third party on the page. Katla's is 15 KB in a single request from a CDN, and the heavy pixels stay held until they are allowed rather than adding to it.
How headless mode works →15 kBOver the wireBanner and your cookie data, brotli
0 msAdded LCPAgainst the same page without it
0Layout shiftThe banner reserves no space in flow
1RequestOne script, cached at the edge
Our own measurements, taken — how they were taken.
Questions WooCommerce teams ask
- Will it break my cart or checkout?
- That is the case the WooCommerce support exists for. Cart, session and fragment cookies are allowlisted, and the checkout script handles are removed from the blocked list even when a rule names them explicitly.
- What about order attribution?
- sbjs_* is treated as marketing rather than necessary, because that is what it is. Gate the wc-order-attribution handle and the cookies are never set; leave it and they wait for consent like any other marketing cookie.
- Do I need anything besides the WordPress plugin?
- No. It is one plugin, and the WooCommerce behaviour switches on when WooCommerce is active.
- Does it work with the block-based cart and checkout?
- Yes. The plugin declares compatibility with the cart and checkout blocks as well as with HPOS.
Add consent to your store without touching checkout.
The free plan scans your WooCommerce site and generates a cookie policy, without a card.