ForzaUKB

Step 1.4 — MVMNT Shipper Profile Creation and Configuration

3 min read

Step 1.4 — MVMNT Shipper Profile Creation and Configuration

File name note

Previously named Step-1.4-EZ-Loader-Shipper-Profile-Creation for historical reasons. Renamed to Step-1.4-MVMNT-Shipper-Profile-Creation on 2026-04-29. The content reflects the actual MVMNT-based process. EZ-Loader migration was cancelled 2026-04-28 (see DECISIONS.md).

Phase: Phase 1 — New Shipper Onboarding Owner: Accounting Trigger: HaulPay credit check complete and decision made (Step 1.3 Tier 1/2) — or self-finance approved by Founder-CEO (Step 1.3a).

🎯 Ideal State

Accounting creates the Shipper profile in MVMNT. MVMNT is Forza’s operational system of record — where loads are built, invoices generated, documents stored, and all operational activity tracked. The profile created here also flows to QuickBooks-Online via the two-way sync (verified in Step 1.10).

Data entered into MVMNT:

Data FieldNotes
Shipper company legal nameMust match exactly what was entered in HaulPay. Mismatches cause invoice rejections and QBO reconciliation problems. Copy-paste from HaulPay to prevent typo drift.
Physical addressStreet, city, state, zip
Mailing addressIf different from physical
Primary contact name, email, phoneFrom intake form
Billing contact name, email, phoneFrom intake form
Federal Tax ID / EINFrom intake form
Assigned Sales rep(s)From intake form — defaults auto-apply to every load for this Shipper
Default GP split percentageFrom intake form — auto-applies to every load; must be correct at setup

Digital Shipper onboarding: MVMNT supports a digital Shipper onboarding webform where the Shipper reviews their company information, views Forza’s W-9 and operating authority, and e-signs the broker/shipper agreement. Status flows: Onboarding Sent → Onboarding Signed → Customer.

Manual fallback: If the digital webform is not used or the Shipper cannot complete it, Accounting enters all data manually, sends the broker/shipper agreement separately for e-signature via Adobe-Acrobat-Pro, and uploads the signed copy into the Shipper profile documents section.

⚠️ Verification needed: Confirm the MVMNT digital Shipper onboarding webform configuration for Forza — what fields it captures, what it produces in the Shipper profile on submission, and whether the broker/shipper agreement can be uploaded as the e-sign document within the webform.

🤖 SYSTEM AUTOMATION

If the digital onboarding webform is configured and used — largely automated. Shipper self-enters, MVMNT tracks status, signed agreement auto-files, and the new Shipper syncs to QuickBooks-Online on the next sync cycle. If manual — fully human, error-prone, slower.

📍 Current State

  • Shipper profiles are created in MVMNT with data copied from emails and conversations rather than a single structured intake form.
  • The digital Shipper onboarding webform in MVMNT has not been fully configured or evaluated for Forza.
  • Broker/shipper agreement is currently signed outside MVMNT (via Adobe-Acrobat-Pro or equivalent) and uploaded to the Shipper profile documents manually.

Who does this today: Accounting.

🚧 Gap

  1. MVMNT digital Shipper onboarding webform is not fully configured or evaluated.
  2. Broker/shipper agreement e-sign happens outside the TMS, creating a manual upload step.
  3. Shipper data flows from ad hoc sources rather than a structured intake form.

🛠️ Gap Closure Actions

  • Action 1 — Evaluate MVMNT digital Shipper onboarding webform with MVMNT support — configuration, customization, agreement upload (Owner: Casey + Ops Manager + MVMNT support | Effort: Medium)
  • Action 2 — If the webform is viable, configure it with Forza branding, W-9, operating authority, and the standard broker/shipper agreement (Owner: Casey + Accounting | Dependency: Webform evaluated | Effort: Medium)
  • Action 3 — Document the Shipper profile creation SOP for Accounting (fields, digital vs. manual fallback, data source from intake form) (Owner: Casey + Accounting | Dependency: Webform decision made | Effort: Low)
  • Action 4 — Evaluate whether Adobe-Acrobat-Pro is still needed for broker/shipper agreement e-sign once the MVMNT webform is in use, or if it can be cancelled/consolidated (Owner: Casey + Accounting | Dependency: Webform configured | Effort: Low)

Previous: Step-1.3-HaulPay-Shipper-Profile-Credit-Check | Next: Step-1.5-MVMNT-Shipper-Billing-Configuration

Graph View

Backlinks