Once Store Syria orders are reaching your conversations, the connection asks little of you. What it does ask
is that someone knows where it lives, how to tell it is healthy, and how to stop it.

That last one is the question merchants ask first, so here is the answer before anything else. **Disconnecting
a store deletes its credentials and its customer links. Your contacts and your conversations are kept**, and
nothing in Store Syria changes.

Two screens hold the two halves: **Settings → Commerce** holds the store itself, and **Settings →
Integrations → Connect an external platform** holds the workspace authorization. Almost everything below is
the first.

## Who can do this

Connecting a store, replacing its token, disabling it, enabling it again and disconnecting it are
**administrator** actions, and each one is recorded in the audit log with who did it and when. Any agent who
can see a conversation sees the Store Syria orders in it, and no agent can change the connection behind it.

## The states a store can be in

**Settings → Commerce** lists each store with its platform, its address, a state, and the time it was last
verified.

| State | What it means | What you can do with it |
|---|---|---|
| **Active** | verified and being read; orders appear beside conversations | Disable it, replace its token, disconnect it |
| **Disabled** | an administrator paused it, and what was cached has been dropped | Enable it, replace its token, disconnect it |
| **Needs re-authorization** | the store rejected the credentials, so nothing is read or shown | Replace its token, restore the connection, disconnect it |
| **Disconnected** | credentials and customer links deleted; the entry stays, so the store can be connected again | Reconnect it |

Only an **Active** store appears beside a conversation. In the other three states the Commerce section shows
nothing for that store: a connection that cannot be trusted shows nothing rather than something stale.

Here is a store in the first of those states, on a test installation, with the three administrator actions
beside it.

![The Commerce settings page listing an Active Store Syria store, with Disable, Replace keys and Disconnect beside it](media:commerce/storesyria-connected-store-en.png)

## Check that it is healthy

There is **no Verify button in Lynomia Chat.** The store list is the check.

1. Open **Settings → Commerce.** The Store Syria store should be listed as **Active**, with the time it was
   last verified beside it.
2. Open a conversation with someone who has bought from you. The Commerce section should name the store
   customer the contact was matched to, and list that customer's latest 5 orders.
3. If one contact shows nothing, that is matching rather than the connection: it is exact, on an email
   address or an international phone number, and names are never used — see
   [Store Syria orders beside a conversation](store-syria-in-the-conversation).

Step 1 lands you on this page. The workspace shown here has no store connected yet, so the list is empty; a
connected Store Syria store is listed in that space with its state and the time it was last verified.

![The Commerce settings page, with an Add store button above an empty store list reading No store connected yet](media:commerce/storesyria-commerce-empty-en.png)

One empty Commerce section is not an outage. A store listed as Active, verified recently, is connected.

## Verifying from Store Syria

Store Syria carries its own check on its Lynomia Chat page, and it is not a status light: **it re-runs the
connection rather than reading its state.** **Verify connection** is offered only beside a **Store data**
line that is already connected, so it is a re-check of a working connection rather than a way to finish one
that never did.

- **Running it again does not create a second store.** A store already connected with the same credential is
  left exactly as it is.
- **A store you disabled in Lynomia Chat stays disabled.** The re-run will not switch it back on; the pause is
  your decision. Enable it in **Settings → Commerce** when you want it back.

## Pause a store, or replace its token

**Settings → Commerce → the store → Disable** stops the store being read at once and drops what was cached, so
agents see nothing from it. The credentials are kept, and **Enable** brings it back after checking the store
still answers. A disabled store still holds a place in your plan.

The store's **Replace keys** action opens **Replace the integration token**. The new token is tested against
the store before it is saved, so one that does not work changes nothing, and it is also the repair for a
store in **Needs re-authorization**. That token comes from **Store Syria's support and operations team**
rather than from your own store admin, so ask them for a fresh one.

## Disconnect, and exactly what that deletes

**Settings → Commerce → the store → Disconnect**, then confirm. This is the whole of what happens.

