> ## Documentation Index
> Fetch the complete documentation index at: https://docs.merchantops.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Export
> Export prices to a spreadsheet with selectable fields, custom column mappings, and reusable templates.
MerchantOps can export price data to a spreadsheet so you can share it, review it
offline, or hand it to a downstream system. You choose which fields to include and
how columns are labeled, and you can save that configuration as a reusable
template. This page is for merchandisers and integrators pulling pricing out of
MerchantOps. For records themselves, see [Price records](/pricing/price-records).
## Exporting records
You can export price records scoped a few ways:
* **A whole batch** — every record in a given [price batch](/pricing/price-batches).
* **Specific records** — a chosen set of record keys.
* **By product** — all records for one or more products, optionally narrowed by a
temporal filter (current price, next upcoming price, or a date range).
You control the columns by passing a mapping of field keys to the labels you want
in the header row. Variant-level fields (such as color, size, or UPC) are joined
in automatically when you include them.
Exporting a batch also records the export on the batch — it stamps the batch as
exported and appends to its export history, so there is an audit trail of what
left the system and when.
## Available fields
Fields fall into three groups you can mix freely:
| Group | Examples |
| -------- | ------------------------------------------------------------------------- |
| Product | Product key, product name, variant key / SKU, brand key, brand name. |
| Pricing | Price type, amount, previous amount, currency, effective date, UMAP flag. |
| Metadata | Status, batch ID, notes, created / updated timestamps. |
Retrieve the full, current list of exportable fields from the export-fields
endpoint rather than hard-coding it.
## Export templates
An export template saves a column mapping and format configuration so you don't
rebuild it each time. Templates are managed with standard create, read, update,
and delete operations, and can be filtered by format. Reuse a template whenever
you run the same kind of export — for example, a recurring feed with a fixed
column layout.
## Formats
Exports produce a spreadsheet (Excel) or CSV. Beyond a generic Excel export, format
presets exist that shape the file for specific downstream systems. When your goal
is to push prices into an external commerce platform, prefer publishing over a
manual export — publishing is batched, scheduled, and audited per target.
A generic file/spreadsheet export is the right tool for ad-hoc review and for
feeds a downstream system ingests on its own schedule. To deliver prices to a live
storefront, use a publishing connector instead.
Deliver prices to external systems, batched and audited.
The unit most exports are scoped to.