Does the BisTrack API cost extra?

It's a separately licensed Epicor product; Automation Studio customers, for example, must also be BisTrack API users. Epicor doesn't publish pricing, so confirm cost and scope with your account rep before planning an integration.

Is the BisTrack API REST?

Epicor doesn't say publicly. The pages describe authenticated, encrypted access and name the platform BisTrack Web Browser and API, but the protocol details come with the product documentation after you engage Epicor.

Can you query the BisTrack database directly?

For reads, yes. Smart Views are SQL-defined by design, and Epicor's release notes give integrators rules for SQL that touches the database, so this is an acknowledged surface, not a hack. Writes should go through the API or the eBusiness and EDI import paths so BisTrack's business logic stays in control.

Can you integrate with on-premise BisTrack?

Yes; Automation Studio and the API support cloud and on-prem. Factor in the sunset schedule though: BisTrack Desktop's final feature release is 2026.2, tentatively December 2026, and the Web and API platform's final on-prem release is 2028.1.

ERP automation guide

BisTrack Integrations and API Guide

By Airdev. We build custom AI order entry for distributors running BisTrack: built to match your exact process, owned by you, with no per-order fees. This guide is what we've learned doing it.

BisTrack has three real integration surfaces. The main one is the BisTrack API, a separately licensed Epicor product whose endpoints cover order and quote pushes, customer and job site data, inventory and pricing by branch, dispatch, and a Smart View endpoint for SQL-defined data pulls. Alongside it sit the eBusiness module, BisTrack's native file-based order import path, and direct SQL against the underlying SQL Server database, a practice Epicor's own release notes acknowledge.

The working knowledge is thinner and more scattered than for Epicor's other ERPs, so knowing where things live matters as much as what exists.

The BisTrack API: what it covers

Epicor packages the API as a named product with its own page, and the documented endpoint groups cover more than you might expect:

Order and quote push. External platforms can push orders and quotes into BisTrack, payment details included.
Customer and contact data, including job sites and lien information (a very LBM touch).
Inventory, pricing, and product images by branch.
Delivery and dispatch data, aimed at telematics and routing integrations.
Financial data exchange and web store connectivity.
Document handling for receipts, confirmations, and proof of delivery.
The Smart View endpoint, which runs SQL-defined queries, so you can pull just about any dataset BisTrack holds.

API licensing and what Epicor doesn't publish

Epicor doesn't publish the technical spec or the price. The public pages say only that API interactions are authenticated and encrypted, and the licensing is its own product: Epicor's Automation Studio page notes that customers must also be BisTrack API users. Access runs through your Epicor account rep (third-party guidance says Epicor routes you to its product developers within a few days), so treat the API as a budget line and a lead-time item, and confirm it's in your contract before an integration plan depends on it.

eBusiness: the file-based import path

The eBusiness module is BisTrack's native file-based order intake. An integration drops files through the BisTrack FTP process within eBusiness, BisTrack polls for new documents every 30 seconds, and an operator opens Tools > eBusiness Browser and clicks Apply to create the sales order, or a quote if the import's Sales Type is set that way. Setup lives in BisTrack System Manager under eBusiness Setup. SaberisConnect, the main vendor-quote-to-order integration in the LBM world, moves its documents over exactly this path.

How to import orders into BisTrack, in depth

Direct SQL against the database

BisTrack runs on SQL Server, and Epicor treats direct SQL as a real integration surface: the release notes instruct integrators who write SQL that generates IDs to use the GetNewID stored procedures rather than touching system tables, and name the tables involved (OrderHeader, OrderLine, InvoiceHeader). Smart Views themselves are SQL-defined grids that users build and share, so SQL literacy is normal in BisTrack shops. Our advice is the standard one: read from the database as much as you like, but send writes through the API or the import paths so BisTrack's own logic stays in charge.

Automation Studio and the ecosystem

Epicor's official low-code option is Automation Studio, an iPaaS built on Workato with a couple thousand prebuilt connectors, which connects through the BisTrack API and works against cloud and on-prem BisTrack alike. Epicor's own named use cases include automated order submission from customer portals into the ERP. It's an extra cost, and it requires the API license.

Around it sits a small but real ecosystem: SaberisConnect for converting vendor quotes from window and door configurators into BisTrack orders, DCKAP for e-commerce and CRM sync, GPS Insight and Trimble for telematics and routing (Trimble's truck routing is embedded in BisTrack Web and BisTrack Delivery), and e-commerce integrations from several Magento and web-store specialists. Community knowledge lives at dbUG, the community-run BisTrack user group, rather than on Epicor's general forums, and there's no community-maintained API documentation like the GitHub docs P21 developers lean on. Plan on working directly with Epicor, and favor builders who have been inside BisTrack before.

What to build first

For most dealers the answer is order intake, because it's the highest-volume manual work: the emailed contractor POs that someone keys into Order Entry today. The API's order and quote push exists for exactly this, and a custom AI order entry system, built by Airdev, can sit in front of it to read those documents, match the lines against your items and that contractor's pricing, and stage draft orders in BisTrack for a person to review and post. Nothing posts unreviewed. The item and pricing matching you build for order intake is the same foundation a quoting workflow reuses later.

As of this writing, none of the usual order automation vendors (Conexiom, Endeavor, OrderPier) publish a BisTrack integration, and the Epicor-Conexiom partnership announced in July 2026 covers Prophet 21 and Eclipse, not BisTrack. For BisTrack shops the realistic route is custom work against the API. That's what we build: a system you own, matched to your process, with no per-order fees.

Frequently asked questions

Want this for your BisTrack?

Built around your exact process and your BisTrack. You own it, with no per-seat or per-order fees.

See how we build these systems