Axya provides a native integration with Infor CloudSuite Industrial (formerly SyteLine), supporting both cloud-hosted and on-premise deployments. The integration leverages Infor's standard services for reliable, bidirectional synchronization.
| Aspect |
Details |
| Type |
Native Connector (built by Axya) |
| Architecture |
Cloud-to-cloud or on-premise middleware |
| Deployment |
Cloud: no middleware needed. On-premise: lightweight Windows service |
| Sync Frequency |
Configurable polling interval (default: 5 minutes) |
| Direction |
Bidirectional |
- Purchase Orders — Headers and line items with full detail (quantities, pricing, delivery dates)
- PO Documents — Retrieved via Infor Document Manager (IDM) or email fallback
- Revisions — Detected via timestamp-based change tracking
- Requisitions / Projects — Imported for RFQ creation
- Reception Data — Goods receipt quantities and dates
- Vendor Contracts — Contract pricing and ranking data
- Supplier Acknowledgments — PO confirmation status
- Confirmed Delivery Dates — Promise dates updated on line items
- Price Adjustments — Negotiated pricing written back
- Quantity Changes — Agreed quantity modifications
- Contract Rankings — Vendor contract preference data (optional)
- Buyer creates a PO in SyteLine and sets the Axya Status dropdown to trigger sync
- The integration detects the status change during its sync cycle
- PO data is retrieved and the PDF is fetched from Infor Document Manager (or email as fallback)
- The PO appears in Axya and the supplier is notified
- The supplier interacts via Axya's portal — acknowledging, confirming dates, or proposing changes
- Supplier responses are written back to SyteLine
- When all lines are received, the PO is automatically archived in Axya
A custom status field is added to the Purchase Order form in SyteLine. Axya provides a step-by-step configuration guide. The status field supports values such as: Send, Success, Failure, Acknowledged, and Revision.
These fields are configured using SyteLine's standard customization functionality and do not modify core tables.
Axya supports two methods for retrieving PO PDF documents:
- Infor Document Manager (IDM) — Preferred method. PDFs are retrieved automatically.
- Email Fallback — If IDM is not available, PDFs can be received via a dedicated email mailbox.
- Timestamp-Based Change Detection — Efficiently detects modified POs without scanning the full table
- Multi-Environment Support — Seamless switching between production, training, and test environments
- Reception Tracking — Line-level receipt data synced for delivery progress visibility
- Vendor Contract Sync — Contract rankings and pricing breaks can be synchronized (optional)
- Requisition Import — Requisitions from SyteLine can be imported as RFQs in Axya for supplier bidding
| Option |
Description |
| Fetch POs |
Import purchase orders from SyteLine |
| Fetch requisitions |
Import requisitions for RFQ creation |
| Sync delivery dates |
Write confirmed dates back to SyteLine |
| Sync contract rankings |
Push vendor contract data (optional) |
| Document source |
IDM (preferred) or email fallback |
| Auto-send POs |
Send immediately or save as drafts |
| Failure notifications |
Email alerts for sync issues |
- ION API service account credentials
- IDM access for PO document retrieval
- Appropriate permissions for PO read and write operations
- All of the above, plus:
- Windows VM (8 GB RAM, 40 GB disk, 2-4 vCPU)
- VPN access to SyteLine servers
- Network connectivity to Axya's cloud endpoints
- OAuth 2.0 authentication with dedicated service account
- All communication over HTTPS
- Write operations use transactional services for data integrity
For setup assistance, contact your Axya account representative.