Remove discontinued offerings without losing the audit trail

Published by Federal Bid Partners LLC · October 26, 2026 · Offering maintenance

A discontinued product creates more than a catalog housekeeping task. It can affect pending quotes, active orders, replacement discussions, and contract records. The MAS Modification Guide includes deletion-modification guidance. Start there and confirm the requirements that apply to the specific change; do not assume that removing an image from a website changes the contract. Find the deletion guidance in the MAS Modification Guide.

Define exactly what is leaving

Create a deletion list using the approved item identifiers. Include manufacturer or service name, part number or category code, unit, affected SIN, and reason for the request. Identify where each item currently appears: contract files, catalog, quote templates, sales sheets, and internal ordering systems. A description such as “older equipment” is too broad to support a dependable reconciliation.

Fictional Granite Supply plans to remove three discontinued network switches. Its team initially lists only marketing names. A catalog specialist discovers that one name covers two different part numbers and that another appears in a bundle. The team revises the list to distinguish the exact items and flags the bundle for review. It has found an operational dependency before a simple deletion becomes an ambiguous instruction.

Separate deletion from replacement

If a successor item exists, place it in a separate proposed-change row. Record how it differs in features, pricing, terms, and identifiers. Do not silently substitute the new item into the old record or assume that discontinuation automatically authorizes a replacement. Follow the applicable addition or change instructions and seek clarification when the correct route is uncertain.

• Contract track: identify the requested deletion and retain supporting evidence.
• Catalog track: plan the correct catalog action for the contract's platform.
• Sales track: mark draft quotes and templates needing review.
• Order track: identify active customer commitments for separate contract-specific handling.
• Archive track: preserve the old approved record and its replacement history.

Use the correct catalog sequence

GSA's Vendor Support Center explains that catalog-related modifications include additions, deletions, and changes. For FCP contracts, catalog loading forms part of the modification workflow while eMod remains involved. This makes platform identification an early planning step. Use current mapping and user guidance for the actual contract rather than imposing a legacy upload sequence. Read Catalog Related Modifications.

Granite's register records three dates separately: requested deletion date, the date established by the executed result, and the date the public catalog is verified. When a public search still shows an old entry, the owner records the discrepancy and follows up. They do not mark the entire project complete because the internal spreadsheet has been updated.

Run a deletion reconciliation

Use a before-and-after check with the same item identifiers. Confirm which items remain, which changed, and which were removed. Sample both the intended deletions and neighboring items to catch accidental omissions. Preserve screenshots or exports that identify the checked record and observation date. This is verification evidence, not a substitute for the executed contract action.

Finish with a short release note for staff: affected items, approved status, effective date, open-order questions, and where to find the authoritative files. The goal is a traceable transition that prevents outdated offerings from continuing to circulate while preserving enough history to explain earlier quotes and orders.