GSA MAS: Refresh 29 preview and readiness guide

Why this Refresh 29 preview matters

For many contractors, the MAS program is the backbone of federal revenue. Refresh 29 is not a dramatic reinvention, but it does re‑wire a few quiet junctions that determine how fast you can add items, adjust prices, and keep your catalog accurate. That’s why we’re treating this as a working preview rather than a one‑time announcement. Our goal is to help you see what changes are coming, why GSA is making them, and how to make smart choices in the first 90 days without creating rework later.

Two themes run through this Refresh 29 preview. First, GSA is standardizing inputs—moving new offers to FAS Catalog Platform (FCP) files and signaling stronger expectations for catalog hygiene. Second, GSA is simplifying how Economic Price Adjustments are handled by introducing a consolidated clause (GSAR 552.238‑120) that turns on when certain events occur. Neither theme should slow you down if you understand the intent and align your actions to it.

Finally, a reminder about sequencing: when the Mass Mod posts, you will typically have 90 days to accept. Acceptance often becomes the gate for other routine modifications. Treat it as the starting pistol for a short, orderly sprint—not an emergency.

Use this preview to:

• Understand the intent behind FCP adoption and the consolidated EPA clause, so your submissions look exactly like a CO expects to see.
• Prevent avoidable slowdowns by sequencing acceptance and follow‑on mods in the right order.
• Decide—before any trigger—whether to maintain or change your EPA method, and document a one‑paragraph rationale.

What’s actually changing (contractor‑relevant)

FCP files vs. legacy PPTs—what to submit and when

GSA is finishing a long, careful shift toward standardized catalog files. New offers are expected to use the FCP Product File (for products) or the FCP Services Plus File (for services and training). If your contract was awarded on legacy PPTs, you do not have to switch formats just to file a modification; keep using the file type used at award. Think of it as two well‑marked lanes: new traffic goes into the FCP lane; legacy traffic stays in its lane until a natural change point. The intent is to protect processing speed and reduce preventable catalog errors while the whole program settles fully onto FCP.

EPA: one clause, clear triggers

The new consolidated EPA clause—GSAR 552.238‑120—doesn’t rewrite your prices overnight. It applies when a trigger happens: you file an EPA or add‑items mod, exercise an option, or propose a new EPA method. Until then, your current approach stays in place. The practical takeaway for this Refresh 29 preview is to decide, in advance, how you want to handle the next trigger. If your market is relatively stable, holding your existing method until option may be sensible. If you’ve been squeezed by volatility, it can be worth preparing the case for an indexed or better‑fitting method when you next touch pricing.

SBSA SINs retired; small business access continues at the order level

GSA is completing the retirement of SBSA‑labeled SINs. This reduces duplicate structures in the Schedule without taking opportunities away from small businesses, because set‑asides still occur at the order level. Contractors should remove residual SBSA labels from pricelists and marketing language and make sure internal CRM tags reflect the non‑SBSA equivalents.

SaaS and HACS clarifications

Two clarifications matter for offerors who live in the services/software space. Under SIN 518210C (SaaS), GSA clarifies that the first NIST cloud characteristic—on‑demand self‑service—need not be present for the SaaS determination, provided the other characteristics are met. That provides breathing room for solutions with human‑in‑the‑loop provisioning. For HACS (54151HACS), GSA steers vendors away from rigid “work role IDs” and toward alignment with the current NICE Framework competencies—closer to how agencies evaluate labor skill fit today.

Category tidying you should actually act on

Not every catalog housekeeping change demands action, but a few do. UAS/drones move under 334220, while fully assembled aircraft remain excluded to 336413; double‑check that your item mapping and any ancillary services are in the right place. In the furniture category, toy/game items are explicitly out of scope. And several obsolete subcategories disappear. Use the refresh as a prompt to clean up SKUs you don’t sell, descriptions that have drifted, and any lingering mismatches between your master data and the public catalog.

The next 90 days—what good looks like

Days 0–30: Get your arms around the scope.
Start with an inventory: list each active contract, the file type used at award (FCP vs legacy PPT), and the SINs that matter for your pipeline. Mark the areas most likely to require work under Refresh 29—catalog file prep, EPA posture, SBSA label cleanup, and any SaaS/HACS narrative tweaks. Pull a small, cross-functional team together and agree on who owns what. The point isn’t volume; it’s clarity.

