# Amazon and eBay Marketplace Integration UK

Source: https://dijituldevelopments.co.uk/marketplace-integration/
Updated: 2026-10-10

> dijitul developments builds Amazon and eBay marketplace integrations for UK sellers, using the Amazon Selling Partner API and eBay's REST Sell APIs to sync listings, stock, prices and orders with your website, ERP or warehouse system. It's built around your rules, not a generic tool's, and quoted at a fixed price after a free chat.

## Problems this solves

- Stock is adjusted by hand on Amazon, eBay and the website, and something always oversells
- Marketplace orders are downloaded as CSVs and keyed into the warehouse system
- Your multichannel tool can't handle bundles, kits or your SKU structure
- Listings broke when Amazon retired the old flat file feeds
- Tracking numbers reach eBay late and your seller metrics suffer
- Nobody can reconcile marketplace payouts against orders and fees

## Key facts

- Amazon integrations use the Selling Partner API (SP-API), authorised with Login with Amazon (LWA) OAuth tokens
- Since 2 October 2023, SP-API no longer requires AWS IAM or Signature Version 4 request signing (Amazon developer changelog)
- Amazon's Feeds API stopped accepting legacy XML and flat file listings feeds on 31 July 2025; listings now use the Listings Items API or JSON_LISTINGS_FEED
- eBay integrations use the REST Sell APIs (Inventory, Fulfillment, Finances) with OAuth 2.0 user tokens
- eBay requires every developer app to handle Marketplace Account Deletion notifications or formally opt out
- Stock is allocated across channels from one source, with optional per-channel buffers
- Orders from every marketplace land in one place with consistent SKUs, VAT and shipping data

## One stock figure, many channels

Selling on Amazon and eBay as well as your own website multiplies the admin. Each channel has its own stock number, its own order screen and its own idea of what a product is. The usual result is overselling on one channel while stock sits unused on another, and a member of staff whose job is mostly copying numbers between tabs.

A marketplace integration makes one system the source of truth for stock, usually your ERP, warehouse system or main shop, and pushes availability out to each channel automatically. Orders come back the other way into the same place, so picking, dispatch and invoicing work the same regardless of where the sale happened. We've been building stock feeds and bulk product loaders since our early OpenCart work, and marketplaces are the same problem at a larger scale.

## Amazon: the Selling Partner API

Amazon's current interface is the Selling Partner API. Requests are authorised with Login with Amazon access tokens, which are exchanged from a long-lived refresh token. According to Amazon's developer changelog, since 2 October 2023 SP-API no longer needs AWS IAM roles or Signature Version 4 signing, which simplified things considerably.

- **Orders API** and order notifications to fetch new orders, with restricted data tokens where buyer address data is needed for dispatch.
- **Listings Items API** and the `JSON_LISTINGS_FEED` feed type for creating and updating listings. Amazon stopped accepting the legacy XML and flat file listings feeds on 31 July 2025, so older integrations built on them need moving across.
- **Product Type Definitions API** to know which attributes each category requires.
- **Reports and Finances APIs** for inventory snapshots, settlements and fee breakdowns.

SP-API uses per-operation rate limits, so we queue calls and back off on 429 responses rather than hammering the endpoint.

## eBay: the REST Sell APIs

eBay's modern interface is a set of REST APIs authorised with OAuth 2.0. The **Inventory API** manages inventory items and offers, the **Fulfillment API** retrieves orders and records shipments, and the **Finances API** exposes payouts and transaction fees. Some older sellers still run on the legacy Trading API; we can maintain that or migrate it. eBay's Notification API pushes events to a webhook endpoint, and every eBay developer app must subscribe to Marketplace Account Deletion notifications (or apply to opt out if it stores no eBay user data). We handle that as part of the build so your keys aren't restricted.

## Rules that generic tools miss

Off-the-shelf multichannel tools are a sensible starting point, and if one fits your business we'll say so. Where we usually come in is when the rules get specific:

