Linnworks eBay Integration UK: How to Set It Up, What Breaks, and How to Fix It
Linnworks and eBay connect via eBay's Trading API — no manual API keys, just an OAuth authorisation that takes under five minutes. After that, orders flow from eBay into Linnworks automatically, stock levels push back out, and tracking confirmation uploads when you despatch. Most of the time, it works cleanly.
When it doesn't, it fails silently. Tracking doesn't upload. Orders sit at "awaiting dispatch" in eBay even though Linnworks shows them as despatched. The API returns success codes on both ends and there's no error message in either system. If you don't catch it, eBay flags the late tracking as a seller defect — and your account metrics take the hit with no warning at all.
This guide covers the full integration: what it does, how to set it up, the specific failure modes that catch UK merchants out, and how to verify it's working properly. If you'd rather hand the setup to Linnworks integration specialists who've done it before, we can help with that too.
What the Linnworks–eBay Integration Actually Does
Before troubleshooting anything, it helps to understand what syncs, in which direction, and via which API.
- New orders (polling every 5 minutes)
- Order status updates (paid, cancelled)
- Buyer shipping address and details
- Payment confirmation before order download
- Stock level updates (push every 15 minutes, default)
- Shipping confirmation and tracking number
- Carrier name (must match eBay's accepted list exactly)
- Despatch notification trigger
- eBay listing titles and descriptions
- Promoted listings data
- Feedback and reviews
- Return/refund signals (manual reinstatement required)
Architecture note: The eBay integration uses Linnworks' direct channel connection via eBay's Trading API and Merchant Fulfilment API — not a REST API key like WooCommerce, and not an App Store OAuth install like Shopify. Authentication is eBay's own OAuth flow, initiated from within Linnworks. Once authorised, no manual API key management is required.
Order polling runs every 5 minutes. Stock push runs every 15 minutes by default. Both are configurable in Linnworks → Settings → Channel Integration → eBay → Channel Settings.
Setup: Connecting Linnworks to eBay UK Step by Step
Prerequisites: Linnworks Standard or above, an eBay Seller account with API access enabled, and the UK marketplace selected. Linnworks Basic does not support multi-channel integrations.
- In Linnworks: Settings → Channel Integration → Add Channel → eBay
- Click Authorise — redirects to eBay's OAuth consent screen
- Log in to eBay Seller Hub and grant Linnworks API access
- Returned to Linnworks — channel appears in your list
- Assign your Linnworks warehouse to the eBay channel
- Set order download rules: default is "paid" — confirm not set to "pending"
- Review carrier settings (see Section 3 — this is where most problems start)
- Enable Auto Upload Tracking: Settings → Channel Integration → eBay → Channel Settings → tick "Auto Upload Tracking"
SKU matching: Linnworks maps products to eBay listings using the eBay listing's Custom Label field — eBay's equivalent of a product SKU. The Custom Label value must match your Linnworks item SKU exactly, including case. If they don't match, Linnworks cannot update stock or despatch confirmation for that listing.
This is the same case-sensitive SKU matching rule as the Linnworks Magento integration and other channels. The difference is eBay uses "Custom Label" as the field name — which catches merchants who set up eBay listings without populating Custom Labels. Check every active listing in eBay Seller Hub → Inventory and confirm the Custom Label column is populated. Any blank Custom Label means Linnworks cannot sync that product.
The Carrier Code Problem: Why eBay Shows "Awaiting Dispatch" When Linnworks Says Despatched
This is the most common silent failure in the Linnworks–eBay integration, and the one that does the most damage.
Linnworks stores carrier names using its own internal format. eBay's Merchant Fulfilment API requires an exact string match from eBay's accepted carrier code list. The two don't always align.
Example: Linnworks stores the carrier as ROYAL_MAIL. eBay's accepted carrier code is Royal Mail.
What happens: Linnworks sends the tracking upload to eBay's Merchant Fulfilment API. The API returns HTTP 200 — success. But because the carrier code string doesn't exactly match eBay's list, eBay silently rejects the carrier mapping. The order status never updates to "shipped."
The merchant sees "Despatched" in Linnworks. The customer sees "Awaiting Dispatch" in eBay. No error is raised in either system. Nothing alerts you that anything went wrong.
Why this causes seller defects: eBay's dispatch tracking window runs from payment — not from when you actually despatch. If tracking isn't confirmed within 3 days of payment, eBay auto-flags the order as a late despatch: a seller defect on your account. During Black Friday or peak sale periods, a carrier code mismatch can generate defects at scale before anyone notices.
How to diagnose it:
- Go to Linnworks → Settings → Shipping → Carriers — note the exact string stored for each carrier you use
- Cross-reference against eBay's accepted carrier code list — strings must match character-for-character, including capitalisation
- Check Linnworks → Settings → Channel Integration → eBay → Channel Log — filter for tracking upload attempts and examine response codes
- Look for HTTP 207 (partial success) in the Merchant Fulfilment API response — this means some line items failed. HTTP 207 means the call was accepted but not all items succeeded. Most merchants never check for this and miss it entirely.
- In eBay Seller Hub → Orders: check the "Tracking uploaded" column. Orders with a Linnworks despatch date but no tracking in eBay Seller Hub confirm the carrier code problem.
- Verify carrier code exact string match: Linnworks Shipping Carriers → compare each carrier name against eBay's accepted carrier code list character-for-character. Update Linnworks carrier name to match eBay's exact string.
- Confirm Auto Upload Tracking is enabled: Linnworks → Channel Settings → eBay → "Auto Upload Tracking" ticked, cron frequency confirmed (default 15 minutes)
- For multi-warehouse merchants: Enable "Dispatch when all locations shipped" in Linnworks Rules Engine (see next section)
- Check Diagnostics for HTTP 207 after the next high-volume period — confirms whether Merchant Fulfilment API calls are fully succeeding or quietly failing on individual line items
If you've hit this problem and need it diagnosed properly, our Linnworks consultants have fixed this specific issue on multiple UK eBay accounts.
Multi-Warehouse Partial Fulfilment: Why eBay Orders Get Stuck
If you fulfil from multiple Linnworks warehouses, there's a second, separate cause for "awaiting dispatch" — distinct from the carrier code issue.
When an eBay order contains multiple SKUs fulfilled from different warehouses, Linnworks won't send the despatch confirmation to eBay until all warehouse picks are complete. If one warehouse has despatched its items but another hasn't, Linnworks holds the despatch status. eBay sees nothing — the order stays at "awaiting dispatch" even though most of it is already on its way.
In Linnworks: Settings → Rules Engine → Add Rule
Set the condition to trigger the despatch signal to eBay only when all fulfilment locations for an order are marked as shipped. Without this rule, a partial despatch trigger may be sent that eBay rejects — leaving the order in "awaiting dispatch" indefinitely.
Particularly important for merchants where a single eBay order pulls from a primary warehouse and a secondary returns or overflow location.
eBay-specific oversell risk: Because Linnworks pushes stock updates to eBay every 15 minutes by default, there's a window where a fast-moving item can sell on both eBay and another channel within the same push cycle. This is structurally the same risk as in the Linnworks Shopify integration, but more acute for high-velocity marketplace sellers with limited stock of popular lines. Practical fix: reduce stock push frequency for high-velocity SKUs, or set a safety buffer stock count in Linnworks channel settings.
eBay-Specific Linnworks Behaviour You Need to Know
eBay enforces API rate limits on order polling and tracking uploads. During high-volume periods — Black Friday, Boxing Day, January sales — a 429 Too Many Requests response triggers Linnworks' exponential backoff: retry intervals extend to 30–60 minutes. Combined with eBay's 3-day tracking window (running from payment, not despatch), peak-period delays can silently push orders past the defect threshold. Check channel logs after every busy trading period.
When Linnworks pushes the despatch signal to eBay, eBay sends the buyer their notification — not Linnworks. Buyers receive a standard eBay "Your order has shipped" message. Linnworks is the trigger; eBay owns the communication. Any tracking link customisation or buyer messaging needs to be handled in eBay Seller Hub, not in Linnworks.
eBay returns and refunds do not automatically reinstate stock in Linnworks. When a buyer opens a return via eBay, Linnworks receives no stock-back signal. Every return quietly understates your actual available stock unless you have a manual reinstatement process or a custom return flow rule. This is the same behaviour as in the Linnworks WooCommerce integration — different channel, same return blind spot.
Linnworks can push product titles, descriptions, and price updates to eBay via the channel listing tool. In practice, most UK merchants use eBay Seller Hub for listing management and Linnworks for fulfilment only — cleaner, and eBay Seller Hub gives better control over listing quality, promoted listings, and category-specific requirements. Use Linnworks for what it does best: stock master and despatch.
Before You Go Live: 8-Point eBay Pre-Launch Checklist
Run this before your first live order. The carrier code check is the most important — it causes silent failures that won't surface until you're already accumulating seller defects.
- SKU match verified: Every active eBay listing has a Custom Label exactly matching the Linnworks item SKU — case-sensitive, no trailing spaces
- Carrier code verified: Linnworks shipping carrier string exactly matches eBay's accepted carrier code list character-for-character (check all carriers, not only Royal Mail)
- Auto Upload Tracking enabled: Linnworks → Channel Settings → eBay → "Auto Upload Tracking" ticked, cron frequency confirmed
- Order download rule confirmed: Set to trigger on "paid" status — not "pending"
- Warehouse assigned: Linnworks warehouse correctly mapped to the eBay channel
- Test order placed: Process a low-value test order end-to-end through Linnworks. Confirm tracking uploads to eBay Seller Hub within 15 minutes. Verify order status updates to "shipped" in eBay — not just "despatched" in Linnworks.
- Multi-warehouse rule set (if applicable): "Dispatch when all locations shipped" configured in Linnworks Rules Engine
- HTTP 207 check: After first live orders, check Linnworks Diagnostics for HTTP 207 partial success responses on Merchant Fulfilment API calls — confirms whether tracking uploads are fully completing or quietly failing on individual line items
When to Use a Linnworks eBay Specialist
- Single Linnworks warehouse
- Single eBay account (UK marketplace)
- Standard carrier setup (Royal Mail, DPD, Evri)
- Low to medium order volume
- Technical resource available in-house
- Multi-warehouse fulfilment with split orders
- High-volume eBay with seller metric risk
- Top Rated Seller status to protect
- eBay + Amazon + storefront via same Linnworks stock master
- Existing "awaiting dispatch" problem not resolved by checklist
- Carrier code mismatch already generating seller defects
Seller defects affect your eBay account standing, Top Rated Seller status, and search visibility within eBay's marketplace algorithm. By the time defects are accumulating, you've already lost revenue from suppressed listings.
If you're running eBay alongside other channels through the same Linnworks account, maintaining a clean stock master across all channels during the 15-minute push windows is a multi-channel architecture question as much as an eBay integration question. That's where a specialist setup pays for itself.
: our guide to Linnworks Amazon integration — covering FBA vs FBM order routing, SP-API authentication, and how Linnworks handles Amazon's stricter rate limits and data requirements.
Whether you're setting it up for the first time or diagnosing a carrier code problem generating seller defects, we've dealt with this before.
Talk to a Linnworks specialist →