Apply as a Vendor

Designing a Mobile Menu That Actually Works on a Phone

by | Jan 23, 2026 | Restaurant Websites & Direct Ordering

On This Page

A menu designed to look good on a wide desktop screen, multiple columns, small text, dense layout, often becomes genuinely hard to use once it's squeezed onto a phone. Since most online orders now happen on a phone, that mismatch directly costs completed orders.

What Makes a Mobile Menu Work

  • A single readable column rather than a multi-column desktop layout squeezed down.
  • Clear category headers a guest can jump between without endless scrolling.
  • Large enough tap targets for adding items and adjusting quantities without mis-taps.
  • Prices and item names visible without needing to zoom in.

A search or filter option, even a simple one, adds real value once a menu grows past a couple dozen items, since scrolling through an entire category list to find one specific dish becomes its own source of friction on a small screen, especially for a guest who already knows exactly what they want to order.

Common Mistakes on a Small Screen

A PDF menu embedded as an image is one of the most common problems, since it forces zooming and panning on a phone and often can't be tapped to add an item directly. A long, uncategorized list with no way to jump between sections creates a similar problem even without a PDF involved.

Modifier lists that expand into a long, unstructured block of checkboxes are another common failure point, particularly for a build-your-own item with many options. Grouping related modifiers together, showing only a few at a time, and clearly separating required choices from optional ones keeps a customizable item usable on a small screen rather than turning it into a wall of text a guest has to scroll through carefully.

Auto-playing background video or animation on a menu page is another mobile-specific problem, since it consumes data and slows page load noticeably on a cellular connection, exactly the kind of friction that costs a completed order during a guest's limited attention window.

Testing It Directly

  1. Open the actual ordering flow on a real phone, not a resized desktop browser window.
  2. Try adding a customizable item, like a build-your-own pizza, from start to finish.
  3. Note anywhere text needed zooming or a tap missed its target.

Why This Matters More During a Rush

A minor mobile friction, a tap that occasionally misses its target, text that needs a quick zoom, is easy to shrug off during a slow test run. During a genuine lunch or dinner rush, when a guest is ordering quickly on a short break or in between other tasks, that same friction has a much higher chance of ending in an abandoned cart rather than a completed order. The busiest ordering windows are exactly when a mobile menu's design gets stress-tested the hardest.

This is exactly why a single calm test run rarely tells the full story. Testing the same flow again during an actual busy window, ideally while genuinely distracted or rushed, gives a far more honest read on how the menu performs under the conditions it actually needs to handle.

How AUANI Handles This

AUANI's direct ordering widget and hosted website, included on the Monthly tier, are built mobile-first rather than as a desktop layout adapted afterward.

That mobile-first approach means the tap targets, modifier grouping, and category navigation described above are handled by the underlying design from the start, rather than something a vendor needs to specify or configure separately during setup.

A vendor can still run the same test-run-during-a-rush check described earlier, since the underlying design being mobile-first doesn't guarantee every specific menu item is set up cleanly, only that the foundation supports getting it right.

Frequently Asked Questions

Does a PDF menu ever work well on mobile?

Rarely, since it typically requires zooming and can't support tappable ordering the way a structured digital menu can.

How many menu categories are too many for mobile?

There's no fixed number, but categories should be specific enough to be useful without requiring endless scrolling through unrelated items.

Does font size really affect conversion?

Yes, text small enough to require zooming adds friction that can cost completed orders, particularly during a busy ordering window.

Is a build-your-own item harder to design for mobile?

It requires more careful structuring, since more selectable options need to fit clearly on a small screen without feeling overwhelming.

What is the wider guide this fits into?

The Restaurant websites & direct ordering guide covers this alongside homepage design and checkout conversion.

When does mobile menu friction cost the most orders?

During the busiest ordering windows, since a guest ordering quickly during a rush is far less tolerant of a mis-tap or a zoom-in than someone browsing casually.

For the wider picture on websites and direct ordering, see the Restaurant websites & direct ordering guide.

