Buyer requirements · 2026
GNet Platform vs GroundSpan
Two different starting points for a TMC ground program: supplier connectivity and booking through established travel channels. Use the requirements below to decide what your workflow needs.
Last verified| Requirement | GNet Platform | GroundSpan |
|---|---|---|
| Booking channels | GNet Platform offers an API for a TMC or OTA booking stack. Native Sabre, Amadeus, Travelport and SAP Concur integrations are not live. | GroundSpan describes GDS and corporate booking tool channels, including SAP Concur, GetThere and Cytric. Confirm the specific channel and commercial availability with GroundSpan. GroundSpan products |
| Supplier relationships | Buyers can browse operators by city, review available profile evidence and request a relationship. Connected partners can exchange reservations through GNet Platform. | GroundSpan says agencies can automate existing vendor relationships and negotiated pricing in its booking system. GroundSpan for agencies |
| Credential evidence | Most operators, including most verified operators, have insurance and licence documentation on file. Documents remain private unless shared. Buyers must confirm each supplier's suitability. | GroundSpan describes preferred supplier and policy controls. Its public product pages do not establish a comparable document-coverage rate; ask what evidence your program can inspect. GroundSpan for corporations |
| Commercial and implementation fit | Discuss buyer-side API scope, supplier onboarding, transaction terms and support responsibilities with GNet before committing. | GroundSpan describes a transactional model for suppliers and tailored client solutions. Request a current quote and implementation plan for your TMC. GroundSpan for suppliers |
Which fits your TMC workflow?
If travelers and agents must book ground directly in a GDS or corporate booking tool, GroundSpan documents those channels and may be the better starting point. Confirm the exact integration, supplier coverage and support model for your account.
If your TMC needs to discover ground suppliers, review available credential evidence and connect its own booking stack through an API, discuss GNet Platform. The products can serve different parts of a program, but this does not imply a native GNet–GroundSpan integration.
Compare an actual market and booking flow with both providers. Confirm who contracts with the performing operator, who handles changes and disruption, and what evidence your team can access.
Test the same workflow with each provider
Choose one real market and a booking/change/cancellation scenario. Record the exact channel, performing supplier, confirmation fields, support owner and commercial terms each provider can deliver for your account. Mark unavailable or unconfirmed requirements explicitly.
Use the ground transportation RFP template to collect comparable responses and the supplier assessment checklist to record evidence. A published capability is a starting point for this evaluation, not acceptance of your particular workflow.
Frequently asked questions
Does GNet Platform connect directly to GDS and corporate booking tools?
GNet Platform offers an API for a TMC's booking stack. Native Sabre, Amadeus, Travelport and SAP Concur integrations are not live. GroundSpan publishes GDS and corporate booking tool channels; confirm the specific integration available for your account.
What supplier documentation can a TMC review through GNet?
Most operators, including most verified operators, have insurance and licence documentation on file. Documents remain private unless shared. Buyers should confirm the evidence available for each supplier and their own approval requirements.
Is there a native GNet Platform and GroundSpan integration?
No native integration between the platforms is represented here. Ask each provider to confirm the booking flow, supplier coverage and support responsibilities for your program.