Buy America Traffic Signal Procurement in 2026: The Documentation Buyers Need

Johnny Wu | Industry perspective | September 25, 2026

U.S. traffic signal procurement is approaching another Buy America milestone. For suppliers, distributors, and contractors, I expect greater attention to whether the ordered model, its manufacturing origin, and its submittal documentation actually match. Selecting a product does not resolve every procurement question if the supporting documents fail to cover the configuration being purchased.

This change directly affects the selection and delivery of LED traffic signal modules. This article focuses on manufactured products in applicable FHWA Federal-aid highway projects. Each project still requires confirmation of its funding, contract provisions, and any applicable waiver. The dates below should not be applied to every U.S. local purchase or treated as a rule for the Canadian market.

Confirm the project date and applicable phase

FHWA's 2025 final rule ended its general waiver for manufactured products and introduced phased requirements. The immediate development is an established policy reaching its next phase; the requirements did not all originate in 2026 (Buy America Requirements for Manufactured Products, 2025).

Under current 23 CFR § 635.410, applicable manufactured products in projects obligated on or after October 1, 2025, must be manufactured in the United States. For projects obligated on or after October 1, 2026, the cost of components mined, produced, or manufactured in the United States must also exceed 55% of the total cost of all components (Buy America requirements, 2026).

The reference point is the project's obligation date. A quotation, purchase order, or delivery date is not a substitute. I recommend confirming the applicable phase with the project contact before quoting and recording it on the first page of the submittal package. A customer's statement that a purchase is happening “this year” does not establish which declaration is needed.

That distinction matters when a distributor is supporting several projects with similar equipment. Two orders entered in the same week may relate to projects with different obligation dates and contractual requirements. A single folder labeled “2026 compliance” can obscure that difference. I would organize the record around the project first, then associate the applicable product evidence with it. For existing inventory, the practical question is whether the exact unit and its supporting documentation satisfy the receiving project's requirements. An earlier purchase date alone does not answer that question. This approach also helps sales teams avoid making a commitment before the customer has provided the information needed to evaluate it.

Verify manufacturing location and component cost separately

FHWA's January 2026 questions and answers explain that importing a product and merely packaging or labeling it in the United States does not establish U.S. manufacture. A supplier's address, shipping warehouse, and manufacturing location are different pieces of information and should be requested separately (Federal Highway Administration [FHWA], 2026, Question 5).

The percentage also requires precision. The regulation says greater than 55%, and the denominator is the total cost of all components, not the selling price. Purchased and manufacturer-produced components must be costed under the prescribed rules. Costs associated with manufacturing the final manufactured product cannot simply be added to increase the domestic percentage (Buy America requirements, 2026, § 635.410(c)(3)).

I would separate the manufacturing-location declaration from the applicable component-cost evidence in the review checklist. One addresses where manufacturing occurs; the other addresses the applicable domestic-content threshold. The submission method should follow the owner's requirements. This does not mean that every purchasing contact must receive a complete, unredacted commercial cost breakdown.

For illustration, a calculated domestic component share of exactly 55% does not clear a requirement that says greater than 55%. Nor does a high share of domestic sales revenue demonstrate the required component-cost percentage. These are different measurements. The lesson for a commercial team is to preserve the language of the underlying requirement when summarizing it. Replacing “greater than” with “at least,” or substituting a broad U.S. business presence for manufacturing evidence, creates ambiguity that a buyer then has to resolve. I would also identify who maintains the supporting calculation and who is authorized to issue the declaration. That internal responsibility should be established before a distributor needs an answer for a time-sensitive submittal.

Define exactly what is being purchased

In traffic signal procurement, a module, a signal head, and an equipment package should not be described interchangeably as a “signal product.” FHWA uses traffic signals to illustrate how delivery as a single product can differ from separate procurement and assembly at the site. A qualifying kit may still be treated as a single manufactured product even when its components arrive separately (FHWA, 2026, Questions 9–11).

I would therefore establish the delivery unit, complete part number, and assembly responsibility before confirming the product boundary covered by the documentation. The purpose is a verifiable procurement record. Splitting an order should not be interpreted as a route around the requirements.

For example, when evaluating Frontier Ball LED traffic signal modules or Frontier Arrow LED traffic signal modules, the product pages provide a starting point for selection. Submittals should still be checked against controlled specifications and declarations covering the actual ordered part number. Ball and arrow modules are separate product families; a shared brand name does not establish that the same documentation covers both (Frontier, n.d.-a, n.d.-b).

