Apply as a Vendor

Building a Simple Win-Back Campaign for Lapsed Guests

by | Feb 11, 2026 | Marketing & Repeat Orders

On This Page

A guest who ordered once, months ago, and never came back looks lost on paper. In practice, a short, specific win-back message often recovers a real share of that group, since many lapsed guests simply drifted rather than made an active decision to stop.

Defining "Lapsed" Clearly First

A reasonable definition varies by vendor type, a coffee shop's lapsed guest looks different from a catering company's, but picking a specific window, say 60 or 90 days without an order, gives the campaign a clear target list to work from.

A vendor with genuinely frequent guests, like a coffee shop where a regular might order several times a week, may need a shorter window, like 30 days, to catch a real drop-off early. A vendor with naturally infrequent orders, like a caterer whose average guest only books a few times a year, needs a much longer window before absence actually signals anything meaningful.

What a Simple Campaign Actually Includes

  1. Identify guests who haven't ordered within the chosen lapsed window.
  2. Send a short, specific message referencing something they've ordered before, if known.
  3. Include a clear, simple way to order again, not a generic link to the homepage.
  4. Track whether the specific message coincided with an order from that guest.

None of these four steps require anything beyond the guest list a vendor already has. A win-back campaign built this simply can run in an afternoon, without any dedicated software purchase or a marketing agency's involvement, which makes it one of the more accessible tactics available to a vendor of any size.

Keeping It Low Pressure

A win-back message reads better as a genuine "we noticed and wanted to reach out" than as a hard sell. An overly aggressive discount can feel like a bribe rather than a reconnection, particularly if it arrives paired with heavy pressure to act immediately.

A message that simply asks whether everything was alright with the last order, without any offer attached at all, can sometimes outperform a discount-led message, since it reads as genuine curiosity about the guest's experience rather than an attempt to buy back their business.

Segmenting Lapsed Guests by Their Own History

Not every lapsed guest lapsed the same way. A guest who ordered ten times over a year and then stopped is a meaningfully different case from a guest who ordered exactly once and never returned, and treating both with an identical message misses an opportunity to tailor the approach. The frequent former guest likely needs a simple reminder that the door is still open, while the single-order guest may need a stronger reason to give the vendor a second try at all.

How AUANI Handles This

AUANI's exportable guest list makes it possible to identify exactly which guests fall into a lapsed window, based on real order history rather than a guess.

Because the list already includes each guest's past order history, a vendor can reference something specific in the win-back message directly from that data, rather than sending a generic note that reads the same to every recipient regardless of what they've actually ordered before.

That same export also makes it straightforward to build the frequent-versus-single-order segmentation described above, since both groups can be filtered directly from existing order history rather than reconstructed manually from memory or a separate spreadsheet.

Running this same win-back check on a recurring schedule, rather than as a one-time project, keeps the lapsed-guest list current as new guests naturally drift out of their own active ordering window over time.

Frequently Asked Questions

What's a reasonable lapsed window to use?

It depends on typical ordering frequency for the vendor; 60 to 90 days is a common starting point for many food and drink categories.

Does a win-back message need a discount to work?

Not necessarily; a genuine, low-pressure reconnection message can work on its own, though a modest, time-limited incentive can help for guests who need more of a nudge.

How often should a win-back campaign run?

Periodically, rather than continuously, since the same lapsed guest shouldn't be messaged repeatedly without a meaningful gap.

Can this be automated based on order history?

Yes, since the guest list is built from real order data, identifying who has crossed the lapsed threshold can be done on a regular schedule.

What is the wider guide this fits into?

The marketing & repeat orders guide covers this alongside message frequency and guest list data limits.

Should a frequent past guest and a one-time guest get the same win-back message?

Ideally not; a frequent past guest usually just needs a simple reminder, while a one-time guest may need a stronger incentive to give the vendor a second try.

For the wider picture on repeat orders, see the marketing & repeat orders guide.

What a Guest List Can and Can’t Actually Tell a Vendor

