Slovakia postal addresses: why 123/5 is not flat 5

A checkout designed around British addresses often expects a single house number, a street and a town. That structure can quietly damage a perfectly usable Slovak address. A slash becomes an apartment separator, a leading postcode zero disappears, or a rural customer is forced to enter a street that does not exist. The fix is to preserve the customer’s meaning through the dispatch process and check uncertain details against the right postal information.

What do the numbers on either side of the slash mean? #

Slovakia’s Ministry of Justice explains the distinction in its official company-register portal manual. In the example 123/5, 123 is the súpisné číslo, the building registration number, and 5 is the orientačné číslo, the orientation number. The example explains the fields; it does not prescribe a real address for your customer. Its practical lesson for a UK shop is that a slash does not reliably separate a house from a flat.

If the buyer supplies a combined number, keep it together unless the booked provider gives you a supported way to map it into separate fields. Do not discard the part that seems unfamiliar or move it automatically into apartment. A label may still look plausible after that change, making the error harder to spot during packing. Ask the customer which is the complete official address when the saved fields are ambiguous.

Keep the same approved number in the booking and the visible address. A handwritten addition on the carton does not repair structured data already sent to a carrier. Likewise, do not correct only the packing note while a later export continues to use the original order fields. Where your shipping integration cannot represent the confirmed address, resolve that mapping before releasing the order to a sender.

How can a postcode lose a digit without anyone noticing? #

The UPU’s Slovakia country sheet defines a five-digit postcode, displayed with a space after the third digit and placed before the delivery-office name. Its official Poprad example uses 058 06. If a system treats the unspaced postcode as a number, it can turn 05806 into 5806. Adding a display space later cannot recover a zero that has already been lost. Store and transfer the postcode as address text.

This is especially worth checking in spreadsheet handoffs. Look at the imported value, the export and the final label, rather than assuming the screen presentation matches the underlying data. Keep the country field separate and verify that Slovakia remains selected throughout the booking. A correct five-digit string with the wrong country selected can still produce a shipment for the wrong postal network.

Use Slovenská pošta’s official PSČ search for the actual street and municipality. PSČ is the Slovak term you will see for a postcode. Keep the result with the order if you are resolving a discrepancy. The directory check answers a postal-routing question; it does not establish that the buyer lives there, that a particular person can receive the parcel or that a private courier supports every receiving arrangement.

Why might the customer’s village and postal town differ? #

The UPU country sheet includes a rural example where the physical locality is followed by a different delivery office. It also covers localities without a street, using the locality name and house number instead. A UK form that requires a conventional street and forces the same locality into every town field cannot faithfully describe all those examples. Review the full confirmed address rather than rejecting it because it does not resemble a city address.

For these orders, preserve the physical locality and postal-routing locality in the appropriate address lines. Ask the buyer to confirm the complete postal version if your system holds conflicting values. Do not replace the delivery office with the municipality found by a map search simply because the map result seems geographically closer. A map answers where a point is located; postal data answers how the item is routed.

If no street exists, avoid inventing one just to make a required field pass. Explain the actual address structure to the booking provider and use its supported format. A temporary workaround should have a recorded reason and an owner, so the next colleague does not silently overwrite it. Keep the customer’s address available in its original line structure while you resolve how the carrier expects the fields.

Which checkout cases should your shop accept or hold? #

Use these cases when reviewing your own workflow with whoever maintains the order export. You do not need to rewrite the shop before accepting a Slovak customer, but you do need a reliable route for legitimate exceptions. Show the packer the final approved address and make unresolved cases visibly pending. Otherwise a well-intentioned person may shorten the number or add a guessed street to get the parcel out of the queue.

What if the address exists but the lookup disagrees? #

Slovenská pošta’s June 2026 address-register article explains that it takes addresses from Slovakia’s official register into its systems for sorting, delivery planning and postcode assignment. It asks municipalities to improve incomplete register records and explains that poor address data also makes collection locations harder to find. That is useful context when a customer supplies a new or unfamiliar building. A missing lookup match deserves investigation rather than an automatic accusation that the buyer entered false details.

Ask the customer for their complete current postal address and the specific field that differs. Compare it with the postal directory and ask the provider how to handle a confirmed new address. Record the outcome so you do not repeat the same investigation on a reorder. Do not promise that you can update an official register or guarantee delivery merely by accepting a customer’s map screenshot.

A useful internal note is precise: which number was confirmed, which postcode/locality result was used and whether the provider approved the field mapping. A note saying address checked gives the next person no evidence to work with. Limit access to the records to people who need them for the order; the point is a usable dispatch trail, rather than making customer address screenshots circulate across unrelated conversations.

What does fixing the data before packing protect? #

Consider only the handling component of a possible second dispatch. AirPost’s shared pricing data checked on 19 October 2026 recommends €3.00 for parcel handling, with a platform component of €0.85. That gives €3.85 before carrier transport, packaging and border costs. A separately booked replacement using the same assumptions would bring the two-dispatch component to €7.70. Actual fees depend on your sender and bookings.

That arithmetic is a reason to approve uncertain address data before release, not a claim about how often Slovak parcels fail or what a return costs. Do not add the platform component twice to a shipping quote that already includes it. Keep the operational cause recorded as well: number truncation, postcode conversion and unsupported pickup addressing need different fixes, even if all three eventually appear as an undelivered parcel in your sales report.

Through AirPost’s fulfilment model, a verified sender can hold your agreed stock and accept, pack, label and drop off your shop orders. You can agree an address-approval rule with a UK sender for direct exports. If you later assess stock held in Slovakia, keep the same customer-address care while separately arranging the batch import and applicable registrations. A different packing location does not repair data lost in your checkout.

Address approval and customs approval are separate dispatch decisions. The UK-to-Slovakia customs guide covers the import handoff for direct shipments from Great Britain. A complete postal address should flow into the required recipient fields, but it does not replace the commercial invoice, product description or the representation arrangement used by the clearing operator.