Shop settings

Settings covers the shop you’re in. Owners and admins find it at the bottom of the sidebar, under Admin (on a phone: More → Settings). Admins see it without the bootstrap token and the Danger zone.

#Shop profile: name and logo

Type the shop name (2 to 60 characters), or click Upload a logo (PNG or JPEG, up to 5 MB, cropped to a square). Remove logo removes it. Then click Save changes.

Customers see this name and logo on your online shop, their own page, their redelivery page and your Plurion Terminal’s messages (the terminal picks up a new name within a few minutes). The name also labels the shop on your Hub and in the sidebar, as soon as you save.

#Devices

Devices lists every Plurion object of the shop, by family: vendors, DropBoxes, terminals, visitor counters, gacha machines and demo boxes. Silent only shows the ones that stopped checking in. The bin deletes one, such as an object you took back or that disappeared. Auto-clean, on by default, retires terminals, counters, gacha machines and demo boxes silent for 30 days. It never touches a vendor or a DropBox.

#Export, sign out, close the shop

• Export your data: download a readable summary or a full technical backup, any time. See Export your data.
• Sign out: ends the session on this device only.
• Danger zone → Delete this shop: closes the shop at once, and nothing is erased for 30 days. Read Closing a shop first.

The Notifications panel has its own chapter: Notifications on your phone.

#The bootstrap token (older scripts only)

You can skip this. Today’s Plurion objects connect to your shop without a token, through the link they give you when you touch them (see Connecting an object to your shop). The panel is Bootstrap token.

Only if you still run objects set up with a notecard

Objects on an older notecard script read this token from their config notecard and send it once, when they first register. Show current token reveals it, and Rotate token replaces it.

Rotating breaks nothing already running. An older object only needs the new value for its next registration, so put it in its config notecard before its next reset. Treat the token like a password, since anyone holding it could register an older-script object to your shop.