Integrations
Connect LEAFIO AI to your existing ERP and data infrastructure without replacing what works
LEAFIO AI is designed to work alongside your existing systems, not replace them. Our integration layer connects to the ERP and data infrastructure you already operate. Integration scope and approach are defined during pre-sales technical discovery.
1. Integration Approach
Flexible by design: no rip-and-replace required
LEAFIO integrates with retail systems using two models, chosen based on your ERP's capabilities and your IT team's preferences:
| Standard Integration Batch data upload - used by most clients |
Client prepares and uploads data batches to LEAFIO via SFTP, S3, or API. LEAFIO returns replenishment orders and results to the client ERP via API or SFTP/S3. Data is updated daily (previous day's sales); more frequent intraday updates available via API on demand.
|
| Custom Integration Tailored connection to client ERP or database |
LEAFIO builds a tailored connection directly to the client's ERP or database, managed end-to-end by the LEAFIO integration team. Client systems generate CSV files for defined data entities (e.g. master items, stores, sales facts) and deliver them to LEAFIO's server via API. Orders and results are returned to the client ERP via API/S3 or SFTP.
|
Both models are proven across 250+ implementations in 40+ countries. Integration model is selected during pre-sales technical discovery.
2. What Data LEAFIO Exchanges
Standard data flows: input and output
LEAFIO receives operational data from your systems and returns actionable outputs. Here is the standard data exchange structure:
| Direction | Data Type & Details |
| → ERP to LEAFIO | Sales data Daily sales data by SKU, store, date: basis for demand forecasting |
| → ERP to LEAFIO | Stock on hand Current inventory levels per SKU per location |
| → ERP to LEAFIO | Orders in transit Open purchase orders and expected delivery dates |
| → ERP to LEAFIO | Product catalog SKU master data: descriptions, units, pack sizes, supplier info |
| → ERP to LEAFIO | Supplier data Lead times, MOQs, ordering calendars |
| → ERP to LEAFIO | Price & promo data Active promotions, price changes, seasonality flags |
| ← LEAFIO to ERP | Replenishment orders LEAFIO-generated purchase orders or order proposals, ready to confirm |
| ← LEAFIO to ERP | Planogram outputs Shelf layout data, facing recommendations, fixture assignments |
| ← LEAFIO to ERP | Forecasts Demand forecasts by SKU/store for planning horizon |
3. ERP Compatibility
ERP platforms with known data compatibility
LEAFIO has active clients running on these ERP platforms across grocery, pharmacy, convenience, and CPG verticals. In each case, data is sourced from the ERP. How that data reaches LEAFIO depends on the integration model selected during discovery.
| SAP S/4HANA · Business One |
Compatible with SAP S/4HANA and SAP Business One. Data exchange via SFTP/S3 or SAP REST API (version-dependent). Standard SAP material master and sales order structures supported. Integration scope confirmed during pre-sales technical discovery.
Specific module versions confirmed during pre-sales technical discovery. |
| Microsoft Dynamics Dynamics 365 · Business Central |
Compatible with Microsoft Dynamics 365 and Business Central. Integration via file exchange (SFTP/S3) or Dynamics REST API / OData. Standard item, inventory, and sales order entities supported. Compatible with on-premise and cloud-hosted Dynamics deployments.
Both legacy NAV/AX migrations and native D365 environments supported. |
| PDI Technologies Convenience & fuel retail |
Compatible with PDI Enterprise, the dominant ERP/back-office platform in convenience and petro retail. File-based integration via SFTP/S3 using PDI's standard data export formats. Supports PDI sales, inventory, and product master data structures out of the box. Relevant for C-store and fuel retail operators running PDI as their primary back-office system.
PDI is the most common back-office platform among North American convenience and petro retail chains. |
| Oracle Retail Enterprise · mid-market |
Compatible with Oracle Retail Merchandising System (RMS) and related modules. File-based integration via SFTP/S3 or Oracle REST API. Standard Oracle item master, store inventory, and order management data structures supported.
Contact us for version-specific compatibility details. |
| Oracle NetSuite Mid-market · cloud-first · multi-store |
Compatible with Oracle NetSuite, the leading cloud-native ERP for mid-market retail chains. File-based integration via SFTP/S3 or NetSuite REST API. Standard NetSuite item master, inventory, sales order, and purchase order records supported. Particularly relevant for cloud-first retailers running NetSuite as their primary back-office and financial system. Compatible with both standard NetSuite and customized implementations.
Contact us to discuss your specific NetSuite version and configuration. |
Using a different ERP or a custom-built system? LEAFIO has been integrated with additional platforms not listed here. If your ERP can export structured data via SFTP, S3, or API, integration is typically achievable. Discuss your stack with our technical team.
4. Integration Discovery Process
How integration is scoped and delivered
Integration scope, timeline, and resourcing are defined during pre-sales technical discovery, based on your ERP, data readiness, and project context.
| Phase | Milestone & What Happens |
| Phase 1 | Technical Discovery ERP version, available export formats, and IT security requirements reviewed. Integration model confirmed (Standard or Custom). Data entities and file formats agreed. |
| Phase 2 | Data Mapping ERP data structures mapped to LEAFIO's data schema. File format specifications agreed with your IT team. Test environment configured. |
| Phase 3 | Test Integration First data files exchanged in test environment. Data quality review. Edge cases resolved (missing SKUs, store hierarchies, supplier data gaps). |
| Phase 4 | Validation & Sign-off Integration validated against live data sample. IT team sign-off. Go-live preparation. |
| Ongoing | Production Monitoring LEAFIO monitors integration pipeline. Alerts on file delivery failures or data anomalies. Your IT team retains access to exchange logs. |
Integration approach, effort, and timeline are scoped individually during pre-sales. Discuss your ERP and data setup with our technical team to get an accurate picture for your environment.
5. IT Requirements by Integration Model
What your team needs to prepare by model
Typical IT-side prerequisites for a LEAFIO integration. Exact requirements are confirmed during technical discovery.
Standard Integration
- Ability to connect to LEAFIO-provided SFTP server or S3 bucket (credentials and endpoint provided during onboarding)
- Ability to schedule ERP data exports (daily or more frequent) and deliver them in agreed CSV format
Custom Integration
- ERP user account with read access to relevant data entities (sales, stock, orders, product master)
- Write access for order output if LEAFIO is pushing replenishment orders back to your ERP
- Network firewall rule to allow outbound connection to LEAFIO's integration endpoints
LEAFIO provides an IT Integration Checklist and network requirements document during pre-sales. Specific effort and readiness time vary by environment and are scoped during technical discovery.
6. Integration Security
Encryption and access control (both models)
- All file transfers use SFTP (SSH-encrypted) or HTTPS for S3; no unencrypted channels
- LEAFIO integration endpoints accept connections only from authenticated clients
- IP allowlisting available for additional perimeter control
- Access credentials rotated on a defined schedule and stored in LEAFIO's secrets management system
- Integration logs retained and available to your IT team for audit purposes
- Data exchanged is limited to operational scope; no customer PII transferred outside agreed scope
For full security and data handling documentation, see Security compliance or request a technical pre-sales call via Contact us
7. Integration Questions & Pre-Sales Support
Our integration and pre-sales engineering team is available to review your technical stack before you commit to a demo.
We can provide
|
Get in touch
Request a technical pre-sales call via Contact us Typical response time: 1 business day |
