Wholesale ERP Consultant, Canada

Price files by region and the cost of distance

Canada's geography puts freight into every wholesale price conversation. A wholesaler based in Ontario that ships to the Prairies, British Columbia or the Atlantic provinces has to decide whether to publish one national price and absorb freight, run regional price files with freight built in, or price ex-warehouse and charge freight on the invoice. Many end up with a mix, plus pickup pricing for trade customers who collect from a branch.

When that mix lives in spreadsheets, the same item can carry several prices with no record of why. I start by mapping the current structure:

• which regions or branches have their own price file, and who maintains it
• whether delivered pricing includes freight and to which destinations
• minimum order values for free delivery, and surcharges for remote areas
• how pickup customers are priced compared with delivered accounts
• which customers have contract prices that override the regional file

From that map I write a pricing design the ERP can hold: a base list, regional adjustments, freight rules and contract overrides, ranked in a clear order. During ERP evaluation one demo order goes to every vendor: identical lines for buyers in three provinces, once delivered and once collected. The differences in how platforms handle that one scenario are revealing.

Currency moves, supplier increases and price protection

A large share of the goods Canadian wholesalers sell are bought in US dollars, either directly from American manufacturers or through distributors who price that way. When the exchange rate moves, replacement cost changes even though the item has not. Wholesalers then face a choice: pass the change through quickly, hold prices for contract customers, or absorb part of it to stay competitive.

The ERP question is how cleanly you can act on that choice. I design a price change procedure with a few defined steps: new cost loaded, proposed sell prices calculated by rule, contract customers identified and protected until their renewal date, customers notified, and the new price file activated on an effective date. Each step leaves an audit trail.

Contracts deserve their own attention. If an institution or a large contractor has a fixed price for a term, the ERP should know the end date and flag the margin while it runs. Account managers can then plan renewal conversations with real numbers rather than discovering at year end that a contract lost money. I include a currency-driven price change in user acceptance testing, because it tests pricing, contracts and notification together in one realistic scenario.

Bilingual catalogs and B2B ordering for Quebec and beyond

Businesses selling into Quebec should expect French to be part of the requirement, from product information to invoices and the ordering portal. The exact obligations that apply to your company and products are a matter for your legal advisor, but the ERP design question is practical: where does French product data live, who maintains it, and does every customer-facing document draw on it?

I define a bilingual item data standard covering names, short and long descriptions, units of measure and any safety or usage text, with a language preference on each customer and contact. The ERP then prints quotes, order confirmations and invoices in the right language, and the B2B portal shows the catalog accordingly. Translation work is assigned to an owner and tracked, so new items are not launched in English only.

Tax is the other piece the portal must get right. Canadian sales tax depends on the province of delivery, and some trade customers provide resale or exemption numbers for provincial tax. My contribution is a scenario list showing current handling by customer and ship-to, which your accountant confirms or corrects. The ERP and portal must then apply that treatment the same way. These flows form part of the ERP integration design.

Customer programs, credit and leaving the current system

Larger Canadian trade accounts often negotiate annual volume incentives, growth bonuses or early payment discounts. When these are tracked outside the ERP, the cost arrives as a surprise and account managers cannot tell customers how close they are to the next tier. Each program becomes a rule: eligible items, tiers of spend, the measurement period and how payout happens. Accruals then build with every invoice, and a customer can be sent a progress statement at any time.

Credit control matters too, especially for contractors whose payment patterns follow their own project cash flow. I specify credit limits by account, holds on overdue balances and an approval path for releasing orders, checked by the portal as well as the order desk.

Typical starting points are Sage 50 or QuickBooks with spreadsheets for pricing, a legacy wholesale package past its support life, or whatever came with an acquired business. Migration covers customers with ship-to provinces and language preferences, active price files and contracts with end dates, program balances to date and items with both language versions. I deliver everything remotely and schedule sessions across Canadian time zones. For more, see Odoo CRM for Canadian businesses, the Canada ERP consultant page, the Canada hub and the wholesale ERP overview.