Shopier Integration

The personal access token comes from the developer portal

You generate the token a Shopier connection needs by opening an account on a separate developer portal, not in your seller panel. Not finding it in the panel is normal. The token is a personal access token and is enough on its own to establish the connection.

The second field, the webhook signature token, works on a different logic: you do not generate it — it comes back inside the response when the webhook subscription is created. So the order matters: subscription first, token second.

The one setup where the order of steps matters

In most connections the order in which you fill fields makes no difference. Shopier is the exception: you do not generate the webhook signature token — it comes back inside the response when the subscription is created. So the subscription comes first and the token reaches you afterwards. Trying to reverse that order means hunting for a value that does not exist yet.

The personal access token, on the other hand, is obtained in advance from the developer portal and is enough on its own to establish the connection. The signature token is only for verifying incoming notifications; if you do not use them it can stay empty.

Not losing orders while selling through social media

Most sellers on Shopier sell through Instagram and WhatsApp, with Shopier handling payment and orders. The model grows fast but hits a wall: once you also open on marketplaces, keeping track of which order came from where — and how much stock is really left — gets hard.

The connection gathers your Shopier orders into the same list as your marketplace orders and manages stock from a shared pool. A sale on one channel drops stock on the others, and price updates happen in one place.

The scope is orders, stock and prices. Creating new product records in Shopier is not done through this connection; you keep managing products from the Shopier panel.