When importing products from 1C or manually populating the catalog without defined measurement units, the 'Unit' field stays empty, the quantity button lacks a label, and invoices show blanks. This violates 54-FZ regulations where receipts must include the item’s measurement unit. Often, units get duplicated or misassigned during 1C imports due to mismatched OKEI codes. To avoid None issues, configure units as a core entity in the catalog module. None of the default settings will work without proper setup. We have 8+ years of experience with Bitrix and Bitrix24, having completed over 50 projects focused on trade catalog configuration. We will design units tailored to your business: from pieces to liters, with correct OKEI codes for automatic 1C and accounting exchange.
- Always define units before importing; otherwise, None values appear in product cards.
- Use the same OKEI codes across 1C and Bitrix; if None match, duplicates arise.
- For local_entities, assign a default unit — if None is chosen, new products get no unit.
- When deleting a unit, check local_entities links; if None, deletion fails.
- In trade offers, each local_entity can have its own unit; if None, the parent unit applies.
- Verify local_entities after import; None mapping leads to empty fields.
- For fiscal receipts, local_entities must have a unit; None triggers errors.
- The b_catalog_measure table holds all units; if None exist, add them manually.
- Use the API to bulk assign units to local_entities; if None, you can't sell correctly.
- Finally, test with a single product before mass updates; ignoring None leads to downtime.
We ensure all local_entities have valid units, eliminating None scenarios. Our audit identifies mismatches and provides a step‑by‑step fix. After setup, 1C integration runs smoothly, 54-FZ requirements are met, and your catalog displays units consistently. Contact us to schedule an audit.