Project teams should also be careful when moving from a module discussion to a wider intersection equipment package. The regulation contains a specific provision for predominantly iron or steel cabinets and enclosures of certain ITS and electronic hardware systems classified as manufactured products and installed in the highway right of way or other real property (Buy America requirements, 2026, § 635.410(c)(2)(ii)). That provision is a reason to define the equipment boundary carefully. Evidence for an LED module does not, by itself, resolve the requirements for a cabinet or an entire system supplied under the same project. My recommendation is to assign each delivery item to a documented review, with the responsible project authority confirming the applicable classification.

Read approval lists at the model level

A directly relevant example is TxDOT's Traffic Signals material producers list. The version reviewed here is dated October 22, 2025. It identifies “LEOTEK Frontier, formerly Dialight” and lists a Buy America status of Compliant for specific models, including the 433-1210-003XL red ball module (Texas Department of Transportation [TxDOT], 2025, p. 3).

The value of this evidence is its connection to an agency list and a complete model number. The list explains that the status reflects manufacturer certification and the applicable classification; a blank status requires project-level certification (TxDOT, 2025, p. 1). A blank entry should therefore not automatically be read as noncompliance.

I would not extend this 2025 list into a blanket assurance covering every Frontier product, every state, or every project obligated from October 2026 onward. The appropriate next step is to check the current list, complete part number, and applicable phase, then confirm that the submitted evidence covers the purchase. An agency list is valuable evidence with a defined version and scope.

For distributors managing legacy records, the wording “formerly Dialight” is especially useful as a cross-reference. It provides a way to locate the listed manufacturer entry when older purchasing files use a different name. It should not be used to infer that every historical model has an interchangeable current replacement. I would record the older identifier, proposed current part number, and document supporting the match in separate fields. Where a match remains unconfirmed, the right action is to ask for clarification. Silently shortening a part number or removing a suffix can make a spreadsheet cleaner while making the purchasing record less reliable. The full identifier is part of the evidence trail.

Buyer’s review matrix. Use the following questions to route evidence to the right reviewer. The contract and agency instructions control the final submittal.

Five information groups suppliers can prepare now

The following is my recommended submittal preparation checklist, not a set of five forms universally mandated by FHWA. The project contract and recipient agency procedures determine the actual format and signature requirements.

1. Project applicability. Record funding, obligation date, applicable clauses, and any waiver or special condition requiring confirmation. Sales and documentation teams should work from the same facts.
2. Complete product identification. Include the part number, suffix, configuration, specification revision, and delivery scope. The quotation, purchase order, and declaration should be mutually traceable.
3. Manufacturing and origin evidence. Prepare manufacturing-location information and the component-origin or cost-percentage evidence appropriate to the applicable phase. Confirm that each declaration covers the product being supplied.
4. Agency acceptance information. Where an approved list is required, retain the verification date, list version, and corresponding entry. Check technical acceptance and Buy America evidence separately.
5. Change and delivery records. Assign a documentation owner. When components, manufacturing locations, or substitute part numbers change, reassess whether existing declarations remain applicable and retain a traceable record.

Consider a hypothetical contractor who accepts a different part-number suffix during delivery planning while retaining the declaration for the original model. That is a gap worth identifying before shipment. This is an illustrative scenario, not a reported Frontier incident. It shows why documentation review should track order changes instead of occurring only at the initial quotation.

Build document review into the purchasing schedule

I would use three review points. At quotation, confirm the project's applicable requirements and identify the proposed models, while marking unresolved questions clearly. Before releasing the order, reconcile the accepted submittal with the actual purchase order and agree on the evidence needed for delivery. Before shipment, check whether the model, configuration, or relevant manufacturing information has changed. These are recommended management steps, not additional federal approval stages. Their purpose is to make document ownership visible while the parties still have time to resolve discrepancies. A small project may need only a concise checklist; a larger package may need a structured register covering several suppliers.

For an alternative product or revised configuration, I would ask two separate questions: does it satisfy the technical specification, and does the evidence cover the project's domestic-content requirements? A positive answer to one does not establish the other. The purchasing team can record both decisions beside the exact part number and revision. If the customer requests a replacement late in the process, that same record makes it easier to see which earlier approvals must be revisited. A delivery commitment should account for the time needed to complete this review. I would not represent a technically acceptable substitute as ready for release while its required supporting documentation remains unresolved.

The process also needs a practical rule for confidential information. A manufacturer may hold detailed cost records that are commercially sensitive. The parties should establish what the recipient agency requires, who can review the supporting material, and what signed statement is acceptable for the project. A general marketing brochure is unlikely to answer those procedural questions. Conversely, collecting more sensitive detail than the project requires can add friction without improving the decision. My preference is a clear request tied to the relevant requirement, with an identified reviewer and a retained response. That gives the commercial and technical teams a shared basis for deciding whether an issue is closed.

