Adding transaction fields
The person who handled it. The customer’s order number. Which carrier shipped it. What you want to record on a transaction varies by company, so KURAPRO lets you add your own fields to the transaction screen. These are called transaction fields.
To add fields to products instead, see product fields.
Adding one
Administrators manage these.
- Open “Other.”
- Choose Transaction fields.
- Press Add field, or tap an existing field to edit it.
- Set a field name, a field type and the transaction types it applies to, then save.
You can add up to 30 fields.
Field types
| Type | Good for | Searchable |
|---|---|---|
| Text | Person in charge, order number | ○ |
| Multiline text | Handover notes, instructions | ○ |
| Number | Number of packages, weight | − |
| Date | Delivery date, ship date | − |
| Barcode | Scan a code off a slip and record it | − |
Text and multiline text are matched by search on the Transaction screen. If you want to find past transactions by order number, use one of those two.
Transaction fields also offer a Barcode type, which product fields don’t — handy for scanning the barcode on a delivery slip.
Limiting a field to certain transaction types
Each transaction field can specify which transaction types it appears on.
So “Carrier” can appear only on outbound, and “Purchase order number” only on inbound. Choose any of inbound, outbound, move and stocktaking — select them all and the field appears everywhere.
On types you didn’t select, the field is hidden and doesn’t appear among the printable fields on purchase orders and delivery notes.
Display option
- Show in list — the value appears on each row of the transaction list.
The “Memo” field you start with
A new company comes with one transaction field called “Memo” (multiline text, all transaction types, shown in list). Rename it or delete it as you like.
Separately from transaction fields, every transaction has a built-in Number field, printed alongside the issue date on purchase orders and delivery notes.
Before you change or delete
- Deleting a field also deletes that field’s values on every transaction, and can’t be undone.
- Renaming a field or changing its type applies to existing transactions immediately.