by | Feb 9, 2026 | Marketing & Repeat Orders

On This Page

A guest list is genuinely valuable data: who ordered, when, and often what they ordered. It's easy to treat that as a complete picture of guest behavior, when it actually only covers what happened, not why. Knowing the limits keeps a vendor from over-interpreting what the data can support.

What a Guest List Can Reliably Tell You

  • Who has ordered, and how often, over a given period.
  • Which items or combinations specific repeat guests tend to choose.
  • Whether a specific marketing push coincided with a change in order volume.

All three of these are genuinely reliable once there's enough order history behind them, and none require guesswork to interpret, since they're built directly from what guests actually did rather than from a survey or an assumption about behavior.

What It Can't Tell You

A guest list can't explain why someone stopped ordering, whether they moved away, found somewhere else, or simply changed habits. It also can't capture guests who never ordered at all, which means it says nothing about people who never became guests in the first place.

It also can't distinguish between a guest who was genuinely dissatisfied and one who simply moved on for reasons that have nothing to do with the vendor, a change in commute, a life event, or a shift in habits entirely unrelated to food quality or service. Treating every lapsed guest as evidence of a specific problem risks chasing a fix for something that was never actually broken.

Filling the Gap Where Data Runs Out

A short, low-pressure win-back message to a lapsed guest can surface some of the "why" a guest list alone can't, since a direct reply or even a lack of response still adds context the raw order data didn't have.

A brief, genuine question, something as simple as asking whether everything was alright with a recent order, tends to get a more honest response than a formal survey, since it reads as a real check-in rather than a data-collection exercise the guest has to set aside time for.

Keeping that outreach occasional rather than routine also matters, since a guest who feels checked in on every time they go quiet is more likely to find it intrusive than genuine, which can undo whatever goodwill the message was meant to build in the first place.

Resisting the Urge to Over-Interpret a Small Sample

A newer vendor with only a few dozen guests on the list can easily read too much into a small pattern, treating three guests who happened to order the same item on the same night as a meaningful trend rather than coincidence. Guest list data becomes genuinely reliable at a larger scale, and drawing firm conclusions from a handful of data points risks steering decisions based on noise rather than a real signal.

A reasonable check is asking whether the same pattern would still look meaningful if just one or two of those data points had gone differently. If a small change in the sample would flip the conclusion entirely, the pattern probably isn't sturdy enough yet to act on.

Waiting for a slightly larger sample before acting on a pattern costs little in most cases, while acting too early on a coincidence can mean changing a menu or a marketing approach based on something that was never actually a trend.

How AUANI Handles This

AUANI's exportable guest list and menu analytics provide the reliable order-level data; interpreting the gaps still depends on a vendor reaching out directly where the data alone can't explain a pattern.

That combination, reliable data for the questions it can actually answer, and a direct check-in for the ones it can't, tends to give a far clearer picture than either approach would on its own.

Frequently Asked Questions

Can a guest list predict who will stop ordering next?

It can flag guests whose ordering frequency has already dropped, but it can't reliably predict future behavior on its own.

Does menu analytics fill in the gaps a guest list can't?

It adds item-level detail, but it still describes what happened rather than why, the same fundamental limit.

Is a win-back message the only way to learn why a guest left?

It's one of the more direct ways, though even then a lack of response is itself limited information rather than a full answer.

Should a vendor avoid drawing conclusions from guest list data at all?

No, it's genuinely useful for spotting patterns, just worth pairing with direct outreach rather than treating as a complete explanation on its own.

What is the wider guide this fits into?

The marketing & repeat orders guide covers this alongside menu analytics and message frequency.

How large should a guest list be before drawing real conclusions from it?

There's no fixed number, but a handful of data points shouldn't be treated as a confirmed trend; patterns become more reliable as the list grows.

For the wider picture on repeat orders, see the marketing & repeat orders guide.

Turning a Slow Weeknight Into a Repeat-Order Opportunity

