Skip to content

Magento development services for catalogue and account workflows

We build and modernize Magento and Adobe Commerce stores for commerce product and IT teams. We develop catalogue models, business accounts and integrations, with release and operating responsibilities defined for the actual edition.

01Capabilities

Magento catalogue, account and integration development

Magento Open Source is the open-source platform; Adobe Commerce is the commercial offering. We scope our e-commerce work against the edition, deployment and extension support.

  • Buyers

    Company accounts, contract prices and approvals

    We model company accounts and buyer hierarchies, with customer price lists, quotes, credit terms and ordering on another buyer's behalf. Availability depends on the edition and B2B extension, with custom scope assessed separately. Rules for business buyers sit within our platforms development and integration work.

  • Catalogue

    Catalogue models and import behavior

    We model attribute sets, configurable and bundled products and multi-source inventory for the estate. The engineering includes import behavior and indexing checks, so catalogue changes are assessed against the data model and release plan.

  • Stores

    Product data across brands and markets

    We assess websites, stores and store views against the estate's brands and markets. That hierarchy shapes product data, pricing and URL decisions, including configuration and development scope.

  • Inherited

    Module and core assessment for modernization

    We review unsupported versions, third-party module maintenance and direct changes to core files. The findings shape the support and upgrade path through legacy modernization, including which customizations to retain, replace or refactor.

02Fit

Choosing the edition and operating model

Adobe Commerce includes SaaS, cloud infrastructure (PaaS) and on-premises models. SaaS uses automatic platform updates and extensions through APIs and events. We scope PHP-module and runtime upgrade work to cloud-infrastructure or on-premises estates.

Six situations, and what we would tell you in each
Your situationWhat we recommend
A detailed catalogue, customer-specific pricing rules and layered buyer accounts Assess edition and B2B fitMatch the catalogue and account rules to Magento Open Source or the chosen Adobe Commerce edition and B2B extension. Include custom implementation and operating responsibilities in the comparison.
A modest catalogue and standard checkout, with hosted operations preferred Compare hosted optionsAssess Shopify against the actual catalogue and checkout requirements. Compare its hosted model with the relevant Adobe Commerce deployment, including extension and operating requirements.
WordPress already holds the content and the catalogue is small Assess WordPress commerceCompare WooCommerce when its catalogue and checkout capabilities fit the existing WordPress estate. Include ongoing maintenance and integration scope when choosing how to connect content and commerce.
Hosting, indexing, cron and upgrades need clear ownership Agree operations ownershipDefine the deployment first, then assign the operating responsibilities. We scope support for hosting, indexing, cron, caching and upgrades according to the deployment.
Still on Magento 1, or a release that no longer receives security fixes Plan a supported transitionMagento 1's official support ended in June 2020. Assess the source version, modules, themes and integrations, then plan a supported migration path and the work needed during transition.
Product data quality needs attention before storefront changes Assess the data pipelineReview the product data pipeline through data engineering before deciding which storefront changes are needed. We scope catalogue data and import behavior work alongside any storefront changes.

Scope

We own the catalogue and account design, extension boundaries and upgrade plan for the estate. That includes assessing custom modules, integration interfaces and support responsibilities. unicrew was founded in 2012 and has 100+ senior in-house engineers across six countries. Our work runs under an ISO 27001:2022 certified information security management system.

Magento is at its best on complex catalogues, with many stores, many price rules and many markets. For a simpler store, we build on Shopify or WooCommerce instead. We settle that choice with you before anything is signed.

Yaroslav HavrylivSenior Engineering Manager, unicrew

03Delivery

Getting an upgrade back onto a schedule

We plan upgrades for Magento Open Source and Adobe Commerce estates using PHP modules, with compatibility and runtime checks sequenced around the trading calendar.

  1. Audit modules and core changesWe review third-party modules, their upstream maintenance status and direct changes to core files. The findings establish compatibility work and which customizations need to be retained, refactored or replaced.
  2. Measure indexing, caching and page behaviorWe inspect indexer state, cache hit rates, slow queries and page timings for logged-in sessions. Measurements establish which application, database or deployment changes the estate needs.
  3. Establish a testable deployment pathWe put configuration in version control and check the deploy mode for the actual estate. A staging environment that reflects production supports module, runtime and release testing.
  4. Sequence the upgrade against your trading calendarWe plan around trading peaks, identify module replacements in advance and rehearse rollback. Our QA and test automation checks cover the agreed upgrade path in staging before the release.

05Questions

Questions that decide whether Magento is the right home

Edition, deployment and module compatibility shape the Magento build or upgrade plan.

Yes. Our engineers work on Magento Open Source and Adobe Commerce catalogue, module and integration requirements. We define delivery scope against the edition and deployment.

An architect outside the delivery team reviews module and integration design. We agree the QA and test automation scope for the code and release changes.

Our managed teams include unicrew delivery coordination. We also deliver scoped web development projects.

We compare the required catalogue and account behavior with Shopify before recommending an edition or platform.

Adobe Commerce B2B company-account, shared-catalogue and quote features depend on the edition and B2B extension.

Hosting and upgrade responsibilities depend on deployment: SaaS automatic updates differ from cloud-infrastructure or on-premises operations.

Our developers joined a client-led WordPress-to-Shopify and ERP programme.

Magento 1 is past official support, which ended in June 2020. We assess the estate and plan a supported migration or replacement.

Magento 2 and other commerce platforms are options to compare against the catalogue and operating requirements. The scope depends on source/target compatibility, data, themes, modules and integrations. We assess extensions individually and define the work needed during transition.

Magento slowness can come from indexing, cache behavior, database work or deployment. We measure the store before recommending changes.

  • Indexer progress and full-page cache behavior, including logged-in sessions.
  • Modules doing database work on each request.
  • Category queries and the indexes supporting them.
  • Hosting, configuration and runtime conditions for the estate.

We scope the catalogue, accounts and build or upgrade requirements on a call with an engineer.

For an existing deployment, send the module list and version, with read access to the repository. You get a written plan covering the build or upgrade path, what to do first and what to retain. Most engagements start within two to four weeks.

We quote Magento and Adobe Commerce implementation against the edition, deployment and custom scope.

  • Time and materials is billed hourly and quoted per project.
  • Fixed price is outcome based and quoted per project.
  • Team extension is billed monthly per team member.

The module and integration assessment informs the build or upgrade estimate.

Plan your Magento build or upgrade

Tell us what the catalogue and pricing rules need to support. For an existing estate, include the version and module list. You get a written recommendation on the build or upgrade path.

Book a scoping call

Thank you

Thanks for your message. We will get in touch with you shortly.