Cross-tenant consolidations

Two different CargoSurge tenants can share a consolidation: one tenant's booking rides under another tenant's master booking. This article covers the invitation flow, the data visibility rules, and when to use it vs a regular vendor relationship.

Overview

A cross-tenant consolidation lets Tenant A (the house booker) push an individual house booking to Tenant B (the consolidator / NVOCC partner), where it's attached to Tenant B's master booking. Both tenants see their respective sides of the deal without seeing the other's commercial terms.

Use case: you have a customer shipping LCL Dubai → New York, but you don't run your own LCL consol. Your partner NVOCC (also on CargoSurge) consolidates every week. Instead of faxing them the details, you push the booking — they pick it up on their side automatically.

When to use

Use cross-tenant consolidation when:

• Both tenants are on CargoSurge (otherwise it's just a normal vendor relationship).
• You're the house booker and your partner is the NVOCC.
• You want your customer-facing side to stay with you (your quote, your invoice) while the physical freight is executed by your partner.

Don't use it for:

• Simple vendor relationships where you buy space from a carrier — that's just a vendor + AP bill flow.
• Co-loading where neither tenant is the NVOCC — that's two peers, not a consolidator.

Setup — the partnership

1. 1
   Tenant A opens Settings → Partner Tenants → + Invite Partner. Enters Tenant B's tenant code or contact email.
2. 2
   Tenant B receives an invite email and a notification on their dashboard. Admins on Tenant B review + accept.
3. 3
   Once accepted, a Partner record exists on both sides. Neither tenant can see the other's data yet — the partnership is just an opt-in to future cross-tenant pushes.
4. 4
   Each tenant can configure what data fields the partner is allowed to see on shared bookings (minimum: cargo specs + pickup/delivery; maximum: everything).

Pushing a house booking

Tenant A has a booking they want Tenant B to consolidate:

1. 1
   Booking detail → Push to Partner Tenant. Pick Tenant B from the dropdown.
2. 2
   Pick the target Master Booking on Tenant B's side (Tenant A can see a list of Tenant B's open masters going the same lane).
3. 3
   Review the data that'll be shared (per the partnership settings).
4. 4
   Click Push. Tenant A's booking gets a cross-tenant flag; Tenant B receives a new sub-booking on their master.

Tenant B can accept or reject the pushed sub-booking. On accept, the sub-booking attaches to the master and participates in the consol manifest.

Data visibility rules

Tenant A sees:

• Everything on their house booking.
• Tenant B's master reference (MBL number, vessel, voyage).
• Tenant B's published ETD / ETA (if shared).
• Their own commercial terms with their customer (unchanged).

Tenant A does NOT see:

• Tenant B's other sub-bookings under the master.
• Tenant B's cost-side buy rates.
• Tenant B's other customers.

Tenant B sees:

• Cargo specs of the pushed house (per partnership settings).
• Tenant A's tenant name + partner reference.
• Tenant B's own master and consol manifest.

Tenant B does NOT see:

• Tenant A's customer identity.
• Tenant A's sell rates to the customer.
• Tenant A's other bookings.

Commercial settlement between partners

Tenant A pays Tenant B for their slot under the master. Two options:

• AP / AR flow — Tenant B invoices Tenant A as a vendor. Tenant A records the AP bill against the cross-tenant booking. Same as any vendor relationship.
• Net billing (monthly) — Tenant B generates a monthly statement of all pushed sub-bookings; Tenant A pays in one wire. Good for high-frequency partnerships.

Either way, the platform doesn't auto-settle — accounting is between the two tenants.

Common pitfalls

Ending a partnership

Either tenant can end the partnership from Settings → Partner Tenants → Remove. Existing cross-tenant bookings stay (can't retroactively unshare); no new pushes can happen after removal.