E-commerce and marketplaces
eBay integration consultant: listings, stock and orders kept in step
SBD builds eBay integrations for sellers with teams of 1 to 1,000 people: listings pushed from one master record, stock kept in step with your other channels, and orders, returns and payouts carried into your operations and ledger, within eBay's call limits. Workflow automation builds start at $1,000, with the fixed price set after a $500 Automation Audit that is credited to the build.
- Tool
- ebay.com
- Usually paired with
- Shopify, Airtable, WooCommerce, QuickBooks
- Timeline
- Most builds live in 2 to 8 weeks
- Owned by
- You, with accounts, credentials and code in your name.
What we build on eBay
- Sync listings, stock and prices from one product record
- Pull orders into your fulfilment system
- Prevent oversells across channels
- Handle listing errors with a review queue
What we sync
Workflows we are asked for
- Shopify to eBay inventory sync
- eBay orders into the fulfilment flow
- eBay listing creation from a product base
- eBay price updates by channel
Full write-ups of eBay integrations
Tools eBay usually needs to talk to
-
eBay and Shopify
The storefront for most of the e-commerce businesses we work with.
-

eBay and Airtable
A relational database with a spreadsheet face, used as the operations base for teams who have outgrown sheets.
-

eBay and WooCommerce
The WordPress store, flexible and usually extended with plugins.
-
eBay and QuickBooks
Intuit's accounting platform for small and mid-size companies, with an API that needs careful handling.
What an eBay integration from SBD does
eBay is usually one channel among several.
The pain is keeping it in step with the others: a product changes and someone edits five listings, an item sells on one channel and stays live on eBay, and orders, returns and fees are pulled out by hand for the accountant.
Typical builds are listings created and updated from a master product record, with eBay's titles, categories, item specifics and images fitted to its rules; stock synced from whichever system owns it, so a sale anywhere updates the eBay quantity; orders pulled into an operations or dispatch system and marked shipped with tracking; and returns, cancellations and payouts carried into the ledger.
We have built this. For a watch reseller we built a product sync across Shopify, eBay and Chrono24, with SmartSuite holding the master record and Make translating each change into every channel's format, including eBay's title, category and image rules. Product updates take 80% less time, and a sale anywhere updates stock everywhere.
When a custom integration beats a listing tool
A good fit
Multichannel listing tools and eBay's own apps cover the common case of one catalogue on a few channels. If one fits your catalogue and volumes, it will cost less than a build, and we will say so in the audit.
A custom integration is worth it when
- Your master record lives in your own system, such as Airtable, SmartSuite, an ERP or a database, and every channel should follow it.
- Items are unique or semi-unique, so stock is one or zero and an oversell is a cancelled order and a defect on your account.
- Each channel needs different titles, descriptions, images or prices from the same record.
- Orders, returns and payouts must reach your ledger and dispatch system with your own rules applied.
eBay API call limits and OAuth tokens
eBay sets default daily call limits per API, designed, in its words, for individuals and smaller businesses
From eBay's call limits page in October 2026: the Inventory API allows 2 million calls a day; the Fulfillment API allows 100,000 calls a day on its order resource; the Feed API 100,000; the Account API 25,000; the Finances API 15,000; the Notification API 10,000; and the legacy Trading API 5,000. Each Post-Order resource, including cancellations, returns, inquiries and cases, has its own limit of 5,000 calls a day. Higher limits are available after an Application Growth Check, in which eBay reviews whether the application follows its licence agreement and uses the APIs efficiently.
The Trading API limit is the one that catches older integrations
A sync built on it that updates listings one by one can run out of calls on a busy day, while the same work through the Inventory API has far more headroom. eBay also now offers GraphQL APIs as generally available, with limits set per operation rather than per API; we choose per integration based on what each operation allows.
Authentication for seller data uses OAuth
A user access token is valid for 7,200 seconds, two hours, and is renewed with a refresh token. In eBay's documented example the refresh token is valid for 47,304,000 seconds, roughly 18 months, after which the seller must authorise the application again. We store the expiry date, alert a named owner well before it, and write the reconnect steps into the runbook, because an expired token stops listings and orders at once.
eBay requirements and data gotchas
Every application on the eBay Developers Program must either subscribe to marketplace account deletion notifications or formally opt out if it stores no eBay data. New applications must do one or the other before their first production API call, and eBay states that failure to comply can end access to its developer tools or reduce API access. An integration that stores buyer names and addresses for dispatch must subscribe, verify its endpoint with eBay's challenge code, and delete the data when told. We build that endpoint as part of every eBay integration.
- Inventory items, offers and listings are separate objects in the Inventory API. A product becomes a listing only when an offer is published, and each needs its own handling.
- Item specifics and categories differ by marketplace and change over time; the mapping is checked against eBay metadata rather than typed once.
- Listings created through the Inventory API and listings created in Seller Hub or older tools are managed differently, so a migration plan is needed before switching.
- Order totals, eBay fees and payouts arrive through different APIs on different days, and the ledger mapping must allow for that.
- Buyer personal data is kept only as long as dispatch and accounting require, and is removed on a deletion notice.
How an eBay engagement with SBD works
- Step 1$500Automation AuditCredited to the build
- Step 2from$1,000Workflow automationFixed after the audit
- Step 3from$3,000Internal toolsFixed after the audit
- Step 4from$50Care planA month, after sixty days of hypercare
Every engagement starts with an Automation Audit at $500, credited in full to your build. For eBay we look at how listings are created today, which APIs or tools are in use, how many calls a day the sync will need, and how orders, returns and payouts reach the rest of the business. You get a ranked list of fixes with fixed prices and a blueprint for the first build.
Workflow automation builds start at $1,000, internal tools at $3,000 and multi-module systems at $5,000. We build on Make, n8n, Supabase or custom code, test in eBay's sandbox where the APIs allow, and release changes to a few listings before the whole catalogue. Cancellations, refunds and first-time buyer messages wait for a person to approve them. Work runs in two-week sprints, sixty days of hypercare follow go-live, and care plans start at $50 a month. See the pricing page.
eBay seller fees and any paid listing tools are paid by you to eBay or their vendors. We do not resell either.
What you own, and moving off a listing tool
Everything below is in your name when the build ends.
- The developer account, application keys, user tokens and workflows are created in your name.
- You receive the channel mapping that says how each field in your master record becomes an eBay title, category, item specific, price and image set; a runbook per integration that says what failure looks like and who is alerted; and the token renewal procedure, with the date each seller token is due.
- Many sellers come to us from a multichannel listing tool they have outgrown, or from a sync built years ago on the Trading API.
- We map the listings that exist, decide which can move to the Inventory API and which should stay as they are for now, and migrate in batches with a short pause on edits for each batch.
- Stock is checked against the master record after every batch, so nothing is oversold during the move.
- The audit tells you whether the move is worth it before you spend on it.
eBay at enterprise scale
Larger sellers typically run eBay alongside their own storefront and other marketplaces, often across several eBay sites by country, with a warehouse or ERP that owns stock and a finance team that needs fees and payouts reconciled. The integration is usually owned by ecommerce operations, with finance and fulfilment as its main customers.
Call limit planning
We count calls per API per day during the audit, move bulk work to the Inventory and Feed APIs, and prepare an Application Growth Check where volumes need it.
Data protection
Account deletion notifications are subscribed and verified, buyer data is kept only as long as needed, and deletions are logged so you can show they happened.
Stock ownership
One system owns stock and every channel follows it. A nightly check compares eBay quantities with the owner and reports differences.
Token continuity
Refresh token expiry dates are tracked per seller account, with alerts well ahead and a written reconnect procedure.
Finance reconciliation
Orders, fees, refunds and payouts are posted to the ledger with the timing differences handled, and a daily check that payouts match the bank.
Engagements we take on
Already on eBay, listings edited by hand
Every product change means editing listings on each channel. We push listings from one master record with eBay rules applied, as in our watch reseller build.
Already on eBay, an old Trading API integration
A legacy sync hits its daily call limit on busy days. We move listing and stock work to the Inventory API, keep what still works, and add monitoring.
Already on eBay, oversells on unique items
One-off items sell twice across channels. We make stock changes event driven with a short reservation on sale, so the second channel ends the listing within minutes.
Read next
Sources
- eBay Developers Program, API call limits (default daily limits per API, Application Growth Check, GraphQL limits), checked 29 October 2026
- eBay Developers Program, Authorisation guide (access token lifetime, refresh tokens), checked 29 October 2026
- eBay Developers Program, Marketplace user account deletion (subscription or opt-out requirement), checked 29 October 2026
Standards on every build
Validation, retries, reconciliation, audit logs and alerts come as standard, with credentials and accounts in your name. Read the integration standards
What people ask about eBay
What about the daily API caps?
Updates are batched and prioritised by what changed, so a quiet day does not burn the quota and a busy day does not hit the ceiling.
Start with the one eBay workflow your team still runs by hand
Bring it to a discovery call. You leave with a yes or no on fit, an outline of the build and what we would do first.
Book the call












