Hoops stores uploaded files against the Customer, allowing them to be reused across future SalesDocs and Jobs without needing to upload them again.

This is particularly useful for artwork, logos, brand guidelines, embroidery files, purchase specifications, and other documents that are used repeatedly for the same customer.

Instead of creating duplicate files, you can simply associate an existing file or proof with the new SalesDoc or Job.

Whenever you upload a file to a SalesDoc or Job, Hoops also stores that file against the Customer record.

This creates a central file library for each customer, making it easy to find previously uploaded artwork and documents for future work.

Over time, this becomes a valuable repository of customer assets that can be reused whenever needed.

When adding files to a SalesDoc or Job, you can choose to associate an existing customer file instead of uploading a new one.

This allows you to quickly attach:

Because the original file is reused, there is no need to maintain multiple copies of the same document.

Previously uploaded proofs can also be associated with new Jobs where appropriate.

This is especially useful for repeat orders where the customer has already approved artwork that will be used again.

Rather than uploading the artwork a second time, simply associate the existing proof with the new Job.

If changes are required, a new proof version can be uploaded and sent through the normal proof approval process.

Associating existing files helps your team:

It also helps ensure everyone is working from the same artwork and supporting documentation across every SalesDoc and Job.

Whenever you're creating a SalesDoc or Job for an existing customer, check whether the required artwork or files have already been uploaded before adding new files.

Reusing existing files keeps your customer library clean, reduces storage duplication, and makes repeat work significantly faster.

If artwork has changed since the previous order, upload the revised version and, if customer approval is required, send it through the Proof Portal as a new proof.