Retail and E-commerce

Connecting your online store · Shopify, WooCommerce and Magento

A guide to connecting SellioCRM to your online store. You enter the store address and the webhook secret under Settings, in Integrations, copy the generated URL into the platform, and start receiving customers and orders automatically. The model is bring your own store: the account is yours, with no cost and no middleman on our side.

The connection to your online store does not live on the Retail screen: it lives under Settings, in Integrations, alongside the other integrations for the account. There are three cards, E-commerce (Shopify), E-commerce (WooCommerce) and E-commerce (Magento). The model is the same in all three: the store is yours, the credential is yours, and we neither charge for it nor sit in the middle of the transaction. The integration is born inert, meaning nothing happens until you configure and activate it.

What the connection brings into the CRM

Store customers become Contacts and orders become Sales orders. On every event, the store notifies the CRM and the record is created or updated. Two guarantees matter here. The first: a redelivery does not duplicate, because the record is looked up by the store identifier before anything is created, and a contact also falls back to the email as a second key. The second: only the populated fields coming from the store are written, so what your team edited in the CRM is not wiped out by an update arriving from outside.

Connecting Shopify

Open Settings, go to Integrations and find the E-commerce (Shopify) card.
Fill in Store domain with the .myshopify.com address, for example mystore.myshopify.com.
Fill in Webhook secret (API secret) with the secret used to sign the webhooks, which lives in Shopify Admin under Settings, Notifications, or is your app's API secret.
If you also want the CRM to read store data through the API, fill in Admin API access token (optional). It is not required to receive webhooks.
Click Save credentials. From then on the screen shows the Webhook URL (Shopify), with a Copy button.
In Shopify Admin, under Settings, Notifications, Webhooks, create a webhook for each topic pointing at that URL, in JSON format. The topics are customers/create, customers/update, orders/create and orders/paid.
Back on the card, click Activate. The badge now reads Connected.

WooCommerce and Magento

WooCommerce: fill in Store URL and Webhook secret, save, copy the Webhook URL (WooCommerce) and create the webhooks under Settings, Advanced, Webhooks, using the same Secret. The topics are Customer created, Customer updated, Order created and Order updated.
Magento and Adobe Commerce: the platform has no standardized native webhooks, so you enter the Store URL and an Authentication secret that you make up yourself, then configure a module or integration that posts customers and orders to the Webhook URL (Magento), authenticating with that secret.

Credential security

Every secret you save is encrypted and never shown back. Once saved, the screen tells you the credentials are stored securely and that you only need to enter them again to change them: leaving the field blank keeps what is already there. Every incoming call is verified against your organization's secret before anything is written. A call with an invalid signature is refused, and so is an endpoint whose integration is disabled. The webhook URL is a delivery point for machines: opening it in a browser returns an explanation, not a page of the system.

Example: Aurora Store runs on Shopify. It saves the domain aurora.myshopify.com and the API secret, copies the webhook URL and creates the four topics in Shopify Admin. Within minutes, a new USD 349.00 order shows up as a Sales order in the CRM, linked to the Contact Marina Alencar. A redelivery test of the same webhook does not create a second order.

How this talks to the Retail screen

The connection described above feeds the CRM's Contacts and Sales orders. The Retail screen works with a mirror layer of its own, the one where every row shows Source and Read at, and which is fed by the vertical's sync. That layer keeps the version already seen for each record, so a repeated or out of order notification does nothing, and it periodically compares its own count with the platform's: when a record is missing, the difference becomes a visible discrepancy instead of silence. That is why the two can grow at different rates, and why the Read at column exists.

Limits and common questions

Configuring an integration is an action for whoever administers the account.
Disabling the integration stops incoming events and does not delete what already came in. Removing the credential means entering it again later.
Nothing is sent from the CRM to the store over this connection: the flow is inbound.
If nothing arrives, check in this order: the integration is activated, the webhooks point at the copied URL, the secret is the same on both sides, and all the topics were created.
The store connection is independent of the Retail vertical: you can receive customers and orders as Contacts and Sales orders without turning the vertical on, and turn the vertical on later to gain the identity, cart, return, review and risk readings.

Open this article inside the system →