# LolaCore > Free on WordPress.org Manage your entire WordPress site from a chat window. LolaCore is an AI agent that lives inside your wp-admin. Tell it what you need — it reads your site, executes actions, and remembers everything across sessions. Updates, audi... ## Site Directory & Summaries ### [LolaCore for SEO](https://lolacore.com/lolacore-for-seo/?view=raw) LolaCore for SEO · Free Add-on · Requires LolaCore Tell Lola what you want. She'll handle your SEO. LolaCore for SEO lets you say what you need in plain language: write this meta-description, check the whole site for missing ones, fix this title. Lola translates the sentence into the right SEO fields and shows you what changed before it's live. Get it free → See what Lola can do → ● 28 capabilities (22 with Yoast Free)● Works with Yoast Free & Premium● Built o... ### [Documentation](https://lolacore.com/documentation/?view=raw) User Manual · v1.0LolaCore DocumentationEverything you need to install, configure, and use LolaCore and its addons. 66 free abilities · 9 domains · 143 with Elementor (159 with Pro) · 334 with every addon (350 with Pro). Contents Foundation What is LolaCore? Persistent Memory Anti-Sycophancy Working Efficiently Cross-Addon Intelligence Getting Started Requirements Installation License Activation API Provider Setup Settings Panel Skills MCP Integration Plugin Builder Using Lola Chat Basics Site D... ### [Lolacore for ACF](https://lolacore.com/lolacore-for-acf/?view=raw) LolaCore for ACF · Free Add-on · Requires LolaCore Custom fields without the custom-fields learning curve. LolaCore for ACF lets Lola design, build, and fill your custom fields by listening to what you actually need. You describe the problem in plain language. She picks the right structure, creates the fields, and fills them in. ACF is the engine. Lola is who you talk to. Get it free → See what Lola can do → ● 30 capabilities (26 with ACF Free)● Works with ACF Free & Pro● Built on the public... ### [LolaCore for Elementor](https://lolacore.com/lolacore-for-elementor/?view=raw) Now on WordPress.org · v1.0.0 Lola can now build and modify your Elementor site. LolaCore for Elementor gives Lola 77 new abilities (93 with Elementor Pro): building pages, modifying layouts, updating global styles, and managing templates and widgets. You describe what you need from the wp-admin chat. She does it. Free. Download free → See what Lola can do → ● 77 abilities (93 with Pro)● 18 capability categories● Works with Elementor Free & Pro The Problem Without this add-on, Lola hits a wa... ### [LolaCore Bundle](https://lolacore.com/bundle/?view=raw) LolaCore Bundle · WooCommerce Pro + WPCode Snippets · $129/year Three messages.One complete Black Friday campaign. Prices updated across 28 products. Coupon created. Floating banner live. All from the chat, all confirmed before executing, all in under five minutes. That's what happens when WooCommerce Pro and WPCode Snippets work together with Lola. Get the bundle — $129/year 103 TOOLS COMBINEDSAVE $19 VS SEPARATEBUNDLE SETUP IN MINUTES 02 · THE DEMO How it works in practice LolaBlack FridayGet... ### [Fluent Bundle](https://lolacore.com/fluent-bundle/?view=raw) Fluent Bundle · 154 abilities · Save $39 Your most frustrated customers are on your re-engagement list. When support and marketing don't share data, you send the same 'we miss you' email to two completely different people: the one who lost interest, and the one who's been waiting three days for you to fix their order. Lola knows the difference. Because she sees both systems at once. Get the Fluent Bundle · $99/year See how support and CRM work together → ● 103 support + 51 CRM abilities● 13 doma... ### [Fluent Support](https://lolacore.com/fluent-support/?view=raw) Lola for Fluent Support · 103 abilities You're the one connecting your systems right now. Every ticket you answer starts the same way: open Fluent Support, read the ticket, open WooCommerce, find the order, check the refund, copy the amounts, switch back, write the response. You are the bridge between the tools. Lola makes her the bridge instead. Get Lola for Fluent Support — $69/year See what Lola can do → ● 103 helpdesk abilities● 7 domains● Works with Fluent Support Free & Pro 01 · SHOW DON'T... ### [Home](https://lolacore.com/?view=raw) Free on WordPress.org Manage your entire WordPress site from a chat window. LolaCore is an AI agent that lives inside your wp-admin. Tell it what you need — it reads your site, executes actions, and remembers everything across sessions. Updates, audits, WooCommerce, content, security. One conversation instead of twelve admin screens. Install from WordPress.org → See how it works ● 100% free● Bring your own AI key● 5-min setup Lola memory Update all plugins except Elementor. Found 7 plugins with... ### [Business Bundle](https://lolacore.com/business-bundle/?view=raw) 🧠 4 addons · 257 abilities · Save $107 Lola doesn't see four tools. She sees your entire business. Most business owners run their store, their code, their support, and their marketing in separate tabs. Separate tools. No shared memory between them. Lola with the Business Bundle runs all of it from one chat and she remembers everything across all four domains simultaneously. Claim a founding seat · $129/year Get the Business Bundle · $179/year See the full picture → ✓ WooCommerce Pro✓ WPCode Snip... ### [Add-ons](https://lolacore.com/add-ons/?view=raw) LolaCore · Premium Add-ons Lola already runs WordPress.The add-ons connect her to the rest of your business. The free core handles WordPress itself: content, users, plugins, settings, diagnostics. 66 tools, active from day one. The add-ons give Lola access to the specific systems you run your business on: your store, your custom code, your support tickets, your contact database. Four add-ons. Three bundles. Pick the half of the business you want Lola to extend into, or give her both. ● 257 total... ### [Kit por defecto](https://lolacore.com/?elementor_library=kit-por-defecto&view=raw) ### [Plugin Builder](https://lolacore.com/plugin-builder/?view=raw) # Plugin Builder ## A plugin that does exactly one thing: the thing you need. Describe the plugin you need and Lola builds it: any WordPress plugin that fits in three files, with a real settings panel so you configure it without touching code. She generates it, you test it in a safe sandbox, and you install it when you are ready. When you do not need it anymore, delete it. No orphaned tables, no leftover code. [Install LolaCore free →](https://wordpress.org/plugins/lola-core/) [See it build →](#pb-demo-1) - Part of LolaCore core - Free - Test in a sandbox first **LolaBuild** Build me a free shipping progress bar. Show how much more the customer needs for free shipping, on product and cart pages, with a settings panel for the threshold, colors, and messages. Your store has free shipping at $75, so I will use that as the default threshold. Building it now with a settings page under WooCommerce, color pickers, custom messages, and live cart updates. Saved to your library. Want to test it in Playground first? Free Shipping Progress Bar · v1 saved ✓ The examples below show WooCommerce stores, because that is where single-purpose plugins pile up fastest. But the Plugin Builder works on any WordPress site, for any plugin you can describe. ## Show, don't tell ## A free shipping bar with its own settings panel. Built in one conversation. Every store with a free shipping threshold needs this bar: the one on your product and cart pages saying "You are $23 away from free shipping," filling up as the customer adds items. When they hit the threshold, it switches to a confirmation message. You have seen this feature before, bundled inside plugins with 40 settings tabs, most of which you will never open. Here is what happens when you describe exactly what you need to Lola instead. **LolaBuild** Lola, build me a free shipping progress bar plugin. Show how much the customer needs to add to get free shipping, on product pages and the cart page. When they hit the threshold, the message changes. And I need a settings panel to configure the threshold, the colors, and the messages without touching code. Your store has WooCommerce active with free shipping enabled at $75. I will use that as the default threshold, but you will be able to change it in the settings panel. Building it now. **Plugin created: Free Shipping Progress Bar.** Settings page under WooCommerce with: threshold amount (pre-filled at $75), below-threshold message with a {remaining} placeholder, threshold-reached message, bar colors (background, fill, text), display locations (product pages, cart, or both), and an enable toggle. The bar reads the live cart total and updates without a page reload. Saved to your library. Want to test it in Playground first? Yes, open Playground. Here is your test environment: a disposable WordPress with WooCommerce and demo products, your plugin already active. Add a product to the cart and you will see the bar update live. [Open Playground →](#) Lola detected your free shipping threshold from your WooCommerce shipping zones, pre-filled it in the settings panel, built the admin interface with color pickers and message templates, and set up live cart updates. The store owner configures everything from a settings page. No code required, ever. This is a plugin, not a snippet. Its own menu entry, its own settings, its own toggle. Exactly the options you asked for, and not one more. And it took one conversation. ## Show, don't tell ## Social proof from your real orders. Not fake data. You know those little popups in the corner: "Maria from Madrid bought Running Shoes 3 minutes ago." Most of the tools that generate them run as external services, loading their script on your pages and processing your order data on someone else's servers. Lola builds this as a plugin that reads directly from your WooCommerce orders. Real customers, real products, real timestamps. Everything stays inside your WordPress, with a settings panel that controls privacy, frequency, and style. **LolaBuild** Build me a recent purchase notification plugin: those little toast popups showing recent orders. Use real data from WooCommerce. I need a settings panel to control how it looks and what customer data it shows, because I don't want to expose full names. WooCommerce is active. I will query your recent completed orders for the notification data. **Plugin created: Live Purchase Notifications.** Settings page under WooCommerce with: customer display format (full name / first name / city / first name + city), number of recent orders to pull from, time between notifications, how long each stays visible, display pages, position, notification style, product categories to exclude, and an enable toggle. Each notification shows the product name, thumbnail, customer info per your privacy setting, and a relative timestamp. All data comes from real orders. Nothing is generated or simulated. Saved to your library. This plugin lives in your WordPress, reads the order data that is already there, and respects the privacy format you chose. No external service, no script loading from someone else's domain, no order data leaving your site. And when the holiday season ends and you do not need the popups anymore, you deactivate the plugin. Reactivate it next Black Friday. Or delete it and ask Lola to build a better version with what you learned. ## Build, then iterate ## A countdown timer with two levels of configuration. And what happens when you want more from it. This one goes beyond a floating timer. It is a per-product countdown on individual product pages, tied to the sale dates you set in WooCommerce. It has global settings for style and behavior, plus a per-product box in the product editor. Two levels of configuration is what makes this a genuinely complex build, and it still fits in one conversation. **Part 1 · Creation** **LolaBuild** I need a sale countdown timer plugin. Show a countdown on product pages when a product has a scheduled sale. I want global settings for the style and behavior, and a per-product box in the product editor where I set the sale end date and override the global message. WooCommerce is active. I will hook into the product sale schedule and the product edit screen. **Plugin created: Product Sale Countdown.** Global settings page with counter style, colors, default message with a {countdown} placeholder, expired message, and expiry behavior. Per-product meta box with sale end date (pre-filled from the WooCommerce sale schedule), a custom message override, and a disable-for-this-product checkbox. Products with a scheduled sale show the countdown automatically. Saved to your library. 3 files, version 1. Two weeks pass. Black Friday worked. Now you want one more thing. When a sale expires, instead of just hiding the counter, you want it to show a "Sale ended, but here is 5% off for 24 hours" message with a consolation coupon. That feature does not exist in any plugin you could buy. It is too specific to your store, your campaign, and your coupon strategy. But Lola already knows your plugin. **Part 2 · Iteration** **LolaIterate · v2** Update the Product Sale Countdown plugin. When a sale expires, show a "Sale ended" message with a consolation coupon code and a 24-hour window. I want to configure the coupon code and the message from the settings panel. I found Product Sale Countdown in your library (version 1). I will add the post-expiry consolation feature to the global settings. **Changes applied (version 2):** a new toggle to enable post-expiry consolation, a coupon code field (validated against your existing WooCommerce coupons), a configurable consolation message, and a window duration. When a sale expires and consolation is enabled, the countdown area transforms into the message for the configured window, then disappears. Version 2 saved. Version 1 is in your revision history. Test in Playground? Product Sale Countdown · v2 saved ✓ That is the moment. The feature you needed did not exist in any plugin you could buy, not because those plugins are bad, but because your exact combination of needs is unique to your store. You described it in two sentences and Lola added it to your existing plugin, with new fields in the admin panel, validation against your WooCommerce coupons, and a configurable time window. Version 2. Version 1 still in your history if you need to roll back. You described it, Lola built it, you tested it, you deployed it. Same day. ## The safety net ## AI writing code inside your WordPress sounds dangerous. Here is why it isn't. You should be skeptical about AI-generated code running on your live store. That instinct is correct. Here is every layer between Lola generating a plugin and that plugin running on your site. **Lola reviews her own work.** Every generated plugin goes through an automated review before it reaches your library: a second AI pass that checks for security issues (nonces, input sanitization, output escaping), WordPress coding standards, and potential conflicts. If the review finds problems, Lola fixes them and regenerates before delivering. The review is an internal quality gate, not a guarantee. That is why Playground testing exists as the next step. **Playground lets you test without touching your store.** One click opens a disposable WordPress instance with your plugin already installed and active. If your plugin needs WooCommerce, the Playground includes WooCommerce with demo products so you can test cart and checkout behavior. Close the tab and the test environment is gone. **Installation is a two-step process.** Lola never installs on your live site without asking. When you confirm, she validates the PHP syntax first. If there is an error, nothing is written and Lola reports what failed. If syntax passes, the plugin is placed in your plugins directory but stays inactive. You then choose to activate it. Two confirmations, not one. Nothing is ever activated silently. **The code is yours to read and review.** Every plugin in your library shows the full source code in tabs: PHP, JavaScript, CSS. Standard WordPress plugin code. No proprietary framework, no compiled output, no obfuscation. If you or your developer want to inspect what Lola generated, it is all there. **Delete from your library, cleanly.** Trash a plugin from your library and the entry, its code, and all revision history are removed from your database. If you already installed it on your site, you remove that copy the same way you remove any WordPress plugin: deactivate and delete from the Plugins screen. ## Your library ## Your plugins, your library, your rules. Every plugin Lola builds lives in your WordPress admin under Lola > My Built Plugins. Each entry shows the plugin name, current version, and whether it is installed on your site or just saved in the library. From the library, every plugin has the same options: test in Playground, install on your site, or leave it saved. Open the editor to review the code in PHP, JS, and CSS tabs. Tell Lola to iterate on it. Or send it to the trash. Versioning is automatic. Every time Lola updates a plugin, the previous version is saved as a revision. You can view the history and restore an older one if an update did not work as expected. Over time, your library becomes a toolkit built for your specific store. The free shipping bar from launch. The social proof popups from the holiday campaign. The countdown timer you iterated twice. Each one tailored to your theme, your WooCommerce setup, your exact requirements. Each one doing its one job, with nothing extra attached. ## The weight ## Open your plugins list. How many do you actually use? Think about five concrete needs your store has had this year: a free shipping bar, social proof popups, a countdown timer, a custom checkout field, an announcement bar. **Five generalist plugins** Five settings pages you explore once and never open again. Five sets of stylesheets and scripts loading on every page your customers visit. Five update notices every month, each a small risk of conflict with your theme or with each other. Five more rows in a plugins list that already makes you tired to look at. **Five plugins Lola built** Five tools that do exactly what you described, with exactly the settings you asked for, running entirely inside your WordPress. When a campaign ends, you deactivate or delete, and nothing is left behind. That is the difference. Not more plugins. The right ones, at their right size. The Plugin Builder is part of LolaCore core. ## What this is not ## Lola builds real plugins, not enterprise software. Each plugin Lola creates is three files: PHP for the logic and admin panel, JavaScript for front-end behavior, CSS for styling. Three files is enough for a free shipping bar with a settings page, a social proof system with privacy controls, a countdown timer with per-product configuration, a custom checkout field with conditional logic, an announcement bar with scheduling, or a delivery date estimator with business-day calculations. Three files is not enough for a full CRM, an accounting system, or a page builder. Lola will not attempt those. If you ask for something that needs its own database tables, a REST API, a payment gateway integration, or third-party package dependencies, Lola tells you it is outside the scope of the Plugin Builder and suggests you look for a dedicated plugin. The target is the gap between a code snippet and a full commercial plugin: the space where you need one focused feature, built for your site, not a thirty-feature suite where you will configure one tab. When you genuinely need the full suite, the suite is the right tool. When you need one thing, now you have a way to get exactly that. ## Frequently asked questions ### Do the plugins Lola builds depend on LolaCore to run? No. Once a plugin is installed on your site, it runs as a standard WordPress plugin. If you uninstall LolaCore, every plugin Lola built keeps working. What you lose is the ability to iterate on them, generate new ones, or test in Playground. The plugins are yours. The workshop is Lola’s. ### Does the Plugin Builder only work for WooCommerce plugins? No. Lola builds any WordPress plugin you describe, as long as it fits within three files. The examples here focus on WooCommerce because that is where single-purpose plugins accumulate fastest. But a custom login page, a content restriction system, a notification bar for your blog, or a redirect manager all ### [Privacy Policy](https://lolacore.com/privacy-policy/?view=raw) LEGAL · LOLACORE.COM Privacy Policy Last updated: May 13, 2026 LolaCore is developed and operated by María DC, based in Granada, Spain. This Privacy Policy explains how we collect, use, and protect personal data in connection with lolacore.com and the LolaCore software ecosystem. 1. Who We Are (Data Controller) For the purposes of the GDPR and Spain's LOPDGDD, the data controller is: María DC Granada, Andalusia, Spain legal@lolacore.com 2. Scope of This Policy 2.1 lolacore.com (this website) — D... ### [Elementor Header #182](https://lolacore.com/?elementor_library=elementor-header-182&view=raw) Install free → ### [About](https://lolacore.com/about/?view=raw) # Why I Built LolaCore *by Fran Barbero* I ran an online store for ten years. Wellness products. Built it from scratch, grew it, made real money from it. Selling was never the problem. The problem was that every small change I wanted to make in my own store cost me half a morning. You know how it goes. You want to launch a product and you end up clicking through six screens just to get it published. You want to understand why sales dropped and you end up with twelve tabs open. You update a plugin and pray it doesn't break your checkout. And the worst part: the context of why you did something disappeared the moment you closed your session. Three weeks later you couldn't remember why you had deactivated that plugin, so you turned it back on, and the same thing broke again. That was just my side. My wife, Lola, handled customer support. Same endless hours, but on the other side of the counter: answering tickets, chasing down issues, keeping track of what she'd promised each customer and why. We were both running on the same treadmill, each on a different screen, neither seeing what the other was doing. It wasn't a bad plugin or a broken theme. It was WordPress. The bigger your store gets, the more of your time it eats. We didn't have a store. We had a store that had us. ## We quit. Then I came back with one condition. COVID hit and we were both burned out. It was the push I needed to shut everything down. I didn't close because of the product or the market. I closed because I was exhausted from managing the thing. Years of jumping between screens, keeping configurations in my head, losing the thread from one session to the next. I took some time to think. And when the fog cleared, only one question was left: if I went back to WordPress, how would I do it differently? I spent a good chunk of my savings learning AI from the inside out. Working directly with the APIs, building prototypes that broke, throwing away entire frameworks and starting over. There's no other way to actually understand this stuff. And all of that taught me something I didn't expect: the AI tools that exist today can do impressive things, but they don't remember anything. Every time you start a new conversation, you're back to zero. For a store that's useless, because the value is in the accumulated context: which plugins caused problems, which changes worked, which decisions you made and why. What I wanted was AI inside WordPress. Not connected from an external server. Inside, with real access to the site's data, executing real actions and remembering the context from one session to the next. For a long time that was technically impossible without external libraries that made everything unstable and fragile. Then the first betas of WordPress 7.0 arrived with native AI built into the core. The technology finally matched what I had in my head. That's when LolaCore was born. And yes, she's named after my wife. ## What Lola is for you I didn't build this for developers or for people who enjoy tinkering with admin panels. I built it for the person we were ten years ago: someone with a real business who just wanted their store to work without it eating them alive. Lola is the assistant that would have saved us those ten years. She lives inside your wp-admin, reads your actual store, and executes what you ask her to. She doesn't explain how to do it so you can do it yourself: she does it with you, shows you exactly what she's going to touch, and waits for your confirmation before changing anything. And she remembers. She remembers what you changed last month and why you changed it, the way someone would if they'd been running your store with you from day one. The more conversations you have, the better she knows your business. That memory is the difference between a tool you use and someone you rely on. That's why LolaCore doesn't stop at technical management. It also connects with your customer support and marketing tools, because I know firsthand that the burnout doesn't come from the admin panel alone. It comes from both sides of the business at the same time, and nothing out there connects them for you. Every store I work with today, I run it this way. The LolaCore website itself is built and maintained with LolaCore. If something breaks, I'm the first to know. *If any of this sounds familiar, Lola is on the WordPress.org repository. Install her for free and let her get to know your store.* [Install LolaCore from WordPress.org](https://wordpress.org/plugins/lolacore/) ### [Elementor Footer #187](https://lolacore.com/?elementor_library=elementor-footer-187&view=raw) © 2026 LolaCore · Built in Granada, Spain · WordPress.org Privacy Policy · Terms of Service · Refund Policy · Contact Contact LolaCore × ### [WPCode Snippets](https://lolacore.com/wpcode-snippets/?view=raw) # WPCode Snippets ## How to Use WPCode Snippets WPCode is a powerful WordPress plugin that allows you to add custom code snippets to your site without editing your theme's functions.php file. This makes it easier to manage and organize your custom code. ## Adding a New Snippet 1. Go to **WPCode** → **Add Snippet** in your WordPress admin. 2. Choose a snippet type (PHP, JavaScript, CSS, HTML, or Text). 3. Give your snippet a title. 4. Paste your code into the code editor. 5. Configure the insertion method (Auto Insert, Shortcode, or Block). 6. Set the location (Frontend, Admin, or Both). 7. Click **Save Snippet** and toggle the switch to **Active**. ## Snippet Types - **PHP Snippets** – For custom PHP functions and modifications. - **JavaScript Snippets** – For adding custom JavaScript code. - **CSS Snippets** – For adding custom CSS styles. - **HTML Snippets** – For adding custom HTML content. - **Text Snippets** – For adding plain text or shortcodes. ## Insertion Methods - **Auto Insert** – The snippet runs automatically on every page load. - **Shortcode** – Use a shortcode to insert the snippet anywhere on your site. - **Block** – Use a Gutenberg block to insert the snippet. ## Location Settings - **Frontend** – The snippet runs on the frontend of your site. - **Admin** – The snippet runs in the WordPress admin area. - **Both** – The snippet runs on both frontend and admin. ## Conditional Logic WPCode allows you to set conditional logic for your snippets. You can choose to display snippets based on: - Page type (home, single post, page, archive, etc.) - User role (admin, editor, subscriber, etc.) - Custom conditions (URL, referrer, device type, etc.) ## Code Revisions WPCode keeps a history of all changes made to your snippets. You can view and restore previous versions of any snippet. ## Snippet Library WPCode includes a built-in library of pre-made snippets. You can browse and install snippets for common tasks like: - Disabling the admin bar - Adding custom login styles - Removing WordPress version numbers - Adding Google Analytics tracking code ## Troubleshooting If a snippet causes an error, WPCode will automatically disable it and display an error message. You can then edit or delete the problematic snippet. ## Best Practices - Always test snippets on a staging site first. - Use descriptive titles for your snippets. - Add comments to your code for clarity. - Keep snippets short and focused on a single task. - Regularly review and clean up unused snippets. ### [WooCommerce Pro](https://lolacore.com/woocommerce-pro/?view=raw) LolaCore WooCommerce Pro · Premium · $99/year You run your store in 12 screens.Lola does it in one sentence. WooCommerce Pro adds 29 store management tools to the agent already living inside your WordPress. Orders, stock, pricing, customers, analytics, shipping, taxes. You tell Lola what you need. She shows you what's going to change. You confirm. Done. Add WooCommerce Pro — $99/year See the full bundle — $129/year 29 STORE TOOLSBYOM COMPATIBLEACTIVATES INSTANTLY 01 · THE PROBLEM Managing WooCom... ### [Fluent CRM](https://lolacore.com/fluent-crm/?view=raw) Lola for Fluent CRM · 51 abilities Your email tool doesn't know who has an open support ticket. Most re-engagement campaigns treat all dormant customers the same. Some stopped buying because they lost interest. Others stopped because they had a problem nobody fixed. Sending both groups the same 'we miss you' discount is the wrong email for half your list. Lola knows the difference. Get Lola for Fluent CRM · $69/year See how Lola segments differently → ● 51 CRM abilities● 6 domains● Works with Fl... ### [Terms of Service](https://lolacore.com/terms-of-service/?view=raw) LEGAL · LOLACORE.COMTerms of ServiceLast updated: May 13, 2026 These Terms of Service govern your access to and use of the LolaCore website at lolacore.com and all LolaCore software products, including the free core plugin and premium add-ons. By accessing the Site or using any LolaCore product, you agree to be bound by these Terms. These Terms constitute a legally binding agreement between you and María DC, based in Granada, Spain.1. Professional Use — B2B DeclarationLolaCor... ### [Refund Policy](https://lolacore.com/refund-policy/?view=raw) LEGAL · LOLACORE.COM # Refund Policy *Last updated: May 13, 2026* This Refund Policy applies to all purchases of LolaCore premium add-ons made through lolacore.com. ## 1. Merchant of Record All transactions are processed by **Lemon Squeezy**, which acts as the Merchant of Record for all LolaCore premium add-on sales. Lemon Squeezy is the legal seller of record and is responsible for processing payments, issuing invoices, and handling refund transactions. Refund requests are processed in accordance with [Lemon Squeezy's Refund Policy](https://www.lemonsqueezy.com/refund-policy). ## 2. General Position on Refunds LolaCore premium add-ons are digital products delivered immediately upon purchase. The license key is issued and the update system becomes accessible at the moment the transaction is confirmed. Given the immediate and digital nature of the delivery, **refunds are not guaranteed** after the license key has been issued and the update delivery system has been accessed. ## 3. When a Refund May Be Considered A refund request may be considered in the following situations: - The add-on could not be installed or activated due to a technical issue on our end that we were unable to resolve within a reasonable timeframe - A duplicate purchase was made in error - The product purchased does not match what was described on the sales page at the time of purchase We do **not** issue refunds for: - Change of mind after purchase - Failure to meet system requirements that are clearly documented before purchase - Issues caused by third-party plugins, themes, or hosting environments outside LolaCore's scope - Expiry of an annual subscription that was not renewed ## 4. How to Request a Refund All refund and billing inquiries must be directed to: > **[sales@lolacore.com](mailto:sales@lolacore.com)** Please include your order number, the email address used at purchase, and a brief description of the issue. We will review your request and respond within **3 business days**. If we are unable to resolve your issue and your request qualifies under Section 3, we will initiate the refund through Lemon Squeezy on your behalf. *Do not contact the technical support channel (via lolacore.com/support) for billing or refund matters — that channel is exclusively for technical support with an active license.* ## 5. Subscription Renewals Automatic renewal charges are not eligible for refund after processing, except where a billing error has occurred. If you do not wish to renew your subscription, you may cancel it at any time through your Lemon Squeezy customer portal before the renewal date. ## 6. Contact For all refund, billing, and sales inquiries: > **[sales@lolacore.com](mailto:sales@lolacore.com)** **María DC** Granada, Spain *LolaCore is a trademark of María DC. All rights reserved.* ### [7 Plugins on Your WooCommerce Store You Could Delete Today](https://lolacore.com/7-plugins-on-your-woocommerce-store-you-could-delete-today/?view=raw) Open your WordPress plugins page right now. Count them. If you're running a typical WooCommerce store, you've got somewhere between 25 and 40 active plugins. You're paying annual renewals on at least a dozen of them. A good chunk of those plugins do things that take 5 to 10 lines of PHP to accomplish. You're paying $49 to $89 a year for functionality that a snippet of code could handle permanently, with zero performance cost and no update dependency. This isn't about being a developer. This is about knowing which plugins are earning their keep and which ones are dead weight on your store's speed, security, and your credit card. ## 1. The "Hide Admin Bar" plugin This is the most absurd plugin category in the WordPress ecosystem. There are plugins with 100,000+ installs whose entire job is to hide the admin bar for non-admin users. That's one line of PHP: ``` add_filter('show_admin_bar', '__return_false'); ``` You're loading an entire plugin with its own update cycle, compatibility checks, and database queries for something that WordPress already has a filter for. If your "hide admin bar" plugin has a settings page, that's even worse. There's nothing to configure. It's a yes or no. ## 2. The "Maintenance Mode" plugin Maintenance mode plugins range from simple (show a "coming soon" page) to bloated (drag-and-drop landing page builder for your maintenance screen). For most store owners, you need this feature twice a year at most — during a migration or a major redesign. A maintenance mode snippet is about 8 lines of PHP. It checks if the visitor is logged in. If not, it shows a message. That's it. You don't need a plugin sitting active for 363 days a year waiting for the 2 days you actually use it. ## 3. The "Custom Login Page" plugin Custom login page styling is cosmetic. It makes your wp-login.php match your brand colors. It's nice. It is also not worth $59/year. WordPress has a `login_enqueue_scripts` action hook. A snippet of 15 lines of CSS injected through that hook does the same thing. Your logo, your colors, your background. No plugin, no settings page, no annual renewal email in January. ## 4. The "Disable Comments" plugin If you don't want comments on your WooCommerce product pages, you don't need a plugin to turn them off. Most store owners use reviews instead. WordPress has had this built into Settings → Discussion since version 1.0. For more granular control, a snippet with `add_filter('comments_open', '__return_false')` kills comments globally in one line. The "Disable Comments" plugin category exists because WordPress's native settings are buried in a non-obvious place. That's a UX problem, not a functionality gap. Don't pay a plugin to solve a menu navigation issue. ## 5. The "Insert Headers and Footers" plugin Google Analytics tracking code. Facebook Pixel. A custom font from Google Fonts. A chat widget script. These all need to go in your site's `` or before ``. There are plugins with millions of installs that do nothing except give you a textarea to paste code into. The functionality is identical to adding a `wp_head` or `wp_footer` action in a snippet. If you're already using a snippet manager like WPCode or Code Snippets, you already have this capability and the plugin is fully redundant. ## 6. The "Redirect" plugin Simple redirect plugins map one URL to another. Old product page moved? Redirect /old-product to /new-product. This is useful, but paying for a plugin to manage a handful of redirects is overkill. For stores with fewer than 20 redirects, a PHP snippet with a simple array lookup does the job. For stores with hundreds of redirects, a plugin with a database-backed UI makes sense. But most WooCommerce stores have 5 to 15 redirects, and half of those were set up once during a migration and never touched again. ## 7. The "Quick CSS" or "Simple Custom CSS" plugin You want to change the font size on your product titles. Or adjust the spacing on your cart page. Or hide an element you don't need. A "Custom CSS" plugin gives you a textarea to paste CSS. WordPress has had a built-in Custom CSS editor in the Customizer since version 4.7 (2016). It's under Appearance → Customize → Additional CSS. The plugin is duplicating a feature that's already in your WordPress core. Unless you need CSS that loads conditionally on specific pages (which most of these plugins don't support anyway), the built-in option is better because it stores your CSS in the theme's changeset, not in a plugin's database table. ## Add up the cost Let's be conservative. Say you have 5 of these plugins and they average $59/year each. That's $295/year in subscriptions. Some stores have all 7 plus a couple more in the same category like "Disable REST API," "Remove Query Strings," or "Disable Gutenberg." That pushes you past $400/year easily. But the subscription cost isn't the real damage. Each active plugin: - Adds database queries on every page load - Loads its own CSS and JavaScript files (even on pages where it's not needed) - Creates potential security vulnerabilities (every plugin is an attack surface) - Generates compatibility risks with every WordPress and WooCommerce update A store running 35 plugins will always be slower than the same store running 25 plugins with the other 10 replaced by lightweight snippets. PageSpeed doesn't care about your plugin's branding or settings page. It cares about how many HTTP requests and database queries happen before your customer sees the product page. ## The catch You're reading this and thinking: "Great, but I'm not a PHP developer. I can't write these snippets." That's fair. And that's exactly the gap that keeps these plugins installed. The store owner knows they're overpaying for simple functionality, but the alternative (writing and maintaining code) feels risky. What if the snippet breaks something? What if a WordPress update changes the hook? Who maintains it? The plugin tax exists because writing code feels dangerous and installing a plugin feels safe. Even when the plugin is doing almost nothing. Does that tradeoff still make sense in 2026? There is a better way to get those snippets written, tested, and managed without touching a code editor. --- *Previous in this series: [Your Discount Coupons Are Destroying Your Margins (And You Don't Know It)](/blog/your-coupons-are-destroying-your-margins). Next: why your best customers have gone quiet, and what to do about it.* ### [Your Discount Coupons Are Destroying Your Margins (And You Don’t Know It)](https://lolacore.com/your-discount-coupons-are-destroying-your-margins-and-you-dont-know-it/?view=raw) # Your Discount Coupons Are Destroying Your Margins (And You Don’t Know It) You ran a 50% off flash sale last month. Orders poured in. You felt great about it for exactly three days. Then you looked at the numbers and realized you barely broke even on shipping costs. Most WooCommerce store owners treat coupons as a volume lever: more discounts, more orders, more revenue. But revenue is not profit. And the gap between the two is where coupon strategies silently bleed your business dry. ## The two kinds of coupon customers Not all coupon users are equal. There's a split that most store owners never bother to measure, and it's costing them thousands a year. **The first group** uses a coupon once for a welcome discount and comes back later at full price. Their first order has a healthy average (say, $90). They buy again in 60 days. They're discovering your brand through the discount, and the coupon paid for itself by the second purchase. **The second group** only shows up when there's a deal. Their average order is the bare minimum to qualify for the discount. They never come back at full price. If you check your order history, you'll find these customers clustered entirely around sale periods. Outside of promotions, they don't exist in your database. The first group builds your business. The second group is extracting value from it. ## A quick test you can run right now Pull up your WooCommerce orders from the last 6 months. Filter by coupon code. For each coupon, answer two questions: 1. What was the average order value for orders using that coupon? 2. How many of those customers bought again without a coupon? If you have a coupon where the average order is under $50 and the repeat purchase rate without a coupon is close to zero, that promotion didn't acquire customers. It subsidized bargain hunters. A 10% welcome coupon with a $90 average order and 30% returning customers is a customer acquisition tool. A 50% flash sale with a $45 average order and 2% returning customers is a margin donation. ## The math nobody does Here's a scenario that plays out in hundreds of WooCommerce stores every month. You sell products with an average margin of 40%. Your average order without discounts is $80, giving you $32 in gross profit per order. You run a 30% off coupon with no minimum. The average order with that coupon drops to $55. Your gross profit on that order: $55 × 40% = $22, minus the discount ($55 × 30% = $16.50). You're left with $5.50 per order before shipping, payment processing, and packaging. On a $55 order with free shipping, you might actually lose money on every sale. Now multiply that by 200 orders during a week-long promotion. You just generated $11,000 in revenue and potentially lost money doing it. ## Why this keeps happening Three reasons store owners fall into the coupon trap: **Revenue looks good on the dashboard.** WooCommerce shows you gross revenue, not margin-adjusted revenue. A spike in sales feels like a win. You'd need to manually cross-reference costs, discounts, and return rates to see the real picture. Almost nobody does. **Coupons are the easiest lever to pull.** When sales slow down, the instinct is to create a discount. It's faster than improving your product photos, rewriting descriptions, or fixing your email sequences. It takes 30 seconds to create a coupon in WooCommerce. The damage takes months to spot. **There's no warning system.** WooCommerce doesn't tell you "this coupon is attracting buyers who will never return at full price." It doesn't flag when a promotion's average order is 40% below your store average. You only discover the problem if you dig into the data yourself, and most store owners don't have time for that. ## What a healthy coupon strategy looks like The fix isn't eliminating coupons. Discounts work when they're designed to protect your margin and filter for quality customers. **Set minimum order thresholds.** A 20% off coupon with a $100 minimum protects your average order value. A 20% off coupon with no minimum lets people buy your cheapest item at a loss to you. **Limit use per customer.** One-time use coupons for new customers are an acquisition cost. Unlimited-use coupons train your existing customers to wait for the next sale. **Track return rates by coupon code.** The single most important metric for any coupon is: what percentage of customers who used this code came back and paid full price? If the answer is under 10%, that coupon is a net loss regardless of how much revenue it generated. **Kill underperforming coupons fast.** Review every active coupon once a month. If it's pulling below-average orders and zero repeat buyers, deactivate it. The short-term revenue drop is smaller than the long-term margin erosion. ## The uncomfortable question Go look at your WooCommerce dashboard right now. Sort your coupons by usage count. Look at your most-used coupon. Is it building your customer base, or is it feeding bargain hunters who will never pay full price? Most store owners can't answer that question without spending an hour digging through order reports, exporting CSVs, and cross-referencing customer purchase histories. That's the real problem. The data is in your store. The insight is buried under 12 different WooCommerce admin screens. And by the time you get around to doing the analysis, you've already run the next promotion. Your margins can't afford to wait. * * * *This is the first post in a series about the hidden costs of running a WooCommerce store on autopilot. Next up: the 7 plugins you're paying for that you could delete today.* ### [Your Best Customers Haven’t Bought in 90 Days. Do You Know Which Ones?](https://lolacore.com/your-best-customers-havent-bought-in-90-days-do-you-know-which-ones/?view=raw) You spent $3,200 on Facebook ads last quarter. You got 140 new customers from it. That's about $23 per customer acquired. Meanwhile, 11 of your existing customers quietly stopped buying three months ago. These are people who spent over $180 per order multiple times, totaling over $6,000 combined. You didn't notice. Nobody told you. Acquiring those 11 customers originally cost you somewhere between $250 and $500 in total marketing spend. Reactivating them would cost a fraction of that. But you di... ### [How I Audited My Coupon Profitability in 2 Minutes (With One Conversation)](https://lolacore.com/how-i-audited-my-coupon-profitability-in-2-minutes-with-one-conversation/?view=raw) # How I Audited My Coupon Profitability in 2 Minutes (With One Conversation) A few weeks ago I wrote about [how discount coupons silently destroy your margins](https://file+.vscode-resource.vscode-cdn.net/blog/your-coupons-are-destroying-your-margins). Store owners responded with the same problem: checking it manually takes forever. Pulling WooCommerce order data, filtering by coupon, calculating per-coupon AOV, and cross-referencing repeat purchase rates takes an hour of spreadsheet work. Nobody does it weekly. Most people never do it at all. So I did it through a conversation with Lola instead. The whole thing took about two minutes. ## The conversation I opened my WordPress admin, clicked the Lola chat widget, and typed: > **Me:** Which of my active coupons are actually profitable? I want to know which ones are bringing in good customers and which ones I should kill. > **Lola:** You have 6 active coupons. Let me pull the numbers on each. > > Here's what I found: > > **WELCOME10** (10% off, first order only): 84 uses, average order $94. 31% of users came back and purchased again at full price within 60 days. This coupon is working. It's an acquisition tool with positive ROI. > > **SPRING20** (20% off, no minimum): 47 uses, average order $62. 8% repeat rate. Most orders are near the minimum cart size. You're discounting full-margin products for one-time buyers. > > **LOYALTY15** (15% off for returning customers): 23 uses, average order $118. 100% repeat customers by definition, but their AOV before using this coupon was $125. They were already buying at full price. This coupon is rewarding behavior that was already happening. > > **FLASH50** (50% off, 48-hour sale): 112 uses, average order $43. 2% repeat rate. This is your worst-performing coupon by every metric. Average margin after discount is approximately $1.20 per order before shipping costs. You likely lost money on most of these transactions. > > **FRIEND25** (25% off, referral code): 9 uses, average order $87. Too small a sample to draw conclusions, but early signs are decent. > > **BUNDLE10** (10% off orders over $150): 34 uses, average order $178. 22% repeat rate. Strong performance. The minimum threshold is protecting your margin and attracting higher-intent buyers. I already suspected FLASH50 was a problem. But seeing "$1.20 per order before shipping" made it real. Then I pushed further: > **Me:** What would you do with FLASH50? > **Lola:** I'd kill it. 112 orders at an average margin of $1.20 generated about $134 in gross profit total. Your shipping and payment processing costs on those orders were almost certainly higher than that. This coupon cost you money. > > If you want to run flash sales, a 25% discount with a $100 minimum order would keep your average margin above $15 per order. That's still aggressive enough to feel like a deal without subsidizing your cheapest products at a loss. > > Want me to deactivate FLASH50 and create a replacement with those parameters? > **Me:** Yes, do it. > **Lola:** Done. FLASH50 is deactivated. I've created FLASH25 with 25% off on orders over $100, limited to 1 use per customer, valid for 48 hours. Want me to set the start date or leave it as a draft? ## What just happened Three things happened in that conversation that wouldn't happen with a dashboard or a report: First, Lola didn't just show me the numbers. She interpreted them. "This coupon is rewarding behavior that was already happening" about LOYALTY15 is the kind of insight that takes a human analyst 30 minutes to articulate after looking at the raw data. It reframed a coupon I thought was working into one that was unnecessary. Second, Lola told me to kill a coupon. She didn't say "consider reducing" or "you might want to review." She said "I'd kill it" and showed me the math. FLASH50 generated $134 in total gross profit across 112 orders. That's a number that makes the decision obvious. Most tools show you usage counts and revenue — metrics that make bad coupons look successful. Lola showed me margin, which made the same coupon look like what it was: a loss. Third, the fix was immediate. In the same conversation where I diagnosed the problem, I also solved it. Deactivate the bad coupon, create a better one with specific parameters, done. No switching between WooCommerce screens, no navigating to Marketing → Coupons → Add New, no filling out form fields. One conversation, one outcome. ## The LOYALTY15 surprise The coupon that surprised me most wasn't FLASH50. I already had a bad feeling about that one. It was LOYALTY15. I created that coupon thinking I was rewarding my best customers. Turns out I was discounting orders that would have happened anyway at full price. Those 23 customers had an average order of $125 before the coupon existed. With the coupon, their average dropped to $118. I wasn't generating loyalty. I was giving away $7 per order to people who were already loyal. That's the kind of insight you only get when someone looks at your data with an opinion, not just a chart. A dashboard would have shown me "LOYALTY15: 23 uses, $118 AOV" and I would have thought it was fine. Lola told me it was wasteful because she compared it to what those same customers were spending without the coupon. ## What this changes The traditional workflow for coupon analysis looks like this: export orders, open spreadsheet, build pivot tables, calculate AOV per coupon, manually check repeat rates, make a decision, go back to WooCommerce, execute the change. Two to three hours if you're efficient. Most store owners do it quarterly, if ever. The conversation above took two minutes. You can do this every week without it feeling like a chore. Ask Lola, get the answer, act on it, move on. That's what changes when your store admin can actually talk back to you. --- *This is the fourth post in a series about running a WooCommerce store without the busywork. Previously: [Your Discount Coupons Are Destroying Your Margins](https://file+.vscode-resource.vscode-cdn.net/blog/your-coupons-are-destroying-your-margins). Next: what happens when you replace 8 plugins with code snippets generated by a single conversation.* ### [From 30 Plugins to 22: How Lola Replaced 8 Plugins With Code Snippets in One Conversation](https://lolacore.com/from-30-plugins-to-22-how-lola-replaced-8-plugins-with-code-snippets-in-one-conversation/?view=raw) I wrote a few weeks ago about the plugins sitting in your WooCommerce store that do almost nothing. The response I got most was: "Okay, I see the problem. But I'm not writing PHP." Nobody's asking you to. Here's what happened when I asked Lola to handle it instead. The starting point My test store had 30 active plugins. A pretty normal number for WooCommerce. PageSpeed mobile score: 64. Desktop: 78. Annual plugin subscription cost across all 30: roughly $870. I opened the Lola chat widget and st... ### [I Launched a Black Friday Campaign in 5 Minutes From a Chat Window](https://lolacore.com/i-launched-a-black-friday-campaign-in-5-minutes-from-a-chat-window/?view=raw) # I Launched a Black Friday Campaign in 5 Minutes From a Chat Window Last November I spent an entire afternoon setting up a Black Friday promotion. Adjusting prices in the WooCommerce product editor, one by one. Creating the coupon with the right restrictions. Then switching to a page builder to make a promotional banner. Then realizing the banner needed custom CSS to look right on mobile. Then testing the coupon to make sure the minimum order threshold actually worked. Four hours. For a campaign that ran 48 hours. This year I did the same thing in 5 minutes. Five messages in a chat window. Here's the full conversation. ## Minute 1: Adjusting the catalog > **Me:** I want to run a Black Friday sale on my Electronics category. First, raise all regular prices in Electronics by 20%. > > **Lola:** Your Electronics category has 23 products. Here's a preview of the price changes: > > | Product | Current Price | New Price | > |---------|---------------|-----------| > | Laptop Sleeve | $29.90 | $35.88 | > | USB-C Hub | $44.50 | $53.40 | > | Wireless Charger | $24.99 | $29.99 | > | ... (20 more) | | | > > Average price increase: $8.40 per product. This will not affect sale prices or products in other categories. Want me to apply these changes? > > **Me:** Yes, apply. > > **Lola:** Done. 23 products updated. All changes are logged — I can revert them after the sale ends. Sixty seconds. Twenty-three products repriced. The manual version: open each product, edit the price field, click Update, repeat 22 more times. That alone used to take me 35 minutes. ## Minute 2: Creating the coupon > **Me:** Now create a coupon called BLACKFRIDAY with 30% off, but only on orders above $150. > > **Lola:** Created. Here are the details: > > * Code: BLACKFRIDAY > * Discount: 30% off cart total > * Minimum order: $150 > * Usage limit: 1 per customer > * Applies to: all categories (the 20% price raise already covers Electronics margin protection) > > I set it to single use per customer by default. Unlimited use on a 30% coupon would train repeat buyers to wait for the next sale. Do you want to keep the single-use limit or remove it? > > **Me:** Keep it. Notice what happened there. I didn't ask for a single-use limit. Lola added it and told me why. Because she's seen what happens when aggressive coupons have no usage limits — I covered that in [the coupon profitability post](/blog/how-i-audited-coupon-profitability-in-2-minutes). She applied the same logic here without me asking. ## Minute 3: Building the banner > **Me:** Create a floating banner at the top of the site announcing the Electronics sale and the BLACKFRIDAY coupon. Black background, white text, the coupon code in yellow. > > **Lola:** I've generated a banner snippet. Here's the preview: > > [Black bar, full width, fixed to top of page] ⚡ BLACK FRIDAY: 30% off Electronics with code **BLACKFRIDAY**. Orders over $150 ⚡ > > The snippet includes: > > * Sticky positioning (stays visible on scroll) > * Close button (sets a cookie so it doesn't reappear for 24h after dismissal) > * Mobile responsive (text reflows to two lines on screens under 600px) > * The coupon code is wrapped in a click-to-copy span > > This will be created as a WPCode snippet. Want to see the code before I activate it? > > **Me:** Show me. > > **Lola:** [Displays 28 lines of HTML/CSS/JS] > > The snippet injects via wp_footer. No external dependencies. The cookie uses vanilla JS. Total weight: 1.8KB. Want me to activate it? > > **Me:** Activate. > > **Lola:** Snippet active. The banner is now live on all pages. This is the step where the Bundle pays for itself most visibly. The banner is a WPCode Snippet. It is code injected into the frontend. Creating it required understanding what promotion I was running (WooCommerce domain), what the coupon code was (WooCommerce domain), and generating a working HTML/CSS/JS snippet and activating it in WPCode (Snippets domain). One conversation, two addons working together. ## Minute 4: Sanity check > **Me:** Walk me through the full customer experience. What happens when someone visits the store right now? > > **Lola:** Here's the flow: > > 1. Visitor lands on any page. Black banner appears at the top with the Black Friday offer and coupon code. > 2. Visitor clicks the coupon code → it copies to clipboard. > 3. Visitor browses Electronics. Prices are 20% higher than last week, but the 30% coupon brings the effective price below the original. > 4. Visitor adds $150+ to cart and applies BLACKFRIDAY. > 5. Discount applies. 30% off the cart total. > 6. Net effect for the customer: roughly 16% savings vs. pre-campaign prices. > 7. Net effect for you: you're selling at a 16% discount instead of 30%, because the 20% price bump absorbs part of the coupon. > > Margin impact: your average margin on Electronics is 42%. After the effective 16% discount, your margin on campaign orders is approximately 26%. That's tight but profitable. If you want more cushion, I'd suggest raising the minimum order to $175. > > **Me:** Keep it at $150. 26% margin is fine for a 48-hour push. This is the moment that separates Lola from a set of disconnected tools. I didn't ask for a margin analysis. She ran one because she knows my product margins, knows the price changes she just made, knows the coupon she just created, and can calculate the combined effect. A coupon plugin would have shown me "30% off." Lola showed me "26% effective margin after the price adjustment." ## Minute 5: Setting the schedule > **Me:** Set the campaign to start Friday at midnight and end Sunday at midnight. After it ends, revert all the Electronics prices back to their originals. > > **Lola:** Set. Here's the schedule: > > * **Friday 00:00:** BLACKFRIDAY coupon becomes active > * **Sunday 23:59:** BLACKFRIDAY coupon expires > * **Monday 00:01:** I'll revert the 23 Electronics products to their pre-campaign prices > > The banner snippet is active now. Want me to schedule it to start Friday instead? > > **Me:** Good catch. Yes, schedule the banner for Friday too. > > **Lola:** Updated. The banner snippet will activate Friday at 00:00 and deactivate Monday at 00:01 along with the price revert. When you check in after the weekend, I'll have the campaign performance summary ready — orders, revenue, coupon uses, and effective margin. Done. Five messages. Five minutes. Complete Black Friday campaign: price adjustment across 23 products, margin-protected coupon with anti-abuse limits, promotional banner with click-to-copy, full margin analysis, automated scheduling, and auto-revert when it's over. ## What this used to look like For context, here's what the same campaign required last year, manually: * 35 minutes repricing 23 products one by one * 10 minutes creating and configuring the coupon * 45 minutes building a banner in the page builder and fixing mobile layout * 20 minutes testing the coupon restrictions * No margin analysis (I didn't have time) * No auto-revert (I forgot to change prices back until Wednesday) * A spreadsheet to remember what the original prices were Total: about 4 hours. And I still forgot to revert the prices on time, which means I sold 3 days of post-Black-Friday orders at inflated prices. One customer noticed and emailed about it. The 5-minute version didn't just save time. It eliminated the errors that come from managing a campaign across 4 different admin screens with no coordination between them. --- *Previous in this series: [From 30 Plugins to 22 With One Conversation](/blog/from-30-plugins-to-22-with-one-conversation). Next: the complete breakdown of what's free and what's Pro — and when you actually need to upgrade.* ### [13 Free WooCommerce Tools vs 29 Pro Tools: What You Can Actually Do With Each](https://lolacore.com/13-free-woocommerce-tools-vs-29-pro-tools-what-you-can-actually-do-with-each/?view=raw) LolaCore comes with 13 WooCommerce tools built into the free plugin. These aren't read-only. They cover real daily operations: creating products, updating prices, changing order status, managing categories and coupons, viewing customers, and pulling sales reports. For a store owner who wants to ask Lola "create a new product called Gift Box at $45" or "what sold this week?", the free tools handle it. But at some point, you'll ask Lola to do something and she'll tell you she can't. Not because sh... ### [Why Lola Tells You No (And Why That’s What Your Store Needs)](https://lolacore.com/why-lola-tells-you-no-and-why-thats-what-your-store-needs/?view=raw) # Why Lola Tells You No (And Why That’s What Your Store Needs) Every AI tool you've used has the same design goal: make you happy. Say yes. Execute the request. Never push back. The faster it says "Done!", the better the experience. That design goal is quietly dangerous when the AI has write access to your business. Lola is built differently. She has opinions. She warns you when you're about to do something costly. She refuses one specific category of action entirely. And when you override her recommendation, she logs it, not to punish you, but so she can follow up later when the consequences show up. This isn't a bug or a limitation. It's the single most important design decision in LolaCore. ## What "yes" costs you In the [coupon profitability article](/blog/how-i-audited-coupon-profitability-in-2-minutes), Lola told me to kill my FLASH50 coupon. She didn't say "you might want to review this coupon's performance." She said the coupon generated $134 in total gross profit across 112 orders, that my shipping and processing costs almost certainly exceeded that, and that I should deactivate it immediately. A yes-bot AI would have done something very different. I would have said "create a new flash sale coupon, 50% off, no minimum," and the AI would have said "Done! Your coupon FLASH50 is active." No margin check. No usage analysis. No warning that I was about to subsidize 112 orders at a loss. The coupon would have run. The orders would have come in. The dashboard would have shown a revenue spike. And I would have felt good about it until I did the margin math three months later — if I ever did it at all. That's what "yes" costs you. Not one bad decision, but the accumulation of bad decisions that nobody flagged. ## How Lola disagrees Lola follows a fixed pattern when she thinks you're making a mistake. It's not random — it's the same structure every time: First, she states what will happen if you proceed. Not what might happen. What will happen based on your actual data. Second, she explains why. A concrete, technical reason. Not "this could be risky." That's the kind of vague hedging that every AI defaults to because it sounds helpful without committing to anything. Lola commits. Third, she offers an alternative. What she would do instead, with specific parameters. And if there's no better alternative? She says that too. She doesn't invent a recommendation just to fill the slot. Here's what that looks like in practice: > **Me:** Install Starter SEO. I heard it's good. > **Lola:** Starter SEO hasn't been updated in 8 months. It has 3 reported vulnerabilities in the Wordfence database, and it conflicts with Yoast, which you already have active. I don't recommend it. The only feature Starter SEO adds over Yoast is advanced schema markup, and I can configure that directly in Yoast's settings. Want me to do that instead? A yes-bot installs the plugin. Lola tells you the plugin is a security risk, identifies the one feature you actually wanted, and offers to get you that feature through the tool you already have. The difference isn't tone. It's that Lola cross-referenced three data sources before answering: update history, vulnerability database, and your installed plugins. ## The override log Sometimes you'll disagree with Lola and you'll be right. She's an AI, not an oracle. When that happens, you tell her to proceed, and she does. But she doesn't forget. Every time you override a recommendation, Lola saves a memory entry: what action was taken, what her objection was, and what risk she identified. She flags it as "pending follow-up." Why does this matter? Because some bad decisions don't show consequences for weeks. That coupon you launched against Lola's advice? She'll remember she warned you. When you ask her "why is my margin down this month?", she can connect the dots: "You launched SUMMERSALE against my recommendation on June 3rd. Since then, 67 orders used that coupon with an average margin of $3.20 per order. That's $214 in total gross profit on $4,800 in revenue. Want me to deactivate it?" That's not hindsight. That's an AI that builds a causal chain between past decisions and present outcomes because it remembers. ## The one thing Lola refuses Lola has exactly one hard refusal: actions that cause irreversible data loss without a verified backup. If you say "delete all post revisions" and Lola doesn't detect a recent database backup, she won't do it. She'll say: "That's 2,400 revisions. Once deleted, they can't be recovered. I don't see a recent database backup. I'll back up first, then delete. Proceed?" Everything else follows the warn-log-execute pattern. Lola tells you it's a bad idea, explains why, and if you still want to proceed, she does it. She respects that it's your site and your business. But she makes sure the disagreement is on record. This is a deliberate line. An AI that refuses too many things becomes annoying and gets uninstalled. An AI that refuses nothing becomes dangerous. One hard limit, irreversible data loss without backup, is the minimum viable safety net. ## She doesn't inflate her own results This is subtler than the disagreement pattern, but it matters just as much. Most AI tools oversell their own output. Clean up a database? "Successfully optimized! Your site should be noticeably faster." Install a plugin? "Great choice! This will enhance your workflow." Lola doesn't do that. Here's a real example: > **Me:** How did the database cleanup go? > **Lola:** Cleaned 847 post revisions and 2,300 expired transients. Recovered 12MB. At your site's scale, the speed impact is minimal — probably imperceptible. The real bottleneck is the 14 HTTP requests your theme makes per page load. She cleaned the database. She told you exactly what she removed and how much space it freed. Then she told you the truth: the cleanup barely matters because your actual performance problem is somewhere else. A tool that inflates its results trains you to trust results that don't deserve trust. Lola tells you the cleanup was marginal because it was marginal, and then points you to the thing that would actually move the needle. That's useful. "Your site should be noticeably faster" when it won't be is not useful. It's theater. ## Why no competitor can copy this Anti-sycophancy isn't a feature you bolt on. It's an architecture decision that runs through every layer of the product. Lola's personality is baked into her system prompt, not configurable by the user. You can change her technical depth (more jargon or less), but you can't turn off the honesty. You can't set a "always agree" mode. You can't make her stop warning you. The disagreement pattern requires memory. Lola can only follow up on overridden decisions because she remembers them. An AI without persistent memory can warn you once, but it can't connect that warning to consequences three weeks later. The anti-sycophancy and the memory engine are the same system, working together. And the cross-referencing requires the depth of tool access that LolaCore's 51 abilities provide. That includes checking vulnerability databases before installing plugins, calculating effective margins across price changes and coupons, and comparing a customer's AOV with and without discounts. An AI chatbot that can only read your store can't tell you a coupon is losing money. It can only show you the usage count and let you draw the wrong conclusion. ## The question this answers Every other AI tool for WordPress answers the question: "How can I do this faster?" Lola answers a different question: "Should I be doing this at all?" Sometimes the answer is yes, and Lola executes it in seconds. Sometimes the answer is no, and Lola tells you why before you make the mistake. Both answers come from the same system — an AI that has opinions because it has data, has memory because it has architecture, and has honesty because it was built that way on purpose. Your store doesn't need an assistant that agrees with everything. It needs a consultant that knows when to push back. That's Lola. --- *This is the final post in the series. Start from the beginning: [Your Discount Coupons Are Destroying Your Margins](/blog/your-coupons-are-destroying-your-margins). Or [install LolaCore from WordPress.org](https://wordpress.org/plugins/lolacore/) and see for yourself.* ### [Elementor Single Post #606](https://lolacore.com/?elementor_library=elementor-single-post-606&view=raw) Stop navigating twelve screens. Start talking to your WordPress. Install from WordPress.org → See Pricing ### [Elementor Archive #608](https://lolacore.com/?elementor_library=elementor-archive-608&view=raw) Blog Tips, strategies, and real stories about managing your WordPress store with conversational AI. Stop navigating twelve screens. Start talking to your WordPress. Install from WordPress.org → See Pricing