Scoping Magento development work before you ask for quotes
A comparable brief separates platform maintenance, presentation-layer replacement and custom product work, then defines ownership, evidence and acceptance before agencies price the project.
Why three quotations often describe three different projects
A useful brief does more than list pages and features. It establishes what is changing, what must remain in place, which risks the agency is accepting and what the merchant will receive at the end.
Without that definition, three agencies can each produce a sensible figure for a different scope. One may be quoting the Magento version upgrade, another a new storefront and the third a catalogue of custom functionality. The figures are not comparable because the underlying assumptions are not comparable.
This matters particularly for Magento development services. Magento stores tend to accumulate extensions, custom modules, integrations and operational work over time. The visible catalogue may look straightforward while the implementation contains several dependencies that must be assessed before anyone can estimate the work responsibly.
Start with the current and target states
Name the current Magento or Adobe Commerce version, the target version and the reason for the change. Distinguish the version in production from the version in the development environment. If they differ, state which one is authoritative.
As of 13 November 2026, the current general release is Magento Open Source and Adobe Commerce 2.4.9, released on 12 May 2026. The 2.4.10-alpha1 pre-release appeared on 13 October 2026 and is not suitable for production. A production brief should not quietly use that alpha as its target.
The target should also be a supported choice. Regular support for 2.4.9 runs to 31 May 2029, while 2.4.8 runs to 31 May 2028 and 2.4.7 runs to 31 May 2027 with extended support to 31 May 2028. Regular support for 2.4.6 ended on 11 August 2026. Magento 1 reached end of life on 30 June 2020, so an upgrade from that platform is a substantial migration rather than a routine update.
For an on-premises 2.4.9 deployment, the brief should identify the intended platform combination. Adobe lists only PHP 8.5 with MariaDB 12.3 or MySQL 8.4, OpenSearch 3, Valkey 9 for cache and sessions, RabbitMQ 4.3 and Composer 2.10. Elasticsearch and Redis are not listed as supported for 2.4.9.
That last point needs to be handled plainly. A quotation that assumes Redis or Elasticsearch without identifying a supported replacement is not quoting the stated 2.4.9 platform. It may still be valid technical work, but it belongs under a separately stated assumption and risk.
Describe the catalogue, not merely its size
Give the number of products and the shape of the catalogue. A thousand simple products and a hundred configurable products create different data, search, checkout and import requirements. Record the relevant product types, including configurable, downloadable, bundle and grouped products where they are used.
| Brief item | What to specify |
|---|---|
| Catalogue volume | Live products, variants, categories and customer groups. |
| Catalogue behaviour | Product options, custom options, bundles, downloadable files and complex prices. |
| Content | CMS pages, blocks, product copy, images, videos and translations. |
| Data volume | Orders, customers, invoices, abandoned carts and imported records. |
| Data quality | Duplicate values, missing identifiers, inconsistent attributes and import constraints. |
Distinguish catalogue data from implementation code. The merchant must own the product information, customer data, orders, media, metadata and business rules needed to export and restore it. An agency should not treat an export from the live database as a complete backup or migration package.
List every extension and customisation
Provide an inventory rather than asking each agency to discover everything from scratch. Include extensions, patches, themes, custom modules, payment methods, shipping methods and plugins. Record their versions, purpose, supplier, licence holder and compatibility with the target Magento version.
Mark which items are essential, which are merely desirable and which are being retired. Include code held in the merchant’s repository, because custom code is often more dangerous during an upgrade than a purchased extension. A precise inventory also gives agencies a fair basis for estimating compatibility work.
For a storefront rebuild, identify the starting point. Luma is the default Magento storefront theme, built on LESS, Knockout.js and RequireJS, with Blank as its parent theme. A quote that refers only to “the Magento theme” does not say whether it will preserve that structure, adapt it or replace it.
Hyvä needs similar precision. The theme became free and open source on 10 November 2025, but Hyvä Checkout, Hyvä Commerce and Hyvä Enterprise are separate paid products. Hyvä is built on Tailwind CSS and Alpine.js rather than Knockout and RequireJS. The quotation should separate the theme, checkout and any commercial or enterprise components.
If PWA Studio is in scope, state whether the agency is proposing an Adobe React-based headless storefront, an integration with an existing headless front end or simply using PWA Studio components. Those are different architectures with different responsibilities.
Map the integrations
List every system that exchanges data with Magento. Include ERP, PIM, CRM, payment gateways, shipping providers, tax services, marketplaces, email platforms, customer support tools, accounting systems, analytics and translation services.
For each integration, state the direction of data flow and the volume involved. Record which credentials, APIs, webhooks, scheduled jobs and middleware are already in use. Note any known limitations, such as intermittent imports, manual reconciliation, unsupported API methods or vendor-maintained extensions that lag behind the platform.
Separate required integrations from optional improvements. Otherwise, a proposal can include a large integration programme under a heading such as “connect the ERP” while giving no indication of its complexity.
Say who owns hosting and delivery
State where the current environment lives, who operates it and whether the merchant has a hosting relationship or an agency-managed arrangement. A hosting quote cannot be compared with a self-managed infrastructure quote unless both include the same responsibilities: patching, backups, monitoring, TLS, email delivery, DNS, security controls, scaling and incident response.
Do not confuse the cloud provider with the party responsible for Magento. A managed cloud account can still require an agency to configure the application, database, search, queue, cron jobs and deployment pipeline. The brief should identify who holds administrator access, who can authorise releases and who responds when the application is unavailable.
Include the target environments. Specify development, staging and production, expected data handling, deployment approvals and access to source control and CI. If the merchant cannot yet provide a staging environment, say so. That is a workstream and a cost, not an assumption to leave out.
Define what “done” means
Acceptance criteria are what turn an estimate into a scope. They should cover functional behaviour, data migration, integrations, administration, performance, accessibility, security, SEO preservation, documentation and support handover.
Describe critical journeys rather than referring to “the site working”. A useful acceptance list might include search, product navigation, variation selection, add to basket, checkout, payment, tax, shipping, account creation, order placement, invoice generation, order status changes, refunds and administrative editing.
Set the evidence required for approval. Decide whether testing must include independent user-acceptance testing, automated regression coverage, migration reconciliation and a documented release checklist. Performance criteria should describe the pages, data volumes, devices and conditions being tested. Without that context, a performance claim has no stable meaning.
State the cutover conditions and rollback plan. Include who signs off, what happens if the rehearsal identifies errors and how long the previous release remains recoverable. Ownership of the final repository, credentials, documentation and production access should appear in the brief rather than being negotiated after handover.
Keep the three kinds of work apart
Most misleading Magento website development estimates combine a version upgrade, a storefront rebuild and new functionality. Each needs its own discovery, risks and acceptance criteria.
| Work type | Principal risk | Useful boundary |
|---|---|---|
| Version upgrade | Extension conflicts, custom-code failures, incompatible infrastructure and data migration. | Platform, dependencies, custom modules, integrations, regression testing and deployment. |
| Storefront rebuild | Loss of catalogue behaviour, checkout coverage, content control or operational familiarity. | Theme architecture, responsive templates, accessibility, performance, SEO continuity and training. |
| New functionality | Unclear business rules, new integrations and custom maintenance burden. | User journeys, data models, admin screens, APIs, tests and acceptance criteria. |
A single programme can still deliver all three, but it needs separate estimates or clearly identified work packages. Combining them hides whether the main uncertainty is technical compatibility, design coverage or product definition.
Questions that reveal competence
Ask agencies to explain how they will reach an estimate. A credible answer addresses discovery, dependencies and evidence. It does not treat the first feature list as a complete specification.
- Which parts are upgrade, rebuild and custom development? The answer should identify boundaries and the risks within each.
- How will extension and custom-code compatibility be established? Expect an inventory and targeted testing, not a claim that everything should work.
- What happens to the current search, cache and session services? For 2.4.9, the response should acknowledge the supported combination rather than hand-wave the migration.
- How will catalogue and order data be reconciled? Counts and sample checks are weak substitutes for field-level reconciliation.
- Which critical journeys will be tested, and where? The answer should cover staging and a release rehearsal.
- Who owns the repository and deployment pipeline? There should be a clear transfer point and documented access model.
- How is a failed release recovered? Backups, rollback and decision authority should be named.
- What is excluded? Scope exclusions often tell you more than the feature total.
Answers that should cause concern
“It is just a version update” is unhelpful unless the agency can explain the extension inventory, custom code, infrastructure changes and regression scope. “We will make the new design pixel-perfect” shifts appearance approval ahead of catalogue, checkout and integration behaviour.
“The free theme covers everything” is a warning sign when checkout, commercial components, custom templates or migration work are involved. “Headless will improve SEO and performance” is not a scope or acceptance criterion. A dependable answer describes the implementation, preservation work and tests.
“It will all work after the upgrade” substitutes confidence for evidence. The same applies to “there is no need for staging” and “we will handle everything” without naming repository, hosting, credentials and data ownership.
Be cautious with a fixed price offered before discovery. It can be appropriate for a well-defined and tested scope, but the agency still needs to state assumptions and a change-control process. A price with no definition of those matters is not comparable with another price.
Ownership must remain with the merchant
Whatever the project type, the merchant must retain the hosting relationship or a deliberate, documented alternative; ownership of the source repository, deployment configuration and project accounts; and an exportable copy of catalogue and business data.
Agency access should be based on named roles, revocable credentials and clear handover. Licence ownership and renewal responsibility should be recorded for every paid component. This avoids a rebuild that works but leaves the merchant dependent on files, accounts or vendor relationships held elsewhere.
Ask for quotations in the same structure
Give every agency the same brief and request the same response format: assumptions, work packages, exclusions, deliverables, acceptance tests, repository and access arrangements, third-party dependencies, risks and change control.
The finished brief does not remove uncertainty. It makes uncertainty visible, gives agencies something consistent to assess and makes the returned quotations capable of comparison. That is the point before Magento development work begins.
Questions this page answers
- What should a Magento brief state about versions?
- Name the current Magento or Adobe Commerce version, the target version and the reason for the change. Distinguish production from the development environment and identify which is authoritative.
- How should a brief describe the catalogue?
- Give the number of products and the catalogueu2019s shape. Record relevant product types, catalogue behaviour, content, data volumes and data-quality issues.
- What should be included in an extension and customisation inventory?
- Include extensions, patches, themes, custom modules, payment methods, shipping methods and plugins. Record versions, purpose, supplier, licence holder and target-version compatibility.
- What should define completion of Magento development work?
- Set acceptance criteria covering functional behaviour, data migration, integrations, administration, performance, accessibility, security, SEO preservation, documentation and support handover. Describe critical journeys and the evidence required for approval.