Skip to main content

Merchant Connectors

Merchant Connectors let a store owner connect another commerce platform to eshopOS and bring structured store data into the current store without rebuilding everything manually.

This feature is not a marketplace sync and it is not a generic API playground. It is a merchant migration and import workspace built for store-to-store transfer into eshopOS.

What a Connector Is​

A connector links one merchant store to an approved external commerce platform. It tells eshopOS:

  • which external platform is connected
  • which external shop or account is linked
  • which permissions were granted
  • when the connection was last active
  • what import activity the merchant has started

Every connector belongs to one store. A connector for one store cannot be reused by another store.

What Connectors Are For​

Use connectors when a merchant wants to:

  • move products into eshopOS from another platform
  • bring collections or categories across
  • reuse external product media
  • carry inventory structure forward
  • bring warehouse/location structure forward
  • reduce manual migration time during onboarding

What Connectors Are Not​

Connectors are not the same thing as:

  • public API keys
  • OAuth apps created by developers for third-party access into eshopOS
  • payment providers
  • shipping providers
  • marketplace channels like Amazon or eBay

Those are separate integration types with different trust models and different operational risks.

How the Connector Flow Works​

The connector flow has four stages.

1. Configure​

The merchant opens the connector workspace, chooses a provider, and starts the connection flow. Shopify uses OAuth. BigCommerce and Squarespace can use provider API credentials.

2. Authorize​

The provider confirms the merchant's authorization and returns the connection result to eshopOS.

3. Inspect​

Once connected, the merchant sees the external account name, the external domain, the granted scope set, and the current connector state.

4. Import​

Import activity uses the connector to bring approved external resources into eshopOS records. A failed import attempt does not mean the merchant must reconnect the provider.

Store Isolation Model​

Connector security depends on strict tenancy boundaries.

  • each connection belongs to the store that started it
  • provider credentials are not shown back to dashboard users after setup
  • connector status is visible to the merchant
  • import activity stays within the selected store context

This model prevents one merchant from seeing or using another merchant’s external platform connection.

Connector Status Meanings​

Live​

The provider account is connected and eshopOS has a valid install record for that store.

Inactive​

The provider is not connected, was disconnected, or the setup has not been completed yet.

Failed​

The connection attempt or callback completed with an error and needs to be retried.

Why Connectors Are Separate From Developer Apps​

eshopOS already contains developer OAuth and public API tooling. That tooling is for outside applications calling into eshopOS.

Merchant connectors solve the opposite problem: eshopOS calling out to an external platform on behalf of a merchant store.

That difference matters because connectors are merchant-controlled import tools, while developer apps are public integrations calling eshopOS with merchant-approved credentials.

Current Scope​

Current connector capabilities include:

  • connection status tracking
  • merchant-authorized provider connections
  • import activity for supported provider resources
  • warehouse-aware inventory import for supported providers
  • retry-friendly import review when a run needs attention