Introduction to Heartland
Heartland Retail is a web-based point of sale and retail management platform designed to help specialty and multi-location retailers manage sales, inventory, and customer data.
Used by specialty retailers and boutique chains that need a cloud-based POS with strong inventory visibility
Popular with businesses managing multiple store locations from a centralized system
Connecting Heartland Retail to iPaaS.com enables sales, product, and customer data to sync automatically with your ERP and eCommerce platforms, keeping in-store, online, and back-office operations aligned
API Version Support
The integration works with the Heartland Retail API, reached at Heartland's API host with the credentials configured in your subscription's connection settings. See the Heartland Connections and Settings and Heartland API Endpoints articles for details.
Data Flows
The table below summarizes the data the integration can move between iPaaS.com and Heartland, and in which direction. Arrows show the direction of transfer:
→ iPaaS.com writes the data to Heartland
← iPaaS.com reads the data from Heartland
←→ the data can move in both directions
Allow Initialization? indicates whether that data can be bulk-loaded from Heartland when a subscription first connects. Whether a given flow is enabled, and in which direction, is configured per subscription during implementation.
iPaaS.com | Direction | Heartland | Allow Initialization? |
Product | ←→ | Product | |
Product Inventory | ← | Inventory | |
Inventory Adjustment | → | Inventory Adjustment | |
Customer | ←→ | Customer | |
Location | ← | Location | ✔️ |
Payment Method | ← | Payment Method | ✔️ |
Shipping Method | ← | Shipping Method | ✔️ |
Gift Card | ← | Gift Card | |
Sales Order | ←→ | Sales Order | |
Invoice | ←→ | Invoice | |
Ticket | ←→ | Ticket | |
Transaction Status | ← | Transaction Status |
Products, customers, sales orders, invoices, and point-of-sale tickets flow in both directions between iPaaS.com and Heartland. Inventory levels and transaction status are captured from Heartland, inventory adjustments are written back, and locations, payment methods, shipping methods, and gift cards are captured from Heartland. Each transaction carries its line items, addresses, taxes, payments, and discounts.
Versions and Release Notes
The integration follows its own version numbers. The current version is 1.0.
Version | Release Notes |
1.0 (current) | Initial release: bi-directional products (with variants and options), customers, sales orders, invoices, and point-of-sale tickets; inventory capture and inventory adjustments; and gift card, transaction status, and reference-data capture. |
Features by Release
The capabilities below are grouped by the version in which they became available. For the current behavior and any limitations of a given feature, see the linked reference articles and the Heartland Known Limitations article.
Version 1.0 (current) — Retail POS, inventory, and transactions
Products: products captured from Heartland, and written to it, with their variants, options, and related products.
Inventory: product and variant stock levels captured from Heartland, with inventory adjustments written back.
Customers: customers captured from Heartland, and written to it, with their addresses.
Sales orders: sales orders captured from Heartland, and written to it.
Invoices: invoices captured from Heartland, and written to it.
Point-of-sale tickets: tickets captured from Heartland, and written to it, with transaction status updates.
Gift cards: gift cards and gift-card activity captured from Heartland.
Reference data: locations, payment methods, and shipping methods.