Customs information
Customs information is generally required for shipments that cross a customs border, such as exports from Norway, imports to Norway, and certain domestic shipments that require Norwegian Goods in Transit (NVIT) information.
Customs scenarios
Depending on the shipment and service, customs information can either be submitted as part of a booking request or managed separately through the Customs API. Customs data is transmitted electronically by Bring to the relevant customs authorities where applicable.
Which API should I use?
Booking API
Use the Booking API when customs information should be submitted together with the booking of the shipment. This is the recommended approach for single shipment services when customs data is available at the time of booking.
Typical use cases
- Creating a shipment and customs declaration in one step
- Shipments requiring Norwegian Goods in Transit (NVIT)
- Services that support customs information as part of the booking request
Customs API
Use the Customs API for shipments to be declared with Bring when customs declarations need to be managed independently of shipment booking. Testing and onboarding is required before production use, as customs information is forwarded to customs authorities.
Typical use cases
- Customs data is not available when the shipment is booked
- For bulk shipments requiring customs data for multiple parcels
What customs information is typically required?
Depending on the shipment and service, customs information may include:
- Importer and exporter information
- Item descriptions
- Quantity and weight
- Value and currency
- Country of origin
- Commodity (tariff) code
- Additional customs-related information such as consent, VOEC, IOSS, or product identifiers where applicable
The exact requirements depend on the shipment type, destination, and service being used. Refer to the relevant API documentation for complete request examples and field definitions.