Getting Started with Logistics Robots in Factorio | Minimal Setup and Placement Design

Logistics robots are convenient, but covering your entire factory with a single network from the start often leads to bottlenecks from charging queues and inefficient routing. This guide walks you through getting your first network running reliably in Factorio 2.0 vanilla, covering minimal setup → placement strategy → optimal uses → troubleshooting in a structured sequence.

The reference points are the roboport's 50×50 logistics range, 110×110 construction range, and 4 simultaneous charging slots—basic specs that let you make smart placement decisions without overextending or cramping yourself. When I limited robot automation to just the mall in my belt-focused factory, resupply became rock solid. But when I tried connecting everything into one massive network, charging gridlock made everything sluggish. The key insight is this: logistics robots shine when you keep them localized and use them for small-batch replenishment, not as a universal logistics backbone.

Background Knowledge Before You Start with Robot Logistics

Target Version and Prerequisites

This guide covers Factorio vanilla 2.0 ground logistics. Logistics robots might look like a universal transport solution, but they only work when three components come together: roboports, logistic chests, and logistics robots—all in the same network.

2.0 has GUI and convenience improvements around robots, but the ground-level mechanics stay the same. Note: Space Age platforms don't run normal roboports or logistics robots, so think of orbital logistics as a separate system entirely.

Buffer chests are useful once you understand the network, but their behavior depends on network state and configuration. Leave them alone until you've mastered the core three.

This difference is quite significant. On the ground, robots flexibly transport across obstacles, but in space, that premise does not exist. Therefore, it is more accurate to view the logistics rules as switching to a different layer rather than thinking that "robot logistics have weakened" when observing the Space Age's space environment. It leads to a design centered around belts and hubs, which is difficult to conceive as an extension of the ground-based robot network.

Next, explore train networks and inter-base supply chains for context on how robot logistics fit into the bigger picture.

The easiest starting point is to place a passive provider chest on the output side and a requester chest on the input side, making sure both sit inside the same roboport's logistics range. This makes it crystal clear: "take from here, deliver there." You'll understand robot behavior much faster this way. Conversely, if a chest is just outside the orange range or you forget to load robots into the roboport, everything looks complete but nothing happens. I spent embarrassing time debugging that early on.

Logistics robots shine because they fly over obstacles and routing is flexible. That said, they're not designed to replace large-scale bulk transport. Think of them as specialists in small-batch replenishment, mall operation, research resupply, and player logistics—all very comfortable use cases. But ore lines and major intermediate supply chains run better on belts or trains. Once you understand the division of labor, robot logistics becomes much more manageable.

Logistic network

wiki.factorio.com

Logistics Network Components and Terminology

To understand logistics networks, start by distinguishing logistics area and construction area. Roboports display two ranges: orange for logistics, green for construction. the baseline is 50×50 tiles for logistics, 110×110 tiles for construction. Not knowing this difference leads to the classic confusion—"it's in the green zone, why isn't the robot delivering?" Green is for building and repairs; orange is for transport. I got stuck here repeatedly when I was learning.

The roboport itself is both a network hub and a charging station. Each roboport charges only 4 robots simultaneously, so as robot count grows, charging queues appear. A sprawling network with few roboports means you'll see more time spent charging than actually delivering. Robots also divert to nearby charging points mid-journey, so actual performance depends on both travel distance and where charging bottlenecks form.

The base stats of logistics robots are worth noting. Uncharged, they fly at 3 tiles/second, store 1.5 MJ, consume 3 kW while airborne, and spend 5 kJ per tile traveled. Roughly speaking, that's about 6 kJ per tile net, meaning an uncharged robot can theoretically travel around 250 tiles before needing a recharge. In practice, with return trips, waiting, and pathfinding detours, this drops fast—so the takeaway is: multi-hundred-tile shuttles are expensive. The real strength of logistics robots is connecting short-to-medium distances flexibly, not reaching across the map.

Charging behavior matters too. Robots prioritize charging over delivery when reserves dip below roughly 300 kJ (about 20% of capacity). This means shorter loops are far more stable than trying to stretch one network across vast distances. Think of logistics robots as excelling at flexible short-range links rather than "delivering anything anywhere," and your designs stop breaking.

