Lightspeed
+
BigCommerce
Point of Sale + Ecommerce Platforms

Lightspeed BigCommerce Integration

Nventory syncs products, inventory, and orders between Lightspeed POS and BigCommerce across all retail locations. Multi-storefront and B2B inventory allocation are supported at scale.

5 data entities synced at enterprise scale across Lightspeed locations and BigCommerce storefronts
Lightspeed POS BigCommerce syncLightspeed BigCommerce inventoryenterprise omnichannel POSBigCommerce retail integration
Lightspeed
NV
BigCommerce

Sync Matrix

5 data entities in the sync matrix — 2 bidirectional, 3 one-way. Tap any row for details.

Good to Know

Platform restrictions outside any integration tool's control

Customer profiles and loyalty data

Customer databases and loyalty program data cannot be synced between POS and ecommerce platforms through Nventory.

Gift card balances

Gift cards and store credit balances are platform-specific and cannot be synced between POS and ecommerce systems.

Lightspeed eCom storefront content

Lightspeed bundles its own eCom platform with some plans. Storefront pages, themes, and domains on Lightspeed eCom are not synced to BigCommerce.

BigCommerce native checkout customizations

BigCommerce checkout scripts, payment gateway configurations, and checkout page customizations are platform-specific and outside the sync scope.

Serialized inventory display on BigCommerce

Lightspeed supports serial number tracking per unit, but BigCommerce has no native serial number field. Serial data is tracked in Nventory but not surfaced on BigCommerce product pages.

Things to Consider

Platform-specific details and how they affect this integration.

Challenge

Lightspeed includes its own eCom platform bundled with Retail plans. Running Lightspeed eCom alongside BigCommerce creates duplicate online storefronts competing for the same stock and potentially confusing customers with different URLs and experiences.

Nventory's Approach

Nventory recommends disabling or deprioritizing Lightspeed eCom when BigCommerce is the primary online channel. If both must coexist, Nventory partitions inventory between the two storefronts with configurable allocation rules.

Who Uses Lightspeed BigCommerce Integration

Common scenarios for connecting Lightspeed and BigCommerce.

Multi-location sporting goods retailer with Lightspeed POS and BigCommerce for wholesale and DTC
Industrial supply company running B2B on BigCommerce and retail counters on Lightspeed
Fashion brand with multiple Lightspeed boutiques and a BigCommerce multi-storefront setup for global ecommerce
Outdoor recreation retailer managing a large catalog across five Lightspeed stores and BigCommerce online
Office supply chain using Lightspeed for retail and BigCommerce for corporate purchasing portal

How It Works

Nventory sits between your platforms and keeps everything in sync.

Lightspeed
Lightspeed
NV
Nventory
BigCommerce
BigCommerce
1

Connect Lightspeed and BigCommerce

Authenticate both platforms in Nventory. Import product catalogs and begin the SKU mapping process across all Lightspeed locations and BigCommerce storefronts.

2

Configure Multi-Location Mapping

Map each Lightspeed retail location to BigCommerce inventory sources. Define which locations can fulfill online orders and set priority rankings for order routing.

3

Set Allocation Rules by Channel

Reserve minimum stock for retail walk-ins, wholesale BigCommerce orders, and DTC BigCommerce orders separately. Nventory enforces these rules in real time.

4

Enable Fulfillment Workflows

Route BigCommerce orders to Lightspeed locations based on proximity, stock availability, and fulfillment capacity. Staff process orders in their Lightspeed workflow.

5

Launch Reporting and Optimization

Use Nventory's analytics to monitor channel performance, stock velocity, and fulfillment efficiency. Identify underperforming locations and optimize allocation rules.

Frequently Asked Questions

Yes. Nventory uses intelligent batching and queuing to stay within Lightspeed and BigCommerce API limits while maintaining near-real-time sync. For enterprise volumes, Nventory negotiates elevated API limits on your behalf.

Absolutely. Nventory maps inventory to individual BigCommerce storefronts so you can control stock availability per storefront while keeping a unified view of total inventory across Lightspeed.

Nventory syncs inventory quantities and product data but respects BigCommerce's native price list and customer group pricing for B2B. Lightspeed retail pricing is managed independently.

Receive inventory into Lightspeed as you normally do. Nventory detects the stock increase and propagates it to BigCommerce in real time. Bulk receiving events are processed as a batch to avoid sync flooding.

Nventory connects to every Lightspeed retail location, including warehouse and back-of-house stock rooms, and maps each one to a BigCommerce inventory source. When staff scan a barcode or process a sale on any Lightspeed iPad register, that location's count updates independently on BigCommerce, giving your online storefronts accurate per-location availability for ship-from-store and local pickup workflows.

Yes. Every Lightspeed POS transaction, whether processed via barcode scan on the iPad register, a manual quantity adjustment in the back office, or a return at the counter, triggers Nventory to push the updated count to BigCommerce in real time. Even sales made during Lightspeed's offline mode queue locally and sync to BigCommerce the moment the device reconnects.

Verify that every Lightspeed outlet (including back-of-house stock rooms and warehouses) is explicitly mapped to a BigCommerce inventory source in Nventory's location settings — unmapped outlets are silently excluded from the sync. BigCommerce's inventory system requires each product to have inventory tracking enabled at the variant level, so products set to 'do not track' on BigCommerce will ignore incoming stock updates. Finally, check Nventory's per-location sync rules to confirm each outlet is set to push rather than pull, and that no location-level filters are accidentally excluding the products in question.