NETWORK

Suppliers, clients, logistics, financiers — all in your record. Free.

Trade is a network sport. Your factory in Penang updates production. Your forwarder in Rotterdam logs the customs clearance. Your client in Munich approves the order amendment. Your financier underwrites on live cargo data. In EDMA, every party works inside your record — not via email, not via portals bolted on, but as first-class participants. Free seats included on every plan. Every counterparty added is one less email thread to chase.

Book a demoTour the 5 portals

Portal kinds

Supplier, Client, Logistics, Financier — one shared record

Free seats

12 included on Starter, unlimited on Enterprise

Data isolation

Service-layer enforced — not a UI toggle to misconfigure

Operator control

The operator is the hub — full visibility, no counterparty sees another

RD-2026-018Medical examination gloves · nitrile · 4,000 ctn$560,000 · CIF Hamburg·ETA May 26·stage · Production
5parties activerefreshed 11s ago
SupplierPortal · mobile

Crescent Manufacturing

Penang · Malaysia · MY-301

LotPL-2026-071
Qty4,000 ctn
StageQC · day 3 / 5
End client▓▓▓▓▓▓▓
Sell price▓▓▓▓▓▓
Sees · their lot7 langs
LogisticsPortal

Cargolink Forwarders

Rotterdam · NL · 3PL-118

BOLCSCO-PKL-9482
VesselCOSCO BREMEN
Customscleared · 02:11
ModalOcean · FCL 40HC
Goods value▓▓▓▓▓
Sees · BOL onlyvia TMS API
★ Main Portal

Operator · the hub

Vela Exports SA/ full record

All five parties active · live · isolation enforced

Order value

$560,000

CIF Hamburg · INCO 2020

Buy / Sell

$418 → $560 /K

all-in landed cost · operator only

Documents

14 / 16

CO & CIQ pending · supplier upload

Comms thread

38 msgs

3 langs · auto-translated · 1 unread

Parties on this order5 active · each scoped at service layer
★
Vela Exports SA — youOperatorthe hub
SEESeverythingActive
S
Crescent ManufacturingSupplierPenang · uploading QC · lot 3 of 5
SEEStheir lot only9:42
L
Cargolink ForwardersLogisticsRotterdam · customs cleared 02:11
SEESBOL data2:11
C
Brevin Health EUClientMunich · reviewing amendment v2
SEESorder detailPending
F
ACME FinancialsFinancierunderwriting on live cargo data
SEESops + riskQ3 2026
Margin · operator only$142,000 · 25.4%
never visible to client · supplier · forwarder
ClientPortal · branded

Brevin Health EU

Munich · DE · procurement

OrderPO-MH-44218
Value€516,000
IncotermCIF Hamburg
ETAMay 26
Supplier▓▓▓▓▓▓▓▓
Cost basis▓▓▓▓▓▓
Sees · order detailvela.exports/meridian
FinancierPortal

ACME Financials

London · UK · underwriting

Facility$3.0M revolving
Drawn$1.84M · 61%
Cargo signalon-water
DSO 90d37 days
Risk scoreA− · stable
Sees · ops + riskQ3 2026

The operator is the hub. Each party sees only their own relationship.The operator sees everything.

THE PROBLEM

Your network is doing the work. Your system is not in the room.

Three ways operators try to make a network of counterparties work today — and three reasons all three quietly break.

PROBLEM 01

Your network lives in email and WhatsApp, not in your system.

Production status from the factory: WhatsApp. Customs update from the forwarder: email. Order amendment from the client: WeChat. You spend 11 hours a week consolidating into your spreadsheet — and the spreadsheet is wrong by Tuesday afternoon.

PROBLEM 02

Bolt-on portals create more work, not less.

You bought a supplier portal, a client portal and a freight platform. Three logins for them. Three sources of truth for you. The integrations between them are partial, and the source-of-truth data still lives in your head — which means it doesn't live anywhere a team can use.

PROBLEM 03

Every counterparty wants something different.

Suppliers need Mandarin, mobile-first, factory-floor UX. Clients need procurement-style approvals and self-serve docs. Forwarders need API integration with their own TMS. Financiers need portfolio views. One generic portal doesn't fit any of them well — so none of them log in.

FOUR PORTALS · ONE PLATFORM

Four reality-tuned counterparty portals. One shared record underneath.

A factory line-lead and a CFO at a buyer don't want the same product. EDMA ships four counterparty interfaces — plus the operator's Main Portal as the hub — all sharing one data model and one isolation engine. Tuned UX, common spine.

PORTAL · 01

SHIPPING

Supplier Portal

Your factories, contract manufacturers and raw material providers — the people whose phones light up on the production floor.

Mobile-first. Built for the factory floor — one-thumb, photo-first.

7 languages at v1 — including Mandarin and Vietnamese. 中文VNID

Performance scorecard visible to the supplier — the same numbers you see.

