GSA released new guidance on how to handle highly configurable products in the FAS Catalog Platform - and this is a big one for vendors struggling with complex catalogs.
If your products can’t realistically be listed as individual SKUs, the traditional Product File approach may not work.
What’s new?
GSA is now formalizing the use of the Services Plus File (SPF) with two structured approaches:
Path A – No Base Model
- Group products (family/series) under one line item
- Apply a standard discount off a commercial price list
- Pricing fields stay blank – discount drives everything
Path B – Base Model + Configurations
- Define a base product with pricing
- Apply a consistent discount to all configurations
- Maintain alignment with your commercial catalog
Both approaches are designed to ensure:
- Clear catalog structure
- Compliant pricing logic
- Proper alignment with TDR reporting
One critical detail:
All pricing is tied to a specific commercial pricing document and date – meaning any change requires a modification.
Also worth noting:
You can still list popular configurations as separate items in the Product File for GSA Advantage – but pricing must match your SPF logic exactly.
Why this matters
This is GSA’s way of solving a long-standing issue:
- Overloaded catalogs
- Broken option structures
- Misalignment between pricing and TDR reporting
If you’re managing large or complex product sets, this guidance directly impacts how you structure your next mod.
Question:
Are you currently using Product File options for configurable items – or already moving toward SPF logic?
