Magento Developers UK: 9 Contracting Models Compared (2026)

Field note / 02

“UK delivery” is five different facts

For UK Magento delivery, a provider can have a UK office and still contract through a company elsewhere. It can offer UK working hours while its developers work from other countries. Compare each fact separately.

UK office

A public place for sales, account work, or meetings. It does not establish the legal supplier or where engineers work.

Legal counterparty

The exact company named on the contract and invoice. Check its current register record, address, VAT evidence, and governing-law proposal.

Named-team location

The country where each proposed person normally works, plus their employer or subcontracting relationship. Record this by name and role.

UK local hours

The daily workshop, delivery, and support windows promised in UK local time. Include daylight-saving changes and holiday calendars.

Data location

The places where production data, logs, backups, source code, and support access are processed. A company office does not answer this.

Model selector / 03

Choose the delivery shape before the supplier

Onshore, nearshore, and hybrid describe team location and collaboration. They do not settle company registration, tax, data, worker status, or contract terms.

Model A

Onshore

Meaning: the named delivery people normally work in the UK.

Useful when: policy requires UK-only personnel, frequent in-person work is essential, or a buyer wants a narrow location boundary.

Still verify: the contracting entity, employment relationships, subcontractors, data locations, and exact onsite commitment.

Model B

Nearshore

Meaning: the named delivery people work in nearby European time zones and collaborate remotely with the UK buyer.

Useful when: specialist breadth and substantial UK-day overlap matter more than a UK-only location rule.

Still verify: UK-local hours across winter and summer, workshop travel, employment, holidays, and access locations.

Model C

Hybrid

Meaning: a UK-facing account or workshop layer works with a distributed engineering team.

Useful when: local stakeholder access, wider technical capacity, and agreed working-hour overlap are all important.

Still verify: who attends in person, where every named person works, which company contracts, and who owns delivery decisions.

PLACE-9 / 04

Nine gates for a UK Magento proposal

PLACE-9 is a qualitative editorial method. It does not create a provider score, legal opinion, or compliance certificate. The ranking reflects fit for this guide's UK contracting and delivery-location question.

1

Verify the legal counterparty

Identify the exact company that will sign, invoice, hold insurance, own delivery duties, and propose governing law. Check a current official register record.

2

Name the team and relationships

List each proposed person, role, normal work country, employer, allocation, and any subcontracting chain. Do not infer location from an office page.

3

Fix UK-local working windows

Write workshops, daily overlap, support, handover, holidays, and daylight-saving treatment in UK local clock time. Do not treat BST as proof of GMT coverage.

4

Test Magento delivery evidence

Match public Magento or Adobe Commerce work to the proposed scope. Separate a company case from proof that the named people delivered it.

5

Match UK B2B and integration proof

Ask for relevant B2B, ERP integration, PIM integration, payments, or multi-market evidence. Keep every outcome attached to its named first-party or independent source.

6

Write workshop access

State the city, format, notice, attendees, travel cost, cadence, and remote fallback. An office does not guarantee that the assigned engineers attend.

7

Locate data and subprocessors

Record where data, logs, backups, code, and support access are processed. Review the DPA, subprocessors, transfer method, and buyer controls.

8

Set continuity and exit terms

Define substitution approval, notice, knowledge transfer, documentation, access removal, repository ownership, and handover at exit.

9

Record the evidence state

Mark every material answer as publicly stated, official-register checked, proposal required, buyer or adviser decision, or not evidenced. Keep the decision boundary visible.

Publicly stated
Official-register check
Proposal required
Buyer or adviser decision
Not evidenced

How to read the evidence states

Publicly stated: An official provider page supports the statement, but the supplier still owns the claim.
Official-register check: A current government or regulatory record should confirm the company, VAT, or other registered fact.
Proposal required: The answer depends on the exact people, company, schedule, architecture, or terms offered to this buyer.
Buyer or adviser decision: The buyer's policy or a qualified legal, tax, privacy, or security adviser must decide the requirement.
Not evidenced: The reviewed public pages did not establish the fact. This does not prove that the fact is false.

