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.
What Customers See
After login, customers land on a portal dashboard branded for the seller. The dashboard summarizes open orders, unpaid invoices, recent shipments, account balance, store credit notices, quick actions, recent orders, and upcoming deliveries.
Customer Portal Navigation
The portal sidebar is organized around customer self-service. Customers can move between operational records without entering the internal Arcus workspace.
- Dashboard: open work, balances, recent orders, deliveries, and quick actions.
- Orders: order history, status, fulfillment state, payment state, totals, and PDFs.
- Quotes: quote list and quote detail, including customer acceptance when the quote is eligible.
- Shipments: package and tracking visibility.
- Returns: customer-safe RMA history, status, return-to address, tracking, and refund summary.
- Invoices and Payments: unpaid invoice review and customer payment entry.
- Addresses: customer-managed billing and shipping addresses when enabled.
- Payment Methods: customer-facing card visibility and supported method actions.
- Documents: customer-safe PDFs and uploaded documents that belong to that account.
- Profile: account identity and contact details exposed to the customer.
How Customers Log In
Customers use the portal login flow, not staff login. The login page asks for the customer email and account number, then sends a verification code or portal link. On success, the browser stores a portal session token and the portal loads only that customer’s account data.
Staff Setup Checklist
- Open Settings, then Sales Channels and Customer Portal.
- Confirm the customer portal is enabled for the entity.
- Review portal branding, support contact details, payment options, tracking visibility, address management, and token expiration.
- Open the customer account and confirm portal access is enabled for that account.
- Confirm the customer’s email and account number are correct before they request a code.
- Send a public order, invoice, quote, payment, or tracking link when the customer needs one-off access without full portal login.
What Customers Cannot See
Portal pages are account-scoped. Customers should not see internal costs, margins, GL entries, internal notes, staff-only documents, other accounts, other entities, or staff user data. If a customer reports seeing the wrong account, treat it as a security issue and stop until the account, token, and entity scope are verified.
Common Blocks
- Customer cannot log in: confirm portal is enabled, the account has portal access, the email is correct, and the account number matches.
- Verification code never arrives: review email delivery, spam filtering, and the account email on file.
- Order or invoice is missing: confirm the record belongs to the same customer account and entity.
- Payment is unavailable: review payment settings, allowed portal payment methods, invoice balance, and Stripe connector health.
- Customer cannot manage a card: some payment-method actions may still require staff handling depending on current portal capabilities.
- Customer asks for a return: send the customer-facing RMA link when they need to start a return, or have them open portal Returns when they need to track an authorized RMA.