Should a Restaurant Website Actually Run a Blog Too

by | Jan 20, 2026 | Restaurant Websites & Direct Ordering

On This Page

A restaurant blog has a bad reputation, mostly because so many of them exist just to exist: a post announcing a new hire, a generic "why our food is great" piece, published once and never followed up on. Done differently, a small set of pages that actually answer questions guests search for can build lasting search visibility a menu page alone can't.

What Doesn't Work

Generic content with no specific question behind it rarely ranks for anything and rarely gets read. A post that could have been written about any restaurant, with the name swapped out, isn't doing real work.

A staff announcement or a generic "visit us today" post also rarely answers anything a search engine would match to an actual guest question, which means it has almost no path to ever showing up in search results in the first place. That kind of content might still be worth sharing on social media, where the audience already follows the business directly, but it isn't doing meaningful work as a page on the website itself.

What Actually Works

  • Answering a specific question guests actually search, like a seasonal menu detail or a dietary accommodation.
  • Covering something genuinely specific to the restaurant: a neighborhood event, a sourcing story, a menu change explained.
  • Content that links naturally to the direct ordering page or a specific menu item.

How Much Content Is Actually Needed

A small number of well-targeted pages, published consistently over time, tends to outperform a large volume of generic posts published in a single burst and then abandoned. Consistency matters more than volume.

A realistic pace for most single-location vendors is one well-researched page every few weeks rather than several rushed posts in a single week followed by months of silence. Search engines reward a steady pattern of genuinely useful pages appearing over time far more than a short burst of activity that never continues, since the burst pattern looks abandoned the moment it stops.

Finding Real Questions Worth Answering

The most reliable source of good topics is the questions guests already ask in person or by phone: whether a specific dish can be made without a particular allergen, whether the restaurant can accommodate a large group without a reservation, what a specific regional dish actually is for a guest unfamiliar with the cuisine. Each of those is also a real search query someone nearby is typing into Google, which makes a page built around it useful to two audiences at once rather than written purely to satisfy a search algorithm.

Staff who actually work the counter or answer the phone tend to hear these repeated questions far more often than an owner does, which makes them a genuinely useful source to check with directly before assuming which topics are actually worth writing about.

How AUANI Handles This

AUANI's hosted website, included on the Monthly tier, supports this kind of content directly, and it works alongside the Google visibility suite's ranking data to show whether specific pages are actually gaining visibility over time.

Seeing which specific pages are actually gaining traction over time also helps a vendor decide where to invest further effort, rather than continuing to write on a topic that never gained any real visibility to begin with.

That same visibility data also makes it easier to spot which topics resonate most with local searchers specifically, information that can then shape what the next page covers rather than guessing at the next topic blind.

A vendor without much time to write regularly can still benefit from this approach at a slower pace, since even one genuinely useful page published every couple of months outperforms a blog that never gets started at all.

Frequently Asked Questions

How often should a restaurant blog publish?

Consistency matters more than frequency; a realistic, sustained schedule beats an ambitious one that stops after a few posts.

Does blog content need to mention the menu directly?

Not every post, but linking naturally to a specific item or the ordering page where relevant helps connect the content to actual orders.

Can a single food truck or small vendor benefit from this too?

Yes, the same principle, answering real questions guests search, applies regardless of vendor size or category.

Does AUANI provide help writing this kind of content?

AUANI's hosted website supports it directly; the specific writing work is generally handled by the vendor or a resource of their choosing.

What is the wider guide this fits into?

The Restaurant websites & direct ordering guide covers this alongside homepage design and checkout conversion.

Where's the best place to find topics for this kind of content?

The questions guests already ask in person or by phone tend to be genuine search queries too, making them a reliable starting point over invented topics.

For the wider picture on websites and direct ordering, see the Restaurant websites & direct ordering guide.

What Belongs Above the Fold on a Restaurant Homepage

by | Jan 16, 2026 | Restaurant Websites & Direct Ordering

