Product Extensions
The AgiqonConnector reads three additional custom fields from the Shopware product, specifically designed for OCI and cXML transfers.
Custom Fields on the Product
The fields are available when editing a product under Products → Specifications → Additional fields, spread across two cards:
| Field | Card | Technical name (data field) | Description |
|---|---|---|---|
| eCl@ss number | Agiqon OCI Product | productOciEClass | Classification number according to the eCl@ss standard (e.g. 19-09-08-01) |
| Packing unit | Agiqon OCI Product | productOciMe | Product-specific unit — used as the primary field ahead of the system and default unit in the default configuration |
| UNSPSC number | Agiqon Connector | productUnspsc | Commodity code according to UNSPSC |
The Agiqon Connector card with the UNSPSC number is created by the plugin itself as of 3.7.500 / 3.6.300 — on installation as well as on update. The fields of the Agiqon OCI Product card originate from the previous version and are only read by the connector; if they are missing, they have to be created manually as Shopware custom fields.
eCl@ss Number
eCl@ss is an international standard for the classification and description of products and services. Many procurement systems, especially in B2B and public procurement, expect this code in the transfer.
Usage: The productOciEClass data field can be used in the field configuration of an OCI or cXML system as a primary field or fallback for any transfer field — e.g. for NEW_ITEM-MATGROUP (OCI) or a corresponding cXML classification.
UNSPSC Number
UNSPSC (United Nations Standard Products and Services Code) is an international commodity classification. In cXML it is the usual domain of the Classification element; in OCI it can serve as the material group key.
Usage: The default cXML systems use it to fill <Classification domain="UNSPSC"> out of the box. In the field configuration, the productUnspsc data field can be used as a primary field or fallback like any other — in OCI for NEW_ITEM-MATGROUP, for example.
Product Packing Unit
The product-specific packing unit is read via the productOciMe data field. Whether it takes precedence over the system unit table (productSystemUnit) and the default unit (systemDefaultUnit) depends on whether productOciMe is configured as the primary field in the field mapping — which it is in the default configuration. There is no fixed, built-in precedence.
When to use: For products where the unit code differs from the general standard — e.g. a product sold in metres while the rest of the range is transferred in pieces.
More on unit logic: Units of Measure