How it works
From a model
to a file the
factory runs
Six steps. The first five are yours and happen once per product; the sixth happens every time somebody orders.
01
Bring the product in
Upload the model. Every part of it shows up in an outliner: crown, brim, panel, web, strap. That list is what everything else hangs off. Nothing gets addressed by position, or by a number that shifts the moment someone reorders something.
Bring a GLB, or bring the product and photographs and we'll tell you what it takes to get a model made.
02
Say what each part is made of
Build the libraries once, meaning colours, palettes and materials, then put them on the parts. A look can be composed live from layers, or baked once as surface detail and tinted afterwards. That second route is how twenty colourways come out of one bake instead of twenty.
Layers group into a named design, so a camo is one decision called camo rather than three rows nobody can read.
03
Say what a shopper may change
Each control is bound to what it sets: a colour grid on a part, a text field in a spot, an artwork upload in a print area, an option that swaps parts of the model. Rules filter what shows, so nobody assembles a combination you cannot make.
Options that change the shape, like a long or short cuff or fourteen web styles, stay one product instead of becoming fourteen.
04
Lay out the journey
Arrange the controls into steps and put them in the order a shopper should meet them. Preview it exactly as the shopper will see it, on a phone as well as a desktop, before anybody outside sees it at all.
Change the order later without rebuilding anything. The controls stay where they are.
05
Launch it
Set the camera angles worth showing and the lighting to show them in, then publish. You get one URL that opens the customizer on any device, and you can have as many launches as you have places to put them.
A launch is a link. There is nothing for your developer to install to use one.
06
Take the order
The shopper saves a design and gets a short code and a share link. The total behind it was computed on our server and signed. When the order is finished it is stored first and forwarded second, to wherever you want it, and the design becomes a job sheet with a print canvas in real millimetres.
Stored first is the point: an integration going down slows an order, it never loses one.
What to bring
Four things,
and none of
them code
- The product. A 3D model if you have one, or the physical product and photographs if you do not.
- Your colours and materials. The palette you actually stock, and what each option is really made of.
- Your prices. The base, the upcharges, and the tiers for team quantities.
- Where orders should go. A webhook, an inbox, or your production team. Either way the order is stored first.
Questions
The ones
worth asking
If yours is not here, ask it on the demo. We would rather tell you a product is a bad fit than take you through an onboarding that ends badly.
Do we need a 3D model already?
It helps, and it's not required. If you have a GLB from your factory or your designer, that is the fastest start. If you do not, bring the product and good photographs. Building a model is a piece of work with a real cost, and we'll tell you what that looks like for your product instead of guessing at it.
Does this replace our store?
No, and it is not trying to. Your store owns the cart, the checkout and the customer. FlyScroll owns the 3D experience, the configuration, the price of the customization, the saved design and the production output. Everything is built around that seam.
How do prices work?
Base price from the product, upcharges from the options you priced, quantity tiers for team orders. Every total is computed on our server and signed over the design and the selections it came from, then re-verified when the order arrives. A shopper cannot edit a price in the browser and have it stick.
What arrives when someone orders?
The full selection tree, the design that replays it, a thumbnail and the signed price record. Then, through the production recipe you authored for that product, a print canvas in millimetres at the resolution and colour mode you set, plus a job sheet your team or your manufacturer can work from.
Can our brands each have their own version?
Yes. A company, its brands and its sub-brands are one hierarchy. A brand opens the parent's templates, palettes and materials, and overrides only what differs. What it does not touch stays in step with the parent.
How do we get started today?
By talking to us. There's no self-serve sign-up while we onboard the first brands by hand. We set the account up with you and go through your product before you commit to anything.
- 01Modelyour GLB, optimised and mapped
- 02Authorlayers, elements, rules
- 03Journeythe steps a shopper walks
- 04Publishone link, or bound to a product
- 05Configurethe shopper builds and saves
- 06Producejob sheet + print canvas
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.