Learn more →

PORTAL · 02

SHIPPING

Client Portal

Your end buyers — procurement leads at hospitals, retailers, distributors. The people who pay you.

Desktop-primary — enterprise procurement workflows, inline approvals.

Operator-branded — your logo, your colors, custom domain. Business+

Self-serve docs, one-click payments, amendment history they can audit.

Learn more →

PORTAL · 03

SHIPPING

Logistics Portal

Your forwarders, 3PLs and customs brokers — the people who already have a TMS and don't want a second one.

Coordination layer, not replacement TMS — interops with their systems.

Modal-adaptive — ocean, air, truck, rail, express. OCEANAIRRAIL

Mobile-necessary at ports and docks — milestone updates from the deck.

Learn more →

PORTAL · 04

Q3 2026

Financier Portal

Your trade finance partners — factors, LC banks, marketplace lenders. Underwriting on operational data, not 4-page PDFs.

Portfolio view across operators — exposure, DSO, concentration.

Marketplace + externally-sourced deal tracking, side by side.

Live cargo data drives underwriting — not a paper bill of lading from last week.

See the Financier Portal →

FREE SEATS · BY TIER

Your counterparties don't pay. You pay for the platform; they participate.

Every paid plan includes external seats — supplier, client and logistics — across the four portals. Most operators stay inside their tier. Pricing scales with you, not with how many factories you talk to.

StarterSoloBusinessEnterprise
Supplier seats51550Unlimited
Logistics seats2520Unlimited
Client seats51575Unlimited
Total free1235145Unlimited

$9/seat above the included count. Most operators stay inside their tier — Business at 145 free seats covers an operator with 50 suppliers, 20 forwarders and 75 clients on a single record. Financier seats follow the same network-seat model when the Financier Portal launches in Q3 2026: operator-invited financiers are free, always; self-signup financiers pay the same operator subscription, scaled by order volume.

COMMERCIAL SURVIVAL RULE

The hub sees everything. Each party sees only themselves.

This is not a privacy preference. This is the commercial reason the operator exists in the first place. If Walmart can talk to your factory, you stop existing. EDMA's data isolation is built like a bank's account boundary, not like a folder permission you can flip.

Order RD-2026-018 · service-layer viewENFORCED

Supplierlot_idqtyqc_photosend_clientsell_pricemargin

Logisticsbolincotermmilestonesgoods_valuesuppliermargin

Clientorder_valueetadocssuppliercost_basismargin

Redaction · at the API · not the UI→ 0 misconfig surface

"I am Pendrew Energy. Walmart orders from me. Three factories produce for me. Two forwarders ship for me.

Walmart must never know about my factories. My factories must never know Walmart is the end buyer. My forwarders must know only what is on the bill of lading.

I am the one who knows everything, and that is the whole point."

— PORTAL ARCHITECTURE SPEC · §2.1

How EDMA enforces it

EDMA enforces this at the service layer, not in the UI. A client query for order detail returns a redacted view. A supplier query for shipment data returns only their lot. A forwarder's BOL lookup never includes goods value.

The architecture carries the complexity — your counterparties just see clean, relevant data. There is no permission matrix in Settings to misconfigure, no "share with" button to click by accident, no edge case where a CSV export leaks the margin. The redact() happens before the row leaves the database.

THE NETWORK BUILDS ITSELF

Every supplier added is reachable by every other operator on EDMA.

Counterparties don't belong to one operator. They have one identity across the platform, with data isolation enforced between operators. The first operator does the onboarding work — every operator after that gets a one-click invitation.

FOR YOU

Onboard once. Re-use forever.

Onboard a new supplier once. They're live on the platform with their identity, KYB documents, scorecard history. Next time you find another supplier, check if they're already on EDMA — they likely are, and onboarding is one click.

FOR THE NETWORK

The trade industry's shared trust layer.

Every supplier invited by one operator joins the EDMA-wide supplier directory — opt-in, identity-protected. Identities verified once; performance signals shared (with consent) across operators. At scale, the platform becomes the trade industry's shared trust layer.

Verified suppliers

1,847across 9 countries

Identity, KYB and sanctions screening done once at platform level — re-used by every operator that engages them.

Logistics partners

423forwarders · 23 corridor lanes

From global forwarders to local customs brokers in Felixstowe and Long Beach. Every corridor an operator uses adds breadth for the next operator.

Onboarding time

4minutes · already on EDMA

vs. 18 minutesfirst-time. By month 12, the median onboarding for new counterparties has dropped to 6 minutes.

AI · ACROSS EVERY PORTAL

Atlas, Bot Studio and the AI suite work across the network — not just inside the Main Portal.

An AI tool that only works in the operator's app is a productivity feature. AI that reaches the supplier in WhatsApp, the client in their procurement workflow and the forwarder's TMS — that's a network advantage.

AATLAS · ACROSS PORTALS

