If you run a shop in Bristol, the questions that decide a WooCommerce project are rarely about plugins. They are about which VAT rate sits on which product, whether your cookie banner does what the law says, what a customer must be told before paying, and who can see the order data afterwards. I handle that side of the build together with the code.
I am Mariusz Szatkowski. WPPoland is one person, based in Gdynia, Poland, working with WordPress since 2006. I work remotely and in writing, so there are no meetings and no site visits. You get a written scope, a staging site and a repository you can read. If you need a WooCommerce developer without the Bristol angle, that page covers the service in general.
#Where Bristol shops sit in the region
The West of England Combined Authority covers three local authority areas: Bath and North East Somerset, Bristol and South Gloucestershire. Its Growth Hub offers business support to firms registered in those three areas, listed on the Combined Authority’s site as funding and advice, technology, workforce and start-up help. If you sell online from a registered address there, check that page for support before you pay for a build yourself. I do not apply for it on your behalf.
Bristol City Council keeps a separate information hub for businesses with business rates, market trading, licences and permits, food business registration and trading standards. A shop owner with a market stall or a food product and a web shop therefore deals with the council on one side and the ICO and HMRC on the other. WooCommerce only touches the second group. I say this early so the scope is clear: a licence or a food registration is yours to sort out, and the shop will not replace it.
The University of Bristol is building the Temple Quarter Enterprise Campus beside Bristol Temple Meads station, with a hub for entrepreneurship and commercialisation. A small shop is a normal starting point, and it still needs the legal basics below.

