Developer Impact: Spring 2010 Announcements
Today, Dinesh Lathi posted an important announcement about the Spring 2010 Release (SR10.1). Here is the developer impact for those features. More details will follow in the documentation as each feature is released.
- List up to 100 items a month Auction-style free—no Insertion Fees—when you start your Auction-style listing under $1.
- Get new, lower Insertion Fees for all other start prices.
- Either way, pay one easy Final Value Fee of 9% of the winning bid—and never more than $50—pay only if your item sells.
- List in Fixed Price for 50¢ with Final Value Fees mostly the same as today
- List in Fixed Price with full search exposure for as low as 3¢ Insertion Fees with Final Value Fees for the most part the same as today
- Get FREE pictures
- Get deeply discounted fees on Auction-style listings
No API changes are needed to support this change. Any rate or subscription changes will be automatically reflected in the API. Sellers are encouraged to review their listing strategy to see which options work best for them.
In the API, the FixedPriceItem (FPI) listing format will be replacing the StoresFixedPrice (SFP) listing format. We are offering a migration phase where AddItem will continue to accept either FPI or SFP as listing formats. However, the item will be displayed as FPI on the site and in search results. GetItem and other Get calls will return the format you originally used in the request (FPI or SFP).
In early 2011, SFP will no longer be an accepted option, and your AddItem call will fail if you include it. We recommend you take the following actions as early as possible to avoid issues:
- Remove StoresFixedPrice as a listing option from your user interface
- Start using FixedPriceItem in your AddItem instead of StoresFixedPrice.
Starting with 653 (late Jan), the existing eBayNotes field in will start returning whether or not that item has had sales in the last 16 months. Sellers can use that information to help them make decisions about which selling strategy works best for them.
As of March 30th, 2010, any existing SFP listings will be treated as FPI on the site. Items will immediately get the higher FPI exposure, and will renew or relist at the FPI price.
Any listing enhancements (e.g., bold, subtitle, etc.) will also renew or relist at FPI rates. Sellers will want to evaluate their use of listing enhancements to see if it supports their listing strategy at the higher rates.
This feature will be available in the Sandbox for testing after the Production release. Note, however, that most Sandbox items will not meet the criteria for having sales information returned in eBayNotes (a listing with no sales for 16 months).
Developers who do not yet support the eBayNotes field in GetMyeBaySelling should consider adding support for it. Sellers will find that information particularly valuable between now and late March as they evaluate their existing SFP listings.
No new API changes for this feature.
No new API changes for this feature.
We know that sellers appreciate visibility into their performance on eBay. Sellers who sell on UK/IE/DE/AT/CH currently have only 3 possible status levels returned in GetSellerDashboard for those sites: BelowStandard, Standard (default), and TopRated. We are adding an additional level of granularity to the response so sellers can also see if they are AboveStandard.
AboveStandard indicates that the seller is performing above the standard level for that country. UK and DE PowerSellers who are AboveStandard are eligible for Final Value Fee discounts.
Starting early Feb, if you specify version 653 or later in your request, you'll also start seeing AboveStandard (when applicable) in the response.
AboveStandard is an already existing enum (as of 635) so you do NOT need to upgrade to the 653 WSDL to pick up this tag. You probably already support it for the US site.
3rd-party developers will want include this status tag in any user dashboard, or listing cost estimates they provide. Note that a default status value is returned for all sites (whether or not there have been any sales on that site), so developers may want to filter out values for sites that the seller does not sell on.
The API fully supports Parts Compatibility. Developers with sellers who list in Motors: Parts & Accessories will want to add support for this feature to their applications.
Parts Compatibility is available today in the Motors Sandbox in selected test categories. Starting in mid-March, Parts Compatibility will be supported in limited Parts & Accessories categories in the Production environment.
Trading API SDK support for Parts Compatibility will also follow in March.
Listing with Parts Compatibility:
- Use the new Product API to retrieve the correct eBay Product ID (ePID) for your part (if available). Include that ePID value in the ProductReferenceID container in your AddItem request. The Product API will be available with 655 (early Feb).
- Use the new Product Metadata API to retrieve a list of parts compatibility information specified as name and value pairs. For example, to specify a part's compatibility with a vehicle, the name would map to standard vehicle characteristics (e.g., Year, Make, Model, Trim, and Engine). The values would describe the specific vehicle, such as a 2006 Honda Accord. Pass those name value pairs in the new Item.ItemCompatibilityList container in AddItem. The Product Metadata API will be available with 655 (early Feb).
- Specify parts compatibility manually by specifying the part's relevant dimensions and characteristics (e.g., Section Width, Aspect Ratio, Rim Diameter, Load Index, and Speed Rating for a tire) using attributes in Item.AttributeSetArray. A table of attribute values is available now.
Finding Parts Compatibility Items:
Parts compatibility improves search relevancy and frees up item titles and descriptions for more useful descriptions of the part. Listings with parts compatibility information also get a Best Match boost in search results. The compatibility match is also displayed in the search results (e.g., Fits: 2004 Honda Accord).
This new search behavior is supported by the Finding API and the Best Match Item Details API. The deprecated calls FindItems, FindItemsAdvanced, GetSearchResults and GetCategoryListings do not support Parts Compatibility items.
For more information, see the Trading API Release Notes.
The Items with Variations feature has been added to more categories. For technical information on how to use this feature in the API, see Describing Variations in a Listing.
Most listing-tool developers should already support required Return Policy and Handling Time in other eBay categories. In late 2010, they will also be required in Motors: Parts & Accessories.
Only new, relisted, and renewed items will be checked for compliance.
Developers can help sellers comply with the new requirement by flagging non-compliant listings for their review. Also by offering bulk editing tools to so sellers can search live listings and revise.
Please refresh your cached categories and item specifics when the changes go live.
- Take part in the upcoming webinar on Thursday, January 28.
- Join me and other leaders from eBay and PayPal in a Town Hall meeting on Thursday, January 29. Check the Announcement Board for more details coming soon.
- Talk with members of my staff during the next two days on a special discussion board we've set up for this purpose.
We recommend taking advantage of the resources that Dinesh mentions above. eBay developers can also get their questions answered:
- On a special technical discussion thread hosted by the eBay Developers Program.
- At an upcoming technical webinar on Thursday, January 28 immediately following the general one.