retailer-verify

Validate retailer integration flows for UPC availability, button rendering, and PDP redirects.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill retailer-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retailer-verify
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/retailer-verify
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill retailer-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually verifying that a retailer integration works correctly from server-side availability updates to shopper-facing landing page and product detail page (PDP) redirects is time-consuming, error-prone, and requires cross-checking multiple systems, APIs, and browser flows to confirm end-to-end functionality.

Core Features & Use Cases

  • End-to-end integration verification: Validates the full retailer workflow, from UPC availability updater execution and saved availability row accuracy to UPC-only offer landing page retailer button rendering and final PDP redirect behavior.
  • Retailer-specific checks: Supports verification for custom retailer integrations including CityHive, using JSPs for production database/server context checks, retailer-list APIs for availability data, and browser tools for click-through validation.
  • Use case example: A developer can use this skill to confirm that a Tractor Supply Co. retailer integration correctly shows an in-stock product for a given UPC, displays the "Shop at Tractor Supply Co." button on the landing page, and redirects shoppers to the correct in-stock product page.

Quick Start

Use the retailer-verify skill to confirm that a specified retailer and UPC pair produces an available result, shows the correct retailer button on the UPC-only landing page, and redirects to the expected in-stock product page.

Frequently Asked Questions about retailer-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify end-to-end retailer availability and PDP redirects for a specific UPC?

End-to-end retailer verification validates UPC availability updater execution, checks saved database rows via retailer-list APIs, and confirms browser click-through redirects to the correct product detail page. This ensures shopper-facing flows operate as intended across all integration points.

What is the best way to test UPC-only landing page retailer button rendering?

UPC-only landing page retailer button rendering is tested using browser click-through validation to confirm the correct retailer button displays. Verification checks that buttons like "Shop at Tractor Supply Co." appear and redirect shoppers to the proper in-stock product page.

Does retailer verification support custom integrations like CityHive?

Retailer verification supports custom integrations including CityHive by using JSPs for production database and server context checks. It validates retailer-list API availability data and performs browser click-through testing to confirm full shopper-facing flow accuracy.

How do I check if a retailer availability updater correctly saved stock status to the production database?

Retailer availability updater verification uses JSPs to query the production database and confirm saved availability rows match expected stock status. The retailer-list API is then checked to validate the availability data reflects accurately for the specified UPC.

Can I validate PDP redirect accuracy without manually clicking through the browser?

PDP redirect accuracy validation combines retailer-list API availability checks with browser click-through testing to confirm redirect behavior. While API checks verify data accuracy, browser tools validate the actual shopper-facing redirect flow to the expected in-stock product page.