Here is an explanation of the steps required to import lots into Snoofa. To learn how to import clients, read more here.
Please note, parts of this documentation can change and introduce backwards incompatible changes.
Contents
How to import Lots
Hover over the plus icon in the top right corner and click Import
| 1. Hover over the plus icon in the top right corner and click Import |
 |
2. Select the Lots import type, select an unlocked auction, select a CSV file (details below), and click Upload |
 |
3. Check that number of rows matches expectations and hit Start import |
 |
4. The import can run for many minutes (depending on the number of rows). Once the import status changes from IN PROGRESS to FINISHED (refresh the page to check the status) the import is done. |
 |
5. Now you can check the errors log (if there are any) and optionally you can Erase Data created by the import. |
CSV template
This CSV file contains all the header columns. You can use it as a template when preparing your import. Below is an explanation of what each column represents.
Explanation of columns
Column | Example value | Notes |
|---|---|---|
vendor_id |
| A unique identifier of the client. In case that the Client Import had happened and made use of the id column, then this id will be used to reference the client entity. All the other vendor details can be empty. |
vendor_email |
| Must be unique for each client. When a duplicate is detected the import shows an error:
When not filled in a unique email for the client gets generated. See What if a client doesn't have an email address? for more details. |
vendor_title |
| |
vendor_firstname |
| Mandatory field) |
vendor_lastname |
| |
vendor_phone |
| Include the country code. |
vendor_vat_number |
| |
vendor_company_name |
| |
vendor_preferred_language |
| Supported options: en, de, ja, es, zh, sv, it, fr, ko |
vendor_registration_date |
| UNIX timestamp |
vendor_address_first_line |
| |
vendor_address_second_line |
| |
vendor_address_third_line |
| |
vendor_address_city |
| |
vendor_address_unit |
| Unit or region. When filled in it must be one of available options: see the full list. |
vendor_address_zip_code |
| |
vendor_address_country |
| When filled in it must be one of available options: see the full list. |
ca_number |
| Must be filled in for all rows |
ca_line |
| All cells must be empty (in that case line numbers are assigned automatically) or all must be filled in. |
item_title |
| |
item_subtitle | 19th centrury | |
item_description |
| |
item_category_id |
| Mandatory. Categories must be first created in |
item_low_estimate |
| |
item_high_estimate |
| |
item_starting_bid |
| |
item_reserve_price |
| |
item_is_antique |
|
|
item_vat_schema |
| Mandatory. MS for Margin Schema or SS for Standard Schema. |
lot_number |
| |
lot_hammer_price |
| |
lot_buyer_commission_id |
| Item Charges must be first created in |
lot_vendor_commission_id |
| Item Charges must be first created in |
lot_vendor_commission_value |
| |
buyer_id |
| All of these columns behave the same way as the |
buyer_email |
| |
buyer_title |
| |
buyer_firstname |
| |
buyer_lastname |
| |
buyer_phone |
| |
buyer_vat_number |
| |
buyer_company_name |
| |
buyer_preferred_language |
| |
buyer_registration_date |
| |
buyer_address_first_line |
| |
buyer_address_second_line |
| |
buyer_address_third_line |
| |
buyer_address_city |
| |
buyer_address_unit |
| |
buyer_address_zip_code |
| |
buyer_address_country |
| |
registration_paddle_number |
| |
registration_type |
|
|
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article