Quotation input preparation
Structure lane, dates, cargo and service requirements before requesting rate data. Match returned options to the actual request and preserve the information needed by the pricing owner.
Explore this workflowAI Operators · Market rates & pricing intelligence
Bring WebCargo live and contract-rate inputs into quotation workflows. Explore rate comparison, access requirements and pricing controls with Shipflow.
Configured for your environment. Available interfaces, accessible records or data and permitted actions depend on your product, account entitlements and agreed workflow.
Discuss your WebCargo workflowConfigured around your environment. Governed by your SOPs.
Where integration creates value
A rate can look attractive while covering different charges, dates or service conditions from the customer’s request. Quotation work therefore needs the surrounding context: cargo requirements, validity, applicable contract terms and the rules for building the selling price.
This guide focuses on WebCargo as a rate source for Shipflow’s proposed quotation workflow. WebCargo is now presented as Freightos for Forwarders. It remains useful to distinguish these shipment-specific rate inputs from Freightos Terminal market benchmarks, even when the names sit within the same provider family.
Workflow opportunities
Structure lane, dates, cargo and service requirements before requesting rate data. Match returned options to the actual request and preserve the information needed by the pricing owner.
Explore this workflowBring relevant authorized rate inputs alongside tender requirements. Highlight differences between a short-validity offer and the tender period rather than treating one as a long-term commitment.
Explore this workflowFlag unclear charges, missing service conditions or unavailable options for a focused inquiry. Direct carrier outreach remains a separately authorized workflow.
Explore this workflowIllustrative workflow · subject to agreed scope
Illustrative workflow: the team needs to assess authorized rate options before preparing a customer response. Access and supported retrieval must be confirmed first.
Check origin, destination, timing, cargo and applicable weight or service requirements. Ask for missing details rather than returning a misleading comparison.
Use the agreed interface and account. Preserve source references and retrieval context without assuming a previously saved result remains valid.
Check units, currency, charges, conditions and validity. Keep unknown exclusions visible and avoid silently treating unlike rates as equivalent.
Apply only the approved pricing rules, show unresolved differences and route the proposed quote for the required review.
Connection approach
Freightos’s official forwarder platform page describes live-rate access, contract-rate management and API integration capabilities. Those vendor capabilities do not establish the endpoint, data coverage or permissions available to a particular Shipflow deployment.
Confirm the exact module, commercial entitlement and approved retrieval interface with the provider and account owner. Obtain the current API contract before implementing requests, authentication or response mappings. Do not reuse Terminal credentials or a generic Freightos endpoint on the assumption that all products share access.
When the requested interface is unavailable, keep the dependency explicit. An approved export could be evaluated as a different workflow with its own freshness rules; this guide does not propose bypassing login controls or scraping an account without authorization.
Setup requirements
Identify the rate tool and account in use, the data covered and the permitted integration method.
Confirm required search fields, supported rate types, authentication, limits and the meaning of returned fields.
Define currency, charge coverage, validity, service constraints and how a rate becomes an approved selling-price input.
Test missing options, stale results, changed requirements and requests that cannot be compared on a consistent basis.
Control and rollout
Keep a specific rate option separate from a market index, historical cost or estimate. Label each source accordingly.
Apply the account’s permitted-use rules before storing or exposing contract-rate information in a customer response.
Rate-data access does not grant authority to book, accept conditions, change margin policy or initiate payment.
Common questions
Its role here is shipment-specific rate input. Freightos Terminal has a separate guide for market benchmarks and intelligence, so the data roles are not conflated.
No. This page scopes rate retrieval and quotation comparison. Booking would require separate interface access, authorization and completion checks.
Do not assume that. Confirm each product’s account, entitlements and authentication separately.
Preserve the gap and route it to the pricing team. A carrier inquiry or another approved source may be needed; do not fill the gap with an invented price.
Product names identify the systems discussed. This page does not imply vendor certification, partnership or endorsement. Supported actions and the implementation scope are confirmed with your team.
Start with a defined scope
Map the inputs, system access and approval boundaries with Shipflow. Agree on a useful first integration and how to verify its result.
Book a working session