Build/service codes

Build/service codes are codes found in some Pontiac Fiero enthusiast references, service references, assembly references, or parts-related documents.

They should not automatically be treated as RPO codes.

Overview

Build/service codes are different from regular production option codes.

While RPO codes identify factory-installed equipment, option packages, paint information, trim information, drivetrain equipment, and other build information on the Service parts identification label, build/service codes may be used for other assembly, service, parts, or identification purposes.

Some build/service codes may describe:

• Component parts
• Assembly details
• Service identifiers
• Model differentiations
• Color differentiations
• Parts used as part of standard equipment
• Parts used within option packages
• Internal build or service references

Because of this, a build/service code should not automatically be interpreted as a factory option.

Difference from RPO codes

RPO stands for Regular Production Option.

RPO codes are normally found on the Fiero Service parts identification label and identify equipment or build information assigned to a specific car.

Build/service codes may appear in other lists or references and may describe parts, assemblies, internal service identifiers, or details that were not separately ordered by the buyer.

In simple terms:

Code type	Typical use	Should it be treated as a buyer option?
RPO codes	Factory equipment, options, paint, trim, drivetrain, and build information	Sometimes, but not always
Build/service codes	Assembly, service, component, model, color, or parts-identification information	No, not automatically

Why the distinction matters

Confusing build/service codes with RPO codes can lead to incorrect conclusions about how a Fiero was originally equipped.

For example, a code may appear to describe a component or option-like feature, but it may actually identify a part used during assembly, a service part distinction, a color-related variation, or a standard-equipment detail.

When documenting a Fiero, the Service parts identification label should be used as the primary source for the car's assigned RPO codes.

Build/service codes can still be useful, but they should be interpreted cautiously.

Relationship to the Service Parts Identification label

The Service parts identification label is the normal factory label used to identify the equipment and build information assigned to a specific Fiero.

It may include regular production options, standard equipment codes, mandatory equipment codes, paint information, drivetrain information, trim information, and other factory build data.

Build/service code lists should not be assumed to match the exact RPO label on a specific car unless the code is actually present on that car's label or confirmed by factory documentation.

Related topics:

• Service parts identification label
• RPO codes
• Fiero RPO code list

Uses

Build/service codes may be useful for:

• Understanding parts references
• Comparing assembly or service information
• Identifying component variations
• Researching model-year differences
• Understanding color or trim distinctions
• Interpreting old enthusiast documents
• Cross-checking parts or service notes

They are best used as supporting information, not as the only proof of a car's original equipment.

Interpreting build/service codes

When using build/service codes:

• Do not assume the code is an RPO code.
• Do not assume the code represents a buyer-selected option.
• Check whether the code appears on the car's Service parts identification label.
• Check model-year applicability.
• Compare the code with physical evidence on the car.
• Verify important conclusions against factory documentation where possible.
• Be cautious with old enthusiast lists that may contain errors, abbreviations, or unclear descriptions.

Examples of possible code areas

Build/service code references may include codes related to:

• Body panels
• Paint or color variations
• Trim variations
• Engine-related components
• Transmission-related components
• Suspension parts
• Electrical components
• Model or package distinctions
• Service replacement parts

The exact meaning of a build/service code depends on its source and context.

Speedometer and drivetrain-related service codes

Some build/service references include speedometer gear or drivetrain-related identification codes.

These should be interpreted cautiously. They may describe service parts, driven gears, drive gears, speedometer calibration parts, or related drivetrain identification rather than buyer-selected options.

Code	Description	Category	Notes
D4N	29-tooth green speedometer driven gear	Speedometer / drivetrain	Listed in enthusiast/forum references; verify application
D4O	30-tooth natural speedometer driven gear	Speedometer / drivetrain	Letter O, not zero; listed in enthusiast/forum references
D9A	10-tooth green speedometer drive gear	Speedometer / drivetrain	Listed in enthusiast/forum references; verify application
D9B	35-tooth natural speedometer drive gear	Speedometer / drivetrain	Listed in enthusiast/forum references; verify application

Related topics:

• Vehicle speed sensor
• Transmission identification
• Transmission gear ratios

Administrative and warranty-related codes

Some codes in enthusiast or service references describe administrative, warranty, regulatory, or paperwork-related items rather than vehicle equipment.

Code	Description	Category	Notes
MDV	New York warranty enhancements	Administrative / warranty	Listed in enthusiast/forum references; verify exact application

Common mistakes

Common mistakes include:

• Treating every code in a build/service list as an RPO code
• Assuming every code represents an optional extra
• Copying a build/service code into an RPO list without verification
• Ignoring model-year differences
• Assuming a code applies to all Fieros
• Using an enthusiast list as the only source for parts identification
• Confusing factory-installed equipment with service-replacement parts

Documentation notes

When adding build/service code information to Fieropedia, include enough context to show what the code is being used for.

Useful details include:

• Code
• Description
• Source type
• Model-year applicability, if known
• Related part or system
• Whether the code is known to appear on a Service Parts Identification label
• Notes about uncertainty or verification

If a code is not confirmed as an RPO code, do not add it to the Fiero RPO code list as if it were one.

Notes

Build/service codes can be useful, but they are not the same thing as RPO codes.

The safest approach is to treat them as supporting reference information unless they are confirmed on a specific car's Service parts identification label or verified by factory documentation.

See also

• RPO codes
• Fiero RPO code list
• Service parts identification label
• Factory options
• Part numbers
• Paint codes
• Interior color codes
• Transmission identification