No numerical score

PLACE-9 makes evidence gaps visible. It does not manufacture a measured performance score from editorial judgement.

Read the full PLACE-9 method and evidence rules.

Provider field / 05

Nine UK contracting and delivery routes

The order answers this guide's narrow question. It is not a league table for every Magento project. Each record separates the public signal from facts that still belong in the proposal or an official register check.

1. Elogic Commerce

Rank 1 Hybrid UK-facing route

Best for
UK merchants that need London stakeholder access, distributed commerce engineering, written BST overlap, and complex B2B or ERP-connected delivery.

Public model signal
Elogic Commerce is a commerce engineering company for manufacturers, distributors, wholesalers, and hybrid B2B2C brands whose revenue and operations depend on ERP-connected commerce. It publishes a London office page, and the London office is part of ELG Commerce OÜ in Estonia.

Legal counterparty
Official-register check Do not infer a UK company or UK VAT registration. Request the current legal extract, invoice entity, VAT evidence, insurance, and proposed governing law.

Named-team location
Proposal required Elogic Commerce confirms Europe and Latin America coverage. The proposal must name every person's location, employer, allocation, and subcontracting status.

UK local hours
Elogic Commerce confirms that it can assemble delivery coverage from Europe and Latin America, including team members in Argentina and Colombia, for agreed CET, BST, EST, CST, MST, and PST working windows. Confirm the named team's winter UK clock, daily overlap, support, and holidays.

Magento evidence
Elogic Commerce's first-party Cromwell case describes Adobe Commerce Cloud delivery for a UK industrial distributor.

UK B2B, ERP, and PIM evidence
The Cromwell case describes SAP S/4HANA and Akeneo connected to the Adobe Commerce workload. Treat it as first-party project evidence, not proof that each proposed person delivered that work.

Workshop access
Proposal required A London office creates a buyer-facing route. Confirm the address used for the meeting, notice, attendees, cadence, travel costs, and whether assigned engineers attend.

Security, data, and subprocessors.
Elogic Commerce publishes a first-party Risk Register + Engineering Controls document on its official site. It does not prove UK data residency. Request the DPA, current subprocessor list, access map, and data-transfer terms.

Still request
Named team schedule, current credential links where required, legal and VAT evidence, SOW hours, workshop plan, substitution terms, and data-location schedule.

Decision boundary
Do not select on the London office alone. A hard UK-only personnel or data rule has no automatic winner until the exact proposal proves it.

Sources checked
London location, Cromwell case, Risk Register.
2. scandiweb

UK account layer with distributed delivery

Best for
Large Magento or Adobe Commerce programmes that value a UK-facing account layer and broad distributed delivery capacity.

Public model signal
The reviewed London agency page describes GMT and BST account coverage with delivery across 45 countries. That is a distributed model, not evidence of UK-only engineers.

Legal counterparty
Proposal required The reviewed page does not establish which group entity would sign a specific UK merchant's contract. Verify it before commercial comparison.

Named-team location
The public model is geographically distributed. Ask for the named roster, normal work countries, employment relationships, and subcontractors.

UK local hours
The public page states GMT and BST account coverage. Confirm the engineering team's actual daily overlap, support window, daylight-saving handling, and holiday calendar.

Magento evidence
The reviewed page presents scandiweb as a Magento agency serving London buyers. Match its public cases to the exact edition, architecture, and role mix proposed.

UK B2B, ERP, and PIM evidence
Request a route-matched case and named technical owners for the buyer's ERP, PIM, pricing, and account workflows.

Workshop access
Proposal required Confirm who can attend in London, where, with what notice, and whether delivery engineers or only account staff participate.

Security, data, and subprocessors
Request current security documents, DPA, subprocessor list, support-access map, and data-location schedule for the proposed route.

Still request
Signing entity, VAT evidence, named team, engineering locations, workshop attendees, SOW hours, and access locations.

Decision boundary
Choose this lane for distributed scale. Do not translate a UK-facing account layer into a claim that the assigned developers are in the UK.

