Magento store development
Fixes, extensions, theme changes and upgrades on Magento 2 and Adobe Commerce stores.
GradaxEuropean companyOrder outright
Founded 2014·Built and operated in Europe·3 days to 4 weeks

About this service
Magento is powerful and unforgiving. Extensions conflict, upgrades break themes and caching hides problems until a sale day. We work on existing Magento 2 and Adobe Commerce stores: installing and configuring extensions, fixing bugs, making theme changes, and preparing or carrying out version upgrades, always on a staging copy first.
Magento rewards discipline
Magento stores that run well share one trait: changes are made the Magento way. Extensions are installed through Composer, custom code lives in modules, theme changes live in a child theme, and nothing in the core is edited. Stores that run badly have the opposite history: extensions copied into folders by hand, quick fixes made directly in vendor files, and nobody sure what has been changed.
The second kind of store breaks on every upgrade, because the upgrade overwrites the edits or clashes with them. Before starting any work, we review how the store has been built and tell you plainly what we find. Sometimes the most useful first job is moving existing hacks into proper modules, so everything after that becomes cheaper.
Staying on a supported version
Adobe publishes support end dates for each Magento 2 version. After that date, security patches stop. Stores on unsupported versions carry real risk: payment data skimming attacks have targeted outdated Magento stores for years. Upgrading becomes harder the longer it is left, because each skipped version adds changes to absorb.
The largest package audits every extension and custom module for compatibility with the target version, carries out a minor upgrade on staging, and lays out a plan for the rest. Major upgrades on heavily customised stores are quoted after that audit, because their cost depends on what it finds.
What you get
Everything below is in the price. Nothing here is an upgrade.
- Requested changes, fixes or extensions
- Staging environment use and deployment
- Code committed to your repository
- Change notes and test record
What changes
- Work done on staging, deployed with a tested rollback
- Extensions installed through Composer, not copied into the codebase
- Changes kept in a custom module or child theme, never in core files
- Indexing, caching and cron checked after every change
How it runs
Assess
Version, extensions and customisations reviewed before changing anything.
Develop
Work done on staging, in modules or child themes.
Test
Checkout, indexing and caching tested after changes.
Deploy
Released with maintenance mode kept short and a rollback ready.
Compare the sizes
The standard price for each size. Extras are priced beside it, not hidden behind a call.
| Included | Small tasks€2903 to 5 working days | Development block€5001 to 2 weeks | Upgrade readiness€1,0502 to 4 weeks |
|---|---|---|---|
| Up to three small tasks or one extension | Included | Included | Included |
| Staging test | Included | Included | Included |
| Deployment | Included | Included | Included |
| Change notes | Included | Included | Included |
| Theme changes | Not included | Included | Included |
| Extension conflict diagnosis | Not included | Included | Included |
| Performance check after deployment | Not included | Included | Included |
| Upgrade compatibility audit of extensions and custom code | Not included | Not included | Included |
| Minor version upgrade carried out on staging | Not included | Not included | Included |
| Upgrade plan for the remaining steps | Not included | Not included | Included |
| Order | Select | Select | Select |
Add what you need
Choose the size
Add what you need
Your total€500
ContinueThe standard price, plus whatever you add. Confirmed in writing before anything starts; nothing is charged until you accept it.
Questions
Do you work on Magento 1?
Magento 1 stopped receiving security updates in 2020. We help plan a move off it, but we do not take on new development for it.
Can you do a major upgrade?
The largest package audits and starts it. A major upgrade on a heavily customised store is usually quoted separately after that audit.
We have no staging environment. Is that a problem?
We set one up first. Working directly on a live Magento store is how most outages happen.
Related searches
Related work
One-timeE-commerce website developmentCustom shop features and integrations built on your platform: product configurators, ERP sync, custom checkout logic.from €350one-time
One-timeSite speed optimisationMeasured, fixed and measured again, with the numbers from your real pages.from €490one-time
One-timeWebsite security hardeningYour website locked down: updates, logins, permissions, firewall and backups checked and fixed.from €290one-time
Order it
Standardised enough to order on its own. The price is confirmed in writing before anything starts.