Written by people who run a real UK trading business. Trade pricing, order ops, getting paid, and the tools that actually help.
Five minutes on the public register before you give credit, pay a deposit or sign a contract: status, registered office, filing history and overdue accounts.
Before AI answers a single customer, sort every job into three piles: what it may do alone, what it drafts for you to approve, and what it must never touch.
Describing a tool to an AI and getting working software back is now realistic for a small firm. The rules that keep it safe: data, secrets, testing and ownership.
Not which tools to buy, but how they fit together: an assistant, the suite you already use, your systems of record, a connector between them, and the security layer.
Business Profile, a plain website, honest location pages, real reviews and Search Console. What Google itself says matters for local results, and what to ignore.
What actually helps your business turn up when people ask ChatGPT, Claude or Google’s AI features: let the right crawlers in, write answer-first pages, keep facts consistent.
Five minutes on the public register before you give credit, pay a deposit or sign a contract: status, registered office, filing history and overdue accounts.
Automated chasing goes wrong in a small number of predictable ways. The exclusion list to build on day one, so it never embarrasses you.
Automated estimate chasing depends entirely on the dates you put on the estimate. How to choose expiry dates that create useful deadlines rather than decoration.
The structure of a follow-up email that gets replies: what to open with, what to add, what to ask, and the four phrases to delete on sight.
Too few and you leave work on the table; too many and you damage the relationship. A defensible cadence, and the signals that should change it.
QuickBooks is the default back office for American small business. Estimates that expire unanswered are its default revenue leak. A practical, automated fix.
Using QuickBooks Online with EU business customers? Estimates stall in approval chains and formal processes. How automated follow-up fits European B2B manners.
EU business customers decide slowly and formally. Why well-timed, well-mannered quote follow-up works especially well in European B2B — and how to automate it from Xero.
Plenty of UK small businesses run on QuickBooks Online. Its estimates have the same fatal gap as everyone else’s quotes: nobody chases them. Here’s the automatic fix.
British politeness is costing you accepted quotes. Why UK firms on Xero under-chase, and how to automate the follow-up without sounding pushy.
Running a US business on Xero? Your quotes deserve the same follow-up discipline your sales pipeline gets. How automated quote chasing works stateside.
Xero happily creates quotes but won’t chase them. Here’s how to follow up expired and unaccepted quotes automatically so “not yet” doesn’t quietly become “never”.
QuickBooks Online tracks estimates but leaves the chasing to you. Here’s the follow-up step that quietly recovers deals — and how to make it automatic.
Most small businesses send quotes and estimates, then never follow up. Here’s how much that costs — and how to fix it without hiring anyone.
Paid, unpaid, pending, resend — if payment status lives anywhere other than the order itself, someone is maintaining a spreadsheet that will eventually be wrong.
Before AI answers a single customer, sort every job into three piles: what it may do alone, what it drafts for you to approve, and what it must never touch.
Describing a tool to an AI and getting working software back is now realistic for a small firm. The rules that keep it safe: data, secrets, testing and ownership.
Not which tools to buy, but how they fit together: an assistant, the suite you already use, your systems of record, a connector between them, and the security layer.
A plain-English guide to putting AI to work in a small UK business: where it saves time, where it doesn’t, and how to find your first wins.
The categories of AI tool that actually earn their keep in a small UK business, how to choose between them, and the ones you may already pay for.
The gap between playing with an assistant and changing how the work gets done, and the four things that close it.
Six tools, nobody sure what any of them do. A one-hour audit that cuts the bill without losing anything you use.
An AI audit (or AI assessment) finds where AI can save your business time and money, with the savings costed. What’s in one, and when it’s worth it.
Six repeating mistakes, in the order they tend to happen, and the smaller shape of project that actually sticks.
The admin that eats a trade business’s week, quoting, chasing, scheduling and invoices, and the AI and automation that take it off your hands.
Where the hours go in a small practice or agency, which of them AI can take, and the client-confidentiality questions to settle first.
Product copy, customer questions, stock and reporting: five places AI helps independent shops and e-commerce sellers get time back.
Where AI speeds up an accountancy or bookkeeping practice, chasing, capture and drafting, and how to use it without putting client data at risk.
Listings, supplier price lists, customer questions and order admin — the jobs worth automating first in a small trading business.
A realistic look at the hours AI can give back to a small business each week, and how to estimate it on your own numbers rather than hype.
Turn an hour of quoting into minutes: how to use AI to draft accurate, on-brand quotes from your price list and past jobs.
Stop the inbox and the phone eating your day: how AI can draft replies, answer common questions and catch missed calls for a small business.
A practical sorting rule, with real examples on both sides of the line and the jobs to keep well away from it.
You don’t need to code to benefit from AI. What a non-technical owner can genuinely do today, and where to get a hand.
The number every automation decision depends on, and the three ways small-business owners get it wrong.
You can get real value from AI without a big bill. The free and cheap ways a small UK business can start, and when paying is worth it.
A straight answer with the arithmetic shown, including the cases where the honest answer is no.
No code and no jargon. What the Model Context Protocol actually is, why it matters if you run stock and orders for a living, and what changes on the day you switch one on.
Not with a tool. Start by finding out where your week actually goes, then pick the two jobs AI can take off you first.
Business Profile, a plain website, honest location pages, real reviews and Search Console. What Google itself says matters for local results, and what to ignore.
What actually helps your business turn up when people ask ChatGPT, Claude or Google’s AI features: let the right crawlers in, write answer-first pages, keep facts consistent.
A hosted connector that lets Claude read your live Linnworks orders, stock, purchase orders and returns, with previewed changes on Pro (coming soon). What it does, what it doesn’t, and the waiting list.
Why the export-filter-report cycle costs more than anyone measures, which questions it suits, and what replaces it when an assistant can read the data directly.
The practical payoff of an MCP connector is the questions that stop needing an export. Thirty real ones across orders, stock, buying, customers and returns.
What changes in the working day once an AI assistant can read your live Linnworks data — and the handful of things it still will not do for you.
When the customer walks out with the goods, a picking step is fiction. Auto-processing counter sales keeps Linnworks accurate without warehouse theatre.
Where should wholesale tier prices live? Inside Linnworks itself, as extended properties on each stock item. Here is why that pattern beats a separate pricing database.
An honest assessment for sellers running a handful of orders a day — including the five situations where buying our connector would be a waste of £249.
Three ways to deal with trade paperwork, and a method for comparing them on your own numbers rather than on anybody’s marketing.
A full DIY method you can follow this week — then an honest account of what paying for one saves, and who should not bother.
Beta places get sold as a bargain. For some businesses they are a distraction with a cost attached. Four honest reasons to say no, and what a good beta tester actually gets.
The rough shape of the market, what each price band buys, and the questions to ask before you pay anyone.
Two ways to let an AI assistant read your order management system. The real differences are where your data goes, what it costs over three years, and who can change it.
The question nobody asks before signing up and everybody asks too late. How to check your exit, what a usable export looks like, and how to build your own safety net.
A practical checklist for judging a young product when there are no reviews, no case studies and no analyst reports to hide behind.
“Beta” has been stretched until it means almost nothing. A working definition, the four things a beta should never do to your money, and when to walk away.
Most wholesalers take orders through four channels at once and have optimised none of them. How to work out which to invest in first.
Businesses sometimes ask which accounting system is better for chasing quotes. The honest answer is that the question is the wrong way round.
If you need faster B2B order entry, there are four broad approaches. An even-handed look at what each is good at and where each runs out of road.
An honest decision guide for Linnworks sellers wondering whether a counter order tool is worth it — including the situations where it plainly is not.
No competitors, no feature tables — just the time, the recovery rate and the break-even point on automating quote follow-up. Including when manual wins.
An honest test for wholesalers wondering whether to move trade pricing off a spreadsheet. Including the cases where the spreadsheet is still the right answer.
Three broad routes to managing trade prices, what each is genuinely good at, and an honest account of who should pick which.
Follow-up software all promises the same outcome. Here is what actually separates the options, and an honest view of when you do not need any of it.
What to look for in trade counter and B2B order-entry software if you run on Linnworks — and the questions that separate a real fit from a rebadged retail till.
Notes from building GraftG at Green & Home Ltd: the assumptions that did not survive, the ones that did, and what we would tell anyone building for the trades.
Free beta places are not generosity, and they are not a discount. What a small software team is actually buying with them — and what that tells you before you take one.
Green & Home Ltd never set out to be a software company. Here’s how running a real trading business on Linnworks led to a portfolio of tools other UK businesses now use.
A single stock question traced from the chat window to the Linnworks API and back, with the failure points named. No code required to follow it.
Not a like-for-like comparison. One gives people a way to ask questions; the other makes a specific thing happen reliably. How to tell which job you have.
How a dev shop can package AI integration for Linnworks clients — what to scope, what to charge for, what to refuse, and the licensing that makes it repeatable.
Before you point an AI assistant at live order and customer data, the questions worth answering — and why deploying without the write tools is a legitimate option.
A practical pre-flight checklist for teams deploying an MCP connector to their own infrastructure — credentials, scope, logging and the questions your security reviewer will ask.
European agencies adding AI to client Linnworks accounts face one question first: where does the data flow? A per-client, self-hosted MCP deployment answers it cleanly.
UK Linnworks sellers want Claude answering questions about orders and stock — without their warehouse data passing through a third party. Self-hosting an MCP server is the clean answer.
US sellers and dev teams on Linnworks can wire Claude straight into orders, stock and customers — hosting the connector themselves on Cloudflare Workers for control and cost.
A competent developer can build a Linnworks MCP server in two to three weeks. The source costs £249. The decision is about more than the price gap.
For dev shops and in-house teams: how to deploy your own Linnworks MCP server on Cloudflare Workers and connect Claude to live Linnworks data — without weeks of integration work.
The practical payoff of a Linnworks MCP server is the questions it answers instantly. Ten real ones, from reorder points to refund patterns.
Strip away the protocol jargon: MCP lets an AI assistant query your live Linnworks data in plain English. What that concretely changes for an ops team.
Admin done at the weekend feels free because no money changes hands. Here is how to work out what it actually costs you — using your numbers, not ours.
New software does not tidy up after you. A one-evening checklist for getting your paperwork into a state where any system — or any bookkeeper — can actually help.
Quotes, chasing, job notes, supplier emails and the paperwork that eats your evenings — what AI can realistically take off a small contractor.
Most trade admin tools are not bad software. They are software designed for a desk and handed to someone standing in a loft. A design argument, and a test you can apply in ten seconds.
Most trades lose jobs to speed, not price. Why a quote sent from site beats a better quote sent on Sunday — and how to make same-day quoting realistic.
A UK service runs a tradesperson’s whole back office over WhatsApp. The model — mileage logs, instant quotes, receipt capture by message — maps neatly onto US contractor pain.
Across the EU, sole traders drown in the same paperwork — mileage, quotes, receipts, VAT records. A UK service does it all over WhatsApp. Here’s the model and what travels.
Mileage, quotes, receipts, invoices — the average UK tradesperson’s evening. How doing the lot over WhatsApp changes it, with HMRC and MTD in mind.
The request every wholesaler gets weekly. What to send, what to leave out, and how to produce it without building a document by hand.
A cost increase lands in an email. What to do in the first hour, the first day and the first week so your margins do not quietly disappear.
The decision that quietly determines whether your pricing stays manageable. A test you can apply in the moment, and how to undo a bespoke price you regret.
US wholesale runs on negotiated pricing and column lists. How named tiers with formulas bring order to distributor pricing — without losing the flexibility your accounts expect.
Selling B2B across EU borders multiplies your price-list problem — currencies, VAT-exclusive norms, per-country expectations. Why a formula-driven tier engine is the sane answer.
Most UK wholesale price lists still live in Excel. Why that clashes with how UK trade actually works now — VAT-registered accounts, digital records, Linnworks warehouses — and the tidier way.
Tier structures fail at the mapping step: hundreds of accounts, no rule for who goes where. A defensible method you can run through your customer list in an hour.
A back-of-the-envelope look at the time and margin a typical UK wholesaler loses to looking up trade prices by hand — and the two-tool fix.
Nobody prices below cost on purpose. It happens through stale costs, generous overrides and old quotes — and a margin warning at the point of sale is the backstop.
Costs went up and your prices have to follow. How to execute a price rise across a tiered catalogue — cleanly, defensibly, and without ambushing your best customers.
The spreadsheet grew for good reasons — and now it is the riskiest file in the business. A practical, low-drama path from pricing-in-Excel to a proper tier engine.
CSV import and export is how real pricing work gets done — supplier updates in, customer price lists out. The habits that keep it clean.
A MOQ that lives in your terms and conditions is a suggestion. A MOQ the order screen enforces at the moment of sale is a policy. How per-tier minimums work.
Trade pricing is a negotiation with a memory. Software that remembers the last price you charged each customer for each SKU removes the friction and the awkwardness.
Charm pricing is retail folklore — but rounding formula-driven wholesale prices to clean endings matters for a different reason: credibility.
The two ways to drive a price tier by formula — markup from cost, or discount from RRP — and when each one is the right choice for a wholesale catalogue.
What price tiers are, why nearly every B2B seller needs them, and how to design a tier ladder that fits how your customers actually buy.
Switching the counter from a duplicate book to a live order system. What to do in week one, what to do in week two, and what to leave alone entirely.
Linnworks gives you one retail price per SKU. Here’s how to run proper per-customer trade tiers on top of it — Trade, Wholesale, RRP and beyond — without living in a spreadsheet.
Cloud order systems need a connection. A practical outage plan for trade counters that keeps the queue moving and gets the orders in afterwards.
A customer you know exists does not appear in search. The usual causes and the workaround that keeps the order moving.
Import errors, wrong values, half-updated catalogues. The CSV issues that cause nearly every failed price import.
Stock in Linnworks disagreeing with the shelf, the POS or a report? The five usual causes, in the order worth checking.
An EU business is at your counter or on the phone. What tax goes on the order? How to set up your process so the answer is automatic, not a debate.
An integration that worked yesterday now cannot authenticate. What invalidates a Linnworks install token, and how to restore access.
Running more than one location? Here is why totals differ between views, and how to keep counter staff out of trouble.
You set up tiers but the counter is still charging standard prices. Work through these in order.
Pushed tier prices or custom fields into Linnworks extended properties but cannot see them? Five things to check.
Reorder relies on the Linnworks processed-orders index, which lags. What that means day to day, and the workaround.
Ex-VAT and inc-VAT confusion, per-line rates, delivery charges. Why trade order VAT surprises people, and how to check it properly.
Two identical orders where there should be one. The four common causes, and how to remove the duplicate without wrecking your stock figures.
Seeing 429s or sluggish responses from Linnworks? What the limits mean, what usually causes bursts, and the fixes.
Wrong price on a line? Work backwards through the four things that set it, and stop it recurring.
Scanner beeps but nothing happens, or types gibberish. The five causes behind nearly every USB barcode scanner problem.
You submitted an order and it is not in Linnworks. A short checklist that finds it (or proves it never made it) in about two minutes.
New starter behind the trade counter on Monday? A shift-shaped training plan that gets them taking real orders safely by the afternoon.
Wrong SKU, wrong quantity, wrong price, wrong address — trade order errors have four sources and each has a specific fix. None of the fixes is "be more careful".
You do not need a POS terminal contract. A tablet, a scanner, a stand and a browser-based order tool cover a full trade counter for under £250.
A quote that has to be typed in again as an order is a quote system working against you. How tier-priced quoting should flow into Linnworks.
No drivers, no config, no special hardware. How scan-to-add works at a trade counter, what scanner to buy, and the settings that make it flow.
Phone orders are where wholesalers lose the most time per order. A workflow for getting a trade phone order into Linnworks while the customer is still on the line.
A retail till and a trade counter do completely different jobs. Using the wrong one quietly costs wholesalers time and margin every day. Here is the difference that matters.
Trade Order POS now has a team-wide Locale setting — currency symbol, tax rate, tax label and default country — so a business selling in the US or EU can run the whole POS in its own market.
US trade customers ordering from your UK operation — dollars, sales tax, addresses and the pipeline. A practical checklist for the order-entry side.
A one-time setting that removes a decision from every order. The small POS features that compound at trade volume.
Plenty is written about the paperwork of UK–EU trade. Less about the day-to-day: how you actually take, price and process an EU trade order without it being a special event.
Pricing in your customers’ currency wins trust and orders. If your operation sells in euros, the clean answer is a POS set to euros — one setting, not a spreadsheet of conversions.
Selling wholesale to US customers means dealing with sales tax — a different animal from VAT. How a trade POS should handle it, and where to get the rules.
Most small traders do not need per-order currency switching. They need their POS to speak the one currency their market uses. How a single team-wide currency setting does that.
If you sell trade into Europe, your point of sale needs to handle VAT properly on EU orders. What to look for, and what to avoid.
Selling B2B to EU customers from a Linnworks warehouse? What a trade POS needs to get right: VAT on EU orders, euro pricing, and orders that land in Linnworks.
The order your rep phones in tonight is the order that should have been placed at the customer’s kitchen table this morning. How tablet-based field ordering works with Linnworks.