B2B medical catalogue platform
A client implementation of a structured, multilingual product catalogue and content platform for specialised B2B products.
Delivered for a client. Public naming and screenshots require permission.
Problem
B2B buyers and sales teams need structured product data — categories, attributes, filters and detail pages — not a brochure site that engineering must edit for every change.
Users
Client editors, sales teams and B2B buyers. The public case does not identify the client.
Current solution
A maintainable catalogue and content platform: pages, product records, coordinated filters and detail views, with multilingual content where the implementation supports it.
Workflow
Editors maintain products and pages in the CMS. Buyers browse catalogue and detail views. Enquiry paths exist where implemented. Public screenshots are withheld until permission is documented.
01
Editors structure categories and product records
02
Catalogue listing applies coordinated filters
03
Product detail presents specifications and media
04
Visitors request contact or further information
Product architecture · Not a live product screenshot
Catalogue platform without client identity
CMS
Editors manage pages, products, media and locales.
Catalogue
Listings, categories and filters over structured product records.
Product detail
Specifications and media for a single SKU or device family.
Enquiry
Contact or request flow for B2B buyers, where implemented.
What exists today
Source implementations exist as client Next.js / Payload catalogue platforms. They are not published here with names, logos or UI captures.
Webbylon can deliver a maintainable B2B catalogue and CMS instead of a static marketing stack. Related independent multilingual medical-catalogue work exists in the same family.
Next milestone
Public naming, screenshots and a written contribution split require client permission. Those facts are not invented on this page.
Permissioned, anonymised or named case assets — only after written clearance.
No public production URL.
Evidence
- Client-platform source includes homepage, catalogue, product detail, CMS admin and API routes
- A second independent multilingual medical-products site exists in the same technical family
- Publication of names and UI is withheld on purpose
Commercial opportunity
Repeatable vertical platform work for specialised manufacturers that outgrow brochure websites. No contract values are published.
Reusable capabilities
- Product information as structured records
- Category and filter models
- Multilingual catalogue publishing
- CMS operations for non-engineering editors
Current limitations
- Confidential case: no client identity on this site
- No public screenshots
- Localization depth varies by implementation and is not over-claimed
What this shows about Webbylon
Webbylon can implement specialised B2B catalogues as maintainable platforms, not one-off page builds.
Investment relevance
Shows paid-shaped delivery capability and a reusable catalogue pattern that can become a productised offer.
Anonymised on purpose. Do not display client names, logos or operational data until permission is confirmed in writing.
Implementation note
- Next.js application with Payload CMS and a PostgreSQL-backed content model
Discuss this direction
The next step is a short conversation about the problem, the maturity, and the next credible milestone.