Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
A truck has arrived at the warehouse. The goods are packed in boxes of 12 units and on pallets of 40 boxes, and each item has only one barcode — for a single bottle. The warehouse worker points the scanner at the box, and the system doesn't recognize it: one unit is received instead of twelve, stock balances "drift," and shipment slows down. You need the box to have its own barcode, the pallet to have its own, and for scanning to pull in the correct quantity. This is exactly what the "Generate Package Barcodes" processing is for: it creates barcodes for all packages of an item at once, without making you type in 13 digits by hand.
Important right away: this is a processing, not a document. It does not create accounting entries, does not generate e-invoices (ЭСФ) or waybills (СНТ), and does not post anything. Its result is records in the "Item Barcodes" information register. So below, instead of "Dr/Cr entries," you will see exactly which barcode rows appear and how they work later during sale and receipt.
1. Purpose
The processing bulk-generates and records barcodes for item packages (box, block, pallet) and their characteristics. One run closes out dozens or hundreds of items at once, instead of manually entering a barcode for each package in the item card.
2. Where to Find It
There is usually no single entry point in the main menu for this processing — it is opened from the item card or via the list of processings:
- From the item card:
Master Data and Administration→Items→ open the item → commandBarcodes→ in the barcode form, buttonGenerate/Generate Package Barcodes. - Via the list of processings:
All Functions→Processings→Generate Package Barcodes("All Functions" item is enabled inService and Settings→Settings→Parameters→ checkbox "Show 'All Functions' command").
Direct 1C navigation link (fastest way): copy the line below, click Service and Settings (☰ in the top right corner) → File → Go to navigation link, paste it, and click OK:
e1cib/list/Обработка.ГенерацияШтрихкодовУпаковок
2a. How to Find Out Your Release
Help (or menu ☰ → About the Program) → the "About the Program" window will open: it shows the line "1C:Enterprise" — the platform version, and a line with the configuration "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)". The first two digits are the edition, the rest is the release. The instructions below have been verified on 3.4.5.21; in nearby releases, button placement may differ slightly.
Barcodes work only if in Master Data and Administration → Section Settings → Warehouse and Delivery (or Marketing and Sales) the "Barcodes" checkbox is enabled. Without it, the generation commands will not appear.
3. How to Fill It In
The form is compact. Let's go through each field — why it's needed and what happens if there's an error.
| Field | Required | Why it's needed and the risk of an error |
|---|---|---|
| Item | ✔ Yes | The item for which barcodes are generated. If the processing was opened from the item card — already filled in. Get the item wrong, and the barcode will "stick" to the wrong SKU, and scanning will sell the wrong item. |
| Characteristic | Depends | Filled in only if the item is tracked by characteristics (color/size). Then the barcode is generated for a specific characteristic. Leave it blank with characteristics enabled, and the barcode won't be tied to the right variant. |
| Package (unit) | ✔ Yes | The whole point: you select which package to create a barcode for — "piece," "box (12 pcs)," "pallet (480 pcs)." The conversion factor to the base unit is taken from the package. Get the package wrong, and scanning a box will post the wrong quantity to stock. |
| Barcode Type | ✔ Yes | EAN-13 — the most common for retail; EAN-8 — for small packages; EAN-128 / GS1-128 and SSCC — for logistics (pallets, transport packages); Code39 — for internal labels. Wrong type — the scanner at the checkout or the mobile data terminal won't read the barcode. |
| Prefix / Series | No | The leading digits of the barcode. For internal barcodes in Kazakhstan, prefix 20–29 is used (the range for internal use, to avoid clashing with GS1 items from other manufacturers). Use someone else's prefix, and you risk a collision with another item's real barcode. |
| Quantity / Range | Depends | How many barcodes to generate (if creating a pool of serial codes). One is enough for a single package. |
| Check Digit | — | Calculated automatically using the EAN algorithm. Do not touch it by hand — the processing itself adds the 13th (or 8th) digit. Manual editing breaks code validity. |
Order of operations: select the Item → (if needed) the Characteristic → the Package → the Barcode Type → optionally set the prefix → click "Generate" → check the value in the table → "Write" (or "OK"). Only after writing does the barcode get into the register and start working during scanning.
4. Worked Example
Item: "Tan-Balyk Drinking Water 0.5 L", base unit — piece, VAT rate 16%. Two packages are set up:
- "Box" = 12 pcs;
- "Pallet" = 480 pcs (40 boxes).
A barcode exists only for the bottle: 4870001234567. The task is to create barcodes for the box and the pallet with internal prefix 20.
Steps:
- Opened the item card →
Barcodes→Generate. - Package = "Box," type = EAN-13, prefix =
20. Clicked "Generate" — got, for example,2000000000121. - Package = "Pallet," type = EAN-13, prefix =
20. Got2000000000138. - Clicked "Write."
What appeared (the "Item Barcodes" register):
| Barcode | Item | Package | Conversion Factor to Base Unit |
|---|---|---|---|
| 4870001234567 | Tan-Balyk Water 0.5 L | piece | 1 |
| 2000000000121 | Tan-Balyk Water 0.5 L | box | 12 |
| 2000000000138 | Tan-Balyk Water 0.5 L | pallet | 480 |
How this is reflected in money. The processing itself does not create accounting entries. But now, at receiving, the warehouse worker scans the box — 12 pcs go into the document. Sold 3 pallets at a price of 90,000 ₸ per pallet (excl. VAT), VAT 16%. The sale is posted by the "Sales of Goods and Services" document, which produces:
- Dr 1210 Cr 6010 — 270,000 ₸ (revenue from sales, 3 × 90,000);
- Dr 1210 Cr 3130 — 43,200 ₸ (VAT 16%);
- Dr 7010 Cr 1330 — cost of goods sold written off (at your recorded cost, e.g. 180,000 ₸).
Total due from the buyer: 313,200 ₸. The barcodes played their role at the scanning stage — thanks to them, the document was automatically filled with 1,440 bottles (3 × 480), rather than three "pallet" line items.
5. Operation Types
The processing does not have a separate "Operation Type" attribute, but in essence it can:
- generate a barcode for a single package of an item;
- generate barcodes for all packages at once of a selected item;
- generate barcodes taking characteristics into account (for items with color/size);
- create a pool (range) of barcodes by prefix and quantity;
- regenerate/fill in missing barcodes for previously set up packages.
6. What Is Generated Upon Writing
Once again: the processing is not posted, and it does not create Dr/Cr entries, e-invoices, or waybills. When "Write" is clicked, the following are generated:
- records in the "Item Barcodes" information register (link between barcode ↔ item ↔ characteristic ↔ package);
- the check digit value and the conversion factor to the base unit.
Afterwards, these barcodes are used by the documents "Purchase of Goods and Services," "Sales of Goods and Services," "Goods Transfer," "Goods Recount," and the cashier's workstation — during scanning, they substitute the item and quantity based on the package. It is these documents that then generate accounting entries (1210, 1330, 3310, 6010, 7010, 3130) and electronic e-invoice/waybill documents.
7. Printed Forms
The processing itself does not print any accounting entries, but printing is available from the barcode form and related places:
- "Label" — a sticker for the package with the barcode, name, and price;
- "Price Tag" — with the package barcode;
- printing via "Print Labels and Price Tags" (
Warehouse and Delivery→ print service) — there you can set a template, size, number of copies, and print labels for the entire pool of generated barcodes.
The barcode type in the label template must match the one you generated (EAN-13 to EAN-13), otherwise the label will display an unreadable code.
8. Common Errors
- "Barcode … is already assigned to item …" — the generated value coincided with an existing one. The cause is a third-party prefix or a repeated run. Change the prefix to an internal one (
20–29) or delete the duplicate in the "Item Barcodes" register. - "Package (unit of measure) is not filled in" — you didn't select which package to create the code for. Specify a package from the item's list of units.
- "Invalid barcode check digit" — the code was edited manually. Delete it and generate it again; the check digit is calculated automatically.
- "Barcodes are not used" / command is inactive — the functionality is disabled. Enable it in
Master Data and Administration→Section Settings→ the "Barcodes" checkbox. - The scanner reads the code, but quantity = 1 — you generated the barcode for "piece" instead of "box," or the package's conversion factor = 1. Check the package and its factor in the item card.
- The code doesn't read at the checkout/mobile data terminal — the barcode type is not supported by the equipment (e.g., EAN-128 on a basic checkout scanner). Regenerate it as EAN-13.
9. FAQ
(see the Q&A block below)
10. Related Documents
- What you're working from: the "Item" card and its packages (units of measure) — the source data for generation; the "Barcodes" setting in the sections.
- Where the results are used: the documents "Purchase of Goods and Services," "Sales of Goods and Services," "Goods Transfer," "Goods Recount (Inventory)," the cashier's workstation, "Print Labels and Price Tags." It is these documents that then generate accounting entries and e-invoices/waybills; the processing only prepares the barcodes for them.
How to Find Out Your Release
Help → About the Program (or menu ☰ → About the Program). The window shows the "1C:Enterprise" platform version and the configuration release "Trade Management for Kazakhstan, edition 3.4." Check against the release of this guide.
The guide was prepared for 1C:Trade Management for Kazakhstan, edition 3.4, release 3.4.5.21.
