【Factorio】Getting Started with Robot Logistics｜Minimal Setup and Layout Design

Logistic robots are convenient, but wrapping your entire factory in a single network from the start causes more charging queues and detours than you'd expect. This guide walks through Factorio 2.0 vanilla to get your first network running reliably: minimum configuration → placement design → ideal use cases → failure prevention.

Your benchmark should be the roboport's 50×50 logistics range, 110×110 construction range, and 4 simultaneous charging slots. With these specs in mind, you can make smart placement decisions—neither overshooting nor squeezing too tight. When I turned just my mall into local robot logistics while keeping belts for the rest, restocking became instantly stable. But when I tried linking the whole factory into one network, charging queues killed throughput. Robot logistics isn't a universal solution; its real strength lies in narrow, localised restocking—kept small and segmented.

Prerequisites: Understanding Robot Logistics Before You Start

Target Version and Basic Requirements

This guide covers Factorio vanilla 2.0 ground-level logistics. "Robot logistics" might look like a catch-all transport solution, but it only works when three components connect on the same network: roboport (logistics network hub), logistics chests, and logistic robots. This minimum configuration serves as the foundation.

2.0 has GUI and peripheral changes around logistics, but ground-level principles stay the same. Note: Space Age platforms don't support standard robot logistics, so treat space as a separate logistics system from ground. For 2.0 change tracking, the best source is the upcoming features section.

Then place a requester chest on the input side. This is the destination. Make sure both chests stay in the same roboport's orange range. Shorter distances = easier to verify, so keep them close to the roboport initially.

Roboports exhibit behaviour (described as internal buffering) that temporarily buffers power, smoothing brief dips. But specifics—capacity, how much downtime it tolerates—shift with patches. When concrete behaviour is discussed, it is important to reference the Roboport page.

To track precisely, this text focuses on vanilla 2.0 ground-level operations that are difficult to overlook. When looking for detailed differences, the organization found in the upcoming features section is clear and useful. This page helps grasp "what's being discussed" and serves as a good entry point for reading the actual patch contents.

Next, train networks (inter-base, main lines) let you dial in roles across your whole factory.

For immediate reference, the train, belt, and main-bus entries are practical resources.

The clearest first setup is: passive provider chest on the output side, requester chest on the input side, both within the same roboport's orange logistics range. This makes "where it comes from" and "where it goes" obvious, so you grasp the robot's behaviour quickly. If the chest is outside the roboport range or you forget to load robots, nothing moves—it looks done but stays silent. To be honest, I didn't understand this at first and spent ages confused.

Robot logistics' strength is flexibility across walls and power lines. But understand upfront: it doesn't replace long-distance bulk transport. For low-volume high-variety restocking, malls, labs, and player supply, it's very comfortable. But ore lines and major intermediate production are more stable on belts or trains. Once you split these roles, robot logistics becomes much easier to work with.

Logistic network/ja

wiki.factorio.com

Logistics Network Components and Terminology

Understanding the network means separating logistics area and construction area. Roboports show two ranges: orange is logistics, green is construction. Per the Wiki, it's 50×50 for logistics, 110×110 for construction. Not knowing this difference causes confusion—robots won't move items even though green covers the area. Green is for building and repair, not transport.

The roboport itself is a network hub and charger. Only 4 robots can charge simultaneously per roboport, so more robots cause charging queues. Wide networks with few roboports see robots queuing for power more than actually hauling. Robots also divert to nearby charging points mid-journey, so "travel distance" isn't the only factor—"where does charging bottleneck?" matters too.

Robot basics help with planning. Unresearched logistics robots fly at 3 tiles/second, hold 1.5 MJ, consume 3 kW in flight plus 5 kJ per tile. Rough math: about 6 kJ per tile, so roughly 250 tiles on a single charge. Of course, real journeys involve return trips, idle time, and inefficient paths, so the rule of thumb is "flying hundreds of tiles back and forth is heavy." Robots prioritise charging when reserves drop to about 300 kJ (20% of 1.5 MJ), so the practical sweet spot is keeping round trips short and frequent rather than sprawling networks.

Chest types also matter. Early on, you'll use passive provider chest (supply side) and requester chest (demand side). There's also storage chest (catches overflow), buffer chest (medium, flexible), and active provider chest (aggressively pushes items out). But starting out, stick to supply and requester only—you'll grasp behaviour faster.

Roboport - Factorio Wiki

wiki.factorio.com

Personal Logistics (Player Requests) Basics

