Clients Area

Moving to SixBit 2.0 CSV Import Print

  • SixBit 2.0, CSV Importing, Flat-File Import
  • 36

With the release of SixBit 2.0 the overall importing and exporting process has been upgraded to provide users with more control and options.  The upgrades to CSV import allow for the import of all types of data including Item/Supplier/Shipment/Sales/Buyer/Compatibility Sets/ Orders, including orders from other venuesthrough CSV. 

However, to allow for the robust improvements, changes to the import process were necessary.  You may find that your import files don’t work as before because of these changes.

Import Options & Tabs

In versions prior to SixBit 2.0, all fields that could be imported to, were located on one tab in the import window.  All fields could be updated with a single import.  One of the first changes you will likely notice is that the Import from File now has several options (Items, Suppliers/Consignors, Inventory, Compatibility Sets) and the Import From CSV window now has multiple tabs.  Most important to note is that the only time all fields can be updated from a single import is when an item is first being created.

ID's vs. Names

SixBit keeps track of some fields by use of an internal numeric identifier in addition to a human readable name.  You may notice in the SixBit 2.0 import many fields can be entered through either an ID or a Name.  For example, each Origin Template has a name, but internally SixBit also keeps track of it by a number.  When importing from a flat file, the Origin Template can be specified by mapping the internal numeric identifier to the Origin Template ID field, or by mapping the name to the Origin Template Name field.  Any destination field that has an ID/Name pair of input fields works the same way.

The internal number is the more reliable identifier since it will never change, however, the name is more common and easier to find.  Users are not expected to know the internal identifiers of a field, but they are exportable.  In scenarios where data is exported, changed, and then reimported, the unique identifiers will be more reliable.


Picture work relatively the same as they did before with a few minor changes. The new name of the Pictures column tab in the CSV is now “Path”. Auto mapping will work if the name is set to PicturesPath or just Path.  You can still use a semi-colon (;) to separate multiple pictures on an import as well

Mapping & Item Templates

Upon upgrading you might find some of your mapping files broken. No problem, to fix this issue just do another import of your CSV and re-map fields to their respective counter parts and save your map file again. Like previously stated, naming on columns has changed slightly but they should still be relatively close to what they were before.

If you have an item template saved you can also still define that in your CSV and whatever fields aren’t being mapped off of the map file will look to the item template for the values.

Importing Variations

Importing variation items has changed slightly.  In versions prior to SixBit 2.0, the Parent Variation ID and Variations ID fields were used.    Now for each variation of the item you must create a variation row that contains a value in its "External ItemID" field so SixBit will know which item the variation is associated with.  Each variation record must also contain a unique SKU so the variants are uniquely identifiable.  See the example below.  The first row is the master item record, and the remaining rows are the variation records.  The master item record and each of the variation records has the External ItemID field filled in.   

External Item ID




Use Variations

Variation In Use

eBay Category1



Qty to List




Keep Calm And…


































Updating Inventory

In versions prior to SixBit 2.0, the only way to import inventory was during an Item import.  This was very limiting because it only allowed the user to specify inventory and supplier information when creating new items.

In SixBit 2.0, a much more robust and separate inventory import process has been created.   Rather than updating item and inventory information in the same import, separate imports are required.  The first import will update the item data and the second import to update the inventory.   This allows for much more control over the inventory update. 

When updating Inventory, you must specify an Action.  Actions include: Add, ReconcileTo, Remove, Set & Shrink.  For a more indepth look at the rules regarding updating inventory please see the User’s Guide: Click Here to Access Updating Inventory from our User's Guide

Was this answer helpful?

« Back

© 2024 SixBit Software. All rights reserved.