Adobe Commerce (Magento) Development

Yes. Upgrades, security patching and version migrations are ongoing work for us rather than one-off projects. If you are running an older Magento 2 release, we can tell you what is involved in getting current, what will break, and how to sequence it so the store keeps trading throughout.

Yes, and it is a common way our engagements start. We begin with a handover audit — codebase, extensions, integrations, hosting, outstanding patches — so you get an independent picture of what you actually own before committing to further work. Nothing about a takeover requires replatforming.

Our head office is in Sydney and we work with clients across Australia — Melbourne, Brisbane, Perth, Adelaide and regional NSW included — as well as in New Zealand, where the duty free stores across the major airports have run on a platform we build and support since 2021. Delivery has been remote-first for years, so a project runs the same way whether you are ten minutes away or across the Tasman: scheduled calls, a shared board you can see at any time, and one named point of contact. We are happy to meet in person in Sydney.

Sometimes, but not automatically. Shopify removes infrastructure and upgrade overhead, which suits teams without dedicated developers. Adobe Commerce earns its complexity when you have deep catalogue rules, complex B2B pricing, multi-store or multi-currency requirements, or ERP integration that would fight a hosted platform. We will give you a straight recommendation, including when it is to stay put.

Because some businesses genuinely do not fit the hosted model. Deep catalogue rules, B2B pricing and customer-specific price lists, multi-store or multi-brand setups, multi-currency and multi-language, and ERP integration that has to be exact rather than approximate. Adobe Commerce gives you control over all of it. If none of that describes you, it is more platform than you need and we will say so — the complexity is only worth carrying when you are actually using it.

Yes, and it is usually the hardest part of the project rather than an add-on. For Aelia Duty Free we run automated sales exports into SAP alongside real-time inventory across multiple airport locations. On venue platforms we have scoped and architected against the POS, ordering and ticketing systems a group already runs, so the store fits the operation rather than the other way round. The pattern matters more than the logo: each system keeps ownership of what it is genuinely best at, and the integration is built to survive one end being unavailable.

Yes — GST handling, Australian shipping carriers and rate logic, local payment gateways, and multi-currency for stores selling overseas. We have built and maintained commerce for Australian retail and duty-free operations, where tax and pricing rules are genuinely non-trivial.

For a mid-market retailer, plan on three to five months from kickoff to launch. Straightforward catalogues move faster; anything with B2B pricing, multiple warehouses or an ERP in the middle sits at the longer end. The variable that moves the date most is rarely development — it is how quickly product data can be cleaned and decisions signed off, which is work on your side that no agency can absorb for you.

Four questions separate agencies quickly. How many replatforms have you delivered from our current version, and can we speak to those merchants? What does your audit cover before you quote — extensions, integrations, customer groups, indexed URL count? How do you handle URL mapping so we do not lose search rankings? And what happens after launch, contractually? An agency that quotes without asking about your extensions and integrations is quoting a number it cannot stand behind.

They are at risk, and the risk is manageable if it is planned rather than discovered. Every indexed URL needs a mapped destination before launch, not after. Category and product URL structures usually differ between platforms, so a one-to-one map is rare and the exceptions need decisions. We treat the redirect map as a deliverable in its own right, and we measure the result afterwards rather than assuming it worked.

Open Source covers a surprising amount: catalogue, checkout, promotions and multi-store all work without a licence. Adobe Commerce earns its cost when you need the B2B suite, Page Builder for a marketing team that will not wait on developers, or Adobe's hosting and support obligations for compliance reasons. If nobody can name which of those you need, you probably do not need the licence yet.

Yes, and it is often the better arrangement. Some retailers need extra capacity for a push rather than a change of supplier; others want a second opinion on architecture before committing. We are equally willing to hand a stabilised platform back as to keep running it.