Migrating Listings to Inventory API Objects

Whether this field is set in the Account API or Business Policies API, its value must be set to true, as all Inventory API listings must be immediate payment.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain this setting after migration. The seller will just not be able to modify this setting once the listing is migrated.

There is no equivalent field in the Inventory API that will indicate if the item is eligible for the eBay Money Back Guarantee.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any listing-level Buyer Requirements after migration. The seller will just not be able to modify these Buyer Requirements once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any listing-level Buyer Requirements after migration. The seller will just not be able to modify these Buyer Requirements once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any listing-level Buyer Requirements after migration. The seller will just not be able to modify these Buyer Requirements once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any listing-level Buyer Requirements after migration. The seller will just not be able to modify these Buyer Requirements once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any listing-level Buyer Requirements after migration. The seller will just not be able to modify these Buyer Requirements once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any listing-level Buyer Requirements after migration. The seller will just not be able to modify these Buyer Requirements once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any listing-level Buyer Requirements after migration. The seller will just not be able to modify these Buyer Requirements once the listing is migrated.

There are no equivalent fields in the Inventory API to support charitable donations, but the active eBay listing will actually retain any charity information after migration. The seller will just not be able to modify this charity information once the listing is migrated.

There are no equivalent fields in the Inventory API to support charitable donations, but the active eBay listing will actually retain any charity information after migration. The seller will just not be able to modify this charity information once the listing is migrated.

There are no equivalent fields in the Inventory API to support charitable donations, but the active eBay listing will actually retain any charity information after migration. The seller will just not be able to modify this charity information once the listing is migrated.

If ConditionDescription field is set in Trading API, the text in this field is mapped to the conditionDescription field of the Inventory Item object in the Inventory API.

The integer value set in ConditionID field in Trading API is mapped to the corresponding enumeratino value in the condition field of Inventory Item object in the Inventory API.

The Country field set for the listing in Trading API is mapped to the marketplaceId field of Offer object in the Inventory API. The value for the Country field is also used to create the identifier for the Location object.

Cross-Border Trade (same listing across multiple eBay sites) is not yet supported in the Inventory API, so this field will actually have no effect/be ignored when the listing is migrated.

The Currency value set for the listing in Trading API is mapped to all currency fields in the Offer object, including the currency field in the pricingSummary.price container.

For a single-variation listing, the text in the Description field of Trading API is mapped to the product.description field of the Inventory Item object and by the listingDescription field of the Offer object. For a multiple-variation listing, the text in the Description field of Trading is mapped to the description field of the Inventory Item Group object and by the listingDescription field of the Offer object.

Digital Gift Card listings are not supported in Inventory API, so Digital Gift Card listings in Trading can not be migrated to the Inventory API.

This field is used at add/revise/relist time and disable listing and account level Buyer Requirements. If this field was used at add/revise/relist time, all Buyer Requirements will be turned off and will remain off after migration, and the seller will not be able to change this setting once the listing is migrated.

eBay Outlet listings are not supported with the Inventory API, so this field will actually have no effect/be ignored when the listing is migrated.

If MinimumAdvertisedPrice field is set in Trading API, the price in this field is mapped to the pricingSummary.minimumAdvertisedPrice field of the Offer object.

If MinimumAdvertisedPriceExposure field is set in Trading API, the enumeration value in this field is mapped to the pricingSummary.pricingVisibility field of the Offer object; None --> NONE, DuringCheckout --> DURING_CHECKOUT, and PreCheckout --> PRE_CHECKOUT.

If OriginalRetailPrice field is set in Trading API, the price in this field is mapped to the pricingSummary.originalRetailPrice field of the Offer object.

If SoldOffeBay field is set to true in Trading API, the value of the pricingSummary.originallySoldForRetailPriceOn field of the Offer object is set to OFF_EBAY.

If SoldOneBay field is set to true in Trading API, the value of the pricingSummary.originallySoldForRetailPriceOn field of the Offer object is set to ON_EBAY.

The seller's handling time is set in the Shipping/Fulfillment policy. This setting can be made/revised through My eBay, through the Business Policies API, or through the Account API Fulfillment Policy object.

eBay Scheduled Delivery listings are not supported with the Inventory API, so this field will have no effect/be ignored when the listing is migrated.

The eBay Plus Program is not supported with the Inventory API, so this field will have no effect/be ignored when the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any gift services after migration. The seller will just not be able to modify these gift services once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any gift services after migration. The seller will just not be able to modify these gift services once the listing is migrated.

There is no equivalent field in the Inventory API to customize the Visit Counter, but the active eBay listing will actually retain any customization of this counter after migration. The seller will just not be able to modify the counter once the listing is migrated.

By default, eBay listings are tracked by Item/Listing ID, so if the InventoryTrackingMethod field is set in Trading API, but its value is set to SKU, the migration will fail. The seller must revise the listing and set the value to ItemID instead. So, each product in a listing must have a defined SKU, but the listing must be tracked by Item ID.

