Changelog

A try-on used to place the person in a fitting setting, standing still. Now the scene is a moment of play for the product's sport: a tackle, a layup, a spike or a climb out of the saddle, with the front of the kit still turned to the camera.

Each try-on also picks its own moment, framing and light, so trying the same design twice gives two different photos instead of the same one.

The Direction field in the Try On window still wins: write the scene you want, such as a night match under floodlights, and the try-on follows it.

Until now, everything that happened in Uniform Builder had to be read through the dashboard. If you already run an ERP, a production board, or an internal ordering tool, that meant somebody re-keying the same order twice: once where the customer placed it, and once where your team actually works.

The new REST API closes that gap. It exposes the objects you already work with, orders, products, and quotes, over a versioned endpoint, authenticated with organization-scoped API keys you create and revoke yourself from the dashboard. Keys are scoped to a single organization, so a key issued for one store cannot read another, and each one can be rotated without disturbing the rest of your integrations.

Alongside it are outbound webhooks, so your systems can react to events as they happen rather than polling for changes. Endpoints are configured per organization and every delivery is signed, which lets your receiver verify a payload genuinely came from us before acting on it.

The API is available on Pro and Enterprise plans. Full endpoint documentation, including authentication and the webhook signature scheme, lives in the API reference in the docs.

Teams that had already settled on a plan kept asking for a way to stop processing a card every month, particularly where an annual purchase order is easier to get signed than a recurring monthly charge.

Basic and Pro are now both available on annual billing, priced below twelve months at the monthly rate. Everything inside the plan is identical; only the billing period and the effective price change.

Switching is handled through the normal subscription screen, and moving between monthly and annual is prorated by Stripe rather than requiring a cancellation and a fresh signup, so you keep your organizations, products, and history intact through the change.

The mockup editor was useful for one-off work, but there was no way to hand a customer a place to browse. Every conversation started with someone sending a file.

Mockup stores give you a public storefront at your own link, showing only the products you have chosen to put in it. A customer opens the link, picks a product, and customises it directly, with no account and no back-and-forth to see something realistic.

You curate the store from the catalogue rather than uploading products one at a time, so building a storefront is a matter of selecting what you want to sell rather than re-creating your range from scratch.

An account here can reach customer records, quotes, and billing, so a password on its own was doing more work than a password should.

You can now enrol an authenticator app from your account settings and be prompted for a code when signing in. Any standard TOTP app works, so there is nothing new to install if you already use one.

Administrative access requires it. Accounts with elevated permissions must be enrolled and must have completed the second step in the current session before those areas open, rather than relying on a password alone.

Support questions clustered tightly around a handful of screens, which is usually a sign that the product is under-explained rather than that customers are doing something unusual.

There is now a complete user manual inside the app, covering stores, products, the design tools, assets, quotes, the project tracker, integrations, and billing. Each section documents a specific screen and links straight to it, so reading about something and doing it are one click apart.

The screenshots are captured from the real dashboard rather than drawn by hand, which means they show the interface as it actually is, and they are refreshed as the interface changes rather than slowly drifting out of date.

The manual is available in English, French, and German.

Parts of the product had been translated before, but unevenly, so a customer could move between two screens and have the language change underneath them.

The interface is now translated end to end: the dashboard, the public design pages your customers see, the quote flow, and the documentation. Your language preference follows your account rather than the device you happen to be on.

Public storefronts respect the language of the visitor rather than the language of whoever built the store, so a customer in France sees a French storefront even when the store was set up in English.