Managing shops
New authorization, reauthorization, renaming and deletion all live on this page.
What you can do
Sidebar · Shops
| Action | Description |
|---|---|
| New authorization | Pick a channel and run the OAuth flow; see Authorize your first shop |
| Reauthorize | Restores an expired authorization without touching local data |
| Rename | Gives the shop a name your team understands; affects display inside TFChat only |
| Delete | Unbinds the shop and clears its local data in TFChat |
Shops are grouped by platform, with a search box at the top — handy once you have many.
The three-month binding lock
Once an account authorizes a shop, that shop enters a three-month binding lock. During that period no other account can authorize the same shop.
- The lock always lets the original account through — you can reauthorize, delete and re-add whenever you like;
- Deleting the shop does not release the lock — local data is gone, but the lock stands until the three months are up;
- The rule exists so the same shop cannot bounce between accounts, which would scramble message ownership and billing.
What deleting does
- Unbinds the shop, which stops receiving new messages;
- Clears that shop's local conversations, products, order cache and to-do items in TFChat;
- Nothing on the platform side is affected;
- The binding lock stays until it expires.
Deletion cannot be undone. For a temporary pause, switch off AI replies and basic reception for that shop instead.