Item CSV Import

The Item CSV Import lets you perform bulk operations on your Arda item catalog by uploading a CSV file. You can create new items, update existing ones, or delete items — all in a single file.

Supported Operations

Each row in your CSV specifies one of four actions:

Action Value	What It Does
ACTION_CREATE	Creates a new item.
ACTION_UPDATE	Updates all fields of an existing item. Blank fields will overwrite existing values.
ACTION_DELETE	Deletes an existing item.
ACTION_IGNORE	Skips the row without validation.
ACTION_SKIP	Skips the row but validates its contents.

[!WARNING] ACTION_UPDATE overwrites all fields, including blanks. If you leave a field empty in the CSV, that field will be cleared on the item.

CSV File Format

Your file must follow these conventions:

1. Fields separated by commas.
2. Text fields containing commas or special characters must be enclosed in double quotes.
3. Rows separated by newlines.
4. The first row must contain headers with field names.
5. Column order does not matter.
6. Column names are case-insensitive and must be unique.

Required Columns

Column	Required For	Description
action (or act)	All rows	The action to perform on this row.
name (or item_name)	All rows	The item name. Cannot be blank.
id (or item_id, uuid)	UPDATE, DELETE	The system UUID of the existing item.

All Available Columns

Item Identity

Column	Aliases	Type	Notes
name	item_name	String (255)	Required for all actions.
id	item_id, uuid	UUID	Required for UPDATE and DELETE.
sku	sku	String (100)	Supplier part number.
image_url	image	URL	Must be a valid URL if provided.

Categorization

Column	Type	Notes
type (or item_type)	String (100)	Broad item category.
sub_type (or item_sub_type)	String (100)	Narrower grouping.
facility	String (100)
department	String (100)
location	String (100)	Physical storage location.
sub_location	String (100)	Specific spot within the location.
color (or item_color)	Enum	See color values below.

Quantities

Column	Type	Notes
min_quantity	Decimal >= 0	Reorder point.
min_quantity_unit	String (100)

Notes

Column	Type	Notes
item_notes	String (8000)	Internal item notes.
card_notes_default	String (8000)	Default text printed on Kanban cards.
taxable	Boolean (true/false)

Primary Supplier

Column	Type
primary_supplier	String (100)
primary_sku	String (100)
primary_order_method	Enum (see below)
primary_url	URL
primary_order_quantity	Decimal >= 0
primary_order_quantity_unit	String (100)
primary_unit_cost	Decimal >= 0
primary_unit_cost_currency	USD or EUR
primary_average_lead_time	Integer > 0
primary_average_lead_time_unit	Enum (see below)

Secondary Supplier

Same columns as Primary Supplier, prefixed with secondary_ instead of primary_.

Print Sizes

Column	Valid Values
card_size	CARD_SIZE_SMALL, CARD_SIZE_MEDIUM, CARD_SIZE_LARGE, CARD_SIZE_EXTRA_LARGE
label_size	LABEL_SIZE_SMALL, LABEL_SIZE_MEDIUM, LABEL_SIZE_LARGE, LABEL_SIZE_EXTRA_LARGE
breadcrumb_size	BREADCRUMB_SIZE_SMALL, BREADCRUMB_SIZE_MEDIUM, BREADCRUMB_SIZE_LARGE, BREADCRUMB_SIZE_EXTRA_LARGE

Enumerated Values Reference

Order Methods: ORDER_METHOD_PURCHASE_ORDER, ORDER_METHOD_EMAIL, ORDER_METHOD_PHONE, ORDER_METHOD_IN_STORE, ORDER_METHOD_ONLINE, ORDER_METHOD_RFQ, ORDER_METHOD_PRODUCTION, ORDER_METHOD_TASK, ORDER_METHOD_THIRD_PARTY, ORDER_METHOD_OTHER

Time Units: TIME_UNIT_MINUTE, TIME_UNIT_HOUR, TIME_UNIT_DAY, TIME_UNIT_WEEK, TIME_UNIT_STANDARD_MONTH, TIME_UNIT_STANDARD_YEAR, TIME_UNIT_LEAP_YEAR

Colors: ITEM_COLOR_BLUE, ITEM_COLOR_RED, ITEM_COLOR_GREEN, ITEM_COLOR_YELLOW, ITEM_COLOR_ORANGE, ITEM_COLOR_PURPLE, ITEM_COLOR_PINK, ITEM_COLOR_GRAY

Validation and Error Handling

Each row is processed independently. A row failure does not affect other rows. The import report shows:

• Number of successful rows.
• Number of failed rows.
• For each failure: the row number (starting at 0) and a description of the error.

Validation rules:

• name is required for all actions and cannot be blank.
• id is required for UPDATE and DELETE and must match an existing, non-deleted item.
• URL fields must be syntactically valid if provided.
• Enumerated fields (order method, color, etc.) must match exact values including case.
• Numeric fields must be valid numbers meeting the specified constraints.
• String fields must not exceed their stated length limits.