Shipping Policy Extractor

Store Positioning

Store title: Shipping Policy Extractor

Short description: Extract shipping policy details from supplied policy pages or text into structured fields for audits, comparison, and support documentation.

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

SEO description: Extract shipping policy details from supplied policy pages or text into structured fields for audits, comparison, and support documentation. 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: shipping, 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. Shipping 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. Shipping 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. Shipping 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. Shipping 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. Shipping 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 Shipping Policy controls on a capped public sample
• Find high-priority Shipping Policy issues before release
• Validate Shipping Policy evidence from supplied pages
• Prioritize Shipping Policy fixes with severity and proof
• Export Shipping Policy QA rows for client review Extract structured shipping policy facts from supplied text or HTML.

What It Does

Extracts delivery windows, processing times, free-shipping thresholds, carrier mentions, regions, restrictions, international signals, evidence, and confidence.

Inputs

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

• policyUrls
• policyText
• html
• maxPages
• extractThresholds
• extractRegions
• includeEvidenceSnippets
• timeoutMs
• maxChargeUsd

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

Outputs

Dataset rows contain:

• sourceUrl
• policySection
• shippingRegion
• deliveryWindow
• processingTime
• freeShippingThreshold
• carrierMention
• restriction
• internationalShipping
• 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 Shipping Policy Extractor issues
• Find Shipping Policy Extractor problems across a website
• Generate a technical Shipping Policy Extractor report

Safe use

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