Epicor BisTrack to Shopify Integration

Selling to that contractor online is a real opportunity and a genuinely hard integration. We are going to be direct about why.

Epicor has a BisTrack API page and it describes real capability. Epicor says it requires "authenticated access for all API interactions" and uses Microsoft tools for encrypted communication. The Smart View Endpoint uses SQL queries "to extract any field or dataset from BisTrack," and records can be created, updated, or saved programmatically. The named capability areas cover customer and contact data, customer data integration, delivery and dispatch integration, document handling, financial data exchange, web store connectivity, order and quote management, inventory access, and reporting and analytics. Several matter directly to a storefront: customer records include "names, job sites, addresses, and lien information," orders and quotes can be pushed into BisTrack "complete with payment details," pricing stays consistent "using your existing BisTrack tables," and inventory access covers "product availability, pricing, and images across branches and channels."

What that page never states is the protocol. It does not say REST. It does not say SOAP, GraphQL or OData; it says only that the API maintains data integrity "with standardized protocols." Epicor offers an eBook that it says covers technical architecture, developer tools, and a "full endpoint overview and setup guidance." The protocol and endpoints for your installation are confirmed against your own instance and with Epicor.

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.

Be careful about who you hire, and ask to see the BisTrack work a partner has delivered. A dealer who does this well gets a channel their competitors are still thinking about.

These are the workstreams 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 its Tallied SKU Entry "allows users to enter multiple lumber lengths and quantities from a single parent SKU." 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. BisTrack's own transaction tools include Customer-Specific Pricing, which Epicor says "automatically applies the correct pricing rules based on the customer making the purchase," so the storefront should resolve prices from BisTrack rather than copy them.

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 Dispatch & Delivery covers delivery scheduling, vehicle assignment, and route optimization. Its Journey Planner builds manifests and tracks load weight and volume with overweight alerts, and its BisTrack Delivery mobile app lets drivers "capture proof of delivery with photos and customer 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.

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 rechecked Epicor's own BisTrack pages for each of them in October 2026, and part of that list is now documented. The BisTrack API page says customer records include "names, job sites, addresses, and lien information." BisTrack's transaction tools include Tallied SKU Entry for multiple lumber lengths from a single parent SKU, and New Job Creation, which "allows users to add project-specific delivery locations directly from quotes and orders." BisTrack's financial tools report charge sales alongside cash sales, and let you "drill into customer balances by job." Tally methods and packaging types are confirmed too. Lien waivers and preliminary notices as named workflows, and contractor charge accounts as a named feature, are confirmed against your own instance in discovery.

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.

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 keeps pricing, inventory, customer data and orders current in both directions, built for B2B so account pricing and terms behave correctly.

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. Inside BisTrack, Epicor lists New Job Creation for adding project-specific delivery locations from quotes and orders, and whether your instance lets the integration create one is a discovery question.

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.

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 drivers capture it in BisTrack Delivery.

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.

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 covers the others.

On BisTrack, the protocol and endpoints are confirmed on your own instance during discovery, before anything is priced as fixed scope.

Timeline and price. Uncap Connect has a typical deploy of 3 to 5 weeks and starts at $8,000 for onboarding, then a flat $390 per month. Those weeks are the Connect app's deploy time, and the full BisTrack schedule comes out of discovery. For a specific ERP and the depth of sync your operation needs, the Uncap team confirms fit directly.

There is no published BisTrack case study from Uncap. Denis Dyli, Uncap's founder and CEO, includes BisTrack in his specialties in his author bio: "connecting Shopify to the ERPs that real operators depend on, from Epicor P21 and Kinetic to Eclipse and BisTrack." On Clutch, Uncap is rated 5.0 from 77 reviews.

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.

Talk to Our Experts, or start with a Blueprint, the paid discovery engagement that establishes the integration mechanism, the pricing model and the phased plan before development begins.