Design Library and Template Management in CraftOps

A busy fabrication shop accumulates design files fast. Between customer uploads, internal prototypes, revised iterations, and one-off test prints, it does not take long before your team is hunting through nested folders, Slack threads, and email attachments trying to find the right version of the right file. CraftOps replaces that chaos with a centralized design library that keeps every file organized, versioned, and instantly searchable.

The design library is not just a file dump. It is a structured repository that connects each design to the jobs, customers, and machines it has been used with. When a returning customer asks you to reprint the bracket you made six months ago, you find it in seconds rather than digging through archived orders. And when your designer iterates on a model, every previous version is preserved with a clear revision history.

Organized Storage with Tags and Categories

CraftOps structures the design library around a flexible tagging and categorization system. Every file can be assigned to one or more categories, such as "enclosures," "mechanical parts," "decorative," or any custom label your shop defines. Tags add a second layer of granularity: material type, machine compatibility, customer name, project code, or difficulty level. Because tags are freeform, your team can develop a vocabulary that matches your specific workflow.

The library view supports filtering by any combination of tags and categories, so an operator looking for all PETG-compatible enclosure designs can narrow the results in two clicks. A thumbnail preview accompanies each file, generated automatically from the 3D geometry, so visual scanning is fast even in a library containing thousands of designs. Search also indexes file names, descriptions, and metadata fields, meaning a quick keyword search surfaces results without needing to remember exact naming conventions.

Folders still exist for shops that prefer hierarchical organization, but they work alongside tags rather than replacing them. A single design can live in a folder structure for project-based navigation while simultaneously being tagged for cross-project discovery. This hybrid approach means you never have to choose between the two organizational philosophies.

Version Control and Revision History

Design iteration is a constant in fabrication work. A customer approves a prototype, then requests a thicker wall. Your designer modifies the part, and suddenly two files exist with nearly identical names. Multiply this across dozens of active projects and version confusion becomes a real production risk, where the wrong revision gets printed and materials are wasted.

CraftOps solves this with built-in version control. When a new revision of a design is uploaded, it is linked to the original file as a new version rather than a separate entry. The library displays the latest version by default, but any team member can expand the version history to see every iteration, who uploaded it, when it was added, and any notes attached to the change. Rolling back to a previous version is a single click, and the rollback itself is recorded in the history so nothing is ever silently lost.

Version control also integrates with the job system. If a job was completed using version 2 of a design but the library now holds version 4, the job record still references the exact file that was printed. This traceability is essential for shops doing contract work or producing safety-critical parts where you need to prove exactly which geometry was fabricated.

Tip: Establish a naming convention early, but do not rely on it exclusively. Use the description field on each design to note what changed between versions. When your team grows, those notes become invaluable for onboarding new members who were not part of the original design decisions.

Team Sharing and Customer Uploads

Collaboration is central to the design library. Every file has granular permission settings: a design can be visible to the entire shop, restricted to specific team roles, or locked so that only the original uploader can modify it. This flexibility matters when you have operators who need to access files for printing but should not accidentally overwrite a designer's work in progress.

For shops that accept customer-submitted files, CraftOps provides a secure upload portal that feeds directly into the library. When a customer uploads an STL through the customer portal or a shared upload link, the file appears in a designated intake area. Your team reviews it, runs the file analysis checks, and either approves it into the main library or sends feedback to the customer requesting corrections. This intake workflow keeps unvetted files separate from your production-ready library while still providing a smooth experience for the customer.

Template reuse is another powerful feature. If your shop produces standard items, such as a particular phone case model, a common jig, or a popular decorative piece, you can mark any design as a template. Templates appear in a dedicated section of the library and can be cloned into new jobs with a single action. The clone inherits the design file, default material settings, and recommended machine profile, so your operator is not configuring the same parameters from scratch every time a repeat order comes in.

What's Next

A well-organized design library is the foundation that every other CraftOps workflow builds on. Files flow from the library into the production scheduler, link to invoices for cost tracking, and surface in the customer portal for reorder convenience. In our next post, we will look at how CraftOps handles shop production scheduling, turning your library of ready-to-print designs into a coordinated calendar of machine assignments and deadline-driven job queues. If your shop is still managing files across scattered drives and cloud folders, CraftOps brings everything under one roof with the structure and history your team needs to move fast without losing track.