Apply as a Vendor

Restaurant Websites & Direct Ordering: The Full Guide

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

On This Page

A vendor that only takes orders through third-party marketplaces is renting its entire online presence. A hosted website with a direct ordering widget changes that: the vendor owns the page, keeps the guest relationship, and on AUANI's Monthly tier, pays 0% marketplace fee on anything ordered through it. This guide covers what that setup actually includes and what makes it convert once it's live.

Why Owning the Website Matters

A third-party ordering page can't be customized to match a vendor's brand, doesn't build search rankings the vendor keeps long-term, and disappears the moment the vendor stops paying for that specific service.

The full breakdown is in Why a Hosted Website Beats a Third-Party Order Page.

What 0% Marketplace Fee Actually Means

A 0% fee claim deserves a real explanation rather than a headline. Not every order type or scenario is covered the same way, and it's worth knowing exactly what qualifies.

The full breakdown is in What a 0% Direct Ordering Widget Actually Means Here.

Reducing Checkout Abandonment

A hosted website and a 0% widget only pay off if guests actually complete checkout once they land on it. Abandonment usually traces back to a small, fixable set of friction points, not a guest simply changing their mind.

The full breakdown is in What Actually Makes a Guest Abandon Checkout Midway.

Fixing those friction points tends to matter more the closer a guest gets to actually finishing an order, since abandonment at the very last step wastes far more of a guest's effort, and a vendor's opportunity, than a guest simply leaving early before committing to anything.

Where AUANI Fits

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

Plan Price Marketplace Fee What's Included
Free $0/mo, no setup fee 10% Pickup, dine-in, real courier delivery, loyalty, POS sync, exportable guest list, verified-order-only reviews
Monthly $300/mo 5% (3% at 2+ locations) Everything in Free, plus a hosted website, a 0% direct ordering widget, the full Google visibility suite, and menu analytics
+Locations +$100/mo per added location 3% across the whole account at 2+ locations Same feature set as Monthly, extended per location

How These Pieces Actually Fit Together

Owning a hosted website, having a genuine 0% path for direct orders, and keeping checkout friction-free aren't three separate projects, they're one connected system. A vendor could build an excellent hosted website and still lose orders if checkout has unnecessary friction, or fix checkout perfectly on a rented third-party page that provides no lasting search value. Getting real value out of the 0% widget depends on the website that hosts it actually converting the traffic it earns, which is exactly why this category treats all three as one guide rather than three unrelated topics.

What belongs above the fold, whether the site runs a blog, and how the mobile menu behaves on a phone all feed into that same conversion outcome too, since each one either helps or hurts a guest's path from landing on the page to finishing checkout.

Every Guide in This Series

Frequently Asked Questions

Is a hosted website required to use AUANI at all?

No, the Free tier covers pickup, dine-in, real courier delivery, loyalty, and POS sync without a hosted website. The hosted website and 0% widget are Monthly tier features.

Does the 0% widget apply to every order type?

It applies to orders placed directly through the widget on a vendor's own site; the full breakdown covers exactly how that's defined.

Can a vendor keep its existing website and just add the widget?

That depends on the vendor's existing setup; AUANI's team can advise on the best way to integrate depending on what's already in place.

Does a hosted website replace social media for a vendor?

No, it works alongside social media and search, as the destination a vendor actually owns rather than one it's renting from a platform.

What is the cheapest way to start on AUANI?

The Free tier, at $0 a month with a 10% marketplace fee and no setup fee.

Do the hosted website, 0% widget, and checkout conversion need to be handled separately?

No, they work together as one system; a website is only as valuable as the checkout it leads to, and a 0% fee only helps on orders that actually complete.

Start with Why a Hosted Website Beats a Third-Party Order Page, then What a 0% Direct Ordering Widget Actually Means Here, What Actually Makes a Guest Abandon Checkout Midway, What Belongs Above the Fold, Should a Restaurant Website Run a Blog, or Designing a Mobile Menu That Works.

Why Build-Your-Own Pizza Needs More Than One Menu Item

