Letters of Supply Guide: Supplier Authority, VPP, IT Category F, and Product Offers

A guide to GSA letters of supply, including supplier authority, Verified Products Portal context, conditional applicability, and what a clean letter should include.

Built for

GSA MAS offer teams building an eOffer upload package from the Refresh 32 checklist

By the end

Know what the Letters of Supply file proves and how to prepare it without creating review friction.

Field guide

Letters of Supply review checks

Check 1

Using a vague letter that does not name the supplied products or brand can fail to prove actual authority.

Signal

Supplier letterhead and signature are current.

Response

Make the file clear enough that a reviewer can follow it without calling the offer team for basic context.

Check 2

Do not let this upload contradict pricing, SAM data, or narrative responses.

Signal

Brands/manufacturers or products are specific.

Response

Make the file clear enough that a reviewer can follow it without calling the offer team for basic context.

Check 3

Do not let this upload contradict pricing, SAM data, or narrative responses.

Signal

Applicability matches current GSA instructions.

Response

Make the file clear enough that a reviewer can follow it without calling the offer team for basic context.

Part 1

What this upload proves

A letter of supply proves the supplier authorizes the offeror to provide specified products under the GSA offer or contract.

It belongs in the product supply-chain lane with supplier agreements, TAA sourcing, and product files.

Part 2

How to prepare it cleanly

Start by naming the proof role, file owner, source system, date pulled or signed, and whether the file is required, conditional, or optional for the selected offer.

Then compare the file against the pricing workbook, SAM record, eOffer narrative, and category/SIN instructions so the package tells one story.

Supplier letterhead and signature are current.
Brands/manufacturers or products are specific.
Applicability matches current GSA instructions.

Part 3

What to watch before upload

Using a vague letter that does not name the supplied products or brand can fail to prove actual authority.

Use filenames that help the reviewer understand the document before opening it. A clear file name with document type, company, SIN or category when relevant, and date is usually better than an internal shorthand.

The upload goal is calm review: current file, clear purpose, no contradictions.

Examples

What this looks like in practice

Real-world exampleHow a clean Letters of Supply upload helps

A reseller offering IT products obtains a supplier-signed letter that names the brand, product scope, offeror, and date, then saves it beside the Product File and TAA support.

Frequently asked questions

Is Letters of Supply always required?

Treat it as conditional for planning purposes, then confirm the live requirement against the solicitation, eOffer prompts, and selected SIN/category instructions.

Where does Letters of Supply fit in the offer package?

It belongs in the product supply-chain lane with supplier agreements, TAA sourcing, and product files.

What is the safest review habit?

Check the document against the pricing file, SAM record, narrative responses, and source instructions before uploading it.