Import row errors

Order, SKU and markup imports check every row. Each problem is listed as "Row (number) (order or SKU): message". Row 1 is the first row under the headings. Fix the rows listed, then upload the whole file again.

A cell is not valid

order_date must be a date (YYYY-MM-DD or DD/MM/YYYY)

Cause. A value in the row is not in a form Forensik can read. The common ones are:

• a date that is not YYYY-MM-DD or DD/MM/YYYY (order_date, ship_date)
• "dest_state ... is not an Australian state or territory": use NSW, VIC, QLD, SA, WA, TAS, NT or ACT
• "dest_postcode must be 4 digits": a leading zero dropped by Excel (such as 800 for 0800) is the usual cause
• "qty must be a whole number from 1 to 10000"
• "must be dollars and cents, for example 34.01" for the freight amounts
• "carrier_code is required when a connote is given", "ship_date is required when a connote is given", or "connote is required when carrier_code, service_code, ship_date or origin_code is given"
• in SKU files, "category must contain a letter or digit"

Fix. Correct the cell in the row named. To keep leading zeros on postcodes in Excel, format the column as Text before typing, or save as CSV and check the file in a text editor. Leave the consignment columns all blank, or fill in at least connote, carrier_code and ship_date together.

When to contact support. If the value looks right and is still refused.

Rows for the same order disagree

order_date, freight_charged_ex_gst differ from row 2 for the same order_id

Cause. Rows with the same order_id are one order, so the order details must be identical on each of its rows: date, customer, destination and both freight amounts. The freight amounts are for the whole order and are repeated on every line, not split between lines. The same applies to a connote: service, ship date, origin and destination must match on every row of that connote. In SKU files, name and category must match on every carton row of a SKU.

Fix. Copy the order's details from its first row onto every other row of the order, or the connote's details onto every row of the connote.

When to contact support. If the rows look identical; hidden spaces or a different date format can be hard to spot, so send us the file.

Nothing was imported

3 of 120 rows failed; nothing was imported

Cause. Imports are all or nothing. One bad row stops the whole file, so you never end up with half an import. If the problem only shows up while saving, you see "The import could not be saved; nothing was imported".

Fix. Fix every row in the list (it shows up to 200, then a count of the rest) and upload the same whole file again. You do not need to remove the rows that were fine.

When to contact support. If you get "The import could not be saved" for a file with no row errors.

Order or connote already exists

Order SHOP-1001 already exists

Cause. An order with this order_id is already in Forensik, from an earlier import, a store connection or a manual entry. Forensik never takes the same order twice. "Connote (number) already exists for (carrier)" means the connote is already used. In SKU and markup files, "already given on row (number)" means a carton number or SKU appears twice in the file.

Fix. Remove orders you have already imported from the file. To add a consignment to an existing order, open the order and use Add consignment. For duplicates within a file, keep one row.

When to contact support. If you need to replace an order that was imported wrongly.

No origin warehouse

no origin warehouse: add one under Orders > Warehouses before recording consignments

Cause. A consignment needs the warehouse it left from. With no warehouses set up, consignments cannot be recorded. With several, each consignment row needs an origin_code ("several warehouses exist"). "origin warehouse (code) not found" means the code in the file does not match any warehouse.

Fix. On the Orders page select Warehouses and add yours. If you have more than one, add an origin_code column with the warehouse code on every row that has a connote.

When to contact support. If the code matches a warehouse you can see and is still not found.

Suburb recorded in another state

Hoppers Crossing 3029 is already recorded in VIC, not NSW

Cause. Forensik keeps one record of each suburb and postcode. This row gives the same suburb and postcode with a different state from one already recorded, usually a typing slip.

Fix. Correct dest_state on the row. If the existing record is the one that is wrong, contact support.

When to contact support. If you are sure the suburb, postcode and state in your file are right.

Markup file errors

SKU not found; add it on the SKUs page first

Cause. A markup file row could not be applied. Other messages include "free_freight must be true or false", "mode must be SKU_MARKUP, POSTCODE_MARKUP or blank", and "Set up a postcode markup table on the Pricing page; a CSV row cannot carry one".

Fix. Add missing SKUs on the SKUs page first. Use true or false in free_freight, and leave mode and percent blank when free freight is true. Postcode markups are set up on the Pricing page, not in the file. See Postcode markups.

When to contact support. If a SKU you can see on the SKUs page is reported not found.