AWS Retail Brazil

iFood

Fraud Detection · Marketing Personalization

iFood needed AI infrastructure that could personalize the ordering experience for tens of millions of monthly orders, improve fraud prevention, and standardize model implementation work for internal developers at marketplace scale.

0.5% of the Brazilian Gross Domestic Product (GDP) in 2022
more than 100 AI models
more than 330,000 partner establishments
more than 80 million orders per month

Reported impact

Business outcome

iFood uses AI at the scale of more than 80 million monthly orders and more than 330,000 partner establishments, routing each purchase through more than 100 AI models to personalize recommendations, improve fraud prevention, and speed internal AI development.

  • Customer Experience
  • Productivity Improvement
  • Revenue Growth
  • Risk Reduction

Solution

iFood uses AWS generative AI and ML services to support two high-impact areas of its marketplace: customer experience personalization and internal developer productivity. Amazon Bedrock and Amazon SageMaker give the company standard building blocks for model implementation, experimentation, and deployment across recommendation, fraud-prevention, and delivery-experience workflows. When users open the iFood app and place orders, they are routed through a large portfolio of AI models that tailor recommendations and operational decisions at scale. The same AWS services also help the engineering organization standardize how new AI features are introduced so teams can move faster without rebuilding core infrastructure. This combination lets iFood apply AI throughout the full order journey, from discovery to delivery, while supporting the operational complexity of a national marketplace.

Data flow

User interactions and order journeys in the iFood app pass through AI workflows built on Amazon Bedrock and Amazon SageMaker, which power personalization, fraud prevention, and developer-facing model implementations across the marketplace.

Solution architecture

2 components · 1 layer
  1. Compute
    • Amazon Bedrock Helps standardize and accelerate generative-AI implementations across iFood's marketplace experiences.
    • Amazon SageMaker Provides the central environment for iFood's data, analytics, and AI model work.

Architecture clues

  • Applies AI across the full order journey from recommendation to delivery.
  • Operates at national-marketplace scale inside a single app experience.
  • Uses the same AWS AI stack for customer-facing and developer-facing use cases.

Evidence from the source

Only with AI can I create a personalized experience for each user, from recommendation to fraud prevention.
more than 330,000 partner establishments
more than 80 million orders per month
uses services such as Amazon Bedrock and Amazon SageMaker to ... optimize the customer experience ... and in fraud prevention processes.
when a user enters the app and makes a purchase through iFood, they go through more than 100 AI models.
Transparency Evidence & methodology 100/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. AWS

    iFood customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/ifood-bedrock
    Source type
    Vendor-published customer story
    Published
    Jan 1, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.