If Parts Compatibility is used for a motor vehicle part/accessory listing in Trading API, a Parts Compatibility list object for the product is created through the Create or Replace Product Compatibility call, and if the CompatibilityNotes field exists for a corresponding compatible vehicle, the text in this field is mapped to the compatibleProducts.notes field of the Compatible Products object.

If Parts Compatibility is used for a motor vehicle part/accessory listing in Trading API, a Parts Compatibility list object for the product is created through the Create or Replace Product Compatibility call, and each NameValueList pair is mapped to the appropriate vehicle aspect (like year, make, model, engine, and trim) in the productFamilyProperties container.

For a single-variation listing, all item specific name-value pairs in the ItemSpecifics.NameValueList container in Trading API will be mapped to the new Inventory Item object under the product.aspects array. For a multiple-variation listing, all item specific name-value pairs in the ItemSpecifics.NameValueList container in Trading API will be mapped to the new Inventory Item Group object under the aspects array.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain styles/formatting of a Listing Designer Template after migration. The seller will just not be able to modify the Listing Designer Template once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain styles/formatting of a Listing Designer Template after migration. The seller will just not be able to modify the Listing Designer Template once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain styles/formatting of a Listing Designer Template after migration. The seller will just not be able to modify the Listing Designer Template once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain this setting after migration. The seller will just not be able to modify this setting once the listing is migrated.

Motors Local Listings are not supported in the Inventory API and this field will have no effect/be ignored once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain this setting after migration. The seller will just not be able to modify this setting once the listing is migrated.

The value for the ListingDuration field in Trading API can only be GTC since the Inventory API only supports fixed-price, GTC listings. If the value for the ListingDuration field is anything other than GTC, the migration will fail.

There are no equivalent listing enhancements fields (like 'Bold Title' or 'Pro Pack Bundle') in the Inventory API, but the active eBay listing will actually retain any listing enhancement after migration. The seller will just not be able to modify these enhancements once the listing is migrated.

The value for the ListingType field in Trading API can only be FixedPriceItem since the Inventory API only supports fixed-price, GTC listings. If the value for the ListingType field is anything other than FixedPriceItem, the migration will fail.

The string in the Location field in Trading API will generally be a city and a state. Upon a successful migration, this city and state value will be picked up by the location.address container in the newly created Location object. The value for the Location field is also used to create the identifier for the Location object (merchantLocationKey).

Accepted payment methods are handled by Payment listing policies. If seller is using the legacy Business Policies API to manage business policy, accepted payment methods are set in the acceptedPaymentMethod field, and the equivalent field in the Account API is paymentMethods.paymentMethodType.

This field is deprecated.

The boolean value of these fields in the Business Policies API and Account API must be set to true to enable a listing for Click and Collect. Click and Collect is currently only available on the UK and Australia sites.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any picture/gallery details after migration. The seller will just not be able to modify these picture/gallery details once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any picture/gallery details after migration. The seller will just not be able to modify these picture/gallery details once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any picture/gallery details after migration. The seller will just not be able to modify these picture/gallery details once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any picture/gallery details after migration. The seller will just not be able to modify these picture/gallery details once the listing is migrated.

Any URLs to pictures specified through one or more PictureDetails.PictureURL fields in Trading API will be mapped to the product.imageUrls array of the Inventory Item object (for single-variation listings), or to the imageUrls array of the Inventory Item Group object (for multiple-variation listings)

The postal/zip code (in string format) in the PostalCode field in Trading API will be mapped to the location.address.postalCode field in the newly created Location object. The value for the postalCode field is also used to create the identifier for the Location object (merchantLocationKey).

The eBay Category ID in the PrimaryCategory.CategoryID field in Trading API will be mapped to the categoryId field of the Offer object.

Private listings are not supported in the Inventory API, so an attempt to migrate one of these listings will be blocked. If the PrivateListing field is set to true, the seller can revise the listing to turn off this setting (change to false or just remove the PrivateListing field in a ReviseFixedPriceItem call), and then the seller should be able to migrate the listing.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any private notes after migration. The seller will just not be able to modify these private notes once the listing is migrated.

The Brand and MPN values set in the ProductListingDetails.BrandMPN container in Trading API will be mapped to the product.brand and product.mpn fields in the Inventory Item object; these name-value pairs will also be picked up by the product.aspects array for the Inventory Item object

The EAN value set in the ProductListingDetails.EAN field in Trading API will be mapped to the product.ean field in the Inventory Item object; this name-value pair will also be picked up by the product.aspects array for the Inventory Item object

There is no equivalent field in the Inventory API, and this field will have no effect/be ignored when the listing is migrated.

There is no equivalent field in the Inventory API, and this field will have no effect/be ignored when the listing is migrated. however, if a product match is found in the eBay catalog based on a GTIN, the URL to a stock photo (if available) will be picked up by the Inventory Item object

