SupplyPing - Automated Supplier Price Change Monitor for Small E-Commerce Sellers
Small e-commerce sellers manually check supplier portals every week to catch price changes that silently kill their margins — some find out only when they are already selling at a loss. SupplyPing monitors your supplier portals via browser automation, detects price and stock changes, and texts you before your margin goes negative.
Difficulty
intermediate
Category
E-Commerce
Market Demand
High
Revenue Score
7/10
Platform
Web App
Vibe Code Friendly
No
Hackathon Score
6/10
What is it?
Shopify sellers sourcing from Alibaba, AliExpress, or dozens of niche wholesale portals have zero automated way to know when their cost of goods changes — and a 15% supplier price bump on their top SKU can turn a profitable month into a loss before they notice. SupplyPing uses Playwright-based browser automation to log into supplier portals on a schedule, scrape product prices and stock levels, diff against stored baseline, and fire SMS or Slack alerts the moment a threshold is breached. Sellers configure their target margin per SKU, and SupplyPing calculates new recommended retail price automatically. Buildable in 2 weeks because Playwright handles authenticated portal scraping reliably, Supabase handles the price history timeseries, and Twilio SMS is a one-hour integration.
Why now?
The April 2026 tariff volatility and global supply chain instability have made supplier cost monitoring existential for thin-margin e-commerce sellers — and Playwright's authenticated scraping is now stable enough to maintain reliably.
- ▸Playwright-based portal scraper that authenticates and pulls prices on configurable schedules (hourly to daily)
- ▸Price change diff engine with per-SKU margin threshold alerts via SMS and Slack
- ▸Price history chart per SKU with 90-day trend line and supplier comparison view
- ▸Recommended retail price calculator that auto-suggests new Shopify price when cost changes
Target Audience
Shopify and WooCommerce sellers sourcing from 3-20 suppliers — estimated 2M+ such stores globally with margins thin enough to need this daily.
Example Use Case
A Shopify dropshipper with 80 AliExpress SKUs wakes up to a SupplyPing SMS saying three products spiked 18% in cost, clicks the Slack link, sees the recommended new retail price, updates Shopify pricing in two clicks, and saves their monthly margin before any customer orders the now-unprofitable SKUs.
User Stories
- ▸As a Shopify dropshipper, I want an SMS alert when my supplier raises prices above my margin threshold, so that I can reprice before selling at a loss. As an e-commerce seller, I want a 90-day price history chart per SKU, so that I can identify which suppliers are most volatile and negotiate better terms.
- ▸As a multi-supplier seller, I want all my portal prices in one dashboard, so that I stop logging into 8 different sites every Monday morning.
Acceptance Criteria
Scraper: done when AliExpress scraper returns correct prices for 20 SKUs authenticated with test credentials. Alert: done when SMS and Slack fire within 60 seconds of a threshold breach detected in diff engine. Price History: done when 90-day chart loads for any SKU with correct timestamps. Billing Gate: done when trial expires and scrape jobs pause until Stripe payment confirmed.
Is it worth building?
$29/month x 100 sellers = $2,900 MRR at month 3. $79/month x 50 power sellers = $3,950 additional. Math: 3% conversion from r/ecommerce and Shopify App Store listing traffic.
Unit Economics
CAC: ~$15 via Reddit outreach and Shopify App Store listing fee amortized. LTV: $696 (24 months at $29/month). Payback: under 1 month. Gross margin: 88%.
Business Model
$29/month for up to 50 SKUs, $79/month for 500 SKUs
Monetization Path
14-day free trial monitoring 5 SKUs. Upgrade to paid for more SKUs and SMS alerts.
Revenue Timeline
First dollar: week 2 via beta conversion. $1k MRR: month 2. $5k MRR: month 6 after Shopify App Store listing.
Estimated Monthly Cost
Playwright on Fly.io (2 workers): $30, Supabase: $25, Twilio SMS: $15 at launch volume, Vercel: $20, Stripe fees: $15. Total: ~$105/month.
Profit Potential
Full-time viable at $5k MRR with 120 paying sellers. Low churn because margin protection is existential.
Scalability
High — Shopify app listing, WooCommerce plugin, Amazon seller expansion, and white-label for 3PL providers.
Success Metrics
Week 1: 20 beta sellers with portals configured. Month 1: 40 paying sellers. Month 3: less than 8% monthly churn.
Launch & Validation Plan
Post in r/dropship and r/ecommerce asking 'How do you track supplier price changes?' — recruit 10 beta testers before writing code.
Customer Acquisition Strategy
First customer: DM 20 active sellers in r/shopify and r/dropship offering free 60-day beta with direct Slack access to founder for portal setup help. Ongoing: Shopify App Store listing, r/ecommerce, r/dropship, YouTube tutorials on margin protection, ProductHunt launch.
What's the competition?
Competition Level
Low
Similar Products
Prisync (retail price tracking, not supplier cost), Kimonix (Shopify analytics, no supplier scraping), no direct competitor for authenticated supplier portal monitoring — gap is authenticated cost-side tracking.
Competitive Advantage
Portal-agnostic scraping with seller-configured credentials means no supplier API partnership needed — works on any portal a human can log into.
Regulatory Risks
Low-medium. Scraping terms of service vary per supplier portal. Frame this as personal data access (user provides own credentials) to stay within ToS. GDPR: supplier credentials encrypted at rest.
What's the roadmap?
Feature Roadmap
V1 (launch): AliExpress and Alibaba scrapers, SMS and Slack alerts, price history dashboard. V2 (month 2-3): Shopify price auto-sync, 10 more portal adapters, stock-out alerts. V3 (month 4+): Shopify App Store listing, Amazon Seller Central integration, multi-user team accounts.
Milestone Plan
Phase 1 (Week 1-2): Playwright scraper, diff engine, Supabase schema, SMS alert working end-to-end. Phase 2 (Week 3-4): Next.js dashboard live, Stripe billing, 10 beta sellers configured. Phase 3 (Month 2): 40 paying sellers, Alibaba adapter shipped, ProductHunt launch.
How do you build it?
Tech Stack
Node.js, Playwright for portal scraping, Supabase for price history, Next.js for dashboard, Twilio for SMS alerts, Stripe for billing — build with Cursor for scraping engine, v0 for dashboard
Suggested Frameworks
Playwright, node-cron, Supabase
Time to Ship
2 weeks
Required Skills
Playwright browser automation, Supabase timeseries queries, Twilio SMS, node-cron scheduling.
Resources
Playwright docs, Supabase docs, Twilio SMS quickstart, Shopify Partner program.
MVP Scope
scraper/runner.ts (Playwright core), scraper/portals/aliexpress.ts, scraper/portals/alibaba.ts, scraper/diff-engine.ts, api/alert.ts (Twilio), pages/dashboard.tsx, pages/skus.tsx, components/PriceChart.tsx, supabase/schema.sql, cron/schedule.ts.
Core User Journey
Add supplier portal credentials -> configure SKUs and margin thresholds -> receive first price alert via SMS -> update Shopify price -> upgrade to paid.
Architecture Pattern
node-cron fires scrape job -> Playwright worker authenticates portal -> price data extracted -> diff engine compares to Supabase baseline -> if threshold breached, Twilio SMS and Slack webhook fire -> price history stored in Supabase -> Next.js dashboard reads history for charts.
Data Model
User has many Suppliers. Supplier has many SKUs. SKU has many PriceSnapshots (price, stock, timestamp). SKU has one AlertConfig (margin threshold, alert channel).
Integration Points
Playwright for portal scraping, Supabase for price history timeseries, Twilio for SMS alerts, Slack Webhooks for team alerts, Stripe for billing, Shopify Admin API for optional price push-back, Vercel for hosting.
V1 Scope Boundaries
V1 excludes: Shopify automatic price sync, Amazon seller support, mobile app, multi-user team accounts, API access, white-label.
Success Definition
A seller configures SupplyPing for their top 20 SKUs without founder help, receives a real price change alert within 48 hours, acts on it, and renews after the trial ends.
Challenges
Supplier portals change their HTML structure without warning, breaking scrapers — this is a continuous maintenance burden, not a one-time build problem, and sellers will churn the moment their key portal breaks.
Avoid These Pitfalls
Do not try to support 20 supplier portals at launch — ship with AliExpress and Alibaba only, then add portals on demand. Do not store supplier passwords in plaintext — encrypt with user-specific key using AES-256. Finding first 10 paying sellers takes longer than building the scraper — budget 3x more time for seller outreach than code.
Security Requirements
Supabase Auth with Google OAuth. Supplier credentials encrypted AES-256 before DB insert. RLS on all user data tables. Rate limit scrape API at 5 req/min per user. GDPR: full data deletion including encrypted credentials on account close.
Infrastructure Plan
Vercel for Next.js dashboard, Fly.io for Playwright scraper workers (2 instances), Supabase for Postgres and auth, Sentry for scraper error tracking, GitHub Actions for CI, dev/staging/prod environments.
Performance Targets
Scrape job completes 50 SKUs in under 3 minutes per supplier. Dashboard price chart loads in under 2 seconds. SMS alert fires within 60 seconds of diff detection. Support 200 concurrent sellers at launch without scaling.
Go-Live Checklist
- ☐Playwright scraper tested on live AliExpress with test account
- ☐Stripe trial and billing tested end-to-end
- ☐Sentry live on Fly.io workers
- ☐Custom domain with SSL
- ☐Privacy policy and credentials security notice published
- ☐5 beta sellers signed off
- ☐Fly.io rollback documented
- ☐ProductHunt and Reddit launch posts drafted.
How to build it, step by step
1. Run 'npx create-next-app supplying' and scaffold Node scraper in /scraper directory. 2. Install Playwright and write aliexpress.ts scraper that authenticates with stored credentials and returns price array. 3. Build diff-engine.ts that compares new prices to Supabase baseline and returns changed SKUs. 4. Set up Supabase schema: suppliers, skus, price_snapshots, alert_configs tables. 5. Integrate Twilio SMS in api/alert.ts triggered when diff exceeds margin threshold. 6. Add Slack webhook alert alongside SMS. 7. Build node-cron scheduler in cron/schedule.ts running every 6 hours per supplier. 8. Build Next.js dashboard with PriceChart using recharts for 90-day history. 9. Encrypt supplier credentials using AES-256 before storing in Supabase. 10. Add Stripe billing, deploy Playwright workers to Fly.io, deploy Next.js to Vercel.
Generated
April 1, 2026
Model
claude-sonnet-4-6