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 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
- Open Settings.
- Go to Company, then open Business Profile.
- Review the entity name, legal name, address, phone, email, tax ID, and time zone.
- Save changes during a quiet operating window when the update affects documents or integrations.
- Test one downstream document or workflow after saving.
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.
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.
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.