What Online Ordering Really Costs

Direct answer

The cost of online ordering is the complete cost to acquire, accept, prepare, fulfill, support, and reconcile an order. Include platform subscription or commission, payment fees, marketplace marketing, delivery charges or subsidies, refunds, chargebacks, packaging, menu maintenance, integration fees, hardware, support, and incremental labor. Then account for food or product cost and channel-specific pricing to estimate contribution margin. Compare first-party and marketplace channels with the same order sample, but do not assume marketplace orders are purely incremental or that a lower commission produces better operations.

Build a per-order model

For each channel, record gross menu value, discounts funded by merchant and platform, taxes, tips, customer delivery fees, merchant delivery subsidy, commission base, payment base, refunds, cancellations, chargebacks, packaging, and labor. Identify which amounts the platform collects as agent and how remittances appear. Reconcile order reports to POS tickets, settlement reports, and bank deposits. Measure menu-price and availability sync, modifier errors, tablet re-entry, throttling, prep-time controls, refund ownership, customer-support handoffs, and payout timing. Model monthly fixed fees separately so their per-order effect changes with volume. Review contract provisions for promotion participation, data access, term, price changes, and termination.

Contribution example

For a $40 food order, assume a $10 food cost, $2 packaging, $5 incremental labor, $8 platform commission, $1.20 payment cost, and $1 merchant-funded promotion. Estimated contribution before fixed overhead is $40 − $10 − $2 − $5 − $8 − $1.20 − $1 = $12.80, or 32% of menu value. If a $300 monthly integration supports 500 orders, allocate another $0.60 per order for analysis, reducing the example to $12.20. This is not an industry benchmark: actual commission bases, taxes, tips, refunds, labor, and incremental demand differ. Model canceled and refunded orders and compare contribution with the capacity they consume.

Build a topic-specific comparison

For first-party and marketplace ordering economics, compare like with like and retain the evidence behind every score. Collect order-level exports showing menu value from the operating business, label its date and owner, and note whether it represents a fact, requirement, assumption, or unresolved dependency. Compare funded discounts under the same locations, channels, volume period, user roles, and exception conditions; reject a demonstration that changes the scenario between providers. Define an acceptance result for taxes, identify which document or reproducible test proves it, and record limitations instead of reducing the result to yes or no. Ask who supplies, configures, bills, supports, and can change tips; preserve the answer with the controlling proposal or agreement rather than relying on a meeting note. Test commissions with ordinary and difficult cases from this business, including a correction or failure path, so the comparison reflects daily work instead of a sales script. Score payment costs separately for current fit, implementation effort, continuing ownership, and exit risk; a strong feature can still create an unacceptable operational dependency. Collect delivery subsidies from the operating business, label its date and owner, and note whether it represents a fact, requirement, assumption, or unresolved dependency. Compare cancellations under the same locations, channels, volume period, user roles, and exception conditions; reject a demonstration that changes the scenario between providers. Define an acceptance result for refunds, identify which document or reproducible test proves it, and record limitations instead of reducing the result to yes or no. Ask who supplies, configures, bills, supports, and can change packaging; preserve the answer with the controlling proposal or agreement rather than relying on a meeting note. Test labor with ordinary and difficult cases from this business, including a correction or failure path, so the comparison reflects daily work instead of a sales script. Score remittances separately for current fit, implementation effort, continuing ownership, and exit risk; a strong feature can still create an unacceptable operational dependency. Collect channel capacity from the operating business, label its date and owner, and note whether it represents a fact, requirement, assumption, or unresolved dependency.

Calculate the relevant costs

