Tangensys • Plan, deliver, measure
Magento development
Use Adobe Commerce or Magento where the catalogue and business rules justify the operational effort. Review the existing installation before choosing an upgrade path.
The work to plan together
A scope shaped around this requirement.
- Upgrades and migrationsScope
- Custom modulesReview
- Performance tuningCheck
- VisitorArrives on a phone or desktop
- NavigationFinds the right page quickly
- Form or integrationEnquiry, booking or order
- Your teamReceives it in the right place
In short
What does Magento development involve?
Magento (Adobe Commerce) development builds, upgrades and maintains large online stores on Magento.
When Magento development is a useful fit
Large catalogues
Review catalogue navigation, search and product-data quality before changing templates.
B2B ecommerce
Map trade accounts, order rules and integrations that retail defaults do not cover.
Stores on older Magento versions
Inventory extensions and data dependencies before planning an upgrade or migration.
Problems worth addressing first
Use these situations to identify the work that deserves attention before expanding the scope.
- The store needs upgrading
- Performance is poor
- Extensions conflict
A practical example
A multi-store catalogue may share product data but use different prices and inventory rules. Changes must be checked across the relevant store views.
This is an illustrative scenario to explain the approach, not a claimed client project.
The work we can include
The final quote identifies the deliverables, quantities, approvals and exclusions. Select the work that serves your goal rather than assuming every item is required.
- Upgrades and migrations
- Custom modules
- Performance tuning
- Maintenance
Where we usually begin
Version compatibility, extension licences, infrastructure and migration effort are established in discovery. A complex store needs a supported maintenance plan.
Practical detail
Review store rules before releasing an extension
For a store with several customer groups, a price-rule change can affect much more than one product page. Test the rule against representative carts and store views.
| Part of the work | Example output | How to review it |
|---|---|---|
| Dependency review | Platform version, extensions and custom overrides | Conflicts and unsupported components are identified before implementation. |
| Pricing regression | Customer group, discount, tax and store-view cases | The approved rule produces the expected totals without stacking unintended discounts. |
| Staging release | Catalogue, checkout and integration checks | Existing important buying and fulfilment journeys still work. |
| Recovery handover | Release version, backup and rollback route | A failed deployment has a defined recovery owner and instructions. |
The edition, version and extension ecosystem change the scope. A proposal should identify those dependencies instead of promising an interchangeable upgrade.
Scope the change around catalogue and operating complexity
Magento development often involves a catalogue, business rules and integrations that need more than a page-level change. Begin with the actual version, extensions and deployment process. The supported approach depends on that environment and the complexity of the requested behaviour.
For ordering or pricing work, document a representative customer and product journey. Include the conditions that change the result, such as customer access or stock state. Separate configuration changes from custom development so the proposal makes testing and maintenance responsibilities clear.
Sign-off needs staging evidence and relevant regression checks. A release should identify database or configuration effects and recovery steps where applicable. Existing performance or compatibility problems can require investigation before a delivery estimate is reliable.
Free technical review
Start with a clear scope and a practical next step.
Tell us what you want to improve and share the relevant website or project details. We will review the starting point, recommend a suitable scope and provide a custom quote.
The initial review is free. Delivery, third-party charges and ongoing support are quoted separately.
Process
How the work is delivered
Review the starting point
Review the current setup, examples of the problem and the information needed to agree the work.
Agree scope and sign-off
Discovery covers existing code, users, data and external systems. We turn the main workflow into sign-off checks, then agree milestones and responsibilities.
Deliver and review
Changes are reviewed on a test environment before release. Handover includes agreed documentation, access and a maintenance route; ongoing support is separately defined.
Hand over the next steps
Review the agreed outputs together. Confirm what your team maintains and what needs a separate ongoing arrangement.
What progress should mean
Measures that match the work
Track agreed feature sign-off, catalogue performance, order integrity and upgrade regressions. Document which environments and extensions were tested.
A record of delivery
See what was completed, reviewed and still dependent on access or approvals. Project delivery and business results are reported separately.
Clear limits in the data
We explain what can be verified and where a result is only an estimate. Contact clicks, conversations and sales are different actions.
Scope and responsibilities
You keep ownership of your business accounts and approved deliverables under the agreed contract. Any third-party licences, subscriptions or usage fees are identified before you commit.
What information helps estimate a Magento development task?
Share the version, environment, extensions, affected journey and desired outcome. Repository, staging and integration documentation can help a technical review. If the cause or dependencies are unknown, agree a discovery task before committing to the full build.
Can you work with a customised store?
We first review the customisations and important workflows. Hidden overrides or unsupported extensions may require discovery before reliable pricing.
Does an upgrade include all extension replacements?
Only those listed. Extension licences, rewrites and separately owned integrations need explicit agreement.
Should we stay on Magento?
It suits complex stores; we compare options in your plan.
How is Magento development priced?
We quote against your goals, current setup and agreed scope. The quote separates delivery from third-party costs and ongoing support. You receive a custom quote within 2 working days.
How long does the work take?
The timeline follows the size of the agreed scope, access, content and approvals. We confirm milestones in the quote; a simple change and a full implementation need different schedules.
How will we communicate?
Your point of contact agrees a review rhythm with you. We use email, WhatsApp and scheduled calls, with decisions and scope changes recorded clearly.
What do you need to get started?
Share your current website or system, your main goal and examples of what is not working. We then agree the access and information needed for discovery.
Is everything included in the free review?
No. The free initial review helps define the next step. Detailed research, design, implementation and ongoing support are included only when stated in your quote.
Explore the related services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days