Marketplace Connectors

​

Use Integrations For Connector-Owned Channels

Open connectors from the deck: open Settings, then under Integrations choose Connectors. The breadcrumb reads Settings > Integrations > Connectors. You need the settings.view permission to open the page. The page title is Integrations. You also arrive here from the command palette, and from the places that need a connection before they can work: a product’s empty marketplace listings, the Marketplace Sync Console, Sales Channels settings, Card Readers when Stripe is not connected, the bank deposit and marketplace payout screens, and the connector warning banners. The Shopify and eBay connection flows return you to this page after you approve access. 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.

​

What You See On The Page

The tiles at the top count your connected services: Connected, Sandbox, Production, and Errors. A tile shows two dashes while the page loads or when it could not read your integrations. When the read fails, the page says “Which services are connected is unknown because this read failed. Nothing is shown as disconnected, and nothing has been changed.” with a Retry button, instead of showing every card as not connected. The cards sit in sections: Two buttons sit beside the title: Sync Dashboard and Marketplace Sync Console, covered below.

​

Connector Card Status

Each card shows one status badge and, once connected, a mode badge. A connected card also shows its masked credentials (stars, never the value), the shop or environment for Shopify and eBay, Last sync, and the most recent sync activity. The card actions are Configure, Test, Log, and Disconnect (or Remove).

​

Who Can Change What

Opening the page needs settings.view. Connecting, saving credentials, changing sync settings, reconnecting, disconnecting, removing a connector, and pushing inventory all need settings.edit. Pressing Sync now on a payout sync needs accounting.post, and Reconcile Stripe data needs settings.edit. Only the server checks these: the buttons show to everyone who can open the page, and a refused action shows the refusal as a red message.

​

Credential Connectors: Stripe, AvaTax, Shippo, PrintNode, Amazon

Click Configure on the card. The dialog is Configure followed by the connector name.

1. When the connector is already saved, a banner reads Connected (or Saved (inactive)) with its last activity, or “No activity yet”. Reconnect lets you paste new credentials.
2. Choose the Environment, Sandbox or Production. Choosing Production shows “Production mode will process real transactions”. Switching environment asks you to confirm: “Switching to production will clear your saved credentials. They don’t carry over between environments.” Choose Switch to the new mode or Cancel.
3. Fill in the Credentials. Saved secrets show as masked, and each field has a helper line and a link to the provider’s page that holds the value. Stripe takes a Secret Key, an optional Publishable Key, and a Webhook Signing Secret. AvaTax takes an Account ID, License Key, and Company Code. Shippo takes an API Token and an optional HMAC Signing Secret that you leave blank unless Shippo provisions one. PrintNode takes an API Key. Amazon takes a Seller ID (Merchant Token), Marketplace ID, LWA Client ID, LWA Client Secret, Refresh Token, and Region, plus an FBA Inbound Settings ship-from name and address that Amazon needs to create inbound shipments.
4. Use Test connection to check the credentials before you save. The dialog says Connection successful or Connection failed.
5. Click Save Changes. Arcus shows “Connector created” for a new connector or “Connector updated” for an existing one.

For providers that send events to Arcus, the dialog also has a Webhook Setup guide that lists the events to subscribe to in the provider’s dashboard. Stripe uses the Webhook Signing Secret you save. Shippo does not sign its events, so you generate a URL token in Arcus instead: use Generate (or rotate) and then Copy webhook URL. The token is shown only once (“Webhook token generated. Copy the full URL now; the token is shown only once.”). Test webhook sends a test event, and the dialog shows when a webhook was last received or “No webhooks received yet”. On Stripe, Reconcile Stripe data checks your customers and saved payment methods against Stripe and reports “Reconcile complete” with how many customers it checked, found stale, and rebuilt, and how many payment methods it deactivated. On the card, Test runs the same connection check and shows “connection OK” with the response time, or the provider’s reason followed by “Check the key and resave.” If the request itself fails you see “Test failed due to network error.” Log opens the Sync Log for that connector. Disconnect (or Remove) asks “Are you sure you want to remove the connector? This will delete all stored credentials.” and then shows “Connector removed”. Removing deletes the stored credentials only. You can add them again at any time.

​

Shopify Connection Flow

1. Open Settings > Integrations > Connectors.
2. Click Connect on the Shopify card. The Connect Shopify dialog first asks you to choose a method: Recommended Shopify App (OAuth), which connects in one click through Shopify and suits most stores, or Custom App (Admin API), which uses your own custom app’s credentials (follow How to set up your app).
3. For the app method, enter the store handle or myshopify.com domain, for example “mystore” or “mystore.myshopify.com”. An invalid store shows “Enter a valid Shopify store.”
4. Click Continue to Shopify and approve the requested access. Nothing is saved until you approve and the connection completes, and Arcus registers real-time webhooks for orders, fulfillments, products, and inventory.
5. When you return, Arcus shows “Shopify” and the store name followed by “connected”. If you started the install from your Shopify admin, a Finish connecting Shopify dialog first asks whether to connect that store to this entity and says orders, products, inventory, and customers will sync with the entity you are working in. Choose Connect store. The link stays valid for 24 hours, and closing the dialog is safe.
6. Open Configure on the Shopify card.
7. Review the Connection, Sync Settings, Mapping, Webhooks, Logs, Accounting, and Tax tabs.
8. Run a test sync or small order workflow before relying on production volume.

