E-commerce Platform
Custom Venom E-commerce Platform — Middle East
A first-of-its-kind e-commerce platform built for a scientifically classified product domain — where standard WooCommerce structures were insufficient and the product architecture had to be engineered from first principles.
One platform. Multiple species. Custom classification fields. Built on WordPress and WooCommerce — with a custom theme engineered from the ground up.
Client
Middle East-based venom supplier (anonymised)
Sector
Specialist Life Sciences Commerce · Middle East
Scale
Single-vendor e-commerce platform · scientific product catalogue
Technology
WordPress · WooCommerce · Custom Theme
Services
Custom Theme Development · WooCommerce Configuration · Product Architecture · UI/UX Design
Status
Delivered
The Starting Point
A Middle East-based venom supplier had an established offline business — sourcing, processing, and supplying venom products to specialist buyers — with no digital sales infrastructure to match it. The client operated in a domain with no precedent for structured online commerce: venom products are not sold through general marketplaces, and no existing e-commerce template or platform came close to addressing the classification complexity the catalogue required.
Each listing carried scientific attributes — species, genus, class, biological origin — that were essential to buyer decision-making. Without those fields, the platform would be functionally useless to its target audience. Standard WooCommerce product fields offered name, SKU, price, and description. The gap between what standard platforms offered and what the domain required defined the entire brief.
Attempting to force this catalogue into a standard e-commerce structure would have resulted in a platform that appeared complete but failed at the level of product discovery — making it unusable for its intended audience.
The practical problem was structural: standard e-commerce product schemas are built for consumer goods, not scientific inventory. Selling venom online required building the data model first, and the platform second.
The Brief
The client required a fully functional e-commerce platform that could:
The specific requirements:
Accept and display scientifically classified products with species, genus, class, and additional biological attributes per listing
Present complex scientific data clearly to non-specialist buyers without sacrificing accuracy
Scale to accommodate a growing catalogue of classified items without requiring structural redevelopment
Operate as a secure, transactional platform with standard e-commerce functionality — cart, checkout, order management
Reflect the specialist nature of the business through design — not a generic storefront aesthetic
The complexity of the problem was not in building an e-commerce site — it was in defining a product structure that could represent scientific data accurately while remaining usable in a commercial interface. There was no existing template, plugin, or reference implementation for this type of catalogue.
What We Did
The build was structured in four stages, each dependent on the decisions made in the previous one. The product architecture had to be resolved before any design work began — and the design had to be validated before development. There was no viable shortcut — the sequence was the solution.
Custom Product Architecture — Building the Data Model
Before a single page was designed, we defined the product data model. WooCommerce’s default product schema — name, SKU, description, price, category — was extended with a structured set of custom fields covering the scientific attributes each product required: species, genus, class, and additional biological classifications specific to the client’s catalogue.
The architecture was built for extensibility. New species types, classification levels, or attribute sets could be added to the model without restructuring the database or redeveloping product templates. The taxonomy was treated as infrastructure, not content.
The architecture was also designed to support controlled access and regulatory constraints specific to the product category, ensuring the platform could adapt to compliance requirements as the business scaled.
Taxonomy-Based Filtering and Search
Buyers on a specialist venom platform do not search by product name. They search by what the product is — its biological origin, its classification, its species. Standard WooCommerce search and filtering operates on product names, categories, and tags. That was not sufficient.
We implemented filtering and search that operated on the custom scientific fields — allowing buyers to narrow by genus, class, or species type directly. Product discovery was rebuilt around how the audience actually navigates a scientific catalogue, not how a general e-commerce system expects them to.
Custom Theme — Design for a Scientific Domain
No existing WordPress or WooCommerce theme was suitable. The platform required product page layouts that could present scientific classification data legibly — structured, scannable, and credible — without the product page becoming a document. A custom theme was designed and developed from scratch.
The interface prioritised clarity: scientific attributes surfaced prominently, product descriptions structured for a specialist reader, and a visual language that communicated the domain’s technical credibility without alienating buyers less familiar with the taxonomy.
WooCommerce Configuration and Secure Transactions
Standard WooCommerce e-commerce functionality — cart, checkout, payment processing, order management — was configured alongside the custom product architecture. The platform operated as a fully transactional store from launch: buyers could browse by classification, add to cart, and complete purchases through a secure checkout flow
Access controls were configured to support restricted catalogue visibility for verified buyers — a consideration appropriate to the product category and the client’s regulatory environment.
The result was not just a working platform, but a system where the product structure, discovery logic, and transaction flow were aligned — enabling the business to scale without rethinking its core architecture.
The Technical Challenge
The core challenge was not WooCommerce configuration — it was extending WooCommerce’s product schema in a way that remained maintainable, scalable, and seamlessly integrated with the filtering and search layer.
Custom product fields and WooCommerce
WooCommerce stores product data in WordPress post meta. Custom scientific fields were implemented as structured post meta with consistent field keys, validated input types, and display logic built into the custom theme templates — not as freeform text appended to descriptions. This distinction matters for filtering: meta-based fields can be queried; description text cannot.
Taxonomy integration with WooCommerce filtering
WordPress taxonomies and WooCommerce product attributes are related but distinct systems. Getting biological classification fields to behave as filterable attributes — appearing in the filter widget, producing correct product query results, and integrating with WooCommerce’s layered navigation — required careful alignment between the data model and WooCommerce’s attribute architecture.
Custom theme without a base framework
Building from scratch rather than customising an existing theme gave full control over the product page layout and scientific data presentation — but also meant every template, hook, and WooCommerce override had to be written and tested. There was no inherited template debt, and no visual compromise forced by a base theme’s structure.
Results
A purpose-built e-commerce platform launched for a product category with no prior structured online sales model — enabling classified product discovery, scalable catalogue growth, and a transition from manual, relationship-based sales to a structured digital channel.
Product data
Offline catalogue — no structured digital format
Custom WooCommerce fields for species, genus, class, and biological attributes per product
Sales channel
Offline and fragmented — no unified e-commerce
Single managed platform — structured online sales from day one
Customer experience
No self-serve product discovery
Taxonomy-based filtering and search — buyers locate products by biological classification
Catalogue scalability
No scalable structure
Extensible product architecture — new species and classifications added without redevelopment
Platform
None
WordPress + WooCommerce on a purpose-built custom theme aligned to the domain
loreD handled our email migration when our infrastructure was in a complicated state. They understood the multi-domain complexity, moved everyone across cleanly, and the system has been solid ever since. When we needed to upgrade the infrastructure, there was no question about who to call
Anil Thomas
Raidco Kerala Limited
What This Engagement Demonstrates
The venom platform demonstrates loreD’s ability to scope and build e-commerce solutions where the product domain itself is the primary engineering challenge — not the platform configuration.
Domain-driven architecture: the platform was shaped by the structure of the product, not by the limitations of the platform.
Product architecture before platform: the data model was defined before any design or development began. Getting the scientific field structure right determined everything that followed.
WooCommerce extended, not replaced: the platform used WooCommerce as its transactional foundation and extended it — custom fields, taxonomy-integrated filtering, bespoke templates — without introducing unnecessary complexity through third-party plugins.
Custom theme as a requirement, not a preference: the domain’s data complexity made a custom theme non-negotiable. Existing frameworks would have constrained the product page layout in ways that compromised the scientific data presentation.
Specialist domain, generalist platform: the challenge was applying a generalist platform — WordPress and WooCommerce — to a highly specialist domain without losing the scientific rigour the buyer audience required.
Scalable by design: the product architecture was built to accommodate catalogue growth without redevelopment. New species and classification types are added as data, not as structural changes.
Building E-commerce for a Specialist Domain?
If your product catalogue requires data structures, filtering logic, or user experience decisions that standard templates cannot support, the platform configuration is the starting point — not the solution. Specialist commerce requires a build that begins with the domain, not the theme.