Fix unit errors before they enter the catalog

Published by Federal Bid Partners LLC · October 26, 2026 · Catalog economics

A price can be arithmetically correct and still describe the wrong unit. The catalog says “each,” the supplier sells a case of ten, and the quote assumes an entire case. That mismatch can distort margins and customer expectations. Establish one unit dictionary connecting purchasing, pricing, catalog, and fulfillment records before adding more products.

A fictional packaging example

Magnolia Supply purchases a case of ten components for $300. The acquisition cost is $30 per component before freight and handling. Its draft catalog line says $300 per “each,” while a sales template says $45 per “case.” Neither description matches the intended offering. A reviewer finds the mismatch by tracing the item from source quote to proposed listing.

The team chooses to model individual components. It allocates $20 of case freight across ten components, creating $2 freight cost per component. It adds an explicitly assumed $3 of handling and support per component, reaching $35 of modeled cost. These fictional allocations illustrate a method; the business should use its own supported costs and contractual treatment.

Build a unit dictionary

For each item, record manufacturer identifier, supplier purchase unit, conversion quantity, customer order unit, included components, and allowed quantity increments. Include an example: purchasing one case creates ten orderable units. If customers must buy a full case, state that clearly instead of converting units in the background.

For services, define the period and included work. A “month” might include a stated service package rather than an unlimited volume of support. Record any usage boundaries and review them against the actual awarded description. Do not add customer-facing limitations that conflict with the approved offering or omit obligations from the cost model.

Use the appropriate catalog process

GSA's current modification guidance points to current Product and Services Plus templates and catalog instructions. Verify the applicable workflow for the contract and offering before assuming that a local spreadsheet edit changes the authorized catalog. Keep proposed content, approved contract information, and published catalog state distinct. GSA modification and catalog guidance.

• Reconcile purchase unit and customer order unit.
• Check conversions with a sample order quantity.
• Identify included accessories, freight, and support.
• Confirm the source and effective date of the price.
• Review rounding at unit and extended-total levels.
• Verify the actual published listing after an authorized update.

Run a small fulfillment rehearsal. Ask one person to prepare a fictional order and another to identify what purchasing would buy and what shipping would send. If the two descriptions disagree, fix the unit dictionary before relying on the price.

Keep the dictionary with the pricing model and update it when a supplier changes packaging. An unchanged part number does not prove that a package quantity or included component stayed the same. The practical objective is simple: purchasing, sales, delivery, and the customer should all mean the same thing when they use one orderable unit.