retailer-upc-resolution-feasibility

Validate retailer UPC-to-item-ID and PDP URL resolution via proxy-backed Java probes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the risk of building production retailer integrations for unproven UPC resolution routes, which would waste engineering time and lead to broken item ID lookups in live systems.

Core Features & Use Cases

  • Production-Runnable Feasibility Probes: Test retailer endpoints using proxy-backed Java requests that mimic Pear datacenter egress, avoiding false positives from local-only testing.
  • UPC Evidence Validation: Enforce proper UPC matching logic to prevent incorrect resolutions, and document clear blockers when routes fail instead of using hardcoded test data.
  • Use Case: An engineer building a new retailer integration can use this skill first to confirm the UPC-to-item-ID route works, then graduate the proven code to a production ItemIdInfoResolver without leftover feasibility artifacts in the final PR.

Quick Start

Use the retailer-upc-resolution-feasibility skill to test if a target retailer can resolve a sample product UPC and name to a valid item ID and PDP URL via production-like proxy-backed requests.

Frequently Asked Questions about retailer-upc-resolution-feasibility

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

FAQPage Schema
How do I validate if a retailer endpoint can resolve a UPC to an item ID before building a full integration?

You can validate UPC resolution feasibility by running production-runnable Java probes that fetch live evidence from retailer endpoints via proxy-backed requests, confirming the UPC-to-item-ID route works before building production classes.

Why does my local UPC resolution test pass but fail in the production datacenter?

Local UPC resolution testing often yields false positives because it bypasses datacenter egress rules; production-runnable feasibility probes use JurlProxyFallback to mimic actual proxy-backed retailer requests and prevent this mismatch.

How do I test retailer UPC matching logic without using ad-hoc string checks?

You can enforce proper UPC matching by using UPC.isAUPCMatch logic within your Java probes, which validates that a product UPC and name correctly resolve to the retailer-specific item ID instead of relying on inaccurate string comparisons.

Can I use proxy-backed Java probes to check if a retailer integration route is viable?

Yes, proxy-backed Java probes can test retailer endpoints by mimicking datacenter egress, allowing you to confirm UPC-to-PDP URL resolution feasibility and document clear blockers if the public endpoints fail before committing to production code.

What should I do with the feasibility probe code after validating the UPC resolution route?

After validating the UPC resolution route, you should graduate the proven probe code into a production ItemIdInfoResolver class and its associated test suites, ensuring no leftover feasibility artifacts remain in the final pull request.