ETD and ETA in Shipping: A Frozen Cargo Buyer Guide
Jun 15, 2020

ETD means Estimated Time of Departure. ETA means Estimated Time of Arrival. In an ocean-freight booking, ETD usually refers to the vessel's expected departure from a named port, while ETA usually refers to its expected arrival at a named destination port. Both are forecasts. They can change, and neither tells you by itself when frozen cargo will be ready at the factory, loaded into a reefer, discharged, cleared by customs or delivered to your warehouse.
That distinction matters because one short date can be interpreted five different ways. A sales team may hear "ETA 12 August" and promise stock on 12 August. The carrier may mean vessel arrival at the port anchorage or terminal. The container might still need discharge, import release, pickup and inland delivery. For frozen fruit and vegetables, the commercial plan also has to protect refrigeration at every handoff.
Direct answer: Use ETD and ETA as versioned transport estimates, not guaranteed delivery commitments. Record the vessel or transport leg, the exact location, local time zone, update time and source. Pair them with cargo-ready date, reefer and document cut-offs, ATD, ATA, discharge, customs release and final-delivery milestones before you plan inventory or promise a customer date.

ETD, ETA, ATD and ATA Answer Different Questions
The International Maritime Organization defines estimated and actual arrival and departure times against a specified location. That final phrase is important. "ETA" without a location is incomplete. A vessel can have an ETA at a pilot boarding place, anchorage, berth or port, and a container can have a different expected time at a rail ramp, depot or consignee warehouse.
| Term | Plain meaning | What you must add |
|---|---|---|
| ETD | Estimated time of departure | Vessel/leg, departure location, time zone, source and revision |
| ETA | Estimated time of arrival | Arrival location, event meant, time zone, source and revision |
| ATD | Actual time of departure | Confirmed event and location; do not substitute a planned sailing time |
| ATA | Actual time of arrival | Confirmed event and location; arrival is not automatically cargo availability |
Estimated events support planning; actual events record what happened. If the original booking shows ETD 3 September and the vessel sails on 5 September, 5 September is the ATD. Do not overwrite the original ETD and lose the variance. Keep both values so you can explain the delay and evaluate schedule performance later.
Also distinguish the transport unit from the cargo. A vessel can depart while a rolled container remains at the terminal. A container can arrive at a transshipment port without reaching the destination port. A truck can collect a reefer after vessel discharge but before the cargo is available at your receiving dock. A useful status line therefore includes the container number, vessel/voyage, port code and event.
Name the Reference Point Before You Use the Date
Write "ETD Xiamen port, vessel ABC voyage 123E" instead of "ETD Friday." Write "ETA Rotterdam terminal, 14:00 CET" instead of "arrives on the 18th." If the date refers to a feeder vessel, mother vessel or second transshipment leg, say so. A container route can carry several ETDs and ETAs because each leg has its own departure and arrival.
Ask what "arrival" means in the system you are reading. Vessel arrival, berth arrival, discharge completion, container availability and final delivery are separate events. They can fall on different days. A destination warehouse should book labor against a realistic delivery appointment, not simply against the vessel ETA. Import documentation and the broker's pre-clearance work should begin earlier.
Time zones create another quiet error. A departure displayed in China Standard Time and an arrival displayed in local European or American time cannot be subtracted casually. Daylight-saving changes can shift the local offset. Preserve the time zone with every timestamp, or store an ISO-style value and show the local equivalent to the person using it.
Practical example: Your booking update says "ETA Hamburg 08:00, 18 October." Procurement records it as vessel ETA at the destination port, local time. Sales receives a separate "expected warehouse availability 22–24 October" range after discharge, release and trucking. The company avoids promising finished stock on 18 October while the container is still under terminal and customs processes.

ETD Does Not Replace the Export Cut-Off Plan
A vessel ETD sits near the end of a longer origin schedule. Frozen cargo has to be produced, inspected, packed, placed into cold storage, released, stuffed and gated in before the carrier's deadlines. The shipping instruction and verified gross mass may have their own cut-offs. Customs or inspection requirements can add earlier internal deadlines.
Carrier schedules show why "three days before ETD" is not a universal rule. Published cut-off tables can set different deadlines for empty-container pickup, dry cargo, frozen reefer cargo, chilled reefer cargo, dangerous goods, shipping instructions and VGM. The deadline also changes by service and terminal. Use the current booking confirmation and current local carrier notice for the exact shipment.
Build backward from the earliest firm cut-off. If the frozen reefer gate-in cut-off is 10:00 Tuesday, a Tuesday afternoon production finish is already too late even if the vessel ETD remains Thursday. Allow time for finished-product release, carton coding, palletization, reefer inspection, pre-cooling where specified, stuffing, seal confirmation, transport to the terminal and unexpected holds.
| Origin milestone | Evidence to retain | Decision if late |
|---|---|---|
| Cargo ready and QA release | Lot, quantity, packing, inspection and release status | Escalate before booking promises are repeated |
| Empty pickup and reefer check | Container number, condition, unit status and requested setting | Replace or rebook if acceptance cannot be met |
| Stuffing and seal | Loading record, temperature checks, photos, seal number and count | Hold release until discrepancies are resolved |
| CY/reefer gate-in cut-off | Terminal acceptance and gate-in event | Confirm late-gate approval or move to a viable sailing |
| SI and VGM cut-offs | Submission version, receipt and correction record | Correct before the carrier deadline; do not assume gate-in cures it |
Packaging decisions must be finalized early enough to support this sequence. The XMSD frozen-food packaging overview shows common bag, carton, label and pallet choices. The actual order still needs approved artwork, case marks, pack count, pallet pattern and document data before dispatch.

