Square: COGS Drift Across Locations

Square for Restaurants tracks menu sales and theoretical food cost per location. It cannot show real COGS drift across locations without QuickBooks vendor bills and inventory counts.

Square for Restaurants runs many fast casual operators across two, five, or fifteen locations. The POS reports sales by menu item at each store. Square does sales reporting well. It cannot show real cost of goods sold drift between locations, because real food cost lives in QuickBooks vendor bills from US Foods, Sysco, and Restaurant Depot, and physical inventory counts live in spreadsheets. Without joining all three to the Square menu sales, food cost per location is a guess based on the recipe card, not a real number. Locations that drift two percentage points high on food cost wipe out a quarter of net margin before anyone notices.

What Square for Restaurants Reports Actually Show

Square for Restaurants shows menu item sales per location, daily sales totals, average check, item modifiers, void rates, and the theoretical food cost per item if recipes are loaded. The sales side is accurate. Inventory deduction against recipes can be configured but is only as good as the recipe build, the prep loss assumptions, and how often inventory is counted. What Square does not have is the actual amount paid for chicken, produce, packaging, and beverages this week per location, the freight charges, the credit memos for returns, or the physical inventory variance between books and shelves.

The Data Square for Restaurants Cannot See

Real food cost per location lives in QuickBooks vendor bills tagged by location class. Each vendor delivers at different price points to each store, with different freight and minimum order surcharges. Physical inventory counts (weekly or biweekly) show variance between what the POS deducted and what is actually on the shelf. Waste and comp logs live in Square but are not reconciled against the vendor bills. The real cost of goods per location is the sum of vendor bills allocated to that location, adjusted for ending inventory and waste, divided by the menu sales for the period. Square holds the menu sales. QuickBooks holds the vendor bills by class. The inventory count and waste log live in operational notebooks. Operators who try to reconcile this rebuild it monthly per location, and by then a high-drift location has bled another month of margin.

Questions Fast Casual Owners Actually Need Answered

These are the questions fast casual operators ask when reviewing locations and recipe builds. Each one requires Square data joined to QuickBooks vendor bills and inventory counts.

• Which locations have the highest food cost percentage this week after vendor bills are loaded?
• Which menu items show the largest gap between theoretical and actual food cost?
• Which vendors charge different prices for the same SKU across our locations?
• Which location has the highest waste-to-sales ratio?
• How much margin are we losing on the locations whose food cost drifted up two points this month?
• Which menu items should be repriced or removed because their actual margin dropped below target?

How DataBlueprint Connects Square for Restaurants and Answers Those Questions

DataBlueprint connects to Square for Restaurants through its API, read-only. It also connects to QuickBooks Online or Desktop, your inventory system if you use one (MarketMan, MarginEdge), and your supplier portals where available. The Knowledge Graph builds automatically and links every Square menu item sold at every location to the vendor bills paid for the ingredients that built it, the physical inventory variance, the waste logs, and the burdened labor for the period. The answer engine is a private LLM running inside your own dedicated environment on AWS Bedrock. Data stays in that environment and is never used to train a public model. Every answer cites the underlying Square sales, the QuickBooks vendor bill, and the inventory count. When the system flags a location as drifting, you see the specific SKUs and vendors driving the drift. Setup runs in one business day. DataBlueprint does not replace Square for Restaurants. The POS, KDS, and online ordering stay in Square. DataBlueprint reads from Square and from QuickBooks and your inventory tools to answer the COGS-drift questions Square cannot answer alone.

Getting Started: Connecting Square for Restaurants to DataBlueprint

Square for Restaurants connects through its API. QuickBooks connects through the Online or Desktop API with the location class structure mapped. Inventory and supplier systems connect in the same window. All connections are read-only. First answers typically arrive within hours. Two practical next steps: model the margin lift from closing the COGS gap on the highest-drift locations with the ROI calculator, then read the Concepts page for how the Knowledge Graph turns Square sales and QuickBooks vendor bills into location-level real COGS.

Frequently Asked Questions

Does DataBlueprint write back to Square for Restaurants?

No. The Square API connection is read-only. DataBlueprint reads sales, menu, modifier, location, and employee data. It does not modify, create, or delete records inside Square.

Why does Square not show real COGS drift between locations?

Square shows theoretical food cost based on the recipe card. Real food cost requires QuickBooks vendor bills tagged by location and a physical inventory reconciliation. Those data sources live outside Square, so the drift cannot be computed inside it.

How does DataBlueprint allocate vendor bills to each location?

Through the QuickBooks location class structure. Each vendor bill line item is tagged to the location it served. The Knowledge Graph aggregates by location and divides by menu sales from Square at that location to produce real COGS per location.

Does DataBlueprint work with MarketMan or MarginEdge?

Yes. When an inventory or food cost tool is in place, DataBlueprint connects to it for the inventory count and recipe data, then joins that into the Square sales and QuickBooks vendor bills.

How fast can I see COGS drift after connecting Square?

First answers arrive within hours of the Square, QuickBooks, and inventory connections going live. The full per-location COGS drift report is usually available the same business day.