When a Kuwait SKU needs a price ping, not a watch

The job is a number you already put next to yours. Same SKU, their shop, a threshold you will actually react to. Their price just crossed it. Someone still hears it from a screenshot after you have already printed the week’s tags.

Teams ask for “price intelligence.” That is a watch. This loop pings when a named SKU crosses the number you wrote down, then stops.

What the automation actually does

It reads the competitor URLs you already named. It compares the price on that SKU to the threshold on your sheet. It sends one note with the old figure, the new one, and the URL. It does not change your price.

Scraping can be the narrow pull when the match rule is already honest. AI automation is the compare-and-ping. We will not promise a legal opinion, and we will not start from a category.

This is not deciding whether to watch competitor prices. That call writes the match rule — barcode, pack size, a Kuwait-only bundle — and who may move your number. A ping assumes both exist. It is also not a Marketplace sold or price-change ping. That job is a card you already hold on a classifieds feed. This job is your shelf against theirs. And it is not a property listing match. A villa is not a SKU.

When we leave the alert with a person

If two buyers still argue whether a 500ml matches a litre, software will page the wrong SKU. If the sites ban automated reads, or the price only exists as an Instagram story, write the public page first. If you price twelve SKUs and check them on Sunday, keep the sheet.

Kuwait retail often mixes KWD on the site with a different number on WhatsApp. Name which number is the one you will react to. Do not average them and call it a threshold.

Bring three SKUs, the two URLs you already open, and the number that would make you reprint a tag. Book thirty minutes or write hello@jamilglobal.com.