Custom stack

Not every stack is on a named platform. Headless storefronts, custom checkouts, native apps and in-house order systems all produce the same commercial events.

If it can make an HTTP request, it can send to Upstack. Custom events are resolved, filtered and forwarded on exactly the same path as a Shopify order.

There is no single answer here, which is the point. A headless storefront, a native app, an in-house order system or a checkout you built yourself all produce the same commercial moments — a cart, a checkout, a purchase, a refund — they just do it in your own vocabulary. What they share is a backend that knows when those moments happened, and the ability to make an HTTP request when they do.

A custom stack gives you total control over your schema and no help enforcing it. Upstack provides the contract: events posted from your backend are validated, resolved against the device graph, filtered for bots and fraud, and mapped to whatever shape each destination expects — without you writing an adapter per tool. Add a destination later and it is a mapping, not another integration project.