Skip to main content
Integration · Epicor

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. It tracks cost, species and grade from the log yard through the mill to the reload yard.

Last updated

In this article Talk to our experts

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.

The question this page answers

A mill or wholesaler asking whether LumberTrack can feed a dealer portal is really asking two things: what LumberTrack exposes, and how the dealer side should work. This page answers both.

What Epicor publishes about LumberTrack

Epicor documents what LumberTrack does. Procurement, financials, shipping logistics, production tracking, data warehousing and reporting, inventory, FiberTrack and Epicor WMS.

The integration mechanism is confirmed against your installation. Which interfaces your LumberTrack instance exposes, and which write path Epicor supports for it, is established against your installation and with Epicor before anything is built or priced as fixed scope.

That shapes the project. An integration here begins with a discovery pass against your actual instance to establish what it can expose and how. Any fixed-price quote written without that step is a guess.

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. Whether your instance exposes it through an API is confirmed in discovery, and 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 these are trade practices rather than product capabilities quoted from Epicor.

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 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 covers Prophet 21, Kinetic and the rest, including BisTrack for building supply dealers on the other side of this transaction.

How the integration runs

On LumberTrack, the integration mechanism is confirmed against your installation before any build work is scoped.

  1. Assessment: we review your LumberTrack setup and scope the work with you.
  2. Uncap Blueprint, if you want the plan first: $7,500 fixed, 4 weeks, with an ERP integration audit and the fee credited 1:1 toward implementation.
  3. Discovery on your instance: which interfaces your LumberTrack instance exposes, and which write path Epicor supports for it, is established before anything is priced as fixed scope.
  4. Map: we bring LumberTrack and Shopify objects and fields into one shared model.
  5. Sync: inventory, orders, customers and pricing sync both ways in real time.
  6. Monitor: every sync is visible in a live console that flags conflicts and replays failed syncs.

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. That figure is the Connect app's deploy time. We set the full LumberTrack schedule after discovery. For a specific ERP and the depth of sync your operation needs, the Uncap team confirms fit directly.

Track record on manufacturing ERPs

Uncap has not published a LumberTrack case study. For a mill, the nearest published proof is a manufacturer: Shopify's case study of Kooks says Kooks chose Uncap in part for "their experience integrating Shopify with key manufacturing systems like ERP and product information management (PIM) tools." Kooks runs Infor Visual ERP from another vendor, which makes this general ERP proof.

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.

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

12 Common questions

Frequently asked questions

Does Epicor LumberTrack have an API?

Which interfaces your LumberTrack instance exposes, and which write path Epicor supports for it, is established by a discovery pass against your installation before anything is priced as fixed scope. Ask any partner quoting fixed scope how they established the mechanism.

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, answered against your instance.

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 LumberTrack feature quoted from Epicor, 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?

The honest answer is that it depends on discovery. 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.

Talk to Our Experts →