Updates to Summer 2009 Release; Part 2 of 2.
Updates to Summer 2009 Release; Part 2 of 2.
On July 29, 2009, Laurel posted an announcement about the July 2009 updates. In this entry, we highlight part 2 of the features that were released since then
For the list of calls changed with each Trading API version, see the Trading API Release Notes.
Because there are many updates, the details have been split into two entries. The first part can be found here. This is the second entry and covers the following topics:
As a reminder, the first entry included: will link to part 1 entry.
If you would like the complete details on the July 2009 Update, please refer to the following links and to the API Release Notes.
- All features are not available to all Sellers, use the Trading call GeteBayDetails to find out which features are available for your site. As part of the seller release, some listing upgrades were removed for some sites, and some will be restricted to eBay Top-Rated Sellers or PowerSellers. The listing features include bold title, border, Featured First, Featured Plus!, gift icon, highlight, Homepage Featured, and ProPack. A new type, ListingFeatureDetails, has been added to the GeteBayDetails response that returns which listing features are available to the seller for the site. Another addition to the GeteBayDetails response, UpdateTime, reports the time of the most recent modification to any Detail.
- A type has been added to the Trading call ListingStartPriceDetailsType.MinBuyItNowPricePercent, which returns the minimum percentage difference between the start price and the Buy It Now price for a listing on the specified site. There is one exception: Use category details to find the percentage requirements for Motor Vehicles (using Site ID 100 - the eBay Motors site.)
- GetSellerEvents now returns variation details in Item.Variations, including StartPrice, Quantity, and QuantitySold, plus SKU and/or VariationSpecifics. Multiple variations are returned together in the same Variations node (similar to GetItem).
- To keep the GetSellerEvents response smaller, the variation specifics are not returned if the variation has a SKU.
- With RelistFixedPriceItem and ReviseFixedPriceItem, you can now use SKU to uniquely identify an existing variation, regardless of whether the listing has inventory tracking set to SKU.
- ReviseInventoryStatus now supports modifying variations when InventoryTrackingMethod is set to ItemID.
- For the site specified in the request, GeteBayDetails now returns variation constraints, such as maximum number of variations, in VariationDetails.
- GetUser now returns QualifiesForVariations (a boolean) to indicate whether the user is eligible to list with variations on the site specified in the request.
- In SetUserNotes, you can now set private notes for variations. These notes will be visible to the user for variations that are displayed in My eBay.
- GetMyeBayBuying and GetMyeBaySelling now return PrivateNotes for applicable variations. Depending on how the notes were set (what was specified in the SetUserNotes request), the variations may be returned within Variations or within Item
-  Shipping Insurance option has been removed from many sites. If shipping insurance is included in AddItem, it will be dropped with a warning, but won't fail. See the Release Notes.
-  Using My eBay, you can create an Exclude Ship-To List of the locations to where you will not ship items. Once set up, all items that you list on eBay will, by default, use the Exclude Ship-To List to exclude the locations you specified in the list. If a buyer's primary ship-to location is a location that you have listed as an excluded ship-to location (or if the buyer does not have a primary ship-to location), they will receive an error message if they attempt to buy or place a bid on your item. Use GetUserPreferences to review the default set of excluded locations that you have set up in My eBay. Use GetUserPreferences to retrieve your global exclusion list. See the Release Notes.
-  Tracking for multiple package shipment for a single item. ShippingCarrierUsed and ShipmentTrackingNumber have been moved to a repeatable ShipmentTrackingDetails container. See the Release Notes.
-  More shipping carriers supported. The type for ShipmentType.ShippingCarrierUsed has been changed from ShippingCarrierCodeType to string. This enables sellers to specify a shipping carrier (via CompleteSale) other than the ones noted in ShippingCarrierCodeType.
- With a request version lower than 627, the value you specify for CompleteSale's ShippingCarrierUsed must be a value found in ShippingCarrierCodeType. If the request version is 627 or higher, you can specify the shipping carrier of your choice, even if it is not in the ShippingCarrierCodeType list, and GetSellingManagerSaleRecord will return that value. See the Release Notes.
-  Local Pickup: Shipping Time DSRs ignored, Shipping and Handling Charges MAY be ignored.
- In the Trading API LeaveFeedback call, DSRs left for Shipping Time will be ignored for all Local Pickup transactions. DSRs left for Shipping and Handling Charges will be ignored for Local Pickup transactions where the seller did not add any special handling fees. See the Release Notes.
- This change affects the following eBay sites: AU, Mn-AT, BE-FR, BE-NL, CA, CA-FR, FR, DE, HK, IN, Mn-IE, IT, MY, Motors, NL, PH, PL, SG, ES, Mn-CH, UK, US
-  Seller Status Now Returned by GetSellerDashboard. See the Release Notes.
- Avoid 1s and 2s
- Only domestic DSRs count
- [629 ] Top-Rated Seller Details Available via GetUser and Other Calls; SellerInfo.SellerLevel to Be Removed
- When Top-Rated Seller details became available in October (see Announcement), GetUser began returning fields that identify the seller as a Top-Rated Seller and gave details about the Top-Rated Seller program. These fields are already present and documented for GetUser and other calls. They include TopRatedSeller and TopRatedSellerDetails.TopRatedProgram, which identifies the Top-Rated-Seller programs for which the seller is qualified. See the Release Notes.
- When the Top-Rated Seller feature became active on the US, DE, and UK sites, SellerInfo.SellerLevel no longer returned results for those sites. Affected calls include GetUser, GetBidderList, GetSellerList, GetItem, and GetItemTransactions.
More categories are becoming catalog-enabled
When Good Till Canceled (GTC) listings are renewed, they will be checked for Return Policy and Handling Time. If these details are not included, the GTC listing renewal will fail. For more info, see this entry in the Forum.
December 17, 2009 in Best Practices, Categories and Item Specifics, Certified Provider, Client Alerts API, Developer Community, Documentation, Finding API, Large Merchant Services, Merchandising API, Product News, Shopping API, Trading API | Permalink
Updates to Summer 2009 Release: Part 1 of 2
On July 29, 2009, Laurel posted an announcement about the July 2009 updates. In this two part entry, we highlight the features that were released since then.(For the change details with each API version, see the API Release Notes.)
Because there have been many updates, this topic will be split into two entries.
This first entry includes:
The second entry (to be published on, or around, December 17) will include:
Items with Variations
-  Multi-Variation Listings: GetSellerEvents and Other Enhancements
-  Changes to ListingFeatureDetails and Some Listing Features to Be Removed and Restricted
Selling Manager Applications
- ShippingCarrierUsed: Type Change
- LeaveFeedback and Shipping API Detailed Seller Ratings (DSRs)
- Reminder: Return Policy and Handling Time Required When You Renew GTC Listings
If you would like details on the July 2009 Update, please refer to the following links and to the API Release Notes.
Please see the BestMatchItemDetails API release notes for details.
[1.2.0] New Feature: Gallery Plus Pictures
[1.2.0] Doc changes: Updated Value for SellerBusinessType Item Filter
Reminder of what changed in Best Match (Details)
- New listing performance score for Fixed Price to replace recent sales
- New multi-quantity and single-quantity Fixed Price listings will be given exposure in Best Match
- Titles are more important than ever
- Seller performance continues to count
- Shipping cost continues to count
- No changes to Auction-style listings
- Optimized by category
- As part of the Edit Live Items feature, a new TransactionID field was added to the GetItemRequest call. This new field will allow both Sellers and Buyers to retrieve a listing as it was at the time of a given purchase by invoking GetItem with a TransactionID in the request (even if the seller has made significant revisions to the listing, following the purchase).
- Sellers are also able to make revisions to their multi-quantity fixed price listings after a purchase has been made (currently, Sellers can not change their multi-quantity fixed price listings, after at least one item in the listing has been purchased).
- Sellers are able to view the updated listing for each transaction, but Buyers are only able to view the transactional version of a listing where they are the successful buyer. Past transactional views of an item will be available for up to 90 days from the date the transaction took place.
 Platform Notification changes and client alerts
