Customs declarations within 7bridges platform

This guide outlines what is required to facilitate customs declarations that are not handled in the paperless trade flow with integrators.

1. The order and movement demand need to be sent via API. There are additional constraints to data passed there:

   1. The order needs to have an additional address field declarant with the data of a declarant that will be sent for the customs declaration. Fields accepted are as always for all the addresses, so:

      "declarant": {
          "name": "string",
          "company": "string",
          "phone": "string",
          "email": "string",
          "street1": "string",
          "street2": "string",
          "city": "string",
          "state": "string",
          "postal_code": "string",
          "country": "string",
          "vat_number": "string",
          "eori_numbers": [
              "string"
          ],
          "type": "business"
      }
      

   2. Additional fields are required for these addresses (except those mentioned in API documentation, which are: street1, city, postal_code and country)

      1. declarant
         1. name
         2. eori_numbers (GB, DE, PL) or vat_number (US)
      2. seller
         1. name
         2. phone
         3. eori_numbers (GB, DE, PL) or vat_number (US)
         4. state (DE)
      3. sender
         1. name
         2. phone
         3. state (DE)

   3. At last, movement demand request needs to have a requires_export_declaration flag set to True
      
      

2. With the shipments flow on the platform, two different use cases are supported
   1. First flow supports sending export declarations after purchasing a shipment:
      1. In this scenario, there’s nothing much to be done, the shipment needs to be simply purchased. After that declaration will be sent
      2. A tracking code will be sent with the rest of the data in order to allow easy identification of a package based on the export declaration
      3. If the declaration ends up being successful, the required documents will be added to the final page of a purchased shipment
      4. In case of errors, it's advised to contact support@the7bridges.com.
   2. second flow supports sending export declarations before purchasing a shipment:
      1. In this scenario, we proceed as usual with the booking flow until the customs page. We used to require the package identifier to be set on packages, though currently, the shipment reference with an index number is used instead in order to identify packages in customs
      2. Just after the customs page is confirmed, the export declaration will be sent and the flow will be paused. Declarations will have to be confirmed by AEB before the shipment can proceed
      3. Keep on checking the Attention tab to monitor the status of this shipment
      4. After the declaration comes back successful, the shipment can be purchased, the relevant identification ID (e.g. MRN) and required documents will be immediately visible before purchase
      5. Again, in case of errors, it's advised to contact support@the7bridges.com.