What should be the source of truth for my product catalog?

Separate facts from the way you sell them

A lamp's dimensions, material, and plug type describe the item. Its marketplace title, promotional price, and position in a seasonal collection describe how you sell it. Mixing those categories makes catalog ownership harder than it needs to be. A channel optimization should not accidentally change the physical specification used by another channel or by your warehouse.

Create a simple field map before choosing tools. Group information into identity, factual attributes, media, commercial terms, and channel presentation. Decide which fields are shared, which may vary, and which require approval to change. This exercise often reveals that the business does not need a completely new catalog platform yet. It needs clear rules for the product information it already has.

Pick authority where the work actually happens

The best authoritative system is not necessarily the most expensive or the one with the largest feature list. It is the place where the responsible team can keep information complete and correct. If merchandising maintains every product in Shopify and your assortment is manageable, introducing a separate master database may create another place to forget an update.

On the other hand, a business with several brands, complex supplier specifications, and many localized descriptions may benefit from a dedicated catalog process upstream of the storefront. Evaluate the number of people editing products, the variety of attributes, and the cost of errors. A system becomes authoritative through ownership, validation, and a dependable publishing process—not because someone labels it the master in a diagram.

Give every sellable variation a durable identity

Product names are poor integration keys. They change, may be translated, and often repeat across a range. Build around stable internal variant identifiers and a deliberate SKU convention. Keep marketplace references alongside them so a channel's listing can change without losing the connection to the underlying item.

Consider a fictional backpack sold in three colors and two sizes. That is six sellable combinations, even if the website presents one product page. Each combination needs a reliable identity and the correct physical details. Shopify's guidance recommends unique SKUs for distinct variants, while GS1 identifiers serve a different purpose in identifying trade items across businesses. Keep those roles distinct rather than forcing one number to answer every question.

Create a field ownership agreement

Write a short agreement that names the owner of each important field. For example, merchandising approves titles and descriptions, the warehouse verifies packed dimensions, purchasing maintains supplier references, and finance approves cost information. Also specify where each approved change is entered and what happens after it is published.

Ownership should include exceptions. A marketplace may require a particular category or attribute vocabulary that does not exist in your central store. That channel-specific value needs a home and an owner, too. Without one, people tend to solve the immediate listing problem in the marketplace portal and forget that a later synchronization may overwrite the correction. Keep overrides deliberate, visible, and narrow.

Use a disputed field to test the agreement. Imagine the warehouse corrects a packaged weight while a merchandising import still contains the old value. The next scheduled upload should not silently reverse the correction. Decide which team can approve the physical fact, how the outdated value is rejected, and whether an affected shipping configuration needs review. This is where field ownership earns its keep: it resolves a real conflict without requiring everyone to remember the last conversation.

Validate the smallest useful set before publishing

Catalog completeness is more useful when it reflects the product and destination. A downloadable product does not need a packed shipping weight; a fragile physical product probably does. Build validation around what the workflow actually needs, including units, allowed values, variation relationships, and required identifiers. A nonempty field is not necessarily a correct field.

A useful review can be surprisingly compact. Check whether the variation exists, whether its identifiers are unique where required, whether numeric measurements use the intended units, and whether images correspond to the exact option being sold. Then apply the destination's requirements. eBay's offer-publishing documentation, for example, distinguishes information needed to create inventory records from the information needed to publish an offer. Saving a product is not the same milestone as making it ready to sell.

Protect approved facts from round-trip edits

A common integration design sends product information outward and then imports everything back as if the channel's record were a new master. That can replace carefully maintained attributes with shortened titles, missing fields, or channel-specific formatting. Decide which information is allowed to return and whether it can overwrite an approved value.

Use a review step for conflicting facts rather than silently choosing whichever system updated last. If a supplier sends a new weight while the warehouse has a recent measured weight, both timestamps matter, but the business rule decides authority. Keep enough history to explain the decision. You do not need a sprawling approval committee; you need a way to avoid accidental changes becoming permanent truth.

Measure whether the catalog is getting easier to trust

Count recurring defects by field and product family. Missing dimensions across one supplier's range calls for a different fix from duplicate SKUs across the whole assortment. Track time from product approval to channel readiness, rejected changes, and the number of manual corrections that do not make it back into the authoritative record.

Review your ownership agreement when the business changes. Adding a warehouse, a new product category, or a wholesale program may alter where particular facts should live. Keep the structure simple enough that a new team member can answer three questions: where do I correct this information, who approves it, and which channels will receive the change? If those answers are clear, your source of truth is doing its job.

Write a change brief before a bulk update

Bulk edits deserve a small change brief: which products are included, which fields will change, why the change is needed, and which destinations should receive it. Export a useful baseline and test a representative sample before applying the update broadly. Include a product with several variants and a product with a channel-specific override, because those are common places for unexpected behavior to surface.

After the update, compare the approved values with what the receiving channel actually displays. Record exceptions rather than repeatedly resending the entire catalog. A disciplined bulk update can save hours; an undocumented one can make hundreds of incorrect fields look like hundreds of unrelated problems. The source of truth becomes valuable when changes through it are understandable and repeatable, not merely when its spreadsheet is larger than everyone else's.