Apply as a Vendor

Handling Large Party Orders Without Breaking the Kitchen

by | Jun 16, 2026 | Restaurant Software & Comparisons

On This Page

An online order for twenty meals looks the same on a screen as an order for one, until it hits the kitchen all at once with the same expected turnaround time as any other ticket. A large party order that isn't flagged or scheduled differently can quietly derail an entire service, turning what should be a vendor's best ticket of the night into the reason every other guest's food comes out late.

Why Large Orders Cause Problems

A kitchen paced for individual or small-party tickets doesn't have slack built in for a twenty-item order arriving with the same expected timing as a two-item one, which can back up every other order behind it. The line cook working the fryer or the grill has a fixed rate of output regardless of how the order arrived, and a single large ticket dropped into a normal queue effectively pauses everyone else's food until it clears.

  • A large order treated like a normal ticket can delay every other guest's order behind it.
  • Without advance notice, a kitchen has no chance to prep ingredients ahead of time, meaning a twenty-item order competes for the same raw inventory as walk-in guests.
  • A guest expecting normal turnaround on a large order is set up for disappointment either way, whether the kitchen rushes and gets the order wrong or takes the time and runs late.
  • Staff scheduled for a normal volume night have no warning that one ticket will consume a disproportionate share of their capacity.

A Practical Approach

Setting a threshold, an order above a certain item count or dollar value, that requires advance scheduling rather than immediate fulfillment gives a kitchen the lead time it needs without turning away the business. A reasonable starting point is a threshold around 10 to 15 individual entrees, or a subtotal in the range of $150 to $200, though the right number depends heavily on a specific kitchen's staffing and equipment.

Once a threshold is set, the online menu itself should reflect it. An order that crosses the line can be routed to a scheduling flow requiring a pickup or delivery time at least a few hours out, rather than the immediate fulfillment path a normal order takes. This keeps the online system from silently accepting a commitment the kitchen has no realistic way to honor.

Communicating the Policy to Guests

A guest placing a large order rarely thinks about kitchen capacity, they're thinking about feeding a group on time. A brief, clear note at checkout, something like a stated minimum lead time for orders above a certain size, sets the right expectation before the order is placed rather than after a guest is already frustrated by a delay nobody warned them about.

How AUANI Handles This

AUANI's ordering system lets a vendor configure scheduled ordering ahead of a specific pickup or delivery time, giving a kitchen the lead time a large order actually needs instead of treating every order as immediate. A vendor can require advance scheduling above a set order size, so a large ticket never lands in the kitchen without warning.

Because AUANI syncs with a vendor's existing POS rather than replacing it, a scheduled large order still flows into the same kitchen display and ticket system staff already use, so there's no separate manual process required to honor a large advance order alongside normal walk-in and pickup volume.

Frequently Asked Questions

How large does an order need to be before it needs advance notice?

There's no universal number, but a threshold based on either item count or dollar value, set by the vendor and matched to real kitchen capacity, works better than treating every order the same. A common starting range is 10 to 15 entrees or roughly $150 to $200, adjusted up or down based on how a specific kitchen actually performs under load.

Should a large order cost more than the sum of its items?

Not necessarily more per item, though some vendors add a lead-time requirement or a minimum notice period rather than a price premium. A price increase can feel punitive to a guest, while a clear scheduling requirement reads as a practical operational need instead.

Can a guest still place a large order for immediate pickup?

That depends on how a vendor configures its own threshold; some allow it with a longer quoted wait, others require advance scheduling above a certain size with no immediate option at all. Either approach is reasonable as long as the guest sees the requirement before completing checkout.

Does AUANI support scheduled ordering for large parties?

Yes, orders can be scheduled ahead of a specific pickup or delivery time rather than only supporting immediate fulfillment, and a vendor can require that scheduling automatically once an order crosses a chosen size threshold.

What is the wider guide this fits into?

