How to prepare product data for sales channels
What makes product data ready for a sales channel?
Product data is ready when the selected products have the descriptions, images, attributes and valid prices that the destination needs, and someone has reviewed the complete collection. Keep shared product facts separate from channel-specific copy, and retain the exact version approved for publication.
Define the source before preparing the channel
Scroll sideways to compare
| Information | Shared product record | Channel preparation |
|---|---|---|
| Identity and specifications | Maintain the product reference and agreed technical facts. | Select the fields the destination actually needs. |
| Descriptions | Maintain reusable product copy. | Review wording for the audience; use channel text overrides where appropriate. |
| Images | Keep linked product images and their descriptions. | Check required image count, original dimensions and linked alt text against configured rules. |
| Selling prices | Maintain a named price list with explicit currency, dates and quantity tiers. | Select a list for the channel; review base prices, currency and channel overrides. Missing list prices have no catalogue fallback. |
| Publication | Current records can continue to change. | Retain the reviewed collection so later edits do not silently replace its copied content. |
Start with the destination's requirements
A direct-sales collection and a wholesale catalogue can need different copy, images and prices for the same product. List the required fields and the person responsible for each. Distinguish missing information from information that is present but unsuitable for the intended audience.
Choose the assortment and selected product fields before writing more descriptions. Otherwise, a team can spend time polishing products that are outside the collection while missing required information on products it plans to sell.
Review the whole collection before publication
A complete-looking product card is not enough. Review missing fields, image requirements and pricing across the collection, then inspect the copied details of representative products. A content check establishes whether configured inputs are present; a human still needs to judge whether the claims and imagery are appropriate.
- Confirm the intended assortment, manual listings, exclusions and availability states.
- Select product views and configure the required text and image rules.
- Resolve missing content and check channel-specific wording against the shared facts. Content keeps search, coverage and assortment scope visible; open Filters for field issues, copy source or ordering.
- Review the price source, pricing date, missing prices and currency conflicts.
- For release-controlled products, complete certification of the current approved revision and any required configuration release. Check paused products too; retained publications preserve the exact release identities.
- Preview the complete collection and save the reviewed publication with its rationale.
- Export the saved publication using Shopify, WooCommerce or General CSV. Review the file in the destination's importer and confirm the result before treating the store as updated.
Illustrative workflow
Example: one jacket, two audiences
Imagine an outdoor jacket appearing in a consumer collection and a wholesale preview. Both use the same product identity and material facts. The consumer description explains intended use; the wholesale description adds partner-facing context. The wholesale copy can remain incomplete while the consumer publication retains its reviewed content.
If the shared description changes later, review the new draft explicitly. ManyRows keeps the saved publication's effective product values and captured asset descriptors; saving that internal publication is separate from sending it to an external storefront.
See assortment and channel publication workflowsWhere ManyRows fits
ManyRows connects product definitions with assortments, selling prices, content checks, channel text and retained publication copies. Evaluate it when those teams need to work from the same product context. Author language-specific copy and image descriptions, then export the retained publication with reusable Shopify, WooCommerce or General CSV mappings. Store presets import as drafts. Shopify can explicitly group variants using saved family rules, ordered option labels, SKUs and prices; WooCommerce can emit variable parents and variations with stable captured SKUs and local attributes. Both exporters keep the simple preset available by default. Automated translation and automatic marketplace delivery require separate tools or integration.
Common questions
Does a saved publication update a storefront automatically?
No. A ManyRows channel publication retains a reviewed collection inside ManyRows. Export the saved publication as Shopify, WooCommerce or General CSV and import the file in the destination. Automatic storefront synchronization requires a separate integration; confirm the import result in the store.
Do channel descriptions change the shared product record?
Channel text overrides apply to the selected channel. Shared records and other channels keep their own values. Turning an override off restores inheritance from the current shared text; a previously saved publication keeps its retained copy.