Platforms · Adobe Commerce & Magento
Magento is powerful and heavy. We build catalogues, B2B accounts and multi store setups that hold up, keep the platform patched and current, and tell you plainly when a lighter platform would serve you better.
You own the code and IP Weekly demos Reply within one business day
Basket · 3 items
Optimised checkoutMerino crew
Canvas holdall
Ceramic carafe
Merino crew · medium
Canvas holdall
Ceramic carafe · pair
Subtotal · delivery included
2.9%
Conversion
41s
To checkout
−22%
Cart abandonment
OlDevs is a full-stack technology studio in Vancouver, British Columbia that builds and maintains Adobe Commerce and Magento Open Source storefronts.The work covers catalogue and attribute architecture, multi store and multi currency setups, B2B features such as company accounts and quoting, ERP and PIM integration, caching and performance, and ongoing security patching. We also handle migrations onto the platform from elsewhere, and off it to Shopify or WooCommerce when the operational weight no longer fits the business. Request a quote to talk through your catalogue and roadmap.
Key facts
Platform expertise
Attribute sets, configurable and bundled products, category trees and product data that stays manageable as the catalogue grows. We model the structure once so merchandising, search and feeds all read from the same source.
One admin, several storefronts. We set up websites, stores and store views with their own currencies, tax rules, shipping and content, so a Canadian, US or bilingual EN and FR presence shares one catalogue instead of duplicating it.
Company accounts, buyer roles and approval rules, negotiable quotes, requisition lists and shared catalogues with company specific pricing. These are Adobe Commerce B2B features, so we configure what the platform already provides and build only what it leaves out.
Orders, inventory, pricing and customers moving between Magento and your ERP, PIM or warehouse system. We use message queues and scheduled jobs rather than live calls in the checkout path, so a slow back office never stalls a sale.
Full page cache, Varnish, Redis, image handling and search tuning on the OpenSearch or Elasticsearch service Magento runs against, plus a hard look at the third party modules and scripts that quietly slow a store down. We measure Core Web Vitals on real category and product templates, not a demo home page.
Security patches and platform releases handled on a schedule rather than in a panic, with module compatibility checked first. Upgrades run on a staging copy with a rollback plan, so you know what changed before your customers do.
Process
Discovery
We look at your catalogue, current platform, integrations and admin habits, then agree what the store has to do for the business and where the present setup gets in the way.
Architecture
Data model, storefront structure, integration map, hosting and upgrade plan written down before the build starts, so the decisions stay visible and reversible.
Build
One accountable team and a working demo every week. You see the catalogue, checkout and admin come together, and you can redirect early instead of at the end.
Migrate and launch
Repeated migration rehearsals, redirect mapping, load testing and a launch checklist with a rollback path. We go live at a time that suits your trading calendar.
Care
Patching, monitoring, upgrades and small improvements on an agreed rhythm. You own all code, designs, accounts and IP throughout, so you are never locked in.
How we work
Attribute sets and category structure are the decisions everything else inherits. We settle them before the theme, because retrofitting product data across a live catalogue is the expensive kind of work.
Adobe Commerce and Magento already do a great deal out of the box. We use native features and settings wherever they fit, and write custom code only where your business genuinely differs from the defaults.
Every extension is a future upgrade problem. We audit what is installed, remove what is unused, and prefer a small amount of clear code over a marketplace module that reaches into the whole application.
ERP, PIM and shipping calls belong in message queues and scheduled jobs, not in the checkout request. When a back office system is slow or unavailable, customers can still complete an order.
Demo catalogues hide problems. We load a realistic copy of your products, prices and customers so indexing time, search relevance and admin usability all get tested at your actual scale.
If your catalogue is small and your process is standard, an off the shelf hosted platform will serve you better and we will tell you so. We would rather lose a build than sell you a platform you have to feed.
Who it's for
Multi brand and multi region catalogues sitting in front of ERP, PIM and finance systems, with the governance, accessibility and audit expectations that come with a large organisation.
Member pricing, restricted catalogues, bilingual EN and FR storefronts and WCAG 2.2 AA accessibility, with procurement friendly documentation and no vendor lock in on the code.
One catalogue, many locations. Store views per franchisee, controlled local pricing and content, shared merchandising, and reporting that rolls up cleanly to head office.
Honest sizing. If Magento suits where you are going, we build the smallest sensible version of it. If it does not, we will say so and point you at a lighter platform.
Weekly
Working demo cadence
One business day
Reply to every enquiry
Since 2014
Building commerce systems
FAQ
Catalogue complexity and how much control you need decide it. If you have a large catalogue, several storefronts, B2B pricing rules and an ERP to talk to, Magento earns its weight. If your catalogue is small and standard, Shopify or WooCommerce will cost you far less attention, and we will say so rather than sell you a bigger platform.
It is a large application with cache layers, a separate search service, message queues and scheduled jobs, and it expects a server setup that suits it. That power is real, but it needs a hosting plan, a patching routine and someone accountable for the stack. An off the shelf hosted platform beats building on Magento whenever that ongoing attention is not something you want to fund.
Yes. We map products, attributes, customers, order history and URLs, then rehearse the migration on a staging copy until the numbers reconcile. Redirects and search continuity are part of the plan rather than an afterthought, because a clean cutover matters far more than a clever one.
We will help you leave. Migrating off to Shopify or WooCommerce is the same discipline in reverse: export catalogue and customer data cleanly, rebuild the parts that actually get used, preserve URLs and order history, and switch over without a gap. We would rather tell you the truth than hold you on a platform you have outgrown.
Sometimes. A decoupled front end helps when you serve several channels from one catalogue, or when your design fights the standard theme. It also adds a second application to build, host and maintain. If a well built theme on the standard stack gets you where you want to go, that is the simpler and calmer answer.
On a schedule. We track the patches and releases that apply to your version, check module compatibility, and apply them on a staging copy with a rollback path before anything reaches production. Skipping patches is how a store ends up with an emergency instead of a routine maintenance window.
Adobe Commerce ships B2B features such as company accounts, buyer roles, negotiable quotes and requisition lists, and they cover a lot of common ground. Magento Open Source does not include them. We configure the native features first and write custom code only where your process genuinely differs. If what you actually need is an ERP or a dedicated quoting system, we will point you there instead.
Let’s connect
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote — no obligation.