Structured government procurement data around the globe β tenders, suppliers and agencies. We help you research what governments around the world buy and find new opportunities to sell to them. No need to get a foreign company or e-signature before deciding there's money to be made. Browse for free; a flat fee unlocks the full dataset, saved searches, REST API and MCP.
the "ancient website, portal from 2004" framing in your screenshots is honest, but it also raises the question I'd actually want answered before paying for this - when a source agency's portal is that old and clearly not built for scraping, how do you catch it silently breaking or going stale? A tender feed that looks alive but is actually 3 months out of date on some obscure agency site seems like the failure mode that would matter most and be hardest to notice from the buyer's side.
@vlad_nadymovΒ that lines up with what I'd expect, honestly, check-and-upsert is the only real option when there's no upstream signal. what I'm actually curious about is whether you monitor the scrapers themselves for silence rather than just for errors. a portal that starts serving a slightly different HTML structure without throwing anything would just quietly stop updating rows, no exception anywhere, and the row would sit there looking current. is there a "this source hasn't changed in an unusually long time" alert on your side, or would that kind of drift currently only get caught by a customer noticing a stale listing first?
Dial
the "ancient website, portal from 2004" framing in your screenshots is honest, but it also raises the question I'd actually want answered before paying for this - when a source agency's portal is that old and clearly not built for scraping, how do you catch it silently breaking or going stale? A tender feed that looks alive but is actually 3 months out of date on some obscure agency site seems like the failure mode that would matter most and be hardest to notice from the buyer's side.
Sell to State
@galdayanΒ well it's the best you can do β if the origin is stale, there is no place to get it at all
usually what we do is check the portal and upsert the changed rows
the problems start if it's unstructured data even at source
Dial
@vlad_nadymovΒ that lines up with what I'd expect, honestly, check-and-upsert is the only real option when there's no upstream signal. what I'm actually curious about is whether you monitor the scrapers themselves for silence rather than just for errors. a portal that starts serving a slightly different HTML structure without throwing anything would just quietly stop updating rows, no exception anywhere, and the row would sit there looking current. is there a "this source hasn't changed in an unusually long time" alert on your side, or would that kind of drift currently only get caught by a customer noticing a stale listing first?