All Collections
POS Integrations
Heartland: Features and Limitations
Heartland: Features and Limitations
Sam Fielding avatar
Written by Sam Fielding
Updated today

As with each of our POS integrations, there are features and limitations that exist based on the integration itself or the POS software. We have noted some of the important ones to know when setting up a Heartland integration with Deliverect.


⚠️ Price Overwrites are supported, meaning that the delivery prices do not need to come from the POS and the delivery menu prices can be managed directly on Deliverect's menu manager. Note that for the Heartland POS to successfully receive these price-adjusted orders with the integration, a Price Rule will need to be created within the POS system as outlined in this guide here.

⚠️ Nested modifiers can be synced in from the POS

⚠️ Heartland does not have a way for stores to set up sound notifications on the POS for incoming orders. The only way you can receive notifications is to use a separate KDS screen and enable Notifications on the KDS. You can also incorporate a separate tablet to run the DMA to receive notifications each time a new order is received through the integration.

⚠️ All orders will come in under the “Online Order User” and cannot be assigned to a server. A staff member will not be able to pick up the ticket without having to have a manager present to transfer checks (if security is set)

⚠️ Meal deals are sent over to the POS as individual items.

⚠️ Ingredients can have modifier size prices.

⚠️ Support for credit and cash tender types (but not debit).

⚠️ Items within the POS can have required ingredients/items, but the API does not support syncing that information. When an order is placed the POS does validate if all required ingredients/items are included and it will cause orders to fail if a required item is not selected. The workaround is to build their menu in Deliverect and ensure all the required choices are mandatory. This will allow orders to pass successfully as the POS will receive all expected ingredients/items.

⚠️ Items must be listed as available online on Heartland, and belong to a group and class that is available online. If not the item will not sync to Deliverect.

⚠️ The carryout settings within Online Ordering do need to be enabled and configured with opening hours set and menu selected in order to receive orders. You do not have to have an online order website with Heartland for this to work.


⛔️ Heartland's API does not support the POS' ability to configure Context items.(Note: Context Items are variable changes that can be performed on a menu Item. For example, Extra, On Side, On Top, Substitute.)

⛔️ Order Notes do not print on receipt and no support for note templates

⛔️ No support for syncing product images from the POS to Deliverect. Images can be added to the menu manually from the Deliverect menu manager as per this guide.

⛔️ No support for syncing tax-inclusive products.

⛔️ No support for syncing meal deals, modifiers in meal deals, upsells, variant pricing

⛔️ No support for orders with internal products.

⛔️ No support for multiple brands.

⛔️ No support for rounding taxes.

⛔️ No support for updating order prep time.

⛔️ No support for driver updates for self-delivery.

Given the above features and limitations, a test order is placed during the initial set-up/onboarding to confirm the integration connection and order injection is successful to the POS. Our team can assist with placing a test order, but note that we do not place test orders for every single item on the delivery menu. Test orders can be placed directly from the Deliverect portal as per this guide here: How to Place a Test Order on Deliverect.

Contact our support team if you encounter issues while placing a test order.

Did this answer your question?