by | Oct 24, 2025 | Restaurant Websites & Direct Ordering

On This Page

A pizza menu listed as a handful of flat items, a large pepperoni, a medium cheese, forces a guest with any real customization in mind into a notes field, typed freeform and easy to misread during a busy rush. A proper build-your-own flow avoids that entirely by structuring size, crust, sauce, and toppings as their own selectable options from the start.

The Problem With a Flat Menu Item

A single "large pizza" listing can't represent every combination of size, crust, sauce, and topping a guest might want, so any customization ends up typed into an open notes field. That field isn't validated, isn't priced automatically, and is the single most common source of kitchen error on a busy night.

  • Typos or unclear notes lead to wrong orders going out.
  • Extra toppings typed in a notes field often don't get priced correctly.
  • No structured way to track which toppings or combinations actually sell.

Staff also lose real time on a busy night calling a guest back to clarify a garbled or ambiguous note, a delay that a structured selection flow removes entirely by making the exact build unambiguous the moment the guest submits it.

What a Structured Build Flow Looks Like

A build-your-own flow breaks a pizza order into a sequence of selectable options, each with its own price modifier, so the final order is fully specified and fully priced before it's ever submitted.

  1. Size selection first, since it usually sets the base price.
  2. Crust and sauce as their own selectable steps.
  3. Toppings selected individually, each with a clear per-topping price.
  4. A final review step showing the complete build and total price before checkout.

This structure also scales cleanly to half-and-half orders, a common pizza-specific request a flat menu item handles even worse than a standard customization, since it requires representing two different topping sets on the same item at once.

The same structure also makes it straightforward to offer size-based topping limits or included toppings, like a certain number of toppings bundled into the base price with additional ones priced separately, a pricing pattern that's nearly impossible to represent cleanly in an open notes field.

What This Solves Beyond Order Accuracy

Beyond reducing kitchen errors, a structured build flow also produces clean, itemized data on which toppings and combinations guests actually choose, data a notes field never produces. AUANI's menu analytics, included on the Monthly tier, can use that structured data to show which builds perform best.

A notes field, by contrast, produces nothing usable in this way at all. Free-text customization requests can't be aggregated or analyzed the way a structured selection can, which means a pizzeria relying on notes has no real way to learn from its own order history over time.

This gap only widens over time too, since a pizzeria running a structured flow accumulates increasingly useful data with every order, while one still relying on a notes field never builds any comparable history no matter how long it operates.

That data also opens the door to targeted combo deals and upsells, since a pizzeria can see exactly which toppings tend to get ordered together and price a bundle around real behavior instead of a guess.

Reviewing that build data every few months also helps a pizzeria retire toppings that rarely get chosen and simplify the build flow accordingly, keeping the selection process quick even as the underlying menu evolves over time.

Frequently Asked Questions

Does a structured build flow slow down checkout?

It typically adds a small number of extra steps, but it removes the ambiguity a notes field creates, which usually nets out faster overall since fewer orders need clarification.

Can toppings be priced individually in this kind of flow?

Yes, each topping, crust, or sauce option can carry its own price modifier that adds automatically to the base price.

Does this replace a fixed specialty pizza menu?

No, a pizzeria can keep fixed specialty pizzas as their own listings alongside a separate build-your-own option.

Does menu analytics track which toppings sell best?

Yes, on the Monthly tier, menu analytics can surface which builds and toppings guests choose most, since the data comes in structured rather than as free text.

Does a build-your-own flow work for other customizable menu items too, not just pizza?

Yes, the same structured approach applies to any item with multiple selectable components, sandwiches, bowls, and salads included, wherever a flat menu listing would otherwise force choices into a notes field.

Can a structured flow handle half-and-half pizza orders?

Yes, representing each half as its own set of topping selections handles this common request more cleanly than a flat menu item or a notes field could.

What is the wider guide for pizzeria vendors?

The pizzeria online ordering guide covers fees, custom order flows, and local search in one place.