Robot logistics shine because you, the player, can be a requester too. Personal logistics auto-supplies preset items—belts, inserters, poles, ammo, repair packs—cutting down on "oops, forgot to bring that" moments. When you're walking the base building and adjusting, this difference is huge.

Think of yourself as "a mobile requester chest." If the network has stock and you're in range, robots deliver missing items. You can also throw away unwanted stuff, sending it back to the network. Compared to manually restocking at a mall every trip, work flow stops far less. For me, the big win was losing the pole-fetch runs during base expansion.

But personal logistics can't escape network performance. If you're far away, charging is congested, or supplies are on a different net, restocking lags. So personal logistics comfort depends less on your settings than on whether robots can short-hop with needed items nearby. If personal logistics feels sluggish, check supply placement and network spread before tweaking request numbers.

2.0 has GUI and peripheral changes around logistics, but ground-level principles stay the same. Note: Space Age platforms don't support standard robot logistics, so treat space as a separate logistics system from ground. For 2.0 change tracking, Factorio Wiki's 『Upcoming features』 is the best source.

Upcoming features/ja

wiki.factorio.com

Your First Robot Network: This Minimal Setup Is All You Need

What You Actually Need

For a first win, cut ruthlessly: roboport, logistic robots, passive provider chest, requester chest, and items to haul. The key is not mixing chest roles. Passive provider on the output side, requester on the input. This way robots understand "take from here, put there" without confusion.

For placement: keep both chests inside the same roboport's orange range. Not the green—the orange. Misaligning this makes items look close but stops delivery cold. I've put a chest outside the orange range "because it looked near enough," only to waste 10 minutes debugging. It matters more than you'd think.

Also easy to forget: requester chests do nothing without settings. Placing one doesn't trigger anything. You have to specify "I want this item, this quantity." When I set the request to 0, nothing happened for 10 minutes. Entering "1" in quantity and watching a robot instantly launch was my "oh, there's the problem" moment. First tests should be one item type, small numbers—easier to see what's happening.

Installation Steps

It's straightforward. Place a roboport first and power it. No power = no movement. This sounds obvious, but you'd be surprised how many people tweak chest settings for ages without checking electricity.

Next, place a passive provider chest on the output side. Stock it with items to haul—say, belts and inserters if you're restocking a mall. Whether you feed it from a production machine or hand-fill doesn't matter; it's the network's source.

Then place a requester chest on the input side. This is the destination. Make sure both chests stay in the same roboport's orange range. Factorio Wiki cites this as the baseline setup. Shorter distances = easier to verify, so keep them close to the roboport initially.

Set the requester chest: pick items and quantities. Start small—1 or 10 units. Once you specify a quantity, that chest registers as "in demand," triggering delivery.

Finally, load logistic robots into the roboport's inventory slots. Once they're aboard, the network activates and robots begin work if conditions align. Many think "hold robot = auto-fly," but robots only activate once they're in a roboport slot.

Troubleshooting: The Core Checklist

When it won't run, diagnose in fixed order, not random guessing. With minimal setup, problems narrow fast.

1. Is power flowing?

No power = roboport idles, robots sit still.

1. Are both chests in the orange range?

One chest just outside happens constantly. Orange, not green.

1. Does the requester chest have items AND a quantity set?

Zero quantity = no job. This trapped me the longest.

1. Are logistic robots actually in the roboport?

Crafted robots in your inventory don't count. They need to be in the roboport slot.

1. Does the passive provider actually hold stock?

No supply = nothing to haul, obviously.

Run through these five in order—most first-time "why won't it work" blocks dissolve. Early snags cluster around power, range, request numbers, robot slots, and supply. Get one trip working and confidence jumps massively.

Roboport Placement: Range Reading and Network Design

Understanding Range Overlap and Network Links

First thing with roboport placement: 50×50 logistics (orange), 110×110 construction (green). Per the Wiki, only orange-range items flow. Vague boundaries break networks silently—it looks reachable but sits inert.

Beginners often trip on range-outside chests don't work. If either supply or demand is outside logistics range, no delivery happens. The green construction area is wide, so it seems like it covers everything. But construction and logistics are separate checks. You can build with green but haul nothing—very common.

Sprawling networks connected edge-to-edge make robots travel far. Distance bloats cycle time, charging detours multiply, and overhead stacks. A unified giant network works on paper but lags in practice.

I once stretched one network across my whole factory. Eventually, robots commuted long distances between the mall and lab, deliveries slowed weirdly. Digging in, the network's skinny connectors forced detours and charging stops piled up. Short, fat local networks beat one long thin one. Robot logistics works best when "commonly used places" stay close and fast.

