Does BC PST apply to an ERP subscription?

Generally yes. The Province of British Columbia's software publication states that software includes software as a service, meaning software or the right to use software where possession is maintained by the provider. Unless a specific exemption applies, 7% PST is payable on the purchase price. This is general information and not tax advice, so confirm your own position with a CPA.

Does it matter that our ERP vendor is outside British Columbia?

Generally no. The Province's guidance ties the tax to use on a device ordinarily situated in B.C. rather than to where the seller is located, and gives the example of a Vancouver resident who downloads an app while in Alberta and still owes PST. A vendor with no BC presence does not by itself remove the obligation.

Why does PST change how a BC company compares ERP quotes?

Because the subscription line is taxable here and is not in Alberta, two otherwise identical quotes carry different total costs depending on the province. It also means the implementation partner's treatment of software, services and bundled charges has a tax consequence, so how a quote is broken down is worth attention rather than a glance.

What is the difference between an Odoo partner and a digital transformation consultancy?

An Odoo partner configures one product and is measured on whether the system runs the business correctly. A transformation consultancy coordinates change across systems and vendors, with ERP as one workstream. They are bought for different constraints: depth inside one product against coordination across many parties.

When should a BC company hire a broad consultancy rather than an ERP specialist?

When the platform is not chosen yet, when several systems are changing at once, when there is no internal IT function, when the underlying problem is that nobody can agree on one process, or when procurement requires insurance limits and audited financials a small firm cannot carry.

What should an importer ask an Odoo partner?

Ask how landed cost is configured, and specifically which costing method the product categories use. Odoo's documentation states that to apply a landed cost to a vendor bill, products on the original purchase order must sit in a product category using AVCO or FIFO. A category left on standard cost blocks landed costs entirely.

Choosing an Odoo Partner in British Columbia

Quick answer: in British Columbia an ERP subscription is generally a taxable purchase, because provincial guidance places software as a service inside the definition of taxable software at 7%. That changes the cost comparison and makes how a partner structures a quote worth reading closely. On capability, buy depth in the product and check it with questions that have verifiable answers.

Local Context

British Columbia has a tax condition that most ERP buying guides, written for a national or American audience, simply do not account for.

The Province’s software publication states that software includes software as a service (SaaS), defined as software or the right to use software where possession stays with the provider or a third party instead of the purchaser. Infrastructure as a service and application programming interfaces appear in the same definition. Unless a specific exemption applies, 7% PST is payable on the purchase price.

The obligation follows use, and the seller’s location does not decide it. The Province’s guidance covers a purchaser who buys software anywhere, including outside B.C., and uses it on a device ordinarily situated in the province, and gives the example of a Vancouver resident downloading an app while in Alberta who still owes the tax. A vendor with no BC footprint does not remove the liability.

There is a genuine exception worth knowing rather than relying on. Where software is merely incidental to a contract for non-taxable services, the Province says it is not treated as a sale of software and PST is not payable. Where software and non-taxable services are bought for a single price, PST is generally payable on the fair market value of the software. That test turns on the substance of the arrangement, which is why the structure of a quote is a real question rather than paperwork.

This is general information and it is not tax advice. The incidental test and any exemption depend on facts specific to your contract. Confirm your position with a CPA before relying on it.

A practical consequence: an identical ERP quote costs a Vancouver company more than a Calgary one, because Alberta has no provincial sales tax. A buyer comparing figures from a supplier used to quoting into Alberta should ask whether PST is included, excluded, or has been considered at all.

What Actually Makes This Market Different

Vancouver’s industry mix is not the distinguishing feature and it would be dishonest to pretend otherwise. Statistics Canada’s business counts for the Vancouver CMA (businesses with employees, July 2025) put manufacturing at 4,146 businesses, 3.4% of the base, which sits between Edmonton and Toronto. Wholesale trade at 4.3% is identical to Toronto’s share. Construction at 11.5% is mid-pack.

What distinguishes the BC buyer is the tax condition above and the trade condition below.

Vancouver’s port exposure puts landed cost inside ERP scope for importers in a way it is not for an inland business serving a domestic market. Duty, freight, brokerage and currency have to attach to the right receipt and end up in the right inventory value, or margin reporting is wrong from the first shipment.

That has a specific, checkable configuration consequence in Odoo. Costing method sits on the product category, one level above the product, and Odoo’s documentation states that to apply a landed cost to a vendor bill, the products on the original purchase order must belong to a product category with a costing method of either AVCO or FIFO. A category left on standard cost blocks landed costs from being applied at all. An importer who finds this after go-live has been valuing inventory incorrectly for as long as the system has run, and the correction reaches into closed periods.

That is the kind of thing product knowledge catches in a discovery call and methodology does not catch at all.

Depth Against Method

