eBay Fulfillment Connector Development

eBay's Fulfillment API handles everything between an order being placed and a package arriving at the buyer's door: order retrieval, shipping label generation, tracking updates and dispute management. For sellers operating on both eBay and Amazon, the fulfillment connector is the second half of the multi-channel automation stack, the first half being Amazon SP-API development. This article covers the architecture of an eBay fulfillment connector, the API surface involved, the differences from Amazon's approach, and what it costs to build a connector that handles the edge cases eBay throws at you.

TL;DR

• eBay's Fulfillment API covers order retrieval, shipping, tracking and disputes. It is REST-based with OAuth 2.0 authentication.
• Key differences from Amazon: eBay uses OAuth (not LWA plus IAM), rate limits are per-application (not per-operation), and there is no equivalent of SP-API Notifications for real-time order events.
• A fulfillment connector build starts at $4,000 and ships in 4 to 6 weeks.
• For multi-channel sellers, build the eBay connector as a module in the same middleware that handles Amazon rather than as a standalone system.

The eBay Fulfillment API surface

eBay's Fulfillment API is a REST API authenticated via OAuth 2.0 user tokens. The core operations are getOrders (retrieve orders by filter criteria), getOrder (single order detail), issueRefund (process full or partial refunds), and the Shipping Label operations (createShippingFulfillment, getShippingFulfillment). The API also covers payment disputes via a separate Dispute API. Unlike Amazon's SP-API, eBay does not have a Notifications equivalent for fulfillment events, which means order retrieval is poll-based: your connector calls getOrders on a schedule and processes new orders as they appear.

The authentication model is simpler than Amazon's. eBay uses standard OAuth 2.0 with a user consent flow. The seller authorises your application, you receive an access token and refresh token, and you include the access token on every API call. There is no IAM role, no STS AssumeRole, and no dual-layer authentication. Rate limits are per-application across all operations (currently 5,000 calls per day for most applications) rather than per-operation, which means a busy fulfillment connector needs to budget its calls carefully across order retrieval, shipping and tracking.

Order retrieval and routing

The getOrders endpoint returns orders filtered by date range, status, or fulfillment status. For a fulfillment connector, the typical pattern is to poll every 5 to 15 minutes for orders in AWAITING_SHIPMENT status, download the order details, and route them to the warehouse management system or shipping provider. If you are also running an inventory and order automation layer for Amazon, the eBay orders feed into the same routing engine. The key is to normalise the order schema across channels so the warehouse processes a single order format regardless of source.

Shipping label generation and tracking

eBay's Shipping API supports generating shipping labels through eBay's own label service or through a carrier API that your connector integrates directly. For most sellers, the carrier integration is already in place (via ShipStation, EasyPost, or a direct carrier API), and the eBay connector's job is to take the label and tracking number from the carrier, call createShippingFulfillment on eBay, and update the order status. eBay requires tracking information within the handling time specified in the listing, and late shipment metrics affect seller performance. The connector needs to handle the case where the carrier returns the tracking number asynchronously (which happens with some carriers that batch label generation).

Differences from Amazon SP-API fulfillment

Multi-channel fulfillment architecture

For sellers on both Amazon and eBay, the fulfillment connector should be a module in a shared middleware rather than a standalone system. The middleware normalises orders from both channels into a single schema, routes them to the same warehouse system, and writes back shipping confirmation to the correct channel. This avoids duplicating warehouse integration logic and ensures inventory updates from fulfillment flow through the same marketplace connectors layer. The Shopify to Amazon sync architecture described in the Shopify to Amazon inventory sync article extends naturally to include eBay as a third channel.

Error handling and edge cases

• eBay order cancellations can arrive after the item has been shipped. The connector needs to check shipment status before processing a cancellation request.
• International orders may require customs declarations that domestic orders do not. The connector needs to detect the destination country and attach the correct customs data to the shipping label request.
• eBay's rate limit is daily, not per-second. A connector that front-loads API calls in the morning can exhaust the quota before the afternoon. Spread calls evenly across the day.
• The Fulfillment API returns paginated results. A connector that does not handle pagination will miss orders on busy days.
• Payment disputes have their own lifecycle and timeline requirements. Respond within the deadline or eBay auto-resolves in the buyer's favour.
• Multi-variation listings on eBay require matching the correct variation to the correct SKU in your warehouse system. The order detail includes the variation but the format differs from Amazon's variation model.

Returns and post-order handling

eBay's Post-Order API handles cancellations, returns, and buyer inquiries. The key difference from Amazon is that eBay requires sellers to respond to return requests within a configurable window (typically 3 business days), and failure to respond results in an automatic resolution in the buyer's favour. The connector needs to surface return requests in your operations workflow, track response deadlines, and handle the inventory adjustment when a return is accepted. For sellers processing returns on both Amazon and eBay, the return handling logic should be channel-aware: Amazon returns flow through the MFN Returns API or FBA return reports, while eBay returns flow through the Post-Order API. Both should update the same source of truth for inventory.

Build cost and timeline

A standalone eBay fulfillment connector (order retrieval, shipping confirmation, tracking, basic error handling) starts at $4,000 and ships in 4 to 6 weeks. A multi-channel connector module added to an existing Amazon middleware starts at $9,500 because the shared queue, database and monitoring already exist. A full multi-channel fulfillment platform covering Amazon, eBay, Shopify and a D2C channel starts at $21,000 and ships in 10 to 14 weeks. The custom ecommerce tools page covers the broader ecommerce development scope. The Amazon SP-API development page covers the Amazon half of the stack, and data pipeline engineering patterns apply to order normalisation and tracking flows.

Frequently Asked Questions

What is the eBay Fulfillment API?

A REST API covering order retrieval, shipping label generation, tracking updates and payment disputes. Authenticated via OAuth 2.0.

How does it differ from Amazon SP-API?

eBay uses simpler OAuth auth (not dual-layer), has per-application daily rate limits (not per-operation), and has no real-time event notifications. eBay also does not warehouse inventory.

Can I use the same system for Amazon and eBay?

Yes. Build the eBay connector as a module in your existing Amazon middleware. Normalise orders to a single schema and route through the same warehouse system.

What does an eBay fulfillment connector cost?

Standalone from $4,000. Added to existing Amazon middleware from $9,500. Full multi-channel platform from $21,000.

How long does it take to build?

Standalone: 4 to 6 weeks. Added module: 3 to 4 weeks. Full multi-channel: 10 to 14 weeks.

Does eBay have real-time order notifications?

No. eBay fulfillment is poll-based. Your connector calls getOrders on a schedule (typically every 5 to 15 minutes).

How do rate limits work on eBay?

Per-application daily quota, currently 5,000 calls per day for most apps. Spread calls evenly across the day to avoid exhausting the quota.

What about returns and disputes?

Returns are handled via the Post-Order API. Payment disputes have their own API and lifecycle with response deadlines.