Charging Ports and Congestion

Roboports have a hard limit: 4 robots can charge simultaneously. Exceed this and robots float idle, queuing. Matters little with few robots, but places like malls or labs spawn high throughput—suddenly that 4-slot cap is your bottleneck.

Congested spots solve by densifying roboports. Don't spread evenly; concentrate them where traffic peaks. Malls especially spike from both pulling finished goods and restocking inputs, so one port suffocates fast. Add a second opposite corner—charging spreads, travel shortens, queues dissolve.

I watched this first-hand: my mall's roboport had robots stacked around it, visibly waiting. Placed a second one diagonally—bot traffic scattered, round-trip times dropped, the queue vanished. Fixing congestion zones beats adding more robots. Charging capacity, not robot count, often kills throughput.

Thin sprawling networks also choke on charging—robots arriving tired, stuck waiting, feeding delivery delays that cascade. When robots feel slow but numerous, suspect charge-port shortage before assuming understaffing.

Power Supply and Internal Buffering

Roboports need more than just a wire. High-traffic periods spike consumption—charging surges spike demand. Thin power lines make robot motion seem unstable, muddying whether the problem is chest settings or power.

Roboports exhibit behaviour (described as internal buffering) that temporarily buffers power, smoothing brief dips. But specifics—capacity, how much downtime it tolerates—shift with patches. When citing concrete behaviour, reference official sources like Factorio Wiki's Roboport page (e.g., "per official documentation...").

In practice, feed fat power lines and cluster roboports in hot zones. Most failures cluster around range misread, overspreading, charging jams, or weak power—not complex logic. Nail these in layout and robots cooperate nicely.

The Five Chest Types: Roles and Beginner-Friendly Splits

The Big Three: Passive Provider / Storage / Requester

Five chest colours exist, but three handle almost everything: passive provider, storage, requester. Honestly, I laid out all five at first and got lost. Sticking to three clarified fast. In one sentence: outbox, stockroom, inbox.

Passive provider is your "take if needed" box. When a production line finishes belts or inserters for a mall, drop them here. Robots don't auto-expel; they pick up on-demand. Stock your output, robots fetch when requesters go hungry. Clean and readable.

Storage chest is your overflow and scrap bin. Leftovers, salvage, lost items funnel here. Robots avoid mixing types, so storage's great for "anything" piles. Add filters and you get "stone-only box" or "wood dump" effortlessly. Without a catch-all, factories jam from unclaimed items.

Requester chest is input-side, quantity-specified pickup. "5 circuits here," "20 plates there." Robots stock it from the network. Perfect for research labs, ammo lines, mall supplies. Explicit need, explicit action, beginner-friendly.

Link these three: production → passive provider, overflow → storage, demand → requester. That flow covers 90% of early logistics. Done. The colour confusion dissolves.

Pitfall: Active Provider's Aggressive Behavior

Active provider looks like "upgraded passive provider" but newbies get punched. It won't tolerate items sitting still—robots shove everything out immediately, hunting destinations, dumping surplus into storage.

This causes avalanches. Line output goes active provider, robots drain it relentlessly into storage. Surplus you weren't ready to ship floods the warehouse. Suddenly your storage is chaos and you can't find anything. Factory vibes collapse.

I binned this mistake: my mall's output was active provider, and robots shoved everything into storage, turning it into a junkyard in minutes. Switched to passive provider and traffic normalized—only needed stuff moved. Huge difference.

Active provider has uses: "this output must leave the area" situations. But for normal production? Stick passive provider as default, active provider for special cases.

Advanced: Buffer Chest's Correct Niche

Buffer chests are convenient but behaviour depends on settings and other chests—their mechanics interact in ways that shift with patches. For reliable detail, check the official Buffer chest Wiki entry or test in-game. As a rule, buffer chests serve as middle-ground storage or load-balancing, but the specifics are best learned through practice or reference docs.

When bewildered by chests, don't memorise all five. Use three, restrict active provider, graduate to buffer later. This progression keeps logistics readable.

Where Robot Logistics Actually Shines

Best Use Cases: Malls / Labs / Personal Logistics / Small Restocking

Robot logistics gel best for low-volume high-variety delivery to specific spots. Concrete examples: hobby shops (malls), science labs, player supply, small-material restocking. These don't need massive belts; they'd clog if you tried. Robots excel—just set chest filters and let them work. Layout changes, no problem.