If the connection does not complete, Arcus shows one of these: “The Shopify connection link expired. Start the connection again.” (and the matching “was not valid” and “was already used” messages), “Shopify did not complete the connection. Try again in a moment.”, “This Shopify install was started in a different Arcus environment. Start the connection again from this environment app.”, or “Shopify connected but the install could not be finished. Try again, and contact support if this persists.” When the claim itself fails you may see “This connection link expired. Restart the install from your Shopify admin.” or “This store was already connected.” To disconnect, use Disconnect Shopify on the card or the Connection tab. The confirm names the store and reads “Future orders will not import; existing data is preserved.” Arcus then shows “Shopify disconnected”.

​

Shopify Configure Tabs

• Connection: connection health, mode, last sync, and the Reconnect via OAuth and Disconnect Shopify actions. Reconnect re-authorizes through Shopify, for example after a token expires or when you need to grant new permissions. It also maps your Shopify locations to Arcus locations (Save mapping), which inventory sync needs before anything can push.
• Sync Settings: controls which Shopify data moves. See Shopify Sync Settings.
• Mapping: decides which Arcus product each Shopify listing pushes inventory into. It links to the unmapped listings inbox, the inventory drift review, the Bulk SKU Mapper, and Bulk Import Shopify Products, which pulls every Shopify product into Arcus and follows your Unknown SKU policy.
• Webhooks: lists each webhook subscription with when it was Registered and Last received, and lets you re-register them. Arcus shows “Webhooks re-registered” when it works and “Re-register failed” with a reason when it does not.
• Logs: shows recent connector activity and failures under Recent sync events, with a retry count. It reads “No sync events yet.” until a webhook or push happens. Refresh reloads it, and Re-sync retries a failed or partial event: Arcus shows “Re-sync succeeded”, “Re-sync partially succeeded (see the row)”, or “Re-sync failed”. Re-sync works only on a failed event that is not a duplicate.
• Accounting: where payouts and disputes from the platform post: Clearing GL, Bank deposit GL (fallback), Fee expense, and Dispute fee account, plus a Dispute escalation email, an SMS phone (chargeback alerts), a Slack webhook URL (chargeback alerts), Auto-reconciliation, and Payout sync frequency. Arcus confirms a save with “Saved”. Saving these fields needs the settings.edit permission. Only the server checks it, so the fields stay editable on the screen, and a refused save shows “Save failed” followed by the refusal.

​

Run A Payout Sync Now

Under Manual sync on the Accounting tab, click Sync now to pull payouts right away. It runs even when the next scheduled poll is not due yet, and it works when the payout sync frequency is set to manual only. Scheduled polling keeps its own cadence. Sync now needs the accounting.post permission. Only the server checks it, so the button shows for everyone who can open the tab.

• “Sync complete” followed by the number of payouts processed means the sync ran.
• “Sync skipped” followed by a reason in plain words means Arcus did not run it, for example because the connector is not configured.
• “Sync failed” followed by a reason means the sync did not run. The reason can be the platform or connection returning an error, so check the connection and logs, or it can be a refusal because your role lacks accounting.post, which is not a platform error.

​

Shopify Sync Settings

Each switch saves as soon as you change it, and takes effect on the next relevant event. If a save fails you see “Failed to save” followed by the setting name and the reason. Below the switches:

