Commerce
Bind it to the product you already sell
A customizer that doesn't know what it's selling produces orders nobody can fulfil. Every one of ours points at a real product in your store, through an explicit link rather than a matching name.
In production on Shopify: products linked in one press, a code for every variant, and prices read live from the store, so a change there shows here.
One lesson from the legacy system we refuse to relearn: never bind by name or by convention. A customizer points at a product through an explicit row, so renaming something in your catalogue doesn't silently detach it and nobody has to work out which “Team Cap” was meant.
The base price comes from the product you bound. The upcharges come from the options you priced. Where a choice really is a variant, like a size or a cut, it maps to that variant and its SKU, so inventory and fulfilment keep working the way they already do.
Choices that aren't variants ride along as line properties and upcharges. That's what keeps a twenty-part colour space from exploding your catalogue.
What you get
- Explicit links. A row, not a naming convention. Renames don't detach anything.
- Price from the product. Base price synced from what you already sell it for.
- Variants where they belong. Size and cut map to real variants and real SKUs.
- Everything else as properties. Colour picks and personalisation ride the line item.
- Bound by handleone product, one journey
- Base priceyours; the customization is ours
- Buttondropped into your theme
- Fallbackunbound products behave as before
Related capabilities
Next
Book a demo
Put your product on the stage
Bring a model, or bring the product and some photographs. We'll walk you through what a customizer for it looks like, and tell you honestly what it takes to get there.
There is no self-serve sign-up yet: we set the account up with you, and go through your product before you commit to anything.