Skip to the content
FreightParse

The Stratech Shipment import dossier, from the invoice and packing list

Stratech Shipment takes a DMS import declaration as one JSON request. FreightParse writes that request from what it read on the supplier's invoice and packing list, checked against the field table Stratech publishes, and leaves the declarant's choices to the declarant.

Forward one shipment's e-mail todocs@freightparse.com

From your work address, with the invoice and packing list as PDFs. In the first reply you accept the trial terms with one button; then that shipment is read, and the goods lines come back in the same thread, usually within 5 minutes. No reply within 10 minutes? Check your junk folder, or write to danil@freightparse.com. Free for 14 days, about 20 pages a day.

Rather accept the terms before you send anything? Use the button above. Or upload in your browser (read in the cloud), or ask a question first.

The request, as it is written

"goodsItems": [
  {
    "sequenceNumber": 1,
    "description": "24IN SQUARE STEEL SLAT FOLDING TABLE",
    "goodsItemType": {
      "hsCode": "94032000",
      "taricSubHeading": "50"
    },
    "countryOfOrigin": "CN",
    "goodsMeasure": {
      "grossWeight": 7755,
      "netWeight": 6957.5
    },
    "invoiceValue": 20350,
    "packaging": [
      {
        "quantity": 275,
        "typeCode": "CT"
      }
    ]
  },
  ...
Goods item 1 of the request for the public test document on the front page. The commodity code 9403200050 is split into hsCode and taricSubHeading; it is the US code the invoice prints. The package type CTNS is not a code from list CL017, so it is listed to check and not written. Three such requests, with every value's page: freightparse.com/dms/.

What is proven for Stratech Shipment

What is proven, and what is not
What Stratech publishesThe field table of the DMS import (40-00): 131 rows, each with its JSON path, type, length and range (Stratech knowledge base). The OpenAPI file itself is on each customer's own Shipment environment and is not public.
What FreightParse writesThe whole request body for POST /api/Import/Importdossier: the dossier number, the goods items (description, commodity code split into hsCode and TARIC subheading, origin, gross and net weight, invoice value, packages), delivery terms, invoice currency and total. The importer is your Shipment address book's code. doSubmitWhenValid is always false.
What it is checked againstEvery field path, type, length and range in the table Stratech publishes, read on 11 October 2026. Not against the OpenAPI file, which is not public.
Posted to Shipment by a deskNot yet. No request has been posted to a Shipment environment so far.
What comes back by e-maillines.xlsx and lines.csv with their sources, not yet the Shipment request. That is written from the same reading by FreightParse's batch tool, so for a test of it, say so in your first e-mail and give your importer code.

How it fits your work in Shipment

The request saves a dossier in Shipment; it does not lodge it. Your declarant opens the dossier, fills in the procedure, the office and the other choices (or fixes them once for your desk), checks the goods items and lodges as always.

Posting the request takes your own Shipment credentials: an ERP client made under Beheer, Instellingen, ERP Koppelingen. FreightParse never holds them and sends nothing to Shipment.

How well it reads

On 20 invoices and packing lists it had never seen, scans included, it got 97.5% of the goods-line fields right and under 1% wrong; the rest were left empty and marked for a person. Every value comes with the page and the text it was read from. How it was tested.

Where your documents go

Read in Google's EU region, not used for training. A request flagged by Google's abuse checks may be kept up to 90 days, in the EU. FreightParse keeps no copy on its server. On the e-mail route, the e-mails are deleted from our mailbox within 30 days.

The data processing agreement comes with the trial. A desk that may not use any cloud can use the local reader instead: text PDFs only.

Questions

Is this made or approved by Stratech?

No. It is the request Shipment's own API takes, written to the field table Stratech publishes. Stratech has not reviewed it, and FreightParse is not affiliated with Stratech.

What happens to the commodity code?

It is read as printed. Ten digits fill hsCode and the TARIC subheading; eight digits fill hsCode and the TARIC part is listed to check. A code is never padded or guessed.

FreightParse is not affiliated with Stratech. Stratech Shipment is theirs and is named here only to say what the file is for.

Other declaration software

SoftwareWhat FreightParse writes for it
Riege ScopeExcel or CSV for Scope's item import (module C89)
Beurtvaartadres ShipmentManagerThe same import dossier request as Stratech Shipment
StreamLinerYour layout, from one example file of yours
FitonYour layout, from the field list of your import
Customs4trade CASThe CustomsShipment document, checked against the published schema
Other softwareAny other: the layout your software imports, from one example file

No desk has imported a FreightParse file into any of these yet; each page says what is proven. FreightParse is not affiliated with any of these vendors.

Try it on one shipment

Forward one shipment's e-mail and accept the trial terms with one button in the reply. The goods lines come back in the same thread, usually within 5 minutes.

Forward one shipment's e-mail todocs@freightparse.com