Alchemy Factory Logistics: Belts, Wagons & Profit
Alchemy Factory Logistics: Belts, Wagons & Profit

Update Datetime: 2026-10-13 13:06
Alchemy Factory / TIPS
Alchemy Factory Logistics: Belts, Wagons & Profit

Alchemy Factory offers several transport systems, and the 1.0 release changes how products, customers and profit upgrades interact. This guide focuses on diagnosing a production network, choosing when a wagon route is useful, and reading shop results without confusing a patched statistics problem with a broken factory.

Version scope: the released 1.0 game and its September hotfixes. The Dedicated Server feature is labelled experimental in the release notes. Prices and availability vary by region.
Transport
Belts / pipes / wagons
Factory space
Multiple floors
Key version
1.0 release + hotfixes
Profit check
Recognition and Ledger

1. Find the first constrained stage of the chain

Trace a product from its material source to processing, transport and final destination. The official description stresses balancing inputs and outputs, but it does not provide a single throughput ratio for every machine. Use the recipe and device information shown in your installed game. An empty input, a stopped process and a blocked output imply different fixes. Observe which appears first before adding parallel equipment; otherwise you can increase production on the wrong side of the same bottleneck.

Sources: Current Steam listing

2. Keep vertical production and shopping access distinct

The factory supports conveyors, pipes and devices at different heights. Customer access also supports upper floors in 1.0, but these are two different routing questions. A material reaching an elevated machine does not prove that customers can reach the shelf nearby. The upper-floor and staircase fixes in September reinforce the need to test both paths. After restructuring, follow one material route and one customer route separately. This makes a transport fault easier to distinguish from a shop navigation issue.

Sources: Current Steam listing / 1.0 release notes / Blueprint and upper-floor hotfix / Invites and stairs hotfix

3. Use wagons when their capacity solves a real problem

The Wagon System has greater transport capacity than conveyors, according to the release notes, while requiring more construction and planning. That is a reason to evaluate it for a demanding route, not a reason to replace every short belt. Plan the source, destination, branches and handoff before building a rail network. The game also permits transforming into a wagon to inspect the route. Use that perspective to understand your layout instead of assuming that additional capacity will correct an incorrectly connected destination.

Sources: 1.0 release notes

4. Verify branches after copying or mirroring track layouts

Hotfix 1.0.4950 fixes reversed route-selection results on mirrored Track Sorters and adds clearer branch indicators. If a mirrored segment seems to send goods in the wrong direction, inspect the current indicators and confirm that you have that fix before redesigning the entire network. The later curved-track collision adjustment allows closer placement; it does not document a universal minimum gap for every layout. Check the actual build preview and the route you created rather than relying on a spacing number from an old guide.

Sources: Unlock and sorter hotfix / Ledger and receiving-rule hotfix

5. Check receiving permissions on magical transport

The Arcane Fountain searches for suitable targets, but Hotfix 1.0.4962 changes the default receiving behavior of Table Saws and Stone Crushers: they no longer accept its inputs unless the player specifies otherwise. A silent receiver may therefore be a configuration issue rather than a missing supply or a full transport route. Check what the target is allowed to receive before adding another fountain. Keep this receiving rule separate from the range and target information shown while constructing throwing devices.

Sources: 1.0 release notes / Ledger and receiving-rule hotfix

6. Re-read recipes before reusing an Early Access layout

Version 1.0 reduces Linseed Oil production and consumption quantities proportionally and changes the Obsidian byproduct from Volcanic Ash to Marble. A blueprint or written recipe plan built around the older outputs can therefore route an unexpected item into storage or the wrong downstream process. Inspect both the principal product and every byproduct when updating a line. Do not invent a new numerical ratio from the proportional-change note; use the values displayed by the current recipe for your actual capacity calculation.

Sources: 1.0 release notes

7. Compare profit over valid days rather than one suspect total

Shop Recognition now includes benefits that previously came through separate sales or purchase-contract upgrades. The Ledger fix subsequently corrects profit-upgrade statistics, with a warning that the first in-game day after updating may show incorrect data. When evaluating a factory change, identify which recognition benefits are active and compare days that are outside that reporting caveat. Keep costs, sale prices and the recorded period consistent. This separates an economic decision from a temporary display issue without promising that a particular line will always be profitable.

Sources: 1.0 release notes / Ledger and receiving-rule hotfix

8. Import blueprints as inspectable modules

Workshop designs can speed up planning, but a large imported blueprint can conceal several different dependencies. Check equipment unlocks and Purchase Contracts, then inspect the material entrances, output destinations and branch controls of one module. The release improves warnings for locked contracts, and a later patch fixes blueprint creation after editing. Confirm those corrections if a blueprint workflow fails. Preserve an understood working route while comparing a new design; a complicated shared factory is a learning aid, not a verified optimal setup for every save.

Sources: Current Steam listing / 1.0 release notes / Blueprint and upper-floor hotfix

SymptomInspect before rebuilding
Saw ignores thrown inputsArcane Fountain receiving permission
Mirrored branch misroutesCurrent Track Sorter indicators and patch
Profit upgrade seems absentRecognition state and valid Ledger days
Practical check

Change one transport or production variable at a time. A usable diagnosis identifies the recipe, receiving device and route where movement stops.

Related guides

Key points

Choose capacity upgrades for an observed need, test customer access separately, check updated byproducts and receiving rules, and judge profit using the corrected Ledger. Verify blueprint dependencies before treating a shared layout as ready to run.

Sources checked October 13, 2026. Published facts are linked beside their explanations. Planning and practice suggestions are editorial advice rather than verified optimal builds.

Comment

No comments yet. Be the first to post one.


Note Do not post abuse, off-site solicitation or illegal information.
None
Attached image preview