Atlas answers supplier questions in WhatsApp — in their language, with full order context.

A factory supervisor in Penang messages your supplier WhatsApp number at 23:48. Atlas answers in Bahasa Melayu, with the full operational context of their lot only, isolation enforced — and writes the supervisor's answer back into the operator's record.

▶ SUPERVISOR · 23:48 · WhatsApp  "Lot 3 QC pass ka?"▶ ATLAS (BM)  "Lot PL-2026-071/L3 — lulus QC. Sila muat naik 6 gambar bagi lot 4. Jadual hantar Jumaat 16/5."→written toPL-2026-071 · 11s

BBOT STUDIO · ON THE EDGE

Bots act on incoming counterparty updates — auto-acknowledge, flag, escalate.

A bot you built in Bot Studio watches the Supplier Portal stream: auto-acknowledges QC uploads, flags exceptions against thresholds, drafts the customer notification, and only pings a human when judgement is required.

▶ BOT  qc-photo-watcher→4 lots ack'd ·no human action→lot 3 photo 5 ·defect detected→drafted note to Brevin ·held for sign-off

LLEGAL AI · CROSS-PORTAL

Contracts shared in any portal arrive with operational context attached.

A supplier uploads a revised MSA via the Supplier Portal; the client sends a redlined PO amendment via the Client Portal. Legal AI reviews both — with the full deal context on the operator's side, redacted views on each counterparty's side.

▶ LEGAL AI  MSA v3 · Crescent Mfg→§7.2 liability captightened −$200K→§11 jurisdiction ·MY → SG · neutral→reviewed onRD-2026-018 context

$ACCOUNTING AI · RECONCILES ACROSS

Payment confirmations reconciled across every portal and channel.

The WhatsApp "PAID" from the supplier's finance team + the Stripe webhook from the client + the bank notification — all link to the same invoice on the same order, in the same record, in seconds.

▶ ACCOUNTING AI  INV-2026-114 · $186K→Stripe webhookmatched 02:47→Mercury notificationmatched 02:51→Brevin WhatsApp "paid"matched→reconciled ·posted to ledger

COMPARE

Bolt-on portals, procurement suites, generic chat. None of them is built for the operator-as-hub.

Five honest reference points trade operators have actually tried — and where each one falls short of the operator-hub model.

CapabilityTradeOSBolt-on partner portalsProcurement suitesGeneric collaborationCustom-built internal
4 portal kinds tuned to each counterparty's reality✓ 5 portals1 generic kindsupplier-only— same UI for allDIY · partial
Cross-tenant data isolation at the service layer✓ redact() in APIUI-onlytenant-level— share & pray— hard to do right
Free seats included on every paid plan✓ 12 → unlimited— per-seat for all— per-seatguests✓ in-house
Operator-branded (your logo, your colors, custom domain)✓ at Business+vendor brandingSAP/Coupa branded— Slack/Google branded✓
Mobile-first for suppliers + logistics; desktop for clients✓ per portaldesktop only— desktop onlymobile chatDIY
Multi-language at v1 (Mandarin, Vietnamese, +5)✓ 7 langsEN + 2✓ 12+✓ many—
Network effect — onboarded once, reachable across the platform✓ 1,847 verified— closedAriba network——
Native integration with AI products (Atlas + Bots + Legal + Accounting)✓ across portals—vendor AIadd-on bots—

Procurement suites are built for one role — the procurement officer at the buyer — and treat suppliers as data sources. Bolt-on partner portals make the operator pay for a separate product per counterparty type, each with its own data silo. Generic collaboration tools work, until margins leak in a shared Drive folder. Custom-built tools are accurate the day they ship, and out of sync six months later. EDMA's bet is that the operator is the hub — and the network is built around that hub from day one, not bolted on afterwards.

FAQ

Frequently asked questions

The questions a head of operations asks the first time we show them how four portals share one record.

No. Free seats are included on every paid plan — 12 on Starter, up to unlimited on Enterprise. You pay for the platform; they participate free. Above the included count, additional seats are $9/month each, billed to you. You never present a price to a counterparty.

See your factory, your forwarder and your client working inside one record.

Book a 30-minute demo. We'll set up a sandboxed workspace with a Supplier Portal for a fictional factory, a Logistics Portal for a fictional forwarder and a Client Portal for a fictional buyer — and walk you through the same order from all four sides. You'll see exactly what each party sees, and why none of them can see what the operator sees.

Book a demoBook a demo

See pricing & free seats per tier →

PRICINGFree seat allowances per tierThe full pricing matrix — Starter through Enterprise — with included supplier, logistics and client seats, plus add-on seat pricing.See pricing →PRODUCTMain Portal — the operator's viewThe operator's cockpit. The hub. The view that sees everything the four portals see, plus the parts they can't.Open product →
Network — Suppliers, clients, logistics, financiers in one record | TradeOS