For the wider picture on running a pizzeria online, including fee comparisons and local search, see the pizzeria online ordering guide.

How a Caterer Collects Event Details Through a Widget

by | Oct 14, 2025 | Restaurant Websites & Direct Ordering

On This Page

A same-day order, a sandwich picked up at lunch, needs almost nothing beyond an item and a pickup time. A catering order for a fifty-person office lunch or a two-hundred-guest wedding reception needs a great deal more, and collecting that detail after the order comes in, rather than during checkout, usually means a phone call has to happen anyway.

What a Catering Order Actually Needs Up Front

A catering inquiry carries variables a same-day order form was never built to collect: guest count, event date and time, delivery address versus pickup, setup or service requirements, and any dietary restrictions across a group rather than one person.

  • Guest count, since portioning and pricing usually scale directly with it.
  • Event date and time, often set well in advance of the order itself.
  • Delivery, pickup, or on-site setup, each with different logistics attached.
  • Dietary notes across the group, not just a single guest's preference.

Collecting all of this upfront also protects the caterer from a common, costly mistake: quoting or preparing based on an assumption that turns out to be wrong, like assuming a delivery when the client actually needed on-site setup, a mismatch that's far cheaper to catch during checkout than to discover the morning of the event.

Building This Into Checkout Instead of a Follow-Up Call

AUANI's direct ordering widget, included at 0% marketplace fee on the Monthly tier, can be configured with the required fields a catering order needs, so a guest fills them in during checkout rather than a caterer chasing that detail down afterward by phone or email.

  1. Set required fields for guest count, event date, and delivery or setup preference.
  2. Confirm the order only once every required field is filled in.
  3. Follow up directly only for anything genuinely custom, not for information the form already collected.

Deposits and Lead Time

Stating a minimum lead time and, where applicable, a deposit requirement directly on the listing sets expectations before a guest submits a request for a date the caterer can't realistically meet, the same principle that applies to any advance-order food and drink business.

Publishing these terms clearly also reduces the number of inquiries that go nowhere, since a client planning an event with an unrealistically short timeline can see the minimum lead time upfront and adjust their planning immediately, rather than submitting a request the caterer has to decline after the fact.

Handling Requests That Fall Outside the Standard Form

Not every catering inquiry fits neatly into a structured form, a highly customized menu, an unusual venue setup, or a request well outside the caterer's normal offerings still needs a real conversation. The goal of a structured widget isn't to eliminate that conversation entirely, it's to make sure the conversation that does happen starts from a complete picture, guest count, date, and basic logistics already known, rather than beginning from scratch with a guest who has to explain everything from the ground up.

That head start tends to shorten the follow-up conversation considerably, since both sides can focus entirely on the genuinely custom part of the request rather than spending the first several minutes re-establishing basic details the form already captured.

A caterer handling a high volume of inquiries also benefits simply from having fewer of them require a full manual conversation at all, since the structured form alone resolves most straightforward requests without any back-and-forth needed on either side.

Frequently Asked Questions

Does a catering order use a different checkout flow than a same-day order?

It can be configured with its own required fields, guest count, event date, and delivery preference, so it collects what a same-day order form wouldn't.

Does AUANI charge extra for custom order fields?

No, the direct ordering widget's configuration is included on the Monthly tier at no additional fee beyond the standard tier pricing.

Can a caterer require a deposit through the same checkout?

Deposit handling depends on how a caterer structures its own pricing and terms, but a lead-time or minimum-notice requirement can be stated directly on the listing.

Does the 0% marketplace fee apply to catering orders too?

Yes, orders placed through the direct ordering widget on the Monthly tier carry the same 0% marketplace fee regardless of order size.

What is the wider guide for catering companies?

The catering company online ordering guide covers fees, event intake, and local search in one place.

Does a structured intake form eliminate the need to talk to guests directly?

No, it front-loads the basic logistics so any follow-up conversation starts from a complete picture rather than eliminating genuinely custom requests from needing a direct conversation.