Malls are a showcase. Many item types, low per-type throughput. Belt routing becomes cramped and tedious. Robots just need passive providers and requesters facing each other—clean, flexible. My mall restocking became so much easier after local-net robot wiring.

Labs are textbook. Producing many science colours on one research block used to be a belt puzzle. Robots carrying small batches fit perfectly—labs grab what they need, no overstocking. Scalable, clean.

Personal logistics is massive in practice. Auto-supply belts, poles, modules, walls, ammo during construction—you never stop for refills. Not game-changing for throughput but game-changing for workflow. Big expansion? Personal logistics value skyrockets.

Small-material top-ups belong here too. Electronics, gears, batteries, engines—niche parts needed everywhere in small doses. Mainline belts snarl if crammed with all this miscellany. Distribute via robots instead, factory clarity improves.

Bad Use Cases: Bulk Long-Distance Primary Transport

Large, distant, continuous flows to bulk production don't suit robots. Ores, plates, core circuits being the main feed. Looks elegant, but runs rough underneath.

Unresearched robots fly at 3 tiles/sec, holding 1.5 MJ. Each run ties up transport time and charging stops. Roboports cap at 4 charging slots, so scaling robots hits ceiling fast. You end up with bots always queuing, flying, or charging—but not hauling. It looks busy; it's actually inefficient.

I tested this: pushing a huge ore line through robots kilometres apart became a nightmare. Charging gridlock throttled everything. Switched to trains and boom—supply freed up instantly. Robots are specialists in short-range finesse, not generalists for bulk.

Big-flow viability is sustained throughput, not flexible single trips. Here, belts excel (continuous, low overhead), trains excel (long-distance, consolidated). Robots can't compete.

Role Divvying: Belts, Trains, and Robots

Robots, belts, and trains play different positions—complement, don't compete. My sweet spot: belts + trains form the backbone, robots fill local gaps.

Rough roles:

This table says it: malls→robots, smelters→belts, ore-to-smelter→trains. Blur them and you lose clarity and stability.

Robot value isn't replacing everything. It's skipping annoying multi-item wiring and hitting the right spot exactly. Narrow that, they become invaluable.

Frequent Failures and Fixes

The Big Three Failure Modes: Range / Requests / Supply

Most robot logistics "won't work" boils to three: range, requests, supply. Learn to slice these and fixes come quick.

Range miss tops the list. Chests in blue construction but outside orange logistics. Confuse these and you'll see robots flying but items not flowing. Chest sits outside orange, nothing moves. I've missed this so many times, staring at chest settings for ages before realising: "oh, it's outside the range."

Missing request settings is second. Requester chest placed, nothing happens. Need to specify items and quantities. Blank quantities = no job. Double-check filter setups on storage; misalignment stops everything.

Empty supply sneaks in third. Request's fine, but the passive provider's depleted. Or the production machine's outlet isn't connected to a provider chest at all. Supply side goes unnoticed because eyes lock on demand.

Bonus: nowhere to put surplus. Active provider dumps everything somewhere; if storage's full or filtered wrong, junk floods and clogs the net. Active provider without a catch-all strangles throughput.

Slice in order: range, request, supply, storage. Most gremlins fall to these.

Spotting Charging Jams vs Power Shortage

Slow robots often indicate charging queue, not understaffing. Watch roboports: are bots stacked waiting? That's queuing. If network-wide movement droops, suspect power shortage.

Visible stacks near roboports = charging gridlock. Fix: more roboports in hot zones, or shrink network distances. Same net, faster locals.

Power issues dim everything. Telltale: roboports failing to keep charge, erratic robot motion.

Either way, solution: densify ports in congestion zones, reduce sprawl, split networks. Correct for roboport shortage first; it's the frequent culprit.

The Gigantic Network Trap and Splitting Basics

Newbies love one enormous network—looks elegant, seems convenient. It's a trap. Sprawl kills it: delays, congestion, opaqueness.

Worst case: link defence supply, distant outposts, and the core in one net. Robots get pulled to periphery emergencies, starving the core. Saw this happen: external walls needed ammo, sucked all logistics robots away. Core mall emptied. Split defence into its own net and boom—internal supply stabilised, defence got dedicated bots.

Breakpoint thinking: segment by purpose. Mall net, lab net, defence net, construction-support net. Local runs = short trips = few charging queues = obvious bottlenecks = fixable problems.

Small tight nets beat one sprawling one. Move distance drops, management tightens, scaling becomes predictable.

