ILLINOIS FOCUS. A NATIONWIDE ADVISORY TEAM.Jason Taken · HedgeStone Business Advisors

BUYING A RESTAURANT / THE RESTAURANT DEAL FIELD GUIDE

Who owns restaurant delivery-platform accounts after a sale?

The purchase agreement alone does not establish that a delivery-platform account, reviews, terms, or payout setup transfers unchanged. Review each platform’s current process and actual merchant contract, confirm the authorized ownership-change or new-account path, and document settlement cutoffs and access. Test the approved configuration before relying on uninterrupted orders or historical channel earnings.

KEY TAKEAWAYS

  • Restaurant assets, platform contracts, account access, and customer information are different rights.
  • Obtain platform-specific confirmation rather than use the seller’s password as a transfer.
  • Reconcile gross orders, commissions, adjustments, and payouts across the closing cutoff.
  • Reviews, rankings, terms, and customer data should never be promised without support.

What is actually included in the restaurant’s digital package?

List every delivery marketplace, direct-ordering service, point-of-sale integration, ordering website, telephone ordering tool, payment account, and related device. Identify the contracting entity, store identifier, authorized administrator, billing details, tax identity, and bank destination for each.

Do not treat the whole package as a single transferable asset called online ordering. A restaurant may own menu photographs while licensing software, use a platform listing subject to provider terms, and receive payments through another merchant service. Each relationship can require separate action.

The buyer hub can organize diligence. Add a digital-rights schedule to the transaction package so historical channel revenue is connected to the actual contracts, permissions, and systems needed to continue generating it.

Why does platform approval matter beyond the purchase agreement?

Buyer and seller can agree between themselves to convey specified assets and cooperate with transition. That agreement does not automatically bind a platform to preserve an account, approve new ownership, maintain pricing, or continue particular features. Review the actual terms and ask the provider about the proposed change.

DoorDash’s merchant-protection announcement describes verification intended to prevent unauthorized ownership changes and account takeovers. It illustrates why a legitimate transaction should follow the provider’s process rather than bypass controls with shared credentials.

The DoorDash merchant FAQ explains aspects of onboarding and merchant information. Current provider instructions and the actual store configuration still need confirmation. Do not assume one platform’s requirements apply to every delivery marketplace or every transaction form.

Which questions should the buyer ask each provider?

Describe the actual entity, ownership, location, brand, and concept changes. Ask whether the existing agreement can continue, whether a new contract or account is needed, who initiates the process, what documents are required, and how the completion is confirmed.

Request clarification about menus, photographs, reviews, listing history, promotions, commission plans, devices, integrations, tax reporting, and settlement timing. Record the support reference, representative, date, and scope of any written response. A generic help article is useful context but not a guarantee for the specific store.

Set deadlines based on provider guidance and transaction dependencies. Avoid a universal promise that an ownership change will complete in a fixed number of days. Missing records, inaccessible administrators, multiple locations, or different account structures can create additional work.

How should the digital handover be organized?

Delivery-platform transition responsibilities
ItemEvidence or actionRisk to resolve
Merchant contractCurrent terms and provider confirmationAssumed assignment or pricing continuity
AdministratorAuthorized identities and approved accessShared passwords or inaccessible seller account
Bank and tax profileProvider-approved verified updatesFunds or reporting directed to the wrong party
Menus and contentRights, pricing, modifiers, and availabilityIncorrect orders or unlicensed content
Listing historyWritten explanation of what may continueUnsupported review or ranking promises
IntegrationTested ordering and reporting connectionLost orders or duplicate revenue entries
Settlement cutoffOrder-to-bank reconciliation and agreementDisputed payouts, refunds, and chargebacks

Name a responsible person for each row. The seller’s cooperation may be essential, but the buyer also needs its own authorized information and a clear method to verify completion.

What does a settlement example reveal?

Assume a hypothetical platform statement shows $18,400 gross orders for a defined period, $4,048 commissions, $680 promotions charged to the merchant, $225 refunds, and $140 other charges. Net settlement would be $13,307 under these simplified assumptions.

If $5,100 of the gross orders were fulfilled before the agreed closing cutoff but settled afterward, the parties cannot allocate the entire $13,307 by deposit date alone. They need the order-level detail, associated fees and adjustments, and the actual contract’s cutoff method.

These invented figures are not platform rates or accounting instructions. Have the CPA determine consistent presentation and reconcile tax, tips, refunds, and other amounts correctly. The POS-sales verification definition helps explain why gross orders, revenue, and cash received are related but different numbers.

How can platform economics change restaurant valuation?

Analyze channel contribution after the actual commissions, packaging, labor, promotions, refunds, and software expense. Determine whether the seller’s reports present gross or net amounts and whether fees are consistently classified. Avoid adding gross platform sales to bank deposits as if they are separate revenue streams.

