> ## 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.
# Entity Configuration
> Entity configuration controls the business identity, locations, default operating context, and document identity for the company you are working in. Treat these fields as shared operational defaults, not just profile information.
## What an Entity Controls
An entity is the business workspace that owns orders, accounts, products, inventory,
accounting activity, users, documents, shipping setup, and connector behavior. In a
multi-entity organization, each entity has its own operational data and settings.
* **Business identity**: legal name, display name, address, phone, email, tax ID, and branding.
* **Locations**: warehouses, offices, stores, receiving points, ship-from addresses, and fulfillment defaults.
* **Numbering**: document numbering for orders, invoices, purchase orders, checks, and related records.
* **Environment context**: sandbox or production behavior, connector mode, and safe testing expectations.
* **Access context**: users can belong to one or many entities with different roles per entity.
## Update the Business Profile
1. Open **Settings**.
2. Go to **Company**, then open **Business Profile**.
3. Review the entity name, legal name, address, phone, email, tax ID, and time zone.
4. Save changes during a quiet operating window when the update affects documents or integrations.
5. Test one downstream document or workflow after saving.
**Business profile changes are visible outside Settings**
The entity name, address, phone, email, and tax details can appear on invoices, packing
slips, customer emails, tax documents, labels, vendor paperwork, and reports. Confirm
the visible output after making changes.
## Branding and Customer Documents
Branding settings control how Arcus presents the company on customer-facing documents.
Keep logos, colors, document names, and contact details aligned with the real business
identity customers expect to see.
## Locations Drive Operations
Locations are more than labels. They decide where inventory is stored, where orders are
fulfilled, where purchase orders can be received, and which address is used when a label
needs a ship-from location.
* **Default location**: used when a workflow needs a fallback location.
* **Sellable**: controls whether inventory at the location can support orders.
* **Receiving**: controls whether purchase orders and standalone receives can use the location.
* **Ships from**: controls whether the address can be used for shipping labels.
* **Address**: used by shipping, tax, documents, and internal routing depending on workflow.
**Test after changing a location**
Create or review a draft order, a receiving workflow, and a shipping label preview after
changing location flags or addresses. That catches most operational surprises early.
## Number Counters and Document Identity
Number counters control the next document number Arcus assigns. They are useful during
setup or migration, but they should be handled carefully once the entity is live.
* Increase counters when you need future documents to start above an old system's range.
* Do not decrease counters into a range that may already exist.
* Keep prefixes consistent with how users search and reconcile documents.
* Test the first new document after a numbering change.
**Do not reuse document numbers**
Reusing order, invoice, purchase order, or check numbers creates audit and reconciliation
confusion. If you are not sure whether a range has already been used, choose a higher
next number and document why it changed.
## Sandbox vs Production
Sandbox is for training, setup testing, and workflow proofing. Production is live work.
The same screen can feel similar in both places, so verify the active environment before
changing payment, tax, shipping, email, numbering, or connector settings.
* Use sandbox before changing automation that can send emails, buy labels, collect payments, or affect accounting.
* Keep test customers, test products, and test vendors clearly labeled.
* Have one person own the production change and one person confirm the downstream result.
## Common Entity Setup Blocks
* **Wrong company identity appears on documents**: review Business Profile, Branding, document templates, sender identity, and the active entity.
* **A location is missing from a workflow**: confirm the location is active and marked for selling, receiving, fulfillment, or ship-from use as needed.
* **Orders default to the wrong location**: check the entity default, user location restrictions, sales channel defaults, account defaults, and order-level overrides.
* **Document numbers look unexpected**: review prefixes, padding, next counters, migration ranges, and whether another user created documents after the change.
* **A user lands in the wrong entity**: check organization membership, default entity, role assignment, and whether the user belongs to multiple entities.
* **Sandbox and production feel mixed up**: verify the URL, environment banner, connector mode, email routing, and payment or shipping test mode before continuing.
## Related Articles
Understand the admin surfaces, settings groups, and workflow impact areas.
Configure business profile, environment, branding, locations, and the workflow impact of company defaults.
Invite users, manage entity access, roles, permissions, location restrictions, PINs, and MFA reset workflows.
Configure PDF terms, document numbering, sender identity, notification toggles, templates, and quote expiration.
Configure Shippo, carrier defaults, shipping rules, freight routing, PackPilot, scanners, and PrintNode printing.