Blog
Product Listing Management Across Marketplaces: One Catalogue
Selling on Tokopedia, Shopee, Lazada and TikTok Shop? Learn what to keep in one master catalogue, what syncs, what breaks and when to get help.
- mid
- marketplace
If you sell on more than one Indonesian marketplace, you need one master catalogue that you control, and the marketplaces should receive their listings from it. In practice that means one place holding your SKUs, names, descriptions, images, prices and stock, with each channel treated as a destination rather than the source of truth. You do not need to sync everything automatically. Syncing stock and price is where the value is. Titles, images and descriptions can stay semi-manual.
This article explains what that looks like, what it costs in effort, and where it goes wrong. It is a business overview, not a technical guide.
Why separate listings drift apart
Most sellers start on one marketplace and add others later. Each listing is created by hand or copied, and then each is edited separately. After a year you often find:
- The same product has three different names and two different SKU codes.
- A price change was made on Shopee but forgotten on Lazada.
- Stock sold on one channel is still shown as available on another.
- Old photos or outdated descriptions remain live on one channel.
The cost is not abstract. Overselling leads to cancelled orders, which marketplaces track against your store performance. Wrong prices either lose margin or lose sales. Both are avoidable.
The foundation: one SKU per sellable item
Everything else depends on a clean SKU structure. Each sellable variant (for example a T-shirt in size M, colour black) needs one internal code that you own and that is used on every marketplace. If you use different codes per channel, you cannot reliably match sales and stock across them.
In an ERP such as Odoo, products and their variants (size, colour and so on) are modelled as one product with attributes, where each variant has its own stock and sales history (Odoo documentation on variants). That is the kind of structure you want to mirror: one parent product, clearly defined variants, one code each.
Fixing SKUs is unglamorous, but it is usually the longest part of the project. Budget for it.
What to centralise and what to leave per channel
| Item | Centralise? | Note |
|---|---|---|
| SKU, product name, base description | Yes | One source, adapted per channel |
| Stock quantity | Yes, and sync automatically | The most important field |
| Price | Yes, with channel-specific rules | Marketplaces have different fees and promotions |
| Images | Yes, store originals centrally | Each channel has its own size and format rules |
| Category and attributes | Map once per channel | Each marketplace uses its own category tree |
| Promotions, vouchers, ads | Leave in each seller center | Too channel-specific to centralise early |
Category mapping deserves a mention. Tokopedia, Shopee, Lazada and others each have their own category structures and required attributes. A product that is accepted on one channel can be rejected or flagged on another for a missing attribute. Plan to map categories once and reuse that mapping.
What actually syncs, and what usually does not
Tools differ, so confirm with any vendor before buying. As a general pattern, integrations reliably handle stock and price updates, and many can pull orders into your system. Creating new listings, updating rich content and handling variants is less uniform. In general, stock and price are the easy part of a sync, and content is harder.
Ask any provider these questions:
- Can it create new listings, or only update existing ones?
- Does it handle variants and your category mapping?
- How often does stock sync, and what happens if a sync fails?
- Are listing rejections from the marketplace reported back to you?
The Tokopedia and TikTok Shop change
Tokopedia and TikTok Shop now run an integrated Seller Center. Tokopedia’s own blog says it launched in June 2025, letting sellers manage operations across both from one dashboard, and that sellers can choose one platform or both (Tokopedia). Tokopedia’s integration page also states that commission fees are the same on both (Tokopedia seller integration page). Press coverage noted a mixed seller reaction, with some adjusting to sudden interface changes (Kontan).
For catalogue management this helps, because two channels can be handled in one place. It does not remove the need for your own master catalogue, since Shopee, Lazada, Blibli and others sit outside it. Rules and tools in this area change often, so verify the current behaviour in your seller center.
What goes wrong
- Bad source data. Syncing a messy catalogue just spreads the mess faster. Clean first, connect second.
- Overselling. Delayed or failed stock syncs. A safety buffer on fast-moving items is a common mitigation, at the cost of showing slightly less stock than you have.
- Price conflicts. Marketplace-run campaigns and your own central price can overwrite each other. Decide who wins before a big sale day.
- Rejected listings. Marketplaces can reject or take down listings for content or category reasons. Someone needs to watch for these.
- Access changes. Marketplaces change what third-party tools can do and how shops are authorised. Choose tools that are actively maintained.
- Over-automation. Auto-publishing without review can push a typo to five channels at once.
What it costs
Costs fall into three buckets, and none of them has a universal price:
- Cleanup: time to standardise SKUs, names and images. This is mostly your own team’s effort.
- Tooling: a subscription marketplace-management tool, a connector for your ERP, or a custom integration. Prices vary by vendor and volume, so ask for current quotes.
- Ongoing operation: someone owns the catalogue, reviews rejections and handles exceptions.
A rough rule: if you have a few dozen SKUs on two channels, spreadsheets with discipline can work. If you have hundreds of SKUs, variants, several channels and frequent price changes, a system becomes cheaper than the errors.
When to get help
Consider outside help when you are overselling regularly, when nobody is sure which price is current, when you are adding a third or fourth channel, or when your ERP and marketplace data no longer match. A short review of your catalogue structure and tool options usually clarifies whether you need a packaged tool, a connector or something custom.
If you would like to talk it through, Teknologia Solutions offers a no-charge conversation about your catalogue, channels and options. No obligation, and we will tell you plainly if a simple tool is enough.
Sources: Tokopedia: Seller Center launch, Tokopedia seller integration page, Kontan, Odoo documentation: product variants. Marketplace rules, fees and tool capabilities change often; verify against your seller center and each vendor’s current documentation before deciding.