by | Feb 4, 2026 | Marketing & Repeat Orders

On This Page

A predictably slow night, a rainy Tuesday, a quiet mid-week evening, often gets treated as an unavoidable fact of doing business. It doesn't have to be. A guest list built from real past orders is exactly the tool needed to turn a known slow period into a targeted, repeatable opportunity.

Why This Works Better Than a General Ad

A message sent to guests who have already ordered before reaches people with a proven willingness to order from this specific vendor, which tends to convert better than a broad ad aimed at people with no prior relationship.

A paid ad campaign also costs money regardless of whether it converts, while a message to an existing guest list costs essentially nothing beyond the time to write it. That cost difference alone makes the guest-list approach worth trying first, even before considering the higher likelihood of conversion from an audience that already knows and trusts the vendor.

What a Slow-Night Offer Can Look Like

  • A specific, time-boxed offer tied only to the slow night, not run continuously.
  • A reminder of a specific item the guest has ordered before, rather than a generic message.
  • A message timed early enough in the day that a guest can actually plan around it.

Framing the message around the specific slow night by name, rather than a vague "order soon" prompt, also helps it read as a genuine, occasional invitation instead of a routine advertisement. A guest is generally more receptive to a specific, honest nudge tied to a real quiet evening than to language that sounds like it could have been sent on any day of the week.

Measuring Whether It Actually Worked

Comparing order volume on the targeted night against a typical slow night baseline, rather than against a busy night, gives a fair read on whether the specific push moved the number.

Running the same push for a few consecutive occurrences of the slow night, rather than judging it off a single attempt, gives a clearer picture too, since any one night can be skewed by weather, a local event, or simple chance in either direction.

Keeping a simple running log of results across each attempt also makes it easier to spot whether the lift is genuinely holding steady or gradually fading as guests grow accustomed to the same recurring message.

A Worked Example

A vendor whose typical Tuesday brings in 20 orders sends a message to its 300-person guest list the morning of a Tuesday, reminding guests of a specific item they've ordered before and noting it's available that evening. If even 4% of that list places an order specifically because of the message, that's 12 additional orders, pushing the night to 32 orders, a 60% lift over the usual baseline from a single, low-cost message rather than a paid ad campaign.

How AUANI Handles This

AUANI's exportable guest list and menu analytics, included on the account, make it possible to identify past guests and see whether a specific slow-night push actually changed order volume.

Because the guest list already segments by order history, a vendor can also test whether the push performs differently among guests who order frequently versus those who've only ordered once, refining the approach further as more of these pushes run over time.

Over several attempts, this kind of testing turns a single good idea into a genuinely reliable, repeatable tactic, rather than a one-time success that's never fully understood well enough to run consistently going forward.

A vendor with more than one predictably slow period, an early weekday lunch as well as a weeknight, can apply the same approach separately to each, building a small set of proven, repeatable pushes rather than a single tactic tried once.

Frequently Asked Questions

Does this work for a business that doesn't have a clearly slow night?

The same targeting approach can apply to any predictable lull, not just a specific weeknight, as long as the pattern is real.

Should a slow-night offer run every week indefinitely?

Running it as a recognizable, occasional push tends to work better than making it a permanent standing discount guests come to expect.

Does this require a large guest list to work?

No, even a modest list of proven repeat guests can produce a meaningful lift relative to a typical slow night.

Can this be combined with the loyalty program?

Yes, a slow-night push can highlight loyalty progress alongside the offer itself, reinforcing both at once.

What is the wider guide this fits into?

The marketing & repeat orders guide covers this alongside message frequency and menu analytics.

Is a guest-list message really cheaper than running an ad?

Yes, a message to an existing list costs essentially nothing beyond the time to write it, unlike a paid ad campaign that costs money regardless of results.

For the wider picture on repeat orders, see the marketing & repeat orders guide.

How Often Is Too Often to Message a Repeat Guest Anyway

by | Jan 30, 2026 | Marketing & Repeat Orders

