Lightspeed Errors

LSI001 - General Lightspeed API Error

This is a general Lightspeed error (not related to BRM/RSM).

If you encounter this error, the best approach is to use the BRM screenshot button to capture a screenshot and send it to support for assistance.

LSI002 - User XYZ Not Linked to Lightspeed

For each of your BRM accounts to integrate with Lightspeed, it must be properly linked/connected.

If you see this error, it means the specific user account is not linked to Lightspeed. This typically occurs when trying to add a Lightspeed-> transaction to a reservation.

To resolve this, click the 'Connect Lightspeed' button to establish the connection in Settings->Integrations->Lightspeed.

LSI004 - Lightspeed Invalid Foreign Keys for Customer

This error occurs when you attempt to addTansaction to a reservation that’s linked to a customer that doesn't exist in Lightspeed

.

When transferring a transaction to Lightspeed, a customer record can be sent along with it. However, if you try to send a customer ID that Lightspeed doesn’t recognize, you’ll receive this error.

Even if you archive a customer in Lightspeed, you won’t see this error — Lightspeed allows transactions to be processed against archived customers. The issue typically arises when customers are merged in Lightspeed. When you merge two customer records, one of the original customer IDs is permanently deleted, which causes this error.

How to Resolve It

To fix this, you need to ensure the correct customer ID in BRM/RSM points to the right customer in Lightspeed.

Here’s what to do:

1. Locate the customer record in BRM/RSM.

2. Update the customer ID to the correct Lightspeed ID (the new one after the merge).

3. Save the changes.

Example Scenario:

Imagine you have two Fred Jones records in Lightspeed:

• Fred Jones - ID61

• Fred Jones - ID205

In BRM/RSM, you have a Fred Jones account linked to Lightspeed’s customer ID61. After tidying up your customer records, you merge the two Fred Jones records in Lightspeed.

This action permanently deletes the old customer ID (ID61), leaving you with just ID205. As a result, you’ll need to update your Fred Jones record in BRM/RSM to point to the new Lightspeed ID (ID205). By updating the ID in BRM/RSM to match the new customer ID in Lightspeed, the error will be resolved.

LSI005 - Lightspeed Invalid Foreign Keys for Employee: x

Occasionally, when setting up your Lightspeed integration, you may encounter this error when trying to "Add Transaction" in BRM.

This error occurs because Lightspeed requires a valid Employee ID to process inbound data from external applications like BRM. By default, we use user ID 1 for this purpose. However, in some cases, this user may not exist in your Lightspeed database, or you might be linked to a Lightspeed user ID that has been removed.

How to Resolve It

To resolve this issue, you need to provide a valid Lightspeed Employee ID. This ensures that when the connection is made, the transaction will appear under the correct user ID in Lightspeed.

Steps to Find the Correct Employee ID:

1. Choose a Lightspeed employee account you wish to use for handling inbound connections.

2. Navigate to Settings > Employees in Lightspeed.

3. Identify the appropriate employee ID.

4. Connect the Lightspeed employee ID to your BRM user account.

This will ensure that BRM transactions are correctly linked to the chosen employee in Lightspeed.

For further clarity, please refer to the diagram below:

When you log in to BRM, you use your account, for example:

[email protected]

In the BRM user database, we associate a foreign key of 2 with this BRM user account.

Next, when you add a transaction to send over to Lightspeed, BRM looks up the foreign key from this account and instructs Lightspeed to process the transaction (as a customer quote) using the employee account with ID 2 (which, in this example, is JOE BLOGGS in Lightspeed).

Lightspeed then attempts to find the employee account with ID 2. If it can’t find this employee, you will encounter the error described in this article.

LSI008 - Lightspeed Missing EAN

This error occurs when the Lightspeed configuration is either incomplete or has become invalid.

In order to create a sales order in Lightspeed, BRM requires a product code that matches the rental inventory in Lightspeed. The EAN (European Article Number) is a SKU or product code that is used to identify items, but it does not manage stock levels—those are handled within BRM.

To resolve this issue, refer to the Lightspeed configuration article for instructions on how to properly set up and fix this configuration.

LSI009 - Lightspeed Employee Locked Out

This is an error that is happening in the Lightspeed shop.  (not actually a BRM error)

When BRM talks to Lightspeed (e.g. to pull in customers and transactions) it must use one of your user's accounts on Lightspeed.  This account is mapped to your BRM user.  It must be active!

The exact message is "Employee can't login. Verify that it isn't locked out or archived". If you are uncertain which employee id is linked to your BRM login, then check against that user account - and it will tell you which Lightspeed user ID it is linked to:

Settings > Users

LSI009 - Lightspeed Employee Locked Out

This error occurs within the Lightspeed shop and is not a BRM error.

When BRM communicates with Lightspeed (e.g., to pull in customers and transactions), it uses one of your Lightspeed user accounts, which is mapped to your BRM user account. The Lightspeed user account must be active for the connection to work properly.

The specific error message you'll see is: "Employee can't login. Verify that it isn't locked out or archived."

If you're unsure which Lightspeed employee ID is linked to your BRM login, you can easily verify it by checking the user account settings in BRM. This will show you the corresponding Lightspeed user ID.

To check:

1. Go to Settings > Users in BRM.

2. Find the linked Lightspeed user ID for your account.
   
   

Make sure the employee account is active and not locked out or archived in Lightspeed.