Documentation center

Attach the right document request to the right SKU.

Route product specifications, size guidance, standard-reference questions, report requests, and quote documentation without losing the SKU, order, or lot context a safety buyer needs for approval.

Open SKU library  → Request documents
Start with
SKU, model, product family
Add when available
Order, PO, quote, lot number
Response path
Support confirms available files or next step
Document type Use case Buyer context needed Availability rule Start
Product spec / SKU summary Internal product approval, reorder comparison, SKU shortlist review. SKU or model, intended task, target product family. Source-derived fields are visible in the SKU library; extra details are confirmed by support. SKU library
Size and fit guidance Crew issue, wearer fit review, substitute-size planning. SKU, size range, wearer count, preferred fit. Available where the SKU has a reliable size path; otherwise support confirms the product record. Contact support
Standard reference review Safety file review, compliance language check, category comparison. Required standard, product family, country or jobsite requirement. References are SKU-specific and should match the product record, claim, and use case. QC method
Test report / certificate question Quote approval, regulated jobsite review, post-order safety record. SKU plus quote, order, PO, or lot number when available. Support confirms whether a report, file, lot detail, or alternate document path is available. Request docs
Packaging / carton data Warehouse planning, freight review, B2B replenishment. SKU mix, quantity, delivery destination, target date. Confirmed during quote or account review because pack and freight context can change by order. B2B quote
Chemical compatibility context Splash, solvent, acid, or permeation review before specification. Chemical or SDS, exposure time, glove material target, quantity. Support reviews the material and claim path; a substitute SKU may be required. Ask support

Request packet

Include the context that proves the file belongs to your order.

  1. 01

    SKU, model, or product URL from the SKU library or PDP.

  2. 02

    Quantity, purchase route, delivery destination, and target date.

  3. 03

    Required standard, report type, or buyer approval format.

  4. 04

    Order, quote, PO, or lot number if the request is tied to a shipment.