Ecommerce Return Policy Extractor

Pull the return-policy details shoppers and ecommerce operators actually care about.

Who Uses It

Ecommerce operators, CX teams, marketplace sellers, agencies, and policy analysts.

Why It Is Useful

This actor does not save a generic web-scrape dump. It saves a compact dataset shaped around one business job, so the output is easier to review, export, and plug into research workflows.

Input

• startUrls - Public pages to inspect.
• logLines - Pasted snippets for fast tests or sources that do not need crawling.
• maxPagesPerStartUrl - Same-domain pages to inspect from each URL.
• maxResults - Maximum clean rows to save, capped at 20.
• proxyConfiguration - Optional Apify proxy settings.

Output Fields

• returnRule - Main return-policy rule in plain language.
• returnWindow - Detected return window.
• refundChannel - Refund method such as original payment, store credit, exchange, or refund mention.
• returnShippingParty - Who appears responsible for return shipping.
• exclusion - Policy exception such as final sale, restocking fee, or receipt requirement.
• customerImpact - Plain-English impact on the shopper.
• policyUrl - Return policy source URL.

Example Output

{
    "returnRule": "Returns accepted within 30 days with receipt.",
    "returnWindow": "30 days",
    "refundChannel": "original payment",
    "returnShippingParty": "customer pays",
    "exclusion": "final sale items excluded",
    "customerImpact": "Customer must keep receipt and may pay shipping.",
    "policyUrl": "https://example.com/returns"
}

Use Cases

• Compare return windows across stores.
• Find shipping responsibility and refund method quickly.
• Audit policy exceptions such as final sale or restocking fees.

Limits

The actor works best with public pages or focused pasted snippets. Login walls, CAPTCHA, heavy anti-bot protection, and very noisy pages can reduce result quality.

Pricing

Recommended pricing is paid per saved dataset item, so users pay for useful rows instead of empty page visits.