Days 31–60: Make the two or three decisions that unlock speed.
Decide your preliminary EPA posture—maintain until option, adjust at the next trigger, or proactively move to a method that fits your market. If any new offers are in play, begin assembling the FCP files and validating attributes so you are not discovering data issues after the Mass Mod. If you sell SaaS or HACS, align your descriptions to the clarified criteria so the contracting officer sees exactly what they expect.

Days 61–90: Accept and sequence.
Accept the Mass Mod within the window and run the plan you just designed. Submit follow-on modifications in a deliberate order—add-items and pricing changes first if they’re blocking revenue, EPA method changes when your justification is ready. Let your federal customers know about any catalog housekeeping they’ll notice (new SIN mapping, discontinued SKUs). None of this needs drama; it just needs a steady cadence.

Making the EPA call—principles, not panic

An EPA method is a tool, not a badge. Under the Refresh 29 preview, you don’t win points for changing methods quickly; you win by choosing the approach that fits your market and timing the change when a trigger naturally occurs. If you sell into a relatively stable category, there’s little harm in maintaining your current method until the option—your administrative burden stays low and your audit trail remains clean. If your category has been swinging with input costs or currency movements, it’s rational to prepare a move toward an index‑based or otherwise better‑fitting method at your next EPA or add‑items filing. The deciding factor should be the quality of your evidence: show that the method you want maps to how your prices truly behave, and be ready to explain it succinctly to the CO. That’s what the consolidated clause is trying to achieve—clarity, not churn.

Quick cues for the decision:

• Move at the next trigger if an indexed method would better mirror recent market movement and you’re already planning an EPA/add‑items mod.
• Wait until option if prices are stable and administrative simplicity is your priority.
• Change only with evidence when you can show index fit, volatility band, and a clean history the CO can verify quickly.

What this means by role

Each team touches a different lever under this Refresh 29 preview. Use the notes below as a role map—who owns what in the first 90 days—so acceptance, EPA choices, and catalog updates move in a single, coordinated lane.

• Contracts & Compliance. Centralize the Mass Mod acceptance and clause mapping so there’s one source of truth. Before you touch anything else, confirm the file type used at award for each contract; that simple check prevents accidental mid‑stream format changes that slow processing. If you have an option year coming up, add a one‑page note to the option file explaining your EPA posture so the contracting officer isn’t guessing.
• Pricing & Finance. Treat the consolidated EPA clause as an opportunity to right‑size your method. Run quick scenarios on the methods you’re considering and keep the backup in a tidy justification pack (market indices, historic cost movement, internal deltas). If you plan to submit add‑items, stage them so they can ride the same window as any EPA action you take—one well‑prepared package is faster than two partial ones.
• Sales & Capture. Update pursuit language to the non‑SBSA SIN equivalents and remind teams that small business participation now shows up at the order level. Refresh pipeline records so SIN mappings and cooperative purchasing flags are accurate; it’s easier to keep the pipeline clean than to explain misaligned SINs to a customer later. If you expect visible catalog changes, set expectations with key accounts early.
• IT/SecOps & Product. FCP rewards clean data. Compare the attributes in your master SKU system to what FCP expects and fix duplicates or retired SKUs now. For SaaS (518210C), make sure your public materials and internal documentation clearly demonstrate the NIST characteristics that do apply; for HACS, align labor narratives to NICE competencies so reviewers aren’t translating your roles on the fly.

Conclusion

Refresh 29 is a pragmatic update, not a reset. New offers move to FCP files; the consolidated EPA clause applies at clear, predictable triggers; SBSA SINs retire while order‑level set‑asides remain; and a handful of category clarifications prompt sensible catalog housekeeping. For most contractors, the winning approach is calm execution: confirm the file type used at award, choose an EPA posture backed by evidence, and accept the mass mod on time while sequencing follow‑on mods deliberately. Treat this Refresh 29 preview as a living guide—we’ll revise promptly when GSA posts the final refresh, and any changes will be summarized in the changelog below.

FAQ

If you need hands‑on assistance for acceptance planning, FCP conversion, or EPA strategy, see Refresh 29 Rapid Response (scope and approach).