If you’ve read Business Bloomer for more than a week, you’ve probably heard me say it: don’t put your custom code in a snippets plugin. Use a child theme, or better, a tiny custom plugin. Keep it clean, keep it fast, keep it under control.
So here’s a confession… the whole Checkout Summit website, from the hotel booking to the microsponsor wall, runs on Code Snippets Pro. And I’m very happy about it!
In case you were wondering, no, I haven’t changed my mind. I’ve just realized that a conference website is a very different animal from a WooCommerce store that needs to run for ten years. This website has a deadline, changes every week, and needs features I can switch on and off in seconds.
In this post I’ll show you what I run, why Code Snippets fits this use case so well, and what you get with Pro compared to the free version.
The rule I always repeat
For more than 15 years I’ve told developers and store owners the same thing: custom PHP code belongs in a plugin, not in a code snippets plugin. My reasons:
- Code saved in the database is outside version control. You can’t easily diff it, review it or roll it back.
- One bad snippet
canused to take the whole site down, and the person who wrote it may not be around to fix it. - Every extra snippet is one more thing that loads on every page.
For a client store that has to run for years, I still stand by all of this. While these snippets are quick and convenient for one-off tweaks during initial setup, they often become a liability over a multi-year lifecycle.
Why a conference website is different
Checkout Summit has a hard end date (next one is 28 April to 1 May 2027, in Palermo). Everything I build for it needs to work for months, not years.
- It changes every week: ticket tiers, sponsors, hotel rooms, guest tickets, activities.
- Features have a short life. The early bird ends, the hotel booking closes after the deadline, and next year it all starts again.
- Speed of development matters more than anything. If a sponsor needs something tomorrow, I want to ship it tonight.
- I need to quickly toggle specific snippets before, during, and after the conference kicks off.
- It’s not a 10,000-product store, so a few extra lines of PHP make no real difference to performance.
What I need is code that works, that I can turn on and off fast, and that I can write quickly. Long term maintenance and raw performance come second. That’s exactly where a snippets plugin shines.
What runs on Code Snippets today
- Hotel booking. A “My Account > Accommodation” tab for ticket holders, with room cards, live stock per room type, up to 7 rooms in one go and a price estimate. Fluent Forms sends the emails and stores the bookings, the snippet adds everything else.

- Microsponsor wall. A shortcode that reads Microsponsor orders and attendee details and shows each microsponsor as a card on the site.

- Thank you page customization. A simple fix that includes a custom page at the top of the default WooCommerce thank you page.

- Store credit. A one-off script that worked out store credit for last year’s founding contributors. It ran once, and now it simply triggers a discount for logged in contributors who are on the checkout page.

That last one is a good example. In a custom plugin, one-off code like that would either be deleted (and lost) or left lying around in a folder. Here it’s a snippet I can switch off once the 2027 edition is over, and I can find it again in a second.
The 3 things that make it perfect for this
1. I only write the code I need
I skip the plugin header, the main file and the folder structure. I open a new snippet, write the 30 lines that matter, and save. On a site where most features are small, that adds up to a lot of saved time.
2. On and off in one click
When the hotel booking deadline passes, I switch the snippet off from the dashboard. If something breaks after a WooCommerce update, I turn off one snippet instead of hunting through files over FTP.
3. I can see everything in the dashboard
Every snippet has a title, a description, tags and a status, all in one list. I don’t need to open a code editor or remember which file does what. I always know what’s running on the site, right from WP admin.

Code Snippets Free vs Pro
The free version on WordPress.org is already solid, with over 1 million active installations. Here’s what it does, and what Pro adds on top.
What the free version does
- PHP snippets, plus HTML content snippets you can place with a shortcode
- One-click activate and deactivate
- Titles, descriptions, tags and priority
- Run everywhere, only in the admin, only on the front end, or just once
- Import and export
- Safe mode, in case a snippet breaks the site
What Pro adds
- CSS and JavaScript snippets
- Conditions, to run a snippet only where and for whom you need it
- The AI Agent, to write, explain and improve snippets
- Cloud Sync and the Cloud Library, to keep snippets in sync across sites and reuse them
- Revision history
- Security scanning
- Snippet Insights, to see how your snippets perform
Pro plans start from $3.90 a month, with yearly and lifetime options too.
AI and Cloud, in practice
AI that lives where the code lives
When I need a quick change, like a new field on a shortcode or a CSS tweak, I can ask the AI Agent right inside the snippet editor, read what it suggests, and save. For small, self-contained snippets like the ones on this site, that’s often all it takes. It can also explain a snippet I wrote months ago, which helps a lot when I come back to it after a long break.

Cloud for staging and for next year
Checkout Summit has a staging site, and every year the same kind of features come back: tickets, hotel, sponsors. With Cloud Sync I keep snippets in my private cloud and send them to the site that needs them, instead of copying and pasting code between sites.

When Code Snippets Fall Short
While snippet plugins excel at speed and flexibility for fast-moving or temporary projects, they quickly reach their limits in complex environments. Long-term projects demand the stability of standard software engineering practices.
Performance and safety at scale are equally critical factors. When custom logic executes on every request across a large product catalog with high traffic, running code through database evaluation introduces performance overhead compared to server-optimized PHP files.
That doesn’t make Code Snippets a bad choice. It means picking the right tool for the job, and for a fast-moving event website, this is the right one.
Thank you, Code Snippets!
A big thank you to the whole Code Snippets team. Your plugin has saved me many hours on Checkout Summit, and it lets me spend my time on the event instead of the code behind it!
If you run a website that changes fast, give it a try.



Leave a Reply