Partner Portal
Your importer clients (or an enterprise's suppliers) get their own authenticated, client-scoped window into their shipments, documents, entries, and invoices — and the document they upload flows straight into the same document-intelligence pipeline your team works from.
Pilot / design-partner ready. Auth, client scoping, storage, Entry Proof, shipment answers, and onboarding sync are implemented; generated 7501/invoice PDF downloads are still stubs — don't demo that flow. Stored executed POA / accepted 5106 downloads are real.
The problem
"'Send me the commercial invoice.' 'Any update?' 'Resend the invoice?' Every client, every shipment. It's the whole inbox."
Broker
"I have no idea where my shipment is unless I email my broker and wait. I get a PDF invoice with no context."
Broker's client
"Collecting origin declarations and certificates from 200 suppliers is a shared mailbox and a spreadsheet."
Enterprise
How Qubere addresses it
"Ask the customer" request workflow
The broker raises a document/data request against a specific shipment from /app/clients; the customer gets an email, opens it in the portal, and answers or uploads. Status tracked the whole way.
Shipment & entry visibility
Per-shipment status, milestones, and the journey — what the customer would otherwise call to ask. The broker chooses when an entry becomes customer-visible: customerVisibleAt is an explicit publish action, so nothing appears early.
Passwordless, scoped invitations
The broker sends a scoped invitation (/invite/<token>); the customer accepts and is provisioned with access limited to their client and, optionally, specific product scopes. For enterprises: the same mechanism scoped to a supplier and their POs.
| Client scope | Product scopes | Status | |
|---|---|---|---|
| priya@acme.com | Acme Corporation | all | Accepted |
| logistics@acme.com | Acme Corporation | Batteries, Enclosures | Pending |
| old@acme.com | Acme Corporation | all | Revoked |
Entry Proof
Expand a line to see its classification, duty measures, valuation, evidence, and review reason. Unavailable rates stay visible — "data unavailable" is never rendered as zero.
Compliance
A published review snapshot for that client's entries, with a value-weighted score whose underlying lines can be inspected. Savings are potential opportunities that still need broker review.
Compliance Profile
A customer-safe rendering of the same context graph the assistant reasons from — internal findings and jargon are stripped or rewritten before the client ever sees a node. Read-only, scoped to their own account.
At a glance
Arrival estimates, costs, requests, and references come from recorded shipment facts. Unknown clearance timing stays "unknown" rather than being guessed.
Your setup
Company registration, signed documents, bond, and people for the signed-in client share one view. Each client is its own workspace — a different login sees a different setup. The broker still controls invitations.
Broker partnership
Exactly. Entry Proof rides alongside them. The broker approves, publishes, answers questions, and keeps the customer informed.
The security model, plainly
The security model was hardened through a formal review. It's a read + respond surface, nothing more.
Objection handling
| "Is this production-ready?" | Pilot-ready. Auth, client scoping, and object storage are real and were hardened through a formal review. The remaining gap is polished generated-PDF downloads and broader automated two-tenant test coverage — fine for a design partner, worth being explicit about for a large rollout. |
| "Can we brand it per broker?" | The portal uses the Qubere design system today. Custom per-broker branding is a roadmap item, not current. |
| "How do suppliers fit the enterprise story?" | Same mechanism — an invitation scoped to a party and product scopes — used for supplier document and origin-data collection rather than importer status visibility. |
The close
And the document they upload does real work the moment it lands.
Next step: pick one of your clients as a design partner. We stand up a scoped portal, run the "ask the customer" loop on a real shipment, and you see whether it takes email off your team's plate.
Full detail: docs/sales/PARTNER-PORTAL-ENTRY-PROOF-DEMO.md