Data Domains
The other Integration pages are organized by mechanism — Table Import, the JSON API, and On-Demand / Sync. That answers "how does data move?"
This section is the other axis: it is organized by data domain and answers "for this kind of data, what are all the ways it can enter or leave Eclipse?" Each page takes one domain (Materials, Coils, Orders, …) and lists every integration path that touches it, with links out to the mechanism page that documents the details. Nothing is duplicated here — when a path is already specified elsewhere, this section just points to it.
Use this section when you are integrating a specific kind of data and want the full picture before choosing an approach.
Coverage at a glance
| Domain | Eclipse Classic | Eclipse Pro |
|---|---|---|
| Materials | Table Import (ASCII / SQL) | Table Import · DB sync (on-demand) · explicit REST API · inline with Order Import · Direct (custom) |
| Coils | Table Import (not recommended) | Coil Sync · Coil Validation |
| Orders | Table Import (orderin/bundlein) | Table Import · JSON API |
| Punch Patterns | Table Import (partin) | Table Import · on-demand pattern import |
| Product Codes (Tooling) | Table Import | Table Import · inline with Order Import |
| Schedule | — | Schedule Sync (DB pull) · REST API push |
| Production (export) | Table / file export | — |
Materials and Schedule have dedicated domain pages — Materials because several of its Eclipse Pro paths are not specified on a mechanism page, and Schedule because it offers two distinct paths (DB sync and REST API push) that share a common data model worth describing in one place. The remaining domains link to their existing mechanism pages; dedicated domain pages for them will be added over time.