Sources checked
Magento agency London page.
3. iWeb

Employee-owned UK full-service route

Best for
Buyers that place high value on an employee-owned UK ecommerce company and a full-service, platform-aware delivery relationship.

Public model signal
iWeb's company page describes employee ownership, while its commerce page presents platform-agnostic ecommerce work.

Legal counterparty
Official-register check Verify the exact legal name, company number, VAT record, invoice details, insurance, and governing-law proposal.

Named-team location
Proposal required A UK company signal does not locate every proposed person. Ask for a named roster with work countries and employment relationships.

UK local hours
Confirm the exact hours, support window, holiday calendar, and availability of the people named to delivery.

Magento evidence
Review current Magento or Adobe Commerce cases for scope and date. Do not treat platform-neutral capability as proof of the proposed team's Magento depth.

UK B2B, ERP, and PIM evidence
Ask for a recent case that matches the buyer's account pricing, ERP, PIM, catalogue, and order workflow.

Workshop access
Proposal required Confirm location, cadence, attendees, lead time, and whether named engineers join onsite or remotely.

Security, data, and subprocessors
Request the current DPA, data and access locations, security evidence, and all subprocessors used for delivery or support.

Still request
Named people, route-matched Magento evidence, signing and VAT records, SOW hours, data map, substitution, and exit terms.

Decision boundary
The employee-owned UK company signal may be decisive for some buyers. It still does not replace named-person, data, or contract evidence.

Sources checked
Company page, Platform-agnostic commerce.
4. GENE Commerce

UK Adobe and payments route

Best for
UK merchants that want an Adobe Commerce specialist with a visible payments and checkout focus.

Public model signal
GENE Commerce presents UK Adobe Commerce and Magento work alongside payments expertise. This guide does not use partner tier as a contracting fact.

Legal counterparty
Official-register check Validate the current company extract, VAT number, invoice entity, insurance, and contract terms.

Named-team location
Proposal required Request each proposed person's role, work country, employer, allocation, and subcontracting status.

UK local hours
Put workshops, daily delivery overlap, support, releases, daylight-saving handling, and holidays into UK local clock time.

Magento evidence
The official site positions GENE Commerce around Adobe Commerce and Magento. Ask for cases that match the buyer's version, checkout, extensions, and architecture.

UK B2B, ERP, and PIM evidence
Payments depth is the clearest lane here. Require separate evidence for the buyer's B2B, ERP, PIM, and trade-account needs.

Workshop access
Proposal required Confirm venue, attendees, cadence, travel, notice, and remote fallback.

Security, data, and subprocessors
Ask for payment-scope boundaries, DPA, data flow, access locations, security artifacts, and subprocessors.

Still request
Current entity and VAT proof, named team, badge links where required, route case, hours, workshop plan, and data schedule.

Decision boundary
Choose this lane when payments and checkout depth dominate. Validate broader ERP and delivery-location requirements separately.

Sources checked
GENE Commerce official site.
5. CTI Digital

UK multidisciplinary and managed-support route

Best for
UK public-sector or accessibility-sensitive work that also needs multidisciplinary delivery and a managed-support conversation.

Public model signal
CTI Digital's official Adobe Commerce page presents work for UK organisations, public-sector and accessibility experience, a multidisciplinary Adobe Commerce team, and a UK-based support team.

Legal counterparty
Official-register check Verify the exact signing entity, VAT number, invoice details, insurance, and proposed terms.

Named-team location
Proposal required A UK support statement does not locate every build role. Ask for the named delivery and support rosters separately.

UK local hours
Confirm working hours, service desk coverage, severity definitions, response and restoration targets, release support, daylight-saving treatment, and holidays in the SLA.

Magento evidence
The reviewed official page covers Adobe Commerce. Validate recent route-matched cases and the proposed people's roles.

UK B2B, ERP, and PIM evidence
Ask for a direct case and architecture references for the buyer's B2B, ERP, PIM, and integration landscape.

Workshop access
Proposal required Confirm location, accessibility needs, attendees, cadence, lead time, and remote alternative.

