Lightspeed reports vs a daily P&L: why the POS looks good and the bank doesn't.

Lightspeed sits at the heart of a lot of small retail and hospitality businesses — a boutique with one register, a small restaurant group with three sites, a bike shop with deep inventory needs. The product is genuinely strong at what it was built for: ringing sales, managing stock, scheduling staff, and rolling up category-level performance across locations. The uncomfortable part is the gap between those reports and your bank balance. You finish a strong Saturday — Lightspeed says €5,400 in sales, top category up 18% week on week — and on Monday the deposit lands at €5,180. By Friday the card processor takes its cut, the supplier invoice clears, the rent comes out and the day that looked great on the POS has become a day that barely broke even. Lightspeed never told you that, because it was never built to. This post walks through what Lightspeed reports show well, what they quietly omit, what Lightspeed's own margin views actually do, what the accounting-bridge integrations are good for, and how to land a real EBIT number for today before you close up — in about 60 seconds of manual entry. nouz is the daily P&L layer that sits next to a Lightspeed setup; this post is the honest version of how to make it work.

TL;DR

What Lightspeed does well

Credit first. Lightspeed is mature software with a clear scope, and inside that scope it does a lot of operational work very well. Most of these are jobs your old cash register and a notebook simply could not do, and they are why owners pay for the platform in the first place:

• Register operations. Fast checkout, split payments, partial refunds, gift cards, customer accounts. Day-to-day till work is reliable and quick — which matters when there is a queue forming.
• Inventory management. Stock counts that update as you ring, low-stock alerts, purchase orders to suppliers, transfers between locations. For a shop with hundreds of SKUs this is the difference between knowing what you have and guessing.
• Multi-location consolidation. If you run two or three sites, Lightspeed rolls them up into one view — sales by location, inventory by location, performance comparisons. Owners who used to walk a spreadsheet between sites every Sunday do not miss that.
• Employee scheduling and performance. Sales-per-employee, hours worked, labour cost reporting at the staff level. Useful for spotting the closer who upsells consistently versus the one who undercharges discounts.
• Category sales reports. Sales by department, by brand, by sub-category, by date range. Surfaces which parts of the shop are growing and which are quietly fading.
• Customer profiles and loyalty. Purchase history per customer, top-spending customers, customer segments for marketing. The kind of CRM-lite that small retailers used to keep in a paper book.
• Vendor and PO management. Track what you have ordered, what is arriving, what is overdue. Reduces the "did we already order more of these?" phone calls.

None of this is fluff. A shop that ignores Lightspeed reports entirely is operating blind on the inventory and operational side. The mistake — and it is the mistake nearly every Lightspeed owner makes — is assuming that because the platform is comprehensive on operations and sales, it must also be comprehensive on profit. It is not. The reporting suite was built to answer questions about commerce and inventory, not questions about the P&L. Those are two different reports and Lightspeed only ships one of them well.

What Lightspeed reports do not surface

The word "hides" is not quite fair to Lightspeed — none of these numbers are concealed. Most of them exist somewhere, in payouts, in supplier emails, in your bank feed, or in a tab you do not check daily. But none of them are subtracted from your sales line on the dashboard you actually look at every morning. Which, operationally, is the same as hiding them. A number that is not on the screen you look at is not factored into your decisions.

1. Payment processor fees do not subtract from your sales reports

When a customer pays €100 on a card through Lightspeed Payments (or any integrated processor), the deposit that lands in your bank is typically €97–€98 — €100 minus a fee that varies by region, card type, plan and processor but generally lands in the 1.5–2.9% range plus a small per-transaction component. That fee is real money leaving your business on every card sale. It is visible inside your payment processor's payouts area, broken out per batch. It does not appear on your Lightspeed sales dashboard, does not subtract from your "sales today" line, and is not reflected in your category sales reports. If you took €5,400 today and 92% of it was on card at a blended 2.1% effective fee, that is roughly €104 of fees you paid today and never saw on the Lightspeed screen.

2. Variable costs outside the POS are entirely invisible

Lightspeed knows what you sold. It does not know what it cost you to fulfil the sale beyond the item cost field. Packaging materials, delivery costs to the customer for click-and-collect or local delivery, in-shop supplies (cleaning, till rolls, gift wrap, coffee for the team), shipping cost from your supplier on the inbound side that was not allocated cleanly into the cost-per-item, ad spend if you run paid traffic to your store — none of this lives in Lightspeed. Each of these is a real cost that comes out of the day's profit, and none of them get subtracted before the dashboard shows you "sales today: €5,400."

3. Fixed overhead is not anywhere in Lightspeed

