Review a possible duplicate item
Resolve a product match using reliable identifiers before changing either catalog.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
For a commerce team authorized to maintain both product catalogs, review newly listed items, compare a stable product reference against existing records, and prepare a matching entry with the approved name, price, reference, and description. An incorrect match, price, or description can affect orders and accounting, while product text and images may be protected material. Verify identifiers, currency, publication status, and content rights; limit access to catalog data; and require a catalog owner to approve each new record or uncertain match before it is created.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
“Keep catalog records consistent while preventing duplicate, mispriced, or unauthorized listings.”
Clear tasks, with review where it matters.
Checks a newly listed product against an existing catalog using its internal reference, then prepares a matching item record when no duplicate is found.
A missing or inconsistent product reference can create duplicates, and a mapped price or description may be wrong or unlicensed. Verify the exact item, price and currency, publication status, and reuse rights; keep customer data out of the product record; and require human approval before a new catalog entry is created.
Select an illustrative task to explore its proposed role. No workflow runs here.
Use product information the business may copy and maintain in the destination catalog.
Check the reference and item attributes, and route blank, repeated, or conflicting identifiers to a person.
Confirm currency, description, public status, and other fields against the approved listing before transfer.
Restrict catalog access and do not copy customer or order data into product records.
Have a catalog owner review the exact destination record and explicitly authorize any create, update, or duplicate resolution.
Use product information the business may copy and maintain in the destination catalog.
These are planning notes for the concept, not instructions for a currently available template.
Name the source and destination owners and confirm the business purpose for cross-catalog updates.
Define which identifiers are authoritative and pause when a possible match is uncertain.
Confirm currencies, source-text permissions, publication status, and the mapping for each product field.
Require an authorized owner to approve new products and any correction that affects customer-facing information.
Published templates and verified customer availability remain pending.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation