FAQs

Carriers handle addresses differently, and US territories may not always be allowed as domestic shipments within the US. When errors are encountered with a US territory destination (AS, GU, MH, PR, VI), it may be necessary to switch between domestic and international services, as well as providing line item and customs details. This will depend on the carrier’s requirements, and Transtream supports both options, but testing different services may be required for each carrier.

For example:

• UPS API and FedEx Web Services will both ship to US territories when the shipment is configured as international. The territory name can be set as the destination country and the state can be left blank. Line item and customs detail will be required.
• USPS Postage will allow for domestic shipments, with the territory name as the state and the country as UNITED STATES.

If the destination address is not validating correctly (either giving an error or is outside the locations supported by a carrier), you can use the Administration App to modify the default address validation carrier. Selecting another carrier as the default may allow for different results that more accurately match the requirements of the shipping carrier in use. Please see Admin set up.

Please note: each carrier handles address validation differently, when supported, but the VALIDATE button only returns what the carrier provides back. If an address does not validate as expected, it may be because the carrier cannot find the address or a suitable suggestion as entered. Confirming the address is entered correctly or verifying online may help highlight an issue. Typically, alternate spellings of street or city names, an incorrect postal code, or a recently-incorporated destination are the most likely causes. Please see Use validation in Apps.

When creating an international shipment (or other shipment that requires commodity data to ship), at the bottom of the app page you will need to select Add Row.

In the line item fields that appear at the bottom you will need to fill in the following:

• Part Number
• Description
• Weight
• Unit Value
• Add to Package

• Country of Origin
• Value (may be optional)

When launching the HubCapp Peripheral Agent and the error above is seen, or a Microsoft .NET Framework unhandled exception occurs, the issue can be resolved by modifying a variable in the Peripheral Agent’s configuration.

To do so, navigate to your Peripheral Agent installation directory, which by default is “C:\Program Files (x86)\HubCapp Peripheral Agent\”.

Open the file “setup.xml” in a text editor.

Change the value for “MinPortNumber” from 50000 to 60000.

Save the file and restart the Peripheral Agent.

Yes, Transtream is FIPS compliant and there are various password standards in place. For more detail on password standards see Forms. For more detail on FIPS accross our software see Security.

For customers not using Single-Sign On - Minimums can be set for: Password Length, Uppercase Characters, Numeric Characters, Special Characters, Password Age, Password History Count. Maximums can be set for Password Age and Repeating Characters. Passwords may also be blacklisted. For more detail about where password controls are set see Transtream Setup Reference.

Inbound access is limited to HTTPS TLS 1.2

Only rest data is encrypted, upon request.

No changes need to be made on the servers regarding the FedEx Web Services Security certificates renewal.

The CarrierID is listed at the top of each carrier's reference page. See Carrier Components and navigate to your chosen carrier.

Yes. This can be done via FedEx Web Services. For more detail on FedEx Web Services carrier see FedEx Web Services. Here is further configuration detail:

1. Select the appropriate Freight service type. For Standard and Premium the service type is Priority. The service type for Basic and Basic by Appointment can be Priority or Economy. FEDEX_FREIGHT_PRIORITY
2. The consignee’s contact information, including mobile phone is included in the recipient information loop.
3. The FedEx Freight Direct keyword BASIC, BASIC BY APPOINTMENT, STANDARD or PREMIUM is included in the ‘DeliveryInstructions’ element of the shipping transaction

Using Designer, replace the following elements of the below script with the relevant values from your setup: CarrierServiceSnippetName and Test Rate Group.

Yes, there are two roles: Admin with access to everything, and User with access to their assigned Apps only. For more detail see Admin App Users.

Ensure your carrier accounts are properly configured, and that the Account Type is set to Consolidated Shipping. See Consolidated Shipping.

Scheduled tasks are run according to server time; location time zone is ignored. Additionally, note that the server time is not displayed within the Task Scheduler. See Task Scheduler.

A total of 4 requests are sent to carriers in 24 hours (one request every 6 hours). See Batch Tracking task.

If a user is enabled, this provides them with access to Transtream. For example, an Admin may be configuring users with access but does not want the user enabled until the system is live, or they might want to disable a user who is on family leave for added security. A user becomes locked if there are authentication issues, for example, if there are too many login attempts or the user's password has timed out. Unlock users by resetting their password.

1. Navigate to the View App. Search using your Overstock Order Number.
2. Find your order. Go into Tracking History and check the current status. This can be:
• Processed - no 990 message has been retrieved. Move to step 3.
• Load Accepted - a 990 message was retrieved by the carrier. Check the App's Package Detail and Documents tab for associated detail.
3. Navigate to Diagnostics in Product Admin.
4. Locate and select the EDIMessageCheck function in the logs. Then, find the EDI File Trace Event.
5. If Overstock received the 990, the logs will show Found file '900.edi' and indicate that it was sucessfully downloaded.

For tracing, recreating, and troubleshooting problems in MS SQL Server you can use SQL Profiler. This tool is used to assist with troubleshooting, for capturing data and to monitor errors. With this software you can capture data about each event and save it to a file or table. When using this tool follow the below steps:

1. Open Microsoft SQL Server Management Studio
2. Navigate to the Tools menu and open SQL Server Profiler
3. Select your events from Trace Properties and click Run

Check for these configuration errors:

• If there are special characters in the printer name that are incompatible with HubCapp.
• If there are duplicate spaces in the printer name.
• If Windows User Account Control (UAC) is restricting HubCapp’s ability to communicate with the printer.
• If the printer drivers are not up to date or the printer is configured improperly.

The View App will not report the most up to date shipment status if the Batch Tracking task has not been enabled and configured correclty in the Task Scheduler. For set up detail, see Batch Tracking.

Hubcapp and SQL Server 2016 supports Service Pack version SP2.

• a. We use a three number system to indicate version.release.patch (8.24.1). Version changes are infrequent and indicate a major platform upgrade. Releases are generally 4-8 weeks apart and introduce new features and support fixes.
• b. Patches occur as necessary to address security items or support fixes.

No. Businesses or organizations comply with GDPR. Product does not. Through the principles of Data Protection by Design, Transtream can help businesses or organizations comply with GDPR. Pierbridge product is developed and tested to exacting data protection standards.

When it is necessary to contact Pierbridge Support submit an email with all pertinent information to help@Pierbridge.com, including:

• Description of the issue.
• Product and Product version.
• Detailed summary of the issue.
• Screenshot of any error messages.
• Your contact information.