The cost model for first-party and marketplace ordering economics should expose dollars, timing, uncertainty, and operational effort. Quantify subscriptions as one-time, recurring, usage-based, loss-related, or internal labor, and state the time period and transaction assumptions behind the amount. Model commission bases at low, expected, and stressed activity, because a fixed monthly price and a per-event price behave differently as volume changes. Trace payment events to a proposal line, contract term, invoice, operating record, or documented estimate; leave it marked unknown when the evidence is incomplete. Identify which party controls promotion funding, what can trigger a change, whether notice is required, and whether the expense continues during migration or termination. Measure delivery separately from revenue or gross payment volume so a percentage headline does not hide dollars, staff effort, customer loss, or cash-flow timing. Reconcile actual integrations after launch to the approved model, investigate the variance, and update the forecast without retroactively changing the original assumptions. Quantify hardware as one-time, recurring, usage-based, loss-related, or internal labor, and state the time period and transaction assumptions behind the amount. Model menu maintenance at low, expected, and stressed activity, because a fixed monthly price and a per-event price behave differently as volume changes. Trace packaging to a proposal line, contract term, invoice, operating record, or documented estimate; leave it marked unknown when the evidence is incomplete. Identify which party controls incremental labor, what can trigger a change, whether notice is required, and whether the expense continues during migration or termination. Measure support separately from revenue or gross payment volume so a percentage headline does not hide dollars, staff effort, customer loss, or cash-flow timing. Reconcile actual chargebacks after launch to the approved model, investigate the variance, and update the forecast without retroactively changing the original assumptions. Quantify refunds as one-time, recurring, usage-based, loss-related, or internal labor, and state the time period and transaction assumptions behind the amount. Model payout timing at low, expected, and stressed activity, because a fixed monthly price and a per-event price behave differently as volume changes.

Common mistakes

Use these failure patterns as review prompts, then document the control or owner that addresses each one.

• Comparing only commission percentage omits payment, promotion, delivery, and operating costs.
• Treating all online volume as new sales overstates incremental benefit.
• Ignoring refunds and remittance timing creates unexplained deposit differences.
• Running different menu data across channels increases errors and support work.
• Allocating fixed costs using peak volume makes low-season economics look artificially favorable.

Implement and test this topic

Implementation for first-party and marketplace ordering economics is complete only when topic-specific success and failure paths have passed. Turn this into a witnessed acceptance test: place modified. Record the starting configuration, expected result, actual result, identifiers, owner, and follow-up for any exception. Assign a trained role to unavailable, restrict permissions to what that role needs, and document the exact point where staff must stop and escalate. Exercise canceled in normal operation and under a realistic failure, correction, timeout, or duplicate condition; a single successful attempt is not adequate evidence. Pilot refunded with limited exposure where practical, preserve a continuity or rollback path, and name the person authorized to pause the launch. Verify reporting and reconciliation after delayed, because a customer-facing success message does not prove settlement, downstream synchronization, or correct accounting. Revisit high-volume orders across channels after the first operating cycle and look for manual workarounds, support delays, configuration drift, customer confusion, or terms that differed from implementation. Turn this into a witnessed acceptance test: trace each into the POS and kitchen. Record the starting configuration, expected result, actual result, identifiers, owner, and follow-up for any exception. Assign a trained role to then reconcile remittance to the bank, restrict permissions to what that role needs, and document the exact point where staff must stop and escalate.

Verify the decision

Verify first-party and marketplace ordering economics with current, appropriately authoritative material and reproducible business records. Use final platform contracts for the claims it is positioned to support, save its publication or version date, and distinguish direct evidence from interpretation. Cross-check promotion terms against the implemented configuration and the controlling agreement; general documentation may not describe negotiated terms or enabled features. Record who reviewed order and payout exports, when it was reviewed, what question it answered, and which material uncertainty remains before a decision can be approved. Recheck POS tickets whenever the provider, network rule, jurisdiction, product version, sales channel, or business workflow changes materially. Preserve measured labor and packaging costs with related correspondence and test results so another reviewer can reproduce the conclusion without depending on memory or vendor assurances. Escalate beyond support records when a legal, tax, accounting, employment, or security conclusion is needed; this resource does not supply professional advice. Use government competition and finance guidance for the claims it is positioned to support, save its publication or version date, and distinguish direct evidence from interpretation.

Primary and authoritative sources

Links were accessed 2026-09-08. Confirm the current version before relying on a rule or requirement.

1. Competition in the Food Delivery Marketplace — Federal Trade Commission
2. Manage your finances — U.S. Small Business Administration