Integrating AutoCount With Shopee / Lazada / TikTok Shop
Short answer: An AutoCount marketplace integration pulls confirmed orders from Shopee, Lazada, or TikTok Shop automatically, creates sales invoices, deducts stock, and pushes fulfilment updates back — replacing a manual keying process that typically takes 30–90 minutes per day and produces regular errors.
Why Manual Sync Fails at Scale
At low order volumes, copying orders from a marketplace dashboard into AutoCount is manageable. At 50+ orders per day across two or three platforms, it stops working. The problems compound:
- Stock quantities in AutoCount lag behind actual sales, leading to overselling
- Invoice creation falls behind packing and shipping, making accounts reconciliation painful
- Staff entering data across platforms introduce inconsistencies in product codes and customer records
- Returns and cancellations require manual reversal entries
Multichannel inventory management breaks down specifically at this sync point — not because of how the warehouse operates, but because the data bridge between the marketplace and the ERP is manual.
How a Proper Integration Works
A marketplace-to-AutoCount integration operates on an event-driven basis:
| Trigger | Action in AutoCount |
|---|---|
| Order confirmed on marketplace | Sales order or invoice created automatically |
| Order packed and shipped | Delivery order generated, stock deducted |
| Payment received from platform | Payment entry recorded against invoice |
| Return or cancellation processed | Credit note or reversal created |
The sync runs continuously — typically every few minutes — so AutoCount stock figures stay current throughout the day. Staff in the warehouse see accurate pick quantities; finance sees invoices without chasing the ops team.
What AutoCount's Standard Setup Handles (and Doesn't)
AutoCount has an e-commerce plugin, but it handles specific marketplace APIs and may require additional configuration for TikTok Shop, which has a different API structure from Shopee or Lazada. The standard plugin also doesn't handle all edge cases: bundled products, platform vouchers affecting net revenue, marketplace-specific SKU mapping, or multi-warehouse allocation logic.
For trading companies running across three or more channels with complex product catalogues, a custom integration via the AutoCount e-commerce sync layer is more reliable than stretching the default plugin.
SKU Mapping: The Hidden Complexity
Shopee, Lazada, and TikTok Shop each have their own product ID systems. Your AutoCount uses its own item codes. Connecting them requires a mapping table — which product on which platform corresponds to which AutoCount item code.
This sounds simple until you have product variations (size, colour, pack size), bundles that don't exist as separate AutoCount items, or products listed under different names across platforms. Getting the mapping right before go-live is what separates a clean integration from one that creates more problems than it solves.
FAQ
Can one integration handle all three marketplaces simultaneously?
Yes. A single integration layer can connect Shopee, Lazada, and TikTok Shop to AutoCount in parallel. Each platform has its own API credentials and event stream, but they all write into the same AutoCount company database.
What happens when an order is cancelled after stock has been deducted?
A properly built integration handles reversals automatically — a cancellation event triggers a credit note or stock adjustment in AutoCount. Without this, cancelled orders silently create phantom stock reductions.
Do I need AutoCount plugins, or is this done through the API?
Both approaches are used depending on the setup. AutoCount exposes an API that allows external systems to create transactions programmatically. Custom integrations typically use this rather than relying solely on plugins, which gives more control over error handling and edge cases.
Book a System Audit