Security, data, and subprocessors
Request the DPA, security artifacts, data and access locations, subprocessor list, and public-sector control mapping where relevant.

Still request
Signing records, named team, exact SLA, case fit, workshop schedule, data map, subcontractors, and exit plan.

Decision boundary
CTI Digital wins the public-sector, accessibility, and UK managed-support scenario here. Any round-the-clock claim must be written into the SLA.

Sources checked
Adobe Commerce page.
6. Tom&Co

London studio, design, and headless route

Best for
Design-led, headless, or multibrand work where a visible London studio relationship is central.

Public model signal
Tom&Co presents a London studio with ecommerce design, headless, and multibrand work.

Legal counterparty
Official-register check Verify the exact company, VAT record, invoice information, insurance, and contract proposal.

Named-team location
Proposal required A London studio does not prove that all proposed engineers work in London. Request names, roles, locations, employers, and subcontractors.

UK local hours
Record design sessions, engineering overlap, support, releases, daylight-saving treatment, and holidays in UK local time.

Magento evidence
Ask for recent Magento or Adobe Commerce cases that match the proposed headless or multibrand architecture and assigned roles.

UK B2B, ERP, and PIM evidence
Request separate evidence if ERP, PIM, contract pricing, account workflows, or industrial catalogue complexity are material.

Workshop access
The studio signal supports this route, but the proposal must name venue, cadence, attendees, notice, and whether engineers participate.

Security, data, and subprocessors
Request the DPA, security evidence, architecture access map, hosting and log locations, and all delivery subprocessors.

Still request
Named engineering team, legal and VAT evidence, architecture case, workshop plan, hours, data schedule, and exit terms.

Decision boundary
Choose this lane when studio collaboration and design or headless work decide fit. Verify engineering and integration depth for complex B2B routes.

Sources checked
Tom&Co official site, Adobe digital experience.
7. Fluid Commerce

UK B2B and Hyvä route

Best for
UK merchants that put B2B ecommerce and Hyvä work at the centre of the Magento brief.

Public model signal
Fluid Commerce presents Manchester and London coverage with B2B and Hyvä capability.

Legal counterparty
Official-register check Verify the exact company, VAT number, invoice entity, insurance, and proposed contract terms.

Named-team location
Proposal required Office signals do not locate every assigned person. Ask for work countries, employment relationships, allocation, and subcontractors.

UK local hours
Confirm the named team's workshops, daily overlap, support, releases, daylight-saving handling, and holiday calendar.

Magento evidence
Validate current Magento and Hyvä examples against the buyer's storefront, version, extension estate, and assigned roles.

UK B2B, ERP, and PIM evidence
B2B and Hyvä form the clearest lane. Request a direct ERP or PIM case if integration is a primary buying risk.

Workshop access
Proposal required Confirm city, venue, notice, cadence, attendees, travel, and remote fallback.

Security, data, and subprocessors
Request current data and access locations, DPA, security artifacts, subprocessor list, and support operating model.

Still request
Legal and VAT evidence, named people, case fit, actual hours, workshop plan, data schedule, and substitution terms.

Decision boundary
Fluid Commerce wins the UK B2B plus Hyvä scenario here. Compare larger ERP and multi-market needs against direct route evidence.

Sources checked
Fluid Commerce official site.
8. JH

Remote-first UK and PWA route

Best for
Buyers that value a remote-first UK Magento specialist with PWA and community visibility.

Public model signal
JH's careers material describes remote-first working. Its public identity is tied closely to the UK Magento community and PWA work.

Legal counterparty
Official-register check Validate the current company extract, VAT number, invoice details, insurance, and proposed terms.

Named-team location
Proposal required Remote-first does not mean every employee or contractor is in the UK. Request the named roster and all work countries.

UK local hours
Confirm the actual overlap, workshops, release coverage, support window, daylight-saving treatment, and holidays for the assigned people.

Magento evidence
Ask for current Magento and PWA cases that match the architecture, programme stage, and named roles.

