Share the fields customers actually need
Customer users can be given access to selected shipment information such as references, routing, milestones, release status, readiness, delays, and other operational fields configured for their account. When enabled by their logistics team, they can also create shipments using a company-specific intake form, generate a reserved CargoFlow File Number, submit pre-shipment information, and make permitted quote decisions. Internal operational controls remain separate.
Control document visibility shipment by shipment
Internal teams decide which documents are customer-visible. The document workflow is deny-by-default, so a stored file is not automatically exposed just because it exists in the shipment record. This is useful for sharing approved documents such as bills of lading, commercial invoices, packing lists, or delivery documents while keeping pricing and internal material private.
Keep internal financial and operational detail private
CargoFlow separates the customer-facing shipment view from internal billing, margins, activity, file notes, and team controls. Customer access is scoped to the correct organization and customer relationship, with authentication and permissions enforced before data is returned.
Use the portal as an extension of the operations file
Because customer visibility is connected to the same shipment record used by the internal team, release updates, milestones, and approved documents can move outward without requiring a separate status spreadsheet. The team still controls what becomes visible and when.