Standards alignment
Portable shipping data, without pretending to be an eBL platform.
The immediate goal is to make reviewed document data interoperable with recognized trade and transport models. Alignment means deliberate field mapping and export semantics; it does not mean certification, legal transferability or endorsement by a standards body.
DCSA Bill of Lading
Internal transport-document fields are organized around shipping instructions, transport-document issuance and amendment use cases. GainingDocx is not claiming DCSA certification or carrier API conformance.
Review referenceUN/CEFACT MMT RDM
Parties, locations, consignment references, equipment, goods items and transport events are modeled for portable exchange rather than tied only to page layout.
Review referenceFIATA eFBL structures
The FIATA eFBL data standard aligns with the UN/CEFACT multimodal model. GainingDocx does not currently issue a secured FIATA eFBL or act as a legally transferable eBL platform.
Review referenceISO 6346
Container numbers are normalized and their check digits calculated. A valid number structure does not confirm ownership, physical condition, availability or current tracking state.
Review referenceUN/LOCODE
Printed location codes and recognizable port names are normalized against the published UN/LOCODE dataset used by the application. Users still confirm the intended terminal and routing.
Review referenceIncoterms representation
The workspace preserves the printed rule and location text where available. It does not infer cost, risk or customs obligations from an incomplete term and does not replace the governing sales contract.
Review referenceDangerous goods and IMDG
The current system performs document-presence, format and cross-document consistency checks on printed dangerous-goods values. The IMO IMDG Code contains substance-specific classification, packing, marking, documentation, stowage and segregation requirements. Those broader decisions remain outside automated approval.
Read the IMO overviewStandards and code lists evolve. Versioned mappings and conformance exports will be documented when released; until then, use the reviewed JSON/CSV/XLSX outputs as operational data, not as certification.