R&D Tax Credits for Ecommerce UK — Complete Innovation Relief Guide 2026
UK ecommerce companies that build custom technology, automate complex operations, develop new software integrations or solve genuine technical uncertainty may be able to claim R&D tax relief. This 2026 guide explains MRDEC, ERIS, qualifying ecommerce activities, eligible costs, HMRC forms, deadlines and compliance risks in plain English.
What Are R&D Tax Credits for Ecommerce?
R&D tax credits for ecommerce are a UK Corporation Tax relief for companies that spend money on projects seeking an advance in science or technology. In an ecommerce context, this can include bespoke software development, complex automation, API architecture, fraud prevention tools, warehouse technology, custom recommendation engines, data engineering or platform integrations where the technical solution was not obvious at the outset.
The relief is not limited to laboratories, manufacturers or pharmaceutical businesses. A UK online retailer, Shopify Plus brand, WooCommerce store, Magento business, Amazon marketplace seller, subscription-commerce company or DTC brand can potentially claim if it is a company chargeable to Corporation Tax and has undertaken qualifying development work. The key point is that the claim must be based on technical uncertainty, not simply commercial risk, marketing innovation or normal website design.
For ecommerce founders, the most common misconception is that buying apps, changing a website theme or improving conversion rate is automatically R&D. It usually is not. However, if your team had to design, test and build a technical solution because standard apps, connectors or platforms could not solve the problem, that work may fall within the scope of HMRC R&D tax relief guidance.
Ecommerce R&D Is About Technology, Not Just Websites
A redesigned storefront, a new product page or standard SEO work is unlikely to qualify. But a custom stock synchronisation engine, a proprietary fulfilment algorithm, a complex API integration, a machine-learning recommendation tool or a fraud detection system may qualify if it sought a genuine technological advance and involved uncertainty a competent professional could not readily resolve.
R&D Tax Relief 2026: The Rules Ecommerce Companies Need to Know
The UK R&D tax credit regime has changed significantly. For accounting periods beginning on or after 1 April 2024, the old SME and RDEC schemes have broadly been replaced by two current routes: the merged R&D expenditure credit scheme, often called MRDEC or merged RDEC, and Enhanced R&D Intensive Support, known as ERIS, for loss-making R&D-intensive SMEs.
In 2026, ecommerce companies need to approach claims more carefully than in previous years. HMRC expects digital submissions, a mandatory Additional Information Form, detailed project narratives, clear cost apportionment and evidence that the work was genuinely scientific or technological. Poorly prepared claims are much more likely to be challenged, delayed or rejected.
| 2026 Requirement | What It Means for Ecommerce Businesses | Action Needed |
|---|---|---|
| Company must be within Corporation Tax | Sole traders and partnerships cannot claim R&D tax credits directly. | Claim through a UK limited company if eligible. |
| Project must seek a technological advance | Commercial improvement alone is not enough. | Document the technical problem and attempted resolution. |
| Additional Information Form is mandatory | HMRC can reject the R&D element if the AIF is missing or late. | Submit the AIF before or on the same day as the CT600. |
| Some claimants must pre-notify | First-time or returning claimants may need advance notification. | Check notification rules before the claim deadline. |
| Overseas spend restrictions apply | Offshore developers and overseas contractors may be partly or fully restricted. | Separate UK and overseas development costs clearly. |
| PAYE/NIC cap may restrict cash credits | Loss-making ecommerce startups with low UK payroll can be affected. | Calculate the cap before assuming the repayment amount. |
The 2026 R&D Tax Relief Schemes Explained
The correct scheme depends on the accounting period and company position. For periods beginning on or after 1 April 2024, most ecommerce companies will claim under the merged RDEC scheme. Loss-making SMEs with high R&D intensity may qualify for ERIS instead. A company cannot claim both MRDEC and ERIS on the same expenditure, so choosing the right route matters.
Main 2026 Scheme
Merged RDEC / MRDEC
For trading companies chargeable to Corporation Tax with qualifying R&D projects. Applies to many ecommerce companies for accounting periods beginning on or after 1 April 2024.
R&D-Intensive SMEs
ERIS
For loss-making SMEs whose relevant R&D expenditure is at least 30% of total expenditure, including connected company costs where applicable.
| Scheme | Who It Is For | Headline Rate | Typical Net Benefit | Best Ecommerce Example |
|---|---|---|---|---|
| Merged RDEC / MRDEC | Most trading companies claiming for periods starting on or after 1 April 2024 | 20% | 15p per £1 at 25% CT; 16.2p per £1 at 19% CT | Profitable ecommerce brand building custom technology |
| ERIS | Loss-making R&D-intensive SMEs meeting the 30% intensity condition | 86% extra deduction + 14.5% credit | Up to about 27p per £1 of qualifying spend | Tech-led ecommerce startup spending heavily on proprietary systems |
| Old SME Scheme | Relevant only for earlier accounting periods before the merged regime | Historical rates | Depends on period, profitability and reform date | Backdated claims for earlier years only |
| Old RDEC | Large companies and certain subsidised/contracted projects before April 2024 | Historical rates | Depends on accounting period | Backdated claims for older periods only |
MRDEC and ERIS Are Not the Same
The merged RDEC is an above-the-line taxable expenditure credit. ERIS is an enhanced SME-style relief for loss-making R&D-intensive SMEs. Ecommerce companies should calculate both eligibility and benefit before filing, especially where the company is loss-making, recently incorporated, grant-funded or part of a group.
Qualifying R&D Activities for Ecommerce
To qualify for R&D tax relief, an ecommerce project must seek an advance in science or technology and attempt to resolve scientific or technological uncertainty. The advance must be in the overall field of technology, not merely an internal business improvement. That does not mean your work has to change the world; it means the answer could not be readily deduced by a competent professional using publicly available knowledge.
Below are ecommerce activities that may qualify when they involve genuine uncertainty, experimentation and development work rather than routine configuration.
Custom Automation Systems
Building bespoke automation for order routing, fulfilment, stock allocation, returns processing or supplier workflows where standard ecommerce apps could not handle the operational complexity.
Complex API Integrations
Developing custom middleware between Shopify, Amazon, ERP, WMS, 3PL, accounting systems or supplier portals where standard connectors failed or caused data conflicts.
Personalisation Engines
Creating algorithmic or machine-learning systems for product recommendations, bundle suggestions, dynamic content or personalised shopping journeys using your own data model.
Fraud & Cybersecurity Tools
Developing transaction-risk scoring, account takeover prevention, bot defence, payment fraud detection or unusual-order flagging systems beyond off-the-shelf security settings.
Checkout & Payment Technology
Solving technical checkout problems involving multi-currency flows, payment orchestration, subscription logic, split payments, failed-payment recovery or custom customer authentication.
Warehouse & Inventory Tech
Developing stock forecasting, warehouse scanning, batch tracking, multi-location inventory logic, RFID workflows or real-time inventory synchronisation between multiple sales channels.
Search & Product Discovery
Building custom search, filtering, faceted navigation, visual search or relevance-ranking algorithms that required technical experimentation and could not be solved through standard plugins.
Data Engineering & Analytics
Creating real-time margin analytics, multi-channel attribution, data pipelines, forecasting models or profitability dashboards where technical uncertainty existed in processing or accuracy.
Logistics Optimisation
Developing carrier-selection logic, delivery prediction models, route optimisation, shipping-rate engines or automated exception handling for unusual fulfilment scenarios.
Examples of Ecommerce R&D That May Qualify
- Custom multi-channel inventory synchronisation where Shopify, Amazon, TikTok Shop, wholesale and warehouse stock had to be reconciled in near real time without overselling.
- New fulfilment allocation logic that selected warehouses based on stock levels, courier cut-off times, margin, delivery promises and return probability.
- Automated pricing algorithms that adjusted prices based on competitor data, stock ageing, fulfilment cost and channel-specific marketplace fees.
- Fraud detection models trained on internal ecommerce order history to flag suspicious transactions more accurately than generic gateway tools.
- Subscription box configuration logic that solved technical uncertainty around product substitutions, customer preferences, stock constraints and recurring billing.
- Custom returns portal technology integrating customer rules, courier labels, refund status, repair workflows and stock re-entry across multiple platforms.
- AI or machine-learning product recommendation tools that required technical experimentation around data quality, ranking accuracy and system performance.
- Data pipelines for real-time profitability combining ad spend, platform fees, COGS, returns, refunds, shipping and payment data into a live margin model.
Routine Ecommerce Work Does Not Qualify
Installing Shopify apps, customising a theme, uploading products, writing product descriptions, running SEO campaigns, creating ad funnels, changing checkout colours, implementing standard integrations or using existing software as intended will usually not qualify. The claim must be rooted in technology uncertainty, not ordinary business improvement.
What R&D Costs Can Ecommerce Businesses Claim?
Once a project qualifies, the claim is built from allowable costs directly connected to the R&D activity. Ecommerce companies often have mixed teams where developers, operations staff and external agencies work across both routine and R&D tasks. Accurate apportionment is essential. You should only claim the proportion of costs that relate to qualifying work from the point the uncertainty starts to the point it is resolved or the work stops.
| Cost Type | Potential Claim Treatment | Ecommerce Examples | Documentation Needed |
|---|---|---|---|
| Direct Staff Costs | Eligible if directly engaged in R&D | Developers, data engineers, systems architects, technical product managers | Payroll reports, time records, project notes, role descriptions |
| Employer NIC & Pension | Eligible with staff costs | Employer costs for employees working on qualifying R&D | Payroll summaries and apportionment calculation |
| Externally Provided Workers | Eligible subject to rules and restrictions | Agency developers, temporary engineers, outsourced technical staff | Contracts, invoices, worker location, project evidence |
| Subcontracted R&D | Often restricted to relevant percentage | Software agencies, freelance developers, specialist data science consultants | Statement of work, technical deliverables, invoices, UK/overseas split |
| Software Licences | Eligible if used directly in R&D | Development tools, testing platforms, code repositories, staging systems | Invoices and explanation of R&D use |
| Data Licences & Cloud Computing | Eligible where directly used for R&D | AWS, Azure, Google Cloud, data sets for model testing | Cloud bills, usage allocation, test environment records |
| Consumables | Eligible when consumed or transformed | Prototype hardware, test devices, materials used in development | Purchase invoices and project link |
| Qualifying Indirect Activities | Potentially eligible if supporting R&D | Technical documentation, security for R&D environment, project administration | Clear link to qualifying project |
Overseas Developers and Offshore Ecommerce Teams
Many ecommerce businesses use overseas developers, offshore agencies or globally distributed technical teams. In 2026, this area needs particular care because restrictions can apply to overseas contractor and externally provided worker costs. If a UK ecommerce company uses a foreign development agency to build a custom integration, the overseas element may be restricted unless a permitted exception applies.
The safest approach is to split every contractor invoice by project, activity, worker location and qualifying percentage. Keep copies of contracts, technical briefs, sprint tickets, Git commits, meeting notes and invoices. Do not assume that because a cost was paid by a UK company it is fully claimable. For complex cross-border development, get specialist advice before filing the claim.
Link R&D Claims to Strong Accounting Records
Your R&D tax credit claim should connect cleanly to your bookkeeping, payroll and Corporation Tax return. Ecommerce companies using cloud accounting should maintain project codes for development work. Our ecommerce accountants can help structure costs in Xero or QuickBooks before the claim period closes.
R&D Tax Credit Calculation Examples for Ecommerce
The benefit depends on the scheme, Corporation Tax rate, profitability, PAYE/NIC cap and whether the company qualifies for ERIS. The examples below are simplified illustrations only. Your accountant should calculate the actual figure through the Corporation Tax computation and CT600.
Example 1: Profitable Ecommerce Company Claiming MRDEC
A profitable Shopify Plus brand develops a custom multi-warehouse inventory engine during its 2025/26 accounting period. The company identifies £120,000 of qualifying expenditure.
| Item | Amount | Calculation | Result |
|---|---|---|---|
| Qualifying R&D expenditure | £120,000 | Staff, software, cloud and eligible contractor costs | £120,000 |
| MRDEC credit | 20% | £120,000 × 20% | £24,000 |
| Corporation Tax on credit | 25% | £24,000 × 25% | −£6,000 |
| Approximate net benefit | £24,000 − £6,000 | £18,000 |
Example 2: Loss-Making R&D-Intensive Ecommerce Startup Claiming ERIS
A subscription-commerce technology startup is loss-making and spends £90,000 on qualifying R&D out of £250,000 total relevant expenditure. Its R&D intensity is 36%, so it may meet the ERIS intensity condition, subject to the detailed rules.
| Item | Amount | Calculation | Indicative Result |
|---|---|---|---|
| Qualifying R&D expenditure | £90,000 | Direct qualifying expenditure | £90,000 |
| Additional ERIS deduction | 86% | £90,000 × 86% | £77,400 |
| Total enhanced amount | 186% | £90,000 + £77,400 | £167,400 |
| Payable credit rate | 14.5% | Applied to surrenderable loss, subject to rules | Up to about £24,273 |
These Examples Are Not a Substitute for a Tax Computation
R&D claims interact with taxable profits, losses, group relief, Corporation Tax rate, PAYE/NIC cap, grants and previous-period claims. Use examples for planning only. Before filing, reconcile the claim to your statutory accounts and Corporation Tax return.
How to Claim R&D Tax Credits — Step by Step
All R&D tax credit claims should be prepared as part of your Corporation Tax compliance process. The claim is made through the Company Tax Return, but the supporting detail must be submitted through HMRC's online Additional Information Form. Below is the practical process for ecommerce businesses.
-
Identify Potential R&D Projects
Review all development work completed during the accounting period. Look for projects involving custom technology, complex integrations, data engineering, automation, fulfilment logic, fraud tools, search algorithms or performance challenges. Focus on technical problems that standard software could not solve.
-
Test Each Project Against HMRC's R&D Definition
Ask whether the project sought an advance in science or technology and whether a competent professional faced uncertainty about whether or how the solution could be achieved. Remove routine configuration, design, marketing, app setup and commercial-only experiments from the claim.
-
Write the Technical Narrative
Prepare a project report explaining the baseline technology, the advance sought, the uncertainty encountered, the development approach, the technical failures or iterations, and the outcome. Keep it technical. HMRC is not looking for a sales pitch about revenue growth; it wants to understand the technological challenge.
-
Collect and Apportion Costs
Gather payroll records, developer timesheets, invoices, software costs, cloud bills and contractor agreements. Apportion mixed costs based on reasonable evidence such as sprint records, time logs, project-management tickets, payroll allocation, Git activity or documented management estimates.
-
Check Scheme Eligibility
Determine whether the claim falls under MRDEC or ERIS. Check the accounting period start date, company size, trading status, Corporation Tax position, R&D intensity percentage, loss position, connected companies, grants and overseas cost restrictions.
-
Consider Advance Notification
Some first-time claimants or companies that have not claimed recently may need to notify HMRC in advance of making an R&D claim. Missing a notification requirement can invalidate the claim, so check early rather than waiting until the CT600 is due.
-
Submit the Additional Information Form
The AIF must be submitted before or on the same day as the CT600, and if filed on the same day it must go first. It includes the company details, accounting period, project descriptions, qualifying expenditure categories and details of the person responsible for the claim.
-
File the CT600 With the R&D Claim
Your accountant includes the claim in the Corporation Tax return and relevant supplementary pages. Under MRDEC, the credit is treated as taxable income and then offset through the RDEC payment steps. ERIS claims are calculated through the enhanced SME support rules.
-
Keep Evidence for HMRC Review
Retain technical notes, project plans, Git commits, Jira/Trello tickets, architecture diagrams, test results, timesheets, payroll reports, cloud invoices and contracts. HMRC compliance checks are common, and evidence quality often determines whether a claim survives enquiry.
Build the Claim During the Project, Not After Year-End
The strongest ecommerce R&D claims are documented while development is happening. If your team waits until the tax return deadline, the technical uncertainty, time allocation and project evidence may be harder to prove. Add R&D project codes to your accounting system and capture evidence monthly.
R&D Claim Deadlines and HMRC Forms in 2026
The main claim time limit is normally two years from the end of the relevant accounting period. For example, if your company year-end was 31 March 2025, the R&D claim window normally closes on 31 March 2027. However, the AIF and potential advance-notification requirements can create earlier practical deadlines.
| Requirement | Deadline / Timing | Why It Matters |
|---|---|---|
| R&D claim in CT600 | Within two years of the accounting period end | Late claims are normally out of time and cannot be revived. |
| Additional Information Form | Before or same day as CT600, but before CT600 if same day | HMRC can reject the R&D claim if AIF is missing or late. |
| Advance Notification | Where required, before the claim is made and within HMRC's notification window | Applies to some first-time or returning claimants. |
| Evidence retention | Keep records for at least the normal Corporation Tax record period | Needed if HMRC opens a compliance check or enquiry. |
| Advance Assurance | Before claiming, for eligible first-time SME claimants | Can provide more certainty for small companies making a first claim. |
HMRC Compliance: What Ecommerce Companies Should Watch in 2026
HMRC has increased scrutiny of R&D claims, especially where narratives are generic, costs are inflated, or claims appear to be prepared by unregulated agents using templated wording. Ecommerce companies should avoid broad statements like “we improved our website” or “we built a better customer journey” without explaining the actual technology problem.
- Name a responsible senior officer who understands the claim and can answer HMRC questions.
- Use project-specific narratives rather than generic descriptions copied from adviser templates.
- Separate commercial and technological objectives so the claim focuses on science or technology.
- Keep cost apportionment evidence, especially for founders and developers who split time across many tasks.
- Check grants and subsidies because funding can affect how expenditure is claimed.
- Identify overseas development costs and apply the restrictions correctly.
- Avoid claiming routine app setup, theme work, standard connector implementation or general website maintenance.
- Review adviser quality because your company remains responsible for the accuracy of the claim.
Beware of “No Win, No Fee” Claim Factories
Some agents aggressively market R&D tax credits to online sellers and overstate eligibility. If HMRC challenges the claim, the company must repay incorrect relief plus interest and possible penalties. Use a qualified accountant or specialist with professional indemnity insurance and ecommerce-sector experience.
Documentation Checklist for Ecommerce R&D Claims
A strong R&D claim should be easy to trace from technical project evidence to the tax computation. Keep a digital claim folder for each project and update it throughout the year.
- Project summary explaining the technical baseline, uncertainty, advance sought and outcome.
- Technical specifications, architecture diagrams, integration maps, API documentation and system designs.
- Project management records from Jira, Trello, Asana, ClickUp, GitHub Issues or internal sprint boards.
- Source-control evidence including Git commits, branches, pull requests, test logs and release notes.
- Failure and iteration evidence showing experiments, rejected approaches, bugs, performance testing and prototypes.
- Staff time evidence such as timesheets, sprint allocation, calendar records or documented estimates approved by management.
- Financial evidence including payroll reports, employer NIC, pension contributions, invoices, cloud bills and payment confirmations.
- Contractor evidence including contracts, statements of work, location of work, invoices and deliverables.
- Grant and subsidy analysis where Innovate UK, local authority, investor or other funding contributed to project costs.
- Board or management approval showing the company decided to undertake the R&D and controlled the project.
Common Ecommerce R&D Claim Mistakes
Claiming the Entire Website Build
A new ecommerce website is not automatically R&D. Most web builds use known technology, standard frameworks and routine development. Only the specific parts that involved scientific or technological uncertainty should be considered. For example, a custom AI recommendation engine might qualify, while the product pages, blog templates and checkout styling do not.
Confusing Commercial Uncertainty with Technical Uncertainty
“Will customers buy it?” is commercial uncertainty. “Can this technical system achieve real-time cross-channel stock accuracy at scale without overselling?” may be technological uncertainty. HMRC is interested in the second question, not the first.
Ignoring Connected Companies
Group structures are common in ecommerce, especially where intellectual property, trading entities, warehouses and overseas teams sit in different companies. Connected company costs can affect SME status, ERIS intensity and expenditure calculations. Always map the group before filing.
Weak Cost Apportionment
Founder salaries, CTO time and agency invoices often cover both routine work and R&D. Claiming 100% without evidence is risky. Use project records, sprint tickets, time estimates and deliverables to support a reasonable apportionment.
Submitting the CT600 Before the AIF
The Additional Information Form must be submitted before or on the same day as the CT600. If both are submitted on the same day, the AIF should be sent first. Filing the CT600 too early can cause HMRC to reject the R&D claim.
How an Ecommerce R&D Tax Specialist Helps
R&D tax credits sit at the intersection of technology, accounting and Corporation Tax. Ecommerce businesses often need an adviser who understands platform architecture, marketplace integrations, stock systems, cloud infrastructure, data pipelines and how HMRC evaluates technical uncertainty.
A specialist can help you identify eligible projects, separate qualifying and non-qualifying work, prepare technical narratives, calculate costs, check MRDEC versus ERIS, review overseas spend, complete the AIF and ensure the claim agrees to your Corporation Tax return. If you sell through Shopify, Amazon, TikTok Shop or multiple channels, link the R&D process with your cloud accounting records and ecommerce bookkeeping from the start.
Practical Rule for Ecommerce Founders
If you paid developers to solve a problem where standard tools failed, keep the evidence. If you paid designers or marketers to make the site look better or sell more, it is probably not R&D. The boundary matters — and it should be documented before you claim.
Frequently Asked Questions — R&D Tax Credits for Ecommerce
Yes, a UK ecommerce company can claim if it is chargeable to Corporation Tax and has undertaken qualifying R&D. The project must seek an advance in science or technology and involve genuine technical uncertainty. The claim is based on the development work, not on the fact that the company sells online.
A Shopify store can claim only where the company has carried out qualifying technical development. Installing Shopify apps, changing a theme or configuring standard features usually does not qualify. Building a bespoke integration, automation engine, recommendation algorithm or technical system that required resolving uncertainty may qualify.
The merged RDEC scheme is the main R&D expenditure credit scheme for many companies with accounting periods beginning on or after 1 April 2024. The headline credit rate is 20%, and the credit is taxable as trading income. It can reduce Corporation Tax or, subject to the payment steps and PAYE/NIC cap, create a payable amount.
Enhanced R&D Intensive Support is for loss-making SMEs that meet the R&D intensity condition. For accounting periods beginning on or after 1 April 2024, relevant R&D expenditure generally must be at least 30% of total relevant expenditure. ERIS gives an extra 86% deduction and a 14.5% payable credit on surrenderable losses.
No. Profit-making companies may reduce Corporation Tax through the merged RDEC scheme, while loss-making companies may receive a payable credit subject to the rules. Loss-making R&D-intensive SMEs may qualify for ERIS, which can provide a higher cash benefit.
The Additional Information Form is a mandatory online form submitted to HMRC to support an R&D claim. It includes company details, project descriptions, qualifying expenditure categories and details of the claim contact. It must be submitted before or on the same day as the CT600, and if both are submitted on the same day the AIF should be sent first.
The usual deadline is two years from the end of the accounting period in which the qualifying expenditure was incurred. For example, a company with a 31 March 2025 year-end would normally have until 31 March 2027 to amend or submit the claim, subject to the AIF and any advance-notification requirements.
Possibly, but overseas contractor and externally provided worker costs are subject to restrictions under the reformed rules. Ecommerce companies using offshore developers should split UK and overseas work clearly and keep evidence of worker location, project scope and technical activities before including costs in a claim.
No. Custom software development only qualifies if it seeks a technological advance and involves uncertainty that a competent professional could not readily resolve. Routine coding, standard integrations, normal bug fixing, theme development and configuration of existing tools are usually not enough.
For ecommerce companies making a first claim, claiming significant amounts, using overseas developers, or working on complex software projects, specialist advice is strongly recommended. A good adviser can prepare robust technical narratives, check eligibility, calculate costs correctly and reduce the risk of HMRC challenge.
Could Your Ecommerce Business Claim R&D Tax Credits?
If your online business has built custom technology, integrations, automation or data systems, you may have a valuable R&D claim. Get the claim reviewed before your Corporation Tax deadline and before key evidence disappears.