About
Built Before WooCommerce Had Rules
Element Stark extensions were developed alongside WooCommerce itself—before there was an extension marketplace, before established patterns, and before most pricing and catalog problems had "standard" solutions.
Where Element Stark started
Element Stark is Lucas Stark, a solo developer who has been building WooCommerce extensions since 2011—the year WooCommerce launched.
At the time there was no extension marketplace and no established way to do dynamic pricing, catalog restrictions, or product add-ons. Store owners needed those features and the solutions didn't exist yet, so the first Element Stark extensions were written to fill the gap. Eight of them are still sold and supported through the official WooCommerce Marketplace today.
What the extensions do
The catalog covers four areas of a WooCommerce store:
Pricing. Dynamic Pricing handles quantity breaks, buy-one-get-one offers, wholesale rates by customer role, and category or cart-total promotions—the discount structures WooCommerce doesn't express on its own.
Product configuration. Gravity Forms Product Add-ons drives a product from a form, so shoppers configure what they're buying and their selections adjust the price and land on the order. Bulk Variation Forms turns a two-attribute variable product into a quantity grid for wholesale ordering.
Merchandising. Catalog Visibility Options decides who sees prices and who can buy. Conditional Content shows targeted messages when your rules match. Recommendation Engine builds recommendations from your store's own view and purchase history.
Customer experience. Variation Swatches and Photos replaces variation dropdowns with colors and images. Wishlists lets customers keep and share more than one list.
They're used by individual store owners, by developers building for clients, and by agencies.
What that means for your store
Writing these extensions alongside early WooCommerce meant learning its internals directly rather than from someone else's implementation. That familiarity with pricing, cart logic, and variation handling is what the extensions are built on.
It matters because a lot of WooCommerce behavior is implicit—tax calculation, coupon stacking, variation availability, how cart totals are assembled. Those details are where a pricing or configuration extension either holds up in a live store or doesn't, and they are the details these extensions are tested against.
How the extensions are maintained
One area per extension
Each extension covers one area of the store. If you need dynamic pricing, that is what you install—not a suite with pricing as one of its features.
Working with WooCommerce
Extensions hook into WooCommerce's own pricing, cart, and checkout logic rather than replacing it, so the rest of your store's stack keeps seeing the data it expects.
Compatibility comes first
New WooCommerce and WordPress releases are the first constraint on any change, not something handled afterwards. These are long-lived products, not launches.
Documented extension points
Hooks and filters are documented so developers and agencies can customize behavior without patching the plugin or forking it.
About Lucas Stark
Lucas has been working with WordPress since 2008 and with WooCommerce since its earliest releases. His specialism is WooCommerce internals—pricing engines, cart and session handling, variation logic, and the hooks and data structures third-party extensions need in order to integrate cleanly.
Element Stark is deliberately a small operation. Every release and every support reply comes from the person who wrote the code, which keeps the feedback loop between a reported problem and a fix short.