Units of Measure
Procurement systems often expect standardized unit codes in the cart transfer — for example PCE for piece or KGM for kilogram. The connector supports a three-level system for managing these units.
Priority Order
The unit for a product is determined in the following order. The more specific setting always takes precedence:
1. Custom field on product (productOciMe) ← highest priority
2. System unit table (per OCI/cXML system)
3. System default unit ← fallback for all products
Level 1: Default Unit (System Fallback)
In the system configuration (OCI or cXML) under Tab: General, a default unit can be set. It is used when no matching unit is found either on the product or in the system unit table.
Recommendation: Enter the most common unit code in the product range here (e.g. PCE for piece).
Level 2: System Unit Table
In the Units of Measure tab of each OCI or cXML system, Shopware units can be mapped to the codes expected by the procurement system.
Example:
| Shopware Unit | Transfer Value |
|---|---|
| Piece | PCE |
| Kilogram | KGM |
| Litre | LTR |
| Metre | MTR |
This allows different systems to map the same Shopware units to different codes.
Level 3: Custom Field on Product
On the product itself, a packing unit can be set in the Custom Fields tab. This value overrides all other settings for this product.
Path: Products → [Select product] → Specifications → Additional fields → Agiqon OCI Product
Data field: productOciMe — available in the field configuration of the system.
- Default unit: For product ranges where almost everything has the same unit
- System unit table: For different unit codes per procurement system
- Custom field on product: For products with an individual unit that differs from the general standard