Bellwright Outpost Deliveries Guide to Prevent Stockpile Shortages

Set the order from the settlement or outpost that needs the item. In Bellwright’s Deliveries screen, the location you are currently viewing is the destination; you then choose the settlement or outpost that supplies the item as the origin. Keep the goods in eligible stockpile storage, make sure the destination has room under the correct storage filter, then use Top Up, Daily, or Weekly based on how the outpost consumes the item. Source: Bellwright Wiki — Deliveries; Bellwright Wiki — Stockpile.

Version note: this guide reflects the maintained delivery documentation and patch records available through 18 June 2026. The reviewed records include an outpost-relocation hotfix dated 27 January 2026 and an update dated 16 February 2026. No numbered game build is stated in those records. Source: 18 June 2026 patch record; 27 January 2026 hotfix; 16 February 2026 update.

Table of Contents (6)

Use Deliveries for transfers, not the Delivery job

The naming is the main trap. Delivery is the local work priority that gets villagers moving goods around inside one settlement or outpost. Deliveries is the inter-settlement screen for requesting items from another one of your locations. Raising local Delivery priority can help move output into a stockpile, but it does not create a transfer order to another base. If your camp has mushrooms sitting in a producer building instead of in storage, local Delivery can help fix that; if you want those mushrooms moved to another settlement, you still need a Deliveries order. Source: Bellwright Wiki — Delivery; Bellwright Wiki — Deliveries.

System	What it handles	How it affects shortages
Delivery	Local hauling within the current settlement or outpost.	It helps get production into eligible storage, where a transfer order can access it.
Deliveries	Transfer orders between your own settlements and outposts.	It directly controls recurring supplies and exports between locations.

Outpost deliveries are simulated. You do not need to wait for an NPC to physically walk a route between the two locations before the order can work. The important checks are the selected origin, eligible stored supply, destination capacity, filters, and the order’s displayed result. In other words, when a transfer stalls, the usual culprit is storage state or capacity, not a missing courier marching through the forest. Source: Bellwright Wiki — Deliveries.

Read the destination target in the right direction

Think of the Deliveries screen as a request made by the location currently on screen. If you are viewing a remote logging outpost, every order you create there asks another settlement to send goods to that outpost. Select the main village as the origin when you want food, tools, or other supplies sent outward. That one mental flip solves a lot of “why are my goods going the wrong way?” confusion. Source: Bellwright Wiki — Deliveries.

For an export order, reverse the setup: open Deliveries while viewing the main settlement, then select the resource-producing outpost as the origin. That makes the main base the receiving target for ore, wood, or another material produced remotely. The destination is always the place you are currently managing in the screen, not the place with the goods. Source: Bellwright Wiki — Deliveries.

Make the item eligible before creating the order

A delivery order draws from the origin settlement’s eligible storage. An item sitting in a hut, workstation, or other production inventory can remain unavailable to the order and show as waiting for pickup rather than becoming transferable stock. Move the item into a stockpile, storage hub, or appropriate category-specific storage first. What you do here is simple: make sure the item exists in storage. What the game does next is equally simple: it checks storage, not wishful thinking. Source: Bellwright Wiki — Stockpile; Bellwright Wiki — Deliveries.

• At the origin: keep the requested item in eligible storage rather than leaving it inside the building that produced it. Source: Stockpile; Deliveries.
• At the destination: leave enough free capacity for the incoming goods, because a full receiving side can block the order even when the source is stocked. Source: Deliveries; Stockpile.
• For storage filters: match the item to the proper storage category. Food belongs in food storage such as a Food Cellar, while weapons require suitable weapon storage such as a Weapon Rack. Source: 19 June 2024 patch record.
• For local production chains: use the Delivery work priority to help villagers move output into stockpiles, then let Deliveries handle the transfer between locations. Source: Delivery; Deliveries.

Since the 19 June 2024 update, outpost deliveries respect storage filters. That means a valid order can still fail to finish if the destination has no acceptable filtered storage or its compatible storage is full. The same logic applies at the origin too: if the item is not sitting in storage that accepts it, the order may have nothing eligible to pull. Source: 19 June 2024 patch record; Bellwright Wiki — Stockpile; Bellwright Wiki — Deliveries.

Choose the schedule that prevents the shortage

Setting	Best use	What to watch
One-time	An initial setup shipment or a single urgent request.	It does not replenish the item again after that delivery.
Daily	Supplies with steady day-to-day consumption, including food, tools, or ammunition.	Confirm the origin has enough eligible stock for each scheduled request.
Weekly	Bulkier goods or predictable, slower consumption.	Leave enough destination capacity for the larger replenishment window.
Top Up	Keeping an outpost at a chosen target amount without constantly managing it.	Set a target the destination can store and the origin can support.

Top Up is the cleaner choice for a remote camp that should always retain a reserve. It was added for outpost deliveries in the 19 June 2024 update. Use Daily or Weekly when you want a fixed scheduled amount instead of maintaining a stock target. In plain language: Top Up says “keep this place at X,” while Daily and Weekly say “send X on a schedule.” Source: Bellwright Wiki — Deliveries; 19 June 2024 patch record.

