Unit of Issue (UOI) is the standardized unit used to identify the quantity in which a product is ordered, priced, and supplied under a government contract. It establishes what a buyer receives when purchasing one unit of a particular catalog item. Common examples include each (EA), box (BX), package (PK), dozen (DZ), and pair (PR).
In General Services Administration (GSA) Multiple Award Schedule (MAS) contracts, the Unit of Issue is an important element of product catalog information. It helps government buyers understand whether an advertised price applies to a single item, a package containing several items, or another defined quantity.
For example, a contractor may sell disposable gloves in boxes containing 100 gloves. If the catalog lists a price of $12.00 per box, the Unit of Issue and product description must clearly communicate that the buyer receives one box containing 100 gloves, rather than one individual glove.
An incorrect UOI can create substantial pricing discrepancies. A contractor that mistakenly lists a box price as the price for an individual item may make its offering appear significantly more expensive than intended. The opposite error can make a product appear unusually inexpensive and create fulfillment disputes when the buyer expects a larger quantity than the contractor intended to supply.
Unit of Issue information is used beyond GSA MAS catalogs. It is also important in federal supply systems, inventory management, requisitioning, invoicing, and logistics operations involving agencies such as the Defense Logistics Agency (DLA).
Although the concept appears straightforward, UOI errors can affect several stages of the procurement process. Accurate unit identification supports meaningful price comparisons, consistent ordering, correct invoicing, and reliable contract data.
Common Unit of Issue Codes and Their Meanings
Federal procurement systems use standardized unit codes to represent how products are supplied. These codes reduce ambiguity in electronic catalogs and purchasing records, particularly when suppliers use different commercial packaging terminology.
The exact code set and accepted values depend on the government system, solicitation, and applicable data requirements. Contractors should therefore use the codes specified for the relevant submission rather than assuming that every commercial abbreviation is universally accepted.
The following table illustrates commonly encountered units.
| Unit of Issue | Code | Meaning | Example |
|---|---|---|---|
| Each | EA | One individual item or defined sellable unit | One flashlight |
| Box | BX | One box containing a specified quantity | Box of 100 disposable gloves |
| Package | PK | One package containing a defined quantity | Package of 10 cable ties |
| Dozen | DZ | Twelve items | Dozen pencils |
| Pair | PR | Two items supplied as a matched pair | Pair of work gloves |
| Set | SE | A defined collection of items supplied together | Set of six screwdrivers |
| Case | CS | One case containing a specified quantity | Case of 24 cleaning bottles |
| Roll | RO | One roll of material | Roll of adhesive tape |
| Foot | FT | One linear foot | Electrical cable sold by the foot |
| Gallon | GL | One gallon of liquid | Industrial cleaning solution |
These examples illustrate commercial packaging arrangements. Contractors must confirm that the relevant codes are valid for the specific federal catalog or reporting system in which they are used.
The code alone may not communicate the full quantity supplied. For example, BX indicates a box, but it does not establish whether that box contains 10, 50, or 100 individual items.
Similarly, PK identifies a package without independently specifying its contents. A product description or other required catalog field must provide the additional information necessary to understand the offering.
This distinction is important because two products may share the same Unit of Issue while containing different quantities.
Consider two listings for cleaning wipes:
- Product A: one package containing 50 wipes, priced at $6.00 per package.
- Product B: one package containing 100 wipes, priced at $9.00 per package.
Both products may use PK as their Unit of Issue. However, Product B provides twice as many wipes per package, and the difference in package contents affects any meaningful comparison of their prices.
For Product A, the effective price is $0.12 per wipe. For Product B, it is $0.09 per wipe.
A comparison based only on the package prices would suggest that Product A is cheaper. A comparison based on the quantity received shows that Product B has the lower price per wipe.
The Unit of Issue and package quantity therefore serve related but distinct purposes. UOI identifies the ordering unit, while package quantity explains how many individual items or how much material that unit contains.
Contractors should avoid using vague descriptions such as “one package” when the number of items inside the package is necessary to understand the product.
Unit of Issue, Unit Price, and Packaging Quantity
Unit of Issue is closely connected to unit price, but the two terms describe different aspects of a transaction. The Unit of Issue establishes what constitutes one ordering unit, while the unit price establishes the amount charged for that unit.
For example, a contractor may offer a package of 25 replacement filters for $75.00. If the approved ordering unit is one package, the catalog price represents the cost of one package containing 25 filters.
The effective cost of an individual filter is $3.00, but that does not necessarily mean the contractor offers filters individually for $3.00 each.
The distinction matters because government buyers generally must purchase products according to the quantities and terms established by the applicable contract or quotation.
A contractor that sells filters only in packages of 25 should not represent them as individually available unless the contract also supports individual sales.
Several related concepts should be distinguished:
- Unit of Issue. The unit in which the product is ordered and supplied.
- Unit Price. The amount charged for one Unit of Issue.
- Package Quantity. The number of individual items or amount of material contained in one package.
- Minimum Order Quantity. The smallest quantity the contractor permits or requires for a particular purchase, subject to the applicable contract terms.
- Order Quantity. The number of ordering units requested by the buyer.
- Total Order Value. The amount payable for the ordered quantity before any separately applicable charges or adjustments.
These elements must be consistent, but they are not interchangeable.
For example, a product may have a Unit of Issue of EA while being subject to a minimum order quantity of 10. In that case, the catalog may identify the product as individually priced, but the contractor’s applicable ordering terms require the buyer to purchase at least 10 units.
Alternatively, the contractor may sell the same product only as a package containing 10 items. That is a different commercial arrangement because one ordering unit represents the entire package.
The following table demonstrates how the Unit of Issue affects an order.
| Product | Unit of Issue | Contents of one unit | Price per unit | Order quantity | Total price |
|---|---|---|---|---|---|
| Safety goggles | EA | 1 pair of goggles sold as one item | $8.00 | 10 | $80.00 |
| Disposable masks | BX | 50 masks | $15.00 | 4 | $60.00 |
| Batteries | PK | 8 batteries | $12.00 | 3 | $36.00 |
| Printer paper | CS | 10 reams | $55.00 | 2 | $110.00 |
| Cleaning cloths | DZ | 12 cloths | $18.00 | 5 | $90.00 |
The figures are illustrative and do not represent actual awarded GSA prices.
In the battery example, an order quantity of three means three packages, not three individual batteries. The buyer receives 24 batteries because each package contains eight.
If the contractor mistakenly records the Unit of Issue as EA while retaining the package price of $12.00, the catalog becomes ambiguous. A buyer may reasonably interpret the listing as charging $12.00 for one battery rather than eight.
The resulting problem is not merely a formatting issue. It can affect the government’s purchasing decision, the contractor’s fulfillment obligations, and the accuracy of the transaction record.
For products sold by length, weight, or volume, the same principle applies. A price per foot cannot be treated as a price per roll unless the roll length and corresponding pricing arrangement are clearly established.
Contractors should also distinguish the Unit of Issue from the physical shipping configuration. A product may be ordered individually but shipped in a larger protective carton containing several separately ordered units.
The shipping carton does not necessarily determine the contractual Unit of Issue. The relevant question is what the government purchases and receives for each priced ordering unit.
Unit of Issue Requirements in GSA MAS Catalogs and FCP
Accurate Unit of Issue information is particularly important for contractors maintaining product catalogs under GSA MAS contracts. Product data must allow government customers to understand the items available for purchase and the prices associated with those items.
The FAS Catalog Platform (FCP) is used for MAS catalog management as contracts transition to the platform. Its catalog submission processes require contractors to provide structured product information using the applicable files, templates, and validation rules.
For product listings, the Unit of Issue must be consistent with the approved offering and the price associated with that offering. Depending on the submission format, related information may include product descriptions, manufacturer part numbers, package quantities, and other catalog attributes.
An incorrect UOI can cause a catalog submission to fail an applicable validation check. However, not every UOI error is automatically detected by the system.
Some errors involve invalid codes or missing required values, which may be identified through automated validation. Others involve commercially inconsistent information that appears technically valid but misrepresents the quantity supplied.
For example, a catalog file might contain the following information:
- Product description: Box of 100 nitrile gloves.
- Unit of Issue: EA.
- Unit price: $14.00.
- Package quantity: 100.
The product description suggests that the buyer receives a box containing 100 gloves. However, the UOI value EA could indicate that the listed price applies to one individual ordering unit, creating uncertainty about what that unit represents.
The correct treatment depends on the actual awarded offering and the applicable catalog data requirements. The contractor should not change the UOI code without first confirming how the product is defined and priced under its contract.
A second example involves a contractor selling adhesive tape in rolls. If the product is priced per roll but the catalog identifies the Unit of Issue as FT, the listing may incorrectly suggest that the buyer can purchase individual feet of tape.
Such discrepancies can affect catalog accuracy even when every field contains a code accepted by the system.
Typical catalog problems involving UOI include:
- Invalid unit codes. The submitted value is not recognized by the applicable catalog format.
- Missing UOI information. A required unit field is left blank.
- Price and unit mismatch. The price represents a package, but the unit code suggests an individual item.
- Inconsistent package quantities. The product description and structured catalog fields indicate different quantities.
- Incorrect conversion. Commercial packaging information is translated into the wrong government unit.
- Inconsistent product variants. Similar items use different units without a clear commercial reason.
- Unapproved changes. Catalog information is revised in a way that does not match the awarded contract terms.
These issues require different corrective actions. An invalid code may be resolved by selecting the correct permitted value, while a discrepancy between the catalog price and the actual product configuration may require a more substantive review.
Contractors should also recognize that catalog data corrections and contractual modifications are not always the same action. Correcting a transcription error may follow a different process from changing the quantity or packaging configuration of an awarded product.
If a contractor intends to replace an individually priced item with a multipack offering, the change may affect the awarded product and pricing arrangement. The applicable MAS modification requirements must be reviewed before implementing the change.
A catalog upload should not be used to introduce an unauthorized commercial change simply by modifying the Unit of Issue field.
How Unit of Issue Errors Affect Pricing and Government Orders
Unit of Issue errors can distort product pricing even when the numerical price is entered correctly. This occurs because a price has no complete commercial meaning without identifying the quantity to which it applies.
For example, consider two contractors offering identical cleaning products:
Contractor A lists one bottle for $8.00. Contractor B lists one case containing 12 bottles for $84.00.
At first glance, Contractor A appears significantly cheaper because its displayed price is lower. However, Contractor B’s effective price is $7.00 per bottle.
The products cannot be compared accurately without considering their Units of Issue and package quantities.
This issue becomes more consequential when government buyers compare numerous catalog listings. An incorrectly classified product may appear more or less competitive than it actually is.
The consequences can extend beyond price comparisons.
An incorrect UOI may cause a buyer to order the wrong quantity, leading to shortages or excess supplies. It can also create disputes when the contractor delivers the quantity it intended to sell but the customer expected a different amount.
For example, a government office may order 20 units of a product listed as EA. If the contractor interprets each unit as a package containing 10 items, the shipment could contain 200 individual items instead of the 20 expected by the buyer.
The reverse situation can be equally problematic. A buyer expecting 20 packages may receive only 20 individual items if the contractor’s internal records do not match the catalog listing.
These discrepancies may result in:
- Order corrections and processing delays.
- Incorrect quantities delivered to government customers.
- Disputes over invoiced amounts.
- Returns or replacement shipments.
- Additional administrative work for the contractor and agency.
- Inaccurate internal inventory records.
- Misleading comparisons between competing offerings.
Invoice accuracy is another important consideration. The quantities and prices on an invoice should correspond to the applicable order and contract terms.
If a purchase order specifies five boxes at $20.00 per box, the invoice should not represent the transaction as five individual items at the same price unless that interpretation matches the contractual arrangement.
The issue may also affect receiving and acceptance. Government personnel responsible for verifying deliveries need to determine whether the quantity received corresponds to the quantity ordered.
A discrepancy between the ordering unit and the delivered packaging can complicate that determination, particularly when the product is supplied in bulk or contains multiple individual components.
For contractors operating across several sales channels, internal system differences can create additional risks. A commercial inventory system may track individual items, while the GSA catalog identifies packages or cases as the sellable units.
For example, an inventory system may record 1,000 individual batteries, while the GSA catalog sells packages containing 10 batteries. The contractor must maintain an accurate relationship between the inventory quantity and the government ordering unit.
Without consistent conversion rules, the contractor may overstate available inventory or incorrectly calculate fulfillment quantities.
This is especially important for distributors managing large product catalogs. A single packaging conversion error can affect multiple listings or recurring orders if the underlying data is reused across systems.
Best Practices for Managing Unit of Issue Data
Accurate Unit of Issue management requires coordination between product data, contract pricing, inventory systems, and order fulfillment processes. Contractors should treat UOI as a core commercial attribute rather than a secondary catalog field.
The most effective approach is to establish a clear definition of the sellable unit before preparing or updating a government catalog listing.
For each product, the contractor should be able to answer three questions: What exactly does the buyer receive when ordering one unit? What price applies to that unit? How is the unit represented in the contractor’s inventory and shipping systems?
A structured review process can help prevent discrepancies.
- Verify the awarded offering. Confirm the product configuration and pricing established under the applicable contract.
- Identify the sellable unit. Determine whether the product is sold individually, by package, by case, or through another measurement.
- Confirm the permitted UOI code. Use the code accepted by the applicable GSA catalog submission format.
- Record package contents. Specify the number of individual items or amount of material included in one ordering unit.
- Check price consistency. Ensure the listed unit price corresponds to the defined Unit of Issue.
- Review product descriptions. Confirm that the description does not contradict the structured unit information.
- Validate inventory conversions. Ensure internal stock records can support the quantities sold through the government catalog.
- Test representative listings. Review products with different packaging configurations before submitting large catalog updates.
- Investigate validation errors. Determine whether a rejected field reflects a formatting problem or a substantive product data issue.
- Maintain change records. Document corrections and confirm whether a contract modification is required.
For example, a contractor managing 5,000 product listings may have several hundred products sold in multipacks or cases. Reviewing every product manually after each catalog update may be inefficient.
Instead, the contractor can establish data quality checks that identify potentially inconsistent combinations, such as a product description containing “case of 24” while the UOI field indicates an individual item.
These checks do not replace human review. A product may legitimately be sold as one individual case, and the applicable data format may require additional fields to clarify its contents.
The purpose of automated checks is to identify records that require examination, not to assume that every apparent inconsistency is an error.
Contractors should also review Unit of Issue information when manufacturers change packaging. A supplier may replace a 12-count package with a 10-count package while retaining a similar product name or commercial identifier.
If the contractor continues using the old package quantity in its GSA catalog, the listing may no longer accurately represent the product being delivered.
A packaging change can also affect the effective price per individual item. For example, a package priced at $24.00 contains products costing $2.00 each when the package includes 12 items, but $2.40 each when the package contains only 10.
Even if the package price remains unchanged, the government receives a different quantity. The contractor must evaluate whether the change affects the awarded offering and requires approval under the applicable contract procedures.
Unit of Issue accuracy is therefore closely connected to contract compliance, pricing transparency, and reliable order fulfillment. A correct code helps identify the ordering unit, but it must be supported by consistent product descriptions, package quantities, and pricing information.
For GSA MAS contractors, maintaining this consistency reduces the risk of catalog validation problems and purchasing misunderstandings. More importantly, it ensures that government buyers can determine exactly what they are purchasing and how much they will pay for the quantity received.