| Deleted | Kept |
|---|---|
| The store's credentials | Every contact, with its attributes and labels |
| Every link between a contact and a store customer, including links an agent made by hand | Every conversation and message, including the ones where orders were discussed |
| The cached order data | The store entry, as **Disconnected**, so you can connect it again later |

**Nothing in Store Syria changes.** No order, no customer and no setting of yours is touched there.

What your team notices is that the Commerce section stops showing Store Syria. The conversations themselves
read exactly as they did. Connect the store again later and matching starts over from your contacts' email
addresses and phone numbers; links an agent made by hand have to be made again.

## Connections Store Syria manages

If Store Syria created your workspace for you, its entry under **Connected platforms** has **no Disconnect
button**. In its place is a sentence saying Store Syria set this workspace up and manages the connection, and
that it should be ended from Store Syria.

That absence protects you. Ending the authorization from this side alone would remove the access the whole
integration rests on while Store Syria went on reporting a healthy connection, with no way back from either
side. End a managed connection **from Store Syria**, so your store and your workspace end together, and ask
Store Syria support if that is not possible.

Store data is separate from this. An administrator can disconnect the store under **Settings → Commerce**
whichever way the workspace was arranged.

## Ending store data is not the same as ending the authorization

| What you want to stop | Where | What it ends |
|---|---|---|
| Lynomia Chat reading this store at all | **Settings → Commerce → Disconnect** | credentials and customer links deleted; contacts and conversations kept |
| Store Syria being able to open this workspace | **Connect an external platform → Connected platforms → Disconnect** | the platform loses access to the workspace at once, and anyone signed in through it is signed out |

Neither does the other's job, and the authorization is the harder one to put back: the way back is a fresh
connection code generated in Lynomia Chat and redeemed by Store Syria, in
[restore a Store Syria connection](store-syria-restore-the-connection). If Store Syria tells you the
authorization was withdrawn and needs restoring, start at
[Store Syria says authorization needs recovery](store-syria-authorization-needs-recovery).

## Plan limits

Where your plan sets a store limit, **Settings → Commerce** shows how many of those stores you have used.
When they are all used, another is refused: upgrade the plan or disconnect a store to make room. The same
refusal reaches you on the Store Syria path, where pressing **Create workspace** reports that there is no
room left in the plan. How many stores a plan carries is a question for whoever sells you yours. A plan
that does not include store data at all is a different refusal again, and there is then no Commerce section
to manage at all.

## Limits

- **Administrator only**, and every one of these actions is recorded in the audit log.
- **Read-only throughout.** Managing the connection changes nothing inside your store.
- **Disabled and Needs-re-authorization stores still count** towards your store limit; only disconnecting
  frees a place.
- **Nothing repairs a connection on a schedule from this side.** Lynomia Chat does not sweep for broken Store
  Syria connections in the background.

## Related

- [Restore a Store Syria connection](store-syria-restore-the-connection)
- [Store Syria says authorization needs recovery](store-syria-authorization-needs-recovery)
- [Store Syria orders beside a conversation](store-syria-in-the-conversation)
- [What the Store Syria integration gives you](store-syria-overview)
- [Connect Store Syria with an integration token](connect-store-syria)
- [What connecting a store gives you](commerce-overview)
- [What each platform supports](commerce-provider-support)

## If it does not work

**The store says Needs re-authorization.** The store rejected the credentials, so nothing is read until it is
authorized again. Replace the integration token with one Store Syria's team issues you, or work through
[restore a Store Syria connection](store-syria-restore-the-connection).

**There is no Disconnect button under Connected platforms.** Store Syria set this workspace up and manages the
connection. End it from Store Syria, or ask their support.

**I disconnected the store by mistake.** Your contacts and conversations are untouched. Connect it again;
matching starts over, and any link an agent made by hand has to be made again.

**Store Syria shows a healthy connection and Lynomia Chat does not.** Each side keeps its own record.
**Settings → Commerce** decides whether your orders are being read; if the authorization behind it was
withdrawn, see [Store Syria says authorization needs recovery](store-syria-authorization-needs-recovery).