1. Separate density from addressed-unit organisation
Density describes the total storage quantity, while organisation describes how the identified memory groups data for communication and addressing. A capacity-only stock entry can therefore leave the addressed-unit question unanswered. Microchip's introductory description distinguishes dedicated byte communication from dedicated word communication within the named EEPROM families. The meaningful distinction is the organisation of the communication unit, rather than another name for the total-density field or a calculation of available storage.
This matters when two records retain the same broad EEPROM description but omit their complete variants. A matching density does not establish that their communication organisation is the same. Preserve the organisation named by the applicable product documentation instead of completing it from the family heading. This guide does not calculate address counts or reproduce protocol details. It identifies why total quantity of stored bits and the organisation used to communicate with those bits belong in separate technical descriptions.
2. Retain dedicated variant identity
In Microchip's named 93AA46, 93LC46 and 93C46 context, A devices provide a dedicated byte organisation and B devices a dedicated word organisation. Retain the complete reference so that this distinction stays with its documented family. It is a manufacturer-specific example of fixed variants, not permission to decode A or B in every other EEPROM product name. The final characters should remain part of the identity rather than disappearing when a list is shortened.
Dedicated organisation also differs from a claim about an adjustable setting. A product described with one fixed communication organisation should not acquire selectable capability because a neighboring member of the family offers it. Conversely, a list containing only the shared family root may no longer identify which kind of product is present. Keeping the variant-specific description intact gives the recipient a concrete technical question to resolve, rather than treating every density-matched EEPROM as the same addressed-unit arrangement.
Consider a record that retains the family root and density while dropping the dedicated or selectable variant. Restoring the full variant changes the communication-organisation description even though the density entry remains unchanged. This shows why the missing characters are a technical identity question, rather than merely a packing suffix. The named A/B/C distinctions provide the example's basis, but another EEPROM family needs its own description. Keep fixed organisation, selectable capability and any separately documented assembly choice distinguishable before considering the data-state or host-operation questions.
3. Separate selectable capability from the actual assembly
Microchip describes the C variants as word-selectable, with organisation determined through an external selection. That is a capability statement about the identified device. It differs from the fixed-organisation description and should retain its own wording. The introductory evidence supports asking which organisation an actual assembly selects, but it does not identify that selection merely because the component carries the selectable variant name. Product capability and assembly state remain separate subjects.
For loose selectable devices, describe the supported capability rather than an invented installed setting. Where an assembly record exists, retain its identity and scope as assembly evidence instead of presenting it as the inherent organisation of every loose component with that code. This article supplies no selection level, physical terminal instruction or connection procedure. Its technical contribution is the distinction between an organisation fixed by the product variant and one whose actual use depends on an external selection.
4. Keep addressing outside protection and data-state claims
Organisation does not answer the memory's protection or contents questions. A byte or word communication description says how information is grouped, not whether writing is currently permitted or which data the device contains. Likewise, the raw-versus-managed NAND guide locates management responsibility, while the NAND-organisation guide concerns page/spare and transfer-register roles. Those architecture discussions cannot replace the narrower EEPROM decision about dedicated versus selectable addressed-unit organisation.
For an ICULTRA EEPROM enquiry, retain the exact variant, its supported organisation and any separately identified assembly context. Keep existing contents or protection declarations distinct from those product attributes. The recipient can then assess the identity being offered without assuming a blank device, an executed erase operation or a compatible host. No command, programming recipe, endurance or security result follows from this classification. It preserves a specific communication-organisation distinction before any further assessment of the physical material or intended use.
Sources and further reading
Microchip DS20001749L physical p1 description and the opening organisation prose on p7 support the named dedicated/selectable distinction. Numeric organisation arithmetic, selection levels, physical pins, commands, contents, wear, security and compatibility are excluded.