The Restaurant & Bar online ordering guide covers this alongside happy hour menus and late-night visibility.

For the wider picture on running a restaurant or bar online, see the Restaurant & Bar online ordering guide.

Why a New Vendor’s First Order Mistake Matters Most

by | Jun 9, 2026 | Restaurant Software & Comparisons

On This Page

Every new vendor eventually gets an order wrong: a missing item, a wrong modification, a late delivery. For an established business with years of reviews behind it, one mistake barely registers. For a brand-new vendor with only a handful of reviews so far, that same mistake can carry disproportionate weight.

Why the First Mistake Hits Harder Early On

A single negative review against a base of only five or ten total reviews moves the average rating far more than the same review would against a base of two hundred, and a new vendor has no accumulated trust yet to absorb the impact.

A searcher browsing a brand-new listing also has almost nothing else to judge it by yet. With no long track record to weigh a single bad experience against, that one review can end up carrying outsized influence over a stranger's very first impression of the business.

The Manual, Free Way to Handle It

Without any specific tools, a vendor can respond directly and promptly to the guest, acknowledge the specific mistake rather than a generic apology, and offer a concrete resolution, all of which costs nothing beyond the time to do it well.

This kind of response works because it demonstrates something a searcher genuinely wants to know before ordering anywhere new: not whether the vendor is perfect, since no vendor is, but whether the vendor actually makes things right when something does go wrong.

A vendor that handles its very first public mistake well often ends up more trusted, not less, than one whose profile shows no mistakes at all, simply because the response demonstrates real accountability rather than an untested, unproven track record.

How Marketplace Platforms Approach This

On a pure marketplace platform, a vendor often has limited visibility into which guest placed which order once a dispute arises, since the marketplace typically owns the guest relationship rather than the vendor.

The AUANI Solution

AUANI's verified-order-only review system ties every review directly to a real completed order, so a vendor always knows exactly which order a review refers to and can respond with specific, accurate context rather than guessing. The exportable guest list also means a vendor can follow up directly with an affected guest rather than relying solely on a public review response.

Knowing exactly which order a review is describing also removes the guesswork of trying to piece together what actually happened from a vague complaint, letting a response address the specific issue directly rather than answering in generalities.

Getting Started

A new vendor can start on AUANI's Free tier, at $0 a month, with the verified-order review system and guest list already included, so a plan for handling that inevitable first mistake is in place before it happens.

Turning the Mistake Into a Second Chance

A guest whose first order went wrong and who receives a genuine, specific response, followed by a real opportunity to try again, sometimes becomes a more loyal guest than one whose first order was simply fine. The mistake itself isn't what determines the outcome nearly as much as how directly and sincerely it gets addressed. A vendor that treats an early mistake as a chance to demonstrate real care, rather than something to minimize or ignore, often converts that guest into someone genuinely willing to give the business a second try.

None of this is a reason to welcome mistakes, but it does mean a new vendor shouldn't panic the first time one happens. Handled with genuine care, that first stumble can end up building more trust than it costs.

Frequently Asked Questions

Is one negative review early on really that damaging?

It can move the average rating more noticeably than it would later, simply because the total review base is still small, though a genuine, specific response helps limit the impact.

Should a vendor respond publicly or reach out privately?

Both together tend to work best: a public response shows other guests the issue was taken seriously, while a private follow-up resolves it directly.

Does AUANI help identify which order a review refers to?

Yes, since every review is tied to a verified completed order, a vendor always has the specific order context available.

How fast should a vendor respond to a negative review?

As promptly as practical; a same-day or next-day response tends to read as more genuine than a delayed one.

What is the wider guide this fits into?

The First $6K Fast Track guide covers this alongside delivery radius and pricing a menu for the first time.

Can a mistake actually make a guest more loyal in the long run?

It can, if handled with a genuine, specific response and a real opportunity to try again, sometimes more so than a guest whose first order simply went fine.

