eBay Inventory API vs Trading API: what the difference means for sellers who use bulk tools

eBay Inventory API vs Trading API: the short answer

The eBay Inventory API vs Trading API question matters to sellers because the API a bulk tool uses decides how it sees and changes your listings. An API (application programming interface) is the official channel software uses to talk to eBay instead of a person clicking in Seller Hub. The Trading API is eBay's traditional listing interface, built around the listing itself. The Inventory API is newer and built around your stock: you describe the product once, then publish an offer that becomes the listing.

You do not need to write code to care about this. It affects whether a tool can manage listings you already have, whether you need SKUs and business policies first, how variations are handled, and what happens if a tool converts your listings from one model to the other. This guide explains each point for eBay.co.uk and eBay.com sellers.

How does each API model a listing?

The Trading API: one listing, one item

In the Trading API, the listing is the thing you work with. A call adds an item with its title, description, price, quantity, category, photos and postage, and later calls revise or end that same item by its item number. eBay groups it with its traditional listing APIs, and it is how many older tools and many listings created over the years were built.

The Inventory API: item, offer and location

eBay's guide to managing inventory and offers describes three main parts:

• Inventory item: a record that defines a product, with a seller-defined SKU, product details, quantity and condition. eBay says an inventory item record must exist before an offer for that product is published.
• Offer: adds the marketplace, quantity, listing format, category, price and references to your payment, fulfilment and return policies. eBay says a published offer is the equivalent of an eBay listing.
• Location: eBay says a seller must have at least one inventory location set up before creating and publishing offers.

For multi-variation listings, an inventory item group holds related products that usually differ by one or two aspects, such as size or colour, with their shared title, description and images. Read eBay's guide on managing inventory and offers.

Inventory API vs Trading API side by side

What happens when a tool migrates your listings?

The Inventory API includes a call, bulkMigrateListing, that converts eligible active listings into the Inventory API model. eBay's migration guide sets out the conditions. Read them on eBay's migrating listings page; in short:

• The listing must use business policies; eBay says legacy payment, return policy and postage fields will not be accepted.
• Items need seller-defined SKUs, and each variation's SKU must be unique.
• The listing needs a postal code or city.
• eBay says the Inventory API only supports fixed price, Good 'Til Cancelled listings for migration; other formats or durations fail.
• The listing's inventory tracking method must be by item ID, not by SKU.
• Private listings are blocked.
• One call converts one to five listings, all from the same eBay marketplace.

A successful migration creates new inventory location, inventory item and offer records for the listing; a multi-variation listing gets an inventory item per variation plus an item group. eBay notes that some listing-level settings, such as buyer requirements and listing enhancements, stay on the listing but cannot be modified after migration.

Why this matters to you

Migration changes how the listing is represented in eBay's systems. Before any tool migrates your listings, ask it to show you exactly which listings will move, what happens to their SKUs and policies, and how your other tools, if you use more than one, will manage them afterwards. Test on a handful of listings first.

How do price and quantity updates differ for a bulk tool?

For sellers who reprice often, the most important work a tool does after listing is changing price and quantity, sometimes thousands of times a day. Both APIs can do it, but the path differs.

• Trading API tools revise the listing itself, identified by its item number, and for variations by the variation's details within that listing.
• Inventory API tools update the inventory item's quantity and the offer's price, identified by SKU and offer. eBay's Inventory API lists bulk versions of its item and offer calls, so one request can carry several changes.

Two things matter more to you than the path. First, eBay sets call limits for its APIs, published on its developer site, so a tool that updates every listing on a timer can run out of calls on a busy day. Ask how the tool decides which listings to update first, and what happens when it reaches a limit. Second, each change should be logged with its reason, whichever API carries it. If a price goes wrong, you need to know which tool sent it and why.

Two tools on one listing

The most common problem is not which API a tool uses but two tools changing the same listing. A listing tool and a repricer that both write prices will overwrite each other, and the last one to run wins. Give each listing one owner for price and stock, and switch the other tool's updates off for it. Our guide to the eBay bulk listing tool options covers batching uploads without that clash.

Which questions should you ask a bulk tool vendor?

You do not need to know how either API works in detail. You need clear answers to these questions, and a vendor that can give them.

1. Which API do you use to create listings, and which to update price and quantity? Many tools use more than one.
2. Can you manage listings I made in Seller Hub or with another tool? If not, you may need to recreate or migrate them.
3. Do my listings need SKUs or business policies first? If so, set them up before connecting the tool.
4. Will you migrate any listings? If yes, which ones, and can you show me a test on five first?
5. How do you handle variations? Each variation should keep its own SKU, price and quantity.
6. What happens to my listings if I stop using you? Your listings stay on eBay, but check whether they will be easy to manage with another tool.
7. How do you sign in to eBay? Through eBay's official consent screen, never with your password.

Our guide to the eBay API for sellers explains how tools use eBay's APIs in plain terms.

A worked example: choosing between two bulk tools

Example, with hypothetical details: you have 1,200 fixed price listings, made over three years in Seller Hub, half without SKUs and some still using old postage settings rather than business policies. You compare two tools.

Tool A uses the Trading API to revise price and quantity by item number. It can manage your listings as they are, from day one. Tool B is built on the Inventory API and offers to migrate your listings. To use it, you first add SKUs to 600 listings and move the rest to business policies, then migrate in batches of up to five per call, which the tool runs for you.

Neither is wrong. Tool A is quicker to start. Tool B may suit you better if you want SKU-based stock across several channels. The point is to know which path you are on before you connect anything, and to test five listings before touching 1,200.

Do you need to choose an API yourself?

Usually not. If you list through Seller Hub, eBay handles this for you. The choice matters when you pick software, and when you switch from one tool to another. Our step-by-step plan for switching tools without gaps includes checks for listings that one tool made and another must manage.

Whatever the API, the listings still have to follow eBay's rules, from the 80 character title limit to the picture policy. If you list items you do not hold, eBay's drop shipping policy allows fulfilling orders directly from a wholesale supplier but not buying from another retailer or marketplace that ships directly to your buyer; an API changes nothing about that.

What to do next

• Check whether your listings have SKUs, and whether they use business policies.
• Write down which tools touch your listings today and which API each one uses.
• Before any migration, ask for a five-listing test and check the results in Seller Hub.
• Keep a list of listings each tool manages, so two tools never fight over one listing.