Estes REST Onboarding Requirements and Configuration Guides [Information]

Modified on Wed, 26 Aug at 7:37 AM


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

This article is the central hub for adding Estes (REST) with techSHIP. It summarizes onboarding requirements, links the related configuration guides, and lists confirmed carrier-specific constraints.

To review all supported carriers and their specific requirements, see: techSHIP supported Carriers - Master List [Guides List].

TABLE OF CONTENTS

Onboarding Requirements
- Information to be Provided
- Settings to be Verified
Setup Articles
Carrier Specifications and Constraints
- Labels
- Operational Details
Next Steps

Onboarding Requirements

Before configuring Estes (REST) in techSHIP, gather the required credentials and verify the required account settings.

Information to be Provided

The following credentials and data points are mandatory to establish the connection. Ensure you have these items available before starting the setup:

DATA ELEMENT	SOURCE (HOW TO OBTAIN)
Estes username	Obtain from an Estes representative.
Estes password	Obtain from an Estes representative.
Estes API Key	Obtain from an Estes representative.
Label type	Confirm the label type to request through the carrier connection.
Induction Address	Confirm the warehouse induction address used as the Sender address.

Settings to be Verified

The following account configurations must be validated to prevent errors during the connection setup or the shipping process:

FEATURE/SETTING	VALIDATION ACTION
Estes credentials	Verify that the Username, Password, and API Key have been provided by an Estes representative.
Label type	Verify the label type before configuring the Baseline Account label settings.
Induction Address	Verify the warehouse induction address before configuring the Baseline Account sender address.

Missing or non-validated setup information may delay the setup process.

Setup Articles

Use the setup articles below to complete the set up in order. Start with onboarding requirements, then configure the Baseline Account, Client (Billing) Account, and optionally, Order-level settings. Select an article number to open the corresponding guide:


COMPONENT	ONBOARDING REQUIREMENTS	BASELINE ACCOUNT	(BILLING) ACCOUNT	ORDER-LEVEL FIELDS
Mandatory
Scope	Requirements	Carrier	Client	Transaction
Description	Identifies the required onboarding information and organizes the related setup guides for this carrier.	Establishes the carrier connection. Must be created first.	Connects a specific client to the Baseline. At least one is required to ship.	Defines order-level fields and settings used when processing shipments for this carrier.

Carrier Specifications and Constraints

This section outlines confirmed operational behaviors, document support, label support, and limitations specific to this carrier.

Labels

The following table summarizes confirmed document and label support:

ITEM	SUPPORTED
Label	Formats: PDF, ZPL Labels are generated through the Estes (REST) carrier connection using the configured label type.
References	Client (Billing) Account reference fields can send selected dynamic values or fixed values with the shipment.
BOL	Estes BOL documents are generated for processed shipments.

Operational Details

This section lists confirmed operational rules and limitations for this carrier. Include only constraints that have been validated for this carrier:

The Client (Billing) Account can consolidate commodity line items when Consolidate commodity line items is enabled.
When commodity consolidation is enabled, techSHIP submits one consolidated line item per handling unit instead of one line item per SKU.
When commodity consolidation is disabled, techSHIP preserves SKU-level commodity line items.
Consolidated commodity line items use the configured consolidated commodity description, handling-unit weight, package data, and freight class.
The Estes BOL displays the configured consolidated commodity when consolidation is enabled.
Carrier-controlled supplemental or customer-order pages may still be present on generated documents.

Next Steps

After reviewing the onboarding requirements, continue with the Reference Data: Estes (REST) Baseline Account Fields [Guide] article to configure the carrier connection in techSHIP.

	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.