Sales store connections
Sales has several ways to work with a store. Start in the Store step of Sales setup. For platforms with a connection form, setup opens the selected provider under Sales → Integrations and provides a way back.
A saved connection proves only the access and capabilities reported for that connection. Activation separately checks whether the current Sales service supports the selected store mode. If setup reports Selling opens soon, that mode cannot be activated yet, even when credentials were accepted.
Website and Shopify connections
| Connection | Setup and scope |
|---|---|
| Public website, on any platform | Save the public website address. Verification reads the site. The assistant can answer from those pages and provide an observed link to checkout there; it cannot read private orders or guarantee stock. |
| Shopify store link | Provide the store address for public catalog and checkout links. This does not install the Shopify app or grant private stock and order access. Selling depends on store-mode availability. |
| Shopify app | Authorize the store through the Shopify connection flow. The app supplies permitted catalog, inventory and order access. Return to setup to verify the selected store and launch requirements. |
Saving a public URL does not prove ownership of the site. The store's own checkout remains responsible for the final price, availability and payment in link-based modes. A website path change may change the source the assistant reads, so verify the saved address after edits.
Commerce platform connections
Enter credentials only in the authenticated provider form. Use a provider account authorized to grant the requested access; never put credentials in chat, documentation or a public URL.
| Platform | Connection requirements | Current boundary |
|---|---|---|
| WooCommerce | Store URL and REST API consumer key and secret. | The form verifies the connection. It does not provide a native Sales commerce runtime; check whether public website mode meets your needs. |
| Adobe Commerce / Magento | Store URL and the integration credentials requested by the form; the supported authentication mode depends on the store configuration. | Catalog, cart, shipping and coupon support depend on the configured store. Paid-order processing and order-status synchronization require separate workspace readiness; connecting does not approve payment launch. |
| VTEX | Account name, app key, app token, sales channel and affiliate settings. | Commerce integration supports catalog, shipping, checkout/order and status work within the approved configuration. Store-mode and launch checks still apply. |
| SAP Commerce Cloud | API URL, base site, OCC path and OAuth client; additional token/public-store settings as required. | Credential verification and catalog import are available. Shipping and voucher checks are validation-only; paid-order submission, order-status synchronization, invoice and refund writeback are not supported by the current Sales integration. |
| Uappi | Store URL, API key and secret key. | Connecting initially saves credentials. Shipping, paid-order submission and order-status synchronization need explicit workspace enablement and verification. Coupon validation, invoice and refund writeback are unsupported. |
| Nuvemshop / Tiendanube | Use the Nuvemshop sign-in/install path when available, or the form for an existing store ID and authorized access token. | Connecting initially saves credentials and can support catalog import. Paid-order submission and status synchronization require workspace verification. Shipping quotes, coupon validation, invoice and refund writeback are unsupported. |
Nuvemshop access tokens come from an authorized partner-app installation; do not look for an ordinary merchant screen that generates a new API token. If the install path is unavailable, follow its setup message or contact Hexagon rather than sharing credentials by email.
The catalog, payment and fulfillment capabilities are independent. For example, a successful product import does not establish that Hexagon can obtain a delivery quote or write an order back to the platform.
Additional providers and unavailable platforms
Intelipost can supply shipping quotes in a separately configured commerce implementation. It is a quote provider, not a store catalog or a standard Sales connection card. Confirm its availability and required shipping checks with Hexagon for the workspace.
Tray, Loja Integrada, Wake, Linx, BigCommerce, Yampi, Magazord and other unlisted platforms currently have an availability-request path for a native connection. Being named there does not mean a native adapter is active. Public website mode is a separate option and remains subject to its own availability and verification.
Verify and maintain the connection
After connecting, check the reported store identity and connection test. Where the provider exposes catalog sync, inspect the result and a representative product rather than assuming a saved credential imported the store. Then return to Sales setup and resolve its readiness checks.
When credentials expire or provider permissions change, use the connection's test/reconnect controls and verify again. Review active Sales work before disconnecting. Revoking provider access and deleting already stored business data are separate actions; see Privacy and your data.