Marketplace Connectors

​

Use Integrations For Connector-Owned Channels

Custom sales channels are managed from Sales Channels settings. Connector-owned channels, such as Shopify, Amazon, and eBay, are managed from Integrations because the connector controls order import, sync, status, and disconnect behavior.

​

Shopify Connection Flow

1. Open Integrations.
2. Open the Shopify card.
3. If connecting for the first time, enter the store handle or myshopify.com domain.
4. Continue to Shopify and grant the requested access.
5. After returning to Arcus, open Configure Shopify.
6. Review Connection, Sync Settings, Mapping, Webhooks, Logs, and Accounting tabs.
7. Run a test sync or small order workflow before relying on production volume.

​

Shopify Configure Tabs

• Connection: connection health, mode, last sync, reconnect, and disconnect.
• Sync Settings: controls which Shopify data moves and how frequently.
• Mapping: connects Shopify data to Arcus records and locations.
• Webhooks: verifies real-time events from Shopify.
• Logs: shows recent connector activity and failures.
• Accounting: future or connector-specific accounting context when available.

​

Amazon And eBay Setup

Amazon and eBay use connector cards with credentials, environment selection, setup guides, test actions, and logs. Their credentials and required permissions come from each external marketplace account.

• Amazon: seller identity, marketplace, application credentials, refresh token, region, and FBA ship-from setup.
• eBay: application credentials and seller refresh token from the OAuth consent flow.
• Mode: use sandbox keys for test entities and production keys for live selling.
• Logs: use connector logs to review import, fulfillment, and sync failures.

​

Use Sync Dashboard For Marketplace Troubleshooting

The Sync Dashboard helps admins review recent marketplace activity across connectors. Use it when orders did not import, fulfillment did not push, or listing/report data seems stale.

​

Marketplace Drift And Missing SKU Review

Marketplace data can drift when a listing, SKU, inventory quantity, fulfillment, or price changes outside Arcus. Use connector logs, product mapping, and listing performance to decide whether Arcus or the marketplace should be corrected.

• Missing SKU: review whether the connector should auto-create a placeholder product or block for manual mapping.
• Inventory drift: compare Arcus available inventory, marketplace available inventory, open orders, transfers, and recent sync activity.
• Price drift: compare product price, pricing rules, marketplace listing price, and any marketplace-side override.
• Fulfillment drift: confirm whether tracking was pushed from Arcus or updated directly in the marketplace.
• Deleted external record: clear stale mapping only after confirming the marketplace record is truly gone.

​

Common Blocks

• Orders do not import: check connector health, sync logs, store permissions, webhook status, and whether the order is inside the configured sync scope.
• Fulfillment does not push back: review fulfillment sync settings, tracking data, carrier/service mapping, and external order status.
• Listings look unmapped: review product SKUs, marketplace listing mapping, and external SKU consistency.
• Wrong channel defaults apply: review Sales Channels settings after confirming the connector is healthy.
• Production marketplace connected to sandbox: disconnect or reconnect with the correct environment and test before continuing.

​

Related Articles