CDON is a genuinely different market from Shopee or Lazada -- Nordic buyers with Nordic payment and delivery expectations versus Southeast Asian marketplaces with their own scale, fee structures, and fulfillment norms. Sellers usually add these because the addressable market is real, not as an afterthought -- but each one is a fully separate integration with its own order format, its own fee reporting, and its own operational quirks.
What's actually different about each
CDON operates primarily in Sweden, Norway, Denmark, and Finland, with Nordic-specific delivery and payment method expectations that don't map directly onto a Western European setup. Shopee and Lazada both operate at very high order volumes across Southeast Asian markets (Singapore, Malaysia, Indonesia, Thailand, Vietnam, Philippines, depending on which you connect to), with their own seller-center APIs, campaign/promotion mechanics, and settlement cycles that are structurally different from European marketplaces.
The common failure mode when adding these without proper integration: treating them as "just another marketplace" and bolting them onto a system that assumes European order/fee patterns, which usually means someone ends up handling CDON, Shopee, or Lazada orders as a manual exception rather than a properly connected channel.
What a proper integration actually needs
The same three things that matter for any marketplace -- order sync, stock sync, and payout reconciliation -- but built against each platform's actual API and settlement format rather than approximated from a generic template. For high-volume platforms like Shopee and Lazada specifically, sync latency matters even more, since order volume amplifies the cost of any manual gap.
How Vedron handles this
CDON, Shopee, and Lazada each connect through their own respective seller/marketplace APIs into the same underlying order, stock, and settlement-reconciliation model used for every other connected channel -- so a sale on any of them decrements shared stock immediately and its settlement is parsed and reconciled the same way Amazon's or Allegro's is, rather than requiring a separate manual process per platform. That's consistent with how every marketplace integration in Vedron works: connect the platform's actual API, write into the same shared data model, and let the existing stock/order/reconciliation logic apply automatically -- not rebuilt per marketplace.
Frequently asked questions
Can I connect just one of these three, not all of them?
Yes -- each connects independently; you're not required to add all three together, and can start with whichever market you're actually expanding into.
Do these marketplaces need separate invoicing/VAT handling?
Depends on where you and your buyers are located -- CDON sales into Nordic EU countries follow standard EU VAT/invoicing rules; Southeast Asian marketplace sales depend on your own business's tax registration and the specific market's requirements, which is worth checking against your own situation rather than assuming one rule fits all four countries.
How does stock work if I'm also fulfilling through a platform-specific warehouse program?
Platform-held stock (similar in concept to Amazon FBA) is tracked as its own pool, physically separate from your own warehouse, but still rolls into the same product's total availability across every connected channel.
Have a question specific to your setup?
Every seller's marketplace mix and stock setup is a little different -- if you're weighing this against your own, book a short call and we'll walk through it with you directly rather than leaving you to figure it out from a blog post alone.
Beta offer: if you join as a beta client, custom integration setup -- configured for your actual marketplace and inventory mix -- is free for your first 2 months.
Still evaluating and need more time than the standard trial window? Just ask us for an extension -- we're happy to give you the room to actually test it properly before deciding.