Run your logistics business on Fauward.

Sign up at fauward.com/signup. No card is required, and every new workspace starts with a 14-day free trial.

Onboarding wizard

After signup, the onboarding wizard walks you through the minimum setup:

1. 1Set your business name and subdomain, such as yourcompany.fauward.com.
2. 2Upload your logo and set your brand colours for the portal, emails, and widget.
3. 3Invite your first team member and choose the right role for them.
4. 4Create your first shipment and confirm the tracking timeline looks right.
5. 5Add the tracking or booking widget to your website when you are ready for customer traffic.

Workspace setup order

First-day checklist

• Create a test shipment from your own address to a known recipient.
• Assign it to yourself or a dispatcher, then move it through each status.
• Generate a proof of delivery document and confirm the customer timeline is clear.
• Check that the sender, recipient, package, price, and service fields are accurate before invoicing.
• Send yourself a sample notification so you can review the sender name and branding.
• Invite the team members who will operate live jobs and enforce MFA for sensitive roles.

First integration path

Most teams start with the hosted booking page or tracking widget, then add API keys and webhooks once they know which shipment fields their own systems should send and receive. Use one internal test key first, then rotate to a dedicated production key for each connected system.

The dashboard is the daily control room for your operation. It is designed for owners, managers, dispatchers, and finance users who need a live summary without digging through every module.

Reading the dashboard

Activity feed

The feed shows recent operational activity such as new shipments, status changes, assignments, invoice updates, customer messages, and failed delivery events. Use it during shift handovers to understand what changed while a manager or dispatcher was away.

Quick actions

Shipments are the core record in Fauward. A shipment contains the sender, recipient, cargo, pricing, route, status history, documents, and customer-facing tracking timeline.

Every shipment moves through a defined status lifecycle:

Exception branches

Status transition rules

Fauward accepts only valid next statuses. This protects timelines, invoices, and customer notifications from skipping operational evidence.

Creating a shipment

Create shipments from the dashboard, shipment list, booking widget, or API. Fill in sender, recipient, cargo details, service type, pricing, and any collection or delivery instructions. A tracking reference such as FW-10482 is generated automatically.

• Sender details: name, company, address, phone, email, pickup notes, and preferred pickup window.
• Recipient details: name, company, address, phone, email, delivery notes, and notification preference.
• Cargo details: item description, quantity, weight, dimensions, declared value, fragility, and special handling notes.
• Commercial details: service level, price, tax treatment, customer account, and invoice reference.
• Compliance details: customs category, item value, HS code, return instructions, and required labels where your workflow uses them.

Tracking & timeline

Every status change is logged with a timestamp, source, and user where available. The internal timeline helps your team audit what happened. The customer timeline presents the customer-safe version of the same journey, including milestones, exception states, delivery attempts, and proof-of-delivery availability without exposing internal notes.

Bulk operations

In the shipment list, select multiple shipments to assign a driver, move them to a new status, export them to CSV, or prepare a manifest. Use filters before selecting rows if you only want to update a specific depot, customer, route, service type, or status.

Documents

Dispatch

The Dispatch page turns shipments into work. Assign jobs to drivers or agents, plan routes, set pickup windows, and monitor progress as field updates come in.

fauward Go

Your field team uses fauward Go, a mobile web app installed directly to their phone with no app store required. Drivers see only their assigned work and step through each job in the correct order.

• View assigned pickups, linehaul movements, deliveries, and exception tasks.
• Scan QR codes or barcodes at each stop to verify the right parcel.
• Capture proof of delivery with recipient name, OTP, signature, or photo.
• Add delivery notes when access is blocked, a recipient is unavailable, or cargo is damaged.
• Work offline while scans and confirmations queue locally and sync when the device is back online.

Stop workflow

Proof of delivery options

Agents

For simpler scan-and-advance workflows, the agents app lets field staff quickly update shipment status by scanning a tracking label. It is useful at depots, warehouses, partner counters, and temporary collection points.

Offline behaviour

Fauward Go stores assigned stops, scans, notes, signatures, photos, and completion attempts locally when connectivity drops. Field users should keep the app open until queued actions sync, then confirm the job no longer shows as pending before leaving a low-signal area.

Finance connects shipment operations to billing. Pricing entered on shipments can flow into quotes, invoices, payment tracking, and reconciliation.

Invoice lifecycle

• Create quotes and convert them to invoices in one click.
• Auto-populate line items from shipment pricing, service type, and customer account details.
• Add manual line items for waiting time, storage, customs handling, insurance, or special services.
• Record partial payments when a customer pays in stages or a remittance covers several invoices.
• Send invoices to customer billing contacts and track when they become overdue.
• Export invoice history, payments, and reconciliation reports to CSV.

Adjustments and cash workflows

Invite team members from Settings -> Team. Each member gets a role that controls what they can see and do.

Invites and onboarding

Members receive an email invite and set their own password. If the invite expires, resend it from the team settings page. For operational staff, confirm they can log in before their first shift and that their assigned role matches the work they need to do.

Role assignment guidance

The role names above are the exact tenant and customer role values used by the platform. Platform-only administration is not assignable from a tenant workspace. Use customer roles only for external customer account access, not for your internal dispatch, finance, or driver staff.

• Use TENANT_ADMIN only for users who can change billing, API keys, branding, and account settings.
• Use TENANT_MANAGER for operations leads who need broad control without every account-level responsibility.
• Use TENANT_FINANCE for users who mainly manage invoices, payments, exports, and reconciliation.
• Use TENANT_STAFF for dispatchers and depot operators who create and move shipments.
• Use TENANT_DRIVER for field users who should work through Fauward Go instead of the full portal.

Security controls

