Improve Demand Forecasting to Boost Sales on Amazon.com
Publication date: April 5, 2022 (Diagram history)
With this architecture, you can understand prior demand trends and anticipate future demand. Companies that sell products on Amazon.com as first-party vendors want to improve On-Time-In-Full (OTIF) metrics and maximize revenue. You programmatically source vendor performance data from the Amazon.com Selling Partner API and use machine learning (ML) to create future demand predictions.
Demand forecasting diagram
The following steps describe the architecture:
-
Amazon EventBridge initiates scheduled tasks that keep the data fresh with controlled latency.
-
Lambda makes API calls to the Amazon Selling Partner API. An AWS Identity and Access Management (IAM) role attached to the Amazon Vendor Central account entitles access.
-
The Selling Partner API authenticates the calling API and uses the IAM role to authorize access to a specific set of vendor codes.
-
Some API responses are stored in Amazon Simple Queue Service as part of a decoupled microservices architecture.
-
Lambda consumes messages from the Amazon SQS queue. It transforms, persists, and creates notifications.
-
Amazon Simple Notification Service receives notifications on data conditions such as product catalog changes.
-
Amazon DynamoDB acts as an intermediate database. It accepts create, read, update, and delete (CRUD) operations while maintaining data integrity.
-
A scheduled AWS Glue job publishes data to a serverless data lake for long-term persistence.
-
Amazon Simple Storage Service is the persistence tier for the serverless data lake. It serves time-series data at any scale.
-
EventBridge triggers a recurring Amazon Forecast routine. AWS Step Functions manages the workflow that sources demand history to generate future predictions.
-
Amazon S3 data is syndicated to consuming applications. Amazon Quick Sight and Amazon Athena provide business intelligence and SQL capabilities.
Further reading
For additional information, see the following resources:
Diagram history
To receive updates about this reference architecture diagram, subscribe to the RSS feed.
| Change | Description | Date |
|---|---|---|
Initial publication | Reference architecture diagram first published. | April 5, 2022 |
RSS subscription requirement
To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.