Review and prepare product data
Keep synchronized product records accurate enough for recommendations, catalogs, campaigns, and revenue analysis.
What you’ll achieve
- A current product set that renders reliably in personalization, catalogs, and customer-facing campaign assets.
Suivez le flux de travail
-
1
Open Data → Own Data → Products
Choose the correct connector and account, then use search and filters to review the active product set.
-
2
Check merchandising fields
Verify title, description, image, destination, price, compare-at price, currency, availability, vendor, type, variants, collections, and update time where available.
-
3
Correct data at its source
For synchronized commerce records, prefer fixing wrong titles, prices, stock, images, or URLs in the connected store so the next sync remains authoritative.
-
4
Use import or feed controls deliberately
When the workspace supports manual import or feeds, map identifiers consistently and avoid creating duplicates of products already owned by a connector.
-
5
Review recommendation readiness
Exclude unavailable or incomplete items from static selections and fallbacks. A usable recommendation needs a public destination and presentable image, name, and commercial state.
-
6
Confirm downstream rendering
Preview representative products in an email, web push, popup, or catalog and verify the customer-facing price, currency, image crop, and click destination.
Verify your work
- Active products have usable images and public destinations
- Price, currency, availability, and variants match the commerce source
- A downstream preview renders without empty product cards
If something doesn’t look right
A product is duplicated
Compare connector IDs and import/feed mapping before deleting or merging records.
Data is stale
Check connector health and last update, then allow the next synchronization to complete.
An image fails in campaigns
Use a publicly reachable HTTPS asset and update the authoritative source record.
Limitations and safeguards
Inventory and price changes are not always instantaneous; verify time-sensitive offers close to send or publish time.