If an outpost burns through food at a fairly even rate, Daily is easy to reason about. If the camp mostly needs periodic restocks, Weekly may be less noisy. If the goal is simply “never let the place run dry,” Top Up is the better fit because it maintains a reserve instead of forcing the same batch size every cycle. Source: Bellwright Wiki — Deliveries.

Worked example: send 10 Smoked Mushrooms to a logging outpost

To supply a remote logging outpost with 10 Smoked Mushrooms per day, view the Deliveries screen for the logging outpost. Select Smoked Mushrooms, choose the main village as the origin, select Daily, set the amount to 10, and assign the order’s priority. The outpost is the destination because it was the location open when the request was configured. Source: Bellwright Wiki — Deliveries.

1. Start at the receiving end, not the sending end. Open the logging outpost and work from its Deliveries screen, because that tells the game this outpost is the destination. You do: pick the place that needs food first. The game does next: it treats every order in that view as a request coming into the outpost. If you open the main village instead, you are building the order in the opposite direction. Source: Deliveries.
2. Pick the item, then the supplier. Add Smoked Mushrooms to the order and choose the main village as the origin. You do: tell the system what the outpost wants and which settlement should provide it. The game does next: it will try to pull that item from the selected origin’s eligible storage, not from every building in the settlement and not from some unnamed global stash. Source: Deliveries; Stockpile.
3. Check storage rules at both ends before trusting the order. In the main village, make sure the mushrooms are already in a stockpile or food-compatible storage instead of sitting in a hut or producer inventory. In the logging outpost, make sure there is free food-compatible storage space. You do: verify origin eligibility and destination capacity. The game does next: it can only transfer stock it recognizes as stored, and it still needs somewhere valid to place the delivery on arrival. Source: Stockpile; Deliveries; 19 June 2024 patch record.
4. Choose the schedule that matches the problem you are solving. For this exact example, select Daily and set the amount to 10. If the outpost instead needs a standing reserve, use Top Up and set the target amount you want it to keep on hand. You do: choose fixed recurring quantity or reserve maintenance. The game does next: Daily and Weekly request the set amount on schedule, while Top Up requests what is needed to bring the destination back to the target. Source: Deliveries; 19 June 2024 patch record.
5. Read the UI before you start rebuilding half the outpost. Check the delivery interface’s available-item count, capacity hint, and last delivery result. You do: use those readouts to see whether the source had enough mushrooms and whether the destination could take the full amount. The game does next: if only part of the request can be filled, the result readout tells you the order under-delivered instead of leaving you to guess. Source: 27 June 2024 patch record.

That same logic works in reverse for exports. If an ore outpost should feed the main village, open Deliveries while viewing the main settlement, choose the ore-producing outpost as the origin, then use Top Up or Daily depending on whether you want a reserve at home or a fixed recurring shipment. Source: Bellwright Wiki — Deliveries; 19 June 2024 patch record.

The delivery UI added available counts for the source and target settlements, delivery-capacity hints, and a last-result readout on 27 June 2024. Use those fields before changing priorities or rebuilding storage: they show whether the origin lacked eligible goods, the target lacked room, or the request was only partially fulfilled. Source: 27 June 2024 patch record.

Fix a stalled or partial transfer

What you see	Likely cause	Practical fix
The order is waiting for pickup.	The item is inside a hut or workstation inventory instead of eligible storage.	Move the item into a stockpile, storage hub, or matching filtered storage at the origin.
The requested goods exist, but the order finds none.	The origin’s storage filter does not accept that item.	Check that the item is stored in a compatible category and is not blocked by a filter.
The order delivers less than requested.	The origin lacks enough eligible stored items, or the target cannot accept the full amount.	Use the available count and last delivery result, then increase compatible storage or reduce the request.
The delivery does not complete at all.	The destination’s compatible storage is full.	Free capacity or add suitable storage at the receiving settlement before retrying.
Goods are travelling the wrong way.	The order was created while viewing the supplying location.	Open Deliveries at the location that should receive the item, then select the supplier as origin.

The reliable fixes are not glamorous, but they are consistent. First, check whether the goods are in real storage or still marked as waiting for pickup. Second, check whether both sides have storage rules that accept the item. Third, check whether the destination has room. Only after that should you worry about changing the schedule or amount. Source: Bellwright Wiki — Stockpile; Bellwright Wiki — Deliveries; 19 June 2024 patch record.

A universal per-cycle delivery limit or a reliable villager-to-throughput formula is not documented in the maintained delivery references. Use the in-game capacity hint, available item counts, and last delivery result for the specific settlements involved instead of planning around an assumed numeric cap. That keeps the troubleshooting grounded in what the current UI actually tells you. Source: 27 June 2024 patch record; Bellwright Wiki — Deliveries.