Amazon is three businesses in one ticker: North America retail, international retail, and Amazon Web Services. The market debate is whether retail margins can expand while AWS growth re-accelerates and advertising becomes a durable third engine. Each segment has different capital intensity, different competitive dynamics, and different margin ceilings) yet one stock price absorbs all three.
Primary sources, not slide decks, settle that debate. Segment footnotes in the 10-K, capex disclosure in MD&A, and AWS commentary on earnings calls give you the building blocks for a model that respects how Amazon actually reports.
This spotlight uses Amazon's company page, linked filings, financial statements, and MCP tools on Vantafin to trace how segment operating income, capex intensity, and working capital have evolved. Everything here you can replicate for any covered symbol.
Segment economics
From the latest 10-K and 10-Q, pull segment revenue and operating income via GET /financials or get_financials in the MCP server. For a deeper cut, get_revenue_segmentation and GET /revenue-segmentation break revenue by business line. AWS is the margin engine most models overweight: watch year-over-year growth and operating margin because enterprise digestion cycles show up here before they appear in headline revenue.
North America retail drives volume and fulfillment complexity. Logistics costs and wage pressure live in this segment's margin walk. International is a smaller profit contributor today but informs long-term TAM stories when management discusses emerging market infrastructure spend. Compare segment growth rates across at least eight quarters. One quarter of AWS re-acceleration is news; four quarters is a thesis change.
Compare retail peers via the screener when you need context on whether Amazon's retail margin move is company-specific or category-wide.
Capital allocation and filings
Amazon's capex narrative matters as much as quarterly EPS for a stock valued on long-duration cash flows. Search filings with the app's semantic search or search_filings for "fulfillment center" and "data center" capex discussion) the mix between retail and cloud infrastructure spend signals where management sees constraint versus opportunity. Set email alerts for material 8-Ks on leadership or segment reorgs; Amazon's reporting structure changes rarely but matters enormously when it happens.
Check the calendar for earnings dates and dividend events. For macro backdrop, overlay treasury yields when discounting long-duration growth. Higher front-end rates pressure terminal value math on businesses still investing heavily in capacity.
Read buyback and stock-based compensation disclosure alongside capex in GET /financials and insider activity on the insider transactions page. Capital allocation is a portfolio of uses; AWS growth funding that crowds out returns to shareholders reads differently than capex funded by operating cash flow with buybacks on top.
Build your coverage workflow
Save AMZN to a watchlist, monitor live quotes on the LS WebSocket channel, and let the MCP server answer peer comparison questions during earnings prep with screen_stocks and get_valuation_metrics. A repeatable workflow beats heroic effort once a quarter: same checklist, same data sources, faster each time as templates mature.
Plan access on pricing; data philosophy on about. Amazon rewards analysts who respect segment detail. The headline revenue number is the least interesting line in the filing.
Setting up an Amazon research workspace
Mega-cap research rewards parallel primary sources rather than a single summary page. Open the Amazon profile in one tab, financials in another, and filing search in a third. That layout mirrors how analysts work a compounder where segment detail drives valuation swings. After each print, update your memo with new transcript quotes and filing diffs rather than letting a stale thesis linger across quarters.
North America retail, international, and AWS each respond to different macro signals. Read segment footnotes in the latest 10-Q via SEC filings before trusting consolidated growth rates. Cloud growth rate and operating margin band drive a large share of valuation, so track hyperscaler commentary across the ecosystem for demand corroboration rather than relying on a single earnings call.
Fulfillment efficiency and advertising attach rate shift the consolidated margin profile quarter to quarter, so do not annualize one noisy print. Compare capital allocation: buybacks, capex intensity, logistics investment) to peers from your screener so you understand how management balances growth versus returns in the current rate environment.
Competitive and ownership context
Read competitor transcripts and filings for mentions of Amazon as customer, rival, or channel partner. Supply chain and cloud narratives often appear in peer disclosures before they surface in Amazon's own filings. Cross-read spotlight Microsoft for cloud peer context when Azure and AWS commentary diverge in the same earnings season.
Review institutional ownership for ETF sponsorship (which passive and thematic funds hold AMZN and at what weight) rather than treating ownership as a timing signal. Pull /etf-holdings on sector funds you track to see whether index rebalances amplify moves around earnings. Model bull and bear cases on AWS growth, retail margin, and multiple using exported financials history rather than spreadsheet guesses.
Regulatory scrutiny, labor costs, and customer concentration belong on every mega-cap retail thesis. Pull exact language from risk factors via search_filings in the MCP server rather than relying on memory from last year's memo. Set calendar alerts so you never miss the date, and route material 8-K events through email filing alerts on the same channel you use for other mega-cap holdings.
Keeping the dossier actionable
Scenario analysis should stress-test the segments independently before rolling up to consolidated EPS. AWS slowing while advertising accelerates produces a different narrative than the reverse, even if the headline number looks inline. Use bulk quote snapshots for mark-to-market checks on position sizing around catalyst weeks rather than stale closing prices from a prior memo.
When you need a quick refresh before a meeting, the MCP server can pull the latest transcript excerpt on capex or pull guidance language from the most recent filing with citations. Confirm data entitlements on pricing if your workflow pulls extended historical financials or international segment detail beyond the standard profile view.