The ISBN value set in the ProductListingDetails.ISBN field in Trading API will be mapped to the product.isbn field in the Inventory Item object; this name-value pair will also be picked up by the product.aspects array for the Inventory Item object.

The ProductListingDetails.NameValueList container is currently only available in Sandbox environment, but once it is fully enabled, any GTIN name-value pairs that are input through this container will be mapped to the corresponding product container fields in the Inventory Item object.

There is no equivalent field in the Inventory API, and this field will have no effect/be ignored when the listing is migrated.

There is no equivalent field in the Inventory API, and this field will have no effect/be ignored when the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any Ticket Listing Details after migration. The seller will just not be able to modify these Ticket Listing Details once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any Ticket Listing Details after migration. The seller will just not be able to modify these Ticket Listing Details once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any Ticket Listing Details after migration. The seller will just not be able to modify these Ticket Listing Details once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain any Ticket Listing Details after migration. The seller will just not be able to modify these Ticket Listing Details once the listing is migrated.

The UPC value set in the ProductListingDetails.UPC field in Trading API will be mapped to the product.upc field in the Inventory Item object; this name-value pair will also be picked up by the product.aspects array for the Inventory Item object

There is no equivalent field in the Inventory API, and this field will have no effect/be ignored when the listing is migrated.

There is no equivalent field in the Inventory API, and this field will have no effect/be ignored when the listing is migrated.

The value in the Quantity field in Trading API will get mapped to the availability.shipToLocationAvailability.quantity field in the Inventory Item object and in the availableQuantity field of the Offer object

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain Minimum Remnant Set value after migration. The seller will just not be able to modify this value once the listing is migrated.

The value in the MaximumQuantity field in Trading API will get mapped to the quantityLimitPerBuyer field of the Offer object.

The description of the Return Policy is set in the returnPolicyProfile.returnPolicyInfo.description field in the Business Policies API, and in the description field of the Return Policy object in the Account API.

The holiday returns boolean value of the Return Policy is set in the returnPolicyProfile.returnPolicyInfo.holidayReturns field in the Business Policies API, and in the extendedHolidayReturnsOffered field of the Return Policy object in the Account API.

The refund option of the Return Policy is set in the returnPolicyProfile.returnPolicyInfo.refundOption field in the Business Policies API, and in the refundMethod field of the Return Policy object in the Account API.

The restocking fee percentage of the Return Policy is set in the returnPolicyProfile.returnPolicyInfo.restockingFeeValue field in the Business Policies API, and in the restockingFeePercentage field of the Return Policy object in the Account API.

In the Business Policies API, the returnPolicyProfile.returnPolicyInfo.returnsAcceptedOption field is set to either ReturnsAccepted or ReturnsNotAccepted to control whether returns are accepted or not, and in the Account API, the returnsAccepted boolean field controls whether returns are accepted or not.

The return period of the Return Policy is set in the returnPolicyProfile.returnPolicyInfo.returnsWithinOption field in the Business Policies API, and in the returnPeriod container of the Return Policy object in the Account API.

The shipping cost payer for a Return is set in the returnPolicyProfile.returnPolicyInfo.shippingCostPaidByOption field in the Business Policies API, and in the returnShippingCostPayer field of the Return Policy object in the Account API.

There is no equivalent field in the Inventory API or Account API, but the active eBay listing will actually retain any Warranty settings after migration. The seller will just not be able to modify Warranty settings once the listing is migrated.

There is no equivalent field in the Inventory API or Account API, but the active eBay listing will actually retain any Warranty settings after migration. The seller will just not be able to modify Warranty settings once the listing is migrated.

There is no equivalent field in the Inventory API or Account API, but the active eBay listing will actually retain any Warranty settings after migration. The seller will just not be able to modify Warranty settings once the listing is migrated.

This field is not applicable because it is only used at Add/Revise/Relist time, and the Inventory API does not allow for scheduled listings. Once an Offer is successfully published with a Publish Offer call, the eBay listing goes live.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain a Secondary eBay Category after migration. The seller will just not be able to modify this Secondary eBay Category once the listing is migrated. And a Secondary eBay Category cannot be used for any offers created through the Inventory API

The payment policy ID used in the PaymentProfileID field in Trading API is mapped to the listingPolicies.paymentPolicyId field in the Offer object of Inventory API, and this particular payment policy is the one that is controlling the payment-related settings.

The Offer object in the Inventory API only accepts a Profile ID, so the PaymentProfileName field in Trading API is not applicable with the Inventory API, and has no effect/is ignored; however, even if only a PaymentProfileName is provided in an Add/Revise/Relist Trading API call, this name is always matched to a profile ID, so this profile ID is always matched to the listingPolicies.paymentPolicyId field in the Inventory API.

The return policy ID used in the ReturnProfileID field in Trading APIis mapped to the listingPolicies.returnPolicyId field in the Offer object of Inventory API, and this particular return listing policy is the one that is controlling the Return Policy-related settings.

