ERP Business Analyst in Montreal

Apparel wholesalers in the Chabanel district and beyond

The Chabanel area in the north of the city has long been home to clothing manufacturers, importers and wholesalers, and many Montreal fashion companies still sell to department stores, chains and independent boutiques across North America. Their processes look simple from a distance and are anything but simple in an ERP.

A single style can exist in many sizes and colors, sold as individual units or as prepacks with a fixed size ratio. Collections are planned by season, ordered from overseas factories well in advance, and landed with freight, duty and broker charges that need allocating to each style. Large retail customers send routing guides and labeling rules, and when a shipment does not comply they deduct money from the payment, sometimes long after the invoice was issued.

I map the full chain from line sheet to cash. Requirements cover the style, size and color matrix, prepack definitions, purchase orders by season, landed cost allocation, retailer-specific labels and documents, and a structured way to record each deduction with a reason so it can be disputed or accepted. Without that last piece, gross margin by customer is usually overstated. Electronic order exchange with retailers is documented as a separate integration requirement, with the formats each retailer expects. The wholesale ERP page covers general distribution requirements.

Food processors: lots, holds and two languages on every pack

Greater Montreal has a large food processing sector, from bakeries and meat processors to dairy, confectionery and specialty products, much of it in industrial parks in Saint-Laurent, Anjou, Laval and the South Shore. These plants share a core requirement: being able to tell, quickly and with evidence, which finished lots used which ingredient lots and where those finished lots went.

Federal food safety rules expect that kind of traceability, and grocery customers often add their own audit requirements, so I treat it as a foundation rather than a feature. I document receiving and lot capture, quality holds and releases, production consumption, catch weights where products are sold by weight, shelf life and expiry rules, and mock recall steps. Each one becomes a requirement with a test case attached.

Packaging adds another layer. Food labels sold in Canada generally carry both official languages, and products sold in Quebec raise additional French-language considerations. In ERP terms that means bilingual item descriptions, separate packaging components when artwork changes, and controls so old packaging is used up or written off deliberately. What the labels must say is a question for your regulatory advisors; how the system controls versions is mine. The food and beverage ERP page has more on production setups.

Quebec contractors and the construction labor regime

Construction in Quebec runs under its own labor framework. Trades and occupations are defined by regulation, wages and benefits follow sector collective agreements, and employers report hours and contributions to the Commission de la construction du Québec. For a Montreal contractor, that framework shapes payroll, job costing and the data an ERP must carry, and it is easy for an implementer from outside the province to underestimate it.

I do not interpret the rules; your payroll provider, accountant and association do that. What I document is how the rules show up in daily work: how hours are captured by worker, trade, project and sector, how premiums, travel and other allowances are recorded, how labor cost flows to each job, and what file the ERP must exchange with the payroll service that produces pay and the required reports.

I also map the project side: estimates, contracts, progress billing, holdbacks, subcontractor invoices and change orders, and how licensing details for the firm and its subcontractors are tracked. The result is a requirement set where labor data is captured once and reused, rather than typed into timesheets, payroll and job cost reports separately. The construction ERP page covers project controls in more general terms.

Event production and rental houses in festival season

Montreal's calendar of festivals, conferences, concerts and sporting events supports a cluster of companies that rent staging, audio, lighting, video, tents, furniture and power. Their busiest weeks stack several large events on top of each other, and the same equipment may leave the warehouse for one site, come back and go out again within days.

Standard ERP sales and inventory processes do not describe this well. The key question is not how many units are in stock but how many are available on a given date range once existing bookings, maintenance and transport time are considered. I document quoting by event and date, kits that contain many items, substitutions, cross-rentals from other suppliers when demand exceeds stock, crew scheduling and call times, loading and returns, and billing for damage, loss and extra days.

These requirements often reveal that a rental-specific application is needed alongside, or instead of, a general ERP. I write them so that both kinds of product can be scored fairly, and I document the integration needed between rental, accounting and payroll so that a busy summer does not end in weeks of reconciliation.

Remote workshops and the documents left behind

The analysis is done remotely through video workshops, screen sharing and review of real documents such as order forms, packing lists, timesheets and invoices. Visits can be arranged for a walk-through of a plant or warehouse where that adds value.

The engagement runs in English. Where some staff prefer to explain their work in French, a bilingual colleague joins the session and relays the discussion, and French field labels or document wording in the requirements are confirmed by native speakers on your team.

The deliverables are maps of today and the target process, a numbered business requirements document, a data migration map listing sources, owners and cleansing rules, a fit-gap matrix for shortlisted platforms and a set of acceptance test scripts based on your own scenarios. Each document is written so it outlives my involvement and can be handed to whichever integrator you choose. For how the requirements feed a platform decision, see the Montreal ERP consultant page; the Canada-wide view of sales tax and cross-border requirements is on the Canadian ERP business analyst page.