Lightspeed Retail (X Series) as a Source
Summary
Lightspeed Retail (X Series) is a retail POS and inventory management platform. As a Flxpoint source it connects using either a Personal Token or an OAuth 2.0 authorization tied to your Lightspeed Retail domain. The integration runs Get Inventory (Primary and Secondary) to sync your catalog, pricing and stock, and Send Fulfillment Requests to record store-fulfilled orders back in Lightspeed as a sale. For setup guidance and mapping details, contact support@flxpoint.com.
Lightspeed Retail (X Series) supports two connection types: Personal Token or OAuth 2.0. Add a Lightspeed Retail (X Series) source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values (or authorize via OAuth), then Test Connection → Save Connection.
| Field | What to enter |
|---|---|
Domain PrefixRequired | Your Lightspeed Retail (X Series) store's subdomain prefix, as shown in your store's web address. |
Personal TokenRequired | A Personal Token generated from your Lightspeed Retail (X Series) admin account, granting Flxpoint API access to your store. |
| Field | What to enter |
|---|---|
Domain PrefixRequired | Your Lightspeed Retail (X Series) store's subdomain prefix. |
Authorize with LightspeedRequired | Click Connect and log in to your Lightspeed Retail (X Series) account to authorize Flxpoint. Flxpoint manages token refresh automatically after authorization. |
support@flxpoint.com.The Lightspeed Retail (X Series) help article is under review: contact support for setup guidance
The dedicated help article for Lightspeed Retail (X Series) as a source is not yet published. For full setup instructions (including connection credentials, which operations are available, and mapping template guidance) email support@flxpoint.com with your account details.
Lightspeed Retail credentials are typically an API Key or OAuth token from your Lightspeed account
Lightspeed Retail (X Series) uses an API-based connection. Credentials are typically an API Key or OAuth access token from your Lightspeed Retail admin. Contact Flxpoint Support at support@flxpoint.com to confirm the exact credential fields and obtain setup instructions while the article is being finalized.
GIP daily for full catalog; GIS for delta updates: Archive on one job only
Once configured, run Get Inventory Primary daily for a full catalog import from Lightspeed Retail. Use Get Inventory Secondary for more frequent price/quantity refreshes. Enable Archive/Un-Archive on one job only to avoid conflicting inventory states.
Test a single manual order before enabling automatic Send FR scheduling
Before enabling automatic order sending, run one manual Fulfillment Request and verify receipt in Lightspeed Retail. Confirm the order appears correctly on the Lightspeed side before enabling automatic scheduling.
OAuth scopes and connection requirements
OAuth connections require products:read, inventory:read, customers:read/write, and sales:write scopes. Ensure your Lightspeed store has a Tax ID, User ID, and Register ID configured to enable full order creation flows. If a refresh token becomes unavailable, Flxpoint will automatically fall back to your Personal Token connection.
App approval and store limits
Lightspeed requires app approval for full production use. If the Flxpoint app status is Not Approved in your Lightspeed account, the integration is limited to a maximum of 30 stores. New signups default to the OAuth connection type, while existing users can rename their legacy connection to Personal Token for clarity.
Imports the full Lightspeed Retail catalog: run once daily.
| Field | Maps To: Notes |
|---|---|
| Product ID | → Product / Variant → Supplier Variant ID. Required. Primary identifier for the catalog item. |
| Product & Variant Images | → Product / Variant → Images. Both product-level and variant-level images are imported. |
| Product Attributes | → Product → Attributes. Name/value attribute pairs from Lightspeed. |
| Product & Variant Options | → Product / Variant → Options. Variant option name/value pairs (e.g. size, color). |
| SKU, Title, Price, Description | → Standard catalog fields. Mapped via Flxpoint's configurable field mapping at connection setup. |
A lighter, more frequent refresh of pricing and quantity by SKU.
| Field | Maps To: Notes |
|---|---|
| SKU | → Inventory Variant → SKU. Required. Primary identifier, matched to the existing catalog item. |
| Price / Quantity | → Pricing & Inventory. Mapped via Flxpoint's configurable field mapping. Full catalog fields (title, images, attributes) come from Get Inventory Primary: run Primary daily and Secondary more frequently. |
Sends store-fulfilled orders to Lightspeed Retail as a sale.
| Source Field | Maps To (Lightspeed Retail): Notes |
|---|---|
| Fulfillment Request line → SKU | → Sale Line Item → Product. Required. Matched to the Lightspeed product via Supplier Variant ID. |
| Fulfillment Request line → Quantity | → Sale Line Item → Quantity. Required. Units sold on the line. |
| Order → Customer | → Sale → Customer. Matched to an existing Lightspeed customer by name/email when available. |
| Order → Payment Amount | → Sale → Payment. Recorded as a payment on the sale. |
| Order → Shipping / Billing Address | → Sale → Addresses. Passed through on the sale record. |
Looking for setup help: the doc is under review
Fulfillment requests failing due to invalid adjustment fields?
Tax not appearing correctly on Lightspeed sales?
Errors when syncing shipping costs?
Fulfillment requests failing with legacy field errors?
Personal Token or OAuth 2.0: which should I use?
How should the inventory operations be scheduled?
Where can I get full setup instructions?
support@flxpoint.com with your account details and the operations you need to configure, and run one manual test order before enabling automatic Send FR scheduling.