Labonyx Product Catalog Website

Summary. The public website and product catalogue for Labonyx, a scientific laboratory supplies company, live at labonyx.com. It is a fast, bilingual static site built with Astro, with small React islands for fuzzy search, variant filtering, and a quote flow. The part worth telling is the content pipeline: the catalogue used to live in Airtable, but as it grew the pricing stopped making sense, so I moved it onto a Google Sheets and Drive backend the company already owned and pulls it in at build time. The result is free, fully configurable, and edited from the same desktop ERP I built.

A static catalogue, built for speed and search

The site is a pure catalogue: categories, products, and their variants down to the SKU, with technical specs, image galleries, an information hub, and a quote and contact flow. It is fully static: every page is prebuilt HTML that loads fast and costs almost nothing to serve. There is no backend, no login, and no database to attack at runtime. Where the page needs to be interactive, a small React island hydrates just that part: a fuzzy search across products and variants, the filterable variant table, and the quote modal. It is bilingual throughout, Turkish at the root and English under /en/, with a localized sitemap.

Off Airtable, onto a backend the company owns

The catalogue started on Airtable, which was convenient until it grew: the pricing did not fit a catalogue this size. So I moved the data onto the Google Sheets and Drive backend the company already used for everything else, and built a small pipeline that pulls it in when the site is built. No runtime database, no per-seat catalogue fees, and full control over the data. Content is edited in the desktop ERP rather than in a developer’s spreadsheet, so a non-technical person owns the catalogue end to end.

A pipeline that only does the work it has to

The build is careful about images, which is where catalogue sites usually get slow. Each image is cached by its Drive file identifier and size, so a rebuild only downloads the ones that actually changed, then converts them to WebP. Images are matched to products by a filename convention rather than by links stored in the data, so swapping a product photo is just uploading a file, which the ERP does automatically. Everything else, the colours, the company details, the contact information, even the link to the dealer portal, comes from a settings sheet, so the whole site is reconfigurable without touching code.

The catalogue content, every product, variant, and image, is edited in the Labonyx internal ERP I built, which writes to the same sheets and Drive folders this site reads at build time. The website, the dealer portal, and the ERP all draw on one source of data the company fully owns.