For the full path from launch to $6,000 a month, see the First $6K Fast Track guide.

Pricing a Menu for the First Time Without Guessing

by | Jun 4, 2026 | Restaurant Software & Comparisons

On This Page

A brand-new vendor pricing a menu for the first time has no sales history, no repeat guests, and no data showing what a price actually does to order volume. Every number on the menu is, in a real sense, a guess. That doesn't mean the guess has to be uninformed.

Why Pricing Feels Like Guesswork Early On

Price too high with no reputation yet to justify it, and a new vendor risks scaring off exactly the guests it needs to build early reviews and repeat orders. Price too low, and thin margins from food cost and marketplace commission can turn even a busy first month into a loss.

An established vendor facing the same pricing question at least has months or years of order history to check any adjustment against. A brand-new vendor is setting every single price for the first time simultaneously, with no internal baseline of its own to compare a change against, which is exactly what makes the very first pricing pass feel so much more consequential than a routine adjustment made later on.

The Manual, Free Way to Approach It

Without any specialized tools, a new vendor can calculate a baseline price per item using actual food cost plus a target food cost percentage, typically somewhere around 28% to 35% of the menu price depending on the category, then check that number against a handful of nearby competitors offering a similar item.

This baseline calculation is really two separate checks working together: the food-cost math confirms a price is financially sound on its own terms, while the competitor comparison confirms it's still realistic for what guests in the area actually expect to pay. A price that passes only one of those checks is worth reconsidering before it ever reaches the menu.

Marketplace commission is worth folding into that same food-cost math from the start rather than treating it as a separate line item later, since a price that looks profitable before commission can turn thin or negative once the actual per-order fee comes out of it.

How Managed Platforms Approach This

Some managed setup services include a pricing consultation as part of their onboarding call, walking a new vendor through the same food-cost math, though that guidance typically comes bundled with a higher monthly software cost or a setup fee.

The AUANI Solution

AUANI's menu analytics, included on the Monthly tier, show which items are actually selling and at what price point once real orders start coming in, letting a vendor adjust pricing based on real data within the first few weeks rather than waiting months to notice a pattern. A vendor uncertain about pricing from day one can also have AUANI's team assist with initial menu setup.

Getting Started

A new vendor can start on AUANI's Free tier, at $0 a month, set initial prices using the food-cost baseline method, and move to the Monthly tier once ready to use menu analytics to refine pricing with real order data.

A Worked Example

A sandwich with $4.50 in raw ingredient cost, priced at a 32% target food cost, works out to roughly $14, calculated by dividing the ingredient cost by the target percentage. Checking that $14 figure against three or four nearby vendors selling a comparable sandwich confirms whether it lands in a realistic range for the area, high enough to cover cost and margin, but not so far outside local norms that it looks obviously overpriced to a first-time guest with no reason yet to trust the higher number.

Running that same two-part check across every item on the menu, rather than just the one or two flagship dishes, takes longer up front but catches the smaller items that are easy to underprice simply because they seem too minor to calculate carefully.

Frequently Asked Questions

What food cost percentage should a new vendor target?

Roughly 28% to 35% of the menu price is a common baseline, though it varies by category and item type.

Should a new vendor match competitor prices exactly?

Not necessarily exactly, but checking a few nearby competitors offering a similar item gives a useful reference point alongside the food-cost calculation.

Can menu prices be changed easily once orders start coming in?

Yes, prices can be adjusted directly at any time as real order data shows what's working.

Does AUANI help with initial menu pricing setup?

AUANI's team can assist with initial menu setup for a vendor uncertain about where to start, and menu analytics on the Monthly tier show real performance once orders begin.

What is the wider guide this fits into?

The First $6K Fast Track guide covers this alongside delivery radius and handling early order mistakes.

For the full path from launch to $6,000 a month, see the First $6K Fast Track guide.

