NetPricer and Trade Service: The Electrical Pricing Files

NetPricer is the electrical pricing service that pipes prices into your estimating software, and Trade Service (now part of Trimble) is the product and pricing data source that feeds distributor systems. Here is the part that changes how you should use both: the pricing your estimating package shows you is not a market price. It is what your distributor chose to send to the service on your behalf. ElectricSmarts states it plainly, describing NetPricer as providing electronic pricing 24/7 but only for products that your distributor feeds to the service for you.

That single sentence resolves a lot of confusion. Your takeoff is reading a mirror of your own supplier relationship, refreshed on your supplier’s schedule.

You want to know four things about that arrangement: what each system actually is, what fields move between them, where the gaps open, and what to check before you bid off a number that came out of a price file.

Trade Service: the catalog and list price layer

Trade Service is the data spine underneath electrical distribution. Trimble, which now owns it, describes the product as managed pricing and product data from major manufacturers delivered in one source, with eDataFlex syncing it into distributor ERPs.

The fields Trimble names for that data set tell you what kind of number you are looking at:

Field	What it is	What it is not
Permanent ID Key	Stable internal identifier for the item	Anything you will ever type
UPC	Barcode identifier	Manufacturer’s catalog number
Manufacturer Catalog Number	The number you and your rep actually say out loud	A distributor SKU
Long Description	Full item description	A spec sheet
List Price	Published manufacturer price	Your price, or anyone’s price
Unit of Measure	Each, C, M, bag, reel	Always the same as how you buy it

Notice what is absent from that list: your net price. Trade Service carries the catalog and the list price. Everything between list and what you pay is your distributor’s layer, and that layer lives in the distributor’s ERP, not in the catalog feed. The vocabulary for those layers is worked through in list price vs net price at your distributor.

This is also why the last field in the table matters more than it looks. Unit of measure mismatches between the file, the quote and the invoice are one of the most common apparent overcharges in the trade, and they are almost always a data problem rather than a pricing decision.

Distributors do not work purely from this feed either. Electrical Trends describes distributors pricing from Trade Service sheets and in-house sheets with columns showing several gross profit percentages, plus customer classification buckets and blanket pricing. So the feed is an input to a pricing decision, not the decision.

NetPricer: the pricing layer inside your estimating software

NetPricer sits one step closer to you. It is built into participating electrical estimating packages and supplies pricing electronically, so an estimator running a takeoff gets priced material without calling anyone for a quote. ElectricSmarts describes the service as available 24/7 inside participating estimating packages, which is genuinely useful and saves real hours on bid day.

The condition attached to it is the whole story. The pricing that flows is for products your distributor feeds to the service on your behalf. Three consequences follow, and none of them are obvious from inside the software:

Coverage is a subset. Items your distributor does not feed simply do not price. Your estimator either falls back to a stale internal price, a target price, or a phone call. The gaps are invisible until someone goes looking for them.

Currency is your distributor’s decision. How often the feed refreshes is set by the distributor, not by you and not by the market. A number that appears in your software today may reflect a decision made some weeks ago.

Scope excludes job support. Manufacturer-supported job pricing is negotiated per job, per contractor, per part number. It does not live in a standing feed. That mechanism is ship and debit, and the reason it cannot show up in your estimating package is structural: there is nothing to feed until someone asks the factory.

None of this is a criticism of the service. A distributor feeding accurate contractor-specific pricing into an estimating package is doing you a real favor, and doing it costs them work. It is a criticism of using the output as if it were an independent market reference.

Why a price file can be right and still be wrong

The gap between a price file and reality is usually latency rather than error, and latency only matters when the underlying commodity is moving. Right now it is moving.

The BLS producer price index for copper and brass mill shapes (series WPU102502, 1982=100) read 747.384 in January 2026 and 803.275 in June 2026, and that June figure is marked preliminary by BLS. Aluminum mill shapes ran 246.9 in January 2025 to 391.268 preliminary in June 2026. AGC’s read on May 2026 was that copper and brass mill shapes were up 26.8% year over year while aluminum mill shapes were up 48.8%, with the overall index of inputs to new nonresidential construction up 8.4% year over year, the largest annual jump since the pandemic. Re-pull those series before you quote them anywhere; preliminary months get revised.

