Skip to main content

AWS Solutions Library

Guidance for Amazon Seller and Vendor Central Data Producer

Overview

This Guidance demonstrates how Consumer Packaged Goods (CPG) companies can ingest data into a modern data environment to enable advanced analytics. Companies can develop efficient and secure applications that integrate with Amazon Seller and Vendor Central and gain valuable insights into their Amazon Retail data, including product catalog updates, sales, shipments, and payments.

How it works

Overview

This architecture uses serverless and managed services to help customers develop efficient and secure applications to integrate with Amazon Seller Central and Amazon Vendor Central. Customers can use this to ingest, process, and gain insights from their Amazon.com data.

Please note: This is the overview architecture. For diagrams highlighting different aspects of this architecture, open the other tabs.

Download the architecture diagram
Diagram illustrating an AWS architecture for Amazon Seller and Vendor Central, featuring Step Functions apps, Lambda functions, Secrets Manager, DynamoDB, S3, and SQS integrated with the Selling Partner API.

Authentication and Authorization

This architecture shows the registration process with Amazon Seller Central and Amazon Vendor Central. It includes: receiving a refresh token, secure token storage, exchanging for an access token, and using an authorized token to make API calls to the Selling Partner API (SP-API).

Download the architecture diagram
Architecture diagram illustrating authentication and authorization flow for Amazon Seller Central and Vendor Central using AWS Step Functions, AWS Lambda, Selling Partner API (SP-API), and AWS Secrets Manager.

Serverless Reports Application

This architecture shows how to create a serverless reports application to automatically ingest, process, and store data obtained from the Amazon Seller Central and Amazon Vendor Central Selling Partner API (SP-API).

Please note: currently, the REPORT_PROCESSING_FINISHED notification type only works for seller applications. Vendor applications will have to use a polling method.

Download the architecture diagram
Architecture diagram illustrating a serverless solution for generating and processing Selling Partner API (SP-API) reports using AWS Step Functions, Lambda, Secrets Manager, Systems Manager, SQS, S3, and KMS.

Serverless Catalog Items and Listing Items Applications

This architecture shows how to create a serverless application to integrate with the Catalog Items and Listing Items APIs from the Amazon Seller Central and Amazon Vendor Central Selling Partner API.

Download the architecture diagram
Architecture diagram demonstrating a serverless solution for Amazon Seller Vendor Central catalog listing items using AWS services. The diagram includes AWS Step Functions, Lambda functions for authorization, data processing, and storage, AWS Secrets Manager, API Client, AWS Key Management Service (KMS), Amazon Simple Storage Service (S3), Amazon DynamoDB, and AWS Systems Manager for managing parameters and endpoints.

Data Storage, Movement, and Insights

This architecture shows how to build a data analytics pipeline using a Modern Data Analytics approach to derive insights from the data.

Download the architecture diagram
Architecture diagram showing how Amazon Seller and Vendor Central data flows through AWS services for scalable data storage, seamless data movement, and purpose-built analytics and insights. Includes Amazon S3, Lake Formation, Glue, Glue DataBrew, Athena, Redshift, QuickSight, EMR, OpenSearch Service, and SageMaker.

Well-Architected Pillars

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

This Guidance consists of serverless services such as Lambda, Step Functions, and Amazon S3 that are loosely coupled and have built-in version control capabilities for implementing changes.

Read the Operational Excellence whitepaper

This Guidance uses a self-authorization model with Amazon Vendor Central. Applications you create are registered in Vendor Central, where you receive a Login with Amazon (LWA) refresh token. These refresh tokens are securely stored in Secrets Manager. LWA refresh tokens are exchanged for LWA access tokens. The LWA access tokens, along with IAM and AWS STS, are used to securely make API calls to Amazon Vendor Central, leveraging well-defined user access permissions.

Read the Security whitepaper

This Guidance consists of serverless and fully managed services with built-in reliability due to a combination of a service-oriented architecture (like the use of Step Functions to create a serverless application) and microservices (where Step Functions uses AWS STS to execute the call). Selling Partner API requests are limited using the token bucket algorithm, so an API client is recommended for rate limiting.

Read the Reliability whitepaper

Scalable and highly available services such as Amazon S3, Lambda, DynamoDB, and Amazon SQS are used as core components to increase performance.

Read the Performance Efficiency whitepaper

This architecture is designed with a serverless-first approach, leveraging services such as Step Functions, Lambda, DynamoDB, and Amazon S3 for cost efficiency.

Read the Cost Optimization whitepaper

Consisting of mostly serverless services, this Guidance reduces the number of resources consumed, contributing to greater sustainability.

Read the Sustainability whitepaper

Related content

Ingest Amazon Retail Data into a Serverless Modern Data Architecture

This post provides an overview of a Retail and CPG client application leveraging Amazon Web Services, Inc. (AWS) serverless and managed services, and how to integrate that application with a Modern Data Architecture using SP-APIs.

Learn more

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.