- Bundles and kits, where a listing's availability depends on several component SKUs.
- Channel buffers, for example holding back stock on Amazon during a website promotion.
- Different prices per channel calculated from cost, fees and a target margin.
- Orders routed to different warehouses or drop-ship suppliers by product.
- Payout reconciliation matched against your accounts package, which ties in with [accounting software integration](https://dijituldevelopments.co.uk/accounting-software-integration/).

## Getting product data right

Most listing errors come from product data rather than code. Amazon defines the attributes each category needs through the Product Type Definitions API, and eBay publishes required and recommended item specifics per category through its Taxonomy API. We read those requirements and validate your data before it's sent, so problems are caught on our side with a clear message rather than coming back hours later as a feed processing error.

We also handle barcodes (GTIN, EAN and UPC), brand and manufacturer part numbers, variation families such as size and colour, and image rules. Where your product data lives in a spreadsheet or an old system, we can build a simple product information screen or import routine so the marketplace data has one tidy source. It's the same bulk product loading work we started doing for OpenCart shops, applied to stricter marketplaces.

## How a project runs

We start with a short scoping stage: which channels, which system owns stock, how SKUs map, and what has to happen when something fails. Then we build the integration as a small service, usually PHP 8 with Laravel or Node.js with TypeScript, with queues in Redis or the database. You get a dashboard showing every order and stock push, with a retry button for anything that failed. For the back-office side see [ecommerce and ERP integration](https://dijituldevelopments.co.uk/ecommerce-erp-integration/).

Every project is a fixed-price quote after a free chat. [Get in touch](https://dijituldevelopments.co.uk/contact/) to start.

## What we deliver

- Order import from Amazon and eBay into your shop, ERP or warehouse system
- Stock and price sync out to each channel, with buffers and channel rules
- Listing creation and updates via the Listings Items API or eBay Inventory API
- Dispatch confirmation and tracking upload to each marketplace
- Settlement and payout reports matched to orders and fees for your accounts
- Bundle and kit logic so component stock drives listing availability
- Monitoring, rate limit handling and a failed-message dashboard

Technologies: Amazon SP-API, Login with Amazon (LWA), eBay Inventory API, eBay Fulfillment API, eBay Notification API, Laravel, Node.js, Redis

## FAQs

### Do I need to be a registered Amazon developer for a private integration?

Yes. A private SP-API application is registered in Seller Central under your account, and you authorise it to access your seller data. dijitul helps you through the registration and the data protection questions Amazon asks.

### Our Amazon listings stopped updating in 2025. Why?

Amazon's Feeds API stopped accepting legacy XML and flat file listings feeds on 31 July 2025. Integrations still using them need moving to the Listings Items API or the JSON_LISTINGS_FEED feed type. dijitul can migrate an existing integration.

### Can you stop us overselling across eBay, Amazon and our website?

That's usually the main goal. We make one system the source of truth for stock, push changes to each channel quickly, and add per-channel buffers for fast-moving lines so the gap between a sale and the next sync can't cause an oversell.

### Can marketplace orders go straight into our warehouse system?

Yes. dijitul imports Amazon and eBay orders into your ERP, warehouse system or main shop with consistent SKUs, addresses and VAT, then sends tracking numbers back to the marketplace when the order is dispatched.

### Should we use a multichannel tool instead?

If an off-the-shelf tool handles your SKUs, bundles and warehouse setup, it's often the cheaper option. Custom integration makes sense when your rules don't fit, or when the tool's fees grow with order volume. We'll give an honest view in the free chat.

### Can you integrate other marketplaces too?

Most marketplaces such as OnBuy, ManoMano or Etsy offer REST APIs with similar patterns. dijitul checks the API documentation and access rules during scoping, then includes them in the fixed-price quote.

## Pricing and contact

Every project gets a fixed-price quote after a free initial chat and a short scoping stage. You own the code and the data. Book a free chat: https://dijituldevelopments.co.uk/contact/ · 01623 650333 · info@dijitul.uk