Why a Narrow Delivery Radius Makes Sense at the Start

by | Jun 1, 2026 | Restaurant Software & Comparisons

On This Page

A brand-new vendor setting up online ordering for the first time has to pick a delivery radius with no order history to base it on. The instinct is usually to cast as wide a net as possible, on the theory that more coverage means more possible orders. In practice, a radius set too wide up front tends to create more problems than it solves.

Why This Decision Feels Harder Than It Should

A radius set too wide means longer delivery times, colder food by the time it arrives, and a driver tied up on one delivery for far longer than a nearby order would take, all of which shows up as bad reviews before a vendor even has enough of a track record to absorb them.

A brand-new listing with only a handful of reviews is especially vulnerable to this timing, since one or two early complaints about cold food from an overly long delivery can dominate the entire review section for months, in a way a single bad review would barely register against an already-established listing with a hundred reviews behind it.

The Manual, Free Way to Approach It

Without any tools at all, a new vendor can estimate a reasonable radius by timing a few test drives to the edges of a candidate delivery zone and checking whether food quality holds up over that drive time, then adjusting the boundary based on what actually held up.

Repeating that same test drive at a different time of day is worth doing too, since traffic and travel time can vary enough between a quiet mid-afternoon and a busy evening rush to change what actually counts as a reasonable boundary.

How Larger Platforms Approach This

Marketplace-model delivery platforms often default a new vendor's radius as wide as their own delivery network allows, since a wider radius means more possible orders and more commission for the platform, regardless of whether that radius actually serves the vendor's own food quality or driver capacity well.

This isn't necessarily a bad-faith design choice, a platform genuinely does earn more from a wider radius generating more orders. It just means the platform's incentive and the new vendor's actual interest, arriving fresh and building a strong early reputation, don't automatically point in the same direction by default.

Recognizing that gap early makes it easier for a new vendor to treat a platform's default radius as a suggestion rather than the correct answer, and to adjust it toward what the kitchen and drivers can genuinely support instead.

The AUANI Solution

AUANI lets a vendor set and adjust its own delivery radius directly, rather than defaulting to whatever maximizes order volume for the platform. A new vendor can start narrow, confirm food quality holds up and drivers can turn deliveries around quickly, then expand the radius deliberately as volume and confidence grow.

Getting Started

A new vendor can apply for AUANI's Free tier, at $0 a month with no setup fee, set an initial delivery radius directly in the dashboard, and expand it once the first few weeks of real orders confirm what the kitchen and drivers can actually handle.

A Simple Way to Decide When to Expand

Rather than expanding on a hunch, a vendor can watch for a specific signal: a stretch of weeks where delivery orders inside the current radius consistently arrive within the promised window and reviews mentioning food temperature or timing stay positive. That's a more reliable trigger to widen the boundary by a modest amount than picking an arbitrary date on the calendar to "try going bigger." Expanding in small increments, then repeating the same check, keeps the radius growing in step with what the kitchen can actually support rather than outrunning it.

Pulling the radius back in is also a legitimate option if an expansion doesn't hold up, rather than something to avoid out of a sense that the boundary can only ever move outward once it's been widened once.

Frequently Asked Questions

How wide should a brand-new vendor's delivery radius be?

There's no universal number, but starting narrower than feels natural and expanding based on real performance tends to work better than guessing wide from day one.

Does a narrow radius mean fewer total orders?

In the short term, possibly, but a narrow radius that arrives fresh and on time tends to build the review base needed to expand confidently later.

Can the delivery radius be changed later on AUANI?

Yes, a vendor can adjust the radius directly at any time as order volume and driver capacity change.

Do marketplace platforms let a vendor set its own radius?

Some do, though defaults are often set wide to maximize the platform's own order volume rather than the vendor's specific needs.

What is the wider guide this fits into?

The First $6K Fast Track guide covers this alongside pricing a menu and handling early order mistakes.