- Changes to the GetItemTransaction API call may cause a change to the behavior of the following Platform Notifications: EndOfAction, AuctionCheckoutComplete, FixedPriceEndOfTransaction, CheckoutBuyerRequestTotal, FixedPriceTransaction, Checkout, FixedPriceTransactionForSeller, FixedPriceTransactionForBuyer, ItemMarkedAsShipped, and ItemMarkedAsPaid.
- The following Client Alerts may have a behavior change as a result of this project: EndOfAuction, FixedPriceEndOfTransaction, FixedPriceTransaction, ItemSold, and ItemWon. Each notification will now be based on the state of the item (a 'snapshot' of the item) at the time the transaction was created.
Finding API - see the Finding API release notes for details.
[1.1.0] New: Gallery Plus Pictures
[1.1.0] Updated Value for SellerBusinessType Item Filter
[1.0.1] eBay Top-rated Seller
With the launch of the Top-rated Sellers program, buyers can find items listed by the highest quality sellers on eBay based on the feedback of other buyers. The sellerInfo node in the search results (searchResult.item.sellerInfo) for the "findItems" calls now includes the topRatedSeller field to indicate (true or false) whether the seller of an item qualifies as an eBay Top-rated Seller. Additionally, a new TopRatedSellerOnly item filter has been added to limit search results to items listed by Top-rated Sellers only.
Note the following site restrictions:
- The searchResult.SellerInfo.topRatedSeller field in the response for the finding calls is supported for the following sites only: US (EBAY-US), Motors (EBAY-MOTOR), DE (EBAY-DE), AT (EBAY-AT), and CH (EBAY-CH).
- The TopRatedSellerOnly item filter is supported for the following sites only: US (EBAY-US), Motors (EBAY-MOTOR), UK (EBAY-GB), IE (EBAY-IE), DE (EBAY-DE), AT (EBAY-AT), and CH (EBAY-CH).
Top-rated sellers consistently receive highest buyers' ratings, ship items quickly, and have earned a track record of excellent service. eBay regularly reviews the performance of these sellers to confirm they continue to meet the program's requirements. See the Top-rated Sellers page on the eBay site for more information.
Trading API - See the Trading API release notes for details.
 Clarifications in Documentation for Unpaid Item Disputes
