Tag: mayonnaise

Hellmann’s: Recitweet

In the past, Hellmann’s has used novel ways to encourage consumers to use their mayonnaise for more than just sandwiches. Now, for their latest campaign, they team up with Ogilvy Brazil to create Recitweet.

The use case is instantly familiar. You open the fridge, you see ingredients, and you still do not know what to cook. With Recitweet, consumers tweet their ingredients with the hashtag #PreparaPraMim (“prepare for me” in Portuguese). Hellmann’s replies with a recipe that is designed to use those exact ingredients.

A recipe engine built on a social reply

The mechanism is ingredient matching through a public tweet. The input is a short list of what you have at home. The output is a tailored recipe suggestion delivered back as a tweet reply, so the brand behaves like a lightweight cooking helper rather than a broadcaster.

In FMCG food brands, this utility-led social pattern turns content into a small service that appears at the exact moment the consumer is stuck.

The real question is: can a food brand reliably remove the “what should I cook” hurdle in the channel where people already ask for help. When you can answer fast and specifically, the helper role beats another round of broadcast recipes.

Why it lands

It respects the consumer’s real problem. “I have food, I lack an idea.” The campaign does not start with a product claim. It starts with a decision obstacle, then uses the brand to remove it. That makes the engagement feel earned, because the interaction produces something usable in the next 30 minutes.

Extractable takeaway: If your product is an ingredient, win by solving the “what do I do with what I already have” question. Make the brand the shortest path from inventory to action, using the channel where the consumer already asks for help.

Stealable moves for social utility

  • Constrain the input. A short list of ingredients forces clarity and makes the interaction easy to start.
  • Return a specific next step. A recipe beats a generic tip, because it includes implied quantities, sequence, and outcome.
  • Make the service feel personal, at scale. The reply is the moment of value. Treat it like customer service, not advertising copy.
  • Design for repeat behavior. The best activations are not one-off stunts. They create a habit loop people can use again the next time the fridge looks random.

A few fast answers before you act

What is Recitweet in one sentence?

Recitweet is a Twitter-based recipe helper that takes a list of tweeted ingredients and replies with a recipe designed to use them.

Why use a hashtag like #PreparaPraMim?

It standardizes the request so the brand can find, process, and respond to it consistently, while keeping participation friction low.

What makes this more effective than posting recipes on a website?

It is contextual and initiated by the consumer. The recipe arrives when the person is actively deciding what to cook, using what they say they have.

What is the minimum viable version of this idea?

A constrained ingredient input and a fast, specific reply that gives one clear next step, without forcing the consumer to leave the channel to “go search.”

What is the biggest operational risk?

Response quality and response time. If replies are slow, irrelevant, or repetitive, the “service” framing collapses and it starts to feel like a gimmick.

Hellmann’s: Recipe Receipt to Recipe Cart

Last year Hellmann’s in Brazil came up with a novel way to encourage consumers to use their mayonnaise for more than just sandwiches. The brand teamed up with supermarket chain St Marche to install special software in 100 of its cash registers. When Hellmann’s is scanned, the system matches the rest of the basket to a recipe, then prints it directly on the receipt at checkout. In the first month of the three-month experiment, sales reportedly increased by 44%.

Now, for their new campaign, shopping carts at Pão de Açúcar in São Paulo are mounted with NFC-enabled touchscreen devices. As consumers move through aisles, the touchscreen detects nearby shelf zones and suggests a relevant recipe that uses Hellmann’s. If a recipe is liked, customers can interact with the display to locate ingredients in-store, or share the recipe with friends via email. The activation reportedly involved 45,000 customers, and sales rose by almost 70%.

Two in-store recipe engines, two different moments

The first mechanic works at the end of the trip. It uses the checkout scan as the trigger, then turns the receipt into a personalized cooking prompt based on what you already bought. The second mechanic works during the trip. It uses aisle-level detection to suggest ideas while shoppers are still deciding what to put in the basket, then helps them navigate to the ingredients needed to complete the recipe.

In FMCG shopper marketing, the strongest in-store activations change behavior at the exact point where choices are made.

The real question is whether you can turn a passive product scan into a contextual meal decision while the shopper still has momentum.

When the goal is basket expansion, the in-aisle version is the pattern worth prioritizing because it intervenes before the choice is locked.

Why it lands

Both ideas attack the same barrier. People know mayonnaise, but they default to a narrow usage script. By “usage script” I mean the default, almost automatic way shoppers think a product is used. These executions widen the script with immediate utility, not persuasion. They do not ask shoppers to “remember later.” They hand them a meal idea in the moment, using their own basket and their current aisle as the context. This works because the suggestion arrives at the moment of intent, so the shopper can act immediately instead of relying on memory.

Extractable takeaway: If you want to grow usage occasions, embed the suggestion inside an existing retail behavior. The basket scan, the aisle browse, the store navigation. Then deliver a next-best action that is specific, contextual, and instantly doable.

What to steal for your own retail activations

  • Anchor to a hard trigger. Checkout and aisle location are reliable moments. Build the experience around signals that already exist.
  • Make relevance visible. Recipes work because the shopper can see why this suggestion fits. It uses what they are holding, or what is right in front of them.
  • Keep the interaction short. In-store attention is scarce. One clear suggestion beats ten options and a browsing experience.
  • Close the loop with navigation. A recipe is only valuable if the shopper can find the missing ingredients quickly.
  • Design for shareable utility. Email sharing is not a gimmick here. It turns a private meal problem into a social handoff.

A few fast answers before you act

What is the difference between Recipe Receipt and Recipe Cart?

Recipe Receipt triggers at checkout and prints a recipe based on the basket. Recipe Cart triggers in-aisle and suggests recipes based on where the shopper is, while helping locate ingredients in-store.

Why does this work better than a normal coupon or promotion?

Because it delivers practical utility tied to the shopper’s context. It expands how people use the product by giving a specific meal idea, not just a price incentive.

What data does a concept like this actually need?

Only basket contents at checkout, or aisle location for the cart experience, plus a curated recipe database that can match ingredients to suggestions.

What is the biggest execution risk?

Low relevance. If the suggested recipes feel generic or mismatched to what shoppers are buying and seeing, the experience becomes noise and loses trust fast.

What is the simplest version to pilot first?

Pilot one trigger and one matching rule set, then measure whether shoppers actually add missing ingredients. Start with whichever moment you can instrument cleanly, checkout or aisle.