FEATURES

Can we build this specific thing?

Features are searchable, buildable pieces. Each one has a client-facing sentence, a concrete interface, a parent system and what we need from you to start.

Message us

Grouped by parent system. After metaobjects are seeded in Admin, each title below should resolve at /pages/features/{handle}.

Under Storefronts

Deposits - Customers pay a deposit on the page for builds, pre-orders or booked experiences.

Restock notifications - Customers leave an email for a size or SKU and get notified when it is back.

Product metafields and filtering - Shoppers filter by the attributes that actually matter for your catalogue.

Multi-market selling - One store serves more than one country or currency with the right catalogue path.

Subscriptions - Customers subscribe to replenishment without a separate ordering habit.

Shop by brand - Customers browse an A to Z brand index that matches your real vendor names.

Under Configurators

Product configurator - Customers build their own spec on the product page and the cart reflects exactly what they chose. Live demo: /pages/configurator.

Under Trade Accounts

Account-only pricing - Approved buyers see their price after login. Everyone else sees retail or a request path.

Under POS

Pickup scheduling - Customers choose a pickup window that matches how your counter actually runs.

Questions

Can we start with one feature?

Yes. Most projects start with one feature or one system, then expand once the path is proven.

Where do systems fit?

Systems are the operating pieces we build and run. Features are the specific, searchable capabilities inside them. See Systems.

NEXT STEP

What would you build first?

Tell us what you sell and how people buy it, and we will map the path that fits.

Message us