Chest roles are terminology worth locking down. The two you'll use most are passive provider chests (supply side) and requester chests (demand side). There's also storage chests (overflow and network inventory consolidation), buffer chests (relay and priority routing), and active provider chests (forceful output). Early on, though, just split supply and demand cleanly; that clarity pays off.

Roboport

wiki.factorio.com

Player Logistics Basics

One major appeal of logistics networks is that you—the player—can be a requester too. Set items to auto-resupply, and logistics robots will keep your inventory topped up. Belts, inserters, poles, ammo, and repair kits stop disappearing from your pockets. Compare that to manually raiding the mall every few minutes; the difference in workflow continuity is huge. I especially noticed it when clearing cut-down poles during expansion—no more roundtrips.

Think of yourself as a "mobile requester chest." If the network has stock and you're in its logistics range, robots refill you automatically. You can also dump unwanted items back into the network via your trash slots. It transforms construction into a much smoother experience.

But player logistics still inherits network performance. If you're far away, charging is jammed, or supplies are in a different network, resupply lags. So comfort depends less on request settings and more on whether short-loop resupply of essentials is physically accessible. Slow player logistics? Check supply placement and network geography before tweaking numbers.

2.0 has GUI and convenience improvements around robots, but the ground-level mechanics stay the same. Note: Space Age platforms don't run normal roboports or logistics robots, so think of orbital logistics as a separate system entirely. For current-version feature status, check the Factorio Wiki's 'Upcoming features' page.

Upcoming features

wiki.factorio.com

Your First Robot Network: Minimal Setup

What You Need

For a working proof-of-concept, keep it dead simple: roboport, logistics robots, passive provider chest, requester chest, and items to move. The critical part is not mixing up chest roles. Put items you want to ship out in a passive provider. Put receiving points at a requester. Robots will pick up the logical "where from, where to" immediately.

Both chests must fit inside the same roboport's orange logistics range. Orange, not green. Outside the orange and your setup looks done but nothing ships. I've been there—chests look close, but one edge is just barely out of range.

One thing people forget: requester chests don't work until you configure them. Placing one does nothing. You have to specify what item and how many you want. I once left request counts at zero and watched nothing happen for 10 minutes. The moment I set it to "1 iron plate," robots flew out of the roboport. Start with 1–2 items and tiny quantities; it's much easier to see what's happening.

Setup Steps

1. Place and power a roboport. Without power, nothing moves—check this first.

1. Place a passive provider chest on the output side. Stock it with items you want to move. If it's next to a mall, load it with belts and inserters.

1. Place a requester chest on the input side. This is your destination.

1. Make sure both chests sit in the orange logistics range of the same roboport. Closer is better for your first try.

1. Set the requester chest to request the item and quantity. Even 1 counts. That "want" triggers delivery.

1. Load logistics robots into the roboport's internal slots. This activates the network. Robots don't work from your inventory—they have to be in the roboport.

That's it. Once all five conditions are met, robots will ferry items from passive to requester.

Minimal Troubleshooting Checklist

When nothing moves, check in order:

1. Is power on?

Unpowered roboports go silent. Start here.

1. Are both chests in the orange range?

One slipped outside? Classic mistake, happens constantly.

1. **Does the requester chest have item name and quantity set?**

Zero quantity = no demand. I burned the most time here.

1. **Are logistics robots inside the roboport's slots?**

Crafted robots sitting in your inventory don't count. They must be loaded into the roboport.

1. Does the passive provider side have stock?

Empty source = nothing to ship. Check it's really there.

These five knock out 99% of early "why isn't it working" moments. Once the first shipment lands, the anxiety evaporates fast.

Roboport Placement, Range, and Network Layout

Understanding Logistics vs. Construction Range

Logistics range = 50×50 (orange). Construction range = 110×110 (green). Only orange-range items get picked up by logistics robots. Green is for construction drones and repair—a totally separate system.

