How to Choose an ERP for a Small Business in Quebec

To choose an ERP for a small or mid-sized business in Quebec, start with what you sell. A company that manufactures or distributes needs a manufacturing ERP; a company that sells hours and projects needs a services ERP. Then compare the three-year cost, where the data is hosted, the French interface, and how GST and QST are calculated.

What is an ERP, and when does a small business need one?

An ERP, short for enterprise resource planning, is software that keeps all of a company’s operations in a single database: sales, the work to be done, purchasing, stock, invoicing and often accounting. The point is simple. A piece of information entered once is used everywhere, and nobody types it again.

The word scares people because it brings to mind big plants and projects that drag on. A twelve-person company can still have the same problem as a three-hundred-person factory: five tools that don’t talk to each other, and someone who spends Fridays copying numbers from one screen to another.

These are the signs you have reached that point:

• The same customer record lives in three places, and none of the three is up to date.
• An invoice gets built by rereading emails, a spreadsheet and paper timesheets.
• Nobody can say, while a job is under way, whether it is profitable.
• One person knows how the spreadsheet works, and that person takes holidays in July.
• Hours worked or purchases never make it onto the invoice.

On the other hand, if a well-kept spreadsheet and an accounting package do the job, keep them. An ERP solves a coordination problem. When that problem doesn’t exist yet, it adds screens to fill in and nothing else. We wrote a page about that move from the spreadsheet to business management software for Quebec SMBs, with what you gain and what you give up.

Manufacturing ERP or services ERP: which one do you need?

A manufacturing ERP is built around the item: the bill of materials, the stock, the production order, the cost price. A services ERP is built around the work: the job, the hours, the contract, the invoice. Both carry the same name, but they don’t solve the same problem, and many buying guides treat them as one.

That distinction changes everything when you choose. In a plant, the question every morning is "what do we have in stock and what do we need to produce?" In a services firm, it is "who is working on what, and will it be billed?" Software designed for the first question was not drawn up for the second. It may have a project module; look at whether the timesheet sits at the centre or off to the side.

The reverse is just as true. A services ERP keeps an inventory of parts and equipment. It does not schedule a production line, calculate raw material requirements or run a multi-location warehouse with barcode scanners.

To find out which side you are on, look at your last invoice. If the lines are mostly items with a quantity and a unit price, you sell products. If they are mostly hours, fixed fees, monthly contracts or project milestones, you sell work. Companies that do both, a shop that installs what it builds for example, have to decide where the bigger risk of error lies: in the stock or in the hours.

That is why our page on ERP for service businesses exists: it explains what this kind of software covers when you sell hours instead of boxes.

The four ERP families and who they are for

Nearly every ERP offered to a small business fits into one of four families: the modular generalist, the manufacturing ERP, the construction ERP and the services ERP. Each one starts from a different trade, and that starting point decides whether the software will suit you, far more than the length of its feature list.

These families overlap. A modular generalist has a manufacturing module, a services ERP keeps a small inventory. What matters is the core of the product, the part the vendor improves with every release. For construction, we go into detail on our page about management software for construction.

How much does an ERP cost in Quebec?

The cost of an ERP has four parts: the subscription, the implementation, the training and your own team’s time. Only the first one is posted on vendor websites, and not always. On October 2, 2026, published subscriptions ranged from $44 to $149.20 per user per month at the vendors we checked, in Canadian dollars before taxes.

There are three ways to bill a subscription. The most common is per-user pricing: every person who logs in adds an amount to the monthly bill. The second is tier pricing: a fixed amount for a group of users, which doesn’t move as long as you stay inside the tier. The third is usage-based pricing, set according to the modules chosen and the volume of transactions.

Here is what the vendors displayed on the day we read their pages. We added our own grid to show what tier pricing looks like.

Sources: odoo.com/fr_CA/pricing, microsoft.com, Business Central pricing (Canada) and acumatica.com/pricing, read on October 2, 2026. Prices in Canadian dollars, before taxes, as displayed. The Odoo page also advertises a 12-month discount on the users in the initial order; the amounts above are the regular prices. The "for 10 users" column is our own calculation.

This table compares prices, not products. Business Central and Odoo include accounting, OKTO PSA does not. A lower price for software that doesn’t do what you need is still too expensive. For Odoo, we worked through the whole exercise in our comparison with Odoo, including the cases where Odoo is the better choice.

What the subscription doesn’t tell you

None of the vendors we checked publishes an implementation price. Nobody is hiding anything: the amount depends on the state of your data, the number of modules and what you want adapted. It is still the hardest line to predict, and the one to get in writing before you sign.

To compare two quotes without surprises, work out the total cost over three years:

1. Multiply the monthly subscription by 36, at the number of users you will have two years from now and not today’s.
2. Take first-year discounts out of the math. They end, the bill stays.
3. Add implementation and data migration, at a fixed price if you can. If you are given an hourly rate, ask for a capped estimate.
4. Add training: the number of hours, who gives it, in which language, and what a refresher session costs six months later.
5. Add the options billed separately: dedicated hosting, modules, occasional users, connectors to your accounting software.
6. Count your team’s time. Someone on your side will spend days cleaning lists and approving screens, and that time appears on no quote.

