Quick Overview
A digital freight marketplace can help forwarders reach buyers comparing shipping services, while a branded customer portal supports a direct experience for quotations, bookings and shipment management. Choose according to your commercial priority: attracting demand, serving accounts or both. Compare customer access, pricing controls, integration requirements and the full cost of each channel.
Start with the business problem
Before choosing a platform, identify where your commercial process needs improvement.
If the problem is finding qualified buyers for particular lanes, evaluate a marketplace’s audience, supplier requirements and booking opportunities.
If customers already contact your team but spend too much time requesting quotes, documents or shipment updates, evaluate a branded portal.
Both approaches require reliable pricing and operational service. Publishing rates or launching a portal will not, by itself, create demand or improve delivery performance.
Digital freight marketplace versus customer portal
This comparison focuses on marketplaces where forwarders offer shipping services to buyers. Platforms used primarily to procure carrier capacity may serve a different purpose.
| Decision area | Digital freight marketplace | Branded customer portal |
|---|---|---|
| Primary commercial role | Participate in a shared environment where buyers can discover and compare services | Provide a direct digital service under the forwarder’s brand |
| Finding customers | May provide access to an existing buyer audience | Depends on the forwarder’s sales, marketing, referrals and customer onboarding |
| Pricing | Offers follow the marketplace’s display, eligibility and selling rules | Pricing can be configured for approved customers, segments or public visitors, depending on the product |
| Branding | Presentation follows the marketplace’s interface and seller-profile options | Typically provides more control over the customer-facing identity and experience |
| Customer relationship | Communication, contact access and repeat transactions depend on platform terms | The forwarder manages the direct account relationship, subject to its software and service arrangements |
| Booking and payment | Workflows follow the marketplace’s supported processes | Workflows must be configured around the forwarder’s services, payment options and account rules |
| Documents and updates | Available functions depend on the marketplace and its connected providers | Available functions depend on the portal, integrations and permissions |
| Integration | May require rate publication and booking-data connections | May require connections to rate management, CRM, TMS, tracking and payment systems |
| Costs | Check subscriptions, transaction charges, commissions and service obligations where applicable | Check software, implementation, integrations, payment processing and ongoing administration |
| Success measures | Qualified demand, profitable bookings and service performance | Adoption, repeat bookings, reduced manual work and customer experience |
These are common evaluation differences, not universal limits. A marketplace may support private pricing, and a branded portal may also allow new customers to register.
Finding new customers versus serving existing accounts
When a marketplace deserves consideration
A marketplace may be useful when you want to reach buyers beyond your existing customer base.
Before joining, ask:
- Does its audience buy the modes, lanes and services you offer?
- Can your business meet the supplier eligibility requirements?
- How are offers displayed and selected?
- What response and service commitments apply?
- Which customer details become available, and when?
- How are cancellations, disputes and additional charges handled?
Assess the demand relevant to your business rather than relying on the platform’s overall audience size.
For example, Freightos provides a marketplace for comparing and booking freight. A forwarder considering participation should separately confirm supplier access, commercial terms and the workflows applicable to its services.
When a branded portal deserves consideration
A portal may be useful when existing accounts repeatedly ask your team for information or actions that could be handled through self-service.
Examples include:
- Requesting rates for repeat lanes.
- Accepting a quotation.
- Submitting shipment details.
- Uploading an invoice or packing list.
- Checking shipment milestones.
- Retrieving approved documents.
Customer adoption matters. A portal creates value when customers use it and the information they receive is dependable.
Public offers versus customer-specific pricing
Decide which prices each audience should see before choosing a channel.
A new buyer, a contracted account and an approved agent may require different prices, service options and payment terms.
| Pricing question | What to establish |
|---|---|
| Who can see a price? | Public visitors, registered users, approved accounts or selected partners |
| Which rate applies? | Published offer, account contract, spot quotation or manually approved price |
| What is included? | Freight, local charges, surcharges and clearly stated exclusions |
| How long is it valid? | Quote expiry and applicable shipment conditions |
| Who may override it? | Authorized users and approval requirements |
| What happens if details change? | Recalculation and approval before the customer is committed to revised charges |
Check whether published and private offers can remain separate. Do not assume a marketplace requires every rate to be public, or that a portal automatically protects account-specific pricing.
Ask the provider to demonstrate the experience using two different customer accounts.
Branding and control of the customer relationship
Branding includes more than a logo. Consider the domain, emails, quotation format, booking confirmations and support experience.
A forwarder evaluating either model should establish:
- Which company the customer sees at each stage.
- Who sends transactional communications.
- Who answers operational questions.
- Who handles payment queries and disputes.
- What customer and transaction data can be accessed or exported.
- What happens to records and access when the service agreement ends.
VelocityOS documents branding options, customer-specific access and workflows for quotes, bookings, payments, tracking and documents in its digital freight portal offering. Confirm the configuration and service availability required for your business.
Compare booking, payment and document workflows
Walk through a complete shipment before assessing either option.
Booking
Confirm what happens after a customer accepts an offer.
Does the action create an enquiry, a booking request or a confirmed operational record? What still needs review?
Keep customer acceptance, internal booking creation and carrier confirmation distinguishable. They are not necessarily the same event.
Payment
Ask who collects payment and which payment methods or account terms are supported.
Clarify:
- Whether payment is required before processing.
- How approved credit accounts are handled.
- Which currencies are available.
- How payment references reach finance.
- How refunds and additional charges are processed.
- Which processing or transaction fees apply.
A payment function should be evaluated alongside reconciliation and support responsibilities.
Documents
Check how customers upload, view and retrieve shipment documents.
Test permissions by customer and shipment. Confirm how revisions are identified and whether internal documents remain separate from customer-visible files.
The workflow should make it clear who reviews missing or incorrect information.
Integration requirements: what must connect?
Both approaches can create manual work if bookings and updates remain separate from your operational systems.
| Information | Connection to evaluate |
|---|---|
| Rates and service offers | How prices, validity and exclusions are published or retrieved |
| Customer records | How accounts are matched without creating duplicates |
| Accepted quotes | How the correct version and service scope reach operations |
| Bookings | How requests, confirmations, amendments and cancellations are exchanged |
| Payments | How payment status and references reach finance |
| Shipment events | Which source supplies milestones and arrival estimates |
| Documents | How files, versions and access permissions are maintained |
For each connection, confirm the supported fields, update timing, error handling and responsible team.
Review the available TMS integration options when planning how commercial channels will connect to shipment operations.
Compare fees and operating costs
Request a written cost breakdown for the actual scope you intend to use. Do not assume every marketplace uses commissions or every portal uses only a fixed subscription.
| Cost category | Marketplace questions | Branded portal questions |
|---|---|---|
| Access | Is there a supplier subscription, listing fee or participation charge? | Which subscription, user, customer or usage limits apply? |
| Transactions | Are commissions or booking fees charged, and on what basis? | Are transaction or usage charges additional to the subscription? |
| Payments | Who pays processing, currency-conversion or refund fees? | Which payment provider is required, and what does it charge? |
| Implementation | What is required to publish offers and receive bookings? | What is required for branding, pricing, accounts and workflows? |
| Integration | Are APIs or connectors included? | Which CRM, TMS, tracking and finance connections cost extra? |
| Ongoing work | Who maintains offers and meets service commitments? | Who maintains pricing, users, content and customer onboarding? |
| Customer acquisition | What demand does participation actually generate? | What sales and marketing investment brings customers to the portal? |
| Exit | What records can be exported, and under which terms? | How are customer, quote, booking and document records retrieved? |
Compare contribution after costs, not booking volume alone.
Illustrative channel-cost comparison
The figures below are hypothetical and are not prices for VelocityOS or any marketplace.
Assume each channel handles 40 completed bookings per month, with USD 200 contribution per booking before channel costs.
| Monthly item | Marketplace example | Branded portal example |
|---|---|---|
| Contribution before channel costs | USD 8,000 | USD 8,000 |
| Assumed transaction charges | USD 1,200 | USD 0 |
| Assumed fixed software or access costs | USD 0 | USD 900 |
| Allocated implementation and integration costs | USD 200 | USD 300 |
| Internal channel administration | USD 300 | USD 500 |
| Allocated sales, marketing and onboarding costs | USD 200 | USD 800 |
| Contribution after listed channel costs | USD 6,100 | USD 5,500 |
This example assumes equivalent underlying shipment economics and excludes costs already included in the starting contribution.
The result does not make the marketplace universally better. The portal’s fixed costs would be spread differently at another volume, and the channels may serve different customers.
Most importantly, equal booking volume is an assumption. A portal does not inherit a marketplace’s audience, and marketplace participation does not guarantee bookings.
When both approaches can work together
A forwarder may use a marketplace for selected customer-acquisition opportunities while operating a branded portal for direct accounts.
For example:
- Publish suitable services on a marketplace for eligible buyers.
- Offer approved direct customers their contracted prices through the portal.
- Use a shared internal rate-management process.
- Feed bookings from both channels into the operational workflow.
- Preserve the original channel and commercial terms on each record.
Do not assume customers acquired through a marketplace can be moved to a direct channel without restrictions. Review the applicable agreement before designing repeat-booking or communication processes.
Illustrative combined approach
A forwarder serves regular importers and wants to test demand on a new lane.
Its existing accounts use the branded portal for repeat quotations, documents and shipment updates. The forwarder also publishes selected offers through a marketplace that accepts its services.
The team measures each channel separately:
| Channel | Measures to review |
|---|---|
| Marketplace | Relevant enquiries, completed bookings, contribution after fees and service workload |
| Branded portal | Active customer accounts, repeat bookings, self-service completion and manual follow-up |
| Both | Pricing accuracy, duplicate records, booking handoff quality and operational exceptions |
This helps the forwarder decide where each channel adds value without assuming they serve identical purposes.
Which should your forwarding business prioritize?
| Your situation | First approach to evaluate |
|---|---|
| You need more qualified demand on specific lanes | A marketplace with relevant buyers and suitable supplier terms |
| Existing customers repeatedly request routine information | A branded portal connected to accurate operational data |
| Your business depends on negotiated account pricing | A portal or other channel that demonstrably supports private pricing |
| You need acquisition and account service improvements | A combined approach with clear channel rules and shared operational processes |
| Rates and booking data are inconsistent internally | Improve pricing and handoffs before expanding digital sales channels |
Start with a defined use case and test it with real users. Confirm that a customer can find the appropriate offer, understand its scope, complete the required action and receive a reliable update afterward.
FAQs
No. A portal provides a digital experience, but acquisition still depends on sales, marketing, referrals or other sources of demand. It may support conversion once a prospective customer arrives.
No. Visibility and pricing arrangements vary. Check whether the platform supports registered users, private offers or account-specific agreements.
Yes, where the commercial agreements and operational setup permit it. Keep pricing, customer access, channel attribution and booking records clearly controlled.
Not necessarily. A portal can provide the customer-facing experience while the TMS manages operational shipment records. Confirm how the two systems exchange information.
It depends on transaction volume, fees, implementation, integrations and internal workload. Compare the total cost for your expected usage and the contribution each channel generates.
Test account access, pricing visibility, quote acceptance, booking handoff, payment reconciliation, document permissions and shipment updates. Include a failed transfer or amended booking to see how exceptions are handled.