A distributor's guide to submittal-ready utility product data

Waterworks buyers don't browse a product page for inspiration. They land on it holding a spec sheet, a submittal package due to an engineer, and a job that stops if the wrong valve shows up on site. When the page can't answer their question in ten seconds, they either open a PDF, call the counter, or order the wrong thing and send it back. Here's what a submittal-ready page looks like, using a resilient-wedge gate valve as the working example.

What a waterworks buyer is actually checking

A gate valve buyer isn't asking "does this fit." They're asking "will this pass submittal review," which is a narrower and stricter question. Based on how AWWA C509 and C515 submittals are structured across manufacturers, the questions come in a predictable order:

• Does it meet AWWA C509 or C515, and which edition?
• Non-rising stem (NRS) or outside-screw-and-yoke (OS&Y)?
• End connection: mechanical joint, flanged, or push-on?
• Direction of opening: open-left (standard) or open-right (many municipal specs deviate on purpose)
• Working pressure and shell test pressure (commonly 250 psi working / 500 psi shell for 3"–12" sizes)
• Body, wedge, and stem materials, plus coating (ductile iron body, fully encapsulated EPDM or NBR wedge, fusion-bonded epoxy interior/exterior per AWWA C550)
• Operating nut size and shape (the standard 2-inch square nut, or a specific municipal variant)
• NSF/ANSI 61 and 372 certification for potable water contact
• Number of turns to open, and whether a gear actuator is required above a size threshold

A generic "resilient wedge gate valve, ductile iron, 2"-48"" listing answers none of these. It reads like a category description, not a part the buyer can put in a submittal binder.

Where the gaps actually bite: returns and support load

This isn't a hypothetical data-hygiene problem. NAED research on distributor product data, cited in this Electrical Wholesaling piece on distribution's data problem, puts the cost of bad product data at roughly $5 billion a year across electrical distribution and manufacturing, split across lost sales, returns, and manual cleanup labor. Waterworks carries the same structural exposure, arguably worse, since the parts are more spec-dense and the failure mode is a valve already in the ground rather than a fitting on a shelf.

In practice, the failure pattern for a gate valve looks like this:

Each of these is a wrong-part return plus a support call plus, often, a delayed inspection. None of it is caused by a bad product. It's caused by a product page that made the buyer guess.

Before and after: a resilient-wedge gate valve listing

Raw feed description (typical manufacturer or distributor ERP export):

"Resilient wedge gate valve, ductile iron body, epoxy coated, 6 inch, mechanical joint."

That's technically true and functionally useless for a submittal. Here's the enriched version pulled from the same underlying manufacturer documentation:

That table is the difference between a page a buyer can cite in a submittal and a page they have to route around by opening a PDF anyway.

Ask an answer engine

Increasingly, that first question doesn't start with a Google search or a distributor site at all. One recent analysis found 73% of B2B buyers now use AI tools like ChatGPT or Perplexity somewhere in purchase research, and these systems have no patience for ambiguity: they move to the next listing rather than calling to clarify a missing spec. Picture a project engineer typing into an answer engine: "6 inch AWWA C509 resilient wedge gate valve, mechanical joint, open left, NSF 61 certified, in stock." If a distributor's page has the opening direction, standard, end connection, and certification as structured attributes, it's a candidate answer. If that data lives only in a PDF cut sheet, the engine skips it, and so does the buyer it's speaking for.

The checklist

For any waterworks SKU going onto a product page, run it against this before it publishes:

• Correct AWWA (or ASME/ASTM) standard and edition called out explicitly
• End connection type stated without abbreviation ambiguity
• Direction of opening specified, not assumed
• Operating nut / actuator type and size listed
• Material and coating specs broken into separate attributes, not buried in a paragraph
• Pressure ratings (working and test) both present
• NSF/ANSI certifications listed by number, not "certified" as a vague claim
• Units consistent across the catalog (no 6" on one SKU and 6 in on the next breaking search and filters)

Where this connects to enrichment

Most of this data already exists somewhere: a supplier cut sheet, a spec PDF, an old submittal package in a project folder. The values usually aren't missing, they just never made it out of a document and into a structured attribute. Anglera plugs into whatever a distributor already runs, PIM or none, and pulls those values out of supplier documentation, quality-scores them against the source, and gap-fills the catalog so a page like the gate valve above is submittal-ready by default. Your PIM or ERP still stores the data; Anglera does the work of making sure it's complete enough that a buyer, or an answer engine speaking for one, never has to guess.