Exporting & Automated Exports
Summary
How manual, on-demand exports and scheduled Automated Exports get data out of Flxpoint using dynamic field mapping, and which record types and delivery destinations they support.
Flxpoint gets data out of the platform two ways: a manual, on-demand export of whatever records are filtered on a grid, and a scheduled Automated Export that delivers files to an external destination on a recurring basis. Both use dynamic field mapping, so you control which columns appear and what the headers are called.
Manual export: best for one-off pulls. Select a subset of records on any supported grid, choose Actions → Export, configure the headers, and download the CSV. Uses the grid's current filters to decide what is included.
Automated export: best for recurring delivery to a partner or internal system. Built from an Export Template, a delivery Connection, a Schedule, and an optional Saved Filter, configured under Account Settings → Automated Exports.
Most domains support dynamic field mapping; Orders are the exception and still use a legacy export only.
| Domain | Dynamic export |
|---|---|
| Orders | Not supported (legacy export only; dynamic field mapping is planned) |
| Fulfillment Requests | Supported |
| Invoices | Supported |
| Source Parents & Variants | Supported |
| Product Parents & Variants | Supported |
| Listing Products & Variants | Supported |
| Profitability Report | Supported |
| Component | Defines |
|---|---|
| Export Template | Which fields and format are in the file. |
| Connection | Where the file is delivered (FTP/SFTP, S3, HTTP File, Email, and more). |
| Schedule | How often and at what time the export runs. |
| Saved Filter (optional) | Narrows which records are included, using reusable filter conditions. |
Channel invoice fields (Invoice export)
When mapping an Invoice export, the Order section exposes the channel invoice amounts from the related order. These fields are available in the Invoice export only.
| Field | What it holds |
|---|---|
| Order - Subtotal | Sum of the order line items on the channel invoice. |
| Order - Tax | Sales tax applied to the order. |
| Order - Shipping | The customer's shipping charge from the channel invoice, not the shipping cost you pay your source. |
| Order - Fee | Any additional fee on the order, typically a dropship fee. |
| Order - Other | Any miscellaneous cost associated with the order. |
| Order - Discounts | Discounts applied to the order. |
| Order - Total | Final channel invoice total for the order. |
Automated export delivered an empty or unexpected file
Run the Export Template manually first and confirm the file structure before enabling the schedule. If a Saved Filter is attached, the file only includes records that match that filter's conditions, so an over-narrow filter can produce an empty file.
Master SKU / mapped import did not update after using export headers
An export template's column headers (for example SKU, Master SKU, UPC) describe the export layout and are not guaranteed to drive an import. If a re-import is not taking effect, confirm you are using the correct import type for that record rather than reusing the export header set.
Can I schedule an export to an FTP or URL that another system polls?
Yes. An Automated Export of Source Inventory, Product Catalog, or Channel Listings can deliver to FTP, SFTP, S3, or HTTP File. With HTTP File you can copy a file URL to poll after each run.
Can I export Orders with custom columns?
Not yet. Orders use a legacy export that cannot be dynamically mapped. For mapped, order-related columns use the Invoices or Fulfillment Requests exports, both of which support dynamic field mapping.
Where do the channel invoice amounts in the Invoice export come from?
They come from the channel invoice on the related order. Order - Shipping is the customer's shipping charge from the channel, not what you pay your source.
Can I reuse a Saved Filter on both a grid and an automated export?
Yes, within the same module. A Saved Filter created in Source Inventory, Product Catalog, or Channel Listings can be applied to that module's grid and to its automated exports.
Why can't I delete a Saved Filter?
It is attached to an automated export. Edit that export to remove or change the filter, then delete the Saved Filter.
What it does
Historical Average Shipping Cost calculates the mean actual cost paid for shipping a specific SKU based on historical fulfillment data. This value is stored at the inventory variant level as avg_shipping_cost and is designed to be exported to third-party repricers, ensuring your channel pricing remains competitive while covering actual logistics expenses.
Calculation logic
To ensure the average is accurate and representative of a single item's shipping cost, Flxpoint applies specific filters to the data used in the calculation:
120-Day Window: The average is calculated using shipment data from the last 120 days.
Single-Item Orders: Only orders containing a single line item with a quantity of 1 are included.
Bundle Support: Flxpoint bundles are included in the calculation if a single quantity of the bundle is ordered without any other items.
Automatic Updates: The average is recalculated automatically every time a new shipment is saved in the system.
Overrides and locks
You can manually manage the shipping cost value if you need to deviate from the calculated historical average.
Manual Override: Enter a specific shipping cost to be used for a variant regardless of historical data.
Locking: Lock the value to prevent the automated 120-day recalculation from updating the field.
Removal: You can remove a lock or override at any time to return to the automated calculation logic.
Exporting for repricers
This feature is primarily used for high-volume marketplace retailers who need to sync data to repricers via FTP or HTTP CSV imports. When configuring your automated export, you can include the following fields:
Field | Description |
|---|---|
Listing SKU | The unique identifier for the product on your sales channel. |
Average Shipping Cost | The |
Estimated Cost | The landed cost of the item from the source. |
Note: This feature requires a specific feature flag to be enabled on your account. Contact your account manager to discuss enabling this functionality.
What it does
The order export tool allows you to generate CSV files containing specific data points from your orders. Recent updates have added financial fields like tax and subtotal, as well as granular fulfillment and shipment data, to help with accounting and logistics reporting.
New export fields
You can now include the following fields in your order exports to get a more complete view of your transactions and fulfillment status:
Financials: Tax, Invoice Sub-Total, and Shipping Cost.
Fulfillment: Fulfillment Request #, SKU, Title, Cost, and Quantity (within the Fulfillment Request section).
Shipments: Shipped At, Tracking #, Cost Carrier, and Method.
Note: The Payment Status field is only available in Flxpoint Pro and Enterprise tiers. It will not appear in the export options for Business tier accounts.
Field groupings
To make the export configuration easier to navigate, fields in the column picker are organized into logical groups:
Group Name | Data Included |
|---|---|
Order Fields | General order details and identifiers. |
Fulfillment Request Fields | Details related to the FR sent to the source, including item-level SKU and cost. |
Shipment Fields | Tracking numbers, carriers, and shipping dates. |
Source Invoice Fields | Financial data related to the supplier's invoice. |
Address Fields | Separate groups for Billing Address and Shipping Address details. |
How to export
Navigate to the Orders page in the Flxpoint sidebar.
Click the Export button (or the column picker icon within the export workflow).
Select the desired fields from the organized groupings listed above.
Run the export.
Note: When exporting orders with multiple shipments, verify that the tracking and cost fields align correctly across rows to ensure data integrity for each fulfillment instance.