Epicor eCommerce integration, Epicor BisTrack integration, BisTrack eCommerce, Eagle eCommerce, ERP integration, lumber yard eCommerce
Epicor eCommerce integration for BisTrack and Eagle: 3 routes
October 29, 2026
Epicor eCommerce integration for BisTrack and Eagle dealers: Epicor's own store, middleware, or an LBM store that owns its connector. Who builds and fixes each.
Executive summary
The Epicor integration guides on page one are written for Prophet 21 and Kinetic. If you run BisTrack or Eagle, the real question is who owns the connector the day after launch.
Epicor eCommerce integration for a BisTrack or Eagle dealer runs one of three ways: Epicor's own commerce, a general platform joined by middleware or custom code, or a store built for lumber dealers with its own connector. Only the third makes the connector the store vendor's job. BigCommerce's two Epicor integration guides name only Prophet 21 and Kinetic.
I run ToolSwift, an online store and contractor portal built for lumber yards, hardware stores and building supply dealers. BisTrack and Eagle are two of the sixteen ERP and accounting systems we connect to, so I sell one of the three routes in this article. Read it with that in mind.
Every outside fact below comes from a vendor page, a vendor's documentation or a syndicated press release, read on October 29, 2026 and linked in the sources. Where a vendor makes a claim about another vendor's product, I say whose claim it is.
A connector is a promise about the future. Ask who keeps it.
Three routes connect BisTrack or Eagle to a store
There are three ways to put a BisTrack or Eagle catalog online, and they differ on one thing that matters more than features: who builds the connector between your ERP and your store, and who fixes it when either side changes.
The first route is Epicor's own commerce. For BisTrack, middleware vendor DCKAP says Epicor Commerce Connect includes a BisTrack connector and "only works with Magento-based stores." For Eagle, Supergood, a third-party API grader, says eCommerce is "effectively outsourced to Modern Retail's tiered packages."
The second route is a general platform, such as Shopify, BigCommerce or Adobe Commerce, joined to the ERP by middleware or by a developer writing to the Epicor API. You choose the store, then you choose who wires it.
The third route is a store built for this trade that ships with its own connector for your ERP. That is ToolSwift. The connector is ours to build and keep running.
Most Epicor integration guides skip BisTrack and Eagle
The Epicor integration content a dealer finds first is written for manufacturers and wholesale distributors on Prophet 21 and Kinetic, and it rarely mentions BisTrack or Eagle at all.
BigCommerce published two Epicor posts in October 2026, dated the 20th and the 26th in its feed. Both name only Kinetic and Prophet 21. The connector they promote, ShopHive by Silk Commerce, has two Shopify App Store listings: "ShopHive for Epicor P21," launched March 4, 2025, and "ShopHive for Epicor Kinetic," launched August 12, 2025. Each shows one plan at CA$558.08 a month and zero reviews. Neither mentions BisTrack or Eagle.
Jitterbit documents a Prophet 21 connector and a Kinetic connector verified against six Kinetic versions, from 10.2.500 to 12.1.100. The Jitterbit pages read name no BisTrack or Eagle connector. Celigo's Epicor page names no Epicor product at all. DCKAP lists Jitterbit and Celigo as BisTrack middleware options, but neither vendor's own pages read name a BisTrack or Eagle connector.
DCKAP is the one middleware vendor in this set that writes about BisTrack. Its integrations page lists Epicor Eagle as an ERP, but the named connectors there are for Prophet 21 and Eclipse. Eagle shows up in integrator content from Clarity Ventures, which says its Clarity Connect links Eagle to storefronts through an Epicor integration API.
Then there is Epicor Automation Studio, which DCKAP describes as Epicor's cloud workflow tool built on Workato. DCKAP's August 2026 comparison names Kinetic, Prophet 21 Cloud and Eclipse as examples and leaves BisTrack out; its July 2026 BisTrack post lists Automation Studio as a BisTrack option.
The finding: of the vendors' own pages read, three name a BisTrack integration (DCKAP, iWeb and ToolSwift) and two name an Eagle one (Clarity Ventures and ToolSwift), and ToolSwift is the only one that names its own connector for both.
Epicor's own commerce ties the store to the ERP roadmap
Taking the store your ERP vendor sells means your storefront moves when your ERP vendor moves, and Epicor has published a schedule for BisTrack.
On January 6, 2026, Epicor announced through Business Wire that future innovation for Kinetic, Prophet 21 and BisTrack moves exclusively to the Epicor Cloud. For BisTrack, the final on-premises Desktop release is 2026.2, tentatively December 2026, with Active Support through December 31, 2028. The final on-premises Web Browser and API release is 2028.1, tentatively July 2028, with Active Support through June 30, 2029. Epicor calls the migration program "Ascend with Epicor." The announcement does not mention Eagle.
So a BisTrack dealer running on-premises faces an ERP decision inside the next three years whatever store they pick. The question is how much of the store gets dragged into it.
On Epicor's route, DCKAP says the BisTrack connector comes inside Epicor Commerce Connect and that it does not support Shopify Plus, BigCommerce or other platforms. Your storefront platform is decided by the ERP vendor's connector. I covered what that store is like to run, tier by tier, in my BisTrack comparison, so I will not repeat it here.
For Eagle, the history matters. Supergood says Eagle traces back to Triad Systems and joined Epicor in the 2008 Activant acquisition, and describes a planned long-term move toward Propello and cloud Epicor. A hardware dealer on Eagle buying Epicor's commerce packages is betting that the packages follow wherever Eagle goes.
Middleware leaves the connector on your desk
On the second route you pick the store, and then you, your agency or your middleware vendor own the connector: its mapping, its schedule and every fix when BisTrack, Eagle or the store changes.
BisTrack gives you three doors, according to DCKAP. The eBusiness module imports XML, CSV or JSON files from an SFTP server or shared folder on a schedule, which is batch integration: prices and stock are as fresh as the last file. The BisTrack Web API gives REST access for real-time work, with Smart Views for custom datasets. Or a middleware product sits between the two systems. DCKAP says a self-integration starts with an Epicor account representative, and that Epicor takes about 2 to 3 days to share the integration details.
iWeb, a UK eCommerce agency, describes BisTrack integration through a licensed API, confirmed per installation: the release, deployment model, Smart View access and endpoint limits. iWeb says it built the Donaldson Group site on Adobe Commerce, connected to BisTrack, in 5 months.
Eagle is narrower. Supergood says "Eagle has no public API." A licensed Eagle API is requested through Epicor account management or a certified VAR, with no public developer portal or sandbox, and Epicor's public API documentation covers Kinetic and Prophet 21. Supergood lists the surfaces an integrator has to choose between: Eagle for Windows, Eagle Browser, Eagle Mobile, ODBC and Compass exports.
Time and cost are thin on this route. BigCommerce's own comparison rates deployment at weeks for ShopHive, weeks to months for iPaaS and months for custom middleware, with cost rated low to high and no dollar figures. No Epicor, Celigo or Jitterbit page read states a price or a timeline for a BisTrack or Eagle storefront integration. DCKAP says middleware usually carries subscription fees and custom builds need ongoing maintenance.
A store built for LBM owns its BisTrack and Eagle connector
On ToolSwift, BisTrack and Eagle are named connectors that we built and maintain, so connecting your ERP is configuration our team does during onboarding rather than a project you staff.
What flows between BisTrack or Eagle and ToolSwift
Three things move. Orders placed in ToolSwift, from the retail storefront, the contractor dashboard or the branded app, sync to your ERP. Customer pricing and stock levels come from your ERP. Invoices and payments stay in sync, so your books match.
Where the ERP supports it, pricing and inventory sync in real time. Customer accounts, credit limits and net terms flow through from your system, so a contractor sees their real available credit in the dashboard, and checkout enforces each account's credit limit automatically. Nobody at the counter has to catch an over-limit order by hand.
That matters more in this trade than in most. A lumber yard's price is per account and often per quantity, stock is per branch, and half the orders go on account. A store that shows the right shelf price but the wrong contractor price is worse than no store, because the contractor calls to check and stops trusting the screen.
Who does the work
Our team does the setup. You tell us what you run: your ERP, accounting system, payment gateway and carriers. We connect and map the systems, so your staff do not have to. Then the data flows, and the counter and the online store work from the same records.
BisTrack and Eagle are already on our list, alongside Prophet 21 and Eclipse from Epicor, Spruce and Deacom from ECI, Agility and Frameworks from DMSi, and Paladin, Genetiq, Sandbox ERP, Profit Master, PRISM, Ogasys/Acceo, QuickBooks and NetSuite. If you run something that is not on the list, we build the connector the same way and then we own it. A ToolSwift launch is measured in weeks, with one team running the integration, the storefront design, the catalog and the training.
Your storefront does not live in the ERP
ToolSwift is headless and API-first. The storefront, the catalog, pricing, orders and customer accounts live in the platform, and the ERP connects to it like any other data source. Your storefront, your catalog work, your customer accounts and your URLs stay where they are.
The ERP stays the source of truth
The same rule runs through the rest of the platform. Dealers on ToolSwift can connect their own Claude or ChatGPT to their store and ask about sales, orders, quotes, customers and credit. When the assistant proposes bulk edits, the dealer previews and approves them, every change is logged and can be undone, and fields the ERP owns are refused. Reports and exports through that connector are coming, and so are draft quotes that only staff can send.
Quotes start from what contractors already have. The Takeoff Agent turns a contractor's voice note, photo, scan, takeoff or file into a draft quote matched against your catalog and your pricing, and your staff review it before it goes out.
What it costs
ToolSwift is $399 a month for the first store and $250 a month for each additional store, with no transaction fees, month to month with 30 days notice. The ERP connection is set up during onboarding, which is quoted separately. The connector is built and run by ToolSwift, so there is no middleware vendor in the middle to pay or to chase.
Five questions to ask any Epicor integration vendor
These five questions sort the three routes in one meeting, because each one asks who carries a cost after launch.
- Is BisTrack or Eagle named on your integration page, by name, today? A Prophet 21 connector is a different product.
- Who maps our account pricing, quantity breaks, branch stock and credit terms, and who fixes the mapping when it breaks?
- Is pricing and stock real time, or a scheduled file? If it is a file, how old can a price on the site get?
- What happens to the connector when BisTrack moves off on-premises, or when Eagle moves?
- Is the connector priced inside the store, or as a second subscription from a second company?
On ToolSwift the answers are: yes for both, our team, real time where your ERP supports it, the storefront stays where it is, and one company, with the integration quoted at onboarding and no second subscription. Put the same five to every vendor and write the answers down.
My rule: the store vendor should own the connector
My rule for a BisTrack or Eagle dealer is simple: buy the store from a company that owns the connector to your ERP, and keep the ERP decision separate from the store decision.
Epicor's own route welds the two decisions together, and Epicor's cloud schedule for BisTrack means that decision is coming by mid-2029 at the latest for every on-premises yard. The middleware route separates them, then hands the connector to you. A store built for LBM with its own BisTrack and Eagle connectors keeps them apart and keeps the connector off your desk.
If you are weighing the store side, my comparison with ECI's EvolutionX makes the same case for Spruce dealers, and the full list of what we connect to is on our integrations page.
FAQ
Does Epicor BisTrack have an API?
Yes. DCKAP describes the BisTrack Web API as REST access for real-time integrations, with Smart Views for custom datasets, and iWeb describes it as a licensed API. DCKAP also describes the eBusiness module, which imports XML, CSV or JSON files on a schedule.
Does Epicor Commerce Connect work with Shopify or BigCommerce?
DCKAP says it does not: Epicor Commerce Connect includes a BisTrack connector and only works with Magento-based stores, so Shopify Plus, BigCommerce and other platforms are not supported.
Does Epicor Eagle have a public API for eCommerce?
Supergood says Eagle has no public API. A licensed Eagle API is requested through Epicor account management or a certified VAR, and Epicor's public API documentation covers Kinetic and Prophet 21, not Eagle.
What happens to BisTrack on-premises?
Epicor announced on January 6, 2026 that BisTrack innovation moves to the Epicor Cloud. The final on-premises Desktop release is 2026.2, tentatively December 2026, supported through December 31, 2028; the final Web Browser and API release is 2028.1, tentatively July 2028, supported through June 30, 2029.
How long does it take to connect ToolSwift to BisTrack or Eagle?
A ToolSwift launch is measured in weeks. BisTrack and Eagle are connectors we already run, so our team configures and maps them as part of onboarding.
---
To see your BisTrack or Eagle data running in a ToolSwift store, book a demo.
Sources
Related in ToolSwift
Connected to the systems you already run
Sixteen ERP and accounting connections, and our team does the setup.