Most Favored Customer Guide: MFC Logic, TDR Status, Discounts, and Pricing Story

A practical guide to the GSA Most Favored Customer concept, discount logic, commercial customer classes, and how MFC thinking changes under TDR-era pricing instructions.

Built for

GSA MAS offer teams, pricing leads, contract administrators, and founders building a Schedule package

By the end

Know when MFC logic matters and how to keep it separate from TDR assumptions.

Field guide

Most Favored Customer decision map

Traditional pricing

Do not treat MFC as a label without explaining the customer relationship.

Signal

The offer or contract uses non-TDR commercial sales practice logic.

Response

Document customer class, commercial pricing, discounts, and the proposed government relationship.

TDR participant

The supplied templates repeatedly signal that MFC fields may be blank for TDR participants.

Signal

The contract or offer is in the TDR model.

Response

Follow current GSA/TDR instructions and avoid mixing old CSP assumptions into the wrong file.

Discount story

Discount math must match the price file and support.

Signal

GSA pricing differs from commercial or MFC pricing.

Response

Show the discount calculation and explain why the relationship is fair and maintainable.

Part 1

MFC is about commercial comparison

Most Favored Customer is a way of thinking about how the proposed government pricing compares to a commercial customer class. The key is the relationship, not just the rate.

When it applies, the file should explain who the comparison customer is, what discount treatment exists, and how the proposed GSA price fits.

Part 2

TDR status changes the conversation

GSA's TDR guidance is the current anchor for MAS pricing operations. When a contract or offer is under TDR, do not blindly apply older non-TDR assumptions.

This is why the MFC page should always cross-link TDR and BOA. They are related concepts, but the answer depends on the actual contract model.

Examples

What this looks like in practice

In practiceA service offer separates MFC from TDR

The team sees an MFC column and starts filling it from old proposal habits. Then they confirm the TDR status and current file instructions before entering anything. The final package does not mix old CSP logic into a TDR workflow.

Frequently asked questions

Is MFC always required?

No. The answer depends on current GSA instructions, offer type, and TDR status. Use official GSA template instructions for the live package.

Is MFC the same as Basis of Award?

They are related but not identical. MFC is the customer/discount comparison idea; BOA is the customer or category relationship that can anchor price reduction obligations under traditional models.

What should I avoid?

Do not mix old non-TDR CSP habits into a TDR-era file without checking current instructions.