ANTE User Manual

Data Import

Settings → Company Settings → Data Import moves your existing data into Ante from spreadsheets — for example the item master you kept in Excel before going live. Every file goes through the same steps: download the template, upload, check the columns, check the rows, import. Nothing is saved until every row is right, and you can undo the latest import while nothing uses what it created.

What you can import

KindMatched byStatus
ItemsSKUAvailable
Opening stockWarehouse + SKUAvailable
CustomersCode, else exact nameAvailable
SuppliersCode, else exact nameAvailable
Supplier price tiersSupplier (code or exact name) + SKU + from quantityAvailable

Each kind needs its own Data import permission (Settings → User Levels → Data Import: Import items, Import opening stock…). Super-admins with full access have all of them.

Give Data import permissions with care

The Data import Items permission can create new items and change existing ones (name, UOM, category, prices) on its own — the user does not need the item create or update permissions in Assets. Give it only to people you would trust to edit the item master.

Importing a file

  1. Pick the kind of data (Items…), then download the template in English, Japanese or Thai. Its second sheet explains every column.
  2. Fill in one row per record and Upload file (an .xlsx file, up to 2,000 rows; a cell keeps at most 2,000 characters). Your own spreadsheet works too — the columns don't have to be in the template's order.
  3. Check the columns: Ante matches them by their headers (and, when that isn't enough, from their contents). Change any that are wrong; required columns are marked *.
  4. Choose Check the file. Every row shows New, Update, Unchanged or Problem with the reason (for example "UOM "bundle" is unknown").
  5. When there are no problems, choose Import. All rows are saved at once.
All or nothing

If any row has a problem, nothing is imported. Use Only rows with problems or Download the rows with problems to see what to fix, correct your file and upload it again.

Uploading the same file again is safe

Rows are matched by their code or SKU, so a second upload of the same file changes nothing, and a changed price only updates that item — nothing is ever duplicated.

Items

  • SKU, Name and UOM are required. A SKU already in Ante updates that item; a new SKU creates one.
  • UOM can be pieces, box, kilogram, gram, meter, liter, set, unit, lot or lump sum — common short forms such as pcs, kg and m also work.
  • Category code must be the code of one of your item categories. Blank optional cells keep what the item already has.
  • When SKUs are numbered automatically (Assets → Settings → SKU Numbering), importing new SKUs needs the Enter own SKU permission.

Opening stock

  • One row per item per warehouse: Warehouse (its name exactly as in Assets → Warehouses), SKU, Quantity, Unit cost and As-of date. Import the items first.
  • One as-of date per file, not in the future, and one unit cost per SKU in a file (accounting values stock per item).
  • Opening stock is only for an item with no stock movements yet in that warehouse — for anything else use a stock adjustment.
  • Importing posts the quantity to each warehouse and the opening value (quantity × unit cost) to accounting: Inventory against Opening Balance Equity, on the as-of date.
  • If an import stops halfway, open it from History and choose Run the import again — nothing is posted twice.
  • Opening stock can't be undone; correct a wrong figure with a stock adjustment.

Customers

  • Name, Email and Contact no. are required; Code (the multibook Biz Partner code, up to 10 characters), contact person, TIN, Currency and Payment term are optional.
  • A row is matched to an existing customer by its code, otherwise by its exact name (capitals don't matter). If two customers share the name, add their code to the file.
  • Each customer in your company needs its own email (an archived customer keeps theirs); another company may use the same email.
  • The payment term must be the code of one of your customer payment terms (Treasury → Settings → Payment Terms).
  • Undo is refused once a customer from the import is used (an order, a project, a document, an invoice…) or was edited since.

Customer Item Names

  • One row per customer and item: Customer (its code, else its exact name), Our SKU and the Customer's item name are required; the customer's part no., a description and Active (Yes / No) are optional.
  • Customer unit and How many pcs in one go together — for example box and 10: that customer's documents then read "2 box (20 pcs)". Give both or neither; blank keeps the unit the name already has (to remove a unit, edit the name on the item).
  • A row for a customer and item that already have a name updates it; undo removes what the import added and puts back what it changed, units included.

Suppliers

  • Only Name is required; Code (the multibook Biz Partner code, up to 10 characters), contact no., email, TIN, Currency, Tax (VAT or No tax), Payment term and Courier (Yes / No) are optional.
  • A row is matched to an existing supplier by its code, otherwise by its exact name (capitals don't matter). Blank cells keep what the supplier already has; a new supplier gets VAT, the company's default supplier payment term and Courier = No.
  • As on the supplier form, a name and an email each belong to one supplier.
  • The payment term must be the code of one of your supplier payment terms (Treasury → Settings → Payment Terms).
  • Undo is refused once a supplier from the import is used (a receipt, purchase request or order, price list, document, request for payment, a delivery's courier…) or was edited since.

History and undo

History lists every file: when, who, and how many rows were new, updated or unchanged. Open one to see its rows again. Undo this import removes the items it created and puts back what it changed — only for the latest import of that kind, and only while none of its items has been used (in stock, on a document or a price list) or edited since.