On This Page

A guest list is a limited resource in a specific sense: every message sent spends some of the guest's patience with that channel. Send too rarely and a vendor is invisible; send too often and a guest opts out or starts ignoring messages entirely, which costs future value the list could have delivered.

The Signs of Overmessaging

  • A rising opt-out rate over consecutive sends.
  • Falling open or click rates on messages that used to perform well.
  • Guests specifically mentioning feeling spammed, whether directly or in reviews.

Any single one of these on its own might just be noise, a slightly rougher week isn't necessarily a trend. Watched together across several consecutive sends, though, they form a pattern that's hard to miss: a channel getting quietly worn down, one message at a time, well before a guest ever bothers to formally opt out.

Finding a Reasonable Baseline

There's no universal number that works for every vendor, but a baseline of roughly one to two messages a month, reserved for genuinely relevant updates, tends to avoid fatigue while still keeping the vendor visible.

A vendor genuinely uncertain where to start can begin conservatively, closer to one message a month, and watch open and opt-out rates over the following few sends before considering an increase. It's far easier to add frequency once the data shows room for it than to win back a guest who already opted out from being messaged too often too soon.

This asymmetry is worth remembering whenever the temptation arises to message more often just because a specific promotion feels worth pushing. The downside of one message too many, a lost subscriber, tends to outweigh the upside of one extra send that might not have moved the needle much anyway.

Relevance Matters More Than Raw Count

  1. Send only messages a guest would plausibly want to receive, not filler content.
  2. Segment where possible, so a lapsed guest and a frequent one aren't getting identical messages.
  3. Watch opt-out and open rates directly rather than guessing at the right frequency.

A message tied to something a guest actually cares about, a seasonal item they've ordered before, a location update for a food truck, a reminder that hasn't been sent in months, tends to survive a higher frequency than the same volume of generic promotional content would. The guest's tolerance is really for irrelevance, not for the raw number of messages received.

Recovering After a Frequency Mistake

A vendor that notices opt-outs climbing after a burst of messages doesn't need to abandon the channel entirely, cutting back to a lower, more conservative frequency for a stretch, and sending only clearly relevant updates during that stretch, tends to rebuild trust with the remaining list over time. Guests who already opted out generally shouldn't be re-added without a fresh, explicit opt-in, since re-messaging someone who already opted out risks a second, more permanent disengagement.

Treating a rising opt-out rate as an early warning worth acting on immediately, rather than something to address only once it's already become a clear trend, tends to make the eventual recovery period considerably shorter.

How AUANI Handles This

AUANI's exportable guest list, included on every tier, gives a vendor direct ownership of this channel, so the vendor controls frequency and targeting directly rather than through a third-party platform's own rules.

That direct ownership matters specifically here, since a platform that owns the guest relationship might have its own incentives around messaging frequency that don't necessarily align with what's actually best for the vendor's own long-term guest relationships.

Owning the list also means a vendor can set its own frequency policy once and apply it consistently, rather than working around limits or defaults imposed by a third-party platform's own messaging rules.

Frequently Asked Questions

Is there an ideal universal messaging frequency?

No, it varies by vendor and audience, though roughly one to two relevant messages a month is a reasonable starting baseline.

Does SMS have a lower frequency tolerance than email?

Generally yes, guests tend to be less tolerant of frequent texts than frequent emails, given how directly SMS interrupts attention.

What's the first sign frequency has gone too high?

A rising opt-out rate or a noticeable drop in open and click rates on messages that previously performed well.

Should every guest get the same message at the same frequency?

Not ideally; segmenting by how recently or often a guest has ordered tends to perform better than one blanket frequency for everyone.

What is the wider guide this fits into?

The marketing & repeat orders guide covers this alongside channel choice and loyalty.

Should a guest who already opted out be messaged again later?

Generally no, without a fresh, explicit opt-in; re-messaging someone who already opted out risks permanently losing that guest as a contact.

For the wider picture on repeat orders, see the marketing & repeat orders guide.

