Custom customer quality document portals

The document for this shipment

Suppose a customer requests the quality certificate for a batch of material they received. A customer service employee finds a certificate for a similarly named product, but its batch number differs. They check the shipment record to identify the correct batch. That batch has two document revisions. The person responsible for quality has approved the later revision as a replacement for the earlier one.

In a portal, the customer could open their shipment, see the associated batch, and download the approved document covering it. A note explaining that it replaces the previous revision would help them understand why it differs from the file they received earlier. Customer service would no longer need to repeat the search from product name to batch number and then ask quality staff which revision to send.

That view depends on links in the records. Someone must identify the batch supplied in the shipment and associate it with a document approved for release. If those records already exist in company systems, the portal can use them. If employees establish the connection only when a customer calls, organizing that part of the work comes first. A product-name search cannot settle which of several similar files covers the delivered material.

The quality team owns the document's content and approval of a new revision. The portal's job is to share the designated file with the right customer.

What happens when a file is replaced?

In the example, the later revision has an approval and an explicit relationship to the earlier document. The date a file was uploaded does not establish either fact. Someone might have uploaded an old document again or added a draft correction. Publication needs to reflect which revision the quality owner approved for that batch.

Preserve the replacement history so an employee can answer a customer who has an older copy. Decide whether customers may open previous revisions and how they will see that a document has been replaced. If customers should receive a notification, it needs to lead to the document for their shipment. Those decisions give a portal project a more useful starting point than a general request to display the latest PDF.

Also decide what customers see when an approved document is not yet available. They could see that it is missing and send a question to customer service. Showing a document for another batch just because the product name matches would defeat the purpose of the portal.

Start with the library or quality system you have

If you use a quality management system, or QMS, ask its vendor about customer document sharing. Walk through one shipment with a replaced document. The necessary links and publishing features may already be available, with configuration or working practices accounting for the gap. Confirm that in your particular product and plan; customer portals are not a universal QMS feature.

For a simpler process, an organized SharePoint library may be sufficient. Microsoft documents sharing with people outside the organization, including customers. External sharing depends on both organization and site settings, with the more restrictive setting taking precedence (SharePoint external sharing overview). A library is therefore a credible option to investigate when staff already associate files with shipments correctly and mainly need a convenient way for customers to retrieve them.

Access needs separate attention. A customer downloading a certificate does not need to change files. Microsoft notes that a guest added as a site member can receive permission to edit, add, and delete content (SharePoint guest permissions). Ask the administrator to demonstrate what a customer account can actually open, including whether it can see another customer's materials.

When to add a portal

An extension makes sense when your current system manages documents well but customers struggle to reach them. A simple list of a customer's shipments could point to approved files in that system. Quality staff would continue using their existing tool. The connection needs access to the relevant shipment links and replacement information so the two views do not start showing different revisions.

Consider a custom application when customer service repeatedly pieces this information together from several places and the existing tools cannot provide convenient access to a shipment's documents. An initial scope could cover one document type and its association with customer shipments. Testing, complaints, and internal quality approvals could remain in their current systems. Buying a portal does not require recreating the entire QMS.

One useful way to assess the project is to ask whether a customer can sign in and find the right document for their shipment without contacting your staff. In the example, that means identifying both the correct batch and the approved revision. An easy download addresses the problem only if an employee no longer has to select the file manually for every request.

Maintaining documents and access

The portal will need attention after launch. Someone in your company still approves documents for publication and resolves missing links between records. The application provider can maintain system connections and help resolve failures, but the scope and terms of that work need to be agreed. Include customer account administration when comparing proposals, especially removing access when someone leaves a customer's organization.

Document history should remain useful if you later change tools. A folder full of files will not tell staff which document replaced an earlier revision or which shipment it covered. Establish whether you can export those relationships and how staff will access the archive. For a custom application, also discuss code ownership and how another provider could take over maintenance.

If you also need to share reports with customers and collect corrections, our article on franchise reporting portals examines that related scope.

Syntalith builds custom applications. A possible project is a view of documents linked to customer shipments, connected to the source where quality staff maintain approved files. Start the conversation with the last request for a certificate: where did the employee search, and how did they know they had found the right document? Describing that process and the systems involved is enough to begin. You do not need a specification or confidential documents. See Syntalith's pricing page for information about billing.