The Offer object in the Inventory API only accepts a Profile ID, so the ReturnProfileName field in Trading API is not applicable with the Inventory API, and has no effect/is ignored; however, even if only a ReturnProfileName is provided in an Add/Revise/Relist Trading API call, this name is always matched to a profile ID, so this profile ID is always matched to the listingPolicies.returnPolicyId field in the Inventory API.

The shipping policy ID used in the ShippingProfileID field in Trading API is mapped to the listingPolicies.fulfillmentPolicyId field in the Offer object of Inventory API, and this particular fulfillment listing policy is the one that is controlling the fulfillment-related settings.

The Offer object in the Inventory API only accepts a Profile ID, so the ShippingProfileName field in Trading API is not applicable with the Inventory API, and has no effect/is ignored; however, even if only a ShippingProfileName is provided in an Add/Revise/Relist Trading API call, this name is always matched to a profile ID, so this profile ID is always matched to the listingPolicies.fulfillmentPolicyId field in the Inventory API.

The current price of a fixed-price listing can be found in the SellingStatus.CurrentPrice field of the Trading API, and this price is mapped to the pricingSummary.price container of the Offer object in the Inventory API.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain this setting after migration. The seller will just not be able to modify this setting once the listing is migrated.

The handling cost for an international shipment is set in the shippingPolicyInfo.internationalPackagingHandlingCosts field in the Business Policies API, and in the shippingOptions.packageHandlingCosts and shippingOptions.optionType fields of the Fulfillment Policy object in the Account API. The optionType value must be set to INTERNATIONAL.

The enumeration value in the ShippingDetails.CalculatedShippingRate.MeasurementUnit field will determine the measurement units that are set in the dimensions.unit and weight.unit fields in the Inventory Item object. If the enumeration value in the ShippingDetails.CalculatedShippingRate.MeasurementUnit field is English, the value of dimensions.unit will be set to INCH and the value of weight.unit will be set to OUNCE, and if the enumeration value in the ShippingDetails.CalculatedShippingRate.MeasurementUnit field is Metric, the value of dimensions.unit will be set to CENTIMETER and the value of weight.unit will be set to GRAM.

Although the values of ShippingDetails.CalculatedShippingRate.OriginatingPostalCode and location.address.postalCode may be the same, the value of location.address.postalCode will actually pick up the value of the PostalCode field in Trading API instead.

The handling cost for a domestic shipment is set in the shippingPolicyInfo.packagingHandlingCosts field in the Business Policies API, and in the shippingOptions.packageHandlingCosts and shippingOptions.optionType fields of the Fulfillment Policy object in the Account API. The optionType value must be set to DOMESTIC.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain this setting after migration. The seller will just not be able to modify this setting once the listing is migrated.

The COD fee for a domestic shipment and international shipment is set in the shippingPolicyProfile.shippingPolicyInfo.domesticShippingPolicyInfoService.codFee and shippingPolicyProfile.shippingPolicyInfo.intlShippingPolicyInfoService.codFee fields in the Business Policies API, respectively. In the Account API, the COD fee for both domestic and international shipments is set in the shippingOptions.shippingServices.cashOnDeliveryFee field of the Fulfillment Policy object, and the optionType value controls whether the fee is for a DOMESTIC or INTERNATIONAL shipping service.

In the Business Policies API, the excluded shipping locations are set in one or more shippingPolicyProfile.shippingPolicyInfo.excludeShipToLocation fields. In the Account API, the excluded shipping locations are set in the shipToLocations.regionExcluded container of the Fulfillment Policy object.

The Global Shipping Program is enabled through the shippingPolicyProfile.shippingPolicyInfo.GlobalShipping field in the Business Policies API, and through the globalShipping field of the Fulfillment Policy object in the Account API.

The shipping insurance fee for domestic shipments is set in the shippingPolicyProfile.shippingPolicyInfo.insurance.domesticInsuranceFee field in the Business Policies API, and in the shippingOptions.insuranceFee and shippingOptions.optionType fields of the Account API. The optionType value would be set to DOMESTIC

Whether shipping insurance is offered or not for domestic shipments is controlled in the shippingPolicyProfile.shippingPolicyInfo.insurance.domesticInsuranceOption field in the Business Policies API, and in the shippingOptions.insuranceOffered and shippingOptions.optionType field of the Account API. The insuranceOffered boolean value should be true and the optionType value would be set to DOMESTIC.

The shipping insurance fee for international shipments is set in the shippingPolicyProfile.shippingPolicyInfo.insurance.intlInsuranceFee field in the Business Policies API, and in the shippingOptions.insuranceFee and shippingOptions.optionType fields of the Account API. The optionType value would be set to INTERNATIONAL.

