The eBay adapter is built on the official eBay Sell APIs (Fulfillment + Inventory) and connects through eBay's OAuth consent — no password ever reaches the CRM, and per-seller tokens are stored encrypted. Orders arrive by scheduled polling because eBay has no order webhooks; the CRM keeps them in sync on every pass and pushes tracking back when your team ships. The adapter is code-complete against the eBay sandbox and stays in QA until a real seller account passes end-to-end verification.
From eBay checkout to a shipped CRM order
- 1
A buyer checks out on eBay
Within 15 minutes the order lands in the CRM with line items, the buyer snapshot (name, email, phone), the shipping address and the payment total.
- 2
The team works it like any CRM order
Payment status from eBay is recorded automatically; the marketplace stays the source of truth until a manager edits the status by hand.
- 3
Shipping goes back to eBay
When the CRM order is marked shipped with a tracking number, the adapter creates a tracked shipping fulfillment on eBay — the buyer sees carrier and tracking in their purchase.
What the adapter does
Orders, idempotently
Polling follows a time cursor with an overlap window, so an order is never imported twice and a missed cycle self-heals on the next run.
Catalog by SKU
CRM prices and stock are pushed to Inventory-API-managed listings matched by SKU; product import pulls every active listing — Inventory-API-managed and ordinary Seller Hub ones alike — into the CRM catalog as reviewable drafts.
What it did not do is visible
The sync only ever touches listings that already exist on eBay. So the report separately shows the products that are not on eBay at all, and the ones it failed to push — silence is never passed off as success.
GDPR-grade cleanup
The adapter ships eBay's marketplace account deletion endpoint: when eBay reports a closed account, that buyer's data is anonymized across the CRM automatically.
Current capabilities
- Seller connection through official eBay OAuth (sell.fulfillment + sell.inventory scopes); tokens sealed at rest.
- Connection test confirms the seller username, environment and refresh-token validity before any sync runs.
- Order import every 15 minutes with line items, buyer snapshot, shipping address and payment total.
- eBay payment and fulfillment status mapped into CRM order status on every poll; refunds and cancellations included.
- A CRM order marked shipped creates a tracked shipping fulfillment on eBay (carrier + tracking from the CRM shipment, idempotent).
- You choose which eBay marketplace the connection sells on; prices go to that market's offers and the sync stays off until you have chosen — never a guess.
- Stock is pushed only for products that track inventory, and a product priced in another currency than the chosen marketplace keeps its price and is reported.
- Product import brings every active listing — Inventory-API-managed and classic Seller Hub ones — into the CRM catalog, deduplicated by SKU and capped per run with an honest truncated flag.
- Publish a product to eBay from its product page — one product at a time, by hand, in two steps: the listing is prepared first, and a second click puts it on sale.
- Before publishing, the CRM checks what eBay will require — shipping/payment/return policies, an inventory location, a completed seller registration — and names what is missing instead of letting eBay reject the listing.
- The sync report also shows what the CRM did NOT do: how many active products are not on eBay at all, and how many items failed to push.
- The marketplace account deletion endpoint answers eBay's challenge and anonymizes closed-account buyer data with signature verification.
QA status and scope
The adapter is in QA: the production keyset is active and the account-deletion endpoint passed eBay's test, but no real seller has completed end-to-end verification. Import covers every active listing, while price/stock push supports both Inventory API offers and classic Seller Hub listings through their Item ID — bulkMigrateListing is no longer mandatory. Order cancellation lives in eBay's separate Post-Order API and is not pushed yet.
Frequently asked questions
How fast do eBay orders appear in the CRM?
The poller runs every 15 minutes and imports every order modified since the last pass, so a new order typically appears within minutes.
Can the CRM update any eBay listing?
Import sees every active listing, including ones created in Seller Hub. The CRM sends price and stock through two official paths: Inventory API for managed offers and Trading ReviseInventoryStatus by Item ID for classic listings. bulkMigrateListing is not mandatory. Automatic matching to a CRM product still requires custom label = SKU.
Can I list a product on eBay straight from the CRM?
Yes — from the product page, one product at a time. It takes two clicks, deliberately: on eBay an unpublished listing is invisible even to you (it is in neither active listings nor Seller Hub drafts), so you review it in the CRM and the second click puts it on sale. The workspace owner has to enable publishing after a dry run first.
Does marking an order shipped in the CRM notify the buyer?
Yes. The adapter creates a shipping fulfillment on eBay with the carrier and tracking number from the CRM shipment, and eBay shows it to the buyer.
What happens when an eBay user deletes their account?
eBay sends a signed deletion notification to the adapter's dedicated endpoint; the CRM verifies the signature and anonymizes that buyer's orders and profile data automatically.
Is this available for live sellers now?
The functionality is built and in QA against the eBay sandbox. Live sync waits for production keyset activation and an end-to-end verification with a real eBay seller account.
One workspace for eBay and every other channel
Orders, buyers, stock and tracking stay in the CRM your team already works in.
Start for free