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.

Most Arcus messages are protective. They usually mean the record needs missing setup, permission, approval, payment, inventory, connector, or accounting-period review before the action is safe.

Read The Message In Context

Open the record detail page and review status, banners, tabs, and related records before retrying the action.
Order detail page with customer context, status badges, action buttons, addresses, documents, progress, and line items
Use this order:
  1. Read the exact message.
  2. Confirm the selected entity and environment.
  3. Confirm your role and location access.
  4. Check the record status.
  5. Check required setup.
  6. Check related workflow state, such as payment, invoice, fulfillment, return, approval, connector, or accounting period.
  7. Fix the cause and retry once.
  8. If it still fails, capture the message and send the record link to an admin or support owner.

Common Messages

Message patternLikely causeWhat to do
Permission deniedYour role cannot perform the action.Ask an admin to review role, entity, and location access.
Missing required fieldThe record is incomplete.Fill in the highlighted customer, address, product, date, account, quantity, or method field.
Cannot edit locked recordThe record has payment, invoice, fulfillment, return, or accounting history.Use correction, refund, return, void, credit, or reversal workflow.
Approval requiredA rule requires manager review.Submit for approval or ask an approver to review the record.
Accounting period closedThe posting date is locked.Use an open date, request reopen, or follow period close policy.
Payment method unavailableSaved method is expired, unverified, removed, or connector is unhealthy.Add or verify a method, use another method, or check Stripe setup.
ACH still processingBank payment has not settled yet.Wait for settlement before risky fulfillment.
Label purchase failedShipping data, address, customs, package, carrier, or Shippo setup is invalid.Review address, package dimensions, weight, customs, carrier service, and Shippo health.
No inventory availableStock is short, reserved, in another location, or not received.Review inventory, backorders, transfers, receiving, purchasing, or manufacturing.
Connector disconnectedExternal service is not connected or credentials expired.Open Integrations and reconnect or test the connector.
PDF unavailableDocument generation is blocked or no customer-safe document exists.Confirm document type, posted state, and customer-facing data.

Disabled Buttons

Disabled buttons are often clearer than errors. Hover or read nearby banners when available, then check:
  • Status: draft, open, posted, paid, fulfilled, cancelled, archived, or voided.
  • Permissions: role and location access.
  • Required setup: account, product, address, terms, tax, connector, or printer.
  • Approval: order, PO, bill, journal entry, or period close approval.
  • History: payment, invoice, shipment, return, refund, credit, or GL activity.

Connector Errors

Connector errors need two checks: connection health and real workflow data.
Integrations dashboard with connector cards, status counters, sandbox and production indicators, and error counters
Examples:
  • Stripe can be connected, but a card can still require authentication.
  • Shippo can be connected, but an address or package can still fail carrier validation.
  • PrintNode can be connected, but the workstation client or printer can still be offline.
  • Plaid can be connected, but a bank can require login refresh.
  • Shopify can be connected, but webhooks or mapping can still fail.
  • AvaTax can be connected, but tax can fail because address or tax-code setup is incomplete.

When To Escalate

Escalate when:
  • A customer could be charged incorrectly.
  • Inventory would move incorrectly.
  • A shipment label would be purchased twice.
  • Accounting would post into the wrong period.
  • A connector appears to affect production unexpectedly.
  • A message mentions data isolation, access, or unauthorized action.
  • The same error repeats after setup has been corrected.

Common Statuses Across Arcus

Understand common order, payment, fulfillment, return, purchasing, accounting, and connector statuses.

Order Exceptions and Recovery Choices

Recover from holds, approvals, backorders, overcharges, marketplace blocks, and failed auto-pack.

Connector Troubleshooting

Recover authorization failures, webhook issues, sync delays, mode mismatch, and stale external records.

Period Close

Understand blocked posting, reopen requests, force close, and accounting-period rules.