Skip to content

Industries · E-commerce

E-commerce development that sells more, not just faster

We work with online sellers on Shopify, WooCommerce, BigCommerce and custom stacks. Storefront speed, clean product data, payments and tax across Canada and the US, and marketing measured on profit rather than clicks.

You own the code and IP Weekly demos Reply within one business day

shop.client.com/checkoutLive

Basket · 3 items

Optimised checkout

Merino crew

Canvas holdall

Ceramic carafe

x1

Merino crew · medium

x2

Canvas holdall

x1

Ceramic carafe · pair

Subtotal · delivery included

Complete order

2.9%

Conversion

41s

To checkout

−22%

Cart abandonment

E-commerce, in short

OlDevs is a full-stack studio in Vancouver, British Columbia that builds and improves online stores on Shopify, WooCommerce, BigCommerce and custom or headless stacks.The work covers storefront performance, product data and feeds, subscriptions, payments and tax across Canada and the US, and integration with marketplaces, ERP and fulfilment. Paid and lifecycle marketing is measured on contribution profit rather than clicks, so budget decisions match what the business actually keeps. Request a quote to talk through your store.

Key facts

01term
value
02term
value
03term
value
04term
value
05term
value
06term
value

E-commerce

What makes e-commerce hard to get right

The problems we are asked to solve most often — and how.

01

Apps and tags that slow the storefront

Every added app, pixel and review widget puts more script in front of the buyer. Speed work fails when it stops at image compression, so we measure real user timings on product and cart pages and remove or defer what does not earn its weight.

Core Web Vitals · Third-party scripts · Checkout

02

Product data that never quite matches

Titles, variants, GTINs and stock live in different shapes across the store, the ERP, Google Merchant Center and the marketplaces. Feeds get rejected, listings drift, and merchandising decisions get made on numbers nobody trusts.

Product feeds · Data quality · Merchandising

03

Tax and payments across two countries

Selling into Canada and the US brings GST, HST and PST alongside US sales tax that varies by state and by local jurisdiction, plus currency, duty and fraud rules at checkout. Getting it wrong surfaces late, in reconciliation and support tickets rather than in testing.

Payments · Tax · Cross-border

04

Subscriptions that outgrow the plugin

Recurring billing starts simple, then needs pausing, swapping, prepaid terms, proration and failed payment recovery. The stock plugin holds until it does not, and the failure lands on your support queue and on the revenue you report.

Subscriptions · Billing · Retention

05

Headless rebuilds that stall halfway

A headless front end can be faster and more flexible, and it can also strip out preview, search, promotions and the merchandising controls the team relied on. The rebuild only pays off when those missing pieces are planned in from the start.

Headless · Architecture · Content

06

Marketing judged on the wrong number

Platform-reported return on ad spend counts differently from the ledger, and blended numbers hide which products actually pay. Without margin, shipping and returns in the model, budget keeps moving toward campaigns that look good and lose money.

Attribution · Profit · Paid media

Process

From audit to peak season

  1. Audit

    We review the storefront, the data, the integrations and the reporting, then show you what is costing orders and what it would take to fix. No rebuild gets proposed before this.

  2. Plan

    A short, ordered plan: what we do first, what it should change, and how we will know. Scope is sized to your trading calendar so nothing risky lands near your busiest weeks.

  3. Build

    One accountable team, a working demo every week, and a staging environment that mirrors production closely enough that surprises appear before customers do.

  4. Launch

    Phased release with analytics, feeds, payments and tax verified against real orders, plus accessibility checks against WCAG 2.2 AA on the paths buyers actually use.

  5. Grow

    Ongoing performance, merchandising and marketing work reviewed on profit, with a code freeze window agreed around peak season so nothing ships when you can least afford it.

How we work

How OlDevs works with online sellers

01

Storefront performance

We profile the real storefront rather than a lab page: script budgets, template rendering, image and font delivery, search and filtering, and the path from product page to paid order. Then we cut, defer or replace what costs more than it returns.

02

Product data and feeds

One clean source for titles, variants, identifiers, pricing and stock, mapped out to the storefront, to Google and Meta feeds, and to the marketplaces you sell on. Rejections and mismatches get fixed at the source instead of patched per channel.

03

Checkout, payments and tax

Payment methods your buyers expect, currency and shipping logic that matches your fulfilment reality, tax configured for the jurisdictions you actually sell into, and fraud rules tuned so genuine orders are not turned away.

04

Subscriptions and lifecycle revenue

Plan design, pausing, swapping, prepaid terms, dunning and a customer portal people can use without emailing support, paired with email and SMS flows that reflect what someone has already bought.

05

Headless and custom builds

When the theme is the ceiling, we build a headless or custom storefront that keeps the editing, preview and promotion tools your merchandising team needs, and we phase the migration so trading never stops.

06

Profit-led paid and lifecycle marketing

Paid search, shopping, paid social and lifecycle run against contribution profit, with margin, shipping and returns in the reporting, and tests designed to answer a question rather than fill a dashboard.

Since 2014

Building and running online stores

1 business day

Reply to every enquiry

WCAG 2.2 AA

Accessibility standard we build to

FAQ

E-commerce — questions we hear first.

Shopify and Shopify Plus, WooCommerce, BigCommerce, and custom or headless stacks with a commerce API behind them. The right choice depends on catalogue size, how much your merchandising team changes each week, and what your ERP and fulfilment systems expect from the store.

Usually, yes. Most stores we look at have several quarters of gains sitting in script cleanup, template and image work, search and filtering, checkout friction and product data. We audit first and say plainly when the platform itself is the constraint, rather than selling a rebuild you do not need.

When the storefront is a real competitive surface: heavy content, complex merchandising, several regions or brands, or performance targets the theme cannot reach. It makes less sense when a small team depends on the platform's built-in editing, preview and promotion tools. We map what you would lose before recommending it.

We implement tax through the platform's own engine or a dedicated tax service, configure the jurisdictions you tell us you sell into, and test the result against real orders, discounts and returns. Rules and thresholds change, so we work alongside your accountant or tax adviser and treat their guidance as the source of truth. This page is general information, not tax or legal advice.

Yes. That covers plan design, pausing and swapping, prepaid terms, proration, failed payment recovery and a customer portal people can actually use. We start with your existing app or plugin where it fits, and build custom logic only where the stock behaviour would create support load or misreported revenue.

On contribution profit. We bring product margin, shipping, discounts and returns into the reporting, keep server-side and platform data reconciled with the ledger, and use holdouts or geo tests where attribution alone cannot answer the question. Budget then moves toward what the business keeps, not what the ad platform claims.

Yes. OlDevs is based in Vancouver, British Columbia and works with sellers across Canada and the US remotely, with video calls in your time zone and on-site visits when the work calls for it. We can also work in English and French where your catalogue and customer support need both. Request a quote to start.

Still have a question? Ask us when you request a quote

Let’s connect

Tell us about your project.

We’ll reply within one business day with next steps and a tailored quote — no obligation.

We’ll only use your details to prepare your quote. No lists, no spam.

Call us Request a quote