--- title: "Epicor LumberTrack to Shopify Integration" url: https://www.uncap.com/integration/epicor-lumbertrack author: "Denis Dyli" published: 2026-09-27 updated: 2026-09-27 summary: "LumberTrack runs the supply side of the wood products business. Epicor sells it to hardwood and softwood sawmills, panel mills, value-added remanufacturers, and to wood products distributors, wholesalers and brokers. Epicor publishes no API or integration documentation for LumberTrack. An integration here begins with a discovery pass against your actual instance to establish what it can expose and how, rather than with a published reference anyone can read in advance." --- # Epicor LumberTrack to Shopify Integration > LumberTrack runs the supply side of the wood products business. Epicor sells it to hardwood and softwood sawmills, panel mills, value-added remanufacturers, and to wood products distributors, wholesalers and brokers. Epicor publishes no API or integration documentation for LumberTrack. An integration here begins with a discovery pass against your actual instance to establish what it can expose and how, rather than with a published reference anyone can read in advance. If you are a dealer buying lumber, this is not your system. If you are the mill or the wholesaler selling to that dealer, it is, and the commerce question is whether your dealer customers can see what you have and order it without calling your trading desk. ## Nobody has written this page before That is not a figure of speech. We pulled the search results for LumberTrack and for lumber ERP software generally, and there is no integration or ecommerce content from anyone. Not an agency, not an integrator, not a middleware vendor. The ranking pages are Epicor's own product page, software review directories and a 2018 press release. One review site does have a heading asking whether LumberTrack offers an API, which tells you the question is being asked even though nobody is answering it. So we will answer it. ## What Epicor publishes about LumberTrack, and what it does not Epicor documents what LumberTrack does. Procurement, financials, shipping logistics, production tracking, data warehousing and reporting, inventory, FiberTrack and Epicor WMS. **Epicor publishes no API or integration documentation for LumberTrack.** We checked its own domain thoroughly. The contrast within Epicor's own product line makes the point: BisTrack, the building supply product, has a dedicated API page stating that the BisTrack API lets building suppliers connect BisTrack with external applications. LumberTrack has no equivalent. That is the honest starting position, and it shapes the project. An integration here begins with a discovery pass against your actual instance to establish what it can expose and how, rather than with a published reference anyone can read in advance. Any fixed-price quote written without that step is a guess. We would rather tell you that than imply a parity that does not exist. ## Available to Sell is the hook, and it is already in your system There is one LumberTrack capability that changes what a dealer portal can be, and it is documented in Epicor's own customer material rather than in marketing copy. Epicor's published Interfor story describes a fully integrated Available to Sell module inside LumberTrack, and notes that previously Available to Sell sat outside LumberTrack and was not integrated with order entry. That matters because available to sell is precisely the number a dealer portal needs. In wood products, on-hand is a poor guide to what you can actually commit: inventory moves in units, production is scheduled, material is in transit between the mill and the reload yard, and some of what exists is already allocated. A storefront built on raw on-hand will promise things your trading desk cannot deliver. If your LumberTrack holds an integrated Available to Sell position, that is what a portal should surface. We will not tell you it is exposable through an API, because Epicor does not document one. Establishing how to reach it is the first task in the project. ## What selling lumber online actually requires This is industry reality rather than a list of LumberTrack features, and we are labeling it that way deliberately because Epicor does not document these as product capabilities. Lumber does not sell like a part. It sells in units and bundles rather than pieces, and a unit is not a fixed quantity across items. It is priced by the thousand board feet as often as by the piece, so the storefront has to express the pricing basis your customers actually buy on. Random length inventory means the item a dealer orders and the item you ship are the same product at different tallies. Species and grade are the product identity, and a grade difference is a different item commercially even when it looks similar. Green versus kiln dried changes what the material can be used for. Treated products carry their own specifications. A generic ecommerce integration handles none of that, which is why generic ecommerce integrations fail in this trade. The question for any partner is not whether they can sync an order. It is whether they can represent a unit of random length number two common in a way a dealer recognizes. ## Where the two systems line up LumberTrack customers become Shopify companies, with ship-to locations and buyer logins, so a dealer signs into their own pricing and their own order history rather than a public catalog. Items are expressed the way you sell them: by unit and bundle, in the pricing basis your customers buy on, with species, grade and treatment as the identity rather than as a description. Availability reflects what you can genuinely commit rather than a raw on-hand figure. Contract pricing and freight adders resolve for the account that is logged in, because in this trade the delivered price is the price. An order placed in the portal reaches LumberTrack with the customer reference, the requested ship date and the specification attached, and its status comes back out. [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 The failure that matters here is the availability one, and it is sharper in lumber than in most trades because the units are large and the money moves fast. A dealer sees a unit in the portal and commits to it. Between the page load and the order, your trading desk sold it on the phone. Under a naive design nobody finds out until someone calls the dealer back, which is exactly the experience the portal was meant to replace. So availability is revalidated at order rather than only at browse, and when the specific material has gone the dealer is told immediately, with what else is available or a date. That is a better answer than silence and it is what a trader would say. Beyond that, transient failures retry on a backoff, permanent failures hold with the payload and the error preserved somewhere your team already looks, and they replay without asking the dealer to reorder. ## What we build A discovery pass against your LumberTrack instance to establish the integration mechanism and the supported write path, before anything is priced as fixed scope. A dealer portal on Shopify with company accounts, ship-to locations and buyer logins from your customer master. Item representation in units, bundles and the pricing basis you actually sell on, with species, grade and treatment as first-class attributes. Availability sourced from what you can genuinely commit, revalidated at order. Contract pricing and freight resolved per account. Order capture into LumberTrack with status, documents and invoices flowing back to the dealer. Phasing that usually starts with visibility and reorder before full transactional checkout, because that sequence gets dealers using the channel while the harder pieces are built. ## Industries that run LumberTrack 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. LumberTrack is one of several Epicor products we connect to Shopify. The [Epicor integration overview](https://www.uncap.com/integration/epicor) covers Prophet 21, Kinetic and the rest, including [BisTrack](https://www.uncap.com/integration/epicor-bistrack) for building supply dealers on the other side of this transaction. ## Ready to talk Bring your LumberTrack version, whether Available to Sell is integrated in your instance, and one dealer account with its pricing and freight terms. Ask us what we do not know yet, because on LumberTrack 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 availability model and the phased plan before development begins. ## Frequently asked questions ### Does Epicor LumberTrack have an API? Epicor publishes no API or integration documentation for LumberTrack. We checked Epicor's own domain, and the contrast is instructive: BisTrack has a dedicated API page while LumberTrack has no equivalent. That does not mean integration is impossible, it means the mechanism is established by discovery against your instance rather than read from a public reference. Ask any partner quoting fixed scope how they established it. ### How is LumberTrack different from BisTrack? They sit on opposite sides of the same transaction. LumberTrack is the supply side: sawmills, panel mills, remanufacturers, wholesalers and brokers, running from log yard through mill to reload yard. BisTrack is the demand side: building supply and lumber dealers selling to contractors and builders. If you sell units to dealers, you are LumberTrack. If you sell to the contractor, you are BisTrack. ### Can a dealer portal show real availability? It should show what you can genuinely commit rather than raw on-hand, because in wood products those are different numbers. Epicor's own customer material describes an integrated Available to Sell module inside LumberTrack, which is the right source if your instance has it. How to reach it is a discovery question, since no API documentation exists. ### How do you handle random length and tally? By representing the product the way your customers buy it rather than the way a generic catalog would. That means units and bundles rather than pieces, the pricing basis you actually sell on, and species, grade and treatment as product identity. This is industry practice rather than a documented LumberTrack feature, and any partner who cannot discuss it fluently has not worked in this trade. ### Can we price by the thousand board feet online? Yes, and for a lot of items you have to, because a per-piece price is not how the trade quotes. The storefront needs to express your actual pricing basis and to carry freight, since the delivered price is usually the number that matters to the dealer. ### Should we launch with full checkout? Usually not first. Availability visibility and reorder from history get dealers using the channel quickly and prove the data is right, while transactional checkout with pricing, freight and credit is built behind it. Sequencing is a choice worth making deliberately. ### How long does an Epicor LumberTrack Shopify integration take? Less predictable than on ERPs with published APIs, which is the honest answer. The discovery pass that establishes the mechanism comes first and the schedule follows from what it finds. The Blueprint engagement exists for exactly this situation.