eBay API NEWS: Compliance API & Product-Based Shopping Experience Fahrplan

eBay gibt für die API Entwickler den Fahrplan 2018 für die Änderungen der Shopping API bekannt und kündigt gleichzeitig die neue Compliance API an. Mit dieser sollen die Händler und Dienstleister die Möglichkeit bekommen fehlerhafte Angebote zu identifizieren. Damit möchte der Marktplatz die Angebots-Qualität anheben.

Compliance API

The Compliance API is used to retrieve listing violations for three different compliance types. Once listing violations are discovered in active listings for the seller, it is up to the seller to make revisions to these listings to correct the listing violations. The three different listing compliance types are summarized below:

Product Adoption: this compliance type is used to see if any listings (or variations within multiple-variation listings) are violating eBay’s new Product-Based Commerce requirement. Beginning in May 2018, some eBay categories and product brands will start requiring that sellers list those products using an eBay catalog product. If a seller does not use a catalog product for categories/brands applicable to the Product-Based Commerce requirement, a create or revise listing action will be blocked. For more information on the Product-Based Commerce mandate, see the Product-Based Shopping Experience Playbook. The Product Adoption compliance type also applies to any listings (or variations within multiple-variation listings) that are missing product identifiers in item specifics, and when variations within multiple-variation listings are wrongfully sharing the same identifier values. In the API interface, the enumeration value for this compliance type is PRODUCT_ADOPTION.

HTTPS protocol: this compliance type is used to see if any listings are violating eBay’s policy of using HTTP links in the listing description instead of HTTPS links. This requirement includes links to externally-hosted listing images. If the server hosting the listing images does not support the HTTPS protocol, this server cannot be used to host listing images. In the API interface, the enumeration value for this compliance type is HTTPS.

Non-eBay Links: this compliance type is used to see if any listings are violating eBay’s policy of not allowing links in the listing description to sites outside of eBay. The seller including a personal email address and/or a phone number in the listing description is also a violation of this policy. All communication between seller and buyers should be handled through eBay’s communication system. The only exceptions to this outside links rule are links to product videos, information on freight shipping services, or any legally required information. In the API interface, the enumeration value for this compliance type is OUTSIDE_EBAY_BUYING_AND_SELLING.

For the initial release of Compliance API, the only supported compliance type is PRODUCT_ADOPTION. HTTPS and OUTSIDE_EBAY_BUYING_AND_SELLING will be supported in later versions of the Compliance API. (Quelle:developer.ebay.com)

Die neue API ist zunächst nur auf folgenden Plattformen verfügbar: US, UK CA und AU. Sie soll euch dabei helfen die Listings zu identifiziert welche die ‘neuen’ Anforderungen nicht erfüllen. Also: Listung mit Katalogdaten , HTTPS und externe Links.

Produkt basierte Einkaufserfahrung

Der Fahrplan ist besonders deshalb spannend, weil er euch schon vorab einen einblick in die zukünftige Darstellung der Suchergebnisse gewährt.

Und so werden die neuen ‘Search Result Pages’ aussehen:

So stellt sich eBay die Product Page vor. Damit entsprechen diese offiziellen Ankündigen den bisherigen Berichterstattungen: eBays neue Produktdetailseite einmal unter die Lupe genommen

Denn vollständigen Fahrplan könnt ihr in Englisch hier nachlesen. Zunächst bleibt der deutsche Marktplatz verschont. Die Neuerungen werden wohl erst 2019 ausrollen.