<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Benjamin Garcia</title>
    <description>The latest articles on DEV Community by Benjamin Garcia (@benjamingarciamtl).</description>
    <link>https://dev.to/benjamingarciamtl</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4254082%2F49f3e9e9-eddf-4106-8409-52345d1dc179.png</url>
      <title>DEV Community: Benjamin Garcia</title>
      <link>https://dev.to/benjamingarciamtl</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/benjamingarciamtl"/>
    <language>en</language>
    <item>
      <title>A price tracker for any online store: get an alert when the price drops</title>
      <dc:creator>Benjamin Garcia</dc:creator>
      <pubDate>Thu, 19 Nov 2026 15:11:27 +0000</pubDate>
      <link>https://dev.to/benjamingarciamtl/a-price-tracker-for-any-online-store-get-an-alert-when-the-price-drops-4ln3</link>
      <guid>https://dev.to/benjamingarciamtl/a-price-tracker-for-any-online-store-get-an-alert-when-the-price-drops-4ln3</guid>
      <description>&lt;p&gt;&lt;em&gt;This guide first appeared on &lt;a href="https://usewrit.app/blog/price-tracker-any-store/" rel="noopener noreferrer"&gt;usewrit.app&lt;/a&gt;. I build Writ, the tool used in the steps below.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Amazon has a whole ecosystem of price-history trackers. Most other stores have none. If the sofa is on Wayfair, the TV on Best Buy, the shoes on Nike, the listing on eBay or the part in a small specialist shop, you are left refreshing the page.&lt;/p&gt;

&lt;p&gt;This guide shows how to track the price of a product on any online store and get an alert when it drops, with the same setup whatever the store.&lt;/p&gt;

&lt;h2&gt;
  
  
  How a price tracker works
&lt;/h2&gt;

&lt;p&gt;Every price tracker does the same three things. It reads the price from the product page, it compares the reading with the previous one, and it tells you when a condition is met: the price drops, falls below a target, or the item comes back in stock.&lt;/p&gt;

&lt;p&gt;Store-specific trackers do this for one site, using what they know about its pages. A general tracker does it for any page by letting you point at the price.&lt;/p&gt;

&lt;h2&gt;
  
  
  Track a price on any store with Writ
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Paste the product URL, from any store.&lt;/li&gt;
&lt;li&gt;Point at the price (and, if you like, the stock status next to it).&lt;/li&gt;
&lt;li&gt;Set your condition: any change, or a price below the threshold you would pay.&lt;/li&gt;
&lt;li&gt;Pick where the alert goes: email, SMS, WhatsApp, Signal, Pushover or a webhook.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Writ reads the price on your schedule, keeps every reading with the value before and after, and alerts you only when your condition matches. On the Free plan a product page can be checked every 5 minutes, or every 15 minutes when it needs a browser, and you start with 1,000 free credits, no card.&lt;/p&gt;

&lt;p&gt;The steps are the same for Walmart, Wayfair, Best Buy, eBay, Macy's, Nike, Etsy or a one-person shop: what changes from store to store is only how the price reaches the page.&lt;/p&gt;

&lt;h2&gt;
  
  
  Walmart, Wayfair, Best Buy, eBay and other stores
&lt;/h2&gt;

&lt;p&gt;Store pages fall into three kinds, and knowing which one you face saves credits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The price is in the page.&lt;/strong&gt; The cheapest case: a check without a browser reads it, for 0.5 credits in the cloud.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The price appears after scripts run.&lt;/strong&gt; Common on large retail sites. The page needs a browser check (5 credits in the cloud), which runs less often.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The price depends on you.&lt;/strong&gt; Member prices, a store or ZIP code chosen in your account, a business account. Attach a &lt;a href="https://usewrit.app/product/personas/" rel="noopener noreferrer"&gt;persona&lt;/a&gt; so Writ checks the page as you, signed in, and sees the price you would pay.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;On your own computer with Writ Desktop, checks of every kind cost 0 credits while it is on and connected. In the cloud they keep running when your computer is off.&lt;/p&gt;

