Return Policy Extractor

Store Positioning

Store title: Return Policy Extractor

Short description: Extract return-policy rules from supplied policy pages or text into structured rows for audits, support documentation, and competitive comparison.

SEO title: Return Policy Extractor — technical SEO, web, and domain audit

SEO description: Extract return-policy rules from supplied policy pages or text into structured rows for audits, support documentation, and competitive comparison. Use it to find crawlability, indexability, security, metadata, and page-quality issues with evidence-backed rows and audit reports.

Categories: SEO_TOOLS, DEVELOPER_TOOLS, ECOMMERCE

Keywords: return, policy, extractor, structured data, web/domain audit

Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: W1 — Web/domain audit
• Primary event: page-audited at $0.00490 base
• Default max charge: $10.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.00500, GOLD $0.00400. Return Policy Extractor: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• page-audited: base $0.00490, GOLD $0.00392. Return Policy Extractor: charged when page audited is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• rule-parsed: base $0.00372, GOLD $0.00298. Return Policy Extractor: charged when rule parsed is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• finding-emitted: base $0.00372, GOLD $0.00298. Return Policy Extractor: charged when finding emitted is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• audit-report-generated: base $0.05000, GOLD $0.04000. Return Policy Extractor: charged when audit report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

The actor accepts actor-start before work, accepts the primary event before each dataset row, and accepts the configured report event before writing report files. If maxChargeUsd or the live PPE limit blocks a charge, the corresponding row or report is not written.

Public Task Concepts

• Audit Return Policy controls on a capped public sample
• Find high-priority Return Policy issues before release
• Validate Return Policy evidence from supplied pages
• Prioritize Return Policy fixes with severity and proof
• Export Return Policy QA rows for client review Extract structured return policy facts from supplied text or HTML.

What It Does

Extracts return windows, refund method, exchange signals, restocking fees, return-shipping responsibility, condition requirements, exclusions, evidence, and confidence.

Inputs

This actor exposes these input fields in .actor/input_schema.json:

• policyUrls
• policyText
• html
• maxPages
• extractFees
• extractExclusions
• includeEvidenceSnippets
• timeoutMs
• maxChargeUsd

The exact default fetches and extracts a single bounded public Apple Returns & Refunds policy page, verified reachable at 2026-07-12T05:48:00Z.

Outputs

Dataset rows contain:

• sourceUrl
• policySection
• returnWindowDays
• refundMethod
• exchangeAllowed
• restockingFee
• returnShippingResponsibility
• conditionRequirement
• exclusion
• evidenceSnippet
• confidence

Sample outputs in examples/output.sample.json and output.sample.json were generated from examples/input.tiny.json through actor logic.

Reports

After the configured report charge is accepted, the actor writes its Markdown, JSON, or CSV reports to the key-value store. A rejected report charge leaves those files unwritten.

Public Task Concepts

• Audit public URLs for Return Policy Extractor issues
• Find Return Policy Extractor problems across a website
• Generate a technical Return Policy Extractor report

Safe use

Use small capped runs first. Network paths are bounded; review output quality and costs before increasing limits.