Do not index
Understanding the Basics 🧐
What is a Code (SKU)?
A Code (SKU) is the unique identifier used to track a product across systems. Wherehouse relies on SKUs to sync products, stock levels, pricing, and orders between platforms.
What is a System of Record?
Your System of Record (SOR) is the primary platform where your product data is managed. This is your “source of truth” for inventory and pricing (e.g. Cin7 Core, Zoho, Shopify, etc.).
What are Code (SKU) Remaps?
Code (SKU) Remaps allow you to link mismatched SKUs across platforms so they are treated as the same product.
If a product exists on a sales channel with a different SKU than the one in your System of Record, Wherehouse will treat them as separate products. This prevents syncing of data (such as stock, pricing, and orders) between the products.
A SKU Remap resolves this by telling Wherehouse:
“This SKU on this marketplace is the same product as this SKU in my System of Record”
When should you use SKU Remaps?
Use SKU Remaps when:
- You have products listed on sales channels (online stores or marketplaces) with SKUs that do not match your SOR
- You cannot change the SKU on the marketplace
- You need a quick way to align SKUs and enable syncing
Best Practice
Where possible, always update the SKU on your sales channel (online store or marketplace) to match your System of Record instead of using remaps.
This keeps your setup clean and reduces complexity.
Marketplace notes:
- Takealot / Amazon / Leroy Merlin: SKUs can typically be updated (recommended approach). Refer to our SKU-changing how-to guides for Amazon and Leroy Merlin:
- Bobshop: Uses a feed, so SKUs are always synced from your System of Record.
- Makro / Loot: SKUs cannot currently be changed on these marketplaces. You will need to use remaps.
Example Scenario
You sell running shoes with the following SKUs:
- SKU RUN-PRO-TY in your System of Record (e.g. Cin7 Core)
- SKU RunPro-Teal on Takealot
Wherehouse imports these as two separate products, because the SKUs do not match.
Result:
- Orders from Takealot won’t sync to your System of Record
- Stock and pricing updates from your System of Record won’t sync to Takealot
Solution:
To resolve this, create a SKU Remap linking:
- Takealot SKU RunPro-Teal → System of Record SKU RUN-PRO-TY
Once mapped, Wherehouse treats them as the same product, and syncing will function correctly.
How to Set Up Code (SKU) Remaps
2️⃣ Find the System of Record Product
Use the search bar or filters to locate the product from your System of Record
e.g. the one showing “Synced to Cin7 Core”
3️⃣ Open the Product
Click on the product to open the product details modal.
4️⃣ Open SKU Remaps
Click the pencil icon next to the Code (SKU) field.
This opens the Code (SKU) Remaps modal.
5️⃣ Add a Remap
Under Add New Code (SKU) Remap:
- Select the relevant platform (e.g. Takealot)
- Enter the SKU as it exists on that platform
- Click Add Remap to save the remap entry
☝️ You can repeat this step for multiple platforms if needed.
6️⃣ Finalise
Click Save Code (SKU) Remap
What happens after setting up a Code (SKU) Remap?
- The marketplace SKU is now linked to your System of Record SKU
- Wherehouse will treat them as one product
- Syncing of orders, stock, and pricing will now work as expected
On your dashboard:
- Only the System of Record SKU will be displayed
- The product will show multiple “Synced To” tags (e.g. Cin7 Core + Takealot)
- The marketplace-only SKU will no longer appear as a separate product
SKU Remaps are a powerful way to fix mismatched product codes across platforms and ensure accurate syncing.
However, for long-term simplicity we recommend:
- Matching SKUs across systems (updating the SKU on the platform to match your SOR)
- Using remaps only when changing SKUs is not possible