Settings

Your company's legal trading name. Appears in the app header, emails, invoices, and PDF labels. Misconfiguration: Wrong name on customer-facing documents is unprofessional and may cause legal/tax issues.

Your company's tax registration number. Printed on invoices as required by most tax authorities for B2B transactions.

Full registered business address. Appears on invoices, PDF labels, and the public tracking page footer.

Main contact phone number. Shown on invoices and the public tracking page for customer inquiries.

Main business contact email. Shown on invoices and tracking page. Not the same as the MAIL_FROM_ADDRESS environment variable (which is the sending address).

Your company website URL. Shown on invoices and in email footers as a clickable link.

ISO 4217 currency code (e.g., USD, EUR, GBP, MXN). Used for all invoices, reports, and financial displays. Misconfiguration: Changing the currency after invoices have been created will cause financial data inconsistency. Set this before creating any invoices.

Your company's country of operation. Used for locale defaults, tax display, and address formatting.

Primary company logo. Appears in the app sidebar header, PDF invoices, and shipment labels. Recommended: PNG with transparent background, minimum 300×100px, max 2MB.

Optional alternate version (e.g., reversed/white logo for dark backgrounds). Used in PDF footers and email headers.

Browser tab icon. Recommended: 32×32px or 64×64px PNG or ICO file. Shows in browser tabs and bookmarks.

Logo shown on the login page above the sign-in form. Can differ from the main logo (e.g., full horizontal logo on login vs. icon-only in sidebar).

Background image for the right panel of the login page. Recommended: 1200×800px minimum, 5MB max. Supports JPEG and PNG. If not set, a gradient background using the primary color is used.

Main accent color used for buttons, active links, highlights, and key UI elements. Default: #FF6B35 (electric coral). Accepts any valid hex color code.

Used for secondary buttons, hover states, and complementary accent elements. Default: #1e2538.

Used for highlights, badges, and callout elements. Creates visual hierarchy alongside the primary color.

Options: dark (default), light, system (follows OS preference). Each user can override the theme in their profile settings — the setting here is the system default for new users.

When enabled, the sidebar collapses to show only icons (no labels), giving more horizontal space to the main content area. Can be toggled per user from the sidebar footer.

Body text font. Select from: Inter (default), Roboto, Open Sans, Poppins, Lato, Nunito. Font is loaded from Google Fonts CDN.

Base font size in pixels. Options: 13, 14 (default), 15, 16. Affects readability and UI density. Larger values are better for accessibility.

Controls padding and spacing throughout the UI. Options: comfortable (spacious, best for focus), normal (default), compact (more data on screen, better for power users).

Visual style for content cards and panels. Options: shadow (default, subtle drop shadow), flat (no shadow, clean), bordered (visible border, no shadow).

When enabled, removes color from status badges and replaces with grayscale patterns. Useful for accessibility (colorblind users) or printing screenshots.

How in-app notifications appear. toast (default) — small temporary pop-up in the corner. banner — full-width bar at the top of the page.

Where toast notifications appear. Options: top-right (default), top-left, bottom-right, bottom-left, top-center.

Milliseconds before a toast notification auto-dismisses. Default: 4000 (4 seconds). Range: 1000–15000. Error toasts do not auto-dismiss regardless of this setting.

Maximum number of toast notifications visible simultaneously. Default: 3. Additional notifications are queued and shown as previous ones dismiss.

Headline text shown on the login page (on the image/background panel). Default: "Welcome Back". Customize with your brand message.

Which side the login form appears. left (default) or right. The image/background occupies the opposite side.

Whether to show a "Register" link on the login page. Disable this if you only want invited users and not self-registration.

Application interface language. Options: en (English, default), es (Spanish). Individual users can override in their profile. Translation files: resources/js/i18n/en.json and es.json.

System timezone for all date/time displays and scheduled operations. Uses PHP/IANA timezone identifiers (e.g., America/New_York, Europe/London, America/Mexico_City). Critical: Set this before going live. Changing after production use creates confusion in historical timestamps.

How dates are displayed throughout the UI and on PDFs. Options: d/m/Y (31/12/2026), Y-m-d (2026-12-31, ISO format), m/d/Y (12/31/2026, US format), d M Y (31 Dec 2026).

12-hour (h:i A, shows AM/PM) or 24-hour (H:i) time display.

kg (kilograms, default) or lb (pounds). Affects shipment weight entry and display in the UI and on labels.

cm (centimeters, default) or in (inches). Affects package dimension entry and display.

ISO 4217 currency code used for formatting monetary amounts in the UI. This is separate from the company.currency setting — they should match. Example: USD, EUR, MXN.

Descriptive name (e.g., "Miami Main", "Guadalajara North"). Shown in branch dropdowns throughout the app and on shipment records.

Short identifier for reports and tracking (e.g., "MIA", "GDL"). 2–6 characters, uppercase. Used as a prefix component in branch-specific tracking numbers if configured.

Physical address and contact number for this location. Shown on shipment labels as the pickup/origin point.

Assign a system user as this branch's manager. They receive branch-specific notifications and alerts.

Inactive branches are hidden from branch selection dropdowns but their historical data is preserved. Use this when a location closes.

The default branch is pre-selected when creating new shipments. Only one branch can be the default at a time.

The name shown to users in the UI and on the customer tracking page. Example: change "Out for Delivery" to "With Driver".

