Print farm workflows: running a farm with the print queue, AutoPrint and automation

Running a print farm is mostly a logistics problem. You have the machines and you know what needs printing - the hard part is getting the right job onto the right printer at the right time, over and over, without babysitting every start. SimplyPrint is built around one idea that solves most of that: stop thinking about individual prints, and start thinking about the queue.

The recommended operating model is simple. Upload files to the print queue the moment you know what to print. From then on your job is to manage the queue - positions, priorities, what's paused, what's on the back burner - and SimplyPrint orchestrates the rest: it matches each job to a compatible printer and gets it started, with 1-Click Print or AutoPrint, all spread out by Staggered Start so you don't trip a breaker. In our 2026 print-farm survey, almost every farm named the print queue as the feature they'd miss most. This article is the map of how the pieces fit together.

Table of contents

• The operating model: upload, then manage the queue
• How SimplyPrint routes each job
• Getting jobs onto printers: 1-Click Print and AutoPrint
• Maintenance: optional, but it pays off
• Filament tracking: optional for farms
• Users and permissions
• The API and order automation
• Scaling from a small farm to a big one

The operating model: upload, then manage the queue

The shift that makes a farm run smoothly is treating the queue as the central hub instead of the thing you reach for when a printer goes idle. As soon as you know a part needs to come off a machine - a customer order, a batch of the same model, a one-off - you add it to the queue. You're not deciding which printer right now. You're just lining up the work.

Once it's in the queue, your day-to-day is managing it, not starting prints by hand. Each item has controls that let you shape the flow:

• Position and priority: drag an item or type a position number. Items print top-down.
• Pause: an item keeps its position but won't be picked up until you resume it.
• Back burner: a low-priority lane. A back-burner item is only matched when nothing higher in the queue matches.
• Infinite: print the same item indefinitely, which is ideal for a product you always want machines filling spare capacity with.
• Max concurrent printers: cap how many printers a single item runs on at once.
• Keep in queue when done: leave a finished item in place to re-run later.

Adding items is just as flexible: upload a file, split a multi-plate 3MF into separate items, attach custom fields or an order number, or push items in over the API. The point of all of this is that the queue holds your intent, and the routing engine figures out the rest.

How SimplyPrint routes each job

SimplyPrint matches each queue item to a compatible printer automatically. A printer is eligible for an item when it satisfies all of the item's requirements:

• the item's filament (its type and colour name) and nozzle size
• any custom tags on the item
• printer, model and group assignment, plus queue group eligibility
• bed type, accepted file type and build-volume fit
• required temperatures and the item's max-concurrent-printers cap

A printer must carry all of an item's tags. It can have extra tags the item doesn't need, never the other way around. You can apply those tags by hand, or let smart tagging set them automatically from file metadata and filename rules, so a freshly uploaded file routes itself without you touching it.

How jobs get spread across the fleet is governed by scheduling and distribution settings that both 1-Click and AutoPrint share: sequential versus round-robin item scheduling, and a printer distribution mode (by position, randomized, or least-recently-used to spread wear evenly). Tune them once and both start methods behave the same way.

Queue groups let you organise the queue by printer set or by purpose, and they have one trick worth knowing for a busy farm: virtual queue groups. A virtual group tracks work that never goes to a SimplyPrint-controlled printer - outsourced parts, a manual finishing step, an unsupported machine, or even a non-3D-printer job. You mark each one done by hand while it keeps its queue position, deadline and tracking, so your whole workload lives in one place even when some of it happens off-platform.

Getting jobs onto printers: 1-Click Print and AutoPrint

With the queue full and routing configured, there are two ways to actually start prints across the fleet. They use the same engine and the same distribution settings - the only real difference is who pulls the trigger.

1-Click Print matches the next job to every printer that can run it and starts the whole batch with one click, after you review the preview. You stay in the loop: you look at what it's about to do, then launch. It's the right default when you want a human to glance at the batch before machines start moving, and it needs no extra hardware.

AutoPrint removes the click. The moment a printer is free and its bed is clear, AutoPrint starts the next matching item automatically. That's the closest thing to lights-out printing - you fill the queue, walk away, and machines keep pulling work as they free up.

The catch with AutoPrint is the bed. A printer can't start the next job until the last one is off the plate, so AutoPrint needs a bed-clearing method. SimplyPrint handles the matching and the software side; you handle the clearing hardware (or clear by hand). The available clearing methods range from manual, to gcode-based push-off with a kit, to belt printers, to API-based ejection rigs - and there's a long list of supported hardware partners. An optional AI bed check (in beta) confirms the bed is empty before the next print starts.

So which do you use? If you don't have bed-clearing hardware, or you want eyes on every batch, run 1-Click Print. If you have the clearing side sorted and want machines to keep themselves fed, switch those printers to AutoPrint. Many farms mix the two: AutoPrint on the machines that can clear themselves, 1-Click on the rest.

Both go through Staggered Start, which limits how many printers can heat up at once. Starting a whole fleet together is the moment you'd trip a breaker - heating draws the power spike, not the printing itself - so Staggered Start releases the next printer once one finishes preheating. An optional download cap helps when a lot of simultaneous file transfers choke the network. Every print start is staggered, whether it came from the web, the app, the API, 1-Click or AutoPrint.

