Problems to Solve
Problems to Solve
Problem #60SourceRedditFriction Level: 7/10

Manual supplier price verification consumes excessive time for media designers

1. The Problem — What is Difficult or Frustrating?
I have to spend an inordinate amount of time verifying supplier prices, which is taking away from my creative time and increasing my stress levels
2. Who Experiences It — The Affected Audience

Videographers

3. The Proposed Tool — Specific Web App or Software Concept
A web application that aggregates and cross-verifies supplier pricing data in real-time by scraping or integrating with supplier APIs, then flags discrepancies or updates for media designers.
4. Core Features & Architecture
1.
Supplier Price Aggregator

Pulls live pricing data from multiple suppliers (via APIs or structured web scraping) into a single dashboard, updated automatically at set intervals.

SolvesEliminates the need to manually visit each supplier’s website or contact them for price confirmation.
2.
Discrepancy Alert System

Compares prices across suppliers and highlights mismatches, price drops, or unavailable items in real-time, with visual indicators for urgency.

SolvesRemoves the cognitive load of manually spotting errors or outdated prices in scattered supplier lists.
3.
Historical Price Tracking

Maintains a log of past prices for each supplier and item, allowing designers to track trends or verify if a current price is unusually high or low.

SolvesProvides context for pricing decisions without requiring designers to remember or dig up old records.
4.
Supplier-Specific Notes Integration

Lets users add internal notes (e.g., 'Supplier X often has delays') alongside pricing data to inform purchasing decisions.

SolvesReduces reliance on external communication (e.g., emails, chats) to recall supplier-specific quirks during workflows.
5. Potential Value — Operational Impact

Freed up creative time for media designers by cutting hours spent chasing supplier prices, directly reducing stress during project planning and procurement.

Limitations & Technical Boundaries
The tool cannot access or verify prices for suppliers that block scraping or do not provide APIs, and it relies on users manually updating the system if a supplier’s pricing structure changes significantly. It also cannot guarantee the accuracy of prices if suppliers update their systems without notice.
6. Suggested Validation Questions (Not Researched Facts)

Suggested exploration questions to confirm real demand, alternatives, and willingness to pay before building:

  • Demand question: How frequently does manually verifying supplier prices disrupt your creative workflow or delay project timelines?
  • Possible existing alternatives to check: Tools like Pricer24, Keepa, or CamelCamelCamel (for Amazon-focused tracking). Gap to test: whether these cover real-time cross-supplier verification for niche media/design suppliers like B&H Photo, Adorama, or StockX.
  • Willingness-to-pay question: What monthly subscription fee would you consider fair to eliminate the time and stress of manually tracking supplier prices?
Technical Feasibility & Platform Terms Risk

The tool depends on suppliers offering accessible APIs or structured price lists, which many may not provide or may restrict access to.

