"Legacy ERP says 5A992, supplier says EAR99": when does the conflict justify an integration review?
A retrospective for export-control software product managers: reconstruct the evidence behind a 5A992/EAR99 conflict and decide whether it reveals a repeatable integration need or only a one-off classification question.
Signals to watch
- A legacy 5A992 record and a supplier EAR99 designation may cover the same revision, but neither can be traced to complete evidence
- The discussion moves from one shipment to repeated catalogue, import or order-screening work
- A team is changing a product-data flow and asks how source, revision and review status will survive the move
“Legacy ERP still has 5A992 for the A-series.”
“The latest supplier sheet says EAR99. I am not sure it covers the same hardware.”
“We are remapping the catalogue this month. Can the import keep the source and revision, or only one code?”
These three lines form a composite, deliberately incomplete Telegram thread. They do not describe a real customer, export or legal conclusion. No part number, model revision, encryption configuration, source date, destination, end user or end use is known.
The first two lines sound like a classification question. The third changes their commercial meaning. A team is not merely asking which code is correct for one shipment; it may be about to carry an unresolved classification into a new catalogue or order-screening flow.
That is the moment an export-control software product manager should notice. They may be following authorised Telegram groups used by electronics exporters, semiconductor distributors, freight forwarders and trade-compliance teams. The useful signal is not the appearance of “ECCN” or “EAR99” by itself. It is a classification conflict arriving together with product-data work, an owner and a near-term system change. If the product manager sees it only after the data model has been agreed, the new workflow may already be built around one code and a free-text note.
The first message is a warning, not yet an integration requirement
5A992 is an Export Control Classification Number (ECCN) on the Commerce Control List. EAR99 is a designation used for an item subject to the Export Administration Regulations but not described by another ECCN. The Bureau of Industry and Security (BIS) explains both concepts in its item-classification guidance.
The two labels can appear side by side without creating a true conflict. The old ERP row may describe an earlier hardware revision. The supplier sheet may cover a component rather than the finished system. One record may refer to software with a different encryption configuration. A copied code may simply have outlived the document that once supported it.
Before treating the thread as a product opportunity, the product manager needs to know whether both records describe the same item, revision and effective period. If the answer is unknown, the right status is “needs evidence”, not “high-intent integration”. A single shipment question may require a classification reviewer, but it does not automatically justify a software project.
Rebuild the chain from the field that failed
The retrospective starts with the ERP field, not with the question “which code should win?” Open the legacy row and recover the product identifier, model or software version, date, source document and any review note. If the row contains only 5A992, it preserves a conclusion but not the path that produced it.
Next, place the supplier sheet beside that row. “Latest” matters only after the sheet is tied to an issuing legal entity, a covered part or model, a revision and a date. A newer PDF for a component does not override an older classification for a finished product merely because its timestamp is later.
The classification route is part of the evidence. BIS describes three ways to classify an item: obtain a classification from the manufacturer, producer or developer; self-classify by applying the Commerce Control List; or submit a formal classification request to BIS. The BIS classification-request page explains the official request route. A product record should therefore preserve where the conclusion came from, not flatten supplier information, an internal determination and a BIS response into interchangeable text.
Once the two records are put back into context, the apparent conflict usually separates into one of three states. Different revisions require versioned classification records. The same revision with different technical facts requires a qualified export-control reviewer to resolve the evidence. Two untraceable codes mean there is not yet a classification record worth migrating. None of these states can be settled by choosing the stricter-looking value or the most recent timestamp.
Destination, end-user and end-use screening remain separate transaction questions. EAR99 does not make a shipment automatically permissible, and an ECCN alone does not decide the licence outcome.
The commercial signal appears when the conflict becomes repeatable work
The thread becomes worth an integration review when the classification problem has somewhere to repeat. The team may be moving a catalogue, importing supplier data, adding order screening or trying to keep multiple product revisions aligned. It may be asking why every update arrives as a spreadsheet and loses its source after upload. Those are product-workflow clues; “which ECCN?” on its own is not.
Three details make the candidate stronger:
- The problem crosses records. The same uncertainty affects multiple SKUs, revisions, imports or order handoffs rather than one isolated shipment.
- A system boundary is visible. Someone mentions a catalogue migration, application programming interface (API), bulk upload, ERP mapping or screening workflow where the evidence is being reduced to one code.
- There is an owner and a decision window. A product, data or compliance owner is preparing a review and needs to decide what the new flow must retain.
The composite thread does not prove any of these facts. “This month” and “can the import keep the source?” are reasons to review the candidate promptly, not permission to infer a buyer, budget or approved project.
In TOP Prospect, a product manager can define a rule for authorised groups that looks for the combination of classification conflict language—old model, supplier sheet, ECCN and EAR99—with system-change language such as catalogue, import, API or order screening. Related fragments can be filtered, merged, deduplicated and ranked while retaining the original message, source and time for human review. The product cannot confirm that two posts describe the same organisation or item, access private transaction records, classify the product, contact the author or decide licence requirements.
Scope the integration around reviewable states, not a perfect answer
The discovery conversation should now stay on product data. Ask which system first loses the source document; how an item and revision are identified; who supplies and approves a classification; whether historical decisions and effective dates must remain visible; and how an unresolved conflict should be represented without silently selecting one code.
A workable integration does not promise to produce the legally correct ECCN on its own. It lets an authorised reviewer trace every active value to an item version, classification route, technical basis, effective date and review state. It also keeps transaction screening outside the item-classification field.
This distinction changes the opportunity assessment. If the team only needs a qualified person to answer one shipment question, the need may be advisory rather than integrative. If classifications repeatedly move from supplier files into ERP, catalogue and screening systems without their provenance, the product problem is already visible—even before anyone asks for a vendor demo.
Return to the three fragments
The legacy 5A992 and supplier EAR99 should not be reconciled inside Telegram. If they cover different revisions, the catalogue needs versioned records. If they cover the same revision but rely on different technical facts, the conflict goes to a qualified reviewer and the integration must preserve an unresolved state. If neither has a traceable source, the team first needs evidence remediation.
The product manager keeps evaluating the opportunity only when the later catalogue message shows that this failure will repeat across a data flow. That closes the opening thread without pretending the software can make an export decision.
The integration signal is not “someone asked for an ECCN”. It is a team preparing to carry an untraceable classification conflict into a new product-data workflow.
FAQ
What must be checked before treating 5A992 and EAR99 as a conflict?
Confirm that both records describe the same commodity, software or technology, the same revision and configuration, and the same effective period. Then compare their sources and technical basis.
Can a supplier sheet settle the classification?
Not by itself. Its issuer, covered item, revision, date and supporting technical basis must be tied to the product record and reviewed against current requirements.
Does EAR99 mean a shipment is automatically allowed?
No. Destination, end user and end use may still create restrictions or licence requirements.
When does the conflict justify an integration review?
When it recurs across product records or system handoffs and the team needs versioned sources, effective dates and review states to survive catalogue, import or screening workflows.
Frequently asked questions
What must be checked before treating 5A992 and EAR99 as a conflict?
Confirm that both records describe the same commodity, software or technology, the same revision and configuration, and the same effective period. Then compare their sources and technical basis.
Can a supplier sheet settle the classification?
Not by itself. It is useful evidence only when its issuer, covered item, revision, date and supporting technical basis can be tied to the product record and reviewed against current requirements.
Does EAR99 mean a shipment is automatically allowed?
No. BIS explains that destination, end user and end use may still create restrictions or licence requirements even when an item is designated EAR99.
When does a classification conflict become an integration requirement?
When the conflict recurs across product records or system handoffs and the team needs versioned sources, effective dates and review states to survive catalogue, import or screening workflows.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
