How State and Local eProcurement Systems Work for Suppliers

An eProcurement system is the software a public agency uses to advertise solicitations, collect vendor registrations, and receive bids online. For suppliers the confusing part is that there are two layers. The top layer is the agency-branded portal you log into, with a name like NJSTART, MissouriBUYS, or the Arizona Procurement Portal. The layer underneath is the software vendor that actually runs it, and a single vendor often powers hundreds of those branded portals. So the NJSTART you register in and a county portal three states away can be the same product with a different logo. Understanding eProcurement this way matters, because it tells you how many genuinely different systems you face versus how many are repeats. It also explains why the official state procurement portals feel so inconsistent: they were built by different vendors at different times for buyers, not for the suppliers trying to sell into all of them at once. The practical consequence is that your real workload as a vendor is learning a few platform interfaces and then repeating the same registration steps across many branded front ends, rather than mastering a different tool for every agency you want to reach.

A short list of vendors powers most US state and local procurement. OpenGov runs cloud procurement for more than 2,000 cities, counties, and special districts, having absorbed the earlier ProcureNow product into its suite. Euna Solutions has folded several well-known names, Bonfire, IonWave, EqualLevel, and DemandStar, into a single platform called Euna Procurement, so a supplier registering in one increasingly touches the others. Periscope S2G, formerly known for its BuySpeed system and now part of mdf commerce, powers many statewide systems and feeds the BidNet Direct notification network. PlanetBids is common across California and the western US, especially with water districts, school districts, and smaller cities. Tyler Technologies exposes a supplier portal inside its Munis and Enterprise ERP products, so the bid system is really just one tab of the agency's accounting software. Statewide systems also run on SAP Ariba or Jaggaer, the latter strong in public universities, and thousands of small agencies use the low-cost Public Purchase. The table below maps these out. The takeaway is that learning five or six platform interfaces, not hundreds, covers most of the market. If you are weighing one of them as a buyer-side tool, our pages on DemandStar alternatives and GovWin and its alternatives go deeper on specific products.

Registration follows the same shape almost everywhere. You create an account, fill in a business profile with your legal name and tax details, upload a W-9, and then select the commodity codes that describe what you sell. Those codes are the trigger for notifications, so the agency emails you when it posts a solicitation tagged with a code you picked. Some systems add steps for insurance, certifications, or small business registration and supplier-diversity status. The problem is multiplication. Each system is a separate registration, a separate login, and a separate set of codes to maintain, and there is no national directory that pushes your profile to all of them. A supplier selling janitorial services across one metro area can easily face fifteen or twenty distinct portals, each with its own renewal cycle. Many systems also ask for proof of insurance, a current business license, and a banking record for ACH payment before they will let you bid, and some require you to re-attest those details every year. Unlike the federal world, where one NAICS codes profile in SAM.gov reaches every agency, state and local registration stays stubbornly local. Treat it as ongoing maintenance rather than a one-time chore, because a profile that lapses on renewal day quietly stops receiving notifications without telling you.

It helps to split the landscape in two. Statewide systems are the single front doors that handle purchasing for state agencies, and often public universities and some local bodies, under names like NC eProcurement, MissouriBUYS, NJSTART, the Arizona Procurement Portal, and Texas SmartBuy. Register there and you reach a large, centralized buyer. The second group is everything below the state line: counties, municipalities, school districts, transit authorities, and special districts. There are tens of thousands of these, and they each choose their own platform, which is where OpenGov, PlanetBids, Euna Procurement, and Public Purchase dominate. Some states add a twist: California runs the statewide Cal eProcure portal while most of its real volume sits in independent city, county, and district systems, and Texas pairs its SmartBuy system with a Centralized Master Bidders List that vendors join separately. Most public spending that suppliers can realistically win sits in this fragmented local layer, not in the tidy statewide systems. Our guide to winning state and local government contracts covers the bidding mechanics once you are registered.

State and local systems do not use the federal classification you may know. Instead most rely on NIGP codes, a five-digit class-and-item scheme, where the first three digits set the broad class and the last two pinpoint the specific item, while a growing number of systems use the international UNSPSC standard with its eight-digit segment, family, class, and commodity hierarchy. When you register, you pick the codes that match what you sell, and the system only notifies you about bids tagged with those exact codes. Pick too few and you miss relevant work. Pick too many and your inbox fills with irrelevant alerts you learn to ignore, which is just as costly. This is a different world from federal contracting, where NAICS codes and PSC codes drive matching inside the federal eProcurement stack and a single SAM.gov registration carries them everywhere. At the state and local level there is no such portability, so code selection has to be redone, carefully, in every portal you join.

Vendors assume that once they register and pick codes, the bids will find them. In practice notifications are keyword-literal and siloed. Each portal only knows about its own solicitations, so a system you never joined will never email you, no matter how good the fit. Codes have to match exactly, and a buyer who tags a contract with the wrong code, which happens often, simply will not reach you. Because there is no way to register in every one of the tens of thousands of local portals, gaps are guaranteed rather than occasional. The bids you lose are usually the ones posted in systems you did not know existed, not the ones you saw and chose to skip. Registering in twenty portals feels like diligence, yet it still leaves most of your addressable market dark.

Three limits trip up suppliers who lean only on per-portal alerts: • Coverage: twenty registrations still leave most of your market invisible to you. • Literal matching: alerts fire only on exact code matches, so mis-tagged bids disappear. • Maintenance: every portal has its own renewal, and a lapsed profile silently stops sending.

The practical fix is to put broad discovery first and registration second, so you spend effort only on the portals where relevant work actually appears. For a product-by-product view of tools that watch many systems at once, see DemandStar alternatives.

Jorpex sits on top of this fragmentation. It monitors more than 50 public procurement sources, including state and local feeds, and uses embedding-based semantic matching rather than literal keyword rules, so a relevant bid surfaces even when the buyer used different wording or tagged an awkward code. Matches arrive in Slack, Microsoft Teams, or email as realtime, daily, or weekly digests, with disqualifier filters to suppress the noise, and matching works across 17 languages. Plans start at $49 per month for Starter and $149 for Pro, with a 14-day free trial. Because the matching reads the meaning of a solicitation rather than just its commodity code, it also catches bids that buyers mis-tagged or described in unusual terms, which is exactly where per-portal alerts go quiet. To be clear about the boundary: Jorpex finds and ranks the opportunities, but you still register in the relevant agency system and submit your bid there, because that is where the buyer collects responses. Used together with focused registrations and tools like federal bid alerts for the federal side, it closes the discovery gap that per-portal alerts leave open.

You cannot register everywhere, so prioritize. Start with the statewide system in any state where you can deliver, since it is the single largest buyer and the registration covers many agencies at once. Next, list the specific local agencies you already sell to or want to, and register directly in their portals. Then layer in the regional aggregators like BidNet Direct or Public Purchase that cover clusters of smaller agencies in your area. Check whether you qualify for set-aside programs or supplier-diversity certifications, because many state and local buyers reserve work for certified firms. Keep a simple spreadsheet of each portal, your login, your codes, and the renewal date, since lapsed registrations quietly drop you from notification lists. A useful rule of thumb is to register where you can name a real buyer and a realistic first contract, and to rely on broad monitoring everywhere else until a concrete opportunity justifies the paperwork. That keeps your active registrations few enough to maintain properly while still seeing the wider market. Our broader US government contracts guide sets this state and local work in the context of the whole public market.