Per-user pricing favours very small teams. Tier pricing favours teams that are growing or that have occasional users. At six people, Odoo’s Standard plan comes to $264 a month, less than our first tier at $300. At ten, it is the other way around. Our tier pricing grid has the details, and we ran the same exercise for sales software in our guide to what a CRM costs a Quebec SMB.

What does Law 25 change when you choose an ERP?

Law 25 turns the purchase of an ERP into a decision you have to document. Section 3.3 of Quebec’s Act respecting the protection of personal information in the private sector requires a privacy impact assessment for any project to acquire, develop or overhaul an information system that involves personal information. An ERP holds plenty: customers, contacts, employees.

We reread the French text on LégisQuébec on October 2, 2026, in the version updated to August 12, 2026. The summaries below are ours, and this is not legal advice: for your own situation, talk to your advisor. These are the sections that weigh on the choice of management software.

• Section 3.1. The person with the highest authority in the business acts as the person in charge of the protection of personal information, and may delegate that role in writing. The title and contact details are published on the company’s website.
• Section 3.3. The assessment is done from the start of the project, in consultation with that person, and must be proportionate to the sensitivity and quantity of the information. The same section asks that the project allow a person’s information to be given back in a structured, commonly used technological format.
• Sections 3.5 and 3.8. A confidentiality incident that presents a risk of serious injury is reported promptly to the Commission d’accès à l’information and to the people affected. The business keeps a register of incidents.
• Section 17. Before communicating personal information outside Quebec, or entrusting its storage to someone outside Quebec, the business must carry out an assessment that takes into account, among other things, the legal framework of the State concerned, then sign a written agreement.
• Section 18.3. Entrusting information to a supplier is done by written contract, which sets out the protection measures and provides that the supplier does not keep the information after the contract ends.
• Section 91. For a business, the penal fine runs from $15,000 to $25,000,000, or 4% of worldwide turnover for the preceding fiscal year if that amount is greater.

Sources: Act respecting the protection of personal information in the private sector, chapter P-39.1, on LégisQuébec (French text), read on October 2, 2026.

In practice, that gives you four questions to put to each vendor, in writing. Where is the data hosted, and where do the backups go? Does your contract set out the protection measures and destruction at the end? Can one person’s information be exported in a common format? How quickly are you told about an incident? Hosting outside Quebec is not forbidden. It does require you to carry out the section 17 assessment and keep it on file.

We gathered the full list of checks in our page on Law 25 and customer management software; it applies just as well to an ERP. How we host is described on the security and Quebec hosting page.

French, GST and QST: what the software has to do here

An ERP used in Quebec has to produce invoices in French, display in French for your employees and calculate GST at 5% and QST at 9.975% on every line. Those are baseline requirements. Better to check them in a demo than to find them in a settings screen after the purchase.

French

The Charter of the French language, reread in French on LégisQuébec on October 2, 2026, has several sections that bear directly on management software. Section 57 provides that invoices, receipts and acquittances are drawn up in French. Section 41 requires the employer to use French in written communications addressed to its staff. Section 55 provides that contracts of adhesion are drawn up in French, a point to raise when the vendor hands you its standard contract.

For businesses that employ 25 people or more over six months, section 139 provides for registration with the Office québécois de la langue française. Section 141 lists the use of French in information technologies among the goals of a francization program. An English-only ERP then becomes a problem to fix, and not just an irritant.

Sources: Charter of the French language, chapter C-11, on LégisQuébec (French text), version updated to August 12, 2026, read on October 2, 2026. The summaries are ours and this is not legal advice.

Don’t rely on the words "available in French" in a brochure. Ask to see, in the demo, the French invoice, the customer portal, the automatic emails, the reports and the error messages. Those are the corners where the translation stops.

GST and QST

Revenu Québec gives a rate of 5% for the GST and 9.975% for the QST, both applied to the selling price, which makes 14.975% when they are calculated in one step. Three decimals, then. Software that rounds badly produces one-cent gaps that travel all the way into your returns.

Sources: Revenu Québec, Calcul des taxes (French page), read on October 2, 2026.

Check that the two taxes appear on separate lines, that zero-rated or exempt items are handled line by line and that the tax amounts go out separately to your accounting. We show what that looks like on our end on the page about invoicing software with GST and QST.

Can an ERP project be financed?

There are public programs that support the digital projects of businesses, but their conditions change often. On October 2, 2026, Investissement Québec’s page for the ESSOR program presented it in five components, the first one aimed at studies done ahead of an investment project, namely feasibility studies and a digital diagnostic.

We give no percentage and no ceiling here: the page we opened doesn’t show any, and we don’t repeat figures read elsewhere. Before building a budget on a grant, call Investissement Québec or your local economic development office and get written confirmation that the program is still taking applications and that your project qualifies.

