B
Overseas Direct Purchase Customs Auto-Settlement Helper
3.80
Derivation Chain
Step 1
Surge in interest in Rakuten overseas direct purchases
→
Step 2
Confusion over customs duty and VAT calculations for 50-something overseas buyers
→
Step 3
Annual cumulative customs management based on purchase history
Problem
When a 50-something office worker directly purchases health foods and hobby items from overseas malls like Rakuten, they must search for customs duties, VAT, and list clearance thresholds ($150/$200) each time, and have no way to track whether their annual cumulative purchases exceed the duty-free limit, leading to unexpected tax bills. A single mistake can result in 30,000-100,000 KRW (~$22.50-75) in additional taxes and 1-2 weeks of customs delays.
Solution
By registering purchase history from overseas malls (email receipts or manual entry), it automatically calculates customs duty and VAT by item, and displays the remaining annual duty-free limit in real time. It also automatically determines list clearance vs. general clearance and provides advance notifications of estimated tax amounts.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
N=.15 U=.20 M=.15 R=.30 V=.20
Feasibility (70%)
Data Availability
20.6/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (57/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Frontend [medium]
Backend [medium]
Data Pipeline [low]