Built for the way Heartland Retail works
Heartland Retail uses an item-grid model for variant products where each style has a grid of color and size combinations. Vendee Pro reads item grids correctly when pulling catalog from Heartland, attaching each child item to its grid parent. When publishing a variant product from Vendee Pro to Heartland, each variant is pushed as its own Heartland item (aggregated-simple style) because Heartland’s public API does not currently support creating new item grids. Updates to existing grids are honored; new grids are not synthesized.
What syncs
- Items. Products from Vendee Pro land in Heartland as items. Variant products create one item per variant. Simple products create a single item.
- Vendors. Vendor records sync from Heartland so Vendee Pro’s vendor list stays in step.
- Locations. Each Heartland Retail location maps to a Vendee Pro location.
- Inventory. Inventory changes from Vendee Pro propagate to Heartland as adjustment sets, the native concept Heartland uses for stock deltas.
- Sales. Sales pull every hour so reports stay current. Per-sale webhook delivery (
sales_transaction_completed) is also supported.
Adjustment sets, not raw on-hand overwrites
Heartland Retail’s adjustment-set model is the right way to push inventory changes: it preserves the audit trail in their system, attributes the change to a reason and a user, and keeps the count accurate even when other adjustments are happening concurrently. Vendee Pro pushes inventory changes as proper adjustment sets, not as raw count overwrites that would clobber concurrent activity.
Real-time webhooks for item and location changes
When an item, item grid, or location changes in Heartland Retail, Vendee Pro receives a webhook (item_created, item_updated, item_grid_updated, location_updated) and dispatches a targeted re-pull of the changed record so local maps stay in sync. That keeps catalog data in step automatically, without nightly polling or manual refresh.
Multi-location ready
If you run multiple Heartland Retail locations, Vendee Pro handles them as first-class entities. POs can target multiple locations in a single document. Inventory is tracked per variant per location. Transfers between locations are clean ship/receive flows. Read the multi-store solution →
Privacy and data handling
The integration accesses the catalog, inventory, and sales data needed for buying and reporting. Customer-level data is not part of the standard integration scope. Read our Privacy Policy for the full disclosure.
Frequently asked questions
Does Vendee Pro support Heartland Retail’s style/color/size grid?
For reading: yes. Vendee Pro pulls item grids and child items, attaches children to their grid parent, and preserves the variant structure. For writing new variant products from Vendee Pro to Heartland: each variant is pushed as its own Heartland item because Heartland’s public API does not currently expose a schema for creating new item grids. Updates to existing grids are supported.
How are partial receipts handled?
Partial PO receipts in Vendee Pro generate adjustment sets in Heartland Retail with the received quantities at the receiving location. Subsequent receipts on the same PO produce additional adjustment sets.
Can I publish products from Vendee Pro to Heartland?
Yes. Simple products push as a single Heartland item. Variant products push as one item per variant, with cost, price, vendor, and location-scoped inventory intact.
What happens if Heartland and Vendee Pro disagree on a count?
The system flags discrepancies in the integration log. Heartland Retail is treated as the system of record for live on-hand at retail locations; Vendee Pro reconciles to it on inbound webhooks.
Connect your Heartland Retail store.
Sign up free. Upgrade to Premium to connect Heartland Retail and unify buying with selling.
Start Free