Custom development
AI personalisation & dynamic pricing
Prices and recommendations that vary by customer, without the store telling one story to buyers and another to search engines.
Scoped and quoted per project. Fixed quote before any work starts. No hourly billing.
A custom WooCommerce dynamic pricing plugin exists because pricing rules are specific to a business in a way off-the-shelf plugins are not. Volume breaks per customer group, contract prices for named accounts, a margin floor that must never be crossed regardless of what a promotion says, a wholesale tier that shows ex-VAT prices and its own minimum order. Generic plugins model some of that, then you spend longer fighting the parts they do not model than the build would have taken.
Recommendations sit in the same place. “Customers also bought” is a query, not a subscription — and one that answers from your own order history is usually more useful than a hosted engine that has seen three weeks of your traffic. Where an AI model genuinely helps, we use it for the parts models are good at, such as grouping products by how they are described, and keep the ranking itself explainable.
Typical build
- Pricing rules as code: customer groups, volume breaks, contract prices, margin floors, scheduled campaigns.
- One resolution order, documented, so it is always clear which rule won and why a customer sees this price.
- Correct public prices in schema and feeds, with personalised prices kept behind login — never contradicting each other.
- Recommendations computed from your own order and catalogue data, with the reasoning visible rather than a black box.
- B2B display rules: ex-VAT or inc-VAT by group, minimum order values, per-account payment terms.
Good fit if…
- You sell to both consumers and businesses from one catalogue and the pricing plugin is fighting you.
- You have negotiated prices for named accounts that currently live in a spreadsheet.
- You want product recommendations without sending your order history to a third-party service.
How it connects to AI visibility
Personalised pricing is where stores accidentally break their own feeds. If a logged-out crawler sees one price and the feed carries another, Merchant Center flags a mismatch and assistants quote a number your customers never pay. We define one public price that schema, feeds and the crawler-visible page all agree on, and keep everything customer-specific behind authentication — which is what the AI Visibility Setup validates against.
FAQ
Straight answers to the questions store owners ask
Does personalised pricing hurt SEO or AI visibility?
Not if the public price stays consistent. What causes problems is cloaking — showing crawlers a different price from buyers — and price data that disagrees between the page, the schema and the feed. Both are avoidable by design.
Can you use an existing dynamic pricing plugin instead?
If one covers your rules, yes, and we will say so. We propose a build when the rules do not fit the plugin’s model, or when working around it has already produced a layer of snippets nobody understands.
Is “AI personalisation” just a recommendation widget?
Often that is all it needs to be. We use models where they earn their place — clustering products from their descriptions, for example — and ordinary queries everywhere else, because an explainable recommendation is easier to fix when it is wrong.
Custom development
Tell us what should happen automatically.
Describe the job someone does by hand, or the system your store cannot talk to. You will get a reply from the engineer who would build it, within one working day.
Describe your automation