Server racks and networking equipment being installed at a data center under construction

FTWZ

Data Center and Telecom Infrastructure Equipment as Project Cargo

20 Aug 2026 · 17 min read

A new data centre can look like just another large building taking shape on a construction site. But inside, an entirely different operation is being assembled — servers, cooling systems, power equipment, network equipment, racks, batteries and monitoring systems all have their place, and none of it works properly if the required equipment isn't available when the installation team needs it. The same applies to telecom infrastructure, where a project may involve towers, antennas, radio equipment and cables spread across dozens or hundreds of locations. From a logistics perspective, these aren't simply individual shipments — they're pieces of a much larger project. A normal commercial shipment is planned around getting goods from point A to point B. Project cargo is different — the question isn't only how to move it, but when the project needs it, where it should be stored until then, and what happens if the site isn't ready.

A Data Centre Is More Than Servers

A working data centre requires server racks, servers, storage systems, network switches, UPS systems, batteries, transformers, switchgear, cooling systems, chillers and monitoring equipment — each arriving at a different stage. A server may not be needed until the rack and power infrastructure are ready; cooling equipment may need to be installed before servers are brought into operation. So the logistics plan needs to follow the construction and commissioning schedule, not simply the supplier's production schedule.

This Is Where Project Logistics Gets Interesting

Imagine a data centre project scheduled to begin server installation in September. The servers are manufactured in July, and the supplier wants to ship them immediately — but what if the building isn't ready until August? The importer now has a decision: send the servers directly to the site and store them there, find temporary storage, use a suitable warehouse, or consider an FTWZ structure for eligible imported equipment. The answer depends on the project, but the logistics decision needs to be made before the equipment arrives.

Project Cargo Doesn't Always Mean Oversized Cargo

Project cargo often makes people think of huge machinery or heavy transformers. But a pallet of network switches can be physically easy to transport and still be critical project cargo if required for a specific commissioning milestone. The complexity comes from the relationship between the equipment and the project schedule — a small missing component can sometimes cause more trouble than a large piece of equipment that arrived two weeks early. Consider a project where racks are installed, power systems are ready and servers have arrived, then someone asks: where is the network module? It turns out one shipment is still in transit. The item may fit into a small carton, but without it, the next stage of testing can't proceed. Project teams need visibility across the entire equipment list, not just the major shipments.

Cooling Equipment Can Be a Different Kind of Challenge

A server can arrive in a standard package. A large chiller or cooling unit is a different story — the logistics team may need to consider weight, height, width, vehicle selection, road restrictions, bridge limitations, turning radius, site access and crane availability. A piece of equipment can successfully reach the Indian port and still face a problem on the last 100 kilometres — the road may be too narrow, the site entrance may not be ready, or a suitable crane may not be available. These aren't problems that should be discovered after the vessel arrives. For larger equipment, the journey should be planned backwards from the project site: how will this equipment enter the site, what vehicle is required, and where will it be unloaded?

Telecom Projects Create a Different Problem

Data centres may involve one major site. Telecom projects can involve many — a telecom operator might be rolling out antennas, radio equipment, cabinets, batteries and cables across several cities at once, coordinated under frameworks maintained by the Department of Telecommunications. Sending every shipment directly from the port to each site can quickly become difficult to manage — this is where a central inventory location becomes useful. Imagine 1,000 network devices arrive in India. The company doesn't need all 1,000 tomorrow — it may need 200 next month, 300 the following month, and the remainder later. Instead of sending everything directly to project locations, the business can hold equipment at a suitable warehouse and release it as projects become ready, giving the logistics team more breathing room.

A Warehouse Is Not Just a Storage Building

For high-value technology equipment, floor space isn't enough. The business needs strong controls around receiving, inventory records, serial numbers, project allocation, security and dispatch. A warehouse holding 500 network devices should be able to answer more than "we have 500 units" — which models, which serial numbers, which project they're allocated to, and whether they're ready for dispatch. Serial-number tracking becomes especially important when the same model is used across several projects — without it, equipment can easily become mixed together. Every additional movement also creates another opportunity for damage, so every movement should have a purpose.

Customs Clearance Should Be Planned Before Arrival

For imported project equipment, customs clearance is one of the steps that should be considered early — a project team should ideally know in advance what equipment is being imported, how it's described, what classification applies, and where it will go after clearance. A shipment may contain servers, batteries, cooling equipment, cables and power equipment — these aren't interchangeable products, and their classifications and documentation can differ. A project should have an equipment-level view rather than treating the entire shipment as "data centre equipment." The basic principle: don't make customs clearance the first time anyone looks closely at the shipment.

See how Astromar handles customs clearance →

Ocean Freight or Air Freight?

The choice usually comes down to cost, urgency, equipment characteristics and project schedule, relevant for electronics and technology equipment covered in part by MeitY policy. Large planned shipments are often better suited to ocean freight — but if a project is waiting for one critical component and the delay could push back commissioning, air freight may become an option. It's faster, but generally more expensive. Using air freight for every shipment isn't a sensible strategy. When a project falls behind schedule, there's a natural temptation to "send everything by air" — but if the rest of the equipment can continue through normal ocean freight, expediting everything just increases costs without solving the actual bottleneck. Project logistics works best when urgency is assigned only to the shipments that genuinely need it.

