Choosing printers for short production runs: batches and traceability

What a short run changes about the buying decision

A scenario to prepare for: two parts in a run of thirty differ. To investigate what changed, record each production’s spool or cartridge, slicer profile, CAD revision and printer. Compare the ways to preserve that information before buying. This record-keeping criterion complements quality, speed and capacity requirements; its importance depends on the project.

Three questions capture the criterion. Does the machine or its software keep a job log you can consult afterward? Can that log be exported out of the platform so you can archive it with your own records? And most importantly, what is missing from that log that you will have to write down yourself? The professional 3D printer guide covers the broader choice. This page focuses on the documentation side.

The rest of the article leans on Formlabs Dashboard because its documentation spells out exactly what gets recorded. That is not a brand recommendation. Apply the same reading grid to any ecosystem you are considering and check each point against that manufacturer's own documentation.

Job history: what a manufacturer platform really records

According to Formlabs documentation, Dashboard starts receiving data once a printer is registered to an account, Dashboard logging is enabled, and the printer has internet access over Wi-Fi or Ethernet. A print is logged each time one is started while the printer is online, including aborted prints. The same documentation states that to see data for a specific print and accurate material usage, the printer must be able to reach the internet at the moment the print starts.

For each past print, the Formlabs page says you can view an enlarged render of the model along with the start date and time, duration, resolution, layer count and volume. Prints can be searched by the job name saved in PreForm, and an Export Data button downloads a CSV of all past prints on registered printers. For a short run, that CSV is the artifact you archive with every batch.

One detail deserves attention. The documentation states that the original FORM file can only be redownloaded for prints uploaded to a Group Queue, not for files sent directly to an individual printer. If you plan to retrieve the exact file behind each job later, how you submit the job becomes part of your procedure rather than an afterthought.

Batch changes: linking documented data to your own records

Formlabs says the Dashboard Statistics page shows material usage and activity over a selected time range for all registered printers or one printer. This lets you consult the described data by machine and period. For your batch workflow, separately check how the selected configuration retains the material lot, part identifier and CAD revision: the fields listed on these two pages do not establish an automatic association with each part.

One proposed method is to assign each run a reference and include it in the PreForm job name, which the history supports searching. Link that reference to your own record: customer or project, file revision and cartridge actually used. Check the exported CSV’s contents before relying on a particular column, and preserve the mapping needed for your batch. This is an organizational method, not an additional Dashboard feature claim.

The success or failure vote, a thumbs up or down on the printer screen or in Dashboard, is described by Formlabs as user feedback. It lets you filter history by outcome, but it is neither an automatic dimensional inspection nor a mechanical qualification. A high success rate in your statistics does not demonstrate that a batch conforms. It reflects what operators declared.

Building your batch record outside the machine

Since the platform covers only part of the story, the batch record lives alongside it, in a spreadsheet or a versioned document. For each run, adapt this proposed worksheet: the batch reference you placed in the job name, the exact file revision and its hash if you compute one, the identifier of the printer used, the material type and the lot number read off the cartridge or spool packaging, post-processing steps with their durations, the result of whatever inspection you actually performed, and any change since the previous batch.

This proposed record is not a traceability certification. Define fields, responsibilities and checks suited to your activity. Mark missing information as unknown instead of inventing an approximate value. The guide to organizing CAD revisions and printing profiles helps name and store the files referenced in the record.

Archive the exported Dashboard CSV together with the record when you close each batch. If a customer or colleague later shows up holding a part, you have both halves: what the machine logged and what you added. The same logic applies to purchased model licenses, covered in the page on archiving model licenses and purchase evidence.

Sharing access and responsibility in the workshop

As soon as two people start prints, "who launched this job?" becomes a traceability question. According to Formlabs documentation, multiple users can share the same printers through the Share function, whether or not the printers are organized into groups, and a printer can belong to only one Printer Group. Invitations go out by email address with a Member or Admin level, and only admins can change a user from Member to Admin or remove access.

The same documentation notes that logging in to PreForm with a Formlabs account links print jobs to that account, which later lets you filter history to show only your own prints. For a short run, that means an identified operator can pull up their batches without sorting through everyone else's. These are access settings, not an authorization audit. They do not replace a written rule about who may edit a profile or switch material mid-run.

On the data side, Formlabs states that model geometries stay on your computer or printer and are never shared without explicit consent, and that sharing data to Dashboard is a separate permission from PreForm's own data collection option. That is a manufacturer statement, to be read alongside its privacy policy. If internet access at print start is a constraint, consult the offline 3D printers guide and check each model’s local logging options; the Dashboard condition does not describe all offline printers.

Spare parts and restart after a stoppage: the matrix to fill in

Prepare the situations to record after a stoppage: resuming on another machine, swapping a wear part halfway through the batch, a half-used cartridge left waiting. Before you buy, draw up a restart matrix with three columns: the possible event, what you will need to note in the batch record, and the part or action required to get going again. Fill it from the manufacturer's documentation, not from assumptions.

For each candidate machine, check its documentation for which parts are sold separately, how they are referenced, and what availability the manufacturer states. A printer whose consumables and wear parts carry clear part numbers makes the "part replaced" line of your batch record much easier to fill in honestly. The pages on repairable 3D printers and spare parts kits give you the list of questions to ask before purchase.

Two closing reminders. Dashboard logs a job only if the printer was online at start, so a gap in the history does not prove a gap in activity; use your own dated record for events it does not capture. And none of these features guarantees profitability. The startup budget tool is there to cost out your own setup, without any revenue projection.

Sources and limits

• Sharing and accessing print data with Dashboard | Formlabs
• Viewing material and print statistics in Dashboard | Formlabs

We organize manufacturer and community documentation; we have not measured these products ourselves. The manual for your exact model takes precedence over general guidance.