PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
OmnistuSTUDIO / SERVICESStart a project

Commerce engineering / Magento

Magento development.
Modules, storefronts and the systems behind orders.

Magento Open Source and Adobe Commerce scope for custom modules, B2B buying, multi-store operations and ERP or PIM integrations. Choose the edition and deployment model before deciding how the store will be extended and operated.

Discuss Magento requirements โ†—
Contents ยท Magento

Keep custom behaviour separate from platform core.

A Magento project can include a new store, module, front-end change, version upgrade, integration or migration. Map the business requirement to the supported extension mechanism for the selected edition and deployment model. Keep custom work documented and versioned rather than editing vendor files or placing operating rules inside a presentation template.

Retailers, manufacturers, distributors, multi-brand businesses and agencies can have different catalogue, pricing and order needs. Define product types, buyer roles, countries, currencies, stock ownership and fulfilment before choosing extensions. A large product count alone does not establish that Magento is the right platform.

Custom-code rights do not replace platform licences.

List custom modules, themes, front ends, configuration, integration services, repositories, Composer files, setup instructions and documentation to be delivered. Agree rights to custom work and distinguish them from Magento Open Source licences, Adobe Commerce terms, paid themes/extensions, media and external services.

Record control of store administration, hosting, developer accounts, domains, merchant services and business data. Agree confidentiality, white-label use, source access, support boundaries, updates and exit responsibilities in writing. A repository handover does not transfer every third-party right or remove operating dependencies.

Keep deployment secrets outside ordinary source and logs, with an approved secure transfer route. The receiving team should demonstrate setup, release and recovery rather than merely receive an archive or account list.

Compare the same buying and operating requirements.

Compare Magento, Shopify, WooCommerce and BigCommerce using the same catalogue, buyers, checkout, integrations and staff tasks. Replace high/medium/low cost labels and product-count thresholds with current terms, a representative demonstration and named operating responsibilities.

A hosted service can reduce some infrastructure work while leaving app and business responsibilities. A WordPress-based store can suit an existing content workflow. Compare Shopify or BigCommerce when their actual constraints fit. No platform is selected by a catalogue-size slogan alone.

Seven decisions before a Magento engagement.

Magento Open Source or which Adobe Commerce offering?

Start by naming the exact product and deployment model. Magento Open Source and licensed Adobe Commerce are not identical entitlements. Adobe also distinguishes Commerce as a Cloud Service (SaaS), Commerce on Cloud infrastructure (PaaS) and on-premises deployments. Their infrastructure, update, customisation and storefront responsibilities differ.

Adobe's current migration guidance says SaaS extensions use supported APIs and external services rather than modifying core application code. PaaS keeps merchant responsibility for application patches, custom code, configuration and supported service versions. On-premises operation has a different infrastructure boundary. Confirm current licensing and included features with Adobe instead of assuming every offering accepts the same PHP module or deployment pipeline.

Company accounts, shared catalogues, negotiable quotes, requisition lists, content staging and other features need an edition/installation check. An Open Source extension can be evaluated against the same business requirement, but its name does not make it equivalent to Adobe Commerce B2B.

What does Commerce on Cloud development involve?

For the PaaS model, Adobe documents application, environment, routes and service configuration files, including .magento.app.yaml, .magento.env.yaml, .magento/routes.yaml and .magento/services.yaml. ECE-Tools provides build, deploy and post-deploy work. Those stages and dependencies need to be understood before changing the release process.

Review environment parity, dependency versions, secret handling, logs, cache/CDN configuration and alert ownership. Adobe notes that some Pro environment changes require Support involvement, including selected service and resource changes. Do not assume a Git push can change every production setting. Validate in integration/staging and verify the final running state.

Fastly and New Relic can be relevant to a selected cloud setup, but confirm current entitlements and operating access. Commerce as a Cloud Service is a different model, not the same PaaS pipeline under another label.

What should the development scope include?

Define custom checkout, pricing, shipping and administrative modules; a selected theme or decoupled storefront; B2B configuration; websites/stores/views; ERP/PIM/CRM/payment/carrier integrations; and performance/operation. A store may need only part of this list. Review each installed extension against maintained versions, licence, supported front end and failure behaviour.

For a traditional PHP deployment, use supported module interfaces, plugins, observers, dependency injection and service contracts as appropriate. For SaaS or other offerings, use that product's extension boundary. No mechanism makes every change upgrade-proof; compatibility requires tests and maintained dependencies.

How is a Magento 1 migration approached?

Treat data, extensions, themes and customisations as separate workstreams. Inventory the existing behaviour and supported destination before promising transfer. Evaluate Adobe's Data Migration Tool for eligible source/target versions and mappings; extension data can need custom transformations or migration steps.