The two failure modes on an ERP project look similar in a status report and behave nothing alike.

A coordination failure produces delay. It is expensive, visible while it happens, and recoverable. Strong project method is built to prevent exactly this, and it does.

A configuration failure produces a system computing the wrong number and continuing to compute it. It surfaces at a month-end, at a year-end, or during an audit, by which time months of transactions rest on the mistake. Governance cannot catch this one. A steering committee can record that somebody approved the costing method; it has no mechanism for knowing whether the approved method was right.

The correctness lives with whoever proposed the setting, which is why who that person is, and what they have configured before, is the thing to interrogate.

The Customization Cost That Arrives Later

Every implementation eventually meets a requirement the product does not answer natively, and the two firms in the room can respond identically for opposite reasons. One knows the native mechanism and judges it insufficient. The other could not find it. Both quote a custom module.

Odoo documents the consequence. A database containing custom modules cannot be upgraded until a version of those modules exists for the target release, and Odoo provides standard support for each major version for three years, with extended support beyond that carrying a mandatory additional fee.

Each custom module is therefore an obligation on a recurring cycle for the life of the system. The most revealing question in an evaluation is not what a firm has built, but what it has talked a client out of building.

Where a Broad Consultancy Is the Right Purchase

These are genuine and a buyer who dismisses them will choose worse.

The platform is unchosen. A firm that implements one ERP should not run your selection, because the shortlist is bounded by what it delivers. Buy that separately from someone neutral.

Several systems are moving at once. When the ERP lands alongside a WMS, a CRM migration and a payroll switch, the constraint is sequencing across vendors. That is programme management, and it belongs above the specialist rather than beside it.

No internal IT function. An MSP holding endpoints, identity, backups and the service desk, which also takes ERP tickets, gives one contract and one escalation path.

The problem is organisational. Business units running incompatible processes with nobody empowered to choose. A larger firm carries political weight a boutique cannot borrow.

Procurement gates. Insurance minimums, audited financials, an approved vendor list. A small firm fails these on paper regardless of merit.

Key-person risk. In a small firm the knowledge sits with named individuals, so ask directly what the cover arrangement is.

The common shape: the binding constraint sits outside the product. Buy breadth for that and scope it explicitly. Once the platform is settled and configuration is the work, the constraint has moved inside the software.

A Structural Note on the BC Advisory Market

One local fact is worth knowing when a firm describes itself as independent. In 2022 Salesforce acquired Traction on Demand, a Burnaby firm widely reported at the time as the largest dedicated Salesforce consultancy in North America. A regional independent of significant scale became part of a software vendor.

That is not a criticism of anyone involved, and it is a reason to ask a direct question of any advisor: what is your relationship to the vendors whose products you recommend, and how are you compensated. A buyer is entitled to a plain answer, and it is a reasonable question to put to a specialist and a generalist alike.

Questions to Put to Every Firm

How many Odoo implementations have you completed, and how many are running a client’s business today? Two numbers, with the gap explained.
Who configures our inventory valuation and landed cost, what were their last three Odoo projects, and what else are they on during ours? A name and a share of their week.
What are the last three customizations you talked a client out of, and what native mechanism replaced them? This cannot be answered without the knowledge behind it.
How do you handle PST on the software component of what you are quoting us? A BC-experienced supplier has a clear answer. A supplier used to quoting into Alberta may not have considered it.
What in Odoo have you been burned by? A named limitation with a version number.
What did the last five Odoo projects quote at signing, and what did they invoice? Real records show variance and name a cause.
Of clients implemented two years ago, how many are on a supported version, and who paid?
What would make you tell us Odoo is the wrong answer?

What Could Not Be Verified Here

Two claims commonly made about this market are left out because they could not be confirmed against a primary source in preparing this guide: Port of Vancouver tonnage figures, which circulate via press summaries, and BC employer health tax thresholds, which should be read directly from the provincial source before anyone relies on them.

Odoo’s Canadian partner directory lists partners nationally without a working city facet, so this guide does not state how many Odoo partners operate in British Columbia.

There is also no public dataset comparing specialist and generalist ERP outcomes. The circulating ERP failure percentages do not survive a search for the underlying study, so nothing above depends on one.

About the publisher

Vancouver Biztech is published by Solvync Inc., an Odoo implementation partner based in Calgary, Alberta.

Two things follow. The publisher sits in one of the categories compared here, so read the argument with that in mind. And a firm based in Alberta should be asked the PST question above with particular care, because a supplier accustomed to quoting into a province with no provincial sales tax may not have priced it. That applies to Solvync as much as to any other out-of-province firm.

Vancouver Business Software Planning Guide covers sequencing before a partner is chosen.
Data Ownership Checklist covers what to secure contractually before an implementation starts.