How to Import Orders into BisTrack

Path 1: eBusiness file imports

The eBusiness module is BisTrack's native file-based intake. An integration drops order files through the BisTrack FTP process, and BisTrack pulls down waiting documents automatically about every 30 seconds. An operator opens the eBusiness Browser under Tools, double-clicks a file to inspect the data, and clicks Apply to create the document in BisTrack. The import can create either a sales order or a quote depending on the sales type set for that import, and setup lives in System Manager under eBusiness Setup, with a source identifier for each integration.

Epicor publishes almost nothing about eBusiness publicly. The clearest documentation of the mechanics above is the FAQ that Saberis maintains for SaberisConnect, its integration that converts vendor quotes from window, door, and kitchen configurators into BisTrack sales orders or quotes through this path. SaberisConnect can also merge an import into an existing sales order. If a tool needs to land documents in BisTrack without touching the API, eBusiness is the path it rides.

Path 2: the EDI interface

BisTrack has a native EDI interface that turns trading partner documents into sales orders. Public documentation on trading partner setup is close to nonexistent, so most shops run it through a provider. The one provider we found with a documented BisTrack integration is Infocon Systems, which maps inbound 850 purchase orders and 860 changes into BisTrack sales orders and sends invoices (810), acknowledgments (855), and ship notices (856) back out. In lumber, the accounts big enough for EDI tend to be large builders and commercial customers; at the dealers we talk to, contractor orders still arrive by email and phone.

Epicor's own Order Entry Automation add-on also delivers its OCR output through the EDI interface, creating a sales order with the customer's PO attached in Related Documents. In practice the EDI interface is BisTrack's general-purpose document-to-order gateway.

Path 3: the BisTrack API

The API is the modern path. The BisTrack API is a named Epicor product, and its documented capabilities include pushing orders and quotes from external platforms into BisTrack with payment details, alongside inventory and pricing by branch, customer and job site data, and delivery and dispatch. It's what web store integrations use, and Epicor's Automation Studio (the company's low-code integration platform) connects through it, with automated order submission from customer portals among its named use cases.

It's a separately licensed product. Epicor's own Automation Studio page says customers must also be BisTrack API users, and Epicor doesn't publish pricing, so it's a line item to confirm before an integration plan depends on it. Getting access starts with your Epicor account rep, who routes you to the product team.

Path 4: the Order Entry Automation add-on (template OCR)

For PO documents themselves, Epicor sells BisTrack Order Entry Automation, a form recognition and OCR add-on that reads scanned and emailed PDF purchase orders. It's template-based. You set up a template for each account customer, the builders and contractors you do repeat business with, and the system then recognizes their POs and extracts the customer number, delivery address, required dates, and the quantity, unit of measure, and price on SKU lines. Non-SKU lines are left blank for manual entry, which matters in LBM, where special orders are routine.

A review screen groups captured POs by customer and site, and the export lands through the EDI interface as a sales order with the original PO attached in Related Documents. Epicor doesn't publish pricing for it. The template model is the real constraint: it earns its keep on repeat customers with consistent PO formats, and it doesn't cover the first order from a new account or anyone whose documents vary.

Importing orders from a spreadsheet

Epicor provides spreadsheet templates for bulk data imports, but those are master-data tools for things like items and customers. There's no supported path for pasting a customer's order from a spreadsheet into BisTrack; a spreadsheet order is just another document that has to become an eBusiness file, an EDI document, or an API call first.

The orders none of these paths cover

Every path above wants structured input or a per-customer template. A contractor's emailed PO, a photo of a handwritten list, or a document that mixes stock items with special orders has neither, so someone keys it into Order Entry by hand. Epicor's OCR add-on covers the repeat customers you've built templates for, and nothing else.

The order automation SaaS vendors haven't claimed this ground either. Epicor's expanded Conexiom partnership, announced in July 2026, covers Prophet 21 and Eclipse, and BisTrack isn't named in it. As of this writing, we can't find any major order automation vendor publishing a BisTrack integration.

The template-free answer is a custom AI order entry system, built by Airdev, sitting in front of BisTrack. It reads whatever arrives, matches lines against your item file and that contractor's pricing, flags anything it isn't sure about, and stages a draft through eBusiness or the API for a person to approve before it posts. The import paths on this page don't change; they just stop being fed by hand.

This is the system we build for BisTrack shops. Talk to us

Frequently asked questions