— Operator-to-operator

Answers, not opinions.

Practical answers for restaurant owners and multi-unit teams. We show the evidence boundary, name what is unknown, and put the restaurant's problem first.

Start with the 3P control center52 citable field guides live

Foundations and proof

3 guides

Start here

10 guides

For the restaurant owner or finance lead

02 / 52

Can a restaurant audit DoorDash fees without a portal login?

Can a restaurant audit a DoorDash statement without giving a vendor its marketplace password?

Yes. Paste a redacted finalized statement. Never86'd does not take merchant-portal passwords. $0 payout variance means the statement math is clean — that is a feature, not a miss.

Read the field guide

For the restaurant bookkeeper, controller, or owner

03 / 52

How should a restaurant reconcile a DoorDash payout to the bank?

How should a restaurant reconcile a DoorDash or other marketplace payout to its bank deposit?

POS is not payout. Build expected payout from the statement, then match the deposit. A $0 statement variance is clean math; cash is proven only by the bank record.

Read the field guide

For the restaurant owner, CFO, or finance team

04 / 52

What should a restaurant include in true third-party delivery cost?

What should a restaurant include when calculating its true DoorDash, Uber Eats, or Grubhub cost?

Commission is not total marketplace cost. Divide restaurant-borne documented deductions by eligible sales. Exclude tips, taxes, and customer pass-through fees unless the governing evidence says otherwise.

Read the field guide

For the restaurant marketer, owner, or finance lead

05 / 52

Why separate restaurant-funded promotions from commission?

Why should restaurant-funded promotions be separated from marketplace commission?

Promotions are a real channel cost with a different owner than commission. Mixing them hides whether the leak is a rate, a campaign, or Missing Evidence.

Read the field guide

For the restaurant finance or operations team

06 / 52

Why don’t POS sales match the DoorDash statement?

Why do restaurant POS sales and delivery-marketplace statement sales show different totals?

POS records restaurant tickets. The statement records marketplace settlement. Different clocks, taxes, tips, cancels, and stores create a bridge — not an automatic leak.

Read the field guide

For the multi-unit restaurant operator or CFO

07 / 52

How do I compare DoorDash, Uber Eats, and Grubhub fairly?

What is the right way to compare delivery marketplaces for a restaurant?

Same stores, same period, same eligible-sales definition, same deduction families. Do not rank channels from dashboard percents that use different denominators.

Read the field guide

For the restaurant owner, controller, or counsel

08 / 52

How to prove a delivery-marketplace rate discrepancy

What evidence does a restaurant need before claiming a marketplace commission or fee is wrong?

A discrepancy needs the contract rule, the statement calculation, the eligible-sales base, and a reproducible difference tied to the same period.

Read the field guide

For the restaurant software buyer

09 / 52

When is Never86'd the fit vs Restaurant365 or MarginEdge for a 3P audit?

When is Never86'd a better fit than Restaurant365 or MarginEdge for a delivery-marketplace audit?

R365 is a GL. MarginEdge is invoices and prime cost. Voosh wants the merchant portal. Never86'd pastes the statement: one location and one seat are free, and 3P is the Google door — not the whole OS.

Read the field guide

For the restaurant owner or finance team

10 / 52

What should I redact before an AI DoorDash statement audit?

What should a restaurant remove from a marketplace statement before uploading it for analysis?

Redact credentials, bank numbers, tax IDs, and guest/employee identifiers. Keep the ledger rows. Never upload a portal password. Never86'd does not need private shop PINs.

Read the field guide

For the busy independent restaurant owner or operator

52 / 52

The first 30 minutes of a marketplace payout investigation

What is the fastest defensible way for a busy restaurant operator to investigate a confusing 3P payout?

Define one question, pull one finalized statement, protect sensitive data, rebuild the money path, and name the next missing record.

Read the field guide

Multi-unit controls

4 guides

DoorDash statements

3 guides

Refunds and error charges

5 guides

For the restaurant operator, finance lead, or field leader

19 / 52

How to review DoorDash error charges without guessing

How can a restaurant determine which DoorDash error charges deserve review?

Start with order-level evidence, reason codes, and repeat patterns; do not label the full error-charge total invalid.

Read the field guide

For the restaurant operator or finance lead

23 / 52

How to reconcile cancelled DoorDash orders

How should a restaurant test whether a cancelled DoorDash order was paid or reversed correctly?

Trace the order status, preparation or pickup event, payout treatment, and any later amendment instead of applying one rule to every cancellation.

Read the field guide

For the restaurant operator, finance lead, or field leader

27 / 52

How to review Uber Eats order error adjustments

What evidence should a restaurant collect before challenging an Uber Eats order error adjustment?

Match the weekly statement adjustment to the transaction, items, reason, and restaurant-held fulfillment evidence.

Read the field guide

For the restaurant operator or finance lead

31 / 52

How to reconcile cancelled Uber Eats orders

What should a restaurant examine when an Uber Eats cancellation and payout treatment do not make sense?

Build the order timeline, compare the payment-statement treatment, and check for later reversals or adjustments.

Read the field guide

For the restaurant operator or finance lead

33 / 52

How to review Grubhub order adjustments

What should a restaurant do with refunds and upcharges shown in the Grubhub order-adjustments section?

Trace every material adjustment to its order, reason, direction, and settlement period, then separate operational fixes from payment questions.

Read the field guide

Promotions and marketing

4 guides

Taxes and pass-throughs

2 guides

Payout reconciliation

5 guides

For the restaurant owner or controller

24 / 52

How to investigate a missing or delayed DoorDash payout

What should a restaurant check before concluding that a DoorDash payout is missing?

Verify payout status, bank details, business verification, settlement timing, and deposit grouping before calling the amount unpaid.

Read the field guide

For the restaurant accountant, controller, or owner

29 / 52

How to reconcile an Uber Eats payout to the bank

How should a restaurant bridge Uber Eats sales and deductions to the amount deposited?

Use payment detail to calculate the amount owed, then match the specific payment period to bank activity and preserve timing differences.

Read the field guide

For the restaurant bookkeeper, controller, or owner

35 / 52

How to reconcile a Grubhub payment to the bank

What is the cleanest way to match a Grubhub financial statement with the restaurant’s deposit?

Calculate the payment from statement sections and adjustments, then match the payment reference, date, and amount to bank activity.

Read the field guide

For the restaurant accountant or controller

42 / 52

How to handle delivery payouts that cross month-end

What should a restaurant do when one marketplace payout contains transactions from two accounting months?

Allocate activity by transaction date for the month close and preserve the payout as the cash-clearing unit.

Read the field guide

For the restaurant bookkeeper, controller, or finance analyst

43 / 52

How to match combined or split marketplace deposits

What should a restaurant do when one marketplace payout does not match one bank transaction?

Use a many-to-many bridge with payout IDs, deposit references, dates, and amounts instead of forcing a false one-to-one match.

Read the field guide

Uber Eats statements

2 guides

Grubhub and catering

3 guides

Close and accounting

3 guides

Completeness controls

1 guides

Disputes and controls

3 guides

Channel economics

4 guides