Shipper Accounts

A shipper account identifies the counterparty on an opportunity. The App Administrator keeps its name, code, contact name, address and eligibility note current within the operating organization. The Relationship Owner selects that counterparty when opening an opportunity, so a manager reviewing a lane can see which shipper relationship the work belongs to. The account is a directory record; the actual pursuit sits on the opportunity.

The organization is the boundary for the account and team membership. It carries its own name, code, active flag, time zone and currency. The team member record links a platform user to the organization with a role name and active flag. That combination gives administrators a practical roster to review before assigning an opportunity or asking a manager to make a decision.

• Account identity. Keep a stable account code and contact name so the same counterparty can be found when a new opportunity is entered.
• Operating scope. Associate the account with its organization and use the active flag when deciding which relationships remain in current use.
• Membership. Keep team member names, role names and time zones aligned with the organization that owns the account.

A typical case starts when a shipper asks for recurring loads between two ZIP codes. The App Administrator confirms the account and its organization. The Relationship Owner opens the opportunity against that account and records the expected close date. The lane details then belong to that opportunity, which keeps the relationship directory separate from each commercial decision.

Agree how account codes are assigned and who maintains contact names and eligibility notes. Decide when an account becomes inactive, especially when earlier opportunities still point to it. Set the operating organization’s currency and time zone before owners start entering expected dates. Identify who can change team membership and who may only read the roster. These choices keep the same shipper name from being interpreted differently across organizations.

The account note should be concise and useful to an owner qualifying a request. If the team checks a counterparty in another system, name that connection in the operating procedure; the account directory is the place to keep the resulting note. A manager can then examine the note alongside the opportunity’s activity and attachments during review.

Choose an active shipper account and assign an opportunity to a Relationship Owner in the same organization. Confirm the owner can find the account by code, see the contact name and create the opportunity against the intended counterparty. Have the App Administrator change the contact detail and confirm the opportunity still points to the same account. Then ask an Auditor to read the relationship without changing it. This rehearsal catches duplicate account naming and unclear ownership before pipeline review begins.

• Active Shipper Accounts — Current counterparties with contact and organization context for starting a pursuit.
• New Shipper Opportunities — Fresh pursuits tied to a counterparty and an accountable owner.

Start with opportunity intake, then see implementation for account and membership setup.