Customer File Preparation: How to Build a Review Process That Prevents Reprints
The file review process that production print farms use to catch printability issues before a job starts — common file problems, what to check, and how to communicate findings to customers without slowing down the order flow.
The most preventable cause of reprints is a file problem that wasn't caught before the print started. Wall thickness too thin to print reliably, unsupported overhangs that the customer didn't know about, geometry errors that slice incorrectly — these are all fixable before the job runs. A file review process catches them before they cost you material, machine time, and a difficult customer conversation.
What goes wrong with customer files
Non-manifold geometry: a watertight mesh is a mathematical requirement for slicing. Holes in the mesh, duplicate faces, self-intersecting geometry, and reversed normals produce a non-manifold model that slicers repair imperfectly — sometimes correctly, sometimes not. STL files exported from consumer CAD tools or modified in tools without proper boolean operations are common offenders.
Wall thickness below printable minimum: features thinner than 0.4mm (one nozzle width) either don't print or print with gaps. Decorative features — embossed text, thin fins, logo details — are frequently below printable thickness. Customers who designed for SLA or CNC don't always know FDM minimum feature sizes.
Unintended overhangs: geometry that works in CAD doesn't always work in print orientation. Features overhanging more than 45° without support need either support structure (adds post-processing) or reorientation. Customers often don't anticipate this.
Scale errors: a file that was designed in millimeters but exported in a unit that the slicer interprets as inches (or vice versa) produces a part 25.4× larger or smaller than intended. Scale mismatches are more common than they should be, especially with files from international collaborators or old CAD files.
Extremely small features: features below approximately 0.2mm (half a nozzle width) are below the resolution of standard FDM. If these features are functionally important, the customer needs to know before the job runs.
Print orientation implications: some files are oriented in a way that produces unnecessary support, weaker mechanical properties, or worse surface finish than a different orientation. Identifying this before printing and confirming with the customer takes 2 minutes and prevents reprints.
The file review checklist
A structured review before every job:
1. Open in slicer and check for errors Bambu Studio and PrusaSlicer flag non-manifold geometry with a warning. If a mesh repair warning appears, investigate — don't just click through. For minor issues, auto-repair (Bambu Studio's "Fix" button, Meshmixer's repair tool) usually resolves them. For complex non-manifold geometry, return the file to the customer with a description of the issue.
2. Verify scale Check the bounding box dimensions match the customer's specified size. A 50mm × 30mm × 20mm part should slice to those dimensions. If it doesn't, you have a scale problem — catch it before printing.
3. Check minimum wall thickness Enable "thin wall detection" in Bambu Studio. Thin wall warnings flag features that may print poorly. Review flagged areas and assess whether they're critical to the customer's use case.
4. Review overhang areas Enable overhang visualization in the slicer. Flag any overhangs above 45° that would require support and confirm with the customer whether support is acceptable (and who's responsible for post-processing removal).
5. Confirm orientation Is the default print orientation optimal? Consider: surface finish requirements (bottom face has plate texture, top face has best finish), mechanical strength (layer lines perpendicular to stress axis), support minimization, and build plate fit.
6. Check fit in build volume Obvious but missed occasionally. Verify the part fits within your printer's 256×256×256mm build volume in the intended orientation.
Communicating file issues to customers
When you find an issue, communicate it quickly — don't let it sit. The message should:
- Describe what you found specifically
- Explain what it means for the print
- Propose a resolution
- Ask for approval or a corrected file
Example:
Hi [Name] — reviewed the file for your bracket order. Two things to flag:
The text embossed on the side face is 0.2mm thick — below our minimum printable feature size with a 0.4mm nozzle. It will likely not print legibly. Options: increase the emboss depth to 0.5mm+ in your CAD tool, or we can print without it and it just won't appear.
The print orientation puts the mounting holes on the top face — this gives them the cleanest finish and the most accurate diameter. Let me know if you'd prefer a different orientation.
Happy to proceed once you confirm how to handle the text, or send a revised file.
Specific, solution-focused, not alarming. Most customers appreciate the catch — it prevents a reprint and shows you're paying attention.
Building the review into your workflow
File review should happen at order confirmation, not after the job is queued. A job that starts without a review and fails mid-print because of a file issue wastes material and machine time.
For high-volume farms with many incoming files: review in batches at the start of the day, or designate a specific file review step in your job intake process. 5–10 minutes per file is a reasonable budget for standard parts.
For complex engineering parts: allocate more time and involve the customer in orientation and support strategy decisions upfront. The investment prevents the rework conversation later.
Print Hive's job management includes file tracking per job — so your file review notes and any customer communication about file issues are stored with the job record, not lost in email threads. Start free →