Discuss a project

QQDEV · KYRGYZSTAN · REMOTE

Sold a box, shipped a piece: check your CRM product units

Why identical quantities can describe different orders, and how to check units before exchanging data with an accounting system.

Published

3 min8

An illustrative example: a salesperson records one package, while delivery sees a quantity of “one” and prepares one piece. The number stayed the same. The order’s meaning changed considerably.

A product line needs more than a name and quantity: its measurement unit matters. Before automating, agree exactly what you sell and which units each system uses.

Separate the product from how it is sold

Describe a training product: can customers buy individual pieces, complete packages or both? State which unit the agreed price applies to and how package contents are recorded.

Do not expect “box” in a product name to convert quantities automatically. The selected solution must explicitly support and test any conversion rule.

For services, distinguish an hour, a session and a work package. A generic “service” label does not explain the included scope to a customer.

Check the Bitrix24 unit directory

Units are configured under CRM > More > Settings > CRM settings > Measurement units. Users with appropriate permissions can add and change them. The official instructions describe the procedure.

Check the actual unit in the product record and a training sale. Before changing an existing directory, establish which documents and connections depend on its values. Do not modify old orders in bulk merely to standardise labels.

Confirm features, interface and permissions for your edition and plan. A unit setting does not establish automatic package conversion.

Agree the exchange with the accounting system

If applications exchange data, document the mapping of product, unit and quantity. Who converts values, and where is the rule visible? What happens to an unknown unit?

For a company in Kyrgyzstan, check labels and codes against the particular accounting system and documents used. Classification examples in product documentation do not replace agreement on your exchange design.

Using training data, test a package, a single piece, changed quantities and a return if included in the workflow. Compare meaning on both sides, not merely a “successfully sent” message.

Review the result as customer and warehouse staff

Open the prepared document and delivery assignment. Is the item and quantity clear in both? If staff must call the author of every line, setup is not finished.

Record the rule in a short instruction and appoint a directory owner. New products should not receive a random unit simply because it is the default.

QQDev implements Bitrix24. The implementation page is a place to discuss product workflows and exchange checks. Bring an anonymised order line and explain what the buyer should physically receive.

← All blog posts