The Project Schedule Should Drive the Logistics Schedule

This is the most important idea in the entire process. Start with the installation schedule — building ready, power systems installed, cooling commissioned, racks installed, networking equipment installed, servers deployed, testing, commissioning — and work the logistics plan backwards from these milestones. If equipment is required in October, the team needs to know when it must leave the supplier. If it needs to arrive early, where will it be stored, and what's the storage cost? These questions are much easier to answer when the project schedule is known.

Where Inventory Positioning and FTWZ Fit

A project may not need all its imported equipment immediately, creating an inventory-positioning question: should equipment be cleared and moved directly to site, stored in a conventional warehouse, or managed through an FTWZ arrangement as part of a wider supply chain strategy where eligible? For eligible imported goods and transactions, an FTWZ can be considered when equipment arrives before the project is ready. Instead of treating arrival at the Indian port as an automatic trigger for immediate domestic movement, a company may evaluate whether eligible equipment can be managed within an FTWZ structure before being released according to the permitted process. For a long-duration data centre or telecom project, that flexibility can be worth considering — but the commercial case still needs to be worked out. An FTWZ isn't automatically the right answer simply because a shipment is imported.

See how Astromar handles project cargo →

Projects Rarely Run Exactly According to Plan

A building handover can move. An electrical installation can be delayed. A commissioning date can change. Equipment supposed to be installed in August may now be required in October — if everything was shipped directly to the site, the project may suddenly have expensive equipment sitting there for two additional months. A warehouse can provide separation between equipment arrival and equipment installation, which can make the supply chain more flexible. Imagine a company managing three projects — Project A needs equipment next month, Project B won't need its equipment for another three months, Project C has been delayed. A suitable warehousing model can allow the company to manage inventory until the project schedule becomes clearer, subject to the applicable framework.

Telecom Projects Need Even More Coordination

A nationwide telecom rollout can be a logistics puzzle — imagine 10,000 pieces of equipment arriving in India, eventually distributed across Chennai, Bengaluru, Hyderabad, Mumbai, Delhi and other regional locations. The logistics team needs to know what belongs to which project and when it should move. This is where inventory visibility becomes essential. A central warehouse can help, but only if the inventory system behind it is reliable — equipment received, inventory recorded, project allocated, installation date confirmed, equipment dispatched. That's a much more controlled process than sending everything to site as soon as it arrives.

Security, Packaging, and the Last Mile

A warehouse full of server equipment may not look particularly dramatic, but the value inside can be substantial — controlled access, CCTV, inventory movement records and serial-number tracking all matter, so the company knows who received the equipment, where it is, and when it left the facility. Project equipment can also spend more time in storage than expected, so packaging needs to remain suitable for the storage period, not just transportation. And the final movement deserves as much attention as the international shipment — for a data centre project, that could mean moving equipment through a busy urban area to a site still under construction; for telecom projects, it could mean reaching remote or dispersed locations.

A Practical Example

Consider a company developing a new data centre requiring servers, racks, UPS systems, cooling equipment, network equipment and power distribution systems — some manufactured overseas, some sourced domestically, arriving at different times. Instead of automatically sending everything to the project site, the company maps the installation schedule. Equipment required immediately goes directly to the project where practical; equipment arriving earlier is evaluated for suitable warehousing, potentially including an FTWZ for eligible imported goods. The result is a more controlled flow: Supplier → Port → Customs Clearance → Warehouse/FTWZ → Project Site, rather than Supplier → Port → Project Site → Find somewhere to store it.

The Biggest Mistake: Treating Every Shipment Separately

A large project can have hundreds of shipments. If every shipment is managed independently, the logistics team can lose sight of the bigger picture. The better approach is one project-level view: which equipment has shipped, which is on the water, which has reached India, which is undergoing customs clearance, which is in the warehouse, and which project needs it. Once the entire flow is visible, delays become easier to identify — and the logistics solution has to connect international sourcing, ocean or air freight, port, customs clearance, warehousing, inventory control, road transportation and the project site as one connected chain, not several isolated stages.

Final Thoughts

A data centre doesn't become operational simply because the building is complete. A telecom network doesn't become operational simply because towers have been installed. The equipment has to arrive, be stored properly, reach the right site and become available at the right stage of the project. Sometimes the challenge is making sure a small but critical component doesn't arrive two weeks late. Sometimes it's finding somewhere secure to keep high-value servers while construction is underway. Sometimes it's arranging a specialised vehicle for a large cooling system. For businesses facing these challenges, an FTWZ can be evaluated as one option for managing eligible imported project inventory within the applicable customs and trade framework. Astromar Logistics Pvt. Ltd. operates a network of 10 FTWZ locations, with 2 Lakh+ sq ft of warehousing, 10K+ sq ft of cold storage, 5K+ pallet positions and 500+ clients, and has been operating since 2017. For data centre, telecom and other project-driven businesses, this network can support broader supply chain planning covering imported inventory, warehousing, customs clearance and multimodal distribution. The important thing is not to choose a logistics model simply because it sounds efficient — it should fit the actual project. For companies handling imported data centre, telecom and other project equipment, the right combination of customs clearance, warehousing, transportation and inventory planning can make the difference between equipment that simply arrives and equipment that arrives when the project is actually ready for it.