¶ Customer and order export - transfer in Hummerce
Customer export and order export are transfers in the Hummerce panel that let store staff save customer or order data to a CSV file - for further analysis in a spreadsheet, reporting, or handing off to another system, without manually retyping data from the panel.
Last updated: 2026-09-29.
¶ Benefits and use cases
- Customer and order data outside the panel - in a spreadsheet, a BI tool, or an external system, without manual retyping.
- Filter by period - export only customers registered, or orders placed, in a chosen date range.
- Filter by last order date - for customer export, useful e.g. for identifying customers inactive for a while.
- Order export from a selected view - separately for each sales channel in stores with multiple views (Views).
- Choice of columns for customer export - a column set matched to your needs (basic data, newsletter consent, tags, or other properties configured in the store).
- Before running the transfer, you choose the exported customer attributes - in the standard configuration: Id, Login, Registration date, Active, First name, Last name, Newsletter consent, Tags. Which columns are actually available to choose depends on the properties assigned to the customer export location in a given store - the same as with item export (Properties and locations).
- Filter by registration date (from-to) - export only customers registered in a given period.
- Filter by last order date (from-to) - export only customers who did (or didn't) place an order in a given period.
- File name - your own name, also saved in the transfer history.
- The file is saved in UTF-8 encoding.
- Before running it, you choose the order placement period (from-to, to the minute) and optionally the view the orders should come from.
- File name - your own name, also saved in the transfer history.
- The export file has a fixed set of columns:
| Column |
Content |
| Order symbol |
the order number in the store |
| Order placement date |
date and time the order was placed |
| Payment method |
e.g. PayU, card |
| Delivery method |
e.g. DHL, InPost |
| Order status |
placed / confirmed / in progress / finished / canceled |
| Payment status |
paid / not paid / prepared / finished / rejected / payment error |
| Delivery status |
not sent / sent / delivered |
| Total (net) |
net order value |
| Total (gross) |
gross order value |
| Customer |
first and last name |
| Company name |
empty if there's no company |
| NIP |
empty if there's no NIP (Polish company tax ID) |
| E-mail |
the customer's email address |
| Address |
street, postal code, city |
The file is saved in Windows-1250 encoding (matching the default CSV opening in the Polish version of Excel).
- The transfer runs in the background - a progress bar at the top of the panel shows the current state.
- On completion, a message shows the transfer's result, with the option to download the resulting file right away.
- The transfer history (at the bottom of the transfer screen) keeps previously generated files - with date, size, and the option to download or delete them again.
- Order export with a view filter requires configured views (Views).
- Extra columns for customer export require properties assigned to the customer export location (Properties and locations).
- General data transfer rules - Data transfer.
- Works out of the box, no implementation needed - both exports are part of the platform standard.
- Adding new columns to customer export (properties outside the standard configuration) requires setting them up and assigning them to the export location first - a simple configuration task, quoted individually after analyzing the need.
- The order export columns are fixed - a custom column can't be added without changing the transfer's configuration (implementation).
- Neither export has a test mode - export only reads data, so there's no risk of saving incorrect data in the store.
- The file contains customer personal data (first name, last name, email, address, NIP) - store and share it according to your own data protection rules.
- We do not verify the task for legal compliance (e.g. GDPR, retention and handling of personal data, store terms of service).
- Choice of columns for order export (currently a fixed set).
- A shared screen for both exports, with a preview of the number of rows before running.
Can I export only customers registered in a given period?
Yes, the registration date filter (from-to) narrows the export to the chosen range.
Can I export orders from just one store view?
Yes, order export has a Choose view filter - useful in stores with several sales channels.
Can customer export columns be extended with custom properties?
Yes, by assigning a property to the customer export location in the configuration - a simple implementation task.
Does the export file contain personal data?
Yes - customer and order export contains first name, last name, email, address, and (for company orders) NIP. We do not verify the task for legal compliance - the store sets the rules for storing and sharing such a file.
How long does implementing these exports take?
Both work out of the box, without implementation. Adding a new column to customer export is a small configuration task, quoted individually.
Want to regularly export customer or order data for your own analytics? Contact the Hummerce team (in Polish).
- Customer export: Data transfer -> Customer export (csv) - choice of exported attributes, registration date filter, last order date filter, file name.
- Order export: Data transfer -> Order export (csv) - order placement period, view choice, file name.
- File history: at the bottom of each transfer's screen - a list of saved files with date, size, and download/delete actions.
| Transfer |
File encoding |
Filters |
| Customer export (csv) |
UTF-8 |
registration date (from-to), last order date (from-to) |
| Order export (csv) |
Windows-1250 |
order placement period (from-to), view |