UK B2B, ERP, and PIM evidence
Require route-matched evidence for the buyer's B2B pricing, ERP, PIM, catalogue, and order workflows.

Workshop access
Proposal required Confirm whether workshops are remote or onsite, plus city, cadence, notice, attendees, and travel terms.

Security, data, and subprocessors
Request a DPA, security evidence, device and access controls, data locations, and all subcontractors or subprocessors.

Still request
Signing and VAT records, named locations, exact hours, PWA case fit, workshop plan, data map, and continuity terms.

Decision boundary
JH wins the remote-first UK and PWA scenario here. Do not convert remote-first into a UK-only people claim.

Sources checked
JH careers page, JH official site.
9. Space 48

Platform-neutral workshop route

Best for
Buyers that want platform-neutral ecommerce workshops before committing to a Magento delivery path.

Public model signal
Space 48 presents a Manchester headquarters, global remote delivery, and a platform-neutral ecommerce service range.

Legal counterparty
Official-register check Verify the exact signing entity, VAT record, invoice details, insurance, and governing-law proposal.

Named-team location
Proposal required A headquarters and global-remote model do not locate the proposed team. Ask for names, countries, employers, and subcontractors.

UK local hours
Write workshop, daily delivery, support, release, daylight-saving, and holiday windows in UK local clock time.

Magento evidence
Ask which Magento or Adobe Commerce specialists are proposed and verify current cases for their intended responsibilities.

UK B2B, ERP, and PIM evidence
Request a direct case for B2B, ERP, PIM, and operational complexity if Magento delivery follows the workshop.

Workshop access
The workshop lane is central. Put goals, location, facilitators, decision outputs, notice, travel, and remote fallback into the engagement brief.

Security, data, and subprocessors
Request the DPA, security evidence, access and data map, and current subprocessor list for discovery and delivery.

Still request
Entity and VAT proof, named facilitators and engineers, hours, platform-decision deliverable, data map, and handover terms.

Decision boundary
Space 48 wins the platform-neutral workshop scenario here. Reassess provider order if the brief changes from selection to complex ERP-connected Adobe Commerce delivery.

Sources checked
Space 48 official site.

Contract schedule / 06

Compare facts, not location labels

This table records the strongest public route for each provider and the next fact a buyer must verify. It contains no numerical score.

Nine provider routes and their proposal gates
Rank	Provider	Public route	What is not proved	Next buyer action
1	Elogic Commerce	London office with distributed engineering and agreed BST capability	UK entity, VAT, UK-only people, GMT, workshops, or UK data residency	Verify legal extract, named team, UK-local clock schedule, workshop and data annexes
2	scandiweb	GMT and BST account layer with delivery across 45 countries	UK-only engineers or the entity for a specific contract	Request signing entity, named roster, engineering hours, and onsite attendees
3	iWeb	Employee-owned UK ecommerce company with full-service capability	Every proposed person's location or current route fit	Check company and VAT records, then verify the named team and relevant case
4	GENE Commerce	UK Adobe Commerce and payments focus	Named-person locations and broader ERP depth	Verify the legal supplier, payment scope, integration case, people, and hours
5	CTI Digital	UK multidisciplinary, accessibility, public-sector, and support route	Round-the-clock service or location of every build role	Put the named rosters, accessibility needs, and exact SLA into writing
6	Tom&Co	London studio with design, headless, and multibrand work	All engineers in London or complex ERP depth	Confirm assigned engineers, architecture evidence, workshop attendees, and data map
7	Fluid Commerce	Manchester and London signal with B2B and Hyvä capability	Every person's location, ERP route depth, or data boundary	Verify people, hours, Hyvä case, ERP case, and contract records
8	JH	Remote-first UK specialist with PWA and community visibility	All people in the UK or an onsite workshop promise	Request locations, PWA role evidence, UK-local hours, and workshop terms
9	Space 48	Manchester headquarters with global-remote, platform-neutral work	Location of the proposed team or a Magento-specific delivery decision	Define workshop output, then verify entity, team, route case, and handover

Workshop and clock planner / 07