&lt;p&gt;If you are writing your own tracker instead, the same split applies: &lt;code&gt;requests&lt;/code&gt; plus a selector covers the first kind, the second needs a headless browser, and the third needs a signed-in session you keep alive yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  Price drops, targets and back-in-stock alerts
&lt;/h2&gt;

&lt;p&gt;Most people want one of three alerts. "Tell me when it changes" is the simplest and the noisiest. "Tell me when it is under my target" is usually what you mean. "Tell me when it is back in stock" watches the availability label instead of the number. Watch both on the same product page and you hear about the drop and the restock.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep a price history
&lt;/h2&gt;

&lt;p&gt;Every reading lands in a dataset with the time and the value before and after. Read it in the &lt;a href="https://usewrit.app/product/data/" rel="noopener noreferrer"&gt;Data explorer&lt;/a&gt;, export it, or call it from your own code. After a few weeks you know whether a "sale" is a real low or the usual price with a crossed-out number above it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tracking many products, or a whole category
&lt;/h2&gt;

&lt;p&gt;For a handful of products, one monitor each is enough. For a catalog, use an API that returns many products in one call. The &lt;a href="https://usewrit.app/marketplace/" rel="noopener noreferrer"&gt;Writ marketplace&lt;/a&gt; has ready-made ones, such as &lt;a href="https://usewrit.app/marketplace/walmart-canada-products-offers/" rel="noopener noreferrer"&gt;Walmart Canada products and offers&lt;/a&gt; or &lt;a href="https://usewrit.app/marketplace/camelcamelcamel-amazon-price-tracker/" rel="noopener noreferrer"&gt;Amazon price history from camelcamelcamel&lt;/a&gt;; for any other store, &lt;a href="https://usewrit.app/blog/turn-any-website-into-an-api/" rel="noopener noreferrer"&gt;turn the site into an API&lt;/a&gt; once and schedule it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do something with the drop
&lt;/h2&gt;

&lt;p&gt;An alert is a start. A price change in Writ is a trigger, so it can also post to your team's channel through a webhook, update a spreadsheet, or start a workflow, such as re-pricing your own listing when a competitor moves. Conditions, a cooldown and an optional approval step keep it inside limits you set.&lt;/p&gt;

&lt;h2&gt;
  
  
  Be a polite visitor
&lt;/h2&gt;

&lt;p&gt;A price rarely needs checking more than a few times an hour; once a day is plenty for most purchases. Watch pages you are allowed to access, use your own account where a sign-in is needed, and follow each store's terms.&lt;/p&gt;

</description>
      <category>automation</category>
      <category>ecommerce</category>
      <category>productivity</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to monitor a website for changes and get an alert</title>
      <dc:creator>Benjamin Garcia</dc:creator>
      <pubDate>Thu, 19 Nov 2026 15:11:00 +0000</pubDate>
      <link>https://dev.to/benjamingarciamtl/how-to-monitor-a-website-for-changes-and-get-an-alert-5b25</link>
      <guid>https://dev.to/benjamingarciamtl/how-to-monitor-a-website-for-changes-and-get-an-alert-5b25</guid>
      <description>&lt;p&gt;&lt;em&gt;This guide first appeared on &lt;a href="https://usewrit.app/blog/monitor-website-changes/" rel="noopener noreferrer"&gt;usewrit.app&lt;/a&gt;. I build Writ, the tool in the last part; the first three methods need nothing from us.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A supplier updates a price list. A competitor quietly changes its pricing page. A school publishes its admission dates, a status page flips to "degraded", a job board posts the role you were waiting for. In every case the information was public, and in every case you found out late, because nobody tells you when a web page changes.&lt;/p&gt;

&lt;p&gt;This guide covers the ways to monitor a website for changes, what each one costs you in time, and how to set up an alert that fires only when the part you care about moves.&lt;/p&gt;

&lt;h2&gt;
  
  
  First, decide what "changed" means
&lt;/h2&gt;

