Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sealType should not be mandatory #128

Open
nissimsan opened this issue Dec 3, 2021 · 2 comments
Open

sealType should not be mandatory #128

nissimsan opened this issue Dec 3, 2021 · 2 comments

Comments

@nissimsan
Copy link
Contributor

I've never seen seal type specified on a BL - it shouldn't be mandatory.

@HenrikHL
Copy link
Contributor

HenrikHL commented Dec 7, 2021

Hi @nissimsan,
I asked our P7 team about this and it is correct that it is not printed on a B/L. It is though still required to be registered in the carrier system and this is the reason it is mandatory.

@cmsdroff
Copy link
Contributor

Im also querying that sealType should not be mandatory, i'm looking specifically at implementing the Shipping Instructions from a Shipper/Forwarder perspective.

When the container is loaded all that is reported back from the load site is

  • Container Number
  • Seal Number
  • Weights etc depending on type of business

The actual type of seal used (provided by carrier to haulier for carrier haul) is not reported, so asking the Shipper to provide this in the Shipping Instruction process I feel maybe problematic to achieve, without the inevitable instruction 'alway a bolt seal so default to that'

"sealType":{
                           "type":"string",
                           "description":"The type of seal. This attribute links to the Seal Type ID defined in the Seal Type reference data entity.\n- KLP (Keyless padlock)\n- BLT (Bolt)\n- WIR (Wire)\n",
                           "enum":[
                              "KLP",
                              "BLT",
                              "WIR"
                           ]
                        }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants