SimpliServDocs

Import & export data

Import master data via CSV/JSON (contacts, products, product categories) and download audit-proof archive and DEP7 exports as a ZIP.

→ Open imports · Open exports

Under Administration → Data & files you import master data from CSV or JSON files and download archive and register exports as a ZIP. Both areas are separate pages in the admin navigation: Imports and Exports.

Import data

On the Imports page you choose at the top between three import targets (the buttons are labelled in English in the interface):

  • Contacts – create or update customer and contact records.
  • Products – catalog products including stock, categories and suppliers.
  • Product categories – create nested category paths.

Each import accepts CSV or JSON (.json / .csv). For CSV you can choose the separator (the "CSV separator" selector, the default is semicolon): Auto, Semicolon (;), Comma (,) or Tab. Via the collapsible JSON format and CSV format blocks you see an example each and can download it as a template via Download JSON / Download CSV.

How an import runs

Choose the import target

Click Contacts, Products or Product categories at the top. Based on the columns, SimpliServ detects when a file fits the wrong target and points it out.

Select the file

Upload your file under File (JSON or CSV) and, for CSV, set the matching separator if needed. The file is read and checked immediately.

Check the preview

SimpliServ shows how many records are ready to import, as well as ignored duplicates and invalid rows. In the "Table preview", faulty rows come first; problematic cells are marked red, automatically set default values italic.

With Dry run you simulate the import without writing data. The result shows e.g. "Would create", "Would update" and "Would skip".

Start the import

Click Start import. A progress bar runs along; afterwards the results appear (created / updated / failed) and a list of errors with the respective row and reason.

Always use the dry run first, especially for large files. It reveals duplicates, missing required fields and unassignable rows before anything is saved.

Import contacts

There are two modes, switchable via the Update existing contacts toggle:

  • Create (default): creates new contacts. At least a first/last name or company is required. Duplicate email addresses within the file are skipped.
  • Patch (toggle active): assigns rows to existing contacts via id (preferred) or email and updates only the filled fields. Unassignable rows are skipped. Only in this mode can created_at and updated_at be overwritten.

Supported fields (a selection, with column aliases): first_name/last_name (or name), email, phone, company, website, uid/vat_id, tax_number, salutation, academic_title, bank_name, iban, bic, image_url, notes, birthday, newsletter_accepted, automatic_emails, customer_type, customer_group.

  • Addresses: either flat via shipping_* and billing_* (e.g. shipping_address1, billing_zip) or structured as an addresses array (JSON) or numbered columns address_1_type, address_1_address1 … (types: billing, shipping, private, work, other). The country is resolved via ISO code or country name.
  • Custom fields: as a JSON object custom_fields or as CSV columns custom_fields_<slug> (e.g. custom_fields_customer_category).

More on maintenance see Contacts, Customer types & groups and Custom fields.

Import products

The required field is name. Missing categories and suppliers are created automatically on import.

  • Prices: price for net or price_gross for gross, controlled via price_input_mode (net / gross). Amounts are also recognized in local notation (20,45 as well as 1.234,56).
  • Defaults: without a value, the tax rate is set to 20% and the unit to piece.
  • Stock & warehouse: quantity for the amount; storage_name accepts nested paths – the first segment is the warehouse, further segments form the location hierarchy (separator > or /, e.g. Main warehouse > Shelf A > Compartment 3). Without a value, stock lands in the default warehouse "Import".
  • Further fields: article_number, ean, description, purchase_price, weight, is_serialized, manufacturer, device_model, supplier_name, categories, custom_fields_<slug>.

Two options are available:

  • Split categories automatically (/ and >) – breaks category entries into path levels. Several categories are separated by a semicolon.
  • Update existing products – matches are searched via EAN, then SKU; if a product is found, it's updated instead of skipped.

In depth: Create a product, Product variants, Categories and Warehouse & stock.

Import product categories

Create category trees in one step. Per row you provide either

  • full_path with the full path (separator >), e.g. Parent > Category > Subcategory, or
  • parent_path + name – the parent path plus the new category name.

A description is optional. SimpliServ sorts the rows by depth, creates missing levels in the right order and skips already-existing paths. If a parent category is missing that isn't itself part of the file, the row is marked as failed with a note.

Download exports

The Exports page offers two direct ZIP downloads from the compliance archive. It requires the admin.exports.read permission.

Exports immutable archive packages by period.

  • Document type: invoices, proposals, estimates, delivery notes or receipts.
  • From / to: choose the start and end date (the start must be on or before the end).
  • With Download ZIP you get the archive package as <type>-archive-<from>-<to>.zip.

Details on the structure and retention of the packages are under GoBD archiving.

Archive and DEP7 exports are audit-proof document outputs for accounting and authorities – not a backup of your master data. For structured data output of individual modules, use the respective list and detail views.

Permissions

  • Imports are reachable via admin.settings.view.
  • Exports require admin.exports.read.

Who sees which admin areas is controlled under Users & roles.

  • Create a contact — what you maintain and add by hand after the contact import.
  • Create a product — single creation as a complement to the product bulk import.
  • Custom fields — defines the custom_fields_<slug> columns the import fills.
  • GoBD archiving — the structure and retention of the archive packages you export here.
  • DEP export (RKSV) — background and obligations for the DEP7 register export.

How is this guide?

On this page