When working with Products, you must define your Master Product Source: the system that serves as the single source of truth for Product data across your ecosystem. This guide explains how to properly configure it based on your Product management scenario.

This configuration is typically required when:
Initializing a new Account.
Migrating Product management from one system to another.

- May result in duplicate products, requiring manual cleanup.
- Will restrict Recurring Jobs (automations) for Import Product options for non-master Channels.
If you are planning this transition, we highly recommend you to carefully review the following before and after changing your Master Product Source:
- Products catalogue, as detailed in How to find/filter Products [Step-by-Step Guide].
- Recurring Jobs (automations) settings, as detailed in How to configure Automations for Sales/Fulfillment channels [Step-by-step guide].
techOMS requires all SKUs to be unique in the Master Product Source.
To configure the Master Product Source:
1. Access the Account settings page.

2. Set the Master Product Source to one of the following:
- techOMS (default): Use techOMS as the master Product catalog. If selected, go to Step 4.
- Sales Channel: Use a Sales Channel as the master source.
- Fulfillment Channel: Use a Fulfillment Channel as the master source.
WARNING: Changing this setting on a live Account may cause product duplication. Manual cleanup and recurring job reconfiguration may be necessary.
3. Select your Master Product Channel.

Disabled channels (shown with a (disabled) suffix) can still be selected, but no Product data will sync from them.
4. Press Save.
Once configured, the selected system becomes the Master Product Source. Product data will sync from that system to techOMS (or originate in techOMS itself, if selected) and then propagate to all connected channels, ensuring a consistent product catalog across your ecosystem.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article