Partner Portal

"Send me the packing list" becomes
a tracked request they answer.

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.

1
client sees only their own data — enforced server-side
0
entries visible to a client before the broker publishes

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

Half your team's day is "any update?" and "can you resend the invoice?"

"'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

A read-and-respond surface for your clients — scoped, not filtered.

  • The customer sees only their shipments, documents, entries, invoices — enforced on every read path, not hidden in the UI.
  • "Ask the customer" is a request raised against a specific shipment, tracked end to end.
  • A document the customer uploads enters the same parse → extract → reconcile → readiness pipeline as a broker upload, including multi-document detection and split.
  • Entry visibility is an explicit publish action by the broker — nothing leaks early.
  • Passwordless, scoped invitations — access limited to one client and optionally specific product scopes.

"Ask the customer" request workflow

Chasing a document is now a tracked request, not an email thread.

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.

  • The uploaded document does real work the moment it lands
  • Broker sees the request resolve; no "did you get it?"
How to demo
Broker: raise "Upload Bill of Lading" on a shipment. Portal: open the request, upload a file, mark answered. Broker: the request shows resolved — and the doc is on the shipment, processing.
Acme Corporation
PC
Priya · Acme
Upload Bill of Lading — SHP-2026-000144
Requested byJoe (Target Brokerage) · 2 days ago
NoteNeed the MBL to complete the entry — ocean leg.
Commercial Invoice — answered✓ uploaded · now processing on the shipment

Shipment & entry visibility

Your clients stop calling to ask where things are.

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.

  • Shipment, freight, and invoice views — all client-scoped
  • Original documents download; generated-PDF download is stubbed
  • Duty Funds page: the client sees their duty-advance balance, ledger and replenishment requests alongside the shipment
How to demo
Broker: publish a filing to the customer. Portal: the entry now appears under the customer's shipment with status. Contrast a second client's login — totally separate data.
Acme/SHP-2026-000144
PC
Priya · Acme
Journey
✓Booked
✓Origin port
3On vessel
4Dest port
5Customs
6Delivered
Entry QBR-2026-3231902published by your broker · Draft
DocumentsCommercial Invoice, Packing List · MBL requested
Latest invoiceINV-202608-A1 · $4,120.00

Passwordless, scoped invitations

The customer sees exactly what you decide, when you decide.

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.

  • Invitation states: PENDING / ACCEPTED / EXPIRED / REVOKED
  • An invited person who already has a login can accept or decline the invitation in the app; client roles are CLIENT_ADMIN / WRITE / READ
  • When enabled, copy the client email address in Setup or Documents
  • Live address autocomplete on entity confirmation — the customer picks a validated address instead of hand-typing one
How to demo
/app/clients → invite a portal user with a client + product scope → walk the invite-acceptance flow.
Clients/Portal access
JT
Joe · Target
EmailClient scopeProduct scopesStatus
priya@acme.comAcme CorporationallAccepted
logistics@acme.comAcme CorporationBatteries, EnclosuresPending
old@acme.comAcme CorporationallRevoked
Client scope enforced server-side on every read path

Entry Proof

Proof, not just status.

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.

How to demo
Target → Entry Proof → expand a line. Attach a new emailed document in the broker app: the updated proof stays a draft until published.
Qubere PortalIllustrative demo view
Line reviewClassification and supporting evidence
Base duty / 301 / 232Applicability and amounts
AntidumpingData unavailable is not zero
EvidencePublished reference + approved classification
QuestionAsk about line → tracked Actions conversation

Compliance

The compliance scorecard.

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.

How to demo
Compliance → sort by score or identified savings → open an entry.
Qubere PortalIllustrative demo view
ENTRY-TGT-240013 of 4 lines verified · $4,400 savings identified
ENTRY-TGT-24007AT RISK · classification and AD/CVD review
ScoreValue-weighted review coverage
PublicationBroker-controlled version history

Compliance Profile

The knowledge graph, in plain English.

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.

How to demo
Compliance → Compliance Profile → search a supplier name → switch client (multi-entity accounts).
Qubere PortalIllustrative demo view
SourceAssistant knowledge graph · customer-safe view
Hidden from clientOpen findings, internal ids, staleness jargon
SearchFind a supplier, shipment, or classification by name
Route/compliance/profile · read-only

At a glance

Answers, not phone calls.

Arrival estimates, costs, requests, and references come from recorded shipment facts. Unknown clearance timing stays "unknown" rather than being guessed.

How to demo
Open a shipment → At a glance → a customer deadline → Actions.
Qubere PortalIllustrative demo view
ArrivalTwo-day slip · previous estimate retained
CostPublished duty + visible charges · partial when incomplete
ClearanceFDA review in progress
Needs from youCustomer deadline and tracked request
Free timeLast free day · estimated exposure

Your setup

Every stakeholder for that client, one setup view.

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.

How to demo
Target Setup → importer registration, signed POA download, people. Sign in as Amazon → a separate setup with a POA still pending.
Qubere PortalIllustrative demo view
Importer of recordMasked EIN · CBP importer number
Documents on fileStored executed POA and accepted 5106
PeopleSigner and login status
AccessRequest access for someone
Your broker teamAssigned contact

Broker partnership

“We already have a broker.”

Exactly. Entry Proof rides alongside them. The broker approves, publishes, answers questions, and keeps the customer informed.

How to demo
Broker filing → refresh proof → publish → customer opens the new version.
Qubere PortalIllustrative demo view
Generate / refreshCreate a new draft snapshot
Publish to customerReplace the prior published version atomically
QuestionsVersion-linked requests and replies
NotificationsEmail + portal bell, respecting preferences
Boundaries7501 / invoice generated PDFs remain stubs

The security model, plainly

What the customer cannot do.

  • See other clients' data — client scope is enforced server-side on every read path.
  • Every portal request is scoped to the authenticated client; a missing or invalid scope fails closed — empty results, never a fallback to cross-tenant data.
  • See unpublished entries — visibility is an explicit broker action.
  • Take compliance actions or reach the broker's internal workspace.
  • Access anything through a guessed URL — the portal is a separate origin with its own auth.

The security model was hardened through a formal review. It's a read + respond surface, nothing more.

Objection handling

Every hard question, answered directly.

"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

"The two questions your clients ask all day — where is it, did you get my document — answer themselves."

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