Custom Fields
Every courier business collects something the default order form was never built for. A receiver’s ID number, a cage count, a customer’s account code, a driver’s licence expiry. Custom fields let you add those to customers, drivers, and orders in Onro, pick who sees them, and make them required where it matters.
Deliveries Optimized
Courier Companies Served
Countries Supported Worldwide
Attach Data to Customers, Drivers, or Orders
Every custom field belongs to one of three things: a customer, a driver, or an order. That choice decides where the field shows up and which record the answer is stored on. Customer fields can apply to business accounts, individuals, or both. Driver fields live on the driver’s profile. Order fields ride along with each order from creation to delivery.
Eleven Types, From a Checkbox to a File Upload
A field can be a drop-down list, a yes/no toggle, a whole number, a decimal, free text, a date, a date and time, an email, a phone number, or a file upload with the formats and maximum size you allow. There is also a JSON type for structured data, enabled from our side when a setup calls for it. Email and phone fields only accept valid values, so bad data gets caught at entry instead of at dispatch. One thing to know before you start: a field’s type is locked once it is created.
Ask at the Right Moment in the Order
Order fields have a stage. Set it to Order Creation and the field appears right after the service options when the order is placed. Set it to Pickup and it sits inside the pickup address details. Set it to Dropoff and it sits with the drop-off address. A gate code belongs at the drop-off. A packing-list reference belongs at creation. You decide, per field.
Choose Every Screen It Appears On
Each field has its own visibility switches, one per screen. An order field can show on customer order creation, in the customer’s order details, in the dispatcher’s order creation and order details, in the driver app’s order details, and on the public tracking page. Driver and customer fields add the driver profile, the customer profile, and the registration forms to that list. Turn on only what each role needs. The dispatcher sees the internal reference. The receiver on the tracking page does not.
Required, Editable, or Both
Toggle Required on and the order, driver, or customer record cannot be saved without an answer. Toggle Editable on and the customer or driver can fill in and change the field themselves. Editable is also what puts a field on the customer or driver registration form. And after an order is placed, customers can still open it in the web app and update its custom field data under Order Info, so a wrong reference number does not have to become a support ticket.
Custom Fields Work in CSV Imports Too
If you bring orders in by CSV, your custom fields come with them. Add a column named CustomField followed by the field key for creation-stage fields, Pickup CustomField for pickup fields, and Dropoff CustomField (or Delivery CustomField on pickup and delivery orders) for drop-off fields. Drop-down fields take the option key, and date fields take a timestamp. That is the entire rule set, and it works from both the dispatcher panel and the customer portal.
Built in the Admin Center in a Few Clicks
Go to Admin Center, then Settings, Data Management, Custom Fields, and click New. Pick the field type, choose a data type, and give it a label. Onro sets the key from the label. Add a tooltip so people know what to enter, set the stage for order fields, flip the Required and Editable toggles, and tick the screens it should appear on. You do not need a developer or a ticket, and the field is live for your team the moment you save.
Start Your Free Demo Today
See how custom fields put the data your operation runs on right inside every order, driver, and customer record.