Full eBay PBSE functional scope

General overview of the marketplace

• Order management and fulfilment • Post-order process management (returns, refunds, cancellations) • Marketing campaign management • Performance reports • eBay metadata (site, category, catalog) • Managing communication with buyers and eBay | • Taxonomy API (Beta) for eBay Category Data • Catalog API (Beta) for eBay product information • Traditional eBay Category Hierarchy APIs |

Flows to be used

• Payment policies • Return policies • payment_program • rate tables • sales tax • privilege | • Create products • Update product • Update stock • Update price • MIP (bulk update) | • Download orders • Download modified orders • Ship orders • Refunds | • Taxonomy management |

Authentication - specifics

All of eBay’s latest APIs are designed based on a common, consistent interface for all applications. They use modern API standards, such as OAuth 2.0 for authentication, JSON payloads, and RESTful design principles. They have been carefully designed to ensure data consistency across all buying and selling tools--both those created within eBay as well as applications created by 3rd-party developers.

Account flows - specifics

1. Account set up For setting up the relevant policies on the eBay account we have to use Account API groups which lets you manage the different business policies that are associated with an eBay seller's account. This includes a seller's payment, fulfillment (shipping), and return policies. Interfaces in the API also allow merchants to opt-in to eBay seller programs, set tax tables for countries that have more than a single tax jurisdiction, and check their seller privileges (such as their selling limits). For more details follow this link Account API

Product flows - specifics

1. Product Creation

   The Inventory API is used to create and manage inventory item records, and then convert these inventory items into product offers on eBay marketplaces. The Inventory API has the following entities:

   • Location: a seller must have at least one store or warehouse inventory location set up before that seller can start creating and publishing offers with the Inventory API. Every inventory location must also have a seller-defined merchant location key value.
   • Inventory Item: before a product can be sold in an offer on an eBay marketplace, an inventory item record must exist for that product. An inventory item record contains such things as product details, item condition, quantity available. Every Inventory Item must also have a seller-defined SKU value, and this value must be unique across the seller's inventory.
   • Offer: an offer is what becomes a live eBay listing. An offer is first created, and then it is published with the Inventory API. Each offer must be associated with an eBay marketplace, an inventory item, an inventory location, and a category ID. The offer will contain quantity available for the offer, the listing description, and an offer price. Every offer must also reference a payment, a fulfillment, and a return business policy, so the seller must be opted in, and have business policies available to apply against the offers.
   • Inventory Item Group: an inventory item group is necessary if the seller would like to create and manage multiple-variation listings through the Inventory API. An inventory item group is a collection of similar inventory items that might vary on a couple of aspects like color and size.
   • Compatible Products: the product compatibility calls allow the seller to create a compatible vehicle list, or vehicles that are compatible with a motor vehicle part or accessory.

For more details follow this link Inventory API

      2. Catalog Creation/Update

               Use the Catalog API to search the eBay catalog for products on which to base a seller's item listing; to retrieve a product record by its eBay product identifier (ePID); to submit a catalog change request to modify an existing product or create a new product; and to manage catalog                     change requests.                For more details follow this link Catalog API

      3. Merchant Integration Platform (MIP)

             The Merchant Integration Platform (MIP) is an easy-to-use, feed-based selling platform for small businesses and enterprise merchants. It lets you easily and efficiently upload your inventory to eBay in bulk and then quickly and efficiently manage your orders. And, it's FAST. MIP can                 upload over 50,000 SKUs in just 30 minutes!              For more details follow this link  MIP

Order flows - specifics

1. The outcome of a buyer's eBay checkout process is an order. This API enables sellers to manage the completion of an order in accordance with the payment method and timing specified at checkout. The line items in the order are grouped into one or more packages. As the seller addresses, handles, and ships each package, the set of specifications for this process is known as a fulfillment. Use the Fulfillment API to facilitate and monitor these activities from the order to completion. Sellers' status on eBay depend partly on their record of timely fulfillment. For more details follow this link Fulfillment API

Other flows - specifics

1. TaxonomyThe purpose of this is do be able automatically get the eBays Taxonomy in terms of Categories and Category Aspects. First we will have to get the category tree using Taxonomy API Then to obtain all the aspects of the category using Catalog API getProductMetadataForCategories call.

Outstanding questions