For the wider picture on running a catering business online, including fee comparisons and local search, see the catering company online ordering guide.

How a Bakery Takes Custom Cake Orders Through a Widget

by | Oct 2, 2025 | Restaurant Websites & Direct Ordering

On This Page

A same-day pastry sale, a croissant or a slice of cake picked up on the way home, needs almost no back-and-forth. A wedding cake or a custom birthday order is a different transaction entirely, and treating it like a same-day item usually means a phone call or an email chain has to happen anyway, after the online order already came in incomplete.

Why a Simple Add-to-Cart Falls Short Here

A custom cake order carries variables a same-day item doesn't: flavor and filling combinations, size and serving count, design references, allergy notes, and a pickup date that's often weeks out rather than the same afternoon. A generic add-to-cart flow either skips these fields entirely or forces a guest through an awkward checkout that wasn't built for the request.

When these details get skipped at checkout, the bakery ends up collecting them manually afterward anyway, usually over email or a phone call, which adds a delay and a round of back-and-forth that a structured intake form would have avoided from the very first submission.

That delay matters more than it might seem, since a prospective client waiting on a reply is also a prospective client still comparing other bakeries, and every extra day spent chasing missing details is a day the inquiry could quietly go elsewhere instead.

What Flagging a Listing as Catering-Available Does

AUANI's `fo_catering_available` flag lets any vendor, including a bakery, mark that it takes bespoke inquiries separately from its regular menu. That distinction matters because it tells the ordering flow to collect the right kind of detail up front instead of treating a custom cake like a walk-in item.

  • Collects event date, size, and design detail before the order is confirmed.
  • Keeps custom orders visually and functionally separate from same-day menu items.
  • Still runs through the same 0% direct ordering widget on the Monthly tier as any other order.
  • Lets a bakery attach reference photos or design notes to the inquiry itself, rather than relying on a separate email thread.

Setting Expectations on Lead Time

A common failure point for custom orders taken online is a guest submitting a request for a date the bakery can't realistically meet. Being explicit about minimum lead time directly in the listing, rather than only in a follow-up email, cuts down on that back-and-forth before it starts.

  1. State a minimum lead time directly on the custom order listing.
  2. Require a pickup or delivery date field before the order can be submitted.
  3. Confirm design and flavor detail in writing before the order is finalized.

Pricing a Custom Order Fairly

Unlike a same-day pastry with a fixed price, a custom cake's cost depends on size, design complexity, and ingredients, which makes a flat listed price impractical. A clearer approach is publishing a starting price with a note that final cost depends on the specifics gathered during intake, giving a prospective guest a realistic anchor without forcing an exact quote before any details are known.

This starting-price approach also filters inquiries somewhat, since a guest with a budget well below the stated starting point can self-select out early, rather than the bakery discovering a mismatch only after collecting full design details and preparing a formal quote.

Publishing a small number of representative examples alongside the starting price, a simple design at the base tier and a more elaborate one further up, also helps a guest calibrate their own expectations before ever submitting an inquiry.

Frequently Asked Questions

Does a custom cake order use a different checkout than the regular menu?

It can be set up as a separate listing with its own required fields, so it collects event date, size, and design detail that a regular menu item wouldn't ask for.

Does AUANI charge extra to mark a listing as catering-available?

No, `fo_catering_available` is a toggle any vendor can use, and it doesn't carry a separate fee.

Can a bakery still sell same-day items alongside custom orders?

Yes, both can run on the same account, with custom orders flagged separately so they collect the right information.

Does a custom order still run through the 0% direct widget?

Yes, on the Monthly tier, custom orders taken through AUANI's direct ordering widget carry the same 0% marketplace fee as any other direct order.

How should a bakery price a custom cake listing online?

A starting price with a note that final cost depends on size and design specifics tends to work better than either a flat price or no price guidance at all.

What is the wider guide for bakery vendors?

The bakery online ordering guide covers fees, custom orders, and local search in one place.

For the wider picture on running a bakery online, including fee comparisons and local search, see the bakery online ordering guide.