Epicor Kinetic label printing: BPMs, REST and database views
Print job, part, lot and shipping labels from Epicor Kinetic (ERP 10/11) using BPM directives that call the REST API, SQL views and watched folders — manufacturing scenarios and a checklist.
Epicor Kinetic is a manufacturing ERP, and its label needs follow the shop floor: job travelers, part tags at operation completion, lot and heat numbers, pack-out labels at shipping. BPM directives already run on those transactions, which makes them the natural place to trigger a label without touching the base product.
Which integration paths fit Epicor
| Path | Fit | Why |
|---|---|---|
| BPM + REST | Best | A method or data directive (C# code block) calls the REST API when a job is completed, a lot is created or a pack is closed. |
| Embedded data (SQL) | Good | Read-only views on Part, PartLot, JobHead and ShipHead; the label completes descriptions and specs by key. |
| Watched folder | Good | A BAQ export or Epicor Functions writes CSV to a folder; EtikStudio prints the batch. |
| Connector + relay | Cloud | Epicor Kinetic in the cloud prints to plant printers through the linked connector. |
Manufacturing scenarios
| Process | Label | Trigger |
|---|---|---|
| Job release | Traveler and operation labels | Job released |
| Operation completion | Part tags with lot/heat and quantity | Labor entry, quantity reported |
| Receiving | PO receipt labels with lot and inspection | Receipt entry |
| Shipping | Pack-out, SSCC and customer-specific labels (AIAG) | Pack closed, shipment confirmed |
Recommended flow
Put the trigger in a data directive on the table that changes (JobHead, PartLot, ShipHead) rather than in the UI, so labels print no matter which screen or handheld created the transaction. Customer-specific formats (automotive AIAG, retail) stay as templates in EtikStudio selected by customer id.
Implementation checklist
- Choose data directives over method directives for reliability across screens and MES devices.
- Map plants and resource groups to printers; one connector per plant if Kinetic runs in the cloud.
- Include lot, heat, quantity and customer part number for AIAG labels.
- Verify Code 128 and Data Matrix on the actual shop-floor printers.
How EtikStudio handles it
Epicor sends the transaction; EtikStudio renders the customer's required format on the plant's printer — Zebra, SATO or TSC — and keeps the print log that automotive audits ask for.
Integration details vary by ERP version, deployment and licensing. Adapters and worked examples are provided during implementation.