Asendia USA Onboarding Requirements and Configuration Guides [Information]ok

Modified on Fri, 28 Aug at 8:09 AM


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

This article is the central hub for adding Asendia USA 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 Asendia USA 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)
Username	Obtain from Asendia USA or the customer’s authorized Asendia USA account contact.
Password	Obtain from Asendia USA or the customer’s authorized Asendia USA account contact.
API key	Obtain from Asendia USA or the customer’s authorized Asendia USA account contact.
API data source	Confirm the value to configure in the Baseline Account.
Processing location	Confirm the value to configure in the Baseline Account.
Sender Address	Confirm the sender company, address, email, and phone values to configure in the Baseline Account.
Account number	Confirm the customer’s Asendia USA account number for the Client (Billing) Account.

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
Carrier code	Confirm the carrier connection uses ASENDIAUSV2 in techSHIP.
Environment	Confirm whether the setup will use Test or Prod.
Sender Address	Confirm the Baseline Account Sender Address is available before configuring client billing accounts.
Label format	Confirm the required label format. Confirmed supported formats are ZPL, PDF, and PNG.

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	Supported: ZPL, PDF, and PNG.
References	Supported: Reference 1, Reference 2, Reference 3, and Reference Types.
BOL	Not supported.

For a comprehensive guide on how to use label references, see: Using order References in your labels [Step-by-Step guide].

Operational Details

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

Asendia USA supports international shipping.
Asendia USA supports rate retrieval, standard shipment processing, label generation, tracking output, and voiding.
Supported label formats are ZPL, PDF, and PNG.
Supported reference fields are Reference 1, Reference 2, Reference 3, and Reference Types.
Asendia USA supports Paper Scan Form at Manifest, manifest generation, customs item data, processing location, overriding sender address, and overriding return address.
When Override sender address is disabled on the Client (Billing) Account, applicable sender information is sourced from the Baseline Account.
When Override sender address is enabled on the Client (Billing) Account, the Billing Account sender override is used.

Next Steps

After reviewing the onboarding requirements, continue with the Reference Data: Asendia USA 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.