Start with an audit

Let’s talk.

Tell us what you’re working on. A person from the team replies to every enquiry, with a time for a 30-minute call.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.
Specialist service · magento development company

Magento development & migration

Stay on Magento when you need complex B2B pricing, multi-store setups or deep ERP integration; migrate when maintenance and hosting costs outweigh those needs and a SaaS platform covers your catalogue and checkout.

Product Engineering practice: abstract red and ink artwork from the Red Balloon reel

Magento, whose commercial edition is now Adobe Commerce, still runs stores that need complex catalogues, B2B pricing and several storefronts, and it punishes neglect. Red Balloon is a Magento development company for electronics retailers, pharma distributors, industrial suppliers and multi-brand sellers on Magento 2 or Adobe Commerce. We take over stores that have fallen behind on patches, stabilise ERP and inventory syncs, speed up indexing and checkout, and plan upgrades in safe stages. When the platform no longer fits, we plan and run migrations to Shopify, WooCommerce or headless builds with redirects and data intact. Magento development cost depends on extensions, customisations, integrations and how far behind the current release you are.

What drives Magento development cost

Magento development cost is set less by the store's size than by its history. The main drivers are how far the store sits behind a supported release, how many extensions and custom modules must be tested or replaced, and how many systems it talks to, such as an ERP, an order management tool or a PIM. Adobe Commerce adds a licence and often managed cloud hosting; Magento Open Source shifts that cost to your own servers and team.

B2B features, multiple storefronts, several currencies and a large product or customer database all add testing time. So do undocumented changes made by earlier developers, which only show up during the audit. That is why we do not quote before looking at the code. As a Magento development company in India working for brands across the country, we price the audit first, then give a fixed plan for the upgrade or migration it recommends.

Keeping the business running while the platform changes

An upgrade or migration takes weeks, and your trading calendar does not stop for it. We plan around your sale dates first, so no cutover lands in the run-up to a festive peak. Feature requests are split into two lists: changes that must ship on the current store and changes that can wait for the new one. That avoids building the same thing twice and keeps the release scope stable.

Merchandising teams keep working in the live admin throughout. Product, price and content changes made during the project are synced or re-imported before cutover, and we agree a short content freeze for the final days. Your business testers get written scripts for the journeys that matter, from B2B quotes to returns, so acceptance testing reflects how the store is actually used rather than a developer's guess.

How the store connects to ads, search and your own data

A Magento store feeds much of your marketing. Product feeds go to Google Merchant Center and Meta catalogues, purchase events go to GA4 and the ad platforms, and category pages carry much of your organic traffic. Our Performance Marketing and Search & Content teams check all three before any release, so a technical upgrade does not quietly break a product feed, a conversion tag or a set of ranking URLs.

The AI & Automation practice often picks up work the store exposes, such as enriching thin product descriptions or routing B2B quote requests to the right salesperson. Throughout, the code repository, hosting accounts, extension licences and admin users stay in your company's name. If you later bring development in-house, your team inherits documented code and working deployment pipelines, not a dependency on us.

Where this works

Real-world situations we're built for

Illustrative · not a client
Electronics retail (Delhi, Nehru Place)

Magento 2.4.3 store, months behind on patches, slow reindexing; team debating a move to Shopify Plus.

What we'd do
Security patching first, then an upgrade-versus-replatform cost comparison with extension and integration inventory.
What moves
Days behind the latest security patch down to zero; upgrade-or-replatform decision made on total cost.
Pharma B2B distribution (Hyderabad)

Adobe Commerce B2B with custom pricing per chemist; ERP sync failures show wrong stock.

What we'd do
Queue-based ERP integration, shared catalogue pricing, sync monitoring and retry logic.
What moves
Sync failures down, order accuracy up; tracked as failed ERP sync messages before and after, over a fixed period
How a project runs

4 phases, each with a deliverable

What happens, how long it takes, what you get and what we need from you.

Audit

1–2 weeks

Code, extensions, patch level, infrastructure, integrations, data size.

You get: Audit and recommendation.

We need: Code repository, server and admin access.

Secure and stabilise

1–3 weeks

Patches, WAF, admin hardening, monitoring.

You get: Hardened store.

We need: Approval for maintenance windows.

Upgrade or migrate

6–16 weeks

Version upgrade, or data and design migration to the chosen platform.

You get: Staging store passing tests.

We need: UAT testers from business teams.

Run

Monthly

Patching, monitoring, performance and feature work.

You get: Monthly report.

We need: Product owner for priorities.

A typical engagement

From first call to result

Illustrative · not a client

Mumbai home appliances brand on Magento Open Source 2.4.4, 9,000 SKUs, SAP Business One ERP.

Weeks 1–2AssessExtension and custom module audit, patch status, infrastructure and integration review.Upgrade-versus-migrate cost comparison.
Weeks 2–3SecureApply security patches, add WAF, admin 2FA and file integrity monitoring; check first for unknown admin users and changed checkout files.Known vulnerabilities closed.
Weeks 3–10UpgradeMove to a supported 2.4.x release with PHP and OpenSearch upgrades; replace abandoned extensions.Upgraded staging passing regression tests.
Weeks 8–11PerformanceVarnish full-page cache, Redis, indexers set to Update by Schedule, load test at festive peak.Load test report at target traffic.
Week 12ReleasePlanned cutover with bin/magento maintenance:enable, rehearsed rollback, monitoring and on-call cover through the first sale.Upgraded production store.
Where it startsPHP 8.1, 60 extensions, 14 custom modules, site crashed during last festive sale, no WAF.
Where it endsThe brand runs a supported, patched Magento; it watches patch lag, p95 page time under load and ERP sync errors weekly.
What we measure