Robopost-spread design: better to densify in hotspots than uniform grid. Roboports cost little; congestion costs throughput.

The design principle: enable robots to quick-cycle locally, not commute globally. That's where logistics robot magic lives.

Advanced: Stock Control and Network Segmentation

Inventory and Bot Count Signals

Once roboport signals feed into circuits, inventory levels trigger equipment. "Restock rails when they drop to 50," "halt research-pack production above 200," "spin up ammo when we hit red"—automatable.

This pairs beautifully with purposeful network splits. Each net's inventory signal = specific zone needs. Read directly, no guessing. "Lab net inventory low" means labs need stock, act accordingly.

Bot count signals also work: rotate robot stockpiles on supply, e.g., "keep 10 spare build robots." High multip-layer construction eats them; signal keeps reserves topped.

Circuits aren't complex arithmetic at first. Start "shortage = make, surplus = stop"—two thresholds. Complexity follows naturally.

Preventing Signal Chatter and Hysteresis

One trap: treating signals like binary 0↔1 switches. In-transit items and reservation delays make counts flutter. Fluttering triggers oscillation—factory spasms.

Solution: hysteresis—separate ON and OFF thresholds. Turn on at 50, off at 100. Flutter between 50–100 doesn't flip. Behaviour stabilises instantly.

This tiny shift—vagueness over precision—sounds wrong but works. Robot networks have slosh; embrace it.

Segmentation Patterns in Practice

Splitting by role unlocks circuit control. Shared networks mix signals; split nets isolate them.

Mall net: multi-item, short-haul, dense. One net, clear inventory meaning, clean restocking logic.

Lab net: bulk-science supply. Isolated, so restocking doesn't fight mall demands. Watch packs separately.

Defence/build net: walls, ammo, repair packs, construction gear. External threats crash demand; split keeps calm.

Each segmented net narrows the signal scope—"this net's inventory" has clear meaning. Control tightens. Troubleshooting simplifies.

Segmentation lets circuit logic actually work. Broad networks = blurry signals = poor automation. Tighter nets = cleaner signals = smarter response.

2.0 / Space Age Deltas and Notes

Ground Robot Logistics' Invariant Core

Even as 2.0 and Space Age evolve logistics, the ground-level design fundamentals hold. I still ask: "How far?" "Where's charging congestion?" "What job does this net handle?" These don't shift with QoL bumps. UI gets friendlier, but the structural reasoning stays put.

Especially: local operation still dominates. Malls, labs, builds, resupply love robots. Tapping the whole factory into one net still sags. Robot smarts don't change physics—far distances and charging waits still cost. Design once acknowledging that, you're golden.

Roboport specs anchor planning. Ranges (50/110), charging slots (4), speed (3 tiles/sec unresearched)—these frame viability. UI sugar doesn't alter the frame.

Shifting Details and Confirmation Sources

2.0 brings QoL: better GUI, integrated radar in roboports, improved visibility. Helpful! But "easier to manage" ≠ "change what works." These tweaks serve you, not reshape fundamentals.

Risk: 2.0 info gets jumbled. "Heard it'll be in 2.0," "saw it once," "got patched since"—hearsay spreads faster than patches. Ground truths, tested now, and planned features mingle. Robots got quality tweaks but not physics overhauls, as far as core design goes.

To track precisely, check Factorio Wiki's Upcoming features page. It separates planned, implemented, and patched, cutting confusion.

Space Age's Separate Ecosystem

Space platforms don't run standard robot logistics—can't place normal chests, porting works differently. Space is a parallel logistics system, not ground extension. Roboports and robots idle in orbit.

This isn't a nerf; it's a rulebreak. Design shifts entirely—belts and hubs, not chests and robots. Not worth forcing ground logic upward.

In this post, focus is ground. Space deserves its own framework. Separate concerns = clearer thinking.

Recap and Next Steps

Robot logistics excels as a surgical tool for tricky zones, not an industry-wide blanket. I start with passive-to-requester basics, densify roboports where queues form, and split labour: robots for multi-item restocking, belts for bulk, trains for long haul.

Next, train networks (inter-base, main lines) let you dial in roles across your whole factory. Check Factorio Wiki's train and main-bus entries for deep dives.

(Sidebar) This site's article count is small; internal link plumbing isn't complete yet. Future reference anchors:

Planned articles (slug — title):

• logistics-train-network — Train Network Essentials

For immediate reference, Factorio Wiki's train, belt, and main-bus entries are your go-to sources.