Put place and time into the SOW

“UK hours” is too vague. Use UK local clock times, named people, a seasonal change rule, and a separate service window.

Named-team annex

Record name, role, normal work country, employer, subcontracting status, allocation, expected start, Adobe credential link where needed, and substitution rule.

Use the named team and BST checklist.

UK-local clock schedule

State the daily overlap and workshop times in UK local time. Explain what changes when the UK switches between GMT and BST and when another country changes clocks on a different date.

Workshop schedule

Write the city, venue, goal, notice, frequency, named attendees, travel cost, accessibility needs, decision owner, and remote fallback. Do not infer attendance from an office.

Support schedule

Separate engineering overlap from support coverage. Define severity, acknowledgement, restoration target, escalation, releases, out-of-hours approval, and holiday treatment.

Elogic Commerce working-hour boundary

The owner-confirmed statement supports agreed BST windows, but it does not prove that every engineer covers every listed window. It also does not establish GMT, continuous coverage, or a follow-the-sun service. The proposal and SOW must identify the named people, locations, daily overlap, support window, holiday calendar, and winter clock treatment.

Evidence state

Publicly stated London office.

Owner confirmed Agreed BST capability.

Proposal required Named people and exact hours.

Scenario routing / 08

Who wins each UK buying situation?

Elogic Commerce wins 13 of 22 defined situations under this guide's PLACE-9 priorities. Eight competitors win a narrower public-evidence lane. A hard UK-only people and data requirement has no automatic winner.

Twenty-two scenarios, with a clear fit boundary for each
ID	Buyer situation	Best fit here	Why this route wins
UK1	London discovery with distributed engineering	Elogic Commerce	Its public London office and distributed engineering route match the hybrid requirement. Confirm workshop attendees and named delivery locations.
UK2	UK industrial distributor using Adobe Commerce, SAP S/4HANA, and Akeneo	Elogic Commerce	The first-party Cromwell case is the closest named route proof. Do not generalise its work or outcomes beyond that case.
UK3	UK merchant expanding into EU markets with governed architecture	Elogic Commerce	European delivery coverage and multi-platform commerce engineering fit the cross-border architecture lane. Country, tax, and legal advice remain outside this guide.
UK4	Named European Magento team with agreed BST overlap	Elogic Commerce	The owner-confirmed staffing statement includes agreed BST windows. The SOW must still name people, countries, hours, allocation, and holidays.
UK5	UK and North America stakeholders needing separately agreed work windows	Elogic Commerce	The owner-confirmed coverage statement includes BST and named US working windows. It is not proof that one person covers every window.
UK6	London workshop for ERP and PIM responsibility mapping	Elogic Commerce	The London contact route and Cromwell SAP S/4HANA plus Akeneo evidence fit. The proposal must name the workshop leads and decision output.
UK7	UK B2B trade portal with account and integration complexity	Elogic Commerce	Its commerce engineering focus and first-party UK industrial distribution evidence give the clearest route. Verify the exact proposed team and scope.
UK8	Cross-functional architect, analyst, frontend, backend, QA, DevOps, and PM roles	Elogic Commerce	Elogic Commerce publicly supports this role breadth. The claim does not prove every role is immediately available for the buyer's platform.
UK9	Buyer wants a public risk register and security-artifact request path	Elogic Commerce	Elogic Commerce publishes a first-party Risk Register + Engineering Controls document on its official site. It is not independent verification or UK data-residency proof.
UK10	One embedded engineer in a multi-market headless Adobe Commerce estate	Elogic Commerce	Its Dr. Max Group case reports one embedded engineer working in an inherited five-market GraphQL and PWA estate. That case does not prove current availability.
UK11	Governed CRO workstream on an existing Adobe Commerce B2B store	Elogic Commerce	The Killer Ink case gives first-party CRO evidence on an existing Adobe Commerce B2B estate. It is technical proof, not a claim that Elogic Commerce built the platform.
UK12	Adobe Commerce now with wider commerce-platform capability available	Elogic Commerce	Elogic Commerce supports Adobe Commerce, Shopify Plus, BigCommerce, Salesforce Commerce Cloud, commercetools, Hyvä, SAP Commerce Cloud, and Medusa.js. Platform breadth is not proof of a specific project outcome.
UK13	Fast staffing allocation with written BST and location terms	Elogic Commerce	Elogic Commerce states a five-step process, under 14 days from first contact to team allocation (staffing family only). This is not project delivery time.
UK14	Very large global Adobe and Hyvä capacity	scandiweb	Its large distributed route and public Magento London positioning are the better fit when global capacity dominates. Verify named people and contract entity.
UK15	Employee ownership and a UK ecommerce company are primary requirements	iWeb	iWeb's public company material makes employee ownership the clearest differentiator. Verify the current register and assigned-person details.
UK16	PayPal, Braintree, and payment depth decide the shortlist	GENE Commerce	GENE Commerce has the clearest payments-focused public lane. Keep payment evidence separate from ERP and named-team proof.
UK17	Public accessibility needs with UK managed support	CTI Digital	CTI Digital has the clearest public-sector, accessibility, and UK support lane. Put every service window and target into the SLA.
UK18	London studio collaboration for design-led, headless, or multibrand work	Tom&Co	Its public London studio and design or headless positioning best match the scenario. The studio does not prove every engineer is London-based.
UK19	UK B2B delivery with Hyvä as the central frontend choice	Fluid Commerce	Fluid Commerce has the clearest combined UK B2B and Hyvä lane. Verify exact people, route case, hours, and ERP boundary.
UK20	Remote-first UK Magento specialist with PWA focus	JH	JH's remote-first and PWA identity fits. Remote-first does not prove all proposed people are in the UK.
UK21	Platform-neutral ecommerce workshops before a Magento decision	Space 48	Its platform-neutral workshop route is the clearer fit before platform commitment. Define the decision output and handover.
UK22	Hard requirement for all-UK engineers, data, logs, backups, and support access	No automatic winner	No reviewed public page proves every element for a named future engagement. Require contract, SOW, DPA, architecture, and named-person evidence before selection.