Whether shipping insurance is offered or not for domestic shipments is controlled in the shippingPolicyProfile.shippingPolicyInfo.insurance.intlInsuranceOption field in the Business Policies API, and in the shippingOptions.insuranceOffered and shippingOptions. The insuranceOffered boolean value should be true and the optionType value would be set to INTERNATIONAL.

The promotional shipping discount rule (set up in My eBay Shipping Preferences or through the SetShippingDiscountProfiles call in Trading API) can be applied through the shippingPolicyProfile.shippingPolicyInfo.shippingProfileDiscountInfo.applyIntlPromoShippingProfile boolean field in the Business Policy API. There is no equivalent field in the Inventory API, but the active eBay listing will actually retain the promotional shipping discount rule after migration. The seller will just not be able to modify this setting once the listing is migrated.

A specific international shipping discount rule (set up in My eBay Shipping Preferences or through the SetShippingDiscountProfiles call in Trading API) can be applied through the shippingPolicyProfile.shippingPolicyInfo.shippingProfileDiscountInfo.intlFlatCalcDiscountProfileId field in the Business Policy API. There is no equivalent field in the Inventory API, but the active eBay listing will actually retain the shipping discount rule after migration. The seller will just not be able to modify this rule once the listing is migrated.

An international shipping service option is specified through the shippingPolicyProfile.shippingPolicyInfo.intlShippingPolicyInfoService.shippingService field in the Business Policies API, and in the shippingOptions.shippingServices.shippingServiceCode and shippingOptions.optionType fields of the Account API. The optionType value would be set to INTERNATIONAL.

The additional cost to ship each additional item (in a multiple-quantity order) is specified through the shippingPolicyProfile.shippingPolicyInfo.intlShippingPolicyInfoService.shippingServiceAdditionalCost field in the Business Policies API, and in the shippingOptions.shippingServices.additionalShippingCost and shippingOptions.optionType fields of the Account API. The optionType value would be set to INTERNATIONAL.

The shipping cost of the shipping service is specified through the shippingPolicyProfile.shippingPolicyInfo.intlShippingPolicyInfoService.shippingServiceCost field in the Business Policies API, and in the shippingOptions.shippingServices.shippingCost and shippingOptions.optionType fields of the Account API. The optionType value would be set to INTERNATIONAL.

The order in which the shipping services appear in the listing is set through the shippingPolicyProfile.shippingPolicyInfo.intlShippingPolicyInfoService.sortOrderId field in the Business Policies API, and in the shippingOptions.shippingServices.sortOrder and shippingOptions.optionType fields of the Account API. The optionType value would be set to INTERNATIONAL.

The shipping locations covered by the shipping service is set through one or more shippingPolicyProfile.shippingPolicyInfo.intlShippingPolicyInfoService.shipToLocation fields in the Business Policies API, and in the shippingOptions.shippingServices.shipToLocations.regionIncluded and shippingOptions.shippingServices.shipToLocations.regionExcluded containers, and the shippingOptions.optionType field of the Account API. The optionType value would be set to INTERNATIONAL.

Payment instructions are set up in the paymentProfile.PaymentInfo.paymentInstructions field in Business Policies API, and in the paymentInstructions field of the Account API.

The promotional shipping discount rule (set up in My eBay Shipping Preferences or through the SetShippingDiscountProfiles call in Trading API) can be applied through the shippingPolicyProfile.shippingPolicyInfo.shippingProfileDiscountInfo.applyDomesticPromoShippingProfile boolean field in the Business Policy API. There is no equivalent field in the Inventory API, but the active eBay listing will actually retain the promotional shipping discount rule after migration. The seller will just not be able to modify this setting once the listing is migrated.

The domestic shipping rate table (set up in My eBay Shipping Preferences) can be applied through the shippingPolicyProfile.shippingPolicyInfo.domesticRateTable field in Business Policies API. There is no equivalent field in the Inventory API, but the active eBay listing will actually retain the domestic shipping rate table settings after migration. The seller will just not be able to modify these settings once the listing is migrated.

The international shipping rate table (set up in My eBay Shipping Preferences) can be applied through the shippingPolicyProfile.shippingPolicyInfo.intlRateTable field in Business Policies API. There is no equivalent field in the Inventory API, but the active eBay listing will actually retain the international shipping rate table settings after migration. The seller will just not be able to modify these settings once the listing is migrated.

The ShippingDetails.SalesTax.SalesTaxPercent field in Trading API and the salesTaxPercentage field in the Sales Tax object of Account API are only used to create/update the sales tax for one state or jurisdiction. Any sales tax rates that are set up are only applicable if the tax.applyTax boolean field in Offer object is set to true.

The ShippingDetails.SalesTax.SalesTaxState field in Trading API and the jurisdictionId value in the Create a Sales Tax Table Entry URI in the Sales Tax object of Account API are only used to create/update the sales tax for one state or jurisdiction. Any sales tax rates that are set up are only applicable if the tax.applyTax boolean field in Offer object is set to true.

