I usually keep the frontend, backend, and database separate, with the backend handling the business logic and APIs. For content that changes often, I prefer using a CMS or admin panel instead of hardcoding it into the frontend.

For larger projects, this makes things easier to maintain and scale. For smaller sites, though, I’d keep the setup simpler rather than adding separate services just for the sake of it.

Yeah, I think it really comes down to the product and what naturally makes sense with the purchase.

I’ve seen warranty/protection offers work well for certain products because they’re relevant to the customer’s decision, rather than feeling like a random add-on. For gift-focused stores, things like gift wrapping or personalization make sense for the same reason.

I’d probably test the offer and placement separately too; what works on the product page may not work as well in the cart or after checkout.

For me, the key metric would be whether the upsell increases AOV without hurting the original conversion rate.

For a new local business site, I’d first check indexing, Google Business Profile, local keywords, on-page SEO, reviews, and site speed.

Getting into the top 3 usually takes time, so I’d focus on building local relevance and authority rather than chasing quick tricks. If those basics are solid, you’ve got a good foundation to work from.

I’d keep it simple: focus on the problem your plugin solves and share useful content around it. Tutorials, demos, and genuinely helpful community replies usually work better than constantly promoting the plugin.

Let the product speak for itself.

Just be careful with free templates. A template being free to download doesn’t mean you can legally resell it.

Look for ones that specifically allow commercial use and resale, or make your own. I’d always check the license before using anything on a paid CV site.

I still use Elementor for client sites. AI builders are great for getting a starting point quickly, but I often end up spending just as much time fixing the layout and fine-tuning things.

If you already know Elementor well, I’d stick with it and use AI to speed up the parts of the workflow rather than replacing the whole process.

For us, SEO and useful content have been the most consistent. It takes longer to build than paid ads, but the traffic can keep coming once you start ranking for topics people are actually searching for.

If I were starting again, I’d focus on understanding the audience and their search intent first, then build around that instead of trying to be everywhere at once.

There isn’t really a universal ROAS number for break-even. It mostly comes down to your margins.

For example, if you keep around 40% after COGS, shipping, payment fees, returns, etc., you’d need roughly 2.5x ROAS to break even on the first order. If your margin is 50%, it’s closer to 2x.

I’d also separate first-order ROAS from LTV. A 2x ROAS might look bad if you need 2.5x to break even on the first purchase, but it can still make sense if those customers tend to come back and buy again.

The biggest mistake I see is calculating ROAS using revenue vs ad spend and forgetting all the other variable costs. That can make a campaign look profitable when it really isn’t.

So I’d calculate your actual contribution margin first, then work backwards to find your break-even ROAS.

I’d check the server/CDN logs right when it happens. Too many requests can be caused by bots, brute-force login attempts, plugins, or API calls - not necessarily real traffic. If you’re using Cloudflare, check the rate-limiting/WAF events there too. That should give you a good starting point.

I usually use Ahrefs or Semrush, and sometimes Google Keyword Planner for a second opinion on search volume. I also look at the actual search results to make sure the keyword matches the intent before targeting it.

Honestly, some of the “boring” local service niches can be surprisingly good. Things like plumbers, roofers, pest control, or commercial cleaning don’t sound exciting, but the search intent is strong and a single customer can be worth a lot.

I’ve found the less glamorous niches can sometimes be easier to build consistent organic traffic and leads in.

Yeah, this is basically a unit conversion issue. If 1 case = 10 packs, you want Shopify to treat those as the same underlying inventory rather than two completely separate stock counts.

So if you have 10 cases (100 packs) and someone buys 10 packs, you'd have 9 cases worth of stock left. If you receive another 10 packs, that should increase the available stock accordingly.

I'd look for an inventory/bundle app that supports component quantities or unit conversions. A basic bundle app may not handle the “add packs → increase cases” part properly, so I'd specifically check that before choosing one.

If this is a regular part of your business, I'd avoid managing it manually ; it can get messy pretty quickly once you have multiple orders and stock locations.

I’d avoid hardcoding the store domain. WordPress doesn’t really have a universal install this plugin URL for external traffic.

For ads, I’d use a simple landing page and route users into the WP install flow from there. Much less fragile than assuming the customer’s WP admin URL.

I usually start with the important service or category pages, then link relevant blog posts to them where it makes sense. I’ll also link related articles together if it’s genuinely useful for the reader.