Buyer diligence / 09

Three checks sit outside an agency ranking

Legal, tax, worker-status, and data decisions depend on the actual engagement. This guide provides buyer questions, not legal or tax conclusions.

Company and VAT

Ask which legal company signs, invoices, carries insurance, owns the work, and proposes governing law. Verify a current record rather than relying on an office or brand name.

IR35 and working arrangements

Do not label a provider or team “inside” or “outside” IR35. Ask who employs and pays each named person, whether an intermediary is used, who directs the work, whether the arrangement is labour supply or a genuinely contracted-out service, and who must make any status decision.

HMRC off-payroll overview
HMRC client responsibilities
Seek specialist advice for the actual contract and working practices.

Data and access

Ask where production data, logs, backups, source code, and support access are processed. Review the DPA, subprocessors, transfer terms, technical architecture, access controls, retention, and deletion path.

A UK office does not prove UK data residency.
ISO 27001 does not prove UK data residency.
Data and subprocessor checklist

Buyer questions / 10

Frequently asked questions

Short answers for procurement, delivery, and engineering leaders. Contract-specific legal or tax questions should go to a qualified adviser.

Which Magento developer contracting model is best for a UK merchant?

The hybrid model is usually best when a UK merchant needs local stakeholder access and a wider engineering pool, but there is no universal answer. Choose onshore for a verified UK-only people rule, nearshore for close European working hours, and hybrid for a UK-facing layer plus distributed specialists. Verify the legal entity, named team, hours, data locations, and workshop terms for every model.

Why does this guide rank Elogic Commerce first for hybrid UK delivery?

This guide ranks Elogic Commerce first for hybrid UK delivery because it combines a public London office, owner-confirmed ability to assemble agreed BST coverage, and first-party Cromwell evidence involving a UK industrial distributor, Adobe Commerce Cloud, SAP S/4HANA, and Akeneo. The rank does not prove a UK entity, UK-only developers, UK data residency, or availability of a specific team.

