Lightspeed X error LSX002 — "Unexpected Lightspeed sale status"

What this error means

BRM received an update from Lightspeed X about a sale (for example, after a payment is taken directly in Lightspeed) but the sale's status wasn't one BRM recognises. Rather than guess, BRM refuses to apply it — the payment is not recorded against the reservation.

Underlying message on the reservation's Events tab: "Unexpected Lightspeed sale status '<status>' on sale <sale id> - payment not ingested."

Why it happens

Lightspeed X returned a sale status value BRM's integration doesn't currently handle — either a genuinely unusual status, or a sale in an intermediate state BRM doesn't expect at that point in its lifecycle. This is a newer, less common message than the general LSX001 API error.

How to fix it

1. Open the sale directly in Lightspeed and check what actually happened — was it completed, voided, refunded, still open?
2. If Lightspeed shows the sale as genuinely paid/completed, reconcile it manually in BRM — record the payment against the reservation yourself so the two systems agree.
3. Note the exact status text from the Events tab entry — it's the key detail support needs.

Still stuck?

Contact support with the reservation reference, the sale id, and the exact status text shown on the Events tab. We may need to add handling for that specific status.