Trade Me vs WooCommerce vs eBay: The Inventory Synchronisation Problem
Sell auto parts on Trade Me, a WooCommerce store and eBay at once and you triple your exposure — and you create three separate opinions about what is in stock. Multi channel inventory sync is the discipline of keeping those opinions identical in near real time. Get it right and each channel is a pure upside; get it wrong and you spend the extra revenue on refunds, apologies and reconciliation. This guide compares how the three channels behave and lays out an architecture that keeps them in agreement.
Why inventory fragments across channels
Each platform maintains its own inventory state and exposes it differently:
- Trade Me — listing-centric. A quantity-one part is a listing that closes when it sells. Withdrawal of unsold stock is an explicit API call. Listings expire on a duration.
- WooCommerce — product-centric with a stock quantity and status. Fully controllable via REST API and webhooks, but it is only as accurate as whatever writes to it.
- eBay — offer/inventory model with its own quantity and fulfilment rules, and its own latency.
Three models, three update mechanisms, three latencies. Without a layer that reconciles them, they drift the moment the first sale lands on any one of them.
The business impact of drift
- Overselling — the same quantity-one part sells twice; one buyer gets a refund and a bad experience.
- Stale listings — sold parts stay live, wasting fees and generating dead-end enquiries.
- Reconciliation labour — someone spends hours a week comparing channels and patching differences.
- Reputation — Trade Me and eBay both weight seller reliability; cancellations have lasting cost.
Why point-to-point syncing doesn’t scale
Connecting channels directly to each other — Trade Me to WooCommerce, WooCommerce to eBay, eBay to Trade Me — means the number of connections grows with every channel you add, and there is no agreed source of truth, so conflicts have no resolution rule. It works with two channels and collapses at four.
The scalable pattern is hub-and-spoke: one source of truth, every channel synced to it. This is the model behind our auto parts API pipeline guide.
The recommended architecture
- Source of truth — usually your yard/DMS or ERP. It holds the authoritative quantity and status for every part.
- Stable identifier — one SKU/stock number maps a part to its listing on every channel.
- Inbound events — order notifications from Trade Me and eBay, webhooks from WooCommerce, all feeding the hub in near real time.
- Immediate propagation — a sale anywhere decrements the source of truth and updates or withdraws the part on every other channel within a minute or two.
- Scheduled reconcile — a background job compares each channel to the source of truth and corrects drift, alerting on what it fixes.
- Order consolidation — all channel orders land in one fulfilment queue; see syncing Trade Me orders to your ERP.
Implementation considerations
- Latency budget — define an acceptable propagation time and monitor it; overselling lives in the gap.
- Conflict rules — simultaneous sales of one part need a deterministic winner.
- Per-channel quirks — Trade Me withdrawal vs eBay quantity zero vs WooCommerce out-of-stock all need channel-specific handling.
- Missed events — assume webhooks fail sometimes; the reconcile job is the safety net.
- Category and content per channel — each marketplace needs its own taxonomy mapping and listing format.
Common mistakes
- Point-to-point connections with no hub — unmanageable past two channels.
- Scheduled-only sync — the interval is the oversell window.
- No reconcile job, so missed events become silent drift.
- Matching on title or price instead of a stable identifier.
- Adding a channel without adding its taxonomy and content mapping.
Where Partsyncer fits
Partsyncer.com is the hub in a hub-and-spoke setup for auto parts sellers. It takes one inventory source, generates channel-appropriate listings with AI titles and images, and keeps Trade Me, WooCommerce and other channels synced in near real time — propagating every sale, consolidating orders, running a reconcile safety net, and relisting eligible expired listings. Adding a channel means adding a spoke, not another point-to-point connection.
If multi channel inventory sync between Trade Me, WooCommerce and eBay is a constant firefight, explore Partsyncer.com.
A worked example
A seller adds eBay as a third channel. In a point-to-point setup they now need connections for Trade Me↔eBay and WooCommerce↔eBay on top of the existing Trade Me↔WooCommerce link — and no rule for what happens when two of them disagree. In a hub-and-spoke setup they add one spoke: eBay syncs to the same source of truth as the other two. A sale on any channel propagates to the other two through the hub, orders land in the same queue, and the reconcile job now checks three channels instead of two.
Frequently asked questions
Why not connect the marketplaces directly to each other?
The number of connections grows with every channel, and there is no source of truth to resolve conflicts. It works with two channels and breaks at four.
What should the hub be?
Your yard/DMS system or ERP — wherever stock is authoritatively managed. Every channel becomes a spoke synced to it.
How are the platform differences handled?
Per-channel adapters: Trade Me withdrawal, eBay quantity-zero, WooCommerce out-of-stock are all triggered by the same “part sold” event.
Do I need real-time sync or is scheduled enough?
Real-time sale events for anything quantity-one; a scheduled reconcile as the safety net. Scheduled-only sync leaves an overselling window.