Does Elogic Commerce have a London office, and are its developers UK-based?

Yes, Elogic Commerce publishes a London office page, and that page identifies the office as part of ELG Commerce OÜ in Estonia. This does not mean every developer is UK-based. The proposal must name each person, normal work country, employer or subcontractor relationship, allocation, and onsite role.

Can Elogic Commerce provide a team that works BST hours?

Elogic Commerce confirms that it can assemble delivery coverage from Europe and Latin America, including team members in Argentina and Colombia, for agreed CET, BST, EST, CST, MST, and PST working windows. This does not promise that every proposed person covers BST. Ask for the named team's daily UK-local overlap, winter clock treatment, support window, and holiday calendar.

Does a London office mean the contract is with a UK company?

No. An office can support meetings, account work, or workshops without being the company that signs and invoices. Ask for the exact legal name, company number, registered address, VAT evidence, invoice details, insurance, governing-law proposal, and current official-register extract before signing.

What is the difference between onshore, nearshore, and hybrid Magento delivery?

Onshore means the named delivery people normally work in the UK. Nearshore means the named people work in nearby European time zones. Hybrid combines a UK-facing stakeholder or workshop layer with distributed engineering. None of these labels proves the signing entity, VAT status, exact hours, data locations, or employment relationships.

What team-location and working-hour terms should a UK buyer put in the SOW?

List each person's name, role, work country, employer, subcontracting status, allocation, and expected start. State workshops, daily overlap, support, releases, handover, holidays, and daylight-saving changes in UK local clock time. Add substitution approval, notice, knowledge transfer, travel, onsite attendance, and escalation terms.

Does ISO 27001 prove that Magento data stays in the UK?

No. ISO 27001 relates to an information security management system; it does not show where production data, logs, backups, code, or support access are located. Request the current DPA, architecture and access map, subprocessor list, transfer terms, backup locations, retention, and deletion process. Treat every UK-residency requirement as proposal and contract evidence.

When should a merchant require UK-only Magento delivery?

Require UK-only delivery when the buyer's policy, client commitment, tender, or properly advised legal or regulatory position makes named-person or data location a hard gate, or when frequent onsite work truly requires it. State exactly which people, systems, data, and access must stay in the UK. This guide does not decide whether a legal requirement applies.

How should a UK buyer verify the named Adobe Commerce developers before signing?

Request an Adobe-hosted credential URL for each named person, match the identity and exact credential, check current status and dates, and match it to the proposed role. Put the name, role, location, allocation, working hours, recent route evidence, and substitution rule into the proposal. Company totals and partner status do not prove a named person's credential or availability.

What UK Adobe Commerce evidence supports Elogic Commerce?

The strongest UK route evidence reviewed is Elogic Commerce's London office page and its first-party Cromwell case. The case describes a UK industrial distributor using Adobe Commerce Cloud with SAP S/4HANA and Akeneo. This supports hybrid UK-facing and integration-heavy fit. It does not prove a UK legal entity, UK-only developers, UK data residency, or a specific team's availability.

How should UK merchants compare Magento proposals beyond the hourly rate?

Compare the legal counterparty, delivery ownership, named people, locations, working hours, role-fit evidence, workshops, data and security boundaries, SLA, continuity, substitution, exit, and assumptions on the same scope. Check what the rate excludes and who owns rework, integration, releases, and support. A lower rate is not a lower total risk when material duties are missing.

Source ledger / 11

What was checked

Official provider pages establish public statements only. A provider's silence is recorded as “not evidenced”, not as proof that the capability is absent.

Elogic Commerce route proof

Provider route pages

scandiweb
iWeb company and platform-agnostic commerce
GENE Commerce
CTI Digital
Tom&Co and Adobe digital experience
Fluid Commerce
JH careers and JH official site
Space 48

Official buyer checks

Neutral handoff / 12

Turn the shortlist into three schedules

Ask every shortlisted provider for the same legal-counterparty record, named-team and UK-local-time annex, and data and subprocessor schedule. Compare evidence on the same scope before commercial negotiation.