Sources: Investissement Québec, ESSOR program (French page), read on October 2, 2026.

One piece of advice that holds for every program: ask whether the application has to be filed before you commit the expense. If it does, signing the software contract and then looking for help is doing things backwards.

How to choose an ERP in 7 steps

Choosing an ERP takes seven steps, in this order: describe your trade, map your tools, write down your needs, make a short list, demand a demo on your own cases, work out the three-year cost, then read the contract. The order matters. If you watch a demo before writing down what you are looking for, the salesperson defines your needs for you.

1. Describe what you sell. Products, work or both, and in what proportion. That one sentence removes half the market and keeps you from comparing a manufacturing ERP with a services ERP.
2. Map your current tools. For each piece of software and each spreadsheet: who uses it, what it holds, what gets copied by hand into another tool. The double entries are your real list of problems.
3. Write ten needs, not a hundred. Separate what is mandatory from what would be nice. "Bill the hours on a monthly contract without retyping them" is a need. "Have a modern dashboard" is not.
4. Keep three products from the right family. Not eight. Past three, the demos blur together and the team runs out of energy before the decision.
5. Have your own scenarios played out. Send three real cases to each vendor before the meeting: a quote that becomes a job, an invoice with a zero-rated item, a timesheet correction after month-end. Watch how many clicks it takes, in French.
6. Work out the three-year cost. Subscription, implementation, training, options, your team’s time, using the method described above. Compare totals, not entry prices.
7. Read the contract before signing. The commitment term, the price increase at renewal, the hosting location, how you get your data back and how long you have to do it. A difficult exit is negotiated before you go in, never after.

An eighth thing, which is not a step: name one person in charge of the project on your side. Not a committee. Someone who decides, who knows the work on the floor and whose schedule has been cleared for it.

Which mistakes should you avoid in an ERP project?

The expensive mistakes in an ERP project rarely come from the software. They come from picking the wrong family, underestimating the cost or migrating data without cleaning it. Here they are, with what can be done about each one.

• Buying too big. You pick software for the company you might be in ten years, and you pay today for modules nobody opens. Take what solves this year’s problems and only check that the next step exists.
• Starting everything on the same day. Sales, purchasing, time, invoicing and inventory on the same Monday morning. Start with the circuit that hurts most, often timesheet to invoice, and add the rest afterwards.
• Migrating the data as is. The duplicates and abandoned records from the old system land in the new one, looking tidier on screen. The cleanup happens before the import. Our page on data migration explains how we go about it.
• Bending the software to every habit. Each customization is paid for at installation, then again at every update. Before asking for one, ask whether the habit is really worth that price.
• Forgetting training. A one-hour presentation is not enough. Plan sessions by role and a refresher a few weeks after go-live, when the real questions come out.
• Letting IT choose alone. Or management alone. The people who fill in timesheets and prepare invoices have to see the software before the signature. They are the ones who will keep it alive or work around it.
• Keeping the spreadsheet in parallel. As long as the old file circulates, the new system holds only half the information. Set a date when the spreadsheet becomes read-only.

The last mistake is quieter: believing one piece of software will do everything. A small business can do very well with a services ERP connected to an accounting package instead of a suite that covers everything.

Where OKTO PSA fits, and when it is the wrong choice

OKTO PSA belongs to the services ERP family. It brings together work management, a CRM and an HR module: tickets, projects, timesheets, contracts, quotes, orders, invoices with GST and QST, payments. It is made for Quebec businesses that sell hours, contracts and projects, and our team uses it every day.

Each customer has a dedicated database, hosted in Quebec. The interface is in French by default, with English at parity. The price is set by tier: $300 per month up to 10 users, $550 from 11 to 20, $700 from 21 to 30, in Canadian dollars before taxes, all three products included. You can see the software without talking to us in the interactive demo, with fictional data.

Now for the cases where we would tell you to look elsewhere.

• You manufacture. OKTO PSA is designed for selling work, not for scheduling a production line. You need a manufacturing ERP or a modular generalist.
• Inventory is the heart of your business. The product tracks purchases and an inventory, mostly in its construction edition, around the job site. For a high-volume distribution warehouse, it is the wrong tool.
• You want accounting in the same software. OKTO PSA replaces neither your accounting software nor your payroll system. Invoices and payments flow into QuickBooks, and hours export to your accountant or your payroll software.
• You need a public API or custom reports. There is no public API, and reports are limited to a fixed dashboard and five CSV exports. Multi-currency is still a draft.
• You want to try it alone before talking to anyone. The seven-day trial is requested from the team; self-serve, there is only the interactive demo.

If you run an IT services firm, the subject is covered in more depth in our PSA software guide for Quebec managed service providers and on the Quebec PSA software page. For everyone else, the rule fits in one sentence: choose the family first, the software second, and have your own invoice shown to you before you sign anything.