On This Page

"Above the fold" is whatever a guest sees before scrolling, and on a phone that's a small amount of space to make a first impression in. A homepage that buries the ordering button, the hours, or the actual name of the restaurant below a large hero image is asking a guest to work harder than they should have to.

What Actually Needs to Be There

  • The restaurant's name and cuisine or category, immediately clear without guessing.
  • A visible way to order, whether that's a button linking to the direct ordering widget or the widget itself.
  • Current hours or an open and closed status.
  • A clear way to find the address or get directions.

None of these elements require much visual space individually, which is exactly why there's rarely a good excuse for a hero image to crowd all four out at once. A well-designed homepage can include a strong visual and still keep every one of these functional elements visible in the same first screen.

What Commonly Crowds This Out

A full-screen hero image or video with no text overlay is the most common offender, since it looks polished but pushes every functional element below the first screen. A rotating slideshow of photos before any ordering link appears does the same thing.

A navigation menu with too many links can crowd the same space too, particularly on mobile, where each additional menu item takes up screen real estate that could otherwise go toward the ordering button or hours. A shorter, more focused navigation tends to leave more room for what a guest actually came to the page to do.

Testing This Directly

  1. Open the homepage on an actual phone, not just a desktop browser.
  2. Note everything visible before scrolling at all.
  3. Confirm a guest could order or find hours without scrolling if they needed to.

Testing this with someone unfamiliar with the site, rather than the owner who already knows where everything is, tends to surface real friction faster. Someone seeing the homepage for the first time will hesitate at exactly the spots a guest genuinely searching for how to order would also hesitate.

This kind of fresh-eyes test costs nothing beyond asking a friend or family member for five minutes of their time, which makes it one of the cheapest ways available to catch a real conversion problem before it costs actual orders.

Repeating the same test every few months, rather than treating it as a one-time check done right after launch, catches drift that creeps in over time as new promotions, banners, or seasonal graphics get added to the homepage without anyone revisiting whether the original layout still holds up.

A guest who typed the restaurant's name directly into their browser already has some intent to visit. A guest arriving from a Google search result, deciding between several nearby options in the same tab session, has far less patience and far less commitment to any single homepage. That guest is the one most likely to leave immediately if the ordering button, hours, or address aren't visible right away, since a competitor's homepage is one tap back away in the search results.

Designing the first screen for that comparison-shopping guest, rather than the loyal regular who already knows where everything is, tends to produce a homepage that actually converts better for both, since a page that's fast and obvious for a stranger is rarely worse for someone who already knows the restaurant well.

How AUANI Handles This

AUANI's hosted website, included on the Monthly tier, is built around keeping the ordering path visible without requiring a guest to scroll past decorative content first.

Frequently Asked Questions

Does a large hero image always hurt conversion?

Not always, but it hurts when it pushes ordering, hours, and location below the first screen with no functional element visible.

Should the direct ordering widget be visible immediately?

Ideally yes, or at minimum a clearly visible button leading straight to it, rather than requiring a guest to find a menu first.

Does this matter more on mobile than desktop?

Yes, since mobile screens show far less before scrolling, making the choice of what's above the fold more consequential.

Is an open or closed status necessary if hours are listed?

It helps, since a guest often wants a quick answer without having to interpret a full hours table.

What is the wider guide this fits into?

The Restaurant websites & direct ordering guide covers this alongside hosted websites and checkout conversion.

Does above-the-fold layout matter more for guests arriving from search than direct visitors?

Yes, a guest comparing options from a search results page has far less patience and will simply return to search if the essentials aren't immediately visible.

For the wider picture on websites and direct ordering, see the Restaurant websites & direct ordering guide.

What Actually Makes a Guest Abandon Checkout Midway

by | Dec 4, 2025 | Restaurant Websites & Direct Ordering

On This Page

A guest who built a cart and left without ordering almost never decided the food wasn't worth it. Far more often, something in the checkout process itself, an unexpected step, a slow page, an unclear total, quietly ended the order before it was placed.