• Enforce MFA with an authenticator app for admins, managers, finance users, and API key owners.
• Use the lowest role that lets each user do their job.
• Reset passwords from team settings when a user cannot complete the self-service flow.
• Suspend users instead of deleting them when you need to preserve ownership history.
• Remove inactive users when staff leave, change depot, or no longer need access.
• Create separate user accounts instead of sharing one dispatcher or driver login.

Embed a branded tracking widget on your own website so customers can check shipment status without contacting your team. This reduces inbound calls and gives customers a self-service way to see the latest timeline.

Embed code

Add one script tag to your site:

<script
  src="https://fauward.com/embed.js"
  data-tenant="yourslug"
  data-api-key="fw_your_public_widget_key"
  async
></script>

Hosted booking page

If you do not want to embed the form on your own site first, send customers to your hosted booking page at https://ship.fauward.com/yourslug. The hosted page uses the same tenant branding and shipment-creation workflow as the embeddable widget.

Widget token flow

The widget exchanges its tenant slug and API key for a short-lived embed token before it submits shipment data. Your site never needs to expose a server secret value.

GET /api/embed/token?tenant=yourslug
Authorization: Bearer fw_your_public_widget_key

What customers see

• A branded tracking search field using your logo and colours.
• Current shipment status, tracking reference, and customer-safe timeline.
• Milestone timestamps such as processing, picked up, in transit, out for delivery, and delivered.
• Exception states when a shipment has a failed delivery, exception, return, or cancellation.
• Phone verification or payment prompts where your workflow enables them for customer-created shipments.

Recommended placement

Add the widget to your public tracking page, customer support page, and post-booking confirmation page. If your website has a customer portal, place it where customers already go for shipment updates.

Fauward is fully white-label, so your customers experience your logistics brand rather than Fauward. Branding applies across the portal, tracking widget, customer emails, and customer-facing documents where supported.

What you can customise

Branding checklist

• Use a clear logo that works on white backgrounds and small screens.
• Choose a primary colour with enough contrast for buttons and important labels.
• Add a support email, support phone number, and customer-facing business address where appropriate.
• Preview the customer tracking page after making changes.
• For a custom domain, add the CNAME shown in Settings -> Domain and wait for the verification status to become Live.
• Send yourself a test notification to confirm the customer-facing sender name.
• Review documents after brand changes if your team prints labels or PODs.

Domain setup flow

1. 1Choose the customer-facing hostname you want to use, such as track.yourcompany.com.
2. 2Add it in Settings -> Domain and copy the DNS record shown in the portal.
3. 3Create the CNAME with your DNS provider and wait for verification.
4. 4Preview tracking, widget, emails, and documents before sharing the domain with customers.

Update your branding any time from Settings -> Branding.

Fauward sends automatic notifications to your customers at key shipment milestones. Use notifications to reduce support volume, improve customer confidence, and keep delivery expectations clear.

Channels

Common triggers

Customer messaging tips

• Keep milestone messages short and specific.
• Use your brand sender name so customers recognise the update.
• Avoid exposing internal route, depot, or staff details in customer-facing messages.
• Use failed-delivery messages to tell customers what happens next.
• Use Relay conversations for two-way support instead of putting long operational notes into SMS templates.
• Test templates after changing branding, phone verification, payment prompts, or support routing.
• Review notifications when you change your operating hours or support process.

API keys and webhooks help you connect Fauward to your own booking forms, ecommerce systems, finance tools, customer portals, warehouse software, and reporting workflows.

API keys

Generate API keys from Settings -> API Keys. Keys are scoped to your tenant and should be treated like passwords.

All API calls use:

Authorization: Bearer fw_your_api_key

Request safety

• Create a separate key for each integration so you can revoke one system without breaking another.
• Use read-only scopes for reporting, tracking, and dashboard sync jobs.
• Use write scopes only for systems that create shipments, update routes, send webhook tests, or manage domains.
• Use idempotency keys for retryable create or update calls where the endpoint supports them.
• Rotate keys when a team member leaves or a connected vendor changes access.

Common API uses

Common endpoints

Webhooks

Register webhook endpoints to receive real-time events when shipments change status, deliveries complete, failed-delivery events occur, and other configured shipment updates happen. Configure endpoints from Settings -> Webhooks.

Each event is delivered as a POST with a JSON payload and signed with your webhook secret. Your receiving system should verify the signature before trusting the payload.

{
  "event": "shipment.status.changed",
  "tenant": "yourslug",
  "data": {
    "trackingReference": "FW-10482",
    "previousStatus": "IN_TRANSIT",
    "status": "OUT_FOR_DELIVERY",
    "updatedAt": "2026-04-26T09:30:00Z"
  }
}

Webhook headers

Common events

Delivery and replay

Webhook deliveries are retried automatically with backoff when your endpoint does not respond successfully. Use the delivery log to inspect response codes, latency, failed attempts, and replay a delivery after fixing the receiving system.

Plans

Plan limits and gates

Upgrade or downgrade from Settings -> Plan & Billing. Changes take effect immediately, and billing is prorated.

Trial

Your 14-day trial includes full Pro features. No card is required to start. Before the trial ends, you will be prompted to add a payment method and choose the plan that fits your shipment volume and operating needs.

Billing administration

• Only users with billing access should manage plans, payment methods, and invoices.
• Keep the billing contact email current so invoice and renewal notices reach the right person.
• Review plan limits before seasonal peaks, new customer launches, or additional depot rollouts.
• Check API and shipment usage before downgrading so critical workflows do not lose access.
• Resolve failed payment status quickly to avoid account suspension and interrupted integrations.
• Export operational and finance data before major account changes if your internal process requires it.

Cancellation

Cancel any time from Settings -> Plan & Billing. Your data is retained for 30 days after cancellation so you can export records or reactivate the workspace if needed.