Most merchants never need this page. The ordinary way to connect is to press **Create workspace** in Store
Syria and let it set everything up for you — see
[set up Lynomia Chat from Store Syria](store-syria-set-up-from-store-syria). That is the path you can complete
on your own, and it is the one to try first.

This page is the **fallback**. Store Syria connects with an **integration token** for one store, which you
paste into Lynomia Chat with the store's address; the connection is tested before it is saved. The token is
issued by **Store Syria's support and operations team**, not by you, so this path starts with a request to
them rather than with a control in your store admin.

The token names the store. That is the whole of the tenancy rule: Lynomia Chat never sends a store id, so there
is nothing in a request for anyone to change, and a token issued for one store cannot be used to read another.

## What you need first

- **Administrator** access in Lynomia Chat, and a plan that includes Commerce.
- Store Syria offered on your installation. If the picker marks it *Not available yet*, it is switched off
  there, and that is an installation setting rather than an account one.
- **An integration token for your store, from Store Syria support.** Ask them for one. There is no control in
  your store admin that issues it.
- The store's address exactly as Store Syria shows it.

## Steps

1. Ask **Store Syria support** for an integration token for the store. They issue it and send it to you. It is
   shown once, and issuing a new one stops any token issued before it from working.
2. In Lynomia Chat: **Settings → Commerce → Add store → Store Syria.**
3. Enter the store's address and a name for it, and paste the token.
4. **Test and connect.** Lynomia Chat calls the store, confirms which store answered, and saves the connection
   as **Active**.

Step 2 opens this dialog, and Store Syria is the last row in it. On the test installation captured here every
platform is marked *Not available yet*, which is how a platform reads wherever the installation does not offer
it.

![The Add a store dialog listing WooCommerce, Salla, Zid, Shopify and Store Syria, each marked Not available yet](media:commerce/storesyria-provider-picker-en.png)

The token is encrypted and never shown again. If you lose it, ask Store Syria support for a fresh one and use
**Replace the integration token** on the store.

## A worked example

A customer writes "has my order shipped yet?".

1. The agent opens the conversation. The contact's verified phone number matched a Store Syria customer, so the
   Commerce section already lists that customer's latest orders.
2. The order is there with its status, what was paid, the items and the total.
3. The agent can **copy the order number** straight into the reply, and can search for an order by the number a
   customer quotes.

Store Syria sends no carrier reference of any kind, so the answer comes from the order's own status rather
than from anything to paste into a courier's site.

## Who can do this

**This path takes two parties, and you are only one of them.** Store Syria's support and operations team
issue the token — nothing in your own store admin does — and a Lynomia Chat **administrator** pastes it.
Start by asking them for it; there is no button to find first.

Connecting, replacing the token, disabling and disconnecting are **administrator** actions, recorded in the
audit log. Any agent who can see a conversation sees the Store Syria orders in it.

## Limits

- **Order actions are not available, and none are planned.** Lynomia Chat reads Store Syria and never writes to
  it. Nothing in the order panel changes an order.
- **There is no separate shipment line on the order card.** Store Syria folds fulfilment into the order's own
  delivery state, so what an agent reads is the status of the order itself, not a shipment record beside it.
- **Neither a tracking number nor a tracking link.** Store Syria sends neither, so neither appears in the
  panel, and a carrier URL is never guessed.
- **Guest checkouts are matched**, by email or phone, the same as registered customers.
- Matching is exact: a normalized email address, or a phone number in international form. Names are never used.
- Only the latest **5** orders per customer are shown, so every figure is *visible*, not lifetime.
- Order dates are read in the time zone the store reports them in.

## Live updates

When the event feed is switched on for your Store Syria installation, Store Syria pushes its own commerce
events to Lynomia Chat from its transactional outbox, and the Commerce section updates on its own when an
order moves. Nothing is registered in the store during the connection, because there is nothing to register:
the store already knows where to deliver from its own configuration. Where the feed is not switched on, the
section is still current each time an agent opens the conversation, because the orders are read when they are
needed.

An event says which customer changed. The orders are then read from the store, so an event can never put stale
or forged order data on an agent's screen.

## Related

- [What the Store Syria integration gives you](store-syria-overview)
- [Set up Lynomia Chat from Store Syria](store-syria-set-up-from-store-syria)
- [What each platform supports](commerce-provider-support)
- [What connecting a store gives you](commerce-overview)
- [Customer 360](customer-360)

## If it does not work

**"This store is already connected."** One store belongs to one Lynomia Chat account. Check whether the store
is connected to another workspace of your own, and disconnect it there. If it is not a workspace you control,
contact support rather than trying again — a second attempt is refused the same way.

**The connection test fails straight away.** The token was replaced in Store Syria, the address is not the
store's own, or the integration is switched off there. Ask Store Syria support for a fresh token and try again
with the address exactly as Store Syria shows it.

**The store rejected the credentials.** The message names Lynomia Chat, not your store, and it means the
store answered and refused the token: it was issued for another store, it has been replaced since, or it has
been withdrawn. A connection keeps the store it was first made for, so a token issued for another store
cannot take its place — that is what stops a rotation quietly serving one merchant's orders under another's
connection. Ask Store Syria support for a token issued for this store, and connect any other store as its
own store.

**A customer I know buys from us is not matched.** Match is exact, on email or an international phone number,
and names are never used. An agent can search by email or phone in the section and link the right customer by
hand.

**Disconnecting.** It removes Lynomia Chat's access and every customer link for that store. Nothing in Store
Syria changes, and you can connect it again later.