טעינת

Logistics

Actualog logistics support turns product facts, packaging facts, and channel requirements into usable values for package fit checks, catalogs, marketplace export, and external systems.

The model keeps separate responsibilities:

Record Responsibility
Product Technical product facts and attribute values
Category Logistics Profile Category-level rules that say which logistics values can be mapped, derived, blocked, or marked not applicable
Product Pack The concrete sellable or shippable unit, including quantity, package, packed overrides, and runtime provenance
Package Reusable physical packaging specification: type, external and internal dimensions, tare, capacity, and fit limits
Channel profile Connector-specific logistics requirements and unit normalization

This separation prevents fake dimensions. A pipe can be described by length and diameter, paint by volume and container, cement by mass and bag or pallet, software by no physical logistics, and live goods by transport handling and packaging requirements.

Logistics values

Actualog resolves logistics values as role-level facts: net weight, gross weight, outer length, outer width, outer height, diameter, volume, density, weight per length, units per pack, temperature range, ventilation, maximum transit time, and other supported roles.

Each resolved value also keeps provenance:

  • explicit Product Pack value;
  • Package value;
  • Product attribute;
  • approved formula;
  • sold quantity;
  • blocked until packaging;
  • not applicable;
  • missing or conflicting mapping.

Marketplace use

Marketplaces do not all ask for the same data. Actualog therefore keeps connector-specific requirements outside the Category itself.

Google separates product measurements from shipping measurements. Yandex Market, Wildberries, Alibaba ICBU, and AliExpress require packed physical values for physical offers. Amazon validation comes from Product Type Definition schemas. Ozon stays gated until its official Seller API field contract is verified.