This distinction trips up almost everyone. The green zone looks huge, so you assume "close enough." Wrong. Even 1 tile outside orange, even if it feels like it should work, and your chest will sit silent. I've wasted time checking chest settings when the real problem was a misaligned range. Always verify orange, not green.

When you daisy-chain roboports to expand, be careful. Bare-minimum overlaps save space but force robots to take longer paths. More travel time = more charging detours = worse overall throughput. I once threaded roboports across my factory like a string, thinking I'd connected everything efficiently. The result? Robots flew slow routes, charging queues formed at bottlenecks, and items took forever to arrive. A tighter, less sprawling network would've been way faster.

Charging Ports and Congestion

One roboport = 4 simultaneous charges, period. Exceed that and robots queue in the air. Places like malls and research labs see constant traffic, so 4-charge limits become real bottlenecks.

The fix: add roboports to hot zones. Don't spread them evenly; cluster them where pickup/dropoff is heavy. Malls especially suffer—you're both pulling finished goods and restocking ingredient, so traffic is brutal with just one port. Add a second one diagonally opposite, and charging congestion drops noticeably. I tested this: one mall roboport had a visible line of waiting robots. Two ports cut that to almost nothing.

This is also why monolithic mega-networks fail. Robots fly long distances just to reach the nearest charger, then queue there, and the whole system drags. More roboport density in traffic zones beats more total robots.

Power Supply Considerations

Roboports need stable power—charging peaks can spike demand. Thin power lines lead to instability that's hard to debug. Is it a chest config issue? Power starved? Unclear.

Feed mixed-load zones generously and cluster roboports where needed. Breakdowns usually trace back to range mistakes, over-expansion, charging jams, or power shortage—rarely to complex logic. Sort those out at placement time.

The Five Chest Types and How to Use Them

Three Core Types: Passive Provider, Storage, and Requester

Five chest colors exist, but master these three first: passive provider, storage, requester. Think "outbox, warehouse, inbox." Once you're stable, branch out.

Passive provider chests say "take items if you need them." Assembly output goes here—finished products sit until a requester or player demand triggers pickup. Stock is visible; robots pull as needed. No forced output.

Storage chests are the "dump everything here" box. Excess, recycled items, unfinished goods—they all land in storage. Robots try not to mix contents, so storage is great for overflow and sorting (filter by item type). Without a storage overflow, your network jams up on "nowhere for extras."

Requester chests pull exact amounts. "I need 10 iron plates here" or "200 science packs to the lab"—you set the count, robots refill. Demand-side intent is crystal clear, so this is the most beginner-friendly.

The flow: Production outputs to passive provider → surplus gets stored → demand requesters pull what they need. That's 80% of stable networks right there.

Active Provider: Proceed with Caution

Active provider chests are tempting but dangerous early on. Unlike passive providers, active providers force items out into the network. Even if you don't have a destination yet, robots move the contents to storage. Do this on a high-throughput output, and your storage fills with junk. I once made a production line output to an active provider and watched storage become a chaotic warehouse. Switching to passive fixed it instantly.

Active providers have a place—forceful evacuation when something must leave a location—but as a default output? No. Stick to passive provider for normal production.

Buffer Chests: Advanced, Skip Early

Buffer chests are useful once you understand the network, but their behavior depends on network state and configuration. Leave them alone until you've mastered the core three. The Factorio Wiki buffer chest page has the details if you get curious, but don't force them into early designs.

Where to Deploy Logistics Robots (and Where to Avoid)

Perfect Use Cases

Logistics robots sing when you have small quantities, many types, short-to-medium distance, and flexible routing. Concrete examples:

Malls are the poster child. Belts, inserters, power poles, assemblers, pipes—dozens of types in low volume. Belt-routing all of them is a mess. Robots make it simple: stack provider chests, space requester chests around the mall floor, done. The throughput is nothing like a megabase supply line, but for building-time restocking, it's effortless.

Research labs need steady multi-type packs. Logistics robots handle small-batch science-pack distribution way better than trying to belt five types neatly. Rearranging research blocks? Just adjust requester amounts. No rewiring.

Player logistics is huge. Auto-resupply of belts, poles, ammo, and repair packs while you're building or exploring cuts downtime dramatically. You stop making "run home to restock" detours.

