The Store Syria integration lets an agent answer "where is my order?" inside the conversation the customer
wrote in. That customer's recent Store Syria orders sit beside the message, so nobody opens the store in a
second tab or promises to come back later.

It helps to think of the integration as two halves, because they are arranged separately and can arrive
separately.

- **A Lynomia Chat workspace.** The account your team signs into: inboxes, agents, contacts and conversations.
- **A store-data connection.** The authorization that lets that one workspace read orders from one Store
  Syria store.

Most merchants get both from a single action in Store Syria, which arranges the workspace first and the store
data after it. Underneath they remain two steps, and the first can succeed while the second is still
outstanding. That is the usual reason a brand-new workspace opens with no Commerce section in it yet.

![How the Store Syria integration fits together](media:commerce/store-syria-architecture-en.png)

## Who it is for

Merchants who sell on Store Syria and answer customers in Lynomia Chat. Agents get the benefit; a Store Syria
merchant administrator and a Lynomia Chat administrator set it up, often the same person.

## What you need first

- A **Store Syria store you administer**. The connection is made one store at a time.
- A Lynomia Chat plan that **includes store data**. Without it the Commerce section and settings page do not
  appear, and a connection attempt is refused saying the plan does not include store data.
- **Administrator** access in Lynomia Chat to connect, replace or remove a connection. If Store Syria arranges
  the workspace for you, your store's owner starts as its administrator.
- Store Syria **offered on your installation**. If the platform picker marks it *Not available yet*, it is
  switched off there — an installation setting, not an account one.

## What your agents get

What any connected store adds to Lynomia Chat — the Commerce section, order conditions in contact filters,
automation triggers, the Flow Builder lookup — is described once in
[what connecting a store gives you](commerce-overview). This is the Store Syria part of it.

| In the conversation | What a Store Syria connection gives you |
|---|---|
| The Commerce section | The store customer this contact was matched to, and that customer's latest **5** orders, newest first |
| Each order | Its status, its payment status, how many items it holds, and the totals in the store's own currency |
| The reply | The agent can **copy the order number** straight into the message |
| Find an order | Looking up an order by the number a customer quotes works on Store Syria |
| Matching | Exact, on a normalized email address or a phone number in international form. **Guest checkouts match too** |

Orders are read when they are needed, not imported: an answer is reused for about 120 seconds, and if the
store cannot be reached the last answer is shown for up to 24 hours, labelled with the time it was fetched.
Store Syria can also push an event when an order changes, so the section refreshes on its own; that is
available once the event feed is switched on for your Store Syria installation, and that is not something
you can change from your store.

Two absences are worth knowing before you promise anything to your team. Store Syria sends **no tracking
number and no tracking link**, so neither appears and there is no shipment line on the order card. And the
cross-store **Overview** tab appears only once you have more than one connected store.

## Lynomia Chat reads your store and never changes it

**Lynomia Chat reads Store Syria. It never writes to it.** Nothing in the panel changes an order: no status
change, no cancel, no refund, no resending a store email. That is the design rather than a gap, and no order
actions are planned. The store stays the system of record. For the row-by-row comparison with the other
platforms, see [what each platform supports](commerce-provider-support).

## Which way you will connect

There are three paths. They are genuinely different, so pick one and follow it through rather than mixing
steps from two.

| Path | Who starts it | Who else must act | Permission you need | What you end up with |
|---|---|---|---|---|
| **Store Syria sets it up for you** | you, pressing **Create workspace** in Store Syria's **Communication & Marketing** section; nothing is pasted | nobody — it runs from end to end | a Store Syria role that may manage Lynomia Chat. You need no Lynomia Chat account beforehand | a new workspace, with your store's owner as its administrator, and the store data connected after it |
| **Connect a workspace you already have** | you, generating a connection code in Lynomia Chat and pasting it into Store Syria | **Store Syria support**, who approve the claim before it finishes | the **administrator** role in Lynomia Chat, plus a Store Syria role that may manage Lynomia Chat | the workspace you already run, connected, with nothing in it replaced |
| **Paste an integration token** | you, by asking **Store Syria support** for a token for the store | **Store Syria support**, who issue it — no control in your own store admin does | the **administrator** role in Lynomia Chat, on a plan that includes store data | that one store read by your workspace. No workspace is created |

The first is the default, and the only one you can complete from end to end on your own — start at
[set up Lynomia Chat from Store Syria](store-syria-set-up-from-store-syria). Take the second if your team
already works in Lynomia Chat and you want to keep that workspace with its agents, contacts and history:
[connect a Lynomia Chat workspace you already have](store-syria-connect-an-existing-workspace). The third is
the fallback for when the first is not available to you, and its token is issued by Store Syria's support and
operations team rather than by you, so ask them for it instead of looking for a button in your own admin:
[connect Store Syria with an integration token](connect-store-syria).

Whichever path you take, the credential behind it names one store. A credential made for one store cannot be
used to read another, and one store belongs to one Lynomia Chat workspace: a store already connected
elsewhere is refused.

## Limits

- **No order actions, and none are planned.** Reading only.
- **No tracking number, no tracking link and no shipment line** on the order card.
- Only the latest **5** orders per customer are read, so every figure is *visible*, not lifetime.
- Matching is exact, on email or an international phone number. **Names are never matched or searched.**
- One store belongs to one Lynomia Chat workspace, and your plan sets how many stores you may connect.
- Connecting, replacing the credential, 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.
- Disconnecting deletes the credential and every customer link for that store. **Contacts and conversations
  are kept**, and nothing in Store Syria changes — see
  [manage your Store Syria connection](store-syria-manage-the-connection).

## Related

- [Set up Lynomia Chat from Store Syria](store-syria-set-up-from-store-syria)
- [Connect a Lynomia Chat workspace you already have](store-syria-connect-an-existing-workspace)
- [Connect Store Syria with an integration token](connect-store-syria)
- [Store Syria orders beside a conversation](store-syria-in-the-conversation)
- [Manage your Store Syria connection](store-syria-manage-the-connection)
- [Store Syria: common questions](store-syria-questions)
- [What connecting a store gives you](commerce-overview)
- [What each platform supports](commerce-provider-support)

## If it does not work

**I connected in Store Syria, but there is no Commerce section in Lynomia Chat.** The two halves arrive
separately, and the store-data half is the one that is missing. Work through
[Store Syria store data did not connect](store-syria-data-did-not-connect).

**I cannot find Commerce in Settings at all.** Your plan does not include store data, or no store is
connected yet.

**Store Syria is marked "Not available yet" in the platform picker.** It is switched off on your
installation. Ask whoever runs it; there is no setting for this in your account.

**A customer we know buys from us is not matched.** Matching is exact and never uses names. An agent can
search the store by email or phone and link the right customer by hand — see
[Store Syria orders beside a conversation](store-syria-in-the-conversation).