Setting Up Smart Alerts That Actually Match

The fundamental problem with keyword alerts is that procurement language is inconsistent. A single product might appear in tenders as "surgical gloves," "examination gloves, latex," "disposable gloves, medical grade," or simply by its NUPCO catalog code. A keyword alert for "surgical gloves" will miss three out of four of these listings.

The opposite problem is equally common. A keyword like "equipment" matches every tender that mentions any kind of equipment — medical equipment, IT equipment, kitchen equipment, office equipment. You get hundreds of irrelevant matches that bury the ones you care about.

Effective alerts sit in the middle: specific enough to filter out noise, broad enough to catch the variation in how your products are described across different government agencies.

Our platform offers two alert types: keyword alerts and product alerts. Product alerts are the more powerful of the two because they match against your full product catalog.

Here is how it works. You add a product to your catalog with a name, description, and a set of keywords. When a new tender is published, the system matches the tender's items against your product keywords. If a tender contains items that match any of your products, you get a notification that tells you which products matched and which specific tender items triggered the match.

The advantage of product alerts over plain keywords is context. A product definition for "latex examination gloves" might include keywords like "gloves," "latex," "examination," "nitrile," "disposable," and "hand protection." The system uses the combination of these terms to score relevance, so a tender for "disposable latex examination gloves" scores much higher than one for "disposable aluminum containers" — even though both contain the word "disposable."

Start by adding your top ten products. For each one, include the primary product name, any common alternate names, the generic category, and specific attributes like material or size range. The more keywords you attach to each product, the better the matching works.

For products or services that do not fit neatly into a product catalog entry, keyword alerts are the right tool. The key is to be specific without being too narrow.

Good keyword alerts use two- to three-word phrases that describe exactly what you supply. Instead of "equipment," use "laboratory analyzer" or "patient monitor" or "autoclave sterilizer." Instead of "medical," use "medical consumables" or "surgical instruments" or "diagnostic reagents."

Also consider the Arabic equivalents of your keywords. Saudi government tenders are published primarily in Arabic, and the same product can be transliterated or translated in multiple ways. Our system searches across both Arabic and English text in tender titles and item descriptions, so adding Arabic keyword variants improves your match rate.

Avoid single-word alerts entirely. They generate too much noise and will quickly make you ignore your notification feed. The only exception is highly specific product names or brand names that are unique enough to be meaningful on their own.

Keywords alone are one dimension of relevance. The other dimension is context: which portal and which government agency. If you only supply medical products, you probably care about NUPCO tenders and Etimad tenders from health-sector agencies, but not Etimad tenders from the Ministry of Municipal Affairs.

On our platform, you can scope alerts by source (Etimad, NUPCO, or both) to eliminate an entire category of irrelevant matches. For users who work with specific agencies, combining keyword alerts with an agency filter dramatically reduces noise.

Think about it this way: a keyword alert for "laboratory reagents" scoped to NUPCO will match only healthcare laboratory procurement. The same keyword without a scope might also match tenders from university labs, environmental agencies, or agricultural testing facilities. The scoped version is more likely to surface tenders you can actually win.

Good alerts are not set-and-forget. We recommend reviewing your alert configuration monthly. Here is a simple routine.

First, look at your notification feed from the past month. Count how many notifications were relevant (tenders you seriously considered) versus noise (tenders you immediately dismissed). If relevance is below fifty percent, your alerts are too broad — tighten your keywords or add source filters.

Second, look at tenders you found through manual search that your alerts missed. These gaps tell you which keywords or products to add. If you won a tender that your alerts did not surface, figure out why — usually it is because the tender used terminology you had not anticipated.

Third, review your product catalog entries. As you add new products to your business or discontinue old ones, update your product list. Stale product alerts generate stale matches.

This monthly review takes fifteen minutes and keeps your alert system tuned. Over time, you build a keyword and product library that closely mirrors the language government buyers actually use in their tender documents.

The ideal alert setup combines product alerts for your core business lines with targeted keyword alerts for niche opportunities. Product alerts handle the bulk of matching because they leverage multi-keyword relevance scoring. Keyword alerts fill in the gaps — new product lines you are exploring, services you offer alongside products, or specific contract types you want to monitor.

Start with products. Add your top ten, review match quality after two weeks, and refine. Then add five to ten keyword alerts for areas not covered by your product catalog. Scope them by source when possible. Review monthly and adjust.

The goal is an alert feed where every notification is worth reading. When you reach that point, you have stopped searching for tenders — the right tenders are finding you.