Using SP-API to improve Price Competitiveness 💰💸🏆

[leonardonakagawa]

Have you ever wanted to build analytics views for your sellers to show pricing strategies from Amazon.com. in an easy manner? Here is an example on how you can build it using Amazon Selling Partner API (SP-API)

To provide competitive pricing insights to selling partners, you can leverage the Product Pricing API's getCompetitiveSummary operation. If you want to know more about it, continue reading!

Authored by: @leonardonakagawa Solutions Architect, Selling Partner Developer Services

The Selling Partner API provides Notifications and APIs that enable developers to use their creativity to build apps that offer competitive price information about products and help sellers be eligible and win the featured offer.

With the getCompetitiveSummary operation you can fetch different types of pricing data (e.g. featuredBuyingOptions, lowestPricedOffers, referencePrices) in a single API call for up to 20 ASINs in a batch, creating actionable insights for your customers. You can find how to call the API in this use case guide.

The response from this operation includes data points like:

• ASIN - The Amazon identifier for the item.
• MarketplaceId - A marketplace identifier.
• featuredBuyingOptions - A list of featured buying options for the given ASIN marketplaceId combination.
• lowestPricedOffers - A list of the lowest priced offers for the given ASIN marketplaceId combination.
• referencePrices - A list of reference prices for the given ASIN marketplaceId combination.

If you want to dive deep in the full getCompetitiveSummary response, click here.

Important

You need to have the Pricing Role in your app to to call the getCompetitiveSummary operation.

Understanding the difference about PRICING_HEALTH and ANY_OFFER_CHANGED:

A common topic discussed with developer is about pricing notifications and when to use it.

• The PRICING_HEALTH is triggered when an offer becomes ineligible for the Featured Offer due to external competition or an atypical high price.
• The ANY_OFFER_CHANGED is triggered when there is a price change to any of the top 20 offers or the Featured Offer, or if the Featured Offer changes.

Be aware that these notifications are not triggered in the same situations so, it is worth to adopt both, in order to receive all information regarding the seller offer.

With that, let's see best practices on how to implement these resources and examples of workflows using the best of SP-APIs.

⚡️ Sample Workflow

To understand how you can incorporate the data provided by the getCompetitiveSummary operation, a Postman flow is provided explaining how to build a dashboard displaying the competition for an ASIN with insightful information about the featured offer winner, other competitors, and a repricing flow for that item.

Below are the steps taken in this sample:

1. getCompetitiveSummary operation call using an ASIN and MarketplaceID.
2. With the getCompetitiveSummary operation response, we collect data to build a prototype dashboard.
3. Structure the data to display in a dashboard view.
4. Create a visualization prototype using pieces of data from the response.
5. Use of CompetitivePriceThreshold to make perform patchListingsItem submission and update SKU price.

Tip

Want to try out ? ➡️ Access the flow here

After running the flow, you will be able to see the metrics for that ASIN showing:

• 💵 Number of Offers: 9
• 📊 Graphics showing the price for each offer
• 📦 Featured Offer fulfillment type: AFN
• 🥇 Featured Offer Winner: Seller ID
• 💰 CompetitivePriceThreshold price: 36.98

Example of Pricing analysis dashboard 📈

After integrating with the pricing endpoints and fetching the data points provided by the getCompetitiveSummary response, you can build a dashboard that provides insights to your customers, such as the number of offers, a price graph, the featured offer fulfillment type, the featured offer winner, and the CompetitivePriceThreshold.

Want to create more? Check out the full Pricing sample solution available, which implements a Re-pricing logic using AWS Serverless resources and utilizes the PRICING_HEALTH and ANY_OFFER_CHANGED notifications.

Discover the main features below:

• ✅ Usage of Pricing Health notification to react against Feature Offer eligibility events.
• ✅ Usage of Any Offer Changed notifications reacting against competitors price changes
• ✅ Java and Python compatibility.
• ✅ Solution compatible with Amazon Business - B2B (Java Only).

Let us know what do you think! 👇 React or reply down below to share your feedback

• ❤️ Like what you see?

• 👍 Excited to try it out?

• 🎉 Want to see more of this?

Keywords: SellingPartnerAPI, AmazonSPAPI, Amazon, Pricing, DeveloperTips, FeaturedOffer, BuyBox, AmazonBuyBox, Repricing, Repricer, CompetitivePricing, Amazon BuyBox, #amazonspapi