For the full path from launch to $6,000 a month, see the First $6K Fast Track guide.

Reading Your First Month of Orders Without the Overwhelm

by | Apr 10, 2026 | Restaurant Software & Comparisons

On This Page

A brand-new vendor's first month of order data feels like a strange in-between: too thin to draw big conclusions from, but still full of small signals worth noticing before a full season of data builds up. Knowing what to actually look at avoids both over-interpreting a slow week and ignoring a real early pattern.

The Manual, Free Approach

  • Which items got ordered more than once by the same guest, even in a small sample.
  • Which times of day or days of the week saw the most orders.
  • Whether any single guest already ordered more than once in the first month.

None of this requires special software in month one, a simple manual tally from order history is enough to start noticing early patterns.

A basic spreadsheet with a row per order, noting the guest, the item, and the date, takes only a few minutes to set up and is usually enough structure to spot the earliest repeat patterns without needing anything more sophisticated in these first few weeks.

How Other Platforms Approach This

Several platforms gate any kind of analytics behind a higher-priced tier from day one, leaving a brand-new vendor with raw order notifications and nothing structured to learn from until it upgrades.

That gap forces a genuinely new vendor to either pay for a higher tier before it has any real volume to justify the cost, or go without any structured way to review its own early order history at all, neither of which is a reasonable position to put a brand-new business in.

How AUANI Solves This

AUANI's exportable guest list, included on the Free tier, already captures which guests are ordering and when, giving a brand-new vendor real data to review manually. Menu analytics, included on the Monthly tier, adds structured item-level detail once volume grows enough to make that worthwhile.

Getting Started

Reviewing the exportable guest list at the end of the first month, even manually, is enough to start spotting which early guests and items are showing repeat behavior.

Setting a fixed date each month for this review, rather than doing it whenever there happens to be a free moment, makes it far more likely the habit actually continues into month two and beyond, once the initial novelty of a brand-new business has worn off.

Avoiding Common First-Month Mistakes

  • Treating a single slow week as proof the location or menu isn't working, when a full month or two of data would show a clearer picture.
  • Discontinuing an item after only a handful of orders, before there's been enough exposure to judge its real popularity.
  • Ignoring which specific guests have already ordered more than once, the single clearest early repeat signal available.
  • Comparing month one directly against an established competitor's numbers, rather than against the vendor's own following months.

Each of these mistakes shares a common root: judging a brand-new operation against a standard that only makes sense for an established one. Month one is genuinely a different phase, and the fairest comparison is always the vendor's own data a month or two later, not someone else's.

Revisiting this same list again at the end of month two, checking whether any of these mistakes crept in during the first busy weeks, helps confirm the early data is being read fairly rather than judged against an unrealistic standard.

By month three, most of these early-reading mistakes tend to resolve on their own simply because there's finally enough real order history to see past the noise of any single slow or unusually busy week.

Frequently Asked Questions

Is one month of data really enough to learn anything?

It's enough to notice early signals, not enough for firm conclusions; the goal in month one is noticing patterns worth watching, not making final decisions.

Does a brand-new vendor need menu analytics from day one?

Not necessarily; the Free tier's guest list already supports basic manual review before menu analytics becomes worth the Monthly tier's cost.

What's the most useful thing to track in month one?

Whether any guest has already ordered more than once, since that's the earliest sign of real repeat behavior forming.

Does AUANI require special software to see this data in month one?

No, the exportable guest list is included on the Free tier and can be reviewed manually right away.

What is the wider guide this fits into?

The First $6K Fast Track guide covers this alongside pickup sequencing and choosing a tier.

Should a new vendor drop a menu item after a slow first month?

Not usually based on a single month alone, since a small sample can easily misrepresent an item's real popularity once demand has more time to show itself.

For the full series, start with the First $6K Fast Track guide.

Photographing a Menu on a Phone When Just Starting