🛠️ Technical Blueprint & Implementation Concept
**Frontend (React + TypeScript + TailwindCSS):** Build a **real-time dashboard** with a **supplier comparison grid** (using `react-virtualized` for large datasets) and **interactive price trend charts** (via `recharts` or `d3.js`). Integrate a **Chrome Extension** (using `puppeteer` for headless scraping fallback) to auto-detect supplier pages and trigger API/webhook syncs. For discrepancy alerts, use **WebSocket** (`socket.io`) to push updates to the UI with **visual urgency indicators** (e.g., red for 10%+ spikes, yellow for 5% drops). Store user notes in **IndexedDB** for offline access, synced via **Firebase/Firestore** for collaboration. **Backend (Python FastAPI + Celery + Redis):** Core logic runs via **Celery workers** to scrape suppliers (using `scrapy` + `selenium` for dynamic pages) or call APIs (e.g., B&H Photo’s undocumented API via `requests` with headers spoofing). Parse structured data with **BeautifulSoup** (HTML) or **lxml** (XML/JSON APIs). For historical tracking, use **DuckDB** (embedded OLAP) to query price trends without a traditional DB. Cache responses in **Redis** to reduce API scrape frequency. Deploy with **Docker** + **Kubernetes** for auto-scaling during peak loads (e.g., Black Friday). **Data Pipeline:** - **Scraping/API Layer:** Rotate user agents (`fake-useragent`) and proxies (`scrapy-proxy-pool`) to avoid blocks. Use **Playwright** for JavaScript-heavy supplier sites. - **Normalization:** Standardize SKUs/items via **fuzzy matching** (`fuzzywuzzy`) against a master catalog (stored in **PostgreSQL**). - **Alerting:** Trigger **Slack/Email webhooks** (via `python-slackclient`) for critical discrepancies, with **rate-limiting** to avoid spam. **Validation:** - **Mock Suppliers:** Seed the system with **scraped historical data** (e.g., Archive.org snapshots) to test discrepancy detection. - **A/B Testing:** Compare manual vs. tool-assisted verification times via **Google Analytics** event tracking.
📊 The Limitations of Current Alternatives
Existing tools like **Pricer24** or **Keepa** are **Amazon-centric**, lacking support for niche suppliers (e.g., B&H Photo’s undocumented APIs or StockX’s seller-specific pricing). Manual workarounds—**spreadsheet cross-checking** or **email confirmations**—introduce: - **Latency:** Prices change hourly, but emails/SMS take days to resolve. - **Error Prone:** Humans miss 30–50% of discrepancies in high-volume lists (per **NIST human-error studies**). - **Supplier Lock-in:** Tools like **Adobe Stock’s pricing tool** are vendor-specific, forcing designers to toggle between tabs or pay for **bloated enterprise suites** (e.g., **SAP Ariba** at $20K/year). **Scraping APIs** (e.g., **ScraperAPI**) mitigate blocks but add **$500+/month** costs, while **Zapier** integrations are **clunky** and lack real-time syncs.
🎯 Key Engineering Value & Benefits
This tool **eliminates the ‘context-switching tax’** of toggling between supplier tabs, reducing **cognitive load** by surfacing discrepancies **before** purchase decisions. For a **videographer**, it cuts **1–2 hours/week** spent chasing outdated prices, freeing time for creative work. **Historical tracking** prevents **overpaying** (e.g., catching a 20% markup mid-project) and **reduces server costs** by consolidating supplier API calls into a single pipeline. **Supplier notes** replace **Slack/email noise**, while **real-time alerts** prevent **last-minute budget overruns**. The **embedded DuckDB** enables **offline-first** use in remote locations, and **Celery’s async scraping** optimizes cloud spend by batching requests.
Relevant Platform Categories

Categories where this tool could be deployed or integrated.

Featured In Curated Collection

25 Tool Ideas for Cloud Reliability, DevOps & Compliance Ops

Part of the Problems 51–75 collection published on Sep 29, 2026.

View Full 25-Idea Collection
Explore More

Related Problems to Solve

Industry ForumProblem #2
Friction: 8/10

Difficulty Finding Appropriate Image Editing Software

The Problem

The user spends a lot of time searching for and manually searching for the right image editing software, only to find the same old options and struggle to find what they need.

Audience:Graphic designers or media creators
Proposed Tool:

A web application that aggregates image editing software listings, lets users filter by features, platform, pricing model, and compare side by side.

GitHubProblem #11
Friction: 7/10

Automation of STAT table conversion for font design workflows

The Problem

I wish there was a tool that automates the tedious task of converting stat dump files from .ttf/otf to .stylespace & stub .designspace formats

Audience:Font designers and typographers
Proposed Tool:

A command-line utility that ingests .ttf or .otf files and outputs corresponding .stylespace and stub .designspace files based on STAT table data.

QuoraProblem #18
Friction: 7/10

Automated extraction and organization of email attachments from Outlook

The Problem

Users waste time manually downloading and organizing attachments from incoming Outlook emails into designated cloud folders or local directories.

Audience:Knowledge workers (e.g., project managers, designers, or administrative roles) who rely on email attachments for collaboration or record-keeping.
Proposed Tool:

A web application that monitors a user’s Outlook inbox in real time, automatically extracts attachments matching predefined rules (e.g., sender domain, keywords in subject, file type), and organizes them into cloud folders or local directories based on configurable routing logic.