Skip to content
BidPulsar
BidPulsar™FBP Product Division
Built by Federal Bid Partners • team has written hundreds of proposals
RP-Led CMMC
Need proposal or grant support? Talk with our capture and CMMC team.
GSA12 min readUpdated June 7, 2026

FCP Product File Guide: Product Data, Options, Accessories, Pricing, and Catalog Readiness

A practical guide to the GSA FCP Product File: the product workbook used for item identity, manufacturer information, SINs, descriptions, options, accessories, quantity pricing, commercial price, and GSA price readiness.

Built for
GSA MAS offer teams, pricing leads, contract administrators, and founders building a Schedule package
By the end
Turn the Product File into a clean catalog and pricing story instead of a fragile spreadsheet upload.
Field guide

FCP Product File decision map

Products tab
Small naming inconsistencies can become catalog cleanup work later.
Signal
Base products and accessories need item identity and pricing.
Response
Check manufacturer, manufacturer part number, vendor part number, SIN, item name, description, unit of measure, and price columns.
Options tab
Options should not become hidden substitute products.
Signal
The item has size, color, feature, configuration, or other options.
Response
Map options to the base item and keep option pricing logic separate from base product pricing.
PRODXACC tab
Accessory relationships are easy to break when teams rename items casually.
Signal
Products and accessories need a relationship.
Response
Tie accessory identifiers back to the correct base product using stable manufacturer data.
Quantity/volume
A discount table without support can invite avoidable review questions.
Signal
The offer uses quantity or volume discount logic.
Response
Make the discount math traceable to pricing support and sales assumptions.
Part 1

Think of the Product File as catalog infrastructure

The Product File is not just an offer spreadsheet. It is the structured product record that should make the item understandable to GSA and, eventually, to buyers through catalog-facing systems.

That is why item identity matters as much as price. A clean price on a messy product record still creates downstream friction.

Part 2

Separate item identity from pricing evidence

The Product File names the item and proposed prices. Pricing support explains why those prices are reasonable. Keep both aligned, but do not expect one file to do the whole job.

For each material product line, the offer team should be able to answer: what is it, who made it, how is it sold commercially, what SIN does it fit, what is the proposed GSA price, and where is the support?

Part 3

Use Refresh 32 files as the working baseline

The supplied Refresh 32 Product File shows tabs for products, options, product/accessory relationships, quantity/volume pricing, reference data, and a worksheet map. Those tabs are a useful mental model even before the team fills anything in.

Start by reading the Read Me and Worksheet Map tabs. They usually explain which fields are required and which fields will matter later for catalog actions.

Examples

What this looks like in practice

In practiceA reseller cleans up 90 product lines before upload

The weak version lists product names the way sales staff say them out loud. The strong version uses manufacturer names, part numbers, item names, descriptions, units, options, and accessories consistently across the Product File and supporting documents.

That consistency helps the reviewer, the future catalog owner, and the person who will later reconcile sales or make a modification.

  • Normalize manufacturer names.
  • Lock part numbers.
  • Separate base items from options.
  • Tie every price to support.

Frequently asked questions

Is the FCP Product File only for new offers?

It is used in the FCP product/catalog workflow for offers and catalog actions. The exact use depends on the current GSA instructions and whether the contract is in FCP.

What is the first Product File cleanup step?

Normalize manufacturer names, part numbers, item names, descriptions, SINs, units of measure, and commercial prices before trying to solve optional fields.

Should product pricing support be uploaded separately?

Usually yes. The Product File carries proposed data; pricing support explains commercial price basis, discounts, and reasonableness.