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 has been verified end-to-end on a real seller account (2026-09-04): orders, product import, price and stock push, listing publication and buyer messages.
From eBay checkout to a shipped CRM order
- 1
A buyer checks out on eBay
Within 3 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.
Capabilities, row by row
The same matrix the CRM shows inside the workspace — nothing here is promised that the adapter does not do.
- Orders arrive in the CRMWorks
New and updated orders are imported with line items, amounts and the platform's order id.
Polled every 3 minutes through the Fulfillment API (every order modified since the previous pass, with overlap). When the owner enables eBay push notifications, a notification wakes the poll within seconds. Verified on a live seller on 2026-09-04.
- Order status follows the platformWorks
When the platform changes an order's status or payment, the CRM order follows — until a manager sets the status by hand.
On every pass: payment (PAID → confirmed, full refund → refunded), fulfillment (IN_PROGRESS → processing, FULFILLED → shipped) and a buyer cancellation → cancelled; a payment record is created from the order total. FULFILLED on eBay is set by the seller uploading tracking — eBay never reports “delivered”. A shipment with a tracking number uploaded in Seller Hub lands in the Shipments tab and moves the order to “shipped” even after a manual status change — forward only, never out of cancelled or refunded.
- CRM status goes back to the platformWith a condition
Marking an order shipped or cancelled in the CRM is reported to the platform.
A CRM order marked shipped with a tracking number creates a tracked shipping fulfillment on eBay (carrier + number), idempotently; the direction can be switched off by the owner. Cancellation lives in eBay's separate Post-Order API and is not pushed — cancel in Seller Hub.
- Parcel trackingWith a condition
Carrier and tracking number for the shipment are visible on the order.
The order shows the tracking number and carrier — uploaded by the seller in Seller Hub or sent by the CRM. eBay does not report the parcel's movement back: tracking exists only where the CRM's own carrier integration provides it — Nova Poshta today.
- Delivery confirmedPlatform does not expose it
The CRM learns that the buyer has received the parcel.
eBay's order model ends at FULFILLED (“shipped”): the Fulfillment API has no delivered or picked-up state, so the CRM cannot learn that the buyer received the parcel.
- Buyer messages in the InboxWorks
Questions buyers send through the platform appear in the unified inbox and can be answered from the CRM.
Buyer questions (Trading GetMemberMessages) reach the inbox every 3 minutes, a follow-up from the same buyer lands in the same thread, and a reply from the CRM is sent immediately. Requires consent to the commerce.message scope — accounts connected earlier are asked to reconnect.
- Buyer contact detailsWorks
Buyer name, phone, email and address are stored on the order and the customer card.
Name, shipping address, plus email and phone when eBay includes them in the order; the buyer is stored under the stable eBay username, so repeat orders from the same person link up.
- Import listings into the catalogWorks
Existing listings are pulled into the CRM catalog, matched by SKU or barcode, with a review queue for the rest.
Two passes: Inventory-API-managed listings (with description, photos, GTIN, condition) and classic Seller Hub listings via Trading ActiveList; deduplicated by SKU and ItemID, new items go to the review queue. A classic listing without a custom label has no SKU and is honestly counted as unusable.
- Price and stock pushWorks
CRM price and stock are pushed to the channel's existing listings.
Off by default; the owner arms it after a dry-run preview. Price hourly, only when the price-list currency matches the marketplace; stock hourly and instantly on every warehouse change, for Inventory API offers and classic listings by Item ID alike. At stock 0 eBay keeps the listing active but unbuyable.
- Create listings from the CRMWorks
A CRM product can be published to the channel as a new listing.
Publish from the product card in two steps: a draft offer buyers cannot see, then an explicit “go live” click. Requires shipping/payment/return policies and an inventory location on eBay — the CRM names what is missing instead of letting eBay reject. Production connections only: the eBay sandbox cannot suggest a category. The shipping policy can be chosen per product (or a connection default) and changed on a live listing without relisting.
- Returns and refundsNot built yet
Buyer returns and refunds initiated on the platform are recorded on the CRM order.
Returns and buyer cancellations live in eBay's separate Post-Order API, which the CRM has not integrated. Handle them in Seller Hub; a full refund reaches the CRM through the order's payment status.
- Channel analyticsNot built yet
Sales, prices and competition on the channel are visible inside the CRM.
eBay's Sell Analytics and Marketing APIs are not integrated. The channel page shows sales and revenue from orders that reached the CRM, not listing traffic or conversion.
Status and scope
The adapter is available: orders, listing import, price/stock push and buyer messaging are verified on a real eBay seller account (ebay.it, September 2026), along with two-step listing publication. Shipment confirmation with a tracking number is pushed to eBay automatically; cancellations are not pushed to eBay. One more limit outside our control: eBay never reports delivered or picked up at all. Small things keep being refined — the matrix above says, row by row, exactly what works.
Frequently asked questions
How fast do eBay orders appear in the CRM?
The poller runs every 3 minutes and imports every order modified since the last pass; with eBay push notifications enabled, a new order or message wakes the poll within seconds.
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, or up to 25 products at a time from the channel page. 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. If you changed the price, photos or item specifics in between, the second click sends the current version — there is no need to recreate the draft. The workspace owner has to enable publishing after a dry run first.
Can I choose the shipping policy for a particular product?
Yes. Each product can use one of your eBay shipping policies — free or paid, with the service, handling time and destinations it defines — or stay on the connection’s default policy. On a listing that is already live the policy is changed in place, without relisting, and the CRM reads the listing back to confirm eBay applied it. You can also assign one policy to up to 25 products at once from the channel page. You create the policies themselves in Seller Hub; the CRM only reads them.
Does marking an order shipped in the CRM notify the buyer?
The adapter creates a shipping fulfillment on eBay with the carrier and tracking number from the CRM shipment. Shipment confirmation with a tracking number is pushed to eBay automatically — just like orders, listing import, price/stock push and buyer messaging, which are verified on a real seller account (September 2026).
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?
Yes. The production keyset is active and the adapter has been verified end-to-end on a real eBay seller account (2026-09-04). Connect through eBay's official OAuth consent on the adapter page.
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