Upload and map a recipient file

Supported files

Upload a CSV or XLSX file. The file is checked by type and size before its rows are parsed. Keep the original file available if your team needs to reproduce a campaign review.

Recommended columns

Use a stable recipient id, recipient name, address lines, city, postal code, country, product SKU or barcode, and quantity. Optional email, phone, note and financial-status columns are supported when the campaign needs them.

Column detection recognises common English and Spanish headers. Treat detection as a proposal: confirm every mapping before running preflight.

Reusable mappings

After confirming a mapping, save it for the store when the same spreadsheet shape will be used again. A mapping is scoped to the authenticated store. It does not grant access to another store and it does not replace the review step.

Rows and duplicates

Keep one intended recipient per row. If a recipient needs multiple products, use the product and quantity structure supported by the batch screen and confirm the grouped result before creation. A stable recipient id is important for retry safety and reporting.