Photo: mattbuck (category), CC BY-SA 3.0, Wikimedia Commons.
#VAT rates and the registration threshold
GOV.UK lists three VAT rates: 20% standard, 5% reduced and 0% zero rate. WooCommerce handles each as a tax class, with a rate table and a switch for whether prices in the shop include tax.
The decision about registration sits before the shop. GOV.UK states that you must register when your taxable turnover for the last 12 months goes over £90,000. Below that, many sellers run without VAT in the shop. Above it, the shop must show VAT and print it on invoices. I can switch WooCommerce between those states. Whether you are over the line is a question for you and your accountant.
One case needs a decision at the start. If your goods are held outside the UK at the point of sale, HMRC says consignments worth 135 pounds or less sold to customers in Great Britain have UK VAT charged at the point of sale, and sales to Northern Ireland are charged import VAT instead. That affects a drop-shipping shop in Bristol more than a stock-holding one.
#Cookies and consent under PECR
Regulation 6 of PECR 2003 stops a person storing information, or gaining access to information stored, on a user’s device, subject to Schedule A1. That schedule was inserted from 5 February 2026 and now lists the exceptions, among them strictly necessary storage for a requested service and statistical purposes.
For statistics, Schedule A1 sets conditions: the sole purpose is to improve the site, the information is not shared beyond that purpose, the user gets clear information, and the user has a simple, free way to object. The ICO guidance says consent needs “some form of unambiguous positive action” and that you cannot set non-essential cookies on the homepage before the visitor has agreed. It gives a shopping basket cookie as an example where you are unlikely to need consent.
In WooCommerce this becomes a build decision:
- The cart and checkout cookies run without a banner.
- Advertising pixels and chat widgets load only after the visitor agrees.
- Analytics are either configured to fit the statistical exception, with notice and an opt-out, or held back like any other script.
- The consent record and the reject button work on a phone as well as on a desktop.
The February 2026 change is recent. If your banner was set up before it, it is worth rereading against Schedule A1 rather than assuming it is still right. Your solicitor decides which exception you rely on.
#What customers must be told before they pay
GOV.UK’s online and distance selling guidance says you must provide the price including all taxes and the delivery arrangements, costs and how long goods will take to arrive. It also says you must tell customers they can cancel up to 14 days after delivery, and that you should deliver within 30 days unless agreed otherwise.
The cancellation period itself comes from regulation 30 of the Consumer Contracts Regulations 2013. For a sales contract the 14 days run from the day the goods reach the consumer. For goods that arrive on different days the period follows the last delivery in some cases and the first in others. That matters for a shop that splits orders between a Bristol workshop and a supplier.
I place this information where WooCommerce can show it: price with tax on product pages, delivery cost and time before the payment step, the cancellation notice on the order confirmation email. The wording of your terms of sale stays with your solicitor. I build the places the wording appears.
#Order data and the ICO
Every order is personal data: name, address, email, phone and what was bought. The ICO’s list of privacy information includes who you are, why you use the data, the lawful basis, how long you keep it, the rights people have and the right to complain to a supervisory authority.
A shop shows that information at the points where data is collected: the checkout, account creation, newsletter signup and the contact form. The ICO also states that organisations, sole traders included, that use personal information need to pay a data protection fee, unless exempt. Check that one before launch.
On the technical side I keep it small:
- checkout fields limited to what the order needs;
- shop managers with the role they need, not full administrator;
- no order exports on public URLs;
- a retention rule for old guest orders that you decide and I implement;
- a restore test of the backup on staging.
#Accessibility of the shop
Section 29 of the Equality Act 2010 says a service provider to the public must not discriminate against a person requiring the service by not providing it, and must not discriminate in how the service is provided. The Act does not set a technical standard for a web shop. I build checkout against practical checks: every field has a label, errors are announced, the keyboard reaches every step and focus is visible. Core Web Vitals use the published web.dev thresholds: LCP 2.5 s, INP 200 ms, CLS 0.1.
#A checklist you can use without hiring me
| Question | Where to look | Done when |
|---|
| Am I over the VAT threshold? | GOV.UK VAT registration page | The accountant has answered in writing |
| Does each product have the right tax class? | WooCommerce tax settings | A test order shows the expected VAT line |
| Do non-essential scripts wait for consent? | Browser network tab on a fresh visit | Nothing marketing loads before a click |
| Is price with tax shown with delivery cost before payment? | Cart and checkout | A tester can find both without scrolling |
| Does the confirmation email mention the 14-day cancellation? | Order email template | A real test order shows it |
| Does the privacy notice list purposes, lawful basis, retention and rights? | Privacy page | Checked against the ICO list |
| Is the ICO data protection fee settled or the exemption noted? | ICO fee page | A record exists |
| Does a restored backup open on staging? | Staging site | Someone placed a test order on it |
#From first email to handover
- You send a short brief. I read the existing shop or the planned catalogue and ask my questions in writing.
- I send back a written scope: what is in, what is out, what I assume, and the acceptance checks.
- Layout, graphic design and wireframes come from you, usually in a spreadsheet that marks which element sits where on each view. I implement it. I do not design.
- I build on a staging copy with gateways in test mode. You review there.
- Acceptance is a click-through of cart, checkout, payment, email, refund and cookie behaviour.
- Release is a documented step with a rollback. After it you get written notes for the shop manager.
If you want updates after launch, that is a separate arrangement, described on the page about WordPress maintenance and support in Bristol. A site without a cart is covered on the WordPress developer in Bristol page.
#What I need from you to start
- The shop address and admin access, or the product list if the shop does not exist yet.
- The goal in a sentence: more orders, a trade portal, a new payment option, a cleaner checkout.
- Your gateway choice. I connect the gateways you pick; I do not choose them for you.
- Your layout spreadsheet and content, or a note that they are still to come.
- Your accountant’s answer on VAT, if registration is open.
- A deadline, and any date when the shop must not change.
#Questions Bristol sellers ask
#Are you a Bristol agency?
No. I am one developer working from Gdynia in Poland. I do not visit Bristol and do not hold meetings. Everything is written: the brief, the scope, the staging notes and the handover.
#Do I need a cookie banner on my WooCommerce shop?
You need consent before non-essential storage or access on a visitor’s device, unless a Schedule A1 exception applies. The ICO treats a basket cookie as unlikely to need consent. Marketing pixels and most tracking do need it. The banner is a visible part of a setup that must also stop the scripts.
Yes, as configuration. I set tax classes for the 20%, 5% and 0% rates, how prices display and what the invoice shows. Which rate applies to a product, and whether you must register, you decide with your accountant or HMRC.
#What must a Bristol shop tell customers before they buy?
GOV.UK lists the price including all taxes and the delivery arrangements, costs and time. It also says customers must be told about the 14-day cancellation right. I place those in the templates. Your solicitor owns the wording of the terms.
#Can the shop be built from my own layout?
Yes. Graphic design and wireframes are yours. I implement them as a working, responsive WooCommerce front end.
#What do I receive before deciding?
A written estimate, free of charge, after you send the details below. Scope and assumptions are written down before work starts.
#Write to me
Send the shop address, what you want to change, your deadline and the current stack (theme, main plugins, payment gateways) through the contact page. I answer in writing on working days. The first written estimate is free, and you decide afterwards whether to go ahead.