record per partner
Shared by BPI, MFT, IDP and Edge, so nothing drifts.
TRADING PARTNER MANAGEMENTSHARED MASTER DATA
Define a partner once. Reference it everywhere.
Trading Partner Management is the spine of CINTAP Orbit: one tenant-scoped record for every customer, supplier, 3PL and carrier, referenced by every process flow, MFT endpoint, document pipeline and API key you build.
to onboard
Profile, credentials, endpoints and message types in a single pass.
duplicate configs
Change a certificate or contact once and every flow picks it up.
Everything a partner is, in one place.
Identity, EDI credentials, people, connection settings, documents and history live together, so the rest of Orbit only ever has to point at the partner.
IDENTITY
Company & classification
Legal entity, partner type (customer, supplier, 3PL, carrier), industry, and lifecycle status on one master record.
ISA IDS
EDI credentials
Sender and receiver qualifiers for X12 and EDIFACT, kept with the partner so every envelope is addressed correctly.
CONTACTS
People & addresses
EDI, AP and logistics contacts plus billing, ship-to and returns addresses, each with a purpose.
INTEGRATIONS
Connection config
AS2, SFTP, OFTP2, FTPS and API settings that SecureFlow MFT and Orbit BPI read directly.
DOCUMENTS
Guides & contracts
Implementation guides, MSAs and certificates stored against the partner in Orbit Vault.
AUDIT
Change history
Every edit, who made it and when, with financial terms and activity kept alongside.
ONE PROFILE, EVERY PROTOCOL
The record your endpoints already trust.
SecureFlow MFT reads AS2 certificates, SFTP keys and OFTP2 settings straight from the partner. Orbit BPI addresses envelopes from the same ISA IDs. Nothing is retyped.
- Credentials resolved from Orbit Vault at runtime
- Certificate rotation propagates to every endpoint
- Partner-scoped API keys through Edge API Gateway
ONBOARDING
Hours, not months.
Create the profile, attach credentials and endpoints, pick the message types, let MAPR AI draft the mapping and dry-run it. Acknowledgements go live the same day.
- Bulk CSV import for partner books you already have
- Supply-chain partner types out of the box
- Activity log and audit trail from the first edit
ENTERPRISE APPLICATIONS
Your own systems, modelled the same way.
SAP, NetSuite, Salesforce and custom ERPs get an enterprise application record with contacts, permissions, connection links and version history, so internal and partner integrations share one vocabulary.
- Application-level permissions per user and team
- Connection links into BPI and MFT
- External APIs so partners can self-serve their own details
What teams ask about Trading Partner Management
Is TPM a separate product?
It is the shared master-data layer of the suite. Its screens live inside Orbit BPI and SecureFlow MFT, and both read and write the same partner and enterprise-application records.
Can partners update their own information?
Yes. External partner and enterprise-application APIs let partners maintain contacts and download integration specs within the boundary you grant them.
How is partner data isolated?
Every record is tenant-scoped. Credentials are stored in Orbit Vault and resolved at runtime, never copied into flows or endpoints.
From partner profile to first 997 in one sitting.
Watch a partner get created, wired to an AS2 endpoint, mapped by MAPR AI and acknowledged, without leaving Orbit.
GET STARTED NOWOne partner record. Every flow, every protocol.
Stop maintaining the same partner in four systems. Define it once in Orbit and let BPI, MFT, IDP and Edge reference it.