The ShippingDetails.SalesTax.ShippingIncludedInTax field in Trading API and the shippingAndHandlingTaxed in Sales Tax object in Account API are only applied to one state or jurisdiction. Any sales tax information that is set up is only applicable if the tax.applyTax boolean field in Offer object is set to true.

A specific domestic shipping discount rule (set up in My eBay Shipping Preferences or through the SetShippingDiscountProfiles call in Trading API) can be applied through the shippingPolicyProfile.shippingPolicyInfo.shippingProfileDiscountInfo.domesticFlatCalcDiscountProfileId field in the Business Policy API. There is no equivalent field in the Inventory API, but the active eBay listing will actually retain the shipping discount rule after migration. The seller will just not be able to modify this rule once the listing is migrated.

Free shipping should only be applied to one domestic shipping service in the Account API's fulfillment policy, and that shipping service should be the number one priority service (shippingOptions.shippingServices.sortOrder set to 1 for that shipping service). The optionType value would be set to DOMESTIC.

A domestic shipping service option is specified through the shippingPolicyProfile.shippingPolicyInfo.domesticShippingPolicyInfoService.shippingService field in the Business Policies API, and in the shippingOptions.shippingServices.shippingServiceCode and shippingOptions.optionType fields of the Account API. The optionType value would be set to DOMESTIC.

The additional cost to ship each additional item (in a multiple-quantity order) is specified through the shippingPolicyProfile.shippingPolicyInfo.domesticShippingPolicyInfoService.shippingServiceAdditionalCost field in the Business Policies API, and in the shippingOptions.shippingServices.additionalShippingCost and shippingOptions.optionType fields of the Account API. The optionType value would be set to DOMESTIC.

The shipping cost of the shipping service is specified through the shippingPolicyProfile.shippingPolicyInfo.domesticShippingPolicyInfoService.shippingServiceCost field in the Business Policies API, and in the shippingOptions.shippingServices.shippingCost and shippingOptions.optionType fields of the Account API. The optionType value would be set to DOMESTIC.

The order in which the shipping services appear in the listing is set through the shippingPolicyProfile.shippingPolicyInfo.domesticShippingPolicyInfoService.sortOrderId field in the Business Policies API, and in the shippingOptions.shippingServices.sortOrder and shippingOptions.optionType fields of the Account API. The optionType value would be set to DOMESTIC.

The shipping surcharge for a domestic shipping service is set through the shippingPolicyProfile.shippingPolicyInfo.domesticShippingPolicyInfoService.shippingSurcharge field in the Business Policies API, and in the shippingOptions.shippingServices.surcharge and shippingOptions.optionType fields of the Account API. The optionType value would be set to DOMESTIC.

The shipping cost type for domestic or international shipping is set through the shippingPolicyProfile.shippingPolicyInfo.domesticShippingType and shippingPolicyProfile.shippingPolicyInfo.intlShippingType fields in the Business Policies API, and in the shippingOptions.costType and shippingOptions.optionType fields of the Account API. The optionType value would be set to DOMESTIC for domestic shipping and to INTERNATIONAL for international shipping.

In Trading API, the ShippingPackageDetails.MeasurementUnit field controls whether the Imperial (used in US) or Metric sytem is used for measurements. In the Inventory API, the LengthUnitOfMeasureEnum type defines the units of measurement used in the packageWeightAndSize.dimenstions.unit field, and the WeightUnitOfMeasureEnum type defines the units of measurement used in the packageWeightAndSize.weight.unit field.

In Trading API, the ShippingPackageDetails.PackageDepth field sets the depth/height of shipping package. In the Inventory API, packageWeightAndSize.dimenstions.height sets the depth/height of shipping package.

In Trading API, the ShippingPackageDetails.PackageLength field sets the length of shipping package. In the Inventory API, packageWeightAndSize.dimenstions.length sets the length of shipping package.

In Trading API, the ShippingPackageDetails.PackageWidth field sets the length of shipping package. In the Inventory API, packageWeightAndSize.dimenstions.width sets the width of shipping package.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain this setting after migration. The seller will just not be able to modify this setting once the listing is migrated.

The ShippingPackageDetails.ShippingPackage field value in Trading API will get mapped to the packageWeightAndSize.packageType field in Inventory API.

The ShippingPackageDetails.WeightMajor and ShippingPackageDetails.WeightMinor field values in Trading API will get mapped to the packageWeightAndSize.weight.value field in Inventory API. The value of the ShippingPackageDetails.MeasurementUnit field in Trading API will control what the value of the packageWeightAndSize.weight.unit field in Inventory API will be.

The ShippingPackageDetails.WeightMajor and ShippingPackageDetails.WeightMinor field values in Trading API will get mapped to the packageWeightAndSize.weight.value field in Inventory API. The value of the ShippingPackageDetails.MeasurementUnit field in Trading API will control what the value of the packageWeightAndSize.weight.unit field in Inventory API will be.

