Credits and limits

What a try-on uses, what stops one, and what your shoppers see when that happens.

Credits

• One picture, one credit. Each try-on picture made takes one credit from your account.
• A try-on that fails gives its credit back.
• A try-on that is refused before a picture is made takes none. That is the case for a product picture on a host your store doesn't allow, and for a daily limit.
• At zero, try-on switches off for all of the account's stores. The button leaves your pages within a couple of minutes, and comes back the same way after a top-up.

Your balance, your statement and top-ups are on the dashboard's Credits page. You can set an email that warns you when the balance is low.

When try-on is off

Before the script adds a button, it asks Labbesne one question: can this key start a try-on right now?

The answer	Your page
Yes	The button is added. availability fires with { available: true }.
No	Nothing is added. availability fires with { available: false }. open() ends in an error with unavailable.
No answer	Nothing is added. availability fires with { available: false }. open() ends in an error with unreachable, and the next open() asks again.

The answer is no when the key is unknown or was rotated away, the store is paused, the account is suspended, or the account has no credit left. Your page is never told which: the answer is only yes or no. The dashboard shows you the reason.

There is no answer when Labbesne can't be reached within 8 seconds, or your page's Content-Security-Policy blocks the request.

The answer is kept for about a minute in the browser and a minute on our side. So a change, such as a top-up or a paused store, reaches a product page within about two minutes.

The question carries your key and nothing else: no cookie, no address of the page, nothing about the shopper.

Daily limits

Two limits count try-ons per day. A day is a UTC day.

• Your account's limit, across all its stores. Labbesne sets it. It is on the dashboard under Settings, in Limits.
• A store's own limit, if you set one: Daily limit for this store in the store's Settings. It keeps one store from using up the account's credits.

When a limit is reached, the button stays, and a shopper who tries is told, inside the try-on, that it isn't available right now and to check back later. They are not told why. No picture is made and no credit is taken. A try-on that was started counts towards the day's limit even if it fails.

A try-on refused because of its picture's host does not count towards a day's limit. See Image hosts.

Other limits

• Stores. Your account has a limit on the number of stores. It is shown with the account's daily limit, under Settings, in Limits.
• Image hosts. A store can list 20 hosts for its product pictures, not counting its own sites.

Rate limits

Labbesne limits how fast one shopper, and one network address, can start and generate try-ons. A shopper who hits it sees a message inside the try-on and can try again shortly. There is nothing to set.

The script's own question is limited too. A limited question counts as a yes, so a busy office or phone network never loses the button.

What a shopper can send

• One photo per try-on, taken with the camera or picked from their device.
• One product per try-on: the one on the page the try-on opened from.

How long a try-on lasts

• Closing and opening again on the same product picks up where the shopper was.
• Opening on another product keeps their photo, so they don't have to take it again.
• Reloading your page starts again. Nothing is kept between page loads.
• After an error screen that your page was told about, the next open starts again too. That includes garment_host_not_allowed: the shopper's photo is not kept. See Errors.