Push Orders

HubRise can push orders from different connected solutions directly into your Lightspeed Restaurant EPOS. You just need to connect Lightspeed Restaurant Bridge to HubRise for orders to be sent to your EPOS, with no additional configuration.

Information Sent to Lightspeed

Items and Options

Lightspeed Restaurant Bridge sends your EPOS the complete information about items and options, including name, EPOS ref code, quantity, and price.

Lightspeed Restaurant Bridge converts options with a ref code that starts with + to production instructions. Note that production instructions have no associated price. Adding a price in a connected app can cause price differences errors.

Every item on Lightspeed must have a ref code. Orders containing items with incorrect or missing ref codes are rejected by the EPOS. For this reason, when sending an order to the EPOS, Lightspeed Restaurant Bridge skips all items without a ref code.

Order Status

Lightspeed Restaurant Bridge creates an order in Lightspeed for each order from HubRise. The order status in HubRise is updated as follows:

received: When the order is created in Lightspeed.
rejected: If the order creation fails. The detailed error is available in the order custom fields, under the key epos.rejection_reason.cause.
awaiting_collection: When the order is marked ready in Lightspeed Kitchen.
completed: When the order is closed in Lightspeed, and if the bridge is configured to mark orders as completed. For more information, refer to the Order Statuses section of the Configuration page.

When an order is marked as cancelled in HubRise, Lightspeed Restaurant prints a message on the connected printer to indicate the cancellation. Depending on your settings, this message may also appear on the EPOS screen. The order remains in Lightspeed and is not deleted.

Payments

Zero, one, or multiple payments can be associated with an order.

Ref codes are used to map each payment in HubRise to the correct payment method in Lightspeed. Payments without a ref code are not sent to Lightspeed.

To find out how to check the payment methods ref codes available in your Lightspeed back office, see Map Ref Codes.

Handling Price Differences

When the total payment amount does not match the total price for the order as calculated by Lightspeed Restaurant, two scenarios might happen:

If the total payment amount is greater than the expected amount, Lightspeed rejects the order.
If the total payment amount is less than the expected amount, Lightspeed accepts the order. However, the order remains open for payment in the EPOS.

Swiss Market Rounding Rules

In the Swiss market, Lightspeed automatically rounds the order total to the nearest 5 cents, as required by Swiss law due to the absence of 1 and 2 cent coins.

To avoid discrepancies between the order total and payment amount, HubRise rounds payments using the same rules. For example, an order total of CHF 12.03 is rounded to CHF 12.05.

Service Types

Lightspeed Restaurant requires each service type (delivery, collection, eat-in) to be defined as an account profile.

The ref code of the service type is used to map the HubRise order to the correct account profile on Lightspeed.

To find out how to check the service types ref codes available in your Lightspeed back office, see Map Ref Codes.

Customer Information

Lightspeed Restaurant Bridge sends to Lightspeed the complete customer information, when available, including name, email address, and delivery address.

When customer information is not available, Lightspeed Restaurant Bridge creates an anonymous customer with Anonymous as the first name.

Order Modifications

When an order created in HubRise is modified in Lightspeed, Lightspeed Restaurant Bridge sends both item and payment changes to HubRise.

However, when an order is modified in HubRise, Lightspeed Restaurant Bridge only sends payment changes to Lightspeed. Support for pushing item changes to Lightspeed may be added in the future. If you need this feature, please contact us.

Orders created in Lightspeed can be pulled into HubRise only when they are closed. Modifications to these orders are not sent to HubRise. For more information, see Pull Orders.

Local Orders

Local orders in Lightspeed correspond to orders with a service type of eat-in in HubRise. When a table name is associated with a local order, it is handled slightly differently. Here are the specifics:

When a local order is created, the bridge checks if the table name is already associated with an open check in Lightspeed. If it is, the bridge will add the items and payments from the open check to the HubRise order.
If the table name is associated with an open check, but another HubRise order is already associated with that table name, the bridge will mark the new HubRise order as rejected.

The following scenarios illustrate how local orders can be used:

Booking solution: When the customer checks in, the booking solution creates an empty eat-in order in HubRise with the table name. When the customer orders and pays, the booking solution is informed of the order and payment details.
Table ordering app: When the customer places an order, the app creates an eat-in order in HubRise. The order can be either paid immediately via the app, or later via the app or at the counter. As mentioned in Order Modifications, the bridge does not currently support adding more items for the same table: the app must pay the order and create a new one.
Pay-at-the-table solution: When the customer is ready to pay, the app creates an empty eat-in order in HubRise with the table name. The bridge then fetches the open check for that table and adds the items in HubRise. The app is notified of the update, and it displays the items and payment amount to the customer. When the customer pays, the app sends the payment to HubRise, which closes the check in Lightspeed.

Feedback on this page