The cost in the ShippingServiceCostOverrideList.ShippingServiceCostOverride.ShippingServiceAdditionalCost field in Trading API will get mapped to the listingPolicies.shippingCostOverrides.additionalShippingCost field in Inventory API.

The cost in the ShippingServiceCostOverrideList.ShippingServiceCostOverride.ShippingServiceCost field in Trading API will get mapped to the listingPolicies.shippingCostOverrides.shippingCost field in Inventory API.

The priority (integer value) of the corresponding shipping service option set in the ShippingServiceCostOverrideList.ShippingServiceCostOverride.ShippingServicePriority field in Trading API will get mapped to the listingPolicies.shippingCostOverrides.priority field in Inventory API.

The value set in the ShippingServiceCostOverrideList.ShippingServiceCostOverride.ShippingServiceType field in Trading API (Domestic or International) will get mapped to the listingPolicies.shippingCostOverrides.shippingServiceType field in Inventory API.

The cost set in the ShippingServiceCostOverrideList.ShippingServiceCostOverride.ShippingSurcharge field in Trading API will get mapped to the listingPolicies.shippingCostOverrides.surcharge field in Inventory API. Note that surcharges cannot be set for international shipping options.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain this setting after migration. The seller will just not be able to modify this setting once the listing is migrated.

The shipping cost type for domestic or international shipping is set through the shippingPolicyProfile.shippingPolicyInfo.domesticShippingType and shippingPolicyProfile.shippingPolicyInfo.intlShippingType fields in the Business Policies API, and in the shippingOptions.costType and shippingOptions.optionType fields of the Account API. The optionType value would be set to DOMESTIC for domestic shipping and to INTERNATIONAL for international shipping.

All ship-to locations set up through ShipToLocations fields in Trading API will get mapped to the shipToLocations.regionIncluded container in Inventory API. The name of each shipping location is mapped to the shipToLocations.regionIncluded.regionName field and the type of region (e.g. Country, State, Region, etc.) is mapped to the shipToLocations.regionIncluded.regionType field.

The Site value in Trading API will get mapped to the marketplaceId in Inventory API.

The SKU value in Trading API will become the unique identifer (SKU) of the newly created Inventory Item object in Inventory API.

Although The StartPrice and SellingStatus.CurrentPrice values in Trading API will be the same for a fixed-price listing unless the price was modified with a Revise action, the StartPrice field in Trading API is not used for the migration.

A seller has the option of loading an item under one or two of their eBay Store Categories. The Storefront.StoreCategory2ID value in Trading API sets the root level for the secondary eBay Store Category. So, if the secondary eBay Store Category is at the third tier of the seller's Store Category hierarchy, the Storefront.StoreCategory2ID value would be 2 since a 0-based index is used. During the migration, both the Storefront.StoreCategory2ID and Storefront.StoreCategory2Name will be used to create the full path to the eBay Store Category in the storeCategoryNames array of the Offer object in the Inventory API.

A seller has the option of loading an item under one or two of their eBay Store Categories. The Storefront.StoreCategory2Name value in Trading API specifies the name for the secondary eBay Store Category, and this category must exist at the level that is specified through the Storefront.StoreCategory2ID field. During the migration, both the Storefront.StoreCategory2ID and Storefront.StoreCategory2Name will be used to create the full path to the eBay Store Category in the storeCategoryNames array of the Offer object in the Inventory API.

A seller has the option of loading an item under one or two of their eBay Store Categories. The Storefront.StoreCategoryID value in Trading API sets the root level for the primary eBay Store Category. So, if the primary eBay Store Category is at the first tier of the seller's Store Category hierarchy, the Storefront.StoreCategoryID value would be 0 since a 0-based index is used. During the migration, both the Storefront.StoreCategoryID and Storefront.StoreCategoryName will be used to create the full path to the eBay Store Category in the storeCategoryNames array of the Offer object in the Inventory API.

A seller has the option of loading an item under one or two of their eBay Store Categories. The Storefront.StoreCategoryName value in Trading API specifies the name for the primary eBay Store Category, and this category must exist at the level that is specified through the Storefront.StoreCategoryID field. During the migration, both the Storefront.StoreCategoryID and Storefront.StoreCategoryName will be used to create the full path to the eBay Store Category in the storeCategoryNames array of the Offer object in the Inventory API.

For a single-variation listing, the value in the SubTitle field in Trading API will be mapped to the product.subtitle field in the Inventory Item object of the Inventory API. For a multiple-variation listing, the value in the SubTitle field in Trading API will be mapped to the product.subtitle field in the Inventory Item object, and to the subtitle field in the Inventory Item Group object of the Inventory API.

The tax category code in the TaxCategory field of the Trading API is mapped to the tax.thirdPartyTaxCategory field in the Inventory API.

