Entering orders to OM is now also possible for the files that contain orders.
Fast steps toward the first import
1. Select additional settings.
2. When additional settings open, click on Order Management and find navigate to Order Import.
3. A template, specifying how the orders will be imported, is required for importing orders.
The template must contain the following key elements:
- title
- settings
- column
Values for creating a .json template are indicated in the table below. Attached you may also find the example of the .json template with sample input file.
(1) Selection of template
(2) Edit current templates
(3) Add new template
(4) Remove current template
4. Upload input file. The supported file formats are csv. and xlsx.
5.
Select the delivery type for imported orders.
6.
(1) Import results will be displayed below.
(2) Import history is available in Other - Requests.
Values for creating a template
Configuration for order import: Konfiguracija za uvoz naročil :
| Type | Meaning | Note |
| title | Template title | Mandatory |
| settings | Import settings | Mandatory |
| column | Column mapping | Mandatory |
| doc_date | Order import date | The value is automatically set to the date and time of import |
Values for settings object:
| Type | Meaning | Note |
| product_position | Method of reading input file | Mandatory Values: per_row |
| store_eshop_sync_id | Store Id | |
| default_tax | Tax | If the value is not given, the default value is taken |
| check_customer_order_not_exist | Before import, verify whether the orders already exist | Values: true/false |
| method_of_payment | Payment method for orders | Example: Bank account |
| mark_as_full_paid | The payment status of the order | Values: yes/no |
| method_of_payment_map | Mapping type of payments | Example: [{"PAY_PAL": "PayPal"}] PAY_PAL - value in PayPay file - Register in MetaKocka |
| payment_map | Mapping type of payments | Example: [{"PAY_PAL": "PayPal"}] PAY_PAL - value in PayPay file - Register in MetaKocka |
| default_status | Status that will be automatically selected when clicking on the template | |
| default_delivery_type | Delivery type that will be automatically selected when clicking on the template | In case of having an EU and non-EU delivery type, enter the EU delivery type here |
| default_delivery_type_nonEU | Delivery type that will be automatically selected when clicking on the template | In case of having a non-EU delivery type |
| create_bill | Create an invoice for an imported order | Values: true/false |
| header_notes | Note on the order - header | |
| footer_notes | Note on the order - footer | |
| empty_customer_order | Order import without customer's order - automatic numeration | Values: true/false If the value is 'true' then it is not possible to verify whether the orders already exist |
Values for column object:
| Type | Meaning | Note |
| title | The header of the column in | Mandatory |
| type | Column type | Mandatory |
| date_format | Date format | |
| replace_before | Keys for symbol/string exchange before using values | |
| delete_after_token_include | Symbol/string by which the value is removed including it | |
| whole_order_value | The column header in the input file that contains the total order value |
Values for type in object column :
| Type | Meaning | Note |
| customer_order | Customer's order | Mandatory |
| buyer_name | Customer's name | Mandatory |
| buyer_surname | Customer's surname | The surname will be merged with the name and separated by a space |
| buyer_street | Customer's address | Mandatory |
| buyer_street_2 | Customer's additional address | buyer_street and buyer_street_2 addresses will be merged and separated by a comma |
| buyer_place | Customer's city/town | Mandatory |
| buyer_post_number | Customer's ZIP Code | Mandatory |
| buyer_province | Customer's province | |
| buyer_country | Customer's country | Mandatory |
| buyer_email | Customer's e-mail address | Mandatory |
| buyer_mobile | Customer's phone number | Mandatory |
| receiver_name | Receiver's name | |
| receiver_surname | Receiver's surname | The surname will be merged with the name and separated by a space |
| receiver_street | Receiver's address | |
| receiver_street_2 | Additional receiver's address | receiver_street and receiver_street_2 addresses will be merged and separated by a comma |
| receiver_place | Receiver's city/town | |
| receiver_post_number | Receiver's ZIP code | |
| receiver_province | Receiver's province | |
| receiver_country | Receiver's country | |
| receiver_email | Receiver's e-mail address | |
| receiver_mobile | Receiver's phone number | |
| count_code | Order number | |
| payment_type | Payment type | |
| order_sum | Total order value | |
| payment_sum | Payment amount | |
| payment_date | Payment date | |
| product_amount | Product quantity | |
| product_sku | Product code | |
| product_price | Product price | |
| currency | Currency | - If the value is not set, the default value is taken. - Symbol: €, $ - Currency code: EUR, HUF, ... |
| whole_product_sum | Total product amount with quantity > 1 | |
| notes_header | Note on sales order - header | |
| notes | Note on sales order - footer |
Example of general import configuration.
Columns will be separating all data.
Example of configuration for import with merged values.
Each order contains only one order that can have an arbitrary quantity.
The paid value is equal to the order value with currency being recorded in the amount.