Skip to content

Custom Columns

Your inbound orders can carry fields that only your company needs: a supplier reference, a temperature flag, a priority. These are custom columns. You define one once, and it appears on every new inbound order.

Custom columns exist for inbound orders. Outbound configuration holds order numbering only.


  1. Open Configurations → Inbound Configuration in the sidebar
  2. Go to Custom Columns and click Add column
  3. Enter the Label, the name your team reads on the form
  4. Choose the Type
  5. Set what the type needs, such as a maximum length or a list of options
  6. Turn on Required on every order if an order cannot be created without it
  7. Turn on Show as a column on the order list to see it in the list
  8. Click Create
Type The person enters What you can set
Text Free text Maximum length, 255 by default
Number A number Minimum, maximum, whole numbers only
Date A date from a picker
Yes / No A checkbox
Select One option from your list The list of options

The column appears on the order form above the Warehouse Items block, which stays last. Orders that already exist do not change, and they show the new column as empty.

You can change the label, and you can archive the column. You cannot change the type. The app freezes the type when the column is created, along with the key it stores values under. To use a different type, archive the column and add a new one.

A required column must have a value before an order can be saved, on a new order and on an edit.

  • A new order must have a value in every required column.
  • An edit checks every required column again, including one that was added after this order was drafted. The form marks the empty column before you submit.
  • A value that somebody cleared on purpose stays cleared. An edit never fills a column for you.
  • You cannot clear a required column.
  • An archived column keeps whatever it recorded, and it is not checked.

Turning a column required therefore reaches old drafts as soon as somebody edits one. Add the column before the busy season, not during it.

Add an option whenever you need one.

You cannot remove or rename an option that an order already used. A rename is a removal plus an addition, so the same rule blocks it. This protects your history: if the app allowed it, every order that recorded the old option would hold a value that no longer means anything.

Rename an option freely while no order uses it. When the wording of an option that is in use must change, archive the whole column and add a new one.


The two actions are not the same, and the app decides which one is allowed.

Archiving hides the column from new orders and keeps everything recorded.

  • New orders no longer show it.
  • Past orders still show it, read only, with the value they recorded.
  • The label, the type, and the options are kept, so an old value still makes sense.
  • You can bring it back with Restore. Its key is reserved the whole time, so nothing else takes it.

Deleting removes the column with no trace. Use it to undo a mistake: a typo in a label, the wrong type, a column added by accident.

The app refuses the delete as soon as any order recorded a value in that column, and tells you to archive it. Deleting a used column would rewrite your receiving history and leave those values with nothing to explain them.

There is no way to erase the recorded values of a column that was used.


A column with Show as a column on the order list turned on appears in the list, and you can sort by it. Sorting follows the type: numbers sort as numbers, dates as dates, and Yes / No sorts No first.

You cannot filter the list by a custom column yet.