The problem. When a DoorDash or Uber Eats order is rung up manually at the register (using "Other Payment → DoorDash" or "→ Uber Eats" as the tender), Scotch would otherwise calculate tax on it like any other sale — even though the platform already collected and remitted that tax to the state on your behalf. Left alone, that's tax counted twice.

Scotch has two ways to prevent that, and they work completely differently under the hood. One zeroes tax on the order immediately, in Scotch. The other leaves tax on and has you subtract the partner-remitted amount later, when you file.

You can only use one per order — and in practice, you should pick one per merchant. They're mechanically incompatible on a single order (more on why below), and mixing them order-by-order will make your own bookkeeping harder to follow later, since some third-party orders will show tax and others won't for what's otherwise the same category of sale.

The mechanism. A customer profile can be marked "Tax exempt." Attaching that customer to the cart before completing the sale zeroes tax on the whole order — the same effect as the manual "Tax exempt" toggle at checkout.

A new customer only needs a name to save. Email and phone are optional — at least one of name, email, or phone is required, so a name alone is enough.

There's no built-in safeguard against picking the wrong customer. The register's customer search is generic and doesn't flag this profile as special — give it an unmistakable name (like "DoorDash" or "Uber Eats") and make sure staff know to look for it specifically. The terminal's customer picker does show a "Tax exempt" column, so a cashier can at least confirm they've picked an exempt profile before attaching it, even without an explanation of why.

Once saved, it syncs to the register in real time. No manual "check for update" needed.

This lowers your recorded total for these orders. Because the zeroed tax applies to the whole line total — merchandise and any third-party surcharge together — Scotch's recorded total for an order using this option will read lower than what the customer was actually charged on the platform.

Tax still shows up on an order you attached the customer to: double-check the customer was actually attached before completing the sale, and that its "Tax exempt" toggle is on.

Not sure the new customer profile has reached the register yet: it should be available within moments of saving — no separate sync step to wait on.

Worried about picking the wrong customer at the register: there's no dedicated safeguard — give the profile a name that won't be confused with a real customer.

The mechanism. Set a price increase for third-party orders (Settings → Devices → "Ecommerce order price increase (%)") — this applies automatically to DoorDash, Uber Eats, Square, City Hive, and Bottle Capps orders at checkout, one shared rate across all of them. That surcharge is designed to be taxed like a price increase, not added tax-free — so the order rings up matching what the customer was actually charged on the partner's platform.

The setting isn't labeled "DoorDash surcharge rate" anywhere in the app — that's only an internal nickname. Look for "Ecommerce order price increase (%)" specifically.

This keeps your recorded total matching the customer-facing charge. Nothing is zeroed in Scotch — the tax question gets handled separately, at filing time.

The surcharge itself is hidden by default, everywhere — not on the receipt, not on the cart summary, and even Back Office's own order view shows it generically as "Adjustment amount." There's no built-in way to visually confirm a Scotch total against a platform's payout report; you'd compare totals manually if needed.

Sales tax total looks too high compared to what you expect to owe: check whether that's just the third-party portion — expected until you subtract the partner-remitted amount at filing time.

Don't have a statement from the partner yet: get it from their own merchant portal — Scotch doesn't generate or track this figure for you.

Can't find the surcharge as its own line on a receipt or order: it's hidden by default everywhere it could show up, with no back-office setting to reveal it.
​
​

Want your Scotch totals to always match what the customer was actually charged, and don't mind a manual subtraction step each filing period? Use Option B.

Want the tax question resolved immediately, order by order, with no extra step at filing time? Use Option A — but know that your recorded totals for these orders will run lower than the customer's actual charge.

Whichever you pick, stick with it across all your third-party orders. Mixing the two per order makes your own later reconciliation harder to follow, and there's no code path that lets a single order use both anyway — marking an order tax-exempt zeroes tax on the entire line total, surcharge included, so Option A can't coexist with Option B's "tax the surcharge" behavior on the same order.