Integration · Epicor Kinetic
Connect your Epicor data to WERISCO.
BAQ-based structured export, mapped once to the WERISCO model. There is no WERISCO Epicor connector today.
Data arrives as a scheduled structured export (file, database view or warehouse table) mapped to the WERISCO model.
What WERISCO reads from Epicor
| Data | Source in Epicor | Used for |
|---|---|---|
| Part bin quantitiesREST / BAQ | REST / BAQ | Inventory health |
| PO linesREST / BAQ | REST / BAQ | PO risk |
| JobsREST / BAQ | REST / BAQ | Production |
- Authentication
- Secure file drop or upload; no Epicor credentials are shared with WERISCO.
- Sync
- Matches your export schedule.
- Write-back
- None. WERISCO reads only; decisions are executed by your team in Epicor.
BAQs give a fast, controlled first extract.
Column mapping is done once and reused.
Setup
- 01Agree the connection route during the audit
- 02Configure the scheduled export (templates provided)
- 03First extract, field mapping and a data-quality report
- 04Scheduled refresh switched on
Supply chain audit
See where your supply chain is exposed.
A 20-minute call and two file exports: stock by item and open orders. You see the inventory and order value exposed. No integration, no savings estimate, and an NDA if you need one.