A scientific catalog is a data model, not a pile of PDFs.
Scientists search by target, species, conjugate, and application. If those facts live only in a spreadsheet or a spec-sheet PDF, the catalog cannot answer the question they typed.
What usually goes wrong
- Hundreds of SKUs sit in a spreadsheet. The website shows a short list of featured products and a contact form.
- Specifications are PDF attachments. A buyer cannot compare two products without downloading both.
- Filters follow the company's internal categories, not the way a scientist searches: target, species, conjugate, application.
- Related products and documents fall out of date because updating one SKU means editing a page by hand.
What you get
A catalog your team can import into and edit. The attributes come from how your buyers already search.
-
An attribute model
The fields a product must carry, agreed before templates exist. Typical fields include target, species, conjugate, application, host, clone, size, and documents.
-
A filterable listing
A catalog index that narrows by those attributes, with a stable URL for each filter state you choose to publish.
-
A product template
Specs, documents, and related products on one record, so a protocol PDF stays attached to the SKU it describes.
-
An import path and training
A route from your sheet into the catalog, a QA pass on the imported records, and training for the people who will add the next SKU.
How the catalog gets built
-
#001
Attributes first
We read your sheet and a handful of real buyer questions, then lock the field list. Design does not start from a homepage comp.
-
#002
Templates
Listing and product templates on staging, using a sample of real SKUs, including ones with missing documents.
-
#003
Import and QA
The sheet comes in. We check counts, empty required fields, and documents that did not attach.
-
#004
Filters and editor training
Filters go live against the imported set. Editors learn how to add a product without breaking the model.
What a typical project looks like
There is no product-catalog client in the published work yet. A typical project looks like this: a sheet of reagents or kits becomes a filterable catalog. Each product page shows the attributes a scientist filters on, the specifications, the protocol or spec sheet, and related products. The marketing site around the catalog, if you need one, is a separate set of pages.
This work is scoped as Authority, because it is a catalog structure, an import, and ongoing support for the data. A device site whose main need is a labeled IFU library, rather than SKU filters, is medical device website design.
Related
- Medical device website design is for product families, indications, and document libraries.
- Life sciences website development is the underlying build: staging, roles, and code your company owns.
Start with a 15-minute call
A sample of the sheet is enough. We'll tell you which columns can become filters, which are missing, and whether Authority is the right package.
Book a 15-minute website audit