Why it matters
Automation equipment acts on instructions from business systems and reports results back to them. Orders, inventory, and task status must stay consistent across every system involved.
A connector that passes a demonstration proves that two systems can exchange a message. It does not prove that a full shift of real transactions, with real exceptions, will reconcile.
What can go wrong
- The WMS or ERP sends work in batches, and the automation expects it continuously.
- Inventory in the automation controller and inventory in the WMS drift apart, with no rule for which is correct.
- Exceptions such as short picks, damaged items, unreadable labels, and mid-task cancellations have no defined workflow.
- Customizations in the existing system block the interface the vendor normally uses.
- No single person or team owns the interface once the integrator leaves.
What evidence to examine
| Evidence | What it can establish |
|---|---|
| Interface inventory and data-flow diagrams | Which systems exchange what, and in which direction |
| API documentation, versions, and licensing terms | Whether required interfaces exist and can be used |
| Measured transaction volumes and timing | Whether current systems respond at the rate automation needs |
| Exception-handling specifications | Whether non-standard events have a defined path |
| System-of-record matrix by data element | Which system is authoritative when values disagree |
| Test environment availability | Whether integration can be proven before go-live |
| Upgrade roadmap and customization register | Changes that could break the interface later |
Warning signs
- Integration is described as “standard” without a list of transactions.
- The WMS, MES, or ERP is due for an upgrade during the project.
- There is no test instance that mirrors production.
- Exception handling is deferred to “phase two.”
What to do next
- List every transaction the automation will send and receive, including exceptions.
- Decide the system of record for inventory, orders, and task status.
- Confirm a test environment and a named interface owner before contract signature.