> ## 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.

# Company Setup

> Company settings control the business identity, environment, branding, and physical locations that other Arcus workflows rely on. Review these settings before going live, adding a warehouse, changing labels, or turning on customer-facing documents.

## 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**.

<Frame caption={"Business Profile is where admins review identity, environment, primary entity, contact, address, icon, and logo settings."}>
  <img src="https://mintcdn.com/arcuserp/ATYxy7SB_HGOBGqh/images/support/screenshots/settings/company-business-profile.png?fit=max&auto=format&n=ATYxy7SB_HGOBGqh&q=85&s=2c4a93b9047419123a48b7ed514a0e19" alt="Entity Settings Business Profile page with entity name, environment, primary entity, website, email, business address, icon, and logo" width="1640" height="950" data-path="images/support/screenshots/settings/company-business-profile.png" />
</Frame>

## 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.

<Warning>
  **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.
</Warning>

## 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.

<Tip>
  **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.
</Tip>

## 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.

* **Primary color**: affects branded buttons, accents, and customer-facing presentation where supported.
* **Icon**: appears in compact app and entity contexts where a square mark works better than a full logo.
* **Logo**: appears on customer-facing documents, email templates, and portal surfaces where supported.
* **Preview**: check the visual result before sales, AR, or support teams send customer-facing documents.

<Frame caption={"Branding should be checked before teams send invoices, quotes, order confirmations, or portal links to customers."}>
  <img src="https://mintcdn.com/arcuserp/ATYxy7SB_HGOBGqh/images/support/screenshots/settings/company-branding.png?fit=max&auto=format&n=ATYxy7SB_HGOBGqh&q=85&s=75c15452a8f4dd677a88c254927f0aed" alt="Entity Settings Branding page with company branding controls and preview" width="1640" height="900" data-path="images/support/screenshots/settings/company-branding.png" />
</Frame>

## 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.

<Frame caption={"Locations connect company setup to inventory, receiving, fulfillment, and shipping behavior."}>
  <img src="https://mintcdn.com/arcuserp/ATYxy7SB_HGOBGqh/images/support/screenshots/settings/company-locations.png?fit=max&auto=format&n=ATYxy7SB_HGOBGqh&q=85&s=d7972ede545f807c96c9c245b6f1cd20" alt="Entity Settings Locations page with location list, type badges, default marker, and Add Location button" width="1640" height="900" data-path="images/support/screenshots/settings/company-locations.png" />
</Frame>

* **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.

## Location Types And Workflow Impact

<div className="not-prose my-6 overflow-hidden rounded-xl bg-white ring-1 ring-border">
  <table className="w-full text-left text-sm">
    <thead className="bg-surface-muted text-xs uppercase tracking-wide text-ink/50">
      <tr>
        <th className="px-4 py-3 font-semibold">Location type</th>
        <th className="px-4 py-3 font-semibold">Typical use</th>
        <th className="px-4 py-3 font-semibold">What to verify</th>
      </tr>
    </thead>

    <tbody className="divide-y divide-border-muted">
      <tr>
        <td className="px-4 py-3 font-medium text-ink">Warehouse</td>
        <td className="px-4 py-3 text-slate-deep">Normal sellable stock, receiving, fulfillment, and shipping origin work.</td>
        <td className="px-4 py-3 text-slate-deep">Sellable, ships from, receives, and address are correct.</td>
      </tr>

      <tr>
        <td className="px-4 py-3 font-medium text-ink">Holding</td>
        <td className="px-4 py-3 text-slate-deep">Returns, inspection, quarantine, or temporary non-sellable stock.</td>
        <td className="px-4 py-3 text-slate-deep">Stock should not be available for normal sales unless intentionally allowed.</td>
      </tr>

      <tr>
        <td className="px-4 py-3 font-medium text-ink">Writeoff</td>
        <td className="px-4 py-3 text-slate-deep">Damaged, scrapped, destroyed, or written-off goods.</td>
        <td className="px-4 py-3 text-slate-deep">Do not mark sellable or receiving for normal operations.</td>
      </tr>

      <tr>
        <td className="px-4 py-3 font-medium text-ink">Marketplace</td>
        <td className="px-4 py-3 text-slate-deep">Marketplace-specific stock routing or imported channel handling.</td>
        <td className="px-4 py-3 text-slate-deep">Confirm connector mapping and inventory visibility before relying on it.</td>
      </tr>

      <tr>
        <td className="px-4 py-3 font-medium text-ink">Dropship</td>
        <td className="px-4 py-3 text-slate-deep">Vendor-fulfilled or third-party ship-from workflows.</td>
        <td className="px-4 py-3 text-slate-deep">Shipping origin, customer communication, and receiving expectations are clear.</td>
      </tr>

      <tr>
        <td className="px-4 py-3 font-medium text-ink">Overflow</td>
        <td className="px-4 py-3 text-slate-deep">Temporary warehouse overflow or seasonal storage.</td>
        <td className="px-4 py-3 text-slate-deep">Sellable and receiving flags match the temporary process.</td>
      </tr>
    </tbody>
  </table>
</div>

## 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.

<Note>
  **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.
</Note>

## 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.
* **Email branding**: send a test email after changing logo or company identity.
* **Customer portal branding**: open a public quote, invoice, or portal page and confirm the brand looks correct.
* **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.
* **Ship-from location**: buy only a safe test label or preview a rate before relying on the address in production.

## 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.
* **Tax or rates use the wrong origin**: review the order ship-from location, default location, business address, and shipping settings.
* **Branding looks wrong on a PDF**: upload a cleaner logo and regenerate a preview document.
* **Email branding did not change**: review Email Configuration and template preview because email logo can be controlled separately.
* **Users land in the wrong entity**: review Primary Entity and each user's entity membership.

## Related Articles

<CardGroup cols={2}>
  <Card title="Settings Overview" href="/support/settings/overview">
    Understand the admin surfaces, settings groups, and workflow impact areas.
  </Card>

  <Card title="Entity Configuration" href="/support/settings/entity">
    Manage business information, numbering, taxes, and defaults.
  </Card>

  <Card title="Shipping Rules" href="/support/settings/shipping">
    Configure Shippo, carrier defaults, shipping rules, freight routing, PackPilot, scanners, and PrintNode printing.
  </Card>

  <Card title="Integrations" href="/support/settings/integrations">
    Connect Stripe, marketplaces, shipping, email, and other services.
  </Card>

  <Card title="User Management" href="/support/settings/users">
    Invite users, manage entity access, roles, permissions, location restrictions, PINs, and MFA reset workflows.
  </Card>
</CardGroup>