Overview
The Trade Partners area of the Admin Portal is where organisations configure, manage, and monitor their B2B partners, external companies who are authorised to book or sell tickets through the Trade Partner Portal, the Public API, or both.
Correct setup ensures:
- Partners see only the products and pricing intended for them
- Commissions are applied accurately and consistently
- Billing and settlement remain clean and auditable
- Each partner has secure, controlled access
- Distribution channels can scale without operational risk
A Trade Partner consists of:
- Business details & access configuration
- Addresses for business & finance
- Product and add-on permissions
- Commission rules
- User accounts
- API credentials
- Integration settings for invoicing (Efinancial)
- Reporting classification fields
The Trade Partners module is a key part of Expian’s revenue, distribution, and operational ecosystem — helping organisations extend reach while maintaining governance and financial integrity.
Why It Matters
Proper configuration of Trade Partners ensures:
- Accurate billing & reconciliation: commissions, fees, and revenue splits remain correct
- Secure access: partners can only view and book the products they are permitted to
- Consistent pricing: prevents leakage, over-discounting, or incorrect commissions
- Channel compliance: bookings follow the right terms, amendment fees, and date restrictions
- Operational oversight: partner performance can be monitored via reporting and integrations
- Scalable distribution: you can add new partners quickly and reliably without risk
In short:
Well-configured Trade Partners = controlled distribution + clean finance + trusted reporting.
Trade Partners Section
1. Trade Partners List
(Admin Portal → Trade Partners)
This is the main landing page for all partner accounts.
From here you can:
- View all existing partners
- Search for a partner
- Edit a partner
- Add a new partner
- Navigate to global Trade Partner Settings
- Use pagination arrows to browse long partner lists
Screenshot Placeholder:
Callout Example:
See Screenshot: Trade Partners List — highlight 'Add a New Trade Partner'.
2. Settings (Global Partner Configuration)
These options apply to all trade partners, regardless of individual settings.
Screenshot Placeholder:
Features
Enable or disable features available to every partner.
Ticket prices with donations
Option to include or exclude donation amounts when showing prices.
Trade Partner Portal Visibility
- Hide Prices: prevents partners from seeing prices in the portal and confirmation emails
- Useful for B2B relationships where pricing is managed offline.
Callout:
See Screenshot: Settings, 'Hide prices in the trade portal and emails'.
3. Creating or Editing a Trade Partner
Description Tab
This defines the core business profile and access rules for the partner.
Screenshot Placeholder:
Fields
- External ID
- Required for API integrations
- No spaces permitted
- Name
- Display name shown in the Admin Portal and Portal
- Website(optional)
- Trade Partner Access
- Trade Partner Portal
- API
- Both
- Partner Status
- Active
- Inactive
- Suspended
- Payment Methods
- Credit Card
- Invoice
- (client-specific methods may appear)
- Trade Partner Markets
- Which markets the partner is authorised to sell in
4. Addresses Tab
Used for storing Business and Finance contact details.
Screenshot Placeholder:
Two separate address types:
- Business address
- Finance address
Both sections include:
- Contact name
- Address lines
- City
- Country
- Postcode
Accurate address data supports invoicing, audit, and contact management.
5. Product Commissions Tab
This is one of the most important areas.
It determines:
- Which products and add-ons a partner can sell
- What date ranges they can transact in
- What commission rate they receive
- Whether commissions apply to transaction date or travel date
- What cancellation/amendment terms apply
Screenshot Placeholder:
Commission Groups
Commission Groups allow multiple, independent configurations.
Each group contains:
A. Access Settings
- Portal
- API
- Both
B. Permissible Products
Select exactly which products the partner may sell.
C. Permissible Add-ons
Optional or mandatory add-ons the partner can sell.
D. Valid Date Ranges
For controlling when:
- Orders can be created
- Travel can take place
Useful for seasonal partners or restricted sales windows.
E. Commission Rates
Screenshot Placeholder:
Options include:
- Percentage (%)
- Fixed amount
Applied based on either:
- Transaction date, or
- Visit/Travel date
F. Cancellation & Amendment Terms
These are linked to predefined Terms & Fees configured in:
Admin Portal → Building Blocks → Terms & Amendment Fees
This ensures consistent financial rules.
6. Users Tab
Trade Partner accounts may have multiple users.
Screenshot Placeholder:
Add New User
Fields include:
- First Name / Last Name
- Phone
- Enable User
- Primary Contact
- Address details
When created, users receive an automated verification email through the authentication system
(as described in Trade Partner User Setup for Local ).
7. API Credentials Tab
For partners using automated integrations.
Screenshot Placeholder:
Two credential types:
- OAuth Client Credentials
- Client ID
- Client Secret
- Shown only once
- Static API Key
Removing credentials will disable API access permanently until re-issued.
8. Integrations Tab (Efinancial / Invoicing)
Though labelled Integrations, this tab currently presents Invoicing settings.
Screenshot Placeholder:
Business Type
High-level category such as:
- Tour Operator
- Travel Agent
- Group Organiser
- etc.
Business Subtype
A detailed descriptor (full list shown in screenshot), including:
- Coach Operator
- DMC
- Group Handler
- Hotel
- Sightseeing
- Student Importer
- …and many others
WHERE/HOW ARE THESE SET UP?
EFIN
A billing reference used for interfacing with Efinancial or other invoicing systems.
Self Billing
Indicates whether invoices are generated by the partner or the organisation.
Direct?
Flags direct billing relationships.
9. Reporting Tab
Simple classification fields used to group or filter partner data inside your reporting suite.
Screenshot Placeholder:
Includes:
- Reporting Code 1
- Reporting Code 2
These fields are optional but recommended for finance categorisation.
Best Practice
- Use consistent External ID naming (e.g.,
TP_ABC_TRAVEL) - Always confirm permissible products when onboarding a partner
- Review commission windows and date ranges annually
- Keep at least one Primary Contact per partner
- Disable unused or old users to maintain security
- Test portal or API access after major configuration updates
- Use Reporting Codes to simplify financial reconciliation
Feature Highlights
| Category | Feature | Description | Why It Matters | Example |
|---|---|---|---|---|
| Access | Partner Access Controls | Define whether a partner uses Portal, API, or both | Ensures correct channel behaviour | API-only aggregator receives programmatic access |
| Products | Permissible Products | Controls what each partner can sell | Prevents unauthorised product distribution | Restrict partner to Admissions only |
| Add-ons | Permissible Add-ons | Controls optional and fixed add-ons | Ensures correct upsell availability | Allow partner to sell audio guides |
| Commissions | Commission Groups | Independent sets of commission & product mappings | Supports complex commercial agreements | School groups vs retail partners |
| Commissions | % or Fixed | Commission type selection | Ensures correct commercial model | 10% or fixed £2 per ticket |
| Finance | Cancellation & Amendment Terms | Links partner to terms configured in Building Blocks | Aligns rules across all channels | School groups use bespoke amendment terms |
| Users | Partner User Accounts | Manage portal users | Maintains secure, auditable access | Add multiple staff from same partner |
| API | OAuth / API Key | Programmatic access for integrations | Enables automated bookings | High-volume aggregator integration |
| Integrations | Business Type/Subtype | Classifies financial relationships | Supports invoicing workflows | “Tour Operator – Coach Operator” |
| Reporting | Reporting Codes | Categorise partner in BI tools | Cleaner reporting and finance grouping | Code 1 = Wholesale, Code 2 = UK |
Summary
The Trade Partners module enables organisations to extend their sales channels securely and efficiently. By configuring:
- Access
- Products
- Commissions
- Users
- API credentials
- Invoicing integrations
- Reporting mappings
you maintain strong governance, accurate finance, and scalable distribution.
A well-configured partner ensures seamless operations, correct revenue capture, and a trusted relationship across both B2B and automated booking channels.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article