Product data management + catalog conflict resolution
Per-attribute conflict resolution across POS, ERP, PIM, supplier feeds, and marketplace feeds — with operator-defined precedence, per-vertical conditioning, and audit-defensible linkage.
The problem
Your POS says the SKU description is one thing, your PIM says another, your ERP has a third, the supplier feed has a fourth, and the marketplace listing yet another. When the same product appears on Amazon, Walmart, Target, and Shopify — and a customer pulls up the page on Google Shopping — the descriptions, prices, and regulated claims are inconsistent.
Your Salsify license ships a hardcoded record-level precedence policy. Informatica costs $200,000+/year and requires a 6-month implementation. PIM platforms (Salsify $30-$300k+/year, Productsup, Akeneo $25-$200k+/year, inriver, Syndigo) handle conflict resolution at the record level only. Enterprise data-quality suites (Informatica Data Quality $50-$200k+/year, IBM InfoSphere $50-$500k+/year, Talend Data Fabric, Trifacta / Alteryx) are over-built for multi-location-operator scale with generic-data focus. Specialized product-data-quality tools (Catsy $500-$5k+/month, Plytix $300-$2k+/month, Pimcore, ChannelEngine) provide mid-market deduplication and basic validation. ETL data-cleansing scripts (Fivetran transforms, dbt models, custom Python pandas) cost $80,000-$150,000/year per data-engineer FTE. DIY (manual CSV review + spreadsheet dedup) falls apart past 1,000 SKUs or 5+ brand portfolios.
The gap is per-attribute conflict resolution with operator-defined precedence policies, per-vertical and per-jurisdiction conditioning, and audit-defensible versioned-history linkage.
What success looks like
Operator-defined per-attribute precedence policies resolve which source wins for every attribute class. Regulated claims default to legal-approved source; pricing defaults to ERP; images default to marketing-asset-management source; inventory defaults to POS.
Per-vertical-compliance-overlay and per-jurisdiction-overlay-config condition the precedence policy — cannabis-state-specific dosage claims resolve to in-jurisdiction-approved source; financial-services performance claims resolve to FINRA-compliant source; FDA structure-function language resolves to legally-substantiated source.
Multi-source ingest from POS, ERP, PIM, supplier feeds, marketplace feeds, and internal marketing asset libraries surfaces conflicts at per-attribute granularity. Every conflict-resolution decision ties to versioned-product-history for audit-defensible regulator inquiry response.
Conflict resolution runs upstream of catalog-change-event-emission. Downstream subscribers (Google Shopping, Meta Marketplace, Amazon, Walmart, retailer feeds, PDP agent, paid creative agent) always consume the operator-resolved attribute value. Feedonomics, GoDataFeed, DataFeedWatch, and Channable continue to optimize downstream feeds; this skill upstream resolves attribute conflicts so feeds stay consistent across channels.
How most operators solve this today
Five tiers of incumbent tools — none provide per-attribute conflict resolution with per-vertical and per-jurisdiction conditioning at multi-location-operator scale.
PIM platforms with built-in conflict-resolution (Salsify, Productsup, Akeneo, inriver, Syndigo)
$20,000-$300,000+/year
Conflict resolution at record-level only — which source wins for the whole record. Per-attribute operator-defined precedence requires custom configuration.
Enterprise data-quality suites (Informatica Data Quality, IBM InfoSphere, Talend Data Fabric, Trifacta / Alteryx)
$50,000-$500,000+/year
Over-built for multi-location-operator scale. Generic-data focused. 3-12 month consulting implementation. Not optimized for product-catalog operations.
Specialized product-data-quality tools (Catsy, Plytix, Pimcore, ChannelEngine)
$300-$10,000+/month
Mid-market deduplication plus basic validation. No per-attribute precedence policy semantics or per-vertical / per-jurisdiction conditioning.
ETL data-cleansing scripts (Fivetran transforms, dbt models, custom Python pandas)
$80,000-$150,000/year per data-engineer FTE
Custom-coded per-skill. API drift maintenance consumes ~1/3 FTE time. Operator-defined policy changes require dev work.
DIY (manual CSV review + spreadsheet dedup + brand-manager attribute-by-attribute review)
Free
Falls apart past 1,000 SKUs or 5+ brand portfolios. No audit trail; no programmatic enforcement.
What changes when this is an agent skill
The Completions catalog-conflict-resolution skill applies operator-defined per-attribute precedence policies across multi-source ingest. Regulated claims default to legal-approved source; pricing defaults to ERP; images default to marketing-asset-management source; inventory defaults to POS.
Per-vertical-compliance-overlay (loop 001) and per-jurisdiction-overlay-config condition the precedence policy. Cannabis-state-specific dosage claims, FINRA financial-services performance claims, and FDA structure-function language all resolve to compliance-approved sources.
Multi-source ingest from POS, ERP, PIM, supplier feeds, marketplace feeds, and internal marketing asset libraries surfaces conflicts at per-attribute granularity. Every resolution decision ties to versioned-product-history for audit-defensible regulator-inquiry response.
Conflict resolution runs upstream of catalog-change-event-emission (loop 026). Feedonomics, GoDataFeed, DataFeedWatch, and Channable continue to optimize downstream feeds; this skill upstream resolves attribute conflicts so feeds stay consistent across channels.
Agents that include this skill
Skills live inside agent rentals. To get this skill in production, hire any of the agents below — context-tuning at onboarding is included in the first month.
Product Catalog Canonicalization Agent
Use-case foundation agent that produces the canonical product catalog every retail-persona surface agent consumes.
Early-adopter
$2,000–$4,000/mo
FAQ
- What is product data management?
- Maintaining canonical product catalog data across every source (POS, ERP, PIM, supplier feeds, marketplace feeds) with per-attribute conflict resolution. This skill provides operator-defined per-attribute precedence with per-vertical and per-jurisdiction conditioning.
- How is this different from Salsify or Akeneo conflict-resolution features?
- PIM platforms ship coarse record-level precedence (which source wins for the whole record). This skill provides per-attribute precedence with per-vertical and per-jurisdiction conditioning.
- How is this different from Informatica or Talend (enterprise data-quality)?
- Enterprise data-quality suites are over-built for multi-location-operator scale ($200,000+/year, 6-12 month implementation, generic-data focused). This skill is purpose-built for product-catalog with operator-defined per-attribute policies.
- What attribute conflicts does the skill resolve?
- Price, inventory state, product description, image, variant attribute, regulated claim, per-jurisdiction descriptor, channel-specific descriptor, marketplace-specific compliance language, and custom operator-defined attribute classes.
- How does this compose with multi-source-catalog-ingest?
- Multi-source-catalog-ingest brings data in from POS, ERP, PIM, supplier feeds, and marketplace feeds. This skill resolves the per-attribute conflicts before downstream consumption.
- How does this compose with catalog-change-event-emission?
- Conflict resolution runs BEFORE emission. Downstream subscribers always consume the operator-resolved attribute value, never the raw feed value.
- How does this compose with per-vertical-compliance-overlay?
- Per-vertical compliance (FDA structure-function, FTC claim substantiation, state-AG cannabis) conditions the precedence policy. Regulated claims always resolve to compliance-approved sources.