The SDE definition supports owner-benefit analysis. Recurring delivery charges do not become discretionary simply because the seller would prefer lower fees. If the buyer obtains different terms, show that as a supported buyer-specific scenario rather than rewrite historical earnings.

The IRS recordkeeping guidance supports retention of source records. Preserve statement detail and underlying exports that permit the buyer to trace channel revenue and costs rather than rely on a screenshot of total orders.

What security and customer-data limits apply?

Use approved role-based access, strong authentication, verified support channels, and documented administrator changes. Do not send passwords, banking credentials, or unrestricted customer files in a closing email. Confirm payment changes through the provider’s secure process and guard against impersonation.

The FTC personal-information guide supports limiting collection, access, retention, and exposure of sensitive information. A buyer should obtain only data it is lawfully entitled to receive and needs for the business, subject to contracts and applicable law.

Ask counsel about privacy promises, contractual restrictions, records retention, and any intended new marketing use. Owning a restaurant’s goodwill does not automatically permit unrestricted use of every customer record visible in a platform dashboard.

What belongs in the purchase agreement and closing calendar?

Have transaction counsel address the specified digital assets and rights, provider cooperation, required approvals, access, settlement allocations, refunds, disputed amounts, and consequences of a failed or delayed migration. Define representations by actual knowledge and evidence rather than promise platform-controlled outcomes.

Plan for account setup and testing without operating under unauthorized ownership or inaccurate tax and bank details. A staged transition needs clear responsibilities and lawful permissions; convenience does not justify bypassing platform controls.

The quality-of-earnings definition can help scope verification of channel dependence. If a large portion of earnings depends on a listing or agreement that may not continue, make that uncertainty visible before final price and financing decisions.

How should the first operating days be checked?

Verify the approved store identity, hours, menus, modifiers, pricing, availability, bank profile, tax information, device access, and point-of-sale connection. Use authorized tests and provider procedures. Review actual orders and settlements promptly so configuration errors do not compound for weeks.

Record outstanding refunds, promotions, chargebacks, and pre-closing adjustments through the agreed reconciliation process. Keep both parties’ access limited to what is appropriate after closing and remove obsolete permissions once required records and cooperation are secured.

Which mistakes should the buyer prevent?

  1. Accepting the seller’s password as proof of account ownership.
  2. Paying for reviews or rankings without provider confirmation.
  3. Assuming old commissions and promotions continue unchanged.
  4. Allocating all settlements solely by bank deposit date.
  5. Copying customer records without contractual and legal review.
  6. Calling migration complete before orders and reporting work correctly.

The useful outcome is an approved, tested ordering channel with clear rights and a reconciled cutoff. Historical sales matter only when the buyer understands the economics and the conditions required to continue them.

What else do owners and buyers ask?

Can the seller just give me the delivery-app password?

A password does not establish a permitted contract transfer, authorized ownership, correct tax identity, or safe payout setup. Follow the platform’s current ownership-change or onboarding process and review the actual agreement. Use approved access controls and confirmation rather than shared credentials, and preserve the information needed to reconcile pre-closing and post-closing transactions.

Will the restaurant keep its delivery reviews after I buy it?

Do not promise that outcome without platform-specific confirmation for the actual change. Reviews, listing continuity, visibility, rankings, menus, and terms may depend on the platform’s process and facts. Document what the provider confirms, distinguish it from the seller’s expectations, and consider the operating effect if some digital history does not continue.

Who receives payouts for orders around the closing date?

Define the contractual allocation and reconcile it to order dates, service dates, platform adjustments, settlement periods, refunds, and actual bank deposits. The payout date alone may not identify the economic owner. Have the CPA and counsel review the cutoff, evidence, collection responsibilities, and any agreed adjustment or holdback mechanism.

Should delivery sales be valued the same as dining-room sales?

Examine contribution and operating requirements by channel rather than apply a universal treatment. Delivery orders can involve commissions, promotions, packaging, refunds, integration fees, and additional labor. Reconcile gross orders to reported revenue and settlements, then assess whether the buyer can retain the channel under the actual platform terms and operating configuration.

Where can you verify the details?

Primary sources reviewed for this guide. Requirements can change; confirm the rules that apply to your address and transaction.

  1. Merchant portal protections and ownership-transfer verification — DoorDash
  2. Merchant frequently asked questions — DoorDash
  3. Protecting personal information: a guide for business — Federal Trade Commission
  4. Recordkeeping for your business — Internal Revenue Service

Return to buying a restaurant

YOUR NEXT CHAPTER STARTS WITH A CONVERSATION

Let’s talk about
your restaurant.

Buying, selling, or weighing your options? Bring your questions. We’ll help you think through the next step.

Book a confidential intro call
Book a confidential intro call