AuctionLogistix editorial guide, published September 23, 2026. Copart’s official pickup and delivery guidance was reviewed on September 23, 2026. Its workflow is a platform-specific example, not a universal auction rule. This is operational education, not auction policy, legal advice, carrier-compliance advice, or a promise of pickup, delivery, pricing, or availability.
Sources:
Start with the decision, not a generic “shipping” status
After an auction award, “shipping” can mean several different things. A buyer may use the auction platform’s delivery offering, arrange an outside transporter, or collect the vehicle through the facility’s self-pickup process. Copart’s current help guidance describes all three paths: Copart Delivered, a third-party transporter selected through Payments Due, and in-person pickup scheduled through the platform. Those are options, not interchangeable confirmations. A clean operating file should record which path the buyer intends to use for one specific unit, the source of that choice, and its current status. Do not report “transport arranged” merely because someone discussed a preference or opened a quote screen. The planning record should distinguish chosen, requested, submitted, confirmed, and completed. That simple separation makes it easier to see what must happen next and stops a broad purchase list from turning a preliminary decision into a driver instruction.
Keep auction delivery and outside transport as separate workflows
Platform delivery and outside transport can both move a vehicle, but they are not the same operational process. Copart says a buyer can select vehicles in Payments Due and use Order Delivery for its delivery option. Its guidance also says a buyer can select Send to Transporter, enter a transporter email when needed, and that the transporter receives a Gate PIN plus instructions to book pickup and check in. Those facts show why the record needs two separate fields: the selected movement path and the facility handoff status. Choosing an outside transporter is not proof that the transporter has accepted the shipment, has a driver assigned, or has a pickup time. Likewise, a platform delivery order should be recorded from the actual order confirmation, not inferred from an estimate. Preserve the confirmation reference and the latest instruction that applies to the unit. Do not copy controlled access details into a broad manifest or casual message thread.
Treat self-pickup as a facility process, not a fallback label
Self-pickup is not simply “no carrier needed.” It has its own facility controls, timing, equipment, and handling questions. Copart says a buyer can schedule pickup from Payments Due and notes that arriving late can mean losing a place in line and needing another pickup time. It also states that vehicles cannot be driven off its facilities for legal and liability reasons. Those details are platform-specific, but the operating lesson is broader: record the applicable facility instruction before treating self-pickup as executable. Put the unit identity, actual site, appointment or queue step, responsible pickup person, known vehicle condition, and destination in the record. Do not assume an award email establishes a pickup slot, a loading arrangement, or permission to use a particular vehicle or trailer. If the plan changes from self-pickup to an outside transporter, mark the old path superseded and document the new facility handoff rather than silently changing a spreadsheet cell.
Use a one-line decision record for every unit
A useful decision record is short enough to maintain and specific enough to audit. It can read: “Stock 4821: outside transporter selected; Send to Transporter completed by buyer operations September 23; facility access instruction pending; transport planning requested; no carrier pickup confirmation.” For a platform-delivery path, substitute the actual order state and reference. For self-pickup, state the appointment or check-in status supplied by the facility. The record should identify who owns the next action and when the source was checked. Avoid vague labels such as “sent,” “handled,” or “with dispatch.” They conceal whether the buyer has acted, the auction has issued a handoff, a transporter has received usable instructions, or a movement has actually been confirmed. This is especially important in a multi-unit purchase, where similar vehicles can be on different paths at the same time. The unit file, not a lane-level assumption, should remain the authority.
Do not confuse an estimate, a request, and confirmation
An estimate can be useful for planning, but it is not a dispatch confirmation. A request to an outside transporter starts a conversation; it does not establish availability, pickup timing, delivery timing, equipment, or price. A facility credential or appointment can be necessary for pickup while still leaving carrier coordination unresolved. Keep each fact in its own field: auction-side access, requested transport path, shipment-planning status, and receiving readiness. Date every update and retain the source message or platform reference. If someone says a unit is “booked,” require the record to show what is actually confirmed and by whom. A practical status set is: path selected; auction handoff pending or complete; transport planning pending or active; pickup appointment or instruction pending or confirmed; destination readiness pending or confirmed. The vocabulary is less important than refusing to let one completed step stand in for all of them. This guide does not promise that any option will be available for a particular vehicle or date.
Build the destination side before finalizing the path
The transport choice should work at the receiving end as well as the auction gate. Whether the vehicle moves through a platform delivery option, an outside transporter, or self-pickup, record the destination address, receiving contact, normal hours, gate or lot instruction, and any known constraint. The receiver may have a limited window, a capacity issue, or a condition-specific process that changes the practical choice. Do not tell an auction or transporter that a unit is ready to move solely because the origin handoff is complete. For multiple units, identify which destination facts apply to each vehicle instead of assuming the whole group can arrive together. If a buyer is comparing paths, use the same known facts for each option: actual pickup site, release state, vehicle condition, timing constraints, and receiving readiness. That makes the decision comparable without inventing a price, a service level, or a promised arrival.
Run a final path check before sharing the handoff
Before a unit becomes a live pickup handoff, confirm the current file answers six questions. Which movement path was chosen? What source proves that selection? Has the auction or facility completed its applicable handoff step? Is transport coordination confirmed, still pending, or not needed because self-pickup is genuinely executable? Are known keys, mobility, and loading facts stated without assumption? Can the named destination receive the unit? If any answer is missing, keep the vehicle in a pending state and name the owner of the next answer. Copart’s guidance is a useful reminder that auction-side delivery, third-party transport, and self-pickup use different processes; buyers should follow the current instruction for their own facility and unit. Once the decision record contains usable facts rather than labels, share it through the AuctionLogistix planning flow so the transport conversation begins with the right path and the open exceptions visible.