An AKTARMA MERKEZİ receives, briefly holds and transfers cargo between vehicles; AKTARMA is the physical unload-and-reload process. Procurement should define the handoff, scan, dwell, damage, custody, route and exception controls instead of buying an undefined transfer promise.
- Separate a true cross-dock transfer from storage, consolidation, deconsolidation or value-added handling.
- Define inbound, sort, staging, outbound and proof-of-transfer events with one shipment identity.
- Set dwell, cut-off, damage, shortage, temperature, security and recovery obligations.
- Make the transfer center accountable for exceptions that occur between carrier handoffs.
A Transfer Center Is a Time-Bounded Handoff
The SSDER glossary describes AKTARMA MERKEZİ as an operating center where inbound cargo is unloaded, briefly held and loaded onto the next vehicle, and AKTARMA as unloading from one vehicle and loading onto another without special processing. A cross-dock is therefore a controlled handoff, not simply a cheap warehouse.
The procurement specification should state whether the provider may store, consolidate, relabel, re-pack, inspect, split, merge or divert goods. Each activity changes cost, custody, inventory visibility and potential liability.
Create One Handoff Identity
Use a shipment, handling-unit or SSCC identity from origin through the transfer center. Record inbound vehicle, seal, package count, condition, scan time, staging location, outbound vehicle, destination and receiving appointment. The outbound label must remain connected to the original purchase order or customer order.
Do not let a transfer center create an untraceable local reference. If a relabel is required, preserve the parent-child relationship and make the mapping available to procurement, carrier, claims and customer service.
Set Dwell and Operating Windows
A cross-dock promise should include cut-off, inbound appointment, sorting time, outbound departure, holiday and overflow rules. The provider should report dwell by shipment, not only a daily average. Long dwell may signal a carrier mismatch, incomplete data, late inbound, missing capacity or an unplanned storage operation.
Price the same scenarios in every bid: late inbound, missed outbound, damage, rework, after-hours handling, overflow storage, temperature deviation and an emergency recovery move.
Control Custody, Damage and Exceptions
The handoff record should identify who accepted the cargo, seal condition, visible damage, count variance, inspection and the next responsible party. A provider must notify the buyer before a shortage or damaged package is mixed into an outbound load.
Measure dwell, on-time transfer, scan completeness, mis-sort, damage, shortage, missed cut-off, overflow, rework and claims. Review exceptions with both carriers and the transfer center; a low dwell average can conceal a few high-impact failures.
Worked Example: Cross-Dock Becomes Storage
A retailer buys a two-hour transfer service. Late linehaul arrivals and incomplete labels cause cartons to remain for two days, while the provider bills the agreed cross-dock rate. The buyer has no storage trigger, scan history or ownership rule and cannot explain the customer delay.
The corrected contract defines cross-dock scope, dwell clock, cut-off, label acceptance, overflow rate, exception owner and proof of transfer. The dashboard distinguishes transfer service from storage and charges root-cause owners for repeated failures.
Metrics and Governance
For transfer center cross-dock controls, measure both service and evidence quality. Useful indicators include first-pass acceptance, exception rate, response time, unplanned cost, document completeness, damage or discrepancy rate, and the percentage of shipments that follow the approved process. A dashboard should distinguish a supplier failure from a carrier, terminal, broker or internal master-data failure.
Review the metric trend with procurement, logistics, finance, quality and the responsible specialist. Use a monthly exception sample to test whether the control worked in a real transaction, not just whether a field was filled. Repeated exceptions should change the sourcing strategy, contract, lane design or supplier development plan.
Keep the control proportionate to risk. High-value, regulated, time-critical or safety-sensitive cargo needs stronger evidence and faster escalation than a routine shipment. Record the decision owner, approval date, source documents and follow-up action so the next buyer can understand the operating history.
Supplier and Carrier Questions
- Which AKTARMA MERKEZİ or related glossary condition is assumed in your quotation, procedure or service description?
- Which party owns each data field, physical handoff, inspection, document and exception?
- What evidence will be available before release, loading, movement, receipt, invoice approval or claim?
- What changes require advance notice, requalification, a revised price or a new risk decision?
- How will the supplier report incidents, delays, mismatches and corrective actions, and within what response time?
Implementation Sequence
Implement the control in a small, representative lane first. Capture the baseline process, test the required data and evidence, run a real transaction, and review every exception with the people who performed the work. Do not declare the control effective only because a supplier signed a procedure.
After the first three shipments or operating cycles, update the purchase-order clause, work instruction, scorecard and training. Scale the control to other suppliers only when the evidence is repeatable and the owner can explain what happens when the normal path fails.
Common Mistakes to Avoid
- Calling a storage operation a cross-dock service.
- Breaking the identity link between inbound and outbound handling units.
- Measuring daily average dwell instead of shipment-level exceptions.
- Paying a transfer rate when labels, seals, count or custody evidence is missing.
- Leaving overflow, damage and missed-cut-off ownership undefined.
Procurement Implementation Checklist
- Define transfer, storage, sort, relabel, consolidation and value-added scope.
- Use one shipment or handling-unit identity across every handoff.
- Set appointment, cut-off, dwell, overflow and recovery rules.
- Record seal, count, condition, scan, staging and outbound evidence.
- Measure on-time transfer, dwell, mis-sort, damage, shortage and rework.
- Escalate shipments that exceed the cross-dock clock into an approved path.
Frequently Asked Questions
What is an AKTARMA MERKEZİ?
It is a transfer center where inbound cargo is unloaded, briefly held and loaded onto another vehicle for onward movement.
Is cross-docking the same as warehousing?
No. Cross-docking is a time-bounded transfer with limited holding; storage, rework or value-added processing requires a different scope and control.
What should be scanned?
At minimum, shipment or handling unit, inbound and outbound vehicle, count, seal or condition, location, timestamp and destination.
Who owns damage during transfer?
The contract should define custody at each handoff, evidence, notification, investigation and claims responsibility.
How should dwell be charged?
Define a free cross-dock window and a separate, approved rate or recovery path when the provider is performing storage or rework.
Related Kurums Guides
- ABC Inventory Analysis
- Freight Network Design
- Freight Contracts and Parties
- Freight Rates and Surcharges
- Container Types and Load Securing
- Cargo Insurance and Claims
Standards and Authoritative Sources
- GS1 — Identification keys for logistics units and locations
- GS1 — Logistic label guidance
- FIATA — Freight forwarding resources
- U.S. FHWA — Freight management and operations
Glossary terms covered: AKTARMA MERKEZİ, AKTARMA, cross-dock, handoff, dwell time, scan, proof of transfer
Kurums.com · Procurement, sourcing and business operations
Discover more from Kurums | Business Intelligence
Subscribe to get the latest posts sent to your email.
