EPICOR INTEGRATION FOR FIELD SALES & DISTRIBUTION
Put Epicor data to work beyond the back office.
Connect Epicor to the mobile workflows your sales and distribution teams use every day—with two-way customers and orders, plus the operational context needed in the field.
Authenticated with your Epicor company connection settings.
CONNECTION REQUIREMENTS
A clear path from credentials to connected workflows.
The integration uses five Epicor connection inputs. Your administrator enters them once in the inSitu Sales Web Backoffice, then validates the supported data flow for the operation.
- 01Enter the Epicor company detailsCompany URL, company ID, and integration user.
- 02Add the authentication credentialsPassword and authentication token stay masked on the page.
- 03Validate the record directionsConfirm two-way and inbound ownership before rollout.
SUPPORTED DATA FLOW
See exactly what moves—and which way.
Use the record groups to review the current integration map. Customers and orders are two-way; the remaining supported records move from Epicor into inSitu Sales.
SELECTED GROUP
Records that move both ways
Customer and order activity can travel between Epicor and inSitu Sales under the configured workflow.
Back-office dataField workflow- Customers
- Orders
FROM ERP RECORD TO FIELD ACTION
Keep Epicor at the center without putting it in every rep’s hands.
inSitu Sales turns approved ERP context into a focused selling workflow while the back office keeps working in Epicor.
- 01
Prepare the visit
Load approved customers, account history, prices, products, inventory, terms, and payment methods.
- 02
Capture the order
Reps build the order in inSitu Sales with the Epicor context selected for that customer.
- 03
Synchronize
Customers and orders move both ways; the remaining supported records flow from Epicor to the field.
- 04
Keep Epicor current
Back-office teams continue operating in Epicor while field execution stays focused in inSitu Sales.
EPICOR INTEGRATION FAQ
Practical answers before implementation.
Use your actual Epicor company configuration and record requirements when validating the final integration scope.
What information is required to connect Epicor?+
The connection uses the Epicor Company URL, Epicor Company ID, username, password, and authentication token shown in the inSitu Sales integration settings.
Which records synchronize both ways?+
Customers and orders are configured as two-way records in the current integration map.
Which Epicor records are available to inSitu Sales?+
Supported inbound records include sales-order and invoice account history, inventory, new customers, payment methods, price lists, price rules, product price lists, products or items, sales reps, sales taxes, sales terms, and warehouses.
Do sales reps need to work inside Epicor?+
No. Reps use inSitu Sales for their assigned field workflows while Epicor remains the back-office system connected to those records.