Cross-Border E-Commerce Autopilot

Problem

Cross-border e-commerce decisions are hard for individual sellers who lack a registered legal entity: platform rules, payment channels, customs, taxes, sourcing, and logistics are scattered, and gut feelings often understate fees or overstate margin.

How the skill works

It breaks the decision into layers:
- Business framework definition: confirm export/import direction, target market, platform, budget, time, and risk tolerance.
- Data-driven comparison: use scripts/platform_fee_calculator.py, scripts/fetch_realtime_pricing.py, and scripts/logistics_calculator.py to compare platform fees, supplier cost, retail price, exchange rates, and direct-mail vs. overseas-warehouse logistics.
- Six-dimension analysis: cover compliance, product selection, logistics, finance, operations, and after-sales, with explicit checks for individual-entity constraints on platform onboarding, payment, customs, and tax.
- Reports and monitoring: generate decision, product-analysis, and logistics-comparison reports, then track price, sales, FX, logistics, inventory, and policy changes with portfolio_manager.py and market_monitor.py.

Fit and cautions

It is best for individual sellers without a legal entity in early validation and product testing. If you need brand registration, Temu full-service onboarding, exceed individual settlement limits, or require export tax rebates, design a proper entity and compliance path separately. Script outputs depend on inputs and external data; verify fees, tax rates, and platform rules against official sources.