Articles on: Get started

Filament workflow for Bambu Lab spools: auto-create and read-and-assign with the AMS

Genuine Bambu Lab spools already carry everything SimplyPrint needs to identify them. Each one has a factory RFID tag that holds the brand, material, color and a unique serial number - and your AMS reads those tags every time you load a spool. That means Bambu is the one brand where your filament inventory can be almost entirely hands-off: drop a real Bambu spool in the AMS and SimplyPrint can create it, identify the exact material, and keep it assigned to the right printer for you.


This article is about the workflow - when to let the AMS do the work, and when to log a spool yourself before it ever goes in. If you run non-Bambu filament (Creality, Anycubic, QIDI, ELEGOO or anything generic), the path is different, so head to the third-party workflow instead. For the bigger picture of static materials, tracked spools and labels, see Filament tracking workflows.


The Filament Manager basics are on every plan, including Free. The AMS auto-sync - loaded spools, and a more accurate remaining weight, both of which are Bambu-only - comes from your hardware, not your plan. Scanning and linking tags yourself uses NFC read and write, which is part of the Filament Manager plan and Pro and up (the Free plan includes a small monthly NFC-write allowance).


A real Bambu Lab spool with its retention rings sitting next to a white NFC reader on a workbench


Table of contents


Why Bambu spools are different

The deciding factor for hands-free filament inventory is simple: does the printer hand SimplyPrint a unique per-spool ID? With Bambu Lab, the answer is yes. Every genuine Bambu spool carries the official RFID tag, the AMS reads it, and that gives SimplyPrint a unique identity it can build a spool record around.


When SimplyPrint has that ID, it uses the Open Filament Database to look up the exact material - not just "PLA", but the specific Bambu product, with its temperatures, density and color. So a spool created from the AMS arrives fully described, with no typing on your part.


Bambu spools also report a more accurate remaining weight. The AMS estimates how much filament is left from the tag, and SimplyPrint can sync that value back to the spool record - a closer reading than gcode-based tracking alone. It's a Bambu-specific extra: other systems sync which spools are loaded, but not a precise remaining weight.


There's a catch to keep in mind: this all relies on genuine Bambu spools. A plain or third-party spool in a Bambu AMS reports no usable ID, so it syncs as material and color only. More on that below.


Path 1: let the AMS auto-create and auto-assign

This is the hands-off path, and for most Bambu users it's all you need.


Put a genuine Bambu spool in the AMS. SimplyPrint reads the tag, creates the spool in your inventory, identifies the exact material through the Open Filament Database, and assigns it to that printer. Move the spool to a different slot or a different AMS unit and SimplyPrint follows along - it unassigns it from the old slot and re-assigns it to the new one, because it recognizes the same tag serial wherever it turns up.


The Bambu X1-Carbon and its mounted AMS unit that read genuine Bambu spools automatically


You don't have to do anything to set this up beyond connecting the printer. Once a Bambu spool exists in SimplyPrint, its usage is deducted automatically whenever a print runs through SimplyPrint, and you get a runout warning before a print starts if the assigned spool doesn't have enough left to finish. That warning only exists because the spool is tracked and assigned - which, on the Bambu path, happens for free.


For the full picture of how loaded spools map to slots and sync across an AMS, see Multi-material printing: mapping and syncing your AMS, ACE or CFS. The deep reference on which systems auto-create and why is Automatic spool creation when syncing materials.


Path 2: pre-create your stock, then read-and-assign

Path 1 only creates a spool the first time you actually use it. Sometimes you want the spool in your inventory before that - to log a delivery, see your full stock at a glance, or track a sealed spool you bought but haven't opened. That's what read-and-assign is for.


The workflow is:

  1. Create the spool in SimplyPrint by hand (pick the brand, material and color, or buy in bulk when you unbox a multi-pack).
  2. Read-and-assign it: scan the spool's existing factory NFC tags to link them to the record you just created.


The Read and Assign workflow on mobile, where you scan a Bambu spool's tags to link them to its record


Why link the tags instead of just letting the AMS create the spool later? Because if you pre-create five spools and then load them, the AMS sees five tags it doesn't recognize and creates five more - now you have ten records, not five. Linking the factory tags when you pre-create tells SimplyPrint "this physical spool is this record", so the first AMS insert matches it instead of duplicating it.


This is the difference between Bambu and every other brand. Bambu is read-and-assign: you link the spool's existing factory tags to its digital twin. You never write anything - SimplyPrint has no write spec for Bambu tags, so it can only read them. (For non-Bambu brands the flow is write-and-assign: you create the spool, then write its identity onto a blank tag yourself. That's the whole of the third-party workflow.)


The two tags on every Bambu spool

Here's the part people miss. A Bambu spool doesn't have one RFID tag - it has two, one sticker on each side, and each tag has its own unique serial number.


That second tag isn't redundant. The unique serial is exactly what lets SimplyPrint tell two otherwise-identical spools apart - two reels of the same Bambu PLA Basic in the same color are different spools because their tag serials differ. So when you link a Bambu spool by hand, you scan both sides, so both tag IDs get recorded against the same digital twin.


The mobile NFC assignment step showing the first of two tags scanned with a green checkmark


After both sides are linked, the first time that spool goes into the AMS, SimplyPrint matches it on its own - it already knows both serials, so it recognizes the spool no matter which way round it sits.


What Bambu can and cannot do

Bambu's tags are a closed, encrypted system. That shapes two things worth being clear about.


Bambu's tags hold real data, but third-party readers can't decode it - only the tag's unique ID is readable. SimplyPrint uses that ID to identify and track the spool, which is all the Bambu path needs. There is no public write spec, so SimplyPrint can read and link Bambu tags but never write to them.


The flip side is that a Bambu AMS will not read a third-party NFC tag. Put a non-Bambu spool - even one you've tagged yourself in another brand's format - into a Bambu AMS and it won't be recognized, because Bambu's system isn't open to outside tags. That spool syncs as material and color only, with no per-spool identity and no weight sync.


So the rule of thumb is:


Bambu spool in a Bambu AMS = full hands-off inventory (auto-create, auto-assign, weight sync). Anything else in a Bambu AMS = material and color only.


If you run third-party filament through a Bambu machine and still want per-spool tracking, you can't lean on the AMS for it - you'd track those spools with labels or by scanning them in another way. The third-party filament workflow covers the options, and labels are covered under Filament tracking workflows.


Slicer multi-material settings with a Bambu PLA Basic and a generic PLA loaded, showing how AMS slots map to materials


Reading Bambu tags from your phone or desktop

Most of the time the AMS does the reading for you. You only need to read a tag yourself for the read-and-assign step, when linking a spool you pre-created. A few ways to do that:


The NFC method picker offering the SimplyPrint NFC Scanner and the Bambu NFC Reader


  • The mobile app is the easiest, and reading a Bambu spool works on both iOS and Android. Hold the spool near the phone and scan each side.
  • A desktop USB reader can read tag IDs for linking. For full read support across tag types there's the NFC Agent desktop app.
  • Web NFC works in some Android browsers, but it only handles NDEF tags, so it cannot read Bambu's encrypted tags - use the mobile app or a desktop reader for Bambu.


Reading a Bambu spool works on an iPhone - good to know if your bench setup is a phone rather than a desktop reader. The per-brand device-support details (which brands need Android or a desktop reader, which work on iOS, which don't do Web NFC) vary a lot, and they live in the third-party workflow and the NFC overview.


For how spools get assigned and the weight-sync detail, the deep references are Assigning filament spools to printers and How does SimplyPrint track filament usage?.



Updated on: 26/06/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!