BorderConnect Wiki

ACE Shipment CSV Upload Feature (ACE Manifest): Difference between revisions

← Older editNewer edit →
No edit summary
No edit summary
Line 1: Line 1:
{{note|This article is part of the [[ACE_Manifest_Software_User_Guide_(CBP)|BorderConnect ACE Manifest Guide]] and the [[BorderConnect_Software_User_Guide|BorderConnect Software User Guide]]|info}}
{{note|This article is part of the [[ACE_Manifest_Software_User_Guide_(CBP)|BorderConnect ACE Manifest Guide]] and the [[BorderConnect_Software_User_Guide|BorderConnect Software User Guide]]|info}}


{{#ev:youtube|bWwYYqaVZ0k|960|center|How to import shipments into an ACE eManifest.}}
{{#ev:youtube|bWwYYqaVZ0k|960|center|How to import shipments into an ACE eManifest}}


[[File:Company-pref.jpg|thumb|360px|right|Selecting Company Settings from the Account menu]]This guide provides '''instructions on how to upload a large volume of shipments into an ACE Manifest''', using BorderConnect's CSV upload feature in an [https://www.borderconnect.com/ace-e-manifest/index.htm ACE Manifest]. The CSV upload feature is designed for users who have a significant amount of shipments on a single trip and would like to avoid entering data separately for each shipment.
[[File:Company-pref.jpg|thumb|360px|right|Selecting '''Company Settings''' from the Account menu]]
== Enabling Import Buttons ==


The first step is to enable the ability to upload shipments. By default, companies will have this option disabled. To enable this option, once logged into BorderConnect, navigate to the top right corner and hover over the menu option '''Account''', and select '''Company Settings'''.  
This guide explains how to import a large number of shipments into an [[ACE_Manifest_Software_User_Guide_(CBP)|ACE eManifest]] using BorderConnect’s CSV upload feature.


Within the '''Company Settings''' page navigate down to '''Display ACE Import Buttons''' under the section '''eManifest Preferences'''. Once the option is selected to 'Yes', click 'Save' on the top left and your company has now enabled the ability to upload shipments.
This feature is ideal when you have many shipments on one trip and want to avoid entering each shipment manually.


== CSV File Format ==
== Overview ==


[[File:Display-ace-import.png|360px|thumb|right|Enabling ACE import buttons from Company Settings]]Before uploading your .csv file, you will need to download the .csv template file that [https://www.borderconnect.com/dist/ace-shipment-csv-template.csv BorderConnect provides here]. The headers in this file must remain intact and un-modified as they are required for the upload to be successful.
Using a BorderConnect CSV template, you can:


When saving your file, you will need to make sure that it is saved in CSV format, even if you are using a spreadsheet program to edit the file. Only CSV file format can be used for this feature.
* Upload shipments in bulk into a new or existing ACE eManifest
* Automatically validate shipment data before it is saved
* Resolve common formatting issues using clear import error messages
 
== Step 1: Enable ACE Import Buttons ==
 
[[File:Display-ace-import.png|thumb|360px|right|Enabling ACE import buttons in Company Settings]]
 
By default, shipment import buttons are disabled for many companies.
 
To enable them:
 
# Go to '''Account''' on the top menu
# Click '''Company Settings'''
# Scroll to '''eManifest Preferences'''
# Set '''Display ACE Import Buttons''' to '''Yes'''
# Click '''Save'''
 
Once enabled, import controls will appear when creating or editing an ACE eManifest.
 
== Step 2: Download the CSV Template ==
 
Before uploading, download the official BorderConnect template file:
 
* [https://www.borderconnect.com/dist/ace-shipment-csv-template.csv ACE Shipment CSV Template]
 
Important rules:
 
* Do not rename, remove, or reorder the column headers
* Save the file as '''CSV''' format before uploading
* CSV is required even if you edit it using Excel or another spreadsheet tool
 
== Step 3: Fill Out the CSV File ==
 
The template includes columns for:
 
* Shipment control number and shipment type
* Shipper and consignee details
* Commodity description, value, quantity, weight, and units
* Country of origin and additional shipment fields


== Field Specifications ==
== Field Specifications ==
Use the sections below to confirm data formatting before uploading.


=== SCN (Shipment Control Number) ===
=== SCN (Shipment Control Number) ===


*Unique identifier assigned to this shipment by the carrier.
The shipment control number uniquely identifies each shipment.
*Starts with carrier's 4 letter SCAC code followed by unique reference number.
*Must be alpha-numeric with no spaces or special characters, '''letters must be upper case'''.
*Minimum length: 8 characters.
*Maximum length: 16 characters.


When entering Shipments Control Numbers into the CSV document, you can enter them manually OR you have the option to use BorderConnect's system to automatically generate SCNs. To import shipments with automatically generated shipment control numbers in sequential order enter your SCAC + the word AUTOFILL (ex. ZZZZAUTOFILL). Using the autofill feature means that all SCNs must use the autofill feature. You cannot have a mix of autofill and non-autofill SCNs.
{| class="wikitable"
! Requirement
! Rule
|-
| Format
| Must start with a 4-character SCAC followed by your reference
|-
| Characters allowed
| Alphanumeric only, no spaces, no special characters
|-
| Uppercase
| Letters must be uppercase
|-
| Length
| 8 to 16 characters
|}
 
==== SCN AUTOFILL Option ====
 
BorderConnect can auto-generate SCNs in sequence.
 
To use autofill, enter:
 
* SCAC + AUTOFILL
Example: '''ZZZZAUTOFILL'''
 
Rules:
 
* If you use AUTOFILL, every shipment in the file must use AUTOFILL
* Do not mix AUTOFILL and manually-entered SCNs in the same upload


=== Shipment Type ===
=== Shipment Type ===


*The type of U.S. Customs clearance for this shipment.
Only the values below are valid and are case sensitive.
*Only the coded values listed in the table below can be used in this field.
 
Below are the valid Shipment Type values.<br>
(Please note that the shipment type values are '''case sensitive''', and the upload will fail if it is not entered ''exactly'' as specified below.)


{| class="wikitable"
{| class="wikitable"
|-
! Shipment Type
! Shipment Type
! Value
! Value
Line 60: Line 120:
|}
|}


=== Province Of Loading ===
=== Province of Loading ===


*The Canadian Province or Mexican State in which the shipment was picked up by the carrier.
This is the Canadian province or Mexican state where the shipment was picked up.
*Must use the 2 letter code of the Canadian province or 3 letter code of the Mexican state.


E.g. For a shipment loading in British Columbia, you must use BC. For a shipment loading in Guerrero, you must use GRO. State or province codes must be '''upper case'''.
* Canada: use 2-letter province code (example: BC, ON)
* Mexico: use 3-letter state code (example: GRO)
* Codes must be uppercase


=== Shipper ===
=== Shipper and Consignee ===


<u>Name</u>:
Use the following limits and formatting.
*The name of the shipper for this shipment.
*Minimum length: 1
*Maximum length: 60


<u>Address</u>:
{| class="wikitable"
*The street number and street name of the shipper for this shipment.
! Field
*Minimum length: 1
! Rule
*Maximum length: 55
|-
| Name
| 1 to 60 characters
|-
| Address
| 1 to 55 characters
|-
| City
| 1 to 30 characters
|-
| State/Province
| Use standard abbreviation, uppercase
|-
| Postal/Zip
| Must match required format for the country
|}


<u>City</u>:
Postal and zip formatting notes:
*The city name of the shipper for this shipment.
*Minimum length: 1
*Maximum length: 30


<u>State</u>:
* Canada: A1A1A1 or A1A 1A1
*The Canadian Province or Mexican State of the shipper for this shipment.
* Mexico: 12345
*Must use the 2 letter code of the Canadian province or 3 letter code of the Mexican state.
* U.S.: 12345 or 12345-6789
*State or province codes must be '''upper case'''.
 
<u>Zip</u>:
*The postal code of the shipper for this shipment.
*For Canadian postal codes, must be in the format "A1A1A1" or "A1A 1A1".
*For Mexican postal codes, must be in the format "12345".
*Letters must be '''upper case'''.
 
=== Consignee ===
 
<u>Name</u>:
*The name of the consignee for this shipment.
*Minimum length: 1
*Maximum length: 60
 
<u>Address</u>:
*The street number and street name of the consignee for this shipment.
*Minimum length: 1
*Maximum length: 55
 
<u>City</u>:
*The city name of the consignee for this shipment.
*Minimum length: 1
*Maximum length: 30
 
<u>State</u>:
*The American State of the consignee for this shipment.
*Must use the 2 letter code of the American state code.
*State codes must be '''upper case'''.
 
<u>Zip</u>:
*The zip code of the consignee for this shipment.
*Must be in the format "12345" or "12345-6789"


=== Commodity ===
=== Commodity ===


<u>Description</u>:
{| class="wikitable"
*A description of the goods in this shipment.
! Field
*Should use plain language and be sufficient to give officer good idea of what is being shipped.
! Rule
*Generic descriptions such as "freight of all kinds" are not allowed by customs.
|-
*Minimum length: 1
| Description
*Maximum length: 45
| 1 to 45 characters, plain language, must describe the goods
|-
| Value
| Numeric only, one decimal allowed, no symbols or commas
|-
| Quantity
| Whole numbers only
|-
| Quantity Unit
| Must use a valid 3-letter package code
|-
| Weight
| Whole numbers only, rounded
|-
| Weight Unit
| Pounds: L, LB, LBS, LBR  Kilograms: K, KG, KGM
|-
| Country of Origin
| 2-letter country code, uppercase
|}


<u>Value</u>:
A full list of country codes can be downloaded here:
*The value of the commodity, in U.S. Dollars.
* [https://www.borderconnect.com/data/countries.json Country codes JSON]
*'''Numeric only''', with one decimal allowed. Must not include dollar sign, commas, etc.
*System will round to nearest whole number, or up to 1 if less than 1 before transmitting to customs.


<u>Quantity</u>:
==== Package Type Codes ====
*The quantity of the lowest external packaging unit. (e.g. if shipments consists of 100 pieces packaged in 5 boxes sitting on 1 skid, the quantity should be entered as 5, because boxes are the lowest external packaging unit.)
*Numeric only, with no spaces or special characters. Decimal values not allowed.


<u>Quantity Unit</u>:
The Quantity Unit field must use one of the valid 3-letter package codes below and is case sensitive.
*The type of packaging for the commodity.
*Must use a 3 letter Package Type code from the table provided.
 
Below are the valid package types for the commodity. E.g. for Cartons, CTN must be entered.<br>
(Please note that the package type values are case sensitive, and the upload will fail if it is not entered exactly as specified below.)


{| class="wikitable"
{| class="wikitable"
Line 275: Line 322:
|}
|}


<u>Weight</u>:
== Step 4: Import the CSV Into an ACE eManifest ==
*The gross weight of the commodity.
*Numeric only, with no spaces or special characters. Decimal values not allowed, should be rounded to the nearest whole number.


<u>Weight Unit</u>:
To import shipments:
*The weight unit for the commodity.
*For Pounds, acceptable values are: "L", "LB", "LBS", "LBR"
*For Kilograms, acceptable values are: "K", "KG", "KGM"


<u>Country of Origin</u>:
# Start a new ACE eManifest or open an existing one for editing
*The country in which the commodity was manufactured, grown or otherwise produced.
# Use the import control near the top of the manifest page
*Must use the 2 letter country code for the country, in upper case letters.
# Click '''Choose File''' and select your CSV
*The full list of acceptable country codes can be [https://www.borderconnect.com/data/countries.json downloaded here].
# Click '''Save'''


== Importing Shipments ==
A message will confirm whether the import succeeded or list the rows that failed validation.


Once you have the CSV file populated with data in the correct format and your company has enabled the ACE shipment import buttons, you can then import the shipments.
Note: The button may reference JSON, but CSV files are accepted for this import tool.


To import the CSV file you must first start a new ACE Manifest or edit an existing ACE Manifest. Then, click the button "Choose File" to navigate locally and select the .csv file you would like to upload. Once the file is selected, click 'Save' on the top left. You will be brought to the ACE Manifest details page where a notice will let you know if the upload was successful, and/or if any errors in the import were found.
[[File:Ace-upload-shipments.png|800px|center]]


Next to the import button you will see that this button is for JSON files, but CSV files will also be accepted.
== Importing 10,000 or More Shipments ==


[[File:Ace-upload-shipments.png|800px]]
{{#ev:youtube|LfbA8W-R9S0|360|right|Importing 10,000 or more shipments into an ACE Manifest}}


== Importing 10,000 Or More Shipments To a Single ACE Manifest ==
BorderConnect supports importing up to 9,999 shipments per manifest by default.


{{#ev:youtube|LfbA8W-R9S0|360|right|Importing 10,000 or more shipments into an ACE Manifest}}By default users can only upload 9999 shipments into a single ACE Manifest, which is enough for most users who wish to import shipments into an ACE for example. However, in some cases more shipments will need to be added to a single ACE Manifest.
If you need 10,000 or more shipments on one trip, the process is:


Importing 10,000 or more shipments into a single ACE Manifest involves creating multiple ACE Manifests and importing no more than 9999 shipments into each separate ACE Manifest, then moving the imported shipments from the second (or third) ACE manifest, back to the original manifest using the Link Shipments to Trip feature.
* Create multiple manifests and import up to 9,999 into each
* Use '''Link Shipments to Trip''' to link shipments back to the original manifest for CBP processing


'''How to Import More than 10,000 Shipments to a Single ACE'''
=== High Volume Workflow ===


*1. Create your first ACE eManifest, so in the drop down menu select ACE eManifests and select Start New ACE Manifest, and after you enter all your trip details, at the bottom you have the option to upload shipments directly into your ACE Manifest in either a JSON or CSV file format. Now click and locate or drag the file into the manifest. Then on the top left, hover over Save and then select Save and View Trip Details. If you’re adding a significant amount of shipments it may take some time to process the shipment upload so it’s important to be patient during this process. Once this process is complete, you’ll be brought to the ACE Manifest Details page where you can see that your shipments have been successfully imported into the ACE Manifest.
{| class="wikitable"
! Step
! What You Do
|-
| 1
| Create the original manifest, import the first batch, save and view trip details
|-
| 2
| Create a second manifest with a modified trip number (example: add B)
|-
| 3
| Enable Show All Fields and set '''Link Shipments to Trip''' to the original trip
|-
| 4
| Import the second batch and save
|-
| 5
| Repeat for additional batches (example: add C, D) if required
|-
| 6
| Send the first manifest to CBP and wait for acceptance
|-
| 7
| Send each linked manifest to CBP using '''Link Shipments to Trip''' transmission
|}


*2. Create a new ACE Manifest, so at the top under ACE eManifest select Start New ACE Manifest. For this second trip number you can use the same trip number as previously, only this time adding a B to the end. Next on the top right, ''Show All Fields'' will need to be enabled, which will reveal the field '''Link Shipments to Trip'''. So click into Link Shipments to Trip and assign the original trip that you created initially. This will link all of this trips shipments to that manifest.  
[[File:Link-shipments-to-trip-field.png|800px|center]]


[[File:Link-shipments-to-trip-field.png|800px]]
[[File:Send-link-shipments-to-trip.jpg|300px|thumb|center|Sending Link Shipments to Trip to CBP]]
 
*3. Next enter the remainder of the trip details, and then at the bottom click and locate or drag the second JSON or CSV file that contains the additional shipments into this manifest. Then go to the top left and hover over Save and select Save and View Trip Details. And just like the first large batch of imports, you will need to be patient as these shipments are imported into BorderConnect. Once the import is complete you will be brought to the ACE Manifest Details page.
 
If you had even more shipments to add to the original manifest, just repeat the process for the second manifest that we created, and create your third ACE manifest while adding “C” to the end of the trip number and import the additional shipments on that manifest.
 
*4. Next Send the first ACE Manifest to CBP, so under ACE Manifests click Search ACE Manifests and then click into or view the original ACE that was created from the ACE Manifest listing page. Once in the ACE Manifest Details page, hover over Send to CBP at the top and click Send Complete Manifest which will move the status to two yellow bars, transmitted. And because this manifest contains a significant amount of shipments, it will take much longer than usual to get processed by CBP and accepted, in some cases up to 20 minutes. But once it does get accepted, it will turn to three blue bars.
 
*5. After the first ACE is on file with CBP you will have to send the second manifest that was created, so again, under ACE eManifests click Search ACE Manifests and View the second ACE Manifest that was created. Once in it, hover over Send to CBP and click ''Link Shipments to Trip'' which will transmit your manifest to CBP linking these shipments to the original manifest at the same time. And after some time it will get accepted and move to three blue bars. Now all the shipments have been successfully accepted and linked to the original first manifest that we created.
 
[[File:Send-link-shipments-to-trip.jpg|300px]]


== Common Import Errors ==
== Common Import Errors ==


Listed below are some of the common errors users receive when trying to upload their .csv file into BorderConnect.
This section lists common CSV upload errors and how to correct them.


'''Shipment Control Number Errors'''
=== Shipment Control Number Errors ===


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Can't perform import since AUTOFILL shipment numbers are combined with explicitly stated shipment control numbers.
Can't perform import since AUTOFILL shipment numbers are combined with explicitly stated shipment control numbers.
</pre>
</pre>


Some of the Shipment Control Numbers in your file are using your SCAC plus AUTOFILL, and some are not. To use the Autofill feature, all Shipment Control Numbers must be filled in as SCAC plus AUTOFILL.
Cause:
* Some rows use SCAC+AUTOFILL and others use manual SCNs
 
Fix:
* Use AUTOFILL for all rows or remove AUTOFILL entirely


It is currently also possible to get this error because there are blank rows at the bottom of your CSV file. You may want to use a plain text editor to check your file for rows consisting of only commas and remove those rows from the file.
Also check for blank rows containing only commas near the bottom of the file.


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
SCAC Code [AAA5] is invalid. Must be 4 alphanumeric characters. [AAA5459071]
SCAC Code [AAA5] is invalid. Must be 4 alphanumeric characters. [AAA5459071]
</pre>
</pre>


The SCAC code has an incorrect amount of characters. SCAC should be four letters.
Cause:
* SCAC is not exactly 4 characters
 
Fix:
* Correct SCAC to 4 alphanumeric characters


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Shipment Control Number is invalid, it must be 8-16 alphanumeric characters with no spaces and letters must be uppercase. [AAAA545907321321321131]
Shipment Control Number is invalid, it must be 8-16 alphanumeric characters with no spaces and letters must be uppercase. [AAAA545907321321321131]
</pre>
</pre>


The Shipment Control Number has too many characters. SCN must be between 8-16 characters.
Cause:
* SCN too long or invalid format


Fix:
* Ensure 8 to 16 characters, uppercase, no spaces


'''Shipment Type Errors'''
=== Shipment Type Errors ===


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Shipment Type [SECTION 321] is invalid [AAAA5459071]
Shipment Type [SECTION 321] is invalid [AAAA5459071]
</pre>
</pre>


The Shipment Type value is incorrect and should be "SECTION_321". Double check acceptable shipment type values and try to upload again.
Cause:
* Incorrect value format


Fix:
* Use the valid value exactly, such as '''SECTION_321''' if applicable for your template version, or match the official list shown above


'''Shipper Errors'''
=== Shipper Errors ===


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Province of Loading code [BX] unrecognized. [AAAA5459071]
Province of Loading code [BX] unrecognized. [AAAA5459071]
OR
OR
Line 387: Line 438:
</pre>
</pre>


The Province of Loading for the shipper is not recognized. Format must use the acronym "BC". (ex. "ON", "MB", "NS", etc.)
Fix:
* Use province/state abbreviations only, example: BC


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
Shipper Name [...] invalid. Must be between 1 and 60 characters, with no accents or other invalid characters. [AAAA5459091]
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Shipper Name [Demo Business Incorporated CO Steven Stevenson Incorporated of Vancouver bla bla] invalid. Must be between 1 and 60 characters, with no accents or other invalid characters. [AAAA5459091]
</pre>
</pre>


The Shipper Name has too many characters. It must be between 1 and 60 characters.
Fix:
* Shorten the name to 60 characters or fewer


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Shipper Canadian Postal Code [VSS 1A1] invalid. [AAAA5459219]
Shipper Canadian Postal Code [VSS 1A1] invalid. [AAAA5459219]
</pre>
</pre>


The shipper postal code is invalid. Should be (letter-number-letter number-letter-number)
Fix:
 
* Ensure valid Canadian postal code format, example: V5S 1A1


'''Consignee Errors'''
=== Consignee Errors ===


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Consignee State [California] is invalid or does not match with country [US]. [AAAA5459219]
Consignee State [California] is invalid or does not match with country [US]. [AAAA5459219]
</pre>
</pre>


The state of the consignee is not recognized. Format must use the acronym "CA". (ex. "NY", "WA", "FL", etc.)
Fix:
* Use 2-letter U.S. abbreviations, example: CA


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Consignee U.S. Zip Code [4321] invalid. [AAAA5459219]
Consignee U.S. Zip Code [4321] invalid. [AAAA5459219]
</pre>
</pre>


The consignee address has a zip code that is invalid. Zip codes must be five character numbers or ten character numbers (ex. 45180-6789 and must include the dash if the ten character format is used).
Fix:
* Use 5 digits or ZIP+4 format


<u>Note</u>: It is common for spreadsheet programs to strip leading zeroes from fields. E.g. zip code beginning with a zero such as 04321 might be saved as 4321 by the spreadsheet program, which would be an unacceptable zip code for upload to BorderConnect.
Note: Spreadsheet tools can remove leading zeroes.
A ZIP like 04321 may become 4321 and fail validation.


It may be necessary to look for solutions within the program that you're using to generate the CSV file to remedy this issue. For some spreadsheet programs, saving the number as ''="04321"'' instead of just ''04321'' works.
A common workaround is to format the cell as text or use:
''="04321"''


'''Commodity Errors'''
=== Commodity Errors ===


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Unknown packaging unit [box]. [AAAA5459219]
Unknown packaging unit [box]. [AAAA5459219]
</pre>
</pre>


The package type is in the incorrect format. The correct variable for the box package type is "BOX". Remember that values are case-sensitive.
Fix:
* Package codes must match exactly, example: '''BOX'''


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Shipment commodity weight is invalid. It must be numeric [0.63]
Shipment commodity weight is invalid. It must be numeric [0.63]
</pre>
</pre>


Commodity weight must be listed in whole numbers only. Should be rounded to the nearest number, or up to 1 if less than 1.
Fix:
* Weight must be a whole number, round up to 1 if under 1


<pre style="white-space: pre-wrap;  
<pre style="white-space: pre-wrap; word-wrap: break-word;">
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
Commodity weight unit [POUNDS] is invalid. [AAAA5459219]
Commodity weight unit [POUNDS] is invalid. [AAAA5459219]
</pre>
</pre>


The unit of measure for the weight is incorrect. It must follow the value guidlines for import. In this case if pounds was the unit of weight, the correct value is "LB", "L", "LBS" or "LBR"
Fix:
* Use valid units: L, LB, LBS, or LBR


[[Category:ACE Manifest Guide]]
[[Category:ACE Manifest Guide]]
[[Category:BorderConnect Software User Guide]]
[[Category:BorderConnect Software User Guide]]
Retrieved from "https://wiki.borderconnect.com/index.php?title=ACE_Shipment_CSV_Upload_Feature_(ACE_Manifest)"