• On-demand order import: Sync orders now imports one batch (it stops after about 30 seconds and can be run again) and shows “Imported” followed by the number of orders and how many were skipped. Backfill all orders imports every eligible order in the background. Choose the scope: Open + unfulfilled orders only (recommended) or Full history (excluding already-imported), which stays off until your Shopify app is approved for full order history.
• Import orders since and Order lock date: orders dated before the lock date are not imported automatically. To pull older orders, use Sync orders now with an explicit since date.
• Capture order payment when: When the order is created (recommended) books whatever Shopify reports collected, When the order is fully paid holds the money until Shopify marks the order paid, and When the order is fulfilled holds it until fulfillment (accounting only).
• Order status on import: Open (recommended) lands orders ready to fulfill, and Draft (review first) lands them as drafts you promote to open.
• Unknown SKU policy: what happens when an order references a SKU Arcus does not have. Reject the order (file as needs-review), Auto-create a placeholder product, or Link to the entity placeholder product.
• Inventory drift resolution: who wins when the four-hourly check finds Arcus and Shopify disagree on a quantity. Arcus wins (recommended) corrects Shopify, Manual review files each drift for a person to resolve, and Shopify wins (migration only) pulls Shopify quantities into Arcus while Shopify is still your stock ledger. The Inventory drift threshold (%) sets how large a gap must be to count.
• Inventory safety buffer (units): held back from every quantity pushed to Shopify, never below zero. Push all listings now pushes the current available quantity of every mapped listing, and shows “Pushed inventory for” followed by the number of products.
• Default location for imported orders and Default customer account: where imported orders land when they name no location, and the fallback account when no customer can be resolved. Leave the account empty to create customers from the Shopify order.
• Import defaults: how new customer accounts are typed (Auto (recommended), Always Individual, Always Business), their pricing level and payment terms, the origin type, the order pricing level and payment terms, and the Due date (Not set or From payment terms). Verify shipping addresses automatically checks each imported address.

​

Shopify Tax Tab

The Tax tab holds Post imported orders to AvaTax. When on, every fully paid imported Shopify order is filed as a committed AvaTax document carrying the tax Shopify actually collected, so your monthly AvaTax filing covers marketplace sales. Tax that the marketplace remits itself is excluded. It needs a connected AvaTax account. The list under it shows each order’s Collected tax, the amount excluded because the marketplace remits it, what AvaTax would have calculated, and the Delta. Turn on Exceptions only to show orders where the collected and calculated tax differ by more than two cents. The filed amount is always what Shopify collected.

​

Shipping Method Mapping

On the Shopify Mapping tab, and on the Shipping Methods tab of the Amazon and eBay dialogs, the shipping methods section maps each shipping method the platform sends to an Arcus method and a Shippo service. It shows “No shipping methods seen yet” until an order arrives. Real carrier services (FedEx, UPS, USPS) are recognized automatically and shipped as paid. Map a method to Local Pickup (no label) when it needs no label, set a Default for unmapped methods, or turn on Strict: hold unmapped orders for review so an order with no mapping waits for you instead of using the default.

​

Amazon And eBay Setup

Amazon uses a credentials card, described above. eBay connects through eBay’s own consent screen, so you never paste a key.

• Amazon: seller identity, marketplace, application credentials, refresh token, region, and FBA ship-from setup.
• eBay: click Connect on the eBay card, choose Sandbox or Production (Production connects your live store and imports real orders), and click Continue to eBay. Nothing is saved until you approve on eBay. Order import, fulfillment sync, returns, and payouts then run automatically, and you see “eBay connected” and a banner that says “Orders now import automatically.” with a pointer to Configure. eBay’s consent has to be renewed about every 18 months with Reconnect. To disconnect, use Disconnect eBay: the confirm reads “Disconnect this eBay account? Future orders will not import; existing data is preserved. You can reconnect at any time.” and Arcus then shows “eBay disconnected”.
• eBay Configure: the dialog has Connection, Sync Settings, Mapping, Shipping Methods, Accounting, and Logs tabs. Its Sync Settings carry the same Unknown SKU policy and Inventory drift resolution choices as Shopify, with Arcus wins (recommended) or Manual review, and its Connection tab has Reconnect via OAuth.
• Mode: use sandbox keys for test entities and production keys for live selling.
• Logs: use connector logs to review import, fulfillment, and sync failures.

If the eBay connection does not complete, Arcus shows one of these: “The eBay connection link expired. Start the connection again.”, “eBay did not complete the connection. Try again in a moment.”, “eBay is not set up for this environment yet. Contact your administrator.”, or “Could not start eBay connection”.

​

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. The Sync Dashboard button opens a window with All, Inbound, and Outbound filters over the latest sync activity of every connector, and “Failed to load sync log” appears if the log cannot be read.

​

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.

​

What Changes Elsewhere

• Orders and customers: imported marketplace orders create Arcus orders and, depending on your settings, new customer accounts and stock reservations at the default location.
• Coupons: when a Shopify order is imported with a coupon, Arcus recalculates that coupon’s use count from the orders that carry it rather than adding one, so the count stays accurate when an order is imported again or edited.
• Inventory: with push on, stock-changing events in Arcus update Shopify and eBay. With pull or “Shopify wins”, Shopify’s quantities become Arcus stock adjustments.
• Accounting: payouts and disputes post to the accounts on the Accounting tab, and tax can be filed to AvaTax from the Tax tab.
• Customers: fulfillment tracking is sent back to the platform, and the platform may email the customer if you turn that on.
• Audit trail: connecting, saving, testing, disconnecting, removing, and re-syncing are recorded in the Audit Log.
• Other open sessions: when another administrator changes a connector, your cards refresh.

​

Messages You May See

​

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