Custom fields let you flexibly extend orders and products with individual information and display it directly in documents. This makes it easy to adapt order documents to industry-specific or internal company requirements. The possible use cases vary depending on the industry and customer. Here are a few practical examples that show what's possible with custom fields:
Wine trade: vintage, grape variety, alcohol content, or certification seal
Coffee or gourmet food trade: organic certification number, roast level, flavor profile
Electronics: series or model variants, technical specifications
Fashion: material composition, care instructions
Fireworks: legal information on explosive content
B2B business: internal references, project numbers, cost centers, or agreements at order level
Marketplace information such as the Amazon transaction ID
Note: Unlike information captured during picking, custom fields let you capture information that applies to all units of a product, so it doesn't have to be entered manually for every order.
Creating custom fields
Custom fields are managed in sets. Under Settings → System → Custom fields you'll find all existing sets. You can also add new custom fields to existing sets later on.
Below, we'll show you the basic steps for creating a new set. To do this, click Add set in the top right corner.
Here you can define the following information:
Technical name – Every set needs a technical name for unique identification, which always starts with custom_. This name cannot be changed later.
Position – If you have multiple custom field sets per entity, you can control the display order using this value. The lower the value, the further forward the set is displayed.
Label – The Label field corresponds to the name of the set as it will later be displayed in the entity. If the Translatable in all admin languages option is enabled, you can also maintain the name of the set in additional languages of your admin, besides your default language.
Use for – Here you select the entities for which the custom field set should be available.
Then save your set.
Now you can create custom fields further down.
First, select a field type here. Depending on the type, you can define additional properties. For the Selection field type, for example, you'll find the option further down to define various options. Regardless of the field type chosen, you can assign the name in the Label field below.
The technical name consists of custom, the name of the custom field set, and any name you choose for the field, each separated by underscores. This name also cannot be changed later. If you accidentally save your custom field without assigning a complete technical name, an error message will appear as soon as you try to fill in the field in an entity.
Once everything is filled in to your satisfaction, click Add to finish.
Filling in custom fields
You'll find custom fields in various places within the respective entities. Here's an overview:
Orders: Details tab → Custom fields section
Products: Specifications tab → Custom fields section
Batches: Custom fields section
Supplier orders: Custom fields tab
Customers: General tab → Custom fields section
Warehouses: Overview tab → Custom fields section
Suppliers: General tab → Custom fields section
Shipping methods: Custom fields section
If you haven't yet created any custom fields for the entity in question, your view will look like this. The link will take you directly to creating custom fields.
When custom fields are available, they're arranged in tabs by set:
Displaying custom fields in documents
For certain document types, you can select custom fields directly in the document configuration. This includes cancellation invoices, delivery notes, invoices, credit notes, and pick lists. There, you'll find a section for products and orders respectively, which you can use to control where which custom fields are displayed and in which order.
Product custom fields appear directly below the respective order line item, while custom fields for the order are summarized at the end of the document.






