Is an SDS portal better than email for SDS and service reports?

This guide covers how a chemical supplier or distributor shares safety data sheets, technical data sheets, certificates of analysis and service or visit reports with business customers. It does not cover consumer sales, workplace SDS management at the customer's own site, or SDS rules outside the US and EU. Legal points here are orientation, not legal advice.

Why do customers keep asking again for documents already sent by email?

Customers keep asking again for documents already sent by email because an attachment lands in one person's inbox, while the people who need it, and the revision they need, change after the email is sent. A safety data sheet (SDS) sent to a buyer with the first order is rarely the copy the plant uses. Under US OSHA rules the employer must keep SDS copies "readily accessible during each work shift to employees when they are in their work area(s)" (29 CFR 1910.1200(g)(8), OSHA, 2026), so the safety coordinator, the shift supervisor and the maintenance planner each need the current sheet. When the buyer leaves, the inbox goes with them. Service and visit reports have the same problem: a report emailed after a March visit is hard to find in June, and nobody can tell from the attachment whether a corrected version followed it. The fix starts with records, not software. For each customer, record who received which document, which revision or report date, on which date and by which channel. Then compare that record with each repeat request. A request for a document already sent usually means one of three things: the wrong person received it, the revision changed, or the customer cannot find it. Each points to a different fix: add the right contact, send the revision, or give the customer one place to look.

SDS portal or email by document type

The channel for each customer document depends on two questions: does a rule require you to send it, and does it change after sending? The table below decides, document by document, whether it goes by email, by portal share or both; a supply contract or quality agreement can override any row.

The row most suppliers get wrong is the SDS for a first shipment: a portal copy helps the customer find it later, but the copy a rule requires still has to be sent to the recipient with or before the shipment. For the TDS and for service reports, the portal is the main channel and email only tells the customer that something new is there. Use the table in two passes. First, mark every document that a rule requires you to send and give it a named recipient at each customer, usually the safety or EHS contact. Second, for everything else, decide who at the customer should see it and put it in that customer's portal space instead of an inbox. Record the channel per document in the customer account, so the next person who handles the account does not have to rebuild the decision.

Does posting an SDS on a portal meet the legal duty to provide it?

Posting an SDS on a portal does not by itself meet the duty to provide it under US OSHA or EU REACH, because both rules put delivery on the supplier, not on the customer's search. OSHA 29 CFR 1910.1200(g)(6)(i) requires chemical manufacturers and importers to provide distributors and employers an appropriate SDS with their initial shipment and with the first shipment after an update, and (g)(7)(i) puts the same duty on distributors toward their own customers (OSHA, 2026). In 1994 OSHA rejected a fax-on-demand system: "Your system requires the MSDS to be sought out by the downstream user(s)." (OSHA, 1994). In 1999 OSHA accepted electronic delivery if the supplier confirms the customer is willing and able to receive it electronically, tells the customer specifically how to obtain it, keeps a backup, and uses a positive means of contact when there is a significant change to the health hazard information (OSHA, 1999). Both letters predate the current text; the (g)(6)(i) text the 1994 letter quotes matches today's wording apart from "material safety data sheet". In the EU, REACH Article 31(8) requires the SDS "free of charge on paper or electronically no later than the date on which the substance or mixture is first supplied" (EU REACH Regulation, 2006). HSENI, the Northern Ireland safety regulator, writes: "A system that merely requires customers to obtain a SDS from a company's website or from a catalogue of SDS is not considered appropriate." (HSENI, accessed 2026).

Can you take back a document after you share it with a customer?

You can take back a document shared through a portal by removing the share, but you cannot take back an emailed attachment, and neither route removes copies the customer already downloaded. Email recall is narrow. Outlook can recall a message only if both sender and recipient have Microsoft 365 work or school accounts in the same organization and the recipient has not opened it (Microsoft, accessed 2026), which rules out almost every customer. Gmail's Undo Send holds a message for a cancellation period of 5, 10, 20 or 30 seconds chosen by the sender (Google, accessed 2026). After that, the attachment is the customer's copy. A portal share can be removed, so the customer stops seeing a wrong report from that moment. Treat withdrawal as a correction, not a deletion:

