Import Compliance

Marketplace Import & Scraping Policy

FairClose uses compliance-first scraping guardrails: robots.txt policy checks, rotating user-agents/proxy context, request throttling, and mandatory manual review before publishing imported content.

Compliance Rules

• Robots.txt is checked per marketplace and route. Disallowed paths are blocked.

• Source attribution is preserved on imported records for auditability.

• Imported data remains in review flow until a seller manually confirms and publishes.

• Request throttling is enforced to prevent abusive scraping patterns.

Rotation & Reliability

• User-agent rotation is applied across supported marketplace requests.

• Optional proxy pool rotation can be configured via environment (`SCRAPE_PROXY_POOL`).

• Scheduled jobs refresh marketplace robots policies to keep compliance rules current.

• When a source marketplace blocks requests, FairClose returns safe warnings instead of crashing flows.

Supported No-API Sources

Current supported no-API import search sources:

• eBay

• Mercari

• Poshmark

Marketplace health can vary by anti-bot controls and policy changes. See Marketplace Availability for status guidance.

Best Practices

• Keep imports focused and specific (exact product URLs or targeted keywords).

• Avoid bulk repeated retries when a source is temporarily blocked.

• Validate imported title/price/condition before publishing.

• Retain source context in listing notes for moderation and trust workflows.