E-commerce, built past ~the easy part.~

Storefronts, replatforms, headless front ends and custom Shopify apps — including the logic that decides what a given customer is allowed to buy.

Shopify and headlessStorefront and checkout
Custom Shopify appsAdmin, webhooks, tags
IntegrationsERP, CRM, 3PL, analytics
scroll
or drop an mp4 here. Deployed, it loads itself from assets/hero.mp4.
What we build

Six things a store needs, and one that most agencies skip.

We run e-commerce end to end: the storefront people see, the platform work underneath it, and the integrations that keep the back office honest. The last of these is where most projects quietly fail.

Storefronts and replatforming

New builds and migrations off legacy carts, with theme architecture a marketing team can run without a developer in the loop.

  • Shopify
  • migrations
  • theme architecture
  • CRO

Headless front ends

Next.js and Hydrogen when the interface has to do more than a theme can, with the commerce layer left where it belongs.

  • Next.js
  • Hydrogen
  • Storefront API
  • WebGL

Custom Shopify apps

Embedded admin apps, checkout and admin extensions, and webhook services for behavior the platform does not ship. This is what we built for TRAUMAGEL.

  • embedded apps
  • webhooks
  • Admin API
  • Flow triggers

B2B and gated commerce

Wholesale, professional-only and license-restricted catalogs where pricing, availability and content change per account.

  • customer tags
  • account portals
  • tiered pricing
  • net terms

Subscriptions and retention

Reorder flows and lifecycle messaging that follow account state rather than a generic drip, including win-back for customers who stalled mid-purchase.

  • Klaviyo
  • state triggers
  • reorder
  • win-back

Integrations and measurement

ERP, CRM and 3PL connected so staff work in one place, with server-side events and consent handling so the reporting still works.

  • ERP and CRM
  • 3PL
  • GA4
  • Meta CAPI
Case study — Cresilon

TRAUMAGEL®

TRAUMAGEL® is a hemostatic gel trusted by EMS, military, hospital, and law enforcement agencies. Purchase online now; orders are held while TRAUMAGEL verifies professional eligibility before payment capture and fulfillment.

client
Cresilon
platform
Shopify, Shopify Flow, custom HCP app
constraint
Licensed US healthcare professionals only
rule
Authorize at checkout, capture after approval
scope
Storefront, gating, HCP app, verification queue, lifecycle email, analytics
shop.traumagel.com
HomeProductsHow it worksShop
Shop0 Cart
Order direct — for licensed healthcare professionals in the USA only
Control bleedingin seconds.

TRAUMAGEL® is a hemostatic gel trusted by EMS, military, hospital, and law enforcement agencies. Purchase online now; orders are held while TRAUMAGEL verifies professional eligibility before payment capture and fulfillment.

Purchase TRAUMAGEL®Review ordering requirements
Prescription medical deviceEMS & military grade

Buy first, verify second

The store never blocks the sale. Checkout authorizes the card, the order is held, and eligibility is resolved afterwards — so a paramedic at 2am is not asked to file paperwork before they can order.

A custom app, not a workaround

We built HCP, an embedded Shopify app that writes and reads verification state directly as customer tags. Storefront, checkout, Flow rules and email all read the same value, so there is one state rather than four.

A queue humans can work

Reviewers get a filtered inbox with counts by state, credential attachments, and one-click approve or reject. No spreadsheet, no inbox archaeology.

Reversible by design

Approval expires and can be revoked. A license that lapses moves the customer back to unverified and stops the next order automatically.

The store is live

Everything described here is running in production today.

Visit shop.traumagel.com ↗
Why this one was hard

A normal store asks one question. This one asks ~five.~

Standard checkout resolves a single condition: is the payment method good? A license-restricted store has to resolve buyer identity, credential status, jurisdiction and product class — after the customer has hit pay, without losing the sale.

i

Is the payment method good?

The only question most checkouts ever ask, resolved in milliseconds by the processor.

ii

Is this buyer a licensed professional?

Requires a human or an API to look at a credential that lives outside the store.

iii

Is that license still current?

Approval is not permanent. Status has to be re-checked, and it can be revoked.

iv

Is the product allowed where they are?

Product class and destination together decide whether the order is legal to ship.

v

Should this order ship at all?

The last question, and the one that has to be answerable before money moves.

The gate

One order, three buyers, ~three endings.~

This is the logic that runs on every TRAUMAGEL order. Choose who is buying and watch the same order take a different path — including what the customer sees, what the card does, and where it lands for staff.

Who is placing this order?
    Playing the order through the gate.
    What staff and the customer see
    order TG-4417 — draft
    customer
    —
    tags
    —
    payment
    —
    fulfillment
    —
    queue
    —
    customer sees
    —
    Setup needed 1 Pending verification 1 Approved 2 Rejected 2 Follow-up 0 Verification queue — counts update as the order resolves

    Tell us the part that ~isn't standard.~

    Most e-commerce work is well understood. If yours has a rule attached to it — a license, a contract, a territory, an approval, a system that has to agree first — that rule is the project. Send it to us and we will tell you where it should live.

    Get in touch

    Let's build what's next.

    © 2026 ASE Creative Group · New York