For the developers who build stores

Install it for a client without regretting it.

You know the app that wrecks a theme, drags Lighthouse down twenty points, and answers support tickets with a chatbot. Cartrella is built by people who ship storefronts: adaptive blocks, real APIs, documented hooks, and a script budget we treat as a contract.

Adapts to the theme you built

Blocks adopt the theme’s own buy-button styling automatically. Custom build? Point them at a selector, restyle via stable documented class hooks, or drop a Custom CSS override in the block settings.

Headless when you want it

Every block runs on app-proxy endpoints you can call yourself — packs, reviews, and submissions on the shop’s own domain. Render your own UI; checkout still re-validates every price.

A reference that can’t drift

The API docs are generated from the same OpenAPI contracts that generate the server stubs — if it’s in the reference, it’s what the service actually does.

One script, hard budget

The whole suite ships one storefront script with a strict size budget. Your client’s Core Web Vitals survive the install — and so does your reputation.

The proxy API in one glance.

# Pack config for a product page (size ladder or mix container)
GET /apps/cartrella/bundles?product_id=<numeric id>

# Published reviews + star summary
GET /apps/cartrella/reviews?product_id=<numeric id>

# Submit a review (lands in the merchant's moderation queue)
POST /apps/cartrella/reviews
{ "product_id", "rating", "title?", "body", "author_name" }

Served on the shop’s own domain via the app proxy — no CORS dance, no tokens in the storefront. Full shapes in the generated reference.