Connect freight providers with clear workflow boundaries

Buyer value in the implemented workflows

Verified EasyPost or ShipEngine credentials let an eligible packed fulfillment request estimate-only parcel rates before an operator chooses how to ship. ShipEngine also supports a separate attended label purchase for one measured, closed LPN.

• EasyPost and ShipEngine rate previews require a packed fulfillment, complete origin and destination addresses, and positive weight and dimensions for every LPN.
• Rate previews are estimates only: they do not buy a label and support at most ten packed LPNs per request.
• The ShipEngine label purchase requires a separately confirmed rate for one measured, closed LPN and does not mark the fulfillment shipped.

TMS and Inventory Tracking prerequisites

The organization needs the TMS module enabled. A member with TMS read access can view connection status, while a TMS module administrator must save, test, or disconnect provider credentials. Parcel-rate previews and attended label purchases run in Inventory Tracking under the separate access and destination prerequisites below.

• Organization-level ownership Each provider configuration belongs to the OLT organization and is available to the separate workflows that are allowed to consume that verified connection.
• Provider credentials Obtain the required endpoint and client credentials or API key from the provider account before setup. OLT credentials are not provider credentials.
• TMS administrator for changes Only a TMS module administrator can save, test, or disconnect a provider. TMS read access is sufficient only to view status.
• Inventory Tracking read access Parcel-rate previews require Inventory Tracking read access.
• Inventory Tracking write access Attended ShipEngine label purchases require Inventory Tracking write access.
• Destination classification Every parcel-rate preview requires a Residential or Commercial destination selection.

Credential and verification steps

Configuration and verification are separate steps so saving a secret never implies that a provider workflow is ready.

1. Open Freight and Parcel Providers In Settings → Integrations, open Freight and Parcel Providers and choose Project44, MacroPoint, EasyPost, or ShipEngine.
2. Save the required credentials OLT encrypts the organization-level values at rest. Saving makes the connection unverified, and blank secret fields preserve values that were already stored.
3. Test the saved connection Use Test connection after saving. A successful supported provider check marks the connection active; a failed check keeps it inactive.
4. Use a separate eligible workflow A verified connection is consumed only when an implemented packed-rate or attended-label workflow explicitly uses it. Configuration alone starts no provider work.

Provider credentials, checks, and current boundaries

The four setup choices do not share the same verification or downstream workflow support.

• Project44

  Credentials: Approved HTTPS Project44 endpoint, OAuth client ID, and client secret; an OAuth scope can also be stored when the account requires one.

  Verification: OLT asks Project44 for an OAuth client-credentials token. Project44's response verifies whether those OAuth credentials are accepted.

  Implemented workflow and boundary: Credential verification only. OLT does not currently consume Project44 shipments or tracking events.

• MacroPoint · Descartes

  Credentials: Approved HTTPS MacroPoint or Descartes endpoint, client ID, and client secret.

  Verification: OLT validates the HTTPS provider host, but the connection remains inactive until its account-specific Descartes API contract can be verified.

  Implemented workflow and boundary: No MacroPoint shipment or tracking workflow runs while the connection is inactive.

• EasyPost

  Credentials: EasyPost API key.

  Verification: OLT authenticates the API key against EasyPost's account endpoint and can activate the accepted connection.

  Implemented workflow and boundary: Estimate-only parcel-rate previews for eligible packed fulfillments. EasyPost label purchase is not implemented in this workflow.

• ShipEngine

  Credentials: ShipEngine API key.

  Verification: OLT authenticates the API key against ShipEngine's carriers endpoint and can activate the accepted connection.

  Implemented workflow and boundary: Estimate-only parcel-rate previews plus a separate attended label purchase for one measured, closed LPN. Buying the label does not mark the fulfillment shipped.

Evaluate OLT with your provider requirements

Contact OLT when the documented freight workflow matches your operation. Access is by invitation.