Catalogue Relay: Better Feed Previews Before Product Changes
Supplier data can help maintain a catalogue, but a new file should not automatically overwrite every field in a store. Catalogue Relay’s development focuses on previewing sources, matching records and making the ownership of product information explicit.

Review what a feed means for your store
Feed preview and mapping workflows give merchants a place to inspect supplier data before proposed changes are applied. Product and variant matching must be understood alongside exceptions such as missing identifiers or repeated rows.
The benefit is a clearer review process: identify what the source contains, which records it refers to and which fields it is allowed to influence. It remains important to use representative samples and confirm matching rules for the specific catalogue.
Preserve merchant-controlled content
A supplier may be the source for one field while the merchant owns another. Field ownership helps keep those responsibilities separate, so a feed-driven workflow can be planned around the information the business intends to maintain.
For example, a merchant may want supplier information considered for an operational field while retaining an edited customer-facing description. The exact mapping and allowed changes need to be agreed and reviewed rather than inferred from a column name.
Reliability includes clear failures and support
Recent development improved feed reliability and privacy safeguards. Support guidance directs merchants towards useful job references and error codes while keeping credentials and unnecessary customer information out of support messages.
A successful upload or a healthy server is only part of the picture. The proposed records, review stage and final merchant workflow still need acceptance checks. Clear failure handling helps the team investigate an exception without treating incomplete work as finished.
Current availability and boundaries
Catalogue Relay remains in development. Inventory execution is disabled. Authenticated merchant acceptance and app-specific policy publication remain outstanding, and public installation and final pricing have not been announced.
The next step for an interested business is to discuss its sources, matching identifiers and field ownership using redacted examples. This update does not announce unattended stock changes or a production-ready public release.