The numbers we report on

Every metric has a formula, a target, a source and a reporting rhythm.

MetricHow it's calculatedTargetSourceCadence
Patch lagDays between an Adobe security patch release and its deployment to production.Critical (CVSS 9.0+) patches deployed as soon as tested; all others within your agreed window.Adobe security bulletins, deployment logPer bulletin
p95 response under load95th percentile response time at expected peak in a load test.Set from baseline; aim to hold it steady at sale-peak traffic.k6 or JMeter, New RelicBefore each sale
Full-page cache hit rateCache hits ÷ cacheable requests × 100.Rule of thumb: 90%+ of category and product views from cache; below that, look for blocks marked cacheable=false in layout XML.Varnish stats or FastlyWeekly
Indexer backlogItems waiting in Magento index queues.Near zero outside bulk imports.bin/magento indexer:status, New RelicDaily
Integration error rateFailed ERP or OMS sync messages ÷ total sync messages × 100.Set from baseline; aim for near zero with automatic retries.RabbitMQ, application logsDaily
Automated by default

What runs itself after launch

The manual work we take out of this service, and the tools we use.

When: New Adobe security bulletin.Patch alerts and pipelineAdobe security bulletin alerts to Slack; patch applied via Composer and deployed to staging by CI.Removes: Shortens exposure to known exploits.
When: Daily and after every deploy.Malware and integrity scansSansec eComscan or similar scanning for card skimmers and changed files.Removes: Detects skimmers before customers' cards are stolen.
When: Merge to main.DeploymentsGitHub Actions or Bitbucket Pipelines building static content and releasing with near-zero downtime.Removes: Removes risky manual deploys.
Rules we work to

Standards and regulations

PCI Security Standards CouncilPCI DSS v4.0 requirements 6.4.3 and 11.6.1

Inventory and authorise payment-page scripts and detect tampering; mandatory since 31 March 2025.

AdobeAdobe Commerce security best practices

Guidance on admin URL, 2FA, file permissions and patching for Magento and Adobe Commerce stores.

Department of Consumer AffairsConsumer Protection (E-Commerce) Rules 2020

Store disclosures and grievance handling apply whatever the platform.

What's changing

Platform and policy updates that affect this work

We track: Adobe Security Bulletins for Adobe Commerce, Adobe Commerce release notes and lifecycle policy.

AdobePatched CosmicSting (CVE-2024-34102), a critical flaw later exploited at scale on unpatched Magento stores.

Unpatched stores are actively attacked; patch lag is a business risk.

AdobeReleased Magento Open Source and Adobe Commerce 2.4.8 with support for newer PHP and service versions.

Plan upgrades from older 2.4.x lines before their support ends.

Before you hire anyone

Questions to ask any agency, including us

How many of our extensions are still maintained?

Why ask

Abandoned extensions block upgrades.

A good answer

Extension list with vendor status, compatibility with the target version and replacements.

How do you test custom modules before an upgrade?

Why ask

Custom code breaks silently.

A good answer

Regression suite, staging with production-like data, and UAT scripts for business teams.

Who on your team has shipped Magento 2 upgrades before?

Why ask

Magento has a steep learning curve.

A good answer

Named developers, Adobe certifications or demonstrable Magento 2 upgrade work you can check.

FAQ

Questions buyers ask us

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

How do you keep a Magento store secure?

We apply Adobe's security patches promptly, keep extensions to a vetted list, enforce two-factor authentication and IP restrictions on the admin, and run malware and file-integrity scans.

  • CosmicSting (CVE-2024-34102) showed how quickly unpatched Magento stores are exploited after disclosure.
  • Payment-skimming scripts are a known Magento threat; a content security policy, script monitoring and Adobe's isolated patches between scheduled releases close most of that gap.
What hosting and infrastructure does Magento 2 need?

Magento 2 needs PHP-FPM, MySQL or MariaDB, OpenSearch, Redis, Varnish and often RabbitMQ, on servers sized for your catalogue and traffic, ideally in an Indian cloud region.

  • Adobe Commerce Cloud includes managed infrastructure; Magento Open Source stores manage their own, and recent releases support OpenSearch rather than Elasticsearch.
  • Load-test indexers and cron jobs before festive sales; a full reindex running during peak traffic is a classic Magento slowdown.
Is Adobe Commerce worth the licence fee over Magento Open Source?

Only if you will use what the licence adds. Adobe Commerce includes built-in B2B features such as company accounts, shared catalogues and quote requests, Adobe support, and an optional managed cloud. Many stores on Open Source cover similar needs with vetted extensions and their own hosting. We compare both against your actual B2B, staffing and hosting needs before recommending either, and the answer is often Open Source.

  • Built-in B2B features and support
  • Open Source plus extensions often enough
  • Decide on actual needs, not features
Can you take over a Magento store built by another agency?

Yes, and it is a common starting point. We begin by moving code into a Git repository you own, collecting every server, admin and extension login, and checking for unknown admin users or changed files. Custom modules are documented as we read them. Within the first weeks you know what the store is made of, what is risky, and what it will take to keep it patched.

  • Code moved into your own Git repository
  • Access and security checked first
  • Custom modules documented
Back to the service

E-commerce development →

Start with an audit

Ready for
lift?

A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.

Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.

A person from the team replies to every enquiry.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.