Keep a Versioned Schedule Instead of One Overwritten ETA
Shipping estimates evolve. The first date may be a pro forma schedule. The booking confirmation may provide a revised estimate. Port congestion, berth availability, weather, mechanical issues, blank sailings, omitted calls, transshipment connection changes and customs holds can move later forecasts. A later ETA is not automatically proof of poor product or supplier performance; it is a signal to identify the event owner and commercial consequence.
DCSA's container track-and-trace framework organizes visibility across pre-shipment, pre-ocean, ocean, post-ocean and post-shipment phases. Its port-call standard also distinguishes estimated, requested, planned and actual event times. You do not need to reproduce the entire data model in a purchase order, but you should preserve the same discipline: event, location, equipment, timestamp type and update source.
Use a simple change log with columns for "original," "current," "actual," "source," "updated at" and "next action." Do not replace yesterday's ETA with today's value and erase the history. That history explains when sales, customs, warehouse and customers were notified. It also separates a one-time schedule change from a recurring lane or carrier pattern.
Practical example: The original ETD is 6 May and ETA is 2 June. A carrier update moves ETD to 9 May and ETA to 5 June. The container actually departs on 10 May. Your log retains all five values, records the ATD, changes the destination planning range, and requests the next confirmed transshipment milestone. It does not report "on the water" from an old ETD.

Frozen Cargo Needs a Cold-Chain Timeline Beside the Vessel Timeline
Codex guidance for quick-frozen foods uses a product temperature of −18°C or colder through the cold chain, subject to permitted tolerances set by competent authorities. It calls for suitably insulated transport, pre-cooled vehicle compartments or containers, temperature supervision at loading, effective stowage, correct refrigeration operation and fast transfer. The XMSD frozen-food definition guide explains how the quick-freezing outcome connects with that continuing cold chain.
An ETD delay does not automatically mean the cargo warmed. A reefer may remain connected at the terminal and continue operating. Conversely, an on-time ETD does not prove correct cargo temperature. Verify the requested set point, container condition, loading temperature basis, air-flow requirements, vent setting where applicable, power continuity, monitoring method and exception procedure for the specific product and order.
Do not confuse return-air, supply-air and product-core readings. They answer different questions and can change at different speeds. State which one the specification or receiving procedure uses. For a temperature excursion, retain the logger record, duration, position, ambient context, product measurements and inspection result. One isolated air reading is not a complete disposition decision.
The receiving side needs a contingency. Who monitors the reefer if customs holds the container? Who can approve a change of depot or delivery appointment? Where will the product go if the booked cold store has no space on the revised date? The XMSD cold-chain distributor framework is a useful starting point for aligning frozen storage, distribution and product requirements before shipment.

Convert ETA Into a Warehouse-Ready Range
The vessel ETA is one input to inventory planning, not the finished output. Add expected time for berth or discharge, terminal processing, customs or inspection, document release, haulage appointment, unloading and receiving checks. Use a range when those steps are uncertain. Separate the best current forecast from the later customer-available date.
Worked example: A frozen vegetable container has a current vessel ETA of 4 November. Your documented planning allowances are 1 day for discharge and availability, 2 days for customs and release, and 1 day for trucking and receiving. The working warehouse date is therefore 4 + 1 + 2 + 1 = 8 November. Adding a two-day operational buffer produces a customer-planning range through 10 November. These illustrative allowances are not a carrier or XMSD promise; use lane-specific evidence and current broker information.
The calculation should be recalculated whenever the vessel ETA or a downstream milestone changes. If the vessel arrives on 4 November but the container is selected for inspection, the original four-day clearance assumption may no longer apply. Update the reason, owner and next checkpoint. Do not merely add "delay" to a spreadsheet without identifying what will confirm release.
For safety stock, compare the forecast arrival range with actual daily usage and existing inventory. If usable stock is 18,000 kg and consumption is 1,500 kg per day, coverage is 18,000 ÷ 1,500 = 12 days. If the warehouse-ready range extends beyond that coverage, you need an allocation, alternative stock or production response before the shortage occurs. Schedule language becomes commercially useful only when it changes a decision.

