Indian Vastraa
E-commerce build covering catalogue structure, product presentation and the checkout path for an apparel collection.
Visit siteServing the United Kingdom
EasyWork Solutions builds e-commerce platforms for UK retailers from Surat, India. The distinctive complexity here is legal rather than technical: UK consumers have statutory cancellation rights that change how orders and refunds must work, and selling into the EU after Brexit is no longer the same transaction it used to be.
E-commerce development for UK businesses must build in statutory consumer cancellation rights, which give most online buyers a period to change their mind and require refunds within a defined window including standard delivery. It also means handling VAT correctly at the right rate per product, and treating EU sales as exports with customs and import VAT consequences.
UK consumers buying online have a statutory right to change their mind on most purchases, independent of whether the goods are faulty. Retailers frequently treat this as a returns policy to be written and published, when it is actually a set of states the order system has to represent.
The mechanics matter. The cancellation window runs from a defined point rather than from the order date, the customer can cancel before dispatch as well as after delivery, and the refund is due within a defined period of the goods being returned or evidence of return being supplied. Certain categories are excluded — personalised goods and some sealed items among them — and getting those exclusions right in the system prevents both wrongful refusals and unnecessary refunds.
The detail retailers most often miss is that the refund generally has to include the standard outbound delivery charge you originally took. A system that models a refund as "the value of the returned items" will under-refund by default, which is both a compliance problem and a customer service one that surfaces as complaints rather than as an error report.
UK VAT is not a single rate applied to an order. Standard, reduced and zero rates apply to different categories, and UK retail has genuinely common zero-rated goods — most food, children's clothing, books and printed matter among them. A store that applies one rate across the basket will be wrong for entire product categories.
That makes rate a property of the product rather than of the shop, and it makes accurate product categorisation a data quality issue with direct financial consequences. Mixed baskets containing items at different rates then need correct apportionment, particularly when a discount or a delivery charge is applied across the whole order.
Discounts and delivery are where implementations usually go wrong, because the correct treatment depends on how the discount is structured and how delivery is billed. These are decisions to settle deliberately with your accountant rather than assumptions to bake in silently, since correcting them later means correcting historical records too.
Before Brexit, shipping from the UK to an EU customer was operationally similar to shipping domestically. It is now an export, and the consequences land squarely on the customer experience if the store does not handle them.
The immediate decision is who pays import charges and when. If you ship on a basis where the customer becomes liable for import VAT and duty on arrival, a proportion of parcels will be refused at the door — and you then absorb outbound shipping, return shipping and the lost sale. If you take on those charges and collect them at checkout, the price shown is higher but the delivery completes.
Either choice is defensible; making no choice is not, because the default outcome is the first one arriving as a surprise to your customer. The store also needs accurate commodity codes and country of origin on products to generate customs documentation, which is product data that has to be captured rather than derived.
UK delivery expectations are specific and unforgiving. Named-day and next-day options are normal rather than premium, click and collect is expected from any retailer with physical locations, and a delivery promise stated at checkout is treated as a commitment rather than an estimate.
That argues for showing real options with real cut-off times rather than a flat charge. A cut-off that reflects your actual dispatch capability, and a promise the operation can meet, generates fewer support contacts than an optimistic one — and a missed delivery promise is a more expensive customer service event than a slower option honestly stated.
Postcode-based charging matters too. UK delivery costs vary substantially for the Highlands, islands and Northern Ireland, and retailers who use a single mainland rate quietly lose money on those orders. Surfacing the correct charge by postcode is better than either absorbing it or discovering it in the carrier invoice.
Abandoned basket emails, review requests and promotional messaging are standard e-commerce practice, and in the UK they sit under PECR as well as data protection law. That makes them a build consideration rather than purely a marketing one.
The practical position is that marketing email to consumers generally needs consent, with a narrow exception for people who bought similar goods from you and were given a clear opportunity to opt out at the point of collection and in every message. Whether you can rely on that exception depends on how your checkout was built, which makes it an engineering decision.
So we build the consent capture and its record properly — what was agreed, when, against which wording — rather than adding a checkbox and hoping. It costs very little at build time and it is the difference between a marketing list you can actually use and one your adviser tells you to stop using.
We do not publish a price list, because a number given before understanding the work is a guess someone pays for later. These are the factors that actually move the figure in this market.
Modelling statutory cancellation states, category exclusions, refund timescales and delivery-charge inclusion is genuine scope, and it is cheaper than correcting refunds retrospectively.
A single-rate catalogue is simple. Mixed standard, reduced and zero-rated products with discounts and delivery apportionment across baskets needs careful, deliberate implementation.
Export documentation, commodity codes, country of origin and the delivered-duty decision each add scope, and getting them wrong shows up as refused parcels rather than as errors.
Flat-rate charging is simple and loses money on non-mainland postcodes. Real options with genuine cut-offs and postcode-accurate charging costs more and reflects reality.
A well-configured hosted platform is a fraction of a custom build. Custom earns its place when pricing, configuration or fulfilment logic is genuinely unusual.
E-commerce build covering catalogue structure, product presentation and the checkout path for an apparel collection.
Visit siteOur cloud inventory platform with real-time multi-warehouse stock and barcode support — the stock accuracy layer serious retail depends on.
Visit siteProduct site for a packaging exporter organised around technical specification and catalogue clarity, the discipline a large SKU set requires.
Visit siteStatutory cancellation windows, category exclusions, refund timescales and delivery-charge inclusion are modelled as order states before build rather than written into a policy afterwards.
Rate per product, mixed-basket apportionment, and the treatment of discounts and delivery charges are decided deliberately rather than assumed and corrected later.
Whether import charges are collected at checkout or left with the customer, plus commodity codes and country of origin captured as product data for customs documentation.
Options and cut-offs that your operation can actually meet, with postcode-accurate charging rather than a mainland flat rate that loses money quietly.
What was agreed, when and against which wording, recorded at checkout — so the resulting list is one you can lawfully use rather than one you are told to stop using.
Where replacing an existing shop, URL mapping and a complete redirect strategy are explicit scope, because migrations that lose rankings lose them at this stage.
These apply to us as much as to anyone else bidding for your work.
They are order states rather than a policy page. The window runs from a defined point rather than the order date, customers can cancel before dispatch as well as after delivery, refunds are due within a defined period, and certain categories such as personalised goods are excluded. Building those states in prevents both wrongful refusals and unnecessary refunds.
Generally the standard outbound delivery charge you originally took, yes. This is the detail retailers most often miss, because systems tend to model a refund as the value of returned items. That under-refunds by default, which surfaces as customer complaints rather than as a system error.
As a property of the product, not the order. UK retail commonly includes zero-rated goods such as most food, children's clothing and books, so a single rate across the basket is wrong for entire categories. Mixed baskets then need correct apportionment, and the treatment of discounts and delivery should be settled with your accountant rather than assumed.
It is now an export. The key decision is whether import VAT and duty are collected from the customer at checkout or left for them to pay on arrival. If you leave them, a proportion of parcels get refused at the door and you absorb shipping both ways plus the lost sale. You also need commodity codes and country of origin as product data to generate customs documentation.
Usually, but it depends on how consent was captured, because PECR applies alongside data protection law. Marketing email to consumers generally needs consent, with a narrow exception for people who bought similar goods and were given a clear opt-out at collection and in every message. Whether you can rely on that exception is decided by how your checkout was built.
It depends on your order volume, margin per order, catalogue complexity and who maintains it in two years. A hosted platform gets standard mechanics working quickly at the cost of fees and constraints. WooCommerce gives control and lower running cost if someone keeps it maintained. Custom is warranted when pricing or fulfilment logic is genuinely unusual.
Yes, and search visibility is the risk to manage rather than hope through. URL mapping, a complete redirect strategy, catalogue and customer data migration and post-launch monitoring are explicit scope. Migrations that lose rankings almost always lost them at the redirect stage.
A meaningful share of search in this market happens in a language other than English. These are the terms people actually use — we work with your translator for customer-facing copy rather than relying on machine translation.
Last reviewed 2026-08-06 by the EasyWork Solutions team.