Project overview
Overview of the team
Vendors vs sellers - 1p vs 3p (third party) Vendors are big brands - Adidas, nike Sellers are smaller sellers Vendors have a lot of channels to sell their products, we take care of all their needs - They usually sign a deal with amazon for like a year (sas signature) Service for vendors - sas signature, service for sellers - sas core
- sas core is not yearly (it’s monthly)
We are directly supporting the account management team (face of amazon, our data goes to them primarily)
Product team works hand in hand with tech team (product design, vision)
Account manager will open Winston, open a ticket (with a specific task), and RBS team will go and execute that
Most of the time the direction comes from the program team (owns the interaction between account managers and the rest)
recently our team was only focused on BI engineering, a year back we started focusing on ds and machine learning
tableau is good for limited amounts of data, but when data size is larger, ams spend more time on just pulling data instead of thinking about strategic initiatives for selling partners
ASIN: Each product on amazon has an ASIN (unique identification number). Are these the specific data entries that Sile was talking about in 202007021400?
in the tableau model, for things to be not super slow, we had to restrict some ASINs (really bad limitation)
also, to interact more with the tech team, we want to integrate stuff with Winston (currently has asin reporting and business reporting)
not able to build many asin level reports rn (can only show top 100 for each seller)
with Winston, everything is standardized
will also have a way to surface machine learning models to this pipeline, whenever an AM logs in, it can show a list of sellers with their attrition score (machine learning model)
will be building a lot more models, for sponsored products, will be helpful to surface details to Winston
Seller 360: Show all the attributes about a seller in Winston
Not just requirements from our team, other teams as well
Two parts to the project - building the service, and integrating with Winston
Design considerations
- Use lambda + API gateway 202007011239
- ECS + Fargate 202007011310 (serverless containerization platform)
- EC2 202007011438 (how things are currently built) (deploy your code right into the machine)
API gateway abstracts a lot of things for you (instead of your own API), just have to call function from lambda
uid: 202007010930 tags: #meetings #amazon