Product data ownership: resolve a price conflict

Write the ownership rule before the next conflict ↗

The register below is a proposed method for a fictional catalog. It separates the application that stores a value from the evidence that supports it. A PIM copy can be useful without being authorized to approve a new retail price.

The download covers nine fields, including availability, lead time, identifiers, variants, and images. Replace the systems and roles with your own. A spreadsheet documents a rule; integrations and permissions must enforce it.

Check that the values describe the same fact ↗

A retail price and a wholesale price are not conflicting copies of one fact. Neither are packaged weight and product weight. Check variant, market, currency, unit count, tax basis, meaning, and effective date before choosing a winner.

For Google Merchant Center, submitted price and currency must meet its landing-page and checkout requirements. Its availability guidance also requires consistency. Those destination rules support an agreement check; they do not tell you which internal application should own the value.

Source: Google Merchant Center: Price; Google Merchant Center: Availability

Work the conflicting-price example ↗

All three observations below describe one fictional black lamp, one retail unit, sold in the US in USD. At 14:05 UTC on August 24, the example register gives the ERP approved retail-price record authority. Revision DEMO-PRICE-17 took effect at 14:00. The pricing lead confirms its approval.

The current approved price is 120. The PIM and feed are stale mirrors, not competing approvals. Hold the affected channel offer, correct the mirrors from revision 17, then confirm the selected-variant landing page, checkout, and destination offer all show 120 USD. Keep the mismatch and correction evidence.

If the authoritative record is unavailable, leave the decision on hold. A recent mirror does not become an approved source just because it can be fetched.

Set freshness for the decision ↗

This example allows price evidence up to five minutes old and availability evidence up to one minute old. Those are fictional operating choices, not Google requirements. Set tolerances with the owner based on change frequency, consequence, and the ability to detect updates.

Observation age, approval, and effective date are separate checks. Fetching an old unapproved record now does not make it authoritative. Stable specifications can use revision-based updates plus periodic evidence review. Recheck the approved source at release time if its observation has expired.

Close the exception with destination evidence ↗

In this proposed workflow, the pricing lead approves the commercial value and commerce operations confirms delivery. A feed job reporting success is insufficient if the destination still displays the old offer. Keep the affected channel restricted until the checks pass; use that channel’s supported controls rather than falsifying stock status.

Google’s variant guidance requires direct selection of the correct variant with its corresponding price and availability. Resolve ownership first, then use the existing variant acceptance test to check the delivered record.

• Confirm the approved revision and its scope.
• Record the correction, responsible role, and destination acknowledgement.
• Compare the selected variant, landing page, checkout, and offer after the correction.
• Recheck evidence age and record who released the hold.
• If a downstream system may write back, route its proposed change through the authoritative approval path.

Source: Google Search: Product variant structured data

Start with three fields ↗

Begin with price, availability, and one specification customers use to choose a product. Fill the register with their owners and run one disagreement through it. An agent may collect evidence or propose a correction within its permissions; approval and release authority still need to be explicit.

This resource addresses ownership and correction. The product-data contract describes the record an agent reads; the variant acceptance test checks whether the published facts agree. Use the three together.