Plan products, categories, customers, orders, promotions, store settings, media, content and integration references. Rebuild or replace incompatible front-end and module behaviour. Trial the migration and reconcile representative relationships, historical records and exceptions, not only totals.

Agree delta/final sync, any trading pause, authorised cutover, rollback and post-launch reconciliation. Stored payment credentials and account authentication require provider-supported checks. No zero-downtime, complete-data or search-ranking guarantee is assumed.

When might another commerce platform be the better fit?

Consider the real operating burden: supported runtime and services, search, cache, database, patching, indexers, cron, consumers, backups and specialist support. Compare it with the business value of required catalogue, B2B or store-scope behaviour. A small catalogue can be complex and a large catalogue can be simple.

A hosted option, WordPress commerce or another operated PHP stack may fit the team better. Compare Shopify, BigCommerce, WooCommerce, OpenCart or PrestaShop against demonstrated workflows, current terms and the team's maintenance capacity. Do not infer total cost or suitability from an arbitrary product count.

How should white-label agency work be scoped?

List whether the engagement covers modules, patches, migration, performance, theme work or ongoing capacity. Name the client-facing and receiving teams, repository/control requirements, review route, confidentiality, branding and third-party licences. Agree who can approve changes and communicate with the end client.

White-label source delivery and confidentiality terms need written agreement; they do not automatically assign every right or create a response-time/support promise. A retainer and a one-off build have distinct capacity, billing and cancellation terms.

A developer or a development company?

Match the assignment to demonstrated skills and continuity. A contained extension fix and a store release with PHP, front-end, integration, operations and QA work are different scopes. Ask who reviews code, rehearses migration, owns patching and receives an incident after handover.

Request relevant work evidence, current credentials if claimed, a representative test/load report and a reproducible handover. Neither a company label nor an individual certification proves the complete store workflow. Agree acceptance and responsibility rather than relying on an agency count or generic title.

Modules, store scopes and integrations need explicit boundaries.

Theme, module and dependency injection

Keep presentation separate from business services and integration adapters. A module should expose its dependencies and supported APIs rather than rely on hidden coupling or direct edits to vendor files. Adobe's dependency-injection guidance uses interfaces and di.xml configuration, with constructor injection rather than ordinary code depending directly on ObjectManager.

Choose plugins, observers or service-layer work based on the actual extension point and execution lifecycle. Review module dependencies, scope-specific configuration, permissions, validation and data ownership. A clean folder structure is not evidence that an upgrade or extension conflict has been tested.

Website, store and store-view scope

Adobe documents a hierarchy of websites, stores and store views sharing an installation and administration. Stores can have distinct root categories and presentation; views can support language differences. Plan that hierarchy before applying configuration, because it shapes how catalogue and storefront settings are managed.

Map domains, locale, currency, price scope, customer sharing, checkout, stock and integration identifiers explicitly. Do not assume every website/store/view has an independent setting for every field. Test a price, language, tax and stock change in each intended scope, including cache and API responses.

The queued fulfilment example needs transaction and replay design

The original observer example watches an order-save event and publishes an order number when the order enters processing. Its useful subject is asynchronous warehouse/ERP fulfilment. A state-transition check alone does not prove that one external shipment is created, that the database commit succeeded or that a repeated save cannot repeat the effect.

No partial observer snippet is presented as a complete module or an exactly-once guarantee. A queue can decouple some external work, but the enqueue step, transaction, consumer and upstream system still affect reliability and customer experience.

Cache, search, indexers and scheduled work

Select services and versions from the requirements for the exact Commerce release and hosting model. The current requirements distinguish cloud and on-premises combinations and can include beta/early-access releases, so a dependency table is not a blanket recommendation to install the first row.

Evaluate Varnish or the selected CDN/full-page-cache service, Redis or another supported cache/session component, and OpenSearch or supported search. Verify anonymous and personalised boundaries, cache invalidation, price/customer-group visibility, catalogue search and stale stock. A cache hit rate alone is not evidence that buyers see correct data.

Define which indexers use the selected mode and how cron and queue consumers are run and monitored. Test imports, price changes, stopped workers, long backlogs and recovery. Avoid universal rules that every indexer or version uses the same scheduling configuration.

Front ends: a theme is not automatically headless

Compare a Luma-based theme, Hyvรค or a decoupled storefront against the actual extension and checkout requirements. Hyvรค's own technical vision describes Magento theme concepts including layout XML, blocks, view models and phtml, and presents it as an alternative to a JavaScript-only PWA approach. Do not label a Hyvรค theme as a headless PWA by default.

For a chosen headless/PWA Studio/custom React option, define GraphQL coverage, customer sessions, checkout, search, content preview, SEO rendering, app compatibility and front-end deployment. For a theme, check required module adapters and checkout behaviour. Measure representative pages and journeys rather than promising speed from the architecture label.

Three engagement shapes, with separate operating terms.