Build One Milestone Sheet for Every Frozen Shipment
Start with the commercial identity: purchase order, SKU, quantity, Incoterm, named place or port, container number, seal number, booking number and vessel/voyage. ETD and ETA do not allocate cost, risk or responsibility by themselves. The agreed Incoterm, contract and service scope do that. Do not infer responsibility merely because one party supplies a schedule update.
Add the product timeline: planned production, actual production completion, QA release, cargo-ready date, cold-store location, packing confirmation and document readiness. If the order depends on a certificate, test report or destination document, name the file and required issue time. The XMSD certification and document center shows available support categories; the actual certificate holder, scope, validity and order requirement must still be checked.
Then add the container timeline: empty release, pickup, inspection, pre-cooling requirement, stuffing start and completion, seal, gate-in, power confirmation, cut-offs, ETD, ATD, transshipment arrival/departure, destination ETA, ATA, discharge, availability, customs release, pickup, delivery and receiving result. Mark every value as estimated or actual.
Assign owners. The supplier can confirm production and loading evidence. The forwarder or carrier supplies booking and movement updates. The customs broker controls clearance preparation and reports holds. The destination warehouse confirms delivery appointments and receiving. One coordinator should reconcile the whole sheet, but should not invent events owned by another party.
Use an Exception Rule, Not Constant Reassurance
Define which changes require notice. A one-hour vessel update may not affect a monthly industrial production plan. A two-day change near an inventory runout can be critical. Set thresholds by product, destination and customer commitment. Examples include missed reefer cut-off, rolled container, unconfirmed transshipment, ETA shift beyond one business day, customs inspection, power interruption or temperature alarm.
Every exception notice should state four things: what changed, what evidence confirms it, what the current impact is, and when the next update will come. "Vessel delayed" is incomplete. "Carrier moved the mother-vessel ETD from 6 to 9 May; the container remains gated in and powered; current destination ETA is 5 June; next carrier update expected 7 May 15:00 CST" is actionable.
Close the record after delivery. Compare original ETD with ATD, original ETA with ATA, and ATA with actual warehouse receipt. Record temperature and package condition at receiving. The differences reveal whether the planning problem occurred before sailing, during ocean transport or after arrival. That makes the next lead-time and safety-stock decision more realistic.

What to Send With a Frozen-Food Shipping Request
A useful request includes the product, cut or grade, pack, quantity, target shipment window, destination port, final delivery point, Incoterm, document list, temperature requirement and any restricted delivery dates. State whether mixed products or mixed suppliers are involved. Identify whether the date you care about is cargo ready, vessel departure, port arrival or warehouse receipt.
For a repeat program, share consumption rate, minimum safety stock and acceptable arrival window. For a promotion or factory shutdown, state the non-negotiable date and the consequence of missing it. We can then discuss product availability and coordination in the right sequence. The XMSD buyer solutions overview helps frame different retail, foodservice, distributor and processing needs.
XMSD coordination note: Send your frozen product, specification, pack, quantity, destination, target warehouse window and required documents. We will review the product and shipment inputs, identify the dates that need confirmation, and separate estimated sailing milestones from order-specific commitments.
Frequently Asked Questions
What is the difference between ETD and ETA?
ETD is the estimated time of departure from a specified location. ETA is the estimated time of arrival at a specified location. Both are forecasts and should name the vessel or leg, location, time zone, source and update time.
Are ETD and ETA guaranteed shipping dates?
No. They are estimates unless a separate contract expressly establishes a commitment and remedy. Vessel, port, weather, connection and clearance conditions can change. Keep the original estimate, revised forecast and actual event separately.
Does ETA mean the frozen container is ready for delivery?
Usually not. A vessel ETA may precede berth, discharge, terminal availability, customs release, truck pickup and warehouse appointment. Ask for the exact event and plan a separate warehouse-ready date or range.
What should I track after a vessel misses ETD?
Confirm whether the container gated in, whether it remains powered, whether it was loaded or rolled, the revised ETD, the new destination ETA, the next connection if transshipment is involved, and the next update time. Protect the original schedule record.
Which date should I use for frozen-food inventory planning?
Use a warehouse-ready range derived from the current vessel ETA plus realistic discharge, release, customs, trucking and receiving allowances. Compare that range with current usable inventory and daily consumption, then update it when an upstream milestone changes.
References
- International Maritime Organization. IMO Compendium current dataset: estimated, requested, planned and actual arrival/departure data elements.
- Digital Container Shipping Association. Track & Trace standard documentation.
- Digital Container Shipping Association. Port Call Standard 2.0.0 purpose and scope.
- Maersk. Example standard cut-off table, illustrating service-specific reefer, SI, VGM and other deadlines.
- Codex Alimentarius. Code of Practice for the Processing and Handling of Quick Frozen Foods, CXC 8-1976.

