Rongta scales: PLU codes not uploading and sync failures — Paloma365 Classic (Windows POS)

"5-digit PLUs don't get onto the scale", "the scale shows a price 10 times higher/lower than the POS", "sync with the scale doesn't go through" — this article covers common problems with syncing Rongta scales with the POS, separately from the basic connection setup.

For connecting scales, uploading products and selling weighted items, see Scales and barcodes. This article is about what to do when the connection is already set up but the data still does not match.

Long PLU codes (5 digits) are not uploaded to the scale

Paloma365 automatically assigns a PLU code to weighted products, and for some products it turns out 5 digits long. On some Rongta scales such codes are not uploaded or not read by the scale, even though shorter PLUs work fine on the same scale.

First check the POS version and the scale driver. For Rongta scales with the "Новый" (new) driver (RLS1100 generation), the current POS version uploads PLUs of up to 6 digits; older versions sent codes longer than 4 digits to such scales incorrectly. If 5-digit codes do not reach a scale with the "Новый" driver, update the POS (see Install and update) and upload to the scale again.

What you can do:

1. Use short PLUs where possible — up to 4 digits is recommended (3–4-digit codes are commonly used).
2. If there are only a few products with a long PLU — manually shorten the PLU code of those products in the Warehouse > Guides > Items guide (/warehouse/guides/s_items), save, then upload the products to the scale again (see Scales and barcodes) and check whether the product appears with the new code.
3. If PLUs were changed before at another point of sale with the same type of scale and 5-digit codes worked there — the issue is most likely the specific scale model/firmware, not a rule that "5 digits never work". Find out the exact scale model (usually written on the label on the underside of the device) and write it here — the specialist will need to re-check for your specific model.

This is a working recommendation from support, not a universally confirmed solution for all Rongta models — if shortening the PLU did not help, include the exact scale model in your request.

The POS does not recognize a label printed by the scale

The flip side of the same topic: the PLU was uploaded, the scale printed the label, but the POS does not accept it.

A weighted-item label is structured like this: first the prefix (the weight prefix, 22 by default), then the product code, then the weight or quantity. The POS parses such a label in one of two modes — in one, 5 digits are allotted to the product code, in the other 4 digits, and the rest of the string is read as the weight. The mode is set in the POS settings, and the client does not change it: if labels are printed with a code of a different length than the POS expects, the weight ends up in the wrong place.

What it looks like on the POS:

• "Error while scanning the barcode for supermarket: …" — the POS read part of the label as the weight, but it is not a number. This almost always means the product code length does not match the parsing mode. Send this text in full (it shows exactly what was read) — a specialist will check the mode against the format of your labels.
• "… special symbols are included! Check the correctness of a barcode!" — the scanned code contains extraneous characters: usually the scanner is set up incorrectly or the label is damaged.
• "Item is not by weight..." — the code was recognized, but the product is not marked as weighted in the guide. Check the item card.

So when reporting "the label from the scale is not read", it helps to attach the exact message text and a photo of the label right away: they show both the mode and the code length.

The price on the scale differs from the POS by a factor of 10

Symptom: for example, a product costs 158 tenge at the POS, but the scale shows 1580 (or the other way round). This usually means the scale is working with old or incorrectly uploaded data.

What to try:

1. Upload the products to the scale again (the "Прогрузить весы" (upload the scale) / "Upload PLU" button, depending on the model — see Scales and barcodes).
2. Restart the scale itself (turn the power off and on) and repeat the upload.
3. Check whether the label was printed after the last upload — an old label keeps the old price even if the data in the scale has already been updated.

"Sync with the scale doesn't work"

If the scale is connected over the network (Ethernet) and the upload/sync does not go through:

1. Check that the network cable is firmly plugged in at both ends (into the scale and into the router/computer). A lit indicator on the connector does not always mean the cable actually carries data — if in doubt, try replacing the cable.
2. Check the scale's IP address — it may have changed (see the instructions for checking the IP address in Scales and barcodes).
3. If several scales have the same IP address, connect and upload them one at a time; you do not need to change the IP settings for this.
4. If that does not help, write here, stating the connection type (Ethernet) and what you have already checked: a specialist will continue the diagnostics.

Open question: keeping the entered code during batch packing

A separate request that comes up sometimes: when packing a large batch of the same product, not having to re-type the PLU code on the scale every time — the code should be "remembered" on the scale screen between weighings. At the time this article was prepared there is no ready solution for this scenario — if you have this need, describe it here together with the scale model, and a specialist will take the question up.

Common problems

• A product is not uploaded to the scale — most often the PLU is not filled in on the item card, or the PLU is too long for this scale model (see the section above).
• The price/name on the scale does not match the POS — upload the scale again from the same POS/account the upload usually comes from, and make sure the label was printed after the last upload.
• Sync hangs or does not start — check the physical connection (cable, IP address), see the section above.

FAQ

Can I simply always use PLUs shorter than 5 digits?

This is the most reliable option while you have few weighted products: 3–4-digit PLUs cause upload problems less often than 5-digit ones.

Are 5-digit PLUs not supported by Rongta scales at all?

There is no hard rule — there are confirmed cases where 5-digit PLUs worked fine on other Rongta scales of the same client. The problem apparently depends on the specific model/firmware — check with a specialist, stating the scale model.

Where do I shorten a product's PLU code?

In the dashboard: Warehouse > Guides > Items (/warehouse/guides/s_items) — open the product and change the code in the corresponding field.