Agree review cadence, milestones, billing, cancellation and support scope. No fixed team size, weekly delivery, first-module deadline or standard service window is implied.

Six acceptance areas before store handover.

Include agreed desktop/mobile browsers, accessibility checks and authorised test-mode payment/refund exercises. A successful test order does not establish live merchant approval, compliance certification or production readiness. Inspect system-of-record evidence and recovery paths.

Select the stack for the edition and supported release.

An option inventory, not an included bundle or evidence of configured services.

Reconcile products, customers, orders and operating relationships.

Inventory the source edition/version, PHP and services, installed extensions, custom modules, core/vendor changes, licences, theme, API users, missing patches and integration contracts. For an upgrade, compare each dependency with the target release before changing it. For migration, map source records and unsupported behaviour explicitly.

Trial on a protected staging environment. Reconcile configurable/bundle/grouped product relationships, media, categories, customer/account behaviour, orders/refunds, coupons, taxes, currencies and external identifiers. Audit passwords, stored payment credentials and active recurring authorisations through supported provider routes. Keep sensitive records out of ordinary documentation.

Adobe's Data Migration Tool supports mapping/handlers and custom steps for appropriate extension data differences; it is not proof that every theme, module and business process migrates automatically. A move to Commerce SaaS also changes application, storefront and integration extension patterns, so it is more than copying a database.

Test redirects, canonical URLs and content continuity, without promising rankings. Agree final sync, cutover, pause if required, rollback and post-cutover reconciliation. Production changes, live charges and domain/DNS updates remain separately authorised actions.

From commerce brief to an operated release.

Content, merchant/provider eligibility, platform support and review decisions can affect delivery. Agree dependencies and change control in writing. No fixed duration, first-commit/module deadline or support period is assumed.

What changes the Magento estimate?

Separate one-time implementation from recurring platform, hosting, extension, payment and maintenance terms. Obtain current written vendor quotes; no sample amount, total-cost ranking or licence figure is treated as a present offer.

An illustrative fashion marketplace migration.

Consider a fashion business moving an older store while adding a vendor marketplace, several languages, ERP connectivity and a revised storefront. This is a requirements scenario, not a claimed Milan client, season-deadline delivery, performance improvement or user-growth result.

No SKU count, language count, delivery duration, percentage speed gain, revenue or user result is asserted. The useful output is a testable commerce and operating scope.

Magento delivery review and handover.

Agree the implementation boundary, deliverables and acceptance checks in the project scope. Include the source and configuration to be handed over, third-party dependencies, account ownership and the receiving owner's installation and operating walkthrough. Review the selected work at the agreed milestones, with unresolved items recorded before release.

The delivery review can cover a reproducible module build, load-test conditions, patch/release rehearsal, order and ERP reconciliation, queue recovery and receiving-team handover. Confirm contracting identity, commercial terms and source/support obligations directly. Unverified agency counts, named testimonials, ratings and guarantees are not reproduced as proof.

Translate sectors into buying and operating rules.

Questions to settle before Magento work.

What administration is included?

List catalogue, orders, customers, content, promotions, tax, store scopes, reports and extension configuration tasks. Verify staff roles and edition/module entitlement against those tasks. Do not give every operator full administration simply to make a workflow pass.

Can an existing store be patched or taken over?

Begin with the version, extension, customisation, service and security audit. Rehearse changes on protected staging, fix compatibility problems and test search, checkout, integrations and recovery. Agree staged work where appropriate without promising uninterrupted trading.

Who handles hosting?

Name infrastructure, application, patch, cache, search, broker, certificate, backup and incident owners for the actual deployment model. Managed hosting does not remove every merchant responsibility. Verify current support and service access before selecting a provider.

What source and access are handed over?

Agree custom modules, themes, configuration, repositories, dependencies, documentation and approved accounts. Distinguish custom rights from Adobe and third-party licences. Prove the handover with setup, release and restore tasks, not a source-code guarantee in marketing text.

Can we use ongoing development capacity?

Scope required skills, availability, review cadence, patching, release approval and support responsibilities in the agreement. A retainer is not automatically an individual hourly hire or a universal team-size/cancellation promise.

How quickly can it launch, and what happens after?

Estimate from the selected edition, catalogue, store scopes, front end, integrations, migration and dependencies. Agree acceptance, milestones, defect boundaries, updates, monitoring and escalation in writing. Document the actual quote, milestone estimate and support window for the engagement.

Platform references used for technical checks.

Official documentation checked on 17 November 2026. Verify the exact product, edition, release, service compatibility and provider terms before implementation.

Bring the catalogue, buyer rule or integration that needs to change.

Describe the store, its buyers and the operational result you need. Keep the edition, front end, integrations and receiving-team responsibilities visible, then agree evidence and scope before committing to implementation.

Discuss your Magento scope โ†—