The Usual Suspects Behind Abandonment

  • An account requirement forced before checkout can even begin.
  • Fees or taxes that only appear at the final step, with no earlier estimate.
  • A slow-loading page, especially on mobile during a busy ordering window.
  • Too many required fields for information that isn't actually necessary.
  • No clear estimated time for pickup or delivery before the guest commits.

Any one of these on its own might only cost a handful of orders a week. Stacked together on the same checkout flow, though, they compound: a guest who survives a slow load only to hit a surprise fee, then an unnecessary account prompt, is far more likely to give up than one facing any single friction point alone.

What to Check First

  1. Test the checkout flow on an actual phone, not just a desktop browser.
  2. Confirm the total price is visible and accurate before the final confirmation step.
  3. Remove any account creation requirement that isn't strictly necessary to complete an order.
  4. Check page load time during a typical peak ordering hour, not just when traffic is low.

Doing this once as an actual guest, not a manager assuming the flow works, tends to surface more real friction than any amount of guessing. Placing a real test order on a phone during a genuinely busy hour shows exactly what a guest experiences, rather than the smoother version an owner might picture from memory.

Repeating this same test every few months, rather than once at launch and never again, catches friction that creeps in gradually, a slower page after a design update, a new required field added without much thought, that a single early test would never reveal.

The Specific Cost of a Surprise Fee at the Last Step

Of all the friction points on this list, an unexpected fee appearing only at the final confirmation screen tends to be the single most reliable way to lose an otherwise-committed guest. A guest who has already built a cart and started checkout has effectively decided to order; seeing the total jump unexpectedly right before confirming reads as a bait-and-switch, even when the fee itself is legitimate, and often ends the order entirely rather than just prompting a shrug and a continue.

Showing the same fee earlier in the flow, even as an estimate rather than an exact figure, largely defuses this reaction, since the guest has time to absorb the true total before becoming psychologically committed to a lower number.

This applies just as much to delivery fees and service charges as it does to tax, since a guest reacts to any unexpected addition the same way regardless of what label the line item actually carries.

How AUANI Handles This

AUANI's direct ordering widget and hosted website, included on the Monthly tier, are built around a straightforward checkout flow, and menu analytics can help identify where guests are dropping off if abandonment is happening at a specific step.

Seeing exactly where in the flow guests tend to leave, rather than guessing at the cause from the final abandonment count alone, makes it far easier to tell whether the real issue is a slow page, a surprise fee, or an unnecessary form field standing in the way.

Frequently Asked Questions

Does requiring an account always hurt conversion?

Not always, but requiring one before checkout, rather than offering it as an option afterward, tends to cost more completed orders than it gains in return visits.

How much does page load speed actually matter?

Meaningfully, since a slow page during a busy ordering window is one of the most common reasons a guest gives up before finishing.

Should delivery fees be shown earlier in the process?

Showing an estimate earlier, rather than only at final checkout, tends to reduce the surprise that leads to abandonment.

Can menu analytics show exactly where guests are dropping off?

It can surface item-level and order pattern data that helps identify likely friction points, though it works best alongside direct testing of the checkout flow itself.

What is the wider guide this fits into?

The Restaurant websites & direct ordering guide covers this alongside hosted websites and the 0% widget.

Why does a surprise fee at checkout hurt more than the same fee shown earlier?

It reads as a bait-and-switch even when legitimate, since the guest already mentally committed to a lower total, and often ends the order rather than just prompting a shrug.

For the wider picture, including why a hosted website matters and how the 0% widget works, see the Restaurant websites & direct ordering guide.

What a 0% Direct Ordering Widget Actually Means Here

by | Dec 1, 2025 | Restaurant Websites & Direct Ordering

On This Page

"0% fee" is the kind of line that invites skepticism, and it should. A vague fee claim usually hides something in the fine print. Here is exactly what AUANI's 0% direct ordering widget covers, and what it doesn't.

