Salesforce Administrator Portfolio

FreightPath

A purpose-built Salesforce CRM for a mid-size freight brokerage — managing carrier relationships, load tracking, shipper accounts, and revenue pipeline in a single platform.

Explore the build View process

Click a segment to view screenshot

● Dashboard reporting ● Loads list ● Load record ● Active flows

Load tracking Carrier management Revenue pipeline Automated task creation Validation rules Permission sets Lane-based routing Margin analytics Dashboard reporting Data import Load tracking Carrier management Revenue pipeline Automated task creation Validation rules Permission sets Lane-based routing Margin analytics Dashboard reporting Data import

Project overview

Built for the brokerage floor

FreightPath replaces the spreadsheet dependency common in mid-size freight brokerages with a structured, automated Salesforce CRM. Every object, field, and flow was designed around how brokers actually operate — assigning carriers, tracking loads by lane, and closing deals.

"I designed a CRM solution to centralise carrier relationships, shipment tracking, and revenue pipeline management — eliminating the spreadsheet dependency common in mid-size brokerages."

The build demonstrates real Salesforce administrator competencies: custom object modelling, validation logic, flow automation, data import, permission set design, and operational dashboard creation.

Scope

Custom objects Load__c · Carrier__c · Lane__c

Standard objects Account · Contact · Opportunity

Validation rules 5 rules across 2 objects

Record-triggered flows 2 active flows

Permission sets FreightPath Broker · Manager

Dashboard components 5 components · 3 reports

Data model

Object architecture

Six objects — three custom, three standard — connected through lookup relationships to model the full brokerage operation. Each custom object was built from scratch with brokerage-specific fields, picklists, formulas, and validation logic.

Custom object

Load__c

The core operational record. Each load represents a freight movement with full financial tracking.

Lane__c Assigned_Carrier__c Load_Value__c Carrier_Cost__c Margin__c Status__c Pickup_Date__c Delivery_Date__c

Custom object

Carrier__c

Carrier database with compliance, equipment, and performance data for every trucking partner.

MC_Number__c DOT_Number__c Equipment_Type__c Primary_Lane__c Carrier_Rating__c Insurance_Expiry__c Active__c

Custom object

Lane__c

Structured origin-to-destination route records. Picklist-controlled for clean, reportable data.

Origin_City__c Destination__c

Standard object

Account

Shipper client companies. Extended with a Shipper Type picklist for brokerage classification.

Shipper_Type__c BillingAddress Phone Industry

Standard object

Opportunity

Revenue pipeline per deal. Linked to Load__c and auto-closed by Flow when a load is delivered.

Load__c Amount StageName CloseDate Expected_Margin__c

Standard object

Contact

Logistics managers and procurement leads at each shipper account.

Name Title Email Phone AccountId

Flow automation

Two flows. Zero manual steps.

Both flows are record-triggered and active in production. Together they automate the two most repetitive broker tasks — carrier assignment follow-up and deal closure — without any manual intervention.

The Delivered to Closed Won flow uses a condition-based query approach to locate related Opportunities, demonstrating advanced Flow architecture without a circular object reference.

Carrier Assignment Task

Trigger: Load record created

New Load record is saved in Salesforce

Flow fires immediately via Run Immediately path

Task created: "Assign Carrier to Load: LOAD-XXXX"

Task assigned to load owner, due on pickup date

Delivered to Closed Won

Trigger: Status updated to Delivered

Load Status field changes to "Delivered"

Flow queries related Opportunity via Load__c field match

Opportunity Stage set to Closed Won, Close Date set to Delivery Date

Billing follow-up Task created, due in 2 days

Sample data

Production-scale records

All data was imported via Salesforce Data Import Wizard and DataLoader.io using generated CSV files — demonstrating real data migration skills, field mapping, and import troubleshooting across two object types.

Active lanes

Carrier partners

Shipper accounts

117

Load records

Opportunities

$502K

Total load value

$245K

Open pipeline

~28%

Avg brokerage margin

Build process

How it was built

Built entirely in a Salesforce Developer Edition org over a single session, following a structured phase-by-phase approach — custom objects first, standard object configuration second, automation third, data fourth, dashboard last.

Phase 1

Custom object design

Built Lane__c, Carrier__c, and Load__c from scratch. Evaluated and rejected Salesforce's native Shipment object as unsuitable for freight brokerage operations.

Phase 2

Field architecture

25+ custom fields including lookup relationships, formula fields for margin calculation, and picklists. Help text added to all key fields for adoption.

Phase 3

Validation rules

5 validation rules across Load__c and Carrier__c — enforcing data integrity at the point of entry. Carrier cost capping, delivery date requirements, insurance expiry checks.

Phase 4

Flow automation

Two record-triggered flows built and activated. The Closed Won flow uses a condition-query approach — avoiding a circular lookup relationship while achieving the same result.

Phase 5

Data import

117 loads ($502K) imported via Data Import Wizard. 50 opportunities imported via DataLoader.io after resolving Account ID lookup issues. Two import iterations required — both debugged and resolved.

Phase 6

Reporting & dashboard

Three summary reports built with custom formula columns for dollar margin. Five-component operations dashboard pinned to the FreightPath app home tab.

Architectural decisions

Key design notes

Native Shipment object rejected

Salesforce's native Shipment object is built for warehouse fulfilment and order management — not freight brokerage. A custom Load__c object was designed to reflect industry-specific requirements including carrier assignment, lane routing, and brokerage margin.

Lookup direction preserved

Opportunity looks up to Load, not vice versa. This avoids a circular reference. The Delivered to Closed Won flow uses condition-based record identification rather than a reverse lookup — a more sophisticated and maintainable solution.

Project-specific page layouts

Standard objects use Salesforce default layouts in this build. For production multi-project orgs, project-specific page layouts should be created to prevent cross-project field contamination — noted as a design decision for future builds.