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.

Open Company Settings

  1. Open Settings.
  2. Choose Entity Settings.
  3. Use the Company group in the left navigation.
  4. Review Business Profile, Branding, and Locations.
Entity Settings Business Profile page with entity name, environment, primary entity, website, email, business address, icon, and logo

Business Profile

The Business Profile is the starting point for entity identity. It controls what users see inside Arcus and what customers see on documents, emails, and shipping workflows.

  • Entity Name: the business name shown in the app and customer documents.
  • Entity Code: the short internal code used to identify the entity.
  • Environment: tells users whether they are working in sandbox or production.
  • Primary Entity: controls the entity users land in first when they have access to more than one entity.
  • Website URL: used as the company website reference where supported.
  • Accounting Email: the accounting or finance email used by payment and accounting workflows.
  • Business Address: the default business origin used by shipping, tax, and location setup.
  • Icon and Logo: branding used in the app and on customer-facing documents.
Confirm the environment before working Sandbox is for testing and training. Production is live. Before creating real orders, buying labels, sending emails, or taking payments, confirm the environment badge and active entity are correct.

Business Address

The business address is more than a mailing address. Arcus uses it as a default origin for connected workflows. Saving the business address can also keep the default location address aligned so shipping and tax calculations have a consistent origin.

  • Shipping labels may use this address when a more specific ship-from location is not selected.
  • Tax and address validation can use it as the company origin.
  • New locations and fallback workflows may rely on it when no other origin is configured.
  • Customer documents may show company contact or address details depending on document settings.
Use a real commercial address For shipping and tax, use the physical business or warehouse address that carriers and tax services should treat as the origin. Avoid vague office-only addresses if orders ship from a warehouse.

Branding

Branding settings control how Arcus presents the business visually. Use this area to keep documents, portal pages, and customer-facing emails consistent with the company.

  • Upload a clean logo with enough resolution for PDF documents.
  • Use brand colors that preserve readable text contrast.
  • Preview the result before sending customer-facing documents.
  • Update branding in sandbox first if you are unsure how it will render.
Entity Settings Branding page with company branding controls and preview

Locations

Locations represent warehouses, receiving areas, holding areas, writeoff areas, stores, offices, marketplace locations, dropship locations, and overflow areas. Location settings decide where stock is received, where orders can sell from, and what address is used for shipping.

Entity Settings Locations page with location list, type badges, default marker, and Add Location button
  • Name and Code: how the location appears in dropdowns, reports, and inventory views.
  • Type: the operational role of the location, such as warehouse, holding, writeoff, marketplace, dropship, or overflow.
  • Sellable: whether stock at the location can be used for sales.
  • Ships From: whether labels can use this location as a shipping origin.
  • Receives: whether purchase orders or manual receiving can use this location.
  • Default: the fallback location for workflows that need a location and do not have one selected.

Add or Edit a Location

  1. Open Entity Settings.
  2. Select Locations.
  3. Choose Add Location or edit an existing row.
  4. Enter a name, code, type, and address.
  5. Confirm whether the location is sellable, ships from, and receives stock.
  6. Set the location as default only if it should be the normal fallback.
  7. Save, then test the workflow that depends on the location.
Location type chooses sensible defaults When you change the location type, Arcus adjusts the default behavior for sellable, ships-from, and receiving flags. Review those flags before saving because the correct answer depends on how your team uses the space.

What to Test After Changes

  • Business address: create a test label or rate preview and confirm the origin address.
  • Logo or branding: generate a quote, order confirmation, invoice, or packing slip preview.
  • Default location: create a draft order and purchase order and confirm the starting location.
  • Receiving location: open receiving and confirm the location appears where expected.
  • Sellable flag: confirm inventory from that location is or is not available for sales as intended.

Common Blocks

  • Save is disabled: check required fields like entity name or address parts.
  • Shipping labels use the wrong address: review the order location, ship-from location, and business address.
  • A location is missing from receiving: confirm the location is marked as receiving.
  • A location is missing from sales: confirm it is marked sellable and has available stock.
  • Branding looks wrong on a PDF: upload a cleaner logo and regenerate a preview document.
  • Users land in the wrong entity: review Primary Entity and each user’s entity membership.

Settings Overview

Understand the admin surfaces, settings groups, and workflow impact areas.

Entity Configuration

Manage business information, numbering, taxes, and defaults.

Shipping Rules

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

Integrations

Connect Stripe, marketplaces, shipping, email, and other services.

User Management

Invite users, manage entity access, roles, permissions, location restrictions, PINs, and MFA reset workflows.