Articles on: Get started

Filament tracking workflows: static materials, tracked spools, labels and NFC

The Filament Manager can look like a black box. You open it, see a prompt to add spools, and it's not obvious whether you should be cataloguing every roll you own, or whether you can ignore it entirely and still get on with printing. The short answer: it's optional, and most people use far less of it than they think they need to.

This article is about the decisions, not the buttons. When do you actually need to track individual spools? When can a lightweight tag do the whole job? When should filament land in your inventory - the day you buy it, or the first time you print with it? And once you do want per-spool tracking, how do you give each spool an identity the system can recognise - a printed label, or an NFC tag? Each path links out to the step-by-step article that covers the mechanics.

The Filament Manager basics are available on every plan, including Free, and so is multi-material mapping and syncing. What your hardware can do (auto-create a spool, sync remaining weight) depends on the printer and the client that connects it, not on your plan. Two things are plan-gated: full NFC read and write comes with the Filament Manager plan and Pro and up (Free includes a small monthly NFC-write allowance), and printing labels straight to a Zebra or DYMO thermal printer needs the Pro plan.

Do you even need to track individual spools?

The first decision is the biggest one, and it's easy to overthink. You do not have to track individual spools at all.

The lightweight path is a static material. This is material-tag data you set directly on a printer (and it can come along with a file or a queue item too): the material type is identified by a material profile - a reusable definition like "PLA" or "Bambu Lab PLA Basic" that carries the print temperatures, density and cost - and the tag adds the colour on top, including a colour name and hex, plus a couple of other details. There's no inventory spool behind it. The queue can still match jobs to printers by material and colour, the printer can preheat to the right temperature, and cost calculations work. Plenty of farms stop right here, and that's a complete, supported workflow.

Think of it as two layers: the material profile answers "what kind of filament is this?" (type, temperature, density, cost), and the static material is that profile plus the specific colour, assigned to a printer. The profile is reusable across every spool of that type; the colour is what makes the tag a particular filament.

Filament tracking onboarding showing the different tracking options, including a no-action path

The deeper path is the Filament Manager itself, which tracks individual spools. This is the layer to add when you care about which physical roll is which - weight remaining per spool, full history, cost per spool, batch traceability. Adding spools is an honest extra step, and you only take it if you want that payoff.

So the real choice is static material versus tracked spool. A static material is the lightweight tag - the material type from a profile, plus its colour - assigned to a printer with no inventory and no per-roll identity. A tracked spool is the Filament Manager layer, where each physical roll gets its own record. If you burn through filament fast and don't need spool-level traceability, static materials are enough. If you need to know that this exact spool is 38% empty or which batch a part came off, that's when per-spool tracking earns its keep.

