B2B portal development: how do partners exchange documents?

On this page

B2B portal development for document exchange covers accounts, submissions and revision requests, with rules for who can see each file. Give each request an owner and a status, and record the version under review. A portal is useful when partners submit documents regularly and decisions are getting lost in email threads.

Start with a job you already do, such as collecting supplier documentation or asking a client for a missing attachment. Write down how the work gets done today and where it stalls. Our guide to B2B portals for businesses covers their wider uses.

When is a shared folder enough, and when do you need a portal?

A shared folder can work well when a small group exchanges files and the tool already handles permissions, version history and activity records. A portal makes more sense when each document belongs to a request with a deadline or a decision for someone to record.

Check what your existing tools can do. If your team keeps a separate status spreadsheet, look at what it tracks. The tools you already pay for may cover the gap. Consider a B2B portal if partners need to see outstanding tasks and respond to individual requests themselves. The portal can be built around that work with no shopping basket.

Who submits, reviews and approves the documents?

For each request, specify which company owns it, who supplies the document and who makes the decision. An administrator may create and revoke accounts, while a reviewer decides whether the submitted document meets the requirement. If one person does both jobs, record both permissions.

Scroll the table sideways to see all columns.

Suggested roles for a document exchange portal
RoleSuggested accessWhat to agree
Partner representativeSubmit and revise documents for assigned requests.Whether they see all their company's requests or only their own tasks.
Document reviewerRead, comment and record a decision on assigned requests.Who covers for them when they are away.
Account administratorCreate accounts and revoke access.Whether they also need separate permission to read documents.
ManagerSee outstanding tasks and delays within their area.Whether they need to see the file itself or only its status.

Try these roles on one request. Two people at the same partner company may have different assignments. An external contractor may need access only until a particular job is complete.

How do you know which version was approved?

Record the decision against the submitted version, along with the date and the person who reviewed it. Give each replacement file a new version and a defined next step. Keep the earlier decision attached to the version it covered.

Decide whether a renewal reopens the original request or creates a new one. Users need to see which version is currently accepted and which submission is still under review. A filename such as “contract-final-2” cannot record an approval decision.

Attach each revision comment to the version it refers to, so a reviewer can see what to check when the corrected file arrives. Show the deadline for responding separately from the document's expiry date. The first tells the partner when to act. The second tells them how long the document is valid under your agreed rules.

How can you notify a partner without sharing a private file?

Send the request number and a link that takes the recipient to the request after they sign in. For confidential requests, keep attachments and sensitive details out of the email. A fictional reminder could read “Request 204 needs an updated document. Open the request in the portal.”

Check the user's permission for the individual request on the server every time, including when a user downloads the file. OWASP's authorisation guidance recommends checking permissions on each request. Agree who revokes access when a partner leaves and who takes over their open requests.

Decide which roles can download copies. A file already saved to a user's computer stays there when their portal access ends.

What should happen when a partner uploads a file?

Accept only the agreed file types and sizes. Validate what the file actually contains and treat the extension and the type reported by the browser as inputs to the checks. Keep private documents out of public storage locations and agree what scanning is appropriate for the documents you handle. OWASP's file upload guidance describes these controls.

Show the permitted formats and size limit before the user uploads. If the upload fails, tell the user what to fix or whether to try again after a connection problem. Mark the request as under review only after the system accepts the document.

The partner submits version 1, receives a revision request and submits version 2, which is approved.
In this example, approval applies to version 2 and the revision request stays with version 1.

What does a revision request look like?

In this fictional example, a supplier sends a product specification to a buyer. The reviewer spots a missing dimension and asks for it. The supplier opens the same request and submits the corrected file as version two.

Keep version one with the original comment and send version two for a fresh decision. If the reviewer approves it, the request displays version two as accepted. If the product changes later, follow the renewal process you agreed. The next reviewer can check which specification supported the earlier decision.

How does this work in one of our projects?

Our Certiwa case study describes a portal for clients and ISO consultants to work on documentation together. The public demo uses fictional data to show requests, statuses and revisions. A separate sign-in area lets assigned accounts submit the documents required of them. ISO certification is decided separately by a certification body.

What should you check before the portal goes live?

Walk through one request with a partner representative and the person who reviews documents. Agree what they should see and be able to do at each step. Include these checks in the first release:

  • Partners can open only requests they have permission to view, even when using a saved link.
  • A corrected file gets a new version and the agreed status.
  • The approval record still identifies the reviewed version after a later submission.
  • A rejected upload leaves no status that could be mistaken for a successful submission.
  • Reminders reach the current assignee or their agreed stand-in.
  • A user whose access was revoked can no longer view private requests through the portal.

For a B2B portal project estimate, send an anonymised sample document, the steps it goes through and a list of the people who handle it. Say whether you need to move an existing archive and which tools the portal must connect to. In the proposal, separate development costs from document migration, storage and ongoing support.

YOUR NEXT PROJECT

We listen. We analyze. We deliver.

Free project estimate