&lt;p&gt;Almost every page changes on every load: a date in the footer, a rotating banner, a visitor counter, an ad. If you compare the whole page, you get an alert every time and you stop reading them within a week. Good change monitoring starts by narrowing the target to the part that matters:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;An element (a CSS selector):&lt;/strong&gt; the price, the status label, the table of dates, one paragraph of the terms.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A visual zone:&lt;/strong&gt; a region of the rendered page, compared as pixels, which catches layout and image changes that text misses.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A screenshot region:&lt;/strong&gt; the same idea for pages where the content is drawn rather than written, such as a chart or a map.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then decide what counts as a change worth an alert: any difference, a number crossing a threshold, a word appearing ("in stock", "open", "approved"), or a word disappearing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four ways to monitor a web page for changes
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Check it by hand
&lt;/h3&gt;

&lt;p&gt;A bookmark and a calendar reminder. It costs nothing and works for one page you visit weekly anyway. It fails the moment the timing matters, because you see the change when you look, not when it happens.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. A browser extension
&lt;/h3&gt;

&lt;p&gt;Extensions reload a tab on a timer and highlight differences. They are quick to set up, but they only run while your browser is open, on that one computer, and they compare what the page shows you, banners and all.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. A script on a schedule
&lt;/h3&gt;

&lt;p&gt;Fetch the page, extract the element, compare it with the last value, send a message. A developer can write this in twenty lines:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;pathlib&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;requests&lt;/span&gt;
&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;bs4&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;BeautifulSoup&lt;/span&gt;

&lt;span class="no"&gt;URL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="no"&gt;SELECTOR&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"https://example.com/pricing"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;".plan-pro .price"&lt;/span&gt;
&lt;span class="n"&gt;state&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pathlib&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Path&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"last.json"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="n"&gt;html&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;requests&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="no"&gt;URL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;timeout&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;20&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;text&lt;/span&gt;
&lt;span class="n"&gt;now&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;BeautifulSoup&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;html&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"html.parser"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;select_one&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="no"&gt;SELECTOR&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get_text&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;strip&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;True&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;before&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;loads&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;state&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;read_text&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;state&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;exists&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;else&lt;/span&gt; &lt;span class="kc"&gt;None&lt;/span&gt;

&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;before&lt;/span&gt; &lt;span class="k"&gt;is&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="kc"&gt;None&lt;/span&gt; &lt;span class="ow"&gt;and&lt;/span&gt; &lt;span class="n"&gt;now&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="n"&gt;before&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;requests&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;post&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="no"&gt;WEBHOOK_URL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"text"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"{URL} changed: {before} -&amp;gt; {now}"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;state&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;write_text&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;dumps&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;now&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The script is the easy part. The work is everything around it: a server that stays on, pages that only render their content after JavaScript runs (the fetch above returns an empty shell), a selector that breaks the day the site is redesigned and fails silently, pages behind a sign-in, and a log of what changed when. Multiply by the number of pages you watch.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. A monitoring service
&lt;/h3&gt;

&lt;p&gt;A service keeps the baseline, runs the checks on its own servers, renders JavaScript when needed and sends the alert. This is what &lt;a href="https://usewrit.app/product/monitors/" rel="noopener noreferrer"&gt;Writ Monitors&lt;/a&gt; do, with two differences that matter in practice: a change can run an action, not only send a message, and a selector that breaks is repaired instead of going quiet.&lt;/p&gt;

&lt;h2&gt;
  
  
  Set up a change alert in Writ, step by step
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Paste the URL of the page you want to watch.&lt;/li&gt;
&lt;li&gt;Pick the target: point at the element, or draw the visual zone or screenshot region.&lt;/li&gt;
&lt;li&gt;Set the condition: any change, a value above or below a threshold, or text that appears or disappears.&lt;/li&gt;
&lt;li&gt;Choose the cadence: as often as your plan allows, or as rarely as once a day.&lt;/li&gt;
&lt;li&gt;Choose the response: an alert (email, SMS, WhatsApp, Signal, Pushover), a webhook to your own tools, or a workflow that runs on the change.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Writ stores a baseline, checks the page on your schedule and records each change with the value before and after, so you also get a history of the page, not only a notification.&lt;/p&gt;