What Qualifies for the 0% Marketplace Fee

Any order placed directly through the widget on a vendor's own hosted website, included on the Monthly tier, carries no AUANI marketplace fee. This applies regardless of how the guest arrived at the website, whether from a Google search, a QR code on a receipt, or a repeat visit.

It also applies consistently across order types, pickup, delivery arranged by the vendor, or catering booked through the same widget, since the qualifying factor is simply that the order moved through the vendor's own hosted checkout rather than through AUANI's marketplace listing.

What Still Costs Something Around It

Payment processing, the cost of running the actual credit or debit card transaction, still applies the same way it would on any online order, regardless of platform. That's a processor cost, not an AUANI marketplace fee, and it's separate from the 0% figure.

This distinction matters because a vendor comparing options shouldn't expect payment processing costs to vanish on any platform, including AUANI's own 0% widget. What the 0% figure specifically removes is the marketplace's own cut of the order, not the underlying cost every card transaction inherently carries regardless of provider.

  • 0% refers specifically to AUANI's own marketplace fee on direct orders.
  • Standard payment processing costs still apply, as they would anywhere else.
  • The Monthly tier's $300 flat monthly cost is separate from any per-order fee.

Why This Differs From a Marketplace Order

An order placed through AUANI's own marketplace listing carries the tier's standard marketplace fee, 10% on Free or 5% on Monthly. An order placed directly through the widget on the vendor's own website skips that fee entirely, since the vendor is bringing its own guest rather than AUANI's marketplace bringing one.

That distinction is really the whole logic behind the 0% figure: a marketplace fee exists to cover the cost of the marketplace finding a vendor a guest it wouldn't otherwise have reached. A guest who already knew to visit the vendor's own website didn't need that discovery service, so there's no discovery fee to charge on that order.

A Worked Example

A vendor on the Monthly tier doing $8,000 a month split evenly between marketplace discovery orders and direct widget orders pays a 5% marketplace fee on the $4,000 in marketplace orders, or $200, and nothing in AUANI marketplace fees on the $4,000 in direct widget orders, only standard payment processing on both halves. As that vendor's direct traffic grows relative to marketplace discovery, more of its monthly revenue shifts into the zero-commission side of that split, without ever needing to change tiers or negotiate a new rate.

This is why investing in things that grow direct traffic specifically, a hosted website, local SEO, a guest list capturing repeat orders, compounds in value over time: each guest moved from marketplace discovery to direct ordering permanently shifts a slice of revenue onto the zero-commission side of that split.

That shift tends to accelerate over time too, since a guest who orders directly once, rather than through the marketplace listing, is more likely to keep returning to that same direct channel on future orders rather than reverting back to marketplace discovery.

Tracking that shift directly, watching what share of monthly orders come through the widget versus the marketplace listing, gives a vendor a concrete way to see this compounding effect playing out in its own real numbers.

Frequently Asked Questions

Does the 0% fee apply to phone orders too?

The 0% marketplace fee specifically applies to orders placed through the direct ordering widget; phone orders would need to be entered through that same channel to qualify.

Is there a minimum order size for the 0% fee to apply?

No, the 0% marketplace fee applies to any qualifying direct order regardless of size.

Does payment processing cost more through the widget than through the marketplace?

Processing costs are generally consistent regardless of channel, since they're set by the payment processor, not AUANI.

Is the 0% widget available on the Free tier?

No, the direct ordering widget and its 0% marketplace fee are Monthly tier features.

What is the wider guide this fits into?

The Restaurant websites & direct ordering guide covers this alongside hosted websites and checkout conversion.

Does growing direct traffic reduce the marketplace fee automatically?

It doesn't change the published rate, but it does shift a larger share of total revenue onto the 0% direct channel, lowering the effective blended commission across all orders.

For the wider picture, including why a hosted website matters and reducing checkout abandonment, see the Restaurant websites & direct ordering guide.

Why a Hosted Website Beats a Third-Party Order Page

