Skip to main content
storekit queues every online order for Lightspeed as soon as it’s placed — you don’t need to accept it first. Pre-orders can be held back with Hold pre-orders until closer to the time in Orders → Edit.

How an Order Reaches Lightspeed

Every order also carries the customer’s name, email and phone number, the items with their SKUs and modifiers, and the generated order note. The tip travels on the payment line, so cash orders (sent unpaid) and orders added to an open bill carry no tip.
The collection code Lightspeed shows is the storekit order code — Lightspeed limits it to 8 characters.

Account Profile Routing

In Orders → Edit on Stores → your store → Settings → Integrations → Lightspeed K-Series you map each fulfillment type to a Lightspeed account profile: Pickup account profile, Delivery account profile and In store account profile. The Add to bill account profile sits in Dine-in & pay at table → Edit. Each dropdown lists the account profiles from your Lightspeed business location. If a field is left unset, storekit sends the account profile code storekit, which must exist in Lightspeed. When an order goes onto an existing bill, the Add to bill account profile takes priority over the fulfillment-type profile.

Payment, Discounts and Charges

  • Payment method — in Orders → Edit, the Lightspeed payment method the order’s payment is recorded against. Defaults to STOREKIT when nothing is selected.
  • Send cash payments as paid — in Orders → Edit, off by default: cash orders are sent with no payment applied, so staff see an open balance and settle it when the customer pays. Turn it on to send cash orders as already paid. Card and other prepaid orders are always sent as paid. See cash and pay-on-collection orders.
  • Discount Product Code (SKU) — in Charges & discounts → Edit, used for a negative discount line item. A discount code with a POS ID applies a native Lightspeed discount instead — see linking storekit discount codes to Lightspeed discounts. Free-delivery discounts add no discount line at all, because the £0 delivery line already reflects the waived fee.
  • Service Charge Product Code (SKU) — in Charges & discounts → Edit, line item used for the order’s service charge.
  • Delivery Product Code (SKU) — in Charges & discounts → Edit, line item used for the delivery fee on delivery orders.
  • Don’t send customer email to Lightspeed — in Orders → Edit, sends an empty email address, for venues that don’t want customer emails in the POS. Name and phone number are still sent.
These product codes must exist in your Lightspeed menu. A missing SKU makes Lightspeed reject the whole order.
On in-store orders, storekit also sends each item’s course number so Lightspeed can fire the order by course.

Linking storekit Discount Codes to Lightspeed Discounts

Each storekit discount code reaches Lightspeed in one of two ways, depending on its POS ID. With a POS ID, storekit sends the code’s POS ID as a native Lightspeed discount on every item in the order and adds no discount line. The discount shows in Lightspeed’s discount reports under that Lightspeed discount.
  1. In Lightspeed, note the code of the discount the storekit code should report under.
  2. In storekit, go to Marketing → Discounts and click the discount code’s row.
  3. Enter the Lightspeed discount code in POS ID (below Description) and click Save in the Unsaved changes bar.
Several storekit codes can share one POS ID — for example THANKSANA and THANKSTOM both set to the same Lightspeed discount — so they all report under that single Lightspeed discount.
Once a code has a POS ID, Lightspeed applies the value configured on its own discount, not the storekit value. The customer still pays the storekit price, so if the two are set up differently the Lightspeed order won’t match — a £1.88 storekit discount linked to a Lightspeed discount set up with a different value can show as a much larger discount in Lightspeed. Give the Lightspeed discount the same type and value as every storekit code linked to it.
Without a POS ID, storekit adds the discount amount as a separate line item, using the product set in Discount Product Code (SKU) under Charges & discounts → Edit (STOREKIT_DISCOUNT if left empty). Lightspeed treats that line as a product, not a discount: it appears in product sales for that product, and not in Lightspeed’s discount reports.
POS ID only shows on the discount form once it’s enabled for your account. If you don’t see it, contact support. There is no setting in the Lightspeed K-Series integration that switches all discounts to native Lightspeed discounts — each code is linked through its own POS ID.

Order Notes

Order note template — in Orders → Edit → Show advanced — controls the note sent with each order (up to 250 characters). Click Insert Variable to see the available variables, and Preview to check the result with sample data. storekit appends the collection or delivery time to the note automatically.

Pre-Order Buffering

By default a pre-order is sent to Lightspeed straight away, which can clutter the kitchen hours ahead of time. To delay it:
  1. In Orders → Edit, turn on Hold pre-orders until closer to the time.
  2. Optionally set Minutes before pickup or delivery (0–720) — the order is injected that many minutes before the requested fulfillment time.
With it on and the minutes left empty, storekit uses the store’s normal prep-time calculation to decide when to inject. Orders without a requested time are never buffered.
15–30 minutes is a good starting point for a busy kitchen.

Add to Bill

For in-store orders on tables in an area that accepts pay-at-table, Add to bill batching for all orders in Dine-in & pay at table → Edit sends every order onto the table’s open Lightspeed bill rather than creating a separate order. The Add to bill account profile is used, and the payment is left off the order because it’s settled against the bill. See Pay at Table.

When an Order Fails

Lightspeed reports the outcome of each order by webhook:
  • Success — the order is marked Accepted in storekit and the Lightspeed receipt reference is stored.
  • Failure — storekit re-queues the order and retries. An immediate order is marked Failed after 5 attempts; a pre-order keeps retrying until its requested time is close (at most 100 attempts), then is marked Failed. Once the order is Failed, the failure reason is stored against it, the store is emailed, and a failed-order ticket prints if the store has printers. Some failures are not retried and are marked Failed on the first attempt: orders being added to an existing bill, an item that could not be added, an item not configured for online orders, and a closed Lightspeed account.
  • If the failure reason is a sales restriction, storekit also snoozes the affected items once the order is finally Failed — see Stock & Availability.
storekit also gives Lightspeed a deadline for accepting the order that scales with how far away a pre-order is: one minute for immediate orders, up to six hours for orders more than a week out. If Lightspeed rejects storekit’s access (a 403), the order fails with “Our access to your Lightspeed account has been disabled, please re-enable the integration user or speak to support” — see Troubleshooting.

The Failed-Order Email

The email is sent once, when the order is finally marked Failed — not on each retry — with the subject Lightspeed Issue: Order #<order ID> for store: <store name> and the failure reason in the body. It goes to the store’s Email address list on Stores → your store → Settings → General (the first address as the recipient, the rest as blind copies), with a copy kept by storekit. No other merchant address gets it: the email you log in to the dashboard with receives nothing unless it is in that list. If that list is empty, no email is sent. See I’m not getting failed-order emails. Any other failure reason is Lightspeed’s own message, stored word for word. The three you’re most likely to see are “Not processed before validity ended” (the Active Device was offline — see Orders Failing: Till Offline), “…one of the items in the order has a Disconnected status in Lightspeed” (Lightspeed does not treat an item in the order as active on the location — see Troubleshooting) and “Failed to sync order Validation failed for method … placeToGoOrder …” on the order’s timeline (Lightspeed rejected the order’s contents before accepting it, so the retry and email rules above never start — see Troubleshooting).

Next Steps

Stock & Availability

Keep sold-out items off the menu

Pay at Table

Bills, payments and add-to-bill