Product (FIX tag 460)

intFIX 4.4

Product (tag 460) is an int field defined in FIX 4.4. It appears in 65 message types, always optionally. It is an enumerated field with 13 defined values.

At a glance

Tag
460
Name
Product
Datatype
int
Dialects
FIX 4.4
Messages
65
Valid values
13

What the specification says

Indicates the type of product the security is associated with. See also the CFICode(146) and SecurityType(167) fields.

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 460

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength117
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
460Product1AGENCY
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum255
Edit and decode it yourself

Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.

Open in the full decoder →

Generated from the FIX 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

ValueMeaningSymbolic name
1AGENCYAGENCY
2COMMODITYCOMMODITY
3CORPORATECORPORATE
4CURRENCYCURRENCY
5EQUITYEQUITY
6GOVERNMENTGOVERNMENT
7INDEXINDEX
8LOANLOAN
9MONEYMARKETMONEYMARKET
10MORTGAGEMORTGAGE
11MUNICIPALMUNICIPAL
12OTHEROTHER
13FINANCINGFINANCING

Where tag 460 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

MessageMsgTypeRequirednessWhere in the message
Advertisement7Optionalinside the Instrument component
AllocationInstructionJOptionalinside the Instrument component
AllocationInstructionAckPOptionaldirectly on the message body
AllocationReportASOptionalinside the Instrument component
AllocationReportAckATOptionaldirectly on the message body
AssignmentReportAWOptionalinside the Instrument component
CollateralAssignmentAYOptionalinside the Instrument component
CollateralInquiryBBOptionalinside the Instrument component
CollateralInquiryAckBGOptionalinside the Instrument component
CollateralReportBAOptionalinside the Instrument component
CollateralRequestAXOptionalinside the Instrument component
CollateralResponseAZOptionalinside the Instrument component
ConfirmationAKOptionalinside the Instrument component
CrossOrderCancelReplaceRequesttOptionalinside the Instrument component
CrossOrderCancelRequestuOptionalinside the Instrument component
DerivativeSecurityListAAOptionalinside RelSymDerivSecGrp › Instrument
DontKnowTradeQOptionalinside the Instrument component
EmailCOptionalinside InstrmtGrp › Instrument
ExecutionReport8Optionalinside the Instrument component
IOI6Optionalinside the Instrument component
ListStrikePricemOptionalinside InstrmtStrkPxGrp › Instrument
MarketDataIncrementalRefreshXOptionalinside MDIncGrp › Instrument
MarketDataRequestVOptionalinside InstrmtMDReqGrp › Instrument
MarketDataSnapshotFullRefreshWOptionalinside the Instrument component
MassQuoteiOptionalinside QuotSetGrp › QuotEntryGrp › Instrument
MassQuoteAcknowledgementbOptionalinside QuotSetAckGrp › QuotEntryAckGrp › Instrument
MultilegOrderCancelReplaceACOptionalinside the Instrument component
NewOrderCrosssOptionalinside the Instrument component
NewOrderListEOptionalinside ListOrdGrp › Instrument
NewOrderMultilegABOptionalinside the Instrument component
NewOrderSingleDOptionalinside the Instrument component
NewsBOptionalinside InstrmtGrp › Instrument
OrderCancelReplaceRequestGOptionalinside the Instrument component
OrderCancelRequestFOptionalinside the Instrument component
OrderMassCancelReportrOptionalinside the Instrument component
OrderMassCancelRequestqOptionalinside the Instrument component
OrderMassStatusRequestAFOptionalinside the Instrument component
OrderStatusRequestHOptionalinside the Instrument component
PositionMaintenanceReportAMOptionalinside the Instrument component
PositionMaintenanceRequestALOptionalinside the Instrument component
PositionReportAPOptionalinside the Instrument component
QuoteSOptionalinside the Instrument component
QuoteCancelZOptionalinside QuotCxlEntriesGrp › Instrument
QuoteRequestROptionalinside QuotReqGrp › Instrument
QuoteRequestRejectAGOptionalinside QuotReqRjctGrp › Instrument
QuoteResponseAJOptionalinside the Instrument component
QuoteStatusReportAIOptionalinside the Instrument component
QuoteStatusRequestaOptionalinside the Instrument component
RFQRequestAHOptionalinside RFQReqGrp › Instrument
RequestForPositionsANOptionalinside the Instrument component
RequestForPositionsAckAOOptionalinside the Instrument component
SecurityDefinitiondOptionalinside the Instrument component
SecurityDefinitionRequestcOptionalinside the Instrument component
SecurityListyOptionalinside SecListGrp › Instrument
SecurityListRequestxOptionalinside the Instrument component
SecurityStatusfOptionalinside the Instrument component
SecurityStatusRequesteOptionalinside the Instrument component
SecurityTypeRequestvOptionaldirectly on the message body
SecurityTypeswOptionalinside the SecTypesGrp component
SettlementInstructionRequestAVOptionaldirectly on the message body
SettlementInstructionsTOptionalinside the SettlInstGrp component
TradeCaptureReportAEOptionalinside the Instrument component
TradeCaptureReportAckAROptionalinside the Instrument component
TradeCaptureReportRequestADOptionalinside the Instrument component
TradeCaptureReportRequestAckAQOptionalinside the Instrument component

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 460 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const product = message.fields[460]?.raw;// e.g. "1" — AGENCY// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(460)  ?.enumValues?.find((e) => e.value === product)  ?.description;

Other int fields

Decode this in your own code

The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.

npm i @boarteam/fix @boarteam/fix-dict-fix44