Maintenance: optional, but it pays off

Maintenance is entirely optional - it's off until you turn it on. But for a farm running machines hard, it earns its keep in two ways: uptime and traceability. When a print fails and you want to answer "why did this go wrong, and when was the nozzle last changed on this printer", a maintenance history is what gives you the answer.

When you switch it on, you get usage-based scheduling (trigger maintenance by days, print hours, filament grams, print count or failure rate), reusable task templates for your standard procedures, a spare-part inventory with stock levels, low-stock alerts and automatic deduction, work-order jobs, and problem reports - all with a full per-printer history.

There's a nice automation here too. Bambu Lab HMS codes (a clogged nozzle, a loose belt, a dirty Lidar, foreign objects on the bed) can drive maintenance for you. SimplyPrint reads the HMS codes in real time and, via a task template's "printer notification" trigger, marks the right maintenance task due on the printer that raised it - then a maintenance schedule turns that due task into a job. The built-in mapping is opinionated, not exhaustive, so it covers common codes rather than every one; unmapped codes still show on the printer but won't fire a maintenance trigger.

Filament tracking: optional for farms

The filament manager is optional, and farms genuinely split on it. Roughly half the farms we surveyed lean on it; the others stick to static materials and that's fully supported. There's no wrong answer here - it depends on whether you need to know about individual spools.

If you don't track per-spool, you use a static material: you tag a printer (or a file) with the material itself - its type, from a material profile, plus the colour, colour name and hex - with no per-spool identity, and never create an inventory spool. The queue still matches on filament type and colour, so routing works perfectly without ever tracking a single spool. This is the right call if you burn through filament fast and don't care which physical spool a print came off.

If you do want spool-level traceability, the filament manager gives each spool a digital twin: automatic usage deduction when prints run through SimplyPrint, a runout warning at print start if there isn't enough on the assigned spool, full per-spool history, cost tracking, and batch or internal-production IDs for traceability. If a customer asks which batch a part came from, that's the answer.

The deeper dive on choosing and running filament tracking is its own workflow - see the filament tracking workflows guide.

Users and permissions

Multi-user accounts (user groups) are a Print Farm, School and Enterprise feature. SimplyPrint has a large, granular set of permissions, organised into categories like printing, the queue, slicer, filament, maintenance, users and organisation management. You don't assign permissions one by one to each person - you bundle them into named user groups and put people in the right group.

For a farm, that usually means an operators group that can start and manage prints, a group for whoever runs maintenance, and an admin group for account-wide settings. The split between "see the printers page" and "start prints from the panel" is separate, so you can give someone visibility without giving them the ability to launch jobs.

The API and order automation

SimplyPrint has a full REST API (Pro and up; the enhanced write API is Print Farm and up). The most common farm use is feeding the queue programmatically: an automation adds queue items for you instead of someone uploading files by hand.

The way farms handle shop orders today is with their own automation: a script (often glued together with a tool like Zapier or n8n) reads a new order from your shop, then pushes a queue item via the API and writes the order number into a custom field so the part stays traceable from order to finished print. It's a build-it-yourself pattern rather than a click-to-connect feature. Tighter order integrations are something farms ask for often, and they're on the roadmap.

Scaling from a small farm to a big one

The nice thing about this model is that it doesn't change shape as you grow. A five-printer farm and a hundred-printer farm both run the same loop: upload to the queue, let matching route, start with 1-Click or AutoPrint, stagger the starts. What changes is how much you lean on each piece.

A smaller farm often runs the queue with 1-Click Print and clears beds by hand. As you add machines, AutoPrint and bed-clearing hardware start to pay for themselves, queue groups keep different product lines or printer sets organised, and maintenance scheduling stops a growing fleet from drifting into surprise failures. Farms in our survey reported saving anywhere from 3 to 20-plus hours a week (most clustering around 10-15), and one 140-printer farm told us they manage roughly twice the printers with the same staff - the same loop, just scaled.

A couple of surfaces help once you're at scale. Display Screens put a live status wall up in the room so anyone can see the state of the fleet at a glance, and the statistics dashboard tracks job counts, print time, success rate and filament used over time. If walk-up operators share machines, the Hub gives them a stripped-down in-room screen to operate printers under their own login.

Related articles

• Workflows: which SimplyPrint workflow fits you
• Ways to start a print: manual, 1-Click, queue and AutoPrint compared
• Filament tracking workflows for farms
• Running SimplyPrint in a school or makerspace
• The print queue: manage, schedule and automate your prints
• 1-Click Print: batch start prints across your printers
• AutoPrint: put your printers on autopilot
• AutoPrint clearing methods: every way to clear the bed
• The Staggered Start feature
• Scheduling and printer distribution: how SimplyPrint assigns prints
• Queue groups: organize your print queue by printer or purpose
• Printer maintenance: keep your fleet running smoothly
• User groups and permissions: what each one controls
• The SimplyPrint API: a quick intro for developers

Updated on: 25/06/2026