How to manage contractor accounts across lumberyard branches

A contractor may buy framing at one branch, request windows from another, and ask an outside rep about the next job. Managing that relationship takes more than a shared customer name. Give the account a clear relationship owner, connect its branch records, make current jobs and conversations visible to the right people, and agree on how the next handoff works. Keep branch-specific pricing, stock, and delivery promises with the teams that can confirm them.

This is an account-coverage routine, not a reason to replace your ERP. Industry software documentation already treats this as a multi-location problem. ECI's Spruce overview describes inventory across yards and account, pricing, and order history for lumber dealers. Its lumberyard overview describes centralized multi-location reporting. Those are ECI product descriptions, not capabilities to assume in every system. The sales question is narrower: when a contractor calls a different branch, can that team understand the relationship and take a useful next step?

Identify the account before you assign the work

Start by checking how each branch names the same contractor. One location may use a legal business name, another a trade name, and a third a separate ERP customer number for a credit account. Do not merge records because the names look similar. Have someone verify the legal entity, billing relationship, contacts, and any parent or subsidiary accounts with the people who maintain your customer master.

Keep the shared relationship separate from the individual job. A builder might have several active projects, each with its own site, estimator, delivery schedule, and material package. An account-wide view should let an authorized rep find the relevant job without treating every quote under that customer as one sale. If a branch cannot see another branch's transaction detail, establish a safe way to request it. Access permissions and credit rules take priority over convenience.

A useful starting audit is a small sample of contractors who have transacted at more than one location. For each, check whether the same identity, main contacts, current projects, and responsible people can be found without relying on one rep's inbox. Record ambiguous matches as exceptions rather than silently combining them. For the technical side of matching ERP records, see SalesJack's ERP and CRM integration guide.

Name an account owner and a job owner

The person responsible for the overall contractor relationship is not always the person running every job. An outside rep might own the account while an inside salesperson manages a takeoff and a branch specialist handles window selections. Name the relationship owner, then identify who owns the next action on each active project. Record a backup when that person is away.

Also distinguish the branch that originated a quote from the branch that will fulfill an order. Those may differ when inventory, delivery routes, or specialist teams cross locations. The distinction helps the sales team ask the right person for a price, availability check, or delivery commitment. It should not be used to improvise commission or revenue-credit rules. The dealer's established policy still governs those decisions.

Use a rule staff can apply at the counter. For example: existing account questions go to the named relationship owner; a live job issue goes first to its current job owner; a new request with no match goes to the manager for assignment. That is an example policy to adapt, not a claim that every yard should route work the same way. SalesJack's dealer CRM page describes assignment by territory or product line; test any proposed routing rule against how your branches actually cover contractors.

Pass along the job, not just a phone number

A handoff should answer what the contractor needs, what has already been said, and who will answer next. Consider a contractor who requested a framing takeoff at the north branch, then visits the south branch to ask whether some materials can be picked up closer to the site. The south counter needs to know the job address, the current quote version, and who can confirm stock and pricing. It should not assume the first branch's estimate is still valid.

A short handoff note can include the project or site, the current request, the last conversation, a named next owner, and any item that still needs verification. Share it where the people involved in the job can see it, subject to your access rules. If the customer must repeat the entire story, inspect where the context was lost. If two reps contact the same contractor about the same job, inspect the ownership rule.

Yesterday's quote follow-up guide explains how to keep an individual estimate current and schedule the next conversation around the contractor's job. Across branches, the extra task is to make that job context travel with the account when the serving location changes.

Keep local promises local

A shared account view does not make every branch's inventory, lead time, or customer price identical. Before promising a pickup or a delivery from another location, verify the product, quantity, transfer plan, and timing with that branch. Confirm which team is authorized to revise a quote or approve an exception. The goal is one informed conversation with the contractor, not a centrally issued promise that a local yard cannot keep.

In ECI's Window Depot customer story, a multi-location window and door dealer says centralized customer records let staff access account details from any location. The same story describes connected pricing and inventory information. That is one vendor-published example of shared context, not a performance promise or a claim that every yard has those capabilities.

If a branch cannot see an item it needs to answer, write down whether the gap is missing data, limited access, stale status, or unclear ownership. Those are different problems. A new dashboard will not fix a pricing-approval rule that nobody has agreed to.

Review the exceptions together

A manager does not need another broad revenue report to spot coordination problems. Review a short list of shared accounts with no named owner, active jobs that changed branch without a handoff, duplicate contacts for the same request, and customer commitments awaiting local confirmation. Assign an owner to resolve each exception, then check whether the rule or the record caused it.

Keep this review separate from broader category, frequency, and wallet-share measures. Those measures explain growth opportunities. The branch review explains whether people can carry out the next customer action without losing context. SalesJack's analytics page says dashboards can be customized by role for leadership, store management, and reps; confirm the specific branch and account views your team needs before assuming they are already configured.

Try the routine on a small set of shared contractor accounts. Have the managers from the affected branches agree on ownership and handoffs, check the source records with the ERP team, and walk through one real customer request from first contact to local fulfillment. If the rep still needs a private spreadsheet to find the answer, note exactly which detail is absent. A repeatable branch process is only useful when the next person can follow it.

To see how SalesJack brings ERP quotes, requests, and conversation history into its CRM, review the CRM workflow. Ask the team to demonstrate it with your branch structure and a real cross-location account before choosing a setup.

Sources

• ECI, Spruce building-materials software: Vendor description of inventory, account, and order data for dealers.
• ECI, software for lumberyards: Vendor description of multi-location reporting for lumber dealers.
• ECI, The Window Depot customer story: One multi-location dealer's account of shared customer information.