My outlook for suppliers and their marketing teams

I expect suppliers with clear documentation ownership and revision control to be better equipped to answer questions from consultants, distributors, and contractors. This is an inference about the procurement process. It does not establish that the rule will cause universal price increases, shortages, or contract wins for any particular brand; the evidence reviewed does not support those market conclusions.

For B2B marketing, useful content can move closer to the actual purchasing decision: explain the dates, demonstrate model verification, provide a document request checklist, and invite the buyer to discuss a specific project. Product positioning can emphasize assistance with selection and documentation review. Any compliance commitment should be supported by evidence covering the relevant model and project.

For distributors and integrators, I recommend scheduling documentation review alongside product selection and giving engineering, purchasing, and sales one shared checklist. Identifying missing information early gives the buyer a better opportunity to resolve it before finalizing the purchase and carrying unresolved questions into delivery.

For a Frontier content program, I would translate this into a focused buyer journey. An educational article establishes the project questions. The relevant ball or arrow product page helps the reader identify the product family. A contact request then captures the model and project information needed for a useful follow-up. The call to action should ask the reader to request documentation for a defined purchase, rather than imply that visiting a page establishes eligibility. This makes the content more useful to engineers and procurement teams while giving sales a better starting point than an inquiry containing only a general request for a “compliant traffic light.”

I would judge that content by the quality of the resulting conversations. Are incoming inquiries more likely to include complete part numbers and project dates? Can the team identify missing evidence earlier? Are repeated clarification requests decreasing? These are suggested measures, not reported Frontier results. They connect marketing activity to the work a buyer actually needs to complete. They also provide a way to improve the article and inquiry process over time: if customers repeatedly misunderstand the obligation date or confuse a module with a complete signal head, that is a specific content gap the team can address.

The development I would watch after October is how individual agencies communicate their documentation expectations and how suppliers maintain evidence when configurations change. The regulation provides a common baseline, while purchasing teams still need usable instructions for a particular submittal. Clearer agency templates or revised approved-product lists could change what information a distributor should collect at the start of an inquiry. Those developments would justify updating sales materials and training, even if the underlying product remains unchanged. I would monitor official agency sources and dated manufacturer documents rather than infer a policy change from a competitor's headline.

This creates a useful discipline for future Frontier articles as well. A claim about manufacturing, approval, or product eligibility should identify its scope and supporting document. A claim about market effects should identify whether it is observed evidence or a forecast. Readers evaluating public-infrastructure purchases need to know which kind of statement they are reading. Keeping that distinction visible gives an expert viewpoint more credibility and makes the resulting content easier for a procurement team to use.

Start with the actual Frontier model

If you are planning a purchase of ball or arrow LED traffic signal modules, use the Frontier product pages above to identify your needs, then contact the Frontier team with the project location, funding source, obligation date, complete part number, and submittal deadline. Request the applicable documentation and current controlled specifications.

I suggest beginning with a specific question: “Does this declaration cover this project, this model, and the configuration being delivered?” When the answer can be checked against the records, the product selection has a stronger foundation for delivery.

Related reading

For the separate question of technical and agency approval, see five checks behind an “approved” traffic signal module. For legacy part-number transitions in a purchasing record, see the Dialight-to-Frontier replacement guide.

References

Buy America requirements, 23 C.F.R. § 635.410 (2026). https://www.ecfr.gov/current/title-23/chapter-I/subchapter-G/part-635/subpart-D/section-635.410

Buy America Requirements for Manufactured Products, 90 Fed. Reg. 2932 (January 14, 2025). https://www.govinfo.gov/content/pkg/FR-2025-01-14/pdf/2024-31350.pdf

Federal Highway Administration. (2026, January 5). Questions and answers (Q&As) on the Federal Highway Administration (FHWA) manufactured products final rule. https://www.fhwa.dot.gov/construction/contracts/pdfs/Manuf_Products_QA_FINAL_RULE_Doc1.pdf

Frontier. (n.d.-a). Frontier arrow 12″ 80–135Vac ITE LED traffic light module. Retrieved September 25, 2026, from https://frontier.leotek.com/product/frontier-arrow-12-inch-80-135v-ite-led-traffic-light-module/

Frontier. (n.d.-b). Frontier ball 8″ / 12″ 80–135Vac ITE LED traffic light module. Retrieved September 25, 2026, from https://frontier.leotek.com/product/frontier-ball-8-12-inch-120v-ite-led-traffic-light-module/

Texas Department of Transportation. (2025, October 22). Traffic signals: Material producers list. https://www.txdot.gov/content/dam/docs/division/mtd/mpl/qtrfsigeqp.pdf