Why a Discount Code Rarely Builds Real Loyalty At All

by | Jan 28, 2026 | Marketing & Repeat Orders

On This Page

A discount code is easy to set up and easy to measure, which makes it tempting to treat as a loyalty strategy on its own. It isn't one. A code changes behavior for exactly the order it's applied to, and once it stops being offered, there's usually nothing underneath it keeping the guest around.

What a Discount Code Actually Does

A code reduces the price of one transaction. It doesn't build a reason for a guest to come back beyond wanting the same discount again, which trains guests to wait for a deal rather than to value the vendor itself.

That training effect is easy to miss because it looks identical to loyalty in the short term, a discount-driven order still shows up as a repeat order on a sales report. The difference only becomes visible once the code disappears, at which point a genuinely loyal guest keeps ordering while a discount-trained one simply waits for the next deal, wherever it happens to appear.

Why This Is Different From Actual Loyalty

  • A loyalty mechanic, like a punch card, rewards a pattern of behavior building over time, not a single transaction.
  • A discount code costs something on every order it touches; a loyalty reward typically costs something only once earned.
  • Loyalty programs tend to reinforce an existing habit; discount codes tend to just subsidize a price-sensitive decision.

When a Discount Code Still Makes Sense

A time-limited code aimed at a specific, narrow goal, like encouraging a genuinely first-time direct order, still has a real place. The problem is running one indefinitely as a substitute for an actual retention mechanic.

The distinguishing question is whether the code has a clear end condition attached to a specific behavior, like a first order or a lapsed guest's return, rather than simply running on and on because it was never actively turned off. A code with no natural stopping point tends to drift into becoming the default price rather than a genuine incentive.

Setting that end condition explicitly, in writing, before the code ever goes live removes the temptation to keep extending it indefinitely once it starts feeling routine rather than special to the guests using it.

A Worked Comparison

A vendor running a standing 15% discount code across every order pays that discount on every single transaction, indefinitely, whether or not the guest would have ordered anyway. Over 100 orders a month at a $30 average, that's roughly $450 a month given up, permanently, with no guarantee any of those guests are actually more loyal than they would have been without the code.

A punch-card loyalty program structured around, for example, a free item after every tenth order costs the vendor one item's cost per ten paid orders, a fraction of what a blanket 15% discount gives up, while still rewarding exactly the guests who are actually building a repeat pattern rather than subsidizing every order regardless of who's placing it.

How AUANI Handles This

AUANI's punch-card loyalty program, included on every tier, is built around rewarding an accumulating pattern of orders rather than discounting any single one.

Because it's included at no added cost on every tier, a vendor doesn't need to weigh the program's cost against a discount code's simplicity, the loyalty mechanic is already available to replace or complement whatever discounting habit a vendor might otherwise default to.

A vendor already running a standing discount code can also transition guests toward the loyalty program gradually, rather than removing the code all at once, giving regulars time to notice and start relying on the new mechanic before the old habit disappears entirely.

Frequently Asked Questions

Is a discount code ever worth using at all?

Yes, for a narrow, time-limited goal like a first direct order, but not as an ongoing substitute for a loyalty mechanic.

Does a loyalty program cost less than running discount codes?

Generally yes, since a loyalty reward typically costs something only once earned, while a recurring code costs something on every order it touches.

Can a vendor run both a loyalty program and occasional codes?

Yes, many vendors do, using a loyalty program as the default and reserving codes for narrow, specific goals.

Does AUANI charge extra for the loyalty program?

No, punch-card loyalty is included on every tier, including Free, with no separate fee.

What is the wider guide this fits into?

The marketing & repeat orders guide covers this alongside channel choice and menu analytics.

How much can a standing discount code actually cost over time?

It scales with every order it touches, so a vendor running a 15% code across 100 monthly orders at a $30 average gives up roughly $450 a month indefinitely, far more than a typical punch-card reward structure.

