shipping-page-generator
This Claude Code skill generates and optimizes shipping and delivery information pages for e-commerce businesses. Use it when creating or updating content about shipping policies, delivery timelines, shipping rates, tracking options, or cross-border logistics. The skill addresses domestic and international shipping scopes, regulatory compliance requirements, and ensures delivery terms are structured for AI shopping agent discoverability, critical as AI tools increasingly influence consumer purchasing decisions.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/shipping-page-generator && cp -r /tmp/shipping-page-generator/skills/pages/legal/shipping ~/.claude/skills/shipping-page-generatorSKILL.md
# Pages: Shipping / Delivery Guides shipping and delivery information page content for e-commerce, covering domestic and cross-border logistics, regulatory compliance, and AI-era discoverability. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment Identify: 1. **Shipping scope**: Domestic only, cross-border, or global — see §Shipping Scope 2. **Product type**: Physical goods (standard), digital/physical bundles, print-on-demand, dropshipping 3. **Carriers & methods**: Standard, express, overnight; carrier names; real-time vs flat-rate 4. **Regulatory exposure**: EU (2026 customs changes, AI Act), cross-border compliance 5. **AI discoverability**: Can delivery terms be parsed by AI shopping agents? — see §AI-Era Readiness --- ## Shipping Scope | Scope | Key Considerations | |---|---| | **Domestic Only** | Simplest; focus on carrier options, timelines, cutoffs, free-shipping thresholds | | **Regional** (e.g., EU-wide) | Harmonized customs within single market; local carrier partnerships; OOH networks | | **Cross-Border / Global** | DDP vs DDU; customs duties transparency; multi-carrier tracking normalization; per-market configurability | --- ## AI-Era Readiness — Critical for 2026 The most significant shift in 2025–2026: **58% of consumers have replaced traditional search engines with GenAI tools** for product research and price comparison (Capgemini 2026). AI shopping agents compare delivery dates, costs, return terms, and total landed costs **before** the shopper ever visits your site. **What this means for shipping policies**: - Delivery terms must be **machine-readable and structured** — an AI agent scraping your site must be able to extract delivery promises, costs, cut-off times, and geographic availability - If your delivery terms are buried in unstructured paragraphs, AI agents may **exclude your brand** from consideration entirely - Standardize delivery options in consistent formats: option name | cost | timeline | cutoff | regions **Practical recommendations**: - Use structured data (schema.org `OfferShippingDetails`) on product and checkout pages - State delivery promises as clearly as shipping-rate tables — avoid prose-only descriptions - Keep policy page content synchronized with structured data (mismatches erode AI trust) --- ## EU Regulatory Deadlines (2026) Two major compliance deadlines converge in summer 2026: ### EU Customs — July 1, 2026 A fixed **€3 customs duty** applies to all consignments valued under €150 entering the EU. This covers **93% of e-commerce imports** into the EU. **Shipping policy impact**: - **Landed-cost transparency at checkout is mandatory** — customers must see the total price including duties, taxes, and fees before completing purchase - If using DDU (duties collected at delivery), explicitly warn: "Additional customs fees of approximately €X may be collected on delivery" - **DDP (Delivered Duty Paid) is strongly recommended** — surprise duties at the door are the #1 cause of refused parcels and lost repeat purchases ### EU AI Act — August 2026 Online marketplaces and e-commerce platforms using AI for shipping decisions (carrier selection, delivery predictions, automated refund/reroute decisions) must comply with transparency obligations: - Automated decisions affecting delivery, refunds, or reroutes must be **auditable** — show what rule fired, what evidence supports the outcome - Customers must be informed when interacting with AI-driven delivery systems - Governance trails for automated logistics decisions are required --- ## DDP vs DDU Decision Framework This is now a commercial decision, not just a shipping detail: | Model | Pros | Cons | Best For | |---|---|---|---| | **DDP** (Delivered Duty Paid) | No doorstep surprises; higher conversion; better AI agent compatibility | Higher upfront logistics complexity; need duty calculation infrastructure | Cross-border brands prioritizing customer experience | | **DDU** (Delivered Duty Unpaid) | Simpler for merchant; lower displayed price at checkout | Doorstep shock; high refused-parcel rates; damages repeat purchase | Low-frequency exporters; items where duties are unpredictable | **Policy language for DDP**: "All duties, taxes, and customs fees are included in the price shown at checkout. You will not be charged additional fees on delivery." **Policy language for DDU**: "International orders may be subject to customs duties and import taxes. These charges are your responsibility and are collected by the carrier upon delivery. Estimated fees: [range or calculator link]." --- ## Cross-Border Shipping Essentials ### Tracking Normalization Cross-border shipments pass through multiple carriers (origin carrier → customs broker → destination carrier → last-mile). Customers need **one coherent tracking story**, not fragmented statuses from each handoff. Policy should state: - How tracking is provided (single tracking page/number even across carriers) - When tracking becomes available (typically 24–48 hours after shipment) - What to do if tracking shows no movement for [X] days ### Route Volatility (2025–2026 Reality) - 2,500+ trade restrictions imposed globally in the first 10 months of 2025 alone (World Bank) - Policy should include: "Delivery times are estimates and may be affected by customs processing, weather, or other factors outside our control" - Build per-market configurability: delivery windows, fees, and service mixes should be adjustable by region without operational chaos ### Prohibited & Restricted Items - List categories that cannot be shipped internationally (batteries, aerosols, certain food items, etc.) - Link to carrier-specific restriction lists - Note that customs may reject items even if the carrier accepts them --- ## Out-of-Home (OOH) Delivery —
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.