Skip to main content

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.

​
Configure Shippo For Shipping

  1. Open Integrations.
  2. Open the Shippo card.
  3. Confirm sandbox or production mode.
  4. Enter the Shippo API token for the matching environment.
  5. Configure the webhook signing secret if tracking webhooks are used.
  6. Save and test the connection.
  7. Test a rate or label workflow from fulfillment before using production labels.
Configure Shippo modal with environment selection, masked API token, webhook signing secret, webhook URL, and setup steps

​
Shippo Workflows

  • Rate shopping: gets carrier services and prices when shipping data is complete.
  • Label purchase: buys parcel labels from selected carrier services.
  • Tracking: receives or syncs tracking updates for shipped packages.
  • Void or refund: sends label cancellation requests where supported.
  • Freight support: supports Shippo-backed freight rate shopping where available.
Label failures are often setup plus data problems A valid Shippo token is only one requirement. Ship-from address, ship-to address, package dimensions, weight, carrier service, shipping rules, and product shipping data can all block label purchase.

​
Configure PrintNode For Printing

  1. Open Integrations.
  2. Open the PrintNode card.
  3. Paste the PrintNode API key.
  4. Save and test the connector.
  5. Install and run the PrintNode client on each workstation that owns printers.
  6. Open Printing settings and choose default label and document printers.
  7. Test printing a label, packing slip, or pick list before relying on auto-print.
Configure PrintNode modal with sandbox and production environment controls plus masked API key
PrintNode requires a running workstation client The connector can be healthy while a specific workstation still cannot print. Confirm the PrintNode client is running, the printer is online, and the user has selected the correct default printers.

​
Common Blocks

  • No rates returned: check Shippo mode, addresses, package dimensions, weight, and allowed carrier tokens.
  • Label purchase fails: review Shippo test result, carrier service, customs or freight requirements, and payment status.
  • Tracking never updates: confirm the tracking webhook setup and recent Shippo activity.
  • Void stays pending: verify the webhook events and carrier refund timing.
  • No printers appear: confirm PrintNode is connected and the local client is running on the printer host.
  • Wrong printer receives labels: review entity printer defaults and the current user’s printing preferences.
Test shipping and printing together A good fulfillment test buys or previews a label, prints the label, prints the packing slip, and confirms the package status updates correctly.

Connector Dashboard

Review connector mode, health, masked credentials, tests, logs, sync dashboard, and safe reconnect steps.

Shipping Labels

Buy labels, void labels, track shipments, and handle carrier errors.

Printing Setup (PrintNode)

Connect printers for labels, packing slips, and warehouse documents.

Shipping Rules

Configure Shippo, carrier defaults, shipping rules, freight routing, PackPilot, scanners, and PrintNode printing.

Pack with Arcus

Use package cards, suggested boxes, and serial capture.

System Operations Settings

Configure PrintNode printing, sidebar module visibility, and system or custom tags.