---
title: "Restock Alerts — Get Emailed When a Size Comes Back in Stock, Alp Korpe"
description: "A small site (\"Has My Size Arrived?\" in Turkish) that watches a product URL for a specific size and emails the user when it becomes available. Born from…"
url: https://yigitalpkorpe.com/projects/monitor/
site: yigitalpkorpe.com
---

[Projects](https://yigitalpkorpe.com/projects/) / Web Tools

*Web Tools*

# Bedeni Geldi mi?

Watches a product page and emails you the moment your size is back in stock.

Stack

-   Python
-   Web Scraping
-   PHP
-   Email Automation

![Bedeni Geldi mi? — Watches a product page and emails you the moment your size is back in stock.](https://yigitalpkorpe.com/_astro/monitor.BgNL7z30_Z1tmbW5.webp)

“Bedeni Geldi mi?” (Turkish for *Has My Size Arrived?*) is a small web service that monitors a product URL for a specific size and emails the user the moment it comes back in stock. The interface is a single form: brand, link, size, your email. No account, no dashboard to check back on.

## The restock-checking problem

Mostly this exists because I wanted it. The pattern of refreshing a clothing brand’s product page, hoping a single sold-out size has restocked since the last check, is a small but real tax on attention: a background task your brain keeps re-running for no good reason. A daemon does this far better than a person: it doesn’t get bored, doesn’t forget, and doesn’t need to be reminded to check again tomorrow.

## How the watch list works

Each submission becomes an entry on a watch list that a scheduled job walks on a fixed interval, re-scraping every tracked product and diffing current size availability against the last known state for that specific size. The moment a watched size flips from sold-out to available, the notification fires on its own. There’s nothing left for the user to check, refresh, or remember. The diff is per size, not per product, so a restock of a different size on the same page doesn’t trigger a false alert.

## Brand-specific scraping, one shared notification path

The form runs on a PHP front end; a Python worker handles scraping and notification, triggered by the same scheduled job that walks the watch list. The scraping side is brand-specific by necessity (every retailer marks up size availability differently, so the parsers diverge site by site), but the notification path is shared across all of them. Adding support for a new brand means writing one new parser, not rebuilding the pipeline.

## Related project

[Series Watcher](https://yigitalpkorpe.com/projects/series-watcher/) uses the same scheduled-email pattern to deliver a weekly TV episode digest.

[Previous PageNote](https://yigitalpkorpe.com/projects/page-notes/) [Next Page Density Checker](https://yigitalpkorpe.com/projects/seo-tool/)

---

Canonical HTML: https://yigitalpkorpe.com/projects/monitor/

Site map: https://yigitalpkorpe.com/sitemap.xml · Summary for LLMs: https://yigitalpkorpe.com/llms.txt · Agent instructions: https://yigitalpkorpe.com/agents.md · All endpoints: https://yigitalpkorpe.com/agents/