Import the original 47-column CSV
Download the 47-column Test sample, review its rows, and follow each order through release and simulated tracking.
This guide uses the original 47-column CSV profile in shared Test. Start with Test workspace and key setup if you have not signed in yet. You can import through the console without an API key.
Download and prepare the sample
Download the original 47-column Test CSV. It contains fictional recipient and product data. Replace its product and shipping values with values from your current Test workspace before importing.
- Keep all 47 column names in their original order, including columns you leave blank.
- Change
Order #to a fresh reference for each new business order, such asTEST-ORDER-1002. - Check
Item SKUagainst your current Test catalog and confirm sufficient inventory. - Fill in the recipient name, phone, street, city, state or region, postal code and country.
Buyer Emailsupplies the recipient email. - Set
Item Quantityto a positive whole number andItem Unit Priceto the sale price per item. - Save as CSV without adding spreadsheet columns or replacing the headers with the generic Mailing CSV template.
Keep identifiers such as Order #, SKU and postal code as text in your
spreadsheet so leading zeroes are preserved. To add another item to the same
order, add a row with the same Order # and identical order-level values,
then change that row’s item fields.
The sample’s Shipping Service is fictional source data. Its value is
retained, while Test fulfillment uses the service configured for the workspace.
A CSV cannot configure a new carrier or select a physical warehouse.
Upload, review and create
- In Test mode, open Orders and choose Import CSV.
- Select the original 47-column CSV profile and choose your file.
- Review the parsed recipients, product matches, quantities and prices. Previewing creates no orders.
- Resolve flagged or incomplete rows in the review. Do not submit until the intended groups are ready.
- Select the ready groups, review the confirmation and submit them.
- Open the recorded orders from the result or from Orders in Test mode.
Orders start On hold. Review and correct them before explicitly releasing them. Follow release, shipment simulation and tracking to finish the walkthrough. The simulator is available to organization Owners and Admins in Test actions.
What the columns mean
| Columns | Meaning in Test |
|---|---|
Order # |
Required durable external order reference. Use the same reference to identify the same business order across CSV and API. |
| Recipient name, company, phone and address | The order’s reviewed recipient. Recipient Full Name wins; first and last name fill it when empty. |
Buyer Email |
The recipient email saved on the order. |
Item SKU, Item Name / Title, Item Quantity, Item Unit Price |
Product match and order lines. Unit price is the sale price, not the customs declaration. |
Shipping Service |
Preserved source information; it does not install or override Test shipping configuration. |
| Remaining payment, dimension, note, gift, custom and item-metadata columns | Preserved source record. They do not create a payment, select a physical origin or grant staff actions. |
The original file has no declared-value override column. It uses the matched
products’ customs defaults and needs compatible product declarations. For
distinct per-item USD customs values, use manual entry or the ordinary API as
described in Test orders. Changing
Item Unit Price does not change a customs declaration.
Re-imports, corrections and API identity
Uploading the same initial order again is a replay, not a request for another shipment. Vault keeps one business order for the reference within the organization and Test mode. New submission keys, another API key or another channel do not make it a new business order.
For API requests that name the same CSV order, use the profile’s fixed source
value and the CSV’s exact Order # as its reference:
{
"externalIdentity": {
"source": "original_47_column_csv",
"reference": "TEST-ORDER-1002"
}
}
This is the identity portion of a create request, not the whole body. The
source value is part of the import contract; it is not returned by an order
read. Keep the initial recipient, lines, quantities, service and declarations
identical for replay. Changed intent under the same reference conflicts.
Retain the original CSV and import/operation IDs. If the initial action was
an API request, retain that request, including its quote and source selections.
Do not reconstruct initial intent from an order that has since been edited.
Use the held-order edit flow for corrections; changing the CSV reference to
work around a conflict risks creating another order. A CSV import creates its
orders On hold. An API or MCP create that names a CSV reference also stays On
hold unless it sets hold: false. Only a held order can be corrected.
If submission has an unknown result, retain the import and operation IDs and read the recorded outcome. Do not upload a renamed copy or invent a fresh reference to retry it. A replay after an accepted held correction cannot undo that correction.
Troubleshooting
| Result | Next step |
|---|---|
| Header or format error | Restore the downloaded sample’s 47 headers and select the original 47-column CSV profile. |
| Product or quantity unavailable | Check the current Test catalog, exact SKU and inventory; do not substitute a Live product ID. |
| Rows with the same reference disagree | Make order-level recipient and shipping values identical before review. |
| Existing-order conflict | Read the existing order and use the eligible held-order correction flow. |
| No tracking yet | Check explicit release, then ask an Owner or Admin to simulate shipment. |
| Old order or receipt disappeared after reset | Use the current Test generation and coordinate a new intentional test with your team. |
Test tracking is synthetic. Successful import, release and simulated shipment do not establish a real carrier label, warehouse dispatch or recipient delivery.