AuctionLogistix editorial guide, published August 30, 2026. The official 2025 annual edition of 49 CFR § 393.128 on GovInfo was reviewed on August 30, 2026 for limited carrier-side context. This is operational education, not an inspection, auction policy, legal advice, carrier-compliance advice, or a promise of equipment, pickup, delivery, price, or availability.
Sources:
Configuration is a handoff fact, not a model-name shortcut
An auction listing gives a buyer a starting point, but a year, make, and model do not necessarily describe the unit that will arrive at the pickup gate. A vehicle may have an altered ride height, oversized tires, roof equipment, loose accessories, damage, or an added load. It may also have none of those things. The planning record should not fill that gap with a guess. Its job is to show what is known about this particular vehicle, where that information came from, and what still needs confirmation. Keep configuration separate from the auction release, the condition report, and the eventual carrier paperwork. That preserves a simple boundary: the buyer passes along reliable facts; the transport professional decides how those facts affect the shipment.
Start with a stable unit identity
Before describing configuration, make sure every note points to one vehicle. Use the VIN when available, plus the auction lot or stock number, year, make, model, sale branch, and actual pickup location if it has been confirmed. A broad note such as “lifted truck at Dallas” is weak when several similar units are in a purchase group. A unit-level record lets a coordinator find the supporting listing, release message, condition material, or photo without guessing which vehicle the comment belongs to. If the physical pickup point differs from the sale branch, mark that as a separate fact. Configuration detail is useful only when it travels with the right vehicle and the right location.
Write only loading-relevant facts you can support
Use a short configuration block with the source beside each fact. For example: “auction photos show roof rack”; “listing reports aftermarket wheels”; “buyer observed lowered stance”; or “accessories unknown.” Notes may cover reported dimensions, unusual clearance, visible exterior attachments, loose or removable parts, or a reported vehicle weight rating when the source supplies it. Do not turn an image into a mechanical conclusion, and do not label a vehicle standard merely because no exception appears in the listing. If the information has not been verified, write unknown or pending confirmation. The point is not to create a detailed inspection; it is to prevent a known feature from disappearing in a chain of messages.
Do not guess at weight or choose a securement method
Vehicle size and weight can matter to a transport conversation, but a buyer should not invent either value from a familiar model. The federal text cited below draws a real regulatory distinction: 49 CFR § 393.128 applies to automobiles, light trucks, and vans individually weighing 10,000 pounds or less, while the next section addresses heavier vehicles, equipment, and machinery. Section 393.128 also sets carrier-side securement requirements for its covered vehicles. That is context for why a reported weight-related or configuration detail belongs in the record. It is not a buyer formula for classifying a unit, selecting equipment, naming tiedown points, or directing securement. Preserve the source of any number and let the carrier determine the applicable handling and compliance approach.
Make mobility and configuration separate fields
A vehicle can have a normal-looking configuration but still be reported non-running, missing keys, or unable to steer, brake, or roll. Conversely, a vehicle can be mobile and still have a feature that needs attention in the planning conversation. Keep those facts on separate lines. In the condition field, use reported language: keys present, reported to run, reported to steer, reported to brake, reported to roll, or unknown. In the configuration field, state only the supported physical detail. This prevents a reader from treating a condition report as a complete description of the vehicle, or treating an accessory note as proof that the vehicle can be loaded routinely. Attach permitted photos or the source report where useful, and label direct observation differently from an auction-provided statement.
Give every material unknown an owner and next action
An unconfirmed configuration point should become an exception, not a silent blank. A useful exception line names the unit, the exact question, the source already reviewed, the person responsible for follow-up, and the next action. For example: “Lot 218, roof equipment visible in photos; buyer operations to verify whether it remains on vehicle before pickup.” That is more actionable than “special unit.” Do not assign an arbitrary deadline unless the auction or receiver has supplied one. A requested pickup date may be recorded nearby, but it does not resolve the condition or configuration question. For multiple vehicles, use the same fields and vocabulary so a lane summary can show which units have confirmed facts, which have reported features, and which require clarification.
Recheck the record when a location or receiver changes
Configuration does not live in isolation from the rest of the move. A new storage yard can provide different pickup information; a destination may have an access constraint that makes a reported vehicle feature relevant to the handoff. When the pickup location, vehicle status, or receiver changes, compare the current configuration block with the active transport request and update the source and time. Do not quietly overwrite an earlier record and assume the revision reached everyone. Keep the current note with the release confirmation, condition evidence, and receiving instructions. That gives the buyer, coordinator, and receiver a common factual trail without presenting an old listing note as a current instruction.
Use a short readiness check before requesting transport
Before the vehicle enters transport planning, ask: can the unit be identified; is the release usable or clearly pending; is the actual pickup location known; are keys and reported mobility stated; are known configuration facts sourced; and can the destination accept the vehicle? A pending configuration question does not automatically prevent a planning conversation, but it should not be hidden behind a routine label. This guide does not guarantee a truck type, a pickup or delivery time, price, availability, or a carrier decision. It gives the team a cleaner record to work from. Once known facts and exceptions are visible, use the AuctionLogistix planning flow to share the complete lane with the transport team.