Do not index
Typically, when using our sync plans Wherehouse pulls product data from your system of record (such as your ERP, accounting system, or online store) via our integrations and uses that data to sync information to your sales channels (online store and marketplaces)
However, there are times when you may want to override the standard sync behaviour for specific SKUs or channels. That’s where Sync Overrides come in.
What Are Sync Overrides?
Sync Overrides allow you to manually set specific stock or pricing values that Wherehouse will prioritise over your normal sync rules.
In simple terms, when a sync override exists, the override value becomes the value that Wherehouse sends to the marketplace, instead of the value coming from your external integration or pricing rules.
This gives you granular control over individual SKUs without needing to change your entire pricing or stock strategy.
Important: Override fields take precedence over values from external integrations and repricer rules.
How Sync Normally Works
In a standard setup, Wherehouse stores several pricing and stock-related fields for each product, including:
- Stock
- Wholesale Price
- Retail Price
- Sale Price
- Cost Price
These values are typically ingested from your system of record (SOR) and used as the source data for syncing to marketplaces.
For example:
- Retail price may be used for marketplace pricing
- Adjustment rules may increase or decrease the price for certain channels
- Stock levels are synced from your SOR as is or with an adjustment/buffer rule
This automated structure works well for most products.
But sometimes you need exceptions.
When Would You Use Sync Overrides?
Sync Overrides are useful when you need SKU-level control for a specific marketplace or situation.
Some examples include:
1️⃣ Marketplace-Specific Pricing
You may want a product to have a different price on a specific marketplace.
Example:
- Retail Price in your system: R500
- Default Takealot pricing rule: Retail + 10%
- Expected Takealot price: R550
But you want the item listed on Takealot at R529 instead.
By setting a Takealot Sell Price override, Wherehouse will sync R529, ignoring the normal pricing rule. It will stick to this price until you:
- Update the pricing override or
- Remove the pricing override (and we sync from your SOR again)
2️⃣ Temporary Pricing Adjustments
Pricing overrides are great for once off promotions without affecting all channels.
You might want to:
- Run a promotion
- Clear old stock
Instead of changing stock or pricing everywhere, you can simply set an override for the affected SKUs on the relevant sales channels
3️⃣ Preventing Certain SKUs From Syncing
In some cases, you may want a product to stop syncing entirely or stop syncing certain data fields.
Sync Overrides allow you to disable:
- Disable Stock Sync – prevents stock updates for a SKU
- Disable Price Sync – prevents price updates for a SKU
- Disable Sync – disables both stock and pricing sync for a SKU
This is useful when a product:
- Is being manually managed on the marketplace
- Has special pricing agreements
- Should remain fixed regardless of system updates
How Sync Overrides Work
Sync Overrides can be applied in two ways:
1. Bulk Import / Export
You can export your catalogue, add override values in bulk, and re-import the file to update multiple SKUs at once.
This is ideal when managing large product catalogues.
2. Per-SKU Overrides on the Wherehouse Dashboard
Overrides can also be set directly within the Wherehouse dashboard for individual SKUs.
This is useful when you only need to adjust one or two products.
Steps on how to do so in this doc:
Setting Sync Overrides on the Wherehouse Dashboard
Note: Because sync happens on scheduled integration cycles, changes made to overrides may only reflect on the next sync cycle, rather than immediately after uploading them.