Documentation Index
Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
Use this file to discover all available pages before exploring further.
Use the Integrations Dashboard
The Integrations page groups connected services by job. It shows how many connectors are connected, which ones are sandbox or production, and whether any connector currently has errors. Each service card has actions for configuration, testing, and log review.

Connector Types
- Stripe: card payments, saved methods, payment failures, refunds, disputes, and payouts.
- AvaTax: address-aware tax calculation, tax document strategy, marketplace routing, and tax error recovery.
- Shippo: shipping labels, carrier rates, tracking, label voids, and freight rate shopping through Shippo-supported flows.
- PrintNode: direct printing for labels, packing slips, pick lists, and fulfillment workstations.
- Shopify: marketplace order import, fulfillment sync, tracking updates, and listing-related context.
- Amazon and eBay: marketplace setup surfaces for order and listing connectivity when enabled.
- RingCentral: phone and communication logging when configured.
- Plaid: bank feed and bank-account workflows used by reconciliation and some payment workflows.
Before You Configure a Connector
- Confirm whether you are in sandbox or production.
- Identify who owns the external service account.
- Confirm the connector has the minimum permissions Arcus needs.
- Prepare a small test workflow, such as a test payment, tax quote, label preview, print test, or marketplace order import.
- Record what changed and who should verify the result.
Use Test and Log Actions
After a connector is configured, use the test action to confirm Arcus can reach the external service. Use the log action when a workflow fails or a sync appears stale.
- Test: confirms the current connector setup can authenticate or reach the service.
- Log: shows recent connector activity and failure context.
- Last sync: helps decide whether a marketplace or connector is current.
- Error count: tells operators whether a connector needs attention before work continues.
Common Blocks
- Connector says Not Connected: configure credentials or reconnect through the service-specific setup flow.
- Test fails: check mode, permissions, revoked keys, external service status, and whether credentials were rotated.
- Marketplace sync is stale: review last sync, connector log, external app permissions, and whether the store is connected to the right entity.
- Payment method entry fails: review Stripe setup and browser access to secure Stripe fields.
- Labels fail: review Shippo setup, shipping settings, addresses, package dimensions, and carrier service.
- Printing fails: review PrintNode setup, workstation client status, default printers, and user printing preferences.
- Tax fails: review AvaTax status, company code, address validation, product tax code, and marketplace tax routing.