New to material profiles? The material profiles article explains exactly what a profile covers (and what it doesn't) - it's the right read before you decide you need full spool tracking.

What tracked spools give you

When you do track a spool, it gets a "digital twin" - a unique record with a short 4-character ID (like RX75) that follows the physical roll through its whole life. That record carries weight tracking, a full per-spool history (when it was dried, weight adjustments, the jobs it ran) and cost.

A tracked spool's detail page showing weight remaining and quick actions

The headline benefit most people want is the runout warning. If a tracked spool is assigned to a printer, SimplyPrint warns you before the print starts when that spool doesn't have enough filament left to finish the job. Worth being precise about what this is: it's a check at print start, not a live mid-print alert. It only exists because the spool is tracked and assigned to the printer - without that, there's nothing for SimplyPrint to weigh the job against.

Usage updates the same way. When you start a print through SimplyPrint - the queue, the print button, the slicer, the mobile app or the API - the filament used is deducted from the assigned spool when the print ends. Cancelled or failed prints deduct proportionally, so a job that died at half-way takes off roughly half. Prints you start straight from a USB stick or the printer's own screen never pass through SimplyPrint, so they aren't tracked automatically; you can always adjust a spool's weight by hand. The filament usage tracking article goes deeper on the maths.

When should you add filament - at purchase or at first use?

Once you've decided to track spools, there are two natural moments to add them, and you can mix both.

The first is at purchase or unboxing. Add a spool the day it arrives - even sealed, even before you've printed a gram - so your stock count is complete from day one. This is the move if you want a true overview of everything you own, including the rolls still in the box. If you buy in 10-packs, you can create the whole batch at once with the quantity field.

The second is at first use. Let a spool create itself automatically the first time a supported multi-material system sees it. You don't catalogue anything up front; the inventory fills in as you print.

One catch worth knowing if you mix the two. If you pre-create Bambu spools in SimplyPrint and then load them into the AMS, link their NFC tags right after you create them. Otherwise the AMS sees a spool it doesn't recognise and creates its own, and you end up with duplicates - five new physical spools but six records. Linking the tags as you create the spools is what stops that.

How auto-creation actually works

Auto-creation feels magical, but it has one hard requirement: the printer has to report a unique per-spool ID. That's the whole ballgame, and it's why the experience differs so much between brands.

When a printer does send a unique ID, SimplyPrint looks the material up in the Open Filament Database to identify exactly what it is, creates the spool, and then auto-assigns and unassigns it as you move it between slots. Here's the reality per system:

Bambu Lab AMS - full support, but only for genuine Bambu spools. Their factory spools carry the official RFID tag with the data on it. A third-party or untagged spool sitting in a Bambu AMS reports no ID, so it syncs as material and colour only, with no per-spool identity (Bambu's tags are encrypted, so third-party readers can't decode them).
Anycubic ACE / ACE Pro - hands-free inventory is not possible; the hardware doesn't send a per-spool ID. You can still map a multi-colour print, just not auto-create spools.
Creality CFS - only works for tags you wrote through SimplyPrint. By default the CFS doesn't hand over a usable serial, so SimplyPrint embeds its own ID onto a tag you write, then recognises that.

That split is the reason this topic has two follow-up articles. If you run Bambu Lab spools, the path is read-and-assign and it's mostly hands-free. If you run anything else, the path is write-and-assign and you do a bit of setup once per spool.

Bambu Lab filament workflow covers the AMS read-and-assign path. Third-party and Creality filament workflow covers writing your own tags for everything else. The automatic spool creation article is the authority on which system does what.

Giving each spool an identity: labels or NFC

Two otherwise-identical spools of black PLA need a way to be told apart, and there are two families of answers: a printed label you scan, or an NFC tag the printer (or your phone) reads.

Labels - the no-NFC option for any printer

Labels are the simplest path, and they work no matter what printer you have - including older or "dumb" machines that can't read a tag. SimplyPrint generates QR-code and barcode labels for your spools, which you print on plain paper, on a sheet of label stickers, or straight to a Zebra or DYMO thermal printer.

The label generator with paper, Zebra and DYMO presets and a live QR preview

To use one, you scan it. Point a phone camera or a webcam at the QR code, or a USB barcode scanner at the barcode, and SimplyPrint pulls up that spool so you can assign or unassign it in seconds. It's a tidy fit for a shared bench: stick a label on every spool, and anyone can scan-to-assign before a print without typing anything.

A printed A4 sheet of filament labels with QR codes and spool IDs

The label generator overview covers layouts and printing, and scanning labels walks through the scan-to-assign flow. Direct printing to Zebra or DYMO thermal printers is a Pro-plan feature.

If you'd rather mark spools without QR codes, there's also a simple-IDs workflow - short human-readable IDs you can write on a spool by hand. It's the most basic identity layer, and it's there for people who want spool tracking without printing anything.

The simple-IDs spool labeling workflow

NFC - read for Bambu, write for the rest

NFC is the tap-and-go option, and how you use it depends on the brand:

Bambu Lab is read-and-assign. The factory spools already carry NFC tags, so you link those existing tags to the spool's digital twin. Spools typically have two RFID stickers, one on each side, and each tag has its own unique serial - that serial is what lets SimplyPrint tell two identical spools apart, which is why you scan both sides when you link one.
Creality, Anycubic, QIDI and ELEGOO are write-and-assign. You create the spool in SimplyPrint, then write its identity onto a cheap blank NFC tag in that brand's format and stick it on any spool. You don't have to buy the brand's filament - you're writing the identity yourself.

One thing that trips people up: NFC is not just NFC. Each brand needs a specific tag type, and the wrong tag won't work. Which device can read or write also varies (the mobile app, a desktop reader, or Web NFC in an Android browser). The per-brand articles below spell this out, because it genuinely differs between Creality, Anycubic, QIDI and ELEGOO.

The NFC overview is the hub for all of this - tag types, devices and standards. Multi-material printing covers mapping and syncing your AMS, ACE or CFS, and assigning spools covers the final assign step both NFC paths end in.

A quick way to pick your path

If you're still not sure how far to go, this is the short version:

Just want matching, preheat and cost? Use a static material. No inventory, no spools to add.
Want to know how much is left and get a runout warning? Track spools, and assign them.
Run genuine Bambu spools in an AMS? Track spools and let auto-create and read-and-assign do most of the work - see the Bambu workflow.
Run Creality, Anycubic, QIDI, ELEGOO or anything else? Track spools and write your own NFC tags, or use labels - see the third-party workflow.
No NFC at all, or older printers? Generate labels and scan to assign.

Filament inventory grouped by brand and material

None of this is all-or-nothing. A common pattern is to start with static materials, add spool tracking for the filament you care about most, and layer NFC or labels on later when the manual assigning starts to feel like a chore. The Filament Manager grows with you - you don't have to adopt the whole thing on day one.

Updated on: 26/06/2026

Was this article helpful?

Thank you!