- Version 639 release notes surveyed various process changes for Unpaid Item Disputes.
- Support for the old process will be removed around March 2010, so please migrate your UPI dispute code to work with the new process.
- How do you know whether the newer or older process applies to your disputes or not? It is all about the request version. If you created a UPI dispute with a request version lower than 637, the old timelines apply and the various platform notifications for messaging are still supported. But if the request version is 637 or greater, the new timelines apply.
- Further, since AddDisputeResponse can no longer be used (for 637 or greater) for buyer or seller communication, these notifications are no longer triggered: BuyerResponseDispute, SellerRespondedToDispute.
- See Newer versus Older Unpaid Item Disputes Process - a before/after table of facts.
 New Features for 639
- Multiple-Package Details for a Single Item
- Selling Manager Calls: No Integration with eBay.com Is Required
- Unpaid Item Disputes: Process Change
GetSellerEvents now returns variation details in Item.Variations, including StartPrice, Quantity, and QuantitySold, plus SKU and/or VariationSpecifics. Multiple variations are returned together in the same Variations node (similar to GetItem).
December 2, 2009 in Best Practices, Categories and Item Specifics, Client Alerts API, Developer Community, Developer Education, Documentation, Feedback API, Finding API, Large Merchant Services, Platform Notifications API, Shopping API, Trading API | Permalink