Your shop rent, your insurance, your salaries (yours and your team's), your Lightspeed subscription itself, the other software you pay for (email tool, scheduling tool, accountant's portal), your loan repayments if you took financing for fit-out — none of this exists inside Lightspeed Reports. It is fixed cost that has to be allocated to each trading day before you can know whether the day was profitable. Lightspeed does not allocate it because Lightspeed does not know about it. A shop with €18,000/month of fixed costs has to clear roughly €592/day just to break even on overhead — before COGS, before fees, before variable costs. That €592 floor is invisible inside Lightspeed.

4. Unrecovered shipping and delivery costs are not netted

If you charge customers €4.95 for delivery and the carrier charges you €6.20, you are losing €1.25 on every delivered order. Lightspeed shows the €4.95 you charged on the order; it does not show the €6.20 the carrier billed you the following week. The same applies to gift wrap, free-shipping thresholds, and any "thrown in" service you offer. The gap between what you charged and what it actually cost is real margin leakage, and it does not appear on any sales report.

5. Refunds and returns lag the report you look at

Lightspeed's sales total is net of refunds processed in the period, but the timing is messy: a return processed on the 4th of next month for a sale rung on the 27th of this month deducts from next month, not as a correction to this month. For a retailer with a meaningful return rate — apparel can run 15–30%, electronics 8–15%, even general gift 4–8% — this lag distorts both months. The dashboard says "we did €92,000 in March"; the truth three weeks later is closer to €83,000 once March returns finish flowing through.

6. True EBIT is simply not computed anywhere

Stacking the five points above: there is no place inside Lightspeed where the formula gross revenue − tax − card fees − COGS − variable costs − fixed overhead = today's EBIT is computed and shown to you. That number — the only number that answers "did today actually make money?" — does not exist in the product. It is the gap a daily P&L fills.

Side-by-side: what Lightspeed shows vs what it hides

The full picture in one table. Read the right-most column as "where you have to go to find the truth, since Lightspeed will not put it on the dashboard for you."

Lightspeed's gross margin view — and why it is not EBIT

Lightspeed knows the sale price of an item and, if you have populated the Cost field on the product, it knows the item cost. From those two numbers it can compute a gross margin per item — sale price minus cost, divided by sale price. Many Lightspeed accounts surface this in some form: as a column on inventory reports, as a margin number on product detail, or aggregated up into a margin view across categories. The exact location and naming varies by Lightspeed product line (Retail vs Restaurant vs Golf) and by plan tier, so check what your specific account shows rather than assuming.

What this gross margin view actually does:

• Multiplies units sold by the Cost field on each product to produce a COGS estimate.
• Subtracts COGS from sale price to produce a gross profit and gross margin %.
• Lets you segment by item, category, location or date range.

What it does not do:

• It does not subtract payment processor fees. Card fees are still in your processor's payouts area, not netted out of sales in the margin view.
• It does not include off-POS variable costs. Packaging, delivery, supplies, ad spend — none of it is pulled in. The "margin" shown is purely gross margin on item cost.
• It does not include fixed overhead. Rent, salaries, insurance, your Lightspeed plan itself, the rest of your software stack — none of it.
• It only works for items where Cost is populated. If you have 1,200 SKUs and 700 have cost data, the margin view is computing margin on roughly 58% of your catalogue and silently treating the rest as 100% margin.
• It does not surface daily EBIT on the dashboard. You have to navigate into the report, set a date range, and read it manually. Most owners do this monthly at most, not nightly.

So Lightspeed's margin view is closer to "gross margin per item, summed up" than to a real P&L. For a shop with clean per-SKU cost data, it answers "what was my gross margin this week?" — useful, but several steps short of "did this week actually make money after everything?" For a shop with patchy cost data, it can be actively misleading: a 64% margin headline that looks healthy because half the catalogue is missing cost inputs and is being treated as pure profit.

Lightspeed + Xero / QuickBooks bridges: an honest take

Lightspeed integrates with Xero and QuickBooks Online — two of the largest small-business accounting platforms. Owners who run a serious shop and have an accountant in the loop often run one of these bridges to push Lightspeed sales, fees and (sometimes) inventory data into the accounting ledger. We are not going to claim specifics of how each integration handles every edge case — they evolve regularly, the exact field mappings change, and the right thing for you to do is read the current integration documentation or ask your accountant who has set it up before. What we can say at the category level is honest enough.

What these bridges are good for. Moving structured sales totals, tax breakdowns and (depending on configuration) payment fee data from the POS into the bookkeeping ledger so that the monthly close is faster and less error-prone. Your accountant can reconcile the bank against bookkeeping against POS without typing the same totals into three places. For a multi-location shop this saves real hours every month.