For the wider picture on repeat orders, see the marketing & repeat orders guide.

How Menu Analytics Reveals Which Items Bring Guests Back

by | Dec 18, 2025 | Marketing & Repeat Orders

On This Page

A vendor's best-selling item by total volume isn't automatically the item that keeps guests coming back. A high-volume item might be a one-time impulse order, while a lower-volume item could be quietly responsible for most of a vendor's repeat business. Total sales numbers alone can't tell the difference.

A "popular" item sells in high volume across many different guests. A "sticky" item shows up disproportionately often in the order history of guests who've ordered more than once. The two overlap sometimes, but not always, and promoting the wrong one wastes marketing effort.

A seasonal special, for example, can post huge numbers for a few weeks purely on novelty, then disappear from the menu without ever building a habit. A quieter, always-available item that a smaller group of guests order again and again is doing far more for actual repeat business, even if its total volume never looks as impressive on a sales report.

What to Look for in the Data

  • Which items appear most often in repeat guests' order history specifically, not total order volume.
  • Whether a repeat guest tends to reorder the exact same item or explore the menu each time.
  • Whether any specific item correlates with a guest becoming a repeat customer after trying it.

Using This to Guide Marketing

Once a vendor knows which items correlate with repeat behavior, that's the item worth featuring in a loyalty reward, a Google Post, or a repeat-order email, rather than defaulting to whatever sells the most in raw volume.

This also changes what a new-guest first offer should highlight. Leading a first-time discount with the sticky item, rather than whatever's currently trending, gives a new guest their first taste of the exact dish most likely to bring them back a second time, instead of leaving that discovery to chance.

The same logic applies to staff recommendations at checkout or on the phone, since pointing a new or uncertain guest toward the item with the strongest track record for producing repeat orders is a more evidence-based recommendation than defaulting to whatever the staff member happens to personally prefer.

A Simple Illustration

A vendor might find that a seasonal special sells the highest total volume in a given month, since it's new and novel, but almost never appears twice in the same guest's order history, since guests try it once out of curiosity rather than because it became a favorite. Meanwhile a specific sandwich, selling in lower total volume, shows up repeatedly across the order history of the vendor's most frequent guests, the item that's quietly doing the real work of bringing people back, even though it never tops the raw sales chart.

How AUANI Handles This

AUANI's menu analytics, included on the Monthly tier, tracks item-level order data that can surface these patterns directly, rather than requiring a vendor to piece it together manually from raw sales totals.

Because the data updates continuously as new orders come in, a vendor isn't stuck with a one-time snapshot, the sticky-item picture can shift as menu items change or seasonal patterns emerge, and the analytics reflect that shift automatically rather than requiring a manual recalculation.

Checking this periodically, rather than once and never again, keeps the vendor's marketing focus aligned with whichever item is actually earning repeat business right now, rather than one that mattered most several menu changes ago.

A vendor that builds this into the same monthly review used for other metrics gets the benefit without adding a separate task, since the data is already sitting in the same dashboard being checked regardless.

Frequently Asked Questions

Is menu analytics included on the Free tier?

No, menu analytics is a Monthly tier feature, alongside the hosted website and 0% direct ordering widget.

How much order history is needed before patterns become useful?

More history generally produces clearer patterns, though even a few months of data can start to surface a meaningful signal.

Can menu analytics identify items to remove from the menu?

It can help identify consistently low-performing items, though a full removal decision usually considers factors beyond just the data.

Does a sticky item need to be a vendor's most expensive item?

Not necessarily, sticky items are defined by their correlation with repeat behavior, not their price point.

What is the wider guide this fits into?

The marketing & repeat orders guide covers this alongside turning delivery guests direct and channel choice.

Can a highest-volume item and a stickiest item be completely different items?

Yes, that's a common pattern; a novel or seasonal item often drives one-time volume while a quieter staple item drives actual repeat behavior.

For the wider picture on repeat orders, including turning delivery guests direct and channel choice, see the marketing & repeat orders guide.