&lt;p&gt;The free &lt;a href="https://usewrit.app/tools/page-change-monitor/" rel="noopener noreferrer"&gt;page change monitor tool&lt;/a&gt; shows what a monitor would track on any page before you sign up.&lt;/p&gt;

&lt;h2&gt;
  
  
  How often to check, and what it costs
&lt;/h2&gt;

&lt;p&gt;On the Free plan a page can be checked every 5 minutes without a browser, and every 15 minutes when it needs one; higher plans go down to every 10 seconds. In Writ Cloud a check without a browser costs 0.5 credits and a browser check 5 credits; a check that could not complete costs nothing. Checks that run on your own computer with Writ Desktop cost 0 credits. New accounts start with 1,000 free credits, no card.&lt;/p&gt;

&lt;p&gt;Faster is not always better. A price or a status page rarely needs more than one check every few minutes; a terms page or a docs page is fine once a day. Match the cadence to how fast you would act on the alert, and respect the site's rate limits.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pages built by JavaScript, and pages behind a sign-in
&lt;/h2&gt;

&lt;p&gt;Many modern pages send an empty shell and build the content in the browser. A plain fetch sees nothing, so the check needs a real browser to render the page first: choose a browser check when the content is not in the page response.&lt;/p&gt;

&lt;p&gt;For a page inside your own account (a supplier portal, an order status, a dashboard), attach a &lt;a href="https://usewrit.app/product/personas/" rel="noopener noreferrer"&gt;persona&lt;/a&gt;: Writ uses your signed-in session to reach the page, with your credentials resolved privately when the check runs.&lt;/p&gt;

&lt;h2&gt;
  
  
  When the site is redesigned
&lt;/h2&gt;

&lt;p&gt;This is where home-made monitors die. The selector no longer matches, the script reads nothing, and the alerts stop without anyone noticing. Writ re-anchors the target as the page shifts, and when a check still fails, auto-repair rebuilds the broken step and tests it on the live page. Repairs are free.&lt;/p&gt;

&lt;h2&gt;
  
  
  Go further than an alert
&lt;/h2&gt;

&lt;p&gt;An alert still needs a person to do the next thing. In Writ, a change is a trigger: it can send the new value to a webhook, add a row to your data, or run a workflow you recorded, such as filling in a registration form the moment a closed page opens. Conditions, a cooldown and an optional approval step keep the action inside limits you set. Two common setups: &lt;a href="https://usewrit.app/solutions/use-case/waitlist-registration/" rel="noopener noreferrer"&gt;register when a page opens&lt;/a&gt; and &lt;a href="https://usewrit.app/solutions/use-case/competitor-monitoring/" rel="noopener noreferrer"&gt;competitor monitoring&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ask your AI agent to watch it
&lt;/h2&gt;

&lt;p&gt;If you use Claude, ChatGPT, Cursor or another MCP client, connect &lt;a href="https://usewrit.app/mcp/" rel="noopener noreferrer"&gt;Writ's MCP server&lt;/a&gt; and ask in plain words: "tell me when the Pro price on this page changes". The agent creates the monitor and wires the alert; the checks keep running after the chat is closed.&lt;/p&gt;

&lt;h2&gt;
  
  
  What people watch
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Competitor pricing, plans and feature pages.&lt;/li&gt;
&lt;li&gt;Stock status on a product page.&lt;/li&gt;
&lt;li&gt;Status pages, changelogs and API docs of the tools you depend on.&lt;/li&gt;
&lt;li&gt;Admissions, grants, tenders and public notices with a deadline.&lt;/li&gt;
&lt;li&gt;Job boards and careers pages for one role or one company.&lt;/li&gt;
&lt;li&gt;Terms of service and privacy policies of your vendors.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Watch pages you are allowed to access, and follow each site's terms.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>automation</category>
      <category>python</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