What these bridges are not good for. Producing a same-day operational EBIT view that you, the owner, look at tonight before going to bed. The accounting ledger lags real-time operations by however often it is reconciled — daily if your bookkeeper is exceptional, weekly if normal, monthly if average. By the time the bridge has pushed today's data into Xero or QuickBooks and someone has reconciled the bank against it and categorised the off-POS expenses that did not flow through the POS, today is no longer today. The bridge serves the accountant's monthly workflow, not the owner's nightly decision.

This is not a criticism of the bridges — they do the bookkeeping job well, which is what they were built for. It is an observation about a different job: if you want a daily P&L number tonight, the accounting ledger is the wrong layer to wait on. The daily P&L sits above the bookkeeping, on top of the POS, owned by the operator, and updated by them in roughly a minute each evening. Different cadence, different audience, different tool.

The daily P&L approach: 5 numbers, 60 seconds

The honest alternative to Lightspeed's sales-side reporting (and to waiting for the monthly Xero/QuickBooks close) is shorter than both: at end of day, enter five numbers and compute one. The discipline takes about 60 seconds once you have done it three times. The five numbers are:

1. Gross revenue today. Take this from Lightspeed's sales summary for today. Includes tax, before any fees deducted, including both cash and card.
2. Tax collected today. Visible on the same Lightspeed sales summary — the tax line broken out. The amount of today's gross that is sales tax / VAT and is not actually your revenue.
3. Card fees on today's sales. Your effective rate × the card-paid portion of today's revenue. Most Lightspeed Payments users (or whichever processor they use) have a stable effective rate they can compute once from a month of payouts (e.g. 2.0%) and apply daily without re-deriving. Card fees apply to card revenue only — never to cash.
4. COGS sold today. Either the per-item Cost data summed across today's receipts if your catalogue is fully populated, or a rough rule-of-thumb (e.g. "our shop averages 42% COGS, today's net revenue × 42%") if not. The rule-of-thumb is acceptable for daily tracking — it does not need three decimal places.
5. Variable costs today. Sum of packaging used, delivery cost paid out, in-shop supplies consumed, ad spend across whatever platforms you run. Each of these is one number from one place — write the three or four numbers, sum them.

Then the one computation:

