Review interfaces, deployment boundaries and operating responsibilities alongside the business process, with current assurance materials for your evaluation. SPICE™ sits between your ERP and every trading partner, and your ERP stays the system of record.
Platform overview / Security and integrations
Security and integrations
Review SPICE™ interfaces, deployment boundaries and operating responsibilities alongside the business process: EDI, APIs, IDocs, AS2, SFTP and files, native middleware, SaaS or BYOC, and current assurance materials.
Fit the platform to your enterprise environment.
Work with your existing systems
Supported REST APIs, SAP IDocs and files connect your ERP, WMS, TMS and existing B2B infrastructure. SPICE™ is ERP-agnostic: it receives transactions from your trading partners, validates them and delivers ERP-ready data, and it takes purchase orders, confirmations, shipment notices and invoices from your ERP and delivers each one in the format and channel the trading partner can use.
Native middleware. SPICE™ maps, validates, translates and routes X12, EDIFACT, IDoc, XML, JSON, CSV and flat-file formats, so trading partners don’t have to change the format they send. Each transaction is checked for completeness and format, then against your customer, supplier, location and item master data, the original order and your business rules. Problems become exceptions for review instead of errors in your core systems.
How SPICE™ connects
- EDI X12 and EDIFACT transactions for procure-to-pay, order-to-cash, transportation and warehouse processes.
- APIs REST APIs for system-to-system integration with your applications and API-capable trading partners.
- Secure file transfer AS2 and SFTP connections with trading partners and enterprise systems.
- Enterprise systems ERP, WMS, TMS and PIM applications, including SAP IDocs, plus existing EDI, VAN and B2B infrastructure where you keep it.
- Non-EDI channels Web portals, PDFs, email and spreadsheets, through SPICE Web OMS™, SPICE Trade™ and SPICE Digital Document Service™.
Because every channel feeds the same validation, a PDF order from one customer and an EDI order from another reach your ERP in the same structure. Your integration team maintains one set of rules instead of one per channel. When an AS2 connection fails or a certificate expires, the SPICE™ team diagnoses it with the trading partner and coordinates the fix. See managed services.
Two deployment models
- SaaS: Azure microservices support the shared platform delivery model. Scope data boundaries, configuration and interfaces in the architecture review.
- BYOC (bring your own cloud): a dedicated single-tenant SPICE™ environment inside your Azure subscription or AWS account, with Azure Government where required.
See deployment options.
Ask for the evidence your review requires
- Role and access design, transaction auditability and business approval rules
- Isolation, encryption, monitoring, backup and incident-response responsibilities
- Current assurance reports and detailed control materials under the appropriate review process
- Data access and governance for embedded SpicY™ and document workflows
Review current assurance materials and the controls applicable to your chosen environment with SPICE™.
Built for change
Because SPICE™ separates your trading partners from your enterprise systems, changes on either side are easier to manage. An ERP migration, an acquisition or a new business unit can connect to the same trading partner program without rebuilding every connection.
The SPICE™ platform
One platform between your ERP and every trading partner
Suppliers, customers, carriers and 3PLs connect through one governed platform, with your ERP as the system of record. Select any part to explore it.
Your ERPWMS · TMS · OMS stay the system of record
FAQ
Frequently asked questions
What is EDI integration?
EDI integration connects your business systems, usually your ERP, with your trading partners' systems so orders, shipment notices and invoices flow automatically. SPICE™ handles the full path: it exchanges EDI with trading partners, translates and validates each transaction against your master data and rules, and delivers ERP-ready data to your systems, with exceptions flagged for review.
Which ERPs does SPICE™ integrate with?
SPICE™ is ERP-agnostic. It connects through EDI, REST APIs, SAP IDocs, XML, JSON and flat files, so it can work with the ERP you run today and the one you move to later. Your ERP stays the system of record. The specific interfaces for your environment are confirmed during an architecture review.
Does SPICE™ support AS2 and SFTP?
Yes. SPICE™ exchanges transactions with trading partners and enterprise systems over AS2 and SFTP, alongside APIs. When a connection fails or a certificate needs renewal, the SPICE™ team works with the trading partner to diagnose and fix it.
How do we review SPICE™ security?
Through your normal security and architecture review. The SPICE™ team covers access design, auditability, isolation, encryption, monitoring, backup, incident response and data governance for your chosen deployment model, SaaS or BYOC, and provides current assurance materials through the appropriate process.
Talk to a platform specialist
Review the interfaces and deployment boundaries
Walk through your architecture, interfaces and security requirements with the SPICE™ team.