Against moves of that size, a price file that lags by a few weeks is not a rounding difference on a wire package. And the response inside the channel is manufacturer price letters, which change list price, which moves every derived price without anyone renegotiating a multiplier. That is the same quiet mechanism behind material price creep.

A contractor on the Mike Holt forums described the downstream version of this: “They may quote the stuff on bid day at say $87,000 but when you add all the total invoices up at the completion of the project they can be from $87,000 to $100,000 or more.” A bid-day price file is a snapshot, and a job is not a snapshot.

What to check before you bid off a price file

Run this once a quarter. It is not long, and the outcome is knowing which of your estimating numbers you can trust.

Pull a coverage report. How many of the SKUs in your standard assemblies actually price from the service, and how many fall back to a default? The fallback list is where bid risk hides.
Find out the refresh cadence. Ask your distributor, in writing, how often they update the feed for your account. There is no standard, and the answer is theirs to set.
Spot-check the file against your last three invoices. Same SKU, same unit of measure, same branch. If the file and your invoices disagree, the invoices win, because that is what you actually paid.
Check unit of measure on every high-volume line. Wire priced per M versus per C is a factor-of-ten error and it survives a total-level review without a blink.
Separate stock pricing from job pricing in your estimate. Anything you expect manufacturer support on should be quoted, not priced from the file. Bidding supported prices you have not secured is the fastest way to a variance you cannot explain.
Compare the file’s implied multiplier to your agreement. Net divided by list, per line, grouped by category. If those decimals do not match the categories in your contract, either the agreement or the feed is out of date. The arithmetic is in column pricing at an electrical distributor.
Keep your own price history regardless. Your last twelve months of invoiced unit prices is the only pricing dataset in this entire chain that nobody else controls.

That last point is not a small one. Every other number discussed in this post is maintained by someone else and refreshed on someone else’s schedule. Yours is not.

Two of those steps deserve a note. The coverage report in step one is the one estimators resist, because pulling it means admitting how much of a bid rests on defaults. Do it anyway, and do it on your standard assemblies rather than on a live bid, so nobody is under time pressure while they look. And step three, the invoice spot-check, is the only one that produces a number you can take to a rep. A price file disagreeing with another price file is a conversation. A price file disagreeing with your own signed invoice is a document.

Questions worth asking, and one worth skipping

Good questions for your distributor:

“Are you feeding my contractor pricing to NetPricer, or is my estimating software seeing list with a default multiplier?” These produce very different bids.
“Which product categories are not in the feed for my account?”
“How often does the feed refresh, and does it refresh when a manufacturer issues a price letter?”
“If my agreement changes, how long before my estimating software reflects it?”

Good questions for your estimating software vendor:

“When a SKU has no NetPricer price, what does the package substitute, and is that visible on the takeoff?”
“Can I flag lines priced from a fallback so an estimator sees them before the bid goes out?”

The question worth skipping: asking your distributor to justify why their fed price differs from a competitor’s fed price. Those are two different agreements with two different companies, and there is no shared reference to compare against. If you want to move your rate, move the rate, using the approach in how to negotiate with your supply house, rather than litigating a data feed.

It is also worth being clear about what nothing here requires. No rule obliges a distributor to feed your contractor pricing rather than list, to refresh on any particular schedule, or to notify you when a fed price changes. All of that is contractual or, more often, simply customary. If you need a commitment, it has to be one you ask for and get in writing.

The short version

NetPricer supplies electronic pricing inside participating electrical estimating packages, but only for products your distributor feeds on your behalf.
Trade Service, now Trimble, supplies the catalog and list price layer that distributor ERPs run on. It carries list price and unit of measure, not your net price.
Your estimating software therefore reflects your supplier relationship, not the market.
Coverage gaps, refresh cadence and the absence of job-specific support pricing are the three structural limits.
Commodity indexes have been moving hard, so file latency is a real bid risk rather than a rounding issue.
Spot-check the file against your own recent invoices, check unit of measure, quote anything you expect job support on, and keep your own price history.