- Bruxel.AI Blog
- Use case: a tender with datasheets, certificates and artwork in one package
Use case: a tender with datasheets, certificates and artwork in one package
By Manuel Mattar4 min read
In short
This is an example scenario. A manufacturer uploads datasheets, certificates and packaging artwork next to each product, approves artwork versions, marks which certificates expire and, when the tender arrives, requests a ZIP package with the file names the call requires and an index with the fingerprint of every file.
This case is an example, not a customer: an imaginary company and a made-up tender to show how Bruxel's documents, their versions, their expiry dates and file packages are used. The catalog numbers belong to the scenario.
The situation
A manufacturer of valves and fittings has 400 products. A public agency issues a tender and asks, for each line item, for three things: the datasheet in PDF, the current standards compliance certificate and the packaging artwork. It also demands an order: one folder per SKU and a file name that says what it is and which version.
Today those files live in emails, in a shared folder with names like "datasheet final v3 good.pdf" and on the computer of whoever designed the packaging. Nobody knows for sure which certificate is still valid or which artwork is the approved one. Putting the delivery together by hand takes days, and there is always the doubt of having sent an old version.
Step 1: define the file types
An administrator goes to Media → File types and creates the organization's types, on top of the default ones (Datasheet, Manual, Certificate, Drawing…):
- Standards certificate, with validity: when one is uploaded, the tab asks for the expiry date and marks it as "Valid", "Expiring soon" or "Expired".
- Packaging artwork, with "Requires approval" and, under "Who approves", the administrator role. Each new version then stays in "Draft" and products keep the approved one.
Step 2: upload the files to each product
On the product page, the "Files" tab offers "Upload document" or "From the library". Bruxel recognizes each file by what it is, not by its name, and gives it a starting type that can be changed under "Type". The same PDF can be on several products: the datasheet for a whole line is uploaded once.
Every document goes through a virus scan before it can be downloaded, never has a public address and is downloaded through a link that lasts 5 minutes. If the scan finds a threat, the file goes to quarantine and is removed from its products.
Step 3: approve the artwork, version by version
The designer uploads a new version of a box's artwork. It stays in "Draft" and he sends it to review from "Versions". The administrator gets a notification that opens the file. If it is right, "Approve" makes it the current one: the products that have it move to it and the previous one becomes "Superseded". If not, "Reject" asks for a reason, which stays in that version's comments and reaches whoever sent it.
To share the work, the product lead uses "Assign review" on the file page: to whom, by when and a note. The person sees it on their home page, under "Files to review".
Step 4: watch what expires
Certificates expire. Besides the validity of the file type, the team has in Catalog → Attributes a date attribute, "Registration expiry", marked as "Is an expiry" with a 60-day notice. Every morning Bruxel checks those dates and notifies in the bell when one enters its notice window and when it expires, with the catalog already filtered. In the catalog, the "Expires in 30, 60 or 90 days or less" filter says what to renew before the delivery date.
In Reports, the "Files by status" report (Images and media family) says for each file whether it complies, whether it expired, whether it is missing the date or the approval, and who is due to review it.
Step 5: the tender package
In Media → Packages, an administrator saves a template: which types it includes (datasheet, certificate and artwork), whether the current version or the latest approved one goes in, which images, and what each file is called inside the ZIP. For this call they use {sku}/{type}_v{version}.{ext}, which gives one folder per SKU with names like datasheet_v2.pdf, and they tick the index option.
Then, in the catalog, they filter the 180 line items of the tender and use "File package with the filtered ones". "Calculate" says how many products and files it includes and what is left out: if an artwork has no approved version, it shows before requesting. Expired items are not removed by the package; that is why the team already checked the filter and the report from step 4. With "Request package", the ZIP is built outside Bruxel and the bell notifies when it is ready.
The ZIP includes indice.csv and indice.pdf: each file's name, its SKU, type, version, date, who approved it and when, its size and its sha256, the fingerprint that proves the file is exactly that one.
What gets solved and what does not
Solved: one place for each product's documents, artwork that never reaches a delivery without approval, certificates with their dates in sight and an orderly package with a verifiable index.
Not everything is solved:
- The ZIP lasts 7 days. The files stay in the library and the package can be requested again.
- There are limits: up to 5,000 products, 10,000 files and 10 GB per package.
- Expiry notices go to the bell, not to email.
- The submission is still yours: Bruxel uploads nothing to the tender portal.
The technical documents and expiry alerts guides have the details. The files and reports pages show where each piece fits.
Frequently asked questions
Can a draft slip into the package?
No. A draft never goes into a package. Depending on the template, the current version or the latest approved one goes in, and only files with a clean virus scan are included.
How do I check that the file they received is the one I sent?
The package index includes the sha256 of every file, and the screen shows the one for the whole ZIP. Whoever receives it can compute the fingerprint and compare.
Does Bruxel submit the bid on the tender portal?
No. Bruxel builds the ZIP and keeps it for 7 days for you to download. Uploading it to the portal or sending it to the buyer is still your team's step.
Sources
About the author
Manuel Mattar
Founder of Bruxel.AI
In 2014 he founded Wolf Sellers, an e-commerce agency in Mexico City, and later Bruxel.AI, the AI-powered PIM.
See all posts by Manuel MattarTry it with your catalog
Create your free account and try Bruxel with your own products using the welcome credits.
Keep reading
· 4 min read
Use case: ecommerce, merchandising and master data in a staged workflow
A step-by-step example: three teams and an ERP hand off each product through a staged flow in Bruxel, with tasks, comments, approval and a board.
· 4 min read
Use case: 500 supplier products a month without the spreadsheet ping-pong
An example scenario: a retailer receives 500 new products a month from 40 suppliers. How it handles them in Bruxel, step by step, and what is still open.
· 4 min read
Catalog reports in Bruxel: from data to decision without building sheets
How Reports and Analytics work in Bruxel: periods, filters, favorites, scheduled sends, catalog health and the PDF quality report.