Reference Data: Estes REST Client (Billing) Account Fields [Guide]

Modified on Wed, 26 Aug at 7:30 AM


Onboarding and Configuration	Baseline Account	(Billing) Account	Order-Level Fields
		You are here

This reference lists the carrier-specific Estes (REST) Client (Billing) Account fields used in techSHIP.

Use it together with the linked Client (Billing) Account setup steps: the setup guide covers the shared configuration flow, while this article defines the confirmed field values, field behavior, and client-specific carrier configuration details.

For a complete overview of supported carriers and related setup guides, refer to techSHIP supported Carriers - Master List [Guides List].

Review and complete Reference Data: Estes (REST) Baseline Account Fields [Guide] before configuring the Client (Billing) Account so the carrier connection is available.

TABLE OF CONTENTS

Adding a Client (Billing) Account
Carrier-Specific Instructions
Next Steps (Optional)

Adding a Client (Billing) Account

Follow the UI Navigation steps in How to Add a Carrier Billing Account [Step-by-Step guide], using the carrier-specific values provided in this guide.

Go to

Essential Configuration	Carrier-Specific This article

Carrier-Specific Instructions

	Return to

Essential Configuration	Carrier-Specific

The Carrier tab contains the Client (Billing) Account fields used to define confirmed carrier-specific behavior for this client. Highlighted fields indicate mandatory and optional configuration groups.

[Insert screenshot here]

Service code: Select the default service used for shipments processed through this Client (Billing) Account.

Package type: Defines the package type stated to the carrier for shipments processed through this Client (Billing) Account.

Freight Class: Sets the freight class used when the order does not provide a different value. Consolidated commodity line items use the Billing Account freight class.

Consolidate commodity line items: When enabled, techSHIP submits one consolidated commodity line item per handling unit instead of one line item per SKU. The generated BOL displays the configured consolidated commodity description.

Override WMS Service Code: Controls whether the configured Billing Account service code is used instead of the service code received from the WMS.

The customer's Estes account number: Identifies the Estes account used for this client’s shipping charges.

Shipment and BOL reference fields: Use Shipment Id (SID) number, Master Bill of Lading number, Purchase Order, and Bill of Lading number to send selected dynamic values or fixed reference values with the shipment.

Default Freight Payment Terms: Defines the freight payment terms used unless the order provides a different value.

Contact and notification fields: Use Contact first name, Contact last name, and the notification checkboxes to define contact and notification details for shipments processed through this account.

Sender address: Defines the sender name and company for shipments processed through this Client (Billing) Account. Use Override sender address when the sender address must differ from the Baseline Account sender address.

Broker and billing address controls: Use Specify customs broker and Override billing address when those shipment address details must be provided for this client.

Click Save before continuing so the configured settings are applied.

Next Steps (Optional)

Optionally, after the Client (Billing) Account is configured and saved, continue with Reference Data: Order-Level Estes (REST) Fields [Guide].

			Go to

Onboarding and Configuration	Baseline Account	(Billing) Account	Order-Level Fields

Name	Host	Duration	Description
_fw_crm_v	techdinamics.freshdesk.com	1 year	Freshchat/Freshworks cookie (Used to track Visitor/User identity and chat sessions performed by the User).
_x_w	techdinamics.freshdesk.com	Session	Contains the shard ID at which the account runs on.
_x_m	techdinamics.freshdesk.com	Session	Contains the state of the shard.
_helpkit_session	techdinamics.freshdesk.com	Session	Your secret key for verifying cookie session data integrity. If you change this key, all old sessions will become invalid!
helpdesk_node_session	techdinamics.freshdesk.com	Session	An encrypted hash that stores the secret key and id of the login attempt.
user_credentials	techdinamics.freshdesk.com	2 months	Used for user authentication.
wf_order	techdinamics.freshdesk.com	Session	Used to check in which the order the tickets are filtered for custom ticket filters eg: due_by, agent_responded_at, requester_responded_at, etc.
wf_order_type	techdinamics.freshdesk.com	Session	Used to check if the order is ascending or descending for custom ticket filters.
wf_filter	techdinamics.freshdesk.com	Session	Denotes which filter is applied for the tickets list.