by | Apr 7, 2026 | Restaurant Software & Comparisons

On This Page

A menu with no photos, or with mismatched stock images, is a common brand-new vendor problem, since a professional photographer is a real expense that doesn't always fit a first-month budget. A phone can produce genuinely usable photos with a few consistent habits, no professional equipment required.

The Manual, Free Approach

  1. Shoot near a window in natural light rather than under artificial kitchen lighting.
  2. Keep the background simple and consistent across every photo.
  3. Photograph the dish as it's actually served, not a specially arranged version.
  4. Take several angles of each dish and keep the clearest, most appetizing one.

Cleaning the phone's own camera lens before shooting is an easy step to overlook but makes a real difference, since a smudge from a pocket or bag can quietly soften every photo taken that day without it being obvious until the images are already uploaded and compared side by side.

Common Phone Photo Mistakes to Avoid

  • Shooting straight down at a harsh angle that flattens the dish instead of showing its height and texture.
  • Using flash indoors, which tends to wash out color and create a flat, artificial look compared to natural light.
  • Cropping so tightly that a guest can't tell the actual portion size being served.
  • Mixing warm and cool lighting across different photos, which makes the whole menu look inconsistent when guests scroll through it.

Any single one of these mistakes is fixable in the moment, before a photo ever gets uploaded, simply by reviewing the shot on the phone's own screen rather than snapping once and moving straight to the next dish. A quick second look catches most of them before they become part of the live menu.

How Other Platforms Approach This

Several platforms sell professional photography as a paid add-on service, which can produce excellent results but adds real cost right at the point a brand-new vendor is trying to control expenses. Package pricing for a professional shoot commonly runs into several hundred dollars for a single session covering a full menu, a cost that's easier to justify once a vendor already has revenue coming in than during the first weeks of operating.

How AUANI Solves This

AUANI's menu display works the same way regardless of whether photos come from a phone or a professional shoot, so a vendor isn't penalized for starting with honest, well-lit phone photos rather than paying for a shoot before there's revenue to support it.

This matters because a menu system that visually favors professional photography would put a brand-new vendor at a disadvantage right from launch, exactly when it can least afford that kind of extra cost before any real revenue is coming in.

A vendor that later does invest in professional photography can simply swap the images in place without needing to rebuild the menu structure around them, since the underlying listing works the same either way.

Getting Started

A vendor can upload phone photos to its AUANI menu immediately, and revisit professional photography later once the business has grown into that expense. A reasonable approach is photographing the five or so best-selling or highest-margin items first, publishing those, and filling in the rest of the menu over the following week rather than waiting until every item has a photo before launching at all.

An item with no photo at all still tends to underperform one with even a modest phone photo, so filling in the remaining gaps within the first couple of weeks, rather than leaving several items permanently photo-less, is worth the modest additional effort.

Retaking a photo later, once revenue allows for better equipment or a professional shoot, is always an option too, so starting with phone photos never locks a vendor into a lower standard permanently, it simply gets the menu live sooner.

Frequently Asked Questions

Does photo quality really affect ranking or orders?

Real, clear photos help both guest decision-making and profile completeness signals; the equipment used to take them matters far less than clarity and honesty.

Should every menu item have a photo?

Ideally yes, though prioritizing the most popular or highest-margin items first is reasonable if time is limited.

Can phone photos be swapped for professional ones later?

Yes, menu photos can be updated at any time as a vendor's budget and priorities change.

Does natural light really make a noticeable difference?

Yes, natural light tends to produce far more appetizing, accurate color than typical kitchen artificial lighting.

What is the wider guide this fits into?

The First $6K Fast Track guide covers this alongside first repeat orders and Google visibility.

Is it worth using a tripod for menu photos?

A small, inexpensive phone tripod helps keep angles and framing consistent across every photo, which matters more for a cohesive-looking menu than any single photo's individual quality.

For the next step, see the First $6K Fast Track guide.