Which Logistics Conditions Should Be Agreed Before Equipment Shipment? ART-514

Start with the supply boundary, not the date

The phrase “the equipment will be delivered” is not precise enough. It does not say whether the shipment includes spare parts, documentation, cables, cooling systems, software, long-distance packaging, insurance, or border support. First establish an agreed supply list and a list of cargo places. Only then can the route and date be planned reliably.

The technical specification or a contract appendix should identify the exact model, configuration, options, and serial numbers when they have already been assigned. One system may arrive in several consignments: the main machine, control cabinets, peripheral equipment, spare units, and documents. Calling all of this simply “the machine” makes it difficult to confirm whether every item has left the supplier and whether a critical option is still in the warehouse.

Separate three dates: readiness for shipment, actual handover to the carrier, and arrival at the agreed destination. They describe different events. The first confirms that the cargo is ready. The second is tied to transport documents. The third does not by itself mean that the equipment has been accepted for completeness or technical condition.

What should be recorded in writing

| Area | What to agree | Why it matters | What should not be assumed | |---|---|---|---| | Scope | Modules, options, accessories, documents, and number of cargo places | Compare shipment with receipt | Everything shown in a photograph or catalogue is included in the price | | Identification | Quotation, line-item and package numbers, and serial numbers when available | Link the cargo to the contract | A general model name is sufficient | | Packaging | Protection type, marking, storage limits, and handling instructions | Reduce transport and handling errors | Any package can withstand any route | | Transfer of risk | Agreed place, event, and supporting document | Keep risk, cost, and ownership separate | Incoterms automatically settle every contractual issue | | Route | Loading and delivery points, access restrictions, and contacts | Plan realistic transportation | Oversized transport can enter the site without checking | | Documents | Invoice, packing list, transport and customs documents where required | Identify the cargo and complete procedures | The carrier will independently know which data is missing | | Receipt | How quantity, visible damage, and discrepancies are recorded | Preserve evidence for further decisions | A receipt signature is the same as technical acceptance |

This table is not a ready-made contract. It turns scattered correspondence into a visible list of open questions. Assign an owner to every line: supplier, buyer, carrier, customs representative, or another party. If no owner is named, the work has effectively not been assigned.

Incoterms are a useful framework, not a substitute for agreement

Incoterms rules help the parties agree the delivery point and allocate certain duties, costs, and risks. They work properly only when the contract names the selected rule, its edition, and an exact place. A city name without an address, terminal, or other defined point may still permit conflicting interpretations.

Incoterms do not govern every aspect of a sale. They do not replace the product description, transfer of title, payment terms, delay liability, warranty, or dispute procedure. Three letters therefore do not close every logistics question. Ask the party proposing the term to explain it in plain language: who books transport, who loads, who handles export and import formalities, where risk transfers, and which document records the transfer.

The selected delivery term must also match the actual route. A party’s willingness to arrange transportation does not mean the receiving plant is ready for the vehicle. The route may require transshipment, temporary storage, permits, or additional coordination. Do not promise in contractual documents what has not been checked in real operating conditions.

Packaging protects the technical integrity of the equipment

Request a packaging description to understand how the equipment is protected against impact, moisture, dust, corrosion, and improper handling. Different units face different risks: an electrical cabinet, optical component, mechanical module, and paper documentation do not need identical protection. Specific requirements, however, should not be invented by analogy. Use the manufacturer’s instructions for the particular model and transport conditions.

A packing list should include the cargo-place number, description, weight, and dimensions, but these values must come from the party that packs the shipment. Never estimate weight by eye when selecting a vehicle or planning lifting. Centre-of-gravity data, lifting points, and permitted orientation cannot be replaced by a general “handle with care” label. If the required data is missing, request it before transport is booked.

Photographs of the package before handover can provide a useful record, but they do not replace an inspection note, marking, or cargo-place list. Agree who takes the photographs, where they are stored, how they are linked to the shipment number, and whether existing package damage is clearly captured.

Check the route and receiving point as a production task

Review the route from the supplier’s gate to the agreed delivery point. The buyer should provide factual information about the address, time windows, vehicle access, security procedure, contacts, and site restrictions. Vehicle and pedestrian movements create their own workplace risks, so a truck should not appear merely “by arrangement with security” without an approved plan.

Do not confuse delivery to the site with delivery to the installation position. “To the premises” may mean the gate, warehouse, unloading bay, or another defined point. Each option creates different duties. If the receiving place is not ready, this cannot safely be solved through improvisation on arrival day. Responsible people need to make a separate decision rather than give an informal instruction to the driver.

For an international shipment, verify early which documents and data the selected customs route requires. Commodity description, country of origin, value, item names, and other details should be consistent across commercial and transport documents. Do not replace them with approximate descriptions. Consistent data makes trade documents easier to process and reduces the risk that the same item has different names in different records.

A practical sequence before shipment

1. Compare the specification, contract, and quotation, then create one agreed list of everything included in the supply. 2. Ask the supplier to confirm readiness, cargo places, packaging, and the data required for transport planning. 3. Record the delivery rule, exact point, allocation of work and costs, and the event at which risk transfers; review legal wording separately. 4. Check the route, contacts, site access, and every point where responsibility passes between parties. 5. Agree the document list and assign an owner for each document before the cargo is handed over. 6. Define how visible damage, missing places, and other discrepancies will be recorded at delivery. 7. Hold a short joint review of open questions before granting permission to ship.

