Lightspeed POS food cost integration
Used across full-service and multi-location restaurants.
There is no Lightspeedintegration. We're not going to pretend otherwise.
- No Lightspeed integration exists today: no OAuth connection, no item sync, no price write-back
- Nothing here syncs sales data either — Marji costs dishes, it doesn't read your till
If you're running Lightspeed
Lightspeed shows up in full-service kitchens and across multi-site groups, where the interesting problem isn't the till at all: the same dish quietly costs different money at different sites because the suppliers aren't the same. Marji costs per location rather than per brand, so two branches of one dish are two sets of numbers instead of one average that flatters the worse kitchen. If you run more than one, that is worth considerably more than a write-back.
How to use Marji with Lightspeed today
Costing runs off a photograph of each location's menu, so a group can be set up one kitchen at a time without touching Lightspeed at all. Invoices keep each location's numbers current on their own. Approved price changes get applied in Lightspeed by hand, per site, which is the same job you already do when a price moves.
What a POS integration buys you, precisely: it saves you retyping an approved price. Costing, watching supplier prices and naming the dish that drifted all run off photographs, whatever till you use.
Why Lightspeedisn't built yet
Not started. Lightspeed sits behind Square, which is built, and Toast, which is next. We'd rather ship one integration that survives a real menu than four that half work.
Start costing now; the integration can come later.
Photograph your menu, get your costed dish list in about a minute. Free tier, no card.
Start free →Status verified against shipped code, not a roadmap. See the changelog for what actually shipped and when, and the pricing page for which plan the Square write-back sits on. No plan here charges for an integration.