Postman collection
Customs Read

pixiReportItemsWithMissingCustomsInfo

Returns items that are not yet tagged with the system tag `AtlasData`, including master data and customs fields, paged by `ItemKey`.

Lists items whose customs information has not been marked as complete yet.

  1. The ID of the system tag AtlasData (tag type 1, IsSystemTag = 1) is looked up in Tag.
  2. All items that have no assignment of this tag in TagMatch are selected.
  3. Only items with ItemKey greater than ItemKeyStart are returned.
  4. The result is sorted by ItemKey ascending and limited to Rowcount rows.

For each item the call returns master data (name, supplier, numbers, EAN, sales price, VAT level, weight and dimensions), all assigned item tags as a pipe-separated string, the ABC classification and the current customs fields (tariff number, country of origin with ISO2 code, tariff text, previous process).

Paging: pass the highest ItemKey of the previous page as ItemKeyStart to get the next page. Start with 0.

Notes

  • "Missing customs info" is defined only by the absence of the AtlasData tag. The customs columns of returned items may already be filled; items with empty customs fields are not returned if they carry the tag.
  • If the system tag AtlasData does not exist, the tag ID is NULL, the NOT EXISTS check never matches and all items (above ItemKeyStart) are returned.
  • The row limit uses SET ROWCOUNT; Rowcount = 0 removes the limit.
  • Inactive items are included; check the Enabled column.
  • All reads use NOLOCK, so uncommitted data may appear.
  • ItemTAGs and ABC are computed per row by scalar functions, which can be slow for large pages.
  • The column Heigth is spelled as in the database.

Tables used

Tag · Read TagMatch · Read items · Read Countries · Read
SQL object:
dbo.pipiReportItemsWithMissingCustomsInfo
Updated at 2026-10-30