Marketplace Connectors
Marketplace connectors publish governed Actualog product data to external commerce channels.
Actualog keeps marketplace requirements outside the Category itself. A Category describes what the product is and how its logistics shape is resolved. A channel profile decides which resolved Product Pack values are required for a destination.
Logistics requirements
Marketplace logistics must come from the selected Product Pack and its resolved Logistics Shape Profile. The Category profile editor is shape-specific and intentionally does not expose connector-only rows such as shipping templates or logistics attribute sets.
- Product attributes describe the base product.
- Product Pack overrides describe a measured packed trade unit.
- Package values describe reusable physical packaging.
- Formula values are allowed only through approved shape recipes.
- Not-applicable and blocked-until-packaging states must remain explicit.
Do not send zero weight or fake dimensions when a channel asks for packed logistics. Preflight must report the missing Product Pack or Package data.
Channel examples
| Channel | Logistics behavior |
|---|---|
| Google Merchant | Product measurements and shipping measurements are separate; shipping values are optional unless the channel profile requires them |
| Yandex Market | Physical offers require packed weight and dimensions in the expected units |
| Wildberries | Physical offers require packed dimensions and gross weight |
| Alibaba ICBU | Physical postings use package weight, package dimensions, logistics properties, and shipping templates from the channel schema |
| AliExpress | Physical postings use package weight, package dimensions, and freight template fields from the product posting schema |
| Amazon | Required logistics fields must be read from the Product Type Definition schema for the selected marketplace and product type |
| Ozon | Must stay disabled until the official Seller API contract snapshot is verified |