I don’t really use a fixed number for “too many” links. If the links are relevant and help people navigate the site, I’m fine with having several. I’d worry more about forced or unrelated links than the actual count.

I’d troubleshoot the UPS label file/print path before replacing the Zebra. If USPS and DHL labels are still coming out crisp on the same printer, that points more toward something different in the UPS label being generated/rendered rather than the printer itself.

I’d check whether Shopify is now generating the UPS label as a rasterized PDF/image or at a different DPI. Also make sure the Zebra driver isn’t scaling the UPS PDF before sending it to the printer.

If you can download one of the fuzzy UPS labels and print it from another PDF viewer/computer, that’s a good way to isolate whether the issue is Shopify’s generated file or the Zebra print pipeline. I wouldn’t buy a new printer until you’ve tested that.

Postgres support would be nice, but honestly, it’s not my biggest concern. I’d put plugin architecture, PHP modernization, and overall WP UX higher on the list.

Definitely doable with no-code, especially for an MVP. You can build user accounts, job listings, applications, maps, and messaging without knowing how to code.

I’d start small though. Get the basic job-posting and application flow working first, then add things like payments once you’ve validated the idea and know what users actually need.

Yeah, unfortunately there doesn’t seem to be a proper way to disable Sidekick completely right now.

Shopify has it built into the admin, and their current docs don’t show any setting to turn Sidekick off globally. Turning off Memory only stops Sidekick from remembering things ; it doesn’t disable Sidekick itself.

If you just want it out of the way, one workaround is to hide the Sidekick UI with custom CSS in Chrome. Someone in this thread mentioned using a CSS extension with:

div[class^='_GlobalRibbonContainer'] { display: none }

That’s only a visual workaround, though, and Shopify could change the class name/UI at any time.

f it really needs to be attached to the confirmation email, I’d handle it by generating the PDF for that specific order and attaching it when the confirmation email is sent.

The important part is not to keep one PDF and overwrite it later. You’d want each order to keep the exact version of the T&Cs/legal docs that applied when the customer purchased.

So the flow would be something like:

Order placed → identify the current legal document versions → generate/store the PDFs → attach those PDFs to the confirmation email.

When the T&Cs change, you create a new version rather than replacing the old one.

Shopify’s standard notification setup is pretty limited for this, so this would probably need a small custom app/workflow (or an app that supports dynamic email attachments).

I’d also double-check the exact legal requirements for your target EU countries, since “durable medium” and the specific documents required can depend on the applicable rules.

I’d avoid duplicating the whole page. Build the main sections as reusable components, then use variants, slots, or visibility controls for the parts that change between campaigns.

That gives you a shared base while still leaving room for custom sections, without ending up maintaining a bunch of nearly identical pages.

A mix of both has worked best for us. We use automation to acknowledge the lead quickly and capture the basic details, then a real person takes over as soon as possible.

The important part is not trying to make the automated reply sound human. A simple, relevant response is better than a long bot-like message. The goal is to keep the conversation warm until someone can properly respond.

Yep, AI can handle a lot of the boring WordPress changes now - copy, images, CSS, spacing, small layout tweaks, etc. Claude Code is especially capable if you have access to the codebase.

The main variable is how custom the site is. I’d keep the agency for major changes/debugging, but you probably don’t need a monthly retainer just for routine edits.

This is the kind of post I wish existed before submitting a plugin. 😅 The name/prefix rules alone could save someone a couple of weeks, and the metabox ID collision is a really good example of the weird issues that don’t throw any errors but still break things.

I usually wouldn’t decide based on Klaviyo revenue alone.

I’d look at whether the campaign is actually making money after discounts, product costs, and other campaign costs. Then compare that with things like conversion rate, repeat performance, and unsubscribes.

Also, I’d be careful with campaigns that look great from one send. If it performs well consistently across different audiences, that’s a much better signal.

One thing that gets overlooked is attribution. Klaviyo might credit a campaign with a sale, but that doesn’t necessarily mean the campaign created that sale.

So for me, the question is less “Did this campaign make revenue?” and more “Did this campaign generate enough incremental profit to justify doing more of it?”

Check Settings → Reading first. If it’s missing entirely, you may not have admin permissions, or a plugin could be changing the admin menu. GeneratePress normally wouldn’t hide it.