Small-item replenishment for stuff like gears, circuits, batteries, engines. Individual sites need a few per second, not a belt stream. Robots drop off exactly what's needed; nothing clogs.

Avoid These: Large-Scale Primary Transport

Do not use logistics robots for ore, plate bulk-transport, or core supply lines across your factory. Uncharged robots fly at 3 tiles/second; they consume 5 kJ per tile traveled. Long-distance shuttles are slow and power-hungry. Plus, charging queues explode with distance.

I tested this once—tried moving ore from a distant mine via one massive robot network. Power costs and charging gridlock were nightmares. Switching to trains fixed it instantly. Robots are specialists; treat them as such.

Division of Labor: Belt, Train, Robot

Each transport type owns a lane:

Malls, research, items → robots. Smelted plates, intermediate supply → belts. Ore, long-range goods → trains. That split works beautifully.

Debugging Common Problems

Three Main Failure Modes: Range, Requests, Supply

When nothing works, isolate fast:

1. Chest outside orange range Even if green is visible, logistics happens only in orange. Double-check with a roboport placed fresh.

2. Requester not configured Item name and quantity both matter. One empty field kills the whole delivery.

3. Passive provider is empty Requests can't be filled if there's nothing to pull. Make sure stock is actually there.

These three account for nearly all early-game hangs. Also check power and ensure robots are in the roboport slots, not just in your inventory.

Charging Queue Backed Up? Add Roboports

If robots hover around a roboport waiting for charger access, the solution is more roboports in that zone, not more robots. Four simultaneous charges is the wall. Spread the load. Malls are the classic culprit—add a second roboport opposite the first, and congestion melts.

Network Too Big?

Mega-networks suffer from long robot paths, charging delays, hard-to-diagnose bottlenecks, and unclear cause-and-effect. Split by function: mall network, research network, defense/expansion network, personal logistics network. Each smaller network moves faster, runs more stable, and is easier to troubleshoot.

Advanced: Inventory Signals and Network Segmentation

Using Inventory and Robot Count Signals

Logistics network inventory and robot counts can be read as signals. Use them to toggle production: "If network iron drops below 50, turn on smelting. Stop at 200." This prevents stockpiling and wasteful production cycles.

Robot count signals also help. Keep surplus construction robots available by monitoring count and reactivating robots when stock dips.

The trick: use hysteresis, not exact thresholds. Turn on at 50, turn off at 200—don't flip on 50 and off at 51. In-flight items and pending requests cause counts to jitter. A band prevents constant on-off toggling.

Smart Network Segmentation

Don't make one giant network. Separate by purpose:

• Mall network: Short loops, high variety, fast refresh.
• Research network: Packs in, no contention from expansion.
• Defense/expansion network: Walls, turrets, ammo—isolated from home logistics.

Each has its own in-network inventory signal, easier to read and control.

What Changed in 2.0 / Space Age, and What Didn't

Ground Logistics Fundamentals Remain

2.0 added convenience features and UI polish, but the core design rules for ground robot networks stand: short is fast, local beats sprawling, charging density matters, and role-splitting (robot vs. belt vs. train) is essential. Roboport specs and network behavior are stable.

What Might Have Shifted

2.0/Space Age may have tweaked GUIs, added roboport variants, or smoothed out rough edges. **These improvements make operation easier, not different**. Your design principles don't invert just because the menu looks better.

For specifics, refer to the Factorio Wiki's 'Upcoming features' page.

Space Age: Separate System

Orbital platforms don't run standard roboports or logistics robots. Logistics works totally differently up there. Don't try to extend your ground network logic to space—it's a fresh design.

Wrap-Up and Next Steps

Logistics robots work best as local specialists, not factory-wide backbones. Set up passive provider → requester chains, cluster roboports where traffic is heavy, and let belts/trains handle bulk. Most of my stable factories segregate robot duties to malls, labs, and resupply, then move everything else by belt or rail.

Next, explore train networks and inter-base supply chains for context on how robot logistics fit into the bigger picture. The Factorio Wiki has excellent train and main-bus articles when you're ready to scale further.