Use our daily profit calculator to run the math on a sample day before you commit to a tool. The monthly fixed overhead is the sum of your shop rent, salaries (yours and your team's), insurance, your Lightspeed subscription, the rest of your software stack, your accountant — divided by 30.4375 (the average number of days per month, so February does not carry a heavier daily slice than March).

The first time you do this, the number will surprise you. Shops that thought they were doing well discover they are running at break-even after fees and fixed costs. Shops that thought they were break-even discover one category is carrying the whole P&L. Shops that thought they were losing money sometimes find out they are actually profitable, just badly under-priced on one product line. The point is not the specific number — it is that you finally have one, and it updates today, not in six weeks.

When Lightspeed reports are enough — and when they aren't

A fair section, because this post should not end with "you need another tool" if the truth is more nuanced.

When Lightspeed reports are enough. If you run a high-volume retailer where the primary operational questions are about item-level velocity ("which SKUs are turning, which are dead stock"), category trends ("is the bike category up or down vs last spring"), and inventory health ("what do I reorder, what do I mark down"), Lightspeed alone gives you everything. You are not really operating to a profit target — you are operating to a sell-through and stock-turn target, and the profit number is computed monthly by your bookkeeper. That is a legitimate way to run a shop. Lightspeed serves it well.

When Lightspeed reports are not enough. If you are operating to a profit target — i.e. you want to know each day whether the shop is on track for the month's EBIT goal, you have a clear monthly break-even number in your head, and you adjust pricing, staffing or marketing on the basis of how the days are stacking up — Lightspeed alone cannot tell you. The platform was not built to roll fees, variable costs and fixed overhead into a single per-day operating profit number. You need a layer on top.

Most small Lightspeed shops are in the second camp, even if they have been operating like the first. Our piece on why retail stores quietly lose money walks through the most common ways this happens — under-priced bestsellers carrying over-priced mistakes, labour creeping above 30% of net revenue without anyone noticing, packaging and delivery costs eating margin on click-and-collect orders. None of these show up in a sales report. All of them show up in a daily EBIT number.

Same logic applies to the daily cadence itself: daily sales reports for retail and daily vs monthly P&L cover the operational difference between checking a number tonight versus reading it next month from your accountant. The short version is that the lag between a problem starting and you finding out is the cost — and a sales report is not a profit report.

How nouz pairs with Lightspeed

A clean honesty section, because the last thing this post should do is sell software that does not match what we just described. nouz is a daily P&L tool built for small physical shop owners — including shops running on Lightspeed. Here is what it is and what it is not.

What nouz is. A simple end-of-day entry form (gross revenue split cash vs card, tax, card fees, COGS, variable costs) plus a fixed-cost stack you configure once (rent, salaries, insurance, Lightspeed subscription, the rest of your software stack). Every evening you spend about 60 seconds entering the day's numbers and the dashboard shows today's real EBIT — net of all the things Lightspeed reports do not surface. Fixed costs are allocated using the monthly ÷ 30.4375 method so February does not over-allocate. Card fees apply to card revenue only, never to cash. The formula lives in one place and the math is auditable on the page — not behind an opaque integration.

What nouz is not. nouz is not a Lightspeed integration. It does not connect to Lightspeed, it does not auto-pull your sales totals, it does not sync inventory, and it does not currently plan to. You read your sales summary from Lightspeed at end of day (about 10 seconds — the totals are right there on the screen), and you type the day's numbers into nouz. The reason this is manual is deliberate: every owner we talked to who used integration-heavy profit dashboards eventually ran into the broken-integration problem — API tokens expiring, a Lightspeed version update changing the data shape, a webhook silently dropping. Manual entry of five numbers from a screen you already have open is faster than maintaining an integration, more reliable than waiting for it to recover, and forces the daily discipline of actually looking at the numbers rather than glancing at a dashboard you trust by default.

A typical pairing in a real retail day: you open the shop, you ring sales on Lightspeed all day, you check inventory and category reports in Lightspeed as needed during the day. At close, you read the day's sales summary on Lightspeed, you type five numbers into nouz on your phone, and the EBIT for today appears before you walk out. The accountant still gets the monthly close from the Lightspeed → Xero or QuickBooks bridge. The owner still gets a real operating-profit number every evening. Different layers, different cadences, no integration to break.

If your shop does €5M/year, runs a real BI stack and has someone in-house who maintains integrations between Lightspeed, the warehouse system, and the BI tool, a fully integrated profit dashboard makes sense. If you are a one- or two-person retail shop doing €15k–€200k/month and trying to know tonight whether today made money, the 60-second manual entry alongside Lightspeed is the lighter, more durable answer. nouz pricing is monthly-only and built for that customer.

What to do tonight

Three steps, fifteen minutes total, no software install required. Do these tonight regardless of whether you end up using nouz, an accounting bridge, or a spreadsheet you build yourself.

1. Compute your effective card fee rate. Take the last 30 days of payouts from your payment processor (Lightspeed Payments or whichever you use). Sum the gross processed and sum the fees deducted. Fees ÷ gross = your effective rate (typically 1.6–2.5% for integrated POS payments). Write it down — you will reuse this number every evening.
2. Compute your blended COGS %. Pull one clean month from Lightspeed's margin view (or estimate it from your supplier invoices if cost data is patchy). Total COGS ÷ total net revenue for that month = blended COGS %. Write it down. Good enough for daily tracking even if it is not perfect at the SKU level.
3. List your monthly fixed costs. Rent, salaries (yours and your team's), insurance, Lightspeed subscription, every other paid software tool, accountant, loan repayments if any. Sum them. Divide by 30.4375. That is the daily slice you subtract from net contribution every evening to land at real EBIT.

With those three numbers configured once, tonight's 60-second close-out is: today's gross revenue and tax (from Lightspeed sales summary), today's card fees (gross × your effective rate × card share), today's COGS (net revenue × your blended COGS %), today's variable costs (packaging + delivery + supplies + any ad spend, summed). Subtract, subtract, subtract the daily fixed slice. That is today's EBIT — and it landed before you closed the shop.

For more on adjacent comparisons: Shopify reports vs daily P&L covers the same gap for Shopify owners, and Square dashboard vs daily P&L does the equivalent for Square users. Best daily P&L tracker 2026 is our honest comparison of the five real options for small shops, including which fits what kind of operation. For the wider operating system Lightspeed-using retailers actually need to land on, see the retail profitability pillar.

Lightspeed Reports is good at what it was built for. It was not built to tell you whether today made money — and pretending it was, by checking sales every morning and feeling informed, is how a lot of Lightspeed shops end up surprised by a month-end report that does not match their gut feel. The honest answer is a five-number close-out at end of day. Sixty seconds. Real EBIT. Tonight.

FAQ