Hex color used for the status badge throughout the app and on the shipment timeline on the tracking page.

Controls the order statuses appear in dropdown menus and legend displays. Drag to reorder.

Whether this status is shown to customers on the public tracking page. For internal statuses (e.g., "On Hold - Pending Payment"), you may want to show customers a more generic "In Progress" message instead.

The text shown to customers on the public tracking page, which may differ from the internal label. Example: Internal = "Exception - Address Not Found", Customer = "Delivery Attempt Unsuccessful".

Display name (e.g., "Standard Delivery", "Express Next Day").

Internal code used in the API and exports. Lowercase, underscores (e.g., standard, express). Cannot be changed after creating shipments with this service.

Default price for this service. Overridden by client contracts when applicable. Shown to dispatchers during shipment creation.

Used to calculate estimated delivery date on the tracking page and to flag overdue shipments in reports.

Inactive services cannot be selected for new shipments. Existing shipments using this service are not affected.

Sends a confirmation email to the receiver (with tracking link) and optionally to the sender. Toggle: Receiver Only, Sender Only, Both, Disabled.

Sends a status update email to the receiver. Configure which status changes trigger an email (e.g., only Picked Up, In Transit, Out for Delivery, Delivered — not internal holds).

Delivery confirmation email to receiver and sender. This is the most important customer-facing notification. Always recommended to keep enabled.

Notifies the sender/client when a delivery attempt fails. Email includes the exception reason and instructions for next steps.

Emails the invoice PDF to the client when status is changed from Draft to Sent.

Payment reminder email sent to the client when an invoice becomes overdue. Configurable: send on due date, 3 days after, 7 days after.

Email alert to the branch manager when an inventory item falls below reorder point. Also sends an in-app notification.

Minimum characters required for all user passwords. Default: 8. Recommended: 12+ for production. Affects new password creation and password changes only.

When enabled, passwords must include at least one uppercase letter (A–Z).

When enabled, passwords must include at least one numeric digit (0–9).

When enabled, passwords must include at least one special character (e.g., !, @, #, $).

Minutes of inactivity before the user session expires and they are logged out. Default: 120. Set lower for high-security environments. Range: 5–480 minutes.

When enabled, users with Super Admin or Admin roles must complete 2FA setup before they can access the application. Applies to new logins — existing sessions are not terminated immediately.

Maximum failed login attempts before the account is temporarily locked. Default: 5. Lock duration: 15 minutes. After the lock expires, the counter resets.

Optional list of allowed IP addresses or CIDR ranges that can access the application. When set, logins from any other IP are rejected. Leave empty to allow access from any IP. Warning: If your server IP changes or you misconfigure this, you may lock yourself out. Always test from whitelisted IP before saving.

public — anyone with the tracking number can access the page without logging in. private — requires the customer to log in to view their shipments.

The URL structure for tracking links. Default: /track/{tracking_number}. The full URL sent to customers: https://yourdomain.com/track/TRK00814726.

Optional Google Maps JavaScript API key for embedding a map showing the delivery route and last known location on the tracking page. Get a key from Google Cloud Console. Leave empty to hide the map section.

Whether to show the sender's name on the public tracking page. Disable for privacy (the receiver may not need to know who sent a gift, for example).

Whether to show package weight and dimensions on the public tracking page. May want to disable for B2B where dimensions are confidential.

Triggers a manual database dump (SQL file) that is stored in storage/app/backups/ and optionally uploaded to your configured S3 bucket. File name includes timestamp. Download link is provided after completion. Best practice: Set up automated daily backups at the OS level as well.

Runs php artisan cache:clear. Clears the Redis/file application cache including settings cache, query results cache, and computed values. Run after making manual database changes or troubleshooting stale data.

Runs php artisan view:clear. Clears the compiled Blade template cache. Rarely needed — only if you've edited Blade PDF templates and changes aren't appearing.

Enables Laravel maintenance mode (php artisan down). All users see a maintenance page until you disable it. A secret token URL is provided so you can still access the app during maintenance. Warning: Enabling this blocks all users including admins from normal access.

Displays: PHP version, Laravel version, database size, storage space used, current queue depth, number of failed jobs, and server memory/CPU usage (if accessible). Useful for diagnosing performance issues.

Enter your purchase code (Envato) or license key. Click Activate License. The system validates the code against your registered installation domain. On success, license details are stored and update checking is enabled. Misconfiguration: If the domain registered with your license doesn't match the APP_URL in .env, activation will fail. Contact support to transfer the license to a new domain.

Displays: Active with expiry date for a valid license, Expiring Soon if within 30 days of expiry, or Expired. Expired licenses continue to run the current version but cannot check for or apply updates until renewed.

When expired, a prominent renewal button links to the purchase page. After renewal, enter the new license key to reactivate.

Queries the update server for the latest available version. If a newer version is available, an update banner is shown with the new version number and a changelog summary.

When an update is available, a banner shows: current version, new version number, update size, and a summary of changes from the changelog.

Initiates the update process. The system: 1) Downloads the update package, 2) Backs up current files and database, 3) Applies the update files, 4) Runs database migrations, 5) Clears caches. A real-time log terminal is shown during the process.

A scrolling log terminal shows each update step in real time. If an error occurs, the terminal shows the error message and the system attempts to roll back to the pre-update backup automatically.