INTEGRATIONS
Trade operations span dozens of systems — accounting, CRM, freight, customs, banking, document storage, messaging, business intelligence. TradeOS connects to all the major ones, plus many specialized tools. Native integrations require no engineering work; custom integrations are part of Enterprise scope. Every connection runs bi-directional with auditable data flow.
Native integrations
60+across 10 procurement-vocabulary categories · alphabetical within each
Protocols supported
RESTGraphQLWebhooksSFTPfive reusable patterns documented in §4 · auth, retry, signing all covered
Development scope
Custom at Enterprise3 custom integrations per year included · EDMA engineering builds + maintains
WHAT EACH INTEGRATION PAGE COVERS
Every card above links to a dedicated page following this template — so the format is consistent whether you're evaluating Xero or HSBCnet. The visible wireframe on the right is the exact sectioning your team will see at /integrations/<slug>.
TEMPLATE · APPLIED TO ALL 80 PAGES
Procurement, IT, and developers each read different sections of the same page. The template separates them cleanly — security review reads Capabilities + Limitations; IT reads Setup; engineering reads Support & docs. Nobody has to scroll past the wrong content.
Integration name
HOW INTEGRATIONS WORK
Every native integration falls into one of five technical patterns. The pattern determines setup time, authentication model, and data freshness. Most modern SaaS is Pattern 1 (5 minutes via OAuth); banking and legacy ERP are usually Pattern 4 (SFTP); bespoke systems are Pattern 5 (scoped at Enterprise).
Pattern 01
2 – 5 min setup
Best for: modern SaaS with first-class API coverage. Default for anything customer-facing.
Pattern 02
5 – 15 min setup
Best for: service-to-service integrations that offer signed webhook delivery.
Pattern 03
30 min – 2 hr setup
Best for: carrier tracking and regulatory data feeds with no push channel.
Pattern 04
1 – 4 hr setup
Best for: enterprise systems without modern APIs. Requires customer IT involvement.
Pattern 05
2 – 12 wk delivery
Scope: included in Enterprise tier. Quoted scope per integration. EDMA engineering builds + maintains.
BUILD YOUR OWN
If your system isn't in the directory — or you'd rather build than wait — the public API covers the same surface area used by every native integration. OpenAPI 3.0 spec, SDKs in three languages, free sandbox at every tier, signed webhooks for 80+ event types.
Comprehensive coverage of platform data — orders, shipments, documents, finance, communications. GraphQL available at Business+ for efficient nested queries; REST at every tier.
Subscribe to 80+ event types — entity changes, status transitions, threshold crossings. Every payload is signed and delivered with exponential-backoff retry. Replay missed events from up to 7 days back.
Documentation
docs.edma.trade
Public docs · OpenAPI · SDK references · code samples.
Sandbox environment
sandbox.edma.trade
Free at every tier · isolated · resettable.
Status & uptime
status.edma.trade
Per-integration health · public incident history.
SOMETHING SPECIFIC?
Three custom integrations per year are part of the standard Enterprise contract — built and maintained by EDMA's engineering team. Anything outside that scope is quoted separately and stated up front, not buried in renewal.
Eligible for any system with a documented API, file-export capability, or webhook surface — including legacy systems EDMA hasn't seen before.
Quoted separately as Statement of Work · scope, timeline, and acceptance criteria fixed before kickoff.
First step: request a discovery call from the CTA section below — flag "Custom integration" and the system name.
Sage Intacct
Bi-directional sync for orders, financials, GL.
BetaCoupa direct integration
Procurement-to-pay coordination with shipment + invoice match.
BetaEU banking aggregation
Expansion of Open Banking coverage across SEPA + non-Eurozone EEA.
SAP S/4HANA
Bi-directional integration · orders, financials, master data, GL.
Microsoft Dynamics 365
CRM-side bi-directional sync · contacts, accounts, opportunities.
Financier Portal API expansion
Standardized financier-side surface — draw, repayment, reconciliation.
WhatsApp Business · voice + video
Channel expansion beyond messaging to scheduled voice + video calls.
Sage Intacct (GA)
Beta → general availability after Q3/Q4 customer pilots.
Coupa (GA)
Beta → general availability after Q3/Q4 customer pilots.
Carrier API multi-region failover
Resilience layer in front of Pattern 03 carrier polling.
Enhanced GraphQL coverage
Parity with REST surface across all platform domains.
Trade Marketplace v2
EDSD settlement on EDMA L2 · settlement-layer integration.
DirectionalPlugin Marketplace · beta
Third-party builders publishing integrations directly into EDMA.
DirectionalPublic bug bounty program
Coordinated disclosure with payout schedule · cross-listed in /security.
DirectionalRegional banking expansion
LATAM + Africa coverage following the global-network rollout.
DirectionalRoadmap subject to revision based on customer demand and technical feasibility. Specific integration requests can be submitted through the customer success team — high-demand integrations get prioritized for the next quarter and published here at the start of each quarter.
COMMON QUESTIONS
Eight questions, grouped open by default. Answers are short, factual, and link back to the section where the underlying capability is documented.
What if my system isn't listed in the directory?
Three paths. (1) Check the API documentation — many integrations are buildable on the public API (§5) even if not in the directory. (2) Submit an integration request through customer success — high-demand requests get prioritized for the next quarter. (3) At Enterprise, custom integration development is included in scope (§6, three per year).
How long does integration setup actually take?
Depends on the protocol pattern (§4). OAuth-based: 5–15 minutes. API key based: 15 minutes to 2 hours depending on customer IT involvement. SFTP-based: 2–8 hours. Custom: 4–12 weeks. Most operators have all critical integrations live within two weeks of starting setup.
Do integrations require ongoing maintenance?
Native integrations are maintained by EDMA — when a third-party API changes, we update the integration before the breaking change lands. Customer-built integrations using our public API are customer-maintained. Enterprise custom integrations are maintained by EDMA as part of the subscription, including through vendor-side API deprecations.
What happens with data sync conflicts (a record edited in both systems)?
Configurable conflict resolution per integration — choices are last-write-wins (default), edma-wins, external-wins, or manual-resolution. All conflicts are written to an audit log available in-product for review. Most integrations rarely encounter conflicts because entity ownership is established by convention (e.g., invoices owned by accounting system, shipments owned by EDMA).
Can I disable an integration without losing data?
Yes. Disabling pauses sync but retains historical data on both sides — nothing is deleted automatically. Re-enabling resumes sync from the disable point. Permanent deletion of integration data requires an explicit action (90-day retention window before purge, configurable up to 365 days at Enterprise).
What's the SLA on integration uptime?
Integration uptime is constrained by both EDMA infrastructure SLA (99.95% at Business+, 99.99% at Enterprise) and the third-party vendor SLA — we can't be more available than the system we're calling. The status page shows per-integration health, and degradations are communicated proactively. Detailed breakdown in /security.
Are integration costs included in the tier price?
Native integrations: included in all tiers, subject to per-integration tier availability (some Identity / BI integrations require Business+). Third-party costs — Twilio SMS fees, carrier API access fees, premium banking endpoints — are passed through to the customer at cost, with no markup. Custom integrations: included in Enterprise tier scope (§6).
Can I see the full data flow for security review?
Yes. Per-integration data flow diagrams show exactly what data moves in which direction, encryption at each hop, and sub-processor involvement. Diagrams ship as part of the security review package — see /security.
GET CONNECTED
Operators usually start with the directory. Procurement teams usually start with a call. Developers usually start with the docs. Whichever fits — every path leads back to a single integration plan for your workspace.
Filter by category, find your systems, see capabilities and tier availability. Best when you already know which systems you need to connect.
80-integration filterable grid
Per-integration capability sheet
Status & tier badging
Live roadmap snapshot
30-minute scoping call with solutions engineering — discuss specific integrations, custom requirements, or migration scenarios. Best for active procurement.
Per-system fit assessment
Custom integration scoping
Migration plan for legacy data
Tier & pricing walkthrough
Public REST + GraphQL, free sandbox at every tier, 80+ event types via signed webhooks. Best when you want to build instead of waiting for a native integration.
OpenAPI 3.0 spec · 3 official SDKs
Sandbox at every tier
Signed webhooks · 7-day replay
Weekly office hours (Business+)