1. Issue the corrected report under the same title with a new date and a one-line note of what changed.

2. Remove the share of the old version.

3. Tell the named contact that the earlier version is withdrawn and why, because a downloaded copy may still exist.

4. Keep the withdrawn version in your own files with the date it was withdrawn.

A safety data sheet is a special case. You do not withdraw an SDS the customer relies on; you replace it with a new, dated version, which REACH Article 31(9) requires to be identified as "Revision: (date)" (EU REACH Regulation, 2006).

How do you keep one customer from seeing another customer's service reports?

Keep one customer from seeing another customer's service reports by giving each customer account its own private space, sharing item by item, and checking every file for other accounts' details before it is shared. Separation by setup is more reliable than separation by care: a shared folder with a subfolder per customer depends on everyone filing correctly, while a space that is private by default shows a customer only what someone deliberately shared. Three checks catch most leaks in service reports. First, file names, headers and photo captions copied from an earlier report can carry another customer's name or site. Second, a comparison chart of "similar plants" can identify a plant by its size and region without naming it. Third, access lists drift: when a contact leaves the customer, end their access in the same week. Where service reports name people, such as operators at a site, the EU General Data Protection Regulation requires personal data to be processed with appropriate security, "including protection against unauthorised or unlawful processing" (Regulation (EU) 2016/679, Article 5(1)(f)). Record, per customer, who can see which item and since when, and review that list at each account review. Before giving a new contact access, open the space as that customer would see it, if your tool offers such a view, and confirm that only their own records appear.

What should a portal do when an SDS is updated?

When an SDS is updated, a portal should replace the current copy, keep the old revision labeled as superseded, and start an active notice to every customer the rules require you to reach. REACH Article 31(9) requires the new, dated version to be provided free of charge, on paper or electronically, to all former recipients supplied within the preceding 12 months (EU REACH Regulation, 2006). OSHA 29 CFR 1910.1200(g)(6)(i) requires the updated SDS with the first shipment after the update (OSHA, 2026), and OSHA's 1999 letter asks for a positive means of contact, such as a letter, when there is a significant change to the health hazard information (OSHA, 1999). An update email sent only to people who signed up on a public download page does not reach every former recipient. Steps for each SDS revision:

1. Publish the new revision with its revision date and a short list of the changed sections.

2. Mark the previous revision superseded, and keep it available so a customer can show which sheet applied on a given date.

3. Pull the list of customers supplied with the product in the preceding 12 months from shipment records, not from portal sign-ups.

4. Email the revision to each named SDS recipient and record the date it was sent.

5. Flag the next shipment to each customer so the updated SDS travels with it.

When should EHS or legal staff review how you share SDS and service reports?

Ask EHS, regulatory or legal staff to review how you share SDS and service reports when you supply hazardous products into more than one jurisdiction, when you plan to rely on electronic delivery for the SDS a rule requires, or when reports contain personal data or information covered by a confidentiality agreement. These are the points where general rules stop being enough: OSHA, REACH and national authorities word the delivery duty differently, other countries have their own SDS rules, and confidentiality duties depend on each agreement's wording. A distributor also needs its suppliers' revision dates, because 29 CFR 1910.1200(g)(7)(i) requires distributors to pass updated SDS to their own customers with the first shipment after an update (OSHA, 2026). Have the reviewer check three records: the SDS recipients per product, the channel and date each revision went out, and who at each customer can see which report. Lubinpla's Field Care shares deliverables, Dataroom files, work logs and projects with a customer item by item and can unshare them at any time, with records private by default so no customer sees another account, and because sharing sends no notification, the SDS a rule requires and the notice of a new report still go out by email. Whatever tool you use, make one person responsible for both the share list and the shipment-linked SDS list, so the two never drift apart.