by | Nov 26, 2025 | Restaurant Websites & Direct Ordering

On This Page

A third-party ordering page, generated automatically by a delivery app or a generic ordering tool, gets a vendor online quickly. It's also a page the vendor doesn't fully control, doesn't build lasting search value for, and could lose entirely if the underlying service changes its terms or the vendor stops paying for it.

What a Generic Ordering Page Can't Do

  • Can't be customized beyond a template, so it rarely matches the vendor's actual brand.
  • Doesn't build the vendor's own search rankings, since the page belongs to the platform, not the business.
  • Disappears if the vendor stops paying for that specific service, taking any accumulated traffic with it.

A template page also typically can't support a vendor's own content, the kind of dish explanations, neighborhood context, or answers to real guest questions that help a page rank for more than just the vendor's exact name, since the platform controls the page's structure and rarely allows that level of customization.

What Owning the Website Actually Buys

A hosted website that the vendor actually owns keeps every improvement made to it, every backlink earned, and every bit of search ranking built over time, none of which transfers away if the vendor ever changes ordering providers.

That accumulation is the real long-term value most vendors underestimate at first. A page's search ranking rarely builds overnight, it grows gradually as content ages, other sites link to it, and a search engine confirms it consistently answers real guest questions, all of which is wasted effort the moment it's built on a page the vendor doesn't actually control.

  1. Content and branding stay fully under the vendor's control.
  2. Search rankings accumulate to a domain the vendor keeps long-term.
  3. The site remains live regardless of which ordering or delivery services the vendor uses.

The Switching Cost Nobody Mentions Up Front

The real cost of a generic third-party ordering page rarely shows up until the vendor decides to leave that service. At that point, whatever search visibility and repeat traffic the page had accumulated simply disappears along with it, and the vendor is starting over at zero on a new platform rather than carrying that history forward. A hosted website avoids this specific risk entirely, since the domain and everything built on it stay with the vendor regardless of which ordering or delivery services come and go over time.

This risk is easy to underestimate precisely because it's invisible for as long as the vendor stays put. It only becomes obvious in hindsight, at the exact moment a vendor most needs its accumulated search visibility to still be there and finds it isn't.

How AUANI Handles This

AUANI's Monthly tier includes a fully hosted website alongside the 0% direct ordering widget, and setup can be handled either way: a vendor can configure it directly, or have AUANI's team build and configure it instead.

This flexibility matters for a vendor without in-house design or technical resources, since owning a website doesn't have to mean taking on the burden of building or maintaining it personally, only that the accumulated value it builds over time stays with the vendor regardless of who does the initial setup work.

That ownership also means a vendor is never locked into a specific ordering setup just to preserve its accumulated search value, since the website and its rankings stay in place regardless of what changes elsewhere in how the vendor takes orders.

A vendor weighing whether to switch any part of its ordering setup can make that decision purely on operational merit, without factoring in a fear of losing accumulated search visibility as a hidden cost of switching.

Frequently Asked Questions

Does a hosted website require ongoing maintenance from the vendor?

AUANI's team can handle setup and ongoing configuration if the vendor prefers not to manage it directly.

Can a vendor migrate an existing website's content over?

Depending on the existing setup, key content like the menu and branding can typically be brought over during setup.

Does a hosted website replace the need for a Google Business Profile?

No, both work together: the website is the destination, and the Google Business Profile is a major way guests find it.

Is the hosted website included on the Free tier?

No, the hosted website and 0% direct ordering widget are Monthly tier features.

What is the wider guide this fits into?

The Restaurant websites & direct ordering guide covers this alongside the 0% widget and checkout conversion.

What happens to a third-party ordering page's traffic if a vendor stops using that service?

It's generally lost entirely, since the page and any search visibility it built belong to the platform, not the vendor, and don't transfer elsewhere.

For the wider picture, including how the 0% widget works and reducing checkout abandonment, see the Restaurant websites & direct ordering guide.