1. Identify the actual IC or supplied board
Begin with what the owner is releasing: loose driver ICs, populated driver boards or a larger drive assembly. Preserve the full manufacturer IC code and any assembly identifier in separate fields. A board sold under an internal controller number can contain a driver, but the IC's category should not silently define the identity or completeness of the whole supplied board.
Retain original label readings, purchase references and permitted board records that connect the identifiers. If a device marking is shortened, keep that reading alongside the supported full code rather than replacing it with an assumed family member. A photograph may help a reviewer locate the correct record, but an unreadable identifier should remain unresolved instead of becoming a confirmed driver classification.
Give the documented motor class its own field. A warehouse category such as motor controller can cover different product contexts and does not answer whether the exact identified driver is described for a stepper or brushed-DC class. Keep quantities attached to supported identities, particularly when loose ICs and surplus boards were stored together under the same programme description.
2. Retain the documented motor-driver class
Texas Instruments' DRV8825 product introduction identifies a bipolar-stepper motor driver. Its DRV8871 product reference identifies a brushed-DC motor driver. These product examples support retaining motor-driver class independently from the general controller category. They are manufacturer identity descriptions, not a statement that either product is present in a seller's inventory or available for a current transaction.
Use each offered product's own applicable reference. Do not turn the two examples into a universal rule based on bridge count, package shape or board layout. A generic topology observation should not replace the manufacturer's explicit class description. This guide supplies no bridge-state interpretation, wiring instruction or numerical operating requirement for an unidentified driver.
Where an inventory record and the exact product description use different terminology, preserve both and ask the technical owner to reconcile the line. An old machine label may describe the complete drive function rather than the internal IC class. Correct classification should show which level each term describes, without rewriting an assembly name as though it were a complete component identifier.
3. Separate class from a configured drive
A motor-driver class identifies the product context; it does not establish the configuration of a board containing that product. Keep any available current-control, decay or step-configuration record with its actual assembly and revision. If those records are absent, state the gap. A product introduction should not fill missing settings or imply that the board is prepared for a particular motor.
The related decay-mode guide addresses a sourcing decision within a stepper-driver requirement. This seller review comes earlier: it establishes the stepper versus brushed-DC identity of the offered material. Keeping those decisions separate prevents a known decay-mode discussion from becoming an assumed configuration for every surplus board carrying a similar-looking driver.
Retain any existing operating or inspection report with the identified units, date, stated conditions and scope. Previous use with a motor is historical context, not approval for another motor or a present operational result. Describe visible board, terminal or body issues where observed and disclose unknown removal or handling history without converting the documented class into a condition guarantee.
4. Offer class-identified driver groups
Arrange released groups by exact supported identity and motor-driver class, preserving the actual sale unit and included-item list. Keep class-unknown items distinguishable from identified stepper and brushed-DC products. If one board record covers only a subset of assemblies, retain that subset rather than applying its IC description and configuration history to visually similar boards elsewhere in the lot. A loose-IC group and a board group can share an internal driver code while requiring different quantity units, included-item descriptions and identification records.
Use the excess-stock list for actual quantity, location, packing and authority to release the material. Add the manufacturer class reference and a separate field for any prior equipment context. This allows a reviewer to see whether the enquiry concerns a known driver IC, a documented board or an unresolved controller assembly, without assuming that the internal component fully identifies the supplied object.
For an ICULTRA motor-driver enquiry, share full codes, supported class descriptions and the permitted records linking them to the offered groups. Explain missing assembly or configuration information and ask what further identification is required. The product examples do not establish motor compatibility, a tested drive or purchase eligibility. Accepted lines, any evaluation and commercial terms need separate confirmation for the actual stock.
Sources and further reading
Manufacturer documents support the technical guidance above. They do not confirm our stock, authorisation or the condition of any offered lot.