For a single-variation listing, the value in the Title field in Trading API will be mapped to the product.title field in the Inventory Item object of the Inventory API. For a multiple-variation listing, the value in the Title field in Trading API will be mapped to the product.title field in the Inventory Item object, and to the title field in the Inventory Item Group object of the Inventory API.

If the UseTaxTable in Trading Map is set to true, the tax.applyTax field will also be set to true.

The aspect in Variations.Pictures.VariationSpecificName is mapped to the variesBy.aspectsImageVariesBy field in the Inventory Item Group object.

Each Variations.Pictures.VariationSpecificPictureSet.PictureURL value is mapped to the imageUrls array in Inventory Item Group object.

Variations.Pictures.VariationSpecificPictureSet.VariationSpecificValue value is mapped to the variesBy.specifications.values array in Inventory Item Group object. Each of these values correspond to the Variations.Pictures.VariationSpecificName value. So, if the Variations.Pictures.VariationSpecificName is Color the values in the variesBy.specifications.values array will be the colors in which the product is available.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain this setting after migration. The seller will just not be able to modify this setting once the listing is migrated.

If Variation.DiscountPriceInfo.MinimumAdvertisedPrice field is set in Trading API, the price in this field is mapped to the pricingSummary.minimumAdvertisedPrice field of the Offer object in the Inventory API.

If Variation.DiscountPriceInfo.MinimumAdvertisedPriceExposure field is set in Trading API, the enum value in this field is mapped to the pricingSummary.pricingVisibility field of the Offer object in the Inventory API; None --> NONE , DuringCheckout --> DURING_CHECKOUT, and PreCheckout --> PRE_CHECKOUT.

If Variation.DiscountPriceInfo.OriginalRetailPricefield is set in Trading API, the price in this field is mapped to the pricingSummary.originalRetailPrice container of the Offer object in the Inventory API.

If Variation.DiscountPriceInfo.SoldOffeBay field is set to true in Trading API, the value of the pricingSummary.originallySoldForRetailPriceOn field of the Offer object in the Inventory API is set to OFF_EBAY.

If Variation.DiscountPriceInfo.SoldOneBay field is set to true in Trading API, the value of the pricingSummary.originallySoldForRetailPriceOn field of the Offer object in the Inventory API is set to ON_EBAY.

The Variation.Quantity value will be mapped to the availability.shipToLocationAvailability.quantity field in Inventory Item object and the availableQuantity field in Offer object.

The Variation.SKU value in Trading API will become the unique identifer (SKU) of the newly created Inventory Item object in Inventory API and will also get picked by the sku field in the Offer object.

The Variation.StartPrice value is mapped to the pricingSummary.price container in Offer object for the corresponding SKU.

The EAN value set in the Variation.VariationProductListingDetails.EAN field in Trading API will be mapped to the product.ean field in the Inventory Item object; this name-value pair will also be picked up by the product.aspects array for the Inventory Item object.

The ISBN value set in the Variation.VariationProductListingDetails.ISBN field in Trading API will be mapped to the product.isbn field in the Inventory Item object; this name-value pair will also be picked up by the product.aspects array for the Inventory Item object.

The Variation.VariationProductListingDetails.NameValueList container is currently only available in Sandbox environment, but once it is fully enabled, any GTIN name-value pairs that are input through this container will be mapped to the corresponding product container fields in the Inventory Item object.

The UPC value set in the Variation.VariationProductListingDetails.UPC field in Trading API will be mapped to the product.upc field in the Inventory Item object; this name-value pair will also be picked up by the product.aspects array for the Inventory Item object.

Each Aspect/Item Specific for a product variation that is defined in the Variation.VariationSpecifics.NameValueList.Name field in Trading API is mapped to the product.aspects array in Inventory Item object. The product.aspects array pairs together Item Specifics and their values, using this syntax: "Storage Capacity": ["128GB"].

Each value for an Aspect/Item Specific for a product variation that is defined in the Variation.VariationSpecifics.NameValueList.Value field in Trading API is mapped to the product.aspects array in Inventory Item object. The product.aspects array pairs together Item Specifics and their values, using this syntax: "Storage Capacity": ["128GB"].

Each aspect that is shared among all variations within a group is defined in the Variation.VariationSpecifics.NameValueList.Name field in Trading API, and is mapped to a variesBy.specifications.name field in Inventory Item Group object.

The values of each aspect that is shared among all variations within a group is defined in the corresponding Variation.VariationSpecifics.NameValueList.Value fields in Trading API, and is mapped to the variesBy.specifications.values array in Inventory Item Group object.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain this setting after migration. The seller will just not be able to modify this setting once the listing is migrated.

There is no equivalent field in the Inventory API, but the active eBay listing will actually retain this setting after migration. The seller will just not be able to modify this setting once the listing is migrated.

The VAT percentage value set in the VATDetails.VATPercent field in Trading API is mapped to the tax.vatPercentage field in the Offer object.

The VIN field is only used when a listing is created/revised/relisted, so this field is not applicable to the migration.