This sequence does not set the technical parameters of transportation. It creates a management framework in which critical information does not disappear between procurement, logistics, and the receiving site.

Perform a pre-shipment review without false optimism

A short joint review is useful when procurement, the supplier, logistics, and the site representative can see the same list of facts. The objective is not to approve everything at any cost. It is to confirm readiness in each critical area or record exactly what prevents shipment, who owns the issue, and what evidence will close it. A verbal “everything will be fine” is not evidence.

Maintain an exception register. It may show that a document will follow later, a serial number is not yet assigned, the route awaits confirmation, or an item will be sent separately. Every exception needs a reason, an owner, a contract-compatible target date, and its consequence for the shipment. The article cannot set a universal deadline; the parties must do so. Without a register, however, a controlled exception becomes a forgotten promise.

Do not equate permission to ship with confirmation that the machine is ready for operation. The equipment may be packed and transferred correctly while installation, connections, commissioning, and acceptance tests still have separate conditions. Keeping these events distinct prevents a signed transport document from being interpreted as acceptance of the complete technical system.

A practical review tool is an open-issues register. For each line record the subject, current fact, responsible party, required evidence, and effect on shipment authorisation. The completeness line may refer to the agreed specification and packing list. The route line may identify the confirmed receiving point and access restrictions. The document line may show which files must accompany each cargo place. “Open” does not automatically mean “prohibited,” but it means that the decision cannot be hidden behind the general word “ready.”

Separate three types of confirmation. Completeness asks whether all agreed items are listed and identified. Visible receipt concerns the number of cargo places, packaging, and obvious damage on arrival. Technical acceptance verifies the functions and criteria agreed for the particular system, often after separate connection and commissioning work. A transport signature may confirm only one of these facts; read what the document actually says instead of adding a broader meaning.

The same principle applies to responsibility. No article can prescribe a universal allocation for every transaction, but the parties should still record who supplies data, books the carrier, receives the shipment, reports deviations, and decides the next action. If a task depends on the contract, label it as a contractual issue instead of presenting it as a technical fact. This makes gaps visible before they become delays or disputes.

Common mistakes

The first mistake is agreeing only a date and generic “delivery terms” without explaining them. The second is treating the packing list as a minor attachment and failing to compare it with the specification. The third is ordering transport before checking site access. The fourth is signing a receipt without understanding what that signature confirms. The fifth is assuming that Incoterms automatically define every risk, warranty condition, transfer of title, and customs obligation.

It is also risky to postpone decisions until delivery day. A missing contact, blocked access, undefined storage location, or inconsistent document rarely disappears without delay. The correct response to an unknown fact is a request, a record, and confirmation by the responsible party—not an assumption.

Before handover, compare three datasets: the specification, packing list, and transport document. The specification shows what was agreed. The packing list shows how it is divided into cargo places. The transport document records what was handed to the carrier. Names, quantities, and identifiers should not contradict one another. If a serial number is not yet available, use an explicitly temporary identifier rather than a guess.

Agree in advance what happens when a discrepancy is found. Receiving personnel can record a shortage, damaged packaging, or incorrect marking, but decisions about further use, return, or technical inspection belong to authorised parties under the contract. A driver or warehouse employee should not be forced to determine the technical condition of the machine. Their task is to record what they are authorised to observe and send the information through the agreed channel.

For a large shipment, prepare a contact list based on roles rather than telephone numbers alone. Name separate contacts for documents, logistics, the site, receipt, and damage escalation. For a cross-border delivery, add the party responsible for customs data. The contact list does not create legal responsibility by itself, but it removes practical uncertainty on handover day. Store its date and version with the open-issues register.

Finally, confirm that every participant uses the same document revision. Conflicting names in an email, packing list, and consignment note should be corrected before departure. If an immediate correction is impossible, record the discrepancy and identify who has accepted it. This small check often determines whether the parties can later establish exactly what was transferred.

What cannot be decided without project data

Without the actual model, route, countries, contract, and manufacturer’s documents, no one can select the vehicle type, route restrictions, packaging method, customs requirements, insurance cover, transfer-of-title rules, loading requirements, or acceptance process. It is equally unsafe to infer that a module is compatible or included merely from the name of a system. These questions belong to the specification and to the manufacturer, carrier, customs representative, and legal advisers within their respective responsibilities.

Checklist before shipment

• [ ] The supply scope, options, and number of cargo places match the agreed documents.
• [ ] Quotation, cargo-place, and available equipment identifiers are recorded.
• [ ] Packaging, marking, and necessary cargo data are agreed.
• [ ] The delivery rule, exact place, and handover document are defined.
• [ ] The route, contacts, access, and receiving point have been checked.
• [ ] Transport and trade documents have named owners.
• [ ] There is a procedure for recording shortages and visible damage.
• [ ] Unloading and installation are covered by a separate competent plan.

Need to agree the equipment delivery?