If you're not using a direct integration with Zamp, you can provide transaction data via CSV. This article covers when to use CSV uploads, the required format, how to export from common systems, and answers to common questions.
When to use CSV uploads
Use CSV uploads when:
Your e-commerce platform doesn't have a direct Zamp integration
You have transactions from marketplaces (Amazon, Target, Walmart, etc.)
You need to provide historical data
You have offline or manual sales
Heads up: If you'd rather not handle CSV exports during onboarding and at the start of every month, we can do it for you. Contact your salesperson, onboarding specialist, or [email protected] to hand off this responsibility.
Zamp CSV template (column reference)
Use the table below as a reference when formatting your CSV. We can also provide an example file on request.
Refunds: For refund transactions, the following fields should have negative amounts: transactionShippingHandling, transactionSubtotal, transactionDiscount, transactionTax, and transactionTotal.
Column Name | Required? | Used for | Notes |
| Yes | The ID for the transaction. | May also be referred to as an invoice ID, order ID, or similar. |
| No | For refund transactions only. The ID for the original order transaction. | Helpful when available. |
| No | The marketplace where the sale took place. | Supported values: AMAZON, META, TIKTOK, WALMART, TARGET_PLUS, ETSY, EBAY, MIRAKL, MACYS, ALIBABA. If not a marketplace sale, use FALSE. |
| No | true, false, or blank to note if the order was sold to a wholesaler/reseller. | Defaults to false if blank. |
| No | The total discount for the order or refund. | Defaults to 0. Must be positive; cannot be a percentage. |
| Yes | The combined total of the order or refund after the discount. | Should not include shipping, handling, or tax. |
| No | The combined shipping and handling cost. | Defaults to 0. |
| Yes | The total tax collected on an order, or refunded for a refund. | Defaults to 0. |
| Yes | The total amount charged or refunded. | Should equal subtotal + shipping/handling + tax. |
| Yes | The date the order or refund occurred. | Example: 10/21/2024. |
| No | First line of the shipping address. | Recommended for accuracy. |
| No | Second line of the shipping address. | Examples: Suite 23, Apt 16. |
| No | The shipping city. | Required if shipToZip is not provided. |
| Yes | The shipping state. | Required if shipToZip is not provided. Supports US states, PR, and Canadian provinces. |
| Yes | The shipping zip / postal code. | US: 12345 or 12345-6789. Canada: e.g., H1A 0A0. |
| Yes | The shipping country. | Supports US and CA. |
| Yes | The transaction's currency. | Defaults to USD if blank. |
| No | A specific Zamp Tax Code for the transaction. | If blank, the product is assumed fully taxable. |
Ship-to address requirements
For US transactions, the minimum required is the zip code, OR the city and state. For non-US transactions, the minimum required is the city and country (use a 2 or 3-character ISO country code). For physical products, use the shipping address. For digital, service, or non-physical products, use the billing address.
How to submit CSV files
Email to support. Attach your CSV file to a message to [email protected].
Include the period. Specify which month/period the data covers.
Note the source. Tell us where the data came from (e.g., "Target January 2026").
Common CSV upload questions
"My CSV has different column names"
That's okay. Just let us know what each column represents and we'll map it correctly.
"I have multiple files"
You can send multiple files. Label each clearly with the source and period.
"Some transactions are missing tax"
If tax wasn't collected on certain transactions, include them anyway. We need the full picture to file accurate returns.
How to export orders from your system(s)
Zamp doesn't integrate with every e-commerce, invoicing, or bookkeeping platform, but we can process transactions from any system when they're imported via CSV.
Transactions versus line items
Most systems distinguish between transactions and line items. The relationship is one-to-many: a single transaction may have one or many line items. If your transactions can include multiple line items, you must list them individually (each on its own row). Otherwise we can't process the import.
Required columns for multi-line item exports
Transaction date. The date of sale.
Transaction/Order/Invoice ID. Needed to connect line items to the same order.
Ship-to state and Ship-to zip code.
Line item quantity and price. Quantity is the number of units; price is the unit price.
Line item and/or transaction discounts. Separate columns for transaction vs. line item.
Line item and/or transaction shipping & handling fees.
Transaction OR line item taxes.
Transaction total. Including price, discounts, shipping, and tax.
Channel. For marketplace-facilitated transactions, value of
MARKETPLACE.Purpose. For wholesale or resale transactions, value of
RESALE.
Required columns for single line item exports
Transaction date, Ship-to state, Ship-to zip code
Transaction subtotal (before discounts, shipping, and taxes)
Transaction discounts, shipping & handling fees, tax
Transaction total (including discounts, shipping, and tax)
Channel. For marketplace-facilitated transactions, value of
MARKETPLACE.
Marketplace-specific guidance
Amazon
Amazon remits tax directly in most states.
We still need transaction data for nexus tracking.
Download reports from Seller Central.
Target
Provide the Sales Tax by State report.
Include all transaction files for the period.
Walmart
Download the Tax Remittance Report.
Include transaction details.
Need help?
Questions about data uploads or exports? Reach out at [email protected].