--- title: "Epicor BisTrack to Shopify Integration" url: https://www.uncap.com/integration/epicor-bistrack author: "Denis Dyli" published: 2026-09-27 updated: 2026-09-27 summary: "BisTrack runs lumber and building materials dealers. Selling to that contractor online is a real opportunity and a genuinely hard integration. Epicor has a BisTrack API page and it describes real capability. There is a Smart View Endpoint that uses SQL queries to extract any field or dataset from BisTrack." --- # Epicor BisTrack to Shopify Integration > BisTrack runs lumber and building materials dealers. Selling to that contractor online is a real opportunity and a genuinely hard integration. Epicor has a BisTrack API page and it describes real capability. There is a Smart View Endpoint that uses SQL queries to extract any field or dataset from BisTrack. Selling to that contractor online is a real opportunity and a genuinely hard integration. We are going to be direct about why. ## What Epicor publishes about the BisTrack API, and what it does not Epicor has a BisTrack API page and it describes real capability. All API interactions require authenticated access. Encrypted communication uses Microsoft tooling. There is a Smart View Endpoint that uses SQL queries to extract any field or dataset from BisTrack. Records can be created, updated and saved programmatically. The named capability areas cover customer and contact data, delivery and dispatch integration, document handling, financial data exchange, web store connectivity, order and quote management, inventory access, and reporting and analytics. **What that page never states is the protocol.** It does not say REST. It does not say SOAP, GraphQL or OData. We looked for public developer documentation or an API reference and found none. We are telling you this rather than quietly assuming REST, because the assumption is where BisTrack projects go wrong. If somebody has quoted you a fixed price for a BisTrack integration, ask them which protocol they are building against and where they read it. There is a correct answer for your instance, and it comes from a scoping conversation with Epicor and a look at your actual environment, not from a web page. The Smart View Endpoint detail deserves its own thought, because SQL extraction is a read mechanism rather than a business-logic-aware one. Reading that way is often fine. Writing that way is how you end up with orders that look correct in a table and behave incorrectly in dispatch. The write path has to go through whatever mechanism enforces BisTrack's own rules, and establishing what that is on your instance is the first task in the project. ## Why nobody, including the AI, can tell you this has been done before We ran an LBM dealer's version of this question through a web-connected model twice, identically. Both runs recommended Epicor's own commerce product as the lowest risk default and explicitly downgraded anything else to "a custom project, not the default answer". One run said plainly that it could find no primary-source evidence of a BisTrack-specific Shopify path. Both closed by hedging that they were reasoning by inference rather than from any hands-on implementation review. That is an honest answer from the model and it is the accurate state of the public record. There is very little published about connecting BisTrack to a modern storefront, by anyone. Which cuts both ways. It is a real reason to be careful about who you hire. It is also why the entire category is wide open, and why a dealer who does this well gets a channel their competitors are still thinking about. ## The seven pieces of work Both prompt runs independently produced the same list of workstreams, which is a decent sign it is the right one. It also matches what an LBM build actually involves. Customer and account sync, covering which branch the account belongs to, their terms eligibility, their ship-to locations, who is permitted to buy under the account, and what pricing level applies. Catalog, including units of measure and special-order items, which in this trade is harder than it sounds. BisTrack supports various packaging types and tally methods, and a storefront that cannot express a tally or a non-stocking unit of measure will generate orders your yard cannot pick. Pricing, which both runs flagged as the hardest part, covering account-level pricing, quantity breaks, branch-level differences and delivery or freight surcharges. Order submission, carrying the purchase order or job reference, the delivery address, the requested date, line notes, and whether it is pickup or delivery. Delivery and fulfillment status back to the buyer. This one is distinctive to LBM. BisTrack's Journey Planner handles delivery scheduling, vehicle assignment, route optimization, manifests, load weight and volume with overweight alerts, and proof of delivery with photos and signatures. A contractor who can see where their lumber is, and the photo proving it was dropped where they asked, is a contractor who orders online again. Accounts receivable visibility, including open invoices, statements and payment history. BisTrack's financial management lets you drill into customer balances by job, which is the view a contractor with several sites running actually wants. Self-service, meaning reorder from history, saved material lists, quote to order, and several buyers working under one account. ## What we are not going to tell you There is a version of this page that lists lien waivers, preliminary notices, random-length lumber handling and contractor charge accounts as BisTrack features, because those are real things in this trade and it reads well. We checked Epicor's own BisTrack pages for each of them and could not confirm any as named, documented functionality. Tally methods and packaging types are confirmed. Drilling into customer balances by job is confirmed. The rest we could not source. That does not mean your BisTrack instance cannot handle them. It means we are not going to describe your system to you from a marketing page. What those processes look like in your yard is a discovery question, and the answer determines the build. ## Where the two systems line up BisTrack customers become Shopify companies. Ship-to locations, including the sites a contractor is currently working, become company locations. The people buying under an account become buyer logins with their own permissions, because a purchasing manager and a foreman on site should not have the same authority. Products carry the units of measure and packaging the yard actually sells in, with tally handled explicitly rather than approximated. Availability comes from the yard the customer is served by, not from a company-wide number, because a contractor cares about what is on the ground where their truck is going. A Shopify order becomes a BisTrack order carrying the job or purchase order reference, the delivery address, the requested date and the pickup-or-delivery decision, written through whatever mechanism enforces BisTrack's own validation on your instance. Delivery status, including proof of delivery, comes back to the buyer's account. [Uncap Connect](https://www.uncap.com/products/connect) keeps pricing, inventory, customer data and orders current in both directions, built for B2B so account pricing and terms behave correctly. ## What happens when an order fails Three failures are worth designing for specifically in this trade. The delivery address is not one BisTrack knows about, because the contractor is on a new site. That should be a supported flow rather than an error, since new sites are how this business grows. The order is for a quantity the yard cannot supply in the unit the buyer chose, which is the tally and units of measure problem showing up at the worst moment. The account has hit whatever limit governs it. That is a credit conversation, not a technical failure, and it should route to a person who can make the call rather than dropping the order. Everything else follows the ordinary pattern. Transient failures retry on a backoff. Permanent failures hold, with the payload and the exact BisTrack error preserved, somewhere your team already looks, and replay without asking the customer to reorder. The buyer's Shopify order stays visible to them throughout. ## What we build A discovery pass against your actual BisTrack instance that establishes the integration mechanism and the supported write path, before anything is priced as a fixed scope. Account, ship-to and buyer permission structures mapped into Shopify companies and company locations. Catalog with real units of measure, packaging types and tally, so orders arrive pickable. Account pricing resolved from BisTrack rather than exported, with quantity breaks and branch differences respected. Order submission carrying job reference, delivery address, requested date and pickup or delivery, with a held-order queue and replay. Delivery visibility to the buyer, including proof of delivery where your Journey Planner configuration captures it. Phased delivery, usually reorder and quoting first and full transactional checkout second, because that sequence gets contractors using the channel while the harder pieces are built. ## Industries that run BisTrack Building Materials, where products sell by area and length, a waste factor has to be added before a quantity is correct, and lead times decide whether a quote is usable. Construction Supply, where the buyer wants pickup or same day delivery and needs to know which yard has it. BisTrack is one of several Epicor products we connect to Shopify. The [Epicor integration overview](https://www.uncap.com/integration/epicor) covers the others. ## Ready to talk Bring your BisTrack version, whether you are hosted or on-premises, and one contractor account with its pricing and its open jobs. Ask us what we do not know yet, because on BisTrack that list is longer than on most ERPs and you should hear it before you hire anyone. Book a strategy session, or start with a [Blueprint](https://www.uncap.com/blueprint), the paid discovery engagement that establishes the integration mechanism, the pricing model and the phased plan before development begins. ## Frequently asked questions ### Does Epicor BisTrack have a REST API? Epicor does not say. The BisTrack API page describes authenticated access, encrypted communication using Microsoft tooling, a Smart View Endpoint that extracts data using SQL queries, and the ability to create and update records programmatically, but it names no protocol, and we found no public developer documentation or API reference. Anyone quoting you a fixed-price BisTrack integration should be able to say which mechanism they are building against and where they confirmed it. ### Can BisTrack be connected to Shopify at all? Yes. Epicor's own capability list includes web store connectivity, order and quote management, inventory access and customer data. What is not publicly documented is the protocol and the reference, which makes discovery against your instance the first real task rather than an optional preliminary. ### Why does so little exist about BisTrack and Shopify? Because very little has been published by anyone. When we tested what a web-connected AI tells an LBM dealer, both runs defaulted to Epicor's own commerce product, one noted it could find no primary-source evidence of a BisTrack-specific Shopify path, and both acknowledged they were reasoning by inference. That is a fair description of the public record, and it is also why the category is open. ### How do tally and units of measure work on a storefront? They have to be expressed properly or the orders will not be pickable. BisTrack supports a range of packaging types and tally methods, and the storefront needs to represent the same product sold in the units your yard actually sells it in. Getting this wrong produces orders that look fine online and cause a phone call at the yard. ### Can contractors see their deliveries? Yes, and it is one of the strongest reasons to build this at all. BisTrack's Journey Planner covers delivery scheduling, vehicle assignment, route optimization, manifests, load weight and volume with overweight alerts, and proof of delivery with photos and signatures. Surfacing that to the buyer's account is what makes a contractor use the channel a second time. ### What about job-level information? BisTrack's financial management supports drilling into customer balances by job, which is the view a contractor running several sites wants. Beyond that, how jobs work in your instance is a discovery question. We are not going to describe your configuration to you from a product page. ### Should we launch with full checkout? Usually not first. Reorder from history, saved material lists and quote to order get contractors using the channel quickly and prove the data is right, while transactional checkout with pricing, delivery scheduling and account limits is built behind it. The sequencing is a choice, and it is worth making deliberately. ### How long does an Epicor BisTrack Shopify integration take? Less predictable than on ERPs with published APIs, which is the honest answer. The discovery pass that establishes the mechanism and the supported write path comes first, and the schedule follows from what it finds. The Blueprint engagement exists for exactly this situation.