Your QuickBooks POS integration is on. But which mode is it on?

Every modern connector (Toast via Shogo, Square's QuickBooks Online sync, Clover Commerce Sync, Revel's QB sync, Lightspeed) lets the operator pick at setup whether to push every POS order line as its own QuickBooks journal entry (Detail mode) or to roll the day's activity into a small handful of category totals (Summary mode). Detail mode preserves item-level information: which menu items sold, which modifiers were attached, what discount codes applied. Summary mode collapses everything into Food Sales, Beverage Sales, Tax, Tip, Discount, and a couple of payment lines. Detail floods the chart of accounts with hundreds of lines per day; Summary is clean but loses item-level visibility entirely. Most operators pick Summary at setup to keep their books readable, then forget the choice was ever made.

Phone orders are the channel where modifier-driven upsells move the average ticket the most. Dine-in customers see physical menu cards. Online ordering forces a clean cart UI. But phone orders, especially when answered by a voice agent, are conversational: 'do you want extra cheese for $1.50, garlic knots for $4, or a 2-liter for $3?' Those modifiers and add-ons account for a real share of phone revenue. In Summary mode, the whole upsell story is invisible inside QuickBooks. In Detail mode, the bookkeeper can pull a P&L slice that shows modifier revenue specifically. The integration is technically working in both modes; only one of them lets you measure whether your upselling is contributing.

Open last week's QuickBooks Sales Journal or Daily Sales report. If you see roughly 5 to 10 lines per day per location (Food Sales, Beverage Sales, Sales Tax Payable, Discounts, Tips, plus payment categories), you are in Summary mode. If you see dozens or hundreds of lines per day with item-specific names ('Pepperoni Pizza Large', 'Extra Cheese', 'Side Salad'), you are in Detail mode. The setting itself lives in the connector dashboard, not in QuickBooks: Shogo settings under Mapping, Commerce Sync under 'Sync Detail Level', Square's QBO sync under 'Sales Sync Type', Revel's connector under 'Journal Mode', Lightspeed under 'Sync Granularity'. Each connector calls it something slightly different but the underlying choice is the same.

Sort of. The pragmatic pattern is: keep the QuickBooks-side connector in Summary mode so the chart of accounts stays manageable, and pull item-level reports out of the POS itself for AOV, modifier mix, and category P&L analysis. The downside is your bookkeeper and your operator are now reading from two systems and need to reconcile them on cadence. The other option is Detail mode plus a strict QuickBooks Class structure that buckets the line items back into a few summary categories at report time. Restaurant 365, xtraCHEF, and a few other middleware bridges sit in this seam specifically. There is no free option; you are picking which workflow to absorb.

PieLine increases the case for Detail mode (or for keeping Summary in QuickBooks plus item-level reporting in the POS). Phone orders processed by an AI agent ramp the modifier rate, the upsell attachment rate, and the substitution rate compared to staff-keyed phone orders. The whole point of an AI voice agent is that it offers add-ons consistently on every call, where a human cashier on hold might skip the upsell. If you cannot see modifier and add-on revenue separately in your books, you cannot tell whether the AI agent is paying for itself through AOV lift, even though the data is sitting in the POS untouched.

Toast: via Shogo or xtraCHEF/Restaurant365 in Item-Level mode, or via Toast's own QuickBooks Online connector in 'Detailed Sync' mode. Square: Square's native QBO sync supports 'Itemized' as an option in addition to the default 'Daily Summary'. Clover: Commerce Sync exposes 'Detailed' as an option; the Intuit-built Clover connector defaults to summary and does not expose item detail at all (a known limitation). NCR Aloha: Detail mode exists via Restaurant365 or Shogo bridges; Aloha's own export is summary-only. Revel: Revel's QBO connector has 'Item-Level' as a paid add-on; the standard plan is summary. Lightspeed: granular item sync is available in the QBO integration. Square and Toast give you the most granular item-level path on the standard plan.

It can if the connector creates new GL accounts on the fly each time the POS gains a new menu item. The fix is to map every POS item or category to an existing QB Item or Income Account before turning Detail mode on. This is a one-day setup project that pays back across years of clean books. The mistake operators make is flipping Detail mode on with no mapping and watching their chart of accounts grow by 200 line items in a week. Set the mapping first, then turn the toggle.

PieLine posts every order to the POS via the POS's native order endpoint with the same payload structure a tablet or KDS would produce: a base item ID, an array of modifier IDs each with its own price delta, and the standard qty/price/tax fields. The POS records modifiers as discrete child line items, exactly the way it would for a manually keyed order. That preservation matters: if the modifier line exists on the POS order, it can survive Detail-mode sync to QuickBooks; if PieLine flattened modifiers into a single price-adjusted parent, no connector could recover them downstream.

Industry data on this is patchy because most restaurants cannot measure it for the reasons in this guide. From PieLine's own deployments, well-tuned voice agents lift average order value by 15 to 20 percent versus the same restaurant's staff-answered baseline. The bulk of that lift comes from systematic add-on offers (drink, side, dessert, upsize, premium toppings), all of which appear in the POS as modifier or accompaniment line items. So if you flip your QuickBooks integration to Detail mode and segment by item type, you should expect to see modifier and side revenue grow as a percentage of phone-channel revenue once the AI agent is running.

Yes. Single-location operators with a fractional bookkeeper, simple menus, and no investor or franchisor reporting requirement do fine on Summary. The reconciliation surface is small enough that pulling the daily POS report once a week to spot-check is workable. Detail mode becomes essential when a franchisor wants item-level reporting per location, when a multi-unit operator needs cross-location item performance to make purchasing decisions, when an investor expects modifier-attached revenue analysis, or when the operator is actively running an AOV experiment (changing scripts, A/B testing prompts, comparing time-of-day upsell rates) and needs item-level signal in QuickBooks-derived reports.

No. Both Summary and Detail are forward-looking from the date you flip the toggle. Historical entries stay as they were. If you want to compare modifier revenue in months before and after the switch, you have to derive the pre-switch numbers from POS reports, not QuickBooks. Plan a clean cutover date (start of a fiscal month is easiest), document the change in a journal entry note, and write down the date in your ops manual so a future bookkeeper does not interpret the structural change in account activity as suspicious.